Swact taking longer in Debian than CentOS due to rabbit & sysinv-inv

[Lucas Borges]

Brief Description

KPI analysis using data from automation execution data from CentOS and Debian indicate that the controlled SWACT operation takes ~40% longer in Debian.

Severity

Minor

Steps to Reproduce

Do the Swact

Expected Behavior

Swact time from Debian should be 10% or less than CentOS.

Actual Behavior

Deviation in SWACT activity duration by 41%.

Reproducibility

Always

Last Pass

NA

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/ha/+/884615
Committed: https://opendev.org/starlingx/ha/commit/42fb99a393df963eefdd99df75f5d0ec3bf6ac1c
Submitter: "Zuul (22348)"
Branch: master

commit 42fb99a393df963eefdd99df75f5d0ec3bf6ac1c
Author: Lucas Borges <email address hidden>
Date: Mon May 29 09:38:07 2023 -0300

    Removing sysinv-conductor dependency from rabbitmq

    The Sysinv components utilize ZeroMQ for communication
    among each other. The service dependency between
    sysinv-conductor and rabbit are removed on Service Manager
    improving the time it takes to swact, by 20%.

    Test Plan:

    PASS: Bootstrap AIO-SX, AIO-DX and Standard.
    PASS: Lock/unlock/swact in all environments
    PASS: Boostrap DC and perform lock/unlock/swact
    PASS: Add subcloud in DC environment
    PASS: Test DC orchestration (dcmanger dcorch)
    PASS: Restart sysinv only
    PASS: Restart sysinv, then dcorch and dcmanager
    PASS: After restart sysinv, dcorch and dcmanager run manage/unmanage
    PASS: After restart sysinv, run subcloud backup
    PASS: After all restart of services verify the whole system is working

    Refer to review
    https://review.opendev.org/c/starlingx/config/+/859571
    for sysinv/ZeroMQ change details

    Closes-bug: 2022083
    Signed-off-by: Lucas Borges <email address hidden>
    Change-Id: I4014c05c914fc946946b14519f28a85067b06b34