Deployment Options for GigaVUE Cloud Suite for OpenStack
This section provides a detailed information on the multiple ways in which GigaVUE Cloud Suite for OpenStack can be configured to provide visibility for physical and virtual traffic. There are four different ways in which GigaVUE Cloud Suite for OpenStack can be configured based on the traffic acquisition method and the method in which you want to deploy fabric components. Refer to theBefore You Begin topic for minimum requirements and prerequisites. For more detailed information and work flow refer 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 supported by these nodes. Refer the following table for the step-by-step instructions.
| Step No | Task | Refer the following 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 Agents. |
For Linux: Linux UCT-V Installation For Windows: Windows UCT-V Installation |
|
3 |
Create a Monitoring Domain Note: Ensure that the Use FM to Launch Fabric toggle button is disabled. |
|
|
4 |
Configure GigaVUE Fabric Components Note: Select UCT-V as the Traffic Acquisition Method. |
|
|
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
If you wish to deploy your fabric components using GigaVUE‑FM, it can done is three ways based on the traffic acquisition method you chose.
Traffic Acquisition Method as UCT-V
Follow instruction in the below table if you wish to use UCT-V as your traffic acquisition method. In this case the traffic from the Virtual Machines are acquired using the UCT-Vs and it is 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 Note: Ensure that the Use FM to Launch Fabric toggle button is enabled. |
|
|
4 |
Configure GigaVUE Fabric Components Note: Select UCT-V as the Traffic Acquisition Method. |
|
|
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 instruction in the below table if you wish to use OVS Mirroring as your traffic acquisition method. Open vSwitch Mirroring Agent is deployed on the hypervisor where the Virtual Machines you wish to monitor are located. Refer to the Prerequisites for OVS Mirroring topic for OpenStack cloud requirements before using OVS Mirroring as your traffic acquisition type.
| Step No | Task | Refer the following topics |
|---|---|---|
|
1 |
Install GigaVUE-FM on OpenStack |
|
|
2 |
Install UCT-V OVS Agents |
|
|
3 |
Create a Monitoring Domain Note: Ensure that the Use FM to Launch Fabric toggle button is enabled. |
|
|
4 |
Configure GigaVUE Fabric Components Note: Select OVS Mirroring as the Traffic Acquisition Method. |
|
|
5 |
Create Monitoring session |
|
|
6 |
Add Applications to the Monitoring Session |
|
|
7 |
Deploy Monitoring Session |
|
|
8 |
View Monitoring Session Statistics |
Traffic Acquisition Method as Tunnel
Follow instruction in the below table if you wish to use Tunnel 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 | Refer the following topics |
|---|---|---|
|
1 |
Install GigaVUE-FM on OpenStack |
|
|
2 |
Create a Monitoring Domain Note: Ensure that the Use FM to Launch Fabric toggle button is enabled. |
|
|
3 |
Configure GigaVUE Fabric Components Note: Select Tunnel as the Traffic Acquisition Method. |
|
|
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 |
