Open rootwarp opened 10 months ago
@xellos00 We could start discussion from this.
@xellos00 We could start discussion from this.
I will set up a meeting next Tuesday, if you are available on 10:00 AM at 9/12/2023 (KST). let me know.
@xellos00 We could start discussion from this.
I will set up a meeting next Tuesday, if you are available on 10:00 AM at 9/12/2023 (KST). let me know.
@xellos00 I'm good.
@xellos00 We could start discussion from this.
I will set up a meeting next Tuesday, if you are available on 10:00 AM at 9/12/2023 (KST). let me know.
@xellos00 I'm good.
Sent you an invitation.
Meeting Paper
@rootwarp and @xellos00 are confirmed that their consensus has met for Vatz V2 development idea.
Background
All of those steps are simply would be done by 3 dockers
The key part of the V2 is reconstructing the gRPC call between the plugin and VATZ by using reflection.
For proofing the possibility, I would suggest followings:
Meeting Paper
@rootwarp and @xellos00 are confirmed that their consensus has met for Vatz V2 development idea.
Background
- @dsrvlabs/validator team doesn't have a service that can make profit from it.
- Vatz V2 mainly targeting a SaaS platform that Validator team can provide overall.
- Targeting a service that run & manage on K8s.
- V2 test scenarios conduct the test briefly and concisely.
V2 poc test scenario based on brief architecture above (Note: let say Plugin:A sends a notification to discord, Plugin:B sends any event
Vatz V2 Agent is running
Plugin A: Connect to Vatz agent (notify to VATZ agent that plugin A is running)
Exchange a Reflection
Register the Plugin A spec
Plugin B: Connect to Vatz agent (notify to VATZ agent that plugin B is running)
Exchange a Reflection
Register the Plugin B spec
Plugin B requests & receives a Query to Check the spec of plugins (for this case Plugin A)
Plugin B creates a event with a schedule itself and request to VATZ agent to call a function in Plugin A
Vatz Agents relay plugin B's call to Plugin A
Plugin A send a notification to discord.
All of those steps are simply would be done by 3 dockers
@xellos00
Regarding background I rather think like this,
@rootwarp I apologize for the huge delay in the developments. now finally could get back to move on v2. will get back to you soon, with its time schedule for the development in the meeting v2 and will give you heads up regarding development.
@rootwarp
I apologize for the huge delay in the developments.
Not finally could get back to move on v2.
will get back to you soon, with its time schedule for the development in the meeting v2 and will give you heads up regarding development.
v2-pilot branch pushed again. 😀
Checklist
[x] New Feature for the SVC/Plugin
[ ] New Feature for CI/CD
[x] Enhancement on Vatz
[ ] Others(etc. e.g, documentation,...)
Parents: https://github.com/dsrvlabs/vatz/issues/493
Please describe, what it's about or related Problem with
Describe the output that you are expecting for above
Describe alternatives you've considered
Additional context
WIP - Drafting.
Rationale
Plugin Side Feature Registration
Technical Challanges
Expected Effects