Troubleshooting and Tuning OpenStack Neutron

Transcription

1 Troubleshooting and Tuning OpenStack Neutron Référence du cours Education Services H8Q17 Durée du Cours 2 jours Mode de réalisation : ILT (Instructor Led Training) Virtual Instructor Led Training (vilt) Inscription Cliquez ici pour aller sur HPE Learning Portal Cette formation de deux jours donne aux participants une connaissance approfondie des éléments complexes du réseau dans OpenStack qui utilise Neutron. L'objectif est d'acquérir les connaissances nécessaires pour concevoir, construire, gérer et dépanner une solution réseau évolutive, extensible et hautement disponible dans un environnement OpenStack. Les participants acquièrent une expérience pratique sur les différents sujets du cours grâce à des Travaux Pratiques réalisés dans un environnement OpenStack dédié et préconstruit. Ce cours prépare les participants à passer le niveau de certification experts sur OpenStack. Notez que la partie théorique et les labs couvrent la dernière mise à jour de Neutron qui a été introduite avec la release Kilo. Audience Administrateurs réseaux Architectes Réseaux Architectes de solution Ingénieurs Commerciaux Membres équipes Marketing Administrateurs OpenStack Architectes OpenStack Pré-requis Une bonne expérience des fondamentaux des réseaux : TCP/IP Ethernet Créé en Novembre 2015

2 Routage et firewalls Haute disponibilité et tolérance aux erreurs Familier avec les outils de mesure de performances : ping tcpdump traceroute Wireshark Et avoir suivi les cours suivant ou avoir des connaissances équivalentes : Fortement recommandé : Networking in OpenStack using Neutron (H4S71S) Fundamentals of OpenStack Technology (H6C68S) Linux Fundamentals (U8583S) Objectifs du Cours : A l'issue de ce cours, vous serez capable de: Nommez les fonctionnalités d'openstack neutrons qui affectent les performances, l évolutivité et la disponibilité Expliquer l approche de Neutron en ce qui concerne la haute disponibilité et la tolérance aux erreurs Utiliser les outils de surveillance et de mesures pour optimiser les performances dans un environnement Neutron Utiliser les outils de logging, debugging, etc pour effectuer des résolutions d incidents avancées dans un environnement OpenStack. Contenu détaillé du Cours Module 1 Neutron Features that Affect Performance Features in Neutron that affect performance, scalability, and availability o DVR o IPv6 routing o ML2 hierarchical port binding o Subnet allocation for creating subnets from a pre-defined pool of addresses Jumbo frames in VXLAN and GRE project networks High-level overview of Kilo enhancements Neutron plug-ins and extensions o Neutron plug-ins and extensions overview o Extensibility o ML2 plug-in Scalability in Neutron o Scalability issues and resolutions o Scalability considerations o L2 population driver Neutron autoscaling with Heat Vertical and horizontal scaling Lab 0 Assembling the Network Map Exercise 1 Use Neutron and OpenStack commands to discover and document the network topology Exercise 2 Building the network map Lab 1 Legacy Routing Exercise 1 Tracing network traffic using tcpdump and ovs-ofctl commands Exercise 2 Measuring performance with ping, traceroute, and wget H8Q17SA.00 - Créé en Novembre

3 Exercise 3 Performing CRUD operations using curl Exercise 4 Troubleshooting network issues using ping, tcpdump, ovs-vsctl, and other tools Module 2 High availability Goals of high availability Neutron high availability and fault tolerance Stateless compared to stateful services Active/passive and active/active configurations Pacemaker cluster stack Cloud controller cluster stack API node cluster stack Neutron controller cluster stack HAProxy o o Basic monitoring functions OpenStack network nodes L3 agent o L3 agent and namespaces o L3 metering agent o L3 architecture for high availability o Multiple external networks Distributed Virtual Routing (DVR) o The problem: Single points of failure o The solution: Distributed Virtual Routing o DVR logical architecture o DVR components o DVR deployment with FIP o VLAN support for DVR o Scenario: High availability using DVR o Scenario with DVR: North/south for instances with a fixed IP address o Scenario with DVR: North/south for instances with a floating IP address o Scenario with DVR: East/west for instances using different networks on the same router ML2 hierarchical port binding o ML2 hierarchical port binding process o ML2 hierarchical port binding from Juno to Kilo o ML2 hierarchical port binding methods Subnet allocation Scenarios and use cases o Scenario: L3 high availability and Open vswitch o Scenario: L3 high availability and Open vswitch node requirements o Scenario: Scalable and highly available DHCP agents Lab 2 DVR Implementation Exercise 1 Demonstrating the advantages of DVR Configuring DVR on two compute nodes. Exercise 2 Using ping, traceroute, and wget to measure network performance as a result of DVR Exercise 3 Troubleshooting DVR network issues Lab 3 Layer 3 High Availability Exercise 1 Tracing network traffic using tcpdump and demonstrating the advantages of L3 HA Exercise 2 Measuring network performance to demonstrate the advantages of L3 HA H8Q17SA.00 - Créé en Novembre

4 Exercise 3 Troubleshooting L3 HA network issues using ping, tcpdump, ovs-vsctl, and other tools Module 3 Optimizing performance Performance tuning o Metrics for measuring network performance o Approaches for measuring network performance o Previous testing Performance monitoring tools o Tools for measuring network performance Performance measuring tools VMTP Performance measuring tools Shaker Performance measuring tools Pktgen Netmap Using ping to find a failure in the path The traceroute command The dig command tcpdump Wireshark Using the ip command Open vswitch and performance o Effects of increasing kernel flows o OVS data plane performance o OVS packet processing o Security groups compared with OVS Traffic flow between Neutron nodes/components o Scenario: General provider network o Network packet flow Load Balancer-as-a-Service and Firewall-as-a-Service o Neutron advanced services o LBaaS o LBaaS versions o LBaaS operations o FWaaS overview o FWaaS changes to support DVR o Using FWaaS o Implementing a firewall with OVS by using Netfilter Connection Tracker NFV and SR-IOV o Network Functions Virtualization o VLAN trunking networks for NFV o SR-IOV networking Configuring a VM to use SR-IOV Bonding SR-IOV interfaces in a VM IPv6 o IPv6 features in Juno and Kilo o Load balancing with VRRP 3 for IPv4 and IPv6 Best practices Module 4 Troubleshooting, Debugging, and Known Issues Troubleshooting methodology o Six-step troubleshooting methodology Managing logging levels and examining log files o OpenStack log files o Reading the logs o Centralized logging using rsyslog o Using Open vswitch commands Using Open vswitch commands H8Q17SA.00 - Créé en Novembre

5 o Open vswitch mirroring o Enabling OVSTD Monitor Debugging o Using debugging tools o Neutron debug command o Debugging Neutron issues o Debugging Open vswitch o Debugging issues reaching the VMs o Debugging DNS issues o Debugging DHCP issues o RabbitMQ Web Management Interface and rabbitmqctl Troubleshooting o Troubleshooting OVS networking traffic o Troubleshooting OVS configuration o Troubleshooting Open vswitch with ovs-vsctl o Troubleshooting SR-IOV o Troubleshooting the Identity service Known issues o Unable to ping or SSH to the VM o Running the add-port command loses connectivity through eth0 o ML2 DVR non-distributed/distributed ports o DVR router scheduling issue o Reserving DHCP port during failovers o Cannot reach floating IPs o Packet loss on the connection to the instance o OVS agent scans all ports on integration bridge at each iteration Resources for troubleshooting Lab 4 Using Troubleshooting Tools Exercise 1 Managing logging levels and examining log files Exercise 2 Monitoring traffic flow through the network using tcpdump and Wireshark Exercise 3 Using rabbitmqctl to troubleshoot rabbitmq messaging service Exercise 4 Using MySQL to troubleshoot database issues Lab 5 Troubleshooting Network Issues Exercise 1 Troubleshooting issues with legacy, distributed, and L3 HA routing H8Q17SA.00 - Créé en Novembre