ad8665a1b7
Uses cluster hbs info to determine which controller to be the survivor when communication lost between 2 controllers with the new rules: 1. If a controller is the only controller to connect to storage-0, it is choosen to be the survivor 2. A controller that can reach more nodes is choosen to be the survivor. 3. A controller is choosen to be failed if it cannot reach any nodes. Story: 2003577 Task: 27704 Change-Id: I79659e1a788b865536500fc125fd65ae2f34123d Signed-off-by: Bin Qian <bin.qian@windriver.com> |
||
---|---|---|
api-ref/source | ||
doc | ||
releasenotes | ||
service-mgmt | ||
service-mgmt-api | ||
service-mgmt-client | ||
service-mgmt-tools | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
CONTRIBUTORS.wrs | ||
LICENSE | ||
README.rst | ||
centos_iso_image.inc | ||
centos_pike_wheels.inc | ||
centos_pkg_dirs | ||
pylint.rc | ||
test-requirements.txt | ||
tox.ini |
README.rst
stx-ha
StarlingX Service Management