Openstack Rally - Benchmark as a Service. Openstack Meetup India. Ananth/Rahul.Rahul Krishna Upadhyaya
Slide deck used at the presentation at Openstack India Meetup on 01/March 2014 at Netapp, Bangalore. Slide talks about installation and use of Rally and its scope to benchmark and measure performance. There is little on how to install Cisco Openstack as a All in One setup.
This document discusses benchmarking OpenStack at scale using Rally. Rally allows OpenStack developers and operators to generate relevant and repeatable benchmarking data on how their cloud operates under different workloads and levels of load. It provides examples of synthetic stress tests and real-life workload scenarios that can be used for benchmarking. The goals of Rally are to help identify performance bottlenecks, validate optimizations, and provide historical data for comparing cloud performance over time as OpenStack and deployments evolve.
Rally is an OpenStack project that allows developers and operators to benchmark OpenStack deployments at scale. It was presented at an OpenStack meetup in Noida, India on January 13, 2015. The presentation covered why Rally is useful for ensuring OpenStack works at scale, detecting performance issues, and running Tempest tests without Tempest setup overhead. It also demonstrated various Rally features through a series of demos showing how to install, configure, run tests on, and view results from an OpenStack cloud deployment using Rally.
Using Rally for OpenStack certification at ScaleBoris Pavlovic
It goes without saying that one of the most important things all OpenStack clouds from big to small is to be 100% sure that everything works as expected BEFORE taking on production workloads.
To ensure that production workloads will be successful, we can do a few key things:
1) Generate real load test from "real" OpenStack users
2) Collect and retain detailed execution data for examination and historical comparison
3) Measure workload performance and failure rate against established SLAs to validate a deployment
4) Visualize results in beautiful graphic detail
Rally can fully automate these steps for you and save dozens if not hundreds of hours.
Full talk you can find here:
https://www.youtube.com/watch?v=-g1tuTLcxik
HKG15-204: OpenStack: 3rd party testing and performance benchmarkingLinaro
HKG15-204: OpenStack: 3rd party testing and performance benchmarking
---------------------------------------------------
Speaker: Andrew McDermott, Clark Laughlin
Date: February 10, 2015
---------------------------------------------------
★ Session Summary ★
Status of Tempest 3rd party testing, discussion on scenarii for Rally benchmarking and hypervisor performance.
--------------------------------------------------
★ Resources ★
Pathable: https://hkg15.pathable.com/meetings/250785
Video: https://www.youtube.com/watch?v=-00rTPCYAyg
Etherpad: http://pad.linaro.org/p/hkg15-204
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2015 - #HKG15
February 9-13th, 2015
Regal Airport Hotel Hong Kong Airport
---------------------------------------------------
http://www.linaro.org
http://connect.linaro.org
OpenStack Watcher is an OpenStack project that performs resource optimization in OpenStack clouds after VM deployment. It aims to rebalance the environment over time using VM live migration if imbalances are detected. Watcher provides cloud optimization, granular optimization goals, evolvability via plugins, and out-of-the-box optimization strategies for CPU, RAM, and energy. It can run in advise, active, or verbose modes.
OpenStack Nova - Developer IntroductionJohn Garbutt
This document provides an overview of Nova, OpenStack's compute service. It discusses Nova's architecture, code structure, API concepts, upgrade process, and how different groups work together as part of the upstream community. The new upgrade process aims to minimize downtime by expanding the database schema, restarting services individually, and signaling services to reload configuration. Collaboration across various groups with different perspectives is important to OpenStack's open development model.
Openstack Rally - Benchmark as a Service. Openstack Meetup India. Ananth/Rahul.Rahul Krishna Upadhyaya
Slide deck used at the presentation at Openstack India Meetup on 01/March 2014 at Netapp, Bangalore. Slide talks about installation and use of Rally and its scope to benchmark and measure performance. There is little on how to install Cisco Openstack as a All in One setup.
This document discusses benchmarking OpenStack at scale using Rally. Rally allows OpenStack developers and operators to generate relevant and repeatable benchmarking data on how their cloud operates under different workloads and levels of load. It provides examples of synthetic stress tests and real-life workload scenarios that can be used for benchmarking. The goals of Rally are to help identify performance bottlenecks, validate optimizations, and provide historical data for comparing cloud performance over time as OpenStack and deployments evolve.
Rally is an OpenStack project that allows developers and operators to benchmark OpenStack deployments at scale. It was presented at an OpenStack meetup in Noida, India on January 13, 2015. The presentation covered why Rally is useful for ensuring OpenStack works at scale, detecting performance issues, and running Tempest tests without Tempest setup overhead. It also demonstrated various Rally features through a series of demos showing how to install, configure, run tests on, and view results from an OpenStack cloud deployment using Rally.
Using Rally for OpenStack certification at ScaleBoris Pavlovic
It goes without saying that one of the most important things all OpenStack clouds from big to small is to be 100% sure that everything works as expected BEFORE taking on production workloads.
To ensure that production workloads will be successful, we can do a few key things:
1) Generate real load test from "real" OpenStack users
2) Collect and retain detailed execution data for examination and historical comparison
3) Measure workload performance and failure rate against established SLAs to validate a deployment
4) Visualize results in beautiful graphic detail
Rally can fully automate these steps for you and save dozens if not hundreds of hours.
Full talk you can find here:
https://www.youtube.com/watch?v=-g1tuTLcxik
HKG15-204: OpenStack: 3rd party testing and performance benchmarkingLinaro
HKG15-204: OpenStack: 3rd party testing and performance benchmarking
---------------------------------------------------
Speaker: Andrew McDermott, Clark Laughlin
Date: February 10, 2015
---------------------------------------------------
★ Session Summary ★
Status of Tempest 3rd party testing, discussion on scenarii for Rally benchmarking and hypervisor performance.
--------------------------------------------------
★ Resources ★
Pathable: https://hkg15.pathable.com/meetings/250785
Video: https://www.youtube.com/watch?v=-00rTPCYAyg
Etherpad: http://pad.linaro.org/p/hkg15-204
---------------------------------------------------
★ Event Details ★
Linaro Connect Hong Kong 2015 - #HKG15
February 9-13th, 2015
Regal Airport Hotel Hong Kong Airport
---------------------------------------------------
http://www.linaro.org
http://connect.linaro.org
OpenStack Watcher is an OpenStack project that performs resource optimization in OpenStack clouds after VM deployment. It aims to rebalance the environment over time using VM live migration if imbalances are detected. Watcher provides cloud optimization, granular optimization goals, evolvability via plugins, and out-of-the-box optimization strategies for CPU, RAM, and energy. It can run in advise, active, or verbose modes.
OpenStack Nova - Developer IntroductionJohn Garbutt
This document provides an overview of Nova, OpenStack's compute service. It discusses Nova's architecture, code structure, API concepts, upgrade process, and how different groups work together as part of the upstream community. The new upgrade process aims to minimize downtime by expanding the database schema, restarting services individually, and signaling services to reload configuration. Collaboration across various groups with different perspectives is important to OpenStack's open development model.
OpenStack Summit Vancouver: Lessons learned on upgradesFrédéric Lepied
Deploying OpenStack in production at any scale, upgrade support is one of the requirements to have a successful deployment. Without upgrade management, adeployment will have bugs and security issues from day 1. Also in longer term, it will miss the latest features that OpenStack offers.
Tempest provides scenario tests that test integration between multiple OpenStack services by executing sequences of operations. Current scenario tests cover operations like boot instances, attach volumes, manage snapshots and check network connectivity. Running scenario tests helps operators validate their cloud and developers check for regressions. While useful, scenario tests have issues like needing more test coverage, complex configuration, and difficulty analyzing failures. The future includes making scenario tests easier to use without command line skills and more flexible in specifying test environments.
TripleO is an OpenStack project that aims to deploy OpenStack using OpenStack. It provides automation to deploy and test OpenStack clouds at the bare metal layer using tools like Heat, Diskimage-Builder, and Ironic. TripleO designs robust gold images to deploy consistently tested and reliable OpenStack environments, reducing costs of operations and maintenance through continuous integration and deployment techniques. By deploying OpenStack on bare metal with tools like Ironic, TripleO can reliably install and upgrade OpenStack clouds.
Performance Benchmarking of Clouds Evaluating OpenStackPradeep Kumar
Pradeep Kumar surisetty presented on performance benchmarking of clouds and evaluating OpenStack. He discussed key cloud characteristics like elasticity and scalability. He then covered various performance measuring tools like Rally, Browbeat, Perfkit Benchmarker, and SPEC Cloud IaaS 2016 benchmark. He also discussed performance monitoring tools like Ceilometer, Collectd/Graphite/Grafana, and Ganglia. Finally, he provided some tuning tips for hardware, instances, over-subscription, local storage, NUMA nodes, disk pinning, and deployment timings.
This document summarizes a presentation about Open Platform for Network Functions Virtualization (OPNFV). It discusses NFV challenges for telecom operators and introduces OPNFV as an open source platform that aims to develop and test an integrated virtual network functions infrastructure. Key aspects of OPNFV covered include its reference architecture, goals of contributing to relevant open source projects and establishing an NFV ecosystem, and examples of feature development and community labs/testing activities.
GUTS is a workload migration engine that automatically migrates existing workloads and virtual machines from previous generation virtualization platforms to OpenStack. It supports migrating VMs, volumes, networks, users, and other resources between OpenStack environments or from platforms like VMware to OpenStack. GUTS has API, scheduler, and migration services to orchestrate the migrations. It can convert disk formats and manage hypervisor-specific tools during the migration process. Future plans include supporting more hypervisors and resource types.
The document discusses OpenStack QA tools used for production cloud testing. It describes tools like Tempest for API and scenario testing, Patrole for RBAC testing, Stackviz for analyzing DevStack performance, and the OpenStack Health dashboard for viewing test status. It explains how these tools like Tempest and Patrole can run tests simultaneously in multiple workspaces on a Cloud Health Node to test different OpenStack sites without needing to upgrade the node for each site upgrade. The dashboard provides a view of test results from across workspaces.
Here are the basic steps to download the latest version of DevStack:
1. Install Git:
- On Ubuntu/Debian: `sudo apt-get install git`
- On CentOS/RHEL: `sudo yum install git`
2. Clone the DevStack repository:
`git clone https://git.openstack.org/openstack-dev/devstack`
3. Change to the DevStack directory:
`cd devstack`
4. Checkout the latest stable branch (e.g. stable/ussuri):
`git checkout stable/ussuri`
5. Download the latest code:
`git pull`
This will download the latest version
One of the impediments to becoming an active technical contributor in the OpenStack community is setting up an efficient R&D environment which includes deploying a simple cloud. Using RDO-manager, get a basic cloud up and running with the fewest steps and minimal hardware so you can focus on the fun stuff - development
TripleO is a collection of OpenStack tools used to deploy a fully functional OpenStack from a minimal OpenStack installation. It leverages tools like Heat, DiskImage Builder, and os-collect-config. DiskImage Builder is used to generate customized virtual machine images with preinstalled packages and configuration templates. Heat templates are then used to deploy the infrastructure using these images and populate configuration files using the templates. This reduces deployment time and complexity compared to traditional configuration management approaches.
This document discusses combining Ceph with Kubernetes for container-based storage management. It describes how Rook provides a simplified way to consume Ceph storage using Kubernetes concepts and APIs. The Ceph dashboard and Ceph management daemon (ceph-mgr) could also be integrated with Rook to provide a unified management experience. This would allow configuring Ceph storage through Kubernetes and the dashboard without needing deep Ceph expertise. The document outlines several ongoing projects aimed at further simplifying Ceph management, such as automatic placement group configuration and progress monitoring. The overall goal is to reduce the cognitive load on users and enable more automated workflows.
The document provides tips for OpenStack cloud transformation. It discusses (1) unifying CPU models on compute nodes for live migration, (2) clustering compute nodes by host aggregate, and (3) configuring options to slow down CPU during live migration for stability. Other tips include increasing HAProxy connection limits, enabling multiple network queues, implementing port level security, and ensuring adequate entropy for scale-out systems. The overall document offers best practices and configurations for improving performance and stability during OpenStack cloud transformations.
1. The document discusses using OpenStack for a 4G core network, including performance issues and solutions when virtualizing the EPC network functions using OpenStack.
2. Key performance issues identified include high CPU usage, competing for CPU resources, latency, throughput, and packet loss. Solutions proposed are CPU pinning, NUMA awareness, hugepages, DPDK, SR-IOV, and offloading processing to smart NICs.
3. Going forward, the next steps discussed are using OVS-DPDK for offloading, SDN, containers, and cloud architectures for 5G.
Build cloud like Rackspace with OpenStack AnsibleJirayut Nimsaeng
Build cloud like Rackspace with OpenStack Ansible Workshop in 2nd Cloud OpenStack-Container Conference and Workshop 2016 at Grand Postal Building, Bangrak, Bangkok on September 22-23, 2016
Cloud Foundry Deployment Tools: BOSH vs Juju CharmsAltoros
Did you know that BOSH is not the only tool for deploying the Cloud Foundry PaaS?.. Initially presented at the 2014 DevOps Summit by Andrei Yurkevich, CTO @ Altoros, this slide deck demonstrates how to deploy CF with Juju Charms and compares this orchestration solution to BOSH. It also covers overlapping features and explains when to use BOSH, Juju Charms, or both.
For more Cloud Foundry research, visit: http://www.altoros.com/research-papers
CAPS: What's best for deploying and managing OpenStack? Chef vs. Ansible vs. ...Daniel Krook
Presentation at the OpenStack Summit in Tokyo, Japan on October 29, 2015.
http://sched.co/49vI
This talk will cover the pros and cons of four different OpenStack deployment mechanisms. Puppet, Chef, Ansible, and Salt for OpenStack all claim to make it much easier to configure and maintain hundreds of OpenStack deployment resources. With the advent of large-scale, highly available OpenStack deployments spread across multiple global regions, the choice of which deployment methodology to use has become more and more relevant.
Beyond the initial day-one deployment, when it comes to the day-two and beyond questions of updating and upgrading existing OpenStack deployments, it becomes all the more important choose the right tool.
Come join the Bluebox and IBM team to discuss the pros and cons of these approaches. We look at each of these four tools in depth, explore their design and function, and determine which scores higher than others to address your particular deployment needs.
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
Paul Czarkowski - Cloud Engineer at Blue Box, an IBM company
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
This document discusses OpenStack Heat, an orchestration service for OpenStack clouds. It describes Heat's architecture, including resource plugins and templates for modeling cloud applications. It also covers problems with the initial Heat-engine design and the convergence improvements made to address these. Finally, it lists some consumers of Heat and references for further information.
Discover the story behind XCP-ng, the free community build of XenServer. Why we did it, and how we built it, from technical and community perspective. And finally, what's coming next.
1. The document discusses how OpenStack can be used to build private and hybrid clouds for enterprises using open source technology free from vendor lock-in.
2. It provides examples of how OpenStack can enable continuous software delivery, cloud-enable applications, and provide IT as a service while reducing reliance on proprietary virtualization.
3. Asdtech offers turnkey OpenStack services including consultancy, cloud setup, custom development, migration, support and training to help enterprises orchestrate their existing infrastructure or build new clouds.
The document provides an introduction to OpenStack, an open source cloud computing platform. It begins with an outline and introduction discussing the growth of data and cloud computing. It then discusses what OpenStack is, providing its definition and key facts about its history, contributors and components. The document demonstrates how to set up and deploy an OpenStack environment using DevStack. It encourages participants to get involved with OpenStack through contributing, events and mailing lists. It concludes with Q&A and additional resources.
OpenStack Summit Vancouver: Lessons learned on upgradesFrédéric Lepied
Deploying OpenStack in production at any scale, upgrade support is one of the requirements to have a successful deployment. Without upgrade management, adeployment will have bugs and security issues from day 1. Also in longer term, it will miss the latest features that OpenStack offers.
Tempest provides scenario tests that test integration between multiple OpenStack services by executing sequences of operations. Current scenario tests cover operations like boot instances, attach volumes, manage snapshots and check network connectivity. Running scenario tests helps operators validate their cloud and developers check for regressions. While useful, scenario tests have issues like needing more test coverage, complex configuration, and difficulty analyzing failures. The future includes making scenario tests easier to use without command line skills and more flexible in specifying test environments.
TripleO is an OpenStack project that aims to deploy OpenStack using OpenStack. It provides automation to deploy and test OpenStack clouds at the bare metal layer using tools like Heat, Diskimage-Builder, and Ironic. TripleO designs robust gold images to deploy consistently tested and reliable OpenStack environments, reducing costs of operations and maintenance through continuous integration and deployment techniques. By deploying OpenStack on bare metal with tools like Ironic, TripleO can reliably install and upgrade OpenStack clouds.
Performance Benchmarking of Clouds Evaluating OpenStackPradeep Kumar
Pradeep Kumar surisetty presented on performance benchmarking of clouds and evaluating OpenStack. He discussed key cloud characteristics like elasticity and scalability. He then covered various performance measuring tools like Rally, Browbeat, Perfkit Benchmarker, and SPEC Cloud IaaS 2016 benchmark. He also discussed performance monitoring tools like Ceilometer, Collectd/Graphite/Grafana, and Ganglia. Finally, he provided some tuning tips for hardware, instances, over-subscription, local storage, NUMA nodes, disk pinning, and deployment timings.
This document summarizes a presentation about Open Platform for Network Functions Virtualization (OPNFV). It discusses NFV challenges for telecom operators and introduces OPNFV as an open source platform that aims to develop and test an integrated virtual network functions infrastructure. Key aspects of OPNFV covered include its reference architecture, goals of contributing to relevant open source projects and establishing an NFV ecosystem, and examples of feature development and community labs/testing activities.
GUTS is a workload migration engine that automatically migrates existing workloads and virtual machines from previous generation virtualization platforms to OpenStack. It supports migrating VMs, volumes, networks, users, and other resources between OpenStack environments or from platforms like VMware to OpenStack. GUTS has API, scheduler, and migration services to orchestrate the migrations. It can convert disk formats and manage hypervisor-specific tools during the migration process. Future plans include supporting more hypervisors and resource types.
The document discusses OpenStack QA tools used for production cloud testing. It describes tools like Tempest for API and scenario testing, Patrole for RBAC testing, Stackviz for analyzing DevStack performance, and the OpenStack Health dashboard for viewing test status. It explains how these tools like Tempest and Patrole can run tests simultaneously in multiple workspaces on a Cloud Health Node to test different OpenStack sites without needing to upgrade the node for each site upgrade. The dashboard provides a view of test results from across workspaces.
Here are the basic steps to download the latest version of DevStack:
1. Install Git:
- On Ubuntu/Debian: `sudo apt-get install git`
- On CentOS/RHEL: `sudo yum install git`
2. Clone the DevStack repository:
`git clone https://git.openstack.org/openstack-dev/devstack`
3. Change to the DevStack directory:
`cd devstack`
4. Checkout the latest stable branch (e.g. stable/ussuri):
`git checkout stable/ussuri`
5. Download the latest code:
`git pull`
This will download the latest version
One of the impediments to becoming an active technical contributor in the OpenStack community is setting up an efficient R&D environment which includes deploying a simple cloud. Using RDO-manager, get a basic cloud up and running with the fewest steps and minimal hardware so you can focus on the fun stuff - development
TripleO is a collection of OpenStack tools used to deploy a fully functional OpenStack from a minimal OpenStack installation. It leverages tools like Heat, DiskImage Builder, and os-collect-config. DiskImage Builder is used to generate customized virtual machine images with preinstalled packages and configuration templates. Heat templates are then used to deploy the infrastructure using these images and populate configuration files using the templates. This reduces deployment time and complexity compared to traditional configuration management approaches.
This document discusses combining Ceph with Kubernetes for container-based storage management. It describes how Rook provides a simplified way to consume Ceph storage using Kubernetes concepts and APIs. The Ceph dashboard and Ceph management daemon (ceph-mgr) could also be integrated with Rook to provide a unified management experience. This would allow configuring Ceph storage through Kubernetes and the dashboard without needing deep Ceph expertise. The document outlines several ongoing projects aimed at further simplifying Ceph management, such as automatic placement group configuration and progress monitoring. The overall goal is to reduce the cognitive load on users and enable more automated workflows.
The document provides tips for OpenStack cloud transformation. It discusses (1) unifying CPU models on compute nodes for live migration, (2) clustering compute nodes by host aggregate, and (3) configuring options to slow down CPU during live migration for stability. Other tips include increasing HAProxy connection limits, enabling multiple network queues, implementing port level security, and ensuring adequate entropy for scale-out systems. The overall document offers best practices and configurations for improving performance and stability during OpenStack cloud transformations.
1. The document discusses using OpenStack for a 4G core network, including performance issues and solutions when virtualizing the EPC network functions using OpenStack.
2. Key performance issues identified include high CPU usage, competing for CPU resources, latency, throughput, and packet loss. Solutions proposed are CPU pinning, NUMA awareness, hugepages, DPDK, SR-IOV, and offloading processing to smart NICs.
3. Going forward, the next steps discussed are using OVS-DPDK for offloading, SDN, containers, and cloud architectures for 5G.
Build cloud like Rackspace with OpenStack AnsibleJirayut Nimsaeng
Build cloud like Rackspace with OpenStack Ansible Workshop in 2nd Cloud OpenStack-Container Conference and Workshop 2016 at Grand Postal Building, Bangrak, Bangkok on September 22-23, 2016
Cloud Foundry Deployment Tools: BOSH vs Juju CharmsAltoros
Did you know that BOSH is not the only tool for deploying the Cloud Foundry PaaS?.. Initially presented at the 2014 DevOps Summit by Andrei Yurkevich, CTO @ Altoros, this slide deck demonstrates how to deploy CF with Juju Charms and compares this orchestration solution to BOSH. It also covers overlapping features and explains when to use BOSH, Juju Charms, or both.
For more Cloud Foundry research, visit: http://www.altoros.com/research-papers
CAPS: What's best for deploying and managing OpenStack? Chef vs. Ansible vs. ...Daniel Krook
Presentation at the OpenStack Summit in Tokyo, Japan on October 29, 2015.
http://sched.co/49vI
This talk will cover the pros and cons of four different OpenStack deployment mechanisms. Puppet, Chef, Ansible, and Salt for OpenStack all claim to make it much easier to configure and maintain hundreds of OpenStack deployment resources. With the advent of large-scale, highly available OpenStack deployments spread across multiple global regions, the choice of which deployment methodology to use has become more and more relevant.
Beyond the initial day-one deployment, when it comes to the day-two and beyond questions of updating and upgrading existing OpenStack deployments, it becomes all the more important choose the right tool.
Come join the Bluebox and IBM team to discuss the pros and cons of these approaches. We look at each of these four tools in depth, explore their design and function, and determine which scores higher than others to address your particular deployment needs.
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
Paul Czarkowski - Cloud Engineer at Blue Box, an IBM company
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
This document discusses OpenStack Heat, an orchestration service for OpenStack clouds. It describes Heat's architecture, including resource plugins and templates for modeling cloud applications. It also covers problems with the initial Heat-engine design and the convergence improvements made to address these. Finally, it lists some consumers of Heat and references for further information.
Discover the story behind XCP-ng, the free community build of XenServer. Why we did it, and how we built it, from technical and community perspective. And finally, what's coming next.
1. The document discusses how OpenStack can be used to build private and hybrid clouds for enterprises using open source technology free from vendor lock-in.
2. It provides examples of how OpenStack can enable continuous software delivery, cloud-enable applications, and provide IT as a service while reducing reliance on proprietary virtualization.
3. Asdtech offers turnkey OpenStack services including consultancy, cloud setup, custom development, migration, support and training to help enterprises orchestrate their existing infrastructure or build new clouds.
The document provides an introduction to OpenStack, an open source cloud computing platform. It begins with an outline and introduction discussing the growth of data and cloud computing. It then discusses what OpenStack is, providing its definition and key facts about its history, contributors and components. The document demonstrates how to set up and deploy an OpenStack environment using DevStack. It encourages participants to get involved with OpenStack through contributing, events and mailing lists. It concludes with Q&A and additional resources.
Docker and containers : Disrupting the virtual machine(VM)Rama Krishna B
This document discusses Docker containers and how they are disrupting virtual machines. It begins with definitions of key terms like virtualization, virtual machines, and hypervisors. It then compares virtual machines to containers, noting that containers are more lightweight and efficient since they share the host operating system and resources, while still providing isolation. The document traces the evolution of containers from early technologies like chroot to modern implementations in Docker. It positions Docker as an open source tool that packages and runs applications in portable software containers. While containers increase efficiency over virtual machines, the document argues both technologies can coexist in cloud environments.
The document discusses OpenStack at CERN. It provides details on:
- OpenStack has been in production at CERN for 3 years, managing over 190,000 cores and 7,000 hypervisors.
- Major cultural and technology changes were required and have been successfully addressed to transition to OpenStack.
- Contributing back to the upstream OpenStack community has led to sustainable tools and effective technology transfer.
The OpenStack Cloud at CERN - OpenStack NordicTim Bell
The document discusses the CERN OpenStack cloud, which provides compute resources for the Large Hadron Collider experiment at CERN. It details the scale of the cloud, including over 6,700 hypervisors, 190,000 cores, and 20,000 VMs. It also describes the various use cases served, wide range of hardware, and operations of the cloud, including a retirement campaign and network migration to Neutron.
OpenStack Project Freezer is a backup and restore service that automates the data backup and restore process. It supports backing up and restoring various platforms and storage types. Freezer has a low memory footprint and supports incremental backups, old backup removal, restoring from a specific date, bandwidth limiting, and clustering of backups across multiple servers. The document then describes Freezer's architecture, components, experiences optimizing backups to Swift storage, and concludes with an overview of demonstrations of Freezer's backup and restore of Nova VMs, Cinder volumes, file systems, and MySQL databases.
SDN Scale-out Testing at OpenStack Innovation Center (OSIC)PLUMgrid
The OpenStack Innovation Center (OSIC), established by Intel and Rackspace, is created to accelerate adoption of open source cloud operating system while supporting open source principles. OSIC provides ready-to-use data center facilities to the OpenStack community for development and test. This case study presentation highlights a scale-out test performed within a 3 week period using OpenStack Ansible Community based on Liberty with an SDN overlay network connecting 131 nodes running over 1,000 VMs. Tempest and Rally tests were conducted to validate functions including high availability failure scenarios. Join this session to find out more about OSIC and the SDN scale-out test configuration, scenarios, and results.
Configure, Debug and Install OpenStack TroveRama Krishna B
This document provides an overview of OpenStack Trove:
- Trove is a database as a service that provisions and manages relational and non-relational databases. It exposes a REST API and stores data in an infrastructure database.
- Key components include the Trove API service, Task Manager, and Conductor service. The Task Manager handles operations like instance creation while the Conductor updates status in the infrastructure database.
- The document then covers installing and configuring Trove on DevStack, including validation steps to create a database instance, database, and user. It also discusses debugging techniques like checking logs and running commands with the debug option.
This document provides an overview of MySQL Database as a Service (DBaaS) with OpenStack Trove. It begins with some background on OpenStack and its components, including Trove which provides database services. The rest of the document outlines the agenda which includes introductions to OpenStack and Trove, benefits of MySQL Enterprise Edition, integrating MySQL with Trove, and future plans. It also includes examples of large companies using OpenStack such as Walmart, Fujitsu, Photobucket, and CERN.
Introduction to OpenStack Trove & Database as a ServiceTesora
Doug Shelley from Tesora gave a presentation on OpenStack Trove and Database as a Service (DBaaS) at the OpenStack Toronto Meetup. He discussed the challenges of traditional database management versus cloud databases, and introduced OpenStack Trove as an open source DBaaS solution like Amazon RDS. Trove provides automated provisioning, management and scaling of relational and non-relational databases running on OpenStack. Recent improvements to Trove were highlighted as well as upcoming features planned for the Newton release.
KVM and docker LXC Benchmarking with OpenStackBoden Russell
Passive benchmarking with docker LXC and KVM using OpenStack hosted in SoftLayer. These results provide initial incite as to why LXC as a technology choice offers benefits over traditional VMs and seek to provide answers as to the typical initial LXC question -- "why would I consider Linux Containers over VMs" from a performance perspective.
Results here provide insight as to:
- Cloudy ops times (start, stop, reboot) using OpenStack.
- Guest micro benchmark performance (I/O, network, memory, CPU).
- Guest micro benchmark performance of MySQL; OLTP read, read / write complex and indexed insertion.
- Compute node resource consumption; VM / Container density factors.
- Lessons learned during benchmarking.
The tests here were performed using OpenStack Rally to drive the OpenStack cloudy tests and various other linux tools to test the guest performance on a "micro level". The nova docker virt driver was used in the Cloud scenario to realize VMs as docker LXC containers and compared to the nova virt driver for libvirt KVM.
Please read the disclaimers in the presentation as this is only intended to be the "chip of the ice burg".
This document discusses Rally, an OpenStack benchmarking tool. It provides an introduction to Rally and its components, including benchmark engines, deployment engines, server providers, and verification. The document demonstrates how to install and configure Rally, set up deployments and benchmarking scenarios, and run and analyze benchmarking tests. It also lists some supported benchmarking use cases and provides information on contributing to and getting involved with the Rally project.
The document discusses using Senlin, an OpenStack clustering service, to provide autoscaling capabilities for multicloud platforms. Senlin allows for managing clusters of nodes across different cloud providers and includes features like load balancing, auto-healing, and scaling policies. It describes how Senlin was implemented at a company to provide a centralized autoscaling solution across OpenStack and VMware cloud environments. Some drawbacks of Senlin are also outlined, along with potential future work like multi-region clusters and global load balancing.
How to integrate_custom_openstack_services_with_devstackSławomir Kapłoński
DevStack is a tool used to quickly deploy OpenStack from source code for development and testing purposes. Plugins allow custom OpenStack services to be integrated with DevStack. A plugin contains scripts that are executed at different points during deployment to install and configure the custom service. Functions are provided to help with common tasks like installing packages or configuring services.
The document provides an overview and cheat sheet for using the OpenShift command line interface. It defines what OpenShift is, lists common commands for login/authentication, managing projects and resources, building and deploying applications, and provides an example of creating a new project, adding users, building an application from source code and image, and checking the status of deployed resources.
This document provides instructions for a hands-on lab on using Azure DevOps deployment groups. It describes how deployment groups can be used to deploy an application to multiple servers in a sequenced manner. The steps show how to set up target Azure virtual machines, configure the necessary service connections in Azure DevOps, create deployment groups, and configure a release pipeline to deploy to the deployment groups. Prerequisites for the lab are also provided.
LinuxCon 2013 Steven Dake on Using Heat for autoscaling OpenShift on OpenstackOpenShift Origin
OpenStack Heat allows modeling relationships between OpenStack resources and managing infrastructure resources throughout application lifecycles. The presentation discusses Heat architecture, autoscaling workflows using Heat and Ceilometer, and demonstrates an OpenShift autoscaling workflow on OpenStack using Heat templates, DIB elements, and CloudWatch alarms. Future work may expand autoscaling to other resources and integrate it more fully across OpenStack projects.
This presentation was given at the Boston Django meetup on November 16, and surveyed several leading PaaS providers including Stackato, Dotcloud, OpenShift and Heroku.
For each PaaS provider, I documented the steps necessary to deploy Mezzanine, a popular Django-based CMS and blogging platform.
At the end of the presentation, I do a wrap-up of the different providers and provide a comparison matrix showing which providers have which features. This matrix is likely to go out-of-date quickly because these providers are adding new features all the time.
Introduction to Apache jclouds at NYJavaSIGEverett Toews
This document provides an introduction to Apache jclouds, an open source toolkit that allows Java applications to access multiple cloud infrastructures through a unified API. It discusses key jclouds concepts like providers, views, and portability. Examples show how to connect to clouds like OpenStack and Rackspace, retrieve API resources, and make cloud-specific calls in a portable way. Community involvement and the jclouds roadmap are also summarized.
2 Day Bootcamp for OpenStack--Cloud Training by Mirantis (Preview)Mirantis
Mirantis, the Global Engineering Services leader for OpenStack™ presents 2-day Bootcamp for OpenStack
www.mirantis.com/training
This two-day intensive course provides hands-on technical training for OpenStack aimed at system administrators and IT professionals looking to get started on an OpenStack Cloud deployment. Each of the two days will consist of lecture, demos and group exercises. Topics include:
• OpenStack Overview & Architecture: Project goals and use cases, basic operating and deployment principles
• Cloud Usage Patterns: OpenStack codebase overview; creating networks, tenants, roles, troubleshooting; Nexenta Volume Driver
• In Production: Deploying OpenStack for real-world use, and practice of OpenStack operation on multiple nodes
• Swift Object Storage: use cases, architecture, capabilities, configuration, security and deployment
• Advanced Topics: Software Defined Networking, deployment and issues workshop, VMWare/OpenStack comparison
PRE-REQUISITES: Comfortable with Linux CLI, understanding of virtualization & hypervisors, Some experience with Linux networking
All course materials will be provided by Mirantis, including access to shared compute resources for labs. A light breakfast and lunch will be available to all course participants.
Mirantis instructors are active code committers to the OpenStack project, with proven experience building OpenStack clouds in the real world. In parallel to delivering expert training, they also consult for some of the notable global companies using OpenStack – including Cisco, NASA, Dell and Internap.
Boris Stoyanov - Troubleshooting the Virtual Router - Run and Get DiagnosticsShapeBlue
Demonstration of CloudStack’s latest features for troubleshooting the Virtual Router connectivity and configuration, called Run and Get Diagnostics. Run Diagnostics gives the admin ability to execute diagnostics commands native the VR OS directly from the CloudStack UI. Admin is able to determine connectivity capabilities of the VR without logging into the SystemVM at all. Get diagnostics feature allow the admin to gather information about the SystemVM as fast as clicking on a button in the ‘QuickView’ of the VM. Admin can also execute custom scripts on each SystemVM type from the CloudStack UI. This session will begin with complete presentation of the features followed by live demo and Q&A.
This document provides an overview of Kubernetes and containerization concepts including Docker containers, container orchestration with Kubernetes, deploying and managing applications on Kubernetes, and using Helm to package and deploy applications to Kubernetes. Key terms like pods, deployments, services, configmaps and secrets are defined. Popular container registries, orchestrators and cloud offerings are also mentioned.
1) Apache Ambari is an open-source platform for provisioning, managing and monitoring Hadoop clusters.
2) New features in Ambari 2.4 include additional services, role-based access control, management packs and a Grafana UI for visualizing metrics.
3) Ambari simplifies cluster operations through an intuitive UI for deploying, securing, monitoring and upgrading Hadoop clusters on-premises and in the cloud.
1. Apache Ambari is an open-source platform for provisioning, managing and monitoring Hadoop clusters.
2. New features in Ambari 2.4 include additional services, role-based access control, management packs and a Grafana UI for visualizing metrics.
3. Ambari simplifies cluster operations through deploying clusters via blueprints, automated Kerberos integration, host discovery and stack advisors. It also supports upgrading clusters with either rolling or express upgrades.
Getting Started with MariaDB with DockerMariaDB plc
This document discusses deploying MariaDB databases with Docker from development to production. It recommends using Docker containers to encapsulate dependencies and isolate processes for easy deployment on-premise, in the cloud, or in hybrid environments. It highlights challenges like orchestration complexity and outlines requirements for data durability, self-discovery, self-healing, and application discovery of database clusters. It demonstrates building a Python/Flask app in Docker, deploying it to a Swarm cluster, and scaling the web tier behind HAProxy. It also shows deploying a 3-node Galera MariaDB cluster and 2-node MaxScale proxy for high availability.
Pyramid is a flexible Python web framework that allows applications to start small and grow as needed without enforcing specific technologies or patterns. The document provides suggestions for structuring larger Pyramid projects, choosing persistence mechanisms, assembling toolkits, using traversal vs URL dispatch, testing, documenting, and deploying applications using buildout, supervisor, and Nginx/mod_wsgi. Project layout, tools, and deployment options depend on each application's specific needs and scope.
Openstack - An introduction/Installation - Presented at Dr Dobb's conference...Rahul Krishna Upadhyaya
Slide was presented at Dr. Dobb's Conference in Bangalore.
Talks about Openstack Introduction in general
Projects under Openstack.
Contributing to Openstack.
This was presented jointly by CB Ananth and Rahul at Dr. Dobb's Conference Bangalore on 12th Apr 2014.
Capacity planning is a difficult challenge faced by most companies. If you have too few machines, you will not have enough compute resources available to deal with heavy loads. On the other hand, if you have too many machines, you are wasting money. This is why companies have started investing in automatically scaling services and infrastructure to minimize the amount of wasted money and resources.
In this talk, Nathan will describe how Yelp is using PaaSTA, a PaaS built on top of open source tools including Docker, Mesos, Marathon, and Chronos, to automatically and gracefully scale services and the underlying cluster. He will go into detail about how this functionality was implemented and the design designs that were made while architecting the system. He will also provide a brief comparison of how this approach differs from existing solutions.
Kirill Rozin - Practical Wars for AutomatizationSergey Arkhipov
The document discusses various testing frameworks and tools used for OpenStack including Rally, Tempest, Proboscis, Pytest, Jenkins API, unified test reporter, TestRail API, and Launchpad API. It provides links to documentation and code examples for interacting with these tools to retrieve information like job details, run tests, manage test cases and results. The tools can be used for tasks like benchmarking OpenStack performance, detecting issues, automating testing, and managing test execution and results.
Delivering IaaS with Open Source SoftwareMark Hinkle
Mark Hinkle presented on delivering Infrastructure-as-a-Service (IaaS) using open source software. He discussed various open source tools for building cloud computing including hypervisors like KVM and Xen, object storage solutions like OpenStack Swift, and automation/orchestration tools like CloudStack and OpenStack. Hinkle emphasized that open source solutions provide many advantages for cloud computing including lower costs, collaboration, and avoidance of vendor lock-in. He also covered management tools for private clouds and highlighted the importance of automation.
Similar to Benchmarking Openstack Installations using Rally (20)
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
Measures in SQL (SIGMOD 2024, Santiago, Chile)Julian Hyde
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
Hand Rolled Applicative User ValidationCode KataPhilip Schwarz
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
A Study of Variable-Role-based Feature Enrichment in Neural Models of CodeAftab Hussain
Understanding variable roles in code has been found to be helpful by students
in learning programming -- could variable roles help deep neural models in
performing coding tasks? We do an exploratory study.
- These are slides of the talk given at InteNSE'23: The 1st International Workshop on Interpretability and Robustness in Neural Software Engineering, co-located with the 45th International Conference on Software Engineering, ICSE 2023, Melbourne Australia
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian CompaniesQuickdice ERP
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
E-commerce Development Services- Hornet DynamicsHornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Takashi Kobayashi and Hironori Washizaki, "SWEBOK Guide and Future of SE Education," First International Symposium on the Future of Software Engineering (FUSE), June 3-6, 2024, Okinawa, Japan
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
2. Agenda
• An Introduction to OpenStack Rally
• Rally Installation
• Rally UseCases and Demos
• Rally UseCases for Benchmarking HP Helion and
Demos
3. What is OpenStack Rally?
• Rally is community based open source project, used to
gather benchmarking data on how the OpenStack cloud
operates at scale.
• Rally automates and unifies multi-node OpenStack
deployment, cloud verification, benchmarking & profiling.
• https://wiki.openstack.org/wiki/Rally
4. OpenStack Rally
• Rally started as an incubator project in Aug 2013
• Became part of OpenStack just before the OpenStack
Kilo release.
• Rally is targeted towards Developers, DevOps, QA
Engineers and Cloud Administrators.
• Key Contributions from Mirantis ,RedHat and IBM
6. More on Rally
• Rally can be configured to test any number of OpenStack
deployments.
• Rally has four key services with a central database repository
– OpenStack deployment engine--which can assist in simplifying OpenStack
deployments. Leverages existing deployment tools like devstack ,Fuel etc.
– Benchmarking and profiling engine--allows you to create parameterized
load on the cloud , based on large repository of benchmarks.
– Verification engine--uses tempest as the verifier.
– Reporting services for viewing and formatting results
9. Useful information on Rally
Rally documentation:
http://rally.readthedocs.org/en/latest/
Rally step-by-step tutorial:
http://rally.readthedocs.org/en/latest/tutorial.html
Launchpad page:
https://launchpad.net/rally
Code is hosted on git.openstack.org:
http://git.openstack.org/cgit/openstack/rally
Code is mirrored on github:
https://github.com/openstack/rally
10. Rally Installation
wget -q -O- https://raw.githubusercontent.com/openstack/rally/master/install_rally.sh | bash
After the Installation is complete need to set up the Rally database
rally-manage db recreate
Rally uses SQL-Lite. The Database is under rally/database
Note: Rally requires Python version 2.6, 2.7 or 3.4.
11. Configure Rally with existing DevStack
First source your OpenStack/devstack Resource File
source openrc #file containing the devstack parameters
The best way to get your Resource file is to access the Horizon UI
,Project=>Compute=>Access & Security=>API Access .Click on Download OpenStack RC File.
Register your OpenStack environment with Rally
rally deployment create --fromenv --name=existing1
12. Configure Rally with existing DevStack
You can use a JSON file to do deployment create
rally deployment create --file=existing.json --name=existing
Sample Contents of existing.json
{
"type": "ExistingCloud","auth_url": "http://example.net:5000/v2.0/","region_name": "RegionOne",
"endpoint_type": "public",
"admin": {
"username": "admin",
"password": "myadminpass",
"tenant_name": "demo"
},
"https_insecure": False, "https_cacert": "",
}
13. Validate your Rally deployment
rally deployment check
deployment check command ensures that your current deployment is healthy and ready to be benchmarked
14. Benchmarking using Rally
There are several benchmarking scenarios already available in the
Rally installation to use.
Access rally/src/samples/tasks
How to run a Benchmarking task
rally task start <benchmark-scenario-file>
Example:
rally task start src/samples/tasks/scenarios/nova/boot-and-
delete.json
18. Multiple Scenarios in the same Task
You can run multiple scenarios in the same task. These scenarios
are executed one after the other.
{
"<ScenarioName1>": [<benchmark_config>,<benchmark_config2>, ...]
"<ScenarioName2>": [<benchmark_config>, ...]
}
Generate Results as before
19. Benchmarking Using existing Users
In the previous scenarios we saw before , Rally creates random
users and tenants to use during the test and delete them after the
tests are done.
In the production world you may want to run the tests as existing
users (either because you cannot create new users or you want to
run tests from an isolated group of users)
Rally facilitates running tests as existing users/tenants
20. Benchmarking Using existing Users
Create a new deployment with existing users/tenants as shown:
{
"type": "ExistingCloud",
"auth_url": "http://example.net:5000/v2.0/",
"region_name": "RegionOne",
"endpoint_type": "public",
"admin": { "username": "admin", "password": "pa55word", "tenant_name": "demo"
},
"users": [
{ "username": "b1", "password": "1234", "tenant_name": "testing"},
{ "username": "b2", "password": "1234", "tenant_name": "testing"
}]}
21. Benchmarking Using existing Users
Make the new deployment Active
rally deployment use <deployment-ID>
Change your scenario specific configuration (ex: NovaServers.boot
and delete_server) to remove “users context”
{ "NovaServers.boot_and_delete_server": [ { "args": { "flavor": { "name": "m1.nano" },
"image": { "name": "^cirros.*uec$" }, "force_delete": false }, "runner": { "type":
"constant", "times": 10, "concurrency": 2 }, "context": {} } ] }
Run your Rally tasks as before
22. Adding SLA to Benchmarking
Rally allows you to set success criteria (also called SLA - Service-
Level Agreement) for every benchmark. Rally will automatically
check them for you. To enforce SLA , add the following to your
scenario configuration:
"sla": {
"max_seconds_per_iteration": 10,
"failure_rate": {
"max": 25 } }
After that run your rally tests as before. The test fails when the SLA
is not met (as in this case exceeds 25% OR Max seconds is > 10
secs)
23. Adding SLA to BenchMarking…Cont
Run the tests…
rally task start ./boot-and-delete-SLA.json
Once the tests have been successfully run , let us run the SLA-
CHECK
rally task sla_check
After that run your rally tests as before. The test fails when the SLA
is not met.
24. Configuring command line parameters
ck
After that run your rally tests as before. The test fails when the SLA
is not met.
25. Configuring Multiple OpenStack deployments
You can configure Rally to run against multiple OpenStack
deployments. Use:
rally create deployment --file=cloud1.json --name=cloud1
for each cloud deployment (user unique name and json files)
Then
rally deployment use cloud1 (or whatever you want to use and all subsequent
rally operations operate on cloud1)
rally task list --all-deployment … for all tasks across all deployments
26. Rally Search and Help
Rally provides a command line search engine to search for
scenarios, help information etc.
rally info BenchmarkScenarios
rally info find <ScenarioGroupName>
27. Rally deployment with OpenStack
Rally provides mechanism to deploy DevStack. To do that
rally deployment create --
file=src/samples/deployments/for_deploying_openstack_with_rally
/devstack-in-existing-servers.json --name=new-devstack
28. Tempest Vs. Rally
• Tempest only supports only single deployment. To test a different deployment,
Tempest must be reconfigured.
• Tempest does not have a central repository to store results across multiple clouds .
• Tempest has no built-in functionality for comparing test results
• Tempest does not have any reporting capabilities.
Also
• Rally is easy to deploy and configure. Can support any number of OpenStack
deployments
• Stores deployment information and verification test results in a central Database
This is important because:
• Verification test results are available forever in database
• Results from multiple Rally deployments can be compared and analyzed
• rally has built in reporting features for viewing and comparing results