Hi Shuicheng

 

We specifically wanted to understand whether “Openstack Services” like Nova, Neutron etc are working in Active/Active or Active/StandBy.

In the “sm-dump”, there are “vim-services” mentioned, but there is no information about the state of individual “Neutron“ services and all other.

 

controller-0:/home/sysadmin# sm-dump

 

-Service_Groups------------------------------------------------------------------------

oam-services                     standby              standby

controller-services              standby              standby

cloud-services                   standby              standby

patching-services                standby              standby

directory-services               active               active

web-services                     active               active

storage-services                 active               active

storage-monitoring-services      standby              standby

vim-services                     standby              standby

---------------------------------------------------------------------------------------

 

-Services------------------------------------------------------------------------------

oam-ip                           enabled-standby      disabled

management-ip                    enabled-standby      disabled

drbd-pg                          enabled-standby      enabled-standby

drbd-rabbit                      enabled-standby      enabled-standby

drbd-cgcs                        enabled-standby      enabled-standby

drbd-platform                    enabled-standby      enabled-standby

pg-fs                            enabled-standby      disabled

rabbit-fs                        enabled-standby      disabled

nfs-mgmt                         enabled-standby      disabled

cgcs-fs                          enabled-standby      disabled

platform-fs                      enabled-standby      disabled

postgres                         enabled-standby      disabled

rabbit                           enabled-standby      disabled

cgcs-export-fs                   enabled-standby      disabled

platform-export-fs               enabled-standby      disabled

cgcs-nfs-ip                      enabled-standby      disabled

platform-nfs-ip                  enabled-standby      disabled

sysinv-inv                       enabled-standby      disabled

sysinv-conductor                 enabled-standby      disabled

mtc-agent                        enabled-standby      disabled

hw-mon                           enabled-standby      disabled

dnsmasq                          enabled-standby      disabled

fm-mgr                           enabled-standby      disabled

keystone                         enabled-standby      disabled

open-ldap                        enabled-active       enabled-active

snmp                             enabled-standby      disabled

lighttpd                         enabled-active       enabled-active

horizon                          enabled-active       enabled-active

patch-alarm-manager              enabled-standby      disabled

mgr-restful-plugin               enabled-active       enabled-active

ceph-manager                     enabled-standby      disabled

vim                              enabled-standby      disabled

vim-api                          enabled-standby      disabled

vim-webserver                    enabled-standby      disabled

guest-agent                      enabled-standby      disabled

haproxy                          enabled-standby      disabled

pxeboot-ip                       enabled-standby      disabled

drbd-extension                   enabled-standby      enabled-standby

extension-fs                     enabled-standby      disabled

extension-export-fs              enabled-standby      disabled

etcd                             enabled-standby      disabled

drbd-etcd                        enabled-standby      enabled-standby

etcd-fs                          enabled-standby      disabled

barbican-api                     enabled-standby      disabled

barbican-keystone-listener       enabled-standby      disabled

barbican-worker                  enabled-standby      disabled

cluster-host-ip                  enabled-standby      disabled

docker-distribution              enabled-standby      disabled

dockerdistribution-fs            enabled-standby      disabled

drbd-dockerdistribution          enabled-standby      enabled-standby

ceph-mon                         enabled-standby      disabled

cephmon-fs                       enabled-standby      disabled

drbd-cephmon                     enabled-standby      enabled-standby

ceph-osd                         enabled-active       enabled-active

helmrepository-fs                enabled-standby      disabled

registry-token-server            enabled-standby      disabled

dbmon                            enabled-standby      enabled-standby

------------------------------------------------------------------------------

 

 

In order to verify it, we captured “neutron-server” logs of both the StarlingX servers.

 

Case 1: Horizon is accessed using Floating Ip and One VM is spawned

 

It goes on Active Controller and “neutron-server” logs of Active Controller shows the creation of network port and assigning port to the VM.

 

Case 2: Horizon is accessed using Floating Ip and Two VM’s are spawned simultaneously

 

In this case, one VM gets spawned on Active Controller and Other on Standby Controller.

But “neutron-server” logs of both the controller shows the creation of network port and assigning port to the VM.

 

Inference:

As per our understanding, if all the “Openstack Services” were configured in Active/Standby, then request would have come to only Active Controller.

But, in this case both the Controllers are serving the request which implies that all the Openstack Services are configured in “Active/Active” State

 

Is our understanding correct that the StarlingX Nodes are in Active-Standby configuration, but all the Openstack Services are configured in Active-Active State?

 

Regards

Anirudh Gupta

 

 

From: Lin, Shuicheng <shuicheng.lin@intel.com>
Sent: 03 December 2019 05:57
To: Anirudh Gupta <Anirudh.Gupta@hsc.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: [Starlingx-discuss] StarlingX 2.0 Duplex Controller in Active/Active HA

 

Hi Anirudh,

What is the purpose or benefit you want to have 2 active controller?

I think it is reasonable there is 1 active controller only, and another controller is standby for backup, this is the meaning of HA.

Two active controller at the same time will cause brain split.

What do you mean “Openstack Services”? Openstack is containerized now, and run in both nodes by K8S.

 

Best Regards

Shuicheng

 

From: Anirudh Gupta <Anirudh.Gupta@hsc.com>
Sent: Monday, December 2, 2019 6:59 PM
To: Lin, Shuicheng <shuicheng.lin@intel.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: [Starlingx-discuss] StarlingX 2.0 Duplex Controller in Active/Active HA

 

Hi Shuicheng,

 

All the services on the Active Controller are “enabled-active” and I can see some services “enabled-standby” on the standby controller.

 

Is there any way we can set all the Openstack Services “enabled-active” on both the Active and Standby Node?

 

Regards

Anirudh Gupta

 

From: Lin, Shuicheng <shuicheng.lin@intel.com>
Sent: 01 December 2019 12:42
To: Anirudh Gupta <Anirudh.Gupta@hsc.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: [Starlingx-discuss] StarlingX 2.0 Duplex Controller in Active/Active HA

 

Hi Anirudh,

Per my understanding, for duplex, there is always 1 active node and 1 standby node.

The active/active” or “active/standby” in the document is for “services”, not for node.

If you try to run “sudo sm-dump” in the standby node, you will find some services are “active”, while some services are “standby”.

 

For the 2nd question, VMs are running in compute node. And for duplex, both controller nodes are compute nodes also.

And the “Active/Standby” is for controller, not for compute function, that is why VMs will run in both node.

 

Best Regards

Shuicheng

 

From: Anirudh Gupta <Anirudh.Gupta@hsc.com>
Sent: Thursday, November 28, 2019 11:45 AM
To: starlingx-discuss@lists.starlingx.io; starlingx-announce@lists.starlingx.io
Subject: Re: [Starlingx-discuss] StarlingX 2.0 Duplex Controller in Active/Active HA

 

Hi Team,

 

Can someone please give me any update on my Query:

 

I need to install StarlingX 2.0 Duplex Bare Metal.

As per the document, there can be 2 modes in which HA controllers can be configure i.e. either active/active” or “active/standby”
https://docs.starlingx.io/deploy_install_guides/r2_release/bare_metal/aio_duplex.html

 

 

Regards

Anirudh Gupta

 

 

From: Anirudh Gupta
Sent: 26 November 2019 10:30
To: starlingx-discuss@lists.starlingx.io; starlingx-announce@lists.starlingx.io
Subject: StarlingX 2.0 Duplex Controller in Active/Active HA

 

Hi Team,

 

I need to install StarlingX 2.0 Duplex Bare Metal.

As per the document, there can be 2 modes in which HA controllers can be configure i.e. either active/active” or “active/standby”
https://docs.starlingx.io/deploy_install_guides/r2_release/bare_metal/aio_duplex.html

 

Can someone please suggest the steps to configure Active-Active state?

And, what difference it would have on my deployment in terms of functionality?

 

 

Regards

Anirudh Gupta

 

DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.