xellos00 commented 2 years ago

Related: https://github.com/dsrvlabs/vatz/issues/157

Checklist
[x] New Feature for the SVC/Plugin
[ ] New Feature for CI/CD
[ ] Enhancement on Vatz
[ ] Others(etc, i.e. documentation,...)

1. Please describe, what it's about or related Problem with

We need to default plugin that we can use.

2. Describe the output that you are expecting for above

Default plugin that can be used as start to running on real node

@dsrvlabs/validator Please, leave a comments on this issue.

Child

Developments
- https://github.com/dsrvlabs/vatz/issues/98 (W/O SDK)
- https://github.com/dsrvlabs/vatz/issues/142 (w/ SDK)
- 121
- https://github.com/dsrvlabs/vatz/issues/118
- 122
- 127
- 156
- 162
- 173
Documentation
- https://github.com/dsrvlabs/vatz/issues/110

rootwarp commented 2 years ago

@xellos00 I'll leave here for SDK version ASAP.

rootwarp commented 2 years ago

@xellos00 For about SDK, I created PR here. https://github.com/dsrvlabs/vatz/pull/105

xellos00 commented 2 years ago

@xellos00 For about SDK, I created PR here. #105

@rootwarp I created new issue for PR #105 and connected with it Please, create an issue that mapping with PR for next time.

xellos00 commented 2 years ago

@dsrvlabs/validator Can you register an issue that create a plugin for current vatz when you start development?

xellos00 commented 2 years ago

1st Plugin Sync

@dsrvlabs/validator I requested polls by yesterday at https://github.com/dsrvlabs/vatz/issues/157#issuecomment-1176321387 but only few members in Validator were responded. I am going to close the poll.

We are going to create a common plugins, but 1st hand, we need to sync all together.

├── Makefile
├── README.md
├── bin
│   ├── build_plugins.sh
│   ├── clean_plugins.sh
│   ├── start_plugins.sh
│   └── stop_plugins.sh
├── logs
│   ├── machine-status-cpu.log
│   ├── machine-status-disk.log
│   ├── machine-status-memory.log
│   ├── near-metric-alive.log
│   ├── near-metric-block-height.log
│   ├── near-metric-chunk-produce-rate.log
│   ├── near-metric-number-of-peer.log
│   ├── near-metric-uptime.log
│   └── sample.log
└── plugins
    ├── machine-status-cpu
    │   ├── Makefile
    │   ├── go.mod
    │   ├── go.sum
    │   └── main.go
    ├── machine-status-disk
    │   ├── Makefile
    │   ├── go.mod
    │   ├── go.sum
    │   └── main.go
    ├── machine-status-memory
    │   ├── Makefile
    │   ├── go.mod
    │   ├── go.sum
    │   └── main.go
    ├── near-metric-alive
    │   ├── Makefile
    │   ├── go.mod
    │   ├── go.sum
    │   └── main.go
    ├── near-metric-block-height
    │   ├── Makefile
    │   ├── go.mod
    │   ├── go.sum
    │   └── main.go
    ├── near-metric-chunk-produce-rate
    │   ├── Makefile
    │   ├── go.mod
    │   ├── go.sum
    │   └── main.go
    ├── near-metric-number-of-peer
    │   ├── Makefile
    │   ├── go.mod
    │   ├── go.sum
    │   └── main.go
    └── near-metric-uptime
        ├── Makefile
        ├── go.mod
        ├── go.sum
        └── main.go

TODOs for Everyone:

Update to follow the structures in https://github.com/dsrvlabs/vatz-plugin-near All your plugins for protocol must include following options
- Redirect all plugins log into log folder
- Build/Start/Stop/Clean all plugins with Makefile with single command
Let it run on testnet node & report bug and register issue on VATZ

Please, check yourself if you've updated your protocol Due is end of Sprint 2022-07-20 Also Put machine info that VATZ is currently running.
[x] @xellos00 near-testnet-validator
[ ] @rootwarp
[ ] @meetrick
[ ] @Choi-Jinhong agoric-devnet-validator-do-nyc1
[ ] @heejin-github solana-testnet-validator-hetzner
[ ] @kim201212
[ ] @skonhwang

xellos00 commented 2 years ago

Share Plugins

Common for every machine (linux)

Requirements

[ ] CPU

[ ] DISK

[ ] Memory

Common for Protocol

Requirements

[ ] Process Up

Common Shared protocol

[ ] Tendermint
- [ ] Missing blocks
- [ ] Block height (increments or diff)
- [ ] Connected peers
[ ] Ethereum
- [ ] Block height (increments or diff)
- [ ] Connected peers

Additional Item for plugins (this is not included on 1st edition)

Be my guest to develop for followings if you have time to do.

[ ] CPU
- [ ] How to get a core CPU Info to find check number of cores and find out vertically for its spec.
[ ] Network Traffic

xellos00 commented 2 years ago

vatz-plugin-common
vatz-plugin-tendermint-common
vatz-plugin-ethereum-common

@dsrvlabs/validator 필수 참여자 @xellos00, @rootwarp , @hqueue 참여자:

at 2022-07-26 13:00:00 +09:00:00 Agenda

Repo policy
- Name
Plugin Design (How to use it or implements on Nodes)

xellos00 commented 2 years ago

moreover, Install all

1. vat (git_repo)
1. vatz-plugin-common A(git_repo)
1. vatz-plugin-flow B (git_repo)

Official plugins(linux, tendermint, eth)
- vatz - plugin - {}

Official VATZ plugin

모두같은 structure를 공유하며, 우리 DSRV Validator가 관리를 할 수 있는 레포 입니다.

xellos00 commented 2 years ago

Official plugins(linux, tendermint, eth)

vatz - plugin - {}

Plugin Structure.

Share mod로 바꾼다 (long term) 👍🏽
2가지, share-mod, individual (기준) 으로간다. 😄
SDK가 그대로 인데, 안바꾼다. 👀

이번에는 꼭 영어로 적지 않으셔도 되니까 더 많은 의견으로 주시면 좋겠습니다.

heejin-github commented 2 years ago

Plugin Structure.

Share mod로 바꾼다 (long term) 👍🏽

2가지, share-mod, individual (기준) 으로간다. 😄

SDK가 그대로 인데, 안바꾼다. 👀

희진

Official Plugin을 public하게 공개하여 plugin에 대한 guide로 제공 : Good Idea!
개별적으로 개발한 plugin의 structure를 통일해야할 필요? : 없다고 생각. 알아서 하도록 하는게 좋지 않을까요?
Official Plugin을 Share mod로 바꾼다.? SDK로 개발하면 개별 module로 개발되는데 Official Plugin guide는 Share mod이면 오히려 혼란하지 않을까요?

kim201212 commented 2 years ago

Official plugins(linux, tendermint, eth)

vatz - plugin - {}

Plugin Structure.

Share mod로 바꾼다 (long term) 👍🏽

2가지, share-mod, individual (기준) 으로간다. 😄

SDK가 그대로 인데, 안바꾼다. 👀

Offical plugin의 이름과 형식을 통일하는건 동의합니다.
vatz plugin SDK 이용하여 만드는 것이 Offical plugin 방식이어야 한다고 생각합니다.
SDK README.md에 SDK를 이용하여 플러그인 만드는 방법 제공
SDK를 제공하면 다른 개발자들도 SDK를 활용하여 플러그인을 만들어 형식이 비슷하게 유지되며 관리하기 용이할 것 같습니다.

meetrick commented 2 years ago

Plugin Structure.

Share mod로 바꾼다 (long term) 👍🏽

2가지, share-mod, individual (기준) 으로간다. 😄

SDK가 그대로 인데, 안바꾼다. 👀

Official Plugin을 선정하여 guide로 공개한다. [필수적이라고 생각합니다]
개별적으로 개발한 plugin의 structure를 통일해야할 필요? [user의 쓰임에 맞게 놔두는게 낫다고 생각합니다]
Official Plugin을 Share mod로 바꾼다? [SDK도 release가 된다는 가정하에 official plugin만 변경되는건 혼란을 야기할것 같습니다.]
추가의견
제품의 완성도를 추구하는것 자체에는 이견이 없습니다. 다만 어차피 plugin을 따로 빌드해서 사용해야하는 user라면 mod를 share하는 방식은 기존 방법에 비해서 나아보이지 않습니다. 물론... 보기에는 좋을 수 있습니다.

xellos00 commented 2 years ago

Official plugins(linux, tendermint, eth)

vatz - plugin - {}

Plugin Structure.

Share mod로 바꾼다 (long term) 👍🏽

2가지, share-mod, individual (기준) 으로간다. 😄

SDK가 그대로 인데, 안바꾼다. 👀

아래는 제가 생각한 방향입니다.

Official plugin 저희에 포트폴리오 TUM의 각 금액기준순으로 생각하고 있습니다.
VATZ-CLI를 통한 자연스런 제어
- Plugin - ON/OFF 기능추가
- Plugin - Install 추가
- Plugin - 삭제 추가
Notification
- Discord
- PagerDuty
- slack
Monitoring 을 위한 grafana dashboard

xellos00 commented 1 year ago

This issue has transferred to our official plugin plan #241

dsrvlabs / vatz

1st edition Plugins for Vatz per protocol #88

Related: https://github.com/dsrvlabs/vatz/issues/157

Checklist

1. Please describe, what it's about or related Problem with

2. Describe the output that you are expecting for above

Child

121

122

127

156

162

173

1st Plugin Sync

Let it run on testnet node & report bug and register issue on VATZ

Common for every machine (linux)

Common for Protocol

Common Shared protocol

Additional Item for plugins (this is not included on 1st edition)

vatz-plugin-flow B (git_repo)

Official plugins(linux, tendermint, eth)

Plugin Structure.

Plugin Structure.

희진

Official plugins(linux, tendermint, eth)

Plugin Structure.

Plugin Structure.

Official plugins(linux, tendermint, eth)

Plugin Structure.