Add SM support for the DC admin network
This commit adds SM support for the DC admin network.
The admin network is intended to be used between a subcloud
and system controller. Because the (existing) management network
is so embedded in other parts of the StarlingX system, it makes
it prohibitively hard to re-configure this network after initial
installation. The admin network is intended to be isolated from
the management network, allowing re-configuration of the network
parameters in the case that the physical network between subcloud
and system controller has been changed.
In the case of admin network usage, the management network still
exist but is a private network in the context of a subcloud.
This specific commit provides for admin-ip and admin-interface
services to be added to the SM database and be recognized in
processing similar to the management, cluster-host, oam, etc
networks.
Since there is a requirement for the admin IP subnet information
to be allowed to change at runtime, in-service updating of SM
information relating to the admin-ip service (floating IP), as
well as unicast heartbeating between peers is also added in this
commit.
Testing:
AIO-SX:
- admin-ip service is enabled when the admin network is
created.
- admin-ip service is not enabled when the admin network is
not created.
- floating-ip is updated on the admin interface when admin
addr-pool information is changed.
AIO-DX:
- admin-ip service is enabled when the admin network is
created.
- admin-ip service is not enabled when the admin network
is not created.
- floating-ip is updated on the active-controller when the
admin addr-pool information is changed.
- When a peer admin interface is down, an alarm is raised.
- When a peer admin IP is not correct (changed), an alarm
is raised.
- Swact between controllers.
- Inactive controller admin interface goes down
Result: A 400.005 major communication loss fault is generated
for the inactive controller entity
- Inactive controller admin interface comes back up
Result: The fault is cleared
- Inactive controller admin IP address is removed/changed
Result: Two 400.005 major communication loss faults are
generated for both controller entities
- Inactive controller admin node IP address is re-applied
Result: The faults are cleared
- Active admin interface goes down
Result: A 400.005 major communication loss fault is generated
for the inactive controller entity. A swact is not
issued.
- Active admin interface comes back up
Result: The fault is cleared
- Active admin node IP address is removed/changed
Result: Two 400.005 major communication loss faults are
generated for both controller entities.
A swact is not issued.
- Active admin floating IP address is removed/changed
Result: A 400.001 critical admin-services / admin-ip alarm
is raised.
A swact occurs.
The floating admin IP is applied to the newly active
controller. Alarms are cleared.
- After the above test, the newly active controller swacts back
to the previously active controller.
Result: No alarms.
The floating IP is applied to the newly active
controller.
- The cable for the management interface on the active controller
is pulled
Result: A swact occurs
- The cable for the OAM interface on the active controller
is pulled
Result: A swact occurs
- The cable for the Admin interface on the active controller
is pulled
Result: A swact occurs. 400.005 alarms are raised.
- The mgmt, cluster-host, oam interfaces are all brought down/up at
the same time. The admin interface is also brought down,
but not brought back up
back up.
Result: A swact occurs, with multiple controller-services
related to the mgmt interface being in degraded state.
Story: 2010319
Task: 47278
Signed-off-by: Steven Webster <steven.webster@windriver.com>
Change-Id: I65df52600f4d5c499dceed32739cab414d36847a
db1eea124d