3. Methodologies

• 3.1. Tools
  • 3.1.1. Control Plane (API) testing
    • 3.1.1.1. JMeter
    • 3.1.1.2. Gatling
    • 3.1.1.3. Wrk and Apache AB
    • 3.1.1.4. Rally
  • 3.1.2. Data Plane testing
    • 3.1.2.1. VMTP
    • 3.1.2.2. KloudBuster
    • 3.1.2.3. Shaker
      • 3.1.2.3.1. Shaker L2 Segment Topology
      • 3.1.2.3.2. Shaker L3 East-West Topology
      • 3.1.2.3.3. Shaker L3 North-South Topology
    • 3.1.2.4. Rally
    • 3.1.2.5. Browbeat
• 3.2. Methodology for testing Hyper-Scale
  • 3.2.1. What is meant by Hyper-Scale?
  • 3.2.2. How is linearity defined in this context?
  • 3.2.3. How Should Code be Instrumented When Looking for Hyper-Scale?
  • 3.2.4. Setup Considerations
  • 3.2.5. An Example: Neutron L3 Scheduling
    • 3.2.5.1. Extracting Execution Time
    • 3.2.5.2. Legacy Results Using Neutron Master as of 11/6/15 - Adding Routers/FIPs
    • 3.2.5.3. Legacy Results Using Neutron Master as of 11/6/15 - Removing Routers/FIPs
  • 3.2.6. References
• 3.3. Methodology for Containerized Openstack Monitoring
  • 3.3.1. Containerized Openstack Monitoring Architecture
    • 3.3.1.1. Operation System Layer
      • 3.3.1.1.1. Baremetal hardware description
      • 3.3.1.1.2. Operating system configuration
      • 3.3.1.1.3. Required system metrics
    • 3.3.1.2. Kubernetes Layer
      • 3.3.1.2.1. Kargo deployment parameters
      • 3.3.1.2.2. Required K8S metrics
    • 3.3.1.3. Openstack Layer
      • 3.3.1.3.1. CCP configuration
      • 3.3.1.3.2. Required Openstack-related metrics
  • 3.3.2. Implementation
    • 3.3.2.1. Server Side Software
      • 3.3.2.1.1. Prometheus
      • 3.3.2.1.2. Grafana
      • 3.3.2.1.3. ElasticSearch
      • 3.3.2.1.4. Kibana
    • 3.3.2.2. Client side Software
      • 3.3.2.2.1. Telegraf
      • 3.3.2.2.2. Heka
  • 3.3.3. Applications
    • 3.3.3.1. Kargo deployment script
      • 3.3.3.1.1. deploy_k8s_using_kargo.sh
    • 3.3.3.2. CCP deployment and configuration files
      • 3.3.3.2.1. deploy-ccp.sh
      • 3.3.3.2.2. ccp.yaml
      • 3.3.3.2.3. configs.yaml
      • 3.3.3.2.4. topology.yaml
      • 3.3.3.2.5. repos.yaml
      • 3.3.3.2.6. versions.yaml
    • 3.3.3.3. Prometheus deployment and configuration files
      • 3.3.3.3.1. Deployment scripts
      • 3.3.3.3.2. Configuration files
    • 3.3.3.4. Grafana dashboards configuration
    • 3.3.3.5. ElasticSearch deployment script
      • 3.3.3.5.1. deploy_elasticsearch_kibana.sh
    • 3.3.3.6. Telegraf deployment and configuration files
      • 3.3.3.6.1. deploy_telegraf.sh
      • 3.3.3.6.2. deploy-telegraf.yaml
      • 3.3.3.6.3. Telegraf system
      • 3.3.3.6.4. Telegraf openstack
      • 3.3.3.6.5. Telegraf inputs scripts
    • 3.3.3.7. Heka deployment and configuration
      • 3.3.3.7.1. Deployment
      • 3.3.3.7.2. Configuration
• 3.4. HA InfluxDB as an external storage for Prometheus
  • 3.4.1. Prometheus storage issue and solutions
  • 3.4.2. InfluxDB installation overview
  • 3.4.3. InfluxDB HA mechanism realization
    • 3.4.3.1. Influx-Relay
    • 3.4.3.2. Nginx
  • 3.4.4. InfluxDB Monitoring
  • 3.4.5. InfluxDB HA performance data
    • 3.4.5.1. InfluxDB database performance data
    • 3.4.5.2. OS performance data
      • 3.4.5.2.1. InfluxDB node1 OS performance
      • 3.4.5.2.2. InfluxDB node2 OS performance
      • 3.4.5.2.3. Load-balancer node OS performance
  • 3.4.6. How to deploy
  • 3.4.7. Applications
    • 3.4.7.1. InfluxdbHA deployment script
      • 3.4.7.1.1. Configuration tarball (for deployment script)
    • 3.4.7.2. InfluxDB configuration
    • 3.4.7.3. Influx-Relay configuration
      • 3.4.7.3.1. first instance
      • 3.4.7.3.2. second instance
    • 3.4.7.4. Nginx configuration
    • 3.4.7.5. Grafana InfluxDB dashboard