Hi Tao, Thanks for your reply. 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?
1. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud... <https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8>
在 2019年11月27日，23:06，Liu, Tao <Tao.Liu@windriver.com> 写道：
Hi Kunpeng,
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 docker_registries: k8s.gcr.io <http://k8s.gcr.io/>: url: registry.central:9001/k8s.gcr.io <http://k8s.gcr.io/> gcr.io <http://gcr.io/>: url: registry.central:9001/gcr.io <http://gcr.io/> quay.io <http://quay.io/>: url: registry.central:9001/quay.io <http://quay.io/> docker.io <http://docker.io/>: url: registry.central:9001/docker.io <http://docker.io/> docker.elastic.co <http://docker.elastic.co/>: url: registry.central:9001/docker.elastic.co <http://docker.elastic.co/> defaults: type: docker username: admin password: Li69nux*
additional_local_registry_images: - registry.central:9001/addition_image_name
Tao
From: 张鲲鹏 [mailto:zhang.kunpeng@99cloud.net] Sent: Wednesday, November 27, 2019 4:40 AM To: starlingx-discuss@lists.starlingx.io; Liu, Tao Subject: [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry.
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?
1. https://bugs.launchpad.net/starlingx/+bug/1846799 <https://bugs.launchpad.net/starlingx/+bug/1846799> 2. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud... <https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8>
Thanks Kunpeng