Use custom node names instead of generating them
There is a number of customers which demand custom nodes naming instead of use automatically generated names node-1,2 etc.
This could be done for example by using the names we provide through the UI.
An FQDN validation on UI and Nailgun (optional, warning) sides should be added also.
Blueprint information
- Status:
- Complete
- Approver:
- Dmitry Pyzhov
- Priority:
- Low
- Drafter:
- Andrey Grebennikov
- Direction:
- Needs approval
- Assignee:
- Fuel Python (Deprecated)
- Definition:
- Approved
- Series goal:
- Accepted for future
- Implementation:
-
Implemented
- Milestone target:
-
7.0
- Started by
- Sergii Golovatiuk
- Completed by
- Sheena Conant
Related branches
Related bugs
| Bug #1376035: Hostnames on nodes are not set according to names specified on Fuel UI | Invalid |
Sprints
Whiteboard
NOTE: the ability to rename nodes is not only needed for cosmetic and
for better memorization reasons, but a is also a common workaround for
plugins, see for example:
[1] https:/
[2] https:/
Please raise the priority, at least for the user_node_name part.
Maybe the previous blueprint can be superseded:
https:/
Gerrit topic: https:/
Addressed by: https:/
Changed node naming method to allow custom names
Addressed by: https:/
Configurable hostnames for physical nodes
Addressed by: https:/
UI part for node hostname changing
Addressed by: https:/
Enhance ShowNodeInfoDialog and dialogMixin
Addressed by: https:/
Configurable hostnames for physical nodes
Addressed by: https:/
Configurable hostnames for physical nodes
Work Items
Dependency tree
* Blueprints in grey have been implemented.
