- play_arrow Overview
- play_arrow Understanding Contrail
-
- play_arrow Installing and Upgrading Contrail
- play_arrow Supported Platforms and Server Requirements
- play_arrow Installing Contrail and Provisioning Roles
- Introduction to Containerized Contrail Modules
- Downloading Installation Software
- Installing the Operating System and Contrail Packages
- Installing Containerized Contrail Clusters Using Server Manager
- Installing Containerized Contrail Using Server Manager Lite (SM-Lite)
- Supporting Multiple Interfaces on Servers and Nodes
- Configuring the Control Node with BGP
- Adding a New Node to an Existing Containerized Contrail Cluster
- Using contrailctl to Configure Services Within Containers
- Supporting Multiple Interfaces on Servers and Nodes
- Contrail Global Controller
- Role and Resource-Based Access Control
- play_arrow Installation and Configuration Scenarios
- play_arrow Using Server Manager to Automate Provisioning
- play_arrow Installing and Using Contrail Storage
- play_arrow Upgrading Contrail Software
- Upgrading Contrail 4.0 to 4.1
- Upgrade Procedure for RHOSP-based Contrail 4.1.2 to Contrail 4.1.3
- Upgrade Procedure for Ubuntu-based Contrail 4.1.3 to Contrail 4.1.4 Using Juju with Netronome SmartNIC
- Upgrade Procedure for RHOSP-based Contrail 4.1.3 to Contrail 4.1.4
- Dynamic Kernel Module Support (DKMS) for vRouter
-
- play_arrow Monitoring and Troubleshooting the Network Using Contrail Analytics
- play_arrow Understanding Contrail Analytics
- play_arrow Configuring Contrail Analytics
- play_arrow Using Contrail Analytics to Monitor and Troubleshoot the Network
- Monitoring the System
- Debugging Processes Using the Contrail Introspect Feature
- Monitor > Infrastructure > Dashboard
- Monitor > Infrastructure > Control Nodes
- Monitor > Infrastructure > Virtual Routers
- Monitor > Infrastructure > Analytics Nodes
- Monitor > Infrastructure > Config Nodes
- Monitor > Networking
- Query > Flows
- Query > Logs
- Example: Debugging Connectivity Using Monitoring for Troubleshooting
-
Using Security Groups with Virtual Machines (Instances)
Security Groups Overview
A security group is a container for security group rules. Security groups and security group rules allow administrators to specify the type of traffic that is allowed to pass through a port. When a virtual machine (VM) is created in a virtual network (VN), a security group can be associated with the VM when it is launched. If a security group is not specified, a port is associated with a default security group. The default security group allows both ingress and egress traffic. Security rules can be added to the default security group to change the traffic behavior.
Creating Security Groups and Adding Rules
A default security group is created for each project. You can add security rules to the default security group and you can create additional security groups and add rules to them. The security groups are then associated with a VM, when the VM is launched or at a later date.
To add rules to a security group: