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

Rahmat Agung agung at btech.id
Tue May 12 16:07:37 UTC 2020


Check, is this the right reply? My first time using milist. :D
Ah, I missed that step. Has been resolved now. Thanks.
But I found a new issue. It seems one of my controller on Central cloud
`degraded` after joining subcloud. Any clue? Or what log I should look for?
Then I do following step:
1. Reboot my controller-0
2. Then, active controller changed to controller-1
3. Boom! no more degraded controller.

My issue right now: There is alarm:
Platform Memory threshold exceeded ; threshold 80.00%, actual 86.87%

But when i checked my host, my used memory still about 20%?

On Tue, May 12, 2020 at 5:34 PM Rahmat Agung <agung at btech.id> wrote:

> Hi, so I have distributed cloud cluster:
> --------------------------------------------------------------
> 1 Central Cloud - AIO Duplex
> OAM: 10.10.10.0/24, MGMT:192.168.1.0/24
> --------------------------------------------------------------
> 1 Subcloud - AIO-Simplex
> OAM: 10.10.11.0/24, MGMT: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 scope host lo
>>        valid_lft forever preferred_lft forever
>>     inet 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 brd 192.168.206.255 scope host lo:5
>>        valid_lft forever preferred_lft forever
>>     inet 169.254.202.1/24 scope host lo
>>        valid_lft forever preferred_lft forever
>>     inet 192.168.206.1/24 scope host secondary lo
>>        valid_lft forever preferred_lft forever
>>     inet 192.168.2.2/24 scope host secondary lo
>>        valid_lft forever preferred_lft forever
>>     inet 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 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 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/283eb1ee/attachment.html>


More information about the Starlingx-discuss mailing list