I'd like to request a FFE for this blueprint[1]. Theremaining changes will be tracked as Depends-On on this oooq change[2]. Initially the aim of this blueprint was to do all container prepare operations in a mistral action before the overcloud deploy. However the priority for delivery switched to helping blueprint containerized-undercloud with its container prepare. Once this was complete it was apparent that the overcloud prepare could share the undercloud prepare approach. The undercloud prepare does the following: 1) During undercloud_config, do a try-run prepare to populate the image parameters (but don't do any image transfers) 2) During tripleo-deploy, driven by tripleo-heat-templates, do the actual prepare after the undercloud registry is installed but before and containers are required For the overcloud, 1) will be done by a mistral action[3] and 2) will be done during overcloud deploy[4]. The vast majority of code for this blueprint has landed and is exercised by containerized-undercloud. I don't expect issues with the overcloud changes landing, but in the worst case scenario the overcloud prepare can be done manually by running the new command "openstack tripleo container image prepare" as documented in this change [5]. [1] https://blueprints.launchpad.net/tripleo/+spec/container-prepare-workflow [2] https://review.openstack.org/#/c/573476/ [3] https://review.openstack.org/#/c/558972/ (landed but currently being reverted) [4] https://review.openstack.org/#/c/581919/ (plus the series before it) [5] https://review.openstack.org/#/c/553104/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180726/e3c199c2/attachment.html>