V2 VATZ Projects Milestone

[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

• POC is over, and VATZ's was too much tended to target or focused on monitoring. As discussed when we started the project at first, it's time to revert back to develop the initially designed product.
  • VATZ is only responsible for relaying all plug-ins
  • Even the behaviors such as sending notification or monitoring has to be handled by plug-in.

Describe the output that you are expecting for above

A clear and concise description of what you expect to happen.

As mentioned above, architecture design has to be redesigned to revert back to first time that we started our project and then its design need to shared and discussed.
Here's a link, update after research whether we can doable or not.

• V1 Architecture Link
• V2 Architecture Link
  • 45. VATZ biweekly meeting at `2023-10-25 08:00:00 -05:00:00` #510 (comment)

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

---

Child Issues

• Request for Proposal - New Architecture for General Plugin System #495

[xellos00]

Meeting Record

2023-11-02

Attended: @xellos00 , @rootwarp

To DOs:

• 1. Move code to VATZ:
     @rootwarp
  • 1. Repo(VATZ-proto):
    • Branch name: V2-pilot
  • 2. Repo(VATZ):
    • Branch name: V2-pilot
  • 3. Repo(VATZ-plugin) repo new:
    • @rootwarp, Create any repo but make it public, please.
• 2. Build Rest service that's left over
  • @xellos00
    • marshaling & unmashaling
    • in & output (shaping code components)
      • will discuss with @rootwarp
  • @rootwarp
    • finish request relayer (svc)
    • service end point (svc)

[xellos00]

@rootwarp
Can you upload all the works on a new branches on VATZ-proto, VATZ with v2-pilot, and new v2 pilot plugin?

[rootwarp]

@rootwarp Can you upload all the works on a new branches on VATZ-proto, VATZ with v2-pilot, and new v2 pilot plugin?

Sorry I'm late.
I will push all of them before today's meeting.

[xellos00]

@rootwarp Can you upload all the works on a new branches on VATZ-proto, VATZ with v2-pilot, and new v2 pilot plugin?

Sorry I'm late. I will push all of them before today's meeting.

No worry, you don't have to, take your time and ping me when you do

[rootwarp]

@xellos00 New codes are pushed

• proto: https://github.com/dsrvlabs/vatz-proto/tree/v2-pilot
• engine(agent): https://github.com/dsrvlabs/vatz/tree/v2-pilot
• plugin(tester): https://github.com/dsrvlabs/vatz-v2-engine-tester/tree/v2-pilot

Name of the new module and plugin project are still open question :)

[rootwarp]

@xellos00 I'm defining interfaces for communicating between modules, but I got some another idea of direction of architecture.
What do you think implementing "handler" and "relayer" as an independent gRPC services?

[xellos00]

@xellos00 I'm defining interfaces for communicating between modules, but I got some another idea of direction of architecture. What do you think implementing "handler" and "relayer" as an independent gRPC services?

@rootwarp
Thanks for update!!
let me ping you tomorrow. I think I need to understand your idea because concept of hander & relayer may different from each other.

[xellos00]

• END Point SVC
• Relayer SVC
• Handler SVC
• Registration SVC

---

Light version

1. VATZ 뜰때 4개를 한꺼번에 띄운다.
   • VATZ를 하나 띄우면 그 안에서 4개의 go Routine이 돌아간다.

Official version

1. 위의 light 버전을 개발하다가 정식으로 마이크로 서비스로 전환을 기획 중