Hi Matt,
Thanks for your answers!
Here is one further question about my #3 question. As you said, the operator will have the capability to run ansible playbook remotely. For now, the first controller network is configured during
config_controller, so to support running playbook remotely for bootstrap, at which stage will the network will be configured, installation stage by anaconda?
Thanks.
See inline.
From: "Wang, Yi C" <yi.c.wang@intel.com>
Date: Friday, December 14, 2018 at 3:53 AM
To: "Peters, Matt" <Matt.Peters@windriver.com>
Cc: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io>
Subject: RE: Deployment Improvements Proposal
Hi Matt,
I just went through your slides. And I have a few questions. I appreciate if you can share more information about your proposal. Many thanks!
1. We know config_controller will do many things, like bootstrap configuration and controller configuration together with required hieradata generation. All the jobs of config_controller
will be taken over by Ansible, or just part of them?
MP> Yes most of these tasks will be handled by the Ansible playbook. However, much of the existing capabilities may be leveraged in the implementation to avoid re-writing everything. The details will be outlined
in the forthcoming spec.
2. Does WindRiver has plan to replace Puppet with Ansible for all configuration jobs in the future?
MP> There are no specific plans to replace Puppet for all configuration management. However, there are several features being actively developed in StarlingX that will be changing the existing
Puppet manifests (e.g. OpenStack Containerization).
3. For the first controller, we still need local execution of Ansible playbook for initial bootstrap. Is my understanding correct?
MP> This is one of the main drivers for changing some of the existing config_controller and Puppet manifest handling. The operator will have the ability to run the Ansible playbook locally
or remotely.
BR.
Yi
From: Peters, Matt [mailto:Matt.Peters@windriver.com]
Sent: Friday, December 14, 2018 3:11 AM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Deployment Improvements Proposal
Hello,
Attached are the slides I presented during the TSC call on Dec 13, 2018 for the proposed improvements to the StarlingX initial bootstrap and system inventory. As indicated on the call, a detailed
stx-spec will follow, but wanted to share the high-level changes being proposed before the arrival of the spec to get some early feedback.
Regards, Matt