Feature/deployment guide cookbook ssr1200 130#982
Feature/deployment guide cookbook ssr1200 130#982Chr1st0ph3rTurn3r wants to merge 31 commits intomasterfrom
Conversation
…130' of github.com:128technology/docs into feature/deployment-guide-cookbook-ssr1200-130
| | Field | Value | | ||
| |-------|-------| | ||
| | Role | `combo` | | ||
| | Asset ID | _(SSR130 serial number, e.g., `SSR130-ABC1234567`)_ | |
There was a problem hiding this comment.
We generate random UUIDs in the conductor's configuration for all router asset IDs and if the quickstart method is used to bring up the router then we set the router's asset ID to the random UUID from config and inject the full config into the router's datastore and bring it up.
We should be recommending the quickstart approach for router onboarding, hence defining the asset ID is not needed.
Asset id for routers and conductors comes from the name field in the onboarding config. For conductors it's required. It's optional for routers. In the case it isn't provided, we try to default to a known value. There's like 4 different things we try, but it's usually the serial numberThis can all be triggered via the universal ISO UI.
We also have a default "unmanaged" mode which happens on first boot unless a config is provided
There was a problem hiding this comment.
I had conversations with both Lane and Kaushik about the Quickstart procedure - with the introduction of the UISO and the Web interface for the initializer procedure, it is no longer recommended to use the Quickstart procedure.
|
…uide-cookbook-ssr1200-130' of github.com:128technology/docs into feature/deployment-guide-cookbook-ssr1200-130
2 participants
pdf version provided in slack channel for easier review by larger audience