add reconfigurator-cli command for bumping Nexus generation#9033
Conversation
…nfigurator-cli-bump-generation
…nfigurator-cli-bump-generation
…i-bump-generation
| internal_dns 427ec88f-f467-42fa-9bbb-66a91a36103c install dataset in service fd00:1122:3344:2::1 | ||
| internal_ntp 6444f8a5-6465-4f0b-a549-1993c113569c install dataset in service fd00:1122:3344:101::21 | ||
| nexus 0c71b3b2-6ceb-4e8f-b020-b08675e83038 install dataset in service fd00:1122:3344:101::22 | ||
| + nexus 16a766ee-9400-4e67-9363-883670371a1b install dataset in service fd00:1122:3344:101::28 |
There was a problem hiding this comment.
(Not in this PR) Should we have a column for the Nexus generation in this zones table? Sucks that it only applies to Nexus, but it seems like a pretty vital piece of info.
There was a problem hiding this comment.
If you want I could have it be a follow-up to #9034
IMO it's pretty handy to see the nexus_generation info co-located with the db_metdata_nexus info, because they're so tightly correlated
There was a problem hiding this comment.
Yeah, I do think we should do this. I was thinking we might want to add a table to the blueprint show output for this, similar to DNS I think? Rather than this table.
I'm game to include it in the database state as well but I think it's important to be able to see it from just the blueprint state too (e.g., in reconfigurator-cli).
3 participants
This will be useful for being able to test Nexus handoffs manually. (I was doing this by hand before.)
Depends on #9023.