Deployment Options for GigaVUE Cloud Suite for OpenStack
This section provides information about configuring GigaVUE Cloud Suite for OpenStack, using multiple ways, to provide visibility for physical and virtual traffic. You can configure GigaVUE Cloud Suite for OpenStack in four ways based on the traffic acquisition method and the method you want to deploy fabric components.
For details on minimum requirements and prerequisites, refer toBefore You Begin
For details and workflow, refer to the following topics:
Deploy GigaVUE Fabric Components using OpenStack
GigaVUE‑FM allows you to use OpenStack as an orchestrator to deploy GigaVUE fabric nodes and then use GigaVUE‑FM to configure the advanced features these nodes support. For instructions, refer to the table below.
Step No | Task | Reference topics |
---|---|---|
1 |
Install GigaVUE‑FM on OpenStack
|
|
2 |
Install UCT-Vs Note: When using OpenStack as your orchestration system you can only use G-TAP Modules. |
For Linux: Linux UCT-V Installation For Windows: Windows UCT-V Installation |
3 |
Create a Monitoring Domain
|
|
4 |
Configure GigaVUE Fabric Components |
|
5 |
Create Monitoring session |
|
6 |
Add Applications to the Monitoring Session |
|
7 |
Deploy Monitoring Session |
|
8 |
View Monitoring Session Statistics |
Deploy GigaVUE Fabric Components using GigaVUE‑FM
You can deploy your fabric components using GigaVUE‑FM in the following three ways based on the traffic acquisition method you chose:
Traffic Acquisition Method as UCT-V
Follow the instructions in the table below to use UCT-V as your traffic acquisition method. In this case, the traffic from the Virtual Machines is acquired using the UCT-Vs and sent to the V Series nodes.
Step No | Task | Refer the following topics |
---|---|---|
1 |
Install GigaVUE‑FM on OpenStack |
|
2 |
Install UCT-Vs |
For Linux: Linux UCT-V Installation For Windows: Windows UCT-V Installation |
3 |
Create a Monitoring Domain
|
|
4 |
Configure GigaVUE Fabric Components |
|
5 |
Create Monitoring session |
|
6 |
Add Applications to the Monitoring Session |
|
7 |
Deploy Monitoring Session |
|
8 |
View Monitoring Session Statistics |
Traffic Acquisition Method as OVS Mirroring
Follow the instructions in the table below to use OVS Mirroring as your traffic acquisition method. Open vSwitch Mirroring Module is deployed on the hypervisor where the Virtual Machines you wish to monitor are located.
For OpenStack cloud requirements before using OVS Mirroring as your traffic acquisition type, refer to Prerequisites for OVS Mirroring.
Step No | Task | Reference topics |
---|---|---|
1 |
Install GigaVUE‑FM on OpenStack |
|
2 |
Install UCT-V OVS Modules |
|
3 |
Create a Monitoring Domain
|
|
4 |
Configure GigaVUE Fabric Components |
|
5 |
Create Monitoring session |
|
6 |
Add Applications to the Monitoring Session |
|
7 |
Deploy Monitoring Session |
|
8 |
View Monitoring Session Statistics |
Traffic Acquisition Method as Customer Orchestrated Source
Follow the instructions in the table below to use Customer Orchestrated Source as your traffic acquisition method. In this case, you can use tunnels as a source where the traffic is directly tunneled to V Series nodes without deploying UCT-Vs or UCT-V Controllers.
Step No | Task | Reference topics |
---|---|---|
1 |
Install GigaVUE‑FM on OpenStack |
|
2 |
Create a Monitoring Domain Note: Ensure the 'Use FM to Launch Fabric' toggle button is enabled.
|
|
3 |
Configure GigaVUE Fabric Components |
|
4 |
Create Monitoring session |
|
5 |
Create Ingress and Egress Tunnel Endpoints |
|
6 |
Add Applications to the Monitoring Session |
|
7 |
Deploy Monitoring Session |
|
8 |
View Monitoring Session Statistics |