Red Hat Bugzilla – Bug 1434060
[RFE] Deploy containerized Ironic services in TripleO
Last modified: 2018-02-05 14:04:43 EST
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.
Upstream patch to tripleo-heat-templates (merged): https://review.openstack.org/#/c/421517/
We need to check, this may be done already.
This seems to be available (and actually running in the containers CI upstream).
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
(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?
>> 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.
This has been tested and verified!
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