Discussions for dockerizing

[xellos00]

Checklist

• New Feature for the SVC/Plugin
• New Feature for CI/CD
• Enhancement on Vatz
• Others(etc. e.g, documentation,...)

---

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

A clear description of what feature need to be developed or enhanced in Vatz

For Dockerizing there are several issue as below.
Once docker has been created we need a new way to dealing with

• Dockerize VATZ #338

1. DBs & Configs

• Internal (pros/cons)
• external (pros/cons)
• Related Issues
  • Store plugin's executing information #388

2. CLIs

• Build a binary won't be placed.
• Related Issues
  • CLIs for plugin #316

3. Monitoring

• It must be separated as Client
• Related
  • Separate Monitoring module into another folder structures #390

4. Operations

• Operation to work with dockers
• Direction to dealing with vatz and docker

[xellos00]

@dsrvlabs/validator
Let's discuss above items overall.
I am going to send an invitation next Tuesday if anyone have trouble to show up, let me know.

[xellos00]

 dongyookang DK 🌙   ~
 cd .vatz
 dongyookang DK 🌙   ~/.vatz
 ls
total 52512
drwxr-xr-x   5 dongyookang  staff       160 Dec  1 22:11 .
drwxr-xr-x+ 67 dongyookang  staff      2144 Jan 31 19:04 ..
-rwxr-xr-x   1 dongyookang  staff  13907440 Dec  1 22:06 cosmos-status
-rwxr-xr-x   1 dongyookang  staff  12960144 Dec  1 22:11 cpu-monitor
-rw-r--r--   1 dongyookang  staff     12288 Dec  1 22:11 vatz.db
 dongyookang DK 🌙   ~/.vatz


[xellos00]

 ./vatz plugin list
2023-01-31T19:09:04-06:00 INF List plugins module=plugin
2023-01-31T19:09:04-06:00 INF List module=plugin
2023-01-31T19:09:04-06:00 INF newReader /Users/dongyookang/.vatz/vatz.db module=db
2023-01-31T19:09:04-06:00 INF Create DB Instance module=db
2023-01-31T19:09:04-06:00 INF List Plugin module=db
+---------------+---------------------+------------------------------------------------------------------------------+---------+
| NAME          | INSTALL DATA        | REPOSITORY                                                                   | VERSION |
+---------------+---------------------+------------------------------------------------------------------------------+---------+
| cosmos-status | 2022-12-01 21:52:44 | https://github.com/dsrvlabs/vatz-plugin-cosmoshub/plugins/node_active_status | latest  |
| cpu-monitor   | 2022-12-01 22:11:05 | https://github.com/dsrvlabs/vatz-plugin-sysutil/plugins/cpu_monitor          | latest  |
+---------------+---------------------+------------------------------------------------------------------------------+---------+

[xellos00]

1. DBs & Configs

• Internal (pros/cons)
• external (pros/cons)

---

[xellos00]

@rootwarp

• Put VATZ on k8s Cluster & dockerizing are different point and need to be separated.

@meetrick

• Do we really nee to go Docker for VATZ?

---

Dockerizing

• Good to done dockerizing.

[xellos00]

• K8s에 필요하다. Final goal

---

• VATz Docker
• docker Watcher

---

2023-02-07

Feedback

@rootwarp 1

• 롱텀으로 봐라보고 접근을 해야하고
• smoothe한 랜딩은 점진적으로 가야한다.
• Validator 팀의 운영하는 입장에서는 시스템이 다운된 상태에서는 보안할 수 없는 문제 있다.
• 선택의 문제가 된다.

@heejin-github

• K8s로 가게 되면 우리에게 얻는 이점이 무엇인가?
• 정확하게 이점이 파악이 안되기 때문에 잘 모르겠다.

---

Why we do?
@rootwarp
@heejin-github

IDK

./vatz plugin list
./vatz plugin start

• Installation vatz path

[xellos00]

@dsrvlabs/validator
I decide not to include docker feature to our official 1.0 release and therefore I am going to close this issue at this time.
Please, let me know if there's other comments or question.
I am going to create new issue for docker after official release if there's need arise.