See inline.

From: "Hu, Yong" <yong.hu@intel.com>
Date: Thursday, December 13, 2018 at 7:49 PM
To: "Peters, Matt" <Matt.Peters@windriver.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Deployment Improvements Proposal

Hi Matt,

How will this improvement proposal impact those configurations done by puppet?

MP> There will be some changes impacting the puppet manifests performed during the initial bootstrap phase (initial controller host), but there are no specific impacts to the use of Puppet for the rest of the configuration management.

As well, as to the proposal of system inventory improvement, you mentioned other BM attributes (Type, IP address, Credentials).

MP> These attributes are existing.  The change in behavior is to support identifying the host hardware based on inventory gathered from the BMC rather than needing the operator to specify the boot interface MAC address explicitelty.

Do we expect something more than PXEboot setting done in BIOS on the host in advance?

MP> Nothing is planned at this time.

Regards,

Yong

From: "Peters, Matt" <Matt.Peters@windriver.com>
Date: Friday, 14 December 2018 at 3:41 AM
To: "starlingx-discuss@lists.starlingx.io" <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