Automating Cloud Orchestration with Puppet and Cloudify
•Download as PPTX, PDF•
3 likes•3,471 views
Ron Zavner, Technical Director, EMEA Presentation from the last DevOps Israel meetup where Ron presented how to achieve easy cloud orchestration using Cloudify for the post-deployment phase, while plugging into Puppet for the configuration management of the pre-deployment and deployment phase. All this on OpenStack.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Automating Cloud Orchestration with Puppet and Cloudify
Similar to Automating Cloud Orchestration with Puppet and Cloudify (20)
More from Cloudify Community
More from Cloudify Community (20)
Recently uploaded
Recently uploaded (20)
Automating Cloud Orchestration with Puppet and Cloudify
- 2. Cloud Automation – How? Orchestration, Automation, Scaling & What’s in Between Ron Zavner Technical Director, EMEA @ GigaSpaces
- 3. Agenda • App lifecycle • Tools for these phases • Conf Management • Orchestration • Real life scenario
- 4. The Automation Continuum Environment Creation Install Configure Monitoring & Alarming Repairing Scaling
- 5. Let’s Look at Some Tools
- 6. Orchestration Tools Environment Creation Install Configure Monitoring & Alarming Repairing Scaling
- 11. Puppet
- 12. Open Source Platform for Deploying, Managing and Scaling Complex Multi-Tier Applications on the Cloud
- 13. The Cloudify Recipe – Your Application Blueprint Middleware services to run Dependencies between services How to install & configure services (Puppet too) Where to get application & service binaries (Puppet too) When to add or remove instances How to monitor each of the services.
- 14. How Does Cloudify Use Puppet? Cloudify creates the virtual machines and installs Cloudify agents on them
- 15. How Does Cloudify Use Puppet? Cloudify agents install Puppet Agents and set the classes to run
- 16. How Does Cloudify Use Puppet? Puppet Agents install the required application services
- 17. Self Healing
- 19. Complete View of the App
- 21. Self Healing
- 22. Auto Scaling
- 23. Advantages of the Integration • Automating puppet deployment - agent installation • Dependency management (e.g tomcat => mysql) • Overall monitoring – deployment and post deployment • Multi Cloud - abstraction layer from the cloud
Editor's Notes
- Usually I start with an intro to what continuous deployment actually is – but since you’re more advanced than that – and could probably teach me a thing or two about CD and CI, I’ll just skip to the interesting stuffwell we all know the motivation for automation, and you may already know this but I’ll just state the obvious, while the cloud isn’t necessarily directly related to DevOps and automation, it’s often times achieved via the cloud because it exposes APIs and is basically software based infrastructure that is more easily manipulated etc etcAutomation Is Key for:TestabilityConsistencyAgilityStability
- ProvisioningVMs / Bare Metal ServersNetwork (Firewall, NAT, VPN, etc.)LB Groups Storage (Block / Blob) InstallOS Configuration (e.g. ulimit, useradd, permissions, etc.)Installation of packages and middleware components Startup orchestrationUpdate (not very frequent) User code installation on software infrastructure e.g. jar, war, rails sources, PHP sources, DB scripts, etc. After setupOn going - can be very frequentPost DeploymentWhat should be monitored? Availability: are my services up or not?Performance (OS &services level metrics). How are my services doing?State: What’s running where, state of system resourcesAlarms upon failure or when reaching certain thresholdsSimple (a-la CloudWatch) or complex (CEP driven)Various types of failuresService level – service not responding, process failedVM / Node failure Infrastructure failure (disk, network) Automation tools can go a certain way Resiliency should also be part of the SW stack Manually or Automatically (alarm triggered) Scaling by Adding / removing instances (AKA out / in)Adding / removing resources within existing instance (AKA up / down)For both, it needs to be supported by the SW stack
- Great at creating openstack resources, basic integration with Chef / puppet for swconfig, basic built in monitoring and alarming, moving to ceilometer in Havana
- Env setup is not automated SW infra setup is good but has no startup orchestration
- Healthnmon is more geared toward cloud resource monitoring and is has more opinionated domain model, ceilometer seems to be picking momentum and
- Talk about what’s next
- Cloudify provisions machines and installs Cloudify agents as part of the deployment
- Cloudify executes a parameterized Cloudify Puppet recipe. This recipe installs and runs the Puppet agent.
- The Puppet agent executes the Puppet Classifier and installs the required software.
- ProvisioningVMs / Bare Metal ServersNetwork (Firewall, NAT, VPN, etc.)LB Groups Storage (Block / Blob) InstallOS Configuration (e.g. ulimit, useradd, permissions, etc.)Installation of packages and middleware components Startup orchestrationUpdate (not very frequent) User code installation on software infrastructure e.g. jar, war, rails sources, PHP sources, DB scripts, etc. After setupOn going - can be very frequentPost DeploymentWhat should be monitored? Availability: are my services up or not?Performance (OS &services level metrics). How are my services doing?State: What’s running where, state of system resourcesAlarms upon failure or when reaching certain thresholdsSimple (a-la CloudWatch) or complex (CEP driven)Various types of failuresService level – service not responding, process failedVM / Node failure Infrastructure failure (disk, network) Automation tools can go a certain way Resiliency should also be part of the SW stack Manually or Automatically (alarm triggered) Scaling by Adding / removing instances (AKA out / in)Adding / removing resources within existing instance (AKA up / down)For both, it needs to be supported by the SW stack