Hands-on Workshop for Operators Manuel Garcia / altoros.com / @rmgarciap
May 06, 2015
Hands-on Workshop for Operators
Manuel Garcia / altoros.com / @rmgarciap
*Why this training?•SysAdmins and DevOps requested it in several
meetup Altoros talks
•Evolution from a minimalistic CF local installation workshop to a full CF deployment done with BOSH
*Goals•Understand how Cloud Foundry is deployed
•Get to know how Cloud Foundry internally works from an PaaS Operator perspective
Hands on?
1, 2, 3… go!
* How do I deploy Cloudfoundry?
Nise Bosh, a lightweight BOSH emulator. Virtual and bare metal
Altoros Vagrant Installer, developer oriented deployment
BOSH, tool chain for release engineering
Bosh Lite, a lite development environment for BOSH. Conteinerized VMs
Canonical Juju Charms, cloud infrastructure automation
*It is so easy
•Install Bosh•Deploy Something (ex.: ElasticSearch)•Upload stemcell•Upload release•Configure deployment manifest•Deploy !
*Bosh Lite – From Local to the Cloud• Prerequisites • GIT• Ruby 1.9.3 (latest. 2.0.X not supported)• RubyGems and Bundler• VirtualBox• Vagrant
• Clone repo and deploy bosh lite (preferable local)• Lower RAM if needed (Vagrantfile)• $ vagrant up
*Bosh Lite – From Local to the Cloud• Upload Stemcell• $ bosh public stemcells• $ bosh download public stemcell bosh….tgz
• Download Elasticsearch bosh release• $ git clone https://github.com/bonzofenix/elasticsearch-boshrelease
• Upload it to Bosh• $ bosh upload release releases/<version>.yml
• Deploy ElasticSeach• $ bosh manifest <elasticsearch manifest file>• $ bosh deploy
* What is Bosh? Why BOSH?
Designed for large scale, distributed services
Tool chain for release engineering, deployment and lifecycle management
Already Supports AWS, OpenStack & VMware vSphere (Cloudstack)
Two floors up from Chef/Puppet. Multi-cloud, IaaS Provider independent
Updates & Operates Deployments
Deploys & Manages Clusters of Cloud Foundry, Databases, etc
BOSH Overview
BOSH Releases
*What is a release?• A collection of configuration:
– files, – job definitions– source code– package definitions – and accompanying information needed to make a
software component deployable by BOSH.
• A release should have no dependencies that need to be fetched from the internet.
*What is a release?• Source directories
– jobs: start and stop commands for each of the jobs (processes) running on Cloud Foundry nodes.
– packages: packaging instructions used by BOSH to build each of the dependencies.
– src: the source code for the components in Cloud Foundry. Note that each of the components is a submodule with a pointer to a specific SHA.
*What is a release?• Releases directories
– releases: yml files containing the references to blobs for each package in a given release; these are solved within .final_builds
– .final_builds: references into the public blostore for final jobs & packages (each referenced by one or more releases)
– config: URLs and access credentials to the bosh blobstore for storing final releases
*Example BOSH Release• ElasticSearch release
• Take me to the repo…
*Cloud Foundry BOSH Release
• Around 20 jobs• Open Source: github.com/cloudfoundry/cf-release• Weekly releses (releases directory)• Fully tested (CAT)
*Bosh Lite (lets continue)• Upload Warden Stemcell• $ bosh public stemcells• $ bosh upload stemcell latest-bosh-stemcell-warden.tgz
*Stemcells• A minimal VM image that can convert into anything
• Contains a BOSH Agent: A process that runs continuously on each VM that BOSH deploys (one Agent process per VM). The BOSH Agent executes tasks in response to messages it receives from the BOSH Director
*In the meantime.. What have we done?•MicroBosh in a local VM
• Director, public API• Blobstore, to store and retrieve
precompiled packages• Health Manager, to track the state of
deployed systems• Internal DNS, called PowerDNS, for
internal unique naming of servers within bosh deployments
• Bosh Database, desired state of a BOSH deployment
• Message Bus (NATS)• Registry, for tracking the
infrastructure that has been provisioned (servers, persistent disks)
• Resurrector• Task Queue (requires Redis), async
queue used by the BOSH Director and Workers to manage tasks
Example Component Interaction
Lets Deploy Cloud Foundry
*CF deployment steps• Download Release from repo and upload it to
BOSH– $ git clone https://github.com/cloudfoundry/cf-release– $ bosh upload release releases/cf-169.yml– Check it is there: $ bosh releases
• Build deployment manifest and tell BOSH to use it– $ ./scripts/make_manifest_spiff– $ bosh deployment manifests/cf-manifest.yml
• Deploy: $ bosh deploy
Test your Cloud Foundry Deployment
*Target and deploy• $ cf login -a https://api.10.0.244.34.xip.io
• Download, build and deploy the app– $ git clone https://github.com/mgarciap/cf-ruby-example.git– $ cd cf-ruby-example– $ cf push
• App metadata? – Manifests
Runtimes and Frameworks
Buildpacks
*• Java
– Java, Grails, Play, Spring or any other JVM-based language or framework
• Node.js– Node or JavaScript
• Ruby– Ruby, Rack, Rails or Sinatra
• Go Lang
Cloud Foundry System Buildpacks
*> cf push = deploy
CLI Cloud Controller
CCDB(MySQ
L)
Blob Store (S3, etc.)
Executor
Stager
W
Build packs
A2
A2 A3
A3
A1
A1
Pkg
Metadata
PkgMetadata
Pkg
Droplet
Droplet
Users
Router
A1.yourdomain.com
Frontend Backend
Stage A1
Deploy A1
DEA Nodes
*• $ cf app [app]• $ cf logs [app]
• Logs are streamed. CC API, Staging, DEA, Router – HTTP and finally your app
• Dump: cf logs [app] –recent
• $ cf env [app name]• $ cf events [app name]• $ cf files [app]
Something wrong deploying the app?
Services
( *aaS )
*• They can be anything external resource as far as they provide
an API and they are registered with the CC• Actions
• Provision/deprovision• Bind/unbind
Services
No downtime deployments
Blue-green deployment release technique
*• One production domain and two apps
• Blue prod • Green next release• $ cf push Blue -n demo-time
Blue-Green Deployment
*• Update App and Push• $ cf push Green -n demo-time-
temp
Blue-Green Deployment
*• Map Original Route to Green• $ cf map-route Green
example.com -n demo-timeBinding demo-time.example.com to Green... OK
Blue-Green Deployment
*• Unmap Route to Blue• cf unmap-route Blue example.com
-n demo-time-tempUnbinding demo-time.example.com from blue... OK
Blue-Green Deployment
*• Remove Temporary Route to Green• $ cf unmap-route Green
example.com -n demo-time-temp
Blue-Green Deployment
Key architectural characteristics
*
Portable
Key architectural characteristics
CPIs
*
Portable
Key architectural characteristics
https://github.com/cloudfoundry
Open Source
*
Scalable• From few servers to thousands• Horizontally and Vertically
Key architectural characteristics
*
Reliable
Very few Single Points of Failure which are been improved (Message Bus -NAT S server-, Collector)
Key architectural characteristics
*
Extensible
Loosely Coupled Components with specific responsibilities and technology agnostic intercommunication through a message bus. Ruby? Rewrite in GO lang? No problem
Key architectural characteristics
Cloud Foundry Architecture Overview
*Core components
* What have we done?
• Install BOSH (with bosh lite)• Install BOSH CLI• Upload stemcell• Upload Release• Create and configure Deployment Manifest• Deploy CF
* What have we done?
• Install Cloud Foundry CLI (cf)• Target and log into CF• Create organization and space• Push an application
* What is next? Deploy CF into a IaaS
• Small/Medium deployment for demos/testing• Microbosh
• Medium to large production deployments• Deploy Microbosh• With Microbosh deploy BOSH• From BOSH deploy CF
Thank [email protected]
@rmgarciap(650) 395-7002