Configure GigaVUE Fabric Components in Azure
This section provides step-by-step information on how to register GigaVUE fabric components using Azure Portal or a configuration file.
Overview of Third-Party Orchestration
You can use your own Azure Orchestrator to deploy the GigaVUE fabric nodes instead of using GigaVUE‑FM to deploy your fabric components.
The third-party orchestration feature allows you to deploy GigaVUE fabric components using your own Azure orchestration system. These fabric components register themselves with GigaVUE-FM using the information provided by the user. Once the nodes are registered with GigaVUE-FM, you can configure monitoring sessions and related services in GigaVUE-FM.
You can either manually deploy the fabric nodes using a configuration file, or you can use the Azure portal to launch the instances and deploy the fabric nodes using Custom data. Using the Custom data provided by you, the fabric nodes register themselves with the GigaVUE‑FM. Based on the group name and the subgroup name details provided in the Custom data, GigaVUE‑FM groups these fabric nodes under their respective monitoring domain and connection name. The health status of the registered nodes is determined by the heartbeat messages sent from the respective nodes.
You can also upload custom certificates to GigaVUE V Series Nodes, GigaVUE V Series Proxy, and UCT-V Controller using your own cloud platform when deploying the fabric components. Refer to Install Custom Certificate for more detailed information.
Refer to the following for more detailed information and step-by-step instructions on how to deploy GigaVUE Fabric Components using Azure:
