Hi, During Rocky cycle we would like to switch tripleoclient to deploy containeirzed undercloud by default but before to get there, we want to switch all CI jobs to it, like it was done when enabling config-download by default. Right now we have 3 jobs which test the containerized undercloud:
- tripleo-ci-centos-7-undercloud-containers: deploy a containerized undercloud and run Tempest - tripleo-ci-centos-7-containerized-undercloud-upgrades: deploy a non-containerized undercloud on Queens and upgrade to a containerized undercloud on Rocky - gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-master: deploy a containerized undercloud and an overcloud with HA architecture and IPv4 network (with introspection, SSL, etc). What's next (target is Rocky M3): - tripleo-ci-centos-7-containers-multinode - currently blocked by https://bugs.launchpad.net/tripleo/+bug/1774297 - all multinode scenarios - current blocked by 1774297 as well but also https://review.openstack.org/#/c/571566/ - gate-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset035-master - currently blocked by https://bugs.launchpad.net/tripleo/+bug/1774557 (with a potential fix: https://review.openstack.org/571620) - all other jobs that run on master, except tripleo-ci-centos-7-undercloud-oooq that we'll probably keep during Rocky and remove in Stein if we successfully switch the default. Once we've reached that point, we'll change tripleoclient's default, and hopefully all of this before m3 :-) Any question or feedback is highly welcome, -- Emilien Macchi
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
