Description of problem: When we deploy Openstack cloud with LBaaS (octavia), We would like to have basic Amphora image ready. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Please clarify the requirements. What packages need to be present in this image?
Upstream blueprint https://blueprints.launchpad.net/tripleo/+spec/octavia-amphorae-in-overcloud This work is currently planned for the Pike cycle.
@Ofer this was never planned or targeted for 11, moving to 12. We have tons of other work we need to do to enable Octavia on a very basic level before we can worry about a better user experience by supplying an image.
We just need to execute an image build like in the following doc : https://docs.google.com/document/d/1FIoSOp7fNoKokf-xHjKsxeJq3A6YTi1j-6W3F_cvT1Y/edit#heading=h.snmyvps3ybia
*** Bug 1432480 has been marked as a duplicate of this bug. ***
Workaround on Infrared side to upload image to Glance on overcloud deployment phase: https://review.gerrithub.io/#/c/403834/ Thanks to Brent and Or, Triple-O can today upload the image to Glance if the image file exists where Triple-O expects it to be (OctaviaAmphoraImageFilename) [1]. On OSP deployments, the amphora image file path differs from what's set upstream, i.e. the image is located in /usr/share/rhosp-director-images/. In conversations within the Octavia squad, we agreed it would be nice to have distro-specific environment files that would override the default image path. Moving back to ASSIGNED. [1] https://github.com/openstack/tripleo-heat-templates/blob/stable/queens/docker/services/octavia/octavia-deployment-config.yaml#L42-L45
The additional steps in comment #18 do not block this RFE. Rather, they should be tracked in a separate rhbz.
To avoid future confusion, I proposed this[1] patch so infrared will not handle the amphora image instead of TripleO [1] https://review.gerrithub.io/c/redhat-openstack/infrared/+/412362
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-2018:2086