Use the floating OAM address for the subcloud. It must match the external_oam_floating_address you will specify in the bootstrap-values.yml file you will use for that subcloud.

Bart

From: Owen Yuen <OwenYuen@cmail.carleton.ca>
Sent: Monday, February 1, 2021 1:46 PM
To: Wensley, Barton <Barton.Wensley@windriver.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: Cannot configure controller-0 on subcloud after bootstrapping from central cloud

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

Thanks Bart,

Another question:

I want to clarify in the distributed cloud setup, when running the config_management script it asks for the “management interface address CIDR”.

Is this address referring to the oam_node_0_address or the oam_floating_address?

For instance, in https://docs.starlingx.io/deploy_install_guides/r5_release/virtual/aio_duplex_install_kubernetes.html if I had followed the example for the “minimal config override file” provided, would I use the 10.10.10.2 or the 10.10.10.3?

$ sudo config_management
Enabling interfaces... DONE
Waiting 120 seconds for LLDP neighbor discovery... Retrieving neighbor details... DONE
Available interfaces:
local interface     remote port
---------------     ----------
enp0s3              08:00:27:c4:6c:7a
enp0s8              08:00:27:86:7a:13
enp0s9              unknown
 
Enter management interface name: enp0s3
Enter management address CIDR: 10.10.10.?/24
Enter management gateway address [10.10.10.1]:
Enter System Controller subnet: 10.10.10.0/24
Disabling non-management interfaces... DONE
Configuring management interface... DONE
RTNETLINK answers: File exists
Adding route to System Controller... DONE

Thanks

Owen

From: Wensley, Barton
Sent: Friday, January 29, 2021 8:38 AM
To: Owen Yuen; starlingx-discuss@lists.starlingx.io
Subject: RE: Cannot configure controller-0 on subcloud after bootstrapping from central cloud

[External Email]

Owen,

You add the route after unlocking the subcloud active controller.

Bart

From: Owen Yuen <OwenYuen@cmail.carleton.ca>
Sent: Thursday, January 28, 2021 5:45 PM
To: Wensley, Barton <Barton.Wensley@windriver.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: Cannot configure controller-0 on subcloud after bootstrapping from central cloud

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

Hi Barton,

Another question: The last step of the distributed cloud guide  says to add a route from the subcloud management network to the central cloud management network. Is this done AFTER I unlock the subcloud active controller or before?

I’m approaching the end and want to make sure I do everything correct.

Thanks

Owen

From: Wensley, Barton
Sent: Thursday, January 28, 2021 8:24 AM
To: Owen Yuen; starlingx-discuss@lists.starlingx.io
Subject: RE: Cannot configure controller-0 on subcloud after bootstrapping from central cloud

[External Email]

Owen – see my comments below…

Bart

From: Owen Yuen <OwenYuen@cmail.carleton.ca>
Sent: Wednesday, January 27, 2021 10:04 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Cannot configure controller-0 on subcloud after bootstrapping from central cloud

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

Hi all,

I’m a student so please bear with me if my questions are rudimentary.

I’m trying to setup a AIO duplex distributed cloud setup with one central cloud and one subcloud. I’ve managed to bootstrap the subcloud from the central cloud successfully and the next steps says to continue the installation from the AIO duplex guide starting from “Configure controller-0”.

On step 2, I need to run system commands but all of them require the host to be unlocked. I’m not able to unlock the host either since I’m on the host itself. I assume these steps are done on the subcloud controller-0 correct?

[Bart] Yes - these steps are done on the subcloud controller-0. They are done BEFORE you unlock the subcloud controller – you will see that following these steps will eventually lead to unlocking the subcloud controller.

Any help will be appreciated.

Thanks

Owen

This email contains links to content or websites. Always be cautious when clicking on external links or attachments. If in doubt, please forward suspicious emails to phishing@carleton.ca.

-----End of Disclaimer-----