Bug 1434060

Summary: [RFE] Deploy containerized Ironic services in TripleO
Product: Red Hat OpenStack Reporter: Ramon Acedo <racedoro>
Component: openstack-tripleo-heat-templatesAssignee: mkovacik
Status: CLOSED ERRATA QA Contact: Dan Yasny <dyasny>
Severity: unspecified Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: apevec, dbecker, dtantsur, dyasny, jcoufal, lhh, mburns, mgould, mkovacik, mlammon, morazi, nlevinki, racedoro, rhel-osp-director-maint, sasha, srevivo, tvignaud
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170616123155.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 21:18:38 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: 1456986, 1483756    
Bug Blocks: 1434063, 1442136, 1478111, 1480137    

Description Ramon Acedo 2017-03-20 16:21:39 UTC
Ironic services to be containerized in TripleO for Pike. This RFE should target all the services required by Ironic in containers except Ironic inspector which will be tracked separately: ironic-conductor, ironic-api, nova-compute, httpd and tftp.

Comment 4 Miles Gould 2017-03-24 17:57:43 UTC
Upstream patch to tripleo-heat-templates (merged): https://review.openstack.org/#/c/421517/

Comment 5 Dmitry Tantsur 2017-04-24 10:43:43 UTC
We need to check, this may be done already.

Comment 6 Dmitry Tantsur 2017-05-22 17:46:11 UTC
This seems to be available (and actually running in the containers CI upstream).

Comment 7 Ramon Acedo 2017-05-24 14:01:17 UTC
As discussed in IRC, this bug should track and test that after the move to containers, not only deploying to containers works but no regressions are encountered. As per Dmitry's initial suggestions:

1. already deployed nodes work after upgrade, 
2. already deployed nodes can be rebuilt, cleaned and torn down, 
3. (when we fix take over) take over still works

Comment 8 Dan Yasny 2017-06-02 19:15:59 UTC
(In reply to Ramon Acedo from comment #7)
> As discussed in IRC, this bug should track and test that after the move to
> containers, not only deploying to containers works but no regressions are
> encountered. As per Dmitry's initial suggestions:
> 
> 1. already deployed nodes work after upgrade, 

This is not ironic specific, is it? The item can be verified by a standard upgrade to containers test, done by the other DFGs

> 2. already deployed nodes can be rebuilt, cleaned and torn down,

Standard regression tests?
 
> 3. (when we fix take over) take over still works

slightly more specific, but still quite the standard regression test.

I do not however, see any container specific testing targets, isn't there anything we would want to test/verify/ensure for ironic specifically?

Comment 9 Dmitry Tantsur 2017-06-05 09:42:07 UTC
>> 1. already deployed nodes work after upgrade, 

> This is not ironic specific, is it? The item can be verified by a standard upgrade to containers test, done by the other DFGs

Not sure I get it. How do tests by other DFGs verify that ironic nodes work, if they don't even deploy ironic. Or do they? Maybe it falls under "standard regression tests" as well.

>> 2. already deployed nodes can be rebuilt, cleaned and torn down,

> Standard regression tests?

I guess so (if we have them).

> I do not however, see any container specific testing targets, isn't there anything we would want to test/verify/ensure for ironic specifically?

Well, from user's perspective, upgrade to containers should not change anything, so I'm not sure we need specific tests.

Comment 11 mlammon 2017-11-03 13:12:27 UTC
This has been tested and verified!

Comment 14 errata-xmlrpc 2017-12-13 21:18:38 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-2017:3462