Hide Forgot
Description of problem: We would like to be able to specify a hostname in instackenv.json that would be set on the overcloud host when deploying that node in the overcloud. For example: { "nodes":[ { "mac":[ "bb:bb:bb:bb:bb:bb" ], "cpu":"4", "memory":"6144", "disk":"40", "arch":"x86_64", "pm_type":"pxe_ipmitool", "pm_user":"admin", "hostname":"controller01", "pm_password":"p@55w0rd!", "pm_addr":"192.0.2.205" } ] } Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. It's not supported 2. 3. Actual results: It's not supported Expected results: It should be supported Additional info: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/sect-Scenario_2_Using_the_CLI_to_Create_a_Basic_Overcloud.html#sect-Registering_Nodes_for_the_Basic_Overcloud
It looks like there was already a commit to add basic name functionality: https://github.com/openstack/os-cloud-config/commit/3b0fb21e514b8369d7bfd32a6b47f37caea78bc3 This would only set the Ironic node name from the "name" tag in the instackenv.json file. The baremetal instance hostname is set by heat using the format %stackname%-rolename-%index% set in /usr/share/openstack-tripleo-heat-templates/overcloud-without-mergepy.html Both features would be great to have in OSP 8.
Customers are requesting it for OSP 7 so the question is , is it easy to implement in both? Thanks, Dave
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Baremetal node name is different the nova server name. But both can be defined in there relevant configuration Baremetal - as shown in the bug description Nova server name heat example: [stack@undercloud-0 virt]$ cat hostnames.yml parameter_defaults: CephStorageHostnameFormat: 'ceph-%index%' ObjectStorageHostnameFormat: 'swift-%index%' ControllerHostnameFormat: 'controller-%index%' ComputeHostnameFormat: 'compute-%index%'