A typo in the previous email:
“This is a recommended method”. => This is not a recommended method.
Tao
Hi Kunpeng,
As I stated previously, the Central Cloud’s Local Registry is exposed on the OAM interface. This is required to allow pushing images from a remote workstation to the Central Cloud, in addition to support bootstrapping via the OAM interface.
As the document in the link below states, ”Using the management interface requires the creation of an additional temporary IP address/subnet on the management interface for bootstrapping”. This is not a recommended method.
Using the OAM interface for bootstrapping means that OAM IP Subnets need to be routable between Central Cloud and Subclouds, and it does not require a direct physical connection.
P.S. The MGMT IP subnets between Central Cloud and Subclouds are interconnected over Layer 3, not as part of an Layer 2 MGMT network.
Tao
Hi Tao,
But I haven’t understood why it is certral oam interface rather than mgmt interface to access registry.central. This guide[1] says the mgmt interface is okay to bootstrap in the section "install a subcloud" step 5. So if the registry.local can be accessed by mgmt network, wo don’t have to access the OAMs between central and subcloud. In addition, there is may only one interface that could be connected between central and subcloud in some case, and how to handle these cases with distributed cloud?
We made the decision to expose the Central Cloud’s Local Docker Registry on the OAM Interface for the following:
1. The OAM Interface and IP address are required to bootstrap the subcloud, and the default images can be pulled from the Central Cloud during the bootstrapping process
2. The OAM access to the Central Cloud’s Local Registry is required, to push images from a remote workstation to the Central Cloud
Add the following override to pull the default images or any additional images from registry.central and store them to the subcloud’s local registry
url: registry.central:9001/gcr.io additional_local_registry_images:
- registry.central:9001/addition_image_name
Hi Distributed Cloud team,
The distributed cloud feature is very cool, and I am concerned about its development always.
There are some questions about subclouds access the central cloud's local reigistry. This is the lp link[1].
As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's.
But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central.
I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography.
Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it?
Another question, how to set bootstrap-values.yml[2] when to bootstrap subcloud with registry.central?