Description of problem: We anticipate deploying Designate with Director in OSP 14, so we will need containers for the service. We are currently shipping Designate packages as tech preview so this should only require adding the containers themselves. There is a patch upstream to add these containers to the TripleO set: https://review.openstack.org/#/c/544675/
The upstream review has been merged for a while. Is there anything else we need to do to get them included in the downstream distribution?
I think new containers need LT approval before we add them into our product. Once that is approved I think the Release Engineering team would be notified to begin building the new container(s) ASAP.
https://github.com/openstack/tripleo-common/blob/master/container-images/overcloud_containers.yaml#L20 contains the ones we have upstream So all of above except pool-manager.
openstack-designate-api openstack-designate-backend-bind9 openstack-designate-base openstack-designate-central openstack-designate-mdns openstack-designate-producer openstack-designate-sink openstack-designate-worker
openstack-designate-api-container-14.0-1 openstack-designate-backend-bind9-container-14.0-1 openstack-designate-base-container-14.0-1 openstack-designate-central-container-14.0-1 openstack-designate-mdns-container-14.0-1 openstack-designate-producer-container-14.0-1 openstack-designate-sink-container-14.0-1 openstack-designate-worker-container-14.0-1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0048
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days