Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Openstack considerations and deployments


Published on

Before to chose a specific cloud development/deployment model, a cloud architect must consider several technical and business drivers.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Openstack considerations and deployments

  1. 1. OpenStack Considerations and Deployments Victor Morales @electrocucarach
  2. 2. Agenda • Cloud In/Out • The importance of Why, Who, What, Where, When and How • PaaS vs IaaS vs SaaS • OpenStack Projects
  3. 3. Start-up/Company example
  4. 4. Cloud In/Out • Cloud In: Launch applications directly onto cloud IaaS, then later pull workloads into your datacenter. • Cloud Out: Move your datacenter into the modern era with virtualization
  5. 5. Choosing Cloud Service Model • Why: “What are the business drivers for leveraging cloud computing services within an organization?”(e. g. for start-ups, building new in the cloud is a no-brainer) • Who: “What organizations interact with the overall system?” • What: Identify Business and Technical Requirements
  6. 6. Choosing Cloud Service Model • Where: Laws and regulations have different constraints across countries, provinces, states and counties. • When and with What: Budget and expected delivery dates • How: The organizational change sometimes is more challenging than the new technology or the new strategy that is being implemented.
  7. 7. • One misperception about cloud computing is that one cloud service model fits all. • Too often companies pick a cloud vendor solely based on technical preferences.
  8. 8. SaaS • Is the most mature of the three cloud service models. • A company should use it to outsource all applications, features, and services that are not a core competency. • SaaS providers do not provide the same level of flexibility that a company would have if it built its own application.
  9. 9. PaaS • It’s the least mature of the three cloud service models. • To manage the performance, reliability, and scalability of each customer and to ensure the heavy loads from one customer do not impact another, the PaaS vendors have various limits (throttling) that they enforce on developers.
  10. 10. IaaS • Applications/services with extremely high volumes or highly distributed that crunch through enormous amounts of data. • The customer can architect for failure and build redundant services across multiple physical or virtual data centers
  11. 11. As we move up the stack toward SaaS we increase speed to market, reduce the number of human resources required, and reduce operational costs. As we move down the stack toward IaaS, we get more control of the infrastructure and have a better chance of avoiding or recovering from a vendor outage.
  12. 12. OpenStack Architecture Design • General purpose: A cloud built with common components that should address 80% of common use cases. • Compute focused: A cloud designed to address compute intensive workloads such as high performance computing (HPC). • Storage focused: A cloud focused on storage intensive workloads such as data analytics with parallel file systems. • Network focused: A cloud depending on high performance and reliable networking, such as a content delivery network (CDN). • Multi-site: A cloud built with multiple sites available for application deployments for geographical, reliability or data locality reasons. • Hybrid cloud: An architecture where multiple disparate clouds are connected either for failover, hybrid cloud bursting, or availability. • Massively scalable: An architecture that is intended for cloud service providers or other extremely large installations.
  13. 13. Compute focused example 1 m1.small instance = 1 vCPU, 20 GB of ephemeral storage and 2,048 MB of RAM. 2 CPUs of 10 cores each(hyperthreading, CPU overcommit ratio of 16:1) = 640 (2 × 10 × 2 × 16) total m1.small instances. …using the default memory overcommit ratio of 1.5:1 you server will need at least 853 GB (640 × 2,048 MB / 1.5) of RAM.
  14. 14. Deployment
  15. 15. Projections ?
  16. 16. The Ceilometer project aims to deliver a unique point of contact for billing systems to acquire all of the measurements they need to establish customer billing, across all current OpenStack core components with work underway to support future OpenStack components. With Blazar user can request the resources of cloud environment to be provided (“leased”) to his project for specific amount on time, immediately or in future.
  17. 17. References • Michael Kavis. (January 28, 2014), “Architecting the Cloud: Design Decisions for Cloud Computing Service Models (SaaS, PaaS, and IaaS)” • 6/ecosystems-in-conflict-amazon-vs-vmware-and- openstak/ • openstack-and-opennebula-a-tale-of-two-cloud- models/