Playbooks & scripts for building, registering and rotating octavia amphora images

[markgoddard]

No description provided.

[jovial]

This is mostly working for me. The one issue was that I can't connect to the internal API from my seed. The octavia openrc file uses the internal interface by default. My workaround was to fudge the openrc file to use public endpoints and run octavia-amphora-image-register.yml with -e openstack_interface=public. Is there a way we could make this work across all deployments? I think having the seed on the internal network is non-standard.

[jovial]

In kayobe, don't we typically use the first controller for these kind of operations (stuff that needs API access), e.g:

https://github.com/openstack/kayobe/blob/master/ansible/baremetal-compute-rename.yml#L7

Just wondering if we should use a controller with the internal openrc file here.

[jovial]

Should we untag the old image? This seems to trigger a warning:

https://github.com/openstack/octavia/blob/bd01ad94dcea3eca7636f1286ceed0753b563a28/octavia/image/drivers/glance_driver.py#L65

This isn't mentioned in the docs and would appear not to have a negative impact as it seems like it would just select the image that was uploaded last.

[jovial]

Any reason to include the qcow2 file extension in the image name?

[jovial]

Wrong line, see: https://github.com/stackhpc/kayobe-ops/pull/12/files#diff-e5ac2a54d5ef4bca658be8fff362434d7d5155f62c23e1b7106198e815f0ff76R64

[markgoddard]

This is mostly working for me. The one issue was that I can't connect to the internal API from my seed. The octavia openrc file uses the internal interface by default. My workaround was to fudge the openrc file to use public endpoints and run octavia-amphora-image-register.yml with -e openstack_interface=public. Is there a way we could make this work across all deployments? I think having the seed on the internal network is non-standard.

In kayobe, don't we typically use the first controller for these kind of operations (stuff that needs API access), e.g:

https://github.com/openstack/kayobe/blob/master/ansible/baremetal-compute-rename.yml#L7

Just wondering if we should use a controller with the internal openrc file here.

Sure, we could change the host to controllers[0], or use a variable:

hosts: "{{ groups('os_clients')[0] | default(groups('controllers')[0]) }}"

[jovial]

This is mostly working for me. The one issue was that I can't connect to the internal API from my seed. The octavia openrc file uses the internal interface by default. My workaround was to fudge the openrc file to use public endpoints and run octavia-amphora-image-register.yml with -e openstack_interface=public. Is there a way we could make this work across all deployments? I think having the seed on the internal network is non-standard.

In kayobe, don't we typically use the first controller for these kind of operations (stuff that needs API access), e.g:
https://github.com/openstack/kayobe/blob/master/ansible/baremetal-compute-rename.yml#L7
Just wondering if we should use a controller with the internal openrc file here.

Sure, we could change the host to controllers[0], or use a variable:

hosts: "{{ groups('os_clients')[0] | default(groups('controllers')[0]) }}"

Would we still build the image on the seed and then transfer it to os_clients[0]?

[markgoddard]

This is mostly working for me. The one issue was that I can't connect to the internal API from my seed. The octavia openrc file uses the internal interface by default. My workaround was to fudge the openrc file to use public endpoints and run octavia-amphora-image-register.yml with -e openstack_interface=public. Is there a way we could make this work across all deployments? I think having the seed on the internal network is non-standard.

In kayobe, don't we typically use the first controller for these kind of operations (stuff that needs API access), e.g:
https://github.com/openstack/kayobe/blob/master/ansible/baremetal-compute-rename.yml#L7
Just wondering if we should use a controller with the internal openrc file here.

Sure, we could change the host to controllers[0], or use a variable:

hosts: "{{ groups('os_clients')[0] | default(groups('controllers')[0]) }}"

Would we still build the image on the seed and then transfer it to os_clients[0]?

We could do. We actually build the IPA images on a controller, which isn't ideal.

[markgoddard]

Moved to stackhpc-kayobe-config