Application M&O on OpenStack
•
2 likes•607 views
This document discusses application management and operations (M&O) on OpenStack. It begins by noting that while OpenStack and other IaaS platforms address initial infrastructure needs, more is required to properly support existing and future applications. The rest of the document then summarizes various approaches for deploying and managing applications on OpenStack through tools like Puppet, Heat, Cloudify, BOSH, Murano and Magnum. It emphasizes the need for application M&O to be integrated with cloud and infrastructure M&O and to support cloud-native applications and microservices. The document promotes further research into tools like Magnum to provide container orchestration as first-class OpenStack resources.
Report
Share
Application M&O on OpenStack
- 1. 1 OpenStack Application M&O Shanghai OpenStack Meet-up at IBM (July 4th, 2015) 王天青 EMC中国研究院
- 2. 2
- 4. 4 BILLIONS OF USERS BILLIONS OF DEVICES MILLIONS OF APPS Application Service IaaS Tomorrow’s Data Center Next Gen Cloud Applications 2016 48M 2012 6M 700% Traditional Applications 2016 141M 2012 83M 70% Today’s Data Center
- 6. 6 • Speed of innovation • Always-available services • Web scale • Mobile-centric user experiences Why Disruptive?
- 7. 7 • The Twelve-Factor App: a collection of cloud- native app architecture patterns • Microservices: independently deployable services that do one thing well • Self-Service Agile Infrastructure: platforms for rapid, repeatable, and consistent provisioning of app environments and backing services • API-based Collaboration: published and versioned APIs that allow interaction between services in a cloud-native app architecture • Anti-Fragility: systems that get stronger when subjected to stress How?
- 8. 8 Application Life Cycle Management 开发 测试 集成 发布 部署 运维 Dev Ops
- 9. 9 • Deployment – Dependency – Installation – Startup – Configuration • Operation – Monitoring (status, Metrics, Log) & Trouble Shooting – Configuration – Upgrade – Scale, Backup, HA, DR Challenges of Ops
- 10. 10
- 11. 11 Deployment on OpenStack, Practice #1 • Image Management – Build: diskimage-builder, Oz, VMBuilder, BoxGrinder, VeeWee, Packer, imagefactory, SUSE Studio • Infrastructure Resource Provisioning – Orchestration by Heat: network (router, gateway, subnet, floating IP…), compute (security group, key pairs, VM…), storage (volume) • Application Deployment and Configuration – Puppet
- 12. 12 Example: Install OpenStack via Puppet
- 13. 13 Bare-metal Orchestration Puppet Policy MCO Broker Node Razor Kick-Start + Proceed Isilon HDFSFile & Block Backup Install Operating System 1. Install OpenStack; 2. Configure EMC Storage to OS Infrastructure M&O Machines && Deployment Specs Puppet Heat & Sahara App M&OCloud M&O Nise Puppet
- 14. 14 Unified M&O
- 15. 15 • Image: CentOS 6.0 • Heat: Provisioning resources • Puppet: Install ScaleIO Install ScaleIO on OpenStack
- 16. 16 • Cloudify integrates with Heat out of the box • Cloudify Heat Template • Infrastructure Orchestration Built-in Network Orchestration with Neutron Deployment on OpenStack, Practice #2
- 18. 18 • Topology and Orchestration Specification for Cloud Applications TOSCA 1. DSL 2. Inputs 成也萧何，败也萧何
- 19. 19 • BOSH is a project that unifies release engineering, deployment, and lifecycle management of small and large-scale cloud software. • It also performs monitoring, failure recovery, and software updates with zero-to-minimal downtime. • While BOSH was developed to deploy Cloud Foundry PaaS, it can also be used to deploy almost any other software (Hadoop, for instance). • In addition BOSH supports multiple Infrastructure as a Service (IaaS) providers like VMware vSphere, vCloud Director, Amazon Web Services EC2, and OpenStack. Deployment on OpenStack, Practice #3
- 20. 20 BOSH Overview
- 21. 21 • Stemcell: A stemcell is a versioned Operating System image wrapped with IaaS specific packaging. • Release: A release is a versioned collection of configuration properties, configuration templates, start up scripts, source code, binary artifacts, and anything else required to build and deploy software in a reproducible way. • Deployment: A deployment is a collection of VMs, built from a stemcell, that has been populated with specific releases and disks that keep persistent data. These resources are created based on a manifest file in the IaaS and managed by the BOSH Director, a centralized management server. BOSH Major Concepts
- 23. 23 Cloud Foundry Deploy Cloud Foundry On OpenStack BOSH-INIT Release: • bosh • bosh-openstack-cpi Stemcell: • bosh-openstack-kvm- ubuntu-trusty-go_agent Manifest • Bosh-deploy.yml OpenStack (IaaS) VM BOSH CPI Controller OS Agent VM Agent VM Agent VM 1 2 Release: • cf-release Stemcell: • bosh-openstack-kvm- ubuntu-trusty-go_agent Manifest • CF-deploy.yml BOSH-CLI 3 4 5
- 24. 24 • Murano: The Murano Project introduces an application catalog to OpenStack, enabling application developers and cloud administrators to publish various cloud-ready applications in a browsable categorized catalog. • http://apps.openstack.org/ Deployment on OpenStack, Practice #3
- 26. 26 Murano - Lattice https://github.com/LaynePeng/murano_lattice
- 30. 30 • Magnum: Magnum is an OpenStack API service to make container orchestration engines such as Docker and K8s available as first class resources in OpenStack. Magnum uses Heat to orchestrate an OS image which contains Docker and K8s and runs that image in either virtual machines or bare metal in a cluster configuration. Future Research Plan - Magnum
- 31. 31 • Application M&O – Integrated with Infrastructure & Cloud M&O (Application M&O -> Cloud M&O -> Infrastructure M&O) – Beyond Deployment, need support Operation. Also should be Development friendly. – Cloud-native app friendly (12 factor apps, Microservices) Summary
- 32. 32 • Vote for OpenStack Tokyo Summit Talk: OpenStack Managed Cloud Foundry Service Marketplace, By Layne Peng and Grissom Wang Advertisement
- 33. 33 Contributors & EMC Labs China Layne Jie Vivian Jinlong