After a Site Rebuild

Mon, 01 Jan 0001 00:00:00 +0000

After a Site Rebuild #

The operator tells you what was rebuilt. What you do depends on which part it was.

What the site rebuilt	What comes back on its own	What you do
The Deevnet API’s registry	Nothing about you, until you apply	`terraform apply`. Your state restores your tenant with the same index and keys, and the plan is otherwise empty. Only if another tenant has taken your index meanwhile are you given a new one, and your network and workloads are rebuilt on it
The tenant hypervisor	Your network, once the operator reconciles your tenant	Your workloads do not come back yet: see below
The whole site	Nothing about you	Wait for the operator’s new handover file: it carries a new developer Wi-Fi key. Then apply. With your state, your tenant comes back with its keys. Without it, use the handover’s enrollment token and create your tenant again from your repository; it may get a new index, which doesn’t matter if you use names, and your devices need new secrets. Then push your application to each workload
DNS, the state store, the log store or dashboards	Your zone and key, your state access, log tokens and dashboards login, once the operator reconciles your tenant	Re-check your names: see below. Log lines and dashboards stored on a lost host are gone

Your workloads, after a tenant hypervisor rebuild #

A rebuilt tenant hypervisor comes back without your VMs. The site still lists them, so a plain terraform apply shows no changes and rebuilds nothing. The API does rebuild a workload’s VM, with the same address and name, whenever that workload is applied again. But there is no tested way yet to make your apply send it. Until there is, ask the operator. Closing this is on the Tenant Platform roadmap.

Lost State or Credentials

Mon, 01 Jan 0001 00:00:00 +0000

Lost State or Credentials #

Your Terraform state holds every credential your tenant was issued, and for your API token it is the only copy. What you can get back depends on what you still have.

You still have	You lost	Do this
Your state	Your API token in this shell	`export DEEVNET_API_TOKEN=$(terraform output -raw api_token)`
State in the site’s state store	The keys to read it (`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`)	See below
A local `terraform.tfstate.backup` from before you moved state into the store	Everything else	That file holds your API token and the state-store keys from before the move. Read them out without printing them, then read your state as usual
Nothing	Your state and your token	Your tenant cannot be reached through its own Terraform. Ask the operator; the recovery is a rebuild, and devices need their keys reissued and reflashing

Keys to the state store #