Razor, Puppet & VMware Giuseppe Guglielmetti vExpert VMware VSP, VTSP, VCP4/5, vExpert 2011/2012 Kiratech srl Email: [email protected] Mobile +39 366 2041096
Jul 16, 2015
Razor, Puppet & VMware
Giuseppe Guglielmetti vExpert VMware VSP, VTSP, VCP4/5, vExpert 2011/2012 Kiratech srl Email: [email protected] Mobile +39 366 2041096
Who I am
• Senior System Engineer for Kiratech
• Virtualization, Storage and Backup specialist
• VCP 4,5, vExpert 2011/2012
• Veeam Technical Sales Professional
• Cisco Unified Computing Technology Support Specialist
@gguglie
Puppet & VMware
• Multiple integration ways…
• Razor
• vCenter integration
• vFabric Application Director integration
• Official VCSA & vShield modules (NEW!)
• ..plus the obvious one: just manage a VM as a physical node (and Facter is your friend!)
Razor
• Tool developed by Nick Weaver
• Open source
• Dynamic provisioning of • operating systems
• hypervisors
• for both • physical server
• virtual servers
• Event driven
How Razor works (1)
Discovery • Single purpose: find out what a
compute node is made of • MicroKernel booted through
PXE • The MicroKernel uses Puppet’s
Facter to gather information on hardware, type of server and type of virtualization it is on
• Real time
How Razor works (2)
Tagging
• Allows to group nodes by applying tags
• A Tag Rule apply a Tag to a node
• A Tag Rule contains qualifying rules called Matchers
• Matchers use attributes collected during discovery to classify nodes
How Razor works (3)
Models
• Model template: one or more files that describe how to do something
• Model Templates for installing common things are available out of the box
• Model: instance of a Model Template plus some metadata required (like license key, password, hostname, domain…)
How Razor works (4)
Policy
• Is a rule that applies a Model to a Node based on matching against Tags
• Fully automatic: • a Node checks-in
• Razor checks the Policies looking for a match
• when a match is found it applies the Policy and binds the Model
How Razor works (5)
Broker plugin (1)
• A Broker is an external system that will configure a Node for its true purpose
• After completing the provisioning of OS/Hypervisor, a Broker comes into play for managing configuration
• The standard broker is Puppet Master
• The Puppet Broker Plugin enables both agent handoff (Linux) and proxy handoff (vSphere ESXi)
How Razor works (6)
Broker plugin (2)
• Razor delivers all the metadata including tags to Puppet
• Puppet can use tags passed by Razor to make decisions on configuration
• e.g.: link similarly tagged ESXi nodes into the same cluster
vCenter integration
• Puppet subcommand node_vmware
• Puppet Enterprise only
• List VM
• Create VM from template
• Start/stop VM
• Destroy VM
• Automatically install Puppet Agent
VCSA & vShield Modules
• Open source Puppet modules • Developed by VMware and PuppetLabs • Management for the vCenter Server Appliance (VCSA)
• Initialization • Datacenter and Cluster configuration • ESXi Host
• Management for the vShield Manager • Initialization • Association to vCenter • vShield Edge Deployment • vShield Edge Configuration
vFabric Application Director
• vFabric Application Director is a cloud-enabled application provisioning and maintenance solution
• simplifies how to create and standardize application deployment topologies across cloud services
• Create complete deployment blueprint
AppDirector integration
• The Puppet integration solution enables • deploy applications via Puppet manifests
• deploy vFabric Application Director blueprints using existing Puppet modules
• Leverages vFabric Application Director management console to • configure Puppet classes
• Use Puppet modules as vFabric Application Director blueprints
Resources
• http://nickapedia.com/2012/05/21/lex-parsimoniae-cloud-provisioning-with-a-razor/
• https://puppetlabs.com/solutions/next-generation-provisioning/
• http://puppetlabs.com/solutions/vmware/
• http://www.vmware.com/products/application-platform/vfabric-application-director/overview.html
• http://www.youtube.com/watch?v=X9QB8FA_hug
• http://nickapedia.com/2013/02/27/vmware-puppet-one-more-step-forward/