v4 infra: zos, registrar, hub, bootstrap #158
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Set up zos4 (dev mode) in an isolated environment (box) with restricted access to our team to be able to ship to farmers
Requirements
Deliverables
UPDATES
Registrar needed more work for tracking uptime for the rewards and auth using httpsig (both are done)
dev instance of the registar is deployed: https://github.com/threefoldtech/tf_operations/issues/3083
however the full flow isn't tested yet.
Path of the upgrade wasn't thought properly so we are going to monitoring flist symlink to decide if the system should upgrade or not
Still in progress:
Still working on the changes for the zos nodes with the registrar
Bootstrap and the hub don't have the changes needed yet. Maxime is working on that.
Should that be in 3.16 project? as that's completely isolated?
https://github.com/threefoldtech/zosbase here's a base repo for all of zos related packages (refactoring to use it in zos3 and zos3light will be done later)
here's a repo for zos4 https://github.com/threefoldtech/zos4
today and tmw the team will be working into replacing tfchain related code with the registar
Registrar needed more work for tracking uptime for the rewards and auth using httpsig (both are done)
dev instance of the registar is deployed: https://github.com/threefoldtech/tf_operations/issues/3083
however the full flow isn't tested yet.
Path of the upgrade wasn't thought properly so we are going to monitoring flist symlink to decide if the system should upgrade or not
Still in progress:
Zos4 devmode boxto v4 infra: zos, registrar, hub, bootstrapwell upgrading by following the symlinks gives away the controlled upgrades that we have right now. Current suggestion is moving that into the version into the registrar.
Still doing changes within zos, it's tightly coupled with tfchain, but still progressing
Node booted with localsetup
Registered on the registrar. What is pending is fixing the flow for updating the node, and update the code for the upgrader module to handle the self-update of zos4.
Aside from that, this has all of the current feature set.
full flow using bootstrap, hub, zos4 and the registarar on devnet
right now working on testing the upgrade procedure, everything seems to be in place
one more note: some of the flists used in zos image are coming from v3 hub, e.g traefik, not a deal breaker for now
upgrade seems to work fine and the nodes are catching the updates
now checking if we can boot a VM in that node (beyond the issue scope)
Also, how people are going to create farms? to use as a kernel param while booting?a small website or a desktop app? or from the phone?new phone app?
didn't get an answer from kds yet on how to create the farms
also today ops tried to boot a new node on qa, and it's not working. Maxime and Ashraf are needed to debug it
OK good to know. So I'll tell vendors they can't test yet. Please lmk when it's possible for them to test.
Well the upgrade worked fine
There are small things need to happen https://github.com/threefoldtech/tf_operations/issues/3138#issuecomment-2662660245 but Maxime's garage was caught on fire.
booted couple of nodes on dev, qa, and booting more on test and main
remaining tooling to show the number of nodes, farms, creating accounts, farms
will provide the docs to use some cli tools for it.