Mik-TF
commented
2 months ago Status
@coesensbert has set many mainnet grid stacks.
See info_grid issue for links to stacks: https://github.com/threefoldtech/info_grid/issues/625
Closed Mik-TF closed 2 months ago
Mik-TF
commented
2 months ago @coesensbert has set many mainnet grid stacks.
See info_grid issue for links to stacks: https://github.com/threefoldtech/info_grid/issues/625
coesensbert
commented
2 months ago current list of mainnet backend stacks
docs: https://docs.grid.tf/threefold/itenv_threefold_main/src/branch/master/grid_operations/grid_backend/mainnet no loadbalancer / geo forwarder yet, will update that ticket
coesensbert
commented
2 months ago all specs satisfied, except the load balancer see: https://github.com/threefoldtech/grid_deployment/issues/56#issuecomment-2312085979 5 independent grid backend stacks deployed
infra docs: https://docs.grid.tf/threefold/itenv_threefold_main/src/branch/master/grid_operations/grid_backend/mainnet all links: https://github.com/threefoldtech/tf_operations/blob/master/docs/all-grid-v3-links.md ops ticket: https://github.com/threefoldtech/tf_operations/issues/2649
Situation
We want to simplify the grid stack project for the first phase. We will not focus on having grid guardians from the community for now. We want to have redundancy and resiliency in a simple manner for now.
Specs
We want to have:
Updates
When we need to update the grid to new releases, we can have 1 of the 3 stacks that is updated and we can then test it and see if everything is OK before the other 2 can update with the new release.
Future
Once we have this set up properly, we can think about going commercial or setting up the grid guardian project.
So for now we want to keep it simple and have redundant grid stacks running independently.
Full Grid Stack
References
WIP being done by @coesensbert and @maxux