Bug 1414022

Summary: [RFE] [Octavia] Supplying the overcloud with base Amphora image after deployment
Product: Red Hat OpenStack Reporter: Alexander Stafeyev <astafeye>
Component: openstack-tripleo-commonAssignee: Brent Eagles <beagles>
Status: CLOSED ERRATA QA Contact: Alexander Stafeyev <astafeye>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: amuller, astafeye, bcafarel, beagles, cgoncalves, dbecker, ealcaniz, jlibosva, jschluet, knylande, mburns, morazi, nyechiel, oblaut, rhel-osp-director-maint, samccann, scorcora, slinaber, sputhenp, tfreger
Target Milestone: rcKeywords: FutureFeature, InstallerIntegration, Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-common-8.6.1-16.el7ost openstack-tripleo-heat-templates-8.0.2-15.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:29:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1434826, 1477480    
Bug Blocks: 1433523, 1433537, 1442136, 1552443    

Description Alexander Stafeyev 2017-01-17 14:44:43 UTC
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:

Comment 1 Lon Hohberger 2017-01-17 15:01:57 UTC
Please clarify the requirements. What packages need to be present in this image?

Comment 3 Brent Eagles 2017-01-17 15:04:52 UTC
Upstream blueprint https://blueprints.launchpad.net/tripleo/+spec/octavia-amphorae-in-overcloud

This work is currently planned for the Pike cycle.

Comment 5 Assaf Muller 2017-01-18 19:11:38 UTC
@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.

Comment 6 Alexander Stafeyev 2017-02-05 20:39:30 UTC
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

Comment 8 Brent Eagles 2017-04-13 18:12:46 UTC
*** Bug 1432480 has been marked as a duplicate of this bug. ***

Comment 18 Carlos Goncalves 2018-03-21 13:36:31 UTC
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

Comment 19 Carlos Goncalves 2018-03-28 07:57:04 UTC
The additional steps in comment #18 do not block this RFE. Rather, they should be tracked in a separate rhbz.

Comment 43 Nir Magnezi 2018-05-24 11:19:20 UTC
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

Comment 49 errata-xmlrpc 2018-06-27 13:29:16 UTC
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