- play_arrow Overview
- play_arrow Understanding Contrail
-
- play_arrow Installing and Upgrading Contrail
- play_arrow Server Requirements and Supported Platforms
- play_arrow Installing Contrail and Provisioning Roles
- Introduction to Containerized Contrail Modules
- Introduction to Contrail Microservices Architecture
- Downloading Installation Software
- Overview of contrail-ansible-deployer used in Contrail Command for Installing Contrail with Microservices Architecture
- Installing Contrail with OpenStack and Kolla Ansible
- Configuring the Control Node with BGP
- Contrail Global Controller
- Role and Resource-Based Access Control
- play_arrow Installation and Configuration Scenarios
- play_arrow Upgrading Contrail Software
- play_arrow Backup and Restore Contrail Software
- play_arrow Contrail Command
- play_arrow Multicloud Contrail
- play_arrow Using Contrail with Red Hat
- play_arrow Using Contrail with Juju Charms
-
- 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
-
Configuring Metadata Service
OpenStack enables virtual machines to access metadata by sending an HTTP request to the link-local address 169.254.169.254. The metadata request from the virtual machine is proxied to Nova with additional HTTP header fields that Nova uses to identify the source instance, then responds with appropriate metadata.
In Contrail, the vRouter acts as the proxy, by trapping the metadata requests, adding the necessary header fields, and sending the requests to the Nova API server.
The metadata service is configured by setting the linklocal-services
property on the global-vrouter-config
object.
Use the following elements to configure the linklocal-services
element for metadata service:
linklocal-service-name = metadata
linklocal-service-ip = 169.254.169.254
linklocal-service-port = 80
ip-fabric-service-ip = [server-ip-address]
ip-fabric-service-port = [server-port]
The linklocal-services
properties
can be set from the Contrail UI (Configure > Infrastructure >
Link Local Services) or by using the following command:
python /opt/contrail/utils/provision_linklocal.py
--admin_user <user> --admin_password <passwd> --linklocal_service_name metadata --linklocal_service_ip
169.254.169.254 --linklocal_service_port 80 --ipfabric_service_ip
--ipfabric_service_port 8775