[Starlingx-discuss] Ansible bootstrap in one node configuration

[Ngo, Tee]

Hi José,

You certainly can automate with Ansible bootstrap. The default parameters can be found in host_vars/default.yml of the bootstrap playbook. Please refer to the wiki for the location of playbook. You can overwrite one or more of these default parameters using either ansible-playbook command line option -e (--extra-vars) or a user override file which is in .yml format.

The default directory which Ansible looks for user override files is /home/wrsroot (this default directory can also be customized). A config override file must have the following naming convention: <inventory_hostname>.yml. Inventory_hostname being the target host specified in the inventory file that is used when you run the bootstrap playbook. As documented on the wiki, the default bootstrap inventory file is /etc/ansible/hosts. You can specify a custom inventory file using ansible-playbook command line opiton -i (--inventory).

I will be able to assist better if I know a bit more about your automation flow and the sample configuration file you use for AIO-SX. Let's set up a zoom session to discuss your setup.

Tee


From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com]
Sent: April-30-19 10:41 AM
To: Ngo, Tee; Cabrales, Ada
Cc: starlingx-discuss at lists.starlingx.io
Subject: RE: Ansible bootstrap in one node configuration

Hi Tee

I'll do a manual try and let you know the results. For automation purposes we use a configuration file, is this option also available using ANSIBLE ? if its supported were I can find the steps to follow ?

Regards,
José

From: Ngo, Tee [mailto:Tee.Ngo at windriver.com]
Sent: Tuesday, April 30, 2019 9:12 AM
To: Cabrales, Ada <ada.cabrales at intel.com>
Cc: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] Ansible bootstrap in one node configuration

Hello Ada,

The One node configuration wiki<https://wiki.openstack.org/wiki/StarlingX/Containers/Installation>  has been updated with instructions to bootstrap the controller using Ansible playbook. Could you give it a try and let me know if there are any issues? Once the new bootstrap method has been successfully incorporated into your sanity workflow, we plan to proceed with the remaining three configurations and cutover to Ansible bootstrap. Config_controller will be disabled as part of the cutover.

It would be great if your team can test this as soon as possible this week as we are looking to cutover to Ansible soon and get some soak time started.

Thank you.
Tee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190430/98f2b40a/attachment.html>