OpenStack Toronto: Juno Community Update

Editor's Notes

1. IT operations are being challenged more than ever from various ends of an organization, each with very different types of application and workload requirements. The result…IT operations are straining to meet these new application and workload demands, using their existing traditional infrastructure. In many cases users are seeking the elasticity and dynamic growth they need, outside of their IT team, creating an uncontrolled “shadow IT” problem. Very quickly, the benefits of a private cloud are becoming apparent to IT operations, as they seek the right cloud solutions to meet their business demands.
2. ...And these new user demands are driving new application development to be more elastic and dynamic and uniquely designed for use in the cloud. Many advantages to this cloud-enabled workload can be rapidly altered and improved, and the architecture they reside on is significantly cheaper if deployed correctly.Traditional Workloads:- often reside on a single, large, stateful VM with several vCPU, lots of vRAM, storage inside VM, etc. - have a high SLA, and cannot tolerate any downtime—if that single VM goes down the enterprise has the potential to lose real dollars. - it needs proper care and maintenance, requires enterprise virtualization features to keep VMs highly available, and must be very carefully monitored with frequent troubleshooting - Scales upward-- as app/user demand grows, the VM gets bigger Cloud workloads are very different Workload runs on many small, stateless VMs, each typically small VMs or even container where: vCPU, vRAM, storage separate) Applications tolerate failure of VMs – If one VM fails, another quickly replaces it Fault tolerance often built into workload – no longer require expensive resiliency tools provided by Virtualization Scales outward, rather than up – as app/user demand grows, add more VMs
3. But what IS OpenStack exactly? OpenStack is actually a series of several independently developed services that comprise the sub-projects that work together to form a cloud framework. The framework is intentionally designed to be modular, which provides for massive scale-out capabilities for the entire framework. As user/application demands grow, administrators can simply add new service nodes as needed. The system is designed to scale to support thousands and tens-of-thousands VMs. Each service, comprise a set of “core” services that make up the framework, and are updated every 6 months with new projects and services.