[Starlingx-discuss] StarlingX distributed cloud documentation for R3.0

[Liu, Tao]

Hi Austin,

The deployment status is shown under ' deploy status' field.  The availability state depends on whether the DC manager can communicate with the Subcloud via the mgmt. interface.  If the Subcloud mgmt. IP is not routable between the Central cloud and Subcloud, the availability state shows 'offline'.  That's why the availability state changed to online after adding route.

You can use the SystemController to add subclouds, synchronize select configuration data (such as the certificate, DNS and NTP),  across all subclouds and monitor subcloud operations and alarms. You can also access the individual subclouds through Horizon dashboard at the Central Cloud to perform subcloud-specific operations such as configuring and managing the subclouds' host nodes. System software updates for the subclouds are also centrally managed and applied from the SystemController.  

Regards,
Tao

-----Original Message-----
From: Sun, Austin [mailto:austin.sun at intel.com] 
Sent: Saturday, October 26, 2019 8:33 AM
To: Liu, Tao; Arce Moreno, Abraham; 'starlingx-discuss at lists.starlingx.io'
Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0

Hi Tao:
     With the V2 guide you shared ,  I deployed dist-cloud on virtual environment successfully.  There is one different between the guide and setup I deployed 
In guide, "After run "dcmanager subcloud add --bootstrap-ip <ip_address> --bootstrap-values <config_file> " , Confirm that the subcloud was deployed successfully"
But The result of 'dcmanager subcloud list' on my setup is offline , not online, it became online only after adding route from subcloud to controller mgmt. network. 

Is it normal behavior ? 

Another question is what the capability about system controller  beside monitoring subcloud alarm . 

The image is using 20191017T013000Z 

Thanks.
BR
Austin Sun. 

-----Original Message-----
From: Sun, Austin 
Sent: Saturday, October 26, 2019 9:21 AM
To: Liu, Tao <Tao.Liu at windriver.com>; Arce Moreno, Abraham <abraham.arce.moreno at intel.com>; starlingx-discuss at lists.starlingx.io
Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0

Hi, Tao:
     Thanks a lot.
So , there are two phase :
     In Phase 1( bootstrap subcloud) ,  sub-cloud OAM is need to routed to central OAM. 
     In Phase 2(provision/manger subcloud)  mgmt. subcloud is need to routed to central cloud mgmt. network.

Thanks.
BR
Austin Sun. 
-----Original Message-----
From: Liu, Tao <Tao.Liu at windriver.com>
Sent: Friday, October 25, 2019 9:02 PM
To: Sun, Austin <austin.sun at intel.com>; Arce Moreno, Abraham <abraham.arce.moreno at intel.com>; starlingx-discuss at lists.starlingx.io
Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0

Hi Austin,

The subcloud bootstrapping interface can be any interface that has connectivity to the system controller.  The script we provided will configure the IP and route on the selected interface.

We recommended using the mgmt. interface previously because it would not require configuring OAM prior to bootstrapping, however, the mgmt. subnet would have to be a different subnet than the one that will be configured on the mgmt. interface after bootstrapping.  This means an 'additional temporary' IP address/subnet on mgmt. interface is required for bootstrapping.  

The decision to use the OAM interface and IP removes the requirement to allocate an 'additional temporary' IP address/subnet, and it is consistent with a NON-DC scenario.

See inline comments for your questions.

Tao

-----Original Message-----
From: Sun, Austin [mailto:austin.sun at intel.com]
Sent: Thursday, October 24, 2019 9:39 PM
To: Liu, Tao; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io
Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0

Hi Tao:
     Thanks your update .  which gerrit or patch enhances using OAM interface and IP to bootstrap the subcloud ?  has this patch already been merged ? 
TL> My document update changes network requirements and no code change is required.

     Another question , will OAM ip in subcloud L3 connection to OAM ip in central cloud ?  does it request mgmt ip in subcloud L2 connect to OAM ip in central cloud for V2? 
TL> Yes, OAM IP Subnets need to be routable between Central Cloud and Subclouds.  No, mgmt. ip in subcloud should not be connected to OAM ip in central cloud.

Thanks.
BR
Austin Sun. 

-----Original Message-----
From: Liu, Tao <Tao.Liu at windriver.com>
Sent: Friday, October 25, 2019 2:27 AM
To: Arce Moreno, Abraham <abraham.arce.moreno at intel.com>; starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0

Thanks Arce!

A decision has been made to use OAM Interface and IP to bootstrap the subcloud. I have updated the document accordingly. The main change is to run the config_management script and enable OAM interface.


Tao

-----Original Message-----
From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com]
Sent: Monday, October 21, 2019 1:25 PM
To: Liu, Tao; starlingx-discuss at lists.starlingx.io
Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0

> Please add Distributed Cloud Configuration Guide to StarlingX R3.0 
> Installation.

Hi Tao, Distributed Cloud team,

Here you have an early review of Distributed Cloud:
  https://review.opendev.org/#/c/689847/

We will take it as our base documentation and do the installation in our labs starting today, some changes likely coming. For now, please let us know if we need to add more people as Co-Authored-By.