Nice, thanks for the answe. On Fri, May 15, 2020, 09:58 Sun, Austin <austin.sun@intel.com> wrote:

Hi Popoi :

Yes , central cloud does not support compute-kits (nova) , this is by design .

You can check the [1] , but set invalid .

And you may find more information related distr-cloud from [2] .

Hope this will help .

[1] https://bugs.launchpad.net/starlingx/+bug/1868031

[2] http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007427.ht...

Thanks.

BR

Austin Sun.

*From:* Popoi Zen <alterriu@gmail.com> *Sent:* Wednesday, May 13, 2020 10:03 PM *To:* Starlingx-discuss@lists.starlingx.io *Subject:* [Starlingx-discuss] No Nova Compute on Distributed Cloud?

Hi, I have 1 central cloud AIO-Duplex and want to deploy Openstack on it. It deployed as VMs.

From kubernetes cluster, it already labeled as compute node:

[image: image.png]

I checked pods and there are no nova pods:

[sysadmin@controller-1 ~(keystone_admin)]$ kubectl get pods -n openstack NAME READY STATUS RESTARTS AGE cinder-api-7c65d84674-btm8s 1/1 Running 0 3h13m cinder-api-7c65d84674-gpdfm 1/1 Running 0 3h13m cinder-backup-7794b779c9-7r4bd 1/1 Running 0 3h13m cinder-backup-7794b779c9-lf4jp 1/1 Running 0 3h13m cinder-backup-storage-init-2zq5v 0/1 Completed 0 3h13m cinder-bootstrap-vqjkg 0/1 Completed 0 3h13m cinder-create-internal-tenant-7twd4 0/1 Completed 0 3h13m cinder-db-init-rsvk8 0/1 Completed 0 3h13m cinder-db-sync-sqk9v 0/1 Completed 0 3h13m cinder-ks-endpoints-8lh65 0/9 Completed 0 3h13m cinder-ks-service-68xv6 0/3 Completed 0 3h13m cinder-ks-user-5ktlh 0/1 Completed 0 3h13m cinder-rabbit-init-smlbt 0/1 Completed 0 3h13m cinder-scheduler-97fc5f8fd-46929 1/1 Running 0 3h13m cinder-scheduler-97fc5f8fd-dwb7h 1/1 Running 0 3h13m cinder-storage-init-dj6tf 0/1 Completed 0 3h13m cinder-volume-7565d7d98d-jzgx8 1/1 Running 0 3h13m cinder-volume-7565d7d98d-x4xdb 1/1 Running 0 3h13m cinder-volume-usage-audit-1589336700-krtts 0/1 Completed 0 13m cinder-volume-usage-audit-1589337000-j9f6w 0/1 Completed 0 8m38s cinder-volume-usage-audit-1589337300-phjln 0/1 Completed 0 3m37s dcdbsync-ks-config-6s9wj 0/1 Completed 0 3h5m fm-db-init-fzgdl 0/1 Completed 0 3h8m fm-db-sync-mxgv7 0/1 Completed 0 3h8m fm-ks-endpoints-8cbhh 0/3 Completed 0 3h8m fm-ks-service-5lq4s 0/1 Completed 0 3h8m fm-ks-user-w9j2x 0/1 Completed 0 3h8m fm-rest-api-6cbc568896-7p8xb 1/1 Running 0 3h8m fm-rest-api-6cbc568896-tgjw4 1/1 Running 0 3h8m glance-api-786bccbcf7-7bzps 1/1 Running 0 3h18m glance-api-786bccbcf7-ppt4j 1/1 Running 0 3h18m glance-db-init-996n8 0/1 Completed 0 3h18m glance-db-sync-8jtc4 0/1 Completed 0 3h18m glance-ks-endpoints-ctvvf 0/3 Completed 0 3h18m glance-ks-service-p7tgm 0/1 Completed 0 3h18m glance-ks-user-5glhc 0/1 Completed 0 3h18m glance-rabbit-init-49lwx 0/1 Completed 0 3h18m glance-storage-init-brt7d 0/1 Completed 0 3h18m horizon-7d477cfb75-th4rk 1/1 Running 0 3h7m horizon-db-init-pvpqg 0/1 Completed 0 3h7m horizon-db-sync-wkhc6 0/1 Completed 0 3h7m ingress-c74489c96-69887 1/1 Running 0 3h25m ingress-c74489c96-nlfmb 1/1 Running 0 3h25m ingress-error-pages-5889bfcf6c-746ch 1/1 Running 0 3h25m ingress-error-pages-5889bfcf6c-c6rjt 1/1 Running 0 3h25m keystone-api-69d4c6dcf-qz7g2 1/1 Running 0 3h20m keystone-api-69d4c6dcf-tj8hn 1/1 Running 0 3h20m keystone-api-proxy-c5c6f49d7-wwt2b 1/1 Running 0 3h4m keystone-api-proxy-ks-endpoints-pbjb7 0/3 Completed 0 3h4m keystone-bootstrap-84jd2 0/1 Completed 0 3h20m keystone-credential-setup-ht7lg 0/1 Completed 0 3h20m keystone-db-init-6767f 0/1 Completed 0 3h20m keystone-db-sync-ck9z4 0/1 Completed 0 3h20m keystone-domain-manage-rmxgm 0/1 Completed 0 3h20m keystone-fernet-rotate-1589328000-57z6s 0/1 Completed 0 158m keystone-fernet-setup-bmn88 0/1 Completed 0 3h20m keystone-rabbit-init-7p7g7 0/1 Completed 0 3h20m mariadb-ingress-5bb8b69fc8-2gmj9 1/1 Running 0 3h25m mariadb-ingress-5bb8b69fc8-b5jzm 1/1 Running 0 3h25m mariadb-ingress-error-pages-847467b5d5-6r6v9 1/1 Running 0 3h25m mariadb-server-0 1/1 Running 0 3h25m mariadb-server-1 1/1 Running 0 3h25m osh-openstack-memcached-memcached-545668bdbd-w9bxn 1/1 Running 0 3h23m osh-openstack-rabbitmq-cluster-wait-dzmrx 0/1 Completed 0 3h22m osh-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 3h22m osh-openstack-rabbitmq-rabbitmq-1 1/1 Running 0 3h22m

I just need confirmation, is it right that Central Cloud didnt have nova service and so all workloud scheduled to sub cloud? I installed Openstack on sub cloud too and seems well like normal Openstack. Or there is something wrong in my config?