Operate and maintain
Documents in this section provide background concepts and procedures for planning, deploying, and maintaining fabrics using the Fabric Services System.
- User Guide
  This document describes concepts necessary to use the Fabric Services System. It also includes procedures for designing, deploying, and maintaining fabrics, and designating fabric resources for allocation to specific sources of demand.
- API Integration Guide
  This document describes aspects of the Fabric Services System REST API.
- Connect Guide
  This document describes aspects of the Fabric Services System Connect, a collection of intermediary software that acts as a bridge between the Fabric Services System and different cloud environments.

Failover to standby in geo-redundant systems for OpenStack plugins

Note: When the Fabric Services System control plane is not operational, OpenStack networking requests resulting in API calls to Connect/Fabric Services System fail; the OpenStack command itself fails, preserving system integrity.

Use the following steps to switchover to the standby system for an OpenStack Cloud operating a Fabric Services System managed fabric:

Initiate the switch-over to the new active cluster.

For instructions, see Initiating failover: switching between the active and standby clusters in the Fabric Services System User Guide.
When the new active cluster is operational, initiate a Connect Full audit on the new active Fabric Services System.
Send the following Connect REST API request:
```
HTTP(S) POST {connect_uri}/rest/connect/api/v1/admin/audits {"deploymentId": "<deployment_id>", "scope": "FULL", "dryrun": false}
```

May 31, 2024