This should only land after we've launched a new nb03.opendev.org running with the new nodepool arm64 docker image. Once that happens and we are happy with how it is running we can safely stop managing the existing nb03.openstack.org server with puppet. Change-Id: I8d224f9775bd461b43a2631897babd9e351ab6aechanges/53/749853/3
parent
ebd9c4c59e
commit
1ea83138ef
@ -1,4 +1,4 @@
|
||||
openstacksdk_config_owner: "{{ nodepool_user }}"
|
||||
openstacksdk_config_dir: /etc/openstack
|
||||
openstacksdk_config_owner: root
|
||||
openstacksdk_config_group: "{{ nodepool_group }}"
|
||||
openstacksdk_config_dir: "~{{ openstacksdk_config_owner }}/.config/openstack"
|
||||
openstacksdk_config_template: clouds/nodepool_clouds.yaml.j2
|
||||
|
@ -1,4 +0,0 @@
|
||||
openstacksdk_config_dir: /etc/openstack
|
||||
openstacksdk_config_owner: root
|
||||
openstacksdk_config_group: "{{ nodepool_group }}"
|
||||
openstacksdk_config_template: clouds/nodepool_clouds.yaml.j2
|
Loading…
Reference in new issue