[Starlingx-discuss] Distributed Cloud Deployement - Add Subcloud Problem

Wensley, Barton Barton.Wensley at windriver.com
Tue May 12 11:40:23 UTC 2020


Hey Rahmat - when an AIO-SX host is configured as a subcloud, the MGMT interface must be a physical interface. Assuming you are using the stx.3.0 release you can see this instruction here:
https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex_install_kubernetes.html#configure-controller-0

Step 4 speaks to this specifically.

Bart

From: Rahmat Agung [mailto:agung at btech.id]
Sent: May 12, 2020 6:35 AM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] Distributed Cloud Deployement - Add Subcloud Problem

Hi, so I have distributed cloud cluster:
--------------------------------------------------------------
1 Central Cloud - AIO Duplex
OAM: 10.10.10.0/24<http://10.10.10.0/24>, MGMT:192.168.1.0/24<http://192.168.1.0/24>
--------------------------------------------------------------
1 Subcloud - AIO-Simplex
OAM: 10.10.11.0/24<http://10.10.11.0/24>, MGMT:192.168.2.0/24<http://192.168.2.0/24>
---------------------------------------------------------------

I little bit confused because on my subcloud, the MGMT interface attached to loopback interface.

[sysadmin at controller-0 ~(keystone_admin)]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8<http://127.0.0.1/8> scope host lo
       valid_lft forever preferred_lft forever
    inet 192.168.2.3/24<http://192.168.2.3/24> brd 192.168.2.255 scope host lo:1
       valid_lft forever preferred_lft forever
    inet 192.168.206.2/24<http://192.168.206.2/24> brd 192.168.206.255 scope host lo:5
       valid_lft forever preferred_lft forever
    inet 169.254.202.1/24<http://169.254.202.1/24> scope host lo
       valid_lft forever preferred_lft forever
    inet 192.168.206.1/24<http://192.168.206.1/24> scope host secondary lo
       valid_lft forever preferred_lft forever
    inet 192.168.2.2/24<http://192.168.2.2/24> scope host secondary lo
       valid_lft forever preferred_lft forever
    inet 192.168.2.5/24<http://192.168.2.5/24> scope host secondary lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth1000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:56:1b:8d brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5054:ff:fe56:1b8d/64 scope link
       valid_lft forever preferred_lft forever
3: eth1001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:4e:57:50 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5054:ff:fe4e:5750/64 scope link
       valid_lft forever preferred_lft forever
4: enp7s1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:ba:44:7f brd ff:ff:ff:ff:ff:ff
    inet 10.10.11.3/24<http://10.10.11.3/24> brd 10.10.11.255 scope global enp7s1
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:feba:447f/64 scope link
       valid_lft forever preferred_lft forever
5: enp7s2: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 52:54:00:63:f3:6d brd ff:ff:ff:ff:ff:ff
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:90:6e:41:f5 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16<http://172.17.0.1/16> brd 172.17.255.255 scope global docker0
--more--


Then, when I did route to join subcloud to central cloud it got this notification.

[sysadmin at controller-0 ~(keystone_admin)]$ system host-route-add 1 lo 192.168.1.0 24 192.168.2.1
No entry found for interface 5
[sysadmin at controller-0 ~(keystone_admin)]$

Is there something wrong with my configuration?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20200512/90d63028/attachment-0001.html>


More information about the Starlingx-discuss mailing list