<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Hack">I'd like to request a FFE for this
blueprint[1].<br>
</font></p>
<p><font face="Hack">The<font face="Hack"> remai<font face="Hack">ning
changes will <font face="Hack">be tracked as Depends-On on
this oooq change[2].</font></font></font></font></p>
<p><font face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack">Initially th<font
face="Hack">e aim <font face="Hack">of this blueprint
was to do all container prepare operations in a
mistral action before the overcloud deploy. However
the pr<font face="Hack">iority for delivery switched
to helping blueprint </font></font></font></font>containeri<font
face="Hack">zed-undercloud with its container prep<font
face="Hack">are. Once this w<font face="Hack">as
complete it was apparent that the overcloud prepare
could share the undercloud prepare approach.</font></font></font></font></font></font></font></p>
<p><font face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack">The undercloud prepare
does <font face="Hack">the following:</font></font></font></font></font></font></font></font></font></p>
<p><font face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack">1<font face="Hack">)</font> During
undercloud_config, do a try-run prepare to
populate the image parameters (but don't do
any image transfers)</font></font></font></font></font></font></font></font></font></font></p>
<p><font face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack">2<font
face="Hack">)</font> D<font face="Hack">uring
tripleo<font face="Hack">-deploy, driven
by tripleo-heat-templates, do th<font
face="Hack">e actual prepare after the
undercloud registry is installed bu<font
face="Hack">t before and containers
are required</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></p>
<p><font face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font
face="Hack">For the overcloud, 1<font
face="Hack">)</font> will be
done by a mistral action[3] and 2)
<font face="Hack">will be done
during overcloud deploy<font
face="Hack">[4].</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></p>
<p><font face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack"><font
face="Hack"><font face="Hack">The
vast majority of <font
face="Hack">code for th<font
face="Hack">is blueprint
has landed and is
exercise<font
face="Hack">d 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 <font
face="Hack">manually
by running the new
command "openstack
tripleo container
image prepare"</font></font></font></font></font>
as <font face="Hack">documented
in this change [5].</font><br>
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></p>
<p><font face="Hack"><font face="Hack">[1] </font><a class="moz-txt-link-freetext" href="https://blueprints.launchpad.net/tripleo/+spec/container-prepare-workflow">https://blueprints.launchpad.net/tripleo/+spec/container-prepare-workflow</a></font></p>
<p>[2] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/573476/">https://review.openstack.org/#/c/573476/</a></p>
<p>[3] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/558972/">https://review.openstack.org/#/c/558972/</a> (landed but
currently being reverted)</p>
<p>[4] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/581919/">https://review.openstack.org/#/c/581919/</a> (plus the series
before it)</p>
<p>[5] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/553104/">https://review.openstack.org/#/c/553104/</a></p>
<p><br>
</p>
</body>
</html>