supportability 3Node Farmers #6

New Issue

despiegk · 2024-03-05T04:10:14Z

despiegk commented

2024-03-05 04:10:14 +00:00

We need to implement couple of measurements to let people trust our grid more, lets also use this opportunity to use mycelium bus and for at least these functions use mycelium & openrpc, we need to go more p2p

we need to make our grid supportable, which it isn't today

webhooks

in zos itself, lets introduce webhooks which will make it easier for farming pools to manage the 3nodes which are linked to them.

Example webhooks

utilization info (1h usage of ..., start/stop of vm, ..)
stats info (e.g. each hour let know current avg uptime, utilization, ...)
error, info, warning information e.g. overload, getting out of space

RPC methods

all over OpenRPC/Mycelium, document them in openrpc spec

to expose our existing functions (stats, deployments, ...)
allow zos admin to set mycelium address groups
- name of group + add/remove mycelium addresses to such a group (source ipv6 or pub key of people connecting over mycelium bus)
address groups can be given admin rights by an existing administrator
allow zos admin to set/modify profile
- description of box (markdown content), e.g. link to website
- email address, telnr (sms), matrix address, whatsapp & telegram (use category so its easy for users to see)
- ability to specify who can see which info (public, or whitelist of mycelium address groups)
allow zos admin to reboot which will also trigger update, or just update
allow zos admin to remove a contract (shut out a user)
allow zos admin to make 3node only usable for dedicated or not
allow zos admin to configure webhooks
allow zos admin to configure which groups or if public can deploy workloads

client generator

generate V, Golang, TS client from openrpc for our methods (using mycelium)

We need to implement couple of measurements to let people trust our grid more, lets also use this opportunity to use mycelium bus and for at least these functions use mycelium & openrpc, we need to go more p2p we need to make our grid supportable, which it isn't today ## webhooks in zos itself, lets introduce webhooks which will make it easier for farming pools to manage the 3nodes which are linked to them. Example webhooks - utilization info (1h usage of ..., start/stop of vm, ..) - stats info (e.g. each hour let know current avg uptime, utilization, ...) - error, info, warning information e.g. overload, getting out of space ## RPC methods all over OpenRPC/Mycelium, document them in openrpc spec - to expose our existing functions (stats, deployments, ...) - allow zos admin to set mycelium address groups - name of group + add/remove mycelium addresses to such a group (source ipv6 or pub key of people connecting over mycelium bus) - address groups can be given admin rights by an existing administrator - allow zos admin to set/modify profile - description of box (markdown content), e.g. link to website - email address, telnr (sms), matrix address, whatsapp & telegram (use category so its easy for users to see) - ability to specify who can see which info (public, or whitelist of mycelium address groups) - allow zos admin to reboot which will also trigger update, or just update - allow zos admin to remove a contract (shut out a user) - allow zos admin to make 3node only usable for dedicated or not - allow zos admin to configure webhooks - allow zos admin to configure which groups or if public can deploy workloads ## client generator - generate V, Golang, TS client from openrpc for our methods (using mycelium)

despiegk added the

Story

Urgent

labels 2024-03-05 04:10:19 +00:00

despiegk added this to the (deleted) project 2024-03-05 04:10:21 +00:00

despiegk removed the

Urgent

label 2024-03-21 11:29:58 +00:00

despiegk commented

2024-04-23 11:33:07 +00:00

lets get feedback about timing, owner?

despiegk modified the project from (deleted) to tfgrid_3_14