Deployment Sets

Time 2021-11-15 20:07:53

Web Name: Deployment Sets

WebSite: http://deploymystage.blogspot.com

ID:234128

Keywords:

Deployment,Sets,

Description:

keywords:
description:

Deployment Sets

Saturday, February 1, 2014 Basic Puppet...


PuppetA Configuration Management Tool
A framework for Systems Automation
A Declarative Domain Specific Language ()
An OpenSource software in written Ruby
Works on Linux, Unix (Solaris, AIX, *BSD), MacOS, Windows
Developed by Labs
Used by (http://puppetlabs.com/customers/companies/)...
... and many others
Configuration Management advantagesInfrastructure as Code: Track, Test, Deploy,Reproduce, Scale
Code commits log shows the history of change onthe infrastructure
Reproducible setups: Do once, repeat forever
Scale quickly: Done for one, use on many
Coherent and consistent server setups
Aligned Environments for devel, test, qa, prodnodes
References and EcosystemLabs - The Company behind
- The OpenSource version
Enterprise- The commercial version
The Community- Active and vibrant
Documentation - Main andOfficial reference
Modules on: Module Forgeand GitHub
Software related to :
MCollective- Infrastructure Orchestration framework
Hiera- Key-value lookup tool where data can be placed
PuppetDB- An Inventory Service and StoredConfigs backend
DashBoard- A Web frontend and External Node Classifier (ENC)
TheForeman - A well-known third party provisioning tool andENC
Geppetto -A IDE based on Eclipse
InstallationDebian, Ubuntu
Available by default

#Onclients(nodes):apt-getinstallpuppet#Onserver(master):apt-getinstallpuppetmaster

RedHat, Centos, Fedora
Add EPEL repository or RHN Extra channel

#Onclients(nodes):yuminstallpuppet#Onserver(master):yuminstallpuppet-server

Use PuppetLabsrepositories for latest updates
InstallationInstructions for different OS
Puppet configuration: puppet.confIt's main configuration file.
On opensource is generally in:

/etc/puppet/puppet.conf

On Enterprise:

/etc/puppetlabs/puppet/puppet.conf

When running as a normal user can be placed in the home directory:

/home/user/.puppet/puppet.conf

Configurations are divided in [stanzas] for different sub commands
Common for all commands: [main]
For puppetagent (client): [agent] (Was [puppetd] in pre2.6)
For puppet apply (client): [user] (Was[puppet])
For puppet master (server): [master](Was [puppetmasterd] and [puppetca])
Hash (#) can be used for comments.
Configuration optionsTo view all or a specific configuration setting:

puppetconfigprintallpuppetconfigprintmodulepath

Important options under [main] section:
vardir:Path where stores dynamic data.
ssldir: Pathwhere SSL certifications are stored.
Under [agent] section:
server:Host name of the PuppetMaster. (Default: puppet)
certname:Certificate name used by the client. (Default is thehostname)
runinterval: Number of minutes betweenruns, when running as service. (Default: 30)
report:If to send runs' reports to the **report_server. (Default: true)
Under [master] section:
autosign:If new clients certificates are automatically signed. (Default:false)
reports: How to manage clients' reports(Default: store)
storeconfigs: If to enable storeconfigs to support exported resources. (Default: false)
Full configurationreference
Common command-line parametersAll configuration options can be overriden by command-lineoptions.
Run puppet agent in foreground and verbose mode.
A very commonoption used when you want to see immediately the effect of arun.
It's actually the combination of: -onetime, -verbose,-ignorecache, -no-daemonize, -no-usecacheonfailure,-detailed-exit-codes, -no-splay, and -show_diff

puppetagent--test

Run puppet agent in foreground and debug mode

puppetagent--test--debug

Run puppet without making any change to the system

puppetagent--test--noop

Run puppet using an environment different from the default one

puppetagent--environmenttesting

Wait for certificate approval (by default 120 seconds) in the firstRun
Useful during automated first fime installation ifPuppetMaster's autosign is false

puppetagent--test--waitforcert120

Other configuration files:auth.conf
Defines ACLs to access 's RESTinterface. Details
fileserver.conf
Used to manage ACL on filesserved from sources different than modules Details
puppetdb.conf
Settings for connection toPuppetDB, if used. Details
tagmail.conf , autosign.conf ,device.conf , routes.yaml
Theseare other configuration files for specific functions. Details
Puppet LanguageA Declarative Domain Specific Language ()
Defines STATES (Not procedures)
code stays in manifests (files .pp)
Code contains resources that affects elements ofthe systme (file, package, service ...)
Resources are often grouped in classes which aregenerally organized in modules
Variables may be defined nodes and can be Facts(generated from the node) or User defined
On the Master are defined the resources or classes to include onthe nodes (clients)
All the resources to apply on a node are defined in the catalog,generated by the Master
Resource Types (Types)Resources are single units of configurationcomposed by:
A type (package, service, file,user, mount, exec ...)
A title (how is called andreferred)
One or more arguments

type{'title':argument=value,other_arg=value,}

Example for a file resource type:

file{'motd':path='/etc/motd',content='Tomorrowisanotherday',}

Complete TypeReference Online or at the command line

puppetdescribefile

Give a glance to code for the list of nativeresource types:

ls$(facterrubysitedir)/puppet/type

Simple samples of resourcesInstallation of OpenSSH package

package{'openssh':ensure=present,}

Creation of /etc/motd file

file{'motd':path='/etc/motd',}

Start of httpd service

service{'httpd':ensure=running,enable=true,}

More Complex examples of resourcesInstallation of Apache package with the correct name for differentOS

package{'apache':ensure=present,name=$operatingsystem?{/(?i:Ubuntu|Debian|Mint)/='apache2',default='httpd',}}

Management of nginx service with parameters defined in module'svariables

service{'nginx':ensure=$nginx::manage_service_ensure,name=$nginx::service,enable=$nginx::manage_service_enable,}

Creation of nginx.conf with content retrived from different sources(first found is served)

file{'nginx.conf':ensure=present,path='/etc/nginx/nginx.conf',source=["puppet:///modules/site/nginx/nginx.conf--${fqdn}","puppet:///modules/site/nginx/nginx.conf-${role}","puppet:///modules/site/nginx/nginx.conf"],}}

Resource Abstraction LayerResources are abstracted from the underlining OS
Resource Types have different providers for different OS
Package type is known for the great number of providers

ls$(facterrubysitedir)/puppet/provider/package

Use puppet resource to interrogate the RAL:

puppetresourceuserpuppetresourceuserrootpuppetresourcepackagepuppetresourceservice

Or to directly modify resources:

puppetresourceservicehttpdensure=runningenable=true

ClassesClasses are containers of different resources.Since 2.6 they can have parameters
Example of a class definition:

classmysql{package{'mysql-server':ensure=present,}service{'mysql':ensure=running,}[...]}

Usage (declaration) of "old style" classea (withoutparameters):
Even if a class is a singleton, you can include itmultiple times: it's applied only once.

includemysql

Usage (declaration) of a parametrized classes
You can declare aparametrized class only once for a node

class{'mysql':required_param='my_value',optional_param='dont_like_defaults',}

DefinesAlso called: Defined resource types or definedtypes
Similar to parametrized classes but can be used multi times, withdifferent parameters
Definition example:

defineapache::virtualhost($template='apache/virtualhost.conf.erb',[...]){file{"ApacheVirtualHost_${name}":ensure=$ensure,content=template("${template}"),}}

Usage example (declaration):

apache::virtualhost{'www.example42.com':template='site/apache/www.example42.com-erb'}

VariablesYou need them to provide different configurations for differentkind of servers
Can be provided by client nodes as facts
Facter runs on clients and collects factsthat the server can use as variables

al$facterarchitecture=x86_64fqdn=Macante.example42.comhostname=Macanteinterfaces=lo0,eth0ipaddress=10.42.42.98ipaddress_eth0=10.42.42.98kernel=Linuxmacaddress=20:c9:d0:44:61:57macaddress_eth0=20:c9:d0:44:61:57memorytotal=16.00GBnetmask=255.255.255.0operatingsystem=Centosoperatingsystemrelease=6.3osfamily=RedHatvirtual=physical

Or can be defined by users
User VariablesYou can define custom variables in different ways:
In manifests:

$role='mail'$package=$operatingsystem?{/(?i:Ubuntu|Debian|Mint)/='apache2',default='httpd',}

In an External Node Classifier ( DashBoard, the Foreman, Enterprise)
In an Hiera backend

$syslog_server=hiera(syslog_server)

NodesA node is identified by the PuppetMaster by its hostnameor certname
You can decide what resources, classes and variables to assign toa node in 2 ways:
Using language ( Starting from /etc/manifests/site.pp )

node'web01'{includeapache}

Using an External Node Classifier (DashBoard, Foreman or customscripts)
When a client connects a PuppetMaster builds a catalogwith all the resources to apply on the client
The catalog is in Pson format (a version of Json)
ModulesSelf Contained and Distributable recipes contained in adirectory with a predefined structure
Used to manage an application, system's resources, a local site ormore complex structures
Modules must be placed in the Master's modulepath

puppetconfigprintmodulepath/etc/puppet/modules:/usr/share/puppet/modules

module tool to interface with Modules Forge

puppethelpmodule[...]ACTIONS:buildBuildamodulereleasepackage.changesShowmodifiedfilesofaninstalledmodule.generateGenerateboilerplateforanewmodule.installInstallamodulefromthePuppetForgeoranarchive.listListinstalledmodulessearchSearchthePuppetForgeforamodule.uninstallUninstallapuppetmodule.upgradeUpgradeapuppetmodule.

GitHub, also, is full of modules
Paths of a moduleModules have a standard structure:

mysql/#Mainmoduledirectorymysql/manifests/#Manifestsdirectory.Puppetcodehere.Required.mysql/lib/#Pluginsdirectory.Rubycodeheremysql/templates/#ERBTemplatesdirectorymysql/files/#Staticfilesdirectorymysql/spec/#Puppet-rspectestdirectorymysql/tests/#Tests/Usageexamplesdirectorymysql/Modulefile#Module'smetadatadescriptor

This layout enables useful conventions
Modules paths conventionsClasses and defines autoloading:

includemysql#Mainmysqlclassisplacedin:$modulepath/mysql/manifests/init.ppincludemysql::server#Thisclassisdefinedin:$modulepath/mysql/manifests/server.ppmysql::conf{...}#Thisdefineisdefinedin:$modulepath/mysql/manifests/conf.ppincludemysql::server::ha#Thisclassisdefinedin:$modulepath/mysql/manifests/server/ha.pp

Provide files based on Erb Templates (Dynamic content)

content=template('mysql/my.cnf.erb'),#Templateisin:$modulepath/mysql/templates/my.cnf.erb

Provide static files (Static content). Note you can use content ORsource for the same file.

source='puppet:///modules/mysql/my.cnf'#Fileisin:$modulepath/mysql/files/my.cnf

Erb templatesFiles provisioned by can be Ruby ERB templates
In a template all the variables (facts or user assigned) can beused :

#FilemanagedbyPuppeton%=@fqdn%search%=@domain%

But also more elaborated Ruby code

%@dns_servers.eachdo|ns|%nameserver%=ns%%end%

The computed template content is placed directly inside thecatalog
(Sourced files, instead, are retrieved from thepuppetmaster during catalog application)
Principes behind a Reusable ModuleData Separation

-Configurationdataisdefinedoutsidethemodule(orevenPuppetmanifests)-Module'sbehaviorismanagedviaAPIs-Allowmodule'sextensionandoverrideviaexternaldata

Reusability

-SupportdifferentOS.Easilyallownewadditions.-Customizebehaviorwithoutchangingmodulecode-Donotforceauthor'sideaonhowconfigurationsshouldbeprovided

Standardization

-FollowPuppetLabsstyleguidelines(puppet-lint)-Havecoherent,predictableandintuitiveinterfaces-Providecontextualdocumentation(puppet-doc)

Interoperability

-Limitcross-moduledependencies-Alloweasymodules'cherrypicking-Beselfcontained,donotinterferewithothermodules'resources

What's a Good Module anyway?The most reusable and customizable
The one full of features
The one that works for you
The most essential, and optimized (but not reusable) one
The quickest one to do now
as usual... your mileage may vary
In 's world the concept of "Best Practices" is somehowfluid... :-)
(It follows the language's features evolution and theblog post of the moment...)
Modules documentation with Puppet DocPuppetdoc generates documentation from manifests comments:

$puppetdoc[--all]--moderdoc[--outputdir][--debug|--verbose][--trace][--modulepath][--manifestdir][--config]

Comment classes as below:

#Class:apache##ThismodulemanagesApache##Parameters:##Actions:##Requires:##[Remember:Noemptylinesbetweencommentsandclassdefinition]classapache{...}

Posted byGMat8:41 AMNo comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to PinterestNode AWS with Puppetlib/puppet/face/node_aws.rb

require 'puppet/face'Puppet::Face.define(:node_aws, '0.0.1') docopyright "Puppet Labs", 2011 .. 2013license   "Apache 2 license; see COPYING"summary "View and manage Amazon AWS EC2 nodes."description -'EOT'    This subcommand provides a command line interface to work with Amazon EC2    machine instances.  The goal of these actions is to easily create new    machines, install Puppet onto them, and tear them down when they're no longer    required.  EOTend

Posted byGMat8:19 AMNo comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Monday, January 27, 2014 Puppet Agent to be seen by PM

Now We will configure our puppet agent to fetch configuration(although we do not have any configuration to be applied as of now) from our puppet master server(slashroot1). We have already started puppet master on the machine slashroot1. Our master server is listening connections on the port 8140.
the first step i will suggest doing is to edit the /etc/hosts file of your puppet agent server(slashroot2 in our case), and add puppet master server's ip and hostname(if you have your DNS entry configured for the master server then its well and fine.).
I believe that you have already installed the packages puppet facter on your agent server as shown in the post "installing puppet agent and master".
Now lets connect our puppet agent to puppet master server for the first time. And see what happens.
?12345678910111213[root@slashroot2 ~]# puppet agent --server slashroot1.slashroot.in --no-daemonize --verboseinfo: Creating a new SSL key for slashroot2.slashroot.inwarning: peer certificate won't be verified in this SSL sessioninfo: Caching certificate for cawarning: peer certificate won't be verified in this SSL sessionwarning: peer certificate won't be verified in this SSL sessioninfo: Creating a new SSL certificate request for slashroot2.slashroot.ininfo: Certificate Request fingerprint (md5): 59:7A:AE:2C:7B:15:DA:E5:A8:14:7D:FF:1F:5B:7A:66warning: peer certificate won't be verified in this SSL sessionwarning: peer certificate won't be verified in this SSL sessionwarning: peer certificate won't be verified in this SSL sessionwarning: peer certificate won't be verified in this SSL sessionnotice: Did not receive certificateAs shown in the above example you can see that, an SSL key is made for this agent machine and is waiting for the corresponding certificate to be signed by the puppet master server.
An Important fact to note here is a notice shown in the above command result, which says that "notice: Did not receive certificate".
--server in the above command specifies the puppet master server hostname
--no-daemonize tells the puppet agent to not to run as a daemon, and also output the messages to the screen. If you run puppet agent without this option, then you will not get the messages on the screen.
Note: If you do not specify the option --server, puppet agent will look for a host named "puppet". This is the main reason of keeping the puppet master hostname as puppet.
The ssl certificate signing is done only the first time an agent connects to the server.
The notice message(notice: Did not receive certificate)will keep on coming on the screen until the certificate request is signed by the puppet master.
How to Sign the SSL certificate from puppet Master?Now as the client node (slashroot2) is waiting for its certificate to be signed, lets go and sign the certificate request from slashroot1(our puppet master server)
On your puppet master run the below command to show the certificate signing requests.

[root@slashroot1 ~]# puppetca --list  slashroot2.slashroot.in (59:7A:AE:2C:7B:15:DA:E5:A8:14:7D:FF:1F:5B:7A:66)[root@slashroot1 ~]#

#puppetca --list command will show you the agent certificate requests that are waiting to be signed.
#puppet cert list command will also show you the same thing
Now lets sign the certificate by the following method.

[root@slashroot1 ~]# puppetca --sign slashroot2.slashroot.innotice: Signed certificate request for slashroot2.slashroot.innotice: Removing file Puppet::SSL::CertificateRequest slashroot2.slashroot.in at '/var/lib/puppet/ssl/ca/requests/slashroot2.slashroot.in.pem'

Now from the above output you can clearly see that the puppet master server signed the certificate and also removed the old certificate signing request.
Now as soon as the certificate gets signed from the master server you will get the below message on the puppet agent's screen(because we ran puppet agent command with --no-daemonize option on our agent).

notice: Did not receive certificatewarning: peer certificate won't be verified in this SSL sessionnotice: Did not receive certificate

warning: peer certificate won't be verified in this SSL sessioninfo: Caching certificate for slashroot2.slashroot.innotice: Starting Puppet client version 2.7.9info: Caching certificate_revocation_list for cainfo: Caching catalog for slashroot2.slashroot.ininfo: Applying configuration version '1355395673'info: Creating state file /var/lib/puppet/state/state.yamlnotice: Finished catalog run in 0.14 seconds

Now what does that message mean? It means that our puppet agent got a signed certificate and the certificate is cached. Also the agents tells us that its applying a configuration version number "1355395673" based on the catalog given by the master server.

From now onwards we can restart and stop our puppet agent whenever required. Note: Keep all the client nodes and the puppet server synchronized with one single ntp source. Because ssl connection rely heavily on time being synchronized.

We ran the command #puppet agent --server slashroot1.slashroot.in --no-daemonize --verbose, just for showing the output on the screen as example.In normal cases you can add the puppet server address in the puppet.conf file of your agent machine. So on our agent we will add server address in the [main] section as shown below.
server=slashroot1.slashroot.in

After adding this server option in puppet.conf file simply restarting puppet agent will start it as a daemon. Which will periodically fetch data from the master server.You can start/restart your puppet agent using the below commands./etc/init.d/puppet startorpuppet agentPosted byGMat5:55 PMNo comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterestpuppet masterPuppet.conf is the main configuration file of puppet. On most of the distribution this file is located under, /etc/puppet/ directory. Most of the times this file (/etc/puppet/puppet.conf) is automatically created during the installation. But if it is not there, you can easily create it by the following command.
[root@slashroot1 ~]# puppetmasterd --genconfig /etc/puppet/puppet.conf
Puppet.conf file is easier to understand, and is very much self explanatory. Its divided into different sections as the following.

[agent] -- this section is for mentioning agent specific parameters.
[master] -- this section is for specifying options for puppet master.
[main] -- this section will contain all global configuration options.

Main section will contain options like the log directory,pid directory etc.(don't worry we will go ahead and configure all those, be patient)
The first step is to configure the /etc/hosts file and DNS entries with the ip of puppet master and its FQDN(Fully Qualified Domain Name).
Am keeping my puppet master name as puppet.slashroot.in. So my host entries will be something like the below.

[root@slashroot1 ~]# cat /etc/hosts# Do not remove the following line, or various programs# that require network functionality will fail.127.0.0.1               slashroot1.slashroot.in slashroot1 localhost.localdomain localhost::1             localhost6.localdomain6 localhost6192.168.0.102 slashroot1.slashroot.in puppet puppet.slashroot.in

Also don't forget to add the same DNS entry in DNS server for your infra.
Now lets configure the [master] section of our puppet.conf file.
We will only be adding certname parameter in [master] section as of now. If you don't have the master section in your puppet.conf file then create it. My master section looks like the below.
[master]
certname=puppet.slashroot.in
Now lets configure an important file in puppet master configuration. Its the site.pp file. This is the file which tells what are the configurations that needs to be applied to the clients(agents).
We will be placing this site.pp file in /etc/puppet/manifests/ directory. Just create a file called site.pp there with no content. We will be adding configuration content inside this file later.
What are manifests in puppet?manifest is nothing but a name that puppet calls those files which contain the configuration options for the clients.
An important fact to note is that all manifest files will also have a .pp extension just the same as site.pp file
You can alter the location of manifests and site.pp file with the help of manifestdir and manifest options in puppet.conf file.
As i have mentioned in my post How does Puppet Work Puppet does all its communication through SSL. And the default directory for SSL certificates is /var/lib/puppet.

[root@slashroot1 ~]# ls /var/lib/puppet/bucket        client_data  facts  reports  server_data  stateclientbucket  client_yaml  lib    rrd      ssl          yaml

Now lets start puppetmaster, which will start master server listening on the port 8140. Starting puppet master server will also create a self signed certificate for the master server which can be found at /var/lib/puppet/ssl/ca/signed/

[root@slashroot1 signed]# /etc/init.d/puppetmaster startStarting puppetmaster:[root@slashroot1 signed]# ls /var/lib/puppet/ssl/ca/signed/puppet.slashroot.in.pem[root@slashroot1 signed]# lsof -i :8140COMMAND    PID   USER   FD   TYPE DEVICE SIZE NODE NAMEpuppetmas 3552 puppet    7u  IPv4   9583       TCP *:8140 (LISTEN)[root@slashroot1 signed]#

As shown in the above example we have started puppet master, which inturn created a signed certificate for our puppet master, (note the fact that the certificate name is exactly the same as the certname in puppet.conf file).
What methods can be used to start puppet master server?Puppet master can be started by the below methods.
#/etc/init.d/puppetmasterd start
OR
#puppetmasterd
OR
#puppet master
For troubleshooting purposes you can run puppet master as the following.
#puppet master --verbose --no-daemonizePosted byGMat5:54 PMNo comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Thursday, January 23, 2014 Install puppet agenthttps://github.com/moviepilot/puppet/blob/master/tools/install-puppet-agent.sh

#!/bin/bashif [ "$(id -u)" != "0" ]; then   echo "This script must be run as root" 12exit 1fi# refresh package listapt-get update# bootstrap ruby envapt-get -y install irb libopenssl-ruby libreadline-ruby rdoc ri ruby ruby-dev git-core augeas-lenses augeas-tools libaugeas-ruby# get a working gem version and update it to the most recent onecd /usr/local/srcwget http://production.cf.rubygems.org/rubygems/rubygems-1.5.2.tgztar -xzf rubygems-1.5.2.tgzcd rubygems-1.5.2ruby setup.rbupdate-alternatives --install /usr/bin/gem gem /usr/bin/gem1.8 1gem update --system# install puppet itselfgem install puppet -v 2.6.8 --no-ri --no-rdoc

Posted byGMat9:47 PMNo comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterestaws auto-scale

Eric LucasOnce Pre-Requisites are in place - this is the command.54.243.63.144Part 1as-create-launch-config jvcauto --image-id ami-e447c38d --instance-type m1.medium -I AKIAJEJVKDX6WSEOAZRQ -S mVKWOxwnKDmH5j0QOrYW8YkAAh1Y13eb63+s7v7Y --region us-east-1 --group jukin-security-1Resultsroot@matrix:/# as-create-launch-config jvcauto --image-id ami-e447c38d --instance-type m1.medium -I AKIAJEJVKDX6WSEOAZRQ -S mVKWOxwnKDmH5j0QOrYW8YkAAh1Y13eb63+s7v7Y --region us-east-1 --group jukin-security-1OK-Created launch configPart 2root@matrix:/# as-create-auto-scaling-group jukinscale --launch-configuration jvcauto -I AKIAJEJVKDX6WSEOAZRQ -S mVKWOxwnKDmH5j0QOrYW8YkAAh1Y13eb63+s7v7Y --availability-zones us-east-1b --min-size 2 --max-size 10 --load-balancers MainLoadJV --health-check-type ELB --grace-period 300OK-Created AutoScalingGroupPart 2-A ModifyCreate new launch-configurationas-create-launch-config jvcm1 --image-id ami-e447c38d --instance-type m1.medium -I AKIAJEJVKDX6WSEOAZRQ -S mVKWOxwnKDmH5j0QOrYW8YkAAh1Y13eb63+s7v7Y --region us-east-1 --group jukin-security-1Update-scaleing grouproot@matrix:/home/macross# as-update-auto-scaling-group jukinscale --launch-configuration jvm1 -I AKIAJEJVKDX6WSEOAZRQ -S mVKWOxwnKDmH5j0QOrYW8YkAAh1Y13eb63+s7v7YOK-Updated AutoScalingGroup2B modify max sizeas-update-auto-scaling-group jukinscale --launch-configuration jvm1 -I AKIAJEJVKDX6WSEOAZRQ -S mVKWOxwnKDmH5j0QOrYW8YkAAh1Y13eb63+s7v7Y --availability-zones us-east-1b --min-size 0 --max-size 3Part 3root@matrix:/# as-put-scaling-policy --auto-scaling-group jukinscale -I AKIAJEJVKDX6WSEOAZRQ -S mVKWOxwnKDmH5j0QOrYW8YkAAh1Y13eb63+s7v7Y --name scale-up --adjustment 1 --type ChangeInCapacity --cooldown 300arn:aws:autoscaling:us-east-1:838069323424:scalingPolicy:4186cee9-06cd-4bf0-968a-e99359e86f58:autoScalingGroupName/jukinscale:policyName/scale-upPart 4root@matrix:/# as-put-scaling-policy --auto-scaling-group jukinscale -I AKIAJEJVKDX6WSEOAZRQ -S mVKWOxwnKDmH5j0QOrYW8YkAAh1Y13eb63+s7v7Y --name scale-dn "--adjustment=-1" --type ChangeInCapacity --cooldown 300arn:aws:autoscaling:us-east-1:838069323424:scalingPolicy:53389773-a8f6-4c54-850d-7b797a9e8529:autoScalingGroupName/jukinscale:policyName/scale-dnPart 5mon-put-metric-alarm --alarm-name auto-scale-up -I AKIAJEJVKDX6WSEOAZRQ -S mVKWOxwnKDmH5j0QOrYW8YkAAh1Y13eb63+s7v7Y --alarm-description "Scale up at 80% load" --metric-name CPUUtilization --namespace AWS/EC2 --statistic Average  --period 60 --threshold 80 --comparison-operator GreaterThanThreshold --dimensions InstanceId=i-52a36c2d --evaluation-periods 3  --unit Percent --alarm-actions arn:aws:autoscaling:us-east-1:838069323424:scalingPolicy:4186cee9-06cd-4bf0-968a-e99359e86f58:autoScalingGroupName/jukinscale:policyName/scale-upOK-Created Alarmmon-put-metric-alarm --alarm-name auto-scale-dn -I AKIAJEJVKDX6WSEOAZRQ -S mVKWOxwnKDmH5j0QOrYW8YkAAh1Y13eb63+s7v7Y --alarm-description "Scale down at 20% load" --metric-name CPUUtilization --namespace AWS/EC2 --statistic Average --period 60 --threshold 20 --comparison-operator LessThanThreshold --dimensions InstanceId=i-52a36c2d --evaluation-periods 3 --unit Percent --alarm-actions arn:aws:autoscaling:us-east-1:838069323424:scalingPolicy:4186cee9-06cd-4bf0-968a-e99359e86f58:autoScalingGroupName/jukinscale:policyName/scale-up

Posted byGMat9:47 PMNo comments: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest HomeSubscribe to:Posts (Atom)About MeGMView my complete profileBlog Archive 2014(6) February(2)Basic Puppet...Node AWS with Puppet January(4)

TAGS:Deployment Sets 

<<< Thank you for your visit >>>

Hot Websites