Hi Greg,

 

Thanks for your response! I’ll be giving the host-add a shot.

 

The reason I asked is because pre-installing the image potentially provides a speedup to deployment times.

Installing the images beforehand would cut down on the downtime waiting for the second controller to be provisioned without personality and on total time assuming that the images for both controllers are installed simultaneously.

 

Best,

Alex

 

From: Waines, Greg <Greg.Waines@windriver.com>
Sent: Thursday, June 10, 2021 1:31 PM
To: Williams, Alexander <Alexander.Williams@commscope.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: Adding hosts (Bare Metal AIO Duplex)

 

Hey Alex, For question 1 your understanding of the “host-update” use case is correct i.e. power on host which dhcp’s on mgmt. network host gets auto discovered by controller-0 and auto-provisioned wit

Hey Alex,

 

 

Greg.

 

From: Williams, Alexander <Alexander.Williams@commscope.com>
Sent: Monday, June 7, 2021 12:23 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Adding hosts (Bare Metal AIO Duplex)

 

[Please note: This e-mail is from an EXTERNAL e-mail address]

Hi all,

 

My current understanding is that whenever adding a host (esp. controller-1) using the system host-update command after a PXE boot, StarlingX will install the base image and then perform the configuration steps to make it a controller, worker, etc., overwriting anything that was previously installed on the machine.

  1. Is my understanding of host-update correct, or am I missing something important here? Does host-add do the same thing, but gets run on controller-0 before booting and not after?
  2. If I install the StarlingX image on a server that will become controller-1, is there any way to add it to the host list of controller-0 and configure its personality without the server reinstalling StarlingX?

 

Best,

Alex