[docs] Document the nailgun node naming algorithm
Bug #1386806 reported by
Fabrizio Soppelsa
This bug report is a duplicate of:
Bug #1385141: Need to add to docs information about the order in which the nodes deploy.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Triaged
|
High
|
Fuel Documentation Team | ||
6.0.x |
Triaged
|
Undecided
|
Fuel Documentation Team | ||
6.1.x |
Triaged
|
High
|
Fuel Documentation Team |
Bug Description
Explain that the node names are determined sequentially, as they appear during discovery. When a node is bootstrapped, it checks in, and nailgun returns this ID for the node. So, each node will get a name like node-<ID>
Changed in fuel: | |
assignee: | nobody → Fuel Documentation Team (fuel-docs) |
tags: | added: docs |
Changed in fuel: | |
status: | New → Confirmed |
status: | Confirmed → Triaged |
importance: | Undecided → Low |
milestone: | none → 6.0 |
tags: | added: low-hanging-fruit |
Changed in fuel: | |
importance: | Low → High |
tags: | added: customer-found |
Changed in fuel: | |
assignee: | Fuel Documentation Team (fuel-docs) → Meg McRoberts (dreidellhasa) |
To post a comment you must log in.
can we add it here? docs.mirantis. com/openstack/ fuel/fuel- 5.1/operations. html?highlight= target% 20node# adding- redeploying- and-replacing- nodes
http://