<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div>Hi,</div>
<div> </div>
<div>In transition to Ansible bootstrap deployment, tomorrow the following commit <a href="https://review.opendev.org/#/c/657693"><font color="blue"><u>https://review.opendev.org/#/c/657693</u></font></a>, which disables config_controller, will be merged. StarlingX
test team has been notified and is making updates to their lab installer, configuration files and automation tools. StarlingX doc team has also been notified to make updates to the installation wikis.</div>
<div> </div>
<div>To ease the transition, once the commit is merged, config_controller can still be used to bootstrap the 1<font size="1"><span style="font-size:7.3pt;"><sup>st</sup></span></font> controller for a limited time (~1wk) using <b>--force</b> option. After which
time, relevant code in config_controller will be removed.</div>
<div> </div>
<div>In the event the doc team is not done with all of their updates by Friday. Please refer to the <a href="https://wiki.openstack.org/wiki/StarlingX/Containers/Installation"><font color="blue"><u>One node installation wiki</u></font></a> for the instructions
on how to run bootstrap playbook and to overwrite the default settings. The extra step that needs to be done following Ansible bootstrap (vs config_controller) is to provision the oam, management and k8s cluster interfaces prior to unlocking controller-0. </div>
<div> </div>
<div><b><u>For AIOSX:</u></b></div>
<div><font size="2"><span style="font-size:10.5pt;"># management and cluster interfaces default to loopback for AIOSX</span></font></div>
<div><font size="2"><span style="font-size:10.5pt;">OAM_IF=enp0s3</span></font></div>
<div><font size="2"><span style="font-size:10.5pt;">system host-if-modify controller-0 $OAM_IF -c platform --networks oam</span></font></div>
<div><font size="2"><span style="font-size:10.5pt;"> </span></font></div>
<div><font size="2"><span style="font-size:10.5pt;"><b><u>For AIO-DX, Standard non-storage, Standard storage</u></b><u>: </u></span></font></div>
<div><font size="2"><span style="font-size:10.5pt;">system host-if-modify controller-0 lo -c none</span></font></div>
<div><font size="2"><span style="font-size:10.5pt;">OAM_IF=enp0s3</span></font></div>
<div><font size="2"><span style="font-size:10.5pt;">system host-if-modify controller-0 $OAM_IF -c platform --networks oam</span></font></div>
<div><font size="2"><span style="font-size:10.5pt;">MGMT_IF=enp0s8</span></font></div>
<div><font size="2"><span style="font-size:10.5pt;">system host-if-modify controller-0 $MGMT_IF -c platform --networks mgmt </span></font></div>
<div><font size="2"><span style="font-size:10.5pt;">system host-if-modify controller-0 $MGMT_IF -c platform --networks cluster-host</span></font></div>
<div><font size="2"><span style="font-size:10.5pt;"> </span></font></div>
<div><font size="2"><span style="font-size:10.5pt;"><b><i><u>Note:</u></i></b><i> enp0s3 is a typical oam interface and enp0s8 is a typical mgmt interface in vbox. You can replace these with the values specific to your test system. </i></span></font></div>
<div> </div>
<div>In return, you get the benefits of the bootstrap playbook:</div>
<ul style="margin:0;padding-left:36pt;">
<li>Use Ansible which is an industry well-recognized tool</li><li>Can bootstrap target host both locally and remotely</li><li>Can bootstrap multiple target hosts simultaneously</li><li>Can reconfigure without having to resinstall</li><li>Require minimal configuration input upfront</li><li>Is simpler to understand</li><li>Is simpler to identify issues</li></ul>
<div> </div>
<div>Tee</div>
<div> </div>
<div> </div>
</span></font>
</body>
</html>