ansible-1.7.2/000077500000000000000000000000001241061774000131405ustar00rootroot00000000000000ansible-1.7.2/.gitignore000066400000000000000000000014521241061774000151320ustar00rootroot00000000000000# build products... *.py[co] build AUTHORS.TXT # Emacs backup files... *~ .\#* # RPM stuff... MANIFEST dist rpm-build # Eclipse/PyDev stuff... .project .pydevproject # PyCharm stuff... .idea #IntelliJ IDEA stuff.. *.iml # Mac OS X stuff... .DS_Store # manpage build stuff... docs/man/man3/* # Sublime stuff *.sublime-project *.sublime-workspace # docsite stuff... docsite/rst/modules_by_category.rst docsite/rst/list_of_*.rst docsite/rst/*_module.rst docsite/*.html docsite/_static/*.gif docsite/_static/*.png docsite/_static/websupport.js docsite/searchindex.js docsite/htmlout # deb building stuff... debian/ deb-build # Vim swap files *.swp *.swo credentials.yml # test output .coverage results.xml coverage.xml /test/units/cover-html # Development /test/develop venv Vagrantfile .vagrant ansible.egg-info/ ansible-1.7.2/CHANGELOG.md000066400000000000000000002241231241061774000147550ustar00rootroot00000000000000Ansible Changes By Release ========================== ## 1.8 "You Really Got Me" - Active Development ## 1.7.2 "Summer Nights" - Sep 24, 2014 - Fixes a bug in accelerate mode which caused a traceback when trying to use that connection method. - Fixes a bug in vault where the password file option was not being used correctly internally. - Improved multi-line parsing when using YAML literal blocks (using > or |). - Fixed a bug with the file module and the creation of relative symlinks. - Fixed a bug where checkmode was not being honored during the templating of files. - Other various bug fixes. ## 1.7.1 "Summer Nights" - Aug 14, 2014 - Security fix to disallow specifying 'args:' as a string, which could allow the insertion of extra module parameters through variables. - Performance enhancements related to previous security fixes, which could cause slowness when modules returned very large JSON results. This specifically impacted the unarchive module frequently, which returns the details of all unarchived files in the result. - Docker module bug fixes: * Fixed support for specifying rw/ro bind modes for volumes * Fixed support for allowing the tag in the image parameter - Various other bug fixes ## 1.7 "Summer Nights" - Aug 06, 2014 Major new features: * Windows support (alpha) using native PowerShell remoting * Tasks can now specify `run_once: true`, meaning they will be executed exactly once. This can be combined with delegate_to to trigger actions you want done just the one time versus for every host in inventory. New inventory scripts: * SoftLayer * Windows Azure New Modules: * cloud: azure * cloud: rax_meta * cloud: rax_scaling_group * cloud: rax_scaling_policy * windows: version of setup module * windows: version of slurp module * windows: win_feature * windows: win_get_url * windows: win_msi * windows: win_ping * windows: win_user * windows: win_service * windows: win_group Other notable changes: * Inventory speed improvements for very large inventories. * Vault password files can now be executable, to support scripts that fetch the vault password. ## 1.6.10 "And the Cradle Will Rock" - Jul 25, 2014 - Fixes an issue with the copy module when copying a directory that fails when changing file attributes and the target file already exists - Improved unicode handling when splitting args ## 1.6.9 "And the Cradle Will Rock" - Jul 24, 2014 - Further improvements to module parameter parsing to address additional regressions caused by security fixes ## 1.6.8 "And the Cradle Will Rock" - Jul 22, 2014 - Corrects a regression in the way shell and command parameters were being parsed ## 1.6.7 "And the Cradle Will Rock" - Jul 21, 2014 - Security fixes: * Strip lookup calls out of inventory variables and clean unsafe data returned from lookup plugins (CVE-2014-4966) * Make sure vars don't insert extra parameters into module args and prevent duplicate params from superseding previous params (CVE-2014-4967) ## 1.6.6 "And the Cradle Will Rock" - Jul 01, 2014 - Security updates to further protect against the incorrect execution of untrusted data ## 1.6.4, 1.6.5 "And the Cradle Will Rock" - Jun 25, 2014 - Security updates related to evaluation of untrusted remote inputs ## 1.6.3 "And the Cradle Will Rock" - Jun 09, 2014 - Corrects a regression where handlers were run across all hosts, not just those that triggered the handler. - Fixed a bug in which modules did not support properly moving a file atomically when su was in use. - Fixed two bugs related to symlinks with directories when using the file module. - Fixed a bug related to MySQL master replication syntax. - Corrects a regression in the order of variable merging done by the internal runner code. - Various other minor bug fixes. ## 1.6.2 "And the Cradle Will Rock" - May 23, 2014 - If an improper locale is specified, core modules will now automatically revert to using the 'C' locale. - Modules using the fetch_url utility will now obey proxy environment variables. - The SSL validation step in fetch_url will likewise obey proxy settings, however only proxies using the http protocol are supported. - Fixed multiple bugs in docker module related to version changes upstream. - Fixed a bug in the ec2_group module where egress rules were lost when a VPC was specified. - Fixed two bugs in the synchronize module: * a trailing slash might be lost when calculating relative paths, resulting in an incorrect destination. * the sync might use the inventory directory incorrectly instead of the playbook or role directory. - Files will now only be chown'd on an atomic move if the src/dest uid/gid do not match. ## 1.6.1 "And the Cradle Will Rock" - May 7, 2014 - Fixed a bug in group_by, where systems were being grouped incorrectly. - Fixed a bug where file descriptors may leak to a child process when using accelerate. - Fixed a bug in apt_repository triggered when python-apt not being installed/available. - Fixed a bug in the apache2_module module, where modules were not being disabled correctly. ## 1.6 "And the Cradle Will Rock" - May 5, 2014 Major features/changes: * The deprecated legacy variable templating system has been finally removed. Use {{ foo }} always not $foo or ${foo}. * Any data file can also be JSON. Use sparingly -- with great power comes great responsibility. Starting file with "{" or "[" denotes JSON. * Added 'gathering' param for ansible.cfg to change the default gather_facts policy. * Accelerate improvements: - multiple users can connect with different keys, when `accelerate_multi_key = yes` is specified in the ansible.cfg. - daemon lifetime is now based on the time from the last activity, not the time from the daemon's launch. * ansible-playbook now accepts --force-handlers to run handlers even if tasks result in failures. * Added VMWare support with the vsphere_guest module. New Modules: * files: replace * packaging: cpanm (Perl) * packaging: portage * packaging: composer (PHP) * packaging: homebrew_tap (OS X) * packaging: homebrew_cask (OS X) * packaging: apt_rpm * packaging: layman * monitoring: logentries * monitoring: rollbar_deployment * monitoring: librato_annotation * notification: nexmo (SMS) * notification: twilio (SMS) * notification: slack (Slack.com) * notification: typetalk (Typetalk.in) * notification: sns (Amazon) * system: debconf * system: ufw * system: locale_gen * system: alternatives * system: capabilities * net_infrastructure: bigip_facts * net_infrastructure: dnssimple * net_infrastructure: lldp * web_infrastructure: apache2_module * cloud: digital_ocean_domain * cloud: digital_ocean_sshkey * cloud: rax_identity * cloud: rax_cbs (cloud block storage) * cloud: rax_cbs_attachments * cloud: ec2_asg (configure autoscaling groups) * cloud: ec2_scaling_policy * cloud: ec2_metric_alarm * cloud: vsphere_guest Other notable changes: * example callback plugin added for hipchat * added example inventory plugin for vcenter/vsphere * added example inventory plugin for doing really trivial inventory from SSH config files * libvirt module now supports destroyed and paused as states * s3 module can specify metadata * security token additions to ec2 modules * setup module code moved into module_utils/, facts now accessible by other modules * synchronize module sets relative dirs based on inventory or role path * misc bugfixes and other parameters * the ec2_key module now has wait/wait_timeout parameters * added version_compare filter (see docs) * added ability for module documentation YAML to utilize shared module snippets for common args * apt module now accepts "deb" parameter to install local dpkg files * regex_replace filter plugin added * added an inventory script for Docker * added an inventory script for Abiquo * the get_url module now accepts url_username and url_password as parameters, so sites which require authentication no longer need to have them embedded in the url * ... to be filled in from changelogs ... * ## 1.5.5 "Love Walks In" - April 18, 2014 - Security fix for vault, to ensure the umask is set to a restrictive mode before creating/editing vault files. - Backported apt_repository security fixes relating to filename/mode upon sources list file creation. ## 1.5.4 "Love Walks In" - April 1, 2014 - Security fix for safe_eval, which further hardens the checking of the evaluation function. - Changing order of variable precendence for system facts, to ensure that inventory variables take precedence over any facts that may be set on a host. ## 1.5.3 "Love Walks In" - March 13, 2014 - Fix validate_certs and run_command errors from previous release - Fixes to the git module related to host key checking ## 1.5.2 "Love Walks In" - March 11, 2014 - Fix module errors in airbrake and apt from previous release ## 1.5.1 "Love Walks In" - March 10, 2014 - Force command action to not be executed by the shell unless specifically enabled. - Validate SSL certs accessed through urllib*. - Implement new default cipher class AES256 in ansible-vault. - Misc bug fixes. ## 1.5 "Love Walks In" - February 28, 2014 Major features/changes: * when_foo which was previously deprecated is now removed, use "when:" instead. Code generates appropriate error suggestion. * include + with_items which was previously deprecated is now removed, ditto. Use with_nested / with_together, etc. * only_if, which is much older than when_foo and was deprecated, is similarly removed. * ssh connection plugin is now more efficient if you add 'pipelining=True' in ansible.cfg under [ssh_connection], see example.cfg * localhost/127.0.0.1 is not required to be in inventory if referenced, if not in inventory, it does not implicitly appear in the 'all' group. * git module has new parameters (accept_hostkey, key_file, ssh_opts) to ease the usage of git and ssh protocols. * when using accelerate mode, the daemon will now be restarted when specifying a different remote_user between plays. * added no_log: option for tasks. When used, no logging information will be sent to syslog during the module execution. * acl module now handles 'default' and allows for either shorthand entry or specific fields per entry section * play_hosts is a new magic variable to provide a list of hosts in scope for the current play. * ec2 module now accepts 'exact_count' and 'count_tag' as a way to enforce a running number of nodes by tags. * all ec2 modules that work with Eucalyptus also now support a 'validate_certs' option, which can be set to 'off' for installations using self-signed certs. * Start of new integration test infrastructure (WIP, more details TBD) * if repoquery is unavailble, the yum module will automatically attempt to install yum-utils * ansible-vault: a framework for encrypting your playbooks and variable files * added support for privilege escalation via 'su' into bin/ansible and bin/ansible-playbook and associated keywords 'su', 'su_user', 'su_pass' for tasks/plays New modules: * cloud: ec2_elb_lb * cloud: ec2_key * cloud: ec2_snapshot * cloud: rax_dns * cloud: rax_dns_record * cloud: rax_files * cloud: rax_files_objects * cloud: rax_keypair * cloud: rax_queue * cloud: docker_image * messaging: rabbitmq_policy * system: at * utilities: assert Other notable changes (many new module params & bugfixes may not not listed): * no_reboot is now defaulted to "no" in the ec2_ami module to ensure filesystem consistency in the resulting AMI. * sysctl module overhauled * authorized_key module overhauled * synchronized module now handles local transport better * apt_key module now ignores case on keys * zypper_repository now skips on check mode * file module now responds to force behavior when dealing with hardlinks * new lookup plugin 'csvfile' * fixes to allow hash_merge behavior to work with dynamic inventory * mysql module will use port argument on dump/import * subversion module now ignores locale to better intercept status messages * rax api_key argument is no longer logged * backwards/forwards compatibility for OpenStack modules, 'quantum' modules grok neutron renaming * hosts properly uniqueified if appearing in redundant groups * hostname module support added for ScientificLinux * ansible-pull can now show live stdout and pass verbosity levels to ansible-playbook * ec2 instances can now be stopped or started * additional volumes can be created when creating new ec2 instances * user module can move a home directory * significant enhancement and cleanup of rackspace modules * ansible_ssh_private_key_file can be templated * docker module updated to support docker-py 0.3.0 * various other bug fixes * md5 logic improved during sudo operation * support for ed25519 keys in authorized_key module * ability to set directory permissions during a recursive copy (directory_mode parameter) ## 1.4.5 "Could This Be Magic" - February 12, 2014 - fixed issue with permissions being incorrect on fireball/accelerate keys when the umask setting was too loose. ## 1.4.4 "Could This Be Magic" - January 6, 2014 - fixed a minor issue with newer versions of pip dropping the "use-mirrors" parameter. ## 1.4.3 "Could This Be Magic" - December 20, 2013 - Fixed role_path parsing from ansible.cfg - Fixed default role templates ## 1.4.2 "Could This Be Magic" - December 18, 2013 * Fixed a few bugs related to unicode * Fixed errors in the ssh connection method with large data returns * Miscellaneous fixes for a few modules * Add the ansible-galaxy command ## 1.4.1 "Could This Be Magic" - November 27, 2013 * Misc fixes to accelerate mode and various modules. ## 1.4 "Could This Be Magic" - November 21, 2013 Highlighted new features: * Added do-until feature, which can be used to retry a failed task a specified number of times with a delay in-between the retries. * Added failed_when option for tasks, which can be used to specify logical statements that make it easier to determine when a task has failed, or to make it easier to ignore certain non-zero return codes for some commands. * Added the "subelement" lookup plugin, which allows iteration of the keys of a dictionary or items in a list. * Added the capability to use either paramiko or ssh for the inital setup connection of an accelerated playbook. * Automatically provide advice on common parser errors users encounter. * Deprecation warnings are now shown for legacy features: when_integer/etc, only_if, include+with_items, etc. Can be disabled in ansible.cfg * The system will now provide helpful tips around possible YAML syntax errors increasing ease of use for new users. * warnings are now shown for using {{ foo }} in loops and conditionals, and suggest leaving the variable expressions bare as per docs. * The roles search path is now configurable in ansible.cfg. 'roles_path' in the config setting. * Includes with parameters can now be done like roles for consistency: - { include: song.yml, year:1984, song:'jump' } * The name of each role is now shown before each task if roles are being used * Adds a "var=" option to the debug module for debugging variable data. "debug: var=hostvars['hostname']" and "debug: var=foo" are all valid syntax. * Variables in {{ format }} can be used as references even if they are structured data * Can force binding of accelerate to ipv6 ports. * the apt module will auto-install python-apt if not present rather than requiring a manual installation * the copy module is now recursive if the local 'src' parameter is a directory. * syntax checks now scan included task and variable files as well as main files New modules and plugins. * cloud: ec2_eip -- manage AWS elastic IPs * cloud: ec2_vpc -- manage ec2 virtual private clouds * cloud: elasticcache -- Manages clusters in Amazon Elasticache * cloud: rax_network -- sets up Rackspace networks * cloud: rax_facts: retrieve facts about a Rackspace Cloud Server * cloud: rax_clb_nodes -- manage Rackspace cloud load balanced nodes * cloud: rax_clb -- manages Rackspace cloud load balancers * cloud: docker - instantiates/removes/manages docker containers * cloud: ovirt -- VM lifecycle controls for ovirt * files: acl -- set or get acls on a file * files: unarchive: pushes and extracts tarballs * files: synchronize: a useful wraper around rsyncing trees of files * system: firewalld -- manage the firewalld configuration * system: modprobe -- manage kernel modules on systems that support modprobe/rmmod * system: open_iscsi -- manage targets on an initiator using open-iscsi * system: blacklist: add or remove modules from the kernel blacklist * system: hostname - sets the systems hostname * utilities: include_vars -- dynamically load variables based on conditions. * packaging: zypper_repository - adds or removes Zypper repositories * packaging: urpmi - work with urpmi packages * packaging: swdepot - a module for working with swdepot * notification: grove - notifies to Grove hosted IRC channels * web_infrastructure: ejabberd_user: add and remove users to ejabberd * web_infrastructure: jboss: deploys or undeploys apps to jboss * source_control: github_hooks: manages GitHub service hooks * net_infrastructure: bigip_monitor_http: manages F5 BIG-IP LTM http monitors * net_infrastructure: bigip_monitor_tcp: manages F5 BIG-IP LTM TCP monitors * net_infrastructure: bigip_pool_member: manages F5 BIG-IP LTM pool members * net_infrastructure: bigip_node: manages F5 BIG-IP LTM nodes * net_infrastructure: openvswitch_port * net_infrastructure: openvswitch_bridge Plugins: * jail connection module (FreeBSD) * lxc connection module * added inventory script for listing FreeBSD jails * added md5 as a Jinja2 filter: {{ path | md5 }} * added a fileglob filter that will return files matching a glob pattern. with_items: "/foo/pattern/*.txt | fileglob" * 'changed' filter returns whether a previous step was changed easier. when: registered_result | changed * DOCS NEEDED: 'unique' and 'intersect' filters are added for dealing with lists. * DOCS NEEDED: new lookup plugin added for etcd * a 'func' connection type to help people migrating from func/certmaster. Misc changes (all module additions/fixes may not listed): * (docs pending) New features for accelerate mode: configurable timeouts and a keepalives for long running tasks. * Added a `delimiter` field to the assemble module. * Added `ansible_env` to the list of facts returned by the setup module. * Added `state=touch` to the file module, which functions similarly to the command-line version of `touch`. * Added a -vvvv level, which will show SSH client debugging information in the event of a failure. * Includes now support the more standard syntax, similar to that of role includes and dependencies. * Changed the `user:` parameter on plays to `remote_user:` to prevent confusion with the module of the same name. Still backwards compatible on play parameters. * Added parameter to allow the fetch module to skip the md5 validation step ('validate_md5=false'). This is usefull when fetching files that are actively being written to, such as live log files. * Inventory hosts are used in the order they appear in the inventory. * in hosts: foo[2-5] type syntax, the iterators now are zero indexed and the last index is non-inclusive, to match Python standards. * There is now a way for a callback plugin to disable itself. See osx_say example code for an example. * Many bugfixes to modules of all types. * Complex arguments now can be used with async tasks * SSH ControlPath is now configurable in ansible.cfg. There is a limit to the lengths of these paths, see how to shorten them in ansible.cfg. * md5sum support on AIX with csum. * Extremely large documentation refactor into subchapters * Added 'append_privs' option to the mysql_user module * Can now update (temporarily change) host variables using the "add_host" module for existing hosts. * Fixes for IPv6 addresses in inventory text files * name of executable can be passed to pip/gem etc, for installing under *different* interpreters * copy of ./hacking/env-setup added for fish users, ./hacking/env-setup.fish * file module more tolerant of non-absolute paths in softlinks. * miscellaneous fixes/upgrades to async polling logic. * conditions on roles now pass to dependent roles * ansible_sudo_pass can be set in a host variable if desired * misc fixes for the pip an easy_install modules * support for running handlers that have parameterized names based on role parameters * added support for compressing MySQL dumps and extracting during import * Boto version compatibility fixes for the EC2 inventory script * in the EC2 inventory script, a group 'EC2' and 'RDS' contains EC2 and RDS hosts. * umask is enforced by the cron module * apt packages that are not-removed and not-upgraded do not count as changes * the assemble module can now use src files from the local server and copy them over dynamically * authorization code has been standardized between Amazon cloud modules * the wait_for module can now also wait for files to exist or a regex string to exist in a file * leading ranges are now allowed in ranged hostname patterns, ex: [000-250].example.com * pager support added to ansible-doc (so it will auto-invoke less, etc) * misc fixes to the cron module * get_url module now understands content-disposition headers for deciding filenames * it is possible to have subdirectories in between group_vars/ and host_vars/ and the final filename, like host_vars/rack42/asdf for the variables for host 'asdf'. The intermediate directories are ignored, and do not put a file in there twice. ## 1.3.4 "Top of the World" (reprise) - October 29, 2013 * Fixed a bug in the copy module, where a filename containing the string "raw" was handled incorrectly * Fixed a bug in accelerate mode, where copying a zero-length file out would fail ## 1.3.3 "Top of the World" (reprise) - October 9, 2013 Additional fixes for accelerate mode. ## 1.3.2 "Top of the World" (reprise) - September 19th, 2013 Multiple accelerate mode fixes: * Make packet reception less greedy, so multiple frames of data are not consumed by one call. * Adding two timeout values (one for connection and one for data reception timeout). * Added keepalive packets, so async mode is no longer required for long-running tasks. * Modified accelerate daemon to use the verbose logging level of the ansible command that started it. * Fixed bug where accelerate would not work in check-mode. * Added a -vvvv level, which will show SSH client debugging information in the event of a failure. * Fixed bug in apt_repository module where the repository cache was not being updated. * Fixed bug where "too many open files" errors would be encountered due to pseudo TTY's not being closed properly. ## 1.3.1 "Top of the World" (reprise) - September 16th, 2013 Fixing a bug in accelerate mode whereby the gather_facts step would always be run via sudo regardless of the play settings. ## 1.3 "Top of the World" - September 13th, 2013 Highlighted new features: * accelerated mode: An enhanced fireball mode that requires zero bootstrapping and fewer requirements plus adds capabilities like sudo commands. * role defaults: Allows roles to define a set of variables at the lowest priority. These variables can be overridden by any other variable. * new /etc/ansible/facts.d allows JSON or INI-style facts to be provided from the remote node, and supports executable fact programs in this dir. Files must end in *.fact. * added the ability to make undefined template variables raise errors (see ansible.cfg) * (DOCS PENDING) sudo: True/False and sudo_user: True/False can be set at include and role level * added changed_when: (expression) which allows overriding whether a result is changed or not and can work with registered expressions * --extra-vars can now take a file as input, e.g., "-e @filename" and can also be formatted as YAML * external inventory scripts may now return host variables in one pass, which allows them to be much more efficient for large numbers of hosts * if --forks exceeds the numbers of hosts, it will be automatically reduced. Set forks to 0 and you get "as many forks as I have hosts" out of the box. * enabled error_on_undefined_vars by default, which will make errors in playbooks more obvious * role dependencies -- one role can now pull in another, with parameters of its own. * added the ability to have tasks execute even during a check run (always_run). * added the ability to set the maximum failure percentage for a group of hosts. New modules: * notifications: datadog_event -- send data to datadog * cloud: digital_ocean -- module for DigitalOcean provisioning that also includes inventory support * cloud: rds -- Amazon Relational Database Service * cloud: linode -- modules for Linode provisioning that also includes inventory support * cloud: route53 -- manage Amazon DNS entries * cloud: ec2_ami -- manages (and creates!) ec2 AMIs * database: mysql_replication -- manages mysql replication settings for masters/slaves * database: mysql_variables -- manages mysql runtime variables * database: redis -- manages redis databases (slave mode and flushing data) * net_infrastructure: arista_interface * net_infrastructure: arista_lag * net_infrastructure: arista_l2interface * net_infrastructure: arista_vlan * system: stat -- reports on stat(istics) of remote files, for use with 'register' * web_infrastructure: htpasswd -- manipulate htpasswd files * packaging: rpm_key -- adds or removes RPM signing keys * packaging: apt_repository -- rewritten to remove dependencies * monitoring: boundary_meter -- adds or removes boundary.com meters * net_infrastructure: dnsmadeeasy - manipulate DNS Made Easy records * files: xattr -- manages extended attributes on files Misc changes: * return 3 when there are hosts that were unreachable during a run * the yum module now supports wildcard values for the enablerepo argument * added an inventory script to pull host information from Zabbix * async mode no longer allows with_* lookup plugins due to incompatibilities * Added OpenRC support (Gentoo) to the service module * ansible_ssh_user value is available to templates * added placement_group parameter to ec2 module * new sha256sum parameter added to get_url module for checksum validation * search for mount binaries in system path and sbin vs assuming path * allowed inventory file to be read from a pipe * added Solaris distribution facts * fixed bug along error path in quantum_network module * user password update mode is controllable in user module now (at creation vs. every time) * added check mode support to the OpenBSD package module * Fix for MySQL 5.6 compatibility * HP UX virtualization facts * fixed some executable bits in git * made rhn_register module compatible with EL5 * fix for setup module epoch time on Solaris * sudo_user is now expanded later, allowing it to be set at inventory scope * mongodb_user module changed to also support MongoDB 2.2 * new state=hard option added to the file module for hardlinks vs softlinks * fixes to apt module purging option behavior * fixes for device facts with multiple PCI domains * added "with_inventory_hostnames" lookup plugin, which can take a pattern and loop over hostnames matching the pattern and is great for use with delegate_to and so on * ec2 module supports adding to multiple security groups * cloudformation module includes fixes for the error path, and the 'wait_for' parameter was removed * added --only-if-changed to ansible-pull, which runs only if the repo has changes (not default) * added 'mandatory', a Jinja2 filter that checks if a variable is defined: {{ foo|mandatory }} * added support for multiple size formats to the lvol module * timing reporting on wait_for module now includes the delay time * IRC module can now send a server password * "~" now expanded on each component of configured plugin paths * fix for easy_install module when dealing with virtualenv * rackspace module now explicitly indicates rackspace vs vanilla openstack * add_host module does not report changed=True any longer * explanatory error message when using fireball with sudo has been improved * git module now automatically pulls down git submodules * negated patterns do not require "all:!foo", you can just say "!foo" now to select all not foos * fix for Debian services always reporting changed when toggling enablement bit * roles files now tolerate files named 'main.yaml' and 'main' in addition to main.yml * some help cleanup to command line flags on scripts * force option reinstated for file module so it can create symlinks to non-existent files, etc. * added termination support to ec2 module * --ask-sudo-pass or --sudo-user does not enable all options to use sudo in ansible-playbook * include/role conditionals are added ahead of task conditionals so they can short circuit properly * added pipes.quote in various places so paths with spaces are better tolerated * error handling while executing Jinja2 filters has been improved * upgrades to atomic replacement logic when copying files across partitions/etc * mysql user module can try to login before requiring explicit password * various additional options added to supervisorctl module * only add non unique parameter on group creation when required * allow rabbitmq_plugin to specify a non-standard RabbitMQ path * authentication fixes to keystone_user module * added IAM role support to EC2 module * fixes for OpenBSD package module to avoid shell expansion * git module upgrades to allow --depth and --version to be used together * new lookup plugin, "with_flattened" * extra vars (-e) variables can be used in playbook include paths * improved reporting for invalid sudo passwords * improved reporting for inability to find a suitable tmp location * require libselinux-python to perform file operations if SELinux is operational * ZFS module fixes for byte display constants and handling paths with spaces * setup module more tolerant of gathering facts against things it does not have permission to read * can specify name=* state=latest to update all yum modules * major speedups to the yum module for default cases * ec2_facts module will now run in check mode * sleep option on service module for sleeping between stop/restart * fix for IPv6 facts on BSD * added Jinja2 filters: skipped, whether a result was skipped * added Jinja2 filters: quote, quotes a string if it needs to be quoted * allow force=yes to affect apt upgrades * fix for saving conditionals in variable names * support for multiple host ranges in INI inventory, e.g., db[01:10:3]node-[01:10] * fixes/improvements to cron module * add user_install=no option to gem module to install gems system wide * added raw=yes to allow copying without python on remote machines * added with_indexed_items lookup plugin * Linode inventory plugin now significantly faster * added recurse=yes parameter to pacman module for package removal * apt_key module can now target specific keyrings (keyring=filename) * ec2 module change reporting improved * hg module now expands user paths (~) * SSH connection type known host checking now can process hashed known_host files * lvg module now checks for executables in more correct locations * copy module now works correctly with sudo_user * region parameter added to ec2_elb module * better default XMPP module message types * fixed conditional tests against raw booleans * mysql module grant removal is now smarter * apt-remove is now forced to be non-interactive * support ; comments in INI file module * fixes to callbacks WRT async output (fire and forget tasks now trigger callbacks!) * folder support for s3 module * added new example inventory plugin for Red Hat OpenShift * and other misc. bugfixes ## 1.2.3 "Hear About It Later" (reprise) -- Aug 21, 2013 * Local security fixes for predictable file locations for ControlPersist and retry file paths on shared machines on operating systems without kernel symlink/hardlink protections. ## 1.2.2 "Hear About It Later" (reprise) -- July 4, 2013 * Added a configuration file option [paramiko_connection] record_host_keys which allows the code that paramiko uses to update known_hosts to be disabled. This is done because paramiko can be very slow at doing this if you have a large number of hosts and some folks may not want this behavior. This can be toggled independently of host key checking and does not affect the ssh transport plugin. Use of the ssh transport plugin is preferred if you have ControlPersist capability, and Ansible by default in 1.2.1 and later will autodetect. ## 1.2.1 "Hear About It Later" -- July 4, 2013 * Connection default is now "smart", which discovers if the system openssh can support ControlPersist, and uses it if so, if not falls back to paramiko. * Host key checking is on by default. Disable it if you like by adding host_key_checking=False in the [default] section of /etc/ansible/ansible.cfg or ~/ansible.cfg or by exporting ANSIBLE_HOST_KEY_CHECKING=False * Paramiko now records host keys it was in contact with host key checking is on. It is somewhat sluggish when doing this, so switch to the 'ssh' transport if this concerns you. ## 1.2 "Right Now" -- June 10, 2013 Core Features: * capability to set 'all_errors_fatal: True' in a playbook to force any error to stop execution versus a whole group or serial block needing to fail usable, without breaking the ability to override in ansible * ability to use variables from {{ }} syntax in mainline playbooks, new 'when' conditional, as detailed in documentation. Can disable old style replacements in ansible.cfg if so desired, but are still active by default. * can set ansible_ssh_private_key_file as an inventory variable (similar to ansible_ssh_host, etc) * 'when' statement can be affixed to task includes to auto-affix the conditional to each task therein * cosmetic: "*****" banners in ansible-playbook output are now constant width * --limit can now be given a filename (--limit @filename) to constrain a run to a host list on disk * failed playbook runs will create a retry file in /var/tmp/ansible usable with --limit * roles allow easy arrangement of reusable tasks/handlers/files/templates * pre_tasks and post_tasks allow for separating tasks into blocks where handlers will fire around them automatically * "meta: flush_handler" task capability added for when you really need to force handlers to run * new --start-at-task option to ansible playbook allows starting at a specific task name in a long playbook * added a log file for ansible/ansible-playbook, set 'log_path' in the configuration file or ANSIBLE_LOG_PATH in environment * debug mode always outputs debug in playbooks, without needing to specify -v * external inventory script added for Spacewalk / Red Hat Satellite servers * It is now possible to feed JSON structures to --extra-vars. Pass in a JSON dictionary/hash to feed in complex data. * group_vars/ and host_vars/ directories can now be kept alongside the playbook as well as inventory (or both!) * more filters: ability to say {{ foo|success }} and {{ foo|failed }} and when: foo|success and when: foo|failed * more filters: {{ path|basename }} and {{ path|dirname }} * lookup plugins now use the basedir of the file they have included from, avoiding needs of ../../../ in places and increasing the ease at which things can be reorganized. Modules added: * cloud: rax: module for creating instances in the rackspace cloud (uses pyrax) * packages: npm: node.js package management * packages: pkgng: next-gen package manager for FreeBSD * packages: redhat_subscription: manage Red Hat subscription usage * packages: rhn_register: basic RHN registration * packages: zypper (SuSE) * database: postgresql_priv: manages postgresql priveledges * networking: bigip_pool: load balancing with F5s * networking: ec2_elb: add and remove machines from ec2 elastic load balancers * notification: hipchat: send notification events to hipchat * notification: flowdock: send messages to flowdock during playbook runs * notification: campfire: send messages to campfire during playbook runs * notification: mqtt: send messages to the Mosquitto message bus * notification: irc: send messages to IRC channels * notification: filesystem - a wrapper around mkfs * notification: jabber: send jabber chat messages * notification: osx_say: make OS X say things out loud * openstack: keystone_user * openstack: glance_image * openstack: nova_compute * openstack: nova_keypair * openstack: quantum_floating_ip * openstack: quantum_floating_ip_associate * openstack: quantum_network * openstack: quantum_router * openstack: quantum_router_gateway * openstack: quantum_router_interface * openstack: quantum_subnet * monitoring: newrelic_deployment: notifies newrelic of new deployments * monitoring: airbrake_deployment - notify airbrake of new deployments * monitoring: pingdom * monitoring: pagerduty * monitoring: monit * utility: set_fact: sets a variable, which can be the result of a template evaluation Modules removed * vagrant -- can't be compatible with both versions at once, just run things though the vagrant provisioner in vagrant core Bugfixes and Misc Changes: * service module happier if only enabled=yes|no specified and no state * mysql_db: use --password= instead of -p in dump/import so it doesn't go interactive if no pass set * when using -c ssh and the ansible user is the current user, don't pass a -o to allow SSH config to be * overwrite parameter added to the s3 module * private_ip parameter added to the ec2 module * $FILE and $PIPE now tolerate unicode * various plugin loading operations have been made more efficient * hostname now uses platform.node versus socket.gethostname to be more consistant with Unix 'hostname' * fix for SELinux operations on Unicode path names * inventory directory locations now ignore files with .ini extensions, making hybrid inventory easier * copy module in check-mode now reports back correct changed status when used with force=no * added avail. zone to ec2 module * fixes to the hash variable merging logic if so enabled in the main settings file (default is to replace, not merge hashes) * group_vars and host_vars files can now end in a .yaml or .yml extension, (previously required no extension, still favored) * ec2vol module improvements * if the user module is told to generate the ssh key, the key generated is now returned in the results * misc fixes to the Riak module * make template module slightly more efficient * base64encode / decode filters are now available to templates * libvirt module can now work with multiple different libvirt connecton URIs * fix for postgresql password escaping * unicode fix for shlex.split in some cases * apt module upgrade logic improved * URI module now can follow redirects * yum module can now install off http URLs * sudo password now defaults to ssh password if you ask for both and just hit enter on the second prompt * validate feature on copy and template module, for example, running visudo prior to copying the file over * network facts upgraded to return advanced configs (bonding, etc) * region support added to ec2 module * riak module gets a wait for ring option * improved check mode support in the file module * exception handling added to handle scenario when attempt to log to systemd journal fails * fix for upstart handling when toggling the enablement and running bits at the same time * when registering a task with a conditional attached, and the task is skipped by the conditional, the variable is still registered for the host, with the attribute skipped: True. * delegate_to tasks can look up ansible_ssh_private_key_file variable from inventory correctly now * s3 module takes a 'dest' parameter to change the destination for uploads * apt module gets a cache_valid_time option to avoid redundant cache updates * ec2 module better understands security groups * fix for postgresql codec usage * setup module now tolerant of OpenVZ interfaces * check mode reporting improved for files and directories * doc system now reports on module requirements * group_by module can now also make use of globally scoped variables * localhost and 127.0.0.1 are now fuzzy matched in inventory (are now more or less interchangeable) * AIX improvements/fixes for users, groups, facts * lineinfile now does atomic file replacements * fix to not pass PasswordAuthentication=no in the config file unneccessarily for SSH connection type * for for authorized_key on Debian Squeeze * fixes for apt_repository module reporting changed incorrectly on certain repository types * allow the virtualenv argument to the pip module to be a pathname * service pattern argument now correctly read for BSD services * fetch location can now be controlled more directly via the 'flat' parameter. * added basename and dirname as Jinja2 filters available to all templates * pip works better when sudoing from unpriveledged users * fix for user creation with groups specification reporting 'changed' incorrectly in some cases * fix for some unicode encoding errors in outputing some data in verbose mode * improved FreeBSD, NetBSD and Solaris facts * debug module always outputs data without having to specify -v * fix for sysctl module creating new keys (must specify checks=none) * NetBSD and OpenBSD support for the user and groups modules * Add encrypted password support to password lookup ## 1.1 "Mean Street" -- 4/2/2013 Core Features * added --check option for "dry run" mode * added --diff option to show how templates or copied files change, or might change * --list-tasks for the playbook will list the tasks without running them * able to set the environment by setting "environment:" as a dictionary on any task (go proxy support!) * added ansible_ssh_user and ansible_ssh_pass for per-host/group username and password * jinja2 extensions can now be loaded from the config file * support for complex arguments to modules (within reason) * can specify ansible_connection=X to define the connection type in inventory variables * a new chroot connection type * module common code now has basic type checking (and casting) capability * module common now supports a 'no_log' attribute to mark a field as not to be syslogged * inventory can now point to a directory containing multiple scripts/hosts files, if using this, put group_vars/host_vars directories inside this directory * added configurable crypt scheme for 'vars_prompt' * password generating lookup plugin -- $PASSWORD(path/to/save/data/in) * added --step option to ansible-playbook, works just like Linux interactive startup! Modules Added: * bzr (bazaar version control) * cloudformation * django-manage * gem (ruby gems) * homebrew * lvg (logical volume groups) * lvol (LVM logical volumes) * macports * mongodb_user * netscaler * okg * openbsd_pkg * rabbit_mq_plugin * rabbit_mq_user * rabbit_mq_vhost * rabbit_mq_parameter * rhn_channel * s3 -- allows putting file contents in buckets for sharing over s3 * uri module -- can get/put/post/etc * vagrant -- launching VMs with vagrant, this is different from existing vagrant plugin * zfs Bugfixes and Misc Changes: * stderr shown when commands fail to parse * uses yaml.safe_dump in filter plugins * authentication Q&A no longer happens before --syntax-check, but after * ability to get hostvars data for nodes not in the setup cache yet * SSH timeout now correctly passed to native SSH connection plugin * raise an error when multiple when_ statements are provided * --list-hosts applies host limit selections better * (internals) template engine specifications to use template_ds everywhere * better error message when your host file can not be found * end of line comments now work in the inventory file * directory destinations now work better with remote md5 code * lookup plugin macros like $FILE and $ENV now work without returning arrays in variable definitions/playbooks * uses yaml.safe_load everywhere * able to add EXAMPLES to documentation via EXAMPLES docstring, rather than just in main documentation YAML * can set ANSIBLE_COW_SELECTION to pick other cowsay types (including random) * to_nice_yaml and to_nice_json available as Jinja2 filters that indent and sort * cowsay able to run out of macports (very important!) * improved logging for fireball mode * nicer error message when talking to an older system that needs a JSON module installed * 'magic' variable 'inventory_dir' now gives path to inventory file * 'magic' variable 'vars' works like 'hostvars' but gives global scope variables, useful for debugging in templates mostly * conditionals can be used on plugins like add_host * developers: all callbacks now have access to a ".runner" and ".playbook", ".play", and ".task" object (use getattr, they may not always be set!) Facts: * block device facts for the setup module * facts for AIX * fact detection for OS type on Amazon Linux * device fact gathering stability improvements * ansible_os_family fact added * user_id (remote user name) * a whole series of current time information under the 'datetime' hash * more OS X facts * support for detecting Alpine Linux * added facts for OpenBSD Module Changes/Fixes: * ansible module common code (and ONLY that) which is mixed in with modules, is now BSD licensed. App remains GPLv3. * service code works better on platforms that mix upstart, systemd, and system-v * service enablement idempotence fixes for systemd and upstart * service status 4 is also 'not running' * supervisorctl restart fix * increased error handling for ec2 module * can recursively set permissions on directories * ec2: change to the way AMI tags are handled * cron module can now also manipulate cron.d files * virtualenv module can now inherit system site packages (or not) * lineinfile module now has an insertbefore option * NetBSD service module support * fixes to sysctl module where item has multiple values * AIX support for the user and group modules * able to specify a different hg repo to pull from than the original set * add_host module can set ports and other inventory variables * add_host module can add modules to multiple groups (groups=a,b,c), groups now alias for groupname * subnet ID can be set on EC2 module * MySQL module password handling improvements * added new virtualenv flags to pip and easy_install modules * various improvements to lineinfile module, now accepts common arguments from file * force= now replaces thirsty where used before, thirsty remains an alias * setup module can take a 'filter=' parameter to just return a few facts (not used by playbooks) * cron module works even if no crontab is present (for cron.d) * security group ID settable on EC2 module * misc fixes to sysctl module * fix to apt module so packages not in cache are still removable * charset fix to mail module * postresql db module now does not try to create the 'PUBLIC' user * SVN module now works correctly with self signed certs * apt module now has an upgrade parameter (values=yes, no, or 'dist') * nagios module gets new silence/unsilence commands * ability to disable proxy usage in get_url (use_proxy=no) * more OS X facts * added a 'fail_on_missing' (default no) option to fetch * added timeout to the uri module (default 30 seconds, adjustable) * ec2 now has a 'wait' parameter to wait for the instance to be active, eliminates need for separate wait_for call. * allow regex backreferences in lineinfile * id attribute on ec2 module can be used to set idempotent-do-not-recreate launches * icinga support for nagios module * fix default logins when no my.conf for MySQL module * option to create users with non-unique UIDs (user module) * macports module can enable/disable packages * quotes in my.cnf are stripped by the MySQL modules * Solaris Service management added * service module will attempt to auto-add unmanaged chkconfig services when needed * service module supports systemd service unit files Plugins: * added 'with_random_choice' filter plugin * fixed ~ expansion for fileglob * with_nested allows for nested loops (see examples in examples/playbooks) ## 1.0 "Eruption" -- Feb 1 2013 New modules: * new sysctl module * new pacman module (Arch linux) * new apt_key module * hg module now in core * new ec2_facts module * added pkgin module for Joyent SmartOS New config settings: * sudo_exe parameter can be set in config to use sudo alternatives * sudo_flags parameter can alter the flags used with sudo New playbook/language features: * added when_failed and when_changed * task includes can now be of infinite depth * when_set and when_unset can take more than one var (when_set: $a and $b and $c) * added the with_sequence lookup plugin * can override "connection:" on an indvidual task * parameterized playbook includes can now define complex variables (not just all on one line) * making inventory variables available for use in vars_files paths * messages when skipping plays are now more clear * --extra-vars now has maximum precedence (as intended) Module fixes and new flags: * ability to use raw module without python on remote system * fix for service status checking on Ubuntu * service module now responds to additional exit code for SERVICE_UNAVAILABLE * fix for raw module with '-c local' * various fixes to git module * ec2 module now reports the public DNS name * can pass executable= to the raw module to specify alternative shells * fix for postgres module when user contains a "-" * added additional template variables -- $template_fullpath and $template_run_date * raise errors on invalid arguments used with a task include statement * shell/command module takes a executable= parameter to specify a different shell than /bin/sh * added return code and error output to the raw module * added support for @reboot to the cron module * misc fixes to the pip module * nagios module can schedule downtime for all services on the host * various subversion module improvements * various mail module improvements * SELinux fix for files created by authorized_key module * "template override" ?? * get_url module can now send user/password authorization * ec2 module can now deploy multiple simultaneous instances * fix for apt_key modules stalling in some situations * fix to enable Jinja2 {% include %} to work again in template * ec2 module is now powered by Boto * setup module can now detect if package manager is using pacman * fix for yum module with enablerepo in use on EL 6 Core fixes and new behaviors: * various fixes for variable resolution in playbooks * fixes for handling of "~" in some paths * various fixes to DWIM'ing of relative paths * /bin/ansible now takes a --list-hosts just like ansible-playbook did * various patterns can now take a regex vs a glob if they start with "~" (need docs on which!) - also /usr/bin/ansible * allow intersecting host patterns by using "&" ("webservers:!debian:&datacenter1") * handle tilde shell character for --private-key * hash merging policy is now selectable in the config file, can choose to override or merge * environment variables now available for setting all plugin paths (ANSIBLE_CALLBACK_PLUGINS, etc) * added packaging file for macports (not upstreamed yet) * hacking/test-module script now uses /usr/bin/env properly * fixed error formatting for certain classes of playbook syntax errors * fix for processing returns with large volumes of output Inventory files/scripts: * hostname patterns in the inventory file can now use alphabetic ranges * whitespace is now allowed around group variables in the inventory file * inventory scripts can now define groups of groups and group vars (need example for docs?) ## 0.9 "Dreams" -- Nov 30 2012 Highlighted core changes: * various performance tweaks, ansible executes dramatically less SSH ops per unit of work * close paramiko SFTP connections less often on copy/template operations (speed increase) * change the way we use multiprocessing (speed/RAM usage improvements) * able to set default for asking password & sudo password in config file * ansible now installs nicely if running inside a virtualenv * flag to allow SSH connection to move files by scp vs sftp (in config file) * additional RPM subpackages for easily installing fireball mode deps (server and node) * group_vars/host_vars now available to ansible, not just playbooks * native ssh connection type (-c ssh) now supports passwords as well as keys * ansible-doc program to show details Other core changes: * fix for template calls when last character is '$' * if ansible_python_interpreter is set on a delegated host, it now works as intended * --limit can now take "," as separator as well as ";" or ":" * msg is now displaced with newlines when a task fails * if any with_ plugin has no results in a list (empty list for with_items, etc), the task is now skipped * various output formatting fixes/improvements * fix for Xen dom0/domU detection in default facts * 'ansible_domain' fact now available (ex value: example.com) * configured remote temp file location is now always used even for root * 'register'-ed variables are not recorded for skipped hosts (for example, using only_if/when) * duplicate host records for the same host can no longer result when a host is listed in multiple groups * ansible-pull now passes --limit to prevent running on multiple hosts when used with generic playbooks * remote md5sum check fixes for Solaris 10 * ability to configure syslog facility used by remote module calls * in templating, stray '$' characters are now handled more correctly Playbook changes: * relative paths now work for 'first_available_file' * various templating engine fixes * 'when' is an easier form of only if * --list-hosts on the playbook command now supports multiple playbooks on the same command line * playbook includes can now be parameterized Module additions: * (addhost) new module for adding a temporary host record (used for creating new guests) * (group_by) module allows partitioning hosts based on group data * (ec2) new module for creating ec2 hosts * (script) added 'script' module for pushing and running self-deleting remote scripts * (svr4pkg) solaris svr4pkg module Module changes: * (authorized key) module uses temp file now to prevent failure on full disk * (fetch) now uses the 'slurp' internal code to work as you would expect under sudo'ed accounts * (fetch) internal usage of md5 sums fixed for BSD * (get_url) thirsty is no longer required for directory destinations * (git) various git module improvements/tweaks * (group) now subclassed for various platforms, includes SunOS support * (lineinfile) create= option on lineinfile can create the file when it does not exist * (mysql_db) module takes new grant options * (postgresql_db) module now takes role_attr_flags * (service) further upgrades to service module service status reporting * (service) tweaks to get service module to play nice with BSD style service systems (rc.conf) * (service) possible to pass additional arguments to services * (shell) and command module now take an 'executable=' flag for specifying an alternate shell than /bin/sh * (user) ability to create SSH keys for users when using user module to create users * (user) atomic replacement of files preserves permissions of original file * (user) module can create SSH keys * (user) module now does Solaris and BSD * (yum) module takes enablerepo= and disablerepo= * (yum) misc yum module fixing for various corner cases Plugin changes: * EC2 inventory script now produces nicer failure message if AWS is down (or similar) * plugin loading code now more streamlined * lookup plugins for DNS text records, environment variables, and redis * added a template lookup plugin $TEMPLATE('filename.j2') * various tweaks to the EC2 inventory plugin * jinja2 filters are now pluggable so it's easy to write your own (to_json/etc, are now impl. as such) ## 0.8 "Cathedral" -- Oct 19, 2012 Highlighted Core Changes: * fireball mode -- ansible can bootstrap a ephemeral 0mq (zeromq) daemon that runs as a given user and expires after X period of time. It is very fast. * playbooks with errors now return 2 on failure. 1 indicates a more fatal syntax error. Similar for /usr/bin/ansible * server side action code (template, etc) are now fully pluggable * ability to write lookup plugins, like the code powering "with_fileglob" (see below) Other Core Changes: * ansible config file can also go in 'ansible.cfg' in cwd in addition to ~/.ansible.cfg and /etc/ansible/ansible.cfg * fix for inventory hosts at API level when hosts spec is a list and not a colon delimited string * ansible-pull example now sets up logrotate for the ansible-pull cron job log * negative host matching (!hosts) fixed for external inventory script usage * internals: os.executable check replaced with utils function so it plays nice on AIX * Debian packaging now includes ansible-pull manpage * magic variable 'ansible_ssh_host' can override the hostname (great for usage with tunnels) * date command usage in build scripts fixed for OS X * don't use SSH agent with paramiko if a password is specified * make output be cleaner on multi-line command/shell errors * /usr/bin/ansible now prints things when tasks are skipped, like when creates= is used with -m command and /usr/bin/ansible * when trying to async a module that is not a 'normal' asyncable module, ansible will now let you know * ability to access inventory variables via 'hostvars' for hosts not yet included in any play, using on demand lookups * merged ansible-plugins, ansible-resources, and ansible-docs into the main project * you can set ANSIBLE_NOCOWS=1 if you want to disable cowsay if it is installed. Though no one should ever want to do this! Cows are great! * you can set ANSIBLE_FORCE_COLOR=1 to force color mode even when running without a TTY * fatal errors are now properly colored red. * skipped messages are now cyan, to differentiate them from unchanged messages. * extensive documentation upgrades * delegate_action to localhost (aka local_action) will always use the local connection type Highlighted playbook changes: * is_set is available for use inside of an only_if expression: is_set('ansible_eth0'). We intend to further upgrade this with a 'when' keyword providing better options to 'only_if' in the next release. Also is_unset('ansible_eth0') * playbooks can import playbooks in other directories and then be able to import tasks relative to them * FILE($path) now allows access of contents of file in a path, very good for use with SSH keys * similarly PIPE($command) will run a local command and return the results of executing this command * if all hosts in a play fail, stop the playbook, rather than letting the console log spool on by * only_if using register variables that are booleans now works in a boolean way like you'd expect * task includes now work with with_items (such as: include: path/to/wordpress.yml user=$item) * when using a $list variable with $var or ${var} syntax it will automatically join with commas * setup is not run more than once when we know it is has already been run in a play that included another play, etc * can set/override sudo and sudo_user on individual tasks in a play, defaults to what is set in the play if not present * ability to use with_fileglob to iterate over local file patterns * templates now use Jinja2's 'trim_blocks=True' to avoid stray newlines, small changes to templates may be required in rare cases. Other playbook changes: * to_yaml and from_yaml are available as Jinja2 filters * $group and $group_names are now accessible in with_items * where 'stdout' is provided a new 'stdout_lines' variable (type == list) is now generated and usable with with_items * when local_action is used the transport is automatically overridden to the local type * output on failed playbook commands is now nicely split for stderr/stdout and syntax errors * if local_action is not used and delegate_to was 127.0.0.1 or localhost, use local connection regardless * when running a playbook, and the statement has changed, prints 'changed:' now versus 'ok:' so it is obvious without colored mode * variables now usable within vars_prompt (just not host/group vars) * setup facts are now retained across plays (dictionary just gets updated as needed) * --sudo-user now works with --extra-vars * fix for multi_line strings with only_if New Modules: * ini_file module for manipulating INI files * new LSB facts (release, distro, etc) * pause module -- (pause seconds=10) (pause minutes=1) (pause prompt=foo) -- it's an action plugin * a module for adding entries to the main crontab (though you may still wish to just drop template files into cron.d) * debug module can be used for outputing messages without using 'shell echo' * a fail module is now available for causing errors, you might want to use it with only_if to fail in certain conditions Other module Changes, Upgrades, and Fixes: * removes= exists on command just like creates= * postgresql modules now take an optional port= parameter * /proc/cmdline info is now available in Linux facts * public host key detection for OS X * lineinfile module now uses 'search' not exact 'match' in regexes, making it much more intuitive and not needing regex syntax most of the time * added force=yes|no (default no) option for file module, which allows transition between files to directories and so on * additional facts for SunOS virtualization * copy module is now atomic when used across volumes * url_get module now returns 'dest' with the location of the file saved * fix for yum module when using local RPMs vs downloading * cleaner error messages with copy if destination directory does not exist * setup module now still works if PATH is not set * service module status now correct for services with 'subsys locked' status * misc fixes/upgrades to the wait_for module * git module now expands any "~" in provided destination paths * ignore stop error code failure for service module with state=restarted, always try to start * inline documentation for modules allows documentation source to built without pull requests to the ansible-docs project, among other things * variable '$ansible_managed' is now great to include at the top of your templates and includes useful information and a warning that it will be replaced * "~" now expanded in command module when using creates/removes * mysql module can do dumps and imports * selinux policy is only required if setting to not disabled * various fixes for yum module when working with packages not in any present repo ## 0.7 "Panama" -- Sept 6 2012 Module changes: * login_unix_socket option for mysql user and database modules (see PR #781 for doc notes) * new modules -- pip, easy_install, apt_repository, supervisorctl * error handling for setup module when SELinux is in a weird state * misc yum module fixes * better changed=True/False detection in user module on older Linux distros * nicer errors from modules when arguments are not key=value * backup option on copy (backup=yes), as well as template, assemble, and lineinfile * file module will not recurse on directory properties * yum module now workable without having repoquery installed, but doesn't support comparisons or list= if so * setup module now detects interfaces with aliases * better handling of VM guest type detection in setup module * new module boilerplate code to check for mutually required arguments, arguments required together, exclusive args * add pattern= as a paramter to the service module (for init scripts that don't do status, or do poor status) * various fixes to mysql & postresql modules * added a thirsty= option (boolean, default no) to the get_url module to decide to download the file every time or not * added a wait_for module to poll for ports being open * added a nagios module for controlling outage windows and alert statuses * added a seboolean module for getsebool/setsebool type operations * added a selinux module for controlling overall SELinux policy * added a subversion module * added lineinfile for adding and removing lines from basic files * added facts for ARM-based CPUs * support for systemd in the service module * git moduleforce reset behavior is now controllable * file module can now operate on special files (block devices, etc) Core changes: * ansible --version will now give branch/SHA information if running from git * better sudo permissions when encountering different umasks * when using paramiko and SFTP is not accessible, do not traceback, but return a nice human readable msg * use -vvv for extreme debug levels. -v gives more playbook output as before * -vv shows module arguments to all module calls (and maybe some other things later) * don not pass "--" to sudo to work on older EL5 * make remote_md5 internal function work with non-bash shells * allow user to be passed in via --extra-vars (regression) * add --limit option, which can be used to further confine the pattern given in ansible-playbooks * adds ranged patterns like dbservers[0-49] for usage with patterns or --limit * -u and user: defaults to current user, rather than root, override as before * /etc/ansible/ansible.cfg and ~/ansible.cfg now available to set default values and other things * (developers) ANSIBLE_KEEP_REMOTE_FILES=1 can be used in debugging (envrionment variable) * (developers) connection types are now plugins * (developers) callbacks can now be extended via plugins * added FreeBSD ports packaging scripts * check for terminal properties prior to engaging color modes * explicitly disable password auth with -c ssh, as it is not used anyway Playbooks: * YAML syntax errors detected and show where the problem is * if you ctrl+c a playbook it will not traceback (usually) * vars_prompt now has encryption options (see examples/playbooks/prompts.yml) * allow variables in parameterized task include parameters (regression) * add ability to store the result of any command in a register (see examples/playbooks/register_logic.yml) * --list-hosts to show what hosts are included in each play of a playbook * fix a variable ordering issue that could affect vars_files with selective file source lists * adds 'delegate_to' for a task, which can be used to signal outage windows and load balancers on behalf of hosts * adds 'serial' to playbook, allowing you to specify how many hosts can be processing a playbook at one time (default 0=all) * adds 'local_action: ' as an alias to 'delegate_to: 127.0.0.1' ## 0.6 "Cabo" -- August 6, 2012 playbooks: * support to tag tasks and includes and use --tags in playbook CLI * playbooks can now include other playbooks (example/playbooks/nested_playbooks.yml) * vars_files now usable with with_items, provided file paths don't contain host specific facts * error reporting if with_items value is unbound * with_items no longer creates lots of tasks, creates one task that makes multiple calls * can use host_specific facts inside with_items (see above) * at the top level of a playbook, set 'gather_facts: no' to skip fact gathering * first_available_file and with_items used together will now raise an error * to catch typos, like 'var' for 'vars', playbooks and tasks now yell on invalid parameters * automatically load (directory_of_inventory_file)/group_vars/groupname and /host_vars/hostname in vars_files * playbook is now colorized, set ANSIBLE_NOCOLOR=1 if you do not like this, does not colorize if not a TTY * hostvars now preserved between plays (regression in 0.5 from 0.4), useful for sharing vars in multinode configs * ignore_errors: yes on a task can be used to allow a task to fail and not stop the play * with_items with the apt/yum module will install/remove/update everything in a single command inventory: * groups variable available as a hash to return the hosts in each group name * in YAML inventory, hosts can list their groups in inverted order now also (see tests/yaml_hosts) * YAML inventory is deprecated and will be removed in 0.7 * ec2 inventory script * support ranges of hosts in the host file, like www[001-100].example.com (supports leading zeros and also not) modules: * fetch module now does not fail a system when requesting file paths (ex: logs) that don't exist * apt module now takes an optional install-recommends=yes|no (default yes) * fixes to the return codes of the copy module * copy module takes a remote md5sum to avoid large file transfer * various user and group module fixes (error handling, etc) * apt module now takes an optional force parameter * slightly better psychic service status handling for the service module * fetch module fixes for SSH connection type * modules now consistently all take yes/no for boolean parameters (and DWIM on true/false/1/0/y/n/etc) * setup module no longer saves to disk, template module now only used in playbooks * setup module no longer needs to run twice per playbook * apt module now passes DEBIAN_FRONTEND=noninteractive * mount module (manages active mounts + fstab) * setup module fixes if no ipv6 support * internals: template in common module boilerplate, also causes less SSH operations when used * git module fixes * setup module overhaul, more modular * minor caching logic added to inventory to reduce hammering of inventory scripts. * MySQL and PostgreSQL modules for user and db management * vars_prompt now supports private password entry (see examples/playbooks/prompts.yml) * yum module modified to be more tolerant of plugins spewing random console messages (ex: RHN) internals: * when sudoing to root, still use /etc/ansible/setup as the metadata path, as if root * paramiko is now only imported if needed when running from source checkout * cowsay support on Ubuntu * various ssh connection fixes for old Ubuntu clients * ./hacking/test-module now supports options like ansible takes and has a debugger mode * sudoing to a user other than root now works more seamlessly (uses /tmp, avoids umask issues) ## 0.5 "Amsterdam" ------- July 04, 2012 * Service module gets more accurate service states when running with upstart * Jinja2 usage in playbooks (not templates), reinstated, supports %include directive * support for --connection ssh (supports Kerberos, bastion hosts, etc), requires ControlMaster * misc tracebacks replaced with error messages * various API/internals refactoring * vars can be built from other variables * support for exclusion of hosts/groups with "!groupname" * various changes to support md5 tool differences for FreeBSD nodes & OS X clients * "unparseable" command output shows in command output for easier debugging * mktemp is no longer required on remotes (not available on BSD) * support for older versions of python-apt in the apt module * a new "assemble" module, for constructing files from pieces of files (inspired by Puppet "fragments" idiom) * ability to override most default values with ANSIBLE_FOO environment variables * --module-path parameter can support multiple directories separated with the OS path separator * with_items can take a variable of type list * ansible_python_interpreter variable available for systems with more than one Python * BIOS and VMware "fact" upgrades * cowsay is used by ansible-playbook if installed to improve output legibility (try installing it) * authorized_key module * SELinux facts now sourced from the python selinux library * removed module debug option -D * added --verbose, which shows output from successful playbook operations * print the output of the raw command inside /usr/bin/ansible as with command/shell * basic setup module support for Solaris * ./library relative to the playbook is always in path so modules can be included in tarballs with playbooks ## 0.4 "Unchained" ------- May 23, 2012 Internals/Core * internal inventory API now more object oriented, parsers decoupled * async handling improvements * misc fixes for running ansible on OS X (overlord only) * sudo improvements, now works much more smoothly * sudo to a particular user with -U/--sudo-user, or using 'sudo_user: foo' in a playbook * --private-key CLI option to work with pem files Inventory * can use -i host1,host2,host3:port to specify hosts not in inventory (replaces --override-hosts) * ansible INI style format can do groups of groups [groupname:children] and group vars [groupname:vars] * groups and users module takes an optional system=yes|no on creation (default no) * list of hosts in playbooks can be expressed as a YAML list in addition to ; delimited Playbooks * variables can be replaced like ${foo.nested_hash_key.nested_subkey[array_index]} * unicode now ok in templates (assumes utf8) * able to pass host specifier or group name in to "hosts:" with --extra-vars * ansible-pull script and example playbook (extreme scaling, remediation) * inventory_hostname variable available that contains the value of the host as ansible knows it * variables in the 'all' section can be used to define other variables based on those values * 'group_names' is now a variable made available to templates * first_available_file feature, see selective_file_sources.yml in examples/playbooks for info * --extra-vars="a=2 b=3" etc, now available to inject parameters into playbooks from CLI Incompatible Changes * jinja2 is only usable in templates, not playbooks, use $foo instead * --override-hosts removed, can use -i with comma notation (-i "ahost,bhost") * modules can no longer include stderr output (paramiko limitation from sudo) Module Changes * tweaks to SELinux implementation for file module * fixes for yum module corner cases on EL5 * file module now correctly returns the mode in octal * fix for symlink handling in the file module * service takes an enable=yes|no which works with chkconfig or updates-rc.d as appropriate * service module works better on Ubuntu * git module now does resets and such to work more smoothly on updates * modules all now log to syslog * enabled=yes|no on a service can be used to toggle chkconfig & updates-rc.d states * git module supports branch= * service fixes to better detect status using return codes of the service script * custom facts provided by the setup module mean no dependency on Ruby, facter, or ohai * service now has a state=reloaded * raw module for bootstrapping and talking to routers w/o Python, etc Misc Bugfixes * fixes for variable parsing in only_if lines * misc fixes to key=value parsing * variables with mixed case now legal * fix to internals of hacking/test-module development script ## 0.3 "Baluchitherium" -- April 23, 2012 * Packaging for Debian, Gentoo, and Arch * Improvements to the apt and yum modules * A virt module * SELinux support for the file module * Ability to use facts from other systems in templates (aka exported resources like support) * Built in Ansible facts so you don't need ohai, facter, or Ruby * tempdir selections that work with noexec mounted /tmp * templates happen locally, not remotely, so no dependency on python-jinja2 for remote computers * advanced inventory format in YAML allows more control over variables per host and per group * variables in playbooks can be structured/nested versus just a flat namespace * manpage upgrades (docs) * various bugfixes * can specify a default --user for playbooks rather than specifying it in the playbook file * able to specify ansible port in ansible host file (see docs) * refactored Inventory API to make it easier to write scripts using Ansible * looping capability for playbooks (with_items) * support for using sudo with a password * module arguments can be unicode * A local connection type, --connection=local, for use with cron or in kickstarts * better module debugging with -D * fetch module for pulling in files from remote hosts * command task supports creates=foo for idempotent semantics, won't run if file foo already exists ## 0.0.2 and 0.0.1 * Initial stages of project ansible-1.7.2/CODING_GUIDELINES.md000066400000000000000000000241301241061774000161350ustar00rootroot00000000000000Coding Guidelines ================= Hi! Thanks for interest in contributing to Ansible. Here are some guidelines for contributing code. The purpose of this document are to establish what we're looking for in code contributions, and to make sure new contributions know some of the conventions that we've been using. We don't think much of this should be too strange to readers familiar with contributing to Python projects, though it helps if we all get on the same page. Language ======== * While not all components of Ansible must be in Python, core contributions to the Ansible repo must be written in Python. This is to maximize the ability of everyone to contribute. * If you want to write non-Python ansible modules or inventory scripts, that's fine, but they are not going to get merged in most likely. Sorry!! PEP8 and basic style checks =========================== * PEP8 is a great Python style guide, which you should read. * PEP8 must not be strictly followed in all aspects, but most of it is good advice * In particular, we don't really care about line lengths. Buy a bigger monitor! * To run checks for things we care about, run "make pep8" * Similarly, additional checks can be made with "make pyflakes" * There is no need to submit code changes for pep8 and pyflake fixes, as these break attribution history. Project leadership will make these periodically. * Do not submit pull requests that simply adjust whitespace in the code Testing ======= * Much of ansible's testing needs are in integration, not unit tests. Add module tests there. * That being said, there are unit tests too! * Code written must absolutely pass tests (i.e. "make tests") * You should anticipate any error paths in your code and test down those error paths. * Additions to tests for core code is welcome, but not always possible. Be sure things are at least well tested manually in that case. Whitespace ========== * Four space indent is strictly required * Include meaningful whitespace between lines of code Shebang Lines ============= * /usr/bin/scripts should start with '/usr/bin/env python' * module code should still use '/usr/bin/python' as this is replaced automatically by 'ansible_python_interpreter', see the FAQ in the docs for more info. Comments ======== * Readability is one of the most important goals for this project * Comment any non-trivial code where someone might not know why you are doing something in a particular way * Though if something should be commented, that's often a sign someone should write a function * All new functions must have a basic docstring comment * Commenting above a line is preferable to commenting at the end of a line Classes ======= * With the exception of module code (where inline is better), it is desirable to see classes in their own files. * Classes should generally not cause side effects as soon as they are instantiated, move meaningful behavior to methods rather than constructors. Functions and Methods ===================== * In general, functions should not be 'too long' and should describe a meaningful amount of work * When code gets too nested, that's usually the sign the loop body could benefit from being a function * Parts of our existing code are not the best examples of this at times. * Functions should have names that describe what they do, along with docstrings * Functions should be named with_underscores * "Don't repeat yourself" is generally a good philosophy Variables ========= * Use descriptive variable names instead of variables like 'x', unless x is a obvious loop index * Ansible python code uses identifiers like 'ClassesLikeThis and variables_like_this * Module parameters should also use_underscores and not runtogether Module Security =============== * Modules must take steps to avoid passing user input from the shell and always check return codes * always use module.run_command instead of subprocess or Popen or os.system -- this is mandatory * if you use need the shell you must pass use_unsafe_shell=True to module.run_command * if you do not need the shell, avoid using the shell * any variables that can come from the user input with use_unsafe_shell=True must be wrapped by pipes.quote(x) * downloads of https:// resource urls must import module_utils.urls and use the fetch_url method Misc Preferences ================ Use the dict constructor where possible when allocating dictionaries: # not this: foo = { 'a' : 12, 'b' : 34 } # this: foo = dict( a = 12, b = 34 ) Line up variables # not this a = 12 foosball = 34 xyz = 'dog' # this a = 12 foosball = 34 xyz = 'dog' Don't use line continuations: # no if (this_is_a_very_long_line and foo and \ i_am_going_to_continue_it): bar() # better: if (this_is_a_very_long_line and foo and i_am_going_to_continue_it): bar() Spacing: # no x=[1,2,3] # no x = [1,2,3] # yes x = [ 1, 2, 3 ] Spacing continued: # no x=foo(12) # no x = foo( 12 ) # yes x = foo(12) Licenses ======== Every file should have a license header, including the copyright of the original author. Major additions to the module are allowed to add an additional copyright line, and this is especially true of rewrites, but original authorship copyright messages should be preserved. All contributions to the core repo should preserve original licenses and new contributions must include the GPLv3 header. Module Documentation ==================== All module pull requests must include a DOCUMENTATION docstring (YAML format, see other modules for examples) as well as an EXAMPLES docstring, which is free form. When adding new modules, any new parameter must have a "version_added" attribute. When submitting a new module, the module should have a "version_added" attribute in the pull request as well, set to the current development version. Be sure to check grammar and spelling. It's frequently the case that modules get submitted with YAML that isn't valid, so you can run "make webdocs" from the checkout to preview your module's documentation. If it fails to build, take a look at your DOCUMENTATION string or you might have a Python syntax error in there too. Python Imports ============== To make it clear what a module is importing, imports should not be sprinkled throughout the code. Python Imports should happen at the top of the file, exempting code from module_utils. When a conditional runtime import is required, do so something like this instead: HAS_FOO = False try: import foo HAS_FOO = True except ImportError: pass ... if not HAS_FOO: raise Exception("the foo library is required") This makes it clear what optional dependencies are but allows this to be deferred until runtime. In the case of module code, the raising of the Exception will be replaced with a "module.exit_json" call. Exceptions ========== In the main body of the code, use typed exceptions where possible: # not this raise Exception("panic!") # this from ansible import errors ... raise errors.AnsibleError("panic!") Similarly, exception checking should be fine grained: # not this try: foo() except: bar() # but this try: foo() except SomeTypedException: bar() List Comprehensions =================== In general list comprehensions are always preferred to map() and filter() calls. However, they can be abused. Optimize for readability, and avoid nesting them too deeply. Regexes ======= There is a time and place for them, but here's an illustrative joke. "A developer had a problem, and used a regular expression to solve it. Now the developer had two problems". Often regexes are difficult to maintain, and a trusty call to other string operations can be a great solution, faster, and more readable. File Conventions ================ If a piece of code looks for a named YAML file in a directory, it should assume it can take no extension, or an extension of '.yml' or '.yaml'. This should be true against all code that loads files. Any code that uses directories should consider the possibility that the directory may be symlink. New Ansible language parameters =============================== If adding a new parameter, like 'can_fizzbuzz: True/False' be sure the value of the parameter is templated somewhere in the Runner code, as if anything can be parameterized in Ansible, there is a user that will try to parameterize it. String Find =========== Use 'in': # not this: if x.find('foo') != -1: # this: if 'foo' in x: String checks ============= To test if something is a string, consider that it may be unicode. # no if type(x) == str: # yes if isinstance(x, basestring): Cleverness ========== Ansible's code is intended to be read by as many people as possible, so we don't particularly encourage clever or heavily idiomatic code. In particular, metaclasses are probably not appropriate, however entertaining they may be to add. Git Practices ============= Pull requests cannot be accepted that contain merge commits. Always do "git pull --rebase" and "git rebase" vs "git pull" or "git merge". Always create a new branch for each pull request to avoid intertwingling different features or fixes on the same branch. Python Version Compliance ========================= All code in Ansible core must support a minimum version of Python 2.6. Module code must support a minimum of Python 2.4, with occasional exception for modules that require code that themselves require 2.6 and later. A quick reminder is that list comprehensions in Python 2.4 are not as fully fleshed out, there are no 'dict' comprehensions, and there is no 'with' statement. But otherwise it's pretty much all the same. The End ======= This was not meant to be a scary document, so we hope it wasn't, but we also hope this helps you write code that is easier to maintain by others in the future. If you have questions about this document, please ask on the ansible-devel mailing list. Thank you! ansible-1.7.2/CONTRIBUTING.md000066400000000000000000000277221241061774000154030ustar00rootroot00000000000000Ansible Community Information ============================== The purpose of the Ansible community is to unite developers, system administrators, operations, and IT managers to share and build great automation solutions. This document contains all sorts of information about how to contribute and interact with Ansible. Welcome! Ways to Interact ================ There are a lot of ways to join and be a part of the Ansible community, such as: Sharing Ansible with Others --------------------------- You can help share Ansible with others by telling friends and colleagues, writing a blog post, or presenting at user groups (like DevOps groups or the local LUG or BUG). You are also welcome to share slides on speakerdeck, sign up for a free account and tag it “Ansibleâ€. On Twitter, you can also share things with #ansible and may wish to follow [@Ansible](https://twitter.com/ansible). Sharing Content and Tips ------------------------ Join the [Ansible project mailing list](https://groups.google.com/forum/#!forum/ansible-project) and you can share playbooks you may have written and other interesting implementation stories. Put your Ansible content up on places like github to share with others. Sharing A Feature Idea ---------------------- Ideas are very welcome and the best place to share them is the [Ansible project mailing list](https://groups.google.com/forum/#!forum/ansible-project) ([Subscribe](https://groups.google.com/forum/#!forum/ansible-project/join)) or #ansible on irc.freenode.net. While you can file a feature request on GitHub, pull requests are a much better way to get your feature added than submitting a feature request. Open source is all about itch scratching, and it's less likely that someone else will have the same itches as yourself. We keep code reasonably simple on purpose so it's easy to dive in and make additions, but be sure to read the "Contributing Code" section below too -- as it doesn't hurt to have a discussion about a feature first -- we're inclined to have preferences about how incoming features might be implemented, and that can save confusion later. Helping with Documentation -------------------------- Ansible documentation is a community project too! If you would like to help with the documentation, whether correcting a typo or improving a section, or maybe even documenting a new feature, submit a github pull request to the code that lives in the “docsite/rst†subdirectory of the project. Docs are in restructured text format. If you aren’t comfortable with restructured text, you can also open a ticket on github about any errors you spot or sections you would like to see added. For more information on creating pull requests, please refer to the [github help guide](https://help.github.com/articles/using-pull-requests). Contributing Code (Features or Bugfixes) ---------------------------------------- The Ansible project keeps it’s source on github at [github.com/ansible/ansible](http://github.com/ansible/ansible) and takes contributions through [github pull requests](https://help.github.com/articles/using-pull-requests). It is usually a good idea to join the ansible-devel list to discuss any large features prior to submission, and this especially helps in avoiding duplicate work or efforts where we decide, upon seeing a pull request for the first time, that revisions are needed. (This is not usually needed for module development) Note that we do keep Ansible to a particular aesthetic, so if you are unclear about whether a feature is a good fit or not, having the discussion on the development list is often a lot easier than having to modify a pull request later. When submitting patches, be sure to run the unit tests first “make tests†and always use “git rebase†vs “git merge†(aliasing git pull to git pull --rebase is a great idea) to avoid merge commits in your submissions. There are also integration tests that can be run in the "tests/integration" directory. In order to keep the history clean and better audit incoming code, we will require resubmission of pull requests that contain merge commits. Use "git pull --rebase" vs "git pull" and "git rebase" vs "git merge". Also be sure to use topic branches to keep your additions on different branches, such that they won't pick up stray commits later. We’ll then review your contributions and engage with you about questions and so on. As we have a very large and active community, so it may take awhile to get your contributions in! See the notes about priorities in a later section for understanding our work queue. Patches should be made against the 'devel' branch. Contributions can be for new features like modules, or to fix bugs you or others have found. If you are interested in writing new modules to be included in the core Ansible distribution, please refer to the [Module Developers documentation on our website](http://docs.ansible.com/developing_modules.html). Ansible's aesthetic encourages simple, readable code and consistent, conservatively extending, backwards-compatible improvements. Code developed for Ansible needs to support Python 2.6+, while code in modules must run under Python 2.4 or higher. Please also use a 4-space indent and no tabs. Tip: To easily run from a checkout, source "./hacking/env-setup" and that's it -- no install required. You're now live! Reporting A Bug --------------- Ansible practices responsible disclosure - if this is a security related bug, email security@ansible.com instead of filing a ticket or posting to the Google Group and you will receive a prompt response. Bugs should be reported to [github.com/ansible/ansible](http://github.com/ansible/ansible) after signing up for a free github account. Before reporting a bug, please use the bug/issue search to see if the issue has already been reported. When filing a bug, please use the [issue template](https://raw2.github.com/ansible/ansible/devel/examples/issues/ISSUE_TEMPLATE.md) to provide all relevant information. Do not use the issue tracker for "how do I do this" type questions. These are great candidates for IRC or the mailing list instead where things are likely to be more of a discussion. To be respectful of reviewers time and allow us to help everyone efficiently, please provide minimal well-reduced and well-commented examples versus sharing your entire production playbook. Include playbook snippets and output where possible. Content in the GitHub bug tracker can be indented four spaces to preserve formatting. For multiple-file content, we encourage use of gist.github.com. Online pastebin content can expire. If you are not sure if something is a bug yet, you are welcome to ask about something on the mailing list or IRC first. As we are a very high volume project, if you determine that you do have a bug, please be sure to open the issue yourself to ensure we have a record of it. Don’t rely on someone else in the community to file the bug report for you. It may take some time to get to your report, see "A Note About Priorities" below. A Note About Priorities ======================= Ansible was one of the top 5 projects with the most OSS contributors on GitHub in 2013, and well over 600 people have added code to the project. As a result, we have a LOT of incoming activity to process. In the interest of transparency, we're telling you how we do this. In our bug tracker you'll notice some labels - P1, P2, P3, P4, and P5. These are our internal priority orders that we use to sort tickets. With some exceptions for easy merges (like documentation typos for instance), we're going to spend most of our time working on P1 and P2 items first, including pull requests. These usually relate to important bugs or features affecting large segments of the userbase. So if you see something categorized "P3 or P4", and it's not appearing to get a lot of immediate attention, this is why. These labels don't really have definition - they are a simple ordering. However something affecting a major module (yum, apt, etc) is likely to be prioritized higher than a module affecting a smaller number of users. Since we place a strong emphasis on testing and code review, it may take a few months for a minor feature to get merged. Don't worry though -- we'll also take periodic sweeps through the lower priority queues and give them some attention as well, particularly in the area of new module changes. So it doesn't neccessarily mean that we'll be exhausting all of the higher-priority queues before getting to your ticket. Release Numbering ================= Releases ending in ".0" are major releases and this is where all new features land. Releases ending in another integer, like "0.X.1" and "0.X.2" are dot releases, and these are only going to contain bugfixes. Typically we don't do dot releases for minor releases, but may occasionally decide to cut dot releases containing a large number of smaller fixes if it's still a fairly long time before the next release comes out. Online Resources ================ Documentation ------------- The main ansible documentation can be found at [docs.ansible.com](http://docs.ansible.com). As mentioned above this is an open source project, so we accept contributions to the documentation. You can also find some best practices examples that we recommend reading at [ansible-examples](http://github.com/ansible/ansible-examples). Mailing lists ------------- Ansible has several mailing lists. Your first post to the mailing list will be moderated (to reduce spam), so please allow a day or less for your first post. [ansible-announce](https://groups.google.com/forum/#!forum/ansible-announce) is for release announcements and major news. It is a low traffic read-only list and you should only get a few emails a month. [ansible-project](https://groups.google.com/forum/#!forum/ansible-project) is the main list, and is used for sharing cool projects you may have built, talking about Ansible ideas, and for users to ask questions or to help other users. [ansible-devel](https://groups.google.com/forum/#!forum/ansible-devel) is a technical list for developers working on Ansible and Ansible modules. Join here to discuss how to build modules, prospective feature implementations, or technical challenges. To subscribe to a group from a non-google account, you can email the subscription address, for example ansible-devel+subscribe@googlegroups.com. IRC --- Ansible has a general purpose IRC channel available at #ansible on irc.freenode.net. Use this channel for all types of conversations, including sharing tips, coordinating development work, or getting help from other users. Miscellaneous Information ========================= Staff ----- Ansible, Inc is a company supporting Ansible and building additional solutions based on Ansible. We also do services and support for those that are interested. Our most important task however is enabling all the great things that happen in the Ansible community, including organizing software releases of Ansible. For more information about any of these things, contact info@ansible.com On IRC, you can find us as mdehaan, jimi_c, Tybstar, and others. On the mailing list, we post with an @ansible.com address. Community Code of Conduct ------------------------- Ansible’s community welcomes users of all types, backgrounds, and skill levels. Please treat others as you expect to be treated, keep discussions positive, and avoid discrimination, profanity, allegations of Cthulhu worship, or engaging in controversial debates (except vi vs emacs is cool). Posts to mailing lists should remain focused around Ansible and IT automation. Abuse of these community guidelines will not be tolerated and may result in banning from community resources. Contributors License Agreement ------------------------------ By contributing you agree that these contributions are your own (or approved by your employer) and you grant a full, complete, irrevocable copyright license to all users and developers of the project, present and future, pursuant to the license of the project. ansible-1.7.2/COPYING000066400000000000000000001045141241061774000142000ustar00rootroot00000000000000 GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: Copyright (C) This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see . The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read . ansible-1.7.2/MANIFEST.in000066400000000000000000000005011241061774000146720ustar00rootroot00000000000000include README.md packaging/rpm/ansible.spec COPYING include examples/hosts include examples/ansible.cfg graft examples/playbooks include packaging/distutils/setup.py include lib/ansible/module_utils/powershell.ps1 recursive-include docs * recursive-include library * include Makefile include VERSION include MANIFEST.in ansible-1.7.2/Makefile000066400000000000000000000202671241061774000146070ustar00rootroot00000000000000#!/usr/bin/make # WARN: gmake syntax ######################################################## # Makefile for Ansible # # useful targets: # make sdist ---------------- produce a tarball # make srpm ----------------- produce a SRPM # make rpm ----------------- produce RPMs # make deb-src -------------- produce a DEB source # make deb ------------------ produce a DEB # make docs ----------------- rebuild the manpages (results are checked in) # make tests ---------------- run the tests # make pyflakes, make pep8 -- source code checks ######################################################## # variable section NAME = ansible OS = $(shell uname -s) # Manpages are currently built with asciidoc -- would like to move to markdown # This doesn't evaluate until it's called. The -D argument is the # directory of the target file ($@), kinda like `dirname`. MANPAGES := docs/man/man1/ansible.1 docs/man/man1/ansible-playbook.1 docs/man/man1/ansible-pull.1 docs/man/man1/ansible-doc.1 docs/man/man1/ansible-galaxy.1 docs/man/man1/ansible-vault.1 ifneq ($(shell which a2x 2>/dev/null),) ASCII2MAN = a2x -D $(dir $@) -d manpage -f manpage $< ASCII2HTMLMAN = a2x -D docs/html/man/ -d manpage -f xhtml else ASCII2MAN = @echo "ERROR: AsciiDoc 'a2x' command is not installed but is required to build $(MANPAGES)" && exit 1 endif PYTHON=python SITELIB = $(shell $(PYTHON) -c "from distutils.sysconfig import get_python_lib; print get_python_lib()") # VERSION file provides one place to update the software version VERSION := $(shell cat VERSION) # Get the branch information from git ifneq ($(shell which git),) GIT_DATE := $(shell git log -n 1 --format="%ai") endif ifeq ($(shell echo $(OS) | egrep -c 'Darwin|FreeBSD|OpenBSD'),1) DATE := $(shell date -j -r $(shell git log -n 1 --format="%at") +%Y%m%d%H%M) else DATE := $(shell date --utc --date="$(GIT_DATE)" +%Y%m%d%H%M) endif # DEB build parameters DEBUILD_BIN ?= debuild DEBUILD_OPTS = --source-option="-I" DPUT_BIN ?= dput DPUT_OPTS ?= ifeq ($(OFFICIAL),yes) DEB_RELEASE = 1ppa # Sign OFFICIAL builds using 'DEBSIGN_KEYID' # DEBSIGN_KEYID is required when signing ifneq ($(DEBSIGN_KEYID),) DEBUILD_OPTS += -k$(DEBSIGN_KEYID) endif else DEB_RELEASE = 0.git$(DATE) # Do not sign unofficial builds DEBUILD_OPTS += -uc -us DPUT_OPTS += -u endif DEBUILD = $(DEBUILD_BIN) $(DEBUILD_OPTS) DEB_PPA ?= ppa # Choose the desired Ubuntu release: lucid precise saucy trusty DEB_DIST ?= unstable # RPM build parameters RPMSPECDIR= packaging/rpm RPMSPEC = $(RPMSPECDIR)/ansible.spec RPMDIST = $(shell rpm --eval '%{?dist}') RPMRELEASE = 1 ifneq ($(OFFICIAL),yes) RPMRELEASE = 0.git$(DATE) endif RPMNVR = "$(NAME)-$(VERSION)-$(RPMRELEASE)$(RPMDIST)" # MOCK build parameters MOCK_BIN ?= mock MOCK_CFG ?= NOSETESTS ?= nosetests ######################################################## all: clean python tests: PYTHONPATH=./lib ANSIBLE_LIBRARY=./library $(NOSETESTS) -d -w test/units -v authors: sh hacking/authors.sh # Regenerate %.1.asciidoc if %.1.asciidoc.in has been modified more # recently than %.1.asciidoc. %.1.asciidoc: %.1.asciidoc.in sed "s/%VERSION%/$(VERSION)/" $< > $@ # Regenerate %.1 if %.1.asciidoc or VERSION has been modified more # recently than %.1. (Implicitly runs the %.1.asciidoc recipe) %.1: %.1.asciidoc VERSION $(ASCII2MAN) loc: sloccount lib library bin pep8: @echo "#############################################" @echo "# Running PEP8 Compliance Tests" @echo "#############################################" -pep8 -r --ignore=E501,E221,W291,W391,E302,E251,E203,W293,E231,E303,E201,E225,E261,E241 lib/ bin/ -pep8 -r --ignore=E501,E221,W291,W391,E302,E251,E203,W293,E231,E303,E201,E225,E261,E241 --filename "*" library/ pyflakes: pyflakes lib/ansible/*.py lib/ansible/*/*.py bin/* clean: @echo "Cleaning up distutils stuff" rm -rf build rm -rf dist @echo "Cleaning up byte compiled python stuff" find . -type f -regex ".*\.py[co]$$" -delete @echo "Cleaning up editor backup files" find . -type f \( -name "*~" -or -name "#*" \) -delete find . -type f \( -name "*.swp" \) -delete @echo "Cleaning up manpage stuff" find ./docs/man -type f -name "*.xml" -delete find ./docs/man -type f -name "*.asciidoc" -delete find ./docs/man/man3 -type f -name "*.3" -delete @echo "Cleaning up output from test runs" rm -rf test/test_data @echo "Cleaning up RPM building stuff" rm -rf MANIFEST rpm-build @echo "Cleaning up Debian building stuff" rm -rf debian rm -rf deb-build rm -rf docs/json rm -rf docs/js @echo "Cleaning up authors file" rm -f AUTHORS.TXT python: $(PYTHON) setup.py build install: $(PYTHON) setup.py install sdist: clean docs $(PYTHON) setup.py sdist rpmcommon: $(MANPAGES) sdist @mkdir -p rpm-build @cp dist/*.gz rpm-build/ @sed -e 's#^Version:.*#Version: $(VERSION)#' -e 's#^Release:.*#Release: $(RPMRELEASE)%{?dist}#' $(RPMSPEC) >rpm-build/$(NAME).spec mock-srpm: /etc/mock/$(MOCK_CFG).cfg rpmcommon $(MOCK_BIN) -r $(MOCK_CFG) --resultdir rpm-build/ --buildsrpm --spec rpm-build/$(NAME).spec --sources rpm-build/ @echo "#############################################" @echo "Ansible SRPM is built:" @echo rpm-build/*.src.rpm @echo "#############################################" mock-rpm: /etc/mock/$(MOCK_CFG).cfg mock-srpm $(MOCK_BIN) -r $(MOCK_CFG) --resultdir rpm-build/ --rebuild rpm-build/$(NAME)-*.src.rpm @echo "#############################################" @echo "Ansible RPM is built:" @echo rpm-build/*.noarch.rpm @echo "#############################################" srpm: rpmcommon @rpmbuild --define "_topdir %(pwd)/rpm-build" \ --define "_builddir %{_topdir}" \ --define "_rpmdir %{_topdir}" \ --define "_srcrpmdir %{_topdir}" \ --define "_specdir $(RPMSPECDIR)" \ --define "_sourcedir %{_topdir}" \ -bs rpm-build/$(NAME).spec @rm -f rpm-build/$(NAME).spec @echo "#############################################" @echo "Ansible SRPM is built:" @echo " rpm-build/$(RPMNVR).src.rpm" @echo "#############################################" rpm: rpmcommon @rpmbuild --define "_topdir %(pwd)/rpm-build" \ --define "_builddir %{_topdir}" \ --define "_rpmdir %{_topdir}" \ --define "_srcrpmdir %{_topdir}" \ --define "_specdir $(RPMSPECDIR)" \ --define "_sourcedir %{_topdir}" \ --define "_rpmfilename %%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm" \ --define "__python `which $(PYTHON)`" \ -ba rpm-build/$(NAME).spec @rm -f rpm-build/$(NAME).spec @echo "#############################################" @echo "Ansible RPM is built:" @echo " rpm-build/$(RPMNVR).noarch.rpm" @echo "#############################################" debian: sdist @for DIST in $(DEB_DIST) ; do \ mkdir -p deb-build/$${DIST} ; \ tar -C deb-build/$${DIST} -xvf dist/$(NAME)-$(VERSION).tar.gz ; \ cp -a packaging/debian deb-build/$${DIST}/$(NAME)-$(VERSION)/ ; \ sed -ie "s#^$(NAME) (\([^)]*\)) \([^;]*\);#ansible (\1-$(DEB_RELEASE)~$${DIST}) $${DIST};#" deb-build/$${DIST}/$(NAME)-$(VERSION)/debian/changelog ; \ done deb: debian @for DIST in $(DEB_DIST) ; do \ (cd deb-build/$${DIST}/$(NAME)-$(VERSION)/ && $(DEBUILD) -b) ; \ done @echo "#############################################" @echo "Ansible DEB artifacts:" @for DIST in $(DEB_DIST) ; do \ echo deb-build/$${DIST}/$(NAME)_$(VERSION)-$(DEB_RELEASE)~$${DIST}_amd64.changes ; \ done @echo "#############################################" deb-src: debian @for DIST in $(DEB_DIST) ; do \ (cd deb-build/$${DIST}/$(NAME)-$(VERSION)/ && $(DEBUILD) -S) ; \ done @echo "#############################################" @echo "Ansible DEB artifacts:" @for DIST in $(DEB_DIST) ; do \ echo deb-build/$${DIST}/$(NAME)_$(VERSION)-$(DEB_RELEASE)~$${DIST}_source.changes ; \ done @echo "#############################################" deb-upload: deb @for DIST in $(DEB_DIST) ; do \ $(DPUT_BIN) $(DPUT_OPTS) $(DEB_PPA) deb-build/$${DIST}/$(NAME)_$(VERSION)-$(DEB_RELEASE)~$${DIST}_amd64.changes ; \ done deb-src-upload: deb-src @for DIST in $(DEB_DIST) ; do \ $(DPUT_BIN) $(DPUT_OPTS) $(DEB_PPA) deb-build/$${DIST}/$(NAME)_$(VERSION)-$(DEB_RELEASE)~$${DIST}_source.changes ; \ done # for arch or gentoo, read instructions in the appropriate 'packaging' subdirectory directory webdocs: $(MANPAGES) (cd docsite/; make docs) docs: $(MANPAGES) ansible-1.7.2/README.md000066400000000000000000000050771241061774000144300ustar00rootroot00000000000000[![PyPI version](https://badge.fury.io/py/ansible.png)](http://badge.fury.io/py/ansible) [![PyPI downloads](https://pypip.in/d/ansible/badge.png)](https://pypi.python.org/pypi/ansible) Ansible ======= Ansible is a radically simple configuration-management, application deployment, task-execution, and multinode orchestration engine. Read the documentation and more at http://ansible.com/ Many users run straight from the development branch (it's generally fine to do so), but you might also wish to consume a release. You can find instructions [here](http://docs.ansible.com/intro_getting_started.html) for a variety of platforms. If you want a tarball of the last release, go to [releases.ansible.com](http://releases.ansible.com/ansible) and you can also install with pip. Design Principles ================= * Have a dead simple setup process and a minimal learning curve * Be super fast & parallel by default * Require no server or client daemons; use existing SSHd * Use a language that is both machine and human friendly * Focus on security and easy auditability/review/rewriting of content * Manage remote machines instantly, without bootstrapping * Allow module development in any dynamic language, not just Python * Be usable as non-root * Be the easiest IT automation system to use, ever. Get Involved ============ * Read [Contributing.md](https://github.com/ansible/ansible/blob/devel/CONTRIBUTING.md) for all kinds of ways to contribute to and interact with the project, including mailing list information and how to submit bug reports and code to Ansible. * All code submissions are done through pull requests. Take care to make sure no merge commits are in the submission, and use "git rebase" vs "git merge" for this reason. If submitting a large code change (other than modules), it's probably a good idea to join ansible-devel and talk about what you would like to do or add first and to avoid duplicate efforts. This not only helps everyone know what's going on, it also helps save time and effort if we decide some changes are needed. * irc.freenode.net: #ansible Branch Info =========== * Releases are named after Van Halen songs. * The devel branch corresponds to the release actively under development. * Various release-X.Y branches exist for previous releases * We'd love to have your contributions, read "CONTRIBUTING.md" for process notes. Author ====== Ansible was created by Michael DeHaan (michael@ansible.com) and has contributions from over 700 users (and growing). Thanks everyone! [Ansible, Inc](http://ansible.com) ansible-1.7.2/RELEASES.txt000066400000000000000000000040241241061774000151040ustar00rootroot00000000000000Ansible Releases at a Glance ============================ Active Development ++++++++++++++++++ 1.8 "You Really Got Me" ---- FALL 2014 1.7.2 "Summer Nights" -------- 09-24-2014 1.7.1 "Summer Nights" -------- 08-14-2014 1.7 "Summer Nights" -------- 08-06-2014 1.6.10 "The Cradle Will Rock" - 07-25-2014 1.6.9 "The Cradle Will Rock" - 07-24-2014 1.6.8 "The Cradle Will Rock" - 07-22-2014 1.6.7 "The Cradle Will Rock" - 07-21-2014 1.6.6 "The Cradle Will Rock" - 07-01-2014 1.6.5 "The Cradle Will Rock" - 06-25-2014 1.6.4 "The Cradle Will Rock" - 06-25-2014 1.6.3 "The Cradle Will Rock" - 06-09-2014 1.6.2 "The Cradle Will Rock" - 05-23-2014 1.6.1 "The Cradle Will Rock" - 05-07-2014 1.6 "The Cradle Will Rock" - 05-05-2014 1.5.5 "Love Walks In" -------- 04-18-2014 1.5.4 "Love Walks In" -------- 04-01-2014 1.5.3 "Love Walks In" -------- 03-13-2014 1.5.2 "Love Walks In" -------- 03-11-2014 1.5.1 "Love Walks In" -------- 03-10-2014 1.5 "Love Walks In" -------- 02-28-2014 1.4.5 "Could This Be Magic?" - 02-12-2014 1.4.4 "Could This Be Magic?" - 01-06-2014 1.4.3 "Could This Be Magic?" - 12-20-2013 1.4.2 "Could This Be Magic?" - 12-18-2013 1.4.1 "Could This Be Magic?" - 11-27-2013 1.4 "Could This Be Magic?" - 11-21-2013 1.3.4 "Top of the World" ----- 10-29-2013 1.3.3 "Top of the World" ----- 10-09-2013 1.3.2 "Top of the World" ----- 09-19-2013 1.3.1 "Top of the World" ----- 09-16-2013 1.3 "Top of the World" ----- 09-13-2013 1.2.3 "Hear About It Later" -- 08-21-2013 1.2.2 "Hear About It Later" -- 07-05-2013 1.2.1 "Hear About It Later" -- 07-04-2013 1.2 "Right Now" ------------ 06-10-2013 1.1 "Mean Street" ---------- 04-02-2013 1.0 "Eruption" ------------- 02-01-2013 0.9 "Dreams" --------------- 11-30-2012 0.8 "Cathedral" ------------ 10-19-2012 0.7 "Panama" --------------- 09-06-2012 0.6 "Cabo" ----------------- 08-06-2012 0.5 "Amsterdam" ------------ 07-04-2012 0.4 "Unchained" ------------ 05-23-2012 0.3 "Baluchitherium" ------- 04-23-2012 0.0.2 Untitled 0.0.1 Untitled ansible-1.7.2/VERSION000066400000000000000000000000061241061774000142040ustar00rootroot000000000000001.7.2 ansible-1.7.2/bin/000077500000000000000000000000001241061774000137105ustar00rootroot00000000000000ansible-1.7.2/bin/ansible000077500000000000000000000175751241061774000152720ustar00rootroot00000000000000#!/usr/bin/env python # (c) 2012, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . ######################################################## import os import sys from ansible.runner import Runner import ansible.constants as C from ansible import utils from ansible import errors from ansible import callbacks from ansible import inventory ######################################################## class Cli(object): ''' code behind bin/ansible ''' # ---------------------------------------------- def __init__(self): self.stats = callbacks.AggregateStats() self.callbacks = callbacks.CliRunnerCallbacks() # ---------------------------------------------- def parse(self): ''' create an options parser for bin/ansible ''' parser = utils.base_parser( constants=C, runas_opts=True, subset_opts=True, async_opts=True, output_opts=True, connect_opts=True, check_opts=True, diff_opts=False, usage='%prog [options]' ) parser.add_option('-a', '--args', dest='module_args', help="module arguments", default=C.DEFAULT_MODULE_ARGS) parser.add_option('-m', '--module-name', dest='module_name', help="module name to execute (default=%s)" % C.DEFAULT_MODULE_NAME, default=C.DEFAULT_MODULE_NAME) options, args = parser.parse_args() self.callbacks.options = options if len(args) == 0 or len(args) > 1: parser.print_help() sys.exit(1) # su and sudo command line arguments need to be mutually exclusive if (options.su or options.su_user or options.ask_su_pass) and \ (options.sudo or options.sudo_user or options.ask_sudo_pass): parser.error("Sudo arguments ('--sudo', '--sudo-user', and '--ask-sudo-pass') " "and su arguments ('-su', '--su-user', and '--ask-su-pass') are " "mutually exclusive") if (options.ask_vault_pass and options.vault_password_file): parser.error("--ask-vault-pass and --vault-password-file are mutually exclusive") return (options, args) # ---------------------------------------------- def run(self, options, args): ''' use Runner lib to do SSH things ''' pattern = args[0] """ inventory_manager = inventory.Inventory(options.inventory) if options.subset: inventory_manager.subset(options.subset) hosts = inventory_manager.list_hosts(pattern) if len(hosts) == 0: callbacks.display("No hosts matched", stderr=True) sys.exit(0) if options.listhosts: for host in hosts: callbacks.display(' %s' % host) sys.exit(0) if ((options.module_name == 'command' or options.module_name == 'shell') and not options.module_args): callbacks.display("No argument passed to %s module" % options.module_name, color='red', stderr=True) sys.exit(1) """ sshpass = None sudopass = None su_pass = None vault_pass = None options.ask_pass = options.ask_pass or C.DEFAULT_ASK_PASS # Never ask for an SSH password when we run with local connection if options.connection == "local": options.ask_pass = False options.ask_sudo_pass = options.ask_sudo_pass or C.DEFAULT_ASK_SUDO_PASS options.ask_su_pass = options.ask_su_pass or C.DEFAULT_ASK_SU_PASS options.ask_vault_pass = options.ask_vault_pass or C.DEFAULT_ASK_VAULT_PASS (sshpass, sudopass, su_pass, vault_pass) = utils.ask_passwords(ask_pass=options.ask_pass, ask_sudo_pass=options.ask_sudo_pass, ask_su_pass=options.ask_su_pass, ask_vault_pass=options.ask_vault_pass) # read vault_pass from a file if not options.ask_vault_pass and options.vault_password_file: vault_pass = utils.read_vault_file(options.vault_password_file) inventory_manager = inventory.Inventory(options.inventory, vault_password=vault_pass) if options.subset: inventory_manager.subset(options.subset) hosts = inventory_manager.list_hosts(pattern) if len(hosts) == 0: callbacks.display("No hosts matched", stderr=True) sys.exit(0) if options.listhosts: for host in hosts: callbacks.display(' %s' % host) sys.exit(0) if ((options.module_name == 'command' or options.module_name == 'shell') and not options.module_args): callbacks.display("No argument passed to %s module" % options.module_name, color='red', stderr=True) sys.exit(1) if options.su_user or options.ask_su_pass: options.su = True options.sudo_user = options.sudo_user or C.DEFAULT_SUDO_USER options.su_user = options.su_user or C.DEFAULT_SU_USER if options.tree: utils.prepare_writeable_dir(options.tree) runner = Runner( module_name=options.module_name, module_path=options.module_path, module_args=options.module_args, remote_user=options.remote_user, remote_pass=sshpass, inventory=inventory_manager, timeout=options.timeout, private_key_file=options.private_key_file, forks=options.forks, pattern=pattern, callbacks=self.callbacks, sudo=options.sudo, sudo_pass=sudopass, sudo_user=options.sudo_user, transport=options.connection, subset=options.subset, check=options.check, diff=options.check, su=options.su, su_pass=su_pass, su_user=options.su_user, vault_pass=vault_pass ) if options.seconds: callbacks.display("background launch...\n\n", color='cyan') results, poller = runner.run_async(options.seconds) results = self.poll_while_needed(poller, options) else: results = runner.run() return (runner, results) # ---------------------------------------------- def poll_while_needed(self, poller, options): ''' summarize results from Runner ''' # BACKGROUND POLL LOGIC when -B and -P are specified if options.seconds and options.poll_interval > 0: poller.wait(options.seconds, options.poll_interval) return poller.results ######################################################## if __name__ == '__main__': callbacks.display("", log_only=True) callbacks.display(" ".join(sys.argv), log_only=True) callbacks.display("", log_only=True) cli = Cli() (options, args) = cli.parse() try: (runner, results) = cli.run(options, args) for result in results['contacted'].values(): if 'failed' in result or result.get('rc', 0) != 0: sys.exit(2) if results['dark']: sys.exit(3) except errors.AnsibleError, e: # Generic handler for ansible specific errors callbacks.display("ERROR: %s" % str(e), stderr=True, color='red') sys.exit(1) ansible-1.7.2/bin/ansible-doc000077500000000000000000000225061241061774000160230ustar00rootroot00000000000000#!/usr/bin/env python # (c) 2012, Jan-Piet Mens # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . # import os import sys import textwrap import re import optparse import datetime import subprocess from ansible import utils from ansible.utils import module_docs import ansible.constants as C from ansible.utils import version import traceback MODULEDIR = C.DEFAULT_MODULE_PATH BLACKLIST_EXTS = ('.swp', '.bak', '~', '.rpm') _ITALIC = re.compile(r"I\(([^)]+)\)") _BOLD = re.compile(r"B\(([^)]+)\)") _MODULE = re.compile(r"M\(([^)]+)\)") _URL = re.compile(r"U\(([^)]+)\)") _CONST = re.compile(r"C\(([^)]+)\)") PAGER = 'less' LESS_OPTS = 'FRSX' # -F (quit-if-one-screen) -R (allow raw ansi control chars) # -S (chop long lines) -X (disable termcap init and de-init) def pager_print(text): ''' just print text ''' print text def pager_pipe(text, cmd): ''' pipe text through a pager ''' if 'LESS' not in os.environ: os.environ['LESS'] = LESS_OPTS try: cmd = subprocess.Popen(cmd, shell=True, stdin=subprocess.PIPE, stdout=sys.stdout) cmd.communicate(input=text) except IOError: pass except KeyboardInterrupt: pass def pager(text): ''' find reasonable way to display text ''' # this is a much simpler form of what is in pydoc.py if not sys.stdout.isatty(): pager_print(text) elif 'PAGER' in os.environ: if sys.platform == 'win32': pager_print(text) else: pager_pipe(text, os.environ['PAGER']) elif hasattr(os, 'system') and os.system('(less) 2> /dev/null') == 0: pager_pipe(text, 'less') else: pager_print(text) def tty_ify(text): t = _ITALIC.sub("`" + r"\1" + "'", text) # I(word) => `word' t = _BOLD.sub("*" + r"\1" + "*", t) # B(word) => *word* t = _MODULE.sub("[" + r"\1" + "]", t) # M(word) => [word] t = _URL.sub(r"\1", t) # U(word) => word t = _CONST.sub("`" + r"\1" + "'", t) # C(word) => `word' return t def get_man_text(doc): opt_indent=" " text = [] text.append("> %s\n" % doc['module'].upper()) desc = "".join(doc['description']) text.append("%s\n" % textwrap.fill(tty_ify(desc), initial_indent=" ", subsequent_indent=" ")) if 'option_keys' in doc and len(doc['option_keys']) > 0: text.append("Options (= is mandatory):\n") for o in sorted(doc['option_keys']): opt = doc['options'][o] if opt.get('required', False): opt_leadin = "=" else: opt_leadin = "-" text.append("%s %s" % (opt_leadin, o)) desc = "".join(opt['description']) if 'choices' in opt: choices = ", ".join(str(i) for i in opt['choices']) desc = desc + " (Choices: " + choices + ")" if 'default' in opt: default = str(opt['default']) desc = desc + " [Default: " + default + "]" text.append("%s\n" % textwrap.fill(tty_ify(desc), initial_indent=opt_indent, subsequent_indent=opt_indent)) if 'notes' in doc and len(doc['notes']) > 0: notes = "".join(doc['notes']) text.append("Notes:%s\n" % textwrap.fill(tty_ify(notes), initial_indent=" ", subsequent_indent=opt_indent)) if 'requirements' in doc and doc['requirements'] is not None and len(doc['requirements']) > 0: req = ", ".join(doc['requirements']) text.append("Requirements:%s\n" % textwrap.fill(tty_ify(req), initial_indent=" ", subsequent_indent=opt_indent)) if 'examples' in doc and len(doc['examples']) > 0: text.append("Example%s:\n" % ('' if len(doc['examples']) < 2 else 's')) for ex in doc['examples']: text.append("%s\n" % (ex['code'])) if 'plainexamples' in doc and doc['plainexamples'] is not None: text.append(doc['plainexamples']) text.append('') return "\n".join(text) def get_snippet_text(doc): text = [] desc = tty_ify("".join(doc['short_description'])) text.append("- name: %s" % (desc)) text.append(" action: %s" % (doc['module'])) for o in sorted(doc['options'].keys()): opt = doc['options'][o] desc = tty_ify("".join(opt['description'])) if opt.get('required', False): s = o + "=" else: s = o text.append(" %-20s # %s" % (s, desc)) text.append('') return "\n".join(text) def get_module_list_text(module_list): text = [] for module in sorted(set(module_list)): if module in module_docs.BLACKLIST_MODULES: continue filename = utils.plugins.module_finder.find_plugin(module) if filename is None: continue if filename.endswith(".ps1"): continue if os.path.isdir(filename): continue try: doc, plainexamples = module_docs.get_docstring(filename) desc = tty_ify(doc.get('short_description', '?')) if len(desc) > 55: desc = desc + '...' text.append("%-20s %-60.60s" % (module, desc)) except: traceback.print_exc() sys.stderr.write("ERROR: module %s has a documentation error formatting or is missing documentation\n" % module) return "\n".join(text) def main(): p = optparse.OptionParser( version=version("%prog"), usage='usage: %prog [options] [module...]', description='Show Ansible module documentation', ) p.add_option("-M", "--module-path", action="store", dest="module_path", default=MODULEDIR, help="Ansible modules/ directory") p.add_option("-l", "--list", action="store_true", default=False, dest='list_dir', help='List available modules') p.add_option("-s", "--snippet", action="store_true", default=False, dest='show_snippet', help='Show playbook snippet for specified module(s)') p.add_option('-v', action='version', help='Show version number and exit') (options, args) = p.parse_args() if options.module_path is not None: for i in options.module_path.split(os.pathsep): utils.plugins.module_finder.add_directory(i) if options.list_dir: # list all modules paths = utils.plugins.module_finder._get_paths() module_list = [] for path in paths: # os.system("ls -C %s" % (path)) if os.path.isdir(path): for module in os.listdir(path): if any(module.endswith(x) for x in BLACKLIST_EXTS): continue module_list.append(module) pager(get_module_list_text(module_list)) sys.exit() if len(args) == 0: p.print_help() def print_paths(finder): ''' Returns a string suitable for printing of the search path ''' # Uses a list to get the order right ret = [] for i in finder._get_paths(): if i not in ret: ret.append(i) return os.pathsep.join(ret) text = '' for module in args: filename = utils.plugins.module_finder.find_plugin(module) if filename is None: sys.stderr.write("module %s not found in %s\n" % (module, print_paths(utils.plugins.module_finder))) continue if any(filename.endswith(x) for x in BLACKLIST_EXTS): continue try: doc, plainexamples = module_docs.get_docstring(filename) except: traceback.print_exc() sys.stderr.write("ERROR: module %s has a documentation error formatting or is missing documentation\n" % module) continue if doc is not None: all_keys = [] for (k,v) in doc['options'].iteritems(): all_keys.append(k) all_keys = sorted(all_keys) doc['option_keys'] = all_keys doc['filename'] = filename doc['docuri'] = doc['module'].replace('_', '-') doc['now_date'] = datetime.date.today().strftime('%Y-%m-%d') doc['plainexamples'] = plainexamples if options.show_snippet: text += get_snippet_text(doc) else: text += get_man_text(doc) else: # this typically means we couldn't even parse the docstring, not just that the YAML is busted, # probably a quoting issue. sys.stderr.write("ERROR: module %s missing documentation (or could not parse documentation)\n" % module) pager(text) if __name__ == '__main__': main() ansible-1.7.2/bin/ansible-galaxy000077500000000000000000000735331241061774000165510ustar00rootroot00000000000000#!/usr/bin/env python ######################################################################## # # (C) 2013, James Cammarata # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . # ######################################################################## import datetime import json import os import os.path import shutil import sys import tarfile import tempfile import urllib import urllib2 import yaml from collections import defaultdict from distutils.version import LooseVersion from jinja2 import Environment from optparse import OptionParser import ansible.constants as C default_meta_template = """--- galaxy_info: author: {{ author }} description: {{description}} company: {{ company }} # Some suggested licenses: # - BSD (default) # - MIT # - GPLv2 # - GPLv3 # - Apache # - CC-BY license: {{ license }} min_ansible_version: {{ min_ansible_version }} # # Below are all platforms currently available. Just uncomment # the ones that apply to your role. If you don't see your # platform on this list, let us know and we'll get it added! # #platforms: {%- for platform,versions in platforms.iteritems() %} #- name: {{ platform }} # versions: # - all {%- for version in versions %} # - {{ version }} {%- endfor %} {%- endfor %} # # Below are all categories currently available. Just as with # the platforms above, uncomment those that apply to your role. # #categories: {%- for category in categories %} #- {{ category.name }} {%- endfor %} dependencies: [] # List your role dependencies here, one per line. Only # dependencies available via galaxy should be listed here. # Be sure to remove the '[]' above if you add dependencies # to this list. {% for dependency in dependencies %} #- {{ dependency }} {% endfor %} """ default_readme_template = """Role Name ========= A brief description of the role goes here. Requirements ------------ Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required. Role Variables -------------- A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well. Dependencies ------------ A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles. Example Playbook ---------------- Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too: - hosts: servers roles: - { role: username.rolename, x: 42 } License ------- BSD Author Information ------------------ An optional section for the role authors to include contact information, or a website (HTML is not allowed). """ #------------------------------------------------------------------------------------- # Utility functions for parsing actions/options #------------------------------------------------------------------------------------- VALID_ACTIONS = ("init", "info", "install", "list", "remove") def get_action(args): """ Get the action the user wants to execute from the sys argv list. """ for i in range(0,len(args)): arg = args[i] if arg in VALID_ACTIONS: del args[i] return arg return None def build_option_parser(action): """ Builds an option parser object based on the action the user wants to execute. """ usage = "usage: %%prog [%s] [--help] [options] ..." % "|".join(VALID_ACTIONS) epilog = "\nSee '%s --help' for more information on a specific command.\n\n" % os.path.basename(sys.argv[0]) OptionParser.format_epilog = lambda self, formatter: self.epilog parser = OptionParser(usage=usage, epilog=epilog) if not action: parser.print_help() sys.exit() # options for all actions # - none yet # options specific to actions if action == "info": parser.set_usage("usage: %prog info [options] role_name[,version]") elif action == "init": parser.set_usage("usage: %prog init [options] role_name") parser.add_option( '-p', '--init-path', dest='init_path', default="./", help='The path in which the skeleton role will be created. ' 'The default is the current working directory.') elif action == "install": parser.set_usage("usage: %prog install [options] [-r FILE | role_name(s)[,version] | tar_file(s)]") parser.add_option( '-i', '--ignore-errors', dest='ignore_errors', action='store_true', default=False, help='Ignore errors and continue with the next specified role.') parser.add_option( '-n', '--no-deps', dest='no_deps', action='store_true', default=False, help='Don\'t download roles listed as dependencies') parser.add_option( '-r', '--role-file', dest='role_file', help='A file containing a list of roles to be imported') elif action == "remove": parser.set_usage("usage: %prog remove role1 role2 ...") elif action == "list": parser.set_usage("usage: %prog list [role_name]") # options that apply to more than one action if action != "init": parser.add_option( '-p', '--roles-path', dest='roles_path', default=C.DEFAULT_ROLES_PATH, help='The path to the directory containing your roles. ' 'The default is the roles_path configured in your ' 'ansible.cfg file (/etc/ansible/roles if not configured)') if action in ("info","init","install"): parser.add_option( '-s', '--server', dest='api_server', default="galaxy.ansible.com", help='The API server destination') if action in ("init","install"): parser.add_option( '-f', '--force', dest='force', action='store_true', default=False, help='Force overwriting an existing role') # done, return the parser return parser def get_opt(options, k, defval=""): """ Returns an option from an Optparse values instance. """ try: data = getattr(options, k) except: return defval if k == "roles_path": if os.pathsep in data: data = data.split(os.pathsep)[0] return data def exit_without_ignore(options, rc=1): """ Exits with the specified return code unless the option --ignore-errors was specified """ if not get_opt(options, "ignore_errors", False): print 'You can use --ignore-errors to skip failed roles.' sys.exit(rc) #------------------------------------------------------------------------------------- # Galaxy API functions #------------------------------------------------------------------------------------- def api_get_config(api_server): """ Fetches the Galaxy API current version to ensure the API server is up and reachable. """ try: url = 'https://%s/api/' % api_server data = json.load(urllib2.urlopen(url)) if not data.get("current_version",None): return None else: return data except: return None def api_lookup_role_by_name(api_server, role_name): """ Uses the Galaxy API to do a lookup on the role owner/name. """ role_name = urllib.quote(role_name) try: parts = role_name.split(".") user_name = ".".join(parts[0:-1]) role_name = parts[-1] print " downloading role '%s', owned by %s" % (role_name, user_name) except: parser.print_help() print "Invalid role name (%s). You must specify username.rolename" % role_name sys.exit(1) url = 'https://%s/api/v1/roles/?owner__username=%s&name=%s' % (api_server,user_name,role_name) try: data = json.load(urllib2.urlopen(url)) if len(data["results"]) == 0: return None else: return data["results"][0] except: return None def api_fetch_role_related(api_server, related, role_id): """ Uses the Galaxy API to fetch the list of related items for the given role. The url comes from the 'related' field of the role. """ try: url = 'https://%s/api/v1/roles/%d/%s/?page_size=50' % (api_server, int(role_id), related) data = json.load(urllib2.urlopen(url)) results = data['results'] done = (data.get('next', None) == None) while not done: url = 'https://%s%s' % (api_server, data['next']) print url data = json.load(urllib2.urlopen(url)) results += data['results'] done = (data.get('next', None) == None) return results except: return None def api_get_list(api_server, what): """ Uses the Galaxy API to fetch the list of items specified. """ try: url = 'https://%s/api/v1/%s/?page_size' % (api_server, what) data = json.load(urllib2.urlopen(url)) if "results" in data: results = data['results'] else: results = data done = True if "next" in data: done = (data.get('next', None) == None) while not done: url = 'https://%s%s' % (api_server, data['next']) print url data = json.load(urllib2.urlopen(url)) results += data['results'] done = (data.get('next', None) == None) return results except: print " - failed to download the %s list" % what return None #------------------------------------------------------------------------------------- # Role utility functions #------------------------------------------------------------------------------------- def get_role_path(role_name, options): """ Returns the role path based on the roles_path option and the role name. """ roles_path = get_opt(options,'roles_path') roles_path = os.path.join(roles_path, role_name) roles_path = os.path.expanduser(roles_path) return roles_path def get_role_metadata(role_name, options): """ Returns the metadata as YAML, if the file 'meta/main.yml' exists in the specified role_path """ role_path = os.path.join(get_role_path(role_name, options), 'meta/main.yml') try: if os.path.isfile(role_path): f = open(role_path, 'r') meta_data = yaml.safe_load(f) f.close() return meta_data else: return None except: return None def get_galaxy_install_info(role_name, options): """ Returns the YAML data contained in 'meta/.galaxy_install_info', if it exists. """ try: info_path = os.path.join(get_role_path(role_name, options), 'meta/.galaxy_install_info') if os.path.isfile(info_path): f = open(info_path, 'r') info_data = yaml.safe_load(f) f.close() return info_data else: return None except: return None def write_galaxy_install_info(role_name, role_version, options): """ Writes a YAML-formatted file to the role's meta/ directory (named .galaxy_install_info) which contains some information we can use later for commands like 'list' and 'info'. """ info = dict( version = role_version, install_date = datetime.datetime.utcnow().strftime("%c"), ) try: info_path = os.path.join(get_role_path(role_name, options), 'meta/.galaxy_install_info') f = open(info_path, 'w+') info_data = yaml.safe_dump(info, f) f.close() except: return False return True def remove_role(role_name, options): """ Removes the specified role from the roles path. There is a sanity check to make sure there's a meta/main.yml file at this path so the user doesn't blow away random directories """ if get_role_metadata(role_name, options): role_path = get_role_path(role_name, options) shutil.rmtree(role_path) return True else: return False def fetch_role(role_name, target, role_data, options): """ Downloads the archived role from github to a temp location, extracts it, and then copies the extracted role to the role library path. """ # first grab the file and save it to a temp location archive_url = 'https://github.com/%s/%s/archive/%s.tar.gz' % (role_data["github_user"], role_data["github_repo"], target) print " - downloading role from %s" % archive_url try: url_file = urllib2.urlopen(archive_url) temp_file = tempfile.NamedTemporaryFile(delete=False) data = url_file.read() while data: temp_file.write(data) data = url_file.read() temp_file.close() return temp_file.name except Exception, e: # TODO: better urllib2 error handling for error # messages that are more exact print "Error: failed to download the file." return False def install_role(role_name, role_version, role_filename, options): # the file is a tar, so open it that way and extract it # to the specified (or default) roles directory if not tarfile.is_tarfile(role_filename): print "Error: the file downloaded was not a tar.gz" return False else: role_tar_file = tarfile.open(role_filename, "r:gz") # verify the role's meta file meta_file = None members = role_tar_file.getmembers() # next find the metadata file for member in members: if "/meta/main.yml" in member.name: meta_file = member break if not meta_file: print "Error: this role does not appear to have a meta/main.yml file." return False else: try: meta_file_data = yaml.safe_load(role_tar_file.extractfile(meta_file)) except: print "Error: this role does not appear to have a valid meta/main.yml file." return False # we strip off the top-level directory for all of the files contained within # the tar file here, since the default is 'github_repo-target', and change it # to the specified role's name role_path = os.path.join(get_opt(options, 'roles_path', '/etc/ansible/roles'), role_name) role_path = os.path.expanduser(role_path) print " - extracting %s to %s" % (role_name, role_path) try: if os.path.exists(role_path): if not os.path.isdir(role_path): print "Error: the specified roles path exists and is not a directory." return False elif not get_opt(options, "force", False): print "Error: the specified role %s appears to already exist. Use --force to replace it." % role_name return False else: # using --force, remove the old path if not remove_role(role_name, options): print "Error: %s doesn't appear to contain a role." % role_path print "Please remove this directory manually if you really want to put the role here." return False else: os.makedirs(role_path) # now we do the actual extraction to the role_path for member in members: # we only extract files, and remove any relative path # bits that might be in the file for security purposes # and drop the leading directory, as mentioned above if member.isreg(): parts = member.name.split("/")[1:] final_parts = [] for part in parts: if part != '..' and '~' not in part and '$' not in part: final_parts.append(part) member.name = os.path.join(*final_parts) role_tar_file.extract(member, role_path) # write out the install info file for later use write_galaxy_install_info(role_name, role_version, options) except OSError, e: print "Error: you do not have permission to modify files in %s" % role_path return False # return the parsed yaml metadata print "%s was installed successfully" % role_name return meta_file_data #------------------------------------------------------------------------------------- # Action functions #------------------------------------------------------------------------------------- def execute_init(args, options, parser): """ Executes the init action, which creates the skeleton framework of a role that complies with the galaxy metadata format. """ init_path = get_opt(options, 'init_path', './') api_server = get_opt(options, "api_server", "galaxy.ansible.com") force = get_opt(options, 'force', False) api_config = api_get_config(api_server) if not api_config: print "The API server (%s) is not responding, please try again later." % api_server sys.exit(1) try: role_name = args.pop(0).strip() if role_name == "": raise Exception("") role_path = os.path.join(init_path, role_name) if os.path.exists(role_path): if os.path.isfile(role_path): print "The path %s already exists, but is a file - aborting" % role_path sys.exit(1) elif not force: print "The directory %s already exists." % role_path print "" print "You can use --force to re-initialize this directory,\n" + \ "however it will reset any main.yml files that may have\n" + \ "been modified there already." sys.exit(1) except Exception, e: parser.print_help() print "No role name specified for init" sys.exit(1) ROLE_DIRS = ('defaults','files','handlers','meta','tasks','templates','vars') # create the default README.md if not os.path.exists(role_path): os.makedirs(role_path) readme_path = os.path.join(role_path, "README.md") f = open(readme_path, "wb") f.write(default_readme_template) f.close for dir in ROLE_DIRS: dir_path = os.path.join(init_path, role_name, dir) main_yml_path = os.path.join(dir_path, 'main.yml') # create the directory if it doesn't exist already if not os.path.exists(dir_path): os.makedirs(dir_path) # now create the main.yml file for that directory if dir == "meta": # create a skeleton meta/main.yml with a valid galaxy_info # datastructure in place, plus with all of the available # tags/platforms included (but commented out) and the # dependencies section platforms = api_get_list(api_server, "platforms") if not platforms: platforms = [] categories = api_get_list(api_server, "categories") if not categories: categories = [] # group the list of platforms from the api based # on their names, with the release field being # appended to a list of versions platform_groups = defaultdict(list) for platform in platforms: platform_groups[platform['name']].append(platform['release']) platform_groups[platform['name']].sort() inject = dict( author = 'your name', company = 'your company (optional)', license = 'license (GPLv2, CC-BY, etc)', min_ansible_version = '1.2', platforms = platform_groups, categories = categories, ) rendered_meta = Environment().from_string(default_meta_template).render(inject) f = open(main_yml_path, 'w') f.write(rendered_meta) f.close() pass elif dir not in ('files','templates'): # just write a (mostly) empty YAML file for main.yml f = open(main_yml_path, 'w') f.write('---\n# %s file for %s\n' % (dir,role_name)) f.close() print "%s was created successfully" % role_name def execute_info(args, options, parser): """ Executes the info action. This action prints out detailed information about an installed role as well as info available from the galaxy API. """ pass def execute_install(args, options, parser): """ Executes the installation action. The args list contains the roles to be installed, unless -f was specified. The list of roles can be a name (which will be downloaded via the galaxy API and github), or it can be a local .tar.gz file. """ role_file = get_opt(options, "role_file", None) api_server = get_opt(options, "api_server", "galaxy.ansible.com") no_deps = get_opt(options, "no_deps", False) if len(args) == 0 and not role_file: # the user needs to specify one of either --role-file # or specify a single user/role name parser.print_help() print "You must specify a user/role name or a roles file" sys.exit() elif len(args) == 1 and role_file: # using a role file is mutually exclusive of specifying # the role name on the command line parser.print_help() print "Please specify a user/role name, or a roles file, but not both" sys.exit(1) api_config = api_get_config(api_server) if not api_config: print "The API server (%s) is not responding, please try again later." % api_server sys.exit(1) roles_done = [] if role_file: # roles listed in a file, one per line # so we'll go through and grab them all f = open(role_file, 'r') roles_left = f.readlines() f.close() else: # roles were specified directly, so we'll just go out grab them # (and their dependencies, unless the user doesn't want us to). roles_left = args while len(roles_left) > 0: # query the galaxy API for the role data role_name = roles_left.pop(0).strip() role_version = None if role_name == "" or role_name.startswith("#"): continue elif ',' in role_name: role_name,role_version = role_name.split(',',1) role_name = role_name.strip() role_version = role_version.strip() if os.path.isfile(role_name): # installing a local tar.gz tar_file = role_name role_name = os.path.basename(role_name).replace('.tar.gz','') if tarfile.is_tarfile(tar_file): print " - installing %s as %s" % (tar_file, role_name) if not install_role(role_name, role_version, tar_file, options): exit_without_ignore(options) else: print "%s (%s) was NOT installed successfully." % (role_name,tar_file) exit_without_ignore(options) else: # installing remotely role_data = api_lookup_role_by_name(api_server, role_name) if not role_data: print "Sorry, %s was not found on %s." % (role_name, api_server) continue role_versions = api_fetch_role_related(api_server, 'versions', role_data['id']) if not role_version: # convert the version names to LooseVersion objects # and sort them to get the latest version. If there # are no versions in the list, we'll grab the head # of the master branch if len(role_versions) > 0: loose_versions = [LooseVersion(a.get('name',None)) for a in role_versions] loose_versions.sort() role_version = str(loose_versions[-1]) else: role_version = 'master' print " no version specified, installing %s" % role_version else: if role_versions and role_version not in [a.get('name',None) for a in role_versions]: print "The specified version (%s) was not found in the list of available versions." % role_version exit_without_ignore(options) continue # download the role. if --no-deps was specified, we stop here, # otherwise we recursively grab roles and all of their deps. tmp_file = fetch_role(role_name, role_version, role_data, options) if tmp_file and install_role(role_name, role_version, tmp_file, options): # we're done with the temp file, clean it up os.unlink(tmp_file) # install dependencies, if we want them if not no_deps: role_dependencies = role_data['summary_fields']['dependencies'] # api_fetch_role_related(api_server, 'dependencies', role_data['id']) for dep_name in role_dependencies: #dep_name = "%s.%s" % (dep['owner'], dep['name']) if not get_role_metadata(dep_name, options): print ' adding dependency: %s' % dep_name roles_left.append(dep_name) else: print ' dependency %s is already installed, skipping.' % dep_name else: if tmp_file: os.unlink(tmp_file) print "%s was NOT installed successfully." % role_name exit_without_ignore(options) sys.exit(0) def execute_remove(args, options, parser): """ Executes the remove action. The args list contains the list of roles to be removed. This list can contain more than one role. """ if len(args) == 0: parser.print_help() print 'You must specify at least one role to remove.' sys.exit() for role in args: if get_role_metadata(role, options): if remove_role(role, options): print 'successfully removed %s' % role else: print "failed to remove role: %s" % role else: print '%s is not installed, skipping.' % role sys.exit(0) def execute_list(args, options, parser): """ Executes the list action. The args list can contain zero or one role. If one is specified, only that role will be shown, otherwise all roles in the specified directory will be shown. """ if len(args) > 1: print "Please specify only one role to list, or specify no roles to see a full list" sys.exit(1) if len(args) == 1: # show only the request role, if it exists role_name = args[0] metadata = get_role_metadata(role_name, options) if metadata: install_info = get_galaxy_install_info(role_name, options) version = None if install_info: version = install_info.get("version", None) if not version: version = "(unknown version)" # show some more info about single roles here print " %s, %s" % (role_name, version) else: print "The role %s was not found" % role_name else: # show all valid roles in the roles_path directory roles_path = get_opt(options, 'roles_path') roles_path = os.path.expanduser(roles_path) if not os.path.exists(roles_path): parser.print_help() print "The path %s does not exist. Please specify a valid path with --roles-path" % roles_path sys.exit(1) elif not os.path.isdir(roles_path): print "%s exists, but it is not a directory. Please specify a valid path with --roles-path" % roles_path parser.print_help() sys.exit(1) path_files = os.listdir(roles_path) for path_file in path_files: if get_role_metadata(path_file, options): install_info = get_galaxy_install_info(path_file, options) version = None if install_info: version = install_info.get("version", None) if not version: version = "(unknown version)" print " %s, %s" % (path_file, version) sys.exit(0) #------------------------------------------------------------------------------------- # The main entry point #------------------------------------------------------------------------------------- def main(): # parse the CLI options action = get_action(sys.argv) parser = build_option_parser(action) (options, args) = parser.parse_args() # execute the desired action if 1: #try: fn = globals()["execute_%s" % action] fn(args, options, parser) #except KeyError, e: # print "Error: %s is not a valid action. Valid actions are: %s" % (action, ", ".join(VALID_ACTIONS)) # sys.exit(1) if __name__ == "__main__": main() ansible-1.7.2/bin/ansible-playbook000077500000000000000000000301741241061774000170760ustar00rootroot00000000000000#!/usr/bin/env python # (C) 2012, Michael DeHaan, # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . ####################################################### #__requires__ = ['ansible'] #import pkg_resources import sys import os import stat import ansible.playbook import ansible.constants as C import ansible.utils.template from ansible import errors from ansible import callbacks from ansible import utils from ansible.color import ANSIBLE_COLOR, stringc from ansible.callbacks import display def colorize(lead, num, color): """ Print 'lead' = 'num' in 'color' """ if num != 0 and ANSIBLE_COLOR and color is not None: return "%s%s%-15s" % (stringc(lead, color), stringc("=", color), stringc(str(num), color)) else: return "%s=%-4s" % (lead, str(num)) def hostcolor(host, stats, color=True): if ANSIBLE_COLOR and color: if stats['failures'] != 0 or stats['unreachable'] != 0: return "%-37s" % stringc(host, 'red') elif stats['changed'] != 0: return "%-37s" % stringc(host, 'yellow') else: return "%-37s" % stringc(host, 'green') return "%-26s" % host def main(args): ''' run ansible-playbook operations ''' # create parser for CLI options parser = utils.base_parser( constants=C, usage = "%prog playbook.yml", connect_opts=True, runas_opts=True, subset_opts=True, check_opts=True, diff_opts=True ) #parser.add_option('--vault-password', dest="vault_password", # help="password for vault encrypted files") parser.add_option('-e', '--extra-vars', dest="extra_vars", action="append", help="set additional variables as key=value or YAML/JSON", default=[]) parser.add_option('-t', '--tags', dest='tags', default='all', help="only run plays and tasks tagged with these values") parser.add_option('--skip-tags', dest='skip_tags', help="only run plays and tasks whose tags do not match these values") parser.add_option('--syntax-check', dest='syntax', action='store_true', help="perform a syntax check on the playbook, but do not execute it") parser.add_option('--list-tasks', dest='listtasks', action='store_true', help="list all tasks that would be executed") parser.add_option('--step', dest='step', action='store_true', help="one-step-at-a-time: confirm each task before running") parser.add_option('--start-at-task', dest='start_at', help="start the playbook at the task matching this name") parser.add_option('--force-handlers', dest='force_handlers', action='store_true', help="run handlers even if a task fails") options, args = parser.parse_args(args) if len(args) == 0: parser.print_help(file=sys.stderr) return 1 # su and sudo command line arguments need to be mutually exclusive if (options.su or options.su_user or options.ask_su_pass) and \ (options.sudo or options.sudo_user or options.ask_sudo_pass): parser.error("Sudo arguments ('--sudo', '--sudo-user', and '--ask-sudo-pass') " "and su arguments ('-su', '--su-user', and '--ask-su-pass') are " "mutually exclusive") if (options.ask_vault_pass and options.vault_password_file): parser.error("--ask-vault-pass and --vault-password-file are mutually exclusive") sshpass = None sudopass = None su_pass = None vault_pass = None options.ask_vault_pass = options.ask_vault_pass or C.DEFAULT_ASK_VAULT_PASS if options.listhosts or options.syntax or options.listtasks: (_, _, _, vault_pass) = utils.ask_passwords(ask_vault_pass=options.ask_vault_pass) else: options.ask_pass = options.ask_pass or C.DEFAULT_ASK_PASS # Never ask for an SSH password when we run with local connection if options.connection == "local": options.ask_pass = False options.ask_sudo_pass = options.ask_sudo_pass or C.DEFAULT_ASK_SUDO_PASS options.ask_su_pass = options.ask_su_pass or C.DEFAULT_ASK_SU_PASS (sshpass, sudopass, su_pass, vault_pass) = utils.ask_passwords(ask_pass=options.ask_pass, ask_sudo_pass=options.ask_sudo_pass, ask_su_pass=options.ask_su_pass, ask_vault_pass=options.ask_vault_pass) options.sudo_user = options.sudo_user or C.DEFAULT_SUDO_USER options.su_user = options.su_user or C.DEFAULT_SU_USER # read vault_pass from a file if not options.ask_vault_pass and options.vault_password_file: vault_pass = utils.read_vault_file(options.vault_password_file) extra_vars = {} for extra_vars_opt in options.extra_vars: if extra_vars_opt.startswith("@"): # Argument is a YAML file (JSON is a subset of YAML) extra_vars = utils.combine_vars(extra_vars, utils.parse_yaml_from_file(extra_vars_opt[1:], vault_password=vault_pass)) elif extra_vars_opt and extra_vars_opt[0] in '[{': # Arguments as YAML extra_vars = utils.combine_vars(extra_vars, utils.parse_yaml(extra_vars_opt)) else: # Arguments as Key-value extra_vars = utils.combine_vars(extra_vars, utils.parse_kv(extra_vars_opt)) only_tags = options.tags.split(",") skip_tags = options.skip_tags if options.skip_tags is not None: skip_tags = options.skip_tags.split(",") for playbook in args: if not os.path.exists(playbook): raise errors.AnsibleError("the playbook: %s could not be found" % playbook) if not (os.path.isfile(playbook) or stat.S_ISFIFO(os.stat(playbook).st_mode)): raise errors.AnsibleError("the playbook: %s does not appear to be a file" % playbook) inventory = ansible.inventory.Inventory(options.inventory, vault_password=vault_pass) inventory.subset(options.subset) if len(inventory.list_hosts()) == 0: raise errors.AnsibleError("provided hosts list is empty") # run all playbooks specified on the command line for playbook in args: stats = callbacks.AggregateStats() playbook_cb = callbacks.PlaybookCallbacks(verbose=utils.VERBOSITY) if options.step: playbook_cb.step = options.step if options.start_at: playbook_cb.start_at = options.start_at runner_cb = callbacks.PlaybookRunnerCallbacks(stats, verbose=utils.VERBOSITY) pb = ansible.playbook.PlayBook( playbook=playbook, module_path=options.module_path, inventory=inventory, forks=options.forks, remote_user=options.remote_user, remote_pass=sshpass, callbacks=playbook_cb, runner_callbacks=runner_cb, stats=stats, timeout=options.timeout, transport=options.connection, sudo=options.sudo, sudo_user=options.sudo_user, sudo_pass=sudopass, extra_vars=extra_vars, private_key_file=options.private_key_file, only_tags=only_tags, skip_tags=skip_tags, check=options.check, diff=options.diff, su=options.su, su_pass=su_pass, su_user=options.su_user, vault_password=vault_pass, force_handlers=options.force_handlers ) if options.listhosts or options.listtasks or options.syntax: print '' print 'playbook: %s' % playbook print '' playnum = 0 for (play_ds, play_basedir) in zip(pb.playbook, pb.play_basedirs): playnum += 1 play = ansible.playbook.Play(pb, play_ds, play_basedir, vault_password=pb.vault_password) label = play.name hosts = pb.inventory.list_hosts(play.hosts) # Filter all tasks by given tags if pb.only_tags != 'all': if options.subset and not hosts: continue matched_tags, unmatched_tags = play.compare_tags(pb.only_tags) # Remove skipped tasks matched_tags = matched_tags - set(pb.skip_tags) unmatched_tags.discard('all') unknown_tags = ((set(pb.only_tags) | set(pb.skip_tags)) - (matched_tags | unmatched_tags)) if unknown_tags: continue if options.listhosts: print ' play #%d (%s): host count=%d' % (playnum, label, len(hosts)) for host in hosts: print ' %s' % host if options.listtasks: print ' play #%d (%s):' % (playnum, label) for task in play.tasks(): if (set(task.tags).intersection(pb.only_tags) and not set(task.tags).intersection(pb.skip_tags)): if getattr(task, 'name', None) is not None: # meta tasks have no names print ' %s' % task.name print '' continue if options.syntax: # if we've not exited by now then we are fine. print 'Playbook Syntax is fine' return 0 failed_hosts = [] unreachable_hosts = [] try: pb.run() hosts = sorted(pb.stats.processed.keys()) display(callbacks.banner("PLAY RECAP")) playbook_cb.on_stats(pb.stats) for h in hosts: t = pb.stats.summarize(h) if t['failures'] > 0: failed_hosts.append(h) if t['unreachable'] > 0: unreachable_hosts.append(h) retries = failed_hosts + unreachable_hosts if len(retries) > 0: filename = pb.generate_retry_inventory(retries) if filename: display(" to retry, use: --limit @%s\n" % filename) for h in hosts: t = pb.stats.summarize(h) display("%s : %s %s %s %s" % ( hostcolor(h, t), colorize('ok', t['ok'], 'green'), colorize('changed', t['changed'], 'yellow'), colorize('unreachable', t['unreachable'], 'red'), colorize('failed', t['failures'], 'red')), screen_only=True ) display("%s : %s %s %s %s" % ( hostcolor(h, t, False), colorize('ok', t['ok'], None), colorize('changed', t['changed'], None), colorize('unreachable', t['unreachable'], None), colorize('failed', t['failures'], None)), log_only=True ) print "" if len(failed_hosts) > 0: return 2 if len(unreachable_hosts) > 0: return 3 except errors.AnsibleError, e: display("ERROR: %s" % e, color='red') return 1 return 0 if __name__ == "__main__": display(" ", log_only=True) display(" ".join(sys.argv), log_only=True) display(" ", log_only=True) try: sys.exit(main(sys.argv[1:])) except errors.AnsibleError, e: display("ERROR: %s" % e, color='red', stderr=True) sys.exit(1) except KeyboardInterrupt, ke: display("ERROR: interrupted", color='red', stderr=True) sys.exit(1) ansible-1.7.2/bin/ansible-pull000077500000000000000000000210401241061774000162220ustar00rootroot00000000000000#!/usr/bin/env python # (c) 2012, Stephen Fromm # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . # # ansible-pull is a script that runs ansible in local mode # after checking out a playbooks directory from source repo. There is an # example playbook to bootstrap this script in the examples/ dir which # installs ansible and sets it up to run on cron. # usage: # ansible-pull -d /var/lib/ansible \ # -U http://example.net/content.git [-C production] \ # [path/playbook.yml] # # the -d and -U arguments are required; the -C argument is optional. # # ansible-pull accepts an optional argument to specify a playbook # location underneath the workdir and then searches the source repo # for playbooks in the following order, stopping at the first match: # # 1. $workdir/path/playbook.yml, if specified # 2. $workdir/$fqdn.yml # 3. $workdir/$hostname.yml # 4. $workdir/local.yml # # the source repo must contain at least one of these playbooks. import os import shutil import subprocess import sys import datetime import socket import random import time from ansible import utils from ansible.utils import cmd_functions from ansible import errors DEFAULT_REPO_TYPE = 'git' DEFAULT_PLAYBOOK = 'local.yml' PLAYBOOK_ERRORS = {1: 'File does not exist', 2: 'File is not readable'} VERBOSITY=0 def increment_debug(option, opt, value, parser): global VERBOSITY VERBOSITY += 1 def try_playbook(path): if not os.path.exists(path): return 1 if not os.access(path, os.R_OK): return 2 return 0 def select_playbook(path, args): playbook = None if len(args) > 0 and args[0] is not None: playbook = "%s/%s" % (path, args[0]) rc = try_playbook(playbook) if rc != 0: print >>sys.stderr, "%s: %s" % (playbook, PLAYBOOK_ERRORS[rc]) return None return playbook else: fqdn = socket.getfqdn() hostpb = "%s/%s.yml" % (path, fqdn) shorthostpb = "%s/%s.yml" % (path, fqdn.split('.')[0]) localpb = "%s/%s" % (path, DEFAULT_PLAYBOOK) errors = [] for pb in [hostpb, shorthostpb, localpb]: rc = try_playbook(pb) if rc == 0: playbook = pb break else: errors.append("%s: %s" % (pb, PLAYBOOK_ERRORS[rc])) if playbook is None: print >>sys.stderr, "\n".join(errors) return playbook def main(args): """ Set up and run a local playbook """ usage = "%prog [options] [playbook.yml]" parser = utils.SortedOptParser(usage=usage) parser.add_option('--purge', default=False, action='store_true', help='purge checkout after playbook run') parser.add_option('-o', '--only-if-changed', dest='ifchanged', default=False, action='store_true', help='only run the playbook if the repository has been updated') parser.add_option('-s', '--sleep', dest='sleep', default=None, help='sleep for random interval (between 0 and n number of seconds) before starting. this is a useful way to disperse git requests') parser.add_option('-f', '--force', dest='force', default=False, action='store_true', help='run the playbook even if the repository could ' 'not be updated') parser.add_option('-d', '--directory', dest='dest', default=None, help='directory to checkout repository to') #parser.add_option('-l', '--live', default=True, action='store_live', # help='Print the ansible-playbook output while running') parser.add_option('-U', '--url', dest='url', default=None, help='URL of the playbook repository') parser.add_option('-C', '--checkout', dest='checkout', help='branch/tag/commit to checkout. ' 'Defaults to behavior of repository module.') parser.add_option('-i', '--inventory-file', dest='inventory', help="location of the inventory host file") parser.add_option('-e', '--extra-vars', dest="extra_vars", action="append", help="set additional variables as key=value or YAML/JSON", default=[]) parser.add_option('-v', '--verbose', default=False, action="callback", callback=increment_debug, help='Pass -vvvv to ansible-playbook') parser.add_option('-m', '--module-name', dest='module_name', default=DEFAULT_REPO_TYPE, help='Module name used to check out repository. ' 'Default is %s.' % DEFAULT_REPO_TYPE) parser.add_option('--vault-password-file', dest='vault_password_file', help="vault password file") parser.add_option('-K', '--ask-sudo-pass', default=False, dest='ask_sudo_pass', action='store_true', help='ask for sudo password') options, args = parser.parse_args(args) hostname = socket.getfqdn() if not options.dest: # use a hostname dependent directory, in case of $HOME on nfs options.dest = utils.prepare_writeable_dir('~/.ansible/pull/%s' % hostname) options.dest = os.path.abspath(options.dest) if not options.url: parser.error("URL for repository not specified, use -h for help") return 1 now = datetime.datetime.now() print >>sys.stderr, now.strftime("Starting ansible-pull at %F %T") if not options.inventory: inv_opts = 'localhost,' else: inv_opts = options.inventory limit_opts = 'localhost:%s:127.0.0.1' % hostname repo_opts = "name=%s dest=%s" % (options.url, options.dest) if VERBOSITY == 0: base_opts = '-c local --limit "%s"' % limit_opts elif VERBOSITY > 0: debug_level = ''.join([ "v" for x in range(0, VERBOSITY) ]) base_opts = '-%s -c local --limit "%s"' % (debug_level, limit_opts) if options.checkout: repo_opts += ' version=%s' % options.checkout path = utils.plugins.module_finder.find_plugin(options.module_name) if path is None: sys.stderr.write("module '%s' not found.\n" % options.module_name) return 1 cmd = 'ansible all -i "%s" %s -m %s -a "%s"' % ( inv_opts, base_opts, options.module_name, repo_opts ) if options.sleep: try: secs = random.randint(0,int(options.sleep)); except ValueError: parser.error("%s is not a number." % options.sleep) return 1 print >>sys.stderr, "Sleeping for %d seconds..." % secs time.sleep(secs); # RUN THe CHECKOUT COMMAND rc, out, err = cmd_functions.run_cmd(cmd, live=True) if rc != 0: if options.force: print "Unable to update repository. Continuing with (forced) run of playbook." else: return rc elif options.ifchanged and '"changed": true' not in out: print "Repository has not changed, quitting." return 0 playbook = select_playbook(options.dest, args) if playbook is None: print >>sys.stderr, "Could not find a playbook to run." return 1 cmd = 'ansible-playbook %s %s' % (base_opts, playbook) if options.vault_password_file: cmd += " --vault-password-file=%s" % options.vault_password_file if options.inventory: cmd += ' -i "%s"' % options.inventory for ev in options.extra_vars: cmd += ' -e "%s"' % ev if options.ask_sudo_pass: cmd += ' -K' os.chdir(options.dest) # RUN THE PLAYBOOK COMMAND rc, out, err = cmd_functions.run_cmd(cmd, live=True) if options.purge: os.chdir('/') try: shutil.rmtree(options.dest) except Exception, e: print >>sys.stderr, "Failed to remove %s: %s" % (options.dest, str(e)) return rc if __name__ == '__main__': try: sys.exit(main(sys.argv[1:])) except KeyboardInterrupt, e: print >>sys.stderr, "Exit on user request.\n" sys.exit(1) ansible-1.7.2/bin/ansible-vault000077500000000000000000000155001241061774000164050ustar00rootroot00000000000000#!/usr/bin/env python # (c) 2014, James Tanner # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . # # ansible-pull is a script that runs ansible in local mode # after checking out a playbooks directory from source repo. There is an # example playbook to bootstrap this script in the examples/ dir which # installs ansible and sets it up to run on cron. #__requires__ = ['ansible'] #import pkg_resources import os import sys import traceback import ansible.constants as C from ansible import utils from ansible import errors from ansible.utils.vault import VaultEditor from optparse import OptionParser #------------------------------------------------------------------------------------- # Utility functions for parsing actions/options #------------------------------------------------------------------------------------- VALID_ACTIONS = ("create", "decrypt", "edit", "encrypt", "rekey") def build_option_parser(action): """ Builds an option parser object based on the action the user wants to execute. """ usage = "usage: %%prog [%s] [--help] [options] file_name" % "|".join(VALID_ACTIONS) epilog = "\nSee '%s --help' for more information on a specific command.\n\n" % os.path.basename(sys.argv[0]) OptionParser.format_epilog = lambda self, formatter: self.epilog parser = OptionParser(usage=usage, epilog=epilog) if not action: parser.print_help() sys.exit() # options for all actions #parser.add_option('-c', '--cipher', dest='cipher', default="AES256", help="cipher to use") parser.add_option('--debug', dest='debug', action="store_true", help="debug") parser.add_option('--vault-password-file', dest='password_file', help="vault password file", default=C.DEFAULT_VAULT_PASSWORD_FILE) # options specific to actions if action == "create": parser.set_usage("usage: %prog create [options] file_name") elif action == "decrypt": parser.set_usage("usage: %prog decrypt [options] file_name") elif action == "edit": parser.set_usage("usage: %prog edit [options] file_name") elif action == "encrypt": parser.set_usage("usage: %prog encrypt [options] file_name") elif action == "rekey": parser.set_usage("usage: %prog rekey [options] file_name") # done, return the parser return parser def get_action(args): """ Get the action the user wants to execute from the sys argv list. """ for i in range(0,len(args)): arg = args[i] if arg in VALID_ACTIONS: del args[i] return arg return None def get_opt(options, k, defval=""): """ Returns an option from an Optparse values instance. """ try: data = getattr(options, k) except: return defval if k == "roles_path": if os.pathsep in data: data = data.split(os.pathsep)[0] return data #------------------------------------------------------------------------------------- # Command functions #------------------------------------------------------------------------------------- def execute_create(args, options, parser): if len(args) > 1: raise errors.AnsibleError("'create' does not accept more than one filename") if not options.password_file: password, new_password = utils.ask_vault_passwords(ask_vault_pass=True, confirm_vault=True) else: password = utils.read_vault_file(options.password_file) cipher = 'AES256' if hasattr(options, 'cipher'): cipher = options.cipher this_editor = VaultEditor(cipher, password, args[0]) this_editor.create_file() def execute_decrypt(args, options, parser): if not options.password_file: password, new_password = utils.ask_vault_passwords(ask_vault_pass=True) else: password = utils.read_vault_file(options.password_file) cipher = 'AES256' if hasattr(options, 'cipher'): cipher = options.cipher for f in args: this_editor = VaultEditor(cipher, password, f) this_editor.decrypt_file() print "Decryption successful" def execute_edit(args, options, parser): if len(args) > 1: raise errors.AnsibleError("create does not accept more than one filename") if not options.password_file: password, new_password = utils.ask_vault_passwords(ask_vault_pass=True) else: password = utils.read_vault_file(options.password_file) cipher = None for f in args: this_editor = VaultEditor(cipher, password, f) this_editor.edit_file() def execute_encrypt(args, options, parser): if not options.password_file: password, new_password = utils.ask_vault_passwords(ask_vault_pass=True, confirm_vault=True) else: password = utils.read_vault_file(options.password_file) cipher = 'AES256' if hasattr(options, 'cipher'): cipher = options.cipher for f in args: this_editor = VaultEditor(cipher, password, f) this_editor.encrypt_file() print "Encryption successful" def execute_rekey(args, options, parser): if not options.password_file: password, __ = utils.ask_vault_passwords(ask_vault_pass=True) else: password = utils.read_vault_file(options.password_file) __, new_password = utils.ask_vault_passwords(ask_vault_pass=False, ask_new_vault_pass=True, confirm_new=True) cipher = None for f in args: this_editor = VaultEditor(cipher, password, f) this_editor.rekey_file(new_password) print "Rekey successful" #------------------------------------------------------------------------------------- # MAIN #------------------------------------------------------------------------------------- def main(): action = get_action(sys.argv) parser = build_option_parser(action) (options, args) = parser.parse_args() if not len(args): raise errors.AnsibleError( "The '%s' command requires a filename as the first argument" % action ) # execute the desired action try: fn = globals()["execute_%s" % action] fn(args, options, parser) except Exception, err: if options.debug: print traceback.format_exc() print "ERROR:",err sys.exit(1) if __name__ == "__main__": main() ansible-1.7.2/docs/000077500000000000000000000000001241061774000140705ustar00rootroot00000000000000ansible-1.7.2/docs/man/000077500000000000000000000000001241061774000146435ustar00rootroot00000000000000ansible-1.7.2/docs/man/.gitignore000066400000000000000000000000211241061774000166240ustar00rootroot00000000000000*.xml *.asciidoc ansible-1.7.2/docs/man/man1/000077500000000000000000000000001241061774000154775ustar00rootroot00000000000000ansible-1.7.2/docs/man/man1/ansible-doc.1000066400000000000000000000052551241061774000177500ustar00rootroot00000000000000'\" t .\" Title: ansible-doc .\" Author: :doctype:manpage .\" Generator: DocBook XSL Stylesheets v1.76.1 .\" Date: 05/26/2014 .\" Manual: System administration commands .\" Source: Ansible 1.7 .\" Language: English .\" .TH "ANSIBLE\-DOC" "1" "05/26/2014" "Ansible 1\&.7" "System administration commands" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .\" http://bugs.debian.org/507673 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .\" ----------------------------------------------------------------- .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" ansible-doc \- show documentation on Ansible modules .SH "SYNOPSIS" .sp ansible\-doc [\-M module_path] [\-l] [\-s] [module\&...] .SH "DESCRIPTION" .sp \fBansible\-doc\fR displays information on modules installed in Ansible libraries\&. It displays a terse listing of modules and their short descriptions, provides a printout of their DOCUMENTATION strings, and it can create a short "snippet" which can be pasted into a playbook\&. .SH "OPTIONS" .PP \fB\-M\fR \fIdirectory\fR, \fB\-\-module\-path=\fR\fIdirectory\fR .RS 4 Add an additional directory to the default path for finding module libraries\&. .RE .PP \fB\-s\fR, \fB\-\-snippet=\fR .RS 4 Produce a snippet which can be copied into a playbook for modification, like a kind of task template\&. .RE .PP \fB\-l\fR, \fB\-\-list=\fR .RS 4 Produce a terse listing of modules and a short description of each\&. .RE .SH "AUTHOR" .sp ansible\-doc was originally written by Jan\-Piet Mens\&. See the AUTHORS file for a complete list of contributors\&. .SH "COPYRIGHT" .sp Copyright \(co 2012, Jan\-Piet Mens .sp Ansible is released under the terms of the GPLv3 License\&. .SH "SEE ALSO" .sp \fBansible\-playbook\fR(1), \fBansible\fR(1), \fBansible\-pull\fR(1) .sp Extensive documentation is available in the documentation site: http://docs\&.ansible\&.com\&. IRC and mailing list info can be found in file CONTRIBUTING\&.md, available in: https://github\&.com/ansible/ansible .SH "AUTHOR" .PP \fB:doctype:manpage\fR .RS 4 Author. .RE ansible-1.7.2/docs/man/man1/ansible-doc.1.asciidoc.in000066400000000000000000000026621241061774000221310ustar00rootroot00000000000000ansible-doc(1) ============== :doctype:manpage :man source: Ansible :man version: %VERSION% :man manual: System administration commands NAME ---- ansible-doc - show documentation on Ansible modules SYNOPSIS -------- ansible-doc [-M module_path] [-l] [-s] [module...] DESCRIPTION ----------- *ansible-doc* displays information on modules installed in Ansible libraries. It displays a terse listing of modules and their short descriptions, provides a printout of their DOCUMENTATION strings, and it can create a short "snippet" which can be pasted into a playbook. OPTIONS ------- *-M* 'directory', *--module-path=*'directory':: Add an additional directory to the default path for finding module libraries. *-s*, *--snippet=*:: Produce a snippet which can be copied into a playbook for modification, like a kind of task template. *-l*, *--list=*:: Produce a terse listing of modules and a short description of each. AUTHOR ------ ansible-doc was originally written by Jan-Piet Mens. See the AUTHORS file for a complete list of contributors. COPYRIGHT --------- Copyright © 2012, Jan-Piet Mens Ansible is released under the terms of the GPLv3 License. SEE ALSO -------- *ansible-playbook*(1), *ansible*(1), *ansible-pull*(1) Extensive documentation is available in the documentation site: . IRC and mailing list info can be found in file CONTRIBUTING.md, available in: ansible-1.7.2/docs/man/man1/ansible-galaxy.1000066400000000000000000000130771241061774000204710ustar00rootroot00000000000000'\" t .\" Title: ansible-galaxy .\" Author: [see the "AUTHOR" section] .\" Generator: DocBook XSL Stylesheets v1.76.1 .\" Date: 05/26/2014 .\" Manual: System administration commands .\" Source: Ansible 1.7 .\" Language: English .\" .TH "ANSIBLE\-GALAXY" "1" "05/26/2014" "Ansible 1\&.7" "System administration commands" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .\" http://bugs.debian.org/507673 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .\" ----------------------------------------------------------------- .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" ansible-galaxy \- manage roles using galaxy\&.ansible\&.com .SH "SYNOPSIS" .sp ansible\-galaxy [init|info|install|list|remove] [\-\-help] [options] \&... .SH "DESCRIPTION" .sp \fBAnsible Galaxy\fR is a shared repository for Ansible roles (added in ansible version 1\&.2)\&. The ansible\-galaxy command can be used to manage these roles, or by creating a skeleton framework for roles you\(cqd like to upload to Galaxy\&. .SH "COMMON OPTIONS" .PP \fB\-h\fR, \fB\-\-help\fR .RS 4 Show a help message related to the given sub\-command\&. .RE .SH "INSTALL" .sp The \fBinstall\fR sub\-command is used to install roles\&. .SS "USAGE" .sp $ ansible\-galaxy install [options] [\-r FILE | role_name(s)[,version] | tar_file(s)] .sp Roles can be installed in several different ways: .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ .sp -1 .IP \(bu 2.3 .\} A username\&.rolename[,version] \- this will install a single role\&. The Galaxy API will be contacted to provide the information about the role, and the corresponding \&.tar\&.gz will be downloaded from \fBgithub\&.com\fR\&. If the version is omitted, the most recent version available will be installed\&. .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ .sp -1 .IP \(bu 2.3 .\} A file name, using \fB\-r\fR \- this will install multiple roles listed one per line\&. The format of each line is the same as above: username\&.rolename[,version] .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ .sp -1 .IP \(bu 2.3 .\} A \&.tar\&.gz of a valid role you\(cqve downloaded directly from \fBgithub\&.com\fR\&. This is mainly useful when the system running Ansible does not have access to the Galaxy API, for instance when behind a firewall or proxy\&. .RE .SS "OPTIONS" .PP \fB\-f\fR, \fB\-\-force\fR .RS 4 Force overwriting an existing role\&. .RE .PP \fB\-i\fR, \fB\-\-ignore\-errors\fR .RS 4 Ignore errors and continue with the next specified role\&. .RE .PP \fB\-n\fR, \fB\-\-no\-deps\fR .RS 4 Don\(cqt download roles listed as dependencies\&. .RE .PP \fB\-p\fR \fIROLES_PATH\fR, \fB\-\-roles\-path=\fR\fIROLES_PATH\fR .RS 4 The path to the directory containing your roles\&. The default is the \fBroles_path\fR configured in your \fBansible\&.cfg\fR file (/etc/ansible/roles if not configured) .RE .PP \fB\-r\fR \fIROLE_FILE\fR, \fB\-\-role\-file=\fR\fIROLE_FILE\fR .RS 4 A file containing a list of roles to be imported, as specified above\&. This option cannot be used if a rolename or \&.tar\&.gz have been specified\&. .RE .SH "REMOVE" .sp The \fBremove\fR sub\-command is used to remove one or more roles\&. .SS "USAGE" .sp $ ansible\-galaxy remove role1 role2 \&... .SS "OPTIONS" .PP \fB\-p\fR \fIROLES_PATH\fR, \fB\-\-roles\-path=\fR\fIROLES_PATH\fR .RS 4 The path to the directory containing your roles\&. The default is the \fBroles_path\fR configured in your \fBansible\&.cfg\fR file (/etc/ansible/roles if not configured) .RE .SH "INIT" .sp The \fBinit\fR command is used to create an empty role suitable for uploading to https://galaxy\&.ansible\&.com (or for roles in general)\&. .SS "USAGE" .sp $ ansible\-galaxy init [options] role_name .SS "OPTIONS" .PP \fB\-f\fR, \fB\-\-force\fR .RS 4 Force overwriting an existing role\&. .RE .PP \fB\-p\fR \fIINIT_PATH\fR, \fB\-\-init\-path=\fR\fIINIT_PATH\fR .RS 4 The path in which the skeleton role will be created\&.The default is the current working directory\&. .RE .SH "LIST" .sp The \fBlist\fR sub\-command is used to show what roles are currently instaled\&. You can specify a role name, and if installed only that role will be shown\&. .SS "USAGE" .sp $ ansible\-galaxy list [role_name] .SS "OPTIONS" .PP \fB\-p\fR \fIROLES_PATH\fR, \fB\-\-roles\-path=\fR\fIROLES_PATH\fR .RS 4 The path to the directory containing your roles\&. The default is the \fBroles_path\fR configured in your \fBansible\&.cfg\fR file (/etc/ansible/roles if not configured) .RE .SH "AUTHOR" .sp Ansible was originally written by Michael DeHaan\&. See the AUTHORS file for a complete list of contributors\&. .SH "COPYRIGHT" .sp Copyright \(co 2014, Michael DeHaan .sp Ansible is released under the terms of the GPLv3 License\&. .SH "SEE ALSO" .sp \fBansible\fR(1), \fBansible\-pull\fR(1), \fBansible\-doc\fR(1) .sp Extensive documentation is available in the documentation site: http://docs\&.ansible\&.com\&. IRC and mailing list info can be found in file CONTRIBUTING\&.md, available in: https://github\&.com/ansible/ansible ansible-1.7.2/docs/man/man1/ansible-galaxy.1.asciidoc.in000066400000000000000000000075341241061774000226540ustar00rootroot00000000000000ansible-galaxy(1) =================== :doctype: manpage :man source: Ansible :man version: %VERSION% :man manual: System administration commands NAME ---- ansible-galaxy - manage roles using galaxy.ansible.com SYNOPSIS -------- ansible-galaxy [init|info|install|list|remove] [--help] [options] ... DESCRIPTION ----------- *Ansible Galaxy* is a shared repository for Ansible roles (added in ansible version 1.2). The ansible-galaxy command can be used to manage these roles, or by creating a skeleton framework for roles you'd like to upload to Galaxy. COMMON OPTIONS -------------- *-h*, *--help*:: Show a help message related to the given sub-command. INSTALL ------- The *install* sub-command is used to install roles. USAGE ~~~~~ $ ansible-galaxy install [options] [-r FILE | role_name(s)[,version] | tar_file(s)] Roles can be installed in several different ways: * A username.rolename[,version] - this will install a single role. The Galaxy API will be contacted to provide the information about the role, and the corresponding .tar.gz will be downloaded from *github.com*. If the version is omitted, the most recent version available will be installed. * A file name, using *-r* - this will install multiple roles listed one per line. The format of each line is the same as above: username.rolename[,version] * A .tar.gz of a valid role you've downloaded directly from *github.com*. This is mainly useful when the system running Ansible does not have access to the Galaxy API, for instance when behind a firewall or proxy. OPTIONS ~~~~~~~ *-f*, *--force*:: Force overwriting an existing role. *-i*, *--ignore-errors*:: Ignore errors and continue with the next specified role. *-n*, *--no-deps*:: Don't download roles listed as dependencies. *-p* 'ROLES_PATH', *--roles-path=*'ROLES_PATH':: The path to the directory containing your roles. The default is the *roles_path* configured in your *ansible.cfg* file (/etc/ansible/roles if not configured) *-r* 'ROLE_FILE', *--role-file=*'ROLE_FILE':: A file containing a list of roles to be imported, as specified above. This option cannot be used if a rolename or .tar.gz have been specified. REMOVE ------ The *remove* sub-command is used to remove one or more roles. USAGE ~~~~~ $ ansible-galaxy remove role1 role2 ... OPTIONS ~~~~~~~ *-p* 'ROLES_PATH', *--roles-path=*'ROLES_PATH':: The path to the directory containing your roles. The default is the *roles_path* configured in your *ansible.cfg* file (/etc/ansible/roles if not configured) INIT ---- The *init* command is used to create an empty role suitable for uploading to https://galaxy.ansible.com (or for roles in general). USAGE ~~~~~ $ ansible-galaxy init [options] role_name OPTIONS ~~~~~~~ *-f*, *--force*:: Force overwriting an existing role. *-p* 'INIT_PATH', *--init-path=*'INIT_PATH':: The path in which the skeleton role will be created.The default is the current working directory. LIST ---- The *list* sub-command is used to show what roles are currently instaled. You can specify a role name, and if installed only that role will be shown. USAGE ~~~~~ $ ansible-galaxy list [role_name] OPTIONS ~~~~~~~ *-p* 'ROLES_PATH', *--roles-path=*'ROLES_PATH':: The path to the directory containing your roles. The default is the *roles_path* configured in your *ansible.cfg* file (/etc/ansible/roles if not configured) AUTHOR ------ Ansible was originally written by Michael DeHaan. See the AUTHORS file for a complete list of contributors. COPYRIGHT --------- Copyright © 2014, Michael DeHaan Ansible is released under the terms of the GPLv3 License. SEE ALSO -------- *ansible*(1), *ansible-pull*(1), *ansible-doc*(1) Extensive documentation is available in the documentation site: . IRC and mailing list info can be found in file CONTRIBUTING.md, available in: ansible-1.7.2/docs/man/man1/ansible-playbook.1000066400000000000000000000127411241061774000210210ustar00rootroot00000000000000'\" t .\" Title: ansible-playbook .\" Author: :doctype:manpage .\" Generator: DocBook XSL Stylesheets v1.76.1 .\" Date: 05/26/2014 .\" Manual: System administration commands .\" Source: Ansible 1.7 .\" Language: English .\" .TH "ANSIBLE\-PLAYBOOK" "1" "05/26/2014" "Ansible 1\&.7" "System administration commands" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .\" http://bugs.debian.org/507673 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .\" ----------------------------------------------------------------- .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" ansible-playbook \- run an ansible playbook .SH "SYNOPSIS" .sp ansible\-playbook \&... [options] .SH "DESCRIPTION" .sp \fBAnsible playbooks\fR are a configuration and multinode deployment system\&. Ansible\-playbook is the tool used to run them\&. See the project home page (link below) for more information\&. .SH "ARGUMENTS" .PP \fBfilename\&.yml\fR .RS 4 The names of one or more YAML format files to run as ansible playbooks\&. .RE .SH "OPTIONS" .PP \fB\-v\fR, \fB\-\-verbose\fR .RS 4 Verbose mode, more output from successful actions will be shown\&. Give up to three times for more output\&. .RE .PP \fB\-i\fR \fIPATH\fR, \fB\-\-inventory=\fR\fIPATH\fR .RS 4 The \fIPATH\fR to the inventory hosts file, which defaults to \fI/etc/ansible/hosts\fR\&. .RE .PP \fB\-M\fR \fIDIRECTORY\fR, \fB\-\-module\-path=\fR\fIDIRECTORY\fR .RS 4 The \fIDIRECTORY\fR search path to load modules from\&. The default is \fI/usr/share/ansible\fR\&. This can also be set with the ANSIBLE_LIBRARY environment variable\&. .RE .PP \fB\-e\fR \fIVARS\fR, \fB\-\-extra\-vars=\fR\fIVARS\fR .RS 4 Extra variables to inject into a playbook, in key=value key=value format or as quoted JSON (hashes and arrays)\&. .RE .PP \fB\-f\fR \fINUM\fR, \fB\-\-forks=\fR\fINUM\fR .RS 4 Level of parallelism\&. \fINUM\fR is specified as an integer, the default is 5\&. .RE .PP \fB\-k\fR, \fB\-\-ask\-pass\fR .RS 4 Prompt for the SSH password instead of assuming key\-based authentication with ssh\-agent\&. .RE .PP \fB\-K\fR, \fB\-\-ask\-sudo\-pass\fR .RS 4 Prompt for the password to use for playbook plays that request sudo access, if any\&. .RE .PP \fB\-U\fR, \fISUDO_USER\fR, \fB\-\-sudo\-user=\fR\fISUDO_USER\fR .RS 4 Desired sudo user (default=root)\&. .RE .PP \fB\-t\fR, \fITAGS\fR, \fB\-\-tags=\fR\fITAGS\fR .RS 4 Only run plays and tasks tagged with these values\&. .RE .PP \fB\-\-skip\-tags=\fR\fISKIP_TAGS\fR .RS 4 Only run plays and tasks whose tags do not match these values\&. .RE .PP \fB\-\-syntax\-check\fR .RS 4 Look for syntax errors in the playbook, but don\(cqt run anything .RE .PP \fB\-\-check\fR .RS 4 Do not make any changes on the remote system, but test resources to see what might have changed\&. Note this can not scan all possible resource types and is only a simulation\&. .RE .PP \fB\-\-diff\fR .RS 4 When changing any templated files, show the unified diffs of how they changed\&. When used with \-\-check, shows how the files would have changed if \-\-check were not used\&. .RE .PP \fB\-T\fR \fISECONDS\fR, \fB\-\-timeout=\fR\fISECONDS\fR .RS 4 Connection timeout to use when trying to talk to hosts, in \fISECONDS\fR\&. .RE .PP \fB\-s\fR, \fB\-\-sudo\fR .RS 4 Force all plays to use sudo, even if not marked as such\&. .RE .PP \fB\-u\fR \fIUSERNAME\fR, \fB\-\-user=\fR\fIUSERNAME\fR .RS 4 Use this remote user name on playbook steps that do not indicate a user name to run as\&. .RE .PP \fB\-c\fR \fICONNECTION\fR, \fB\-\-connection=\fR\fICONNECTION\fR .RS 4 Connection type to use\&. Possible options are \fIparamiko\fR (SSH), \fIssh\fR, and \fIlocal\fR\&. \fIlocal\fR is mostly useful for crontab or kickstarts\&. .RE .PP \fB\-l\fR \fISUBSET\fR, \fB\-\-limit=\fR\fISUBSET\fR .RS 4 Further limits the selected host/group patterns\&. .RE .SH "ENVIRONMENT" .sp The following environment variables may be specified\&. .sp ANSIBLE_HOSTS \(em Override the default ansible hosts file .sp ANSIBLE_LIBRARY \(em Override the default ansible module library path .SH "FILES" .sp /etc/ansible/hosts \(em Default inventory file .sp /usr/share/ansible/ \(em Default module library .sp /etc/ansible/ansible\&.cfg \(em Config file, used if present .sp ~/\&.ansible\&.cfg \(em User config file, overrides the default config if present .SH "AUTHOR" .sp Ansible was originally written by Michael DeHaan\&. See the AUTHORS file for a complete list of contributors\&. .SH "COPYRIGHT" .sp Copyright \(co 2012, Michael DeHaan .sp Ansible is released under the terms of the GPLv3 License\&. .SH "SEE ALSO" .sp \fBansible\fR(1), \fBansible\-pull\fR(1), \fBansible\-doc\fR(1) .sp Extensive documentation is available in the documentation site: http://docs\&.ansible\&.com\&. IRC and mailing list info can be found in file CONTRIBUTING\&.md, available in: https://github\&.com/ansible/ansible .SH "AUTHOR" .PP \fB:doctype:manpage\fR .RS 4 Author. .RE ansible-1.7.2/docs/man/man1/ansible-playbook.1.asciidoc.in000066400000000000000000000073601241061774000232040ustar00rootroot00000000000000ansible-playbook(1) =================== :doctype:manpage :man source: Ansible :man version: %VERSION% :man manual: System administration commands NAME ---- ansible-playbook - run an ansible playbook SYNOPSIS -------- ansible-playbook ... [options] DESCRIPTION ----------- *Ansible playbooks* are a configuration and multinode deployment system. Ansible-playbook is the tool used to run them. See the project home page (link below) for more information. ARGUMENTS --------- *filename.yml*:: The names of one or more YAML format files to run as ansible playbooks. OPTIONS ------- *-v*, *--verbose*:: Verbose mode, more output from successful actions will be shown. Give up to three times for more output. *-i* 'PATH', *--inventory=*'PATH':: The 'PATH' to the inventory hosts file, which defaults to '/etc/ansible/hosts'. *-M* 'DIRECTORY', *--module-path=*'DIRECTORY':: The 'DIRECTORY' search path to load modules from. The default is '/usr/share/ansible'. This can also be set with the ANSIBLE_LIBRARY environment variable. *-e* 'VARS', *--extra-vars=*'VARS':: Extra variables to inject into a playbook, in key=value key=value format or as quoted JSON (hashes and arrays). *-f* 'NUM', *--forks=*'NUM':: Level of parallelism. 'NUM' is specified as an integer, the default is 5. *-k*, *--ask-pass*:: Prompt for the SSH password instead of assuming key-based authentication with ssh-agent. *-K*, *--ask-sudo-pass*:: Prompt for the password to use for playbook plays that request sudo access, if any. *-U*, 'SUDO_USER', *--sudo-user=*'SUDO_USER':: Desired sudo user (default=root). *-t*, 'TAGS', *--tags=*'TAGS':: Only run plays and tasks tagged with these values. *--skip-tags=*'SKIP_TAGS':: Only run plays and tasks whose tags do not match these values. *--syntax-check*:: Look for syntax errors in the playbook, but don't run anything *--check*:: Do not make any changes on the remote system, but test resources to see what might have changed. Note this can not scan all possible resource types and is only a simulation. *--diff*:: When changing any templated files, show the unified diffs of how they changed. When used with --check, shows how the files would have changed if --check were not used. *-T* 'SECONDS', *--timeout=*'SECONDS':: Connection timeout to use when trying to talk to hosts, in 'SECONDS'. *-s*, *--sudo*:: Force all plays to use sudo, even if not marked as such. *-u* 'USERNAME', *--user=*'USERNAME':: Use this remote user name on playbook steps that do not indicate a user name to run as. *-c* 'CONNECTION', *--connection=*'CONNECTION':: Connection type to use. Possible options are 'paramiko' (SSH), 'ssh', and 'local'. 'local' is mostly useful for crontab or kickstarts. *-l* 'SUBSET', *--limit=*'SUBSET':: Further limits the selected host/group patterns. ENVIRONMENT ----------- The following environment variables may be specified. ANSIBLE_HOSTS -- Override the default ansible hosts file ANSIBLE_LIBRARY -- Override the default ansible module library path FILES ----- /etc/ansible/hosts -- Default inventory file /usr/share/ansible/ -- Default module library /etc/ansible/ansible.cfg -- Config file, used if present ~/.ansible.cfg -- User config file, overrides the default config if present AUTHOR ------ Ansible was originally written by Michael DeHaan. See the AUTHORS file for a complete list of contributors. COPYRIGHT --------- Copyright © 2012, Michael DeHaan Ansible is released under the terms of the GPLv3 License. SEE ALSO -------- *ansible*(1), *ansible-pull*(1), *ansible-doc*(1) Extensive documentation is available in the documentation site: . IRC and mailing list info can be found in file CONTRIBUTING.md, available in: ansible-1.7.2/docs/man/man1/ansible-pull.1000066400000000000000000000103731241061774000201540ustar00rootroot00000000000000'\" t .\" Title: ansible .\" Author: :doctype:manpage .\" Generator: DocBook XSL Stylesheets v1.76.1 .\" Date: 05/26/2014 .\" Manual: System administration commands .\" Source: Ansible 1.7 .\" Language: English .\" .TH "ANSIBLE" "1" "05/26/2014" "Ansible 1\&.7" "System administration commands" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .\" http://bugs.debian.org/507673 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .\" ----------------------------------------------------------------- .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" ansible-pull \- set up a remote copy of ansible on each managed node .SH "SYNOPSIS" .sp ansible \-d DEST \-U URL [options] [ ] .SH "DESCRIPTION" .sp \fBAnsible\fR is an extra\-simple tool/framework/API for doing \*(Aqremote things\*(Aq over SSH\&. .sp Use ansible\-pull to set up a remote copy of ansible on each managed node, each set to run via cron and update playbook source via a source repository\&. This inverts the default \fBpush\fR architecture of ansible into a \fBpull\fR architecture, which has near\-limitless scaling potential\&. .sp The setup playbook can be tuned to change the cron frequency, logging locations, and parameters to ansible\-pull\&. .sp This is useful both for extreme scale\-out as well as periodic remediation\&. Usage of the \fIfetch\fR module to retrieve logs from ansible\-pull runs would be an excellent way to gather and analyze remote logs from ansible\-pull\&. .SH "OPTIONAL ARGUMENT" .PP \fBfilename\&.yml\fR .RS 4 The name of one the YAML format files to run as an ansible playbook\&. This can be a relative path within the checkout\&. If not provided, ansible\-pull will look for a playbook based on the host\(cqs fully\-qualified domain name, on the host hostname and finally a playbook named \fBlocal\&.yml\fR\&. .RE .SH "OPTIONS" .PP \fB\-d\fR \fIDEST\fR, \fB\-\-directory=\fR\fIDEST\fR .RS 4 Directory to checkout repository into\&. If not provided, a subdirectory of ~/\&.ansible/pull/ will be used\&. .RE .PP \fB\-U\fR \fIURL\fR, \fB\-\-url=\fR\fIURL\fR .RS 4 URL of the playbook repository to checkout\&. .RE .PP \fB\-C\fR \fICHECKOUT\fR, \fB\-\-checkout=\fR\fICHECKOUT\fR .RS 4 Branch/Tag/Commit to checkout\&. If not provided, uses default behavior of module used to check out playbook repository\&. .RE .PP \fB\-f\fR, \fB\-\-force\fR .RS 4 Force running of playbook even if unable to update playbook repository\&. This can be useful, for example, to enforce run\-time state when a network connection may not always be up or possible\&. .RE .PP \fB\-i\fR \fIPATH\fR, \fB\-\-inventory=\fR\fIPATH\fR .RS 4 The \fIPATH\fR to the inventory hosts file\&. This can be a relative path within the checkout\&. .RE .PP \fB\-\-purge\fR .RS 4 Purge the checkout after the playbook is run\&. .RE .PP \fB\-m\fR \fINAME\fR, \fB\-\-module\-name=\fR\fINAME\fR .RS 4 Module used to checkout playbook repository\&. Defaults to git\&. .RE .PP \fB\-o\fR, \fB\-\-only\-if\-changed\fR .RS 4 Run the playbook only if the repository has changed .RE .SH "AUTHOR" .sp Ansible was originally written by Michael DeHaan\&. See the AUTHORS file for a complete list of contributors\&. .SH "COPYRIGHT" .sp Copyright \(co 2012, Michael DeHaan .sp Ansible is released under the terms of the GPLv3 License\&. .SH "SEE ALSO" .sp \fBansible\fR(1), \fBansible\-playbook\fR(1), \fBansible\-doc\fR(1) .sp Extensive documentation is available in the documentation site: http://docs\&.ansible\&.com\&. IRC and mailing list info can be found in file CONTRIBUTING\&.md, available in: https://github\&.com/ansible/ansible .SH "AUTHOR" .PP \fB:doctype:manpage\fR .RS 4 Author. .RE ansible-1.7.2/docs/man/man1/ansible-pull.1.asciidoc.in000066400000000000000000000054571241061774000223450ustar00rootroot00000000000000ansible(1) ========= :doctype:manpage :man source: Ansible :man version: %VERSION% :man manual: System administration commands NAME ---- ansible-pull - set up a remote copy of ansible on each managed node SYNOPSIS -------- ansible -d DEST -U URL [options] [ ] DESCRIPTION ----------- *Ansible* is an extra-simple tool/framework/API for doing \'remote things' over SSH. Use ansible-pull to set up a remote copy of ansible on each managed node, each set to run via cron and update playbook source via a source repository. This inverts the default *push* architecture of ansible into a *pull* architecture, which has near-limitless scaling potential. The setup playbook can be tuned to change the cron frequency, logging locations, and parameters to ansible-pull. This is useful both for extreme scale-out as well as periodic remediation. Usage of the 'fetch' module to retrieve logs from ansible-pull runs would be an excellent way to gather and analyze remote logs from ansible-pull. OPTIONAL ARGUMENT ----------------- *filename.yml*:: The name of one the YAML format files to run as an ansible playbook. This can be a relative path within the checkout. If not provided, ansible-pull will look for a playbook based on the host's fully-qualified domain name, on the host hostname and finally a playbook named *local.yml*. OPTIONS ------- *-d* 'DEST', *--directory=*'DEST':: Directory to checkout repository into. If not provided, a subdirectory of ~/.ansible/pull/ will be used. *-U* 'URL', *--url=*'URL':: URL of the playbook repository to checkout. *-C* 'CHECKOUT', *--checkout=*'CHECKOUT':: Branch/Tag/Commit to checkout. If not provided, uses default behavior of module used to check out playbook repository. *-f*, *--force*:: Force running of playbook even if unable to update playbook repository. This can be useful, for example, to enforce run-time state when a network connection may not always be up or possible. *-i* 'PATH', *--inventory=*'PATH':: The 'PATH' to the inventory hosts file. This can be a relative path within the checkout. *--purge*:: Purge the checkout after the playbook is run. *-m* 'NAME', *--module-name=*'NAME':: Module used to checkout playbook repository. Defaults to git. *-o*, *--only-if-changed*:: Run the playbook only if the repository has changed AUTHOR ------ Ansible was originally written by Michael DeHaan. See the AUTHORS file for a complete list of contributors. COPYRIGHT --------- Copyright © 2012, Michael DeHaan Ansible is released under the terms of the GPLv3 License. SEE ALSO -------- *ansible*(1), *ansible-playbook*(1), *ansible-doc*(1) Extensive documentation is available in the documentation site: . IRC and mailing list info can be found in file CONTRIBUTING.md, available in: ansible-1.7.2/docs/man/man1/ansible-vault.1000066400000000000000000000115201241061774000203260ustar00rootroot00000000000000'\" t .\" Title: ansible-vault .\" Author: [see the "AUTHOR" section] .\" Generator: DocBook XSL Stylesheets v1.76.1 .\" Date: 05/26/2014 .\" Manual: System administration commands .\" Source: Ansible 1.7 .\" Language: English .\" .TH "ANSIBLE\-VAULT" "1" "05/26/2014" "Ansible 1\&.7" "System administration commands" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .\" http://bugs.debian.org/507673 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .\" ----------------------------------------------------------------- .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" ansible-vault \- manage encrypted YAML data\&. .SH "SYNOPSIS" .sp ansible\-vault [create|decrypt|edit|encrypt|rekey] [\-\-help] [options] file_name .SH "DESCRIPTION" .sp \fBansible\-vault\fR can encrypt any structured data file used by Ansible\&. This can include \fBgroup_vars/\fR or \fBhost_vars/\fR inventory variables, variables loaded by \fBinclude_vars\fR or \fBvars_files\fR, or variable files passed on the ansible\-playbook command line with \fB\-e @file\&.yml\fR or \fB\-e @file\&.json\fR\&. Role variables and defaults are also included! .sp Because Ansible tasks, handlers, and so on are also data, these can also be encrypted with vault\&. If you\(cqd like to not betray what variables you are even using, you can go as far to keep an individual task file entirely encrypted\&. .SH "COMMON OPTIONS" .sp The following options are available to all sub\-commands: .PP \fB\-\-vault\-password\-file=\fR\fIFILE\fR .RS 4 A file containing the vault password to be used during the encryption/decryption steps\&. Be sure to keep this file secured if it is used\&. .RE .PP \fB\-h\fR, \fB\-\-help\fR .RS 4 Show a help message related to the given sub\-command\&. .RE .PP \fB\-\-debug\fR .RS 4 Enable debugging output for troubleshooting\&. .RE .SH "CREATE" .sp \fB$ ansible\-vault create [options] FILE\fR .sp The \fBcreate\fR sub\-command is used to initialize a new encrypted file\&. .sp First you will be prompted for a password\&. The password used with vault currently must be the same for all files you wish to use together at the same time\&. .sp After providing a password, the tool will launch whatever editor you have defined with $EDITOR, and defaults to vim\&. Once you are done with the editor session, the file will be saved as encrypted data\&. .sp The default cipher is AES (which is shared\-secret based)\&. .SH "EDIT" .sp \fB$ ansible\-vault edit [options] FILE\fR .sp The \fBedit\fR sub\-command is used to modify a file which was previously encrypted using ansible\-vault\&. .sp This command will decrypt the file to a temporary file and allow you to edit the file, saving it back when done and removing the temporary file\&. .SH "REKEY" .sp *$ ansible\-vault rekey [options] FILE_1 [FILE_2, \&..., FILE_N] .sp The \fBrekey\fR command is used to change the password on a vault\-encrypted files\&. This command can update multiple files at once, and will prompt for both the old and new passwords before modifying any data\&. .SH "ENCRYPT" .sp *$ ansible\-vault encrypt [options] FILE_1 [FILE_2, \&..., FILE_N] .sp The \fBencrypt\fR sub\-command is used to encrypt pre\-existing data files\&. As with the \fBrekey\fR command, you can specify multiple files in one command\&. .SH "DECRYPT" .sp *$ ansible\-vault decrypt [options] FILE_1 [FILE_2, \&..., FILE_N] .sp The \fBdecrypt\fR sub\-command is used to remove all encryption from data files\&. The files will be stored as plain\-text YAML once again, so be sure that you do not run this command on data files with active passwords or other sensitive data\&. In most cases, users will want to use the \fBedit\fR sub\-command to modify the files securely\&. .SH "AUTHOR" .sp Ansible was originally written by Michael DeHaan\&. See the AUTHORS file for a complete list of contributors\&. .SH "COPYRIGHT" .sp Copyright \(co 2014, Michael DeHaan .sp Ansible is released under the terms of the GPLv3 License\&. .SH "SEE ALSO" .sp \fBansible\fR(1), \fBansible\-pull\fR(1), \fBansible\-doc\fR(1) .sp Extensive documentation is available in the documentation site: http://docs\&.ansible\&.com\&. IRC and mailing list info can be found in file CONTRIBUTING\&.md, available in: https://github\&.com/ansible/ansible ansible-1.7.2/docs/man/man1/ansible-vault.1.asciidoc.in000066400000000000000000000070111241061774000225100ustar00rootroot00000000000000ansible-vault(1) ================ :doctype: manpage :man source: Ansible :man version: %VERSION% :man manual: System administration commands NAME ---- ansible-vault - manage encrypted YAML data. SYNOPSIS -------- ansible-vault [create|decrypt|edit|encrypt|rekey] [--help] [options] file_name DESCRIPTION ----------- *ansible-vault* can encrypt any structured data file used by Ansible. This can include *group_vars/* or *host_vars/* inventory variables, variables loaded by *include_vars* or *vars_files*, or variable files passed on the ansible-playbook command line with *-e @file.yml* or *-e @file.json*. Role variables and defaults are also included! Because Ansible tasks, handlers, and so on are also data, these can also be encrypted with vault. If you’d like to not betray what variables you are even using, you can go as far to keep an individual task file entirely encrypted. COMMON OPTIONS -------------- The following options are available to all sub-commands: *--vault-password-file=*'FILE':: A file containing the vault password to be used during the encryption/decryption steps. Be sure to keep this file secured if it is used. *-h*, *--help*:: Show a help message related to the given sub-command. *--debug*:: Enable debugging output for troubleshooting. CREATE ------ *$ ansible-vault create [options] FILE* The *create* sub-command is used to initialize a new encrypted file. First you will be prompted for a password. The password used with vault currently must be the same for all files you wish to use together at the same time. After providing a password, the tool will launch whatever editor you have defined with $EDITOR, and defaults to vim. Once you are done with the editor session, the file will be saved as encrypted data. The default cipher is AES (which is shared-secret based). EDIT ---- *$ ansible-vault edit [options] FILE* The *edit* sub-command is used to modify a file which was previously encrypted using ansible-vault. This command will decrypt the file to a temporary file and allow you to edit the file, saving it back when done and removing the temporary file. REKEY ----- *$ ansible-vault rekey [options] FILE_1 [FILE_2, ..., FILE_N] The *rekey* command is used to change the password on a vault-encrypted files. This command can update multiple files at once, and will prompt for both the old and new passwords before modifying any data. ENCRYPT ------- *$ ansible-vault encrypt [options] FILE_1 [FILE_2, ..., FILE_N] The *encrypt* sub-command is used to encrypt pre-existing data files. As with the *rekey* command, you can specify multiple files in one command. DECRYPT ------- *$ ansible-vault decrypt [options] FILE_1 [FILE_2, ..., FILE_N] The *decrypt* sub-command is used to remove all encryption from data files. The files will be stored as plain-text YAML once again, so be sure that you do not run this command on data files with active passwords or other sensitive data. In most cases, users will want to use the *edit* sub-command to modify the files securely. AUTHOR ------ Ansible was originally written by Michael DeHaan. See the AUTHORS file for a complete list of contributors. COPYRIGHT --------- Copyright © 2014, Michael DeHaan Ansible is released under the terms of the GPLv3 License. SEE ALSO -------- *ansible*(1), *ansible-pull*(1), *ansible-doc*(1) Extensive documentation is available in the documentation site: . IRC and mailing list info can be found in file CONTRIBUTING.md, available in: ansible-1.7.2/docs/man/man1/ansible.1000066400000000000000000000137131241061774000172030ustar00rootroot00000000000000'\" t .\" Title: ansible .\" Author: :doctype:manpage .\" Generator: DocBook XSL Stylesheets v1.76.1 .\" Date: 05/26/2014 .\" Manual: System administration commands .\" Source: Ansible 1.7 .\" Language: English .\" .TH "ANSIBLE" "1" "05/26/2014" "Ansible 1\&.7" "System administration commands" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .\" http://bugs.debian.org/507673 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .\" ----------------------------------------------------------------- .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" ansible \- run a command somewhere else .SH "SYNOPSIS" .sp ansible [\-f forks] [\-m module_name] [\-a args] .SH "DESCRIPTION" .sp \fBAnsible\fR is an extra\-simple tool/framework/API for doing \*(Aqremote things\*(Aq over SSH\&. .SH "ARGUMENTS" .PP \fBhost\-pattern\fR .RS 4 A name of a group in the inventory file, a shell\-like glob selecting hosts in inventory file, or any combination of the two separated by semicolons\&. .RE .SH "OPTIONS" .PP \fB\-v\fR, \fB\-\-verbose\fR .RS 4 Verbose mode, more output from successful actions will be shown\&. Give up to three times for more output\&. .RE .PP \fB\-i\fR \fIPATH\fR, \fB\-\-inventory=\fR\fIPATH\fR .RS 4 The \fIPATH\fR to the inventory hosts file, which defaults to \fI/etc/ansible/hosts\fR\&. .RE .PP \fB\-f\fR \fINUM\fR, \fB\-\-forks=\fR\fINUM\fR .RS 4 Level of parallelism\&. \fINUM\fR is specified as an integer, the default is 5\&. .RE .PP \fB\-\-private\-key=\fR\fIPRIVATE_KEY_FILE\fR .RS 4 Use this file to authenticate the connection\&. .RE .PP \fB\-m\fR \fINAME\fR, \fB\-\-module\-name=\fR\fINAME\fR .RS 4 Execute the module called \fINAME\fR\&. .RE .PP \fB\-M\fR \fIDIRECTORY\fR, \fB\-\-module\-path=\fR\fIDIRECTORY\fR .RS 4 The \fIDIRECTORY\fR search path to load modules from\&. The default is \fI/usr/share/ansible\fR\&. This can also be set with the ANSIBLE_LIBRARY environment variable\&. .RE .PP \fB\-a\fR \*(Aq\fIARGUMENTS\fR\*(Aq, \fB\-\-args=\fR\*(Aq\fIARGUMENTS\fR\*(Aq .RS 4 The \fIARGUMENTS\fR to pass to the module\&. .RE .PP \fB\-k\fR, \fB\-\-ask\-pass\fR .RS 4 Prompt for the SSH password instead of assuming key\-based authentication with ssh\-agent\&. .RE .PP \fB\-K\fR, \fB\-\-ask\-sudo\-pass\fR .RS 4 Prompt for the password to use with \-\-sudo, if any .RE .PP \fB\-o\fR, \fB\-\-one\-line\fR .RS 4 Try to output everything on one line\&. .RE .PP \fB\-s\fR, \fB\-\-sudo\fR .RS 4 Run the command as the user given by \-u and sudo to root\&. .RE .PP \fB\-t\fR \fIDIRECTORY\fR, \fB\-\-tree=\fR\fIDIRECTORY\fR .RS 4 Save contents in this output \fIDIRECTORY\fR, with the results saved in a file named after each host\&. .RE .PP \fB\-T\fR \fISECONDS\fR, \fB\-\-timeout=\fR\fISECONDS\fR .RS 4 Connection timeout to use when trying to talk to hosts, in \fISECONDS\fR\&. .RE .PP \fB\-B\fR \fINUM\fR, \fB\-\-background=\fR\fINUM\fR .RS 4 Run commands in the background, killing the task after \fINUM\fR seconds\&. .RE .PP \fB\-P\fR \fINUM\fR, \fB\-\-poll=\fR\fINUM\fR .RS 4 Poll a background job every \fINUM\fR seconds\&. Requires \fB\-B\fR\&. .RE .PP \fB\-u\fR \fIUSERNAME\fR, \fB\-\-user=\fR\fIUSERNAME\fR .RS 4 Use this remote \fIUSERNAME\fR instead of the current user\&. .RE .PP \fB\-U\fR \fISUDO_USERNAME\fR, \fB\-\-sudo\-user=\fR\fISUDO_USERNAME\fR .RS 4 Sudo to \fISUDO_USERNAME\fR instead of root\&. Implies \-\-sudo\&. .RE .PP \fB\-c\fR \fICONNECTION\fR, \fB\-\-connection=\fR\fICONNECTION\fR .RS 4 Connection type to use\&. Possible options are \fIparamiko\fR (SSH), \fIssh\fR, and \fIlocal\fR\&. \fIlocal\fR is mostly useful for crontab or kickstarts\&. .RE .PP \fB\-l\fR \fISUBSET\fR, \fB\-\-limit=\fR\fISUBSET\fR .RS 4 Further limits the selected host/group patterns\&. .RE .PP \fB\-l\fR \fI~REGEX\fR, \fB\-\-limit=\fR\fI~REGEX\fR .RS 4 Further limits hosts with a regex pattern\&. .RE .SH "INVENTORY" .sp Ansible stores the hosts it can potentially operate on in an inventory file\&. The syntax is one host per line\&. Groups headers are allowed and are included on their own line, enclosed in square brackets that start the line\&. .sp Ranges of hosts are also supported\&. For more information and additional options, see the documentation on http://docs\&.ansible\&.com/\&. .SH "FILES" .sp /etc/ansible/hosts \(em Default inventory file .sp /usr/share/ansible/ \(em Default module library .sp /etc/ansible/ansible\&.cfg \(em Config file, used if present .sp ~/\&.ansible\&.cfg \(em User config file, overrides the default config if present .SH "ENVIRONMENT" .sp The following environment variables may be specified\&. .sp ANSIBLE_HOSTS \(em Override the default ansible hosts file .sp ANSIBLE_LIBRARY \(em Override the default ansible module library path .sp ANSIBLE_CONFIG \(em Override the default ansible config file .SH "AUTHOR" .sp Ansible was originally written by Michael DeHaan\&. See the AUTHORS file for a complete list of contributors\&. .SH "COPYRIGHT" .sp Copyright \(co 2012, Michael DeHaan .sp Ansible is released under the terms of the GPLv3 License\&. .SH "SEE ALSO" .sp \fBansible\-playbook\fR(1), \fBansible\-pull\fR(1), \fBansible\-doc\fR(1) .sp Extensive documentation is available in the documentation site: http://docs\&.ansible\&.com\&. IRC and mailing list info can be found in file CONTRIBUTING\&.md, available in: https://github\&.com/ansible/ansible .SH "AUTHOR" .PP \fB:doctype:manpage\fR .RS 4 Author. .RE ansible-1.7.2/docs/man/man1/ansible.1.asciidoc.in000066400000000000000000000100661241061774000213630ustar00rootroot00000000000000ansible(1) ========= :doctype:manpage :man source: Ansible :man version: %VERSION% :man manual: System administration commands NAME ---- ansible - run a command somewhere else SYNOPSIS -------- ansible [-f forks] [-m module_name] [-a args] DESCRIPTION ----------- *Ansible* is an extra-simple tool/framework/API for doing \'remote things' over SSH. ARGUMENTS --------- *host-pattern*:: A name of a group in the inventory file, a shell-like glob selecting hosts in inventory file, or any combination of the two separated by semicolons. OPTIONS ------- *-v*, *--verbose*:: Verbose mode, more output from successful actions will be shown. Give up to three times for more output. *-i* 'PATH', *--inventory=*'PATH':: The 'PATH' to the inventory hosts file, which defaults to '/etc/ansible/hosts'. *-f* 'NUM', *--forks=*'NUM':: Level of parallelism. 'NUM' is specified as an integer, the default is 5. *--private-key=*'PRIVATE_KEY_FILE':: Use this file to authenticate the connection. *-m* 'NAME', *--module-name=*'NAME':: Execute the module called 'NAME'. *-M* 'DIRECTORY', *--module-path=*'DIRECTORY':: The 'DIRECTORY' search path to load modules from. The default is '/usr/share/ansible'. This can also be set with the ANSIBLE_LIBRARY environment variable. *-a* \'_ARGUMENTS_', *--args=*\'_ARGUMENTS_':: The 'ARGUMENTS' to pass to the module. *-k*, *--ask-pass*:: Prompt for the SSH password instead of assuming key-based authentication with ssh-agent. *-K*, *--ask-sudo-pass*:: Prompt for the password to use with --sudo, if any *-o*, *--one-line*:: Try to output everything on one line. *-s*, *--sudo*:: Run the command as the user given by -u and sudo to root. *-t* 'DIRECTORY', *--tree=*'DIRECTORY':: Save contents in this output 'DIRECTORY', with the results saved in a file named after each host. *-T* 'SECONDS', *--timeout=*'SECONDS':: Connection timeout to use when trying to talk to hosts, in 'SECONDS'. *-B* 'NUM', *--background=*'NUM':: Run commands in the background, killing the task after 'NUM' seconds. *-P* 'NUM', *--poll=*'NUM':: Poll a background job every 'NUM' seconds. Requires *-B*. *-u* 'USERNAME', *--user=*'USERNAME':: Use this remote 'USERNAME' instead of the current user. *-U* 'SUDO_USERNAME', *--sudo-user=*'SUDO_USERNAME':: Sudo to 'SUDO_USERNAME' instead of root. Implies --sudo. *-c* 'CONNECTION', *--connection=*'CONNECTION':: Connection type to use. Possible options are 'paramiko' (SSH), 'ssh', and 'local'. 'local' is mostly useful for crontab or kickstarts. *-l* 'SUBSET', *--limit=*'SUBSET':: Further limits the selected host/group patterns. *-l* '\~REGEX', *--limit=*'~REGEX':: Further limits hosts with a regex pattern. INVENTORY --------- Ansible stores the hosts it can potentially operate on in an inventory file. The syntax is one host per line. Groups headers are allowed and are included on their own line, enclosed in square brackets that start the line. Ranges of hosts are also supported. For more information and additional options, see the documentation on http://docs.ansible.com/. FILES ----- /etc/ansible/hosts -- Default inventory file /usr/share/ansible/ -- Default module library /etc/ansible/ansible.cfg -- Config file, used if present ~/.ansible.cfg -- User config file, overrides the default config if present ENVIRONMENT ----------- The following environment variables may be specified. ANSIBLE_HOSTS -- Override the default ansible hosts file ANSIBLE_LIBRARY -- Override the default ansible module library path ANSIBLE_CONFIG -- Override the default ansible config file AUTHOR ------ Ansible was originally written by Michael DeHaan. See the AUTHORS file for a complete list of contributors. COPYRIGHT --------- Copyright © 2012, Michael DeHaan Ansible is released under the terms of the GPLv3 License. SEE ALSO -------- *ansible-playbook*(1), *ansible-pull*(1), *ansible-doc*(1) Extensive documentation is available in the documentation site: . IRC and mailing list info can be found in file CONTRIBUTING.md, available in: ansible-1.7.2/docs/man/man3/000077500000000000000000000000001241061774000155015ustar00rootroot00000000000000ansible-1.7.2/docs/man/man3/.gitdir000066400000000000000000000000001241061774000167520ustar00rootroot00000000000000ansible-1.7.2/docsite/000077500000000000000000000000001241061774000145725ustar00rootroot00000000000000ansible-1.7.2/docsite/.gitignore000066400000000000000000000003171241061774000165630ustar00rootroot00000000000000# Old compiled python stuff *.py[co] # package building stuff build # Emacs backup files... *~ .\#* .doctrees # Generated docs stuff ansible*.xml .buildinfo objects.inv .doctrees rst/modules/*.rst *.min.css ansible-1.7.2/docsite/.nojekyll000066400000000000000000000000001241061774000164100ustar00rootroot00000000000000ansible-1.7.2/docsite/Makefile000066400000000000000000000025231241061774000162340ustar00rootroot00000000000000#!/usr/bin/make SITELIB = $(shell python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()") FORMATTER=../hacking/module_formatter.py all: clean docs docs: clean modules staticmin ./build-site.py -(cp *.ico htmlout/) -(cp *.jpg htmlout/) -(cp *.png htmlout/) variables: (mkdir -p htmlout/) dot variables.dot -Tpng -o htmlout/variables.png viewdocs: clean staticmin ./build-site.py view htmldocs: staticmin ./build-site.py rst clean: -rm -rf htmlout -rm -f .buildinfo -rm -f *.inv -rm -rf *.doctrees @echo "Cleaning up minified css files" find . -type f -name "*.min.css" -delete @echo "Cleaning up byte compiled python stuff" find . -regex ".*\.py[co]$$" -delete @echo "Cleaning up editor backup files" find . -type f \( -name "*~" -or -name "#*" \) -delete find . -type f \( -name "*.swp" \) -delete @echo "Cleaning up generated rst" -rm rst/list_of_*.rst -rm rst/*_by_category.rst -rm rst/*_module.rst .PHONEY: docs clean modules: $(FORMATTER) ../hacking/templates/rst.j2 PYTHONPATH=../lib $(FORMATTER) -t rst --template-dir=../hacking/templates --module-dir=../library -o rst/ staticmin: cat _themes/srtd/static/css/theme.css | sed -e 's/^[ \t]*//g; s/[ \t]*$$//g; s/\([:{;,]\) /\1/g; s/ {/{/g; s/\/\*.*\*\///g; /^$$/d' | sed -e :a -e '$$!N; s/\n\(.\)/\1/; ta' > _themes/srtd/static/css/theme.min.css ansible-1.7.2/docsite/README.md000066400000000000000000000025341241061774000160550ustar00rootroot00000000000000Homepage and documentation source for Ansible ============================================= This project hosts the source behind [docs.ansible.com](http://docs.ansible.com/) Contributions to the documentation are welcome. To make changes, submit a pull request that changes the reStructuredText files in the "rst/" directory only, and Michael can do a docs build and push the static files. If you wish to verify output from the markup such as link references, you may install sphinx and build the documentation by running `make viewdocs` from the `ansible/docsite` directory. To include module documentation you'll need to run `make webdocs` at the top level of the repository. The generated html files are in docsite/htmlout/. If you do not want to learn the reStructuredText format, you can also [file issues] about documentation problems on the Ansible GitHub project. Note that module documentation can actually be [generated from a DOCUMENTATION docstring][module-docs] in the modules directory, so corrections to modules written as such need to be made in the module source, rather than in docsite source. To install sphinx and the required theme, install pip and then "pip install sphinx sphinx_rtd_theme" [file issues]: https://github.com/ansible/ansible/issues [module-docs]: http://docs.ansible.com/developing_modules.html#documenting-your-module ansible-1.7.2/docsite/_static/000077500000000000000000000000001241061774000162205ustar00rootroot00000000000000ansible-1.7.2/docsite/_static/ansible-local.css000066400000000000000000000001521241061774000214350ustar00rootroot00000000000000/* Local CSS tweaks for ansible */ .dropdown-menu { overflow-y: auto; } h2 { padding-top: 40px; }ansible-1.7.2/docsite/_static/basic.css000066400000000000000000000204171241061774000200170ustar00rootroot00000000000000/* * basic.css * ~~~~~~~~~ * * Sphinx stylesheet -- basic theme. * * :copyright: Copyright 2007-2011 by the Sphinx team, see AUTHORS. * :license: BSD, see LICENSE for details. * */ /* -- main layout ----------------------------------------------------------- */ div.clearer { clear: both; } /* -- relbar ---------------------------------------------------------------- */ div.related { width: 100%; font-size: 90%; } div.related h3 { display: none; } div.related ul { margin: 0; padding: 0 0 0 10px; list-style: none; } div.related li { display: inline; } div.related li.right { float: right; margin-right: 5px; } /* -- sidebar --------------------------------------------------------------- */ div.sphinxsidebarwrapper { padding: 10px 5px 0 10px; } div.sphinxsidebar { float: left; width: 230px; margin-left: -100%; font-size: 90%; } div.sphinxsidebar ul { list-style: none; } div.sphinxsidebar ul ul, div.sphinxsidebar ul.want-points { margin-left: 20px; list-style: square; } div.sphinxsidebar ul ul { margin-top: 0; margin-bottom: 0; } div.sphinxsidebar form { margin-top: 10px; } div.sphinxsidebar input { border: 1px solid #98dbcc; font-family: sans-serif; font-size: 1em; } div.sphinxsidebar #searchbox input[type="text"] { width: 170px; } div.sphinxsidebar #searchbox input[type="submit"] { width: 30px; } img { border: 0; } /* -- search page ----------------------------------------------------------- */ ul.search { margin: 10px 0 0 20px; padding: 0; } ul.search li { padding: 5px 0 5px 20px; background-image: url(file.png); background-repeat: no-repeat; background-position: 0 7px; } ul.search li a { font-weight: bold; } ul.search li div.context { color: #888; margin: 2px 0 0 30px; text-align: left; } ul.keywordmatches li.goodmatch a { font-weight: bold; } /* -- index page ------------------------------------------------------------ */ table.contentstable { width: 90%; } table.contentstable p.biglink { line-height: 150%; } a.biglink { font-size: 1.3em; } span.linkdescr { font-style: italic; padding-top: 5px; font-size: 90%; } /* -- general index --------------------------------------------------------- */ table.indextable { width: 100%; } table.indextable td { text-align: left; vertical-align: top; } table.indextable dl, table.indextable dd { margin-top: 0; margin-bottom: 0; } table.indextable tr.pcap { height: 10px; } table.indextable tr.cap { margin-top: 10px; background-color: #f2f2f2; } img.toggler { margin-right: 3px; margin-top: 3px; cursor: pointer; } div.modindex-jumpbox { border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; margin: 1em 0 1em 0; padding: 0.4em; } div.genindex-jumpbox { border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; margin: 1em 0 1em 0; padding: 0.4em; } /* -- general body styles --------------------------------------------------- */ a.headerlink { visibility: hidden; } h1:hover > a.headerlink, h2:hover > a.headerlink, h3:hover > a.headerlink, h4:hover > a.headerlink, h5:hover > a.headerlink, h6:hover > a.headerlink, dt:hover > a.headerlink { visibility: visible; } div.body p.caption { text-align: inherit; } div.body td { text-align: left; } .field-list ul { padding-left: 1em; } .first { margin-top: 0 !important; } p.rubric { margin-top: 30px; font-weight: bold; } img.align-left, .figure.align-left, object.align-left { clear: left; float: left; margin-right: 1em; } img.align-right, .figure.align-right, object.align-right { clear: right; float: right; margin-left: 1em; } img.align-center, .figure.align-center, object.align-center { display: block; margin-left: auto; margin-right: auto; } .align-left { text-align: left; } .align-center { text-align: center; } .align-right { text-align: right; } /* -- sidebars -------------------------------------------------------------- */ div.sidebar { margin: 0 0 0.5em 1em; border: 1px solid #ddb; padding: 7px 7px 0 7px; background-color: #ffe; width: 40%; float: right; } p.sidebar-title { font-weight: bold; } /* -- topics ---------------------------------------------------------------- */ div.topic { border: 1px solid #ccc; padding: 7px 7px 0 7px; margin: 10px 0 10px 0; } p.topic-title { font-size: 1.1em; font-weight: bold; margin-top: 10px; } /* -- admonitions ----------------------------------------------------------- */ div.admonition { margin-top: 10px; margin-bottom: 10px; padding: 7px; } div.admonition dt { font-weight: bold; } div.admonition dl { margin-bottom: 0; } p.admonition-title { margin: 0px 10px 5px 0px; font-weight: bold; } div.body p.centered { text-align: center; margin-top: 25px; } /* -- tables ---------------------------------------------------------------- */ table.docutils { border: 0; border-collapse: collapse; } table.docutils td, table.docutils th { padding: 1px 8px 1px 5px; border-top: 0; border-left: 0; border-right: 0; border-bottom: 1px solid #aaa; } table.field-list td, table.field-list th { border: 0 !important; } table.footnote td, table.footnote th { border: 0 !important; } th { text-align: left; padding-right: 5px; } table.citation { border-left: solid 1px gray; margin-left: 1px; } table.citation td { border-bottom: none; } /* -- other body styles ----------------------------------------------------- */ ol.arabic { list-style: decimal; } ol.loweralpha { list-style: lower-alpha; } ol.upperalpha { list-style: upper-alpha; } ol.lowerroman { list-style: lower-roman; } ol.upperroman { list-style: upper-roman; } dl { margin-bottom: 15px; } dd p { margin-top: 0px; } dd ul, dd table { margin-bottom: 10px; } dd { margin-top: 3px; margin-bottom: 10px; margin-left: 30px; } dt:target, .highlighted { background-color: #fbe54e; } dl.glossary dt { font-weight: bold; font-size: 1.1em; } .field-list ul { margin: 0; padding-left: 1em; } .field-list p { margin: 0; } .refcount { color: #060; } .optional { font-size: 1.3em; } .versionmodified { font-style: italic; } .system-message { background-color: #fda; padding: 5px; border: 3px solid red; } .footnote:target { background-color: #ffa; } .line-block { display: block; margin-top: 1em; margin-bottom: 1em; } .line-block .line-block { margin-top: 0; margin-bottom: 0; margin-left: 1.5em; } .guilabel, .menuselection { font-family: sans-serif; } .accelerator { text-decoration: underline; } .classifier { font-style: oblique; } abbr, acronym { border-bottom: dotted 1px; cursor: help; } /* -- code displays --------------------------------------------------------- */ pre { overflow: auto; overflow-y: hidden; /* fixes display issues on Chrome browsers */ } td.linenos pre { padding: 5px 0px; border: 0; background-color: transparent; color: #aaa; } table.highlighttable { margin-left: 0.5em; } table.highlighttable td { padding: 0 0.5em 0 0.5em; } tt.descname { background-color: transparent; font-weight: bold; font-size: 1.2em; } tt.descclassname { background-color: transparent; } tt.xref, a tt { background-color: transparent; font-weight: bold; } h1 tt, h2 tt, h3 tt, h4 tt, h5 tt, h6 tt { background-color: transparent; } .viewcode-link { float: right; } .viewcode-back { float: right; font-family: sans-serif; } div.viewcode-block:target { margin: -1px -10px; padding: 0 10px; } /* -- math display ---------------------------------------------------------- */ img.math { vertical-align: middle; } div.body div.math p { text-align: center; } span.eqno { float: right; } /* -- printout stylesheet --------------------------------------------------- */ @media print { div.document, div.documentwrapper, div.bodywrapper { margin: 0 !important; width: 100%; } div.sphinxsidebar, div.related, div.footer, #top-link { display: none; } }ansible-1.7.2/docsite/_static/bootstrap-dropdown.js000066400000000000000000000032321241061774000224250ustar00rootroot00000000000000/* ============================================================ * bootstrap-dropdown.js v1.4.0 * http://twitter.github.com/bootstrap/javascript.html#dropdown * ============================================================ * Copyright 2011 Twitter, Inc. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. * ============================================================ */ !function( $ ){ "use strict" /* DROPDOWN PLUGIN DEFINITION * ========================== */ $.fn.dropdown = function ( selector ) { return this.each(function () { $(this).delegate(selector || d, 'click', function (e) { var li = $(this).parent('li') , isActive = li.hasClass('open') clearMenus() !isActive && li.toggleClass('open') return false }) }) } /* APPLY TO STANDARD DROPDOWN ELEMENTS * =================================== */ var d = 'a.menu, .dropdown-toggle' function clearMenus() { $(d).parent('li').removeClass('open') } $(function () { $('html').bind("click", clearMenus) $('body').dropdown( '[data-dropdown] a.menu, [data-dropdown] .dropdown-toggle' ) }) }( window.jQuery || window.ender ); ansible-1.7.2/docsite/_static/bootstrap-scrollspy.js000066400000000000000000000056721241061774000226350ustar00rootroot00000000000000/* ============================================================= * bootstrap-scrollspy.js v1.4.0 * http://twitter.github.com/bootstrap/javascript.html#scrollspy * ============================================================= * Copyright 2011 Twitter, Inc. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. * ============================================================== */ !function ( $ ) { "use strict" var $window = $(window) function ScrollSpy( topbar, selector ) { var processScroll = $.proxy(this.processScroll, this) this.$topbar = $(topbar) this.selector = selector || 'li > a' this.refresh() this.$topbar.delegate(this.selector, 'click', processScroll) $window.scroll(processScroll) this.processScroll() } ScrollSpy.prototype = { refresh: function () { this.targets = this.$topbar.find(this.selector).map(function () { var href = $(this).attr('href') return /^#\w/.test(href) && $(href).length ? href : null }) this.offsets = $.map(this.targets, function (id) { return $(id).offset().top }) } , processScroll: function () { var scrollTop = $window.scrollTop() + 10 , offsets = this.offsets , targets = this.targets , activeTarget = this.activeTarget , i for (i = offsets.length; i--;) { activeTarget != targets[i] && scrollTop >= offsets[i] && (!offsets[i + 1] || scrollTop <= offsets[i + 1]) && this.activateButton( targets[i] ) } } , activateButton: function (target) { this.activeTarget = target this.$topbar .find(this.selector).parent('.active') .removeClass('active') this.$topbar .find(this.selector + '[href="' + target + '"]') .parent('li') .addClass('active') } } /* SCROLLSPY PLUGIN DEFINITION * =========================== */ $.fn.scrollSpy = function( options ) { var scrollspy = this.data('scrollspy') if (!scrollspy) { return this.each(function () { $(this).data('scrollspy', new ScrollSpy( this, options )) }) } if ( options === true ) { return scrollspy } if ( typeof options == 'string' ) { scrollspy[options]() } return this } $(document).ready(function () { $('body').scrollSpy('[data-scrollspy] li > a') }) }( window.jQuery || window.ender );ansible-1.7.2/docsite/_static/bootstrap-sphinx.css000066400000000000000000000002731241061774000222600ustar00rootroot00000000000000/* * bootstrap-sphinx.css * ~~~~~~~~~~~~~~~~~~~~ * * Sphinx stylesheet -- Twitter Bootstrap theme. */ body { padding-top: 42px; } div.documentwrapper { float: left; width: 100%; }ansible-1.7.2/docsite/_static/bootstrap.css000066400000000000000000001560751241061774000207650ustar00rootroot00000000000000/*! * Bootstrap v1.4.0 * * Copyright 2011 Twitter, Inc * Licensed under the Apache License v2.0 * http://www.apache.org/licenses/LICENSE-2.0 * * Designed and built with all the love in the world @twitter by @mdo and @fat. * Date: Sun Nov 20 21:42:29 PST 2011 */ /* Reset.less * Props to Eric Meyer (meyerweb.com) for his CSS reset file. We're using an adapted version here that cuts out some of the reset HTML elements we will never need here (i.e., dfn, samp, etc). * ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- */ html, body { margin: 0; padding: 0; } h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, cite, code, del, dfn, em, img, q, s, samp, small, strike, strong, sub, sup, tt, var, dd, dl, dt, li, ol, ul, fieldset, form, label, legend, button, table, caption, tbody, tfoot, thead, tr, th, td { margin: 0; padding: 0; border: 0; font-weight: normal; font-style: normal; font-size: 100%; line-height: 1; font-family: inherit; } table { border-collapse: collapse; border-spacing: 0; } ol, ul { list-style: none; } q:before, q:after, blockquote:before, blockquote:after { content: ""; } html { overflow-y: scroll; font-size: 100%; -webkit-text-size-adjust: 100%; -ms-text-size-adjust: 100%; } a:focus { outline: thin dotted; } a:hover, a:active { outline: 0; } article, aside, details, figcaption, figure, footer, header, hgroup, nav, section { display: block; } audio, canvas, video { display: inline-block; *display: inline; *zoom: 1; } audio:not([controls]) { display: none; } sub, sup { font-size: 75%; line-height: 0; position: relative; vertical-align: baseline; } sup { top: -0.5em; } sub { bottom: -0.25em; } img { border: 0; -ms-interpolation-mode: bicubic; } button, input, select, textarea { font-size: 100%; margin: 0; vertical-align: baseline; *vertical-align: middle; } button, input { line-height: normal; *overflow: visible; } button::-moz-focus-inner, input::-moz-focus-inner { border: 0; padding: 0; } button, input[type="button"], input[type="reset"], input[type="submit"] { cursor: pointer; -webkit-appearance: button; } input[type="search"] { -webkit-appearance: textfield; -webkit-box-sizing: content-box; -moz-box-sizing: content-box; box-sizing: content-box; } input[type="search"]::-webkit-search-decoration { -webkit-appearance: none; } textarea { overflow: auto; vertical-align: top; } /* Variables.less * Variables to customize the look and feel of Bootstrap * ----------------------------------------------------- */ /* Mixins.less * Snippets of reusable CSS to develop faster and keep code readable * ----------------------------------------------------------------- */ /* * Scaffolding * Basic and global styles for generating a grid system, structural layout, and page templates * ------------------------------------------------------------------------------------------- */ body { background-color: #ffffff; margin: 0; font-family: "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: 13px; font-weight: normal; line-height: 18px; color: #404040; } .container { width: 940px; margin-left: auto; margin-right: auto; zoom: 1; } .container:before, .container:after { display: table; content: ""; zoom: 1; } .container:after { clear: both; } .container-fluid { position: relative; min-width: 940px; padding-left: 20px; padding-right: 20px; zoom: 1; } .container-fluid:before, .container-fluid:after { display: table; content: ""; zoom: 1; } .container-fluid:after { clear: both; } .container-fluid > .sidebar { position: absolute; top: 0; left: 20px; width: 220px; } .container-fluid > .content { margin-left: 240px; } a { color: #0069d6; text-decoration: none; line-height: inherit; font-weight: inherit; } a:hover { color: #00438a; text-decoration: underline; } .pull-right { float: right; } .pull-left { float: left; } .hide { display: none; } .show { display: block; } .row { zoom: 1; margin-left: -20px; } .row:before, .row:after { display: table; content: ""; zoom: 1; } .row:after { clear: both; } .row > [class*="span"] { display: inline; float: left; margin-left: 20px; } .span1 { width: 40px; } .span2 { width: 100px; } .span3 { width: 160px; } .span4 { width: 220px; } .span5 { width: 280px; } .span6 { width: 340px; } .span7 { width: 400px; } .span8 { width: 460px; } .span9 { width: 520px; } .span10 { width: 580px; } .span11 { width: 640px; } .span12 { width: 700px; } .span13 { width: 760px; } .span14 { width: 820px; } .span15 { width: 880px; } .span16 { width: 940px; } .span17 { width: 1000px; } .span18 { width: 1060px; } .span19 { width: 1120px; } .span20 { width: 1180px; } .span21 { width: 1240px; } .span22 { width: 1300px; } .span23 { width: 1360px; } .span24 { width: 1420px; } .row > .offset1 { margin-left: 80px; } .row > .offset2 { margin-left: 140px; } .row > .offset3 { margin-left: 200px; } .row > .offset4 { margin-left: 260px; } .row > .offset5 { margin-left: 320px; } .row > .offset6 { margin-left: 380px; } .row > .offset7 { margin-left: 440px; } .row > .offset8 { margin-left: 500px; } .row > .offset9 { margin-left: 560px; } .row > .offset10 { margin-left: 620px; } .row > .offset11 { margin-left: 680px; } .row > .offset12 { margin-left: 740px; } .span-one-third { width: 300px; } .span-two-thirds { width: 620px; } .row > .offset-one-third { margin-left: 340px; } .row > .offset-two-thirds { margin-left: 660px; } /* Typography.less * Headings, body text, lists, code, and more for a versatile and durable typography system * ---------------------------------------------------------------------------------------- */ p { font-size: 13px; font-weight: normal; line-height: 18px; margin-bottom: 9px; } p small { font-size: 11px; color: #bfbfbf; } h1, h2, h3, h4, h5, h6 { font-weight: bold; color: #404040; } h1 small, h2 small, h3 small, h4 small, h5 small, h6 small { color: #bfbfbf; } h1 { margin-bottom: 18px; font-size: 30px; line-height: 36px; } h1 small { font-size: 18px; } h2 { font-size: 24px; line-height: 36px; } h2 small { font-size: 14px; } h3, h4, h5, h6 { line-height: 36px; } h3 { font-size: 18px; } h3 small { font-size: 14px; } h4 { font-size: 16px; } h4 small { font-size: 12px; } h5 { font-size: 14px; } h6 { font-size: 13px; color: #bfbfbf; text-transform: uppercase; } ul, ol { margin: 0 0 18px 25px; } ul ul, ul ol, ol ol, ol ul { margin-bottom: 0; } ul { list-style: disc; } ol { list-style: decimal; } li { line-height: 18px; color: #808080; } ul.unstyled { list-style: none; margin-left: 0; } dl { margin-bottom: 18px; } dl dt, dl dd { line-height: 18px; } dl dt { font-weight: bold; } dl dd { margin-left: 9px; } hr { margin: 20px 0 19px; border: 0; border-bottom: 1px solid #eee; } strong { font-style: inherit; font-weight: bold; } em { font-style: italic; font-weight: inherit; line-height: inherit; } .muted { color: #bfbfbf; } blockquote { margin-bottom: 18px; border-left: 5px solid #eee; padding-left: 15px; } blockquote p { font-size: 14px; font-weight: 300; line-height: 18px; margin-bottom: 0; } blockquote small { display: block; font-size: 12px; font-weight: 300; line-height: 18px; color: #bfbfbf; } blockquote small:before { content: '\2014 \00A0'; } address { display: block; line-height: 18px; margin-bottom: 18px; } code, pre { padding: 0 3px 2px; font-family: Monaco, Andale Mono, Courier New, monospace; font-size: 12px; -webkit-border-radius: 3px; -moz-border-radius: 3px; border-radius: 3px; } .module { font-family: Monaco, Andale Mono, Courier New, monospace; font-size: 12px; } code { color: rgba(0, 0, 0, 0.75); } pre { background-color: #f5f5f5; display: block; padding: 8.5px; margin: 0 0 18px; line-height: 18px; font-size: 12px; border: 1px solid #ccc; border: 1px solid rgba(0, 0, 0, 0.15); -webkit-border-radius: 3px; -moz-border-radius: 3px; border-radius: 3px; white-space: pre; white-space: pre-wrap; word-wrap: break-word; } /* Forms.less * Base styles for various input types, form layouts, and states * ------------------------------------------------------------- */ form { margin-bottom: 18px; } fieldset { margin-bottom: 18px; padding-top: 18px; } fieldset legend { display: block; padding-left: 150px; font-size: 19.5px; line-height: 1; color: #404040; *padding: 0 0 5px 145px; /* IE6-7 */ *line-height: 1.5; /* IE6-7 */ } form .clearfix { margin-bottom: 18px; zoom: 1; } form .clearfix:before, form .clearfix:after { display: table; content: ""; zoom: 1; } form .clearfix:after { clear: both; } label, input, select, textarea { font-family: "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: 13px; font-weight: normal; line-height: normal; } label { padding-top: 6px; font-size: 13px; line-height: 18px; float: left; width: 130px; text-align: right; color: #404040; } form .input { margin-left: 150px; } input[type=checkbox], input[type=radio] { cursor: pointer; } input, textarea, select, .uneditable-input { display: inline-block; width: 210px; height: 18px; padding: 4px; font-size: 13px; line-height: 18px; color: #808080; border: 1px solid #ccc; -webkit-border-radius: 3px; -moz-border-radius: 3px; border-radius: 3px; } select { padding: initial; } input[type=checkbox], input[type=radio] { width: auto; height: auto; padding: 0; margin: 3px 0; *margin-top: 0; /* IE6-7 */ line-height: normal; border: none; } input[type=file] { background-color: #ffffff; padding: initial; border: initial; line-height: initial; -webkit-box-shadow: none; -moz-box-shadow: none; box-shadow: none; } input[type=button], input[type=reset], input[type=submit] { width: auto; height: auto; } select, input[type=file] { height: 27px; *height: auto; line-height: 27px; *margin-top: 4px; /* For IE7, add top margin to align select with labels */ } select[multiple] { height: inherit; background-color: #ffffff; } textarea { height: auto; } .uneditable-input { background-color: #ffffff; display: block; border-color: #eee; -webkit-box-shadow: inset 0 1px 2px rgba(0, 0, 0, 0.025); -moz-box-shadow: inset 0 1px 2px rgba(0, 0, 0, 0.025); box-shadow: inset 0 1px 2px rgba(0, 0, 0, 0.025); cursor: not-allowed; } :-moz-placeholder { color: #bfbfbf; } ::-webkit-input-placeholder { color: #bfbfbf; } input, textarea { -webkit-transition: border linear 0.2s, box-shadow linear 0.2s; -moz-transition: border linear 0.2s, box-shadow linear 0.2s; -ms-transition: border linear 0.2s, box-shadow linear 0.2s; -o-transition: border linear 0.2s, box-shadow linear 0.2s; transition: border linear 0.2s, box-shadow linear 0.2s; -webkit-box-shadow: inset 0 1px 3px rgba(0, 0, 0, 0.1); -moz-box-shadow: inset 0 1px 3px rgba(0, 0, 0, 0.1); box-shadow: inset 0 1px 3px rgba(0, 0, 0, 0.1); } input:focus, textarea:focus { outline: 0; border-color: rgba(82, 168, 236, 0.8); -webkit-box-shadow: inset 0 1px 3px rgba(0, 0, 0, 0.1), 0 0 8px rgba(82, 168, 236, 0.6); -moz-box-shadow: inset 0 1px 3px rgba(0, 0, 0, 0.1), 0 0 8px rgba(82, 168, 236, 0.6); box-shadow: inset 0 1px 3px rgba(0, 0, 0, 0.1), 0 0 8px rgba(82, 168, 236, 0.6); } input[type=file]:focus, input[type=checkbox]:focus, select:focus { -webkit-box-shadow: none; -moz-box-shadow: none; box-shadow: none; outline: 1px dotted #666; } form .clearfix.error > label, form .clearfix.error .help-block, form .clearfix.error .help-inline { color: #b94a48; } form .clearfix.error input, form .clearfix.error textarea { color: #b94a48; border-color: #ee5f5b; } form .clearfix.error input:focus, form .clearfix.error textarea:focus { border-color: #e9322d; -webkit-box-shadow: 0 0 6px #f8b9b7; -moz-box-shadow: 0 0 6px #f8b9b7; box-shadow: 0 0 6px #f8b9b7; } form .clearfix.error .input-prepend .add-on, form .clearfix.error .input-append .add-on { color: #b94a48; background-color: #fce6e6; border-color: #b94a48; } form .clearfix.warning > label, form .clearfix.warning .help-block, form .clearfix.warning .help-inline { color: #c09853; } form .clearfix.warning input, form .clearfix.warning textarea { color: #c09853; border-color: #ccae64; } form .clearfix.warning input:focus, form .clearfix.warning textarea:focus { border-color: #be9a3f; -webkit-box-shadow: 0 0 6px #e5d6b1; -moz-box-shadow: 0 0 6px #e5d6b1; box-shadow: 0 0 6px #e5d6b1; } form .clearfix.warning .input-prepend .add-on, form .clearfix.warning .input-append .add-on { color: #c09853; background-color: #d2b877; border-color: #c09853; } form .clearfix.success > label, form .clearfix.success .help-block, form .clearfix.success .help-inline { color: #468847; } form .clearfix.success input, form .clearfix.success textarea { color: #468847; border-color: #57a957; } form .clearfix.success input:focus, form .clearfix.success textarea:focus { border-color: #458845; -webkit-box-shadow: 0 0 6px #9acc9a; -moz-box-shadow: 0 0 6px #9acc9a; box-shadow: 0 0 6px #9acc9a; } form .clearfix.success .input-prepend .add-on, form .clearfix.success .input-append .add-on { color: #468847; background-color: #bcddbc; border-color: #468847; } .input-mini, input.mini, textarea.mini, select.mini { width: 60px; } .input-small, input.small, textarea.small, select.small { width: 90px; } .input-medium, input.medium, textarea.medium, select.medium { width: 150px; } .input-large, input.large, textarea.large, select.large { width: 210px; } .input-xlarge, input.xlarge, textarea.xlarge, select.xlarge { width: 270px; } .input-xxlarge, input.xxlarge, textarea.xxlarge, select.xxlarge { width: 530px; } textarea.xxlarge { overflow-y: auto; } input.span1, textarea.span1 { display: inline-block; float: none; width: 30px; margin-left: 0; } input.span2, textarea.span2 { display: inline-block; float: none; width: 90px; margin-left: 0; } input.span3, textarea.span3 { display: inline-block; float: none; width: 150px; margin-left: 0; } input.span4, textarea.span4 { display: inline-block; float: none; width: 210px; margin-left: 0; } input.span5, textarea.span5 { display: inline-block; float: none; width: 270px; margin-left: 0; } input.span6, textarea.span6 { display: inline-block; float: none; width: 330px; margin-left: 0; } input.span7, textarea.span7 { display: inline-block; float: none; width: 390px; margin-left: 0; } input.span8, textarea.span8 { display: inline-block; float: none; width: 450px; margin-left: 0; } input.span9, textarea.span9 { display: inline-block; float: none; width: 510px; margin-left: 0; } input.span10, textarea.span10 { display: inline-block; float: none; width: 570px; margin-left: 0; } input.span11, textarea.span11 { display: inline-block; float: none; width: 630px; margin-left: 0; } input.span12, textarea.span12 { display: inline-block; float: none; width: 690px; margin-left: 0; } input.span13, textarea.span13 { display: inline-block; float: none; width: 750px; margin-left: 0; } input.span14, textarea.span14 { display: inline-block; float: none; width: 810px; margin-left: 0; } input.span15, textarea.span15 { display: inline-block; float: none; width: 870px; margin-left: 0; } input.span16, textarea.span16 { display: inline-block; float: none; width: 930px; margin-left: 0; } input[disabled], select[disabled], textarea[disabled], input[readonly], select[readonly], textarea[readonly] { background-color: #f5f5f5; border-color: #ddd; cursor: not-allowed; } .actions { background: #f5f5f5; margin-top: 18px; margin-bottom: 18px; padding: 17px 20px 18px 150px; border-top: 1px solid #ddd; -webkit-border-radius: 0 0 3px 3px; -moz-border-radius: 0 0 3px 3px; border-radius: 0 0 3px 3px; } .actions .secondary-action { float: right; } .actions .secondary-action a { line-height: 30px; } .actions .secondary-action a:hover { text-decoration: underline; } .help-inline, .help-block { font-size: 13px; line-height: 18px; color: #bfbfbf; } .help-inline { padding-left: 5px; *position: relative; /* IE6-7 */ *top: -5px; /* IE6-7 */ } .help-block { display: block; max-width: 600px; } .inline-inputs { color: #808080; } .inline-inputs span { padding: 0 2px 0 1px; } .input-prepend input, .input-append input { -webkit-border-radius: 0 3px 3px 0; -moz-border-radius: 0 3px 3px 0; border-radius: 0 3px 3px 0; } .input-prepend .add-on, .input-append .add-on { position: relative; background: #f5f5f5; border: 1px solid #ccc; z-index: 2; float: left; display: block; width: auto; min-width: 16px; height: 18px; padding: 4px 4px 4px 5px; margin-right: -1px; font-weight: normal; line-height: 18px; color: #bfbfbf; text-align: center; text-shadow: 0 1px 0 #ffffff; -webkit-border-radius: 3px 0 0 3px; -moz-border-radius: 3px 0 0 3px; border-radius: 3px 0 0 3px; } .input-prepend .active, .input-append .active { background: #a9dba9; border-color: #46a546; } .input-prepend .add-on { *margin-top: 1px; /* IE6-7 */ } .input-append input { float: left; -webkit-border-radius: 3px 0 0 3px; -moz-border-radius: 3px 0 0 3px; border-radius: 3px 0 0 3px; } .input-append .add-on { -webkit-border-radius: 0 3px 3px 0; -moz-border-radius: 0 3px 3px 0; border-radius: 0 3px 3px 0; margin-right: 0; margin-left: -1px; } .inputs-list { margin: 0 0 5px; width: 100%; } .inputs-list li { display: block; padding: 0; width: 100%; } .inputs-list label { display: block; float: none; width: auto; padding: 0; margin-left: 20px; line-height: 18px; text-align: left; white-space: normal; } .inputs-list label strong { color: #808080; } .inputs-list label small { font-size: 11px; font-weight: normal; } .inputs-list .inputs-list { margin-left: 25px; margin-bottom: 10px; padding-top: 0; } .inputs-list:first-child { padding-top: 6px; } .inputs-list li + li { padding-top: 2px; } .inputs-list input[type=radio], .inputs-list input[type=checkbox] { margin-bottom: 0; margin-left: -20px; float: left; } .form-stacked { padding-left: 20px; } .form-stacked fieldset { padding-top: 9px; } .form-stacked legend { padding-left: 0; } .form-stacked label { display: block; float: none; width: auto; font-weight: bold; text-align: left; line-height: 20px; padding-top: 0; } .form-stacked .clearfix { margin-bottom: 9px; } .form-stacked .clearfix div.input { margin-left: 0; } .form-stacked .inputs-list { margin-bottom: 0; } .form-stacked .inputs-list li { padding-top: 0; } .form-stacked .inputs-list li label { font-weight: normal; padding-top: 0; } .form-stacked div.clearfix.error { padding-top: 10px; padding-bottom: 10px; padding-left: 10px; margin-top: 0; margin-left: -10px; } .form-stacked .actions { margin-left: -20px; padding-left: 20px; } /* * Tables.less * Tables for, you guessed it, tabular data * ---------------------------------------- */ table { width: 100%; margin-bottom: 18px; padding: 0; font-size: 13px; border-collapse: collapse; } table th, table td { padding: 10px 10px 9px; line-height: 18px; text-align: left; } table th { padding-top: 9px; font-weight: bold; vertical-align: middle; } table td { vertical-align: top; border-top: 1px solid #ddd; } table tbody th { border-top: 1px solid #ddd; vertical-align: top; } .condensed-table th, .condensed-table td { padding: 5px 5px 4px; } .bordered-table { border: 1px solid #ddd; border-collapse: separate; *border-collapse: collapse; /* IE7, collapse table to remove spacing */ -webkit-border-radius: 4px; -moz-border-radius: 4px; border-radius: 4px; } .bordered-table th + th, .bordered-table td + td, .bordered-table th + td { border-left: 1px solid #ddd; } .bordered-table thead tr:first-child th:first-child, .bordered-table tbody tr:first-child td:first-child { -webkit-border-radius: 4px 0 0 0; -moz-border-radius: 4px 0 0 0; border-radius: 4px 0 0 0; } .bordered-table thead tr:first-child th:last-child, .bordered-table tbody tr:first-child td:last-child { -webkit-border-radius: 0 4px 0 0; -moz-border-radius: 0 4px 0 0; border-radius: 0 4px 0 0; } .bordered-table tbody tr:last-child td:first-child { -webkit-border-radius: 0 0 0 4px; -moz-border-radius: 0 0 0 4px; border-radius: 0 0 0 4px; } .bordered-table tbody tr:last-child td:last-child { -webkit-border-radius: 0 0 4px 0; -moz-border-radius: 0 0 4px 0; border-radius: 0 0 4px 0; } table .span1 { width: 20px; } table .span2 { width: 60px; } table .span3 { width: 100px; } table .span4 { width: 140px; } table .span5 { width: 180px; } table .span6 { width: 220px; } table .span7 { width: 260px; } table .span8 { width: 300px; } table .span9 { width: 340px; } table .span10 { width: 380px; } table .span11 { width: 420px; } table .span12 { width: 460px; } table .span13 { width: 500px; } table .span14 { width: 540px; } table .span15 { width: 580px; } table .span16 { width: 620px; } .zebra-striped tbody tr:nth-child(odd) td, .zebra-striped tbody tr:nth-child(odd) th { background-color: #f9f9f9; } .zebra-striped tbody tr:hover td, .zebra-striped tbody tr:hover th { background-color: #f5f5f5; } table .header { cursor: pointer; } table .header:after { content: ""; float: right; margin-top: 7px; border-width: 0 4px 4px; border-style: solid; border-color: #000 transparent; visibility: hidden; } table .headerSortUp, table .headerSortDown { background-color: rgba(141, 192, 219, 0.25); text-shadow: 0 1px 1px rgba(255, 255, 255, 0.75); } table .header:hover:after { visibility: visible; } table .headerSortDown:after, table .headerSortDown:hover:after { visibility: visible; filter: alpha(opacity=60); -khtml-opacity: 0.6; -moz-opacity: 0.6; opacity: 0.6; } table .headerSortUp:after { border-bottom: none; border-left: 4px solid transparent; border-right: 4px solid transparent; border-top: 4px solid #000; visibility: visible; -webkit-box-shadow: none; -moz-box-shadow: none; box-shadow: none; filter: alpha(opacity=60); -khtml-opacity: 0.6; -moz-opacity: 0.6; opacity: 0.6; } table .blue { color: #049cdb; border-bottom-color: #049cdb; } table .headerSortUp.blue, table .headerSortDown.blue { background-color: #ade6fe; } table .green { color: #46a546; border-bottom-color: #46a546; } table .headerSortUp.green, table .headerSortDown.green { background-color: #cdeacd; } table .red { color: #9d261d; border-bottom-color: #9d261d; } table .headerSortUp.red, table .headerSortDown.red { background-color: #f4c8c5; } table .yellow { color: #ffc40d; border-bottom-color: #ffc40d; } table .headerSortUp.yellow, table .headerSortDown.yellow { background-color: #fff6d9; } table .orange { color: #f89406; border-bottom-color: #f89406; } table .headerSortUp.orange, table .headerSortDown.orange { background-color: #fee9cc; } table .purple { color: #7a43b6; border-bottom-color: #7a43b6; } table .headerSortUp.purple, table .headerSortDown.purple { background-color: #e2d5f0; } /* Patterns.less * Repeatable UI elements outside the base styles provided from the scaffolding * ---------------------------------------------------------------------------- */ .topbar { height: 40px; position: fixed; top: 0; left: 0; right: 0; z-index: 10000; overflow: visible; } .topbar a { color: #bfbfbf; text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.25); } .topbar h3 a:hover, .topbar .brand:hover, .topbar ul .active > a { background-color: #333; background-color: rgba(255, 255, 255, 0.05); color: #ffffff; text-decoration: none; } .topbar h3 { position: relative; } .topbar h3 a, .topbar .brand { float: left; display: block; padding: 8px 20px 12px; margin-left: -20px; color: #ffffff; font-size: 20px; font-weight: 200; line-height: 1; } .topbar p { margin: 0; line-height: 40px; } .topbar p a:hover { background-color: transparent; color: #ffffff; } .topbar form { float: left; margin: 5px 0 0 0; position: relative; filter: alpha(opacity=100); -khtml-opacity: 1; -moz-opacity: 1; opacity: 1; } .topbar form.pull-right { float: right; } .topbar input { background-color: #444; background-color: rgba(255, 255, 255, 0.3); font-family: "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: normal; font-weight: 13px; line-height: 1; padding: 4px 9px; color: #ffffff; color: rgba(255, 255, 255, 0.75); border: 1px solid #111; -webkit-border-radius: 4px; -moz-border-radius: 4px; border-radius: 4px; -webkit-box-shadow: inset 0 1px 2px rgba(0, 0, 0, 0.1), 0 1px 0px rgba(255, 255, 255, 0.25); -moz-box-shadow: inset 0 1px 2px rgba(0, 0, 0, 0.1), 0 1px 0px rgba(255, 255, 255, 0.25); box-shadow: inset 0 1px 2px rgba(0, 0, 0, 0.1), 0 1px 0px rgba(255, 255, 255, 0.25); -webkit-transition: none; -moz-transition: none; -ms-transition: none; -o-transition: none; transition: none; } .topbar input:-moz-placeholder { color: #e6e6e6; } .topbar input::-webkit-input-placeholder { color: #e6e6e6; } .topbar input:hover { background-color: #bfbfbf; background-color: rgba(255, 255, 255, 0.5); color: #ffffff; } .topbar input:focus, .topbar input.focused { outline: 0; background-color: #ffffff; color: #404040; text-shadow: 0 1px 0 #ffffff; border: 0; padding: 5px 10px; -webkit-box-shadow: 0 0 3px rgba(0, 0, 0, 0.15); -moz-box-shadow: 0 0 3px rgba(0, 0, 0, 0.15); box-shadow: 0 0 3px rgba(0, 0, 0, 0.15); } .topbar-inner, .topbar .fill { background-color: #222; background-color: #222222; background-repeat: repeat-x; background-image: -khtml-gradient(linear, left top, left bottom, from(#333333), to(#222222)); background-image: -moz-linear-gradient(top, #333333, #222222); background-image: -ms-linear-gradient(top, #333333, #222222); background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%, #333333), color-stop(100%, #222222)); background-image: -webkit-linear-gradient(top, #333333, #222222); background-image: -o-linear-gradient(top, #333333, #222222); background-image: linear-gradient(top, #333333, #222222); filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#333333', endColorstr='#222222', GradientType=0); -webkit-box-shadow: 0 1px 3px rgba(0, 0, 0, 0.25), inset 0 -1px 0 rgba(0, 0, 0, 0.1); -moz-box-shadow: 0 1px 3px rgba(0, 0, 0, 0.25), inset 0 -1px 0 rgba(0, 0, 0, 0.1); box-shadow: 0 1px 3px rgba(0, 0, 0, 0.25), inset 0 -1px 0 rgba(0, 0, 0, 0.1); } .topbar div > ul, .nav { display: block; float: left; margin: 0 10px 0 0; position: relative; left: 0; } .topbar div > ul > li, .nav > li { display: block; float: left; } .topbar div > ul a, .nav a { display: block; float: none; padding: 10px 10px 11px; line-height: 19px; text-decoration: none; } .topbar div > ul a:hover, .nav a:hover { color: #ffffff; text-decoration: none; } .topbar div > ul .active > a, .nav .active > a { background-color: #222; background-color: rgba(0, 0, 0, 0.5); } .topbar div > ul.secondary-nav, .nav.secondary-nav { float: right; margin-left: 10px; margin-right: 0; } .topbar div > ul.secondary-nav .menu-dropdown, .nav.secondary-nav .menu-dropdown, .topbar div > ul.secondary-nav .dropdown-menu, .nav.secondary-nav .dropdown-menu { right: 0; border: 0; } .topbar div > ul a.menu:hover, .nav a.menu:hover, .topbar div > ul li.open .menu, .nav li.open .menu, .topbar div > ul .dropdown-toggle:hover, .nav .dropdown-toggle:hover, .topbar div > ul .dropdown.open .dropdown-toggle, .nav .dropdown.open .dropdown-toggle { background: #444; background: rgba(255, 255, 255, 0.05); } .topbar div > ul .menu-dropdown, .nav .menu-dropdown, .topbar div > ul .dropdown-menu, .nav .dropdown-menu { background-color: #333; } .topbar div > ul .menu-dropdown a.menu, .nav .menu-dropdown a.menu, .topbar div > ul .dropdown-menu a.menu, .nav .dropdown-menu a.menu, .topbar div > ul .menu-dropdown .dropdown-toggle, .nav .menu-dropdown .dropdown-toggle, .topbar div > ul .dropdown-menu .dropdown-toggle, .nav .dropdown-menu .dropdown-toggle { color: #ffffff; } .topbar div > ul .menu-dropdown a.menu.open, .nav .menu-dropdown a.menu.open, .topbar div > ul .dropdown-menu a.menu.open, .nav .dropdown-menu a.menu.open, .topbar div > ul .menu-dropdown .dropdown-toggle.open, .nav .menu-dropdown .dropdown-toggle.open, .topbar div > ul .dropdown-menu .dropdown-toggle.open, .nav .dropdown-menu .dropdown-toggle.open { background: #444; background: rgba(255, 255, 255, 0.05); } .topbar div > ul .menu-dropdown li a, .nav .menu-dropdown li a, .topbar div > ul .dropdown-menu li a, .nav .dropdown-menu li a { color: #999; text-shadow: 0 1px 0 rgba(0, 0, 0, 0.5); } .topbar div > ul .menu-dropdown li a:hover, .nav .menu-dropdown li a:hover, .topbar div > ul .dropdown-menu li a:hover, .nav .dropdown-menu li a:hover { background-color: #191919; background-repeat: repeat-x; background-image: -khtml-gradient(linear, left top, left bottom, from(#292929), to(#191919)); background-image: -moz-linear-gradient(top, #292929, #191919); background-image: -ms-linear-gradient(top, #292929, #191919); background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%, #292929), color-stop(100%, #191919)); background-image: -webkit-linear-gradient(top, #292929, #191919); background-image: -o-linear-gradient(top, #292929, #191919); background-image: linear-gradient(top, #292929, #191919); filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#292929', endColorstr='#191919', GradientType=0); color: #ffffff; } .topbar div > ul .menu-dropdown .active a, .nav .menu-dropdown .active a, .topbar div > ul .dropdown-menu .active a, .nav .dropdown-menu .active a { color: #ffffff; } .topbar div > ul .menu-dropdown .divider, .nav .menu-dropdown .divider, .topbar div > ul .dropdown-menu .divider, .nav .dropdown-menu .divider { background-color: #222; border-color: #444; } .topbar ul .menu-dropdown li a, .topbar ul .dropdown-menu li a { padding: 4px 15px; } li.menu, .dropdown { position: relative; } a.menu:after, .dropdown-toggle:after { width: 0; height: 0; display: inline-block; content: "↓"; text-indent: -99999px; vertical-align: top; margin-top: 8px; margin-left: 4px; border-left: 4px solid transparent; border-right: 4px solid transparent; border-top: 4px solid #ffffff; filter: alpha(opacity=50); -khtml-opacity: 0.5; -moz-opacity: 0.5; opacity: 0.5; } .menu-dropdown, .dropdown-menu { background-color: #ffffff; float: left; display: none; position: absolute; top: 40px; z-index: 900; min-width: 160px; max-width: 220px; _width: 160px; margin-left: 0; margin-right: 0; padding: 6px 0; zoom: 1; border-color: #999; border-color: rgba(0, 0, 0, 0.2); border-style: solid; border-width: 0 1px 1px; -webkit-border-radius: 0 0 6px 6px; -moz-border-radius: 0 0 6px 6px; border-radius: 0 0 6px 6px; -webkit-box-shadow: 0 2px 4px rgba(0, 0, 0, 0.2); -moz-box-shadow: 0 2px 4px rgba(0, 0, 0, 0.2); box-shadow: 0 2px 4px rgba(0, 0, 0, 0.2); -webkit-background-clip: padding-box; -moz-background-clip: padding-box; background-clip: padding-box; } .menu-dropdown li, .dropdown-menu li { float: none; display: block; background-color: none; } .menu-dropdown .divider, .dropdown-menu .divider { height: 1px; margin: 5px 0; overflow: hidden; background-color: #eee; border-bottom: 1px solid #ffffff; } .topbar .dropdown-menu a, .dropdown-menu a { display: block; padding: 4px 15px; clear: both; font-weight: normal; line-height: 18px; color: #808080; text-shadow: 0 1px 0 #ffffff; } .topbar .dropdown-menu a:hover, .dropdown-menu a:hover, .topbar .dropdown-menu a.hover, .dropdown-menu a.hover { background-color: #dddddd; background-repeat: repeat-x; background-image: -khtml-gradient(linear, left top, left bottom, from(#eeeeee), to(#dddddd)); background-image: -moz-linear-gradient(top, #eeeeee, #dddddd); background-image: -ms-linear-gradient(top, #eeeeee, #dddddd); background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%, #eeeeee), color-stop(100%, #dddddd)); background-image: -webkit-linear-gradient(top, #eeeeee, #dddddd); background-image: -o-linear-gradient(top, #eeeeee, #dddddd); background-image: linear-gradient(top, #eeeeee, #dddddd); filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#eeeeee', endColorstr='#dddddd', GradientType=0); color: #404040; text-decoration: none; -webkit-box-shadow: inset 0 1px 0 rgba(0, 0, 0, 0.025), inset 0 -1px rgba(0, 0, 0, 0.025); -moz-box-shadow: inset 0 1px 0 rgba(0, 0, 0, 0.025), inset 0 -1px rgba(0, 0, 0, 0.025); box-shadow: inset 0 1px 0 rgba(0, 0, 0, 0.025), inset 0 -1px rgba(0, 0, 0, 0.025); } .open .menu, .dropdown.open .menu, .open .dropdown-toggle, .dropdown.open .dropdown-toggle { color: #ffffff; background: #ccc; background: rgba(0, 0, 0, 0.3); } .open .menu-dropdown, .dropdown.open .menu-dropdown, .open .dropdown-menu, .dropdown.open .dropdown-menu { display: block; } .tabs, .pills { margin: 0 0 18px; padding: 0; list-style: none; zoom: 1; } .tabs:before, .pills:before, .tabs:after, .pills:after { display: table; content: ""; zoom: 1; } .tabs:after, .pills:after { clear: both; } .tabs > li, .pills > li { float: left; } .tabs > li > a, .pills > li > a { display: block; } .tabs { border-color: #ddd; border-style: solid; border-width: 0 0 1px; } .tabs > li { position: relative; margin-bottom: -1px; } .tabs > li > a { padding: 0 15px; margin-right: 2px; line-height: 34px; border: 1px solid transparent; -webkit-border-radius: 4px 4px 0 0; -moz-border-radius: 4px 4px 0 0; border-radius: 4px 4px 0 0; } .tabs > li > a:hover { text-decoration: none; background-color: #eee; border-color: #eee #eee #ddd; } .tabs .active > a, .tabs .active > a:hover { color: #808080; background-color: #ffffff; border: 1px solid #ddd; border-bottom-color: transparent; cursor: default; } .tabs .menu-dropdown, .tabs .dropdown-menu { top: 35px; border-width: 1px; -webkit-border-radius: 0 6px 6px 6px; -moz-border-radius: 0 6px 6px 6px; border-radius: 0 6px 6px 6px; } .tabs a.menu:after, .tabs .dropdown-toggle:after { border-top-color: #999; margin-top: 15px; margin-left: 5px; } .tabs li.open.menu .menu, .tabs .open.dropdown .dropdown-toggle { border-color: #999; } .tabs li.open a.menu:after, .tabs .dropdown.open .dropdown-toggle:after { border-top-color: #555; } .pills a { margin: 5px 3px 5px 0; padding: 0 15px; line-height: 30px; text-shadow: 0 1px 1px #ffffff; -webkit-border-radius: 15px; -moz-border-radius: 15px; border-radius: 15px; } .pills a:hover { color: #ffffff; text-decoration: none; text-shadow: 0 1px 1px rgba(0, 0, 0, 0.25); background-color: #00438a; } .pills .active a { color: #ffffff; text-shadow: 0 1px 1px rgba(0, 0, 0, 0.25); background-color: #0069d6; } .pills-vertical > li { float: none; } .tab-content > .tab-pane, .pill-content > .pill-pane, .tab-content > div, .pill-content > div { display: none; } .tab-content > .active, .pill-content > .active { display: block; } .breadcrumb { padding: 7px 14px; margin: 0 0 18px; background-color: #f5f5f5; background-repeat: repeat-x; background-image: -khtml-gradient(linear, left top, left bottom, from(#ffffff), to(#f5f5f5)); background-image: -moz-linear-gradient(top, #ffffff, #f5f5f5); background-image: -ms-linear-gradient(top, #ffffff, #f5f5f5); background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%, #ffffff), color-stop(100%, #f5f5f5)); background-image: -webkit-linear-gradient(top, #ffffff, #f5f5f5); background-image: -o-linear-gradient(top, #ffffff, #f5f5f5); background-image: linear-gradient(top, #ffffff, #f5f5f5); filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#ffffff', endColorstr='#f5f5f5', GradientType=0); border: 1px solid #ddd; -webkit-border-radius: 3px; -moz-border-radius: 3px; border-radius: 3px; -webkit-box-shadow: inset 0 1px 0 #ffffff; -moz-box-shadow: inset 0 1px 0 #ffffff; box-shadow: inset 0 1px 0 #ffffff; } .breadcrumb li { display: inline; text-shadow: 0 1px 0 #ffffff; } .breadcrumb .divider { padding: 0 5px; color: #bfbfbf; } .breadcrumb .active a { color: #404040; } .hero-unit { background-color: #f5f5f5; margin-bottom: 30px; padding: 60px; -webkit-border-radius: 6px; -moz-border-radius: 6px; border-radius: 6px; } .hero-unit h1 { margin-bottom: 0; font-size: 60px; line-height: 1; letter-spacing: -1px; } .hero-unit p { font-size: 18px; font-weight: 200; line-height: 27px; } footer { margin-top: 17px; padding-top: 17px; border-top: 1px solid #eee; } .page-header { margin-bottom: 17px; border-bottom: 1px solid #ddd; -webkit-box-shadow: 0 1px 0 rgba(255, 255, 255, 0.5); -moz-box-shadow: 0 1px 0 rgba(255, 255, 255, 0.5); box-shadow: 0 1px 0 rgba(255, 255, 255, 0.5); } .page-header h1 { margin-bottom: 8px; } .btn.danger, .alert-message.danger, .btn.danger:hover, .alert-message.danger:hover, .btn.error, .alert-message.error, .btn.error:hover, .alert-message.error:hover, .btn.success, .alert-message.success, .btn.success:hover, .alert-message.success:hover, .btn.info, .alert-message.info, .btn.info:hover, .alert-message.info:hover { color: #ffffff; } .btn .close, .alert-message .close { font-family: Arial, sans-serif; line-height: 18px; } .btn.danger, .alert-message.danger, .btn.error, .alert-message.error { background-color: #c43c35; background-repeat: repeat-x; background-image: -khtml-gradient(linear, left top, left bottom, from(#ee5f5b), to(#c43c35)); background-image: -moz-linear-gradient(top, #ee5f5b, #c43c35); background-image: -ms-linear-gradient(top, #ee5f5b, #c43c35); background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%, #ee5f5b), color-stop(100%, #c43c35)); background-image: -webkit-linear-gradient(top, #ee5f5b, #c43c35); background-image: -o-linear-gradient(top, #ee5f5b, #c43c35); background-image: linear-gradient(top, #ee5f5b, #c43c35); filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#ee5f5b', endColorstr='#c43c35', GradientType=0); text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.25); border-color: #c43c35 #c43c35 #882a25; border-color: rgba(0, 0, 0, 0.1) rgba(0, 0, 0, 0.1) rgba(0, 0, 0, 0.25); } .btn.success, .alert-message.success { background-color: #57a957; background-repeat: repeat-x; background-image: -khtml-gradient(linear, left top, left bottom, from(#62c462), to(#57a957)); background-image: -moz-linear-gradient(top, #62c462, #57a957); background-image: -ms-linear-gradient(top, #62c462, #57a957); background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%, #62c462), color-stop(100%, #57a957)); background-image: -webkit-linear-gradient(top, #62c462, #57a957); background-image: -o-linear-gradient(top, #62c462, #57a957); background-image: linear-gradient(top, #62c462, #57a957); filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#62c462', endColorstr='#57a957', GradientType=0); text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.25); border-color: #57a957 #57a957 #3d773d; border-color: rgba(0, 0, 0, 0.1) rgba(0, 0, 0, 0.1) rgba(0, 0, 0, 0.25); } .btn.info, .alert-message.info { background-color: #339bb9; background-repeat: repeat-x; background-image: -khtml-gradient(linear, left top, left bottom, from(#5bc0de), to(#339bb9)); background-image: -moz-linear-gradient(top, #5bc0de, #339bb9); background-image: -ms-linear-gradient(top, #5bc0de, #339bb9); background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%, #5bc0de), color-stop(100%, #339bb9)); background-image: -webkit-linear-gradient(top, #5bc0de, #339bb9); background-image: -o-linear-gradient(top, #5bc0de, #339bb9); background-image: linear-gradient(top, #5bc0de, #339bb9); filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#5bc0de', endColorstr='#339bb9', GradientType=0); text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.25); border-color: #339bb9 #339bb9 #22697d; border-color: rgba(0, 0, 0, 0.1) rgba(0, 0, 0, 0.1) rgba(0, 0, 0, 0.25); } .btn { cursor: pointer; display: inline-block; background-color: #e6e6e6; background-repeat: no-repeat; background-image: -webkit-gradient(linear, 0 0, 0 100%, from(#ffffff), color-stop(25%, #ffffff), to(#e6e6e6)); background-image: -webkit-linear-gradient(#ffffff, #ffffff 25%, #e6e6e6); background-image: -moz-linear-gradient(top, #ffffff, #ffffff 25%, #e6e6e6); background-image: -ms-linear-gradient(#ffffff, #ffffff 25%, #e6e6e6); background-image: -o-linear-gradient(#ffffff, #ffffff 25%, #e6e6e6); background-image: linear-gradient(#ffffff, #ffffff 25%, #e6e6e6); filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#ffffff', endColorstr='#e6e6e6', GradientType=0); padding: 5px 14px 6px; text-shadow: 0 1px 1px rgba(255, 255, 255, 0.75); color: #333; font-size: 13px; line-height: normal; border: 1px solid #ccc; border-bottom-color: #bbb; -webkit-border-radius: 4px; -moz-border-radius: 4px; border-radius: 4px; -webkit-box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.2), 0 1px 2px rgba(0, 0, 0, 0.05); -moz-box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.2), 0 1px 2px rgba(0, 0, 0, 0.05); box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.2), 0 1px 2px rgba(0, 0, 0, 0.05); -webkit-transition: 0.1s linear all; -moz-transition: 0.1s linear all; -ms-transition: 0.1s linear all; -o-transition: 0.1s linear all; transition: 0.1s linear all; } .btn:hover { background-position: 0 -15px; color: #333; text-decoration: none; } .btn:focus { outline: 1px dotted #666; } .btn.primary { color: #ffffff; background-color: #0064cd; background-repeat: repeat-x; background-image: -khtml-gradient(linear, left top, left bottom, from(#049cdb), to(#0064cd)); background-image: -moz-linear-gradient(top, #049cdb, #0064cd); background-image: -ms-linear-gradient(top, #049cdb, #0064cd); background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%, #049cdb), color-stop(100%, #0064cd)); background-image: -webkit-linear-gradient(top, #049cdb, #0064cd); background-image: -o-linear-gradient(top, #049cdb, #0064cd); background-image: linear-gradient(top, #049cdb, #0064cd); filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#049cdb', endColorstr='#0064cd', GradientType=0); text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.25); border-color: #0064cd #0064cd #003f81; border-color: rgba(0, 0, 0, 0.1) rgba(0, 0, 0, 0.1) rgba(0, 0, 0, 0.25); } .btn.active, .btn:active { -webkit-box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.25), 0 1px 2px rgba(0, 0, 0, 0.05); -moz-box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.25), 0 1px 2px rgba(0, 0, 0, 0.05); box-shadow: inset 0 2px 4px rgba(0, 0, 0, 0.25), 0 1px 2px rgba(0, 0, 0, 0.05); } .btn.disabled { cursor: default; background-image: none; filter: progid:DXImageTransform.Microsoft.gradient(enabled = false); filter: alpha(opacity=65); -khtml-opacity: 0.65; -moz-opacity: 0.65; opacity: 0.65; -webkit-box-shadow: none; -moz-box-shadow: none; box-shadow: none; } .btn[disabled] { cursor: default; background-image: none; filter: progid:DXImageTransform.Microsoft.gradient(enabled = false); filter: alpha(opacity=65); -khtml-opacity: 0.65; -moz-opacity: 0.65; opacity: 0.65; -webkit-box-shadow: none; -moz-box-shadow: none; box-shadow: none; } .btn.large { font-size: 15px; line-height: normal; padding: 9px 14px 9px; -webkit-border-radius: 6px; -moz-border-radius: 6px; border-radius: 6px; } .btn.small { padding: 7px 9px 7px; font-size: 11px; } :root .alert-message, :root .btn { border-radius: 0 \0; } button.btn::-moz-focus-inner, input[type=submit].btn::-moz-focus-inner { padding: 0; border: 0; } .close { float: right; color: #000000; font-size: 20px; font-weight: bold; line-height: 13.5px; text-shadow: 0 1px 0 #ffffff; filter: alpha(opacity=25); -khtml-opacity: 0.25; -moz-opacity: 0.25; opacity: 0.25; } .close:hover { color: #000000; text-decoration: none; filter: alpha(opacity=40); -khtml-opacity: 0.4; -moz-opacity: 0.4; opacity: 0.4; } .alert-message { position: relative; padding: 7px 15px; margin-bottom: 18px; color: #404040; background-color: #eedc94; background-repeat: repeat-x; background-image: -khtml-gradient(linear, left top, left bottom, from(#fceec1), to(#eedc94)); background-image: -moz-linear-gradient(top, #fceec1, #eedc94); background-image: -ms-linear-gradient(top, #fceec1, #eedc94); background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%, #fceec1), color-stop(100%, #eedc94)); background-image: -webkit-linear-gradient(top, #fceec1, #eedc94); background-image: -o-linear-gradient(top, #fceec1, #eedc94); background-image: linear-gradient(top, #fceec1, #eedc94); filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#fceec1', endColorstr='#eedc94', GradientType=0); text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.25); border-color: #eedc94 #eedc94 #e4c652; border-color: rgba(0, 0, 0, 0.1) rgba(0, 0, 0, 0.1) rgba(0, 0, 0, 0.25); text-shadow: 0 1px 0 rgba(255, 255, 255, 0.5); border-width: 1px; border-style: solid; -webkit-border-radius: 4px; -moz-border-radius: 4px; border-radius: 4px; -webkit-box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.25); -moz-box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.25); box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.25); } .alert-message .close { margin-top: 1px; *margin-top: 0; } .alert-message a { font-weight: bold; color: #404040; } .alert-message.danger p a, .alert-message.error p a, .alert-message.success p a, .alert-message.info p a { color: #ffffff; } .alert-message h5 { line-height: 18px; } .alert-message p { margin-bottom: 0; } .alert-message div { margin-top: 5px; margin-bottom: 2px; line-height: 28px; } .alert-message .btn { -webkit-box-shadow: 0 1px 0 rgba(255, 255, 255, 0.25); -moz-box-shadow: 0 1px 0 rgba(255, 255, 255, 0.25); box-shadow: 0 1px 0 rgba(255, 255, 255, 0.25); } .alert-message.block-message { background-image: none; background-color: #fdf5d9; filter: progid:DXImageTransform.Microsoft.gradient(enabled = false); padding: 14px; border-color: #fceec1; -webkit-box-shadow: none; -moz-box-shadow: none; box-shadow: none; } .alert-message.block-message ul, .alert-message.block-message p { margin-right: 30px; } .alert-message.block-message ul { margin-bottom: 0; } .alert-message.block-message li { color: #404040; } .alert-message.block-message .alert-actions { margin-top: 5px; } .alert-message.block-message.error, .alert-message.block-message.success, .alert-message.block-message.info { color: #404040; text-shadow: 0 1px 0 rgba(255, 255, 255, 0.5); } .alert-message.block-message.error { background-color: #fddfde; border-color: #fbc7c6; } .alert-message.block-message.success { background-color: #d1eed1; border-color: #bfe7bf; } .alert-message.block-message.info { background-color: #ddf4fb; border-color: #c6edf9; } .alert-message.block-message.danger p a, .alert-message.block-message.error p a, .alert-message.block-message.success p a, .alert-message.block-message.info p a { color: #404040; } .pagination { height: 36px; margin: 18px 0; } .pagination ul { float: left; margin: 0; border: 1px solid #ddd; border: 1px solid rgba(0, 0, 0, 0.15); -webkit-border-radius: 3px; -moz-border-radius: 3px; border-radius: 3px; -webkit-box-shadow: 0 1px 2px rgba(0, 0, 0, 0.05); -moz-box-shadow: 0 1px 2px rgba(0, 0, 0, 0.05); box-shadow: 0 1px 2px rgba(0, 0, 0, 0.05); } .pagination li { display: inline; } .pagination a { float: left; padding: 0 14px; line-height: 34px; border-right: 1px solid; border-right-color: #ddd; border-right-color: rgba(0, 0, 0, 0.15); *border-right-color: #ddd; /* IE6-7 */ text-decoration: none; } .pagination a:hover, .pagination .active a { background-color: #c7eefe; } .pagination .disabled a, .pagination .disabled a:hover { background-color: transparent; color: #bfbfbf; } .pagination .next a { border: 0; } .well { background-color: #f5f5f5; margin-bottom: 20px; padding: 19px; min-height: 20px; border: 1px solid #eee; border: 1px solid rgba(0, 0, 0, 0.05); -webkit-border-radius: 4px; -moz-border-radius: 4px; border-radius: 4px; -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.05); -moz-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.05); box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.05); } .well blockquote { border-color: #ddd; border-color: rgba(0, 0, 0, 0.15); } .modal-backdrop { background-color: #000000; position: fixed; top: 0; left: 0; right: 0; bottom: 0; z-index: 10000; } .modal-backdrop.fade { opacity: 0; } .modal-backdrop, .modal-backdrop.fade.in { filter: alpha(opacity=80); -khtml-opacity: 0.8; -moz-opacity: 0.8; opacity: 0.8; } .modal { position: fixed; top: 50%; left: 50%; z-index: 11000; width: 560px; margin: -250px 0 0 -280px; background-color: #ffffff; border: 1px solid #999; border: 1px solid rgba(0, 0, 0, 0.3); *border: 1px solid #999; /* IE6-7 */ -webkit-border-radius: 6px; -moz-border-radius: 6px; border-radius: 6px; -webkit-box-shadow: 0 3px 7px rgba(0, 0, 0, 0.3); -moz-box-shadow: 0 3px 7px rgba(0, 0, 0, 0.3); box-shadow: 0 3px 7px rgba(0, 0, 0, 0.3); -webkit-background-clip: padding-box; -moz-background-clip: padding-box; background-clip: padding-box; } .modal .close { margin-top: 7px; } .modal.fade { -webkit-transition: opacity .3s linear, top .3s ease-out; -moz-transition: opacity .3s linear, top .3s ease-out; -ms-transition: opacity .3s linear, top .3s ease-out; -o-transition: opacity .3s linear, top .3s ease-out; transition: opacity .3s linear, top .3s ease-out; top: -25%; } .modal.fade.in { top: 50%; } .modal-header { border-bottom: 1px solid #eee; padding: 5px 15px; } .modal-body { padding: 15px; } .modal-body form { margin-bottom: 0; } .modal-footer { background-color: #f5f5f5; padding: 14px 15px 15px; border-top: 1px solid #ddd; -webkit-border-radius: 0 0 6px 6px; -moz-border-radius: 0 0 6px 6px; border-radius: 0 0 6px 6px; -webkit-box-shadow: inset 0 1px 0 #ffffff; -moz-box-shadow: inset 0 1px 0 #ffffff; box-shadow: inset 0 1px 0 #ffffff; zoom: 1; margin-bottom: 0; } .modal-footer:before, .modal-footer:after { display: table; content: ""; zoom: 1; } .modal-footer:after { clear: both; } .modal-footer .btn { float: right; margin-left: 5px; } .modal .popover, .modal .twipsy { z-index: 12000; } .twipsy { display: block; position: absolute; visibility: visible; padding: 5px; font-size: 11px; z-index: 1000; filter: alpha(opacity=80); -khtml-opacity: 0.8; -moz-opacity: 0.8; opacity: 0.8; } .twipsy.fade.in { filter: alpha(opacity=80); -khtml-opacity: 0.8; -moz-opacity: 0.8; opacity: 0.8; } .twipsy.above .twipsy-arrow { bottom: 0; left: 50%; margin-left: -5px; border-left: 5px solid transparent; border-right: 5px solid transparent; border-top: 5px solid #000000; } .twipsy.left .twipsy-arrow { top: 50%; right: 0; margin-top: -5px; border-top: 5px solid transparent; border-bottom: 5px solid transparent; border-left: 5px solid #000000; } .twipsy.below .twipsy-arrow { top: 0; left: 50%; margin-left: -5px; border-left: 5px solid transparent; border-right: 5px solid transparent; border-bottom: 5px solid #000000; } .twipsy.right .twipsy-arrow { top: 50%; left: 0; margin-top: -5px; border-top: 5px solid transparent; border-bottom: 5px solid transparent; border-right: 5px solid #000000; } .twipsy-inner { padding: 3px 8px; background-color: #000000; color: white; text-align: center; max-width: 200px; text-decoration: none; -webkit-border-radius: 4px; -moz-border-radius: 4px; border-radius: 4px; } .twipsy-arrow { position: absolute; width: 0; height: 0; } .popover { position: absolute; top: 0; left: 0; z-index: 1000; padding: 5px; display: none; } .popover.above .arrow { bottom: 0; left: 50%; margin-left: -5px; border-left: 5px solid transparent; border-right: 5px solid transparent; border-top: 5px solid #000000; } .popover.right .arrow { top: 50%; left: 0; margin-top: -5px; border-top: 5px solid transparent; border-bottom: 5px solid transparent; border-right: 5px solid #000000; } .popover.below .arrow { top: 0; left: 50%; margin-left: -5px; border-left: 5px solid transparent; border-right: 5px solid transparent; border-bottom: 5px solid #000000; } .popover.left .arrow { top: 50%; right: 0; margin-top: -5px; border-top: 5px solid transparent; border-bottom: 5px solid transparent; border-left: 5px solid #000000; } .popover .arrow { position: absolute; width: 0; height: 0; } .popover .inner { background: #000000; background: rgba(0, 0, 0, 0.8); padding: 3px; overflow: hidden; width: 280px; -webkit-border-radius: 6px; -moz-border-radius: 6px; border-radius: 6px; -webkit-box-shadow: 0 3px 7px rgba(0, 0, 0, 0.3); -moz-box-shadow: 0 3px 7px rgba(0, 0, 0, 0.3); box-shadow: 0 3px 7px rgba(0, 0, 0, 0.3); } .popover .title { background-color: #f5f5f5; padding: 9px 15px; line-height: 1; -webkit-border-radius: 3px 3px 0 0; -moz-border-radius: 3px 3px 0 0; border-radius: 3px 3px 0 0; border-bottom: 1px solid #eee; } .popover .content { background-color: #ffffff; padding: 14px; -webkit-border-radius: 0 0 3px 3px; -moz-border-radius: 0 0 3px 3px; border-radius: 0 0 3px 3px; -webkit-background-clip: padding-box; -moz-background-clip: padding-box; background-clip: padding-box; } .popover .content p, .popover .content ul, .popover .content ol { margin-bottom: 0; } .fade { -webkit-transition: opacity 0.15s linear; -moz-transition: opacity 0.15s linear; -ms-transition: opacity 0.15s linear; -o-transition: opacity 0.15s linear; transition: opacity 0.15s linear; opacity: 0; } .fade.in { opacity: 1; } .label { padding: 1px 3px 2px; font-size: 9.75px; font-weight: bold; color: #ffffff; text-transform: uppercase; white-space: nowrap; background-color: #bfbfbf; -webkit-border-radius: 3px; -moz-border-radius: 3px; border-radius: 3px; } .label.important { background-color: #c43c35; } .label.warning { background-color: #f89406; } .label.success { background-color: #46a546; } .label.notice { background-color: #62cffc; } .media-grid { margin-left: -20px; margin-bottom: 0; zoom: 1; } .media-grid:before, .media-grid:after { display: table; content: ""; zoom: 1; } .media-grid:after { clear: both; } .media-grid li { display: inline; } .media-grid a { float: left; padding: 4px; margin: 0 0 18px 20px; border: 1px solid #ddd; -webkit-border-radius: 4px; -moz-border-radius: 4px; border-radius: 4px; -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075); -moz-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075); box-shadow: 0 1px 1px rgba(0, 0, 0, 0.075); } .media-grid a img { display: block; } .media-grid a:hover { border-color: #0069d6; -webkit-box-shadow: 0 1px 4px rgba(0, 105, 214, 0.25); -moz-box-shadow: 0 1px 4px rgba(0, 105, 214, 0.25); box-shadow: 0 1px 4px rgba(0, 105, 214, 0.25); } ansible-1.7.2/docsite/_static/default.css000066400000000000000000000077101241061774000203630ustar00rootroot00000000000000/* * default.css_t * ~~~~~~~~~~~~~ * * Sphinx stylesheet -- default theme. * * :copyright: Copyright 2007-2011 by the Sphinx team, see AUTHORS. * :license: BSD, see LICENSE for details. * */ @import url("basic.css"); /* -- page layout ----------------------------------------------------------- */ body { font-family: sans-serif; font-size: 100%; background-color: #11303d; color: #000; margin: 0; padding: 0; } div.document { background-color: #1c4e63; } div.documentwrapper { float: left; width: 100%; } div.bodywrapper { margin: 0 0 0 230px; } div.body { background-color: #ffffff; color: #000000; padding: 0 20px 30px 20px; } div.footer { color: #ffffff; width: 100%; padding: 9px 0 9px 0; text-align: center; font-size: 75%; } div.footer a { color: #ffffff; text-decoration: underline; } div.related { background-color: #133f52; line-height: 30px; color: #ffffff; } div.related a { color: #ffffff; } div.sphinxsidebar { } div.sphinxsidebar h3 { font-family: 'Trebuchet MS', sans-serif; color: #ffffff; font-size: 1.4em; font-weight: normal; margin: 0; padding: 0; } div.sphinxsidebar h3 a { color: #ffffff; } div.sphinxsidebar h4 { font-family: 'Trebuchet MS', sans-serif; color: #ffffff; font-size: 1.3em; font-weight: normal; margin: 5px 0 0 0; padding: 0; } div.sphinxsidebar p { color: #ffffff; } div.sphinxsidebar p.topless { margin: 5px 10px 10px 10px; } div.sphinxsidebar ul { margin: 10px; padding: 0; color: #ffffff; } div.sphinxsidebar a { color: #98dbcc; } div.sphinxsidebar input { border: 1px solid #98dbcc; font-family: sans-serif; font-size: 1em; } /* -- hyperlink styles ------------------------------------------------------ */ a { color: #355f7c; text-decoration: none; } a:visited { color: #355f7c; text-decoration: none; } a:hover { text-decoration: underline; } /* -- body styles ----------------------------------------------------------- */ div.body h1, div.body h2, div.body h3, div.body h4, div.body h5, div.body h6 { font-family: 'Trebuchet MS', sans-serif; background-color: #f2f2f2; font-weight: normal; color: #20435c; border-bottom: 1px solid #ccc; margin: 20px -20px 10px -20px; padding: 3px 0 3px 10px; } div.body h1 { margin-top: 0; font-size: 200%; } div.body h2 { font-size: 160%; } div.body h3 { font-size: 140%; } div.body h4 { font-size: 120%; } div.body h5 { font-size: 110%; } div.body h6 { font-size: 100%; } a.headerlink { color: #c60f0f; font-size: 0.8em; padding: 0 4px 0 4px; text-decoration: none; } a.headerlink:hover { background-color: #c60f0f; color: white; } div.body p, div.body dd, div.body li { text-align: justify; line-height: 130%; } div.admonition p.admonition-title + p { display: inline; } div.admonition p { margin-bottom: 5px; } div.admonition pre { margin-bottom: 5px; } div.admonition ul, div.admonition ol { margin-bottom: 5px; } div.note { background-color: #eee; border: 1px solid #ccc; } div.seealso { background-color: #ffc; border: 1px solid #ff6; } div.topic { background-color: #eee; } div.warning { background-color: #ffe4e4; border: 1px solid #f66; } p.admonition-title { display: inline; } p.admonition-title:after { content: ":"; } pre { padding: 5px; background-color: #eeffcc; color: #333333; line-height: 120%; border: 1px solid #ac9; border-left: none; border-right: none; } tt { background-color: #ecf0f3; padding: 0 1px 0 1px; font-size: 0.95em; } th { background-color: #ede; } .warning tt { background: #efc2c2; } .note tt { background: #d6d6d6; } .viewcode-back { font-family: sans-serif; } div.viewcode-block:target { background-color: #f4debf; border-top: 1px solid #ac9; border-bottom: 1px solid #ac9; }ansible-1.7.2/docsite/_static/doctools.js000066400000000000000000000152701241061774000204110ustar00rootroot00000000000000/* * doctools.js * ~~~~~~~~~~~ * * Sphinx JavaScript utilities for all documentation. * * :copyright: Copyright 2007-2011 by the Sphinx team, see AUTHORS. * :license: BSD, see LICENSE for details. * */ /** * select a different prefix for underscore */ $u = _.noConflict(); /** * make the code below compatible with browsers without * an installed firebug like debugger if (!window.console || !console.firebug) { var names = ["log", "debug", "info", "warn", "error", "assert", "dir", "dirxml", "group", "groupEnd", "time", "timeEnd", "count", "trace", "profile", "profileEnd"]; window.console = {}; for (var i = 0; i < names.length; ++i) window.console[names[i]] = function() {}; } */ /** * small helper function to urldecode strings */ jQuery.urldecode = function(x) { return decodeURIComponent(x).replace(/\+/g, ' '); } /** * small helper function to urlencode strings */ jQuery.urlencode = encodeURIComponent; /** * This function returns the parsed url parameters of the * current request. Multiple values per key are supported, * it will always return arrays of strings for the value parts. */ jQuery.getQueryParameters = function(s) { if (typeof s == 'undefined') s = document.location.search; var parts = s.substr(s.indexOf('?') + 1).split('&'); var result = {}; for (var i = 0; i < parts.length; i++) { var tmp = parts[i].split('=', 2); var key = jQuery.urldecode(tmp[0]); var value = jQuery.urldecode(tmp[1]); if (key in result) result[key].push(value); else result[key] = [value]; } return result; }; /** * small function to check if an array contains * a given item. */ jQuery.contains = function(arr, item) { for (var i = 0; i < arr.length; i++) { if (arr[i] == item) return true; } return false; }; /** * highlight a given string on a jquery object by wrapping it in * span elements with the given class name. */ jQuery.fn.highlightText = function(text, className) { function highlight(node) { if (node.nodeType == 3) { var val = node.nodeValue; var pos = val.toLowerCase().indexOf(text); if (pos >= 0 && !jQuery(node.parentNode).hasClass(className)) { var span = document.createElement("span"); span.className = className; span.appendChild(document.createTextNode(val.substr(pos, text.length))); node.parentNode.insertBefore(span, node.parentNode.insertBefore( document.createTextNode(val.substr(pos + text.length)), node.nextSibling)); node.nodeValue = val.substr(0, pos); } } else if (!jQuery(node).is("button, select, textarea")) { jQuery.each(node.childNodes, function() { highlight(this); }); } } return this.each(function() { highlight(this); }); }; /** * Small JavaScript module for the documentation. */ var Documentation = { init : function() { this.fixFirefoxAnchorBug(); this.highlightSearchWords(); this.initIndexTable(); }, /** * i18n support */ TRANSLATIONS : {}, PLURAL_EXPR : function(n) { return n == 1 ? 0 : 1; }, LOCALE : 'unknown', // gettext and ngettext don't access this so that the functions // can safely bound to a different name (_ = Documentation.gettext) gettext : function(string) { var translated = Documentation.TRANSLATIONS[string]; if (typeof translated == 'undefined') return string; return (typeof translated == 'string') ? translated : translated[0]; }, ngettext : function(singular, plural, n) { var translated = Documentation.TRANSLATIONS[singular]; if (typeof translated == 'undefined') return (n == 1) ? singular : plural; return translated[Documentation.PLURALEXPR(n)]; }, addTranslations : function(catalog) { for (var key in catalog.messages) this.TRANSLATIONS[key] = catalog.messages[key]; this.PLURAL_EXPR = new Function('n', 'return +(' + catalog.plural_expr + ')'); this.LOCALE = catalog.locale; }, /** * add context elements like header anchor links */ addContextElements : function() { $('div[id] > :header:first').each(function() { $('\u00B6'). attr('href', '#' + this.id). attr('title', _('Permalink to this headline')). appendTo(this); }); $('dt[id]').each(function() { $('\u00B6'). attr('href', '#' + this.id). attr('title', _('Permalink to this definition')). appendTo(this); }); }, /** * workaround a firefox stupidity */ fixFirefoxAnchorBug : function() { if (document.location.hash && $.browser.mozilla) window.setTimeout(function() { document.location.href += ''; }, 10); }, /** * highlight the search words provided in the url in the text */ highlightSearchWords : function() { var params = $.getQueryParameters(); var terms = (params.highlight) ? params.highlight[0].split(/\s+/) : []; if (terms.length) { var body = $('div.body'); window.setTimeout(function() { $.each(terms, function() { body.highlightText(this.toLowerCase(), 'highlighted'); }); }, 10); $('

' + _('Hide Search Matches') + '

') .appendTo($('#searchbox')); } }, /** * init the domain index toggle buttons */ initIndexTable : function() { var togglers = $('img.toggler').click(function() { var src = $(this).attr('src'); var idnum = $(this).attr('id').substr(7); $('tr.cg-' + idnum).toggle(); if (src.substr(-9) == 'minus.png') $(this).attr('src', src.substr(0, src.length-9) + 'plus.png'); else $(this).attr('src', src.substr(0, src.length-8) + 'minus.png'); }).css('display', ''); if (DOCUMENTATION_OPTIONS.COLLAPSE_INDEX) { togglers.click(); } }, /** * helper function to hide the search marks again */ hideSearchWords : function() { $('#searchbox .highlight-link').fadeOut(300); $('span.highlighted').removeClass('highlighted'); }, /** * make the url absolute */ makeURL : function(relativeURL) { return DOCUMENTATION_OPTIONS.URL_ROOT + '/' + relativeURL; }, /** * get the current relative url */ getCurrentURL : function() { var path = document.location.pathname; var parts = path.split(/\//); $.each(DOCUMENTATION_OPTIONS.URL_ROOT.split(/\//), function() { if (this == '..') parts.pop(); }); var url = parts.join('/'); return path.substring(url.lastIndexOf('/') + 1, path.length - 1); } }; // quick alias for translations _ = Documentation.gettext; $(document).ready(function() { Documentation.init(); }); ansible-1.7.2/docsite/_static/favicon.ico000066400000000000000000000004761241061774000203500ustar00rootroot00000000000000(( €õñÿÿ7æúú:õ=õúõT€“Y€ET€•Y€ET€•Y€ETƒ3333ˆ•YIIIIIIET‚""b"(•Y€ET€•Y€Eq€•YˆˆˆˆˆˆESIIIIII5UUUUUUPøøøøøøøøøø€ansible-1.7.2/docsite/_static/file.png000066400000000000000000000006101241061774000176420ustar00rootroot00000000000000‰PNG  IHDRóÿabKGDÿÿÿ ½§“ pHYs  šœtIMEÕ  )¶TIDAT8Ë­‘±JÄ@†¿Ir('[ "&xØÙYZ ‚Xø0‚!i|†_@±Ô÷•t§ÓDÄæÏ] ¹#¹Äxÿjv˜ùç› Y–ÐN‡ažE‘i«(ŠÌÄÉ™yž£µ@D¦£&±ˆ`Û6®ë–P¦Zk’$)5%"ôz½Ê.NñA#Aœba‘`Vsø¾_3ñc°,«™àä2m¼Ýñþjó [kŸìlv¹y|!IÕ´ðþyô;ÀðvÈé "Œß®°—a©?ŸAúðÄ7Œ`ô˜ñÇc^énôk?¸²Bg}»TЙ¹D#ÁÑÞ "R¹D1÷£çyüEŽRê*ŽãÝ6MJ©3þK_U«t8F~ÇIEND®B`‚ansible-1.7.2/docsite/_static/minus.png000066400000000000000000000003071241061774000200610ustar00rootroot00000000000000‰PNG  IHDR &Îàq pHYs  šœtIME× <®8åtEXtCommentöÌ–¿RIDATÓczô(BÅñãÇáÒpö¿ÿ¨èˆip»‘¹P÷îÝÃc· ¸ |¶IEND®B`‚ansible-1.7.2/docsite/_static/pygments.css000066400000000000000000000075341241061774000206110ustar00rootroot00000000000000.highlight .hll { background-color: #ffffcc } .highlight { background: #eeffcc; } .highlight .c { color: #408090; font-style: italic } /* Comment */ .highlight .err { border: 1px solid #FF0000 } /* Error */ .highlight .k { color: #007020; font-weight: bold } /* Keyword */ .highlight .o { color: #666666 } /* Operator */ .highlight .cm { color: #408090; font-style: italic } /* Comment.Multiline */ .highlight .cp { color: #007020 } /* Comment.Preproc */ .highlight .c1 { color: #408090; font-style: italic } /* Comment.Single */ .highlight .cs { color: #408090; background-color: #fff0f0 } /* Comment.Special */ .highlight .gd { color: #A00000 } /* Generic.Deleted */ .highlight .ge { font-style: italic } /* Generic.Emph */ .highlight .gr { color: #FF0000 } /* Generic.Error */ .highlight .gh { color: #000080; font-weight: bold } /* Generic.Heading */ .highlight .gi { color: #00A000 } /* Generic.Inserted */ .highlight .go { color: #303030 } /* Generic.Output */ .highlight .gp { color: #c65d09; font-weight: bold } /* Generic.Prompt */ .highlight .gs { font-weight: bold } /* Generic.Strong */ .highlight .gu { color: #800080; font-weight: bold } /* Generic.Subheading */ .highlight .gt { color: #0040D0 } /* Generic.Traceback */ .highlight .kc { color: #007020; font-weight: bold } /* Keyword.Constant */ .highlight .kd { color: #007020; font-weight: bold } /* Keyword.Declaration */ .highlight .kn { color: #007020; font-weight: bold } /* Keyword.Namespace */ .highlight .kp { color: #007020 } /* Keyword.Pseudo */ .highlight .kr { color: #007020; font-weight: bold } /* Keyword.Reserved */ .highlight .kt { color: #902000 } /* Keyword.Type */ .highlight .m { color: #208050 } /* Literal.Number */ .highlight .s { color: #4070a0 } /* Literal.String */ .highlight .na { color: #4070a0 } /* Name.Attribute */ .highlight .nb { color: #007020 } /* Name.Builtin */ .highlight .nc { color: #0e84b5; font-weight: bold } /* Name.Class */ .highlight .no { color: #60add5 } /* Name.Constant */ .highlight .nd { color: #555555; font-weight: bold } /* Name.Decorator */ .highlight .ni { color: #d55537; font-weight: bold } /* Name.Entity */ .highlight .ne { color: #007020 } /* Name.Exception */ .highlight .nf { color: #06287e } /* Name.Function */ .highlight .nl { color: #002070; font-weight: bold } /* Name.Label */ .highlight .nn { color: #0e84b5; font-weight: bold } /* Name.Namespace */ .highlight .nt { color: #062873; font-weight: bold } /* Name.Tag */ .highlight .nv { color: #bb60d5 } /* Name.Variable */ .highlight .ow { color: #007020; font-weight: bold } /* Operator.Word */ .highlight .w { color: #bbbbbb } /* Text.Whitespace */ .highlight .mf { color: #208050 } /* Literal.Number.Float */ .highlight .mh { color: #208050 } /* Literal.Number.Hex */ .highlight .mi { color: #208050 } /* Literal.Number.Integer */ .highlight .mo { color: #208050 } /* Literal.Number.Oct */ .highlight .sb { color: #4070a0 } /* Literal.String.Backtick */ .highlight .sc { color: #4070a0 } /* Literal.String.Char */ .highlight .sd { color: #4070a0; font-style: italic } /* Literal.String.Doc */ .highlight .s2 { color: #4070a0 } /* Literal.String.Double */ .highlight .se { color: #4070a0; font-weight: bold } /* Literal.String.Escape */ .highlight .sh { color: #4070a0 } /* Literal.String.Heredoc */ .highlight .si { color: #70a0d0; font-style: italic } /* Literal.String.Interpol */ .highlight .sx { color: #c65d09 } /* Literal.String.Other */ .highlight .sr { color: #235388 } /* Literal.String.Regex */ .highlight .s1 { color: #4070a0 } /* Literal.String.Single */ .highlight .ss { color: #517918 } /* Literal.String.Symbol */ .highlight .bp { color: #007020 } /* Name.Builtin.Pseudo */ .highlight .vc { color: #bb60d5 } /* Name.Variable.Class */ .highlight .vg { color: #bb60d5 } /* Name.Variable.Global */ .highlight .vi { color: #bb60d5 } /* Name.Variable.Instance */ .highlight .il { color: #208050 } /* Literal.Number.Integer.Long */ansible-1.7.2/docsite/_static/searchtools.js000066400000000000000000000372531241061774000211160ustar00rootroot00000000000000/* * searchtools.js_t * ~~~~~~~~~~~~~~~~ * * Sphinx JavaScript utilties for the full-text search. * * :copyright: Copyright 2007-2011 by the Sphinx team, see AUTHORS. * :license: BSD, see LICENSE for details. * */ /** * helper function to return a node containing the * search summary for a given text. keywords is a list * of stemmed words, hlwords is the list of normal, unstemmed * words. the first one is used to find the occurance, the * latter for highlighting it. */ jQuery.makeSearchSummary = function(text, keywords, hlwords) { var textLower = text.toLowerCase(); var start = 0; $.each(keywords, function() { var i = textLower.indexOf(this.toLowerCase()); if (i > -1) start = i; }); start = Math.max(start - 120, 0); var excerpt = ((start > 0) ? '...' : '') + $.trim(text.substr(start, 240)) + ((start + 240 - text.length) ? '...' : ''); var rv = $('
').text(excerpt); $.each(hlwords, function() { rv = rv.highlightText(this, 'highlighted'); }); return rv; } /** * Porter Stemmer */ var Stemmer = function() { var step2list = { ational: 'ate', tional: 'tion', enci: 'ence', anci: 'ance', izer: 'ize', bli: 'ble', alli: 'al', entli: 'ent', eli: 'e', ousli: 'ous', ization: 'ize', ation: 'ate', ator: 'ate', alism: 'al', iveness: 'ive', fulness: 'ful', ousness: 'ous', aliti: 'al', iviti: 'ive', biliti: 'ble', logi: 'log' }; var step3list = { icate: 'ic', ative: '', alize: 'al', iciti: 'ic', ical: 'ic', ful: '', ness: '' }; var c = "[^aeiou]"; // consonant var v = "[aeiouy]"; // vowel var C = c + "[^aeiouy]*"; // consonant sequence var V = v + "[aeiou]*"; // vowel sequence var mgr0 = "^(" + C + ")?" + V + C; // [C]VC... is m>0 var meq1 = "^(" + C + ")?" + V + C + "(" + V + ")?$"; // [C]VC[V] is m=1 var mgr1 = "^(" + C + ")?" + V + C + V + C; // [C]VCVC... is m>1 var s_v = "^(" + C + ")?" + v; // vowel in stem this.stemWord = function (w) { var stem; var suffix; var firstch; var origword = w; if (w.length < 3) return w; var re; var re2; var re3; var re4; firstch = w.substr(0,1); if (firstch == "y") w = firstch.toUpperCase() + w.substr(1); // Step 1a re = /^(.+?)(ss|i)es$/; re2 = /^(.+?)([^s])s$/; if (re.test(w)) w = w.replace(re,"$1$2"); else if (re2.test(w)) w = w.replace(re2,"$1$2"); // Step 1b re = /^(.+?)eed$/; re2 = /^(.+?)(ed|ing)$/; if (re.test(w)) { var fp = re.exec(w); re = new RegExp(mgr0); if (re.test(fp[1])) { re = /.$/; w = w.replace(re,""); } } else if (re2.test(w)) { var fp = re2.exec(w); stem = fp[1]; re2 = new RegExp(s_v); if (re2.test(stem)) { w = stem; re2 = /(at|bl|iz)$/; re3 = new RegExp("([^aeiouylsz])\\1$"); re4 = new RegExp("^" + C + v + "[^aeiouwxy]$"); if (re2.test(w)) w = w + "e"; else if (re3.test(w)) { re = /.$/; w = w.replace(re,""); } else if (re4.test(w)) w = w + "e"; } } // Step 1c re = /^(.+?)y$/; if (re.test(w)) { var fp = re.exec(w); stem = fp[1]; re = new RegExp(s_v); if (re.test(stem)) w = stem + "i"; } // Step 2 re = /^(.+?)(ational|tional|enci|anci|izer|bli|alli|entli|eli|ousli|ization|ation|ator|alism|iveness|fulness|ousness|aliti|iviti|biliti|logi)$/; if (re.test(w)) { var fp = re.exec(w); stem = fp[1]; suffix = fp[2]; re = new RegExp(mgr0); if (re.test(stem)) w = stem + step2list[suffix]; } // Step 3 re = /^(.+?)(icate|ative|alize|iciti|ical|ful|ness)$/; if (re.test(w)) { var fp = re.exec(w); stem = fp[1]; suffix = fp[2]; re = new RegExp(mgr0); if (re.test(stem)) w = stem + step3list[suffix]; } // Step 4 re = /^(.+?)(al|ance|ence|er|ic|able|ible|ant|ement|ment|ent|ou|ism|ate|iti|ous|ive|ize)$/; re2 = /^(.+?)(s|t)(ion)$/; if (re.test(w)) { var fp = re.exec(w); stem = fp[1]; re = new RegExp(mgr1); if (re.test(stem)) w = stem; } else if (re2.test(w)) { var fp = re2.exec(w); stem = fp[1] + fp[2]; re2 = new RegExp(mgr1); if (re2.test(stem)) w = stem; } // Step 5 re = /^(.+?)e$/; if (re.test(w)) { var fp = re.exec(w); stem = fp[1]; re = new RegExp(mgr1); re2 = new RegExp(meq1); re3 = new RegExp("^" + C + v + "[^aeiouwxy]$"); if (re.test(stem) || (re2.test(stem) && !(re3.test(stem)))) w = stem; } re = /ll$/; re2 = new RegExp(mgr1); if (re.test(w) && re2.test(w)) { re = /.$/; w = w.replace(re,""); } // and turn initial Y back to y if (firstch == "y") w = firstch.toLowerCase() + w.substr(1); return w; } } /** * Search Module */ var Search = { _index : null, _queued_query : null, _pulse_status : -1, init : function() { var params = $.getQueryParameters(); if (params.q) { var query = params.q[0]; $('input[name="q"]')[0].value = query; this.performSearch(query); } }, loadIndex : function(url) { $.ajax({type: "GET", url: url, data: null, success: null, dataType: "script", cache: true}); }, setIndex : function(index) { var q; this._index = index; if ((q = this._queued_query) !== null) { this._queued_query = null; Search.query(q); } }, hasIndex : function() { return this._index !== null; }, deferQuery : function(query) { this._queued_query = query; }, stopPulse : function() { this._pulse_status = 0; }, startPulse : function() { if (this._pulse_status >= 0) return; function pulse() { Search._pulse_status = (Search._pulse_status + 1) % 4; var dotString = ''; for (var i = 0; i < Search._pulse_status; i++) dotString += '.'; Search.dots.text(dotString); if (Search._pulse_status > -1) window.setTimeout(pulse, 500); }; pulse(); }, /** * perform a search for something */ performSearch : function(query) { // create the required interface elements this.out = $('#search-results'); this.title = $('

' + _('Searching') + '

').appendTo(this.out); this.dots = $('').appendTo(this.title); this.status = $('

').appendTo(this.out); this.output = $('
    ').appendTo(this.out); $('#search-progress').text(_('Preparing search...')); this.startPulse(); // index already loaded, the browser was quick! if (this.hasIndex()) this.query(query); else this.deferQuery(query); }, query : function(query) { var stopwords = ["and","then","into","it","as","are","in","if","for","no","there","their","was","is","be","to","that","but","they","not","such","with","by","a","on","these","of","will","this","near","the","or","at"]; // Stem the searchterms and add them to the correct list var stemmer = new Stemmer(); var searchterms = []; var excluded = []; var hlterms = []; var tmp = query.split(/\s+/); var objectterms = []; for (var i = 0; i < tmp.length; i++) { if (tmp[i] != "") { objectterms.push(tmp[i].toLowerCase()); } if ($u.indexOf(stopwords, tmp[i]) != -1 || tmp[i].match(/^\d+$/) || tmp[i] == "") { // skip this "word" continue; } // stem the word var word = stemmer.stemWord(tmp[i]).toLowerCase(); // select the correct list if (word[0] == '-') { var toAppend = excluded; word = word.substr(1); } else { var toAppend = searchterms; hlterms.push(tmp[i].toLowerCase()); } // only add if not already in the list if (!$.contains(toAppend, word)) toAppend.push(word); }; var highlightstring = '?highlight=' + $.urlencode(hlterms.join(" ")); // console.debug('SEARCH: searching for:'); // console.info('required: ', searchterms); // console.info('excluded: ', excluded); // prepare search var filenames = this._index.filenames; var titles = this._index.titles; var terms = this._index.terms; var fileMap = {}; var files = null; // different result priorities var importantResults = []; var objectResults = []; var regularResults = []; var unimportantResults = []; $('#search-progress').empty(); // lookup as object for (var i = 0; i < objectterms.length; i++) { var others = [].concat(objectterms.slice(0,i), objectterms.slice(i+1, objectterms.length)) var results = this.performObjectSearch(objectterms[i], others); // Assume first word is most likely to be the object, // other words more likely to be in description. // Therefore put matches for earlier words first. // (Results are eventually used in reverse order). objectResults = results[0].concat(objectResults); importantResults = results[1].concat(importantResults); unimportantResults = results[2].concat(unimportantResults); } // perform the search on the required terms for (var i = 0; i < searchterms.length; i++) { var word = searchterms[i]; // no match but word was a required one if ((files = terms[word]) == null) break; if (files.length == undefined) { files = [files]; } // create the mapping for (var j = 0; j < files.length; j++) { var file = files[j]; if (file in fileMap) fileMap[file].push(word); else fileMap[file] = [word]; } } // now check if the files don't contain excluded terms for (var file in fileMap) { var valid = true; // check if all requirements are matched if (fileMap[file].length != searchterms.length) continue; // ensure that none of the excluded terms is in the // search result. for (var i = 0; i < excluded.length; i++) { if (terms[excluded[i]] == file || $.contains(terms[excluded[i]] || [], file)) { valid = false; break; } } // if we have still a valid result we can add it // to the result list if (valid) regularResults.push([filenames[file], titles[file], '', null]); } // delete unused variables in order to not waste // memory until list is retrieved completely delete filenames, titles, terms; // now sort the regular results descending by title regularResults.sort(function(a, b) { var left = a[1].toLowerCase(); var right = b[1].toLowerCase(); return (left > right) ? -1 : ((left < right) ? 1 : 0); }); // combine all results var results = unimportantResults.concat(regularResults) .concat(objectResults).concat(importantResults); // print the results var resultCount = results.length; function displayNextItem() { // results left, load the summary and display it if (results.length) { var item = results.pop(); var listItem = $('
  • '); if (DOCUMENTATION_OPTIONS.FILE_SUFFIX == '') { // dirhtml builder var dirname = item[0] + '/'; if (dirname.match(/\/index\/$/)) { dirname = dirname.substring(0, dirname.length-6); } else if (dirname == 'index/') { dirname = ''; } listItem.append($('').attr('href', DOCUMENTATION_OPTIONS.URL_ROOT + dirname + highlightstring + item[2]).html(item[1])); } else { // normal html builders listItem.append($('').attr('href', item[0] + DOCUMENTATION_OPTIONS.FILE_SUFFIX + highlightstring + item[2]).html(item[1])); } if (item[3]) { listItem.append($(' (' + item[3] + ')')); Search.output.append(listItem); listItem.slideDown(5, function() { displayNextItem(); }); } else if (DOCUMENTATION_OPTIONS.HAS_SOURCE) { $.get(DOCUMENTATION_OPTIONS.URL_ROOT + '_sources/' + item[0] + '.txt', function(data) { if (data != '') { listItem.append($.makeSearchSummary(data, searchterms, hlterms)); Search.output.append(listItem); } listItem.slideDown(5, function() { displayNextItem(); }); }, "text"); } else { // no source available, just display title Search.output.append(listItem); listItem.slideDown(5, function() { displayNextItem(); }); } } // search finished, update title and status message else { Search.stopPulse(); Search.title.text(_('Search Results')); if (!resultCount) Search.status.text(_('Your search did not match any documents. Please make sure that all words are spelled correctly and that you\'ve selected enough categories.')); else Search.status.text(_('Search finished, found %s page(s) matching the search query.').replace('%s', resultCount)); Search.status.fadeIn(500); } } displayNextItem(); }, performObjectSearch : function(object, otherterms) { var filenames = this._index.filenames; var objects = this._index.objects; var objnames = this._index.objnames; var titles = this._index.titles; var importantResults = []; var objectResults = []; var unimportantResults = []; for (var prefix in objects) { for (var name in objects[prefix]) { var fullname = (prefix ? prefix + '.' : '') + name; if (fullname.toLowerCase().indexOf(object) > -1) { var match = objects[prefix][name]; var objname = objnames[match[1]][2]; var title = titles[match[0]]; // If more than one term searched for, we require other words to be // found in the name/title/description if (otherterms.length > 0) { var haystack = (prefix + ' ' + name + ' ' + objname + ' ' + title).toLowerCase(); var allfound = true; for (var i = 0; i < otherterms.length; i++) { if (haystack.indexOf(otherterms[i]) == -1) { allfound = false; break; } } if (!allfound) { continue; } } var descr = objname + _(', in ') + title; anchor = match[3]; if (anchor == '') anchor = fullname; else if (anchor == '-') anchor = objnames[match[1]][1] + '-' + fullname; result = [filenames[match[0]], fullname, '#'+anchor, descr]; switch (match[2]) { case 1: objectResults.push(result); break; case 0: importantResults.push(result); break; case 2: unimportantResults.push(result); break; } } } } // sort results descending objectResults.sort(function(a, b) { return (a[1] > b[1]) ? -1 : ((a[1] < b[1]) ? 1 : 0); }); importantResults.sort(function(a, b) { return (a[1] > b[1]) ? -1 : ((a[1] < b[1]) ? 1 : 0); }); unimportantResults.sort(function(a, b) { return (a[1] > b[1]) ? -1 : ((a[1] < b[1]) ? 1 : 0); }); return [importantResults, objectResults, unimportantResults] } } $(document).ready(function() { Search.init(); });ansible-1.7.2/docsite/_static/sidebar.js000066400000000000000000000110321241061774000201640ustar00rootroot00000000000000/* * sidebar.js * ~~~~~~~~~~ * * This script makes the Sphinx sidebar collapsible. * * .sphinxsidebar contains .sphinxsidebarwrapper. This script adds * in .sphixsidebar, after .sphinxsidebarwrapper, the #sidebarbutton * used to collapse and expand the sidebar. * * When the sidebar is collapsed the .sphinxsidebarwrapper is hidden * and the width of the sidebar and the margin-left of the document * are decreased. When the sidebar is expanded the opposite happens. * This script saves a per-browser/per-session cookie used to * remember the position of the sidebar among the pages. * Once the browser is closed the cookie is deleted and the position * reset to the default (expanded). * * :copyright: Copyright 2007-2011 by the Sphinx team, see AUTHORS. * :license: BSD, see LICENSE for details. * */ $(function() { // global elements used by the functions. // the 'sidebarbutton' element is defined as global after its // creation, in the add_sidebar_button function var bodywrapper = $('.bodywrapper'); var sidebar = $('.sphinxsidebar'); var sidebarwrapper = $('.sphinxsidebarwrapper'); // original margin-left of the bodywrapper and width of the sidebar // with the sidebar expanded var bw_margin_expanded = bodywrapper.css('margin-left'); var ssb_width_expanded = sidebar.width(); // margin-left of the bodywrapper and width of the sidebar // with the sidebar collapsed var bw_margin_collapsed = '.8em'; var ssb_width_collapsed = '.8em'; // colors used by the current theme var dark_color = $('.related').css('background-color'); var light_color = $('.document').css('background-color'); function sidebar_is_collapsed() { return sidebarwrapper.is(':not(:visible)'); } function toggle_sidebar() { if (sidebar_is_collapsed()) expand_sidebar(); else collapse_sidebar(); } function collapse_sidebar() { sidebarwrapper.hide(); sidebar.css('width', ssb_width_collapsed); bodywrapper.css('margin-left', bw_margin_collapsed); sidebarbutton.css({ 'margin-left': '0', 'height': bodywrapper.height() }); sidebarbutton.find('span').text('»'); sidebarbutton.attr('title', _('Expand sidebar')); document.cookie = 'sidebar=collapsed'; } function expand_sidebar() { bodywrapper.css('margin-left', bw_margin_expanded); sidebar.css('width', ssb_width_expanded); sidebarwrapper.show(); sidebarbutton.css({ 'margin-left': ssb_width_expanded-12, 'height': bodywrapper.height() }); sidebarbutton.find('span').text('«'); sidebarbutton.attr('title', _('Collapse sidebar')); document.cookie = 'sidebar=expanded'; } function add_sidebar_button() { sidebarwrapper.css({ 'float': 'left', 'margin-right': '0', 'width': ssb_width_expanded - 28 }); // create the button sidebar.append( '
    «
    ' ); var sidebarbutton = $('#sidebarbutton'); light_color = sidebarbutton.css('background-color'); // find the height of the viewport to center the '<<' in the page var viewport_height; if (window.innerHeight) viewport_height = window.innerHeight; else viewport_height = $(window).height(); sidebarbutton.find('span').css({ 'display': 'block', 'margin-top': (viewport_height - sidebar.position().top - 20) / 2 }); sidebarbutton.click(toggle_sidebar); sidebarbutton.attr('title', _('Collapse sidebar')); sidebarbutton.css({ 'color': '#FFFFFF', 'border-left': '1px solid ' + dark_color, 'font-size': '1.2em', 'cursor': 'pointer', 'height': bodywrapper.height(), 'padding-top': '1px', 'margin-left': ssb_width_expanded - 12 }); sidebarbutton.hover( function () { $(this).css('background-color', dark_color); }, function () { $(this).css('background-color', light_color); } ); } function set_position_from_cookie() { if (!document.cookie) return; var items = document.cookie.split(';'); for(var k=0; k <‰uIDATxÚbxóæÍ02 D H"„U 0½}ûÂBfB?2‡ غ‰`@ØMÀnv‡acb*Ñ €°‡±¡B¾ÕLÄx™_”½FB¬P?IPÙ/$¸‘Ú`dúÂUÖ­s:HIEND®B`‚ansible-1.7.2/docsite/_themes/000077500000000000000000000000001241061774000162165ustar00rootroot00000000000000ansible-1.7.2/docsite/_themes/srtd/000077500000000000000000000000001241061774000171725ustar00rootroot00000000000000ansible-1.7.2/docsite/_themes/srtd/__init__.py000066400000000000000000000005631241061774000213070ustar00rootroot00000000000000"""Sphinx ReadTheDocs theme. From https://github.com/ryan-roemer/sphinx-bootstrap-theme. """ import os VERSION = (0, 1, 5) __version__ = ".".join(str(v) for v in VERSION) __version_full__ = __version__ def get_html_theme_path(): """Return list of HTML theme paths.""" cur_dir = os.path.abspath(os.path.dirname(os.path.dirname(__file__))) return cur_dir ansible-1.7.2/docsite/_themes/srtd/breadcrumbs.html000066400000000000000000000007031241061774000223510ustar00rootroot00000000000000
    • Docs »
    • {{ title }}
      • {% if not pagename.endswith('_module') and (not 'list_of' in pagename) and (not 'category' in pagename) %}
    • Edit on GitHub
      • {% endif %}
    ansible-1.7.2/docsite/_themes/srtd/footer.html000066400000000000000000000024021241061774000213540ustar00rootroot00000000000000
    {% if next or prev %}
    {% if next %} Next {% endif %} {% if prev %} Previous {% endif %}
    {% endif %}

    © Copyright 2014 Ansible, Inc.. {%- if last_updated %} {% trans last_updated=last_updated|e %}Last updated on {{ last_updated }}.{% endtrans %} {%- endif %}

    Ansible docs are generated from GitHub sources using Sphinx using a theme provided by Read the Docs. {% if pagename.endswith("_module") %}. Module documentation is not edited directly, but is generated from the source code for the modules. To submit an update to module docs, edit the 'DOCUMENTATION' metadata in the module source tree. {% endif %}
    ansible-1.7.2/docsite/_themes/srtd/layout.html000066400000000000000000000167331241061774000214070ustar00rootroot00000000000000{# TEMPLATE VAR SETTINGS #} {%- set url_root = pathto('', 1) %} {%- if url_root == '#' %}{% set url_root = '' %}{% endif %} {%- if not embedded and docstitle %} {%- set titlesuffix = " — "|safe + docstitle|e %} {%- else %} {%- set titlesuffix = "" %} {%- endif %} {% block htmltitle %} {{ title|striptags|e }}{{ titlesuffix }} {% endblock %} {# FAVICON #} {% if favicon %} {% endif %} {# CSS #} {# JS #} {% if not embedded %} {%- for scriptfile in script_files %} {%- endfor %} {% if use_opensearch %} {% endif %} {% endif %} {# RTD hosts these file themselves, so just load on non RTD builds #} {% if not READTHEDOCS %} {% endif %} {% for cssfile in css_files %} {% endfor %} {%- block linktags %} {%- if hasdoc('about') %} {%- endif %} {%- if hasdoc('genindex') %} {%- endif %} {%- if hasdoc('search') %} {%- endif %} {%- if hasdoc('copyright') %} {%- endif %} {%- if parents %} {%- endif %} {%- if next %} {%- endif %} {%- if prev %} {%- endif %} {%- endblock %} {%- block extrahead %} {% endblock %}
    {# SIDE NAV, TOGGLES ON MOBILE #}
    {# MOBILE NAV, TRIGGLES SIDE NAV ON TOGGLE #} {# PAGE CONTENT #}
    {% include "breadcrumbs.html" %}
    {% block body %}{% endblock %}
    {% include "footer.html" %}
    {% include "versions.html" %} ansible-1.7.2/docsite/_themes/srtd/layout_old.html000066400000000000000000000162551241061774000222440ustar00rootroot00000000000000{# basic/layout.html ~~~~~~~~~~~~~~~~~ Master layout template for Sphinx themes. :copyright: Copyright 2007-2013 by the Sphinx team, see AUTHORS. :license: BSD, see LICENSE for details. #} {%- block doctype -%} {%- endblock %} {%- set reldelim1 = reldelim1 is not defined and ' »' or reldelim1 %} {%- set reldelim2 = reldelim2 is not defined and ' |' or reldelim2 %} {%- set render_sidebar = (not embedded) and (not theme_nosidebar|tobool) and (sidebars != []) %} {%- set url_root = pathto('', 1) %} {# XXX necessary? #} {%- if url_root == '#' %}{% set url_root = '' %}{% endif %} {%- if not embedded and docstitle %} {%- set titlesuffix = " — "|safe + docstitle|e %} {%- else %} {%- set titlesuffix = "" %} {%- endif %} {%- macro relbar() %}

    {{ _('Navigation') }}

      {%- for rellink in rellinks %}
    • {{ rellink[3] }} {%- if not loop.first %}{{ reldelim2 }}{% endif %}
      • {%- endfor %} {%- block rootrellink %}
    • {{ shorttitle|e }}{{ reldelim1 }}
      • {%- endblock %} {%- for parent in parents %}
    • {{ parent.title }}{{ reldelim1 }}
      • {%- endfor %} {%- block relbaritems %} {% endblock %}
    {%- endmacro %} {%- macro sidebar() %} {%- if render_sidebar %}
    {%- block sidebarlogo %} {%- if logo %} {%- endif %} {%- endblock %} {%- if sidebars != None %} {#- new style sidebar: explicitly include/exclude templates #} {%- for sidebartemplate in sidebars %} {%- include sidebartemplate %} {%- endfor %} {%- else %} {#- old style sidebars: using blocks -- should be deprecated #} {%- block sidebartoc %} {%- include "localtoc.html" %} {%- endblock %} {%- block sidebarrel %} {%- include "relations.html" %} {%- endblock %} {%- block sidebarsourcelink %} {%- include "sourcelink.html" %} {%- endblock %} {%- if customsidebar %} {%- include customsidebar %} {%- endif %} {%- block sidebarsearch %} {%- include "searchbox.html" %} {%- endblock %} {%- endif %}
    {%- endif %} {%- endmacro %} {%- macro script() %} {%- for scriptfile in script_files %} {%- endfor %} {%- endmacro %} {%- macro css() %} {%- for cssfile in css_files %} {%- endfor %} {%- endmacro %} {{ metatags }} {%- block htmltitle %} {{ title|striptags|e }}{{ titlesuffix }} {%- endblock %} {{ css() }} {%- if not embedded %} {{ script() }} {%- if use_opensearch %} {%- endif %} {%- if favicon %} {%- endif %} {%- endif %} {%- block linktags %} {%- if hasdoc('about') %} {%- endif %} {%- if hasdoc('genindex') %} {%- endif %} {%- if hasdoc('search') %} {%- endif %} {%- if hasdoc('copyright') %} {%- endif %} {%- if parents %} {%- endif %} {%- if next %} {%- endif %} {%- if prev %} {%- endif %} {%- endblock %} {%- block extrahead %} {% endblock %} {%- block header %}{% endblock %} {%- block relbar1 %}{{ relbar() }}{% endblock %} {%- block content %} {%- block sidebar1 %} {# possible location for sidebar #} {% endblock %}
    {%- block document %}
    {%- if render_sidebar %}
    {%- endif %}
    {% block body %} {% endblock %}
    {%- if render_sidebar %}
    {%- endif %}
    {%- endblock %} {%- block sidebar2 %}{{ sidebar() }}{% endblock %}
    {%- endblock %} {%- block relbar2 %}{{ relbar() }}{% endblock %} {%- block footer %}
    {%- if show_copyright %} {%- if hasdoc('copyright') %} {% trans path=pathto('copyright'), copyright=copyright|e %}© Copyright {{ copyright }}.{% endtrans %} {%- else %} {% trans copyright=copyright|e %}© Copyright {{ copyright }}.{% endtrans %} {%- endif %} {%- endif %} {%- if last_updated %} {% trans last_updated=last_updated|e %}Last updated on {{ last_updated }}.{% endtrans %} {%- endif %} {%- if show_sphinx %} {% trans sphinx_version=sphinx_version|e %}Created using Sphinx {{ sphinx_version }}.{% endtrans %} {%- endif %}

    asdf asdf asdf asdf 22

    {%- endblock %} ansible-1.7.2/docsite/_themes/srtd/search.html000066400000000000000000000027751241061774000213400ustar00rootroot00000000000000{# basic/search.html ~~~~~~~~~~~~~~~~~ Template for the search page. :copyright: Copyright 2007-2013 by the Sphinx team, see AUTHORS. :license: BSD, see LICENSE for details. #} {%- extends "layout.html" %} {% set title = _('Search') %} {% set script_files = script_files + ['_static/searchtools.js'] %} {% block extrahead %} {# this is used when loading the search index using $.ajax fails, such as on Chrome for documents on localhost #} {{ super() }} {% endblock %} {% block body %} {% if search_performed %}

    {{ _('Search Results') }}

    {% if not search_results %}

    {{ _('Your search did not match any documents. Please make sure that all words are spelled correctly and that you\'ve selected enough categories.') }}

    {% endif %} {% endif %}
    {% if search_results %}
      {% for href, caption, context in search_results %}
    • {{ caption }}

      {{ context|e }}

      • {% endfor %}
    {% endif %}
    {% endblock %} ansible-1.7.2/docsite/_themes/srtd/searchbox.html000066400000000000000000000042631241061774000220430ustar00rootroot00000000000000
    ansible-1.7.2/docsite/_themes/srtd/static/000077500000000000000000000000001241061774000204615ustar00rootroot00000000000000ansible-1.7.2/docsite/_themes/srtd/static/css/000077500000000000000000000000001241061774000212515ustar00rootroot00000000000000ansible-1.7.2/docsite/_themes/srtd/static/css/badge_only.css000066400000000000000000000056601241061774000240750ustar00rootroot00000000000000.font-smooth,.icon:before{-webkit-font-smoothing:antialiased}.clearfix{*zoom:1}.clearfix:before,.clearfix:after{display:table;content:""}.clearfix:after{clear:both}@font-face{font-family:fontawesome-webfont;font-weight:normal;font-style:normal;src:url("../font/fontawesome_webfont.eot");src:url("../font/fontawesome_webfont.eot?#iefix") format("embedded-opentype"),url("../font/fontawesome_webfont.woff") format("woff"),url("../font/fontawesome_webfont.ttf") format("truetype"),url("../font/fontawesome_webfont.svg#fontawesome-webfont") format("svg")}.icon:before{display:inline-block;font-family:fontawesome-webfont;font-style:normal;font-weight:normal;line-height:1;text-decoration:inherit}a .icon{display:inline-block;text-decoration:inherit}li .icon{display:inline-block}li .icon-large:before,li .icon-large:before{width:1.875em}ul.icons{list-style-type:none;margin-left:2em;text-indent:-0.8em}ul.icons li .icon{width:0.8em}ul.icons li .icon-large:before,ul.icons li .icon-large:before{vertical-align:baseline}.icon-book:before{content:"\f02d"}.icon-caret-down:before{content:"\f0d7"}.icon-caret-up:before{content:"\f0d8"}.icon-caret-left:before{content:"\f0d9"}.icon-caret-right:before{content:"\f0da"}.rst-versions{position:fixed;bottom:0;left:0;width:300px;color:#fcfcfc;background:#1f1d1d;border-top:solid 10px #343131;font-family:"Lato","proxima-nova","Helvetica Neue",Arial,sans-serif;z-index:400}.rst-versions a{color:#2980b9;text-decoration:none}.rst-versions .rst-badge-small{display:none}.rst-versions .rst-current-version{padding:12px;background-color:#272525;display:block;text-align:right;font-size:90%;cursor:pointer;color:#27ae60;*zoom:1}.rst-versions .rst-current-version:before,.rst-versions .rst-current-version:after{display:table;content:""}.rst-versions .rst-current-version:after{clear:both}.rst-versions .rst-current-version .icon{color:#fcfcfc}.rst-versions .rst-current-version .icon-book{float:left}.rst-versions .rst-current-version.rst-out-of-date{background-color:#e74c3c;color:#fff}.rst-versions.shift-up .rst-other-versions{display:block}.rst-versions .rst-other-versions{font-size:90%;padding:12px;color:gray;display:none}.rst-versions .rst-other-versions hr{display:block;height:1px;border:0;margin:20px 0;padding:0;border-top:solid 1px #413d3d}.rst-versions .rst-other-versions dd{display:inline-block;margin:0}.rst-versions .rst-other-versions dd a{display:inline-block;padding:6px;color:#fcfcfc}.rst-versions.rst-badge{width:auto;bottom:20px;right:20px;left:auto;border:none;max-width:300px}.rst-versions.rst-badge .icon-book{float:none}.rst-versions.rst-badge.shift-up .rst-current-version{text-align:right}.rst-versions.rst-badge.shift-up .rst-current-version .icon-book{float:left}.rst-versions.rst-badge .rst-current-version{width:auto;height:30px;line-height:30px;padding:0 6px;display:block;text-align:center}@media screen and (max-width: 768px){.rst-versions{width:85%;display:none}.rst-versions.shift{display:block}img{width:100%;height:auto}} ansible-1.7.2/docsite/_themes/srtd/static/css/theme.css000066400000000000000000003075371241061774000231040ustar00rootroot00000000000000* { -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; } article, aside, details, figcaption, figure, footer, header, hgroup, nav, section { display: block; } audio, canvas, video { display: inline-block; *display: inline; *zoom: 1; } audio:not([controls]) { display: none; } [hidden] { display: none; } * { -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; } html { font-size: 100%; -webkit-text-size-adjust: 100%; -ms-text-size-adjust: 100%; } body { margin: 0; } a:hover, a:active { outline: 0; } abbr[title] { border-bottom: 1px dotted; } b, strong { font-weight: bold; } blockquote { margin: 0; } dfn { font-style: italic; } hr { display: block; height: 1px; border: 0; border-top: 1px solid #ccc; margin: 20px 0; padding: 0; } ins { background: #ff9; color: #000; text-decoration: none; } mark { background: #ff0; color: #000; font-style: italic; font-weight: bold; } pre, code, .rst-content tt, kbd, samp { font-family: monospace, serif; _font-family: "courier new", monospace; font-size: 1em; } pre { white-space: pre; } q { quotes: none; } q:before, q:after { content: ""; content: none; } small { font-size: 85%; } sub, sup { font-size: 75%; line-height: 0; position: relative; vertical-align: baseline; } sup { top: -0.5em; } sub { bottom: -0.25em; } ul, ol, dl { margin: 0; padding: 0; list-style: none; list-style-image: none; } li { list-style: none; } dd { margin: 0; } img { border: 0; -ms-interpolation-mode: bicubic; vertical-align: middle; max-width: 100%; } svg:not(:root) { overflow: hidden; } figure { margin: 0; } form { margin: 0; } fieldset { border: 0; margin: 0; padding: 0; } label { cursor: pointer; } legend { border: 0; *margin-left: -7px; padding: 0; white-space: normal; } button, input, select, textarea { font-size: 100%; margin: 0; vertical-align: baseline; *vertical-align: middle; } button, input { line-height: normal; } button, input[type="button"], input[type="reset"], input[type="submit"] { cursor: pointer; -webkit-appearance: button; *overflow: visible; } button[disabled], input[disabled] { cursor: default; } input[type="checkbox"], input[type="radio"] { box-sizing: border-box; padding: 0; *width: 13px; *height: 13px; } input[type="search"] { -webkit-appearance: textfield; -moz-box-sizing: content-box; -webkit-box-sizing: content-box; box-sizing: content-box; } input[type="search"]::-webkit-search-decoration, input[type="search"]::-webkit-search-cancel-button { -webkit-appearance: none; } button::-moz-focus-inner, input::-moz-focus-inner { border: 0; padding: 0; } textarea { overflow: auto; vertical-align: top; resize: vertical; } table { border-collapse: collapse; border-spacing: 0; } td { vertical-align: top; } .chromeframe { margin: 0.2em 0; background: #ccc; color: #000; padding: 0.2em 0; } .ir { display: block; border: 0; text-indent: -999em; overflow: hidden; background-color: transparent; background-repeat: no-repeat; text-align: left; direction: ltr; *line-height: 0; } .ir br { display: none; } .hidden { display: none !important; visibility: hidden; } .visuallyhidden { border: 0; clip: rect(0 0 0 0); height: 1px; margin: -1px; overflow: hidden; padding: 0; position: absolute; width: 1px; } .visuallyhidden.focusable:active, .visuallyhidden.focusable:focus { clip: auto; height: auto; margin: 0; overflow: visible; position: static; width: auto; } .invisible { visibility: hidden; } .relative { position: relative; } big, small { font-size: 100%; } @media print { html, body, section { background: none !important; } * { box-shadow: none !important; text-shadow: none !important; filter: none !important; -ms-filter: none !important; } a, a:visited { text-decoration: underline; } .ir a:after, a[href^="javascript:"]:after, a[href^="#"]:after { content: ""; } pre, blockquote { page-break-inside: avoid; } thead { display: table-header-group; } tr, img { page-break-inside: avoid; } img { max-width: 100% !important; } @page { margin: 0.5cm; } p, h2, h3 { orphans: 3; widows: 3; } h2, h3 { page-break-after: avoid; } } .font-smooth, .icon:before, .wy-inline-validate.wy-inline-validate-success .wy-input-context:before, .wy-inline-validate.wy-inline-validate-danger .wy-input-context:before, .wy-inline-validate.wy-inline-validate-warning .wy-input-context:before, .wy-inline-validate.wy-inline-validate-info .wy-input-context:before, .wy-tag-input-group .wy-tag .wy-tag-remove:before, .rst-content .admonition-title:before, .rst-content h1 .headerlink:before, .rst-content h2 .headerlink:before, .rst-content h3 .headerlink:before, .rst-content h4 .headerlink:before, .rst-content h5 .headerlink:before, .rst-content h6 .headerlink:before, .rst-content dl dt .headerlink:before, .wy-alert, .rst-content .note, .rst-content .attention, .rst-content .caution, .rst-content .danger, .rst-content .error, .rst-content .hint, .rst-content .important, .rst-content .tip, .rst-content .warning, .btn, input[type="text"], input[type="password"], input[type="email"], input[type="url"], input[type="date"], input[type="month"], input[type="time"], input[type="datetime"], input[type="datetime-local"], input[type="week"], input[type="number"], input[type="search"], input[type="tel"], input[type="color"], select, textarea, .wy-tag-input-group, .wy-menu-vertical li.on a, .wy-menu-vertical li.current>a, .wy-side-nav-search>a, .wy-side-nav-search .wy-dropdown>a, .wy-nav-top a { -webkit-font-smoothing: antialiased; } .clearfix { *zoom: 1; } .clearfix:before, .clearfix:after { display: table; content: ""; } .clearfix:after { clear: both; } @font-face { font-family: fontawesome-webfont; font-weight: normal; font-style: normal; src: url("../font/fontawesome_webfont.eot"); src: url("../font/fontawesome_webfont.eot?#iefix") format("embedded-opentype"), url("../font/fontawesome_webfont.woff") format("woff"), url("../font/fontawesome_webfont.ttf") format("truetype"), url("../font/fontawesome_webfont.svg#fontawesome-webfont") format("svg"); } .icon:before, .wy-inline-validate.wy-inline-validate-success .wy-input-context:before, .wy-inline-validate.wy-inline-validate-danger .wy-input-context:before, .wy-inline-validate.wy-inline-validate-warning .wy-input-context:before, .wy-inline-validate.wy-inline-validate-info .wy-input-context:before, .wy-tag-input-group .wy-tag .wy-tag-remove:before, .rst-content .admonition-title:before, .rst-content h1 .headerlink:before, .rst-content h2 .headerlink:before, .rst-content h3 .headerlink:before, .rst-content h4 .headerlink:before, .rst-content h5 .headerlink:before, .rst-content h6 .headerlink:before, .rst-content dl dt .headerlink:before { display: inline-block; font-family: fontawesome-webfont; font-style: normal; font-weight: normal; line-height: 1; text-decoration: inherit; } a .icon, a .wy-inline-validate.wy-inline-validate-success .wy-input-context, .wy-inline-validate.wy-inline-validate-success a .wy-input-context, a .wy-inline-validate.wy-inline-validate-danger .wy-input-context, .wy-inline-validate.wy-inline-validate-danger a .wy-input-context, a .wy-inline-validate.wy-inline-validate-warning .wy-input-context, .wy-inline-validate.wy-inline-validate-warning a .wy-input-context, a .wy-inline-validate.wy-inline-validate-info .wy-input-context, .wy-inline-validate.wy-inline-validate-info a .wy-input-context, a .wy-tag-input-group .wy-tag .wy-tag-remove, .wy-tag-input-group .wy-tag a .wy-tag-remove, a .rst-content .admonition-title, .rst-content a .admonition-title, a .rst-content h1 .headerlink, .rst-content h1 a .headerlink, a .rst-content h2 .headerlink, .rst-content h2 a .headerlink, a .rst-content h3 .headerlink, .rst-content h3 a .headerlink, a .rst-content h4 .headerlink, .rst-content h4 a .headerlink, a .rst-content h5 .headerlink, .rst-content h5 a .headerlink, a .rst-content h6 .headerlink, .rst-content h6 a .headerlink, a .rst-content dl dt .headerlink, .rst-content dl dt a .headerlink { display: inline-block; text-decoration: inherit; } .icon-large:before { vertical-align: -10%; font-size: 1.33333em; } .btn .icon, .btn .wy-inline-validate.wy-inline-validate-success .wy-input-context, .wy-inline-validate.wy-inline-validate-success .btn .wy-input-context, .btn .wy-inline-validate.wy-inline-validate-danger .wy-input-context, .wy-inline-validate.wy-inline-validate-danger .btn .wy-input-context, .btn .wy-inline-validate.wy-inline-validate-warning .wy-input-context, .wy-inline-validate.wy-inline-validate-warning .btn .wy-input-context, .btn .wy-inline-validate.wy-inline-validate-info .wy-input-context, .wy-inline-validate.wy-inline-validate-info .btn .wy-input-context, .btn .wy-tag-input-group .wy-tag .wy-tag-remove, .wy-tag-input-group .wy-tag .btn .wy-tag-remove, .btn .rst-content .admonition-title, .rst-content .btn .admonition-title, .btn .rst-content h1 .headerlink, .rst-content h1 .btn .headerlink, .btn .rst-content h2 .headerlink, .rst-content h2 .btn .headerlink, .btn .rst-content h3 .headerlink, .rst-content h3 .btn .headerlink, .btn .rst-content h4 .headerlink, .rst-content h4 .btn .headerlink, .btn .rst-content h5 .headerlink, .rst-content h5 .btn .headerlink, .btn .rst-content h6 .headerlink, .rst-content h6 .btn .headerlink, .btn .rst-content dl dt .headerlink, .rst-content dl dt .btn .headerlink, .nav .icon, .nav .wy-inline-validate.wy-inline-validate-success .wy-input-context, .wy-inline-validate.wy-inline-validate-success .nav .wy-input-context, .nav .wy-inline-validate.wy-inline-validate-danger .wy-input-context, .wy-inline-validate.wy-inline-validate-danger .nav .wy-input-context, .nav .wy-inline-validate.wy-inline-validate-warning .wy-input-context, .wy-inline-validate.wy-inline-validate-warning .nav .wy-input-context, .nav .wy-inline-validate.wy-inline-validate-info .wy-input-context, .wy-inline-validate.wy-inline-validate-info .nav .wy-input-context, .nav .wy-tag-input-group .wy-tag .wy-tag-remove, .wy-tag-input-group .wy-tag .nav .wy-tag-remove, .nav .rst-content .admonition-title, .rst-content .nav .admonition-title, .nav .rst-content h1 .headerlink, .rst-content h1 .nav .headerlink, .nav .rst-content h2 .headerlink, .rst-content h2 .nav .headerlink, .nav .rst-content h3 .headerlink, .rst-content h3 .nav .headerlink, .nav .rst-content h4 .headerlink, .rst-content h4 .nav .headerlink, .nav .rst-content h5 .headerlink, .rst-content h5 .nav .headerlink, .nav .rst-content h6 .headerlink, .rst-content h6 .nav .headerlink, .nav .rst-content dl dt .headerlink, .rst-content dl dt .nav .headerlink { display: inline; } .btn .icon.icon-large, .btn .wy-inline-validate.wy-inline-validate-success .icon-large.wy-input-context, .wy-inline-validate.wy-inline-validate-success .btn .icon-large.wy-input-context, .btn .wy-inline-validate.wy-inline-validate-danger .icon-large.wy-input-context, .wy-inline-validate.wy-inline-validate-danger .btn .icon-large.wy-input-context, .btn .wy-inline-validate.wy-inline-validate-warning .icon-large.wy-input-context, .wy-inline-validate.wy-inline-validate-warning .btn .icon-large.wy-input-context, .btn .wy-inline-validate.wy-inline-validate-info .icon-large.wy-input-context, .wy-inline-validate.wy-inline-validate-info .btn .icon-large.wy-input-context, .btn .wy-tag-input-group .wy-tag .icon-large.wy-tag-remove, .wy-tag-input-group .wy-tag .btn .icon-large.wy-tag-remove, .btn .rst-content .icon-large.admonition-title, .rst-content .btn .icon-large.admonition-title, .btn .rst-content h1 .icon-large.headerlink, .rst-content h1 .btn .icon-large.headerlink, .btn .rst-content h2 .icon-large.headerlink, .rst-content h2 .btn .icon-large.headerlink, .btn .rst-content h3 .icon-large.headerlink, .rst-content h3 .btn .icon-large.headerlink, .btn .rst-content h4 .icon-large.headerlink, .rst-content h4 .btn .icon-large.headerlink, .btn .rst-content h5 .icon-large.headerlink, .rst-content h5 .btn .icon-large.headerlink, .btn .rst-content h6 .icon-large.headerlink, .rst-content h6 .btn .icon-large.headerlink, .btn .rst-content dl dt .icon-large.headerlink, .rst-content dl dt .btn .icon-large.headerlink, .nav .icon.icon-large, .nav .wy-inline-validate.wy-inline-validate-success .icon-large.wy-input-context, .wy-inline-validate.wy-inline-validate-success .nav .icon-large.wy-input-context, .nav .wy-inline-validate.wy-inline-validate-danger .icon-large.wy-input-context, .wy-inline-validate.wy-inline-validate-danger .nav .icon-large.wy-input-context, .nav .wy-inline-validate.wy-inline-validate-warning .icon-large.wy-input-context, .wy-inline-validate.wy-inline-validate-warning .nav .icon-large.wy-input-context, .nav .wy-inline-validate.wy-inline-validate-info .icon-large.wy-input-context, .wy-inline-validate.wy-inline-validate-info .nav .icon-large.wy-input-context, .nav .wy-tag-input-group .wy-tag .icon-large.wy-tag-remove, .wy-tag-input-group .wy-tag .nav .icon-large.wy-tag-remove, .nav .rst-content .icon-large.admonition-title, .rst-content .nav .icon-large.admonition-title, .nav .rst-content h1 .icon-large.headerlink, .rst-content h1 .nav .icon-large.headerlink, .nav .rst-content h2 .icon-large.headerlink, .rst-content h2 .nav .icon-large.headerlink, .nav .rst-content h3 .icon-large.headerlink, .rst-content h3 .nav .icon-large.headerlink, .nav .rst-content h4 .icon-large.headerlink, .rst-content h4 .nav .icon-large.headerlink, .nav .rst-content h5 .icon-large.headerlink, .rst-content h5 .nav .icon-large.headerlink, .nav .rst-content h6 .icon-large.headerlink, .rst-content h6 .nav .icon-large.headerlink, .nav .rst-content dl dt .icon-large.headerlink, .rst-content dl dt .nav .icon-large.headerlink { line-height: 0.9em; } .btn .icon.icon-spin, .btn .wy-inline-validate.wy-inline-validate-success .icon-spin.wy-input-context, .wy-inline-validate.wy-inline-validate-success .btn .icon-spin.wy-input-context, .btn .wy-inline-validate.wy-inline-validate-danger .icon-spin.wy-input-context, .wy-inline-validate.wy-inline-validate-danger .btn .icon-spin.wy-input-context, .btn .wy-inline-validate.wy-inline-validate-warning .icon-spin.wy-input-context, .wy-inline-validate.wy-inline-validate-warning .btn .icon-spin.wy-input-context, .btn .wy-inline-validate.wy-inline-validate-info .icon-spin.wy-input-context, .wy-inline-validate.wy-inline-validate-info .btn .icon-spin.wy-input-context, .btn .wy-tag-input-group .wy-tag .icon-spin.wy-tag-remove, .wy-tag-input-group .wy-tag .btn .icon-spin.wy-tag-remove, .btn .rst-content .icon-spin.admonition-title, .rst-content .btn .icon-spin.admonition-title, .btn .rst-content h1 .icon-spin.headerlink, .rst-content h1 .btn .icon-spin.headerlink, .btn .rst-content h2 .icon-spin.headerlink, .rst-content h2 .btn .icon-spin.headerlink, .btn .rst-content h3 .icon-spin.headerlink, .rst-content h3 .btn .icon-spin.headerlink, .btn .rst-content h4 .icon-spin.headerlink, .rst-content h4 .btn .icon-spin.headerlink, .btn .rst-content h5 .icon-spin.headerlink, .rst-content h5 .btn .icon-spin.headerlink, .btn .rst-content h6 .icon-spin.headerlink, .rst-content h6 .btn .icon-spin.headerlink, .btn .rst-content dl dt .icon-spin.headerlink, .rst-content dl dt .btn .icon-spin.headerlink, .nav .icon.icon-spin, .nav .wy-inline-validate.wy-inline-validate-success .icon-spin.wy-input-context, .wy-inline-validate.wy-inline-validate-success .nav .icon-spin.wy-input-context, .nav .wy-inline-validate.wy-inline-validate-danger .icon-spin.wy-input-context, .wy-inline-validate.wy-inline-validate-danger .nav .icon-spin.wy-input-context, .nav .wy-inline-validate.wy-inline-validate-warning .icon-spin.wy-input-context, .wy-inline-validate.wy-inline-validate-warning .nav .icon-spin.wy-input-context, .nav .wy-inline-validate.wy-inline-validate-info .icon-spin.wy-input-context, .wy-inline-validate.wy-inline-validate-info .nav .icon-spin.wy-input-context, .nav .wy-tag-input-group .wy-tag .icon-spin.wy-tag-remove, .wy-tag-input-group .wy-tag .nav .icon-spin.wy-tag-remove, .nav .rst-content .icon-spin.admonition-title, .rst-content .nav .icon-spin.admonition-title, .nav .rst-content h1 .icon-spin.headerlink, .rst-content h1 .nav .icon-spin.headerlink, .nav .rst-content h2 .icon-spin.headerlink, .rst-content h2 .nav .icon-spin.headerlink, .nav .rst-content h3 .icon-spin.headerlink, .rst-content h3 .nav .icon-spin.headerlink, .nav .rst-content h4 .icon-spin.headerlink, .rst-content h4 .nav .icon-spin.headerlink, .nav .rst-content h5 .icon-spin.headerlink, .rst-content h5 .nav .icon-spin.headerlink, .nav .rst-content h6 .icon-spin.headerlink, .rst-content h6 .nav .icon-spin.headerlink, .nav .rst-content dl dt .icon-spin.headerlink, .rst-content dl dt .nav .icon-spin.headerlink { display: inline-block; } .btn.icon:before, .wy-inline-validate.wy-inline-validate-success .btn.wy-input-context:before, .wy-inline-validate.wy-inline-validate-danger .btn.wy-input-context:before, .wy-inline-validate.wy-inline-validate-warning .btn.wy-input-context:before, .wy-inline-validate.wy-inline-validate-info .btn.wy-input-context:before, .wy-tag-input-group .wy-tag .btn.wy-tag-remove:before, .rst-content .btn.admonition-title:before, .rst-content h1 .btn.headerlink:before, .rst-content h2 .btn.headerlink:before, .rst-content h3 .btn.headerlink:before, .rst-content h4 .btn.headerlink:before, .rst-content h5 .btn.headerlink:before, .rst-content h6 .btn.headerlink:before, .rst-content dl dt .btn.headerlink:before { opacity: 0.5; -webkit-transition: opacity 0.05s ease-in; -moz-transition: opacity 0.05s ease-in; transition: opacity 0.05s ease-in; } .btn.icon:hover:before, .wy-inline-validate.wy-inline-validate-success .btn.wy-input-context:hover:before, .wy-inline-validate.wy-inline-validate-danger .btn.wy-input-context:hover:before, .wy-inline-validate.wy-inline-validate-warning .btn.wy-input-context:hover:before, .wy-inline-validate.wy-inline-validate-info .btn.wy-input-context:hover:before, .wy-tag-input-group .wy-tag .btn.wy-tag-remove:hover:before, .rst-content .btn.admonition-title:hover:before, .rst-content h1 .btn.headerlink:hover:before, .rst-content h2 .btn.headerlink:hover:before, .rst-content h3 .btn.headerlink:hover:before, .rst-content h4 .btn.headerlink:hover:before, .rst-content h5 .btn.headerlink:hover:before, .rst-content h6 .btn.headerlink:hover:before, .rst-content dl dt .btn.headerlink:hover:before { opacity: 1; } .btn-mini .icon:before, .btn-mini .wy-inline-validate.wy-inline-validate-success .wy-input-context:before, .wy-inline-validate.wy-inline-validate-success .btn-mini .wy-input-context:before, .btn-mini .wy-inline-validate.wy-inline-validate-danger .wy-input-context:before, .wy-inline-validate.wy-inline-validate-danger .btn-mini .wy-input-context:before, .btn-mini .wy-inline-validate.wy-inline-validate-warning .wy-input-context:before, .wy-inline-validate.wy-inline-validate-warning .btn-mini .wy-input-context:before, .btn-mini .wy-inline-validate.wy-inline-validate-info .wy-input-context:before, .wy-inline-validate.wy-inline-validate-info .btn-mini .wy-input-context:before, .btn-mini .wy-tag-input-group .wy-tag .wy-tag-remove:before, .wy-tag-input-group .wy-tag .btn-mini .wy-tag-remove:before, .btn-mini .rst-content .admonition-title:before, .rst-content .btn-mini .admonition-title:before, .btn-mini .rst-content h1 .headerlink:before, .rst-content h1 .btn-mini .headerlink:before, .btn-mini .rst-content h2 .headerlink:before, .rst-content h2 .btn-mini .headerlink:before, .btn-mini .rst-content h3 .headerlink:before, .rst-content h3 .btn-mini .headerlink:before, .btn-mini .rst-content h4 .headerlink:before, .rst-content h4 .btn-mini .headerlink:before, .btn-mini .rst-content h5 .headerlink:before, .rst-content h5 .btn-mini .headerlink:before, .btn-mini .rst-content h6 .headerlink:before, .rst-content h6 .btn-mini .headerlink:before, .btn-mini .rst-content dl dt .headerlink:before, .rst-content dl dt .btn-mini .headerlink:before { font-size: 14px; vertical-align: -15%; } li .icon, li .wy-inline-validate.wy-inline-validate-success .wy-input-context, .wy-inline-validate.wy-inline-validate-success li .wy-input-context, li .wy-inline-validate.wy-inline-validate-danger .wy-input-context, .wy-inline-validate.wy-inline-validate-danger li .wy-input-context, li .wy-inline-validate.wy-inline-validate-warning .wy-input-context, .wy-inline-validate.wy-inline-validate-warning li .wy-input-context, li .wy-inline-validate.wy-inline-validate-info .wy-input-context, .wy-inline-validate.wy-inline-validate-info li .wy-input-context, li .wy-tag-input-group .wy-tag .wy-tag-remove, .wy-tag-input-group .wy-tag li .wy-tag-remove, li .rst-content .admonition-title, .rst-content li .admonition-title, li .rst-content h1 .headerlink, .rst-content h1 li .headerlink, li .rst-content h2 .headerlink, .rst-content h2 li .headerlink, li .rst-content h3 .headerlink, .rst-content h3 li .headerlink, li .rst-content h4 .headerlink, .rst-content h4 li .headerlink, li .rst-content h5 .headerlink, .rst-content h5 li .headerlink, li .rst-content h6 .headerlink, .rst-content h6 li .headerlink, li .rst-content dl dt .headerlink, .rst-content dl dt li .headerlink { display: inline-block; } li .icon-large:before, li .icon-large:before { width: 1.875em; } ul.icons { list-style-type: none; margin-left: 2em; text-indent: -0.8em; } ul.icons li .icon, ul.icons li .wy-inline-validate.wy-inline-validate-success .wy-input-context, .wy-inline-validate.wy-inline-validate-success ul.icons li .wy-input-context, ul.icons li .wy-inline-validate.wy-inline-validate-danger .wy-input-context, .wy-inline-validate.wy-inline-validate-danger ul.icons li .wy-input-context, ul.icons li .wy-inline-validate.wy-inline-validate-warning .wy-input-context, .wy-inline-validate.wy-inline-validate-warning ul.icons li .wy-input-context, ul.icons li .wy-inline-validate.wy-inline-validate-info .wy-input-context, .wy-inline-validate.wy-inline-validate-info ul.icons li .wy-input-context, ul.icons li .wy-tag-input-group .wy-tag .wy-tag-remove, .wy-tag-input-group .wy-tag ul.icons li .wy-tag-remove, ul.icons li .rst-content .admonition-title, .rst-content ul.icons li .admonition-title, ul.icons li .rst-content h1 .headerlink, .rst-content h1 ul.icons li .headerlink, ul.icons li .rst-content h2 .headerlink, .rst-content h2 ul.icons li .headerlink, ul.icons li .rst-content h3 .headerlink, .rst-content h3 ul.icons li .headerlink, ul.icons li .rst-content h4 .headerlink, .rst-content h4 ul.icons li .headerlink, ul.icons li .rst-content h5 .headerlink, .rst-content h5 ul.icons li .headerlink, ul.icons li .rst-content h6 .headerlink, .rst-content h6 ul.icons li .headerlink, ul.icons li .rst-content dl dt .headerlink, .rst-content dl dt ul.icons li .headerlink { width: 0.8em; } ul.icons li .icon-large:before, ul.icons li .icon-large:before { vertical-align: baseline; } .icon-glass:before { content: "\f000"; } .icon-music:before { content: "\f001"; } .icon-search:before { content: "\f002"; } .icon-envelope-alt:before { content: "\f003"; } .icon-heart:before { content: "\f004"; } .icon-star:before { content: "\f005"; } .icon-star-empty:before { content: "\f006"; } .icon-user:before { content: "\f007"; } .icon-film:before { content: "\f008"; } .icon-th-large:before { content: "\f009"; } .icon-th:before { content: "\f00a"; } .icon-th-list:before { content: "\f00b"; } .icon-ok:before { content: "\f00c"; } .icon-remove:before, .wy-tag-input-group .wy-tag .wy-tag-remove:before { content: "\f00d"; } .icon-zoom-in:before { content: "\f00e"; } .icon-zoom-out:before { content: "\f010"; } .icon-power-off:before, .icon-off:before { content: "\f011"; } .icon-signal:before { content: "\f012"; } .icon-gear:before, .icon-cog:before { content: "\f013"; } .icon-trash:before { content: "\f014"; } .icon-home:before { content: "\f015"; } .icon-file-alt:before { content: "\f016"; } .icon-time:before { content: "\f017"; } .icon-road:before { content: "\f018"; } .icon-download-alt:before { content: "\f019"; } .icon-download:before { content: "\f01a"; } .icon-upload:before { content: "\f01b"; } .icon-inbox:before { content: "\f01c"; } .icon-play-circle:before { content: "\f01d"; } .icon-rotate-right:before, .icon-repeat:before { content: "\f01e"; } .icon-refresh:before { content: "\f021"; } .icon-list-alt:before { content: "\f022"; } .icon-lock:before { content: "\f023"; } .icon-flag:before { content: "\f024"; } .icon-headphones:before { content: "\f025"; } .icon-volume-off:before { content: "\f026"; } .icon-volume-down:before { content: "\f027"; } .icon-volume-up:before { content: "\f028"; } .icon-qrcode:before { content: "\f029"; } .icon-barcode:before { content: "\f02a"; } .icon-tag:before { content: "\f02b"; } .icon-tags:before { content: "\f02c"; } .icon-book:before { content: "\f02d"; } .icon-bookmark:before { content: "\f02e"; } .icon-print:before { content: "\f02f"; } .icon-camera:before { content: "\f030"; } .icon-font:before { content: "\f031"; } .icon-bold:before { content: "\f032"; } .icon-italic:before { content: "\f033"; } .icon-text-height:before { content: "\f034"; } .icon-text-width:before { content: "\f035"; } .icon-align-left:before { content: "\f036"; } .icon-align-center:before { content: "\f037"; } .icon-align-right:before { content: "\f038"; } .icon-align-justify:before { content: "\f039"; } .icon-list:before { content: "\f03a"; } .icon-indent-left:before { content: "\f03b"; } .icon-indent-right:before { content: "\f03c"; } .icon-facetime-video:before { content: "\f03d"; } .icon-picture:before { content: "\f03e"; } .icon-pencil:before { content: "\f040"; } .icon-map-marker:before { content: "\f041"; } .icon-adjust:before { content: "\f042"; } .icon-tint:before { content: "\f043"; } .icon-edit:before { content: "\f044"; } .icon-share:before { content: "\f045"; } .icon-check:before { content: "\f046"; } .icon-move:before { content: "\f047"; } .icon-step-backward:before { content: "\f048"; } .icon-fast-backward:before { content: "\f049"; } .icon-backward:before { content: "\f04a"; } .icon-play:before { content: "\f04b"; } .icon-pause:before { content: "\f04c"; } .icon-stop:before { content: "\f04d"; } .icon-forward:before { content: "\f04e"; } .icon-fast-forward:before { content: "\f050"; } .icon-step-forward:before { content: "\f051"; } .icon-eject:before { content: "\f052"; } .icon-chevron-left:before { content: "\f053"; } .icon-chevron-right:before { content: "\f054"; } .icon-plus-sign:before { content: "\f055"; } .icon-minus-sign:before { content: "\f056"; } .icon-remove-sign:before, .wy-inline-validate.wy-inline-validate-danger .wy-input-context:before { content: "\f057"; } .icon-ok-sign:before { content: "\f058"; } .icon-question-sign:before { content: "\f059"; } .icon-info-sign:before { content: "\f05a"; } .icon-screenshot:before { content: "\f05b"; } .icon-remove-circle:before { content: "\f05c"; } .icon-ok-circle:before { content: "\f05d"; } .icon-ban-circle:before { content: "\f05e"; } .icon-arrow-left:before { content: "\f060"; } .icon-arrow-right:before { content: "\f061"; } .icon-arrow-up:before { content: "\f062"; } .icon-arrow-down:before { content: "\f063"; } .icon-mail-forward:before, .icon-share-alt:before { content: "\f064"; } .icon-resize-full:before { content: "\f065"; } .icon-resize-small:before { content: "\f066"; } .icon-plus:before { content: "\f067"; } .icon-minus:before { content: "\f068"; } .icon-asterisk:before { content: "\f069"; } .icon-exclamation-sign:before, .wy-inline-validate.wy-inline-validate-warning .wy-input-context:before, .wy-inline-validate.wy-inline-validate-info .wy-input-context:before, .rst-content .admonition-title:before { content: "\f06a"; } .icon-gift:before { content: "\f06b"; } .icon-leaf:before { content: "\f06c"; } .icon-fire:before { content: "\f06d"; } .icon-eye-open:before { content: "\f06e"; } .icon-eye-close:before { content: "\f070"; } .icon-warning-sign:before { content: "\f071"; } .icon-plane:before { content: "\f072"; } .icon-calendar:before { content: "\f073"; } .icon-random:before { content: "\f074"; } .icon-comment:before { content: "\f075"; } .icon-magnet:before { content: "\f076"; } .icon-chevron-up:before { content: "\f077"; } .icon-chevron-down:before { content: "\f078"; } .icon-retweet:before { content: "\f079"; } .icon-shopping-cart:before { content: "\f07a"; } .icon-folder-close:before { content: "\f07b"; } .icon-folder-open:before { content: "\f07c"; } .icon-resize-vertical:before { content: "\f07d"; } .icon-resize-horizontal:before { content: "\f07e"; } .icon-bar-chart:before { content: "\f080"; } .icon-twitter-sign:before { content: "\f081"; } .icon-facebook-sign:before { content: "\f082"; } .icon-camera-retro:before { content: "\f083"; } .icon-key:before { content: "\f084"; } .icon-gears:before, .icon-cogs:before { content: "\f085"; } .icon-comments:before { content: "\f086"; } .icon-thumbs-up-alt:before { content: "\f087"; } .icon-thumbs-down-alt:before { content: "\f088"; } .icon-star-half:before { content: "\f089"; } .icon-heart-empty:before { content: "\f08a"; } .icon-signout:before { content: "\f08b"; } .icon-linkedin-sign:before { content: "\f08c"; } .icon-pushpin:before { content: "\f08d"; } .icon-external-link:before { content: "\f08e"; } .icon-signin:before { content: "\f090"; } .icon-trophy:before { content: "\f091"; } .icon-github-sign:before { content: "\f092"; } .icon-upload-alt:before { content: "\f093"; } .icon-lemon:before { content: "\f094"; } .icon-phone:before { content: "\f095"; } .icon-unchecked:before, .icon-check-empty:before { content: "\f096"; } .icon-bookmark-empty:before { content: "\f097"; } .icon-phone-sign:before { content: "\f098"; } .icon-twitter:before { content: "\f099"; } .icon-facebook:before { content: "\f09a"; } .icon-github:before { content: "\f09b"; } .icon-unlock:before { content: "\f09c"; } .icon-credit-card:before { content: "\f09d"; } .icon-rss:before { content: "\f09e"; } .icon-hdd:before { content: "\f0a0"; } .icon-bullhorn:before { content: "\f0a1"; } .icon-bell:before { content: "\f0a2"; } .icon-certificate:before { content: "\f0a3"; } .icon-hand-right:before { content: "\f0a4"; } .icon-hand-left:before { content: "\f0a5"; } .icon-hand-up:before { content: "\f0a6"; } .icon-hand-down:before { content: "\f0a7"; } .icon-circle-arrow-left:before { content: "\f0a8"; } .icon-circle-arrow-right:before { content: "\f0a9"; } .icon-circle-arrow-up:before { content: "\f0aa"; } .icon-circle-arrow-down:before { content: "\f0ab"; } .icon-globe:before { content: "\f0ac"; } .icon-wrench:before { content: "\f0ad"; } .icon-tasks:before { content: "\f0ae"; } .icon-filter:before { content: "\f0b0"; } .icon-briefcase:before { content: "\f0b1"; } .icon-fullscreen:before { content: "\f0b2"; } .icon-group:before { content: "\f0c0"; } .icon-link:before { content: "\f0c1"; } .icon-cloud:before { content: "\f0c2"; } .icon-beaker:before { content: "\f0c3"; } .icon-cut:before { content: "\f0c4"; } .icon-copy:before { content: "\f0c5"; } .icon-paperclip:before, .icon-paper-clip:before { content: "\f0c6"; } .icon-save:before { content: "\f0c7"; } .icon-sign-blank:before { content: "\f0c8"; } .icon-reorder:before { content: "\f0c9"; } .icon-list-ul:before { content: "\f0ca"; } .icon-list-ol:before { content: "\f0cb"; } .icon-strikethrough:before { content: "\f0cc"; } .icon-underline:before { content: "\f0cd"; } .icon-table:before { content: "\f0ce"; } .icon-magic:before { content: "\f0d0"; } .icon-truck:before { content: "\f0d1"; } .icon-pinterest:before { content: "\f0d2"; } .icon-pinterest-sign:before { content: "\f0d3"; } .icon-google-plus-sign:before { content: "\f0d4"; } .icon-google-plus:before { content: "\f0d5"; } .icon-money:before { content: "\f0d6"; } .icon-caret-down:before { content: "\f0d7"; } .icon-caret-up:before { content: "\f0d8"; } .icon-caret-left:before { content: "\f0d9"; } .icon-caret-right:before { content: "\f0da"; } .icon-columns:before { content: "\f0db"; } .icon-sort:before { content: "\f0dc"; } .icon-sort-down:before { content: "\f0dd"; } .icon-sort-up:before { content: "\f0de"; } .icon-envelope:before { content: "\f0e0"; } .icon-linkedin:before { content: "\f0e1"; } .icon-rotate-left:before, .icon-undo:before { content: "\f0e2"; } .icon-legal:before { content: "\f0e3"; } .icon-dashboard:before { content: "\f0e4"; } .icon-comment-alt:before { content: "\f0e5"; } .icon-comments-alt:before { content: "\f0e6"; } .icon-bolt:before { content: "\f0e7"; } .icon-sitemap:before { content: "\f0e8"; } .icon-umbrella:before { content: "\f0e9"; } .icon-paste:before { content: "\f0ea"; } .icon-lightbulb:before { content: "\f0eb"; } .icon-exchange:before { content: "\f0ec"; } .icon-cloud-download:before { content: "\f0ed"; } .icon-cloud-upload:before { content: "\f0ee"; } .icon-user-md:before { content: "\f0f0"; } .icon-stethoscope:before { content: "\f0f1"; } .icon-suitcase:before { content: "\f0f2"; } .icon-bell-alt:before { content: "\f0f3"; } .icon-coffee:before { content: "\f0f4"; } .icon-food:before { content: "\f0f5"; } .icon-file-text-alt:before { content: "\f0f6"; } .icon-building:before { content: "\f0f7"; } .icon-hospital:before { content: "\f0f8"; } .icon-ambulance:before { content: "\f0f9"; } .icon-medkit:before { content: "\f0fa"; } .icon-fighter-jet:before { content: "\f0fb"; } .icon-beer:before { content: "\f0fc"; } .icon-h-sign:before { content: "\f0fd"; } .icon-plus-sign-alt:before { content: "\f0fe"; } .icon-double-angle-left:before { content: "\f100"; } .icon-double-angle-right:before { content: "\f101"; } .icon-double-angle-up:before { content: "\f102"; } .icon-double-angle-down:before { content: "\f103"; } .icon-angle-left:before { content: "\f104"; } .icon-angle-right:before { content: "\f105"; } .icon-angle-up:before { content: "\f106"; } .icon-angle-down:before { content: "\f107"; } .icon-desktop:before { content: "\f108"; } .icon-laptop:before { content: "\f109"; } .icon-tablet:before { content: "\f10a"; } .icon-mobile-phone:before { content: "\f10b"; } .icon-circle-blank:before { content: "\f10c"; } .icon-quote-left:before { content: "\f10d"; } .icon-quote-right:before { content: "\f10e"; } .icon-spinner:before { content: "\f110"; } .icon-circle:before { content: "\f111"; } .icon-mail-reply:before, .icon-reply:before { content: "\f112"; } .icon-github-alt:before { content: "\f113"; } .icon-folder-close-alt:before { content: "\f114"; } .icon-folder-open-alt:before { content: "\f115"; } .icon-expand-alt:before { content: "\f116"; } .icon-collapse-alt:before { content: "\f117"; } .icon-smile:before { content: "\f118"; } .icon-frown:before { content: "\f119"; } .icon-meh:before { content: "\f11a"; } .icon-gamepad:before { content: "\f11b"; } .icon-keyboard:before { content: "\f11c"; } .icon-flag-alt:before { content: "\f11d"; } .icon-flag-checkered:before { content: "\f11e"; } .icon-terminal:before { content: "\f120"; } .icon-code:before { content: "\f121"; } .icon-reply-all:before { content: "\f122"; } .icon-mail-reply-all:before { content: "\f122"; } .icon-star-half-full:before, .icon-star-half-empty:before { content: "\f123"; } .icon-location-arrow:before { content: "\f124"; } .icon-crop:before { content: "\f125"; } .icon-code-fork:before { content: "\f126"; } .icon-unlink:before { content: "\f127"; } .icon-question:before { content: "\f128"; } .icon-info:before { content: "\f129"; } .icon-exclamation:before { content: "\f12a"; } .icon-superscript:before { content: "\f12b"; } .icon-subscript:before { content: "\f12c"; } .icon-eraser:before { content: "\f12d"; } .icon-puzzle-piece:before { content: "\f12e"; } .icon-microphone:before { content: "\f130"; } .icon-microphone-off:before { content: "\f131"; } .icon-shield:before { content: "\f132"; } .icon-calendar-empty:before { content: "\f133"; } .icon-fire-extinguisher:before { content: "\f134"; } .icon-rocket:before { content: "\f135"; } .icon-maxcdn:before { content: "\f136"; } .icon-chevron-sign-left:before { content: "\f137"; } .icon-chevron-sign-right:before { content: "\f138"; } .icon-chevron-sign-up:before { content: "\f139"; } .icon-chevron-sign-down:before { content: "\f13a"; } .icon-html5:before { content: "\f13b"; } .icon-css3:before { content: "\f13c"; } .icon-anchor:before { content: "\f13d"; } .icon-unlock-alt:before { content: "\f13e"; } .icon-bullseye:before { content: "\f140"; } .icon-ellipsis-horizontal:before { content: "\f141"; } .icon-ellipsis-vertical:before { content: "\f142"; } .icon-rss-sign:before { content: "\f143"; } .icon-play-sign:before { content: "\f144"; } .icon-ticket:before { content: "\f145"; } .icon-minus-sign-alt:before { content: "\f146"; } .icon-check-minus:before { content: "\f147"; } .icon-level-up:before { content: "\f148"; } .icon-level-down:before { content: "\f149"; } .icon-check-sign:before, .wy-inline-validate.wy-inline-validate-success .wy-input-context:before { content: "\f14a"; } .icon-edit-sign:before { content: "\f14b"; } .icon-external-link-sign:before { content: "\f14c"; } .icon-share-sign:before { content: "\f14d"; } .icon-compass:before { content: "\f14e"; } .icon-collapse:before { content: "\f150"; } .icon-collapse-top:before { content: "\f151"; } .icon-expand:before { content: "\f152"; } .icon-euro:before, .icon-eur:before { content: "\f153"; } .icon-gbp:before { content: "\f154"; } .icon-dollar:before, .icon-usd:before { content: "\f155"; } .icon-rupee:before, .icon-inr:before { content: "\f156"; } .icon-yen:before, .icon-jpy:before { content: "\f157"; } .icon-renminbi:before, .icon-cny:before { content: "\f158"; } .icon-won:before, .icon-krw:before { content: "\f159"; } .icon-bitcoin:before, .icon-btc:before { content: "\f15a"; } .icon-file:before { content: "\f15b"; } .icon-file-text:before { content: "\f15c"; } .icon-sort-by-alphabet:before { content: "\f15d"; } .icon-sort-by-alphabet-alt:before { content: "\f15e"; } .icon-sort-by-attributes:before { content: "\f160"; } .icon-sort-by-attributes-alt:before { content: "\f161"; } .icon-sort-by-order:before { content: "\f162"; } .icon-sort-by-order-alt:before { content: "\f163"; } .icon-thumbs-up:before { content: "\f164"; } .icon-thumbs-down:before { content: "\f165"; } .icon-youtube-sign:before { content: "\f166"; } .icon-youtube:before { content: "\f167"; } .icon-xing:before { content: "\f168"; } .icon-xing-sign:before { content: "\f169"; } .icon-youtube-play:before { content: "\f16a"; } .icon-dropbox:before { content: "\f16b"; } .icon-stackexchange:before { content: "\f16c"; } .icon-instagram:before { content: "\f16d"; } .icon-flickr:before { content: "\f16e"; } .icon-adn:before { content: "\f170"; } .icon-bitbucket:before { content: "\f171"; } .icon-bitbucket-sign:before { content: "\f172"; } .icon-tumblr:before { content: "\f173"; } .icon-tumblr-sign:before { content: "\f174"; } .icon-long-arrow-down:before { content: "\f175"; } .icon-long-arrow-up:before { content: "\f176"; } .icon-long-arrow-left:before { content: "\f177"; } .icon-long-arrow-right:before { content: "\f178"; } .icon-apple:before { content: "\f179"; } .icon-windows:before { content: "\f17a"; } .icon-android:before { content: "\f17b"; } .icon-linux:before { content: "\f17c"; } .icon-dribbble:before { content: "\f17d"; } .icon-skype:before { content: "\f17e"; } .icon-foursquare:before { content: "\f180"; } .icon-trello:before { content: "\f181"; } .icon-female:before { content: "\f182"; } .icon-male:before { content: "\f183"; } .icon-gittip:before { content: "\f184"; } .icon-sun:before { content: "\f185"; } .icon-moon:before { content: "\f186"; } .icon-archive:before { content: "\f187"; } .icon-bug:before { content: "\f188"; } .icon-vk:before { content: "\f189"; } .icon-weibo:before { content: "\f18a"; } .icon-renren:before { content: "\f18b"; } .wy-alert, .rst-content .note, .rst-content .attention, .rst-content .caution, .rst-content .danger, .rst-content .error, .rst-content .hint, .rst-content .important, .rst-content .tip, .rst-content .warning { padding: 24px; line-height: 24px; margin-bottom: 24px; border-left: solid 3px transparent; } .wy-alert strong, .rst-content .note strong, .rst-content .attention strong, .rst-content .caution strong, .rst-content .danger strong, .rst-content .error strong, .rst-content .hint strong, .rst-content .important strong, .rst-content .tip strong, .rst-content .warning strong, .wy-alert a, .rst-content .note a, .rst-content .attention a, .rst-content .caution a, .rst-content .danger a, .rst-content .error a, .rst-content .hint a, .rst-content .important a, .rst-content .tip a, .rst-content .warning a { color: #fff; } .wy-alert.wy-alert-danger, .rst-content .wy-alert-danger.note, .rst-content .wy-alert-danger.attention, .rst-content .wy-alert-danger.caution, .rst-content .danger, .rst-content .error, .rst-content .wy-alert-danger.hint, .rst-content .wy-alert-danger.important, .rst-content .wy-alert-danger.tip, .rst-content .wy-alert-danger.warning { background: #e74c3c; color: #fff; border-color: #d62c1a; } .wy-alert.wy-alert-warning, .rst-content .wy-alert-warning.note, .rst-content .attention, .rst-content .caution, .rst-content .wy-alert-warning.danger, .rst-content .wy-alert-warning.error, .rst-content .wy-alert-warning.hint, .rst-content .wy-alert-warning.important, .rst-content .wy-alert-warning.tip, .rst-content .warning { background: #e67e22; color: #fff; border-color: #bf6516; } .wy-alert.wy-alert-info, .rst-content .note, .rst-content .wy-alert-info.attention, .rst-content .wy-alert-info.caution, .rst-content .wy-alert-info.danger, .rst-content .wy-alert-info.error, .rst-content .hint, .rst-content .important, .rst-content .tip, .rst-content .wy-alert-info.warning { background: #2980b9; color: #fff; border-color: #20638f; } .wy-alert.wy-alert-success, .rst-content .wy-alert-success.note, .rst-content .wy-alert-success.attention, .rst-content .wy-alert-success.caution, .rst-content .wy-alert-success.danger, .rst-content .wy-alert-success.error, .rst-content .wy-alert-success.hint, .rst-content .wy-alert-success.important, .rst-content .wy-alert-success.tip, .rst-content .wy-alert-success.warning { background: #27ae60; color: #fff; border-color: #1e8449; } .wy-alert.wy-alert-neutral, .rst-content .wy-alert-neutral.note, .rst-content .wy-alert-neutral.attention, .rst-content .wy-alert-neutral.caution, .rst-content .wy-alert-neutral.danger, .rst-content .wy-alert-neutral.error, .rst-content .wy-alert-neutral.hint, .rst-content .wy-alert-neutral.important, .rst-content .wy-alert-neutral.tip, .rst-content .wy-alert-neutral.warning { background: #f3f6f6; border-color: #e1e4e5; } .wy-alert.wy-alert-neutral strong, .rst-content .wy-alert-neutral.note strong, .rst-content .wy-alert-neutral.attention strong, .rst-content .wy-alert-neutral.caution strong, .rst-content .wy-alert-neutral.danger strong, .rst-content .wy-alert-neutral.error strong, .rst-content .wy-alert-neutral.hint strong, .rst-content .wy-alert-neutral.important strong, .rst-content .wy-alert-neutral.tip strong, .rst-content .wy-alert-neutral.warning strong { color: #404040; } .wy-alert.wy-alert-neutral a, .rst-content .wy-alert-neutral.note a, .rst-content .wy-alert-neutral.attention a, .rst-content .wy-alert-neutral.caution a, .rst-content .wy-alert-neutral.danger a, .rst-content .wy-alert-neutral.error a, .rst-content .wy-alert-neutral.hint a, .rst-content .wy-alert-neutral.important a, .rst-content .wy-alert-neutral.tip a, .rst-content .wy-alert-neutral.warning a { color: #2980b9; } .wy-tray-container { position: fixed; top: -50px; left: 0; width: 100%; -webkit-transition: top 0.2s ease-in; -moz-transition: top 0.2s ease-in; transition: top 0.2s ease-in; } .wy-tray-container.on { top: 0; } .wy-tray-container li { display: none; width: 100%; background: #343131; padding: 12px 24px; color: #fff; margin-bottom: 6px; text-align: center; box-shadow: 0 5px 5px 0 rgba(0, 0, 0, 0.1), 0px -1px 2px -1px rgba(255, 255, 255, 0.5) inset; } .wy-tray-container li.wy-tray-item-success { background: #27ae60; } .wy-tray-container li.wy-tray-item-info { background: #2980b9; } .wy-tray-container li.wy-tray-item-warning { background: #e67e22; } .wy-tray-container li.wy-tray-item-danger { background: #e74c3c; } .btn { display: inline-block; *display: inline; zoom: 1; line-height: normal; white-space: nowrap; vertical-align: baseline; text-align: center; cursor: pointer; -webkit-user-drag: none; -webkit-user-select: none; -moz-user-select: none; -ms-user-select: none; user-select: none; font-size: 100%; padding: 6px 12px; color: #fff; border: 1px solid rgba(0, 0, 0, 0.1); border-bottom: solid 3px rgba(0, 0, 0, 0.1); background-color: #27ae60; text-decoration: none; font-weight: 500; box-shadow: 0px 1px 2px -1px rgba(255, 255, 255, 0.5) inset; -webkit-transition: all 0.1s linear; -moz-transition: all 0.1s linear; transition: all 0.1s linear; outline-none: false; } .btn-hover { background: #2e8ece; color: #fff; } .btn:hover { background: #2cc36b; color: #fff; } .btn:focus { background: #2cc36b; color: #fff; outline: 0; } .btn:active { border-top: solid 3px rgba(0, 0, 0, 0.1); border-bottom: solid 1px rgba(0, 0, 0, 0.1); box-shadow: 0px 1px 2px -1px rgba(0, 0, 0, 0.5) inset; } .btn[disabled] { background-image: none; filter: progid:DXImageTransform.Microsoft.gradient(enabled = false); filter: alpha(opacity=40); opacity: 0.4; cursor: not-allowed; box-shadow: none; } .btn-disabled { background-image: none; filter: progid:DXImageTransform.Microsoft.gradient(enabled = false); filter: alpha(opacity=40); opacity: 0.4; cursor: not-allowed; box-shadow: none; } .btn-disabled:hover, .btn-disabled:focus, .btn-disabled:active { background-image: none; filter: progid:DXImageTransform.Microsoft.gradient(enabled = false); filter: alpha(opacity=40); opacity: 0.4; cursor: not-allowed; box-shadow: none; } .btn::-moz-focus-inner { padding: 0; border: 0; } .btn-small { font-size: 80%; } .btn-info { background-color: #2980b9 !important; } .btn-info:hover { background-color: #2e8ece !important; } .btn-neutral { background-color: #f3f6f6 !important; color: #404040 !important; } .btn-neutral:hover { background-color: #e5ebeb !important; color: #404040; } .btn-danger { background-color: #e74c3c !important; } .btn-danger:hover { background-color: #ea6153 !important; } .btn-warning { background-color: #e67e22 !important; } .btn-warning:hover { background-color: #e98b39 !important; } .btn-invert { background-color: #343131; } .btn-invert:hover { background-color: #413d3d !important; } .btn-link { background-color: transparent !important; color: #2980b9; border-color: transparent; } .btn-link:hover { background-color: transparent !important; color: #409ad5; border-color: transparent; } .btn-link:active { background-color: transparent !important; border-color: transparent; border-top: solid 1px transparent; border-bottom: solid 3px transparent; } .wy-btn-group .btn, .wy-control .btn { vertical-align: middle; } .wy-btn-group { margin-bottom: 24px; *zoom: 1; } .wy-btn-group:before, .wy-btn-group:after { display: table; content: ""; } .wy-btn-group:after { clear: both; } .wy-dropdown { position: relative; display: inline-block; } .wy-dropdown:hover .wy-dropdown-menu { display: block; } .wy-dropdown .caret:after { font-family: fontawesome-webfont; content: "\f0d7"; font-size: 70%; } .wy-dropdown-menu { position: absolute; top: 100%; left: 0; display: none; float: left; min-width: 100%; background: #fcfcfc; z-index: 100; border: solid 1px #cfd7dd; box-shadow: 0 5px 5px 0 rgba(0, 0, 0, 0.1); padding: 12px; } .wy-dropdown-menu>dd>a { display: block; clear: both; color: #404040; white-space: nowrap; font-size: 90%; padding: 0 12px; } .wy-dropdown-menu>dd>a:hover { background: #2980b9; color: #fff; } .wy-dropdown-menu>dd.divider { border-top: solid 1px #cfd7dd; margin: 6px 0; } .wy-dropdown-menu>dd.search { padding-bottom: 12px; } .wy-dropdown-menu>dd.search input[type="search"] { width: 100%; } .wy-dropdown-menu>dd.call-to-action { background: #e3e3e3; text-transform: uppercase; font-weight: 500; font-size: 80%; } .wy-dropdown-menu>dd.call-to-action:hover { background: #e3e3e3; } .wy-dropdown-menu>dd.call-to-action .btn { color: #fff; } .wy-dropdown.wy-dropdown-bubble .wy-dropdown-menu { background: #fcfcfc; margin-top: 2px; } .wy-dropdown.wy-dropdown-bubble .wy-dropdown-menu a { padding: 6px 12px; } .wy-dropdown.wy-dropdown-bubble .wy-dropdown-menu a:hover { background: #2980b9; color: #fff; } .wy-dropdown.wy-dropdown-left .wy-dropdown-menu { right: 0; text-align: right; } .wy-dropdown-arrow:before { content: " "; border-bottom: 5px solid #f5f5f5; border-left: 5px solid transparent; border-right: 5px solid transparent; position: absolute; display: block; top: -4px; left: 50%; margin-left: -3px; } .wy-dropdown-arrow.wy-dropdown-arrow-left:before { left: 11px; } .wy-form-stacked select { display: block; } .wy-form-aligned input, .wy-form-aligned textarea, .wy-form-aligned select, .wy-form-aligned .wy-help-inline, .wy-form-aligned label { display: inline-block; *display: inline; *zoom: 1; vertical-align: middle; } .wy-form-aligned .wy-control-group>label { display: inline-block; vertical-align: middle; width: 10em; margin: 0.5em 1em 0 0; float: left; } .wy-form-aligned .wy-control { float: left; } .wy-form-aligned .wy-control label { display: block; } .wy-form-aligned .wy-control select { margin-top: 0.5em; } fieldset { border: 0; margin: 0; padding: 0; } legend { display: block; width: 100%; border: 0; padding: 0; white-space: normal; margin-bottom: 24px; font-size: 150%; *margin-left: -7px; } label { display: block; margin: 0 0 0.3125em 0; color: #999; font-size: 90%; } button, input, select, textarea { font-size: 100%; margin: 0; vertical-align: baseline; *vertical-align: middle; } button, input { line-height: normal; } button { -webkit-appearance: button; cursor: pointer; *overflow: visible; } button::-moz-focus-inner, input::-moz-focus-inner { border: 0; padding: 0; } button[disabled] { cursor: default; } input[type="button"], input[type="reset"], input[type="submit"] { -webkit-appearance: button; cursor: pointer; *overflow: visible; } input[type="text"], input[type="password"], input[type="email"], input[type="url"], input[type="date"], input[type="month"], input[type="time"], input[type="datetime"], input[type="datetime-local"], input[type="week"], input[type="number"], input[type="search"], input[type="tel"], input[type="color"] { -webkit-appearance: none; padding: 6px; display: inline-block; border: 1px solid #ccc; font-size: 80%; font-family: "Lato", "proxima-nova", "Helvetica Neue", Arial, sans-serif; box-shadow: inset 0 1px 3px #ddd; border-radius: 0; -webkit-transition: border 0.3s linear; -moz-transition: border 0.3s linear; transition: border 0.3s linear; } input[type="datetime-local"] { padding: 0.34375em 0.625em; } input[disabled] { cursor: default; } input[type="checkbox"], input[type="radio"] { -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; padding: 0; margin-right: 0.3125em; *height: 13px; *width: 13px; } input[type="search"] { -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; } input[type="search"]::-webkit-search-cancel-button, input[type="search"]::-webkit-search-decoration { -webkit-appearance: none; } input[type="text"]:focus, input[type="password"]:focus, input[type="email"]:focus, input[type="url"]:focus, input[type="date"]:focus, input[type="month"]:focus, input[type="time"]:focus, input[type="datetime"]:focus, input[type="datetime-local"]:focus, input[type="week"]:focus, input[type="number"]:focus, input[type="search"]:focus, input[type="tel"]:focus, input[type="color"]:focus { outline: 0; outline: thin dotted \9; border-color: #2980b9; } input.no-focus:focus { border-color: #ccc !important; } input[type="file"]:focus, input[type="radio"]:focus, input[type="checkbox"]:focus { outline: thin dotted #333; outline: 1px auto #129fea; } input[type="text"][disabled], input[type="password"][disabled], input[type="email"][disabled], input[type="url"][disabled], input[type="date"][disabled], input[type="month"][disabled], input[type="time"][disabled], input[type="datetime"][disabled], input[type="datetime-local"][disabled], input[type="week"][disabled], input[type="number"][disabled], input[type="search"][disabled], input[type="tel"][disabled], input[type="color"][disabled] { cursor: not-allowed; background-color: #f3f6f6; color: #cad2d3; } input:focus:invalid, textarea:focus:invalid, select:focus:invalid { color: #e74c3c; border: 1px solid #e74c3c; } input:focus:invalid:focus, textarea:focus:invalid:focus, select:focus:invalid:focus { border-color: #e9322d; } input[type="file"]:focus:invalid:focus, input[type="radio"]:focus:invalid:focus, input[type="checkbox"]:focus:invalid:focus { outline-color: #e9322d; } input.wy-input-large { padding: 12px; font-size: 100%; } textarea { overflow: auto; vertical-align: top; width: 100%; } select, textarea { padding: 0.5em 0.625em; display: inline-block; border: 1px solid #ccc; font-size: 0.8em; box-shadow: inset 0 1px 3px #ddd; -webkit-transition: border 0.3s linear; -moz-transition: border 0.3s linear; transition: border 0.3s linear; } select { border: 1px solid #ccc; background-color: #fff; } select[multiple] { height: auto; } select:focus, textarea:focus { outline: 0; } select[disabled], textarea[disabled], input[readonly], select[readonly], textarea[readonly] { cursor: not-allowed; background-color: #fff; color: #cad2d3; border-color: transparent; } .wy-checkbox, .wy-radio { margin: 0.5em 0; color: #404040 !important; display: block; } .wy-form-message-inline { display: inline-block; *display: inline; *zoom: 1; vertical-align: middle; } .wy-input-prefix, .wy-input-suffix { white-space: nowrap; } .wy-input-prefix .wy-input-context, .wy-input-suffix .wy-input-context { padding: 6px; display: inline-block; font-size: 80%; background-color: #f3f6f6; border: solid 1px #ccc; color: #999; } .wy-input-suffix .wy-input-context { border-left: 0; } .wy-input-prefix .wy-input-context { border-right: 0; } .wy-inline-validate { white-space: nowrap; } .wy-inline-validate .wy-input-context { padding: 0.5em 0.625em; display: inline-block; font-size: 80%; } .wy-inline-validate.wy-inline-validate-success .wy-input-context { color: #27ae60; } .wy-inline-validate.wy-inline-validate-danger .wy-input-context { color: #e74c3c; } .wy-inline-validate.wy-inline-validate-warning .wy-input-context { color: #e67e22; } .wy-inline-validate.wy-inline-validate-info .wy-input-context { color: #2980b9; } .wy-control-group { margin-bottom: 24px; *zoom: 1; } .wy-control-group:before, .wy-control-group:after { display: table; content: ""; } .wy-control-group:after { clear: both; } .wy-control-group.wy-control-group-error .wy-form-message, .wy-control-group.wy-control-group-error label { color: #e74c3c; } .wy-control-group.wy-control-group-error input[type="text"], .wy-control-group.wy-control-group-error input[type="password"], .wy-control-group.wy-control-group-error input[type="email"], .wy-control-group.wy-control-group-error input[type="url"], .wy-control-group.wy-control-group-error input[type="date"], .wy-control-group.wy-control-group-error input[type="month"], .wy-control-group.wy-control-group-error input[type="time"], .wy-control-group.wy-control-group-error input[type="datetime"], .wy-control-group.wy-control-group-error input[type="datetime-local"], .wy-control-group.wy-control-group-error input[type="week"], .wy-control-group.wy-control-group-error input[type="number"], .wy-control-group.wy-control-group-error input[type="search"], .wy-control-group.wy-control-group-error input[type="tel"], .wy-control-group.wy-control-group-error input[type="color"] { border: solid 2px #e74c3c; } .wy-control-group.wy-control-group-error textarea { border: solid 2px #e74c3c; } .wy-control-group.fluid-input input[type="text"], .wy-control-group.fluid-input input[type="password"], .wy-control-group.fluid-input input[type="email"], .wy-control-group.fluid-input input[type="url"], .wy-control-group.fluid-input input[type="date"], .wy-control-group.fluid-input input[type="month"], .wy-control-group.fluid-input input[type="time"], .wy-control-group.fluid-input input[type="datetime"], .wy-control-group.fluid-input input[type="datetime-local"], .wy-control-group.fluid-input input[type="week"], .wy-control-group.fluid-input input[type="number"], .wy-control-group.fluid-input input[type="search"], .wy-control-group.fluid-input input[type="tel"], .wy-control-group.fluid-input input[type="color"] { width: 100%; } .wy-form-message-inline { display: inline-block; padding-left: 0.3em; color: #666; vertical-align: middle; font-size: 90%; } .wy-form-message { display: block; color: #ccc; font-size: 70%; margin-top: 0.3125em; font-style: italic; } .wy-tag-input-group { padding: 4px 4px 0px 4px; display: inline-block; border: 1px solid #ccc; font-size: 80%; font-family: "Lato", "proxima-nova", "Helvetica Neue", Arial, sans-serif; box-shadow: inset 0 1px 3px #ddd; -webkit-transition: border 0.3s linear; -moz-transition: border 0.3s linear; transition: border 0.3s linear; } .wy-tag-input-group .wy-tag { display: inline-block; background-color: rgba(0, 0, 0, 0.1); padding: 0.5em 0.625em; border-radius: 2px; position: relative; margin-bottom: 4px; } .wy-tag-input-group .wy-tag .wy-tag-remove { color: #ccc; margin-left: 5px; } .wy-tag-input-group .wy-tag .wy-tag-remove:hover { color: #e74c3c; } .wy-tag-input-group label { margin-left: 5px; display: inline-block; margin-bottom: 0; } .wy-tag-input-group input { border: none; font-size: 100%; margin-bottom: 4px; box-shadow: none; } .wy-form-upload { border: solid 1px #ccc; border-bottom: solid 3px #ccc; background-color: #fff; padding: 24px; display: inline-block; text-align: center; cursor: pointer; color: #404040; -webkit-transition: border-color 0.1s ease-in; -moz-transition: border-color 0.1s ease-in; transition: border-color 0.1s ease-in; *zoom: 1; } .wy-form-upload:before, .wy-form-upload:after { display: table; content: ""; } .wy-form-upload:after { clear: both; } @media screen and (max-width: 480px) { .wy-form-upload { width: 100%; } } .wy-form-upload .image-drop { display: none; } .wy-form-upload .image-desktop { display: none; } .wy-form-upload .image-loading { display: none; } .wy-form-upload .wy-form-upload-icon { display: block; font-size: 32px; color: #b3b3b3; } .wy-form-upload .image-drop .wy-form-upload-icon { color: #27ae60; } .wy-form-upload p { font-size: 90%; } .wy-form-upload .wy-form-upload-image { float: left; margin-right: 24px; } @media screen and (max-width: 480px) { .wy-form-upload .wy-form-upload-image { width: 100%; margin-bottom: 24px; } } .wy-form-upload img { max-width: 125px; max-height: 125px; opacity: 0.9; -webkit-transition: opacity 0.1s ease-in; -moz-transition: opacity 0.1s ease-in; transition: opacity 0.1s ease-in; } .wy-form-upload .wy-form-upload-content { float: left; } @media screen and (max-width: 480px) { .wy-form-upload .wy-form-upload-content { width: 100%; } } .wy-form-upload:hover { border-color: #b3b3b3; color: #404040; } .wy-form-upload:hover .image-desktop { display: block; } .wy-form-upload:hover .image-drag { display: none; } .wy-form-upload:hover img { opacity: 1; } .wy-form-upload:active { border-top: solid 3px #ccc; border-bottom: solid 1px #ccc; } .wy-form-upload.wy-form-upload-big { width: 100%; text-align: center; padding: 72px; } .wy-form-upload.wy-form-upload-big .wy-form-upload-content { float: none; } .wy-form-upload.wy-form-upload-file p { margin-bottom: 0; } .wy-form-upload.wy-form-upload-file .wy-form-upload-icon { display: inline-block; font-size: inherit; } .wy-form-upload.wy-form-upload-drop { background-color: #ddf7e8; } .wy-form-upload.wy-form-upload-drop .image-drop { display: block; } .wy-form-upload.wy-form-upload-drop .image-desktop { display: none; } .wy-form-upload.wy-form-upload-drop .image-drag { display: none; } .wy-form-upload.wy-form-upload-loading .image-drag { display: none; } .wy-form-upload.wy-form-upload-loading .image-desktop { display: none; } .wy-form-upload.wy-form-upload-loading .image-loading { display: block; } .wy-form-upload.wy-form-upload-loading .wy-input-prefix { display: none; } .wy-form-upload.wy-form-upload-loading p { margin-bottom: 0; } .rotate-90 { -webkit-transform: rotate(90deg); -moz-transform: rotate(90deg); -ms-transform: rotate(90deg); -o-transform: rotate(90deg); transform: rotate(90deg); } .rotate-180 { -webkit-transform: rotate(180deg); -moz-transform: rotate(180deg); -ms-transform: rotate(180deg); -o-transform: rotate(180deg); transform: rotate(180deg); } .rotate-270 { -webkit-transform: rotate(270deg); -moz-transform: rotate(270deg); -ms-transform: rotate(270deg); -o-transform: rotate(270deg); transform: rotate(270deg); } .mirror { -webkit-transform: scaleX(-1); -moz-transform: scaleX(-1); -ms-transform: scaleX(-1); -o-transform: scaleX(-1); transform: scaleX(-1); } .mirror.rotate-90 { -webkit-transform: scaleX(-1) rotate(90deg); -moz-transform: scaleX(-1) rotate(90deg); -ms-transform: scaleX(-1) rotate(90deg); -o-transform: scaleX(-1) rotate(90deg); transform: scaleX(-1) rotate(90deg); } .mirror.rotate-180 { -webkit-transform: scaleX(-1) rotate(180deg); -moz-transform: scaleX(-1) rotate(180deg); -ms-transform: scaleX(-1) rotate(180deg); -o-transform: scaleX(-1) rotate(180deg); transform: scaleX(-1) rotate(180deg); } .mirror.rotate-270 { -webkit-transform: scaleX(-1) rotate(270deg); -moz-transform: scaleX(-1) rotate(270deg); -ms-transform: scaleX(-1) rotate(270deg); -o-transform: scaleX(-1) rotate(270deg); transform: scaleX(-1) rotate(270deg); } .wy-form-gallery-manage { margin-left: -12px; margin-right: -12px; } .wy-form-gallery-manage li { float: left; padding: 12px; width: 20%; cursor: pointer; } @media screen and (max-width: 768px) { .wy-form-gallery-manage li { width: 25%; } } @media screen and (max-width: 480px) { .wy-form-gallery-manage li { width: 50%; } } .wy-form-gallery-manage li:active { cursor: move; } .wy-form-gallery-manage li>a { padding: 12px; background-color: #fff; border: solid 1px #e1e4e5; border-bottom: solid 3px #e1e4e5; display: inline-block; -webkit-transition: all 0.1s ease-in; -moz-transition: all 0.1s ease-in; transition: all 0.1s ease-in; } .wy-form-gallery-manage li>a:active { border: solid 1px #ccc; border-top: solid 3px #ccc; } .wy-form-gallery-manage img { width: 100%; -webkit-transition: all 0.05s ease-in; -moz-transition: all 0.05s ease-in; transition: all 0.05s ease-in; } li.wy-form-gallery-edit { position: relative; color: #fff; padding: 24px; width: 100%; display: block; background-color: #343131; border-radius: 4px; } li.wy-form-gallery-edit .arrow { position: absolute; display: block; top: -50px; left: 50%; margin-left: -25px; z-index: 500; height: 0; width: 0; border-color: transparent; border-style: solid; border-width: 25px; border-bottom-color: #343131; } @media only screen and (max-width: 480px) { .wy-form button[type="submit"] { margin: 0.7em 0 0; } .wy-form input[type="text"], .wy-form input[type="password"], .wy-form input[type="email"], .wy-form input[type="url"], .wy-form input[type="date"], .wy-form input[type="month"], .wy-form input[type="time"], .wy-form input[type="datetime"], .wy-form input[type="datetime-local"], .wy-form input[type="week"], .wy-form input[type="number"], .wy-form input[type="search"], .wy-form input[type="tel"], .wy-form input[type="color"] { margin-bottom: 0.3em; display: block; } .wy-form label { margin-bottom: 0.3em; display: block; } .wy-form input[type="password"], .wy-form input[type="email"], .wy-form input[type="url"], .wy-form input[type="date"], .wy-form input[type="month"], .wy-form input[type="time"], .wy-form input[type="datetime"], .wy-form input[type="datetime-local"], .wy-form input[type="week"], .wy-form input[type="number"], .wy-form input[type="search"], .wy-form input[type="tel"], .wy-form input[type="color"] { margin-bottom: 0; } .wy-form-aligned .wy-control-group label { margin-bottom: 0.3em; text-align: left; display: block; width: 100%; } .wy-form-aligned .wy-controls { margin: 1.5em 0 0 0; } .wy-form .wy-help-inline, .wy-form-message-inline, .wy-form-message { display: block; font-size: 80%; padding: 0.2em 0 0.8em; } } @media screen and (max-width: 768px) { .tablet-hide { display: none; } } @media screen and (max-width: 480px) { .mobile-hide { display: none; } } .float-left { float: left; } .float-right { float: right; } .full-width { width: 100%; } .wy-grid-one-col { *zoom: 1; max-width: 68em; margin-left: auto; margin-right: auto; max-width: 1066px; margin-top: 1.618em; } .wy-grid-one-col:before, .wy-grid-one-col:after { display: table; content: ""; } .wy-grid-one-col:after { clear: both; } .wy-grid-one-col section { display: block; float: left; margin-right: 2.35765%; width: 100%; background: #fff; padding: 1.618em; margin-right: 0; } .wy-grid-one-col section:last-child { margin-right: 0; } .wy-grid-index-card { *zoom: 1; max-width: 68em; margin-left: auto; margin-right: auto; max-width: 460px; margin-top: 1.618em; background: #fff; padding: 1.618em; } .wy-grid-index-card:before, .wy-grid-index-card:after { display: table; content: ""; } .wy-grid-index-card:after { clear: both; } .wy-grid-index-card header, .wy-grid-index-card section, .wy-grid-index-card aside { display: block; float: left; margin-right: 2.35765%; width: 100%; } .wy-grid-index-card header:last-child, .wy-grid-index-card section:last-child, .wy-grid-index-card aside:last-child { margin-right: 0; } .wy-grid-index-card.twocol { max-width: 768px; } .wy-grid-index-card.twocol section { display: block; float: left; margin-right: 2.35765%; width: 48.82117%; } .wy-grid-index-card.twocol section:last-child { margin-right: 0; } .wy-grid-index-card.twocol aside { display: block; float: left; margin-right: 2.35765%; width: 48.82117%; } .wy-grid-index-card.twocol aside:last-child { margin-right: 0; } .wy-grid-search-filter { *zoom: 1; max-width: 68em; margin-left: auto; margin-right: auto; margin-bottom: 24px; } .wy-grid-search-filter:before, .wy-grid-search-filter:after { display: table; content: ""; } .wy-grid-search-filter:after { clear: both; } .wy-grid-search-filter .wy-grid-search-filter-input { display: block; float: left; margin-right: 2.35765%; width: 74.41059%; } .wy-grid-search-filter .wy-grid-search-filter-input:last-child { margin-right: 0; } .wy-grid-search-filter .wy-grid-search-filter-btn { display: block; float: left; margin-right: 2.35765%; width: 23.23176%; } .wy-grid-search-filter .wy-grid-search-filter-btn:last-child { margin-right: 0; } .wy-table, .rst-content table.docutils, .rst-content table.field-list { border-collapse: collapse; border-spacing: 0; empty-cells: show; margin-bottom: 24px; } .wy-table caption, .rst-content table.docutils caption, .rst-content table.field-list caption { color: #000; font: italic 85%/1 arial, sans-serif; padding: 1em 0; text-align: center; } .wy-table td, .rst-content table.docutils td, .rst-content table.field-list td, .wy-table th, .rst-content table.docutils th, .rst-content table.field-list th { font-size: 90%; margin: 0; overflow: visible; padding: 8px 16px; } .wy-table td:first-child, .rst-content table.docutils td:first-child, .rst-content table.field-list td:first-child, .wy-table th:first-child, .rst-content table.docutils th:first-child, .rst-content table.field-list th:first-child { border-left-width: 0; } .wy-table thead, .rst-content table.docutils thead, .rst-content table.field-list thead { color: #000; text-align: left; vertical-align: bottom; white-space: nowrap; } .wy-table thead th, .rst-content table.docutils thead th, .rst-content table.field-list thead th { font-weight: bold; border-bottom: solid 2px #e1e4e5; } .wy-table td, .rst-content table.docutils td, .rst-content table.field-list td { background-color: transparent; vertical-align: middle; } .wy-table td p, .rst-content table.docutils td p, .rst-content table.field-list td p { line-height: 18px; margin-bottom: 0; } .wy-table .wy-table-cell-min, .rst-content table.docutils .wy-table-cell-min, .rst-content table.field-list .wy-table-cell-min { width: 1%; padding-right: 0; } .wy-table .wy-table-cell-min input[type=checkbox], .rst-content table.docutils .wy-table-cell-min input[type=checkbox], .rst-content table.field-list .wy-table-cell-min input[type=checkbox], .wy-table .wy-table-cell-min input[type=checkbox], .rst-content table.docutils .wy-table-cell-min input[type=checkbox], .rst-content table.field-list .wy-table-cell-min input[type=checkbox] { margin: 0; } .wy-table-secondary { color: gray; font-size: 90%; } .wy-table-tertiary { color: gray; font-size: 80%; } .wy-table-odd td, .wy-table-striped tr:nth-child(2n-1) td, .rst-content table.docutils:not(.field-list) tr:nth-child(2n-1) td { background-color: #f3f6f6; } .wy-table-backed { background-color: #f3f6f6; } .wy-table-bordered-all, .rst-content table.docutils { border: 1px solid #e1e4e5; } .wy-table-bordered-all td, .rst-content table.docutils td { border-bottom: 1px solid #e1e4e5; border-left: 1px solid #e1e4e5; } .wy-table-bordered-all tbody>tr:last-child td, .rst-content table.docutils tbody>tr:last-child td { border-bottom-width: 0; } .wy-table-bordered { border: 1px solid #e1e4e5; } .wy-table-bordered-rows td { border-bottom: 1px solid #e1e4e5; } .wy-table-bordered-rows tbody>tr:last-child td { border-bottom-width: 0; } .wy-table-horizontal tbody>tr:last-child td { border-bottom-width: 0; } .wy-table-horizontal td, .wy-table-horizontal th { border-width: 0 0 1px 0; border-bottom: 1px solid #e1e4e5; } .wy-table-horizontal tbody>tr:last-child td { border-bottom-width: 0; } .wy-table-responsive { margin-bottom: 24px; max-width: 100%; overflow: auto; } .wy-table-responsive table { margin-bottom: 0 !important; } .wy-table-responsive table td, .wy-table-responsive table th { white-space: nowrap; } html { height: 100%; overflow-x: hidden; } body { font-family: "Lato", "proxima-nova", "Helvetica Neue", Arial, sans-serif; font-weight: normal; color: #404040; min-height: 100%; overflow-x: hidden; background: #edf0f2; } a { color: #2980b9; text-decoration: none; } a:hover { color: #3091d1; } .link-danger { color: #e74c3c; } .link-danger:hover { color: #d62c1a; } .text-left { text-align: left; } .text-center { text-align: center; } .text-right { text-align: right; } h1, h2, h3, h4, h5, h6, legend { margin-top: 0; font-weight: 700; font-family: "Roboto Slab", "ff-tisa-web-pro", "Georgia", Arial, sans-serif; } p { line-height: 24px; margin: 0; font-size: 16px; margin-bottom: 24px; } h1 { font-size: 175%; } h2 { font-size: 150%; } h3 { font-size: 125%; } h4 { font-size: 115%; } h5 { font-size: 110%; } h6 { font-size: 100%; } small { font-size: 80%; } code, .rst-content tt { white-space: nowrap; max-width: 100%; background: #fff; border: solid 1px #e1e4e5; font-size: 75%; padding: 0 5px; font-family: "Incosolata", "Consolata", "Monaco", monospace; color: #e74c3c; overflow-x: auto; } code.code-large, .rst-content tt.code-large { font-size: 90%; } .full-width { width: 100%; } .wy-plain-list-disc, .rst-content .section ul, .rst-content .toctree-wrapper ul { list-style: disc; line-height: 24px; margin-bottom: 24px; } .wy-plain-list-disc li, .rst-content .section ul li, .rst-content .toctree-wrapper ul li { list-style: disc; margin-left: 24px; } .wy-plain-list-disc li ul, .rst-content .section ul li ul, .rst-content .toctree-wrapper ul li ul { margin-bottom: 0; } .wy-plain-list-disc li li, .rst-content .section ul li li, .rst-content .toctree-wrapper ul li li { list-style: circle; } .wy-plain-list-disc li li li, .rst-content .section ul li li li, .rst-content .toctree-wrapper ul li li li { list-style: square; } .wy-plain-list-decimal, .rst-content .section ol, .rst-content ol.arabic { list-style: decimal; line-height: 24px; margin-bottom: 24px; } .wy-plain-list-decimal li, .rst-content .section ol li, .rst-content ol.arabic li { list-style: decimal; margin-left: 24px; } .wy-type-large { font-size: 120%; } .wy-type-normal { font-size: 100%; } .wy-type-small { font-size: 100%; } .wy-type-strike { text-decoration: line-through; } .wy-text-warning { color: #e67e22 !important; } a.wy-text-warning:hover { color: #eb9950 !important; } .wy-text-info { color: #2980b9 !important; } a.wy-text-info:hover { color: #409ad5 !important; } .wy-text-success { color: #27ae60 !important; } a.wy-text-success:hover { color: #36d278 !important; } .wy-text-danger { color: #e74c3c !important; } a.wy-text-danger:hover { color: #ed7669 !important; } .wy-text-neutral { color: #404040 !important; } a.wy-text-neutral:hover { color: #595959 !important; } .codeblock-example { border: 1px solid #e1e4e5; border-bottom: none; padding: 24px; padding-top: 48px; font-weight: 500; background: #fff; position: relative; } .codeblock-example:after { content: "Example"; position: absolute; top: 0px; left: 0px; background: #9b59b6; color: #fff; padding: 6px 12px; } .codeblock-example.prettyprint-example-only { border: 1px solid #e1e4e5; margin-bottom: 24px; } .codeblock, div[class^='highlight'] { border: 1px solid #e1e4e5; padding: 0px; overflow-x: auto; background: #fff; margin: 1px 0 24px 0; } .codeblock div[class^='highlight'], div[class^='highlight'] div[class^='highlight'] { border: none; background: none; margin: 0; } .linenodiv pre { border-right: solid 1px #e6e9ea; margin: 0; padding: 12px 12px; font-family: "Incosolata", "Consolata", "Monaco", monospace; font-size: 12px; line-height: 1.5; color: #d9d9d9; } div[class^='highlight'] pre { white-space: pre; margin: 0; padding: 12px 12px; font-family: "Incosolata", "Consolata", "Monaco", monospace; font-size: 12px; line-height: 1.5; display: block; overflow: auto; color: #404040; } pre.literal-block { @extends .codeblock; } @media print { .codeblock, div[class^='highlight'], div[class^='highlight'] pre { white-space: pre-wrap; } } .hll { background-color: #f8f8f8; border: 1px solid #ccc; padding: 1.5px 5px; } .c { color: #998; font-style: italic; } .err { color: #a61717; background-color: #e3d2d2; } .k { font-weight: bold; } .o { font-weight: bold; } .cm { color: #998; font-style: italic; } .cp { color: #999; font-weight: bold; } .c1 { color: #998; font-style: italic; } .cs { color: #999; font-weight: bold; font-style: italic; } .gd { color: #000; background-color: #fdd; } .gd .x { color: #000; background-color: #faa; } .ge { font-style: italic; } .gr { color: #a00; } .gh { color: #999; } .gi { color: #000; background-color: #dfd; } .gi .x { color: #000; background-color: #afa; } .go { color: #888; } .gp { color: #555; } .gs { font-weight: bold; } .gu { color: purple; font-weight: bold; } .gt { color: #a00; } .kc { font-weight: bold; } .kd { font-weight: bold; } .kn { font-weight: bold; } .kp { font-weight: bold; } .kr { font-weight: bold; } .kt { color: #458; font-weight: bold; } .m { color: #099; } .s { color: #d14; } .n { color: #333; } .na { color: teal; } .nb { color: #0086b3; } .nc { color: #458; font-weight: bold; } .no { color: teal; } .ni { color: purple; } .ne { color: #900; font-weight: bold; } .nf { color: #900; font-weight: bold; } .nn { color: #555; } .nt { color: navy; } .nv { color: teal; } .ow { font-weight: bold; } .w { color: #bbb; } .mf { color: #099; } .mh { color: #099; } .mi { color: #099; } .mo { color: #099; } .sb { color: #d14; } .sc { color: #d14; } .sd { color: #d14; } .s2 { color: #d14; } .se { color: #d14; } .sh { color: #d14; } .si { color: #d14; } .sx { color: #d14; } .sr { color: #009926; } .s1 { color: #d14; } .ss { color: #990073; } .bp { color: #999; } .vc { color: teal; } .vg { color: teal; } .vi { color: teal; } .il { color: #099; } .gc { color: #999; background-color: #eaf2f5; } .wy-breadcrumbs li { display: inline-block; } .wy-breadcrumbs li.wy-breadcrumbs-aside { float: right; } .wy-breadcrumbs li a { display: inline-block; padding: 5px; } .wy-breadcrumbs li a:first-child { padding-left: 0; } .wy-breadcrumbs-extra { margin-bottom: 0; color: #b3b3b3; font-size: 80%; display: inline-block; } @media screen and (max-width: 480px) { .wy-breadcrumbs-extra { display: none; } .wy-breadcrumbs li.wy-breadcrumbs-aside { display: none; } } @media print { .wy-breadcrumbs li.wy-breadcrumbs-aside { display: none; } } .wy-affix { position: fixed; top: 1.618em; } .wy-menu a:hover { text-decoration: none; } .wy-menu-horiz { *zoom: 1; } .wy-menu-horiz:before, .wy-menu-horiz:after { display: table; content: ""; } .wy-menu-horiz:after { clear: both; } .wy-menu-horiz ul, .wy-menu-horiz li { display: inline-block; } .wy-menu-horiz li:hover { background: rgba(255, 255, 255, 0.1); } .wy-menu-horiz li.divide-left { border-left: solid 1px #404040; } .wy-menu-horiz li.divide-right { border-right: solid 1px #404040; } .wy-menu-horiz a { height: 32px; display: inline-block; line-height: 32px; padding: 0 16px; } .wy-menu-vertical header { height: 32px; display: inline-block; line-height: 32px; padding: 0 1.618em; display: block; font-weight: bold; text-transform: uppercase; font-size: 80%; color: #2980b9; white-space: nowrap; } .wy-menu-vertical ul { margin-bottom: 0; } .wy-menu-vertical li.divide-top { border-top: solid 1px #404040; } .wy-menu-vertical li.divide-bottom { border-bottom: solid 1px #404040; } .wy-menu-vertical li.current { background: #e3e3e3; } .wy-menu-vertical li.current a { color: gray; border-right: solid 1px #c9c9c9; padding: 0.4045em 2.427em; } .wy-menu-vertical li.current a:hover { background: #d6d6d6; } .wy-menu-vertical li.on a, .wy-menu-vertical li.current>a { color: #404040; padding: 0.4045em 1.618em; font-weight: bold; position: relative; background: #fcfcfc; border: none; border-bottom: solid 1px #c9c9c9; border-top: solid 1px #c9c9c9; padding-left: 1.618em -4px; } .wy-menu-vertical li.on a:hover, .wy-menu-vertical li.current>a:hover { background: #fcfcfc; } .wy-menu-vertical li.tocktree-l2.current>a { background: #c9c9c9; } .wy-menu-vertical li.current ul { display: block; } .wy-menu-vertical li ul { margin-bottom: 0; display: none; } .wy-menu-vertical li ul li a { margin-bottom: 0; color: #b3b3b3; font-weight: normal; } .wy-menu-vertical a { display: inline-block; line-height: 18px; padding: 0.4045em 1.618em; display: block; position: relative; font-size: 90%; color: #b3b3b3; } .wy-menu-vertical a:hover { background-color: #4e4a4a; cursor: pointer; } .wy-menu-vertical a:active { background-color: #2980b9; cursor: pointer; color: #fff; } .wy-side-nav-search { z-index: 200; background-color: #2980b9; text-align: center; padding: 0.809em; display: block; color: #fcfcfc; margin-bottom: 0.809em; } .wy-side-nav-search input[type=text] { width: 100%; border-radius: 50px; padding: 6px 12px; border-color: #2472a4; } .wy-side-nav-search img { display: block; margin: auto auto 0.809em auto; height: 214px; width: 26px; background-color: #2980b9; padding: 5px; /* border-radius: 100%; */ } .wy-side-nav-search>a, .wy-side-nav-search .wy-dropdown>a { color: #fcfcfc; font-size: 100%; font-weight: bold; display: inline-block; padding: 4px 6px; margin-bottom: 0.809em; } .wy-side-nav-search>a:hover, .wy-side-nav-search .wy-dropdown>a:hover { background: rgba(255, 255, 255, 0.1); } .wy-nav .wy-menu-vertical header { color: #2980b9; } .wy-nav .wy-menu-vertical a { color: #b3b3b3; } .wy-nav .wy-menu-vertical a:hover { background-color: #2980b9; color: #fff; } [data-menu-wrap] { -webkit-transition: all 0.2s ease-in; -moz-transition: all 0.2s ease-in; transition: all 0.2s ease-in; position: absolute; opacity: 1; width: 100%; opacity: 0; } [data-menu-wrap].move-center { left: 0; right: auto; opacity: 1; } [data-menu-wrap].move-left { right: auto; left: -100%; opacity: 0; } [data-menu-wrap].move-right { right: -100%; left: auto; opacity: 0; } .wy-body-for-nav { background: left repeat-y #fff; background-image: url(data:image/png; base64, iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAIAAACQd1PeAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAyRpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuMy1jMDExIDY2LjE0NTY2MSwgMjAxMi8wMi8wNi0xNDo1NjoyNyAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvIiB4bWxuczp4bXBNTT0iaHR0cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL21tLyIgeG1sbnM6c3RSZWY9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9zVHlwZS9SZXNvdXJjZVJlZiMiIHhtcDpDcmVhdG9yVG9vbD0iQWRvYmUgUGhvdG9zaG9wIENTNiAoTWFjaW50b3NoKSIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDoxOERBMTRGRDBFMUUxMUUzODUwMkJCOThDMEVFNURFMCIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDoxOERBMTRGRTBFMUUxMUUzODUwMkJCOThDMEVFNURFMCI+IDx4bXBNTTpEZXJpdmVkRnJvbSBzdFJlZjppbnN0YW5jZUlEPSJ4bXAuaWlkOjE4REExNEZCMEUxRTExRTM4NTAyQkI5OEMwRUU1REUwIiBzdFJlZjpkb2N1bWVudElEPSJ4bXAuZGlkOjE4REExNEZDMEUxRTExRTM4NTAyQkI5OEMwRUU1REUwIi8+IDwvcmRmOkRlc2NyaXB0aW9uPiA8L3JkZjpSREY+IDwveDp4bXBtZXRhPiA8P3hwYWNrZXQgZW5kPSJyIj8+EwrlwAAAAA5JREFUeNpiMDU0BAgwAAE2AJgB9BnaAAAAAElFTkSuQmCC); background-size: 300px 1px; } .wy-grid-for-nav { position: absolute; width: 100%; height: 100%; } .wy-nav-side { position: absolute; top: 0; left: 0; width: 300px; overflow: hidden; min-height: 100%; background: #343131; z-index: 200; } .wy-nav-top { display: none; background: #2980b9; color: #fff; padding: 0.4045em 0.809em; position: relative; line-height: 50px; text-align: center; font-size: 100%; *zoom: 1; } .wy-nav-top:before, .wy-nav-top:after { display: table; content: ""; } .wy-nav-top:after { clear: both; } .wy-nav-top a { color: #fff; font-weight: bold; } .wy-nav-top img { margin-right: 12px; height: 45px; width: 45px; background-color: #2980b9; padding: 5px; border-radius: 100%; } .wy-nav-top i { font-size: 30px; float: left; cursor: pointer; } .wy-nav-content-wrap { margin-left: 300px; background: #fff; min-height: 100%; } .wy-nav-content { padding: 1.618em 3.236em; height: 100%; max-width: 1140px; margin: auto; } .wy-body-mask { position: fixed; width: 100%; height: 100%; background: rgba(0, 0, 0, 0.2); display: none; z-index: 499; } .wy-body-mask.on { display: block; } footer { color: #999; } footer p { margin-bottom: 12px; } .rst-footer-buttons { *zoom: 1; } .rst-footer-buttons:before, .rst-footer-buttons:after { display: table; content: ""; } .rst-footer-buttons:after { clear: both; } #search-results .search li { margin-bottom: 24px; border-bottom: solid 1px #e1e4e5; padding-bottom: 24px; } #search-results .search li:first-child { border-top: solid 1px #e1e4e5; padding-top: 24px; } #search-results .search li a { font-size: 120%; margin-bottom: 12px; display: inline-block; } #search-results .context { color: gray; font-size: 90%; } @media screen and (max-width: 768px) { .wy-body-for-nav { background: #fff; } .wy-nav-top { display: block; } .wy-nav-side { left: -300px; } .wy-nav-side.shift { width: 85%; left: 0; } .wy-nav-content-wrap { margin-left: 0; } .wy-nav-content-wrap .wy-nav-content { padding: 1.618em; } .wy-nav-content-wrap.shift { position: fixed; min-width: 100%; left: 85%; top: 0; height: 100%; overflow: hidden; } } @media screen and (min-width: 1400px) { .wy-nav-content-wrap { background: #fff; } .wy-nav-content { margin: 0; background: #fff; } } @media print { .wy-nav-side { display: none; } .wy-nav-content-wrap { margin-left: 0; } } .rst-versions { position: fixed; bottom: 0; left: 0; width: 300px; color: #fcfcfc; background: #1f1d1d; border-top: solid 10px #343131; font-family: "Lato", "proxima-nova", "Helvetica Neue", Arial, sans-serif; z-index: 400; } .rst-versions a { color: #2980b9; text-decoration: none; } .rst-versions .rst-badge-small { display: none; } .rst-versions .rst-current-version { padding: 12px; background-color: #272525; display: block; text-align: right; font-size: 90%; cursor: pointer; color: #27ae60; *zoom: 1; } .rst-versions .rst-current-version:before, .rst-versions .rst-current-version:after { display: table; content: ""; } .rst-versions .rst-current-version:after { clear: both; } .rst-versions .rst-current-version .icon, .rst-versions .rst-current-version .wy-inline-validate.wy-inline-validate-success .wy-input-context, .wy-inline-validate.wy-inline-validate-success .rst-versions .rst-current-version .wy-input-context, .rst-versions .rst-current-version .wy-inline-validate.wy-inline-validate-danger .wy-input-context, .wy-inline-validate.wy-inline-validate-danger .rst-versions .rst-current-version .wy-input-context, .rst-versions .rst-current-version .wy-inline-validate.wy-inline-validate-warning .wy-input-context, .wy-inline-validate.wy-inline-validate-warning .rst-versions .rst-current-version .wy-input-context, .rst-versions .rst-current-version .wy-inline-validate.wy-inline-validate-info .wy-input-context, .wy-inline-validate.wy-inline-validate-info .rst-versions .rst-current-version .wy-input-context, .rst-versions .rst-current-version .wy-tag-input-group .wy-tag .wy-tag-remove, .wy-tag-input-group .wy-tag .rst-versions .rst-current-version .wy-tag-remove, .rst-versions .rst-current-version .rst-content .admonition-title, .rst-content .rst-versions .rst-current-version .admonition-title, .rst-versions .rst-current-version .rst-content h1 .headerlink, .rst-content h1 .rst-versions .rst-current-version .headerlink, .rst-versions .rst-current-version .rst-content h2 .headerlink, .rst-content h2 .rst-versions .rst-current-version .headerlink, .rst-versions .rst-current-version .rst-content h3 .headerlink, .rst-content h3 .rst-versions .rst-current-version .headerlink, .rst-versions .rst-current-version .rst-content h4 .headerlink, .rst-content h4 .rst-versions .rst-current-version .headerlink, .rst-versions .rst-current-version .rst-content h5 .headerlink, .rst-content h5 .rst-versions .rst-current-version .headerlink, .rst-versions .rst-current-version .rst-content h6 .headerlink, .rst-content h6 .rst-versions .rst-current-version .headerlink, .rst-versions .rst-current-version .rst-content dl dt .headerlink, .rst-content dl dt .rst-versions .rst-current-version .headerlink { color: #fcfcfc; } .rst-versions .rst-current-version .icon-book { float: left; } .rst-versions .rst-current-version.rst-out-of-date { background-color: #e74c3c; color: #fff; } .rst-versions.shift-up .rst-other-versions { display: block; } .rst-versions .rst-other-versions { font-size: 90%; padding: 12px; color: gray; display: none; } .rst-versions .rst-other-versions hr { display: block; height: 1px; border: 0; margin: 20px 0; padding: 0; border-top: solid 1px #413d3d; } .rst-versions .rst-other-versions dd { display: inline-block; margin: 0; } .rst-versions .rst-other-versions dd a { display: inline-block; padding: 6px; color: #fcfcfc; } .rst-versions.rst-badge { width: auto; bottom: 20px; right: 20px; left: auto; border: none; max-width: 300px; } .rst-versions.rst-badge .icon-book { float: none; } .rst-versions.rst-badge.shift-up .rst-current-version { text-align: right; } .rst-versions.rst-badge.shift-up .rst-current-version .icon-book { float: left; } .rst-versions.rst-badge .rst-current-version { width: auto; height: 30px; line-height: 30px; padding: 0 6px; display: block; text-align: center; } @media screen and (max-width: 768px) { .rst-versions { width: 85%; display: none; } .rst-versions.shift { display: block; } img { width: 100%; height: auto; } } .rst-content img { max-width: 100%; height: auto !important; } .rst-content .section>img { margin-bottom: 24px; } .rst-content a.reference.external:after { font-family: fontawesome-webfont; content: " \f08e "; color: #b3b3b3; vertical-align: super; font-size: 60%; } .rst-content blockquote { margin-left: 24px; line-height: 24px; margin-bottom: 24px; } .rst-content .note .last, .rst-content .note p.first, .rst-content .attention .last, .rst-content .attention p.first, .rst-content .caution .last, .rst-content .caution p.first, .rst-content .danger .last, .rst-content .danger p.first, .rst-content .error .last, .rst-content .error p.first, .rst-content .hint .last, .rst-content .hint p.first, .rst-content .important .last, .rst-content .important p.first, .rst-content .tip .last, .rst-content .tip p.first, .rst-content .warning .last, .rst-content .warning p.first { margin-bottom: 0; } .rst-content .admonition-title { font-weight: bold; } .rst-content .admonition-title:before { margin-right: 4px; } .rst-content .admonition table { border-color: rgba(0, 0, 0, 0.1); } .rst-content .admonition table td, .rst-content .admonition table th { background: transparent !important; border-color: rgba(0, 0, 0, 0.1) !important; } .rst-content .section ol.loweralpha, .rst-content .section ol.loweralpha li { list-style: lower-alpha; } .rst-content .section ol.upperalpha, .rst-content .section ol.upperalpha li { list-style: upper-alpha; } .rst-content .section ol p, .rst-content .section ul p { margin-bottom: 12px; } .rst-content .line-block { margin-left: 24px; } .rst-content .topic-title { font-weight: bold; margin-bottom: 12px; } .rst-content .toc-backref { color: #404040; } .rst-content .align-right { float: right; margin: 0px 0px 24px 24px; } .rst-content .align-left { float: left; margin: 0px 24px 24px 0px; } .rst-content h1 .headerlink, .rst-content h2 .headerlink, .rst-content h3 .headerlink, .rst-content h4 .headerlink, .rst-content h5 .headerlink, .rst-content h6 .headerlink, .rst-content dl dt .headerlink { display: none; visibility: hidden; font-size: 14px; } .rst-content h1 .headerlink:after, .rst-content h2 .headerlink:after, .rst-content h3 .headerlink:after, .rst-content h4 .headerlink:after, .rst-content h5 .headerlink:after, .rst-content h6 .headerlink:after, .rst-content dl dt .headerlink:after { visibility: visible; content: "\f0c1"; font-family: fontawesome-webfont; display: inline-block; } .rst-content h1:hover .headerlink, .rst-content h2:hover .headerlink, .rst-content h3:hover .headerlink, .rst-content h4:hover .headerlink, .rst-content h5:hover .headerlink, .rst-content h6:hover .headerlink, .rst-content dl dt:hover .headerlink { display: inline-block; } .rst-content .sidebar { float: right; width: 40%; display: block; margin: 0 0 24px 24px; padding: 24px; background: #f3f6f6; border: solid 1px #e1e4e5; } .rst-content .sidebar p, .rst-content .sidebar ul, .rst-content .sidebar dl { font-size: 90%; } .rst-content .sidebar .last { margin-bottom: 0; } .rst-content .sidebar .sidebar-title { display: block; font-family: "Roboto Slab", "ff-tisa-web-pro", "Georgia", Arial, sans-serif; font-weight: bold; background: #e1e4e5; padding: 6px 12px; margin: -24px; margin-bottom: 24px; font-size: 100%; } .rst-content .highlighted { background: #f1c40f; display: inline-block; font-weight: bold; padding: 0 6px; } .rst-content .footnote-reference, .rst-content .citation-reference { vertical-align: super; font-size: 90%; } .rst-content table.docutils.citation, .rst-content table.docutils.footnote { background: none; border: none; color: #999; } .rst-content table.docutils.citation td, .rst-content table.docutils.citation tr, .rst-content table.docutils.footnote td, .rst-content table.docutils.footnote tr { border: none; background-color: transparent !important; white-space: normal; } .rst-content table.docutils.citation td.label, .rst-content table.docutils.footnote td.label { padding-left: 0; padding-right: 0; vertical-align: top; } .rst-content table.field-list { border: none; } .rst-content table.field-list td { border: none; } .rst-content table.field-list .field-name { padding-right: 10px; text-align: left; } .rst-content table.field-list .field-body { text-align: left; padding-left: 0; } .rst-content tt { color: #000; } .rst-content tt big, .rst-content tt em { font-size: 100% !important; line-height: normal; } .rst-content tt .xref, a .rst-content tt { font-weight: bold; } .rst-content dl { margin-bottom: 24px; } .rst-content dl dt { font-weight: bold; } .rst-content dl p, .rst-content dl table, .rst-content dl ul, .rst-content dl ol { margin-bottom: 12px !important; } .rst-content dl dd { margin: 0 0 12px 24px; } .rst-content dl:not(.docutils) { margin-bottom: 24px; } .rst-content dl:not(.docutils) dt { display: inline-block; margin: 6px 0; font-size: 90%; line-height: normal; background: #e7f2fa; color: #2980b9; border-top: solid 3px #6ab0de; padding: 6px; position: relative; } .rst-content dl:not(.docutils) dt:before { color: #6ab0de; } .rst-content dl:not(.docutils) dt .headerlink { color: #404040; font-size: 100% !important; } .rst-content dl:not(.docutils) dl dt { margin-bottom: 6px; border: none; border-left: solid 3px #ccc; background: #f0f0f0; color: gray; } .rst-content dl:not(.docutils) dl dt .headerlink { color: #404040; font-size: 100% !important; } .rst-content dl:not(.docutils) dt:first-child { margin-top: 0; } .rst-content dl:not(.docutils) tt { font-weight: bold; } .rst-content dl:not(.docutils) tt.descname, .rst-content dl:not(.docutils) tt.descclassname { background-color: transparent; border: none; padding: 0; font-size: 100% !important; } .rst-content dl:not(.docutils) tt.descname { font-weight: bold; } .rst-content dl:not(.docutils) .viewcode-link { display: inline-block; color: #27ae60; font-size: 80%; padding-left: 24px; } .rst-content dl:not(.docutils) .optional { display: inline-block; padding: 0 4px; color: #000; font-weight: bold; } .rst-content dl:not(.docutils) .property { display: inline-block; padding-right: 8px; } @media screen and (max-width: 480px) { .rst-content .sidebar { width: 100%; } } span[id*='MathJax-Span'] { color: #404040; } .admonition.note span[id*='MathJax-Span'] { color: #fff; } .admonition.warning span[id*='MathJax-Span'] { color: #fff; } .search-reset-start { color: #463E3F; float: right; position: relative; top: -25px; left: -10px; z-index: 10; } .search-reset-start:hover { cursor: pointer; color: #2980B9; } #search-box-id { padding-right: 25px; } ansible-1.7.2/docsite/_themes/srtd/static/font/000077500000000000000000000000001241061774000214275ustar00rootroot00000000000000ansible-1.7.2/docsite/_themes/srtd/static/font/fontawesome_webfont.eot000066400000000000000000001110351241061774000262140ustar00rootroot00000000000000’7‘LPB5fÐFontAwesomeRegular$Version 3.2.0 2013&FontAwesome RegularBSGPÔ‘/‘3{êÍéŒÏÒY£D MåFx™ ¤>°›ÞÞÆ)[1ɵHÑí¦‰-A)FàÕÙœ1ÎÍ.Ó/ dºU'ë&a /‚ž³s%á%„<ÝÔ® ¾€­ÜO%pïVù "˜Ûu¦Kupp^c˜RB`\÷}TÛŒW œÅÖÁË ‹ ýÑ£ÇzÒ®5*ÿݱLzSq>Ð×?­¸Tô†35(¥œ}þ­¿ŽâœáÙ†aKPÔ'¢ÔšìŽÞ2Ë45Û$[GVzi„æ<—QAî2#+¨£%a^êV Pü Ü=öG ð,·¿‹âö'ܧ×Áì *Ü°¢¢Èñ”S„kÄû6>Œ\ö¿²‡ì:ðù^ CÀ»=P O*¦õ-<€‚ @a(0‘•LšĻ ›"žgmL%ŸÆªiC…̼¥ø´‰a’A^É舱þú– h–Q% ./Œ"}„ÐþÒ‚è»JŸÀDÍpb('0E1¯ÝÕç¢ hQšôúQÐJŸî Úà ªDp7Hk‚„3L4K«4dÎÈ S²*¢?á€êe [!•ì=8Ðg¤ÞF"bTÓÅá*¹?¨G.W“À0âQçÁ'ð^xn©?²[Ÿ ä(ý›"´“wðZðhMz"°zõ´hŽ,jç°Î÷D° ö‰„&%X Æ5²š«ôg„"‚`hñÔšl Ã78ªK'ļ³çñmƼÓF“±ˆïŲ€œÕÿÄù{b|ÔÛœ³™¥-4H¡fðP[»ËÑ1<æͥ+ð-w˜ÄE ¢:hÇKŒuOTRT;Õ)/‚- â9˜L2 ÐÂ%3LU®2ñ†Õ8ßÅY€% ­)Gˆ–ªÕ¤5 uÍêúÀÅÇØËÇË:AbÀ65W{‘”D“!dåNóÇ£zúKÇõE°Å<½U³EçqUžä*5Z-Š„}Sq¦*ºÐ(Yéõ!`‘;0.ªAGCF|Á¹yö)5.£ã@²C€Ù4XGZ`-ò¤Ë.a6ŠÃ ˆÒ¸žšâ•.¸m|>d‹;-xP«²KL›H «*KG—Ä%EF9B͆HÒi•0zÖuŠ1Tpß`FöU Ö¡›cc+UŸ²¸³^µÀúóÃÆ4x®¶(øÚF4xˆØìXݽŒð‰·‡z(R6LïV£?ˆS÷G‚Ùcà"W/B]ŽŽO€5Á!Ï.ÁО¯u»_wÎ¥±Q€C\UĶ`ÞÙv=¶£Mð­Hê¯Sײ7]\bB£Øö-—Aãj]¢zxW Wp_5MQºTw"‰A‡äqþ[MÞŒœ<§ùcô¨´v¯C›ýG¬&aYG°ŠÂÑ%ód2Ÿ‚$¶ttB&ÑDÁÁë{‹0RPu›ŒÝ¹¹0¤?,ÔÜØjý³:ÞQ íQ˜"•§0·æ 87Fà‰©„ýŒ¿ŠñAœ¯Ñãº]ž¤˜Hƒ‡P¨î<Ó!ÑoËn¸ø'|§í3rÞKÊå>]Ç.R¡Ó¡šn¾ (ãùZw)¥å¤¶¼ï™up[2•b›gã¾8Ý@W)Ê¿kì’«Yœ8åŒL›<'s†i½³BB Dþ¿ÜÅå(OC0PO©tÞt‚¢Æå6¨/6oÃâM˜ˆ²ÏEÓhÎ.Ì ‘ùä7M­I$t£ù¨–èÒôüÆÐU¿f¢! œ96H"rà‰6ÇA8ʉEÎ"Q)¿f¡RJJhì$Ǧö9[VfÆ%c£xPƒqDPœÍ$艨´,¸µvœŽUäIûm5X¨¤¡L‡¸äšj$q51§hhª«'ÞÛ þõ .L‰©®ï Žœ Lš¹¤àЀÓ®Ýbшط%UFÑUtä¥\¦ÅŸB] Sƾbõ[­›‚3Ÿf€uÀ¦{ÃØéãS6õ>÷ð³%nEqŽ˜`{1Õy*„é¨VJT(B+ñ†i¿0(/å$¥¼šÙˆ;¤¶*aR)öúIà…œ:Raõ3ÙŽìÝö{¸àosC¨ÕÐhááßàÒ"KÍ•£ë©AG‘Ôä<ø^a2¡™PK¡’—¤¹Hy˜ë3ƒNêyŽG°F„¨FÝ) »L–­o‹›7[:£’à T*ÂB¡I‹aÿ Ûñà ·x‹«eÖU,¦ ëÒµÁ›–ôÿSG7¥Ã•Îqo99ÊH+ß,W½üeÓNe{ˆ¹›/#/( ,w{Ù P»zAt‹3ìÄhfš¥'VRÔæõ# ØÓ»ýr뿾²Fîøf™ÚO[r¦±IÉë'"á÷Á-:?ŸË$€d@‰ª£±š©¤ƒõ¾4t_‹I& ŒAµB…Ä“²›$ðqb{FÉ Î$¹ƒÃ ™äÜ☊"¡¿Ï‚)ÌÙúfÌ68AÛ å5Lt|›1ÐTqˆ„ÒÓx|“ “dZI¶¸ÑZ“›ËË÷O‰ê(}ÕÍ™DýLÇȹbä¢A2Fdÿ Ù=ã´Gb4eD êóC"û#'ÁcÇàˆKj}}” 1x&”µ$±©*<›“20ÎÐb_e@Îê•‚ j úo¶œ#•¤)œ…Ï´Yi2uõã¾vù°{@$ˆ÷A9zUë:©Î-k"HŽk‚GiÑAš[=¯"D\d‰‚j´Ï}rž!†× ÔUß›~e…ƒµ´ƒ¦ó:‚ +G›Qlâ'Z‹gÇg‚W%Gn¤Á%úŒiß,ˆ•’‚µˆZ<ñe™åy4‡á °1è|—ÁªŽ`®*Ó%—v%ôƒã¡ÃL+¶t¤³ñ|9­'ÙZ9Ô¹­+ûŸ„¢uÑÂw¨«â¡Ð솹TVÁ>ô.ŒTøíË0U+S>T³JƒÀ|ûQTi¹èLØeD-A)¬p˜%ùF?õELb» ›Ÿ¦˜'ÍŽH¯äÝHMâëÙ¾5E%2£žÓiUOhx#ÃÀr.öñ‰rƒl ¿)5™•¡-‰C.(,oç8œ'Ù­q&¶ |€ãÒ7×Qÿ¸æ oM+£‰}ðQ„.ý†ÐëN—WŽ‡¬ñ33:½ ;=–Þw€ÎD÷_ ÚjœÀÇezO!fF’Ó²ßNðúqQý¡âÄ=8ö"ÊY—ßsà1]Ü#Ž;’®Á+"ÛHÞZÍ„öy†„äFD˜€¹s}&Í^BâŠ.4§Î9ÊÊ`±äÄ£ÍÛþ'é‡þ“º·ZÞb»0­ÕJw0ŠvT…RW&xÛ²ÅMÝAಈ•€Ò7¬ít=CFé$mÁË¥fj¿vB¦Š¢òñ5lÏu Œ®I£´70<%õh^Þ¡~Ü"_S©Þ&!‹úý¸ê"ÔÎ;1pjÑd¯,*`›¢Ò «€˜¢z¯_!oh‘ÿ»áÐëH(rz¡}v:c%³ÿ—€]x*•†bb™ƒÈï·ûXá|Ð9(®-¿(ž"ÍŠ»—Lyöϳ{"1P»Ë’Z&ÔBâ¦Â€ßxPS ŽÕ¤YuJ¥ÀÈ ¨eœ98GULœcKP‘4IÈÆQƒï†|ŸÌà›ƒj·õé%”H<"`›2ZQuU›1ˆT‹Wv ³Q,ýp[÷ ¾õ@–ŽÂ âÁ fÖ¤Û®£E×Ò³zfDµ2ªÅ%Æ+T‡ácý)ÉìòFÂ9v"bœ†cõ>§F*þðæÞgqR+Õæ€9^NPþ¶ÁbßÞA÷¬nÍhŒˆ¢áöèùZT™÷Ì¢)L!X2ŸNU¶ÈŠ ² Ç=¥J¶¼’+ìPa—ʬá3·ZÍ ©›|Fm-õÇ+}¾’¶ÂxP öA 0ùÂœû,JÓª”mPNb¤ ;XáSæV]eS”âëΫÓ2)l`3ï~½ ®]÷š#/»Ò•ÝZñ{=dœÍCRÜ‚Z&fƒðã“l>e¶‚¦Žæ«3a Â~‘`r‡ òIÇ´€»PšNCû`šä\ïÑÖÌQšÉXAH$íŒÎøðŠ-;Ê€¥¯Dmé¦ ð-é›~2{ñe.Œ^{sØLË—ñÝzÝ„[¿Ÿ£r$ÁÈ[Ð3%å„•Ì*fŒZÁg§t,Hê9NŒ„M‰ÇO iR?GÞ QÆÑü´tÃïš:–殾öÜ@Ÿ­©•03¦øå®P¤PõXßC‚t“±\ROþVêãÐ-5pg™2{QÊ»o'Úa_Ð äf?‚Mëïwp¡œ<ø˜w7Ô¬-XTaø‡÷RY=‘au»*fïq(‚qê(T-]ÎѺŠ³ ÜÉžoÌ#ë<ÎrÁÀÆ0º# |z³÷Pù?/WÞ¦žVdú7¼Ñ–¿v„´ãv㤴OXk›³ Šøù´‚Æñ2ú:ßŒàš¸0N:N8 šÚ·½Ú=/ž2-b‹pƒCâÐÛþËmï³^…N"s›k §¯+Ö .žº¬ƒ5€ÅäÕ:ŒFÅ~Z²ïò‰‰ÍÅ(›` + %ªÖöP_\d5ò®¸q‰K‡<Ñdjáé£ÉƬ%LÖUdF’dÌ?Õ9nm«þÊöÑ,Í(^ôCÕ-½G6ß³´†€-¦ ³¶éOO¿;‡;¶Ú=”dœåisÏ% ìƒ?°2ÏO\Ø’¨”:6åê­mê´æxnŒ8D$bƒä©pD!uŠÑ‡ÙvIðìÀz™áj&›þÝZµ³á°@K¯Ñ£&‚n ƒdÓ;è+™7²¤øi`Ql±šá£NA†‚!|ô RŸŸ†Ý+AGƒý’ˆO’[ä þc×@-¬RšêÎ’D– ó¿«êBÕˆ*H ÿv¿?ëÚväNì‘À"„„’6N&Žø4G é9PHž@ ¨H69µà0°ä«-]«²7Q˜Fp±ñlïBÇ ÌHÑ q^j)º¬$oŒÏËÑ5%H^ÂY…P™èSð6‰"EåÒ×™ûÂnûÓœ“=-±Àô³Ðàõÿåv Eö²Ž+Ç«0W¢o¬¢eè5+4©Qyß àÅàÆž“òÖœM)§w¦TÒVèM÷XR¸P†DwŸÏBÙRªê{¯P‘|ÞæÙÖˆß|»DV'Ä¢Öf¢ß…õ œ³¸ÚÀuIñm¼tÈ‹|ÝVkŘ'm/ü#·–€€ƒ\!aÖ{s@Žý5‰Dˆþ€C «ëkv¥y ÃnLí¤Õ÷!¼;ÐÚÀÎÌèÓŽ· eD=Ý¢<+Aˆ Àõü+?9à|#ù!Ú‚œ77ˆi&P,T*Ó„Ïÿ9 fŒ¤ç_ ‚"gª–‘Îc5‡yˆdGý‰{¶ÅZûˆx,«m?#Íd¬>x dØ·Ñ ÎœýsÛ¦UçÑã+6^v¦Ìþ›Œ´®IV>̲w”ÞGúÐ>Ê4€öKãH\ì ñr{­Â¡]SÓû úÑZ‚¢£hÃq^¢ƒ <®ÖÊãE#"I/C´ï𮬖gvúÔúËIy Ð=FÀrÔåÞŽ’–^©ÏL–¦`·¶W¤4òLÿd⌠£a/¾‰öÝ;è'f,9̤]„N?.^d|ŒK‚6¯ÑÆz§8>‰gƒ›Ó\䯽Á÷ÞŠ@¤#sOÊböTÒ´úÕ• «›rB¡‰@ %ÇXB›ÜG{ÑÜÅh.c*µIŽ¿âbÓT„í‚/ÛQR­‹JÿÉ-=Ð _Š*q}Å”8Ô/³"’¢]íÅ£eFõñ8b¢9É鶾êª%+d)Rá÷ï×ô»Ñ@‡”»:Mœ~!hF¹™B ‘¤¨`’ ­ÅŠj<^•T‚^¾ßÀcl¢w+µX;‚áršÏRŸ*–¦Z¿°ÑÆþ¢î½jËTÕ5L;(˜²Ù[á')¤¼ñ–¦”3¨Ka+„°@.–^°?Sm#íå=c|ˆaÈÛ5ž¸kR‡CA¿ê%¦œåïh¡–Üfyî­Y}ñ ÷´ƒƒ‰h»ç\…ËfŒa­íÐàs™ï…×(N~Æëëº6,ir‰¦‡èÓÂØ«_íˆÔz?`(Íùm %íɉ|Rò"Åc±Ð@ýé} py’¸ž†«À`SAv'PÞûG ìúÇë’aª&,o’^<gj B£¹@üALø»³Ú£‹Žu=lîèör»ñ½…ð×ÂjÐyÒ#R_ [¤*”h€$ó vÁH79öÊ k2U«+4°W`ªDÉ—¬PF¹æ¨eEt+ÅïMüŠdBp¾–ʼáÝÈ+ D(†ù@Û—­F¡ƒ¦Z1B¨iˆûKϵ¥ª8.¡‡Ðrx²ÂB0‡¥Ê¨¨^nx—Ü\'Ù˜>VŠDϼ܆mP·ÂÓ€(x9ÙŒ¶Úæe{Ü ®L[ÂîE[nÿ_F×c— ƒXQ68j-—wkvsl¢[±yìl°¬.„êói N²4!h‰Wy÷\F÷Mb6²œ„ÕOl(X=mW×C±v8ž­£½)Ü\#3ÖÞËÈLÑ,TGĈ{GŸÓ…B2îœFSsLR2Q|£Ò="*R~õòäÆ®ŒSâ˜Ào”ýPe79E8ËÙõZ„ñ÷²µ ÕD¹`':ôïH©ãN¡R}š§/°èʱô(¨¸«Ð%Fhr™bR½Œ£½˜ÉAê[6 ÓË浺p°Ìp×B"ДêDlŽ±æSâÀjAñ:©ECUl.Tð›ŒzÙbA2Ñ€KMH̾ðÉTË {5h¨[2¬`¢ñ}­†œUx ùŠ'¿™£/~ðÕEÀŒM‡{^,ƒyJÊìúêX© u –i4ïdÚó;}h,ƒ’ÆòùÛ\m$v£Êû½ /y—“´ÿ¾Q èí'X%¤¾‘,© ÆÙØÍäÀŸÔZb3ª””É;â@S}Ò RIÍ6ÁN£guc瀹#¡üU @Þi&²¨2’P@‚þ8‰Ö¾u'b/Ч"NÊËYÜËàêíÔPOÜ6k³6iC¯N¿!†HÇ"ÿAÍ`Ëä‡>@q˜N¡ô# “£¢ä@hâŠ((eÏ÷J7„>†i¨_<ÂI¸³Ayñð|ÉŸ­öÂÙ ûsÚ{ ÑßÎdÈ…ú »©´CÝ“Øpæ "´\‘9B–±ºòL@MíŸÚúQhjŽœœºxŽÉþaÙ½bÔh¯ZÒ 09}ûÙq’n«<× ‹±ö+÷¼¯5ÒÓK&h˲Tû–*zý:Ÿ%’[44b›`Ȭ×ï&º•Ã&½TSvžÆšè`7²£þèPrWüyþ4\èéEÌEÌ•¢ªwu#DZã0Cp\ìÁðŒÎF¥ìšccϪvÃÌš/¬LkY ÒœJv~ê‰ËlP‡ŸFbV[Lu>Â!aî¾µfă—€îäš:¹Ù«À¼¢ÍÝ,"Âp‘Ýñ ü¤e©:Ûù‚l·šóœ¤ÉÅ @±£Þ¢âÊqkS€N¡¦S…  b{s<lÌÒ?ÓÌt ÕçW³×çLÀX'Üvµ<¼Èð¦–,¤‰¨FY¼/eÙç—Mz²0†™å+ÔšþÜéy꜊³©Bøþ 0‹x]Åje¯]R\èáú`ÅuöŠ.E­§©. ʻ릙¡B<›¼6¾Áê–råj ÚÇ9Á߃⊋ÍBf-ì,Q…Ï‘N¶#Ð/•ÅÃðþMÈ" q«ÓA@2X~ÏD0á]C´°­ý[iÇpr Å@aTŠUt©©BŸÏ÷oÝ•Òœ]©mþØA«#ÖO‡Â(¿®JŒiÔŒ¬6v[{„q®yÞÈX‘šR6Tí±ávƒ(‡ˆr‹­sŒè5Îs<âØ>¨¤¿•¦$Ç,·mR¢Fž#:ÆlBD`…H9PUôî›ÜÈ‚H4ªáÆ@ÿ˜· €ˆô·!4ò6õž5ÇDc>Ø>˱:½A0a¶0îŒÄÉ@Գثöƒ¢qÄ—f²´Á[æzÖÙ_<¤®~À¦qúŒÜbV‡ù!k29ň¼ÕŒ¶ÀB=Nº´ºÕÿ'¶*ÇW÷³€ôœÒð݉¸~‹Hx8ʘÊþ TÒ±èGFözh[õo5,¶-¾ÃÝX_ƒdƆK@U€•ùÇO¸Y“c` Ô¶49J©=‡¿P_Ìê8tânRç÷‹”Eÿ!Ç5>ÓDÐ ¡.ïÞÅ/Qê¯íÕДÞÒ¨1ˆÎ¬`n³ÝÌ[4N}¾¿Ý¯7}.úµüpN¬°Èê ,nå±{µ´r¸©R Ta¨°±«ûüÅ™œ^<¹èh ×vˆ!î}Û¿ ©÷CEÞËACéJ¶Žl¼Í$Ú„º© eü˜Æ½’8ƒÁœ‘W ‹Uš(í£¤5¥,´9ÌÖd¥8-Ù!Kjéô(˜³+ TXv¶š6F§—“eNÂL2ŽLìf) ¯¥†‰fª þ…‡-Ž3‰a,Ó¤L¼š‡ ÙXh b^’¸äUB› äPâ#IF[c˜K¡å­ä(~Ìï"!H¡UUrX¥Fe‰Â%¯.¨û¥‹]LDDæ;–PÎÀh d4f»XrQqzpzŸ0(#+bvt‰ ‘p¾oê×ìÌš8lœ£ô@Ü™¡G¤\]™œ‰¬”{AÕOÌ’¦?N$•~†; .ÎqY“U[Sèå <•N6wgÍMŽ†¢OjM–QXó‰cmg:‰G‘‚g˜ …´Ž¿âøá…³‘a©¯]¸“1è "À|btÛè³Ïê”1C<·à²@Ð3Äôp|ß,†¥ŸðÅb (åäÇÕ½0 NGFÆ3 RqðŒL“Ô¦¶BVàˆHk i+F8[}3l&iC¾´Ì£¸ ©D”TNž”ëåò„+‘ŽX $ñõFŒžD?¬¥ØÈz r©8Iì]êu*<à@ˆBmrÌÂm¶«ÔåȆžkLE‚iäŒÚ{« ‘4OJ Há¬Kp Ä\€a’h8S§F#Dy*ß!]Ðoä¾CÄ|O:8Ž£nÅçñXÀGà!r"¦“Œ†yÊ'“ÐûÉýVy#bÑ5*ãi&( ÁÂ6lB§ ÁdT H@/e'äfÎ×`ðFKÒ¹È(OíÇ’‚CžŽ‰Á˜¦$„å/Ô1v|Bxß8ÏMDô÷Áݲ)› Ýfè åѹçe“RÐÏðqd´.Èä(@· \C¼ÐOTèùdË*àâµ)“ ÐH*€ ÕÉš sN·,Qðj)í´™Îz»æÍ °'‹ò¡lB ¯£ÍzÒ&"žåÉøR èo×4¾!y;BBJûª—O] Âð7`цŽ+t9=7°“ŒõÙ92´ržRDÃîü|\¤€o,}±‡!î8ð®õ V4¬ç¤${øÊ ÅHRX«Aˆƒ&Y¤Ò±Š†8‡ , ¯â‹Z¢sñl!ÒVÀ-…[³vËAmü9ÌeÃUÇEMí­H´Fø‡£€E)µY‹_‹b&_“£ñfbÈ“‘]È1w_ ÕþÓ ÖÃ]1%Ô˜»|)˜«_)‹H.+ø˜¥2Ç\{¤?‹7I§åè›$*âM€ðâÅõõÜPe´‡…mšT*¶ò$× ^À"~¬›íª[ô,†©ó‹È3OÙr4€ÒªBC´÷±EÍB ûÑÑ%a‘¤aÈ+T¸–½‚L 0f(#–"k¥¡†É_°]µÝµ%PAø•yŠÊ›$YÔ M#àLä Ê»¾=H„©­àê¡œˆ. òøªöL Šdª0¹æà(ÃÊèd}ÁÔ sýnjҰizS«`j©Æ›mßÌvϺ/5>*ÌM£Ì|ÆÐ"*¶VigÀAú’ üFL ë4¡ÎäÓ$-á­„¿¸­¢M—lúÓÇì6ç >ŽŽã)´¼Æ}fq_WD! ¦eÖðžoÿ(Hƒ¼Ì2ñø?/H=¨?¢*qõ¾qU½h6µ°o¨}Í k-Õe0 $/~»F”BsÏ ¶:˜ýØä´…êcE§v”ñ³FsH¡%ši˜·n„þ”e‚\‰å5ë<žíbÊæ=¹£f>Ë PCE¥y®ÿd,K *3Ô ο´¨3à ˆš¨¾íÑ ûþá…ÿ¼Ù¥Ã*„Fœ”µ5bk¥€e–áV¸àÄ]UOˆÄðuŽ¶bd`G†s{òKUOÇPáú݆gQH@½e*FÙÄ©/j’¯sš¹ÌW°‘í ‹]—Qi ÿÿ“ÙÌyÜåqÉ@J‹Ž¤Sœˆ¿í­ºX¹ˆUƒ)ì…r& U}Ñ“5‡ ²/꼃M?¾Fo_So(qNðV&,±0Å¥CÉ,ëô\ð€ÒLØ￯5¹ˆ^È¿ ß#4JoìcÓÔ¬öXøÌmTˆ¥Lªˆ4Mœ&‹s ûaókÿ#-¨PXD, ?ðú–pVþ0¤Ž2i nè·ô)nCwDí¹1¾BȲ¾)xgÚóñ©kê–ã†1‰û>¢WF{Piü´›¯‚1„Uä ;†w,ë5ž¿Äû„—§NtŸÍ3/ÏÞÅ¢ ©\KÂvpr˜Ô’ÀÏ qåúñ'‘‰Ž#±†9T¾Hr6^ò™d$E|cílÇTæCH{÷' *Ý ;±Ôôóe<>¾4õnóÅUêo~øq®Î1‘GâM6QjÕJ¸QÙT}FS𯮺ùé«»@æ®jfM—¯ø‹-’ü37qõUµm´ÑíHÌñ‘Y<€UÆððá¬ìZZ@üt8,ÉÝ–yÌ$Û]­¢!Ó«.Q·‚æoÕñÈ<›eâÀDº‰ÄÁT(^6µÏΠέ¸Þ3¬8µ¸Æ¥!¿†?ã C§a…ÒFjq7Vð"ò#[V0&™Ê_Ä×’ý?ý¼ñ¨ÀýìqˆYí¹[ÅÕË>Z}©‹*"'Dÿ{üc°  Í Zé£3·Á wÌ îìôâ1)_o⬲Ùä\ðÇðÃQ,F‡ k… ži¶0Ð Á”áï´â„†²-¶aŸòòÕ‰Ô¿ð$hJ^H×UyhîÃÙ'¾’7KÓÈ7 bç3ŒãtõŽ*iÄ­Q¤giºeI±„(t%aàá%R„©¢8ß3GTUžª·z$àMºé*~‘…Æ€J–Ñصn–u˜ B¡4èγRÒ-:‹;qÌÖ½Ñà™(™Ð;ÏQĘ)Ô“1EF÷ËÓv:T~ïýלŽziŠ¶4*оT‰\â˜<þÎÍËó韴©5ï¶Ç…ÐÑ!e¾f¾ƒO/wŒž©)’Ê9EÄ˱üyFæìÀtá /t>^G^,°U Ɯًi!sNvSš$ü!òèÔF¼qÄÄoB2¤‘ œÝ`O÷èe‘âæ@5Ö‘¯r;[Uª­ª ­.|"?Î!Í€åÒÿj@=1Ró¡Šàk©k||êü½{Ô%-º®Ç=öÂ'§qø¢b†¶ Éš‰ 6›š¬ï€ òtnK]{ˆ3H³ãêBÍ à¹ÜÊv,n‚)ˆCŠæ«Å‘]|–TQH‰„<£GÉMx4]b  ÐPèã|'øì± *‡ØÏ!ó¶+qwÜtž™Äôn€Ï‰!%|O;„Þ6ØIÕiMùÒ›Ú(½ÜØdVÁe»0BßÝfé\N¥¼ã€ƒ|ãÚb¤_ƒÔK1œLÄÏã¾T%Ÿ’–éYÂ0rÈExìÀשÐy®ˆLÀcº\Y°q½³PLØú5$|A}½ñ@ÉÙt¸-ÿ{Õ}lÓèá“ fŽ~möK¨´¦¦Kƒ¡þýëÚ½hû>‡G~^ +‹±ÑqcEyî'Ûƒ¯›OC0÷«ÎÕCÉ1"嵦4Oë-µŸÜˆ|ˆ’SÃ8cÛZž<=Ç äí•íòM4¦t?ó¶]Ë´º9 ž+J3¼Cd ¦-æd¼®X!Ê!ˆ¸ZVRÒg ø¤å‘’Å›¬‹̲¬\8Ú^òù!Õ#Á®xÚi ¶»_ÈDÆ™.ˆ:‹DªŠ3‘‹ÁdVÜmw»ZláµÓŸ¹yB|t±ŽR†›Aí31>Û$¡UÎl†6í@;ŠáÙ_«ä4tA!²3ç|éõÈ+p[äA¾…kî˜ÖæXA¢ÂkOFšt¦Ün¿”ípP(Æòˆ6Ø•Ô"þ²¨è7/„1¨)A¶@VÀ !1ø( •C@ðª èi.**ÄPXC'‚ ^GT<áúe“c—ãMB)ÛR…ÈÕÈȨ¼Ý¶¾=š»‹¤ÞêQñ”_’*]‰¯W%çC}÷œ÷Ž3V> ñ‡ÎO\/ññì{§7,YžoÓÓ|²CÇs xš ˜!qF ðײ‚ò·æã`Ê>ÂÖ˜F=Ú"ùžgË^<º‰rãU,dʼ1¡µQ{!ŒXX@“<ÿDß-qÊ@7´âèêø}é#£‡*ÄvÞzýp³wÑŠtï÷™BoèdÀ›öÅÞšÁ z.­î U1âÀ÷ÄT QJä×ÈXyå‹‚zõ/6×!Ò‡]8Sª²rv=‚§ÑSÈËƱ^©É5ØÝH%M©×#p`E² Ng[Ç™$j…ßUבK½˜>æŘä:ÔWô¢P*ŸòÎBM›BɯýÃ+6șDžiÿ—RýØgyürÏ%/^Mà¦UÝÀã{U%b¨ ŽÞÁ(êŠÒbÜ9b/eÚ(h”ƒ÷|kBnÁ¹ ÄÀFVKŸ_â#(± Jƒ)™øšgK«À¤+žìC ¥(P‰—*´nŽ4òŠ@²û,ÛNkg€µTÛÊúxXc•6g/9¬XO,xÄüå™q+ÒdaSL§ä“ÄÙ.9¸óÃ؈øÏl¸¹9­éê× {ýeT£òŠ1؆¾Gª†G¨¶‘ü)ÍxaG#Ö\¯ÁóN$ÇæšvØ`KŒöát|ÚNU3ÕÖkJ|Zq9z1!'Å"ùd}¿Ÿ ¬ À¸yuJÉý¤YygF/F·[ëÄr¬š],O'­ãct4÷›ÃŒ”œw¢ 6¾cHì³ÿ`&{SPeÊÖ–ùmÙ'/j7Ïí4‹Gâúˆ¤j|>Ì©( EAÜõúf>b‘„ÑKu rn· ·Ïbšc¿;ágKC;8irA1“/øß j€¾}²yI@èT|ËdPÔ8Ï„™Aù=å)€<Ão *`|f\úQdzé¯ð‘-øÞOCŠÀÆÓÚ¯§bØþÏp²ûçfÊÛ\ÙˆÊóêr+™I±;9•O½D-#³!d¸àq\²`1ö$Ëñ2aù‡±ðYíSéìÌ-ƒ} øûÝLq¤†A-Ü9äIRòÂGn†ê„#¡D#QM7—Ér\"k6Ê ';+[±©]¥wý3IK$½«Ž¹Xðð·k¤‰Û-—H7 À¾ +>%'ûën! kÒ`X=ÁeÂmê^0»ÕŒiÓ-€ÙàGAçM‡øÃ|á3X¼pm•ºÆEP̬3¢0·VÜ^Oñßô,¦ÍBQã<èI°@sÉ2sÄ‹›¢ÅîðMQzÝ&[|I¯Aÿz(Ò mIo†í¹@F‡tæµ;è5< , ´ØvR?›@?}øßeR†Å³ã­®Î(hÓÁ4…o¯ÀôwþžMyKjÛ¶:: òÌAÁ.¯ñðvq×¥Ï2$ºÝ¸¬Pë—C‡òøÀšÝ¡Kn¾sGîÁ36·N GÇÑ…øOÆ’JVî9†ýAߨŠ†ÆÚ'"œ§•ÛLüV†ª×Æ÷Dàþ±ÇtGyÙyê#BøXDÏ?‘fªD,Ýñ–J×¹Œ^+ž4è’Ë °7¥J‹ný?V99~:?׆(¾"’ täõ‹cfIb øÆ‘ÿ>¶ÿEyÅö?ˆL §úó `rïÕ&ÆÞ¸†ŸšâTýí Æ00â!Ðãk‚‰wgTþå/u¹À<ÿiJí{àÔx“7¬jë#tÍ*&ŽI kçA¡IMûšÕÄk?“Ò `ÞÊ»¨à‚a~)Íì¸@¤‘hÜ+v˜µ„˜OT8‡›Ž Å&…g£¦dv$¿o¸Â¨(F¾ÙpÙŠçQË]§þ컀^4ðQ•TP::4A¤yïO׶ñèÐWóÞ´?K¢¯½'îK¾Oy©˜sºÿHÓXýà@ë~óJ ,³C©­“=ý.8’¢:d¥žàŽ£a/ô°BÿÙ°<äo ÏãÒ›càð~‡îbÇå‰0E„ §»jßÄÌávT|äé†É”è´v¯®Iôœ¹¼º_ÐôéÏ‹zP¨H–l"ŽÛ§‰W"ój?žš» ÀAF tŠÂñ‘Þb:¬‘ "ÐäÜ 'ÁÛ]`oäèsæ™Å¤. egÐ3,©©(Óè°pUR%D¤Œ5qIÝ£)PðÄLAdRdŒto=k“Bø7·lô¹³á¦c=jÓüiObçcÝ•8$–ÒNeHS´‘}Ùïm„tÙi >'è ´FžÒô—‡§Gù'n2ÓÉJ¦í 3L-%O• 1‰Lûv‹Þ‡L´µˆæo ñ-ŠÈ©DZ_-˜sc‘Iµ/Ü“ÁÒjû]+"׬ˆèy‰Q…8yy C`ŠÃàM:XS¼ÒkŒ]«ñM²È:˜©ˆ¥ÍWq`$E蹘 ±ø{X7žµfQr9”W”Ü6 ­¤ß^@tQ$YF´fhtÊnñKKn€¥(‘H [;}²/#”Ðíf|$T,ç¨@²³æ8@ìhÕ68ò/ðRK±Ñ㾯“6ö{E% Ç™r@MHä Ûý¤—ÓDFJò? *äêÒƒÁŽÍŽÖçhŒBÄS4ȱTe˜,F ¸B¤B’7ûßÃ@պĽÀ­^Ë@ÂË8 þq3"àŽOH¨lN *¸iô¼ÞC-½ðd÷wµ¥M‘P)7¡1ÜBª[×òOÙ o4 o73ð%¥˜Bá™3˜qhKY¶á~õˆeöûI¶Pm2ãÞw" óuß<ây s\fƒ¬…Kx¹Æ%h‹ÀK¦=k“q€+ˆ…ÚØ8ÀÜ@$fÃK R©äÝ¢èHàv0$‡`…¨_åß Ç¦s‚]ÍL‘uÔ¥qqœ[2f¦‚ÉLOQ*kúmò ‰Š=TÍéö4Ô°ù±‚å"rtÀdìD(, Q–Q!݃†ÙA„qË…i S¢á€Åú$>„Ê”ê^¾‰*,;LÚnïä:Pñ‚Ä’‰´îö辂¡¾ä",#f]$óW>ƒád$æXŠ©qt‰µþl¶dd]L& ^Ÿ|§¿új&Gñý3§²\l „àÖ›lU.í@MŽŽ\n)“Ú„ÿ­#œ“2AǼ IÏ·rn™‘’<Æ“w ¤Tƒäz0nÜʃr,(Ô^&¼ãÒ•WŘ08‚åÊvßÂÕ£³ê"÷vþÏc}²BãÜ*@ñI,Ú×wš÷0ƒ×Ùy˜)Ä ·s7›è'ed22|4ýP?Ò•kûhˆfy³î !—™ïÅ›/gG¯„ª#“©¨:ÂZÿñm=Δ~ qN]éæ %¿x`Uœìª×è`èÀ—Ç2#j£8RcŽ\‡\{éˆ8LÕÛˆìCüèÚÌ-Œ\ׯöÐn¨·ÅOŒD`õ<ôqLþGŒe˜Dú o)eD–Ñt§¹Ü¹K…¥•Mn­w¸LQpù,›WŽÍt]e›~¼²ƒr›î–“ë´,; L4¨f`¸&¬·KóX§cñr)F‹¸µg…¤E ЉpÖZ6$x•ñ®Ö®nTù¦yÔ@“ ž¼“«Û·8 ¬\Çã…|.&x½Æz ßÝŠ´ZB%9ø±D„@7ßœ¼ç}œ u¹¨!¹´BåàtÒžŸyí¹gå ¹k‘—9EÒ ñ.ÙŒ¶Ú.¯iù ÔmÀnÛ šì ¶ Ë óÖÎô‹†ßyF ûhžŠ†w)®Aš²9ÈX”Á±Ø“”37U¸wª!Ïu÷-iÝβÓæm¬‰ e"¸F‹ é½4 á$YÀÅ-M‘cŽ Q”Ó^“™Að1^ÛYˆ¦‹…é`ÞGíݘ©wLn3è@Ef¾Ð7¨¯aº¼8iÄpÇ÷èL“žX=GSé ƒ EY>&Rl[²gP`’œk6=€Õ©%i«~ÈAgŠD‘«@ÏÈÚh  ðâOÃ(f7Ž¾ÕX½!×Ý)$ b9S´`XH e ~á¢Ç¸@–ý‚ÀXæÖ”c(@SƒUŸœ®”‰ÿ8ø%¡Q× QâzM¦Æ(܉ÚF}@³ß7Ë°îqóqÛH{5Y4Ö NÌAIoåØÅ|ž}¿- Dð&>‹/}|CÙà[$:—7û¢ŠÔ*ìt,¤Pþpðh’ iM¼„·- q4„NI9 ‡—‹WìçãâÐzÓH1.#º*Nzt…$S\„´0äÌ.Í2)ú¿n).­û°ÙãÆw,r·ÏË¢[¹;®*\ãpHôŽ¯,?Åý–q8$Ãà÷ÌŸa>í{¤8M=ˆ£OIºA ™ò€92@¶=é‚|É)…¿®—¾XhäÙq¢-èðXÿÕìh-Uø½2ÅbH«uߤ™–>¢ÎlÁ›ÒOJœ½ï'E8b€jÿj J²öFAö×+ÙM¾&ô¼¬ç XÏ•0:ë§aµ²ØŒP,/Ô(lýãu)¿%’Ä#Êréæ›Íû,—f¶GDÊ·£D^Xƒø%öQÔ§£{Œôi®è xø¢`Ôφ‹›`dÑQ’Ixà IÑõ¸ûõ=aGÖø¾6Ð!ÄÈg$ý©ØYM¦4¶’¤·YA1MN趄š¶(4q°¼YlƒùêWügé¾7$† Š£¦ û˨īY‰• ઠ%¡%Úð`¸'¯^F6ÙǵqmÅìâHi*ni,ùc~`½4È—°Ý4ëŸg Ï$¸a¡*xâ àˆ¯‚=õ2Ê0“‹HBÑQ¥@‡5H©³htUL‘áJ6 e)Cà<8-‰2zÃ!è„”âÂwÒpÖŽXÅ*Ê1§’æZ\†»õbÿã—C•‹e¥Ë?ù# ”I0Ö©ñrøÌCiÆ‚¥Ç?ªÃXË‹åßú 0\ok‰“¾…"{5K´û*Ÿç‡è„Þ":r]?ªX9@#‡&‘c²iACƒnt'*Í• ÷P& ´0 옙t€n'Üë6ª¨/h Y;<$âbó1©Ñ?=…àÖ‰”Á+DX8²TÆüÑΤ¶i ýÑ‘]8¹×°‘‚Ší›.×V€94¶ŠqMªLƒt£ª4ˆ`Ê) a–ÝkÈë@µIvn.’4瀲_c?'¦œªú™P+„’UØ“dràŸEá—àr:ëÙgß„®ë¿ÈÈÙ9NM…›zŠŒ}´ªÏ¬š£mN€•×X2PŠ±E ;Ñ‘p€²Q²BOôÓɳyÈ@T‰ŽéUOG÷œòp?È{9‘È'FõrÚ'‹Õ@¤3 fÁCÂ>wRñTj@ŠÛ?#Ëý){ÍÄ€ó‚&½€¡ÉDsrˆ³>0ó+>É:&ࢠ1†Ad'çNf0\œÙêBZ”P€`4G¿%¨C¥@³9 d" A¢R2«¤dæW}Ô˜xF8YMMÙC1ãiBÛƒ´&ÿþ~— ñm˜†€éVÿ“Å’¥Ñ²W˜¯g}Ä.5‡sÅ{x±š.vaïa°^íÍk²ûœQ¨fÎ µ™ÙöÄ\EjÅRýGORbg¾¢åºHä—½ØI×AbŒÎÂE˜×ÁÉä›7Šv×E&˜*þ𥎰ôç… —AãCó.dâÜ£kú‹Ü¦¹²ÚûOÓ ÅT¢º°Ù^‡.Fhã1uÇ5^‰(éYÊÀÊ”I#s’¹Ó4 †^‘Rkì¿á‰jÝíˆfuä¦h ƒg@¹XdÁI!fS4{÷Aé)÷nßâúúš«ËJ¡Bv­õˆ.…û4>Þ†r9Ó,iõÌt&§€+ˆ½r6†¹3]ûù 4…6”=¡M û[Úvàa QÊ‚(E‘ôguUÀ;&´²2= ÓÀ#¸Á•ôLpD,z yDÀWvÄÈ°i£+›É{$x䉃‚õ-uFPƒÁ]sÈ©DMŽ(4ìyÎÐÐl!³b•áBÒ°õšVƒJ²àËŠk<ò^'Vf G_P±0EÉü3­è|bA8Äó%Q…žÔSãéõ§='Àq¾6%3Yéóú>᪠ÍÓŸ,žqá96JÌví,HÃódzÕÈãL[¢g’;÷>%Èó|~{G¾l~ßx1@Y:MTTÔØú$bŠ„Aµ}÷¬$õ²r¢L´çƒ¤O •ŒÎöįÃ<ý NV ¶!Œ®/Ë›ißâEá£eŽÝ4Žð–]é¤\]¢¸9QÝ-ŠxKû‘œS(á#6d—BBíò,'‚;‡SШ`ärsÀÕù~¸æI³,æ//«Ç {åJÑJ`”ÿ|­†Rì†`Ï4tÓö$âø'wL¥ÿfŸò±Ë0à€W°ã€×ûvâ#m‹sñMuq2 ¦ˆL(óC¶ HSZHó|zˆPp€AŠÒ”öîñÑöâÔ„üÉÇ4=n¤V5ke3ü·]® +£RRd…Ì ]Dˆ7ö×q,{ÈBFðÂÎhˆ@RG~¤{cHfŸˆ öTâl†Ñ*%ºŒîn*8àv^ZQQ[°uý‚ÔQ%Ý sÛ9Ò^¹=ž„’"ÔEŠzS4„h+%üX¿½è¾hæ$6Š@ˆÃj¨0¬'å ø?,ˆ!3øh…Гa@mFÕs”X Õ9t×Õ!”’(õ4½u·>‚3Pâ Ü<Üð_ÛŠ‚|4¯ÂS&g|«Å¸r;•ýàêL„Ò.âQ²:äp DfIÁàP§ÄCÛ4 oþÌdæíHl,p³þƒ¹ ýd  ÂñÌpÏýˆµÞAîoÛD 0(,Á°d„Pýâ›Ü6zdžÜwy›Ÿ ‚„øT£Ÿìð<€r8G:>—”ô#¦Ñèîg\amÝ„eèyDôkû`bºÐ˜~ÇAÎÊÔ‚<2j"HÞ3N±LÁ¼¿Bc®-}ÍÜÕ/…=ØG±ïë÷»®©Ñú»Þü"àÚ˷܆ÎE„8nÌU8&ÃYÙÛž?–µÿ½W&Èvn8«n­ÅÔ2ÙÛ2¦z\îklí[úH¿T”eý3\ü¢@î¼&Ô¸Â%çÔâLìÆE˜aPï´ˆ3 ljO˜õuIpˆ`1ö@¥‹í!&63¯–T1ç?Â;ú¢¹°ÇÿF¸;£Þ]ÇTB³Míy£ ;Ɖ‡lnt$XÓövt2LÄ0[P±i !=#ÊA0T“ÝK/Ô-Ä‘ÛwøÜŸ0·.’4"©W†Ìñm47!Bg¦^P‘¥BF”œÜŠütHûá4xc8¦êûDhä¨óEŠgðe¦ˆ3hêòÙzWóf·Æ ÂH`”"YÙPˆ2Kzk; wÀ‚õIÛˆáÁ\"11¾¯ñá‰Å­bôŠ—Âý¢\8“cNz°Ž—H"‚Ä×jõ}ðÛ:ÈgËuŠr„¼ŸÔšNÿ,Y<ûÆ3ý­Á(ûö ®Ðts|%R¶òæñ¦b-Ôl¦Éª•ÇåF ¥pž+¿`3qƒs¨¾ßáÅ&ÏÕòhö¹Á3 ò*‚«ŸÅ Î0˱¾CZ#‹¸ =«‰a´îh  8k‡v\XXQ"1,ƒx â£Á:ô¿pmzŠ!>Àª–RŒD'¦êåMN"Ûy‹- ® 3#÷íJ¬³{e*n<ß´„Áy&Å©B\m“í*ä„ò™¾[F ¤ˆ÷ØOé/l^þÖºçA[" øÈ)øî0ý‡Ç÷T¬@ÁX—DÜ8b/( |½°ÐWHƒ£¶BBµÙ)3ˆ3¢ Ç’ ±~ó$ªªÈ{:ºŒ:> öZ2c^&òüÄC\V€Ûþ€hÚK§ðÜÎÔiÔ%I°,q?À2ã!±,§a±6ø4Ëh» åö$¿Ów° ßæÝìhÇɸ{¡Šz`±G¨ËyÀìvOmƒ^ˆ’ÅZÎ1PVêê”Éæ9ü¾l]ó‡ŸíÃÔ½¢}LÙ¾: î¿\x¿BnûCú•î¿°>5®’?ò ŸX´Ÿ, @p*øx8C>µ½µv;…^ ÞKëÎÇ4¥p}%xK¨±™ÌR ©¥j“4GZèÜW±‘ Œ0Û¤Ëu< .B;ôŒ4"/ºx\õΈÊEc|ã}Më+ÊsÝKŠ= rÐfÁø#uÆnb²1ÙÏ<°Î ÎñÝ ðj/<$n2ð*ßš˜,¶Óí`R€nPCJ ]…-€ ÀÈps»oÅa D€d¶î"Ž,â ^„‹œ¨]ú::1cw^_¹–“4û±§YýÕ 'Zò¤Ý’CáJBÓÒì)wf¶‘›,È\j>„Ž¿,ʸ}HÜ­š7»Éé – @ÿµŒ VFÖ~dGó¸(¿qy0,|›\‘!*ší¶fÕÐÍâ 7Dˆž.¦/úBм†)§€Ü[§BÕ'á,TŠû¾â<}ŸÂíÜäÊbcS¨ ^ï.5#bâgxP¦˜€KÓÌ’™aD 6‰ñfWžŠeþ&“µ±–ošåœ»(Ñ*Éì+ PÔãÃå*8ê!è_£f‚‘¦kÐg+mÔ–ƒÒÖÆ™¼Âm¹bŠMÀ/ŠdG~ *–~È-*üw"=¥ñE9|GÍ鋈ŽÔWô Ié5"Ì`6:.ß‚ªÿLð‚HÌ*ƒ´î•y‡ ¡Å…z^°N€‡å.øáB¦Ñœ—™í2xÝe©ýå%í¼5.;Áv+$BkœR…ûáPH½†+Ƥ™«Æ‘ß@˜`?‰ áô€²½SÕ]œBâV|tzpØCÒ‡bX‹8T³y™Kæ;ûTšM† ,¡C19ì°% B„à¼Ì´¸"aÉƾ/3W¥ ›"ëʇYÝfá5ö}æI‰,=²67ILÉŸ#À{$óL4V9§ ºµïV<‡›èßrnö6 d¼t_Ó@È –;׺náÚ0’¹!–¾I+B%ÃH‰šëF½fdZ ÊÈ/RÔd_ñäAêã€I‹WfrqµÿÎ++aŽšPY†Y¨$/‰ÛXmƒ¢V?®°WÖÊÌô }lÂl`À+X• 3Àã’e‘fG@‘Ïøo·ˆnñŸÒ:Æô,Ö¯ ‰\ $¥×fú/4J„¦Si!dßœ ¤É÷¨ýì£%êêЫ‡Vëœh”yí5»Oüßèl8'Ä«ï)h´ˆûÑâ({%FÇŠKç¶zª=v[`:ú£ Ï$k ÷Ï%FA]ãQ^¨EU YàœÒ +›_úóÕ£¯êý:éÈêÏ•ÂQU)GYT$Ï19T*Õ™¹ºÈ€Lö³}Æœ’_ü %î–Ò‘êŸNÔ,3ö=ëú$ß8†Tœ ìDãánr€DŸ¦™Xà@Æ2„Ȉá'Z¢‘{ è^qÝÔÖ^XDò¸Ï¯˜7ÜeâèÇökTÇd4…ÏÚ•p嫱Ç‘=Ösû³+^€IÏÔ—ŒœŠ¾gt`¬¯i4÷$ô**¢ik•9™®åM$ÍmÜ*¡,x˜R¿MPO“ŽT­ê²tÆ:åÀTGo•Ûïûê¢Fò0½':|ð¨Tnôe3/L-Þ*m¢ 4§¯¡²\êBO¥-³„âÖa·¾a‘ƒ+:7â×q(ËGè`‘ÕÆvŸ ÐGWH §?Ž÷uÏ4ë[í Æ*‚Ìo%äšøY)î@0Æ|¥¡³$€ƒ\‹Æ4p¥¹ ×B#í¿†:XÕ°Õy“¼àå(jq±S ªQ1%ÌÓ‘À7| 4T{Ö6ìgyTÏL2k}ë3Û(îå•aþÚ“Íûªs¤ ®òðÙ”N^5´JiG$ ‰  Á— ÆÞ æøù<•ÁUTÞ§åµI×å0D˜g_Š=áÃ^Ôóa¿¯šGöí‡_ ™Ö£„‚ ()Ì/;û©ófcS‡ s}¦W $!_ö]oBñ ·—‘î'*¨ÀQuW‚·Fªcø@‰0’¯ ˆ[”(‚èi2x‰¹|¼úwÉ1 vɹ‡skÃç¶S¬À‡£ÎƒL.ân«CÙå_í S5¿¶?É®¯Ú7 q?$ì¸Ò­gÃ,“ÑZh&[á9$@Gü•‹ ±Ï±Ç=³p–€Ù>&¡Ùv†>¤ƒ^lãá@`\S+.foÁ.‡]Ât mz©ÉQÎ}–å‚øú-~ÛQeb»ÇIýCÆš4…|²HƵÂa²Y}1áÊ|ŒÀ¸èÀø׬˓ºí?M;R—~Gä4˜I8ÉçV-±-tÊ]Xïáˆäè‰ÃÔ>;*îõòÃw'ñvÇÁ$4v$_J{Ñ'È_˜Ü[sÆuA,Öî)z+ÀÏßz ÚE…ñ·~Q4´ØÖÅIp¹;Ò/ÌÍÏ•GÏ<Éß­ÄnÆäsâv1ADS••RÝ°.¨ï~,îÒ†¸šfP"ðÏá‹èþ"cè’çæÉCrá –:ˆK Ä6c°È| »†#ó®)ÿ‹3Âa5éPrAƒæ½ B°¤‚Õ€»zâÊ oª …fÉ ‹êØÙÛ ïÎ ¼)ä±ÂDºCFIj–ÝfaD#˜e#õ\8bÔ¨>ËøVŠ¢ä³#ÓèîµØŽìÁS!Á ûV¸¥íªë®hˆ^ÕÈ0º#±xH"ײ~«àKלݤ·$ƒTĠ/[\wŽuº!t Ëîs{XA³Mëè"G\Ç{¿ bu³™!æÂí»Õ9¹¸I˜v­ñ­Ç#…Ù" r0iNÙRG74„WØcØ<å;L‹onQ$Õ@‡_…v]<_#¹8 |Múf–eÆ@P+ÒZa—;à%Ø>“¯¹ÙãçB؉¨c(G{SãgC§ŠøyZaPÊòvÅÌJƒ¤°+½a_VÏ×L¸§=ºÿÎà],^øÞ ÇÐ’@¤Ó®â Ev+«fs9ßLpª`xAHƼF`×mÞXÍ´^Ò ,tÁj¶æËÔœ- Ô§® Zö¤¢cŒDè7ñ ñAA?àÎd–ƒpü+)SÈnËó< JB Šç„ö^ü‚‚1¬ìÞÜO×[õ\çéOÀ »V¢bH €CåP:`WIé~é˜CXãS¨¡U72GάXÖµ–ÕEØ#’2tHEÕs`õwñ+Á–ÚD·=uÅ~bt[_NÈ«(vË‹l(Báꄽ<(CBÀB±À#À - ~ƒÆ],Õzù³•@˜Ú)›!ÖÇþ¯\|O_ÌOŠë·ð3øýáËFM-±‚÷Ê¡úãF¸Óˆ Iá6yÎuëŽ{pOY'"í’ÊäÜ-ìÌûÿ¤.°ý#dsç!ëáLGoÃv$Ž~øŽ]PN²{¾îNo`Èãobý…Ìøï«f,c÷ºƒê8gŠ¼3šsßJè»uôX,zL5‹!œ9·tüqðF5ú¬?XaéÐä·Û²Sµ+ó&3Åa&Ôã³ ÇHÀd7ªö‚t_$Ôn«D¶%DA¾*àHq*X=ñûÇOO¦ïOjúôßRŒ8xŠ$4VØu–|Q: ìü¤¥], 53åÍIaùøÉ0_&,:ÝœD=—œÆG –Ñò…1U^,QÓàë>ô¢Š Þ´ L‘¶5­@ˉâ*/^Én`11QU‚ùUksœ‹ìCxˆï¾‡G!r†æ6¸syxId~ÙÊD]­g>gÍXÄEÛy3Ãn©{±XÈÎó†ÉÈÐóÂHPôW¸½Ø> ßØ'è DÛò²™‡xE&¯"&k8ŒùD=œÞ'Ì!A´õþͱ-´¯òÐ4­Ô¸KS ÛŒTÀ»" ´-WïdH®öy]ˆ6ÅŽŽæ ˜y±g [@—WÙ@‰|¼ƒ`q£é_ºa1®)ŒÂ:l4s\Û/DÉ ±D/µ¦Öõ5IÊc U5¿ßÙZ‹êEMGŸÚí›N¬HÞ}ie¯“š¡kýh’q`j ¡’˜GOß Ðù„ù92¯CÇ'Ø…«:Ò Ù–„b`j ‰ü{ÃŽ]ìŠ1ËFÐ ‰«{@8ú‰wibºxV)Šæ+Q9ždf¦¯‚{@”b,";BšcDþÚQ‘·9üeˆNT&‘…Ë^Ïý2PoN06.6ñym·©«LÌB4â[äb†¡(*»NùBQ°¨TÌ"-᱇< Š 50‘´Æñ‚Øyv†[ˆ˜€âö¹ˆ¿aÛŸ«\_ËÐÜ&p4{d"É‚ˆZ½ªœä¥x9'ƒkÕìÉGñ`œZ”ûá¼DøqåÄ8 Šô#ØÌ8@ãD0A¬k†zD&âíqò¡Còž¥@7ÃŒvúþpADQV)@™è\Ö)P´­{×_\ã…îœ) €”i@Ó²£S»PnÌHa³¨>qaNBñP ë|¢T‘)$Æ¥•ë0çGÃ-* ¢"^ÞצLÿ,ìü¹B0}¡ çãüÊpB¸3P‡öŠÎÒ7ÕBÕ,XÈì q0Û;ÜŒ<x,Ì*;ç÷Œ/'>ê³rba¡b„(XËaiæÍkÅÊ.N‘LèÆÓÀ„vc̉çÎP|L(XIC‚“daLV$亡'?±Jê½J¨µýT,ŒªpÇ™ø%BøŻɬ|9YêcµÓ¢}áSã#6ŸRlÉ>Yx¹‚| ­ÛþP U¤8 4œ V ó†ÓþÆ¥CÛ´hè±Ð‘#×'*_ñàŠÖ½à!të.²¥¸¹ÇîŒÃçå+¯±"éÍš-zÂ_ˆF`P4À‹rûÚÓŠq•ùž¿}£èM€4Ë*ƒ0Ίc¯Ä!Ôˆ2'‚ÜàÜ…9®AEoJW¤´„wÆ;kÁÁ¹þùzxšs¸X¨mhbHtóhnHh?£Û¼;ÌMIz›:°öaÞ28z˜ÍЈ}òŠ’©DÓòÀ}†\Ÿ«ØìW¥šPþ…(5€óc‰À§ ¾„R}C(3ÎZé)Ä«»¢=±ð#ˆ¶ŠƒÁîÀ«‹ig‘6‰àæRœ  $qØšHØÎ,>,wÒáÙT]70‚Ñ¡(éÙ4m´ ¹%§p%Šë»]ÎŒÎÉ£w¸WN"%§Y8t>´G<yÕ!¾ËíÔJ,³þy«mÔ…­¢îáW”™’o6`S QÀÉkq% Ža5øg›ôc°ˆ¾DòßVñC÷œKõK*&(£ãdªjš8*€W ?ì{RU•3xÁíGhe?I‘K”°TºX˜äçÆ#FŽ›¤bÈæ#¼$…‚ø‘PÈɼP#^‹Áݵ]yœ¸áB:ˆ `xòÛÆK0Ÿ£© ÷”—ðü’  é´§k]të¿$4Ô¬xc¤ÿ?Ä¿àWÿI³ %‹Ã¹é¢@8[‚°nÍa(¬§p—c×FSdDôå3_ˈVv/3i^fbsxšÂýj3Òþã­õàY¥¹3lÜ4 Ó-°º–›E«Í=s\YÈïÐÞZª Á k]kñË4‘«êm§ì2pÕ¿Ê+¥ ~­qõ!Qª>ë¥ t»ŠwåÀ ý,\Ó›þlMs@“ý' yÈ¡8™hàISú:Õ0ÊìÖ’ßG›ØzK¿‚Ãnx‹–ËFólÁÛ„4™òná·8‘HIÄ œ½Á60~úªÕ!lÿ%øt ©ìºaÊ´¼úT.´R¢xeèN@¼òáÒp aÏ:æ»×i%¶C ÷-0{ó19LõK“l­KMÈ9Ôjô„I€—?iÑÄ•ÌFc?hÜY¼Áƒl l^ª:öö«þñZæ³mqé÷L®µîšÐÉ$ê*'fè X¯e<€·ôú¼MŒqAfŒ£wÖê%îÄëšaDUjZ"Ä2W°XØˆÝ GŸ X tp;ü)Ô?8hq(ô!–^)»wðN>€ÌÆF0µÉn†Slãÿ­C\[Ø,ÓS@S@cë…€CÂ>û÷»µ×`ù «ÿZcÿ4©ÐM,ÆçÒP÷Å­Í5¾„Éùb¸z-à¸6QvÉ8ä/æ@l™ÙËKn¥¶/$·0Ø9ýG•C£L\&ƒéfû}ê@bÍw,™IK9B *x”»É4Bï1"›kk«2ÚÃÂDIx ž0jäÇÁžå¼ÎnåíÊ07ãg‹» Ø”H.“S vªM\ &”k3•¸xO%"•±R$ÂF àË&^ê2Ÿ5z’5»ä& œÏÙ®ÆÝÝ"]ÈÐkH™¸¿xý&U/ï1Iö´¯VS{I^ÚÅ2ÆxšÜpøØÔ”Ö7¹g}BHäzÆ Îkw­.G§(˜D¨£Š± °Ýتmªñl„…Í3£õÖgžTIY¯—Öi5ª‡·"aLã±í¥B9 æÉå¬,(ž—Ž‡C+"›Ζgƒž\ýÒÓÆão§JJ“Sb<Ÿ%cûFh©·jÄ*Y¯ÌÊÚƒkb@º3M<3cµÏ½ù•ù4 Xî“JqyA„ï&EÊ4kÄf‘AÐ ð#é_¶Öå²q7È<_©Ðò” ·¼Û‘LÔŠŸö ™Ä1Y^Þê!¢ [—Gx‰vƒcúÃQ`!¦ð&ÙM{®ÕÒ0*n·N .˜ÐD˜‘¾éÓ*A:ôIÝòùèLáb;»(PxýÀÏœ Añ³ŽLÂmSªé©`ÿíë±àã¬Vº¹C®= n²±!²z¬+ÃJµA8HÖÿ=^Ñíƒvψ™9iˆ|ƒÆFtƆÕôAÕ †»ë‘½ˆñe&f'ƒÙ› Ô2|Å`',äÀ“þª3;²„‚(廨§Ïæ€  M|‡€`Û¹üŠÄ\k¨H^ÜV<†§æ0>ê‚@5÷¦]òPWóRz‡èÇiáÕ}ãf°‚æîhiÏ ÇHÛ¼DЙ[µQÁˆ)Ö¬ŠâdÓÒdö ×E üœÙí$Í š%JÈտZR)$s‘VàC”èy–…Ž-@Z6\êüç]è¥8¦ÄlŒ‹‹{´=Ç—4§DÂ;Aº}æïpš7 /;G[© BèH¢"íæ³2Ò)Ä~ÿ4-ÕoZ‚ë?1› Ä®ìVF÷²+DÇ"ÎÆÙTå+¬$z2ë.Àâ™93½‰³d;üÂâ!ë*U¥9Ì™/¥Âæ‡à£A¹#!ìD{âÁmÈ"~`Xºq ŒÜ×S¯EÇk0‘½º¢Ó·3²Îö^ j~€°ã±#뽸®Û>/1ÚX}nŠš‚š¨T9;¢÷qBSfÏòér³ "°fÖÌ÷;럘‘(û8[‰øŠå"SZ¸ †Ç­œ¶˜K`øO«4O!pd7X@N73ŸEÍP앃8r¨N#gm E†dÊ1ŠÖVçªÆn^Ä“,B¡,…»³ul®ñ&˜!œ˜ñ‚KlmӮѷE¦ÅCŠé|mêjŠ¯¯P­hÖ?Pö—Ì ¸¦`2ДȂ9z½¢Ë¨Cš4Aq¸³"À•¸‹)ÝŠŠjýOè%cÌwJ<ÂH­..,s+ÏÀZõßq&VMs^‚ÜÅq˜½&|-üí.Ò=,GÂbŒñæ\º0¿Šdõ Íœy#úó‰Û±—5^`}/ œÒx4ñ6QÁ ‡êü:‹ „ã_m™ê75_™—årì1§ì>E|€È 0:™MÀÎv”É}†„Cà ÉK—Ív!+Ì$GaÃSú{{ íkÌJü<’ /´‰;²‰’Wî4´¡º˜E<‡¯ Ö-kõ8ÌèÛ";#7tµÁ„ÿ ¬¯Öšû¨|®P»2¤r=äË x´=Æ®R‡Ï—/oubæÏ%bÓÝ/qOÅÿ[6[Éfµoh­ý•"x(°…€.Óß“@ æ Jìb¾€3n™®Õüçñ§­A T$h¡ðbZ®¤˜ž$üÀXêÌ Øåx¶;Zß7È£ŽÒúáŒwNDIS¡H„UùM›¥R1Ì#Éñuk¾˜Nt[&ZjwQåeì8²`sI0aVÆq„¯mø‘•x!²öš™Û9Éýÿ¾÷.¢#¾ÄPÅžOwìõ+“¥Ø <Œ1…5EöµéYS°ÿØæïÒÖœ ’ŠÓ ©ÿâ:cÓxGdô §–vf=îi— Çϼ!¾ËLÈ>®ÅžçIdW `ŠŽqbá ÿ‚>L.Kœ9OðÚ|‰×†±.Š1Ci6”¶8ÃûI²ÆÎ’eÒG'š»JLŽÒ[ÃYçŒv&+”¿PŒùYŸMaBM5¸Áb¤CçõUAËGm=PSÊ£%ÇÐ Ý jÌ@«–æ«™©ª³³eLè-¦V&uÆç-áË‘(åðL§ÀÚKâ  ¯ø4nGâìÀ¥æheªÉŽ¡Õgò;j¥™FîÍOÁ©g2c$xJ…È£­‘+X§0Mdf°¿Í®©€g*p•††¦|ùô£Z(F_ŒÀ'+^OÙf›š‘E„´õ¹iVÄšBsu•=²™²€„µyY"T,®T±? |z ˜ùlF?5ííµ> RlOO;Yj I?.°8¥ù6o&‡ñ3U‡¡áà™a”À ãï¬_ÝΕèÒ”L?áLV ò©-”É%šÆ•F¯дí†×&µ¡PžÈÃüY‚&˜Ãì ®Ó]WóPÄþH ê"•Õfÿ}?©ó“„b`õ'AvšÝ_# ¡€s\Ö¢ÑV§®‰9W‡¥Ù ˽¦Î3šÊŽ]æ”÷äqLíÃ?a~SNQÂt^0„j—vERÁòï̃ŒĵB ¬Rds›`óýõ'¼Aæ¸ÍV #“-*å V ¨hkT¾U­2 *K*Ýl ÃU£Ó<AiÑÙŸs$<‡ðèl÷Á“‡˜»àtؘ7þÁ&J+ê3Ÿ²?œêï,fùL‡¦“‰4ôÖ„+êÚ%sßÀ6³äy*m±†9PzË[(-ÁóCÁ;TjÙ.¼IQ‹o_kn‰TúêÌ¢@3hå“+zÅÛÏþ#£`­©ågªœ²vU”;p†nƒzhbýB‰b„#‘^@à€ïo\a‡=Ê]p=m4%ÁFi6²”õÄ®!æªÝ[Fö›ÝŽ%•»Z¡ðR…Ï{Í„òMÉHà‘}BQó^vym^= š¶rÇÏŽ{Š V²d¾ J>gÆ£™Ž­Tvn^Cäè€SúË„ºR(²¥pö’û ›Z‘!¨4±³Z0’(=Û²LYËŸî`FdÍŒ ˶/» p€Ëm#0ËñféÞ©öýÒº ütÏ£qe@[DZTæ .Æêy$Îßîó´ßrh`@=:'˜8Vª ÁÎV`å­°ÐKÁ1 GÁä}ê$70¹¢’†siYÂ2?z}JôAÙÌ„"wØZåø­zZwY  ïv'Hþ»ó6æ§Ä$8ĉØ?¶½i'ÙËEh¡¦}“ ¹¡Eb5ùçz_¾ñêS¢Ó¹R–ñõeqÅ X­Œ ±þJ ÔDhq >ú0Ã⹜º‚ /òÃP~‹ÀmàMÙ±6â–‚Ó“¡…’þ‡ÀÇ0q¦´²`1 ‘¡A›ƒüfÑf¾iþÅÕ¼6Ÿ$mÐ/ÊÐ¥æNµªpäªhµå‚ôÍnñC‚5¿¼V“«áKEKä<†|Fgh¥Øxäªêæµg: ·‡Ÿ#xüYëNnüu¸37ä€ûOÖBwvÓBîì-¸fz¡HËCÛŸ?ÁþD,h˜ÓúHð[ùLŠþx•t OY¦ö­`¯¯Àr¨÷ k¤¶$¬-ßØ3•Ù4§Û€d@H‚K)òûÂ-±CŠ:]mK@–æÉÀ«ÑØ›·fN3†ÿaZ Xc}{6c¥kùk /©››0•ÒTN ª¼¢Z]F,;´8 EÓÄJÏ)°zYø’—Êßp© (DB²0Ù©Gÿñ@ ®+™U5ˆN@äšp„Ÿ°ÀÇÝ-ÅâJpoðŽð%Òz9Îpí0lų°–I>"{b`þÞEØOè—‰$÷Ô® ÁœØÚi!‡ÓÈAlØ¡†\u,Aì××]=ò"Á/€i ±cô?ï¨ÖÔЗbY­$b#“ÑCá‘3ç×ûÜf*j ÈDF†êl|3b³IÅ)ïÿ np2‡ßëÄá+q¦±:&VÖò·‡¿wÁ·ÔIÔzÏU ™y:‘ŠÔ§W}6Õûf#–h’Kç±C#6òìnˆP·2J´Ï y†ì¾yÇ&‡±–>]€è8_ºB…¤pÏR `?gcFŠ¤9VŠ&$MùÄß`B^rUñyA}4'Íúöý᪊“nà 䉕ô{O.„rU^Ld!¨|€c#TnO$vÉ×€étÃpRÞw®’°Š ^Æl„ü*¼¯Û ƒÃ5ìL/¦Ù[˜õ(ßvãTõuÆ¡Ù3hH–—ˆàt;!dg‘ ò×êF$» ¼R‡Dn^e\»Wªœ/ÇkÑ_çÞÝ_œX£'jJM¦ L‘Z²ÙflÑ4è‘Ñ›F—ŽèŒª„`¿ÒìŸN$,-€ ²å)Hø½Á"ëï¨;6ÜÒÍ:vÐi'Z¬>úGÚæ(ñAp‹ãÁر5je‚ÞX¬!ÆD¢BØP• Í 9! •,¿øÓdTª°T…à†(fÌîÜhìêYXç sɆ8#GQÄF3Æ­nÏ7Þ•ÙbEtïm ¥ÒˆtΤ¤¼ÁùœÏÅúˆ@O‡¿Í×H2ÛTÀ߃ þvO¥t#åÙî=Ê$¡Åꆨòf4díO1 ų¤fÊê(#ªey€ t`Ãþ[¼¶Ê6%“¾úöWU’žwÒÅÂ\¤8*lÁ’8ÔQJ`(òøžBë#ßð\ˆ_¼ $ô;M°ÿ³þN÷=1N]áÒ ‰54«IM©>Áù¬(Ì 0Ìù ÕWѬ9º¡pª¸®ëã9lÃÀ¤uÝÎ`‡Tµü€•RÁš­ÜÊ+¦¿X[ †2[ž£ ¬9?SÊtå×£bvlËÄ‚5Æ?€ü.‘qúÍ\îá|"e§5¸ÌX³]wT’ɇÍê— ¢)Š/˜~ˆ›A|À]‚~§7ÕÛT}z/Ï ±åLÉÆCBX ¬g™#'g«0[Réöi*ƒy¬ñí»ÕádߢQ†ú)ô 'wDã­]±ôq”e÷%S_®|Tóµ­wpà?PŽÇi,¢ÛäÆiüí¾êL„QÍídÉH â ä#Ÿ«Ì2ºìÈG`êóŠŒ&áöá¯ÚÀio,™w€Ý¡ù%jâY°g«¢*Æð˜â§¨Þ&æ  ™¤ñC×ÏÀÚÇ'Ý  §™òÿœaš›Ši^­@[ ËX]Fªˆg ¡Ç1å̶4pïÅ%[Ëo¯P.fä,Î_Þ_KmÉ zí25 ؼà(Û)“ÈVÕäZ„5€yÛÀöˆx +³ill$hD`é8§•zF3d<^Ã,ï8³4ç{vÜØ~°åšp‹0‰fÆËp·ãÇHlF ©T¿€zPŠ0[l/«Zú´5f…Þ ­¯…ˆ¢ÍOÁ/˜¯=(T 7©Ð7øìTB¾{¸4·öèÔèÍq wÁì˜XÐ&ìc綒u_Ê™3™o¡–ëßNPM9˜Õ»UãëßÌŸcÀ Ä=<†ÏÒ]½ôR/˜*¡üŽØjïç_úÁÆAO¼?œ¨šg}Ž­™ 2Ç“¸åe8=yÈô6€ªk誽zˆR¸à¸ZfÄE䲩!EÝð6ôçp õ§nE€ñ­²^’(áëBiÕ’¾Ô'lKjöX£¸Wx6d[.Ë’¨3¡JQ¬Ý³ìY´n"ãúP%þ×d˜×Q¾WL€žCE.žÕ–ô*ÙØŽ_í½ÁVÎÕqJ£j‘TÇϯ<xúyø´‚);Œ‰­Z¨"ÑÈÐHG* ÕÁÛ‘Ä%hË­`w”™hójq°ž§—qA—w}7Pýݸ÷Sù‡ƒWÕàÂÐü6¼´¼ÃeUköBÍéÀW«©*B3&I(_ &t8¦îù,ÿ(GŠ:J+ä1¶xùâËlŽg€1â#È1]BŒÊÜìÆa÷-Hºë/7Z‹Ëà'i¬"^(óvPXs¡´êx‚xƒäIÒ»ÑTÚ/¤çO 5ðŽûA4Æ6r¼®h4­º‰£iöBOQh1%%‚ræ,ècáÚŽt¾S¸ßFÀú5 ¼Zz§ LìëØÜkøÒnŠ‘Èý† Ì<ȲE£Ã,ëí­K.Pð%³íÎH‰Xã\¨ôâ”ÀÍŸË[ÈÀ=n/ ½¬(|\ظ§" ÅÃõP3Ò@Þ| t’P ?A_-$qÝž¬³áñTÛ{„ªC•YµDˆ¨8tX½yˆàllPpšÒtvY-´þ¹Èd¡×K•CWîoòÏ ¢)ÄA:Ùg–ì)Ÿ»›Ð§ 5¬‰â˜¢bxÕL<1¯9g–q¿cÿ÷½Q8Pš¡Ì©PJƒv_ß\Ý’ rXâMá¶x‡XÊ:#­¹’"ø¹‚F‡„1Îñá}‹«ø×[²å_(3RF. ¡JŽ <gÎådT O{ÞÜõ“Àad‰Ei„LAèC›´s‚-˱è~5‘aŠó,7ÈÅåƒ+Ç°pƒ9µÞØ` $$¤vÙ‰öƨôñKQí|/¶«&âŠY¶~¼9œ’»‘*‡ç´ÑÊv-¨°a…ª[‹:UK‘‰¾EvY9µ&cPD).©&²uÂ$™Æ :'à9Ûü'ß0šó`li¨è~HFÛùì;uBÚò섾hçŠÈØà”è_âÙléî®áZ:h|Î;£Â»…²è×TDÿ:Ä2."pàT„–4cž/ëZÍ•í.D*oWvЀTÊ[T¹éA,¢IPd\ }/"ÔbmãØA ‰†c2¡ù‘S4z„μ 3p ð™ß5C <#õ¹$$2µÃD Q¬në-¨ÚVT²ª ®a¦o¦Š›$>ú¬ÊN·LkKèËkµõŽèÜb¹þñœŸ½sìt~¢Ÿr õ©±`Ã꟒WÓ¶. ‘ ¦"Á°Ô¸/êdàñêÆxB®ù8;Th6ZŒªãÐÿ$ÄB7;·’2Ie™ò„C7–y^—`™Ik7)â$”¡½­ÑŒùQËÝL˜¸ÙS}Ñ%«Í"q ÀM‰, ‹n•LºÜŠÏØssSñá°m¤.þÑüã!“¶-êR»cú’¶²@½k¢‹OÌtý¹zÇšЬ±OŽi¨æãê•;È)EoÙêíÜ€2kÔÆÛ³d]“z ÒŠSÈ Èî0’›¥…bÖ!˜0ÛªA× ½>XÃ¥ôš):Äl~+ƒæd4¢Dä6g©vøÃ8jéqÊs]|ÈÒ³JûwXÑ +,YŒ"æPj¼e½ý(tº™´Dv:¦è@œà¸4ÉÍ^ñýÍ«€ŒA-Äóà#nv;©M¼GêCKZYË6n2bÍvO9_åU†^˜èÁ|\`‹†þ À•“ ²K·“¨ÏwwèK¯‰åéG;#·EFè‰ÎH@àº!ÁK·Ž Úƈº­–Ù‰³.$¬kŒ§Ü;–£·X*°70¹&©¨œ»‰×¯™¬gvÝKJ(¥¸…†€*¹8¢²UK ÍÅ5’ŠüOcLKoNö„¤«’†ÎªD¥p!ì›d0z((MŒ fÀ•–‹ jTĵÔôb”X=lL@BŠ¤§ý…RH6]I5RÃ?pDVßF€xi øЧ—áèQ«TÔYÚÔ(Lj~~XóV0†‘‘bá\B.‚ɼa&Ö©m7FeüdÖQ¸S—Äõ7YÔµF;wìê¢zˆeÎŒ™ô:Ó>mMþO ôÂNŠàýcOQ?ß ˆ1Ný¿¦=ÿwu›Ìg#’ˆs³ÌTp¥¾»¨QŸ„®”â½3ŒJ(¥7Éã‘s»4ÉØ‘c/Üå> CüËg^¥c|!ÀéÇsIºœ¦/ø´¸µ®,à¯\JöPŒûÿPïÈÉ ¿=cFn„|è—ÿð°5#¹¬‹¹u*Ãg(Uè¼â2ß79Ô<ý,NÈEà~ÓZ×Xs6z-Ê%"‰æ…›Jä³/äàŠÙ"÷Ã’3¢{¾ãÆålE’Jïå„M‰âsÈ'—ƒ»NÖe‚~! ‡×a¯‹Z»1x@”ƒk`);Žl̤vy yM@+×gfÊ<û0ÖLZ†èc%xŠð}qãE“»ýpQÍH¼^a+!q£Ÿ\úí/]lž†©5•Ù€/½‹f»#¬€û/ T3ñ—{‰Ê¢€6hQÑܶYÔ°qt)U.­h*Ò„$YƒÂ·éÖôµ˜®öÒàÓzÀ %¥4Ðu„1]I±E\)ŸJæSCff2jt@þ³Y|õšÒ\Iô~U… æä"³œ™¿îVÞOe•-´çH¸ÈÈv®Å´ 4mE€"¾å€u¿‰"Ä ¹óI>• ¤:ZõÇ‘ÂÖOžÎ?÷ıÓò´î@»'QÜ•¥dk*iã[ÊÀp^|Çen-y=¢.åÄ«?'.‹^=tQðœmy2»„v„pã%t“ZE·Y,Öñ‰KtUíÎœÉ:‘áp!"¹‹ƒ4؛Ί_Ëo¶Pï² "aÈš/.ö· Y# ž¬'e†VãÉxĶAG˜Éo #šúÃ}€îi·²ôxrÉõºû|2?¹øë*»¡‡s(Øû P›áþ;ý#æ;m8ð’Ëñ9ëmÓJ³ÆÎaZf6oúŒÁØË}«O§A1ß¿· è"±y¼Å£›K¹õÞ?"†Ëè$ºî «bƒh-ÂwÌᶛévÒ+²^'Tð¿Å.i¶·ÐÙ¹`T‡8Zœ7­Ž”üÿM•5ª‰Á„_äÛC Ê ·;Œ†Ì;>tŒ{×êãÎ*ígì7W.Z㎙ÕÈÊœ¶ëÙJ™•(qKâ¿Y–àãÝ8Â):©Y—©Pb¦MwM4¾Þ«¤û ›;jK‚šcÒ-‰Ñn}‰΢>ÊÛ©²FˆX#Ñ.Ú¨DŽäi¯¬~©CÃba´3ªsŸ©©âÞC“–¢ùä­Ó_ÊyŠ 课hNÌ.˜‰f¾hãHØã.çQVÍ•Kc²¤Ç¶“Úq0öœc |ßKÞŽh×®Ž,àØ\^e/1œ­™Q¶¿=’fOè¥L9}r ÕiÅ3IÂÅC’P£I\ób5´nbÊÛ3Žxsw)1:3¿Ðzs,@¶ùÅ#®ÿb®–Æë• «´‹U‘×Èœ0*Ø™Æ) ØÃÚ Ò¡ l"IÊm0ôÆqÛý½Drô›Õ%,ÓWbgé!„pèFBÝži†À *ý6¹æ"8ÇUÉ(? ácȯ·­d6ÙîX$0ç˜Xl@š×eé™K>‚¬ÆmÈ’”ãرJVÊ°”HãPí`Fe½$¤zåÞ¤G£Ïêß „q³ „0Ñ[ö̆Œ=é·‘ïb¨²ßl³CöÆt‘+›d˜«‚•{Ì‚) ¼}xé$Žק³ ½&²¹…/¯iî6y¨ê5¸R§EŠFFÓ\³3cm=qú/aZRš¢¹õe% Ìýw?²ÊªV ¹(:JÝ‹™‹kèÆøÄ¢‚^2PZK%còêù&-«ÍÇF¦ì@K#Ɖ>%’°ŠMÕ9 N<ˆ‚V.-òl—ÃÔú^à%ŒXX¶‰½áh­Ñï¢jÌâ)<’bÝù} dyCVZ<éYô»hêæ¯ Î…#öУ±Ã†ÿÈ P'4z–ìÀjJÙÓƒOƒq®I€ÜÈû'߉$¦Od9¡@Õ¤RgFÊÛq† µÊ?—¯¹‘€»NOb£ý?ª­7UÐËý(ÜäœÕ' ¡3Se49n``„§•)o´ÜÌo&ÛJ{¤8´ “¦¶YÁ¢$ ôÂhØIbBó'Ú0æå¢Z“äxžƒ[B•¢”úžÃŒEõòÙ_OFÈ Àl+i5áœD²£­†ëº~ϵ±ÒO@JÍœU o¯ïzR§iÙ*Bž64gy"`<êSø”ÞÃg¡ùܼÉâŸiŠãfÙZ%÷Oç˜L'ëÁ*\LÒC¥P”\ä -sï, ®@•·'(  :ý Í€ansible-1.7.2/docsite/_themes/srtd/static/font/fontawesome_webfont.svg000066400000000000000000006023051241061774000262310ustar00rootroot00000000000000 ansible-1.7.2/docsite/_themes/srtd/static/font/fontawesome_webfont.ttf000066400000000000000000002323441241061774000262310ustar00rootroot00000000000000€`FFTMepaÑìGDEF´ OS/2‹z(`cmapé5°òˆjgaspôglyf2‡÷üÄhead\Ã"À6hhea ‚áø$hmtxÙìlocaqµê4maxpÝ!D name<eš!d¸post2Í¿$¾webfŒRQ¸4ÜÌ=¢ÏËT‚0ÍÞ<цáŒ3†Œ3sZ3pyrs@ õÿ# dHN@  ©®´Æ / _!"""`àððð>ðNð^ðnð~ðŽðžð®ð²ðÎðÞðîðþñññ.ñ>ñNñ^ñnñ~ñŽõÿÿ  ¨®´Æ / _!"""`àððð!ð@ðPð`ðpð€ðð ð°ðÀðÐðàððñññ ñ0ñ@ñPñ`ñpñ€õÿÿÿãÿdÿ]ÿYÿTÿCà ßæß·ÞõÝúݹ ÿþýüûúùø÷ † ÿÿp7!!!àÀþ@p p úpú1]ÿ£€!2#!"&463!&54>3!2£+ýˆ@&&ü€&&@ýˆ+$(€($F#+ýˆý&4&&4&x+#ÿ€+".4>32".4>32467632DhgZghDDhg-iWýDhgZghDDhg-iW&@ (8 û 2N++NdN+'íý;2N++NdN+'Ç3 8ÿ€€!  #"'#"$&6$ €þùþŽþùrL46$þ©³Üþû½oo½½o|W%rþùþŽþùþ€4L&V|o½½oo½þûܳþ©%ÿ€=M%+".'&%&'3!26<.#!";2>767>7#!"&5463!2€ %þôž3@m00m@3žþô%  À  ú@ “ÁÐ:"7..7":ÐÁ6]€^Bú@B^^BÀB^ $΄+0110+„Î$ý (   ¨t˜¥1%%1¥˜+‘`ûÀB^^B@B^^ÿ€€"'.54632>32š4ý #LoP$$Po>àþåý‘€Z$_dŽCÜø+I@$$@I+øÜÝåý¨ÿ­€à"#"'%#"&547&547%62€þ•Vþ?þ?Vþ”8öá<áö8yþžþ   ìì ôb% IÇ))þ9I ÿ­€à + % %#"'%#"&547&547%62q2þZ½½þZ2IzyÇþ•V)þ?þ?Vþ”8öá<áö8)>~þ‚>þ×þ[ÇÇ þžþ  2 ìì ôb% IÇ))þ9I ÿ€€€'%#!"&54>322>32 &6 €’yü–y’ 6Fe= BS…†…SB =eF6 þÀáþÂáá>ƒx‹‹x5eud_C(+5++5+(C_dueçþÂáá>á ÿ€€/?O_oŸ¯54&+";2654&+";2654&+";264&#!"3!2654&+";2654&+";264&#!"3!2654&+";2654&+";2654&+";267#!"&5463!2€&€&&€&&€&&€&&€&&€&&ý&&&ü&€&&€&€&€&&€&þ€&ý&&&€&€&&€&&€&&€&&€&&€&€^BùÀB^^B@B^@€&&€&&š€&&€&&š€&&€&&ý&&þ&&š€&&€&&ûš€&&€&&&&þ&&þš€&&€&&š€&&€&&š€&&€&&ºúÀB^^B@B^^€€/?#!"&5463!2#!"&5463!2#!"&5463!2#!"&5463!2L4þ4LL44LL4þ4LL44L€L4þ4LL44LL4þ4LL44Lþ€4LL4€4LLÌþ€4LL4€4LLüÌþ€4LL4€4LLÌþ€4LL4€4LL €/?O_o#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!28(þÀ(88(@(88(þÀ(88(@(8€8(þÀ(88(@(8ý€8(þÀ(88(@(8€8(þÀ(88(@(8€8(þÀ(88(@(8ý€8(þÀ(88(@(8€8(þÀ(88(@(88(þÀ(88(@(8 À(88(À(88ØÀ(88(À(88ýØÀ(88(À(88ØÀ(88(À(88ýØÀ(88(À(88ýØÀ(88(À(88ØÀ(88(À(88ýØÀ(88(À(88ØÀ(88(À(88€/?O_#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!28(þÀ(88(@(88(þÀ(88(@(88(ü@(88(À(8û8(þÀ(88(@(88(ü@(88(À(88(ü@(88(À(8 À(88(À(88ØÀ(88(À(88ýØÀ(88(À(88ØÀ(88(À(88ýØÀ(88(À(88ØÀ(88(À(88y‡²"/&4?62 62‡ý,ˆPˆþ–ˆP&PˆòPý,ˆˆjPˆþÙ‘ˆnÿî’#$"' "/&47 &4?62 62 ˆPþÚþÚPˆ&þÚˆP&&PˆþÚ&þPˆ&þÚˆP&&PˆþÚ&ˆPþÚþÚÿ€€#+D++"&=#"&=46;546;232  #"'#"$&6$  à @ à  à @ à €þùþŽþùrK56$þ©³Üþû½oo½½o|Wà@ à  à @ à  àærþùþŽþùþµjK&V|o½½oo½þûܳþ©ÿ€€0#!"&=463!2  #"'#"$&6$  ýÀ  @ €þùþŽþùrK56$þ©³Üþû½oo½½o|Wà@  @ ærþùþŽþùþµjK&V|o½½oo½þûܳþ©ÿ€)5 $&54762>54&'.7>"&5462zÎþäþÈþäÎz¡’+i *bkQŠ½Ð½ŠQkb* j*’¡ý€LhLLhL€œþäÎzzÎœ¶Bm +*i JÖyh½ŠQQŠ½hyÖJ i*+ mþ¾Jý€4LL4€4LLÿ€€/?O%+"&=46;2%+"&546;2%+"&546;2+"&546;2+"&546;2ÀÀ€ÀÀ€ÀÀ€ÀÀ€ÀÀ`ÀÀrþÀ@òýÀ@rü@Àòú@Àÿ€€n4&"2#"/+"&/&'#"'&'&547>7&/.=46?67&'&547>3267676;27632–Ô––Ô– ¹#H  Š,/ Þ1)  ~'H·  º(C ‘ Š,/ Þ1)Ž  $H· Ô––Ô–mÞ 6%2X  %Ž lˆ2 ¸k r6 [21 Þ ..9Q $ kˆ2 ¸k w3 [20ÿ€€€/;Cg+"&546;2+"&546;2+"&546;2!3!2>!'&'!+#!"&5#"&=463!7>3!2!2@@@@@@€ü€@ý`À0 þà o`^BüÀB^`5FN(@(NF5 ýÀ@ýÀ@ýÀ@ý´üL%%Ju  •@üLSyuS¸@§%44%§f5#!!!"&5465 7#"' '&/&6762546;2€&þ€ÿþ€&??ß>  ýLýL > Ï X ôÀÛ  þ &€þ€&àÚþ&AJ Aý¿ J WÌÃþh¶ÿ€€#3!!"&5!!&'&'#!"&5463!2€þ`(8þ€x þÇ 8(ûÀ(88(€(`8(8( þ€ 9 þhü€(88(@(8(þÈ`ÿ€€ ,#!"&=46;46;2.  6 $$ €þÀà@ ’úþØú’’ú(úrÎþŸþ^þŸÎÎa¢aàþ@@`ýþ(ú’’úþØú’’_þ^þŸÎÎa¢aÎÎ2NC5.+";26#!26'.#!"3!"547>3!";26/.#!2W º  ô ö.ý@  þð  ý@.¡$S  ¦  S$¡@  þÀ þ9I   ÿ I6> ÀÀ ûì>€%=$4&"2$4&"2#!"&5463!2?!2"'&763!463!2!2&4&&4&&4&&4¦8(ú@(88(ч:œ:ˆÐ(8þ»þ@6þ@*&&*¦4&&4&&4&&4& þÀ(88(@(8ˆ88ˆ8)þ@À)'À&&þ@ÿ€€$0"'&76;46;232  >& $$ ` þÁ  þÀÀÀÀÌþØú’’ú(ú’’rÎþŸþ^þŸÎÎa¢a` þÁ @`þ 2’úþØú’’ú(ú½þ^þŸÎÎa¢aÎÎÿ€€$0++"&5#"&54762  >& $$ ^ÀÀÀ ?  @ÒþØú’’ú(ú’’rÎþŸþ^þŸÎÎa¢a”þ ` ? þÀù’úþØú’’ú(ú½þ^þŸÎÎa¢aÎÎ #!.'!!!%#!"&547>3!2ÿ<Ôý<Ô<_@`&ú€&î 5@5 î@ ðþ À¢þ&&â>=(""ýØ=ÿ€€'#"'&5476.  6 $$   ýà !  ’úþØú’’ú(úrÎþŸþ^þŸÎÎa¢a¥JþÀ %€%þÀË(ú’’úþØú’’_þ^þŸÎÎa¢aÎÎÿ€€3#!"'&?&#"3267672#"$&6$3276&þ@*Š”Éh½ŠQQŠ½hwÔI ‰ mþʬœþäÎzzÎœ“k‚)'þ@&('Š‰QŠ½Ð½ŠQh_  Š „‘zÎ8Îzoeÿ€€$G!"$'"&5463!23267676;2#!"&4?&#"+"&=!2762ç@þhþî’þïk4&&À&‰G´a†èF *À &þ@&Š”ɆèF *Ç Aš’k‚4&àþôþ³nf&À&&4‰BH‚rdþ@&&4Š‰‚rd  Moe&€/?O_o+"&=46;25+"&=46;25+"&=46;2#!"&=463!25#!"&=463!25#!"&=463!24&#!"3!26#!"&5463!2€ @  @  @  @  @  @ € ü@  À  ü@  À  ü@  À € ú@  À €^Bú@B^^BÀB^`@  @ ó@  @ ó@  @ ýó@  @ ó@  @ ó@  @ ý3@  üÀ MûÀB^^B@B^^€€!54&"#!"&546;54 32@–Ô–@8(ü@(88( p (8Àj––jþàýÀ(88(@(8À¸þø¸À8@ÿ€€7+"&5&5462#".#"#"&5476763232>32@@ @ @KjKÀך=}\‹IÀþð&:ì¹kº~&26]S &H&û  ò&H5KKuýt,4,’ &æ x:;*4*&€€K#+"&546;227654$ >3546;2+"&="&/&546$ €<¹‰X@@Gv"D°þ×þ²þ×°D"vG@@X‰¹<†à4L4à†Š¦”1!Sk @ G< _b”œœþú”b_ 4.54632&4þ³þú&&M4&€UF &""""& F ûÀ&M&€&M&þ˜ƒ%.D.%ÿ¹€G-Ik"'!"&5463!62#"&54>4.54632#"&54767>4&'&'&54632#"&547>7676'&'.'&54632&4þ³þú&&M4&€UF &""""& FUªŒ &'8JSSJ8'& ŒªþÓ &'.${ŠŠ{$.'& Ó ûÀ&M&€&M&þ˜ƒ%.D.%7þÎþý;&'6£¸£6'&;¶þ4þ[&$ [2[ $&[ €€ #/37#5#5!#5!!!!!!!#5!#5!5##!35!!!€€€€€€ü€€þ€€þ€€þ€ÿý€€€€€€þ€€€€€ý€ý€€ý€€€€€€€€ü€€þ€€ý€ý€€þ€€€€þ€€þ€€€€ý€€ý€€€ #'+/37;?3#3#3#3#3#3#3#3#3#3#3#3#3#3#3#3#3???? ^>>~??????~??~??^??½^^? ^??€úúúúúúúúúúúúúúú€€ÿ•ë€4&"2#"'.5463!2ÀKjKKjv%þ'45%ý5&5L4 5€&Ë% jKKjKþ@5%þ%%Ì%€5 4L5&ý6'ÿ•k€54&"2#"'.5463!2#"&'654'.#32ÀKjKKjv%þ'45%ý5&5L4 5€&Ë%€%þ'4$.Ö%%ý5&€5à5€&Ë% jKKjKþ@5%þ%%Ì%€5 4L5&ý6'45%þ%Ö%54'Ê&55&ý6' ÿ€y€Tdt#!"&'&74676&7>7>76&7>7>76&7>7>76&7>7>63!2#!"3!2676'3!26?6&#!"3!26?6&#!"g(þísAüeM ,*$/ !'& ùJPþî$G]ü› x›6,&ûí `  ý  h `  ý  "9Hüv@WkNC<.  &k& ( "$p" . #u&#  %!' pJüvwEFÛ#  @  þÀ  @  ÿ—€2#"' #"'.546763Œ!''!0#þGþG$/!''!€ 8"ú÷"8  ¨þX! 8" "8 ÿ€€€ <)!!#"&=!4&"27+#!"&=#"&546;463!232€€ü€€ (8ý€€&4&&4¦ à8(ü@(8à qO@8( (`˜(@Oq€€8( ý&4&&4&@þ`  (88(   Oq (8(˜`(ÿqÿ€€!)2"&42#!"&546;7>3!2  Iî©©î©àj––jú€j––jà3e55e3ýgrþùþŽþù`©î©©îI–jü€j––j€j–ˆ1GG1ˆû€rþùþŽÿ€€€ Q37&'&#7676767;"'&#"4?6764/%2"%ÕªI¡M <5ý:YíK5 Íg'9') //8Pp]`O8È:ƒ8 /\þ>KM'Bþå0QÑþ>_’„ûþO 4hÔþ ò7f…:jCR1'  -! räAÑ@   ÿ€€€%e%3267654'&'&#"32654'&#"767676765'&'&'&'&/-72632;2/&+L@ƒª%&):SP§J+B¯²UT«4Nýä-M.   3T|-)JXg+59-,*@?|±Z\2BJI‚RtÅTÖ! RHForB^ ­þòÍ‚ŸpKK ,!zb+üe^  B€ñ”W  S  //rAFt/9)ij‚LU>7H$$ ÿ€€J767676?7>5?5&'&'7327>3"#"'&/&IL( 8  )g ='"B”!F76@% ,=&+ @7$ ~Æ)…J~U%@‹ @,Q5(?‡2&g  9,&ÇkþÉžë-   ÿ€ú€i…;?!6?2&'.'&'&"#"2#"'&#"#&5'56767676'&64&'&'&#"#&'52"/&6;#"&?62+Q6¿‚s×%"* ' Gˆ+"!  1( 8nMH¦X‘0:‹ &n+r  , Ð!~:~!PP!~:~!P5d: +UM6a'˜þ´þ™“.'  -   !& #Àñ¬>q\ 0f!)Vû%¢¢%%¢¢%üÿ†€h„;?!6?2&'.'&'&"#"52#"'&#"#&5'56767676''&'&'&#"#&'5&=!/&4?6!546Q6¿‚s¾>"* ' g®)^!  1( 8nMH¦R—-:‹ &n2í  , á¢%ü%¢¢%%5d: +UM6a'˜4þ™“.'  -    !& #‰(,  0f!)Vúó:~!PP!~:~!PP!€/?%#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2&ù€&&€&þ€&û&&&&ú&&&þ€&û€&&€&À€&&€&&f€&&€&&f€&&€&&f€&&€&&€/?%#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2&ù€&&€&þ€&ü€&&€&&ú€&&€&þ€&ý€&&€&À€&&€&&f€&&€&&f€&&€&&f€&&€&&€/?%#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2&ù€&&€&&û&&&&ú&&&&û€&&€&À€&&€&&f€&&€&&f€&&€&&f€&&€&&€/?%#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2&ù€&&€&&ù€&&€&&ù€&&€&&ù€&&€&À€&&€&&f€&&€&&f€&&€&&f€&&€&&€/?O_o%+"&=46;2+"&=46;2+"&=46;2#!"&=463!2+"&=46;2#!"&=463!2#!"&=463!2#!"&=463!2 À  À  À  À  À  À  úÀ  @ ú À  À  úÀ  @  úÀ  @  úÀ  @ àÀ  À sÀ  À sÀ  À üóÀ  À sÀ  À üóÀ  À sÀ  À sÀ  À €/?O#"'&47632#!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2€  þà   € ù@  À  ûÀ  @  ûÀ  @  ù@  À àýÀ     üóÀ  À sÀ  À sÀ  À sÀ  À €/?O#"&54632 #!"&=463!2#!"&=463!2#!"&=463!2#!"&=463!2` þà     © ù@  À  ûÀ  @  ûÀ  @  ù@  À Î þà  @  þàþ À  À sÀ  À sÀ  À sÀ  À #"'#!"&5463!2632' þm©wý@w©©wÀw©“ ' ûÀ*“¦w©©wÀw©©w¥’ÿ€€€."&462!5 !"3!2654&#!"&5463!2€p pp pú€@ ùÀ  @ “^BùÀB^^B@B^ pp pýÀþ@À@   û@  À  û@B^^BÀB^^ÿ€ëk%!7'34#"3276' !7632k[ë[€v ýâ 6 üÀþ`ë%¦þ`¦$65&ë%[ë[k€ ýâ Êþ`üÀ à5%¦ ¥&&ê'ÿ€€4&"2"&'&54 –Ô––Ô–!þ”?H?þ“!,¨,Ô––Ô–mFüú!&&!FmÔ,þÔÿ€€%" $$ ”ú’’ú”ÎþŸþ^þŸÎÎa¢a`@’úþØú’ñþ^þŸÎÎa¢aÎÎÀ-4'.'&"26% 547>7>2"KjKþÔþXþÔQqYn 243nYqQ€$!+!77!+!$5KKµÔþÔ,Ô‘‚ £‹Ù]""]Ù‹£ ø€9>H7'3&7#!"&5463!2'&#!"3!26=4?6 !762xt˜t` þ¢ ^Q©wüÀw©©w@?6 1üÀB^^B@B^ @(` ý`þà\\þà\P˜`t˜t8`À þ¢ ^ýϾw©©w@w© 1^BüÀB^^B~ @Íþàý` \ \˜P€+Z#!"&5463!12+"3!26=47676#"'&=# #"'.54>;547632€©wüÀw©©wÿ M8 pB^^B@B^íþ€ ' þ½sw- 9*##;NoŠµj ' €#þýw©©w@w© "^BüÀB^^BÖ  Üþ€*Àƒ‰þ°  "g`„81T`PSA:'À*þ€4€/D#!"&5463!2#"'&#!"3!26=4?632"'&4?62 62€©wüÀw©©w@?6 1 üÀB^^B@B^ @ çüÒBþRnB‡Bn^þÂw©©w@w© 1 ^BüÀB^^Bþ @ ÔüÒ®Bnþù‡nBÿC"&=!32"'&46;!"'&4762!#"&4762+!5462ÿ4&þ€€&ÿ4ÿ&€þ€&4ÿ4&€€&4&€€&4š4ÿ&€þ€&4ÿ4&€€&4&€€&4ÿ4&þ€€&ÿÿ€€6'&'+"&546;267Óý: &€&&€& s ú@ Æ ýZ&&€&&ýZ ÿ€€+6'&''&'+"&546;267667Óý: ý: &€&&€& Æ s ú@ Æ ý: Æ ýZ&&€&&ýZ Æ ý: zÿ€€€6'&''&47667Sý:ý:Æs ú@ Æ ý: Æ4Æ ý: ÿ|„ &546húÐ!!0aý À ý $ÿ€€#!"&5463!2#!"&5463!2&þ&&&ü€&þ&&&@ú€&&€&&ú€&&€&&ÿ€€#!"&5463!2&ú€&&€&@ú€&&€&&ÿ€€&54646&5-ÆÆý:s À ý: Æ ý:4ý: Æ ÿ€€+&5464646;2+"&5&5-ÆÆ&€&&€&ý:s À ý: Æ ý: ¦&&ú€&&¦ ý: Æ ÿ€€&54646;2+"&5-Æ&€&&€&s À ý: ¦&&ú€&&¦  62#!"&!"&5463!2Æ4Æ ú@ Æú€&&€&&-Æý:ýæ&&&ÿ&5ÿ¶ Ë&4762 "æýt%%Œ%k%K%%þæ%%K%k%‹%k%‹%%K%k%þþ&j%K%uÿµKË"/&547 &54?62K%ýt%j%L%%æþ%%L$l$Œ%À4'ýu%%K'45%æå'45%K&&ýu%ÿ€€#/54&#!4&+"!"3!;265!26 $$ À&ÿ&€&ÿ&&&€&&@ÎþŸþ^þŸÎÎa¢a@€&&&ÿ&€&ÿ&&&+þ^þŸÎÎa¢aÎÎÿ€€54&#!"3!26 $$ À&ý&&&@ÎþŸþ^þŸÎÎa¢a@€&&€&&+þ^þŸÎÎa¢aÎÎÿ€€+74/7654/&#"'&#"32?32?6 $$ }µµZµµZµµZµµZƒÎþŸþ^þŸÎÎa¢ažµµZµµZµµZµµZÎþ^þŸÎÎa¢aÎÎÿ€€#4/&"'&"327> $$ [4þhâ4[jüÎþŸþ^þŸÎÎa¢a"ZþiâZþ–Jþ^þŸÎÎa¢aÎÎÿ€€:F%54&+";264.#"32767632;265467>$ $$ €ÀÀo¦Wó€„  5!"40K(0?iÀ+! ":€ÎþŸþ^þŸÎÎa¢a ÀÀ®X–RÕd D4!&.uC$=1/J=þ^þŸÎÎa¢aÎÎÿ€€.:%54&+4&#!";#"3!2654&+";26 $$ `þÀ``À€ÀÀ€ÎþŸþ^þŸÎÎa¢a   þÀ Ž  Áþ^þŸÎÎa¢aÎÎÿ€€/_#"&=46;.'+"&=32+546;2>++"&=.'#"&=46;>7546;232­m&&m ¡l&€&l¡ m&&m ¡l&€&l¡s&%ë¡&€&¡ë%&&%ë¡&€&¡ë%&&€&l¡ m&&m ¡l&€&l¡ m&&m ¡,€&¡ë%&&%ë¡&€&¡ë%&&%ë¡&ÿ€€#/;"/"/&4?'&4?627626.  6 $$ I’  ‰‰  ’ ‰‰ ’  ‰‰  ’ ‰‰ Í’úþØú’’ú(úrÎþŸþ^þŸÎÎa¢aÉ’ ‰‰ ’  ‰‰  ’ ‰‰ ’  ‰‰ (ú’’úþØú’’_þ^þŸÎÎa¢aÎÎÿ€€ , "'&4?6262.  6 $$ “þZ4þÚf4“4fz’úþØú’’ú(úrÎþŸþ^þŸÎÎa¢aÓþZ&4f“f4ú(ú’’úþØú’’_þ^þŸÎÎa¢aÎÎÿ€… "4'32>&#" $&6$  Wý‰ oÉ’Vü󇥔ú’ zÍþãþÈþãÍzzÍ8̓¡†ýYW’˼ò[’ü”¢?þÆþâÎzzÎ:ÎzzÎ@ÿ5K #!#"'&547632!2A4ý@%&&K%54'ýu%%‹&54&K&&þÛÀ4A€€5KþÚ$l$L%%Œ%54'Š&&J&j&þÛKÿ5ÀK #"/&47!"&=463!&4?632À%ýu'43'K&&%ý@4AA4ÀþÛ&&K&45&‹%@6%ýu%%K&j&%K5€5K&$l$K&&ýu#5ÿ€K@!#"'+"&5"/&547632K%K&56$þÚK5€5KþÚ$l$K&&‹#76%‹%53'K&&%ý@4AA4ÀþÛ&&K&45&‹%%ýu'5ÿµK€"#"'&54?63246;2632K%ýu'45%ýu&&J'45%&L4€4L&%54'K%À5%ýt%%Œ$65&K%%þÚÀ4LL4ý@&%%K'ÿ€À,"&5#"#"'.'547!3462þ4&àb›™qb>#  5¢Éà&4š4þ& 6Uu e7D#  "¦Ç†“&þÿ€€/#!"&546262"/"/&47'&463!2ó þ´&þ@&&4L  r&4þ´  r L&À&í þ´4&&À&L rIþ@&þ´ r  L4&& ÿós/"/"/&47'&463!2#!"&546262&4þ´  r L&À&ó þ´&þ@&&4L  r@þ@&þ´ r  L4&&“ þ´4&&À&L r€€##!+"&5!"&=463!46;2!2€8(þ`8(À(8þ`(88( 8(À(8 (8 À(8þ`(88( 8(À(8 (88(þ`8€€#!"&=463!2€8(û@(88(À(8 À(88(À(88zÿ€€5'%+"&5&/&67-.?>46;2%6Ê.@g.þöL4€4Lþö.g@. þö.@g. L4€4L .g@.þöæg.n.™þÍ4LL43™.n.gššg.n.™34LL4þÍ™.n.gšÿ€€ -  $54&+";264'&+";26/¢aÎÎþŸþ^þŸÎβ À  À  Ü ¹€ÎþŸþ^þŸÎÎa¢aûï¾ ¾ fm  ý“ @ J%55!;263'&#"$4&#"32+#!"&5#"&5463!"&46327632#!2 þÀ$À$þ8Ã~+(88Ø8(+}Â(°`8(ûÀ(8`¸]ƒƒ]k=€€=k]ƒƒ]¸´8ÔÀÀþ,8e¡8P88P8¡ þÀþ`(88( @ƒºƒM¥¥Mƒºƒ€O4&#"327>76$32#"'.#"#".'.54>54&'&54>7>7>32&¬þÜãz&^‰¶&.þëÛÖà”Š’/+>*>J> W—¾m7´³²•' '"''? &4&c©‡&^|h_bàþÂml/J@L@ #M6:D 35sÒŸw$ '% ' \„tÿ€3#!"&=463!2'.54>54''€ úÀ  @ ÿ1O``O1CZŒ‰Z71O``O1BZŒ‰Z7 @  @ N„]SHH[3`€)Tt¬bN„]SHH[3^‚)Tt¬€!1&' 547 $4&#"2654632 '&476 €˜å=þùþŽþù=嘅‘Ô‘ýµ}³(zVlŒþ'ýòþ'ŒŒÙÙŒ@ìuhy¹þù¹yhuìÍóó9(³}VzþÒD#æþëå#D#åþêåÿ à =CU%7.5474&#"2654632%#"'&547.'&476!27632#76$7&'7+NWb=嘧‰}³(zV‡iþ\j1  z,ñX™Æ Y[6 $!%ž‚À'F–þuÞJÔiys§?_¯9É?Àkyhuìþþn(³}Vzï¼ý ½YF  KA؉Lëa  þ0‹å2ö-„F"@Q¬¾„î¼³sp@²_ÿ€ð!3%54&+";264'&+";26#!"&'&7>2 À  À  Ü ¹ #%;"ú";%#`,@L¡ € þéþý5 `  ½ü  ` Âþ €™ LÀ`4ÀL¡ýH` üþýÂ`  ü½ a 5 € Ÿ L@ÿ€ #37;?Os!!!!%!!!!%!!!!!!!!%!!4&+";26!!%!!!!74&+";26%#!"&546;546;2!546;232€ þà`@þÀþ  þà`@þÀþ  þàà@þÀþ€@þÀ þàþ€@þÀþ  @  @ à þàþ€@þÀ€ þà  @  @ €L4ú€4LL4€^B@B^€^B@B^€4L€ þà @@þÀ@@ ü À ü @@   þà ü­@@ þà À  þà Mû4LL44L`B^^B``B^^B`Lÿ à7q.+"&=46;2#"&=".'673!54632#"&=!"+"&=46;2>767>3!54632š7>7&54>$32ðþdôFKÆþú1A  0) µŽðL¶ôœ.þ¤þÙ«¯C58.H(Y–‚í¬e«ÿ€€#3C $=463!22>=463!2#!"&5463!2#!"&5463!2Åþ¡þHþ¡Å&€&/7#"&463!2!2€KjKKjËKjKKjË ûì˜&&ü&%±Ì&& ±&5jKKjKKjKKjKÀþ%z 0&4&&3D7&4& %&€€#!"&5463!2!2€„\û@\„„\@\„ \„ ý@\„„\À\„„\ „W€*#!"&547>3!2!"4&5463!2!2Wþ°+›BûÀ"5P+›B@"5þ©üÀ^Î=þ¯„\@\„ \„H#þt3G#Œ3G: _HþtÀ\„„\ „@ÿÀ+32"'&46;#"&4762À&€€&ÿ4ÿ&€€&4Ú4&ü&4ÿ4&&4ÿ@À"&=!"'&4762!5462ÿ4&ü&4ÿ4&&4š4ÿ&€€&4&€€&ÿÿ€€€ /!!!!4&#!"3!26#!"&5463!2ÿ€ÿ€ÿ€ÿ€ ùÀ  @ €^BùÀB^^B@B^þ€€ü€€ÿý€€€üû À  û@ Íû@B^^BÀB^^ÿ€€0@67&#".'&'#"'#"'32>54'6#!"&5463!28ADAE=\W{âO[/5dI kDt‘”®pÄŒe1?*©wü@w©©wÀw©ž (M& B{Wta28r=Ku?RZ^Gw›©T -ü@w©©wÀw©©ÿ€€#7#546;5#"#3!#!"&5463!2Æ8n¯˜„ƒƒ”©wü@w©©wÀw©jÛm1'ÛƒÛý…{öü@w©©wÀw©©ÿ€€#'.>4&#"26546326"&462!5!&  !5!!=!!%#!"&5463!2 B^8(ò–Ô––Ôü–ú€áþÂáá>üá€þ€€üÄ@ý|€K5ú5KK55K²^B(8Ô––Ô–ü€>ááþÂá€þÀvŠ€€û5KK55KKÿH“€G4&"&#"2654'32#".'#"'#"&54$327.54632@p p)*Ppp p)*PÃb '"+`ÜN*(ýa°½£Í¾2 £Íƒc`." b PTY9° ppP*)p ppP*)þb ".`Ü(*NŸƒÍ£ 2¾Í£½°þ`+"' b MRZBÿ€ð½û4&"24&"264&"26#"/+"&/&'#"'&547>7&/.=46?67&'&547>3267676;27632#"&'"'#"'&547&'&=4767&547>32626?2#"&'"'#"'&547&'&=4767&547>32626?2€–Ô––Ô–LhLKjKLhLKjKþ€ › "8w s%( º ")v  > ˜  › "8x s"+ º ")v  < ˜ €• 3zLLz3 •• 3>8L3)x3 •• 3zLLz3 •• 3>8L3)x3 •Ô––Ô–ÿ4LL45KK54LL45KKþ¹ #)0C wZ l/ ™ Y… N,& ¹ #)0C vZl. ™ Y… L0"ýàŒqG^^GqŒq$ ]G)FqðŒqG^^GqŒq$ ]G)Fqÿ€%O#"'#"&'&4>7>7.546$ '&'&'# '32$7>54'€¼þ»¿VZ|š$2 $ |Ž¼E~E<Ž| $ 2$š|ZVþñÉ:¡(t}†–‹þêì‰X(  &%(HÒw‹ì‰‰ý‰xÑH(%& (X„ZT\ð†MKGÖÿ€<m$4&"24&#!4654&#+32;254'>4'654&'>7+"&'&#!"&5463!6767>763232&4&&4¦N2þ `@`%)7&,$)' %/0ÓƒyÀ#5 +€1 &<¬$]`»{tþà5KK5$e:1&+'3T†F0°h˜¦4&&4&€3M:Ë;b^v…+D2 5#$ý€I§IJ 2E=\$YJ!$MCeM‹¡-+(K5€5KƒK5y„*%AŠu]c˜ÿ€=p4&"24&'>54'64&'654&+"+322654&5!267+#"'.'&'&'!"&5463!27>;2&4&&4¦+ 5#bW€ƒÓ0/% ')$,&7)%`@``2N€˜h°0##†T3'"( 0;e$þî5KK5 t€¾ipŒ­<& 1&4&&4&þ#\=E2 JIURIý€$#5 2D+…v^b;Ë:M2g˜c]vDEA%!bSV2MƒK5€5K(,,ž‰MeCM$!Jÿ­@à#"&547&547%6@þ?Vþ”8öáàúÅì ôb% IÇ)ÿ€€94.""'." 67"'.54632>32€+C`\hxeH>Hexh\`C+»ED¼€åý‘4ý #LoP$$Po>àþ¬Q|I.3MCCM3.I|Q¨»ýÐ/¼¨Ýåý¨Z$_dŽCÜø+I@$$@I+ø (@%#!"&5463!2#!"3!:"&5!"&5463!462€ þÀw©©w@  þÀB^^B   ýà4&þ@&&À&4 `  ©wÀw©   ^Bý@B^ 24ýà& &€& &ýàÿ€€%573#7.";2634&#"35#347>32#!"&5463!2íççöFtIG9;HIç’xˆIçç<,tÔ©wü@w©©wÀw©z¶Ö4DD43EEü§ŽšžueBýŒ„&#1sü@w©©wÀw©©ÿ€€ .4&"26#!+"'!"&5463"&463!2#2à &þS3 Lþl&c4LL4€4LL4c Àþ@þ®&þ å&{ÅLhLLhLþÅ'?#!"&5463!2#!"3!26546;2"/"/&47'&463!2€©wüÀw©©wÀý@B^^B@B^@€&4°ýt  r Œ°&&`þÀw©©w@w©@^BüÀB^^B@Rþ&°ýt r  Œ°4&&@"&5!"&5463!462 #!"&54&>3!2654&#!*.54&>3!2 ýà4&þ@&&À&4 s©wþÀ  @B^^Bþà  @w©š4ýà& &€& &ýà3ý@w©   ^BÀB^   ©ÿ€€€ I&5!%5!>732#!"&=4632654&'&'.=463!5463!2!2ÊJÿ½ÃÿJ½€SÍq*5&=CKuüÀuKC=&5*qÍS8( ^B@B^ (8¢Ñ`N¨ö`Ñ¢¨Î€GtO6)"M36J[E@@E[J63M")6OtG€(8`B^^B`8ÿ€€%-3%'&76'&76''&76'&76'&6#5436&76+".=4'>54'6'&&"."&'./"?+"&5463!2Š  2  5    z<: Æ©wà 49[aA)O%-j'&]Æ]5r,%O)@a[9( 0BA; + >HCàw©©wÀw©¸  5 /)  u    ±ü@w©ïa-6OƒUyU[q ( - q[UyU‚P6$C +) (  8&/ &‚©wÀw©©ÿ€€À'?$4&"2$4&"2#!"&5463!3!267!2#!#!"&5!"'&762&4&&4&&4&&4¦8(ú@(88(«c==c«(8þ»*ÿ&ÿ&ÿ*À6À&4&&4&&4&&4& þÀ(88(@(88HH88`(þ@&&À('Àþ@ÿ€ÿ€1d4&'.54654'&#"#"&#"32632327>7#"&#"#"&54654&54>76763232632   N<è;+gC8‰A`1a9á9µgÕw€Œü›|Ê9â8aIe$I€VNšÂz<ç:LQJ  Æ,‹-[% 061Iéï( )W,$-׋¥þ»û7,oIX(¡)oÕζA;=N0 eTZ  (€€O#".'&'&'&'.54767>3232>32€ e^\3@P bM€þïO0# 382W# & 9C9 Lĉ" 82<*9FF(W283 #0O€Mb P@3\^e FF9*<28 "‰ÄL 9C9 & #€€!"3!2654&#!"&5463!2`üÀB^^B@B^^Þ©wüÀw©©w@w©^BüÀB^^B@B^ üÀw©©w@w©©ÿ—€#!72#"' #"'.546763€ü§YY§ !''!0#þGþG$/!''!û&–UUþjZ 8"ú÷"8  ¨þX! 8" "8 ÿ€€EU4'./.#"#".'.'.54>54.'.#"32676#!"&5463!2G55 :8 c7 )1)  05.D <9¤0)$9“©wü@w©©wÀw©W + AB 7c  )$+ -.1 “9$)0¤þÇ< D.59ü@w©©wÀw©©,T1# '327.'327.=.547&54632676TC_L›ÖþÒ¬þñá#+á°i¦!+*p“DNBN,y[ƽ†Œ`m`%i]hbE‚þýî·m‘Š}a ±u&,ŽSXK•³ &$†½f9s? ÿ€ð!#!#3546;#"ÿãþ«ªª¬ÅãŽ'/ÔþäüÈ8«¶»þä "# ÿ§€R&=4'>54'6'&&"."&'./"?'&54$ þÛè49[aA)O%-j'&]Æ]5r,%O)@a[9( 0BA; + >HCèþÛÎa¢a΀ûþoMÓa-6OƒUyU[q ( - q[UyU‚P6$C +) (  8&/ &fM‘ûÑaÎÎþŸ€€%+"&54&"32#!"&5463!54 €&@&–Ô–`(88(ü@(88( rÀÿ&&j––jÀ8(ýÀ(88(@(8À¹þùÿ€€€#'+2#!"&5463"!54&#265!375!35!àB^^BùÀB^^B € ù€ `€€€^Bû@B^^BÀB^€ àà û `ý  €€€€€€€!="&462+"&'&'.=476;+"&'&$'.=476; €p pp p‡$þ»å! $qr‡ % ²þãþ}×#ߺ»Ö pp pþÅ!åE$‡ ‡rqþÜ¢#׃² % Ö»ºþ!)?"&462"&4624&#!"3!26!.#!"#!"&547>3!2/B//B//B//BŸ û@  À û2œüò±^Bû@B^Å\77\ÅaB//B//B//B/ð@  þÀ íâ  ý~þÀB^^B@2^5BB5ý¢2ÿƒ€.42##%&'.67#"&=463! 2€5KK5L4þ_þu:B&1/&¥¬.- zB^^Bà³Í4L€þvþŠy€KjKþ€4L[!^k'!A3;):2*54&#"+323254'>4'654&'!267+#"'&#!"&5463!2>767>32!2&4&&4¦N2ýÀ$YGB (HGEG H¾ÅQ½#5K4L€—i©!<¬…½¤;þà5KK5 A# ("/?&}£vh˜¦4&&4&€3M95S+C=‹,@QQ9ý€@@§IJ 2E=L5i˜>9eM‹¡E;K5€5K J7R>@#†zD<˜ÿ€€7?s%3#".'.'&'&'.#"!"3!32>$4&"2#!"#"&?&547&'#"&5463!&546323!2` #A<(H(GY$ýÀ2NL4K5#aWTƾh&4&&4¦K5þà;¤¾Ž°=!©i—˜hv£}&?/"( #A  5K€€2*!Q@.'!&=C+S59M34L=E2 JI UR@@&4&&4&€ý€5K;E›ŒLf9>˜ig˜R7J Kÿ5h4&"24#"."&#"4&#"".#"!54>7#!"&54.'&'.5463246326326&4&&4¦§IJ 2E=L43M95S+C=‹,@QQ9€@@€E;K5ý€5K J7R>@#†zD<˜gi˜>9eM‹¡Z4&&4&<½#5K4LN2ýÀ$YGB (HGEG H¾ÅV…½¤;þà5KK5 A# ("/?&}£vh˜—i©!<¬ÿ4<p4.=!32>332653272673264&"2/#"'#"&5#"&54>767>5463!2€@@ý€2*! Q@.'!&=C+S59M34L.9E2 JI UR€&4&&4&›ŒLf6A˜ig˜6Jy‡#@>R7J K5€5K;E@TƾH #A<(H(GY$ýÀ2NL4K#5#a=4&&4&ýDŽ°=©i—˜hv£}&?/"( #A  5KK5þà;¤¾ÿ€€+54&#!764/&"2?64/!26 $$ &þ ½[6þ–[[j6[½ö&ÎþŸþ^þŸÎÎa¢a@€&½4[þ–[6[þ–[6½&+þ^þŸÎÎa¢aÎÎÿ€€+4/&"!"3!277$ $$ [þ–6[½þ &&ö½[6j[ ÎþŸþ^þŸÎÎa¢ae6[j[6½&€&½4[j[þþ^þŸÎÎa¢aÎÎÿ€€+4''&"2?;2652?$ $$ þ–[6[þ–[6½&€&½4[ÎþŸþ^þŸÎÎa¢af6j[[þ–6[½þ &&ö½[ýþ^þŸÎÎa¢aÎÎÿ€€+4/&"4&+"'&"2? $$ [6½&€&½4[j[6[jÎþŸþ^þŸÎÎa¢ad6[½ö&&þ ½[6þ–[[jÿþ^þŸÎÎa¢aÎÎÿ€€ Ø  $2>767676&67>?&'4&'.'.'."#&6'&6&'3.'.&'&'&&'&6'&>567>#7>7636''&'&&'.'"6&'6'..'/"&'&76.'7>767&.'"76.7"7"#76'&'.'2#22676767765'4.6326&'.'&'"'>7>&&'.54>'>7>67&'&#674&7767>&/45'.67>76'27".#6'>776'>7647>?6#76'6&'676'&67.'&'6.'.#&'.&6'&.5/¢aÎÎþŸþ^þŸÎÎD&"      4   $!   #          .0"’Y +  !       $     "  +       ½Î‘      €ÎþŸþ^þŸÎÎa¢aþÅ                        PŽ   ' -( # * $  "  !     * !   (         ü‚$™      2 ÿ~€/$4&"2 #"/&547#"32>32€&4&&4ªýV%54'j&&©'—Ü/ë¹þù¹:,þÛÁ”{ &4&&4&äýV%%l$65&©b—Œ'C†§r! " ©àk[G€ +;%!5!!5!!5!#!"&5463!2#!"&5463!2#!"&5463!2€ý€þ€ü€€þ€&ù€&&€&&ù€&&€&&ù€&&€&€€€€€€ü@ÿ&&&&æÿ&&&&æÿ&&&&ÿ€{#"'&5&763!2{þ' ÿþ**Ù)þý*æí)'/!5!#!"&5!3!26=#!5!463!5463!2!2€þ€^Bú@B^ &@&`ÿù^B`8(@(8`B^€ýþ B^^Bà && €€àþ€€B^ (88( ^ÿ€€G 76#!"'&? #!"&5476 #"'&5463!2 '&763!2#"'þc)'&þ@*þþ*þ@&('cþ (&À*cc*À&' ãþþ*þ@&('cþ'(&À*cc*À&('þc'(&þ@*ÿ€19AS[#"&532327#!"&54>322>32"&462 &6 +&'654'32>32"&462Q¢g†Rp|Kx;CB€’yü–y’ 6Fe= BP†ˆ†PB =eF6 ü–Ô––ÔVáþÂáá>!pR†g¢QBC;xK|€–Ô––Ô€{QNa*+%‹ýx‹‹x5eud_C(+5++5+(C_due2Ô––Ô–þþÂáá>áýŸNQ{u‹%+*jÔ––Ô–ÿpð!Ci4/&#"#".'32?64/&#"327.546326#"/&547'#"/&4?632632°Ð(* 8( !Î)(“ýAÎ('“Ð)* 8( !U“SxySÎSXXVzxTÐTU“SxySÎSXXVzxTÐ@(Ð  (8 *(Ï’è(Ï’'(Ð (8 ýáðS’SUÏSx{VXXTÐTðS’SUÏSx{VXXTЀ€#!"5467&5432632€áŸûÀ¹þùŽt,Ôž;F`j–)¨€Ÿá¹„Û6Ô,°Ž>–jK?Ñsÿ€ €!%#!"&7#"&463!2+!'5#÷8Ejû€jE8÷@&&&&@þìþðÈþð€XYY&4&&4&þqDþS­%þq%ÿ€N\jx†Œ2"&4#"'#"'&7>76326?'&'#"'.'&676326326&'&#"32>'&#"3254?''7¦4&&4&lû€ ýNnbS„‘ˆVZ bR„’SD zz DS’„Rb)+U‰‘„Sbn² €û\.2Q\dJ'.2Q\dJ.Q2.'Jd\Q2.'Jd`!O×`à€ý  `€ýø± €&4&&4þr$#@ƒB10M5TNT{LŽ5T II T5ŽL;l'OT4ŽM01Bƒ@#$Š*„3;$*„3;ý;3„*$;3„*$ : $/é @@þQq`þÀ@˜Šÿ"%3<2#!"&5!"&5467>3!263! !!#!!46!#! (88(ü@(8ýà(8(˜`( (8D<€þÕ+ý€þÕ+Ä<þ€8(þ`(Øþ€8(þ`€8(û@(88( 8( (`˜(8(þ¸(ÕþÕ«þÕþ¤< þ`(8ý€(`üø€þ`(8ý€ÿ„||?%#"'&54632#"'&#"32654'&#"#"'&54632|žu‡dü÷qÜŸžs] = ý¢Ofj’L?R@T?ý»"&š > þf?rRX=Ed—uždsœŸÞqý¢ = _M–jiLü÷?T@R?E& þf > š=XRr?ý»bÿ€€!1E)!34&'.##!"&5#3463!24&+";26#!"&5463!2€ý€€ þç 08(ýÀ(8€€8(@(8þ€ À  À €8(úÀ(88( (`(€þ€€1  þ`(88( û (88(@  þÀ ü`(88(@(8(þè`ÿ€€#!"&5463!2©wü@w©©wÀw©`ü@w©©wÀw©©/%#!"&=463!2#!"&=463!2#!"&=463!2&ú€&&€&&ú€&&€&&ú€&&€&À€&&€&&æ€&&€&&æ€&&€&&ÿÀ@'7G$"&462"&462#!"&=463!2"&462#!"&=463!2#!"&=463!2€p pp pp pp ð û@  À ú€p pp ð û@  À  û@  À Рpp p pp pý À  À ã pp pý À  À óÀ  À ÿ÷<L\l|#"'732654'>75"##5!!&54>54&#"'>3235#!"&=463!2!5346=#'73#!"&=463!2#!"&=463!2}mQjB919+i1$AjM_3<þ–/BB/.#U_:IdDREê û@ À ú€þ±k*Gˆjì û@ À  û@  À TP\BX-@8 C)5˜Xs J@Ÿ$3T4+,:;39SG2S.7<þÁÀ  Àvcc)¢( %Lþlþ}À  ÀóÀ  À ÿ€€5e2#!"&=463%&'&5476!2/&'&#"!#"/&'&=4'&?5732767654'&àù@Ã0†…2uBo  T25XzrDCBBÕEh:%ì›)0%HPIP{rQŒ9f#-+>;I@KM-/Q"€@@@#-a[µ€ $&P{<•8[;:XICC>.ÿ'5oe71#.0(  l0&%,"J&9%$<=DTIÿ€€cs&/6323276727#"327676767654./&'&'737#"'&'&'&54'&54&#!"3!260% <4„"VRt8<@< -#=XYhW8+0$"+dTÍLx-'I&JKkm’§uw<=Vú@À!X@ v 'åþè|N;!/!$8:IœOb“V;C#V  &   ( þ‡ÃmL.A:9 !./KLwPM¼$ú‚@@ €€/?O_oŸ%54&#!"3!2654&#!"3!2654&#!"3!2654&#!"3!2654&#!"3!2654&#!"3!2654&#!"3!2654&#!"3!2654&#!"3!26#!"&5463!2þÀ@þÀ@þÀ@þþÀ@þÀ@þÀ@þþÀ@þÀ@þÀ@€^BúÀB^^B@B^ ÀÀŽÀÀþŽÀÀÀÀþŽÀÀþŽÀÀÀÀþŽÀÀŽÀÀNûÀB^^B@B^^ÿ›€#+3 '$"/&4762%/?/?/?/?¦%kþÛ*úú6Æ6ÆúËbbbb|ÄÄ<<ÄÄ<Þbbbbýžbbbb»%kþÛÕ6úúÆ6Æ‘bbbþü<<ÄÄ<<Äý^bbbbbb@ÿ€M$4&"2!#"4&"2&#"&5!"&5#".54634&>?>;5463!2€LhLLhþÌ€ž à LhLLhL! '–Ô–þ€–Ô–@' !&  Æ? &&LhLLhL€ à ý®hLLhLÀü j––jj––j &@6/" ÆÀ&&ÿ€€J#"'676732>54.#"7>76'&54632#"&7>54&#"&54$ ÎþŸÑok; -j=y¾hwâŽi¶[+PM 3Ñ©—©‰k=J%62>VcÎþÎa¢aQþ^þŸÎ ]G"±'9‰ð–rÈ~:`}†Chž 0=Z—Ù¤ƒªîW=#uY2BrUI1þ^Fk[|éÑaÎÎÿ€€L2#!67673254.#"67676'&54632#"&7>54&#"#"&5463àw©©wý+U ,i<µåF{¶jhµ}Z+OM  2ϧ•§‡jX–Õ¢¨ìW<"uW1AqSH1þbdš©wÀw©ÿ€€"3g!"&'>32 327#".54632%#!654.54>4&'.'37!"463!2!#!!3¦ þ„_™Znh7 1-$ þÛê—gª &ìWa3\@0g]Bj> Ò©wþ,',CMC,.BA.51 ‡‡þKŠÕL¢~Àw©ÿ€ÿ€9&!q[-A"" ""$!'JN±v=C­dy4Shh/`ŠR~†ý w©ITBqIE2;$@;Ft’‘.  @M_~®©w`ÿ€ÿÿ€€-co%4.'&#"32>4.#"326!#!".547>7&54>7#"&54676!#!5!3l $-1!6hpT6Gs~@;k^7x!=kB]f0@\3aWƒµ‡‡GN.BB.!5@@5!Œ˜þô;y{^<% €¢”L@ (•Õ¾‹^lÿ€ÿ€G'!$"" "$8^2"&5!#2!46#!"&5463!2€€r”M* €*M~–~M**M~–~M*j–û€–jj–€–ê&ù&&&€`À‰P%þàæŒ|NN|Œ|NN|þ*–jj–þ–jj–@û€&&€&&@€ "'&463!2þ@4þ@&€Z4þ@À4&@ #!"&4762&ü€&À4ÀZ4&&4Àþ@@€€€ "'&4762€&4þ@À4&@ü€&À4À&€@€ "&5462@þ@4&&4Àš4þ@&€&þ@ÿ€€€ 3!!%!!26#!"&5463!2 `ý€mý€` €^BúÀB^^B@B^€û   `û€Íû@B^^BÀB^^ÿÀ@ "'&463!2#!"&4762þ@4þ@&€&&ü€&À4ÀÚ4þ@À4&Z4&&4Àþ@ÿÀ "'&463!2þ@4þ@&€Ú4þ@À4&@ #!"&4762&ü€&À4ÀZ4&&4Àþ@ÿ€:#!"&5;2>76%6+".'&$'.5463!2^Bú@B^,9j‡9Gv33vG9ªH9+bIþˆ\ A+=66=+A [þª">nSMÀA_:üæB^^B1&öc*/11/*{Þ'VO3þû@/$$/@í*“?Nh^ÿ°l+!+"&5462!4&#"!/!#>32]þ¶_gTRdg¦dþ·QV?U þ·I*Gg?«Ðü!ß2IbbIJaaüÝýÈiwE33ý×ð00 08ãÿ€€4#"$'&6?6332>4.#"#!"&54766$32zÎþ䜬þÊm‰ IÔwh½ŠQQŠ½hb´F‰*þ@&('‚k“œÎþÈþäÎz‘„ Š  _hQŠ½Ð½ŠQGBŠ'(&À*eozÎ(ÿëØq!#"'&547"'#"'&54>7632&4762.547>32#".'632ë%k'45%þ•&+ÿ~(  (þh  &  \(  (˜  &  ~+54'k%5%l%%l$65+~  &  ˜(  (\  &  þh(  (~ÿ+%þ•'ÿ€!)19K4&"24&"26.676&$4&"24&"24&"2#!"'&46$ €KjKKj KjKKj÷e2.e<^PšŠ,bKjKKjýËKjKKj KjKKj‹#ú†#ŽðLlLðŽKjKKjK jKKjKþŸ~-þ‚M7>7&54$ LþhþÑ‚W.˜{+9E=ÌcÑÑQðþdôFKÆþú1A  0) µðœèœ€‹ì‰pËJ2`[Q?l&‹ììÇþ¤þÙ«¯C58.H(Y–®'««ÿ€:d 6?32$64&$ #"'#"&'&4>7>7.546'&'&'# '32$7>54'YþÎþöj`a#",5NK™ ýž~E¼¼þ»¿VZ|š$2 $ |Ž¼: $ 2$š|ZVþñÉ:¡(t}†–Ž€h²fR˜88T h²Ì²è‰ìþêì‰X(  &%(HÒw‹ìûø(%& (X„ZT\ð†MKGÖ{xÑÿ|€!#"'.7#"'&7>3!2%632u ýä  Åþj ÉH«ŒÊû{(e 9 þ1bÿ€€U#!"&546;5!32#!"&546;5!32#!"&546;5463!5#"&5463!2+!2328(þÀ(88(`þ`(88(þÀ(88(`þ`(88(þÀ(88(`L4`(88(@(88(`4L`(8 þÀ(88(@(8ÀÀ8(þÀ(88(@(8ÀÀ8(þÀ(88(@(8À4LÀ8(@(88(þÀ(8ÀL4À8ÿ€€ÀOY"&546226562#"'.#"#"'.'."#"'.'.#"#"&5476$32&"5462€˜Ð˜&4&NdN!>! 1X:Dx+  +wˆw+  +xD:X1 -ÿU¾Œ à¥!ý*,*&4&Äý¼h˜˜h&&2NN2D &  ..J< $$ 767#"&'"&547&547&547.'&54>2àl4  2cK Eo‡Š‡oED ) € ä € ) D€g-;</- ?.P^P.? -/<;-gY‘·¾·‘YÀ  .2 L4H|O--O|HeO , ™‘‘™ , Oe›q1Ls26%%4.2,44,2.4%%62sL1q›c«qAAq«ÿ à4#!#"'&547632!2#"&=!"&=463!54632 ú  þÁ @  `  þÀ  ú   ` ?`À À  @  @  À! þÀ  À À À þÁ€€54&+4&+"#"276#!"5467&5432632à À à  `  _ €áŸûÀ¹þùŒv,Ôœ;G_j–)‚§``  þ   þ  _ ԟṂÜ7 Ô,®>–jL>Ñ€€54'&";;265326#!"5467&5432632 þ   þ¡ à À à €áŸûÀ¹þùŒv,Ôœ;G_j–)‚§  ` þ¡ þ   `þíŸá¹‚Ü7 Ô,®>–jL>Ñÿ€€€X`$"&462#!"&54>72654&'547 7"2654'54622654'54&'46.' &6 €&4&&4&’yü–y’ %:hD:Fp pG9„F„j– 8P8 LhL 8P8 E; Dh:% þÀáþÂáá>Ú4&&4&}yŠŠyD~–s[4DËd=PppP=dË>hh>@–jY*(88(*Y4LL4Y*(88(*YDw" A4*[s–~ØþÂáá>áÿ€€€M4&"27 $=.54632>32#"' 65#"&4632632 65.5462&4&&4¦G9þùþŽþù¤Ü& <#5KK5!¼¼!5KK5#< &ܤ¼¼9Gp p&4&&4&@>bþuŸáោØ&$KjKþnj––j’KjK$&þØ„j––j‹b>Pppÿ€€ %!5!#"&5463!!35463!2+32€þþ @\„„\ ü€8(@(8„\@@\„€€€û„\@\„û (88( àüÀ\„„ÿ€ -4#"&54"3#!"&5!"&56467&5462P;U gI@L4þ@–Ô–þ@4L¾ÂÀ¨8P8¨À° U;Ig04Lj––jL4¡Ù¥Â(88(Â¥þúþ'ÿ€@"4&+32!#!"&+#!"&5463!2€pP@@Pùð–jûj–@áŸ@„\ý@\„&€Ÿ0 pþ€ýÀj–– þÂá \„„\à&ÿ€-B+"&5.5462265462265462+"&5#"&5463!2€G9L4€4L9G&4&&4&&4&&4&&4&L4€4Là ¼„&Àý€=düõ4LL4 d=€&&þ`&& &&þ`&& &&ùÀ4LL4  „¼&ÿ€€(/C#!"&=463!25#!"&=463!2!!"&5!!&'&'#!"&5463!2ý@Àý@Àü€þ`(8þ€x þÇ 8(ûÀ(88(€(`8(`@@ò@@ý’8( þ€ 9 þhü€(88(@(8(þÈ`ÿ€/?O_oŸ¯¿Ïßïÿ-=%+"&=46;25+"&=46;2+"&=46;2%+"&=46;2+"&=46;2%+"&=46;2%+"&=46;2%+"&=46;2+"&=46;2%+"&=46;2%+"&=46;2%+"&=46;2+"&=46;2%+"&=46;2%+"&=46;2+"&=46;2%+"&=46;2+"&=46;2!!!5463!2#!"&5463!2€ @  @  @  @  @  @ ÿ @  @  @  @ ÿ @  @ ÿ @  @ ÿ @  @  @  @ ÿ @  @ ÿ @  @ ÿ @  @  @  @ ÿ @  @ ÿ @  @  @  @ ÿ @  @  @  @ ÿ€û€€ @ &û&&&à@  @ ó@  @  @  @ ó@  @ ýó@  @ ó@  @ ó@  @ ó@  @ ýó@  @ ó@  @ ó@  @ ó@  @ ýó@  @ ó@  @ ó@  @ þó@  @ ó@  @  @  @ ú“úà  `ù€&&€&& ÿ€/?O_oŸ·Ûõ%+"&=46;25+"&=46;2+"&=46;2%+"&=46;2+"&=46;2%+"&=46;2%+"&=46;2+"&=46;2%+"&=46;2+"&=46;2!!#!"&=!!5463!24&+"#54&+";26=3;26%#!"&5463!463!2!2€ @  @  @  @  @  @ ÿ @  @  @  @ ÿ @  @ ÿ @  @  @  @ ÿ @  @  @  @ ÿ€ÿ8(þ@(8ÿ€ @  @ € @  @ € @ &û&&@8(À(8@&à@  @ ó@  @  @  @ ó@  @ ýó@  @ ó@  @ ó@  @ þó@  @ ó@  @  @  @ ü“€ (88( û€à  À@  ``  þÀ  `` -û&&& (88(þà&@ÿ€€€<c$4&"2!#4&"254&+54&+"#";;26=326+"&5!"&5#"&46346?>;463!2€KjKKjþË€žÃKjKKjËàÀààÀà&À–Ô–þ€–Ô–€&&Æ@ &€&KjKKjK€à ý­jKKjK ÀààÀàà.û€&j––jj––j&4& @Æ@&&ÿ€€#'1?I54&+54&+"#";;26=326!5!#"&5463!!35463!2+32àÀààÀàý€þþ€ \„„\ÀûÀ 8(@(8„\ \„ ÀààÀààû„\@\„û (88( àüÀ\„„€€: #32+53##'53535'575#5#5733#5;2+3€þáþ à@þÛE&&` @@ À` €ÀÀ€ `À @@ `&&E%@à`@ @ @þ    à À € À à   þ @ :#@€€!3!57#"&5'7!7!€ÿK5€û€€€Ÿá@ à À @€€ÿ5Kþ@ÀÀÀáŸ@@€€À üàÿ€€#3%4&+"!4&+";265!;26#!"&5463!2&€&þ&€&&€&&€&©wü@w©©wÀw©À€&&þÀ@&&ü€&&@þÀ&&ºü@w©©wÀw©©ÿ€€#354&#!4&+"!"3!;265!26#!"&5463!2&þÀ&€&þÀ&&@&€&@&©wü@w©©wÀw©@€&@&&þÀ&€&þÀ&&@&:ü@w©©wÀw©©-Mó3)$"'&4762 "'&4762 s 2  þ. Ò  2 þw‰Š 2  þ. Ò  2 þw‰­ 2 Ò  Ò 2  þwþw  2 Ò  Ò 2  þwþw MÓ3)"/&47 &4?62"/&47 &4?62S þ.  2 ‰þw 2  ÒŠ þ.  2 ‰þw 2  ÒM þ. 2  ‰‰  2 þ.  þ. 2  ‰‰  2 þ.M3S)$"' "/&4762"' "/&47623 2  þwþw  2 Ò  Ò 2  þwþw  2 Ò  Òí 2 ‰þw 2  Ò þ.v 2 ‰þw 2  Ò þ.M­3s)"'&4?62 62"'&4?62 623 þ.  þ. 2  ‰‰  2 þ.  þ. 2  ‰‰  2­ þ. Ò  2 þw‰ 2v þ. Ò  2 þw‰ 2-Ms3 "'&4762s þw‰ 2  þ. Ò  2í þwþw  2 Ò  Ò 2 MS3"/&47 &4?62S þ.  2 ‰þw 2  ÒM þ. 2  ‰‰  2 þ.M 3S"' "/&47623 2  þwþw  2 Ò  Òm 2 ‰þw 2  Ò þ.M-3s"'&4?62 623 þ.  þ. 2  ‰‰  2- þ. Ò  2 þw‰ 2ÿ€€/4&#!"3!26#!#!"&54>5!"&5463!2 ùÀ  @ €^Býà &þ& ýàB^^B@B^ @  üÀ MûÀB^%Q= &&& $$ ”þØú’’ú(ú’’rÎþŸþ^þŸÎÎa¢a ’úþØú’’ú(ú½þ^þŸÎÎa¢aÎ΀€!C#!"&54>;2+";2#!"&54>;2+";2pPþ€PpQŠ½h@&&@j–8(àPp€pPþ€PpQŠ½h@&&@j–8(àPp@þ€PppPÀh½ŠQ&€&–j (8pPþ€PppPÀh½ŠQ&€&–j (8p€€!C+"&=46;26=4&+"&5463!2+"&=46;26=4&+"&5463!2QŠ½h@&&@j–8(àPppP€Pp€QŠ½h@&&@j–8(àPppP€PpÀý@h½ŠQ&€&–j (8pP€PppPý@h½ŠQ&€&–j (8pP€Pppÿ€À !)19A$#"&4632"&462"&462"&462"&462$"&462"&462"&462ðU;bq™›bà&4þ4&àÉ¢5 ¦þã"  #D7e uU6 ÿ&4&ÿþm†ÿ€€ 1X".4>2".4>24&#""'&#";2>#".'&547&5472632>3€=T==T=™=T==T=¹Šv)šG¬G˜+vŠ@b’†R¨R†’b@à=&‡“Á–\N€§Šˆj!>ˆ3l¤k“¢”„i¤k3ˆhPTDDTPTDDTPTDDTPTDD|x¨ ¨xXƒK--KƒÏ|Mp<# )>dA{ÐíŸRXtfOT# RNftWQ €€,%4&#!"&=4&#!"3!26#!"&5463!2!28(ý@(88(þÀ(88(À(8€„\û@\„„\@\„ \„àÀ(88(@(88(ü@(88èý@\„„\À\„„\ „u€'E4#!"3!2676%!54&#!"&=4&#!">#!"&5463!2!232õ5ûÀ([þÚ5@(\&û‹8(ýÀ(88(þÀ(8,9.þÙ+’CûÀ\„„\@\„ \„À6Z]#+þ•#,k´ (88(@(88(ü«;5E£>:þ•5E„\À\„„\ „\ 1. €€#3C++"&=#"&=46;546;2324&#!"3!26#!"&5463!2€à@àà@à€8(ý@(88(À(8€ƒ]ý@]ƒƒ]À]ƒ`@àà@ààþrÀ(88(ý@(88èý@\„„\À]ƒƒ€€/2#!"&54634&#!"3!262#!"&=463 ]ƒƒ]ý@]ƒƒ] 8(ý@(88(À(8 ýÀ€ƒ]ý@\„„\À]ƒü`À(88(ý@(88È@@ÿ€€$4@"&'&676267>"&462"&462.  > $$ n%ÊþÊ%/‡¨‡02þ KjKKjKKjKKjKf«íþüí«ff«íí«æÎþŸþ^þŸÎÎa¢aÍy””y/PccP/ÏjKKjKKjKKjKýþí«ff«íþüí«ff«@þ^þŸÎÎa¢aÎÎÿ€€$4@&'."'.7>2"&462"&462.  > $$ n20‡¨‡/%ÊþÊþ7KjKKjKKjKKjKf«íþüí«ff«íí«æÎþŸþ^þŸÎÎa¢a3/PccP/y”” jKKjKKjKKjKýþí«ff«íþüí«ff«@þ^þŸÎÎa¢aÎÎÿ€€ +7#!"&463!2"&462"&462.  > $$ €&ý€&&€þ&KjKKjKKjKKjKf«íþüí«ff«íí«æÎþŸþ^þŸÎÎa¢aÚ4&&4&µjKKjKKjKKjKýþí«ff«íþüí«ff«@þ^þŸÎÎa¢aÎ΀#+3C54&+54&+"#";;26=3264&"24&"2$#"'##"3!2@À€ÀÀ€À@KjKKjKKjKKjKþÔÔÀ’Ü’ÀÔþÔ,Ô€ÔÀ€ÀÀ€ÀÀgjKKjKKjKKjKÔþXþÔ€€,¨,€€ #/;GS_kwƒŸ£³+"=4;27+"=4;2'+"=4;2#!"=43!2%+"=4;2'+"=4;2+"=4;2'+"=4;2+"=4;2+"=4;2+"=4;2+"=4;2+"=4;54;2!#!"&5463!2€``€àà€``ü `ý€``€``€``€``€``€``þ````àp`€ù€K5ù€5KK5€5Kp``ð``ð``ýð``ð``ð``þð``ð``þð``þð``ð````þ `ðý€ü€€ü€5KK5€5KK@ÿ€€*V#"'.#"63232+"&5.5462#"/.#"#"'&547>32327676€©‰R?d¨^­æõ¼7ac77,9xûm#@#KjKÀ# Ú—XF@Fp:fþõ_ #W¤IpÂp&3z¼ ëh[ 17ý©q%q#:ûò:#5KKuý't#!X: %æ#+=&>7p @ÿ€€ *2Fr56565'5&'. #"32325#"'+"&5.5462#"/.#"#"'&547>32327676@µËͳ¬Ô×éë•8 2.,#,fµk*1x­©‰-!”û¬#@#KjKÀ# Ú—XF@Fp:fþõ_ #W¤IpÂp&3z¼ Àe¹`°Åv½oþ8¸t-à  Þ:5 ¼½[Ä*î#:ûò:#5KKuý't#!X: %æ#+=&>7p  €3$ "/&47 &4?62#!"&=463!2Iþ.  2 ‰þw 2  Ò -ü@À)þ. 2  ‰‰  2 þ. þ-@@-ÿ“Sí$9%"'&4762  /.7> "/&47 &4?62i2  þ. Ò  2 þw‰ Eþ‹ > u > þ.  2 ‰þw 2  Ò ‰2 Ò  Ò 2  þwþw !úõ   ýhþ. 2  ‰‰  2 þ. ÿ€»;#"'&476#"'&7'.'#"'&476€' þ)'þs "+5+•@Õ¡' þ)'›¼©ÆF*4*Eþr4þM:—}}8 ¥GO û*4*þúÁ­ÿ­~à (-/' #"'%#"&7&67%632¢þœBŸ;>< õþ•Vþ?þ?Vþ” -öááö-Cú4 <Bü=¨cB5þžþ !% ìì %!ôb 7IÇ))þ9I7ÿ€€ #"'.5!".67632yý€( ýÀ#  £û##@,( €)ÿ€€8! !++"&=!"&5#"&=46;546;2!76232-Sý€Sý­€àÀü ààÀSö  ÷àSýÚSý`Ààà`Ààà÷  öü­ÿ€€K$4&"24&"24&"27"&5467.546267>5.5462 8P88P88P88P¸8P88P˜4,àD‡€S,4p p4,,4p p4,6d7AL*',4p pP88P8¸P88P8HP88P8`4Yþá&+(>EY4PppP4Y4Y4PppP4Yþ%*54&#"#"/.7!2Àðð<'G,')7ð‚N;2]=A+#H  ¤  0P¢‚RððH6^;<T%-S“#:/*@Z}   >h—€€.%#!"&=46;#"&=463!232#!"&=463!2€&þ&&@@&&€&@&€&ÿ&&&À€&&€&€&€&&ýÀ&fÀ&&À&&b€#!"&=463!2#!"&'&63!2&ÿ&&&'ÿ'%@% à&&à&&ý&&&&þk"G%#/&'#!53#5!36?!#!'&54>54&#"'6763235øŸ ›þþ€Å¹‰‹Œ}¸Ìêýþ4NZN4;)3.i%Sinˆ1KXL7觧ü* ú§#¨ä& *ä¨þõþاÎ@jC?.>!&1' \%Awc8^;:+54&#"'6763235øŸ ›þþ€Å¹‰‹Œ}¸Ììýþ4NZN4;)3.i%PlnˆEcdJ觧ü* ú§#¨ä& *ä¨þõþØÙÎ-@jC?.>!&1' \%AwcBiC:D'P%! #!"&'&6763!2€Pýþ°õ ü€&:ý&? €&:&?€€þ€5"Kü,)""K,)ÿÜ€h#".#""#"&54>54&#"#"'./"'"5327654.54632326732>32€YO)I-D%n  "h.=T#)#lQTv%.%P_– % %–_P%.%vUPl#)#T=@è/#,-91P+R[¶Ql#)#|'˜' 59%D-I)OY[R+P19-,##,-91P+R[YO)I-D%95%–_P%.%vÿ€€'3!2#!"&463!5&=462 =462 &546 €þÙÙ&&ý€&&ÙþÙ&4&r&4&ÿ¼þø¼¼¼@€Ýþ¹„&4&&4&„GÝ€&&€¹þù¹€&&fþ„¼¼„„¼¼ ÿ€s CK&=462 #"'32=462!2#!"&463!5&'"/&4762%4632e*&4&iþ—¼„76`al¹&4&þÙÙ&&ý€&&}nþ  R Ò  R þzý“¼„f¥Oego€&&€5þ—€„¼`3¹€&&€Ýþ¹„&4&&4&„ Dþ R  Ò R zý“„¼vÿ€€"!676"'.5463!2@þ@w^ëÀCc‰t~5  5~t‰cC&€&@€û?J¸°ýV©ƒ|RIIR|ƒ©V&&ÿ€#G!!%4&+";26%4&+";26%#!"&546;546;2!546;232€€ú€€@@@@€L4ú€4LL4€^B@B^€^B@B^€4L€À þà þàNû4LL44L`B^^B``B^^B`Lÿ€€àL4&"2%#"'%.5!#!"&54675#"#"'.7>7&5462!467%632&4&&4¦  þ@ ÿo‘&þ&}c ;pG=(  8Ai8^„^. À  &4&&4&`þÀ ` f°süà&& j©o/;J!# 2 KAE*,B^^B! ` $ÿ €€-4&"2#"/&7#"/&767%676$!2 8P88P—²Qrþ€ @ Uþçþì @ à {`P¼TP88P8€ùþ•³P`þ… à @U @€rQ»Ž¬!6'&'&'&+!!!!2¬¼þе ÅÍþÑÌþÐÍþÐsXVqüQ ü@Àü@vtÿ€€ %764' 64/&"2 $$ fþÍ3f4þ:Æ4†ÎþŸþ^þŸÎÎa¢af4334fþ:4þ:×þ^þŸÎÎa¢aÎÎÿ€€ %64'&" 2 $$ ÍÆþ:4f3þÍf4FÎþŸþ^þŸÎÎa¢aÆ4Æf4þÍþÍ4f×þ^þŸÎÎa¢aÎÎÿ€€ 764'&"27 2 $$ fþ:4þ:f4334†ÎþŸþ^þŸÎÎa¢af4Æþ:4f3þÍ×þ^þŸÎÎa¢aÎÎÿ€€ %64/&" &"2 $$ -Æf4þÍþÍ4fÆ4æÎþŸþ^þŸÎÎa¢aíÆ4fþÍ3f4þ:wþ^þŸÎÎa¢aÎÎÿ@€€7!!/#35%!'!%jüŒ/dÅÄ ¯jg2ý|þ8€€ý¾ý«¯ýêä55Œþêdc µÕúb¢¢ ÿ@ô€! !%!!7!áþöüÜýFG)¦æDûH:¹&ûH€úËþõ d“¡¡S)¿ÿU4&"2#"/ $'#"'&5463!2#"&=46;5.546232+>7'&763!2À&4&&4f ]wþqþ4þqw] `dCõ•À&&À:F–Ô–F:À&&À•õCd`æ4&&4&ü þ  ]§§] `d[}‡&€&£"uFj––jFu"£&€&ýy}[d€#2#!"&546;4 +"&54&" (88(ü@(88( r&@&–Ô–8(ýÀ(88(@(8@¹þù¹&&j––jþÀÿ€€'3"&462&    .  > $$ –Ô––ÔáþÂáá>aþÔþXþÔ,¨¬f«íþüí«ff«íí«æÎþŸþ^þŸÎÎa¢aêÔ––Ô–þa>ááþÂáTþXþÔ,¨,ý~í«ff«íþüí«ff«@þ^þŸÎÎa¢aÎ΀€/+"&=46;2+"&=46;2+"&=46;2€8(À(88(À(88(À(88(À(88(À(88(À(8 À(88(À(88(À(88(À(88(À(88(À(88€€/+"&=46;2+"&=46;2+"&=46;2€8(À(88(À(88(À(88(À(88(À(88(À(8 À(88(À(88ØÀ(88(À(88ØÀ(88(À(88ÿ€€5E$4&"2%&'&;26%&.$'&;276#!"&5463!2KjKKjª þ¸è šÜ  € f±éþáš  Ì\Ñ € ©wü@w©©wÀw©ËjKKjK"èH  €  Üš  šé±f € Ñþ¤Ì  Íü@w©©wÀw©©ÿ€€   $64'&327/¢aÎÎþŸþ^þŸÎβ ýà! €ÎþŸþ^þŸÎÎa¢aý—J@%ý€% 6ÿ5ËÊ/ 64'&"2 "/64&"'&476227<ýÄþÄijþ–6ý–j6‹üu%k%~8p 8}%%‹%k%}8p 8~%<þÄýÄ<þij4jý–4þ–üt%%~8 p8~%k%Š%%}8 p8}%kÿ€€54&#!"3!26#!"&5463!2&ü€&&€&©wü@w©©wÀw©@€&&€&&:ü@w©©wÀw©©€€/#!"&=463!24&#!"3!26#!"&5463!2€üÀ@€^BüÀB^^B@B^€©wüÀw©©w@w©à@@þ2@B^^BüÀB^^‚üÀw©©w@w©©ú+#!"'&?63!#"'&762ú(Àý@   @À(@>@¥%ü À €%%€þ€ ÿ€ú!232"'&76;!"/&76 À À($þÀ>þÀ(ÀþÀ   ü¡J þ€€&%€ Àÿ€€$%64/&"'&"2#!"&5463!2­ff4þ-Ó4ff4f©wü@w©©wÀw©íf4fþ-Óf4þš†ü@w©©wÀw©©ÿ€€/#5#5'&76 764/&"%#!"&5463!2”˜48`ÒþÝ #þû þàýà€\˜P\ ©wü@w©©wÀw©¬˜4`8º þÝ #ý@  ýàþà`\P˜\`ü@w©©wÀw©©ÿ€€)4&#!"273276#!"&5463!2&þ *ýêf4 '©wü@w©©wÀw©`à&')ýê4f*ü@w©©wÀw©©ÿ€€%5 64'&"3276'7>332#!"&5463!2í`þ '(wƒa8! § ,j.¨Œ( &©wü@w©©wÀw©³`4`* '?_`ze<µß  bw4/ *Àü@w©©wÀw©©ÿ€€-.  6 $$ €ÿ€þ ’úþØú’’ú(úrÎþŸþ^þŸÎÎa¢aÀ€€OýâÿþÝ(ú’’úþØú’’_þ^þŸÎÎa¢aÎÎÿ€€ -"'&763!24&#!"3!26#!"&5463!2yþÀBþÀ(€(˜ ü@  À ©wü@w©©wÀw©]#þ@À##ý À  ü@ Íü@w©©wÀw©©ÿ€€ -#!"'&7624&#!"3!26#!"&5463!2y(ý€(@B@u ü@  À ©wü@w©©wÀw©£###Àþ@þÚÀ  ü@ Íü@w©©wÀw©©ÿ€€ -'&54764&#!"3!26#!"&5463!2@þ@####ÀÛü@À©wü@w©©wÀw©¡BþÀ(€(þÀýìÀü@Îü@w©©wÀw©©ó€`%#"'#"&=46;&7#"&=46;632/.#"!2#!!2#!32>?6Ð#  !"'êþ¢?_  BCbCaàf\ + ~È2Ô þË  þ}0Ë$ åŸ Ý q 90rÒ Ÿ €p r%D p u‰ü€?#!"&=46;#"&=46;54632'.#"!2#!!546;2üüD a__÷¿¹– g *`-Uh1  þÏž¢þ‘–  ƒß«Þ}   $^L׃ þ…µ 4ÿÒb+"&=.'&?676032654.'.5467546;2'.#"ÒÇŸ‡ B{PDg q‚%%Q{%P46'-N/B).Ä ‡9kC< Q 7>W*_x*%K./58`7E%_™Ý¯ ¯ ,-3‡  cVO2")#,)9;J)ŠÐ´ °"!*’ #VD,'#/&>AX‚€>++"''&=46;267!"&=463!&+"&=463!2+32‚¨Ôª§$ à þÎÀ  p„¡þU9Ó‘ @é/«*f´²þš oÌ  VRfq …f=Sÿ€E!#"&5!"&=463!5!"&=46;&76;2>76;232#!!2#![¬ þà   þà  Öþ¿  ×% )¿¿ þÇ×  þÞ"  þÞJg Uh BþW&WX¤ý½ hU gþ¶ ÿ瀀L\+"&5##"/&67>7> 7!"&=463!2+;26=46;2#!"&=463!2€¼„€„¼à$=5R9[/*G :!3' ÿÀà&€&Àþ€ü@À` „¼¼„àf±‡vQJ+- ²   (->K\rB  þ&&@ò  € n#467!!3'##467!++"'#+"&'#"&=46;'#"&=46;&76;2!6;2!6;232+32QŸKt#þÜ ¡‹#FŸN¢Qo!þ×"€Õ¤Ÿ¦Ñ§Ÿ  Ð¯!ŽmY ‰Zga~bm]‰ [o‘"³U+þÔ¬€€€ýÔ,þÕ­€€ @ý˜hý˜ h@€@X þ˜hþ˜h þ¨@€8ÿè€3H\#5"'#"&+73273&#&+5275363534."#22>4.#2>•ut 3NtRšP*šHÈo2 LoÔ@!šR(šOzh=Ñ,GID2Fýž þÁ þÀÀÀÀî8PuE>.'%&TeQ,j†m{¤þ+§>RÀ{ß?jJrL6V þÁ @`ú 7>wmR1q uWei’½/rr° :V¹ýr"ÿÎ $7V4&#"326#"'&76;46;232!5346=#'73#"'&'73267##"&54632BX;4>ID2Fýž þÁ þÀÀÀÀÐþ+§>RÀ{Ã8PuE>.'%&TeQ,j†m{¤ß?jJrL6ûª þÁ @`ú ürr° :V¹ýr3>wmR1q uWei’½ÿ€@€ \%4&#"326#!"&5463!2+".'&'.5467>767>7>7632!2&%%& &þà&& & 7.' :@…$LBœWM{#&$h1D!  .I/! NrÀ&&%%ý€&&€&&V?, L=8=9%pEL+%%r@W!<%*',<2(<&L,"rÿ@ \#"&546324&#!"3!26%#!#"'.'.'&'.'.546767>;&%%& &þà&& &i7qNþë !/I.  !D1h$&#{MWœBL$…@: '.À&&%%ýå€&&ý€&&¯=XNr%(M&<(2<,'*%<!W@r%%+LEp%9=8=L ÿ€€ +=\dŒž²Â%54#"327354"%###5#5#"'&53327#"'#3632#"'&=4762#3274645"=424'.'&!  7>76#'#3%54'&#"32763##"'&5#327#!"&5463!2—¸BBýÅPJN±C'%! B? )#!CC $) û 54f…"þ@@ B+ˆþìþíˆ,A  A+‰&‰+A ý ZK35N # J!1331µCCC $)÷©wü@w©©wÀw©é2à«"33èFþY§F~þ‘(-&"þòo’4*)$í¡(*¶ (&;;&&:LA3  8œ33œ4ý±S,;;,W­°T+<<+T;(ÃÃ\g7Éx‚:&&:‚:&&<rþåþÛ%-ü@w©©wÀw©© ÿå +=[c}‰›¯#"'632#542%35!33!3##"'&5#327%54'&#"5#353276%5##"=354'&#"32767654"2 '.'&547>76 3#&'&'3#"'&=47632%#5#"'&53327Ë''RZZü:kþÈid YYY .06­ 62+YY-06 R[!.³'CD''EH$ý VVÏX:¸ý¸:Y X;·æ¸:Y üfyd/%jG¶%EC&&CE%O[52. [$ÓC-D..D–^^ýÇîþ†* lþy1%=^ÅI86Ùýi077S 3 $EWgO%33%O­O%35 ÂÒEEÒFýWêt;PP;pîêt;PP;pþqþñJŠgTþùF¯Q%33&P¯P%33%Rþ 7>%3Šþ‘!+}ÿ€{ö'+"&72'&76;2+"'66;2U ÷&ï ý¡ ï(Ê ýðP ï*þ­'ñeþJ."À-düZý™-n Ž-ÿ€€'74'&+";27&+";276'56#!"&5463!2­~¸}Ä ¹7»þe ¸ þü™Û©wü@w©©wÀw©Ý" Øþ¦ $Q #ý'þ!# ÜÓˆü@w©©wÀw©©/4'&327$ '.'.4>7>76 þ"!!jGÞü~ÞGkjGÞ‚ÞGk[J@&ý€& @–Àl¥AIddIA¥lÀl¥AIddIA¥@ÿ€ÀŠ '5557 ’îþªþ,þþ“VWýQVþþ®.Rþþ©Wéþ®þ=þÏþã?þälþÛ%l`þäØþãþÐþòþñþÁ~þÁþò0ÿ~#%5!'#3! %% % ý=´û”#y üØÀ ý?R«'ýUÊaMýŸµŽ|þqBy•y‡——[ýC#àý–jXA–AÒ·’·ïþ˜‚hÍý·UHéýG¹ÿ€€/?%##"547#3!264&#"3254&+";267#!"&5463!2R‡€Ü‚Åþè#-$þäµ€µµ€Ñ(®((®(®tQûŠQttQvQtnˆ?D~Õ|ÀD?ýx##³ø¯¯ø¯“¥))¥((íûŠQttQvQttÿ€€2#!"&54634&"2$4&"2àw©©wü@w©©wš|°||°°|°||°€©wü@w©©wÀw©ü¨°||°||°||°|ÿ€€ !3 37! $$ Éþn6^þ5þ5^h ûÎþŸþ^þŸÎÎa¢a’þÎà³ýM 1þ^þŸÎÎa¢aÎÎÿP£ *Cg'.676.7>.'$7>&'.'&'? 7%&'.'.'>767$/u5'&$I7oÆb?K“\[zäH,1þÝþí+.@\7<äÜ?5\V ,$VÏÅg.GR@ ß7àµU,+!üþšø’  # "8$}¼{)›<¥?L RR ;kr,yE[€˜z# /1 "# #üeCI0/"5#`Ä ””"8¸§þ4~&p )4 2È{¬H- .%W.L>ÿ€€':Yi4&67&'&676'.'>7646&' '7>6'&'&7>7#!"&5463!2PR$++'TJX„j7-F¶C',›©,&C ."ÆÒ!$28 ¡þh¢ /ù³"‡ +pØþñ„^&+3$ i³µ0(©wü@w©©wÀw©š+.i6=Bn \C1XR:#"ý'jj š8Q.cAjÇ57!? "0DŒÊ$4" P[ & 2ü@w©©wÀw©©Nÿ€€#3!!327#"'&'&'&5#567676†Ûlþ” '2CusfLM`iQN<:ª[@@''€þ|ñþvˆ$%Lò02366kÙ67MNÿ€€#3%5#"'&'&5!5!#33276#!"&5463!2cXV3% þî¤ 10D*+=>NC>9ê©wü@w©©wÀw©µ8c'µ#Z99*(£þlN+*$% ü@w©©wÀw©©ÿ@ý#"'&76;46;23õ þ¢  þ  àÀà&þ€ €àû ÿýÀ++"&5#"&7632ý àÀà ^  c û à&€ þ€@ý#!'&5476!2û &þ€ €ààÀà ^  b àÀý'&=!"&=463!546À þ€û à&€ ƒ þž àÀà þ¢ ÿ€q&8#"'&#"#"5476323276326767q'T€1[VA=QQ3˜•“qp¬Hih"-bfGw^44O#AŠþá?66%CKJ°A}}Ä !"òä’""A$@C3^q|Æz=KK?6 •lk) ÿ€€ %!%!ªýVªýV€üu‹üuýu^-çým5ýwüî}•nüæÿ€~7M[264&"264&"2"&546+"&=##"&5'#"&5!467'&766276#"&54632Ý  ¼  üû*<;V<<O@-K<&4'>&4.'.'.'.'.'&6&'.'.6767645.'#.'6&'&7676"&'&627>76'&7>'&'&'&'&766'.7>7676>76&6763>6&'&232.'.6'4.?4.'&#>7626'.'&#"'.'.'&676.67>7>5'&7>.'&'&'&7>7>767&'&67636'.'&67>7>.'.67— \ þ›U7  J#!W! '  " ';%  k )"    '   /7*   I ,6 *&"!   O6* O $.(¨ *.'  .x…,  $CNý¡    £  * ´ 8   7%&&_f& ",VL,G$3¤@@$+ "  V5 3"  ""#dA++ y0D- %&n 4P'A5j$9E#"c7Y 6" & 8Z(;=I50 ' !!e  þR  þš "+0n?¢t(-z.'< >R$A"24B@( ~ 9B9, *$        < > ?0D¨9f?Ae ‡ .(;1.D 4H&.Ct iY% *  7à ì   úÈ  J  <    W 0%$  ""I! *  D  ,4A'¾4J" .0f6D4pÆZ{+*ŸD_wqi;ÐW1G("% %T7F}AG!1#%  JG 3 ÿ€€ '.2>Vb%&#'32&'!>?>'&' &>"6&#">&'>26 $$ *b6”~ˆ#¸ê„= þÉþ–XP2“Š{&%gx|ŠÀ .ÜÒÇW)o”üñO¹øLOƒsEzG<ä’ CK}E $MFD<5+ zÎþŸþ^þŸÎÎa¢a$ñMWŽM –“1>]|áYY›^D ÖÕ¥Aò—ï<ïæKåm‘¤ªÔE6<þ"è² @9I5*Èþ^þŸÎÎa¢aÎÎÿ€€>^4./.543232654.#"#".#"32>#"'#"$&547&54632632•':XM1h*+D($,/9p¬`D€oC&JV<’Z PA3Q1*223ô©I†oBkែhMIþû½oPែhMI½oPÙ2S6, M!"@-7Y.?oI=[<%$('3 -- <-\ƒ%FuŸáPo½IMh‚ŸáPo½þûIMhÿ€€#< "'&4762 '&#"327#1"'&'&4?6262Ëýµ4—5ýµ55K5–5 þr¼*9;)x**–%<'k5‚xý& þiy ,ü>*ýµ55K5–5K55þ÷þq¼*)y(;:*þh )k5–=x*ý& ˜*xü?ÿ€€/%4&#!"3!264&#!"3!26#!"&5463!2Àþ à þ à &ú€&&€&ÀüŽ€ý€ú€&&€&&ÿà19#"'#++"&5#"&5475##"&54763!2"&4628(3ã-÷ &ÀB. .BÀ& ÷-ã3(8Ig€gIþ`ƒºƒƒºà(8+U„þe&þð.BB.&›„þ«+8(€kkþ€`ºƒƒºƒÿà%-"&5#"&5#"&5#"&5463!2"&4628P8@B\B@B\B@8P8pP€Ppþàƒºƒƒº@þ`(88(`üp.BB.Ðþ0.BB.þ (88( Pppͺƒƒºƒÿ€€!%>&'&#"'.$ $$ ^/(V=$<;$=V).XÎþŸþ^þŸÎÎa¢aêÙJ`"(("`JŽþ^þŸÎÎa¢aÎÎ,ÿÔÿI4."2>%'%"/'&5%&'&?'&767%476762%6À[›ÕêÕ›[[›ÕêÕ›oþÜ þÜ´ ´þÜ þÜ ´´ $ $´ " ´$ $ ´´  êÕ›[[›ÕêÕ›[[›5`þÎ ^ø ø^ 2` øø `2 ^ø ø^ þÎ` øø ÿ€¾1%#"$54732$%#"$&546$763276î68¶þÊ´hÉÿf«í‚&^þ…àœþäÎzsÅ™,!V[’ú”vn)é ´6¶À¥<þ®×‚í«f{ÃËózÎœ™Ì}))NÏs”ú’3(@ÿ€À€ +4&#!"3!2#!"&5463!2#!"&5463!2@&ÿ&&f&ú€&&€&@&ú&&&¦4&&4&ü@&&À&&¦ÿ&&&& ÿ `ÀBH+"/##"./#"'.?&5#"&46;'&462!76232!46 `&àCÐ6Æ@Bb0€3eI;·Ê:à&&à­&4­L­4&­àþFý€» »Z4&«wÑ4Å) €ü€'' Ï5ãr &4&&­4&­­&4­þÚ…»»ÿÿ}G†3#&/.#./.'&4?63%27>'./&'&7676>767>?>%6}­)N @2*&ÿ@P9A #sG–q] #lh<* 46+(  < 5ºR5"*>%"/ +[>hy  ÿª÷K !/Ui%6&'&676&'&6'.7>%.$76$% $.5476$6?62'.76&&'&676%.76&'..676£#"NDQt µ-âokQ//Ñjo_  þÿ’ßþÛ  ’ß%&JÁþýþæþôÕ‚‹€©YJA-‹Ö.-- 9\DtT+X?*<UW3' 26$>>¬W0 {òü"F!"E ›   ^f`$"¹_]\µ<`”Fí’`”FíŽDƒh>Cw·ls€©†J@‘ ;=?s  :i_^{8+?` ) O`ýs2R´DE58/K`€˜ &1:%#"'>7&54&5#"'>71654'6&5%z‹xbŠŠþ³‘»€€‘³Ä(z‹xbŠŠþ¶’……A‘³Â£CC=°gg°¸þ¨³þÚF˜ÇÈ0™˜ÇÉ–F(´U!ü,CC=°gg°¸þ¨³þÚFšÅÃœ—þ É–F(´U þЃÐf5B_<õ ÍÞ<ÑÍÞ<Ñÿÿÿ€þÝ€ÿÿÿÿ€„€pUÀÀ€À3U3€ô]€€€€€€y€n€€€€€2€€@€€€€€€ €€€€€€€€z€€€5€u@€5€5 €€€z€€€€5€5€€€€@€€€€€€€€€€,€€€€€€€€€€s€€€@€€€@€€(€€€€€€€€€€€€@€€@- €M€M€-€ €M€M€€€€€ €€€€€€€@@€ €-€€€€`€€b€€€€ €€€$€ €€€6€4‚€8€"€"""""€€€@€€N@€€€ €,@€ €ÿÿ€P’ÔBp®<$‚HÎú<¦üTÄfüT’à H ¨ þ R Ú , š D x Ê 6 \ ¤D¨L¦XŠâ*ªD¶x8”ðJ¤NÀ2f²ö$P˜Žø`Ö"Vt¤êLv¤ð$~À*‚h¼þ 6 n ¨ â!&!v!Æ!ü""p"¼#&#˜#â$8$À%%f& &¼&ü'`'Œ'¼(*(‚(¦(ì)")X)¬* *B*¦+,n,ä-z..:.’.ð/@/ˆ/æ0D0¬1~1â2l2à33R3Ì44>4¼4ö585œ66V6¬7"7²8P8à9|9Ê::b:°=¾>>l>–>à?R?Ø@l@š@ÔA²BBxBâCCDC®DZDîE–FrFÔGDG²HH®IFI¢IÀIÞIüJJLJ€JžJ¼KK\K®LJLÈM*M¾MøNhNìOFOÈPPjP¾QDQ²QîR2RjRÈS2TÌVV’VúWLWxWÄXX\X¨XôY@YjY”Y¾YèZ0Z~Z¼[[6[’[î\V\t\¸]6]x]â^@^ˆ^ö_d_Â`$aa„b(bhbÐc2c€cªcþdle?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqï rstuvwxyz{|}~€‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ     " !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abÒcdefghijklmnopqrstuv”uni00A0uni2000uni2001uni2002uni2003uni2004uni2005uni2006uni2007uni2008uni2009uni200Auni202Funi205FuniE000glassmusicsearchenvelopeheartstar star_emptyuserfilmth_largethth_listokremovezoom_inzoom_outoffsignalcogtrashhomefile_alttimeroad download_altdownloaduploadinbox play_circlerepeatrefreshlist_altlockflag headphones volume_off volume_down volume_upqrcodebarcodetagtagsbookbookmarkprintcamerafontbolditalic text_height text_width align_left align_center align_right align_justifylist indent_left indent_rightfacetime_videopicturepencil map_markeradjusttinteditsharecheckmove step_backward fast_backwardbackwardplaypausestopforward fast_forward step_forwardeject chevron_left chevron_right plus_sign minus_sign remove_signok_sign question_sign info_sign screenshot remove_circle ok_circle ban_circle arrow_left arrow_rightarrow_up arrow_down share_alt resize_full resize_smallexclamation_signgiftleaffireeye_open eye_close warning_signplanecalendarrandomcommentmagnet chevron_up chevron_downretweet shopping_cart folder_close folder_openresize_verticalresize_horizontal bar_chart twitter_sign facebook_sign camera_retrokeycogscomments thumbs_up_altthumbs_down_alt star_half heart_emptysignout linkedin_signpushpin external_linksignintrophy github_sign upload_altlemonphone check_emptybookmark_empty phone_signtwitterfacebookgithubunlock credit_cardrsshddbullhornbell certificate hand_right hand_lefthand_up hand_downcircle_arrow_leftcircle_arrow_rightcircle_arrow_upcircle_arrow_downglobewrenchtasksfilter briefcase fullscreengrouplinkcloudbeakercutcopy paper_clipsave sign_blankreorderulol strikethrough underlinetablemagictruck pinterestpinterest_signgoogle_plus_sign google_plusmoney caret_downcaret_up caret_left caret_rightcolumnssort sort_downsort_up envelope_altlinkedinundolegal dashboard comment_alt comments_altboltsitemapumbrellapaste light_bulbexchangecloud_download cloud_uploaduser_md stethoscopesuitcasebell_altcoffeefood file_text_altbuildinghospital ambulancemedkit fighter_jetbeerh_signf0fedouble_angle_leftdouble_angle_rightdouble_angle_updouble_angle_down angle_left angle_rightangle_up angle_downdesktoplaptoptablet mobile_phone circle_blank quote_left quote_rightspinnercirclereply github_altfolder_close_altfolder_open_alt expand_alt collapse_altsmilefrownmehgamepadkeyboardflag_altflag_checkeredterminalcode reply_allstar_half_emptylocation_arrowcrop code_forkunlink_279 exclamation superscript subscript_283 puzzle_piece microphonemicrophone_offshieldcalendar_emptyfire_extinguisherrocketmaxcdnchevron_sign_leftchevron_sign_rightchevron_sign_upchevron_sign_downhtml5css3anchor unlock_altbullseyeellipsis_horizontalellipsis_vertical_303 play_signticketminus_sign_alt check_minuslevel_up level_down check_sign edit_sign_312 share_signcompasscollapse collapse_top_317eurgbpusdinrjpycnykrwbtcfile file_textsort_by_alphabet_329sort_by_attributessort_by_attributes_alt sort_by_ordersort_by_order_alt_334_335 youtube_signyoutubexing xing_sign youtube_playdropbox stackexchange instagramflickradnf171bitbucket_signtumblr tumblr_signlong_arrow_down long_arrow_uplong_arrow_leftlong_arrow_rightwindowsandroidlinuxdribbleskype foursquaretrellofemalemalegittipsun_366archivebugvkweiborenren_372_373_374Q¸ŒQansible-1.7.2/docsite/_themes/srtd/static/font/fontawesome_webfont.woff000066400000000000000000001250641241061774000263750ustar00rootroot00000000000000wOFFª44äFFTMDepaÑGDEF` ´OS/2€>`‹zcmapÀ jé5°ògaspàglyfè–¯Ä2‡÷head™˜16\Ã"hhea™Ì$ ‚áhmtx™ìÂÙìloca›°õqµêmaxpž¨ ÝnamežÈf¸<ešpost 0 ù¾2Í¿webfª,ŒRQ¸Ì=¢ÏËT‚0ÍÞ<ÑxÚc`d``àb `b`d`dl’,` ºxÚc`f}È8•…¥‡Å˜¡ B33Dù8AAeQ1ƒƒÂW6†ÿ@>£2bDR¢ÀÀR xÚÍ‘½JQ…çn~Ô {ÇßÄ(Ëf@}‚°±ZRØX·Hò!•eð $¥6ADtV–â $Y,åLÔ¨¹n\lÄÂs†‡¯˜!¢ųF*rRÕ(©÷œTÛÑö©D)²É¥6P‡ÎéÊ͸î~Áó/ 6ᣂháœá}Üc,¶8².Eñ¥"5iHkHÆDÜ ïøƒG_xF%” Ž&ÑÆ).qƒW6¥$e ¤.Í ÏÜšªÙ3»fÇl…™ÁÝà¢?ìz]7Ï«œçgy™—x‘xžç˜9Á+&môX¿êý¬GúI?ê‡Ùƒø)•¦O¨²"³¾âüM¥³Ó©•ÊýØHþŠûâ2tnÿÿxÚ¼½ |TåÕ0~Ïs·™;ûÜY’Éd2ûd$d¶Y†°“ÙĈ¢.  ŠÛ(ˆâ.*¥¶jÔª¥«]ì×jñÚjW}mkWý÷‹mµý^­µ¶?[!sùÎóÜ™É$$¢}ÿï™{Ÿ}=ÏóœsžsÎå·ãx»„Næ¸lÈâ!Ç´Üv2¼] Û.qÇ8ú¸ª3¨ÿÌœô¨˜çêÑã’Áêð¸¤H(Oe’!ÄÓ©H†: =ÚR¼r¾xÜ7š§OÈon‰6zż·1*.ˆ`t‘‹§âøÇs䊖ˆ·Î`¨cubÖÑ‚‡ËJ­$ÕC’^‡8Þ›Êd!“ìðHܼ-ç¯;Ë<|M¿`Mq¼7àsf{c§<>ܱ´ÅínYz.¾¤ö/ÅÙÕü÷’ pB'GXòØ™ a×í\þ»N>¢qbwf¢AÁãtã0x„¼öv‡öÈp)/¤2QíÈ×^»S;~ô’KŽ‚^r5¬‰L²žX˧â°úê±—ÕŽßùÚ×´#1:;܉¼Ì‰ç㺹AŽ‹9$Y­¤GñX<ápyp¬3Ž.ÒÊãHn—×ã ³IGŸÍd{ ëÐ''í Óƒ•Æ´<˜Ì]ÔÐ~Q.ù öXPµˆ‹ ¢d6ËYÔ{¾ó²4+œmu¸Z³áYÒËßÉœ™ßØw,×·qcŸXèÛä¹hà¥}-í3f´·ì{)-rU‰Óè0(¢jùìÎÉ3|1§3æ›!>v¸åî¡ãš[ eèsLû–çü'චilaG€x{xœP:¦üý)gñ.%2ÐÕ¦ô\ɲhtÙ%×÷ŒhoïÎ;É:Cô¬sï˜ûÚ¿Zç¢ÑÜâ–½öÿ½Qü¬^öqîF¸°£*Gç-&â4«R0ÍÆÔL‡WqL|Ú}«ÁíRÝZ¯Ö‹ê&«µ{k;áý×Õ.õux¿“¿ÒãÓÔ̲Å]o~ûms½[²Â?`S;f\ ßojÒf.6Ò%B*u)ô!f©åcb¹S7CØÚº£GµuбöÀ•ð}Ö®¦©›E\ÐÔ×j7ôh¿ÒÖÿû¼RnfLJ´’¶!ǾK T• $Õ#Òñï ++ rv)·g‚bþà•£‡®<(»ƒ™›»}+oÜãÊ>c÷æ™ [Ö ¯kϽþ:ôì½âÖ[¯HoÞuîYs[Ò-ø×8÷¬swmæÿ¤Ç¿Îq&º¦dZ¯ knãz¹Ó¸³¸K¸ë¸;¹‡¸/sœ˜NÅ[ ,ÕƒË3¬OáG*Π¾´ `büÇLªú&.&ÈÇ}lg›â!pq_‘£Ÿ£ÜXŒX•SËW§:U™¸ ?` IÂ…”«DÁý“9‹> ÖèS ?>æä«“h÷Ÿ¢À§±ºE¶ˆ ðRõ|ÒÝzÜÕ„;E<Ï ¤4.50"ì9ææóSÅŽn£) Oò“*ÏèO¦ŠáØbeûÏÉ°È[oU7è­rLðÃÿ°b}„ëlÔ £Ï17ÉWûŠù©ã>zÊj7™“>à×gqÌÉOzÊU…!M:ÿ¿ÏÂGUcFYaǹ©ãªÝÿæX <»®ä¬ÒMÂW9úðÌ¥p@<Õ xJñÑÒMþâ´›ýËü7k‡ü~ê€8¹‹úù÷–±(ÿÍ°•úý~í7änôb¹ŸxGt ¹ÇE]6 #в㩬q|ù—lÑÉJÖ~«ýV/ âè*ÕñRé¿ÅÐõWJÑñ}¿ˆàÙ8OŸáýA§%¢ÏÍlÜ–ñÑá©<ˆ „yqSa^§ZFT ¢-#ˆ‚Œ9Çácýé©ð12rRNê|³ I{jkÿHZuŸlœ—k? j?Zû‹Z+É}¼V³ö~ä––Î}‰.·&.M1#" AlM:åÌf<^$[±õ Àƒ/Ñ ˆ?z=Nºgë;4ų÷¼¤ýQûöÇ—ö<|°å‚† ­yÓ¶å·}ùè-Ë·mj¶¶6|¸˜Ø2€$ÿišrÏKàÿô7 ï¢ µ¥ù‚à’_^¹“c®-WþrIð‚ækð"íY²¤È6hÂ6hü'Vpı}‹UÀE’˜C÷ÓöMæ‡Sù9§µ`u²ä?ž{¨ìp^ª1'äðù^‘¹ uÃ¥£ôeåi¼wŒyDê›Fc\ŒþT<,¹<‚p}Ê8#.œ‘®QIÆÿ´Õ¸\2¤x‚¢ŽˆßcP+ÐÁÀœ-‡&qgÿg=ÄíÍ"j”E«­ cPáîÐ+‡½BÙÍßR]‘EŠ±î.ÙzË´6»E®ÿÕ þM·+6«éÚ„l°-rÖYÿ—Ån7=m­mœ«}w{,–ñ‰ï0Ú,æë£,±Ï†‰‰‡Öp.úÙCü™XÇZ³O‰Ýa¼Ðk»¹Ãï°|ÓîÞf4]šQ,f“{}mÇŒ:ⶰ´­­3—›ÍŠ%z§²­:±²;i°ê‰ÛýÄÍÎŽ.«ÃÈln.w¾Ž‡Tϲx ¿Šô¯+@éÖ€ŽnH’Ei„%R^ÓYFßâ²3ÄiesŠ˜ÂÍ[m<ŸãmÖâÚeEû®"ó—8­CûFŸb “^`[JO˜¥¶¶:ù`Y§pü×Gæ1aÉ.#!Æû0xt`å•»Vòßdµ?K¥bO8õõïÃ;Oä9•­Ö5ìx ÿJÁ“E@‹°“!AaR×J¥ýØíð⦂ø©–?8⪤—ôÂÿî1Xx‹¡8P0›-†QÈ×ÿÁ–Æ« !A-H[Šè¿ÕâdÎ#‘ɜ‗(u²ÆçûÉwiß´-ß |FÿŠt}pvñÜJ–Ú‚P<+a"6éE°Î œ6ÔØ©q$W(fíûæzzÐg‡,É7ù¡ÓßÈc kùz3Ì4+Ú–Ñ<ñ,oôk?ðéu³µé½{Úf«ï;%°áì­´‚=Á g'¸›âÖŽ;;›„¾#Œèà0|ð˜öëcƒÆcpéKÚCÚFí¡—^‚³á8›Ñ*pCa¡¨aªƒ¥ä¬ê¤/½Äæ±ñ¥¥¸=:Ú9Hó­@É™wK:㊠u“À`Jíȼ„ÔN7 ¦› KFwŽ6°¦\–§-.¨§ùf'y¿µ˜³8Á…Áڻ˜kõÁƨ Vbˆ CÇ$6L+]Q<ì#~Øɤ³ÝŽô¦jÊ°œÀçâLàRýªEß7-è<þvO™Ž(hãb\7b(¥½°üVÇÍ´×ÓÑKWxdŠÇ@=ëfxÁãGƒ–sfœZ®Ááh$Í€_\óã)=ýƒàÞws'þGS½–SU(Ô7% Àè¦\¬ÔpQ†¸*íª€ŠÛ‘Äí¢,=` Uð" )ÚwL5&­`3<¶pðï'˜9xð$¨!Cf³ö£rvÕÅàƪ ;IG¤= t&i«¾Ç雡Ζ ˜ LÝÖU-T › 9ÛÏ>´©÷º´a¶É 9­f3ôZÁ|HS ƒ ŠXèʇP+$ø‡WÈŠACVÕwc¯êáO@ððJ±ë|A×Y#Cqß1ܨjßQÒ>>çK+ïÔ’¯ðð®f'fRxD 0Îäï{ºIcm8\[üuwÕÙ¸:Ê!¡x8;ti…›)–½0,ŽØv{0j Á]ôä±%N­`4¨1’©NU+üøÃV=TÚ”¬ìE‰x/Ä#a+Aœ-ÙAÏûz°Ë’PA2“žýˆÚqR›Ž†[îýaùÚýÊbÙn50‚á"íG_CÕîuÛ á"§å|ñÆDà–%oËY 1Þb¨UöÝMSB'ø_ÚsÉæëqUã3Qn![„ …£ˆ°ŒmÑHyà1ÛQANÊ ;źRÁsºÁÉ…XÛñ¬þä´-Ú;µ¿n»^MÑ镧Xøõ³÷ÿy©ÁÑ¢ÖÒþa(v¯ø}‹:îõ ¸¶Ý€Ù`D$Ú?´¯]|Þõª^D<¥è[tÃ¥Žs½*¯ÒìrË=À"ƒ±kjœ‚¢aJ~0Òô)üéÒô)üꮕzJ'¦z?Ê<<#3&wc¢cÌC9Áãx½0T)îŠÿðè$ÏÜ£´>a°š ÌÖ¸ óØèOÓÝÞ]}ªSZÏ_J zp9S”•Ï•‰î `;‚òfÐk­¿bÖlµ9Õ/ß³0:²Ÿ¶ÐFñwÇQëñ‡ ""¸Õ·«çÔ¬ cH#ìU‰À”ò]®oy¬ÃF^žWÿ¤ö+í«Ú¯ž¬Ÿ¾|áXÜÚžo¹ºö@  5²ŸÜòø½3B+·ÇÏàÂ.óY›îéÓŸÖŽÝ»é,s×ÂàRܶ24ãÞÇ?5/îÙó¢ög½_AžFçdû‹ØŃÆÃãY­j_ÓŽ±}X‚A\ªÂðqºÂaC(š9¨¯A /A!ÏÊš>yiœ>‘”™Í§Zyv¥à´ÈŸ¾@±ùâ5áp ýÅ}6eÁ$kÎÃ{ýb¬Î]ï®m×Z‹ïº˜XÇ@÷»oáœ-díYÌmû8mÂ#µÊîiÞfÄÛÄ8¤ðv’ y%ÅGîœþ¹Û,æºx¢ÓµdåÊ%®ÎDÜg±ÜŸÓ~nA0MÈ rkôª[n¹*ÚŠNùó> Yí%­8[Œû®z[æÑo>š±Õ»ý³¿¡¥´ëÖcLÔ+X„Zßz°CØ×ûjÑëb’õœ™ùæé=¤ wV•óâ‰Û€'~žst­º#i!ü£U(ò?t@)i·tÄq„ÜÉ4èIÇ|I/JvÐÏÑç ®˜òy­åÙ»ˆÿEüÑ ž£ÙF®ƒR>Kò §|f $,! ¦?ŽÝ –φ“û‘àZJ}™MùãɈ#©þ7~½ø/ÜØÐðþõô\ÛÐÐËþèíÅ¿kÙßÆÞÞ£7Òd½½bþØõâuÿÖ΋~¦ß'¾Åöèú*E #B bŒøò@7Çþ­Âå1ÍH¥cÅt<=‚át>N~L4²_Ë¥cš+#?‰åÓ0œHÇ‹™D7½OÞVª+}ªÚD=É@Üi\$ùZym À/c4.ŸùíK±@fÂÊÈâi½Ù<§ Îs%¶yw.·!i+¥»p9gS¸vãÙ–qœ>':0JòʬK¥|²äeÇ<¢á (1w/dâc¤\•_:¿Ñ£ýE½lÎèæÁ;ý5 ðL$f·äfàEÂûyw³² DµM!VdpXTW(ᇸ…|°d™G{'ºðÌÑOÕ™LJÍü§ê3˜&“øñ¿f+²Ô nt‡Ñ±å¤!þUOĨ -Z¡âÔïs?!–ÃwéÀ¦Œ |ê`çµp›×J$Bjm{D[¨-Œ¶é~·WÌ-ácÿ wZ Aø¬¶6Dý¢ýÆò^ž—ô½ÈŒ4Ç5é› ãû„Ê ˜u”XÖ:†)Ï%°¤ø7£ôwŸQü Ó»!¯¢ªeDÇ]F,êŽÓ!ÃCþÃþÆÜi;€£{NgãpQ§=sÚE¦ØÌ0’Ðçí AÊœ8ìj<Áí(Éè4sˆkÂP1 Ä£KÈÀUaW•øÐv~ñ;GŽ¼s„¡(Ó±<}Ž$ÕÍiÂ¥7«Éâùcüd~èMJÚ:ÊÒñø¼yÆÂ…3n>ž‡ŠÃo™ŽŸ‘[Ž³Ä#IBÙ‘É2\?«Âl@"Í;î¿Û%# Û½ÈfRm$†ˤ: 'ˆÉùÅç?ë¶RðO'Ò%¨IðñŒŽ9RÚÙJèuA<áHã&`Ó/÷èÖ„›T¯~±Gy=Ë3®ÿ¸A½ìW [ý²Ül£“%$êkë 6±Xå…7·„C ¡<óŒFì´\"ou]<¸èñµw·{¸gÝê2ò"bFA2Ä/n¹ÔnqúLR<Í,½rº®uÍŸ3´lYµG¼®NÄR Ø ßésgUßrzÍ`†ØBij‡µ¯kŸ¼§5Q++vÁ LqöƒUð>cÈ7»#…¿Ázvlð"Hu&cûy!ÕW瀦ÕÇIÌ÷ˆÿbWv–ö¦ýŒ/±…ÛW™ñ”sþHsàHØ“MeuHôèÀµÛ¦_°" ‡4nÆ[šxz¦˜ƒó¿Ô´qª9Xñ‰éµå9DBØ tüÅZ™ñõR׫‡ã#}j’¡·ˆcC§Ñb¢CïWª†þØß'pêátþî8Þ »ÅûïÜåË\Ü÷“J‘J4Ç™‹È˜¸qß1擸RK)à³0&ÔrÞ)œÿÚ­‹FòùR»™O,K1ùh·ãcúÇ·»z´«Çúßéÿ'm>µûc¶ùCx‚o©§ðO7ª¾§Z =ÅCÂøcÌ#"’}Œ›*f*÷H¥4¸l2çèß+NaÒÐɳ±;ÿ“ÆTçwÓû””.í ÿMÈ S«Q1!h´ZTý°J¬)ÇÙSÈMt¥áG¨ÈÍî§S÷¬º““ö±tÇ ó¨$ηC´ƒŒiÅ&ŠG>nÉK~Z‚.–‚.Íø1º¨ó3™ìr›?vv–ûT&âë7KæsS»èÈîbn÷‘#»Ia÷¸ÇYg¶$(3ªÙ!ªpÏãå˜#»ƒƒªè¨Ðm²ÎC¶r®•Ž$¥ƒ2H¾¥²ŠuŽǽØç$¿}xûöaaû±<ä† b °~Ht$î©–¶ì4áöbAËXRâà±0Kð8c™ …’l$Òo‰Û8 ©ÉZ¤ ¸P6!»“nH!Hã f‹$>¶Ïˆ*e7#ŠÛÖ¿µ>O.÷(rñ÷2>I@ÎÀðhAߊ=® =ͤãoÅ0Õ¶‚–PÖk·{³¡EÓýýO½¢a¿^¹û㣷þæÌ@88ó7·>j¼N_¯Ò¿°ŸÂØL®‡[„­Òg“‹ã\z² ŽmŠ0Ú¨EõÅ .MŠòlÊeœp&kÇ_±óðÎ!ÂÚ#Ž 6.?²{”A9ŸëÍØxÞ<ÃêôzFòbÆœ­q‚Å!mDØ°AÙà_æ?ì‡!,¦sˆ*åÿóY½”ÝGje»‹‘$]àdcßµ,ÅN^ÔFŠXño€à?–²¬2þì>¾…[7Q¦wFG‰¥U=£¨°×£ê÷¤Ý Ê’êa«žJö÷Èô&‡I!a—Å|¹‹Ü ‹êìT¤íåÞ9ý>»êþ‹–g«X;zÙîé¼× ØÅ3³9"»#³—^rËS[‡qË𩸓“ˆV,÷SµÔ‰¾°Pîå/UÅRc7á5-ûEsaïíI¯ ìðùCû:g¬Z¶rά„‡m0˜$Uîûu8×mLBÑ1Ù´22उ¥;™ªßû—¦ëneF /ŸSÅ"I®?þ¬¦¯F[QSs1¾A&7áëâ²Q{nüT*¤2•N¥ÂàÌ[_bj´0+-¤¤Ãs—(ÎçÜÒ9ÃXZ”MUT`,,J©”OYº93ÞWY€ÉBQê=¸ÜOpj qTD…˜“>1B¤•9UàØ…¦NúÀh ÑÀ‘û?^zu|mU|ªƒ”aü.*4A¦ËíÈdùŸ«>ŸZœeª¤òâeªÙw,ç3«ä£R\Wƹã^g2T馴L,ŠjX¢LVªÔvräÕwRͳ¦h&6ûŠ³X[ö”øjµ“´%U©y¥^³A¤OU¥µ‰†IkÃÑ+žõõjñ:qÕÎ0"ÁJ»ÅÖè–c/{C!¯Øî%g—O,ø\tE¹q²‹¶Ò ?îP'ªq% ¦m0š¯ö‰¹1ª§šŠ—a·\ÏIµHã(¦qåŒå•ô±óVºæ-õPf½•äétèÈ tèp`èðáÐÑ‘Ã›é˜šÈ Ì#‡³¼ +å—áä¤ò½ŽñW³´ªÉj4ˆUj!†©kGÇãcDWŒÕ·&Æ·eb#*µW×;¾Æ ±ùÆ$%„“:ŽSõMÍTÍ­Ç:cöĪ¦…L/±¯ø¦.s÷À§>žéßLâcâÄÒ>TGgÜ”0y³¸3#·Å¶Åúc1ÍoÆб-FnÕÌ£ù´ºøVtêeî:ñ”ÐezËrYmLëÊHŸ½z7„þ–»56‹Á›š/ˆ^ÅZH!•(îÂRéõ¼ oÐw<Žaã×½¯ä¨6Q$äÐU†ÜŽ®7” 9tå¡´OŠqÒBÚu6þ'Ø8€îa‚h¹‰âB¹RÌÉy ådÙ©*ù¥R»Ê­9¹ UºG“ÖZ¢}[&‘C,×ÓÂîjSm@ÞmT’ÇŒ¯OñÜÙÓ“ìè/{ŽoÃ5êSO©ê:µÎG¾:tž{'´ ü°ä¥xiʱñ2¹2ÚZDǽdmõÒVR9ɪö‰‚s=´¶å÷ø\ïtÂVZipŽN”ã ûX³vÁï±j§ šC*M·dBªåËfq sž¨§–jI[£ ¢Ð+”Sà9œí¢DN+2êÜ%¯ù{ÞæÝ'›íÆt(œjïolï½€E¶„‚áY µŸÐúáŠ0;ùÒÚC+~Qã,CøâEt!]|øB¶œ.|881.‹ûõ0ó>üVìN?!€pSå®À´©³—ÆËF˜Ô<§+ɺFP/.ˆ”~gP¢Rl¸r]™©äT|Êø8¨Ð·2Áÿâ‡IBÂ'ÏTñ×~¸8ôɲÚÆ*,¼J‡È”B›÷hëèòþ­ªž‡ï{@ÅçyêžÞü9æQ!ÎR²,4ï±ØÎ9#çdºÉ©0ù2‘Éq"PaÃtœ’†\S´¾ä‡WÖ’¿ßô’ÓbpÏ‹Ú´h BV¸%tBý‹dïÃû‹¶3Öüñ·É{ëŽÞûôj/h¿g˜õÔEÏÃ܉4¶¡Gª¤«¤Ÿ­Œ¿–Ölì̆`ÍIs‹Çû©Ø= É­˜*Ž‡ ö*sH>Ÿî×~‹çå;˜©pÄ-ñø’øVLЯã%i±PªOçq13¨ðªô‰b”¡Xˆw%RÉ–±b.5gNŠ´W±þx*Çžä21v$cëOcíÇÚÙ©Ñqˆ¼Ô/æ¨Ö>”;VÁ~*Ç©B©K¢ZV¿eE±Ž`QäÖH6C ’þ¶Ð¶–ñ–§°Î|Yß¼<˜¥nUp°ÒØb¥´—i|âH1Ü">ʧ NǯñŽtLGt(¯‡b:¿Å± s§èÈîY ð^¢é¨ü¶UÄCÌUÒwo% ‚}u†’Ž2ݦQJjdÓ§>¹cSOD6»Y6ÛøëÒŽ µE8©3’_À™2§ïÞœ'EŒ6—ÃèÓ²þñïï‡{(&‚©¸qçi›Þ¯g K//?&×e…Cº½èÌ·¿+Ú×ïRuá]¬þ.ÀE)ï¥níëÔ­(0pWIbþâcé+BÀ4=&_ÌdiLïcRñ’Ì åÄíâßÅËôöMÕŽ©ÚÍäì&iÈí&¹IBî™´Ùû¢®YZ`­¬ QÊŠêê1}QªçBÕX˜†;ùàd¡,}©.‚uñ:-5_LË=ÎÄj…B©¤²RªNƒR:Šj À†_bLÏN”tU¡éxöâÙç+íe¨ö™$‹âZë|9ßù­Úû Òµ÷[ÏG]+(èÔ£@ÑRŠÒÞ‡71øbŒþ¤ö"SÝN~Ã/Æøûï/Ç@’iƒ¿X‰©>(­2I:Ë;þD^M%h⨪BÚô-»¼å“¯:-‹Ë…'q*Šõ5«¢8\ÖoYUq"rü¯ÏZU—åY‹K…óÈEfÉ`ÌÅ{›­|Ç…íÊq΃TóŠ%9Ò!·Ã]Âû’ìÙ剦òœìÐõÔªuÐtJ‹Y[a§sR7¿ÒáᇵBÔ_ðGµÎï^ëkÁ™#¿îllñ]ó\#<‰x”®¥cSßñìEÙ¯í«÷%”„+œ¨Iôí|<?çÈMî\s5Õ«·€tÖ¦í¹‹.l—är_½`•,rd03Kæ)Éôe?{hwÔi㉘’pxöíÔmÁˆ”j£ÚâÄ›Ût^Æèq÷&½S»/;ÁÍ8mhè´sXwÛuYÝ×Çë¾áŠ´¼ .ÝwæÊE‹Ö'‡òM«v^ÿ…Må7”BJ¸wÊ´‡˜ažxw}/.Év6:ÃœI st‚nyÙ ¾½Rþðݺ W÷‡o„»á¸»ø”ßuÍ×üþ=«]ü…®Û´Dñ=-q›Ëuü†Xá7·‘ÜÛ»¶\ù-ª¢ü­+·ìzûÅ¿ÿÌlôí—ßïZ½GûټțÚ[ày#2/òx´ÿzƒéñËTÜÈÕrÝÜ\ît„ül+°¦:'¶3FÛYâ²b *õL[ê`Z¬”ׯ"-„T;cC xRG³ñDmÒ²tÍ&ìËäÀX/à&¸@Û°u†â4ï±O»óok]®O `9c}FqŠ¾h ÄÛcÞ5(¸ i»~·ä¸àÊËžè=ëË3x{oaí§¦‘‹ÇºùW™|»h>z†}Û?ç×Þ»ãl»YuªDÑÚo}£ÞŸ¾oA8·ü Ïîs¾óí¯]¶=÷Õ³ô¹³ãþô.ƒ§…¨Ø)÷$ç°‰iô¨l·˜Ï6BxðìvSÞ">4<£'Ù ý®âdÙë²ÔõiÜeç-IŽÇ&¼¡Ú_aÞ”öãªtÙ q± Z*%r/Te»À“‡ 6CÓ ÚðD7aî<}ò ÑÝÚð˜ê¦©„+-8 ùÔ1¦1ŸßØ—ëÛú Côzƒ9–-—ƒà(–ý¡$A&eKŒ~‘%¡ UÁƒÇ™ŸCôšaH”è\ÏâR1YnÕ!”[…*q…ò]v7 QÓ*%2Ù€ éª à¬D†ð(À%l­–tÀƒ “í‘*©Éý]ƒž@2Ù?m„©Ó%£V ÷ÚÁ­ëR}©Yu³KI¨ÖuY½&9Áµ/íj® ¶Ö7Íí^sæóô2&–s žšž]ÔTÏX £V?-×/[½áÖîÄ™_gñTïQû¿»œ ÐÕÛÚsQߺ+–­N†Xæq!zò±{Ü)jŠ ®(IÄ=,žHÇ3qzŠYjŽ¡¨âžÌ½«ûý/hÇfÌqÔ ¼ 1¹ÝÝT0=ðÔïÂÀ7þŸæ[µÏh¿ù¼áËs­âq‚`l¼•ÒÞÎÖEg€t膿|aóçÇÓüI¦9ìv1¬¨|’áþà;zøÊÉvJ®þóÚÃÚ"íáçuM‘¶®­Í­+ºÚt/5x¤é–ßJÆÆ|¤ÿ¡öìSOAßucj î%„(Ÿø¼±¤ÕÙÊ|bn—Ô/ô³ígœ@ÚU(;Ÿæ+u:u »¶R&.¼¡Õ!-G),–c妱\»k9‰Ž3V“o´è1òíMxS§ÜøœNÕ‘[Ë”›Î£NTîUå<žÙ1ªå¥ÛÝjå» ÆiÞêvBL |A—Öoèô.2Ã"¼Iz‡'rTÏ`’‚´… rj— 9[ÜW 9»qX&y›VpÍriV,Ð0ªóWÎk^P$‡ä‚aF”ËyGË;j¨š©`‚C5-ïõ ‚¼¹`4eцªøIyQ×ážMmÌèRBéMµe1@Ü.¹b1Bz–è¦;‚—‰c0í þÇìõã`íñ·AkøÃÌŽ ’žùÊOtÖ·½Öfd¾â‹§™î†þÇ4®&Æï‘ëk{;§÷Y“ó>‹N‹³Á“ãUúv®“ï•êï#¿oÃñ܆}û6>Éð†}üp‘ùù}÷Íé&÷ݬC~N—Õí©´ÕÔ95¾|yMƒöd˧úŽÂéX†.!NkGF _êÖ¾,B©â þ5D´É…¾@CnÃ7Ì>k‘¶SBUc(o‡#‰ÉÜp ˆ&^ñŽ]è’.º ×·UׯÂoStýVÝÎ \å2VßË 's|A¯«|§<ñyü}ñ¤ŽÝO¸ý-Ýö–l|ÈÕzb :-rŒÿ}¸ž,ÁÝ—äÇ~T lLÔgœ]5ªêyÂQ ŽL× ò£H¿té)†«¿X-ð3ŽÒÎåØ©˜AüVGn½ˆÆÒW<ˆ®—n,ˆ¯Òåÿ!%”Èœ´ÙrsæÕΙ߽aÍUâõ¿?­~}[úÜÅõ‹Ï½mÞλ}5÷~iû÷nÛ<iîæ#»G™Ü_Ø}„°ÖØ8·ô]µ¦^•wžÝÑyi7Ô’þ]VƒÐ»ÖñîþÔ‘UNãt c¹ŽŒk¿Ê¸ÙÛuÒŒmq'ÙOhd÷…†Î‹¿|xßÞ½ Á½Õ ![_½hFâÕ»nßûjñFr¼_]›\eÛ‡âkTS®•ë)QUÔ@¦,ÍJ‡8{<(Ù=AêæCnrµ)Ý€Ò¨TˆÄÙÙh}É4¢¶L…|ÉNáèëT³»9ú½\ñj)ߟ>Æ¥ûûÓ>ÉWýÎ}Ghì40±§ÑçòÐ=¯ÓÌÉk…ËoÉç³ "}²1[$ÝÃèß…%ù*:ÍŒŒgÊJÿ2åâ„ì-1ætI¿”3Z²t™-«…>·}x»ÚÔ¼l{éÍw“Ø·ðC¯ù—67ú‹g?yôÑŸ…ŽáG_Ü ç ñ­áà&‡E‘–­:c&ÿäðöíËš›Ôí¥·Æ96ñÁÌÍKý䡽/>: ϾøèÑ'µ†ø<9›ipź¾òZ³áZ{gÈórw”;^%7¦÷{樸ªì¹?Ä`ÑÇ7WTe¬˜ÌQI?žÀM†Öòǩ¸?beQUm/î9X¾^¶ÊñßÉÌçñ‡¶ àÙ¢?µ¼Õø)“;Ü)ËÞݪI¹,Öh2ËÞ§MNð†›.—-&å.Yé±{͇k%©ç š4ÜRÔ`¦IÍ]6¯ “’ü}fgRØC V—Ëe0=BÒi¾ï>‹#)=¥ˆd“$\!$–û>nú’I¦ ¹GÒ%‡v×·j"MísÅ,vËëTó…m56å“Šû ÙpcQ±.õL‹×€ÃTIj2š ËåuNë…­ã’Ú<ía/qGn³ÛêjwÔ üÂnBÜòzëlvŒ¨÷Ò ž‰Q ›Èç­·ñïþ;¹*{0ñcŒe—–ÍÌád§ÃîëÞ¯à”íHÒ˜‡ ÒE¨ÄµKÍ}[{æ?V¯»úþhoR Dä%£öz·rõ߆ùp-Ì']w\­¸ëíQ$ªw‰É\æŽèýW¯[­ý퇳CãÎkö{¯?Äߪý×ÛìkHÑò²$ 2OÅBܱƚE?Û}ëÛ\ñÓE51w\Œ$Iæ­vkíû„u«6¼»°á/+ø<Óìâ.³šô Leè½…ÂBT{JIWìWàCYo¸"]le°ŸÔBè í§tQRŠŒÚáÃTôZ7­#<¾´CÊ ùjbMž¬¯mJ؃AK¬¾ÍÛ.þ|ï•1q¦]¶`K~†1ŽXînž9ôÌU;=ÚÝ?ÁÝ<½¥±?Mòéþš½ýéÚ+÷5ÇæܲëÌsse;}º¬j7µ]µ£%Ø\SEªŒÎˆ‘­¢>`"U¾#^ºÇÓT'—"Uå]ŽI¥RSa•Ó†î`²»2¢•áj Ú\ig$ nZ“ßûs±ÝÛV³ƒöDStZm\Èzšb5>OêXš?¼åÉöHdÿªd"ÜhªQÛgoŽjï°1 zv柽`ûm_„.>nœ!躢ÙŽîÚùÁ%‹íßé+‡Á&Kż3I;ÄyÞ–/÷mÜ4ûdz;Î?|Ι—Ï›?'Ú´rµ»cpo>jÓ¦=x@ÜìqÏŒ†–èv”ù£óÛ:Éj1Ÿ›h•X9öüÉf‡«×%ÕáIo>[yFýÓQ [y<2‘¼Ê–pÕ ¶ ¥|ËÜ¡ [®Ø¼¨ÆÙã¬Y´ùŠ-†æ¶ÒHq¹˜Ëc%Õx†»PÂ6g‘_¹…«$ÓoÝHž€h³hL”ZÇ*y)îÔ¢¸CR~X-ŽP!Gf/ ô*.8$Ý>‹.ô®Z˜gc_‘⧂l")šKv‚ˆ0Gʺ̺=jO+ÍqÙ¤#‚»;±õ›Š,‡åd:âáÑÍa÷Dìî/úÓû°`çâ…3aö"²øO¯¸y1ùÏÿI¶uMÛ ¯Tc{{È7~™š7/•œ?ô ¸ãþwmî+ÞûâÎÈŒÈeÕ¸ã§3»/&*¯:*á`¸mo¥æÌ<£¢2IG‰>¤D£w Äîð ­ª­L‡êÄíB_üs*æ#Sç<@†‰‹0ÛjÚ—˜­7;êà¸ïªç §Û§Ô¸ç+4ÝG“Ù0®×mW+T,INv—8&îKXŠ¹Šl33ñF…ZŸ,îÔ¯ÉmOªº$Ò e!_–°,àËŒJò+¨À$ËÇni>zÅ9f'ËKát 4Vú”Š#–SÒ„ˆ„š E<õ 0ÂeGvSe|³Àz¢”`¶†˜þý“ƒ"$‹¹*È%r :XWxT®ÞÂ-¦wi¤ =±tÈ%ãÉäv駰ˤò<è÷.lK¦6QJ̪te ?Zr‚;*|÷·äö£ù•·¿¸£9¯ïžÛ¿ËiÅ)ÙÕ?·»>žnÞñâí+;!ˆ-£ìÓ`c'¹ý‘Ÿ-ýìûC?}¤þ³/åÞµó41ÓLf–¬Ÿ¯[É™¿~I&9nʈ§í¼ka¾±Sç‹vêú`}+çá¸ö¦sIîvÜ?¤DœÊÇ'<²„ŽDÉë­zÓ—+"¥SIj¯ ƒKR ­”=—è蕈#¦Ë­8.^\ËÞKÇ'LmôáêE–ñÇ÷` iÌPÔ-³Åh0›;ŒFƒÓhL‹…çÅ/)F{žö.»Ãî˜E‚‚Ýοpd÷ˆÝáQR3ן=§é´ØtÿÖDüÌδ§/­Ÿ;­)wöú™Fw{߯:ÛårÛ%3â¹-ŠbéY4—ãðxFÊ ÿ›F³É€¿´Y–|¢Ü&‹¢,òb“¬˜DÉhÚe– ÚMÄb"¼b¨á ÿºmƒÛñ׳§K5™Óöž~åéëwkj|>SpºqÇz ¸aY¦FŠ"ÖÚÒlx£Õ*ŠJ§×o³€ Äoà=^¾Bä–í<ŸŠ­÷·5ÈŒ‚f²tøô»y=ŠZ_+±ë¦²6øy÷9ÝÀuŸã†Ï3ƒƒÍTp“Jmžà¨!6(83N(4ħ08عhQg'j,/ÇFÄF ªªå•óT<°6ƒ;—ž§Ty9*Y '5(¢«‡¸™8]Bô²˜ÝÊ:³.¢%ÒÓ²Œú5¬.m¨§Ål Æ ¾Îj2+EŒêRWןg·œ?·óÀœ¡ëfÔzj<5g×Î|}æSç_ÿ‹ÝùÛF?uõfþ¾ÃoöÔFçW/½ÿ¹=]š¥¸–/Qˆ ‰ÝI^˜vk]À?Ýç]ï‰9ÁØî­ñdf,þ?½¾q¸É»fZ½§!:ýWàºõ1í™ãÙiõõ—,®Yëm|¸é’_¼ô9³»—¶+›Wy×y‡CñHŒ—¥ :ƒÌb¥»–ÆѽB([b¶p» ÜH:>Ô Þ¯›ú¢NB5=ļËäÞ¼qC]2װ̸i0¯ýõ´ö09ådgGíš:«ìŒ˜âA_o9w¦"»aà{HØZgtvvt¹¬õÍBíÌꉇƺ5µIÙi ð‘öÓÀ‘Üd\ÖKÖmظÙmrñ¦›Y+4×[]]Nc5L|oܲ‚e[ëy[0nŠ8åòyU±yËJÁMÓ3Ùø»1U”ÝGD®|Æиá±ýŒÖm®HºýEd½ ~¨ñ•ü(OœqY²ìçð³*[š¢-6Åã¥é­3‚‚Ç}ÏL{´¶ÉÙ.}Fû~qÊQœ×šægŽç¿•å’V‰ú‡vÇ‚XAÐ)Rz®¿ºÁãewçÁ[²FùŒiÕܳ`àS¿Ô~öío¯GZ^ò‚ÇBþ–æí÷Ì[Ú·tÚ•°þÃÑý· ]4»àLa˦ùVÿ ZñÿuÑÝÂ-äš³E“÷+»„8?펕kûïûšî?zž{æe½JY¿€çÄw97…>B-ã8tósT쌸á@àÚç?÷¹/<ÿ‡;mn‰EûãèøNðþÏh´„#AVÎl^WÐ5ÊÉÔD¿{¼á©ÉQ.ZPpJœöêŸëjÿÝsÊW÷gíÕ²°&É×.kœ?ÿ÷Oóxg8wÿ©.Jijñg¡:Nù«Éñv{(FÃ1u܇ûÿ¡W }l1[f{‡/”u¨mžBgc•õÃoQÓ<êú^Q[²GÆM°”tÓP니_S=º™dÓÔžZÈ-ÐýAg[T)¯Z,êø.Xîƾ1.8ŒXÔãœj!CÅa‹JͦåuY±ü-¥î* ]Î$¤Û3ã R BµÇ)Vb‹33{ôºÂ.ÙNTgýMµQâÑžy£6ävøÄaˆî¸ô&b!.§ÿN_ Ì_Õþ ]ó«ÚˆËéãA‚ÿýô3¿]‹W{Þïr‡j߀ù­½©Þé°ÜtéíµGê\®Hí¯`/ÔÕ±Ú;‘Ø°üò™§µPI”+Ýq5pM{à&Üsy'~c&T6à “Z­ìm}mm}ÐÆ^U+ï>ý€Pc}ÏZ#_ÑGÚþ¼cC–·f78ž·ÃÙ}z6ú÷.ŒY΂¿Àï-‡¥xm‰ÌÌÕvé¾¾tñ‘¶·îe´x+—bÐ@)+üq1+î-VÀãÏ ô¼Ìd+Vσhx':)Oy)í,m׬>!î’œ3Úâõ}¡Už®ÖñŠc«s¾/¦òÚåÚ-p%Ÿg|ÓÔ¬©·%Bs’³›³:êš½×w]¾jGfcµ5šHFù§µŸ5iï5Wø6T¾Ã„;O¸ÃW”&€Pœ¤íA‡‹ˆthÙg ègœôDÒm{º]2Yv'¿Ì>ûôàù‹‹»Eçg+æc؃®,-—xö¹Âg Ë: Ÿ-<÷dðôÙvûâó¡ý)xQ¬_Ó’O¥è"H= ¿é±ç\N•®5Õézî1í˜V’&ˆ“iâ5Œ–ñ"ÛØ“ŠÕËLîYffÕé³—±é“Ú<¢Ïf Š>½ýicvgdqè–€bnüvÚÜPßôt»Òd–\7ÝäonRÚŸnªo0§¿ÝhV·LHÕTÓMõMãÓü„lÄC³™šÆ²5ûÇݤ˜n½5`RÆ¥©|›Œ®é4·e"ï‘ öQ¹t@¹i¸ÇUóËü4©Ä|,iÕ–Oë‘âj‚~CªpÅÇ—v hàŒ…5}5–ÆE 󃋞}~ùÑÇúê>qÁ!ĸŽ7ýÌìË1¨xkÜuÖ2'bi ·õƯyÔ—W3]3Ó+[ævß:Í[¾¼vf1ŸËU3ÒsçÏÖÙfFÕá·ùù%Y÷Šž\dÿžy]‡¹ªñÉâ.qR€I‡Ž·èv¾ZvË…(ûjn{ñJôr‘»=0aèz/è·:Ξ éç?•‰ó$†â ƒ‘9]õ„É¢Fk ¨NÛ°ð ±b¡cé@ úuN¤pöšU/< [tª¥?­Ìþ̳×Ýñ$@7Ž\ð‰Ã[àrÏ£×Ä{Û–ÈRc­s×x¦ûó$_ÓÑây‰,ÏyÃŽÝs[V¦gº“© +²&xúŠ\.^Ý"ÖìùŸºM8ÏãžÙsø‚ówÍÛ³?’ëYáÎ.áqª±¿Â«e|m[By$¨é„V³;UÙ¡ß:˜Ù^ÝfûÏŽ2ÆØ–ªN¹V±Ddôï2†‚ÇË°§2 ÷ø¸©N ¡!O§½8ù´Ÿ?ëôÏvUÃäT€»ú#@hœ¹êñIq]”—MõÅØå;ã—ÐÿVA"’t0Â/í ¸£Wõ‘ŠÜ›$v?Âî%©zhÉP-“ªÒê¤ÔP.WdÓn'›ôÖ™csž/QÄ¥¹ÎÌ¡sYråMæš­ŸÙóI!qQ p Â`Ñ¡–ïfC[œ§ƒj@þpP-öxš¢aAL/’d*€²äj _ !ô$©L²¦UÕõô›‡Ö;ëa+:ÑqÞ§š™“iNÕizLªÂ\è8úẔ¬m\Š~ô‰ê$b£*º›¬‰žŽ,d«5ÿD‘•­7FSFø~©©°u=X&6ms†µ¾ÔßXC1µ6¥¾d©] ]Wô¦ôBE»•}”!:^oò¤žW*ëÄVÇZ뜢/ÅSµ« WEHSWèty5kœMªÏ9IÏlTNn×¹c³< p'>LÍ¿&5ô¬ wô”ì>zã”Ñ R<á’Sq)Q&l)•gÆäd¤ŠäL<‘dQ2Ò@n=!h”„»•P3sôL‘é¦î4½¶‹x˜ü=»žLÂÃRHÞ¸h aZd†È°=5\'ydJcRB+ÎØ’TdEÖ ñf=Þ8½DGÚ,f¦($ë‘3 C¡íòdqK‘½ø–JÌ@–"ŒŸ’Íè¬;X‹PÃ-”ëBŸtg¢Ÿ Êêq” õd3i)‘j%”ÙËòÒQ’ÜaziÙÃÇo‹ÊNRZ¸X(x˜PAăíʦâYO–UŽ»mg ò•JcýV3Ñ‘ #nž¡Y±6öʤ؄d"4€Ž}Çù COdè$ðRD¶ò^Êp£Ô©ÇVº°%†ñá@»ðo¢& ?Ø$"Š Ù­ñ°ƒxy¾†'fHF+Q ˆÏ‹’A^ÂÕ7ñ6»"yY›‹7¤ð-ƒÅ/ð>^”e’(ð&U^IŒÖ†$I6ó„7‚Yæ#6Ñ"U´òF³QäÍ6ƒ»Œ¢ÁÀûµN®“D0)b•ˆEÁEÑÀËAE¨qˆ‚¼`å[Û%I´“°A´J2vH&‚Íj°KÏEðŠQ‚•ð°/ËØ:Â;,–¶Üi³xxàky ‚D|6Š•æâ«‹HvƒÑ#‰!³‹ë ŠÙ!ÚürT%¢I&¢OÄ„.ƒµÁ)ò„F" ®ïy Ž£DLfUzE–-*½|7 „6‡äÉ&‹D¬ákE{&*Äd @ÿÙdE«CpK²8ÜFYE£Y–Ä^&¼à!žwZ;o6òbó8Ž¾t7¯òN d£'Š`’d:UÜ6Ñl4I"ÁÅ$ò6£U°œ;¢—Õ:"Øíp’¢ö<8@1ƒl$ƒJ<€`á»AŠàÐkxÑ$"x‹ŠBp\ ˆ’‚]Œ"ɨò’U”ƒ]0¸%"Ð1=¶ZÑ`´XŒ"Xm¼ä¥k3 6±ÇR¡JN¬Àˆ#äE¸«›Á fŽ™l”1PçUp b­`äA ²‡ÛæÃ&Á*‹v£ÀK’Yâ­8’ËîìØøΙ§‚ ÌÓy¾ÑÄd”Ĉ$ù¸™Ñ<ÄÕ\+ˆnÇÚd·ÝC¤:—bˆJ²ERº€} ª,N/9%A4Ô¾Þ#Âì 5¼‘ # ®`·˜±*o3ð< Ív%ä°Oíi ¼Q2YÀ!Ö9yGðåE«Òˆ.‡I6Þ©A4ªÝˆ5™x;1+ƒ,KGU4€I ì®4 Š$ŽÞý$փȂ™¶Ö€ÓL!Ç pYID(®•p嚈‘ìØ^é°48jmA®30-÷ ·t-£›ÜTŠ±ŒåKš±Tn4€`ÎD 8;ǾAá’E·Wÿ …ŽZ‘ÏWS‰ã­ñ89’øyÍÛöÖíºRάë¦ÙíÚ«ßï½Êhs”îþˆÉc2Yç#›>·%æîBg"…¦°éÈÈ6~ýBWý-N]Ö²O×ÙH½„Ò!(ÿNñ ׉~£¨¿–¸QúQ.jBÿ#Yfdæùño4WfsQ3oNå¡ô·ˆô÷U"Çx”¹bvŽ*þ²oDuˆW94•Y›;Á©šJ?þ$rÍÂošê5µèc†æ8ÕoÂ_ê›cv)ÙÌQ9Å6ö’ª1¹Ë6 "îûþÀÄëHB¿À ¥oªÐkkúQô¡XöÜÆ>ÒYv0Ô·QäòEN êì“aÚµaª’ïÛ¨ßXmg!Ç e¸Ç¾dd'P™Ñ”¡Ê9rùãEº +%ôñ Y¬ÈkÀ9wa§Ë ºK{@{à.:@¥Ýç`€ê3›é}Kç`&ö­‚/Î,rñ˜<_ 1!5ÈEsѬn–‚Ö-ªº"Çì›;¸ÜLn·’[ϸâ”@±ëÜ„,"B0ù׫KܸòW¬™ &ßÃn1/)¥ Ë9ÿŠíWKýWÌžÛ' ã?w­ô-Ûóþe}Jés×£º<~uIš”m_±ÿüG–‹}sg_Ñ/]­ „ÂåKáìæo¬þÖ¢uŠOc‹LOk(}!»øÐÒåW‰»n­y[ša+‹,ë‹Ý%mßåBÜ\î‚’Õ$…#Û3°’²–rX¶,NÃ{3%m }ŸI”tñKJ\”Ïâe.ñIÿËþÆæ4©rg£­ÖgnàCþ—êšý÷ø‹sü/ùõ÷øý/×5MLÅ_wú=+¯¸råK+×®]½çŠU/¯šà‡\#–ä̾Z[c§¬šÐÝÜèÿÏ:ßA?ù3:üuý LT×0>QñõwW\yú®¼âªÕk×bÉã½%›“”Ï\Çîÿ.¸´Îä臰ô+M9rþõ‡Žp»¼c'i¯<0{ÁÐÖCM×ò½Ž{è¾W3~Û+0íÉ;zmíï üéËpÍY˜ž{ˆZwgP—Õ%êKÒ)-ôA"íˆ8Üâ?;ço=žß:¿þ™+›ºŠûrÚÛÚ»äÚ»®üÚ3®»î ¾î, q혧­„/6ÄàNmGLßv $Ë(sK¹ ÜVî n?wÛ˜­‘íq 9·––:ÃÙ“L•É4†Ù·cØÕ.ö©PmiÒ)ƒ1£›¨—Ø׎øfºË¢>jõ ¡%ãæJ€[f&éÑ¥µò:ó .„ã~^ ä-v‡µ¸ôbƒ€8ñ¦•ûî¾yõ:“¼ižƒ+ç-{öXŒóVÜ·b“,6µœ~àî}+7ɘÒp1ùªÕa·ä"ï?¾¡µcù†s—$ôWëòŽÖÄ’s7è/°…¬§ùx«ˆxÒ¯†Èî˜ÃÔ¼½UðñCù⿾BLD?$}Ú¥®hÄžC”ooŸ3ÚoO¯Zºêª;Ò«,ÆÅ‹–†Ué;f_˜8mUêŽÁö ôÁ^ƒœ³G¢®[š÷%gGé£8;¹¯9Êdx–)ê2´ùx;¢Eð‚$—Ó–ï2A° >­ƒÃ·ð‚~ \˜‹qIúE‰q÷.¥²¬%âvd’2„ŒRé!Rú4g*SñHÃå âýÐOAPýþy]yíÐRdÏïA—Æ,®‘ÿµî*ªý,}s3cÚ7¡ý‚|^û…ö袺<ôkÀ5þKÈë>Æ×N쯯fV™]e­(Ý‚FI ½¤å¥/ŒùÝÒ‹W?¸ë¦sGÿ¹ãµ‡¼Œœ©tÛ-Jñ‘ÓÎÛzp€7ô®È­ê->ã ×Çká~¥ÇnV´óz/]±¶›Ì?÷»<—7\öé‡~·£øˆb¶w+ä¬ÁC[/ýgïªÜŠ^2¿&^¬ÓÎøîï^»âR,lÓ8y8ª+=_ÿ¶“cßÓ¯w$Ë,¯‰º â$ßú! ŽÏç]Šö'¥Ý¦ßÀåq¸yn-_¥¡‹aÇØíφ¿ÆßÈ>J”·ÎP Vq•ìsºÅÂUÝ樣CU_'ý³èÔvñª¯©…¡ñ×Ìú}»Ç*iÒ|\KÛãíîM宲¦ýædNvÆdjA¿OKpYŠÑ”5Çœå[ µsS„Ÿlå™Ýêâ»Õ7kÇò“V»_fÙà.ÝàïpÅ°1ÿ‡‰!ð÷*«ÇtXmLÇóŸ\WüîÚrWãvÀVAV_r¢‡dÓa)Â>`…ç‘ê1¦«~g’èa—Á”™›LŸl<”N¦(¶)ɉlÒqÊA¸æ¢å[ûfΘYßrÏ0#ªÚçØ·ÂàYÉ.¢’ÚúúÚêk[#§×œ5kñ¹óV̇ëÄÿÒÇÁiÕJûÊ6 †æ…7oß®Ž©­UË6ô­^ïÏ:•¹MN éÃk/3/!¹‡¢ÎäªTË4omݬÙÉ™+v¬lÍÖvißÑÇÌêTùËÏ9§é‘F³#6pv¡vM%b¸òUúBiú}˜ Ó•I2º‘Vª½aª|¶Êåªú‚ Ã~˜Å›ÓY]êÇ[²¹F%©$¦0ü“üƒïú½íûo¡cWß%ŠÉ*šWY;Òk÷\:on_ß/æo™{>%7yÛc‹–-^vÕ¥Ëo›i3Pºñ<[À&F¦·ôÌ^œëœÞ¶d6@Ðòz²cŸ›¡é=ªgläôO^à†“ˆO´/Ø3𖺮Ծðê; ]¹.Õ`•¦Gº×ž±eMgK»#êpË6¤¹Õp˹V²êÅ+ÖŸžX,ÙxƒUrÛ|ñ%ýÛ.:øÄ®Ý]Ý»£V\í´Ž}>] ²™Gßš3k­—[ÒÚŸ¯^:;Ôæw†¢þÎY‹?}Ú¦{VÏžëŽáW+¼…Ä-rL’Í'7šTí¦ï^4Ð:gÖÌ`¨µ­`÷²`ðÛµÑc7”çÆÉqJEfc¢ÿ;¹‡tË Õ}wLðÃÿ°b}'ë<–íè1)â*÷ø›:¬vSr—ɈT´¬b[î¨8µ1'o,ô” ª ƒ¥Õ_¥ûp݉O•ìB¨L¿°…ZÚ@¢e+ %û¢1/Ý)z¦x Cl›ö*iv;æÌ8_p:E‰¾ýxÓ¦@põ÷¾×Õ…?þw¥âƒ%ÿ Ëû‹ Í‹Y34¯ó…»Yd`“6Êòu}¯¸±B%ã=ä*ø¿«á«nÙ©mfJâUÔX.«è"쉘Nø!"ÓÃSÃLÌL…nòž‰¿k?üƒãw¢.Õ2'xJ”RJ6Ç'Ì!«j@£jyAí­Žû¤dtùy‚È"淿ļBa”³y­F€ KÐo´zmÔ¶¨!ãi« c!¾‚®È?†Ã,©ØC %í©J3ÄS}Yý¢ôõK¥¤ßÎK—tE½¼ä¥vèíŽDoâ~zɶ٪qºkk÷•ÏnÙýû;.øÆuë[–  ÄL$Gò§G>qäÀ¶î%VCÌ›éèY]{ŽCxI+[ñ\Îø´Á3†¿’˜yàÝC—þàÚYC×쟻åÁ 9(·K^W÷ºOüæ3{?÷ΚîÈ®3þosïGq÷ïÌ–ë{w»×Oº^TO–Nw§®Sqor·±±…ml¹€;¶16‡m06Í0¦Ñ«LIœä’@BB¨§zæt™Q³œ±áÕnzàÀÚ6\9K¬¾}žm¹Íø ¾Ä% Iðâ…¾ÇÃM ü_sïØ9¹¹×åÝ«n÷°j¾Æh;}ëîËühA›oÛw}צ9“ê¥å+o•¥Gª8¶ÄŠÖ5Qj5–m—‡êX]*À)ˆ­•\”•ÙX9RO2 aBžûáh{Få•e„ÅÓ‹„px¿ZÚ¿ì§íœ #Wo¬F»Z%ýáÛW?ì ™?Zp^tIrœuõ¹Ýk;<ôm—jÂ5=Ó{j"Ý]‘X=gPiؤ©‡Þšv÷\úÓú¦RÍ!ï¦Åµ]>2>­Ïè³¼a0E1|÷"¶ÝÞŽ¯ÜÙ8g` ®ÿÐì=W¸2žíMžÛ½iòø†VW Ù:aë‘ë#œšåÕÉéËö<öÐö~ì!DrÎñQÈóEU‹æà hŽhŒ(±‚ß6&êî€tcÖe»Çi¯ÂÃëÈuϸ^Òj˜Þ@öÉκh'âHúÃMÃMD¯W©íÆ€Xk¬çŒÞøÀƹñ‰[ö$[×-Mìð¶¯ë>w•u\rIô¼ûÀ‰&ΈtwG¼±d2æ½ú˜ô?­;w-m zRwß8-ÉpjXáºé­]µ”YŸk¥‰æ°7`GÍ£õ14-më]×î²Ç–Òw´Ø3ûPÝÀÀœÆ°sfíÝ §l™ÐÚp4DÚ'®h¼xŸ©nü=íS’çÖ[áœn­ÕàT²Ïßxõ;nS.Üjyý*ÆТ«!«dB窰ÆqÐR‰Á¾D­Ð€Ö[FytÃa@foã¨Ùs¼¦6ß8½J‡u®UÓ÷Ý3½JÞÀªµGO¥ð˜Ä¤Ž~rü‹hcô8ÕÒû‚&ièý«_2cÆ%‡åT)|ƒD~édÛ(”Å?`ÐÚÒå¢nÆ*C‰R#Š&EBìDŸCöEs¸ähIMÑIù^™ÿ\&À )Ã!qÒ€ø‘ˆ²ã¿|o’JAŒ!¢Ë³ gá°Ö£ð &Yœ˜ã˜NÁ$STfìÐ `’”Y~çÉ>”}îÈXrŠŠz‰ŸhsdŽ–;a&%²dR°_¦ÏËLêÔ Nô0ý§R% XvM32>ž³´U…’vÙÆ¡’fû}QKŒÑ†ä9èqg}w#2ÊÞKSÙ2žåÝÑ¥Ï-Ä&;0BraÕn±2Vl…Ä/ Çðf”‚gª! ^ w–ÒJ6"Ô4ƒµš'^ zÑÄæ‡Á¤æêå“¥+—¨»ªÛãV$ºÄÛ«»Ô‹¥‡}ΙΦ»–Ñ-ÃïOG}èŸ+ªêêëëªvý1 æÏ<•N%uåA”×)’Ûªnèœ1°”¼ó'ÐX¿žÄVg7,²Û2ö­$Öâ‹…ñÎCðšý$dœ+= –Õsáì•«ï_É\'=3k~ç<³Fz-‰Àdhªš¸ºó‘×è놽ôŸ@ÃäåË'O9ï¼áw2/BaÍöñQW4ópølܸÞqMî?äh$òí„CJ Š5’xh•GVE‰ ƒ2Žºøé½Û•~u(ªõÅä7·üðЬY‡~8°ü© ‹¬{×ñ†ÛAÙ+t™ô¢ôÞ+_¿_mWRAõ²”ü5t×ÄîCEVËÎßpñ+¨Œ§ÍÜßØßb\,ï`]ìêâpð0›=×ÁÐjÖšíBúlV¯Æ3$|… c|Þ^íß‚ëñM¡êÓÔ¾‚‡fÆÀ(é2Ú©q]E™4P¦RY4.ÚRŒj#g‚<–Œ•#é@Uc Þº`,¸>ØjX гxhâP"ƒ:„nÐXT*¢EÔ¡¬4N”©en†è1èY£“¢R‘tÏiªÕ%Låñ@dßjÌh‹­>S qÚyAWŒGŽˆ'¾0˜_9P’"ç- Ù&fl”Á” c ¼ùò|ÎÙQœß¶Ô`ê»õÉP—“+|fÓ]uèÿú ¿x FÜëÁ´Ï®2ÒÌRFß ö8jy§CÚËNo›~¨¢ozÛf^NñÙl“Ó¥¥S,/pOãL®ýLz*7.ȸ`<ÿQHˆEr!†ÍWÄeÄü@Üb €aÊ`$b²ž& Hw¼~ÝÞN[äØ®êæñí¿+^Ì*Âcõ¶Q@bŸÛÁàv&uÕG7¾4¥¡ñ¬Îõ!NyÕG@øèp1³q l±Ç@ø‘G ú4&¢±meq-òuh á·ð ˆ à›±hL/’^‘þyÇÚþóü¾²šØŒ©·õwd¾ƒ1Nž©mùV ×2©ï­š}¬©i®It«ùïýú{üè,° §¾:;bñœ¦èKÐæ•mÔ²q&!²²á&€F :ˆ>yz› É¼§+gÔF#ó‚´–Q :ý%c3€I¢ƒ}\­dDúW&Û©]vÈ–èŠóFo£›yÁnTª¥úå°˜§dÞH]1ZzÍÑRÂè1Ï£¶$ÑG5G³H‡ ª©B]ì—(¢­óhZ#”I€cE?Äè‚MÅaét.õGÓÒ¹{ñÙô´ÆtSA6I£•þLjQV.ʹÿcc¼AÖÀâ%%—3“aO;PrH&3ç NáY›Ë€9äSìèԱ׎…C3VÎðvÐ^Q§ÑÖ/léÝQ­03£ aÌŠêíWn'‡‚‘îèmYX¯ÕèDPKó~t5Ð Ý窪¦ »E?Ÿ99pìØafÌh€½šNTG"SÚÔÎhäê¶)Åû‘ˆZÔ±ð`¼²ï†?‚ðå.ÇB)“·9))’ hmæ•íLÞQŠ$o>&¼}$ ±lÐH²Å6 )…™$3DÓ Ó¨¨–Þ‚TÁÕTÁ =³Ï)læƒÀ“dzÍ\€ÒÏËw>(›0°ÙI§GóA^®$¼5ª‚ZBì¶$L]¶«â`L4¥ãø2±\Z£q¢ H˜°÷_g¯šI ys¹?ìk#K‡D‡¸¾—«aÅÔÁñ:°a|¯ºRÒ½§K¡mojumkSg·×ê:#¦¾¥}¦H§®Ön¯cÚZkW/ºþ™=sý"šh¥# (7Ï´ÆI—̬­yɤógjj4·\ý-h3óüÛ6ÕOÛÒP:ÁÆr«-ÒPÓØXÓ±YËñ¹xYÖiõ›n[ñȦ®®Mñ_ÆÇux¢Â/ØÍdÎKâJb(ÂÎ ßeˆ5Ý׃¢N«•~¢R$¡µìÇÄ óëA‚DÜ/#]‚~T ôOÒavÈ$F±¡7hIÔîyØÊn!áQŠ‘Xãê‚u,gçÃd†ì7ØÜYJà‡HÆC˜8³g.SÃœ%þê‹°%þv@·N\¶öhåÞ`?/€~b$lƒ¨ZË´oûüÞ·.Ý› æ±ÃG×Nëp¿>ºŒaâÔ-ã]ä}”£Y„‰3–?µÂ]ê¢Â~Cy\”^«å‰´1è¥ÏPÈ<ñ j!Õ_°v±y?:¾Rz ƒàHOOuüõæÑÂd8q 7bÿT“wz‘ÍàLHviÑ[z--6nœØlß&ì·¯=êiêkòL˜F¶ã[`ÔÊÞ– FJg]\~OÌû»w:´³wÏÑ-‹õ½/™V¶÷mÜØ×¾ÒôR‡{`ÀÝ‘<ºvQyþ¸«ÊaüÂQïvŸºËÝX%êo9º‡þmÖÙ%Ã.·Åô‚¤—@Ë£‰ñ0©J–•˜ÄÈÞ¥'.Ç)}™üöpH²Y¾B$‰†|HÇÄfâúÞ·CNmlóã¯û$Pžt{ñ¾¿Í¨æ¡·ïŧš'¢Ö¡e‡ŒdÇr³´íÎwß½s¿é·‡ D‡+€¤8Aºh6è à‚˜ËìðoMûÉÉ«ÌË;PÓdyIe›3^Íe¿1¶áŽÖNѼ›Xç=šó“ Ò$38L¥d÷0Hí_’D'™ Û¿„Fû§¼%{… §—ìg©ý²,™—«-‰–ûÖ1rtò¬¡qg ‡“åÁdVž÷‘·K*¼rGG´º„–KmìK&ûþõ™‚:ºöµö¨"ùîÉýK0ê&V¼ÜIÜ(¥2iôhF…ú‘·ÂìaŒöZª[–ù[¹‘nb‘ñ[Fî³ù”þb^؉̈́ yb1DŽê¡Èy44œÜ]Ùt&…>…á/pǧ5èã€2lm?qN,Ýÿáò€hĦ=ûO†ä]6Ç¥WAÕe±yGrc¥†ÝüÌîÅ,®a0†&RÊ»L‰&·?Œæ\2¿cÌj­ô m9žÕOÉÄ)ì£ÐTVúó¦°Ïó{™#4…§y)U®ÍZµ40œ*òOx‘Lì¦"ÌüÑv³Ç©S¯R¢>E‘¸A-hÍ™+9fKŽƒcpdÓõàÿÏî?[úÒúâ7nÌy–ŽÂjÂh¦y±«€NöOíÓg8úÿbzx†ó#Ë R§R¸n8‹*fžÊ×ô£+^t.ó1Nþãÿ`BéßX²¯oÀ€¤C²@VäúŒ5ŠßðÍâ(ä â³(QÎ\˜ck-öµL˶(L»‘³IáAÂô÷Kü0KÊõmøcÇ*—”–Ë––Ÿ%—*YZ2™@6)—nä °¥¼–šNÿƒ‰")®¯Põ `fÌòñ2c„[Ô j‡ZŠ¨Õà ´Ó VKÛÁAphÌÓÇÉ9ƒ~ä$Û¥íê±OË\n¨\ÿ‘+UðãQå(×Q¹Æ8 çà‡ËùDO ™‚7P¹Æ: §Ëe%GÁÁl‰#ê±OãrM§®a¢Ìœí¥*r2¬'cœd¢g«õˆÓ**~>¸hÌÓ”\®ã¨\[ŠÛ«„^ë$*׫;Æix|ôËE)pÁÆ8Ç"Ô¿àòq©rìÎ…Þ„:R6õˆ~C+¦;Mmì“R}±ÉžÌfɵG›*†ú6Ò©3\€I|zcLcS?™úŽ®E¯œ|ŒóÔ˜åæaÑ2Ézdž.¦Fúæ45ª`û@ —û ˜t&YZb@J|†óTmšRQFÊž·¤wMsVišŽ<Ã6Prœ‹•ŸÍkm›;·­²²üoK÷/]ºŸ¹°{Iw÷’ \}dõê#0!ó& ’ÇHÞ1wÒ_d ½ß´4ó ¾©›^„oZÝOâ*†? ¬“à2Ò{Gú|hdÑ\¯äJW²~›EoG.0Ñ." vŠÝÙê‘þSfcÔ#¢ÑðRZ¯Uh z#Ëú;–oºå¶å˜W¢D¼fD8üåÝ10x¿ôg…Ï¡2šô*?×›8pÛ¼¸[‹ã‘I2üƒÑ^¥ ®ÈcÎRä;«§â‘Ÿ¾h$L~EûV5Ëeý1%-š<ã÷E˜pβ%ë½±Zœ˜¿`ÊÞ>·ÝŽà-ùÝç]TyëÄG'«¾èPrù‘+f?8ûŠ#Ë“Cí¡7üäè’©]¹ÖÛq¥3ºþÞu7Ü}ãþ5÷®‹:¯}s{{çŽü¹dǃfÆüàŽ…û¦Öò|íÔ}@ùê%Ó7¶ùUœXÙ±²k×kß9{áÖU3çú=³g¬Úº`ÖàÈïÈŠßBvœÃ_É7Ž¶2Zzg’ó1&¦EÊ4ɵd~PÊÒ$senc1WfGFµ0÷ñ 7VZ0´Pe lNÅå"o«…û"v*]±Ø!ý^ˆ1ÉŠ%vN]…u£2#.4 j³ÍéwÕGzN¥óåF+¹tü‹žë¯vK7Ù þ7Xgyj°P•G@klü=-ÒM±ñ…Ê,¬ÏcL1—›¬P—¡<}1¡x–9ŽN‘ue²°Ä”wS¹÷€Û:µïÜL³ÆÂô¹û`ÿ¨ÄxWÚ,¿•Lñ Áé÷,{ŽÉ©²T‚¡Kb}èAü|¹´§¸pƒDÍM”Ý )hîÁÃýE%/âor™Yþø2*@5ö&bNXÏÀJÁ)CzxhpA4k Ťò%ý*¨´9ìuJûØ•ãl’Zö+’yÊÀÔU|, üÈ*´ÌǼ_2¢—wÞxãN”ʦoÅŠ>‡ÍP^-":ËHø¶U…lÐTW2Ž]7 w”}°÷ zþº)m ã²µª³;lJ\W)ñïÕ-j¯3䪥DÙ ªBÕÿ¶nãQ=r>™¸Cû*¥BŽ Y«Ã”C ý{5‘ ¤àÄ¿Uø¬ŒŒ6rdJÏ·Ó.1%¾nå÷…ýœ âm “Ÿø/È‘1¹]˜ÌV&»‘Þ|3}äí#é7¥7AÍ›têMuÞ]Mª“õv{SZ(½™Jð À¬óú¼N Ïk~ô%·R©9Ô2jµÚG´Ö÷PO’± Õ }º¨‰¢ýpÑ>JƒÞÚGµž9ÍYÏŸiŸ-Þ7æ÷cøXƒÙ ¤ ýô/e2 Ù#†2 #a›î7dò×ÉŒ}˜ÛJTö¸°EÙnÄ7ü ‰(Scÿ"˜ªYl$)>+úÍ|6ê”4ÆAväMöŸ4HÒpœ2¦³&¢ñ¯<'³zN UEÍÇ’nÎOJa$qC”˜S³VÓ\%vºeò(# ✋,Deꡃ³;W>¸ôøû_œLœ·"‘(«iÞqê9Ëý¨o±i¿Zñû›N(KNØزJúb™^0\{úÅæcòüf$e*F©&-&šÑ1ù\À0âc®KS©†ã¥««¶C§cÀ6y^3fŽ­Åc¼_n62V«‘w2cW®'ðÊŒ±—€9c„+„ñM °¡‰§³`v],IdFO@Ë‚t$/]Ê+ÃÒQät¾êX§4q´Vß”|뮑iÀm'?Ÿ€Qx²ëì?^ÚŒ£"¦·Ü¼{w“Ö”pø¾‰3u§JÒI_—ýä¸,÷ÃÓǹ=쥦*PjQÛÓF+K‡U@$X¿AÂ'…Ù¤â˜L ­fDÖ˜»nïvÝÙ :Ú´à é¦ù¬Åj´JR'ÚXØùÒ¡üó]Sy™ù]ðÏZö|ݨnÝÃíîÁŠn“¾#i½AíGiƒ^ÌCåI(0 U¥Ô$³±ì à!+~ù|V^þ7ÖÀ¡Þ©95hyßX“ÝÄW&º¦U…äÐFnaž%›Iä·¿q‘]z÷ÒPuEÇx‡}Q#Vz Stca_Ò;ÜF{°ªmfödN÷õ <å BTu.µ†Ú†$‘ì[Ϊm-&«ì LœBE#›Øc64*àHˆ&²Š<ª’(BE¼Ð­à Y€¢¬Y¬ÝÍ?q† ˆŸšÑ£æÃ¥²ÐLÒ'Ÿ™Q‘æ_Dn¾k^#SrQEYÞ7âaò˜Ð>”a¢nË­X‹<ðˆÆŸ%ŽÿYq2Ÿ‚„àÅμi’hlä´¹Ãk• t¤7ïÑÚpn{Wµ’NÐêîÕ±ÊA0®ïî½³-wƒ NŠ/mmsZ¬síFwP¬sƒßÙRW•,·ŸcPîV»t@Ý1psNwñ7íÂedð|\:¡r—çÎ:à ûbFŒŸ‚…[Üž f'ôS˜ŒÇŒµ¯‡E&YB‹‚E3+'×ö/ô‹Æwé@¤}®¿Ò¿~ÖÜ‹\AW$Ø·ì¨*¨Ò¡;H]ÖŒ óÍë[RÍmO~PXØü5µ–æú¾êÙ‹ÁÓ³ð¥KÂÇÂ,5Ô±æ`oíäÊ™‹Ï®î«o¶ÔÖøm†*¹5[’昫äiYYŒInÀ(ùþ(…9O`OðCþ‰ŠŠòd÷ñ,à!³€Ç¤¤ßýŽ@Tfu €úô;¬2 œhç4uRúê$ö?¦“©w¤çlûeGÓý60ñyˆ±= ‚Ò*‰Úòä~ˆ±w1’e¶ß<›£ óÅQ9Š@½¨£*VãaXLA äýù8D…Y#Ý|r"ÞÞúçHyGÕg÷…ég«ÕÌd+]œ¹áäþU÷Á™ç¯Þ W ]ÒÍ©ý'Åþh¶"ŽUÕõJjt§g·(\Ëò~â2•Oö Aߥh4ñ,!ÍãÔ3I)¹}éßÒ=+nÝ3hË´†Øž­WôÈB0 S§®ëœò,ýD†šÿоKfOv(8Ná˜<û’}Í—ÂB ;ÄÇC«×è –x‹Œ>.‰˜Ê wÅX4™|>¿‚ú‘¦ û˜üäkÂ^™ZÚ å :ƒ$¶4ð€"ÓíÏ8ELz,Ž¤"L„òï4Òn4‘s‡¬7­à_ÌB~#8ÔKæóÊ•;Ã8ÙÏÇååĽèb@ AÙ³ž¾_«Ô2´”Ô𧩠×Ë“ÝîžÖÛMŒ±Â ³µ¬ØÔµ¦É¾tÿRDx HÓ º‹•ßy¿”6¨  šUÖ'¶ “©‰ö¬}ȵ¡®uŠWéWhljÏÔ®ñBU ®•×­`?P¨pݧ=œlÇ­-bó5a‰•æ¬Œî„–ù=\þD<€uƒD8¶›¿7k³ òRJ¡Òj’:vžôßÒG4Ç«’FíÚvõ÷sË›YJ©I7=Ù×/]nP1*üÒLÀ>¨’¢ ¤xhÚ<ë׊y®§G /'h¯—“ªñ¾—öŒSÅ=zRzíƒÚD-–^–^ÿµôÚËÒkÀÀl¹cá|zÓðuô,3ZðjÕp’N'YꢭEv[<àPÁD¼­ªr<‰Æ)6•Ñ׬EéeÅUx×"Šàçb#¼¢D“y ¾ ¢(]£ˆïh‘Ãßœ{_~>zt8KV`Ue‰ŠŸ_F“³CÙ‚¨ô2)=¡ôù¸T¸hr1_Féðg{>HÄsÑ>2=‚ªäùÌ5Eµ •¥ ä(-,øÍhŒÿ1Ú€4¿*×¥ï vT½ä—PªNþ˜4Bé ƒÛÇhƒ$‰1âU,H ^…áŠü"Eoxi6Ȭ5 _]WZ^x^÷¸¬eÀê†Ì%z©‰M¥2?Êü”~äñ̇ïÅbWK®+ çxëëåwßMú¯öt’ûŸ,¾ WE¯‚EùŠÞ„ˆì»Ò?‡ßÎL˜*ËÁýàýÞS“Z˜çB§&¡áí%é  +o¸ë.0Tþ8ÛV…Ìç2¯è[•Ç¡:À¡V Â(vkÑR¹hÑiŽæ¼Œ ‘2¦Óò¨´Ê¤dtês·K›¤FiÓösU<£4¡³ß¢TêWö|q“,\·L8úæÑ -òÁM_ô¬Ô+•ÐÏ Ìûdl”-J¨:÷º¸î\”/šDÃÊÅ»Mð‘Öïñm›€½G'lóÝCNdvšv/^iM‚üý¹Á?ʾ…ý_Q§É.tb2û1ã)¼y²’A–ú­`R$8ÑIÂíö.9~º”¦FØ°äu=‘V (È!g°x(•ý;“D†7–lì8O"J¢òô,†ø¡ g|èxßçæo­Éì9«5‡èPÈž¢ vÁ³øšò=O5UvJcÙ±÷iOnoÌŸ¼}0ßF•Ãx–ãârŒõ e¿k·gIA9©¶Zç}…0™)± þ @dŒ€fø ç-Œ _Í ekð°NzöÞdÔÝú¶º”Î.eW}÷¯Ò»·ò*µ û5Xòº‚\Pk€»Ø“TF4ð}&é€ ]€æí[uF“îVàþëwW±@­&g¯K÷þZ'¨UôË¥þ¥»³„… 儸‰¬%F1h|»¤¹½Á`ÔbUÈÜ,L@RÄ`&•*ô.ã§cÜK쯈,‡Þ¥Š-Ìx–ÕÀqÔ¶ŠpN&Ú/«Å„ m™ç¥çÁ¸ Ș—&sÛk…8}Õð¶àºàž¦ƒM»ƒAú*t°ì 2mÒóŒÃ‹ïjÄ©ñ]ø~xÝðÖ ºip#J·.H ¢›ÐÁîàºí"¯õKC¶Çðý•ŒéÔ˜Þ¾²Ja¤w/=‚;¶n ÂY|°Rr˜hyhå¯à—*æ–…Cy½Ô@¨gå”ôÞbšY4N¢Ñ_³—ReØ/½€ì±÷¼¿@³L-T¤q ›Y©Ôª ™®Œ:Ð+wÒ÷±–T0éÓ˜ Ý e±H)™ËŒžAáÞ&æô5Y×KL+iô 1îÁîr銀SJ£L¥´Ãˆ)¥yÍ N¥b)‘¾kŠGBù‚”;„)Mš7‰#e@‘,ÂY`Ôgx®ÊÎîµÿ‘°L´ªø-~ Wee”FN|«H_Qü> ã>‡FvsöZ؉ŸÀKöSÑF%ºÒö)¼ñXcS?xƒ7Jïu¼øÒ)葆2CtjIYÙ±²¾²%ppóí£Çû›À÷uø^‡oÉ$¡ oS‚ýKÐÇÊÊ–ôŸé»·c䬗‡‚sçؤ@V Œéåî!Ô™冀–ÂS« —tû~€áÊrœŽ´J'²FXU\’B9‚8V\•tÊgeE"†˜(Z>*-ý1èG/eЮØþÓ}ç5yÕ¨õ ÎB׬^øÓ#Ü­´«/Õ¨bËK§ýFà÷éDéò2à5 OSôhý°\æ²Ï‹˜Ø ´_YÇÉðÍXßJ‡#JlœËëš0z¶Y¦Q ­D¿ñ‹;þ€NìÞÕ×kgúÕ ƒ^7í gírûãáÚuÝ•»ñù;DÝ^h^×Ó&pFí,¥ž×ÑÖDÇ‚ªe;ŒUÁ©‘ºXSb|ЖÝòŽãqÜ«jj£6ô¬j5p…C9fYƒ¯Òj6~gMesë”ÊC¯¹žÂâOp>o•LGô€VÓ‚¿Ü:¿×QvúEÁd­ ut-̾³½èuädp(,YÖè0Î;['òL('‡G½¹U¢ÅŠ­3{þAë›?¼Ziþ™A%½‚±N6î¿Ë"Í#:µ;šÿãz\4š|­3>‚VƒU«xáðS¦ïI·A 6üZ¥»T'Ο-ðèÂ&Qw9N‹vÛçÔ‰„³žòú³$Y˜–|w“EŽŒ¾–¯"ÙGãj4×ÍÌ…gâàâGQ§ 1À#oÿSú±R©~*ª#Õ•Š+Í?6ªUJé¿!}îÀ'oQUÀ_­ç ü€N„݃A„ØÁ½¢7f~(êxaž¨[Í ÒÓ:Í6îÓÿMôjÓ9ŒÀ+ó˜é‚§C•ð–6u>¢·;<‚7 urjÿÉ!h´Çf7/®«bÊ”ŒE9‘UkÖínñF]a‹UNSÄ …ŒnCDŽ%m)5bxì÷`E8ZõÝÍšR]+P·3}OgciÔêœöŠÚŽ©K6w <ñ ÄèÕÄ ‡‡ËÏsçjï•’Ò"IÊŽFò QýE¿h1YãbÂkõFÃ~|-°äòú“&½‘öÓ2c9N c-{ç^qÄÖ¢ óÊ ¶ýÃYwNlõKo{À]Wù'€;gÜ= Ùà•~CpãߺWa»Ó¦¸ÿõÐVc„ƒ¯áj<î½o.XĪՆƒö°ú<…mM±\p.ë8hP«ÙÅp’ë}O¢–›ªÑÒœÁÌr¦R© Z¦Ko¡têx*åA ”9f³ÁôË«á‘ãe­5X¨×imÒ10`“µ:½ô`6^;7¦˜P;F©I¤Y0áÏ(Ìþ˜/lö}èM Ë ùØáÑÚˆEÍñ(úqÑtc„ñ€×† itpÌuÂMÛ¶êÑ[/}k_Õ­Â$ñE÷†¥Së¦mx3é½uvÅ­3/hÝU3±maÃL¥²%Ô[ß©w‰í¶†ÉÕ] ¶Õ×]Ó têéieG¯š¸~B…9} S§Á3Qpwï½  ¿V¸[ÏËÜh ص”4«58|ð•7굪9¤—ÑÔ£ä­îH‘Â(Ç®ŽˆdGЋ‘µ(›ÙÀ\,å=»45ÐÔðPC£j¥@Fß ½Ø ËylzìYrVÌù3=ûÌp `ìR æ—p€/ì^x†¢¢²úNSÜn£æ¨nj6j‡(¦šò+ÐdìªÜ’K!ÈJŒÅÄiñN€)1°· fÅH`1ã„13^„ýŠ(ÞŠQ‘y໓´˜Z‘É|¦–~‚=*¤4ÖÞ¥ÉÝcz3Ï‚MZ&áÓ ì€ é:N¯áUæ¯Þ†¦Öý£nªôî„÷ï~Ÿø}1Ÿö”+œeMl?®ë׃Âå=•Šô–¿,Ê|¢4Âíôek×>¼v-<šY+Û‹Šë݈ë,Ô›=c½AIÍèol‡oQï;FÔNC«Ñ~FwÎÔhl†Ò£ðk¦¯¹¼>ê4›Ñúró‰žÞÃiPîàËb¥Ð_ïh0 ñE£L&ì‘®¯¨-3„€OúÜõn`Ûp¤Ñ\UßUQe~ZUÎ[„Š³õ²Vg(TÖ2­+êZ³†nº=½½1CwNM+«×³­5 Ž?1·º ï·UÏ¥[AÅÏ~f]b]ø厽-å¡Py Ù8ÛÀfé/n´ƒô‡ à¬Ê‘z_ôu ñò/h¼,ôÅÔ j7uºzœ¬21²#z×,z‚QŒAlŒzÇx-¹—C½#F^^0æ'¦DG½ØfLò¡Ã¨¬à<¤‹`˜uÔ+<¤‡€(rÇÞQ1×÷ä~†û^pŒJ¿¶Z,Ö0˜}Î9Ã-ë¤׬žE‹\N‹”Úȸ88®2ƪ-ª7ªÀìÅhX‹<é ÷ô†ËÊÃã'¡Ì Ο_uð [žÍ8žmY¤s ýÖgàûdرjçJ¾.X¶v"xº,8¾'TVê,3Ç":åb@ NüGÔZz#‘Þ£K—f~>‘®¨2Ó°^ÚYo ¶/}a²£)þ»Ìšq‰„sŽ.ªŒ_°zf0 Î<Ž61§SEÿôñãߘYðáÖÖ>ÎlæúZ7~‚÷&“í3¼´Iú;ÐO9´z®ô¯ ÏBw‡úïÙ̖t‰Ž - I×{¡¥ì–ý.1ó?)#,N^'Ćpn!Œ5Éæœ"Ä> ç©¿t†>5›ÔîÒjTÖO+ô¯4šÌg O£V[>­²IÇìá¿[èóiJć¹Ð+ÔëkÁJƒyø¹ÅdÔ× =ôµµÞ <6‰„_#Ãb¶:˜iΊõ @Î Gñ0@b¸u”ÁfÙý¬ T(w?¯R) ϹE:¡0þÀ%Jç£e´Éó¬ Pª¤ap‹ò#Û4xǧÑ ¤ûy^ giý™0”¼~´poø†+GãQ2<Áó FšDAÀ$“±Ê}s£€BoÆ ¶.‰rû¼^ƒÞÄC º ^oX;ñÃ{þ8q×Ãì1½7{¼xŠ$M‚ʤB‚R ’GÓëïëš¼Ri·+WNîºoýÈCJÆ ãÒì!bSŬØnôi3f`+bh=þ%Ì*-ZL"=,YØÉ‚ÖÊÖÀ|À‚Ì,0_¤Çؘ-Y¥‡ÀðWé1I Û¥W¥?ƒNé½õÒþ/¸¾”a=é=æ·ÒŸ¥×/}.ý]ú (§÷H?‘>ãoÅî!¾zú|iüØÛ—£Âì cRO¯QA‘E@¡‚ 4=˜i§Ÿ§nôƒôàðoaZ—éœ  gæý ž7=s'8®½DÚ»wÞ´óÀÍàf°8ÓãGåÊ…kvío0]ãw0µö€ôÞ‰Ô¥'N\š¯W”?V^A~Û:ëÔ¡Y[·Îb.šµõBxegïž·.útogf‡ÃïO~õøã_=o¸¯¬²²ì>tÓÇ…ä[‹¾=Á(›<ÍE‹J*¹ƒ[/yâ’Kž€OMŽoJîÙÃâsÙÅß%D³æk½lT¢ ï·)ê—Ò…0¾TŠI±¥P N•¢>‘^‚Of¦‚ú±âƒûØËØ{œŽ£{0[°paçGKGè“AŸˆ$±‹¤OìÄŒ¤0‘Ä"ŽªP¸ 1Â8‘#AtšÁW0G"Àb? ºN¹-./ &'6ð?_Þ9•fnX²øâ÷L“jê¥w¤«#IÁµ$ÑöÞÛ±%ó•z]M`þ«/¬ŽLœ4Ù=œð'˜2s†ŽylMµwXºõ«#z³ŽU@•ßìPÑ徦€k÷I° TÞÖfð¾ÎiãìÙFAÛj\·¹¦lçøÅ)¥ò¼ØéW)ëêjŸ£Ì¯R”—)•þaÁq~ÏdÓ¸:Ú¨4ùbþþç ªoä|Mô³H6Wc™qOȹQ[^élT5¼¸ëÑIŽZ—K¯‰Á‘i¦ÂÓ*¿+%E[ÐZ—°‡et—þ€ÊX½ñ·Òß÷/ UG¥%À%'èÖ< è6·›*FXÖn­ŽXLkk¼½ûBí’žú…&÷lÐbvp¬ÉÄ)ì&Ѧ@;«°ghEØά]ËiomšåŒ¬»ÖÂ_Ä, o§Sëӛƹz¯þU€m4ù4}¦²Å:SÈ 4 ¡d|ÔŒl ö ‹Ê3S–ŠÓ<‚]Ó#ÜpàŠ? éüF^nèÙ¶eÕ´éýkfÍhk1[^œL†ÃlJºäïÒEW‚V÷´ÏÇE§½!¯ƒÎß¹â‰é3ÆÀš ƲO‰61¿ÌëiŽM ÔQvÊ çGƒåj ¤OîÕ”—×ë½Ôh¬ªnï˜ÑÓÑ >,nÒKO4Ye® |øÏin®ª°Þ#­ŸQ]šL¼ŽaGµ }: 3ñ—¥,c/¡át·ZÇ«¥;tJ•)‹ˆI)¥Vƒ”Aâ }*ç÷AÁ ›&>¸²oIæ9‘Ý‚™|>fƒ,Źƒ:FO'kf(d(s)eÈòoZAÑ’g©?‡Óo•B.AI¡àÐÈg,çI ²|`4—Îæ)ÛŽG"ücæŸ4.BI©à>Ôßá•ÅU@ ”÷™ß„Ú3D¢³Ý Ç~ cYé¿g²Â’9^AŽW&*´š,ì¦ðÜËRõ‹çwµÏš=vÓ ›6>:iÍ€¯vùª‰Û—66Îôw’Þ-wuÆãÁzê”'fî®Ý»Ÿ÷x¼>tÀ~þÞ‘Ã.—Ï×HöD—nºäçÌÅíS§vÆ wÓúu•´f´Å¼y4šÓ52«uÐH§²[øpf>þãRÃÛ°û2Û–ÂZøß™ `,³}ø“Ýð&úÂá÷á²=cé²{ˆ?d’ü¦£5E5ÄɼÅd·¬<»É\†ç$ŽíxyIóabÇÃØ{›º±«àV/$û4XÀ;«Õc'=‹Ç:|ªª­u~[33Y;µm~Û¡¶êª60%’„­K ¯H­Ÿ¨Ðê“–½¹l’B§U€£øz[UuSnÅùÈÿ^m«’fW·µUƒÇªÚÄ̪HòÏøèÏòo2o7%^ضí…Ä>‚ÓگåºÌM¹»ª[[ÑüªAmñ/ ¢§|@L êÁDð)Á9ñcÚ©+R J-×;è6BsjÄÊ Æj tËd ųê <ø£Ù –ãè4g5ù#¨£«!ó4áQLA‚”¬ Ž•’©—Æs§ ó° Ù#$ÏhZÅ<Ö`ñ ³VœÂ‚“à÷ œ,ñ’›]ÐGšÊÑÍ$¾gFl¬q<5E;|Ëc¶XZjâ1ò nD¢G†>S'hÄKD?–'è‘œAC¸ . €)4gRðtXnœ?n"ˆÇHQn.ZaÂyâb-Ñ}…ðE¢õBµNȳf”@Ì(²i-ø!4ɵnÔlÆÙvv±ðfŠaEv £WÛ”´tð4­PpŒ‘HÏK0H¼Eb® ¨§ømÞ^MØ­•YÐéï³[Ƥ ë[9%g±ËÔÉF»Å°NªJ; |eÎrTF…šc4 #&›Ñ€E¥ «æ-j§¥.«œV¥ai•Ö4YUã°ÇÕìUÆÏë´è ä8BG—ÍŒ[ÌU¸Êu‚u¦Niö0cX&a+Óƒ*ív)«øH˜Ñq€6©#;.¯±j´=’3ÓVТ€ž™»h §‚´š¦54¸ªŒ«b9HóU‚Jó”ZKó yFÙÄêh½JÅÒ¨!Ã(y%0ð0a²@…Ít„”¡eeÆU!Áªö¹jæ‹ÓL5Ѳò{“b2PmcÕ>Ðð­æç]6sÌõ©tÔ² ðÑ´Ït™ß¶²ËZ]M &õÎq½µ |‚K¡ ZB¦ y-ûÂ]±µæñ,’V$é‘¢Q;qŸàT<´„ƒIT7SÑÚ>96Nöx½4x½ÃàdÎ"àPU€žÖè8i6PYV©†À ¦•øuCéVÁ¦·; åjŸ¢šw¡ÉÔy÷Ö ÈÔ^ ·¹-è˜í XÌ]>%í ¡ÐÝvQ¯`’¬«Â¬¢•{ô*šQ4wÐìÖ׸!­QrÑâUFÏk­€w°J«^ hUFÏ¡’Ðœ›$•2ŒÞ €Ö êUŒ ²,ÃÑ À·9´š·ŠVØ;Çõ–s6 «”6³»³¬Ll×ùZc= ÒG*h}k}ÄÖ«4(!«R4ô“BJ.bï±–q«Ç¼f‘Cz4t•Ñ¡ŠzÓO• š¡Õœ@C‚Âƨ€€qÒìGSB=Ðé8FÇr4j6À|ý¢ÖnµXŒ&ÀˆSœ… *· nŒ^R™Ç@›uk­Qc] 1Œ TZF-ø|“½&–Öé«8›Ö¢Ñ÷òFgWržæj»ÂÆ5Nñ©lK9fb_ï5]׸ñççìª6ƒrgս˶oZÓúÚ‚ú‰ú‚¨Ñ•¢¶œ òsvwMd½õ~;ª–]£™2Q뎺œ}¯/Eñ”ÉÖªê æc¯Ÿ`ˆöcÃ9æ@£CaÆ‹gh«LåŒF4LxØpÀ§ˆ³xnGŒ ã»ÈXÒ\Œ5>Âÿj9„†ø{®ôëŸýp»Ù#ýR: ö5ÜphW(È«w\r(íúí7~± rÃÃG:œùÜWÓfîÛ2þâ‰mú÷è#@eꙺ{¼]„*:0}Bo[¬Ú¥¾¸dmÀwræé ®®9 o¨ï8WÁ_òî¢E·-íåu€ýÏ·îëúüæOÛÜŸ¾?õ/ô\¯øð›Žññ6³äûà{@kO6O.‹UqVÔ½h´b`á‹cáKfÛ¯ƒZŠ×$º`†áh!×ͲHC¯êÆ‹³LJœ³Yt@™ ý0‘^BVßct=Æ"`l=æ¦pËÂéõ®²*A¸º·"Pã¨kÞøhojCOhÊü¶#çX<}]ÑYõU å ÑÿyhòºÁºwïÜ;0}òuÒ©n0ôe‹ÀïæÄkl›Ba08ŒÓm^Ÿ-Y›Xqwn˜Ü¾¸-È,¼©"õÔÖzÚj—ì NØvøÎwû ~Øë&OØ+H§ðA¾ "Û·Éø+9ô« Oe9Ø‹D‰“­ Í»ÄLUYü7@?ìK™7Ç2'b185v4TÒæ“UÍ­•;ªªÀQW+k Ãu0¶wÏgBF­´†çwêjøaØ¡¯‚Tþ^ô“¾”6¬ªÜYÑÚR…™)™J¸ŽŽ…í;ôUúLH ÓWñ;ôúaØ©¡ ¾ÌÁQÞ“gÁiÅv_"#ƒ¡¬E44r|ML,úM3Äž:L"yH,¥Ä^Jó…D¡¹¬ .kxÇf…[ÿ¶r›åqÒ¨¦¾¦d÷’nò‡ö7öÁTßFiˆ”†NJ2w_ÿðFR’פqxK–n!ìÛ¸¼\(GNÿåÅ>ñXEcÚƒHŒ²XÅŠ,5Ëë*æ·Ûm­[ûüÊH¹ÑÀ,,T>¿³Léw;„RQQæwÿ˵cŒ 5h=ñ&{õ£ÉX‡JHäÐ ÐЂh(Á±gá ‰{f‰«n0„Ý*±\™¿]6?‰ ÁÒa‰s¬Õ¦ßöÖ‡oݶXÞ€ ŒAz[§ç¥·ŸR{ÔOIoózô¶aUO=¥b ‹ ð”ʧz ÐEÈ^„šB6hÓ³ýÒ+µš[ú•N÷ÕRN­6€†~VoÔ~õ•Î€®‚ùªV+_•^AW º¯¾Òf×z?b/¥ÔC© ËðPÆA™p<$L¹„'4 ¢1†ÙÀμDòf>‰7=-ýê©_ž^õÈÇ{£I2´Tº|èvL{»å ÜRc¼óùúÆ‹.¬tóŠ¿¢ÚÄŸNß×&=ö›½?²j×Ï^úÇů€²ÛoÖ_ïæ`e¥{Æ«[nüúHTpó2Æ—ÎÚŒ«I þ„É\ªeo’,B´€«Š¿`tåkr…ÃÜ\÷Ë0|Ô0AÛ VNp ƒ`ixNrýlšê¦&‘è¸j´àÅ#!î<ƒM’¾¬ËÑAv‚,qE+0†ñ÷á&H=Y àÅÁý\È1Ôóš( qáç¬)Ù½|\*zþäV^ÿŒ©Ì&Š´ñW-2äÆq1Ô(§§Câñ!‡4!“úPÿžÓzdûëb£(Š/°†Jƒ´9ÃaÿªÙ ÄLÞ<ˆ+’o”³‘~©ËðôŸ>MÅnf"uñµãäµ›5ê†H€hqÇr!4#ÒH&°š‘‡ŸÃuŒÐhaEl¤‚gFüë¢ At K,ÜWÐ:ÆDPY°¶`½Z‹ ZƒhÝ¢Øm=n«œ¡5ºI,'\Ó€"ʪÐiÊ–4™\}Í]6Zmõ@Á0‚ËÄ£›ÎµÙÕþõ×´q4£¯‚Ö²¥©Qo(WW”é '¨Ô,䜽M'ͱïÏŽ™œH¦Grä²3¬I«5Ï_§¬Í?¾ZoçX‘f*»zl6uŵƒ€»Æ`a9ɘ ­17¬++o[X_Æe e`rE·NëSA‹¨q@ enoK㢦ÃWçVAÆQ½¸c`§ZOÓýƒ¬^%s?Ì}ÉN¥ÔdÔ«£æQk¨KÑ™_c¾b²‹Öö&jÖ`Ðú Œ‰x ˆÖºhdÄ1¯:Ä‹@v Æoôé’%t,xg­)å…dœ#§ÂxA+/Ëá=ؼ:ÃlzgmUªt|¹Âèâ]'jÿkúYuu¯¯Ý° ­ ¥ÓGþ$ýW päO BSÿDÊHïKÿóÖÞ«RESºjŽ×sÜUÿ©­…,¯Ö6/éÝ:×.*«­¨`¦…¶*†uØÚÀ¼Ñ°ª!îP–::]P6Në.Ûõù°o‚žwx}ã=ÎÛtN–ÕèÜ<«Yºª?à{nÙ¹Kœå'ÚúoœÀ[?>"o®í½nß@GÏögÖoLê¡+¦$¯çµ¨ÀÖöÎ-:^ƒzT˸lé®&ôtT†Î~zº­’ÕÍìÏlq:„çì§zÇÇÎÝTÇ9¦æü|û)æ¥B£eB#f‹ÑÔ oªóM®x?«ö.åÚ™‰¦þ`8†³Pöªô'•kŒèÁ¹-€ù[ïð©ìý¼‹Ç ïÆÖ7{¨qbžÞ¿ß ñí‘c¯œˆ|bž€gøì»AbÃ~ÔýÄ»ƒ<]×oáeGw_u]=§7ªÇ½Žñß~™Þ]¹/H‡ùHt´œ¢Û@2³‰NÐ/1(Ìÿ 8ä4s5…´Z‡Ü{/ÿ`Ç>uŸÕn{hö)˜ÿìÏErŽcúýµ{šŸ?îe‰xÚc``#Ê10Lb¸ÂèÄXÀ¸Ž‰É†Y…¹‰ÅƒåË/VÖe¬ØBØŽ°§±ÿáá˜Äñ€Óƒsç?® ® \·¸u¸gñ¸ðTðœâ5ãá]Âç·‚_Œß‡™@„@—À#A-ÁUB.BÛ„+D,D¦ˆ|õ]"æ'v@ÜHÈRÈJÈZ”õ([(Û"{Sö«Ÿœ 9—rrËrÏäþËsË«È[‘÷,ß&¿!ÿRHA\ÁŠ‚O…U…—ŠBŠÖów•è•¬*¹VªSº¢L©lQ¹Rù‚ ¹Š%•UÕÕeÕjjÒj6ÕòÕ:Õ–ÔIÔ¨ûUïU_R?¯þDý§¯†¢†ÍÇZÒZ^´úµÎh}×fÔVÔö¢Ý¢½¦ýYǚκÎG0ŽDxÚc`d``lg’da& fB0ŸýxÚmËNÂ@†ÿ¼£+C\6Ƹpm1a*^B„ A·åR!J!m½àcø.\ø ®tçÒ'ð9ü{:E0d2g¾óÏÌÎ €¼"•Î°9cVÈ2‹y«8ќšÓØ£æylâEóï¾k^¤û·æ%¬«'ͬ©gÍËØVoš?U_š?aª\àe¨`ˆ¼Àñ!|ÁGñ1|ŸÀ'ñ)|ŸÁgñ9|_Àq?¾„/ã+ø*¾†¯ãø&¾…oã;ø.¾‡ïãø!~„ã'ø)~†Ÿãø%~…_ã7ø-Àïð{üÄŸðgüÅßðwüÿÄ¿ðoüR…@DU2¨FujP“ZÔ¦u©G4IS4MhÚ•v£ÝiÊA´'íE{Ó>´/íGûÓô:¢ƒé:”£Ãé:’Ž¢£é:–Ž£ãi†6Ò,ÍÑ&ÚL[hž¶Ò6:N¤“èd:…N¥Óh;NgЙtMçйtOÐ…t]L—Ð¥t]NWЕt]M×еt]O7ÐtÝL&ÝBÙ•ûÉ!—õi@ù´ƒ†PHIŠi'%”RF9-Tîkä‘?3³}FÉÙ™™±ÜXÊÙRΕrS)7—rK)çK¹µ”ÛJ¹½³gr³–gñ>µA`¥i-ÌSß©§ÂJ¯)¢ÈXÔ<¶3#ͬ¤­S„q62òT$FßÂf晕 e^Cé~š‘ÖÊÑX–24ý¨©¥Ì³ªì÷ë©?ˆ¬ êÈA-K¬Ô3<Š&¯&L+Ȍ̅‘HËíºr1 XQÝͱQÏc%j~dË¥NX#Óñ'¼g,¬¬‘ˆ~"R¯©\Ñ ÒýÀ´ù0nìÉH¤íä¡0ÙŸN©ª Z¥žÇõ‰#]Ñ°--«™50ø/5l)‡MÕ„V2¬Å‰euÇ Eb}eü=pë~f¾ÓÉÄRfzÂxY[닾›ymþ6ˆÌ@ô³n¡:"ÊDÒ)ŒD ïúŽ<ÍüþÈPgéø‘ËãŠy¥®ÇNô-G¨¨™ ¾+d#ö,OD=‘ãíЊMå«Hꖫ䳟Âõ³ZêY‰¨9žà© 륙ˆMÛr†‹Vâöú‡pl5ÇŠ¡‚^‹-CƾLTWz¥Ò¨‰Âɺ¼ÏB"‹“÷Ɔ>B+òÔTÀh‡~TªDZoÈ¡–½¹àð£P$ÅfÒP.L–Ž/ˆ$óyÇéÒödâ/3|­ Åˆ7O-’-úã²¼™‚½¶ºâMÞ<‘Õ¡œÍi³t9íe^Ú)ûª7YZÊ]e·4‘xVÐïhv)8¥¡ÖeŠè~4dp¡lÄyêñ±zœ="aÚ0ÕgM!~TçÍcoÔø¼ƒ]à `µM-`ppU¾w4Ä‹&ÆÉ[˜m= Ø¬LËN|Ñw¬T´r‹<© ™Ç†Še1’»u[XÌU'Ïø*cŽŠküø±‘Z ¢­âcÚ Ô!#N&Œ'Ê’3FâEæñ‚¯•3/%¼¬`ì@Ô¼¾Ã4Ÿ;Ã_#ûÃé;±¢é°O ¤ðiV8 ³¦£Æw(FmŽ¹ÈôI›…ÊIZ(:‰ UÇŠó†)mñaŠ±5®þÁ¨]Rfj-jZCƒÊn‹¥Xeaq»|q1®–†ìH­Ï©UCá5Ìu±å6™æ4.šê-¡FNhES £ÙmrŒ¹zY¡^ -í &Wø®$ &“¢Xèü5f±–š¢ÊåP‘ £Ò0gç·uÖT–NšsFrúú1Ã:· ‡mëÆùò²Š/ÁT-¨Â8±ªšúáåù"p'Æ…¦ðfZ•(“ÑÄÊýÔãˆ&LvBž%Çe‚*«M:~´lX×SÔÚ.EPkmMP^› 'MçêŒM¦ÌvÁª%ˆ™™¸:îÂx÷ãÔOפ镾qÑ2̹™¹–~ú©õëÜÉþN¬¾t¹.(_w6ÁI¯`X(±ÅwýŒÐ´®SÂœÛ8Û.J¾®œöœÖª²YE CWž¯Š<©츚§nÕ’êŽxTu¢Qu˜,VíÌQÏdÑZÉÙ)ÍC¶FìY6g¤97»mÃJoÆtjç™Hwÿß.u¬Þ¸[sðô:Ks“97·I5›»#®¦¹]¤4Œ%¾æÖÒøé±2F³á2XøQÍ”Î/½1yñ‹íAb…õ>¿i‡IÕr™:6Îoœ°ýÌÎUèËk`& ’N!t×d y£Õ*Õ[cçñÚ¯ WSkì"Åù™+Ó§i"}·Æ‰‘/±›¾­jK:Å\Ôdž¤;s¾1~0Td½Ï´C5ª€g~\Msuµ[¶4Ô?7þ‚¨Úù€†µEáÛ’ÿqˆø—ÌϪfN5›þ jw©¤Q¸ŒQansible-1.7.2/docsite/_themes/srtd/static/js/000077500000000000000000000000001241061774000210755ustar00rootroot00000000000000ansible-1.7.2/docsite/_themes/srtd/static/js/theme.js000066400000000000000000000013051241061774000225340ustar00rootroot00000000000000$( document ).ready(function() { // Shift nav in mobile when clicking the menu. $("[data-toggle='wy-nav-top']").click(function() { $("[data-toggle='wy-nav-shift']").toggleClass("shift"); $("[data-toggle='rst-versions']").toggleClass("shift"); }); // Close menu when you click a link. $(".wy-menu-vertical .current ul li a").click(function() { $("[data-toggle='wy-nav-shift']").removeClass("shift"); $("[data-toggle='rst-versions']").toggleClass("shift"); }); $("[data-toggle='rst-current-version']").click(function() { $("[data-toggle='rst-versions']").toggleClass("shift-up"); }); $("table.docutils:not(.field-list").wrap("
    "); }); ansible-1.7.2/docsite/_themes/srtd/theme.conf000066400000000000000000000001471241061774000211450ustar00rootroot00000000000000[theme] inherit = basic stylesheet = css/theme.min.css [options] typekit_id = hiw1hhg analytics_id = ansible-1.7.2/docsite/_themes/srtd/versions.html000066400000000000000000000022521241061774000217310ustar00rootroot00000000000000{% if READTHEDOCS %} {# Add rst-badge after rst-versions for small badge style. #}
    Read the Docs v: {{ current_version }}
    Versions
    {% for slug, url in versions %}
    {{ slug }}
    {% endfor %}
    Downloads
    {% for type, url in downloads %}
    {{ type }}
    {% endfor %}
    On Read the Docs
    Project Home
    Builds
    Free document hosting provided by Read the Docs.
    {% endif %} ansible-1.7.2/docsite/build-site.py000077500000000000000000000062611241061774000172150ustar00rootroot00000000000000#!/usr/bin/env python # (c) 2012, Michael DeHaan # # This file is part of the Ansible Documentation # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . __docformat__ = 'restructuredtext' import os import sys import traceback try: from sphinx.application import Sphinx except ImportError: print "#################################" print "Dependency missing: Python Sphinx" print "#################################" sys.exit(1) import os class SphinxBuilder(object): """ Creates HTML documentation using Sphinx. """ def __init__(self): """ Run the DocCommand. """ print "Creating html documentation ..." try: buildername = 'html' outdir = os.path.abspath(os.path.join(os.getcwd(), "htmlout")) # Create the output directory if it doesn't exist if not os.access(outdir, os.F_OK): os.mkdir(outdir) doctreedir = os.path.join('./', '.doctrees') confdir = os.path.abspath('./') srcdir = os.path.abspath('rst') freshenv = True # Create the builder app = Sphinx(srcdir, confdir, outdir, doctreedir, buildername, {}, sys.stdout, sys.stderr, freshenv) app.builder.build_all() except ImportError, ie: traceback.print_exc() except Exception, ex: print >> sys.stderr, "FAIL! exiting ... (%s)" % ex def build_docs(self): self.app.builder.build_all() def build_rst_docs(): docgen = SphinxBuilder() if __name__ == '__main__': if '-h' in sys.argv or '--help' in sys.argv: print "This script builds the html documentation from rst/asciidoc sources.\n" print " Run 'make docs' to build everything." print " Run 'make viewdocs' to build and then preview in a web browser." sys.exit(0) # The 'htmldocs' make target will call this scrip twith the 'rst' # parameter' We don't need to run the 'htmlman' target then. if "rst" in sys.argv: build_rst_docs() else: # By default, preform the rst->html transformation and then # the asciidoc->html trasnformation build_rst_docs() if "view" in sys.argv: import webbrowser if not webbrowser.open('htmlout/index.html'): print >> sys.stderr, "Could not open on your webbrowser." ansible-1.7.2/docsite/conf.py000066400000000000000000000143141241061774000160740ustar00rootroot00000000000000# -*- coding: utf-8 -*- # # documentation build configuration file, created by # sphinx-quickstart on Sat Sep 27 13:23:22 2008-2009. # # This file is execfile()d with the current directory set to its # containing dir. # # The contents of this file are pickled, so don't put values in the namespace # that aren't pickleable (module imports are okay, they're removed # automatically). # # All configuration values have a default value; values that are commented out # serve to show the default value. import sys import os # pip install sphinx_rtd_theme #import sphinx_rtd_theme #html_theme_path = [sphinx_rtd_theme.get_html_theme_path()] # If your extensions are in another directory, add it here. If the directory # is relative to the documentation root, use os.path.abspath to make it # absolute, like shown here. #sys.path.append(os.path.abspath('some/directory')) # sys.path.insert(0, os.path.join('ansible', 'lib')) sys.path.append(os.path.abspath('_themes')) VERSION='0.01' AUTHOR='Ansible, Inc' # General configuration # --------------------- # Add any Sphinx extension module names here, as strings. # They can be extensions # coming with Sphinx (named 'sphinx.ext.*') or your custom ones. extensions = ['sphinx.ext.autodoc'] # Later on, add 'sphinx.ext.viewcode' to the list if you want to have # colorized code generated too for references. # Add any paths that contain templates here, relative to this directory. templates_path = ['.templates'] # The suffix of source filenames. source_suffix = '.rst' # The master toctree document. master_doc = 'index' # General substitutions. project = 'Ansible Documentation' copyright = "2013 Ansible, Inc" # The default replacements for |version| and |release|, also used in various # other places throughout the built documents. # # The short X.Y version. version = VERSION # The full version, including alpha/beta/rc tags. release = VERSION # There are two options for replacing |today|: either, you set today to some # non-false value, then it is used: #today = '' # Else, today_fmt is used as the format for a strftime call. today_fmt = '%B %d, %Y' # List of documents that shouldn't be included in the build. #unused_docs = [] # List of directories, relative to source directories, that shouldn't be # searched for source files. #exclude_dirs = [] # A list of glob-style patterns that should be excluded when looking # for source files. exclude_patterns = ['modules'] # The reST default role (used for this markup: `text`) to use for all # documents. #default_role = None # If true, '()' will be appended to :func: etc. cross-reference text. #add_function_parentheses = True # If true, the current module name will be prepended to all description # unit titles (such as .. function::). #add_module_names = True # If true, sectionauthor and moduleauthor directives will be shown in the # output. They are ignored by default. #show_authors = False # The name of the Pygments (syntax highlighting) style to use. pygments_style = 'sphinx' # Options for HTML output # ----------------------- html_theme_path = ['_themes'] html_theme = 'srtd' html_short_title = 'Ansible Documentation' # The style sheet to use for HTML and HTML Help pages. A file of that name # must exist either in Sphinx' static/ path, or in one of the custom paths # given in html_static_path. #html_style = 'solar.css' # The name for this set of Sphinx documents. If None, it defaults to # " v documentation". html_title = 'Ansible Documentation' # A shorter title for the navigation bar. Default is the same as html_title. #html_short_title = None # The name of an image file (within the static path) to place at the top of # the sidebar. #html_logo = None # The name of an image file (within the static path) to use as favicon of the # docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32 # pixels large. #html_favicon = 'favicon.ico' # Add any paths that contain custom static files (such as style sheets) here, # relative to this directory. They are copied after the builtin static files, # so a file named "default.css" will overwrite the builtin "default.css". #html_static_path = ['.static'] # If not '', a 'Last updated on:' timestamp is inserted at every page bottom, # using the given strftime format. html_last_updated_fmt = '%b %d, %Y' # If true, SmartyPants will be used to convert quotes and dashes to # typographically correct entities. #html_use_smartypants = True # Custom sidebar templates, maps document names to template names. #html_sidebars = {} # Additional templates that should be rendered to pages, maps page names to # template names. #html_additional_pages = {} # If false, no module index is generated. #html_use_modindex = True # If false, no index is generated. #html_use_index = True # If true, the index is split into individual pages for each letter. #html_split_index = False # If true, the reST sources are included in the HTML build as _sources/. html_copy_source = False # If true, an OpenSearch description file will be output, and all pages will # contain a tag referring to it. The value of this option must be the # base URL from which the finished HTML is served. #html_use_opensearch = '' # If nonempty, this is the file name suffix for HTML files (e.g. ".xhtml"). #html_file_suffix = '' # Output file base name for HTML help builder. htmlhelp_basename = 'Poseidodoc' # Options for LaTeX output # ------------------------ # The paper size ('letter' or 'a4'). #latex_paper_size = 'letter' # The font size ('10pt', '11pt' or '12pt'). #latex_font_size = '10pt' # Grouping the document tree into LaTeX files. List of tuples # (source start file, target name, title, author, document class # [howto/manual]). latex_documents = [ ('index', 'ansible.tex', 'Ansible 1.2 Documentation', AUTHOR, 'manual'), ] # The name of an image file (relative to this directory) to place at the top of # the title page. #latex_logo = None # For "manual" documents, if this is true, then toplevel headings are parts, # not chapters. #latex_use_parts = False # Additional stuff for the LaTeX preamble. #latex_preamble = '' # Documents to append as an appendix to all manuals. #latex_appendices = [] # If false, no module index is generated. #latex_use_modindex = True autoclass_content = 'both' ansible-1.7.2/docsite/favicon.ico000066400000000000000000000145661241061774000167270ustar00rootroot00000000000000 (&  (N(  9•ÊééÊ”9“ÿÿÿÿÿÿ ÿÿ’µÿÿù úüüúùÿÿ´“ÿù>>>ûÿþþ###þÿÿ444ûùÿ“: ÿÿûËËËÿ»»»þþ444þþþÇÇÇþÖÖÖÿúÿý:•ÿùÿ¨¨¨þðððþ@@@þþPPPþ×××þÿÿÿþÆÆÆþÿ øÿ“Ëÿúþ+++þëëëþœœœþgggþéééÿßßßþíííþwwwþÿ###ùÿÉêÿ üþþµµµþòòòþèèèþŸŸŸþ«««þÚÚÚþþþûÿèêÿü###þþ`a`þûûûþ£££þþåååþ§§§þþ(((þûÿèËÿúþþþÕÕÕþ®®®þƒ„ƒÿêëêþ888þþÿùÿÉ•ÿùÿ***þþ”””þäääþßßßþºººþþ$$$þÿøÿ“:ÿÿûÿþþæçæþÿÿÿþYYYþþ!!!ÿúÿý:“ÿùú"""ÿÿ¢¢¢ÿ¿¿¿ÿÿÿúúÿ“µÿÿø ùüüùøÿÿµ“þÿÿÿÿ ÿÿý“:”Éé éÉ“:( @ [–¿Øðð׿–[/—çÿÿÿÿÿÿÿÿÿÿç—/ ‰õÿÿüúúûýýûúúýÿÿõˆ 'ÊÿÿùúþÿÿÿþþþÿÿþúùÿÿÉ'4æÿúûÿÿþþþþþþþþþþÿÿûúÿæ3'æÿøþ ÿþþþþþþþþþþþþþþ ÿþøÿæ& Êÿøþþþþþ þþþþÿþþþþþþþþ þÿøÿÉ ‰ÿúþþ þ###þþþþ þþþþþþþþþþ333þþþ þþúÿˆ0õÿûÿþþªªªþðððþÉÉÉþþþþþÿþþ%%%þþÿ¯¯¯þóóóþ®®®þþ þ þûÿõ/˜ÿùÿþþþˆˆˆþÿÿÿþÿÿÿþ€€€þþ þþþþ(((þþþÊÊÊþÿÿÿþÿÿÿþÒÒÒþþþþþûÿ™çÿûÿþþþþ×××þÿÿÿþÃÄÃþþ þ þþþþ\\\þßßßþÿÿÿþÿÿÿþÿÿÿþ“““þþ þþÿúÿæ\ÿüþþþþþþžžžþÿÿÿþñññþSSSþþ***þþþ„„„þñññþÿÿÿþùùùþÿÿÿþåæåþ)))ÿþþþþýþÿ\—ÿùÿþþþþþFFFþìììþÿÿÿþ¥¥¥þþþþ¦¦¦þÿÿÿþÿÿÿþÓÓÓþéééþÿÿÿþ°°¯þþ###þþþþÿúÿ•Àÿúþþþþ þþþ»»»þÿÿÿþßßßþþþÃÃÃþÿÿÿþÿÿÿþ®®®þ~~~þÿÿÿþöööþZZZþþ!!!þþþþÿùÿ½Øÿûþþþþþ%%%þþoooþûûûþÿÿÿþþÑÑÑþÿÿÿþ÷÷÷þšššþþÇÇÇþÿÿÿþÈÈÈþþþþþþþÿùÿÕñÿýþþþþþþþþÕÕÕþÿÿÿþûûûþÿÿÿþæææþrrrþþ___þõõõþÿÿÿþ~~~þþ###þþþþþÿüÿîñÿýþþþÿþþ'''þþ“““þÿÿÿþÿÿÿþÏÏÏþ666þþþ«¬«þÿÿÿþÞÞÞþþþþþÿþþÿüÿîØÿûþþþþþþþþþçççþÿÿÿþþþþþáááþÿÿÿþžžžþþþþþþþþÿùÿÕÀÿúþþþþþþþ þþ­­­þÿÿÿþÞÞÞþ'''þþˆˆˆþÿÿÿþïïïþDDDþþþþþþþþÿùÿ½—ÿùÿþþþþþþþþXXXþöööþÿÿÿþ~~~þþÌÌÌþÿÿÿþºººþþþþþþþþþÿúÿ•\ÿüþþþþþÿþþ þþÅÅÅþÿÿÿþ¼¼¼ÿ@@@þøùøþüüüþoooþÿ!!!þþÿþþþþýÿÿ\çÿúÿþþþþþþ þþ~~~þÿÿÿþëìëþÀÀÀþÿÿÿþÕÕÕþþþþþþþþþÿúÿå˜ÿùÿþþþþþþþþþÞÞÞþÿÿÿþüüüþÿÿÿþ–––þþ'''þþþþþþþþûÿ™0õÿûÿþþþþþþ###þþ¤¥¤þÿÿÿÿÿÿÿþçççþ///þþÿþþþþþþûÿõ.‰ÿúþþþþþþþþþEEEþðððÿÿÿÿþ°°°þþ$$$þþþþþþþþúÿˆ Êÿøÿþþþþþþþþ›››þÈÈÈþHHHþþþþþþþþÿ÷ÿÉ 'æÿ÷þþþþþþþþþþþþþþþþþþ÷ÿæ&4çÿúûþÿþþþþþþþþþþÿþûúÿæ2'ÊÿÿûúýÿÿÿÿÿÿÿÿýúûÿÿÉ& ‰õÿÿþúùùüüùùúÿÿÿõˆ /šæÿÿÿÿÿÿÿÿÿÿæ™/]–¾ÕïïÕ½•\ansible-1.7.2/docsite/js/000077500000000000000000000000001241061774000152065ustar00rootroot00000000000000ansible-1.7.2/docsite/js/ansible/000077500000000000000000000000001241061774000166235ustar00rootroot00000000000000ansible-1.7.2/docsite/js/ansible/application.js000066400000000000000000000055261241061774000214740ustar00rootroot00000000000000angular.module('ansibleApp', []).filter('moduleVersion', function() { return function(modules, version) { var parseVersionString = function (str) { if (typeof(str) != 'string') { return false; } var x = str.split('.'); // parse from string or default to 0 if can't parse var maj = parseInt(x[0]) || 0; var min = parseInt(x[1]) || 0; var pat = parseInt(x[2]) || 0; return { major: maj, minor: min, patch: pat } } var vMinMet = function(vmin, vcurrent) { minimum = parseVersionString(vmin); running = parseVersionString(vcurrent); if (running.major != minimum.major) return (running.major > minimum.major); else { if (running.minor != minimum.minor) return (running.minor > minimum.minor); else { if (running.patch != minimum.patch) return (running.patch > minimum.patch); else return true; } } }; var result = []; if (!version) { return modules; } for (var i = 0; i < modules.length; i++) { if (vMinMet(modules[i].version_added, version)) { result[result.length] = modules[i]; } } return result; }; }).filter('uniqueVersion', function() { return function(modules) { var result = []; var inArray = function (needle, haystack) { var length = haystack.length; for(var i = 0; i < length; i++) { if(haystack[i] == needle) return true; } return false; } var parseVersionString = function (str) { if (typeof(str) != 'string') { return false; } var x = str.split('.'); // parse from string or default to 0 if can't parse var maj = parseInt(x[0]) || 0; var min = parseInt(x[1]) || 0; var pat = parseInt(x[2]) || 0; return { major: maj, minor: min, patch: pat } } for (var i = 0; i < modules.length; i++) { if (!inArray(modules[i].version_added, result)) { // Some module do not define version if (modules[i].version_added) { result[result.length] = "" + modules[i].version_added; } } } result.sort( function (a, b) { ao = parseVersionString(a); bo = parseVersionString(b); if (ao.major == bo.major) { if (ao.minor == bo.minor) { if (ao.patch == bo.patch) { return 0; } else { return (ao.patch > bo.patch) ? 1 : -1; } } else { return (ao.minor > bo.minor) ? 1 : -1; } } else { return (ao.major > bo.major) ? 1 : -1; } }); return result; }; }); ansible-1.7.2/docsite/man/000077500000000000000000000000001241061774000153455ustar00rootroot00000000000000ansible-1.7.2/docsite/man/ansible-playbook.1.html000066400000000000000000000104011241061774000216210ustar00rootroot00000000000000 ansible-playbook

    Name

    ansible-playbook — run an ansible playbook

    Synopsis

    ansible-playbook <filename.yml> … [options]

    DESCRIPTION

    Ansible playbooks are a configuration and multinode deployment system. Ansible-playbook is the tool used to run them. See the project home page (link below) for more information.

    ARGUMENTS

    filename.yml
    The names of one or more YAML format files to run as ansible playbooks.

    OPTIONS

    -i PATH, --inventory=PATH
    The PATH to the inventory hosts file, which defaults to /etc/ansible/hosts.
    -M DIRECTORY, --module-path=DIRECTORY
    The DIRECTORY to load modules from. The default is /usr/share/ansible.
    -f NUM, --forks=NUM
    Level of parallelism. NUM is specified as an integer, the default is 5.
    -k, --ask-pass
    Prompt for the SSH password instead of assuming key-based authentication with ssh-agent.
    -T SECONDS, --timeout=SECONDS
    Connection timeout to use when trying to talk to hosts, in SECONDS.

    ENVIRONMENT

    The following environment variables may specified.

    ANSIBLE_HOSTS  — Override the default ansible hosts file

    ANSIBLE_LIBRARY — Override the default ansible module library path

    AUTHOR

    Ansible was originally written by Michael DeHaan. See the AUTHORS file for a complete list of contributors.

    COPYRIGHT

    Copyright © 2012, Michael DeHaan

    Ansible is released under the terms of the GPLv3 License.

    SEE ALSO

    ansible(1)

    Extensive documentation as well as IRC and mailing list info is available on the ansible home page: https://ansible.github.com/

    ansible-1.7.2/docsite/man/ansible.1.html000066400000000000000000000156401241061774000200150ustar00rootroot00000000000000 ansible

    Name

    ansible — run a command somewhere else

    Synopsis

    ansible <host-pattern> [-f forks] [-m module_name] [-a args]

    DESCRIPTION

    Ansible is an extra-simple tool/framework/API for doing 'remote things' over SSH.

    ARGUMENTS

    host-pattern
    A name of a group in the inventory file, a shell-like glob selecting hosts in inventory file, or any combination of the two separated by semicolons.

    OPTIONS

    -i PATH, --inventory=PATH
    The PATH to the inventory hosts file, which defaults to /etc/ansible/hosts.
    -f NUM, --forks=NUM
    Level of parallelism. NUM is specified as an integer, the default is 5.
    -m NAME, --module-name=NAME
    Execute the module called NAME.
    -M DIRECTORY, --module-path=DIRECTORY
    The DIRECTORY to load modules from. The default is /usr/share/ansible.
    -a 'ARGUMENTS', --args='ARGUMENTS'
    The ARGUMENTS to pass to the module.
    -k, --ask-pass
    Prompt for the SSH password instead of assuming key-based authentication with ssh-agent.
    -o, --one-line
    Try to output everything on one line.
    -t DIRECTORY, --tree=DIRECTORY
    Save contents in this output DIRECTORY, with the results saved in a file named after each host.
    -T SECONDS, --timeout=SECONDS
    Connection timeout to use when trying to talk to hosts, in SECONDS.
    -B NUM, --background=NUM
    Run commands in the background, killing the task after NUM seconds.
    -P NUM, --poll=NUM
    Poll a background job every NUM seconds. Requires -B.
    -u USERNAME, --remote-user=USERNAME
    Use this remote USERNAME instead of root.

    INVENTORY

    Ansible stores the hosts it can potentially operate on in an inventory file. The syntax is one host per line. Groups headers are allowed and are included on their own line, enclosed in square brackets.

    FILES

    /etc/ansible/hosts — Default inventory file

    /usr/share/ansible/ — Default module library

    ENVIRONMENT

    The following environment variables may specified.

    ANSIBLE_HOSTS  — Override the default ansible hosts file

    ANSIBLE_LIBRARY — Override the default ansible module library path

    AUTHOR

    Ansible was originally written by Michael DeHaan. See the AUTHORS file for a complete list of contributors.

    COPYRIGHT

    Copyright © 2012, Michael DeHaan

    Ansible is released under the terms of the GPLv3 License.

    SEE ALSO

    ansible-playbook(1)

    Extensive documentation as well as IRC and mailing list info is available on the ansible home page: https://ansible.github.com/

    ansible-1.7.2/docsite/modules.js000066400000000000000000000001321241061774000165740ustar00rootroot00000000000000function AnsibleModules($scope) { $scope.modules = []; $scope.orderProp = "module"; }ansible-1.7.2/docsite/rst/000077500000000000000000000000001241061774000154025ustar00rootroot00000000000000ansible-1.7.2/docsite/rst/YAMLSyntax.rst000066400000000000000000000064451241061774000201160ustar00rootroot00000000000000YAML Syntax =========== This page provides a basic overview of correct YAML syntax, which is how Ansible playbooks (our configuration management language) are expressed. We use YAML because it is easier for humans to read and write than other common data formats like XML or JSON. Further, there are libraries available in most programming languages for working with YAML. You may also wish to read :doc:`playbooks` at the same time to see how this is used in practice. YAML Basics ----------- For Ansible, nearly every YAML file starts with a list. Each item in the list is a list of key/value pairs, commonly called a "hash" or a "dictionary". So, we need to know how to write lists and dictionaries in YAML. There's another small quirk to YAML. All YAML files (regardless of their association with Ansible or not) should begin with ``---``. This is part of the YAML format and indicates the start of a document. All members of a list are lines beginning at the same indentation level starting with a ``-`` (dash) character:: --- # A list of tasty fruits - Apple - Orange - Strawberry - Mango A dictionary is represented in a simple ``key:`` and ``value`` form:: --- # An employee record name: Example Developer job: Developer skill: Elite Dictionaries can also be represented in an abbreviated form if you really want to:: --- # An employee record {name: Example Developer, job: Developer, skill: Elite} .. _truthiness: Ansible doesn't really use these too much, but you can also specify a boolean value (true/false) in several forms:: --- create_key: yes needs_agent: no knows_oop: True likes_emacs: TRUE uses_cvs: false Let's combine what we learned so far in an arbitrary YAML example. This really has nothing to do with Ansible, but will give you a feel for the format:: --- # An employee record name: Example Developer job: Developer skill: Elite employed: True foods: - Apple - Orange - Strawberry - Mango languages: ruby: Elite python: Elite dotnet: Lame That's all you really need to know about YAML to start writing `Ansible` playbooks. Gotchas ------- While YAML is generally friendly, the following is going to result in a YAML syntax error: foo: somebody said I should put a colon here: so I did You will want to quote any hash values using colons, like so: foo: "somebody said I should put a colon here: so I did" And then the colon will be preserved. Further, Ansible uses "{{ var }}" for variables. If a value after a colon starts with a "{", YAML will think it is a dictionary, so you must quote it, like so:: foo: "{{ variable }}" .. seealso:: :doc:`playbooks` Learn what playbooks can do and how to write/run them. `YAMLLint `_ YAML Lint (online) helps you debug YAML syntax if you are having problems `Github examples directory `_ Complete playbook files from the github project source `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/community.rst000066400000000000000000000010431241061774000201560ustar00rootroot00000000000000Community Information ````````````````````` Ansible is an open source project designed to bring together developers and administrators of all kinds to collaborate on building IT automation solutions that work well for them. Should you wish to get more involved -- whether in terms of just asking a question, helping other users, introducing new people to Ansible, or helping with the software or documentation, we welcome your contributions to the project. `Ways to interact `_ ansible-1.7.2/docsite/rst/developing.rst000066400000000000000000000010401241061774000202630ustar00rootroot00000000000000Developer Information ````````````````````` Learn how to build modules of your own in any language, and also how to extend Ansible through several kinds of plugins. Explore Ansible's Python API and write Python plugins to integrate with other solutions in your environment. .. toctree:: :maxdepth: 1 developing_api developing_inventory developing_modules developing_plugins Developers will also likely be interested in the fully-discoverable in :doc:`tower`. It's great for embedding Ansible in all manner of applications. ansible-1.7.2/docsite/rst/developing_api.rst000066400000000000000000000062541241061774000211300ustar00rootroot00000000000000Python API ========== .. contents:: Topics There are several interesting ways to use Ansible from an API perspective. You can use the Ansible python API to control nodes, you can extend Ansible to respond to various python events, you can write various plugins, and you can plug in inventory data from external data sources. This document covers the Runner and Playbook API at a basic level. If you are looking to use Ansible programmatically from something other than Python, trigger events asynchronously, or have access control and logging demands, take a look at :doc:`tower` as it has a very nice REST API that provides all of these things at a higher level. Ansible is written in its own API so you have a considerable amount of power across the board. This chapter discusses the Python API. .. _python_api: Python API ---------- The Python API is very powerful, and is how the ansible CLI and ansible-playbook are implemented. It's pretty simple:: import ansible.runner runner = ansible.runner.Runner( module_name='ping', module_args='', pattern='web*', forks=10 ) datastructure = runner.run() The run method returns results per host, grouped by whether they could be contacted or not. Return types are module specific, as expressed in the :doc:`modules` documentation.:: { "dark" : { "web1.example.com" : "failure message" }, "contacted" : { "web2.example.com" : 1 } } A module can return any type of JSON data it wants, so Ansible can be used as a framework to rapidly build powerful applications and scripts. .. _detailed_api_example: Detailed API Example ```````````````````` The following script prints out the uptime information for all hosts:: #!/usr/bin/python import ansible.runner import sys # construct the ansible runner and execute on all hosts results = ansible.runner.Runner( pattern='*', forks=10, module_name='command', module_args='/usr/bin/uptime', ).run() if results is None: print "No hosts found" sys.exit(1) print "UP ***********" for (hostname, result) in results['contacted'].items(): if not 'failed' in result: print "%s >>> %s" % (hostname, result['stdout']) print "FAILED *******" for (hostname, result) in results['contacted'].items(): if 'failed' in result: print "%s >>> %s" % (hostname, result['msg']) print "DOWN *********" for (hostname, result) in results['dark'].items(): print "%s >>> %s" % (hostname, result) Advanced programmers may also wish to read the source to ansible itself, for it uses the Runner() API (with all available options) to implement the command line tools ``ansible`` and ``ansible-playbook``. .. seealso:: :doc:`developing_inventory` Developing dynamic inventory integrations :doc:`developing_modules` How to develop modules :doc:`developing_plugins` How to develop plugins `Development Mailing List `_ Mailing list for development topics `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/developing_inventory.rst000066400000000000000000000073411241061774000224120ustar00rootroot00000000000000Developing Dynamic Inventory Sources ==================================== .. contents:: Topics :local: As described in :doc:`intro_dynamic_inventory`, ansible can pull inventory information from dynamic sources, including cloud sources. How do we write a new one? Simple! We just create a script or program that can return JSON in the right format when fed the proper arguments. You can do this in any language. .. _inventory_script_conventions: Script Conventions `````````````````` When the external node script is called with the single argument ``--list``, the script must return a JSON hash/dictionary of all the groups to be managed. Each group's value should be either a hash/dictionary containing a list of each host/IP, potential child groups, and potential group variables, or simply a list of host/IP addresses, like so:: { "databases" : { "hosts" : [ "host1.example.com", "host2.example.com" ], "vars" : { "a" : true } }, "webservers" : [ "host2.example.com", "host3.example.com" ], "atlanta" : { "hosts" : [ "host1.example.com", "host4.example.com", "host5.example.com" ], "vars" : { "b" : false }, "children": [ "marietta", "5points" ] }, "marietta" : [ "host6.example.com" ], "5points" : [ "host7.example.com" ] } .. versionadded:: 1.0 Before version 1.0, each group could only have a list of hostnames/IP addresses, like the webservers, marietta, and 5points groups above. When called with the arguments ``--host `` (where is a host from above), the script must return either an empty JSON hash/dictionary, or a hash/dictionary of variables to make available to templates and playbooks. Returning variables is optional, if the script does not wish to do this, returning an empty hash/dictionary is the way to go:: { "favcolor" : "red", "ntpserver" : "wolf.example.com", "monitoring" : "pack.example.com" } .. _inventory_script_tuning: Tuning the External Inventory Script ```````````````````````````````````` .. versionadded:: 1.3 The stock inventory script system detailed above works for all versions of Ansible, but calling ``--host`` for every host can be rather expensive, especially if it involves expensive API calls to a remote subsystem. In Ansible 1.3 or later, if the inventory script returns a top level element called "_meta", it is possible to return all of the host variables in one inventory script call. When this meta element contains a value for "hostvars", the inventory script will not be invoked with ``--host`` for each host. This results in a significant performance increase for large numbers of hosts, and also makes client side caching easier to implement for the inventory script. The data to be added to the top level JSON dictionary looks like this:: { # results of inventory script as above go here # ... "_meta" : { "hostvars" : { "moocow.example.com" : { "asdf" : 1234 }, "llama.example.com" : { "asdf" : 5678 }, } } } .. seealso:: :doc:`developing_api` Python API to Playbooks and Ad Hoc Task Execution :doc:`developing_modules` How to develop modules :doc:`developing_plugins` How to develop plugins `Ansible Tower `_ REST API endpoint and GUI for Ansible, syncs with dynamic inventory `Development Mailing List `_ Mailing list for development topics `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/developing_modules.rst000066400000000000000000000413261241061774000220260ustar00rootroot00000000000000Developing Modules ================== .. contents:: Topics Ansible modules are reusable units of magic that can be used by the Ansible API, or by the `ansible` or `ansible-playbook` programs. See :doc:`modules` for a list of various ones developed in core. Modules can be written in any language and are found in the path specified by `ANSIBLE_LIBRARY` or the ``--module-path`` command line option. Should you develop an interesting Ansible module, consider sending a pull request to the `github project `_ to see about getting your module included in the core project. .. _module_dev_tutorial: Tutorial ```````` Let's build a very-basic module to get and set the system time. For starters, let's build a module that just outputs the current time. We are going to use Python here but any language is possible. Only File I/O and outputting to standard out are required. So, bash, C++, clojure, Python, Ruby, whatever you want is fine. Now Python Ansible modules contain some extremely powerful shortcuts (that all the core modules use) but first we are going to build a module the very hard way. The reason we do this is because modules written in any language OTHER than Python are going to have to do exactly this. We'll show the easy way later. So, here's an example. You would never really need to build a module to set the system time, the 'command' module could already be used to do this. Though we're going to make one. Reading the modules that come with ansible (linked above) is a great way to learn how to write modules. Keep in mind, though, that some modules in ansible's source tree are internalisms, so look at `service` or `yum`, and don't stare too close into things like `async_wrapper` or you'll turn to stone. Nobody ever executes async_wrapper directly. Ok, let's get going with an example. We'll use Python. For starters, save this as a file named `time`:: #!/usr/bin/python import datetime import json date = str(datetime.datetime.now()) print json.dumps({ "time" : date }) .. _module_testing: Testing Modules ``````````````` There's a useful test script in the source checkout for ansible:: git clone git@github.com:ansible/ansible.git source ansible/hacking/env-setup chmod +x ansible/hacking/test-module Let's run the script you just wrote with that:: ansible/hacking/test-module -m ./time You should see output that looks something like this:: {u'time': u'2012-03-14 22:13:48.539183'} If you did not, you might have a typo in your module, so recheck it and try again. .. _reading_input: Reading Input ````````````` Let's modify the module to allow setting the current time. We'll do this by seeing if a key value pair in the form `time=` is passed in to the module. Ansible internally saves arguments to an arguments file. So we must read the file and parse it. The arguments file is just a string, so any form of arguments are legal. Here we'll do some basic parsing to treat the input as key=value. The example usage we are trying to achieve to set the time is:: time time="March 14 22:10" If no time parameter is set, we'll just leave the time as is and return the current time. .. note:: This is obviously an unrealistic idea for a module. You'd most likely just use the shell module. However, it probably makes a decent tutorial. Let's look at the code. Read the comments as we'll explain as we go. Note that this is highly verbose because it's intended as an educational example. You can write modules a lot shorter than this:: #!/usr/bin/python # import some python modules that we'll use. These are all # available in Python's core import datetime import sys import json import os import shlex # read the argument string from the arguments file args_file = sys.argv[1] args_data = file(args_file).read() # for this module, we're going to do key=value style arguments # this is up to each module to decide what it wants, but all # core modules besides 'command' and 'shell' take key=value # so this is highly recommended arguments = shlex.split(args_data) for arg in arguments: # ignore any arguments without an equals in it if "=" in arg: (key, value) = arg.split("=") # if setting the time, the key 'time' # will contain the value we want to set the time to if key == "time": # now we'll affect the change. Many modules # will strive to be 'idempotent', meaning they # will only make changes when the desired state # expressed to the module does not match # the current state. Look at 'service' # or 'yum' in the main git tree for an example # of how that might look. rc = os.system("date -s \"%s\"" % value) # always handle all possible errors # # when returning a failure, include 'failed' # in the return data, and explain the failure # in 'msg'. Both of these conventions are # required however additional keys and values # can be added. if rc != 0: print json.dumps({ "failed" : True, "msg" : "failed setting the time" }) sys.exit(1) # when things do not fail, we do not # have any restrictions on what kinds of # data are returned, but it's always a # good idea to include whether or not # a change was made, as that will allow # notifiers to be used in playbooks. date = str(datetime.datetime.now()) print json.dumps({ "time" : date, "changed" : True }) sys.exit(0) # if no parameters are sent, the module may or # may not error out, this one will just # return the time date = str(datetime.datetime.now()) print json.dumps({ "time" : date }) Let's test that module:: ansible/hacking/test-module -m ./time -a time=\"March 14 12:23\" This should return something like:: {"changed": true, "time": "2012-03-14 12:23:00.000307"} .. _module_provided_facts: Module Provided 'Facts' ``````````````````````` The 'setup' module that ships with Ansible provides many variables about a system that can be used in playbooks and templates. However, it's possible to also add your own facts without modifying the system module. To do this, just have the module return a `ansible_facts` key, like so, along with other return data:: { "changed" : True, "rc" : 5, "ansible_facts" : { "leptons" : 5000, "colors" : { "red" : "FF0000", "white" : "FFFFFF" } } } These 'facts' will be available to all statements called after that module (but not before) in the playbook. A good idea might be make a module called 'site_facts' and always call it at the top of each playbook, though we're always open to improving the selection of core facts in Ansible as well. .. _common_module_boilerplate: Common Module Boilerplate ````````````````````````` As mentioned, if you are writing a module in Python, there are some very powerful shortcuts you can use. Modules are still transferred as one file, but an arguments file is no longer needed, so these are not only shorter in terms of code, they are actually FASTER in terms of execution time. Rather than mention these here, the best way to learn is to read some of the `source of the modules `_ that come with Ansible. The 'group' and 'user' modules are reasonably non-trivial and showcase what this looks like. Key parts include always ending the module file with:: from ansible.module_utils.basic import * main() And instantiating the module class like:: module = AnsibleModule( argument_spec = dict( state = dict(default='present', choices=['present', 'absent']), name = dict(required=True), enabled = dict(required=True, choices=BOOLEANS), something = dict(aliases=['whatever']) ) ) The AnsibleModule provides lots of common code for handling returns, parses your arguments for you, and allows you to check inputs. Successful returns are made like this:: module.exit_json(changed=True, something_else=12345) And failures are just as simple (where 'msg' is a required parameter to explain the error):: module.fail_json(msg="Something fatal happened") There are also other useful functions in the module class, such as module.md5(path). See lib/ansible/module_common.py in the source checkout for implementation details. Again, modules developed this way are best tested with the hacking/test-module script in the git source checkout. Because of the magic involved, this is really the only way the scripts can function outside of Ansible. If submitting a module to ansible's core code, which we encourage, use of the AnsibleModule class is required. .. _developing_for_check_mode: Check Mode `````````` .. versionadded:: 1.1 Modules may optionally support check mode. If the user runs Ansible in check mode, the module should try to predict whether changes will occur. For your module to support check mode, you must pass ``supports_check_mode=True`` when instantiating the AnsibleModule object. The AnsibleModule.check_mode attribute will evaluate to True when check mode is enabled. For example:: module = AnsibleModule( argument_spec = dict(...), supports_check_mode=True ) if module.check_mode: # Check if any changes would be made by don't actually make those changes module.exit_json(changed=check_if_system_state_would_be_changed()) Remember that, as module developer, you are responsible for ensuring that no system state is altered when the user enables check mode. If your module does not support check mode, when the user runs Ansible in check mode, your module will simply be skipped. .. _module_dev_pitfalls: Common Pitfalls ``````````````` You should also never do this in a module:: print "some status message" Because the output is supposed to be valid JSON. Except that's not quite true, but we'll get to that later. Modules must not output anything on standard error, because the system will merge standard out with standard error and prevent the JSON from parsing. Capturing standard error and returning it as a variable in the JSON on standard out is fine, and is, in fact, how the command module is implemented. If a module returns stderr or otherwise fails to produce valid JSON, the actual output will still be shown in Ansible, but the command will not succeed. Always use the hacking/test-module script when developing modules and it will warn you about these kind of things. .. _module_dev_conventions: Conventions/Recommendations ``````````````````````````` As a reminder from the example code above, here are some basic conventions and guidelines: * If the module is addressing an object, the parameter for that object should be called 'name' whenever possible, or accept 'name' as an alias. * If you have a company module that returns facts specific to your installations, a good name for this module is `site_facts`. * Modules accepting boolean status should generally accept 'yes', 'no', 'true', 'false', or anything else a user may likely throw at them. The AnsibleModule common code supports this with "choices=BOOLEANS" and a module.boolean(value) casting function. * Include a minimum of dependencies if possible. If there are dependencies, document them at the top of the module file, and have the module raise JSON error messages when the import fails. * Modules must be self-contained in one file to be auto-transferred by ansible. * If packaging modules in an RPM, they only need to be installed on the control machine and should be dropped into /usr/share/ansible. This is entirely optional and up to you. * Modules should return JSON or key=value results all on one line. JSON is best if you can do JSON. All return types must be hashes (dictionaries) although they can be nested. Lists or simple scalar values are not supported, though they can be trivially contained inside a dictionary. * In the event of failure, a key of 'failed' should be included, along with a string explanation in 'msg'. Modules that raise tracebacks (stacktraces) are generally considered 'poor' modules, though Ansible can deal with these returns and will automatically convert anything unparseable into a failed result. If you are using the AnsibleModule common Python code, the 'failed' element will be included for you automatically when you call 'fail_json'. * Return codes from modules are not actually not significant, but continue on with 0=success and non-zero=failure for reasons of future proofing. * As results from many hosts will be aggregated at once, modules should return only relevant output. Returning the entire contents of a log file is generally bad form. .. _module_dev_shorthand: Shorthand Vs JSON ````````````````` To make it easier to write modules in bash and in cases where a JSON module might not be available, it is acceptable for a module to return key=value output all on one line, like this. The Ansible parser will know what to do:: somekey=1 somevalue=2 rc=3 favcolor=red If you're writing a module in Python or Ruby or whatever, though, returning JSON is probably the simplest way to go. .. _module_documenting: Documenting Your Module ``````````````````````` All modules included in the CORE distribution must have a ``DOCUMENTATION`` string. This string MUST be a valid YAML document which conforms to the schema defined below. You may find it easier to start writing your ``DOCUMENTATION`` string in an editor with YAML syntax highlighting before you include it in your Python file. .. _module_doc_example: Example +++++++ See an example documentation string in the checkout under `examples/DOCUMENTATION.yml `_. Include it in your module file like this:: #!/usr/bin/env python # Copyright header.... DOCUMENTATION = ''' --- module: modulename short_description: This is a sentence describing the module # ... snip ... ''' The ``description``, and ``notes`` fields support formatting with some special macros. These formatting functions are ``U()``, ``M()``, ``I()``, and ``C()`` for URL, module, italic, and constant-width respectively. It is suggested to use ``C()`` for file and option names, and ``I()`` when referencing parameters; module names should be specifies as ``M(module)``. Examples (which typically contain colons, quotes, etc.) are difficult to format with YAML, so these must be written in plain text in an ``EXAMPLES`` string within the module like this:: EXAMPLES = ''' - action: modulename opt1=arg1 opt2=arg2 ''' The EXAMPLES section, just like the documentation section, is required in all module pull requests for new modules. .. _module_dev_testing: Building & Testing ++++++++++++++++++ Put your completed module file into the 'library' directory and then run the command: ``make webdocs``. The new 'modules.html' file will be built and appear in the 'docsite/' directory. .. tip:: If you're having a problem with the syntax of your YAML you can validate it on the `YAML Lint `_ website. .. tip:: You can use ANSIBLE_KEEP_REMOTE_FILES=1 to prevent ansible from deleting the remote files so you can debug your module. .. _module_contribution: Getting Your Module Into Core ````````````````````````````` High-quality modules with minimal dependencies can be included in the core, but core modules (just due to the programming preferences of the developers) will need to be implemented in Python and use the AnsibleModule common code, and should generally use consistent arguments with the rest of the program. Stop by the mailing list to inquire about requirements if you like, and submit a github pull request to the main project. .. seealso:: :doc:`modules` Learn about available modules :doc:`developing_plugins` Learn about developing plugins :doc:`developing_api` Learn about the Python API for playbook and task execution `Github modules directory `_ Browse source of core modules `Mailing List `_ Development mailing list `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/developing_plugins.rst000066400000000000000000000134301241061774000220320ustar00rootroot00000000000000Developing Plugins ================== .. contents:: Topics Ansible is pluggable in a lot of other ways separate from inventory scripts and callbacks. Many of these features are there to cover fringe use cases and are infrequently needed, and others are pluggable simply because they are there to implement core features in ansible and were most convenient to be made pluggable. This section will explore these features, though they are generally not common in terms of things people would look to extend quite as often. .. _developing_connection_type_plugins: Connection Type Plugins ----------------------- By default, ansible ships with a 'paramiko' SSH, native ssh (just called 'ssh'), 'local' connection type, and there are also some minor players like 'chroot' and 'jail'. All of these can be used in playbooks and with /usr/bin/ansible to decide how you want to talk to remote machines. The basics of these connection types are covered in the :doc:`intro_getting_started` section. Should you want to extend Ansible to support other transports (SNMP? Message bus? Carrier Pigeon?) it's as simple as copying the format of one of the existing modules and dropping it into the connection plugins directory. The value of 'smart' for a connection allows selection of paramiko or openssh based on system capabilities, and chooses 'ssh' if OpenSSH supports ControlPersist, in Ansible 1.2.1 an later. Previous versions did not support 'smart'. More documentation on writing connection plugins is pending, though you can jump into `lib/ansible/runner/connection_plugins `_ and figure things out pretty easily. .. _developing_lookup_plugins: Lookup Plugins -------------- Language constructs like "with_fileglob" and "with_items" are implemented via lookup plugins. Just like other plugin types, you can write your own. More documentation on writing connection plugins is pending, though you can jump into `lib/ansible/runner/lookup_plugins `_ and figure things out pretty easily. .. _developing_vars_plugins: Vars Plugins ------------ Playbook constructs like 'host_vars' and 'group_vars' work via 'vars' plugins. They inject additional variable data into ansible runs that did not come from an inventory, playbook, or command line. Note that variables can also be returned from inventory, so in most cases, you won't need to write or understand vars_plugins. More documentation on writing connection plugins is pending, though you can jump into `lib/ansible/inventory/vars_plugins `_ and figure things out pretty easily. If you find yourself wanting to write a vars_plugin, it's more likely you should write an inventory script instead. .. _developing_filter_plugins: Filter Plugins -------------- If you want more Jinja2 filters available in a Jinja2 template (filters like to_yaml and to_json are provided by default), they can be extended by writing a filter plugin. Most of the time, when someone comes up with an idea for a new filter they would like to make available in a playbook, we'll just include them in 'core.py' instead. Jump into `lib/ansible/runner/filter_plugins/ `_ for details. .. _developing_callbacks: Callbacks --------- Callbacks are one of the more interesting plugin types. Adding additional callback plugins to Ansible allows for adding new behaviors when responding to events. .. _callback_examples: Examples ++++++++ Example callbacks are shown in `plugins/callbacks `_. The `log_plays `_ callback is an example of how to intercept playbook events to a log file, and the `mail `_ callback sends email when playbooks complete. The `osx_say `_ callback provided is particularly entertaining -- it will respond with computer synthesized speech on OS X in relation to playbook events, and is guaranteed to entertain and/or annoy coworkers. .. _configuring_callbacks: Configuring +++++++++++ To active a callback drop it in a callback directory as configured in :ref:`ansible.cfg `. .. _callback_development: Development +++++++++++ More information will come later, though see the source of any of the existing callbacks and you should be able to get started quickly. They should be reasonably self-explanatory. .. _distributing_plugins: Distributing Plugins -------------------- Plugins are loaded from both Python's site_packages (those that ship with ansible) and a configured plugins directory, which defaults to /usr/share/ansible/plugins, in a subfolder for each plugin type:: * action_plugins * lookup_plugins * callback_plugins * connection_plugins * filter_plugins * vars_plugins To change this path, edit the ansible configuration file. In addition, plugins can be shipped in a subdirectory relative to a top-level playbook, in folders named the same as indicated above. .. seealso:: :doc:`modules` List of built-in modules :doc:`developing_api` Learn about the Python API for task execution :doc:`developing_inventory` Learn about how to develop dynamic inventory sources :doc:`developing_modules` Learn about how to write Ansible modules `Mailing List `_ The development mailing list `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/faq.rst000066400000000000000000000273111241061774000167070ustar00rootroot00000000000000Frequently Asked Questions ========================== Here are some commonly-asked questions and their answers. .. _users_and_ports: How do I handle different machines needing different user accounts or ports to log in with? +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Setting inventory variables in the inventory file is the easiest way. For instance, suppose these hosts have different usernames and ports:: [webservers] asdf.example.com ansible_ssh_port=5000 ansible_ssh_user=alice jkl.example.com ansible_ssh_port=5001 ansible_ssh_user=bob You can also dictate the connection type to be used, if you want:: [testcluster] localhost ansible_connection=local /path/to/chroot1 ansible_connection=chroot foo.example.com bar.example.com You may also wish to keep these in group variables instead, or file in them in a group_vars/ file. See the rest of the documentation for more information about how to organize variables. .. _use_ssh: How do I get ansible to reuse connections, enable Kerberized SSH, or have Ansible pay attention to my local SSH config file? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Switch your default connection type in the configuration file to 'ssh', or use '-c ssh' to use Native OpenSSH for connections instead of the python paramiko library. In Ansible 1.2.1 and later, 'ssh' will be used by default if OpenSSH is new enough to support ControlPersist as an option. Paramiko is great for starting out, but the OpenSSH type offers many advanced options. You will want to run Ansible from a machine new enough to support ControlPersist, if you are using this connection type. You can still manage older clients. If you are using RHEL 6, CentOS 6, SLES 10 or SLES 11 the version of OpenSSH is still a bit old, so consider managing from a Fedora or openSUSE client even though you are managing older nodes, or just use paramiko. We keep paramiko as the default as if you are first installing Ansible on an EL box, it offers a better experience for new users. .. _ec2_cloud_performance: How do I speed up management inside EC2? ++++++++++++++++++++++++++++++++++++++++ Don't try to manage a fleet of EC2 machines from your laptop. Connect to a management node inside EC2 first and run Ansible from there. .. _python_interpreters: How do I handle python pathing not having a Python 2.X in /usr/bin/python on a remote machine? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ While you can write ansible modules in any language, most ansible modules are written in Python, and some of these are important core ones. By default Ansible assumes it can find a /usr/bin/python on your remote system that is a 2.X version of Python, specifically 2.4 or higher. Setting of an inventory variable 'ansible_python_interpreter' on any host will allow Ansible to auto-replace the interpreter used when executing python modules. Thus, you can point to any python you want on the system if /usr/bin/python on your system does not point to a Python 2.X interpreter. Some Linux operating systems, such as Arch, may only have Python 3 installed by default. This is not sufficient and you will get syntax errors trying to run modules with Python 3. Python 3 is essentially not the same language as Python 2. Ansible modules currently need to support older Pythons for users that still have Enterprise Linux 5 deployed, so they are not yet ported to run under Python 3.0. This is not a problem though as you can just install Python 2 also on a managed host. Python 3.0 support will likely be addressed at a later point in time when usage becomes more mainstream. Do not replace the shebang lines of your python modules. Ansible will do this for you automatically at deploy time. .. _use_roles: What is the best way to make content reusable/redistributable? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ If you have not done so already, read all about "Roles" in the playbooks documentation. This helps you make playbook content self-contained, and works well with things like git submodules for sharing content with others. If some of these plugin types look strange to you, see the API documentation for more details about ways Ansible can be extended. .. _configuration_file: Where does the configuration file live and what can I configure in it? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ See :doc:`intro_configuration`. .. _who_would_ever_want_to_disable_cowsay_but_ok_here_is_how: How do I disable cowsay? ++++++++++++++++++++++++ If cowsay is installed, Ansible takes it upon itself to make your day happier when running playbooks. If you decide that you would like to work in a professional cow-free environment, you can either uninstall cowsay, or set an environment variable:: export ANSIBLE_NOCOWS=1 .. _browse_facts: How do I see a list of all of the ansible\_ variables? ++++++++++++++++++++++++++++++++++++++++++++++++++++++ Ansible by default gathers "facts" about the machines under management, and these facts can be accessed in Playbooks and in templates. To see a list of all of the facts that are available about a machine, you can run the "setup" module as an ad-hoc action:: ansible -m setup hostname This will print out a dictionary of all of the facts that are available for that particular host. .. _host_loops: How do I loop over a list of hosts in a group, inside of a template? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ A pretty common pattern is to iterate over a list of hosts inside of a host group, perhaps to populate a template configuration file with a list of servers. To do this, you can just access the "$groups" dictionary in your template, like this:: {% for host in groups['db_servers'] %} {{ host }} {% endfor %} If you need to access facts about these hosts, for instance, the IP address of each hostname, you need to make sure that the facts have been populated. For example, make sure you have a play that talks to db_servers:: - hosts: db_servers tasks: - # doesn't matter what you do, just that they were talked to previously. Then you can use the facts inside your template, like this:: {% for host in groups['db_servers'] %} {{ hostvars[host]['ansible_eth0']['ipv4']['address'] }} {% endfor %} .. _programatic_access_to_a_variable: How do I access a variable name programmatically? +++++++++++++++++++++++++++++++++++++++++++++++++ An example may come up where we need to get the ipv4 address of an arbitrary interface, where the interface to be used may be supplied via a role parameter or other input. Variable names can be built by adding strings together, like so:: {{ hostvars[inventory_hostname]['ansible_' + which_interface]['ipv4']['address'] }} The trick about going through hostvars is necessary because it's a dictionary of the entire namespace of variables. 'inventory_hostname' is a magic variable that indicates the current host you are looping over in the host loop. .. _first_host_in_a_group: How do I access a variable of the first host in a group? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ What happens if we want the ip address of the first webserver in the webservers group? Well, we can do that too. Note that if we are using dynamic inventory, which host is the 'first' may not be consistent, so you wouldn't want to do this unless your inventory was static and predictable. (If you are using :doc:`tower`, it will use database order, so this isn't a problem even if you are using cloud based inventory scripts). Anyway, here's the trick:: {{ hostvars[groups['webservers'][0]]['ansible_eth0']['ipv4']['address'] }} Notice how we're pulling out the hostname of the first machine of the webservers group. If you are doing this in a template, you could use the Jinja2 '#set' directive to simplify this, or in a playbook, you could also use set_fact: - set_fact: headnode={{ groups[['webservers'][0]] }} - debug: msg={{ hostvars[headnode].ansible_eth0.ipv4.address }} Notice how we interchanged the bracket syntax for dots -- that can be done anywhere. .. _file_recursion: How do I copy files recursively onto a target host? +++++++++++++++++++++++++++++++++++++++++++++++++++ The "copy" module has a recursive parameter, though if you want to do something more efficient for a large number of files, take a look at the "synchronize" module instead, which wraps rsync. See the module index for info on both of these modules. .. _shell_env: How do I access shell environment variables? ++++++++++++++++++++++++++++++++++++++++++++ If you just need to access existing variables, use the 'env' lookup plugin. For example, to access the value of the HOME environment variable on management machine:: --- # ... vars: local_home: "{{ lookup('env','HOME') }}" If you need to set environment variables, see the Advanced Playbooks section about environments. Ansible 1.4 will also make remote environment variables available via facts in the 'ansible_env' variable:: {{ ansible_env.SOME_VARIABLE }} .. _user_passwords: How do I generate crypted passwords for the user module? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The mkpasswd utility that is available on most Linux systems is a great option:: mkpasswd --method=SHA-512 If this utility is not installed on your system (e.g. you are using OS X) then you can still easily generate these passwords using Python. First, ensure that the `Passlib `_ password hashing library is installed. pip install passlib Once the library is ready, SHA512 password values can then be generated as follows:: python -c "from passlib.hash import sha512_crypt; print sha512_crypt.encrypt('')" .. _commercial_support: Can I get training on Ansible or find commercial support? +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Yes! See `our Guru offering `_ for online support, and support is also included with :doc:`tower`. You can also read our `service page `_ and email `info@ansible.com `_ for further details. .. _web_interface: Is there a web interface / REST API / etc? ++++++++++++++++++++++++++++++++++++++++++ Yes! Ansible, Inc makes a great product that makes Ansible even more powerful and easy to use. See :doc:`tower`. .. _docs_contributions: How do I submit a change to the documentation? ++++++++++++++++++++++++++++++++++++++++++++++ Great question! Documentation for Ansible is kept in the main project git repository, and complete instructions for contributing can be found in the docs README `viewable on GitHub `_. Thanks! .. _keep_secret_data: How do I keep secret data in my playbook? +++++++++++++++++++++++++++++++++++++++++ If you would like to keep secret data in your Ansible content and still share it publicly or keep things in source control, see :doc:`playbooks_vault`. .. _i_dont_see_my_question: I don't see my question here ++++++++++++++++++++++++++++ Please see the section below for a link to IRC and the Google Group, where you can ask your question there. .. seealso:: :doc:`index` The documentation index :doc:`playbooks` An introduction to playbooks :doc:`playbooks_best_practices` Best practices advice `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/galaxy.rst000066400000000000000000000006711241061774000174250ustar00rootroot00000000000000Ansible Galaxy `````````````` `Ansible Galaxy `_, is a free site for finding, downloading, rating, and reviewing all kinds of community developed Ansible roles and can be a great way to get a jumpstart on your automation projects. You can sign up with social auth, and the download client 'ansible-galaxy' is included in Ansible 1.4.2 and later. Read the "About" page on the Galaxy site for more information. ansible-1.7.2/docsite/rst/glossary.rst000066400000000000000000000554741241061774000200160ustar00rootroot00000000000000Glossary ======== The following is a list (and re-explanation) of term definitions used elsewhere in the Ansible documentation. Consult the documentation home page for the full documentation and to see the terms in context, but this should be a good resource to check your knowledge of Ansible's components and understand how they fit together. It's something you might wish to read for review or when a term comes up on the mailing list. Action ++++++ An action is a part of a task that specifies which of the modules to run and the arguments to pass to that module. Each task can have only one action, but it may also have other parameters. Ad Hoc ++++++ Refers to running Ansible to perform some quick command, using /usr/bin/ansible, rather than the orchestration language, which is /usr/bin/ansible-playbook. An example of an ad-hoc command might be rebooting 50 machines in your infrastructure. Anything you can do ad-hoc can be accomplished by writing a playbook, and playbooks can also glue lots of other operations together. Async +++++ Refers to a task that is configured to run in the background rather than waiting for completion. If you have a long process that would run longer than the SSH timeout, it would make sense to launch that task in async mode. Async modes can poll for completion every so many seconds, or can be configured to "fire and forget" in which case Ansible will not even check on the task again, it will just kick it off and proceed to future steps. Async modes work with both /usr/bin/ansible and /usr/bin/ansible-playbook. Callback Plugin +++++++++++++++ Refers to some user-written code that can intercept results from Ansible and do something with them. Some supplied examples in the GitHub project perform custom logging, send email, or even play sound effects. Check Mode ++++++++++ Refers to running Ansible with the ``--check`` option, which does not make any changes on the remote systems, but only outputs the changes that might occur if the command ran without this flag. This is analogous to so-called "dry run" modes in other systems, though the user should be warned that this does not take into account unexpected command failures or cascade effects (which is true of similar modes in other systems). Use this to get an idea of what might happen, but it is not a substitute for a good staging environment. Connection Type, Connection Plugin ++++++++++++++++++++++++++++++++++ By default, Ansible talks to remote machines through pluggable libraries. Ansible supports native OpenSSH ('ssh'), or a Python implementation called 'paramiko'. OpenSSH is preferred if you are using a recent version, and also enables some features like Kerberos and jump hosts. This is covered in the getting started section. There are also other connection types like 'accelerate' mode, which must be bootstrapped over one of the SSH-based connection types but is very fast, and local mode, which acts on the local system. Users can also write their own connection plugins. Conditionals ++++++++++++ A conditional is an expression that evaluates to true or false that decides whether a given task will be executed on a given machine or not. Ansible's conditionals are powered by the 'when' statement, and are discussed in the playbook documentation. Diff Mode +++++++++ A ``--diff`` flag can be passed to Ansible to show how template files change when they are overwritten, or how they might change when used with ``--check`` mode. These diffs come out in unified diff format. Facts +++++ Facts are simply things that are discovered about remote nodes. While they can be used in playbooks and templates just like variables, facts are things that are inferred, rather than set. Facts are automatically discovered by Ansible when running plays by executing the internal 'setup' module on the remote nodes. You never have to call the setup module explicitly, it just runs, but it can be disabled to save time if it is not needed. For the convenience of users who are switching from other configuration management systems, the fact module will also pull in facts from the 'ohai' and 'facter' tools if they are installed, which are fact libraries from Chef and Puppet, respectively. Filter Plugin +++++++++++++ A filter plugin is something that most users will never need to understand. These allow for the creation of new Jinja2 filters, which are more or less only of use to people who know what Jinja2 filters are. If you need them, you can learn how to write them in the API docs section. Forks +++++ Ansible talks to remote nodes in parallel and the level of parallelism can be set either by passing ``--forks``, or editing the default in a configuration file. The default is a very conservative 5 forks, though if you have a lot of RAM, you can easily set this to a value like 50 for increased parallelism. Gather Facts (Boolean) ++++++++++++++++++++++ Facts are mentioned above. Sometimes when running a multi-play playbook, it is desirable to have some plays that don't bother with fact computation if they aren't going to need to utilize any of these values. Setting `gather_facts: False` on a playbook allows this implicit fact gathering to be skipped. Globbing ++++++++ Globbing is a way to select lots of hosts based on wildcards, rather than the name of the host specifically, or the name of the group they are in. For instance, it is possible to select "www*" to match all hosts starting with "www". This concept is pulled directly from Func, one of Michael's earlier projects. In addition to basic globbing, various set operations are also possible, such as 'hosts in this group and not in another group', and so on. Group +++++ A group consists of several hosts assigned to a pool that can be conveniently targeted together, and also given variables that they share in common. Group Vars ++++++++++ The "group_vars/" files are files that live in a directory alongside an inventory file, with an optional filename named after each group. This is a convenient place to put variables that will be provided to a given group, especially complex data structures, so that these variables do not have to be embedded in the inventory file or playbook. Handlers ++++++++ Handlers are just like regular tasks in an Ansible playbook (see Tasks), but are only run if the Task contains a "notify" directive and also indicates that it changed something. For example, if a config file is changed then the task referencing the config file templating operation may notify a service restart handler. This means services can be bounced only if they need to be restarted. Handlers can be used for things other than service restarts, but service restarts are the most common usage. Host ++++ A host is simply a remote machine that Ansible manages. They can have individual variables assigned to them, and can also be organized in groups. All hosts have a name they can be reached at (which is either an IP address or a domain name) and optionally a port number if they are not to be accessed on the default SSH port. Host Specifier ++++++++++++++ Each Play in Ansible maps a series of tasks (which define the role, purpose, or orders of a system) to a set of systems. This "hosts:" directive in each play is often called the hosts specifier. It may select one system, many systems, one or more groups, or even some hosts that are in one group and explicitly not in another. Host Vars +++++++++ Just like "Group Vars", a directory alongside the inventory file named "host_vars/" can contain a file named after each hostname in the inventory file, in YAML format. This provides a convenient place to assign variables to the host without having to embed them in the inventory file. The Host Vars file can also be used to define complex data structures that can't be represented in the inventory file. Lazy Evaluation +++++++++++++++ In general, Ansible evaluates any variables in playbook content at the last possible second, which means that if you define a data structure that data structure itself can define variable values within it, and everything "just works" as you would expect. This also means variable strings can include other variables inside of those strings. Lookup Plugin +++++++++++++ A lookup plugin is a way to get data into Ansible from the outside world. These are how such things as "with_items", a basic looping plugin, are implemented, but there are also lookup plugins like "with_file" which loads data from a file, and even ones for querying environment variables, DNS text records, or key value stores. Lookup plugins can also be accessed in templates, e.g., ``{{ lookup('file','/path/to/file') }}``. Multi-Tier ++++++++++ The concept that IT systems are not managed one system at a time, but by interactions between multiple systems, and groups of systems, in well defined orders. For instance, a web server may need to be updated before a database server, and pieces on the web server may need to be updated after *THAT* database server, and various load balancers and monitoring servers may need to be contacted. Ansible models entire IT topologies and workflows rather than looking at configuration from a "one system at a time" perspective. Idempotency +++++++++++ The concept that change commands should only be applied when they need to be applied, and that it is better to describe the desired state of a system than the process of how to get to that state. As an analogy, the path from North Carolina in the United States to California involves driving a very long way West, but if I were instead in Anchorage, Alaska, driving a long way west is no longer the right way to get to California. Ansible's Resources like you to say "put me in California" and then decide how to get there. If you were already in California, nothing needs to happen, and it will let you know it didn't need to change anything. Includes ++++++++ The idea that playbook files (which are nothing more than lists of plays) can include other lists of plays, and task lists can externalize lists of tasks in other files, and similarly with handlers. Includes can be parameterized, which means that the loaded file can pass variables. For instance, an included play for setting up a WordPress blog may take a parameter called "user" and that play could be included more than once to create a blog for both "alice" and "bob". Inventory +++++++++ A file (by default, Ansible uses a simple INI format) that describes Hosts and Groups in Ansible. Inventory can also be provided via an "Inventory Script" (sometimes called an "External Inventory Script"). Inventory Script ++++++++++++++++ A very simple program (or a complicated one) that looks up hosts, group membership for hosts, and variable information from an external resource -- whether that be a SQL database, a CMDB solution, or something like LDAP. This concept was adapted from Puppet (where it is called an "External Nodes Classifier") and works more or less exactly the same way. Jinja2 ++++++ Jinja2 is the preferred templating language of Ansible's template module. It is a very simple Python template language that is generally readable and easy to write. JSON ++++ Ansible uses JSON for return data from remote modules. This allows modules to be written in any language, not just Python. Library +++++++ A collection of modules made available to /usr/bin/ansible or an Ansible playbook. Limit Groups ++++++++++++ By passing ``--limit somegroup`` to ansible or ansible-playbook, the commands can be limited to a subset of hosts. For instance, this can be used to run a playbook that normally targets an entire set of servers to one particular server. Local Connection ++++++++++++++++ By using "connection: local" in a playbook, or passing "-c local" to /usr/bin/ansible, this indicates that we are managing the local host and not a remote machine. Local Action ++++++++++++ A local_action directive in a playbook targeting remote machines means that the given step will actually occur on the local machine, but that the variable '{{ ansible_hostname }}' can be passed in to reference the remote hostname being referred to in that step. This can be used to trigger, for example, an rsync operation. Loops +++++ Generally, Ansible is not a programming language. It prefers to be more declarative, though various constructs like "with_items" allow a particular task to be repeated for multiple items in a list. Certain modules, like yum and apt, are actually optimized for this, and can install all packages given in those lists within a single transaction, dramatically speeding up total time to configuration. Modules +++++++ Modules are the units of work that Ansible ships out to remote machines. Modules are kicked off by either /usr/bin/ansible or /usr/bin/ansible-playbook (where multiple tasks use lots of different modules in conjunction). Modules can be implemented in any language, including Perl, Bash, or Ruby -- but can leverage some useful communal library code if written in Python. Modules just have to return JSON or simple key=value pairs. Once modules are executed on remote machines, they are removed, so no long running daemons are used. Ansible refers to the collection of available modules as a 'library'. Notify ++++++ The act of a task registering a change event and informing a handler task that another action needs to be run at the end of the play. If a handler is notified by multiple tasks, it will still be run only once. Handlers are run in the order they are listed, not in the order that they are notified. Orchestration +++++++++++++ Many software automation systems use this word to mean different things. Ansible uses it as a conductor would conduct an orchestra. A datacenter or cloud architecture is full of many systems, playing many parts -- web servers, database servers, maybe load balancers, monitoring systems, continuous integration systems, etc. In performing any process, it is necessary to touch systems in particular orders, often to simulate rolling updates or to deploy software correctly. Some system may perform some steps, then others, then previous systems already processed may need to perform more steps. Along the way, emails may need to be sent or web services contacted. Ansible orchestration is all about modeling that kind of process. paramiko ++++++++ By default, Ansible manages machines over SSH. The library that Ansible uses by default to do this is a Python-powered library called paramiko. The paramiko library is generally fast and easy to manage, though users desiring Kerberos or Jump Host support may wish to switch to a native SSH binary such as OpenSSH by specifying the connection type in their playbook, or using the "-c ssh" flag. Playbooks +++++++++ Playbooks are the language by which Ansible orchestrates, configures, administers, or deploys systems. They are called playbooks partially because it's a sports analogy, and it's supposed to be fun using them. They aren't workbooks :) Plays +++++ A playbook is a list of plays. A play is minimally a mapping between a set of hosts selected by a host specifier (usually chosen by groups, but sometimes by hostname globs) and the tasks which run on those hosts to define the role that those systems will perform. There can be one or many plays in a playbook. Pull Mode +++++++++ By default, Ansible runs in push mode, which allows it very fine-grained control over when it talks to each system. Pull mode is provided for when you would rather have nodes check in every N minutes on a particular schedule. It uses a program called ansible-pull and can also be set up (or reconfigured) using a push-mode playbook. Most Ansible users use push mode, but pull mode is included for variety and the sake of having choices. ansible-pull works by checking configuration orders out of git on a crontab and then managing the machine locally, using the local connection plugin. Push Mode +++++++++ Push mode is the default mode of Ansible. In fact, it's not really a mode at all -- it's just how Ansible works when you aren't thinking about it. Push mode allows Ansible to be fine-grained and conduct nodes through complex orchestration processes without waiting for them to check in. Register Variable +++++++++++++++++ The result of running any task in Ansible can be stored in a variable for use in a template or a conditional statement. The keyword used to define the variable is called 'register', taking its name from the idea of registers in assembly programming (though Ansible will never feel like assembly programming). There are an infinite number of variable names you can use for registration. Resource Model ++++++++++++++ Ansible modules work in terms of resources. For instance, the file module will select a particular file and ensure that the attributes of that resource match a particular model. As an example, we might wish to change the owner of /etc/motd to 'root' if it is not already set to root, or set its mode to '0644' if it is not already set to '0644'. The resource models are 'idempotent' meaning change commands are not run unless needed, and Ansible will bring the system back to a desired state regardless of the actual state -- rather than you having to tell it how to get to the state. Roles +++++ Roles are units of organization in Ansible. Assigning a role to a group of hosts (or a set of groups, or host patterns, etc.) implies that they should implement a specific behavior. A role may include applying certain variable values, certain tasks, and certain handlers -- or just one or more of these things. Because of the file structure associated with a role, roles become redistributable units that allow you to share behavior among playbooks -- or even with other users. Rolling Update ++++++++++++++ The act of addressing a number of nodes in a group N at a time to avoid updating them all at once and bringing the system offline. For instance, in a web topology of 500 nodes handling very large volume, it may be reasonable to update 10 or 20 machines at a time, moving on to the next 10 or 20 when done. The "serial:" keyword in an Ansible playbook controls the size of the rolling update pool. The default is to address the batch size all at once, so this is something that you must opt-in to. OS configuration (such as making sure config files are correct) does not typically have to use the rolling update model, but can do so if desired. Runner ++++++ A core software component of Ansible that is the power behind /usr/bin/ansible directly -- and corresponds to the invocation of each task in a playbook. The Runner is something Ansible developers may talk about, but it's not really user land vocabulary. Serial ++++++ See "Rolling Update". Sudo ++++ Ansible does not require root logins, and since it's daemonless, definitely does not require root level daemons (which can be a security concern in sensitive environments). Ansible can log in and perform many operations wrapped in a sudo command, and can work with both password-less and password-based sudo. Some operations that don't normally work with sudo (like scp file transfer) can be achieved with Ansible's copy, template, and fetch modules while running in sudo mode. SSH (Native) ++++++++++++ Native OpenSSH as an Ansible transport is specified with "-c ssh" (or a config file, or a directive in the playbook) and can be useful if wanting to login via Kerberized SSH or using SSH jump hosts, etc. In 1.2.1, 'ssh' will be used by default if the OpenSSH binary on the control machine is sufficiently new. Previously, Ansible selected 'paramiko' as a default. Using a client that supports ControlMaster and ControlPersist is recommended for maximum performance -- if you don't have that and don't need Kerberos, jump hosts, or other features, paramiko is a good choice. Ansible will warn you if it doesn't detect ControlMaster/ControlPersist capability. Tags ++++ Ansible allows tagging resources in a playbook with arbitrary keywords, and then running only the parts of the playbook that correspond to those keywords. For instance, it is possible to have an entire OS configuration, and have certain steps labeled "ntp", and then run just the "ntp" steps to reconfigure the time server information on a remote host. Tasks +++++ Playbooks exist to run tasks. Tasks combine an action (a module and its arguments) with a name and optionally some other keywords (like looping directives). Handlers are also tasks, but they are a special kind of task that do not run unless they are notified by name when a task reports an underlying change on a remote system. Templates +++++++++ Ansible can easily transfer files to remote systems, but often it is desirable to substitute variables in other files. Variables may come from the inventory file, Host Vars, Group Vars, or Facts. Templates use the Jinja2 template engine and can also include logical constructs like loops and if statements. Transport +++++++++ Ansible uses "Connection Plugins" to define types of available transports. These are simply how Ansible will reach out to managed systems. Transports included are paramiko, SSH (using OpenSSH), and local. When ++++ An optional conditional statement attached to a task that is used to determine if the task should run or not. If the expression following the "when:" keyword evaluates to false, the task will be ignored. Van Halen +++++++++ For no particular reason, other than the fact that Michael really likes them, all Ansible releases are codenamed after Van Halen songs. There is no preference given to David Lee Roth vs. Sammy Lee Hagar-era songs, and instrumentals are also allowed. It is unlikely that there will ever be a Jump release, but a Van Halen III codename release is possible. You never know. Vars (Variables) ++++++++++++++++ As opposed to Facts, variables are names of values (they can be simple scalar values -- integers, booleans, strings) or complex ones (dictionaries/hashes, lists) that can be used in templates and playbooks. They are declared things, not things that are inferred from the remote system's current state or nature (which is what Facts are). YAML ++++ Ansible does not want to force people to write programming language code to automate infrastructure, so Ansible uses YAML to define playbook configuration languages and also variable files. YAML is nice because it has a minimum of syntax and is very clean and easy for people to skim. It is a good data format for configuration files and humans, but also machine readable. Ansible's usage of YAML stemmed from Michael's first use of it inside of Cobbler around 2006. YAML is fairly popular in the dynamic language community and the format has libraries available for serialization in many languages (Python, Perl, Ruby, etc.). .. seealso:: :doc:`faq` Frequently asked questions :doc:`playbooks` An introduction to playbooks :doc:`playbooks_best_practices` Best practices advice `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/guide_aws.rst000066400000000000000000000317731241061774000201160ustar00rootroot00000000000000Amazon Web Services Guide ========================= .. _aws_intro: Introduction ```````````` .. note:: This section of the documentation is under construction. We are in the process of adding more examples about all of the EC2 modules and how they work together. There's also an ec2 example in the language_features directory of `the ansible-examples github repository `_ that you may wish to consult. Once complete, there will also be new examples of ec2 in ansible-examples. Ansible contains a number of core modules for interacting with Amazon Web Services (AWS). These also work with Eucalyptus, which is an AWS compatible private cloud solution. There are other supported cloud types, but this documentation chapter is about AWS API clouds. The purpose of this section is to explain how to put Ansible modules together (and use inventory scripts) to use Ansible in AWS context. Requirements for the AWS modules are minimal. All of the modules require and are tested against boto 2.5 or higher. You'll need this Python module installed on the execution host. If you are using Red Hat Enterprise Linux or CentOS, install boto from `EPEL `_: .. code-block:: bash $ yum install python-boto You can also install it via pip if you want. The following steps will often execute outside the host loop, so it makes sense to add localhost to inventory. Ansible may not require this step in the future:: [local] localhost And in your playbook steps we'll typically be using the following pattern for provisioning steps:: - hosts: localhost connection: local gather_facts: False .. _aws_provisioning: Provisioning ```````````` The ec2 module provides the ability to provision instances within EC2. Typically the provisioning task will be performed against your Ansible master server in a play that operates on localhost using the ``local`` connection type. If you are doing an EC2 operation mid-stream inside a regular play operating on remote hosts, you may want to use the ``local_action`` keyword for that particular task. Read :doc:`playbooks_delegation` for more about local actions. .. note:: Authentication with the AWS-related modules is handled by either specifying your access and secret key as ENV variables or passing them as module arguments. .. note:: To talk to specific endpoints, the environmental variable EC2_URL can be set. This is useful if using a private cloud like Eucalyptus, exporting the variable as EC2_URL=https://myhost:8773/services/Eucalyptus. This can be set using the 'environment' keyword in Ansible if you like. Here is an example of provisioning a number of instances in ad-hoc mode: .. code-block:: bash # ansible localhost -m ec2 -a "image=ami-6e649707 instance_type=m1.large keypair=mykey group=webservers wait=yes" -c local In a play, this might look like (assuming the parameters are held as vars):: tasks: - name: Provision a set of instances ec2: > keypair={{mykeypair}} group={{security_group}} instance_type={{instance_type}} image={{image}} wait=true count={{number}} register: ec2 By registering the return its then possible to dynamically create a host group consisting of these new instances. This facilitates performing configuration actions on the hosts immediately in a subsequent task:: - name: Add all instance public IPs to host group add_host: hostname={{ item.public_ip }} groupname=ec2hosts with_items: ec2.instances With the host group now created, a second play in your provision playbook might now have some configuration steps:: - name: Configuration play hosts: ec2hosts user: ec2-user gather_facts: true tasks: - name: Check NTP service service: name=ntpd state=started Rather than include configuration inline, you may also choose to just do it as a task include or a role. The method above ties the configuration of a host with the provisioning step. This isn't always ideal and leads us onto the next section. .. _aws_advanced: Advanced Usage `````````````` .. _aws_host_inventory: Host Inventory ++++++++++++++ Once your nodes are spun up, you'll probably want to talk to them again. The best way to handle this is to use the ec2 inventory plugin. Even for larger environments, you might have nodes spun up from Cloud Formations or other tooling. You don't have to use Ansible to spin up guests. Once these are created and you wish to configure them, the EC2 API can be used to return system grouping with the help of the EC2 inventory script. This script can be used to group resources by their security group or tags. Tagging is highly recommended in EC2 and can provide an easy way to sort between host groups and roles. The inventory script is documented doc:`api` section. You may wish to schedule a regular refresh of the inventory cache to accommodate for frequent changes in resources: .. code-block:: bash # ./ec2.py --refresh-cache Put this into a crontab as appropriate to make calls from your Ansible master server to the EC2 API endpoints and gather host information. The aim is to keep the view of hosts as up-to-date as possible, so schedule accordingly. Playbook calls could then also be scheduled to act on the refreshed hosts inventory after each refresh. This approach means that machine images can remain "raw", containing no payload and OS-only. Configuration of the workload is handled entirely by Ansible. Tags ++++ There's a feature in the ec2 inventory script where hosts tagged with certain keys and values automatically appear in certain groups. For instance, if a host is given the "class" tag with the value of "webserver", it will be automatically discoverable via a dynamic group like so:: - hosts: tag_class_webserver tasks: - ping Using this philosophy can be a great way to manage groups dynamically, without having to maintain separate inventory. .. _aws_pull: Pull Configuration ++++++++++++++++++ For some the delay between refreshing host information and acting on that host information (i.e. running Ansible tasks against the hosts) may be too long. This may be the case in such scenarios where EC2 AutoScaling is being used to scale the number of instances as a result of a particular event. Such an event may require that hosts come online and are configured as soon as possible (even a 1 minute delay may be undesirable). Its possible to pre-bake machine images which contain the necessary ansible-pull script and components to pull and run a playbook via git. The machine images could be configured to run ansible-pull upon boot as part of the bootstrapping procedure. Read :ref:`ansible-pull` for more information on pull-mode playbooks. (Various developments around Ansible are also going to make this easier in the near future. Stay tuned!) .. _aws_autoscale: Autoscaling with Ansible Tower ++++++++++++++++++++++++++++++ :doc:`tower` also contains a very nice feature for auto-scaling use cases. In this mode, a simple curl script can call a defined URL and the server will "dial out" to the requester and configure an instance that is spinning up. This can be a great way to reconfigure ephemeral nodes. See the Tower documentation for more details. Click on the Tower link in the sidebar for details. A benefit of using the callback in Tower over pull mode is that job results are still centrally recorded and less information has to be shared with remote hosts. .. _aws_use_cases: Use Cases ````````` This section covers some usage examples built around a specific use case. .. _aws_cloudformation_example: Example 1 +++++++++ Example 1: I'm using CloudFormation to deploy a specific infrastructure stack. I'd like to manage configuration of the instances with Ansible. Provision instances with your tool of choice and consider using the inventory plugin to group hosts based on particular tags or security group. Consider tagging instances you wish to managed with Ansible with a suitably unique key=value tag. .. note:: Ansible also has a cloudformation module you may wish to explore. .. _aws_autoscale_example: Example 2 +++++++++ Example 2: I'm using AutoScaling to dynamically scale up and scale down the number of instances. This means the number of hosts is constantly fluctuating but I'm letting EC2 automatically handle the provisioning of these instances. I don't want to fully bake a machine image, I'd like to use Ansible to configure the hosts. There are several approaches to this use case. The first is to use the inventory plugin to regularly refresh host information and then target hosts based on the latest inventory data. The second is to use ansible-pull triggered by a user-data script (specified in the launch configuration) which would then mean that each instance would fetch Ansible and the latest playbook from a git repository and run locally to configure itself. You could also use the Tower callback feature. .. _aws_builds: Example 3 +++++++++ Example 3: I don't want to use Ansible to manage my instances but I'd like to consider using Ansible to build my fully-baked machine images. There's nothing to stop you doing this. If you like working with Ansible's playbook format then writing a playbook to create an image; create an image file with dd, give it a filesystem and then install packages and finally chroot into it for further configuration. Ansible has the 'chroot' plugin for this purpose, just add the following to your inventory file:: /chroot/path ansible_connection=chroot And in your playbook:: hosts: /chroot/path Example 4 +++++++++ How would I create a new ec2 instance, provision it and then destroy it all in the same play? .. code-block:: yaml # Use the ec2 module to create a new host and then add # it to a special "ec2hosts" group. - hosts: localhost connection: local gather_facts: False vars: ec2_access_key: "--REMOVED--" ec2_secret_key: "--REMOVED--" keypair: "mykeyname" instance_type: "t1.micro" image: "ami-d03ea1e0" group: "mysecuritygroup" region: "us-west-2" zone: "us-west-2c" tasks: - name: make one instance ec2: image={{ image }} instance_type={{ instance_type }} aws_access_key={{ ec2_access_key }} aws_secret_key={{ ec2_secret_key }} keypair={{ keypair }} instance_tags='{"foo":"bar"}' region={{ region }} group={{ group }} wait=true register: ec2_info - debug: var=ec2_info - debug: var=item with_items: ec2_info.instance_ids - add_host: hostname={{ item.public_ip }} groupname=ec2hosts with_items: ec2_info.instances - name: wait for instances to listen on port:22 wait_for: state=started host={{ item.public_dns_name }} port=22 with_items: ec2_info.instances # Connect to the node and gather facts, # including the instance-id. These facts # are added to inventory hostvars for the # duration of the playbook's execution # Typical "provisioning" tasks would go in # this playbook. - hosts: ec2hosts gather_facts: True user: ec2-user sudo: True tasks: # fetch instance data from the metadata servers in ec2 - ec2_facts: # show all known facts for this host - debug: var=hostvars[inventory_hostname] # just show the instance-id - debug: msg="{{ hostvars[inventory_hostname]['ansible_ec2_instance_id'] }}" # Using the instanceid, call the ec2 module # locally to remove the instance by declaring # it's state is "absent" - hosts: ec2hosts gather_facts: True connection: local vars: ec2_access_key: "--REMOVED--" ec2_secret_key: "--REMOVED--" region: "us-west-2" tasks: - name: destroy all instances ec2: state='absent' aws_access_key={{ ec2_access_key }} aws_secret_key={{ ec2_secret_key }} region={{ region }} instance_ids={{ item }} wait=true with_items: hostvars[inventory_hostname]['ansible_ec2_instance_id'] .. note:: more examples of this are pending. You may also be interested in the ec2_ami module for taking AMIs of running instances. .. _aws_pending: Pending Information ``````````````````` In the future look here for more topics. .. seealso:: :doc:`modules` All the documentation for Ansible modules :doc:`playbooks` An introduction to playbooks :doc:`playbooks_delegation` Delegation, useful for working with loud balancers, clouds, and locally executed steps. `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/guide_gce.rst000066400000000000000000000216651241061774000200610ustar00rootroot00000000000000Google Cloud Platform Guide =========================== .. gce_intro: Introduction ------------ .. note:: This section of the documentation is under construction. We are in the process of adding more examples about all of the GCE modules and how they work together. Upgrades via github pull requests are welcomed! Ansible contains modules for managing Google Compute Engine resources, including creating instances, controlling network access, working with persistent disks, and managing load balancers. Additionally, there is an inventory plugin that can automatically suck down all of your GCE instances into Ansible dynamic inventory, and create groups by tag and other properties. The GCE modules all require the apache-libcloud module, which you can install from pip: .. code-block:: bash $ pip install apache-libcloud .. note:: If you're using Ansible on Mac OS X, libcloud also needs to access a CA cert chain. You'll need to download one (you can get one for `here `_.) Credentials ----------- To work with the GCE modules, you'll first need to get some credentials. You can create new one from the `console `_ by going to the "APIs and Auth" section. Once you've created a new client ID and downloaded the generated private key (in the `pkcs12 format `_), you'll need to convert the key by running the following command: .. code-block:: bash $ openssl pkcs12 -in pkey.pkcs12 -passin pass:notasecret -nodes -nocerts | openssl rsa -out pkey.pem There are two different ways to provide credentials to Ansible so that it can talk with Google Cloud for provisioning and configuration actions: * by providing to the modules directly * by populating a ``secrets.py`` file Calling Modules By Passing Credentials `````````````````````````````````````` For the GCE modules you can specify the credentials as arguments: * ``service_account_email``: email associated with the project * ``pem_file``: path to the pem file * ``project_id``: id of the project For example, to create a new instance using the cloud module, you can use the following configuration: .. code-block:: yaml - name: Create instance(s) hosts: localhost connection: local gather_facts: no vars: service_account_email: unique-id@developer.gserviceaccount.com pem_file: /path/to/project.pem project_id: project-id machine_type: n1-standard-1 image: debian-7 tasks: - name: Launch instances gce: instance_names: dev machine_type: "{{ machine_type }}" image: "{{ image }}" service_account_email: "{{ service_account_email }}" pem_file: "{{ pem_file }}" project_id: "{{ project_id }}" Calling Modules with secrets.py ``````````````````````````````` Create a file ``secrets.py`` looking like following, and put it in some folder which is in your ``$PYTHONPATH``: .. code-block:: python GCE_PARAMS = ('i...@project.googleusercontent.com', '/path/to/project.pem') GCE_KEYWORD_PARAMS = {'project': 'project-name'} Now the modules can be used as above, but the account information can be omitted. GCE Dynamic Inventory --------------------- The best way to interact with your hosts is to use the gce inventory plugin, which dynamically queries GCE and tells Ansible what nodes can be managed. Note that when using the inventory script ``gce.py``, you also need to populate the ``gce.ini`` file that you can find in the plugins/inventory directory of the ansible checkout. To use the GCE dynamic inventory script, copy ``gce.py`` from ``plugins/inventory`` into your inventory directory and make it executable. You can specify credentials for ``gce.py`` using the ``GCE_INI_PATH`` environment variable -- the default is to look for gce.ini in the same directory as the inventory script. Let's see if inventory is working: .. code-block:: bash $ ./gce.py --list You should see output describing the hosts you have, if any, running in Google Compute Engine. Now let's see if we can use the inventory script to talk to Google. .. code-block:: bash $ GCE_INI_PATH=~/.gce.ini ansible all -i gce.py -m setup hostname | success >> { "ansible_facts": { "ansible_all_ipv4_addresses": [ "x.x.x.x" ], As with all dynamic inventory plugins in Ansible, you can configure the inventory path in ansible.cfg. The recommended way to use the inventory is to create an ``inventory`` directory, and place both the ``gce.py`` script and a file containing ``localhost`` in it. This can allow for cloud inventory to be used alongside local inventory (such as a physical datacenter) or machines running in different providers. Executing ``ansible`` or ``ansible-playbook`` and specifying the ``inventory`` directory instead of an individual file will cause ansible to evaluate each file in that directory for inventory. Let's once again use our inventory script to see if it can talk to Google Cloud: .. code-block:: bash $ ansible all -i inventory/ -m setup hostname | success >> { "ansible_facts": { "ansible_all_ipv4_addresses": [ "x.x.x.x" ], The output should be similar to the previous command. If you're wanting less output and just want to check for SSH connectivity, use "-m" ping instead. Use Cases --------- For the following use case, let's use this small shell script as a wrapper. .. code-block:: bash #!/bin/bash PLAYBOOK="$1" if [ -z $PLAYBOOK ]; then echo "You need to pass a playback as argument to this script." exit 1 fi export SSL_CERT_FILE=$(pwd)/cacert.cer export ANSIBLE_HOST_KEY_CHECKING=False if [ ! -f "$SSL_CERT_FILE" ]; then curl -O http://curl.haxx.se/ca/cacert.pem fi ansible-playbook -v -i inventory/ "$PLAYBOOK" Create an instance `````````````````` The GCE module provides the ability to provision instances within Google Compute Engine. The provisioning task is typically performed from your Ansible control server against Google Cloud's API. A playbook would looks like this: .. code-block:: yaml - name: Create instance(s) hosts: localhost gather_facts: no connection: local vars: machine_type: n1-standard-1 # default image: debian-7 service_account_email: unique-id@developer.gserviceaccount.com pem_file: /path/to/project.pem project_id: project-id tasks: - name: Launch instances gce: instance_names: dev machine_type: "{{ machine_type }}" image: "{{ image }}" service_account_email: "{{ service_account_email }}" pem_file: "{{ pem_file }}" project_id: "{{ project_id }}" tags: webserver register: gce - name: Wait for SSH to come up wait_for: host={{ item.public_ip }} port=22 delay=10 timeout=60 with_items: gce.instance_data - name: add_host hostname={{ item.public_ip }} groupname=new_instances - name: Manage new instances hosts: new_instances connection: ssh roles: - base_configuration - production_server Note that use of the "add_host" module above creates a temporary, in-memory group. This means that a play in the same playbook can then manage machines in the 'new_instances' group, if so desired. Any sort of arbitrary configuration is possible at this point. Configuring instances in a group ```````````````````````````````` All of the created instances in GCE are grouped by tag. Since this is a cloud, it's probably best to ignore hostnames and just focus on group management. Normally we'd also use roles here, but the following example is a simple one. Here we will also use the "gce_net" module to open up access to port 80 on these nodes. The variables in the 'vars' section could also be kept in a 'vars_files' file or something encrypted with Ansible-vault, if you so choose. This is just a basic example of what is possible:: - name: Setup web servers hosts: tag_webserver gather_facts: no vars: machine_type: n1-standard-1 # default image: debian-7 service_account_email: unique-id@developer.gserviceaccount.com pem_file: /path/to/project.pem project_id: project-id roles: - name: Install lighttpd apt: pkg=lighttpd state=installed sudo: True - name: Allow HTTP local_action: gce_net args: fwname: "all-http" name: "default" allowed: "tcp:80" state: "present" service_account_email: "{{ service_account_email }}" pem_file: "{{ pem_file }}" project_id: "{{ project_id }}" By pointing your browser to the IP of the server, you should see a page welcoming you. Upgrades to this documentation are welcome, hit the github link at the top right of this page if you would like to make additions! ansible-1.7.2/docsite/rst/guide_rax.rst000066400000000000000000000721421241061774000201110ustar00rootroot00000000000000Rackspace Cloud Guide ===================== .. _introduction: Introduction ```````````` .. note:: This section of the documentation is under construction. We are in the process of adding more examples about the Rackspace modules and how they work together. Once complete, there will also be examples for Rackspace Cloud in `ansible-examples `_. Ansible contains a number of core modules for interacting with Rackspace Cloud. The purpose of this section is to explain how to put Ansible modules together (and use inventory scripts) to use Ansible in a Rackspace Cloud context. Prerequisites for using the rax modules are minimal. In addition to ansible itself, all of the modules require and are tested against pyrax 1.5 or higher. You'll need this Python module installed on the execution host. pyrax is not currently available in many operating system package repositories, so you will likely need to install it via pip: .. code-block:: bash $ pip install pyrax The following steps will often execute from the control machine against the Rackspace Cloud API, so it makes sense to add localhost to the inventory file. (Ansible may not require this manual step in the future): .. code-block:: ini [localhost] localhost ansible_connection=local In playbook steps, we'll typically be using the following pattern: .. code-block:: yaml - hosts: localhost connection: local gather_facts: False tasks: .. _credentials_file: Credentials File ```````````````` The `rax.py` inventory script and all `rax` modules support a standard `pyrax` credentials file that looks like: .. code-block:: ini [rackspace_cloud] username = myraxusername api_key = d41d8cd98f00b204e9800998ecf8427e Setting the environment parameter RAX_CREDS_FILE to the path of this file will help Ansible find how to load this information. More information about this credentials file can be found at https://github.com/rackspace/pyrax/blob/master/docs/getting_started.md#authenticating .. _virtual_environment: Running from a Python Virtual Environment (Optional) ++++++++++++++++++++++++++++++++++++++++++++++++++++ Most users will not be using virtualenv, but some users, particularly Python developers sometimes like to. There are special considerations when Ansible is installed to a Python virtualenv, rather than the default of installing at a global scope. Ansible assumes, unless otherwise instructed, that the python binary will live at /usr/bin/python. This is done via the interpreter line in modules, however when instructed by setting the inventory variable 'ansible_python_interpreter', Ansible will use this specified path instead to find Python. This can be a cause of confusion as one may assume that modules running on 'localhost', or perhaps running via 'local_action', are using the virtualenv Python interpreter. By setting this line in the inventory, the modules will execute in the virtualenv interpreter and have available the virtualenv packages, specifically pyrax. If using virtualenv, you may wish to modify your localhost inventory definition to find this location as follows: .. code-block:: ini [localhost] localhost ansible_connection=local ansible_python_interpreter=/path/to/ansible_venv/bin/python .. note:: pyrax may be installed in the global Python package scope or in a virtual environment. There are no special considerations to keep in mind when installing pyrax. .. _provisioning: Provisioning ```````````` Now for the fun parts. The 'rax' module provides the ability to provision instances within Rackspace Cloud. Typically the provisioning task will be performed from your Ansible control server (in our example, localhost) against the Rackspace cloud API. This is done for several reasons: - Avoiding installing the pyrax library on remote nodes - No need to encrypt and distribute credentials to remote nodes - Speed and simplicity .. note:: Authentication with the Rackspace-related modules is handled by either specifying your username and API key as environment variables or passing them as module arguments, or by specifying the location of a credentials file. Here is a basic example of provisioning an instance in ad-hoc mode: .. code-block:: bash $ ansible localhost -m rax -a "name=awx flavor=4 image=ubuntu-1204-lts-precise-pangolin wait=yes" -c local Here's what it would look like in a playbook, assuming the parameters were defined in variables: .. code-block:: yaml tasks: - name: Provision a set of instances local_action: module: rax name: "{{ rax_name }}" flavor: "{{ rax_flavor }}" image: "{{ rax_image }}" count: "{{ rax_count }}" group: "{{ group }}" wait: yes register: rax The rax module returns data about the nodes it creates, like IP addresses, hostnames, and login passwords. By registering the return value of the step, it is possible used this data to dynamically add the resulting hosts to inventory (temporarily, in memory). This facilitates performing configuration actions on the hosts in a follow-on task. In the following example, the servers that were successfully created using the above task are dynamically added to a group called "raxhosts", with each nodes hostname, IP address, and root password being added to the inventory. .. code-block:: yaml - name: Add the instances we created (by public IP) to the group 'raxhosts' local_action: module: add_host hostname: "{{ item.name }}" ansible_ssh_host: "{{ item.rax_accessipv4 }}" ansible_ssh_pass: "{{ item.rax_adminpass }}" groupname: raxhosts with_items: rax.success when: rax.action == 'create' With the host group now created, the next play in this playbook could now configure servers belonging to the raxhosts group. .. code-block:: yaml - name: Configuration play hosts: raxhosts user: root roles: - ntp - webserver The method above ties the configuration of a host with the provisioning step. This isn't always what you want, and leads us to the next section. .. _host_inventory: Host Inventory `````````````` Once your nodes are spun up, you'll probably want to talk to them again. The best way to handle his is to use the "rax" inventory plugin, which dynamically queries Rackspace Cloud and tells Ansible what nodes you have to manage. You might want to use this even if you are spinning up Ansible via other tools, including the Rackspace Cloud user interface. The inventory plugin can be used to group resources by metadata, region, OS, etc. Utilizing metadata is highly recommended in "rax" and can provide an easy way to sort between host groups and roles. If you don't want to use the ``rax.py`` dynamic inventory script, you could also still choose to manually manage your INI inventory file, though this is less recommended. In Ansible it is quite possible to use multiple dynamic inventory plugins along with INI file data. Just put them in a common directory and be sure the scripts are chmod +x, and the INI-based ones are not. .. _raxpy: rax.py ++++++ To use the rackspace dynamic inventory script, copy ``rax.py`` into your inventory directory and make it executable. You can specify a credentails file for ``rax.py`` utilizing the ``RAX_CREDS_FILE`` environment variable. .. note:: Dynamic inventory scripts (like ``rax.py``) are saved in ``/usr/share/ansible/inventory`` if Ansible has been installed globally. If installed to a virtualenv, the inventory scripts are installed to ``$VIRTUALENV/share/inventory``. .. note:: Users of :doc:`tower` will note that dynamic inventory is natively supported by Tower, and all you have to do is associate a group with your Rackspace Cloud credentials, and it will easily synchronize without going through these steps:: $ RAX_CREDS_FILE=~/.raxpub ansible all -i rax.py -m setup ``rax.py`` also accepts a ``RAX_REGION`` environment variable, which can contain an individual region, or a comma separated list of regions. When using ``rax.py``, you will not have a 'localhost' defined in the inventory. As mentioned previously, you will often be running most of these modules outside of the host loop, and will need 'localhost' defined. The recommended way to do this, would be to create an ``inventory`` directory, and place both the ``rax.py`` script and a file containing ``localhost`` in it. Executing ``ansible`` or ``ansible-playbook`` and specifying the ``inventory`` directory instead of an individual file, will cause ansible to evaluate each file in that directory for inventory. Let's test our inventory script to see if it can talk to Rackspace Cloud. .. code-block:: bash $ RAX_CREDS_FILE=~/.raxpub ansible all -i inventory/ -m setup Assuming things are properly configured, the ``rax.py`` inventory script will output information similar to the following information, which will be utilized for inventory and variables. .. code-block:: json { "ORD": [ "test" ], "_meta": { "hostvars": { "test": { "ansible_ssh_host": "1.1.1.1", "rax_accessipv4": "1.1.1.1", "rax_accessipv6": "2607:f0d0:1002:51::4", "rax_addresses": { "private": [ { "addr": "2.2.2.2", "version": 4 } ], "public": [ { "addr": "1.1.1.1", "version": 4 }, { "addr": "2607:f0d0:1002:51::4", "version": 6 } ] }, "rax_config_drive": "", "rax_created": "2013-11-14T20:48:22Z", "rax_flavor": { "id": "performance1-1", "links": [ { "href": "https://ord.servers.api.rackspacecloud.com/111111/flavors/performance1-1", "rel": "bookmark" } ] }, "rax_hostid": "e7b6961a9bd943ee82b13816426f1563bfda6846aad84d52af45a4904660cde0", "rax_human_id": "test", "rax_id": "099a447b-a644-471f-87b9-a7f580eb0c2a", "rax_image": { "id": "b211c7bf-b5b4-4ede-a8de-a4368750c653", "links": [ { "href": "https://ord.servers.api.rackspacecloud.com/111111/images/b211c7bf-b5b4-4ede-a8de-a4368750c653", "rel": "bookmark" } ] }, "rax_key_name": null, "rax_links": [ { "href": "https://ord.servers.api.rackspacecloud.com/v2/111111/servers/099a447b-a644-471f-87b9-a7f580eb0c2a", "rel": "self" }, { "href": "https://ord.servers.api.rackspacecloud.com/111111/servers/099a447b-a644-471f-87b9-a7f580eb0c2a", "rel": "bookmark" } ], "rax_metadata": { "foo": "bar" }, "rax_name": "test", "rax_name_attr": "name", "rax_networks": { "private": [ "2.2.2.2" ], "public": [ "1.1.1.1", "2607:f0d0:1002:51::4" ] }, "rax_os-dcf_diskconfig": "AUTO", "rax_os-ext-sts_power_state": 1, "rax_os-ext-sts_task_state": null, "rax_os-ext-sts_vm_state": "active", "rax_progress": 100, "rax_status": "ACTIVE", "rax_tenant_id": "111111", "rax_updated": "2013-11-14T20:49:27Z", "rax_user_id": "22222" } } } } .. _standard_inventory: Standard Inventory ++++++++++++++++++ When utilizing a standard ini formatted inventory file (as opposed to the inventory plugin), it may still be adventageous to retrieve discoverable hostvar information from the Rackspace API. This can be achieved with the ``rax_facts`` module and an inventory file similar to the following: .. code-block:: ini [test_servers] hostname1 rax_region=ORD hostname2 rax_region=ORD .. code-block:: yaml - name: Gather info about servers hosts: test_servers gather_facts: False tasks: - name: Get facts about servers local_action: module: rax_facts credentials: ~/.raxpub name: "{{ inventory_hostname }}" region: "{{ rax_region }}" - name: Map some facts set_fact: ansible_ssh_host: "{{ rax_accessipv4 }}" While you don't need to know how it works, it may be interesting to know what kind of variables are returned. The ``rax_facts`` module provides facts as followings, which match the ``rax.py`` inventory script: .. code-block:: json { "ansible_facts": { "rax_accessipv4": "1.1.1.1", "rax_accessipv6": "2607:f0d0:1002:51::4", "rax_addresses": { "private": [ { "addr": "2.2.2.2", "version": 4 } ], "public": [ { "addr": "1.1.1.1", "version": 4 }, { "addr": "2607:f0d0:1002:51::4", "version": 6 } ] }, "rax_config_drive": "", "rax_created": "2013-11-14T20:48:22Z", "rax_flavor": { "id": "performance1-1", "links": [ { "href": "https://ord.servers.api.rackspacecloud.com/111111/flavors/performance1-1", "rel": "bookmark" } ] }, "rax_hostid": "e7b6961a9bd943ee82b13816426f1563bfda6846aad84d52af45a4904660cde0", "rax_human_id": "test", "rax_id": "099a447b-a644-471f-87b9-a7f580eb0c2a", "rax_image": { "id": "b211c7bf-b5b4-4ede-a8de-a4368750c653", "links": [ { "href": "https://ord.servers.api.rackspacecloud.com/111111/images/b211c7bf-b5b4-4ede-a8de-a4368750c653", "rel": "bookmark" } ] }, "rax_key_name": null, "rax_links": [ { "href": "https://ord.servers.api.rackspacecloud.com/v2/111111/servers/099a447b-a644-471f-87b9-a7f580eb0c2a", "rel": "self" }, { "href": "https://ord.servers.api.rackspacecloud.com/111111/servers/099a447b-a644-471f-87b9-a7f580eb0c2a", "rel": "bookmark" } ], "rax_metadata": { "foo": "bar" }, "rax_name": "test", "rax_name_attr": "name", "rax_networks": { "private": [ "2.2.2.2" ], "public": [ "1.1.1.1", "2607:f0d0:1002:51::4" ] }, "rax_os-dcf_diskconfig": "AUTO", "rax_os-ext-sts_power_state": 1, "rax_os-ext-sts_task_state": null, "rax_os-ext-sts_vm_state": "active", "rax_progress": 100, "rax_status": "ACTIVE", "rax_tenant_id": "111111", "rax_updated": "2013-11-14T20:49:27Z", "rax_user_id": "22222" }, "changed": false } Use Cases ````````` This section covers some additional usage examples built around a specific use case. .. _network_and_server: Network and Server ++++++++++++++++++ Create an isolated cloud network and build a server .. code-block:: yaml - name: Build Servers on an Isolated Network hosts: localhost connection: local gather_facts: False tasks: - name: Network create request local_action: module: rax_network credentials: ~/.raxpub label: my-net cidr: 192.168.3.0/24 region: IAD state: present - name: Server create request local_action: module: rax credentials: ~/.raxpub name: web%04d.example.org flavor: 2 image: ubuntu-1204-lts-precise-pangolin disk_config: manual networks: - public - my-net region: IAD state: present count: 5 exact_count: yes group: web wait: yes wait_timeout: 360 register: rax .. _complete_environment: Complete Environment ++++++++++++++++++++ Build a complete webserver environment with servers, custom networks and load balancers, install nginx and create a custom index.html .. code-block:: yaml --- - name: Build environment hosts: localhost connection: local gather_facts: False tasks: - name: Load Balancer create request local_action: module: rax_clb credentials: ~/.raxpub name: my-lb port: 80 protocol: HTTP algorithm: ROUND_ROBIN type: PUBLIC timeout: 30 region: IAD wait: yes state: present meta: app: my-cool-app register: clb - name: Network create request local_action: module: rax_network credentials: ~/.raxpub label: my-net cidr: 192.168.3.0/24 state: present region: IAD register: network - name: Server create request local_action: module: rax credentials: ~/.raxpub name: web%04d.example.org flavor: performance1-1 image: ubuntu-1204-lts-precise-pangolin disk_config: manual networks: - public - private - my-net region: IAD state: present count: 5 exact_count: yes group: web wait: yes register: rax - name: Add servers to web host group local_action: module: add_host hostname: "{{ item.name }}" ansible_ssh_host: "{{ item.rax_accessipv4 }}" ansible_ssh_pass: "{{ item.rax_adminpass }}" ansible_ssh_user: root groupname: web with_items: rax.success when: rax.action == 'create' - name: Add servers to Load balancer local_action: module: rax_clb_nodes credentials: ~/.raxpub load_balancer_id: "{{ clb.balancer.id }}" address: "{{ item.rax_networks.private|first }}" port: 80 condition: enabled type: primary wait: yes region: IAD with_items: rax.success when: rax.action == 'create' - name: Configure servers hosts: web handlers: - name: restart nginx service: name=nginx state=restarted tasks: - name: Install nginx apt: pkg=nginx state=latest update_cache=yes cache_valid_time=86400 notify: - restart nginx - name: Ensure nginx starts on boot service: name=nginx state=started enabled=yes - name: Create custom index.html copy: content="{{ inventory_hostname }}" dest=/usr/share/nginx/www/index.html owner=root group=root mode=0644 .. _rackconnect_and_manged_cloud: RackConnect and Managed Cloud +++++++++++++++++++++++++++++ When using RackConnect version 2 or Rackspace Managed Cloud there are Rackspace automation tasks that are executed on the servers you create after they are successfully built. If your automation executes before the RackConnect or Managed Cloud automation, you can cause failures and un-usable servers. These examples show creating servers, and ensuring that the Rackspace automation has completed before Ansible continues onwards. For simplicity, these examples are joined, however both are only needed when using RackConnect. When only using Managed Cloud, the RackConnect portion can be ignored. The RackConnect portions only apply to RackConnect version 2. .. _using_a_control_machine: Using a Control Machine *********************** .. code-block:: yaml - name: Create an exact count of servers hosts: localhost connection: local gather_facts: False tasks: - name: Server build requests local_action: module: rax credentials: ~/.raxpub name: web%03d.example.org flavor: performance1-1 image: ubuntu-1204-lts-precise-pangolin disk_config: manual region: DFW state: present count: 1 exact_count: yes group: web wait: yes register: rax - name: Add servers to in memory groups local_action: module: add_host hostname: "{{ item.name }}" ansible_ssh_host: "{{ item.rax_accessipv4 }}" ansible_ssh_pass: "{{ item.rax_adminpass }}" ansible_ssh_user: root rax_id: "{{ item.rax_id }}" groups: web,new_web with_items: rax.success when: rax.action == 'create' - name: Wait for rackconnect and managed cloud automation to complete hosts: new_web gather_facts: false tasks: - name: Wait for rackconnnect automation to complete local_action: module: rax_facts credentials: ~/.raxpub id: "{{ rax_id }}" region: DFW register: rax_facts until: rax_facts.ansible_facts['rax_metadata']['rackconnect_automation_status']|default('') == 'DEPLOYED' retries: 30 delay: 10 - name: Wait for managed cloud automation to complete local_action: module: rax_facts credentials: ~/.raxpub id: "{{ rax_id }}" region: DFW register: rax_facts until: rax_facts.ansible_facts['rax_metadata']['rax_service_level_automation']|default('') == 'Complete' retries: 30 delay: 10 - name: Base Configure Servers hosts: web roles: - role: users - role: openssh opensshd_PermitRootLogin: "no" - role: ntp .. _using_ansible_pull: Using Ansible Pull ****************** .. code-block:: yaml --- - name: Ensure Rackconnect and Managed Cloud Automation is complete hosts: all connection: local tasks: - name: Check for completed bootstrap stat: path: /etc/bootstrap_complete register: bootstrap - name: Get region command: xenstore-read vm-data/provider_data/region register: rax_region when: bootstrap.stat.exists != True - name: Wait for rackconnect automation to complete uri: url: "https://{{ rax_region.stdout|trim }}.api.rackconnect.rackspace.com/v1/automation_status?format=json" return_content: yes register: automation_status when: bootstrap.stat.exists != True until: automation_status['automation_status']|default('') == 'DEPLOYED' retries: 30 delay: 10 - name: Wait for managed cloud automation to complete wait_for: path: /tmp/rs_managed_cloud_automation_complete delay: 10 when: bootstrap.stat.exists != True - name: Set bootstrap completed file: path: /etc/bootstrap_complete state: touch owner: root group: root mode: 0400 - name: Base Configure Servers hosts: all connection: local roles: - role: users - role: openssh opensshd_PermitRootLogin: "no" - role: ntp .. _using_ansible_pull_with_xenstore: Using Ansible Pull with XenStore ******************************** .. code-block:: yaml --- - name: Ensure Rackconnect and Managed Cloud Automation is complete hosts: all connection: local tasks: - name: Check for completed bootstrap stat: path: /etc/bootstrap_complete register: bootstrap - name: Wait for rackconnect_automation_status xenstore key to exist command: xenstore-exists vm-data/user-metadata/rackconnect_automation_status register: rcas_exists when: bootstrap.stat.exists != True failed_when: rcas_exists.rc|int > 1 until: rcas_exists.rc|int == 0 retries: 30 delay: 10 - name: Wait for rackconnect automation to complete command: xenstore-read vm-data/user-metadata/rackconnect_automation_status register: rcas when: bootstrap.stat.exists != True until: rcas.stdout|replace('"', '') == 'DEPLOYED' retries: 30 delay: 10 - name: Wait for rax_service_level_automation xenstore key to exist command: xenstore-exists vm-data/user-metadata/rax_service_level_automation register: rsla_exists when: bootstrap.stat.exists != True failed_when: rsla_exists.rc|int > 1 until: rsla_exists.rc|int == 0 retries: 30 delay: 10 - name: Wait for managed cloud automation to complete command: xenstore-read vm-data/user-metadata/rackconnect_automation_status register: rsla when: bootstrap.stat.exists != True until: rsla.stdout|replace('"', '') == 'DEPLOYED' retries: 30 delay: 10 - name: Set bootstrap completed file: path: /etc/bootstrap_complete state: touch owner: root group: root mode: 0400 - name: Base Configure Servers hosts: all connection: local roles: - role: users - role: openssh opensshd_PermitRootLogin: "no" - role: ntp .. _advanced_usage: Advanced Usage `````````````` .. _awx_autoscale: Autoscaling with Tower ++++++++++++++++++++++ :doc:`tower` also contains a very nice feature for auto-scaling use cases. In this mode, a simple curl script can call a defined URL and the server will "dial out" to the requester and configure an instance that is spinning up. This can be a great way to reconfigure ephemeral nodes. See the Tower documentation for more details. A benefit of using the callback in Tower over pull mode is that job results are still centrally recorded and less information has to be shared with remote hosts. .. _pending_information: Orchestration in the Rackspace Cloud ++++++++++++++++++++++++++++++++++++ Ansible is a powerful orchestration tool, and rax modules allow you the opportunity to orchestrate complex tasks, deployments, and configurations. The key here is to automate provisioning of infrastructure, like any other pice of software in an environment. Complex deployments might have previously required manual manipulation of load balancers, or manual provisioning of servers. Utilizing the rax modules included with Ansible, one can make the deployment of additional nodes contingent on the current number of running nodes, or the configuration of a clustered application dependent on the number of nodes with common metadata. One could automate the following scenarios, for example: * Servers that are removed from a Cloud Load Balancer one-by-one, updated, verified, and returned to the load balancer pool * Expansion of an already-online environment, where nodes are provisioned, bootstrapped, configured, and software installed * A procedure where app log files are uploaded to a central location, like Cloud Files, before a node is decommissioned * Servers and load balancers that have DNS records created and destroyed on creation and decommissioning, respectively ansible-1.7.2/docsite/rst/guide_rolling_upgrade.rst000066400000000000000000000361631241061774000224770ustar00rootroot00000000000000Continuous Delivery and Rolling Upgrades ======================================== .. _lamp_introduction: Introduction ```````````` Continuous Delivery is the concept of frequently delivering updates to your software application. The idea is that by updating more often, you do not have to wait for a specific timed period, and your organization gets better at the process of responding to change. Some Ansible users are deploying updates to their end users on an hourly or even more frequent basis -- sometimes every time there is an approved code change. To achieve this, you need tools to be able to quickly apply those updates in a zero-downtime way. This document describes in detail how to achieve this goal, using one of Ansible's most complete example playbooks as a template: lamp_haproxy. This example uses a lot of Ansible features: roles, templates, and group variables, and it also comes with an orchestration playbook that can do zero-downtime rolling upgrades of the web application stack. .. note:: `Click here for the latest playbooks for this example `_. The playbooks deploy Apache, PHP, MySQL, Nagios, and HAProxy to a CentOS-based set of servers. We're not going to cover how to run these playbooks here. Read the included README in the github project along with the example for that information. Instead, we're going to take a close look at every part of the playbook and describe what it does. .. _lamp_deployment: Site Deployment ``````````````` Let's start with ``site.yml``. This is our site-wide deployment playbook. It can be used to initially deploy the site, as well as push updates to all of the servers:: --- # This playbook deploys the whole application stack in this site. # Apply common configuration to all hosts - hosts: all roles: - common # Configure and deploy database servers. - hosts: dbservers roles: - db # Configure and deploy the web servers. Note that we include two roles # here, the 'base-apache' role which simply sets up Apache, and 'web' # which includes our example web application. - hosts: webservers roles: - base-apache - web # Configure and deploy the load balancer(s). - hosts: lbservers roles: - haproxy # Configure and deploy the Nagios monitoring node(s). - hosts: monitoring roles: - base-apache - nagios .. note:: If you're not familiar with terms like playbooks and plays, you should review :doc:`playbooks`. In this playbook we have 5 plays. The first one targets ``all`` hosts and applies the ``common`` role to all of the hosts. This is for site-wide things like yum repository configuration, firewall configuration, and anything else that needs to apply to all of the servers. The next four plays run against specific host groups and apply specific roles to those servers. Along with the roles for Nagios monitoring, the database, and the web application, we've implemented a ``base-apache`` role that installs and configures a basic Apache setup. This is used by both the sample web application and the Nagios hosts. .. _lamp_roles: Reusable Content: Roles ``````````````````````` By now you should have a bit of understanding about roles and how they work in Ansible. Roles are a way to organize content: tasks, handlers, templates, and files, into reusable components. This example has six roles: ``common``, ``base-apache``, ``db``, ``haproxy``, ``nagios``, and ``web``. How you organize your roles is up to you and your application, but most sites will have one or more common roles that are applied to all systems, and then a series of application-specific roles that install and configure particular parts of the site. Roles can have variables and dependencies, and you can pass in parameters to roles to modify their behavior. You can read more about roles in the :doc:`playbooks_roles` section. .. _lamp_group_variables: Configuration: Group Variables `````````````````````````````` Group variables are variables that are applied to groups of servers. They can be used in templates and in playbooks to customize behavior and to provide easily-changed settings and parameters. They are stored in a directory called ``group_vars`` in the same location as your inventory. Here is lamp_haproxy's ``group_vars/all`` file. As you might expect, these variables are applied to all of the machines in your inventory:: --- httpd_port: 80 ntpserver: 192.168.1.2 This is a YAML file, and you can create lists and dictionaries for more complex variable structures. In this case, we are just setting two variables, one for the port for the web server, and one for the NTP server that our machines should use for time synchronization. Here's another group variables file. This is ``group_vars/dbservers`` which applies to the hosts in the ``dbservers`` group:: --- mysqlservice: mysqld mysql_port: 3306 dbuser: root dbname: foodb upassword: usersecret If you look in the example, there are group variables for the ``webservers`` group and the ``lbservers`` group, similarly. These variables are used in a variety of places. You can use them in playbooks, like this, in ``roles/db/tasks/main.yml``:: - name: Create Application Database mysql_db: name={{ dbname }} state=present - name: Create Application DB User mysql_user: name={{ dbuser }} password={{ upassword }} priv=*.*:ALL host='%' state=present You can also use these variables in templates, like this, in ``roles/common/templates/ntp.conf.j2``:: driftfile /var/lib/ntp/drift restrict 127.0.0.1 restrict -6 ::1 server {{ ntpserver }} includefile /etc/ntp/crypto/pw keys /etc/ntp/keys You can see that the variable substitution syntax of {{ and }} is the same for both templates and variables. The syntax inside the curly braces is Jinja2, and you can do all sorts of operations and apply different filters to the data inside. In templates, you can also use for loops and if statements to handle more complex situations, like this, in ``roles/common/templates/iptables.j2``:: {% if inventory_hostname in groups['dbservers'] %} -A INPUT -p tcp --dport 3306 -j ACCEPT {% endif %} This is testing to see if the inventory name of the machine we're currently operating on (``inventory_hostname``) exists in the inventory group ``dbservers``. If so, that machine will get an iptables ACCEPT line for port 3306. Here's another example, from the same template:: {% for host in groups['monitoring'] %} -A INPUT -p tcp -s {{ hostvars[host].ansible_default_ipv4.address }} --dport 5666 -j ACCEPT {% endfor %} This loops over all of the hosts in the group called ``monitoring``, and adds an ACCEPT line for each monitoring hosts' default IPV4 address to the current machine's iptables configuration, so that Nagios can monitor those hosts. You can learn a lot more about Jinja2 and its capabilities `here `_, and you can read more about Ansible variables in general in the :doc:`playbooks_variables` section. .. _lamp_rolling_upgrade: The Rolling Upgrade ``````````````````` Now you have a fully-deployed site with web servers, a load balancer, and monitoring. How do you update it? This is where Ansible's orchestration features come into play. While some applications use the term 'orchestration' to mean basic ordering or command-blasting, Ansible refers to orchestration as 'conducting machines like an orchestra', and has a pretty sophisticated engine for it. Ansible has the capability to do operations on multi-tier applications in a coordinated way, making it easy to orchestrate a sophisticated zero-downtime rolling upgrade of our web application. This is implemented in a separate playbook, called ``rolling_upgrade.yml``. Looking at the playbook, you can see it is made up of two plays. The first play is very simple and looks like this:: - hosts: monitoring tasks: [] What's going on here, and why are there no tasks? You might know that Ansible gathers "facts" from the servers before operating upon them. These facts are useful for all sorts of things: networking information, OS/distribution versions, etc. In our case, we need to know something about all of the monitoring servers in our environment before we perform the update, so this simple play forces a fact-gathering step on our monitoring servers. You will see this pattern sometimes, and it's a useful trick to know. The next part is the update play. The first part looks like this:: - hosts: webservers user: root serial: 1 This is just a normal play definition, operating on the ``webservers`` group. The ``serial`` keyword tells Ansible how many servers to operate on at once. If it's not specified, Ansible will parallelize these operations up to the default "forks" limit specified in the configuration file. But for a zero-downtime rolling upgrade, you may not want to operate on that many hosts at once. If you had just a handful of webservers, you may want to set ``serial`` to 1, for one host at a time. If you have 100, maybe you could set ``serial`` to 10, for ten at a time. Here is the next part of the update play:: pre_tasks: - name: disable nagios alerts for this host webserver service nagios: action=disable_alerts host={{ inventory_hostname }} services=webserver delegate_to: "{{ item }}" with_items: groups.monitoring - name: disable the server in haproxy shell: echo "disable server myapplb/{{ inventory_hostname }}" | socat stdio /var/lib/haproxy/stats delegate_to: "{{ item }}" with_items: groups.lbservers The ``pre_tasks`` keyword just lets you list tasks to run before the roles are called. This will make more sense in a minute. If you look at the names of these tasks, you can see that we are disabling Nagios alerts and then removing the webserver that we are currently updating from the HAProxy load balancing pool. The ``delegate_to`` and ``with_items`` arguments, used together, cause Ansible to loop over each monitoring server and load balancer, and perform that operation (delegate that operation) on the monitoring or load balancing server, "on behalf" of the webserver. In programming terms, the outer loop is the list of web servers, and the inner loop is the list of monitoring servers. Note that the HAProxy step looks a little complicated. We're using HAProxy in this example because it's freely available, though if you have (for instance) an F5 or Netscaler in your infrastructure (or maybe you have an AWS Elastic IP setup?), you can use modules included in core Ansible to communicate with them instead. You might also wish to use other monitoring modules instead of nagios, but this just shows the main goal of the 'pre tasks' section -- take the server out of monitoring, and take it out of rotation. The next step simply re-applies the proper roles to the web servers. This will cause any configuration management declarations in ``web`` and ``base-apache`` roles to be applied to the web servers, including an update of the web application code itself. We don't have to do it this way--we could instead just purely update the web application, but this is a good example of how roles can be used to reuse tasks:: roles: - common - base-apache - web Finally, in the ``post_tasks`` section, we reverse the changes to the Nagios configuration and put the web server back in the load balancing pool:: post_tasks: - name: Enable the server in haproxy shell: echo "enable server myapplb/{{ inventory_hostname }}" | socat stdio /var/lib/haproxy/stats delegate_to: "{{ item }}" with_items: groups.lbservers - name: re-enable nagios alerts nagios: action=enable_alerts host={{ inventory_hostname }} services=webserver delegate_to: "{{ item }}" with_items: groups.monitoring Again, if you were using a Netscaler or F5 or Elastic Load Balancer, you would just substitute in the appropriate modules instead. .. _lamp_end_notes: Managing Other Load Balancers ````````````````````````````` In this example, we use the simple HAProxy load balancer to front-end the web servers. It's easy to configure and easy to manage. As we have mentioned, Ansible has built-in support for a variety of other load balancers like Citrix NetScaler, F5 BigIP, Amazon Elastic Load Balancers, and more. See the :doc:`modules` documentation for more information. For other load balancers, you may need to send shell commands to them (like we do for HAProxy above), or call an API, if your load balancer exposes one. For the load balancers for which Ansible has modules, you may want to run them as a ``local_action`` if they contact an API. You can read more about local actions in the :doc:`playbooks_delegation` section. Should you develop anything interesting for some hardware where there is not a core module, it might make for a good module for core inclusion! .. _lamp_end_to_end: Continuous Delivery End-To-End `````````````````````````````` Now that you have an automated way to deploy updates to your application, how do you tie it all together? A lot of organizations use a continuous integration tool like `Jenkins `_ or `Atlassian Bamboo `_ to tie the development, test, release, and deploy steps together. You may also want to use a tool like `Gerrit `_ to add a code review step to commits to either the application code itself, or to your Ansible playbooks, or both. Depending on your environment, you might be deploying continuously to a test environment, running an integration test battery against that environment, and then deploying automatically into production. Or you could keep it simple and just use the rolling-update for on-demand deployment into test or production specifically. This is all up to you. For integration with Continuous Integration systems, you can easily trigger playbook runs using the ``ansible-playbook`` command line tool, or, if you're using :doc:`tower`, the ``tower-cli`` or the built-in REST API. (The tower-cli command 'joblaunch' will spawn a remote job over the REST API and is pretty slick). This should give you a good idea of how to structure a multi-tier application with Ansible, and orchestrate operations upon that app, with the eventual goal of continuous delivery to your customers. You could extend the idea of the rolling upgrade to lots of different parts of the app; maybe add front-end web servers along with application servers, for instance, or replace the SQL database with something like MongoDB or Riak. Ansible gives you the capability to easily manage complicated environments and automate common operations. .. seealso:: `lamp_haproxy example `_ The lamp_haproxy example discussed here. :doc:`playbooks` An introduction to playbooks :doc:`playbooks_roles` An introduction to playbook roles :doc:`playbooks_variables` An introduction to Ansible variables `Ansible.com: Continuous Delivery `_ An introduction to Continuous Delivery with Ansible ansible-1.7.2/docsite/rst/guide_vagrant.rst000066400000000000000000000104071241061774000207550ustar00rootroot00000000000000Using Vagrant and Ansible ========================= .. _vagrant_intro: Introduction ```````````` Vagrant is a tool to manage virtual machine environments, and allows you to configure and use reproducible work environments on top of various virtualization and cloud platforms. It also has integration with Ansible as a provisioner for these virtual machines, and the two tools work together well. This guide will describe how to use Vagrant and Ansible together. If you're not familiar with Vagrant, you should visit `the documentation `_. This guide assumes that you already have Ansible installed and working. Running from a Git checkout is fine. Follow the :doc:`intro_installation` guide for more information. .. _vagrant_setup: Vagrant Setup ````````````` The first step once you've installed Vagrant is to create a ``Vagrantfile`` and customize it to suit your needs. This is covered in detail in the Vagrant documentation, but here is a quick example: .. code-block:: bash $ mkdir vagrant-test $ cd vagrant-test $ vagrant init precise32 http://files.vagrantup.com/precise32.box This will create a file called Vagrantfile that you can edit to suit your needs. The default Vagrantfile has a lot of comments. Here is a simplified example that includes a section to use the Ansible provisioner: .. code-block:: ruby # Vagrantfile API/syntax version. Don't touch unless you know what you're doing! VAGRANTFILE_API_VERSION = "2" Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.box = "precise32" config.vm.box_url = "http://files.vagrantup.com/precise32.box" config.vm.network :public_network config.vm.provision "ansible" do |ansible| ansible.playbook = "playbook.yml" end end The Vagrantfile has a lot of options, but these are the most important ones. Notice the ``config.vm.provision`` section that refers to an Ansible playbook called ``playbook.yml`` in the same directory as the Vagrantfile. Vagrant runs the provisioner once the virtual machine has booted and is ready for SSH access. .. code-block:: bash $ vagrant up This will start the VM and run the provisioning playbook. There are a lot of Ansible options you can configure in your Vagrantfile. Some particularly useful options are ``ansible.extra_vars``, ``ansible.sudo`` and ``ansible.sudo_user``, and ``ansible.host_key_checking`` which you can disable to avoid SSH connection problems to new virtual machines. Visit the `Ansible Provisioner documentation `_ for more information. To re-run a playbook on an existing VM, just run: .. code-block:: bash $ vagrant provision This will re-run the playbook. .. _running_ansible: Running Ansible Manually ```````````````````````` Sometimes you may want to run Ansible manually against the machines. This is pretty easy to do. Vagrant automatically creates an inventory file for each Vagrant machine in the same directory called ``vagrant_ansible_inventory_machinename``. It configures the inventory file according to the SSH tunnel that Vagrant automatically creates, and executes ``ansible-playbook`` with the correct username and SSH key options to allow access. A typical automatically-created inventory file may look something like this: .. code-block:: none # Generated by Vagrant machine ansible_ssh_host=127.0.0.1 ansible_ssh_port=2222 If you want to run Ansible manually, you will want to make sure to pass ``ansible`` or ``ansible-playbook`` commands the correct arguments for the username (usually ``vagrant``) and the SSH key (usually ``~/.vagrant.d/insecure_private_key``), and the autogenerated inventory file. Here is an example: .. code-block:: bash $ ansible-playbook -i vagrant_ansible_inventory_machinename --private-key=~/.vagrant.d/insecure_private_key -u vagrant playbook.yml .. seealso:: `Vagrant Home `_ The Vagrant homepage with downloads `Vagrant Documentation `_ Vagrant Documentation `Ansible Provisioner `_ The Vagrant documentation for the Ansible provisioner :doc:`playbooks` An introduction to playbooks ansible-1.7.2/docsite/rst/guides.rst000066400000000000000000000007051241061774000174160ustar00rootroot00000000000000Detailed Guides ``````````````` This section is new and evolving. The idea here is explore particular use cases in greater depth and provide a more "top down" explanation of some basic features. .. toctree:: :maxdepth: 1 guide_aws guide_rax guide_gce guide_vagrant guide_rolling_upgrade test_strategies Pending topics may include: Docker, Jenkins, Google Compute Engine, Linode/Digital Ocean, Continuous Deployment, and more. ansible-1.7.2/docsite/rst/guru.rst000066400000000000000000000015761241061774000171270ustar00rootroot00000000000000Ansible Guru ```````````` While many users should be able to get on fine with the documentation, mailing list, and IRC, sometimes you want a bit more. `Ansible Guru `_ is an offering from Ansible, Inc that helps users who would like more dedicated help with Ansible, including building playbooks, best practices, architecture suggestions, and more -- all from our awesome support and services team. It also includes some useful discounts and also some free T-shirts, though you shouldn't get it just for the free shirts! It's a great way to train up to becoming an Ansible expert. For those interested, click through the link above. You can sign up in minutes! For users looking for more hands-on help, we also have some more information on our `Services page `_, and support is also included with :doc:`tower`. ansible-1.7.2/docsite/rst/index.rst000066400000000000000000000045361241061774000172530ustar00rootroot00000000000000Ansible Documentation ===================== About Ansible ````````````` Welcome to the Ansible documentation! Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible's goals are foremost those of simplicity and maximum ease of use. It also has a strong focus on security and reliability, featuring a minimum of moving parts, usage of OpenSSH for transport (with an accelerated socket mode and pull modes as alternatives), and a language that is designed around auditability by humans -- even those not familiar with the program. We believe simplicity is relevant to all sizes of environments and design for busy users of all types -- whether this means developers, sysadmins, release engineers, IT managers, and everywhere in between. Ansible is appropriate for managing small setups with a handful of instances as well as enterprise environments with many thousands. Ansible manages machines in an agentless manner. There is never a question of how to upgrade remote daemons or the problem of not being able to manage systems because daemons are uninstalled. As OpenSSH is one of the most peer reviewed open source components, the security exposure of using the tool is greatly reduced. Ansible is decentralized -- it relies on your existing OS credentials to control access to remote machines; if needed it can easily connect with Kerberos, LDAP, and other centralized authentication management systems. This documentation covers the current released version of Ansible (1.6.10) and also some development version features (1.7). For recent features, in each section, the version of Ansible where the feature is added is indicated. Ansible, Inc releases a new major release of Ansible approximately every 2 months. The core application evolves somewhat conservatively, valuing simplicity in language design and setup, while the community around new modules and plugins being developed and contributed moves very very quickly, typically adding 20 or so new modules in each release. .. _an_introduction: .. toctree:: :maxdepth: 1 intro quickstart playbooks playbooks_special_topics modules modules_by_category guides developing tower community galaxy test_strategies faq glossary YAMLSyntax guru ansible-1.7.2/docsite/rst/intro.rst000066400000000000000000000011771241061774000172750ustar00rootroot00000000000000Introduction ============ Before we dive into the really fun parts -- playbooks, configuration management, deployment, and orchestration, we'll learn how to get Ansible installed and some basic concepts. We'll go over how to execute ad-hoc commands in parallel across your nodes using /usr/bin/ansible. We'll also see what sort of modules are available in Ansible's core (though you can also write your own, which we'll also show later). .. toctree:: :maxdepth: 1 intro_installation intro_getting_started intro_inventory intro_dynamic_inventory intro_patterns intro_adhoc intro_configuration intro_windows ansible-1.7.2/docsite/rst/intro_adhoc.rst000066400000000000000000000252551241061774000204360ustar00rootroot00000000000000Introduction To Ad-Hoc Commands =============================== .. contents:: Topics .. highlight:: bash The following examples show how to use `/usr/bin/ansible` for running ad hoc tasks. What's an ad-hoc command? An ad-hoc command is something that you might type in to do something really quick, but don't want to save for later. This is a good place to start to understand the basics of what Ansible can do prior to learning the playbooks language -- ad-hoc commands can also be used to do quick things that you might not necessarily want to write a full playbook for. Generally speaking, the true power of Ansible lies in playbooks. Why would you use ad-hoc tasks versus playbooks? For instance, if you wanted to power off all of your lab for Christmas vacation, you could execute a quick one-liner in Ansible without writing a playbook. For configuration management and deployments, though, you'll want to pick up on using '/usr/bin/ansible-playbook' -- the concepts you will learn here will port over directly to the playbook language. (See :doc:`playbooks` for more information about those) If you haven't read :doc:`intro_inventory` already, please look that over a bit first and then we'll get going. .. _parallelism_and_shell_commands: Parallelism and Shell Commands `````````````````````````````` Arbitrary example. Let's use Ansible's command line tool to reboot all web servers in Atlanta, 10 at a time. First, let's set up SSH-agent so it can remember our credentials:: $ ssh-agent bash $ ssh-add ~/.ssh/id_rsa If you don't want to use ssh-agent and want to instead SSH with a password instead of keys, you can with ``--ask-pass`` (``-k``), but it's much better to just use ssh-agent. Now to run the command on all servers in a group, in this case, *atlanta*, in 10 parallel forks:: $ ansible atlanta -a "/sbin/reboot" -f 10 /usr/bin/ansible will default to running from your user account. If you do not like this behavior, pass in "-u username". If you want to run commands as a different user, it looks like this:: $ ansible atlanta -a "/usr/bin/foo" -u username Often you'll not want to just do things from your user account. If you want to run commands through sudo:: $ ansible atlanta -a "/usr/bin/foo" -u username --sudo [--ask-sudo-pass] Use ``--ask-sudo-pass`` (``-K``) if you are not using passwordless sudo. This will interactively prompt you for the password to use. Use of passwordless sudo makes things easier to automate, but it's not required. It is also possible to sudo to a user other than root using ``--sudo-user`` (``-U``):: $ ansible atlanta -a "/usr/bin/foo" -u username -U otheruser [--ask-sudo-pass] .. note:: Rarely, some users have security rules where they constrain their sudo environment to running specific command paths only. This does not work with ansible's no-bootstrapping philosophy and hundreds of different modules. If doing this, use Ansible from a special account that does not have this constraint. One way of doing this without sharing access to unauthorized users would be gating Ansible with :doc:`tower`, which can hold on to an SSH credential and let members of certain organizations use it on their behalf without having direct access. Ok, so those are basics. If you didn't read about patterns and groups yet, go back and read :doc:`intro_patterns`. The ``-f 10`` in the above specifies the usage of 10 simultaneous processes to use. You can also set this in :doc:`intro_configuration` to avoid setting it again. The default is actually 5, which is really small and conservative. You are probably going to want to talk to a lot more simultaneous hosts so feel free to crank this up. If you have more hosts than the value set for the fork count, Ansible will talk to them, but it will take a little longer. Feel free to push this value as high as your system can handle it! You can also select what Ansible "module" you want to run. Normally commands also take a ``-m`` for module name, but the default module name is 'command', so we didn't need to specify that all of the time. We'll use ``-m`` in later examples to run some other :doc:`modules`. .. note:: The :ref:`command` module does not support shell variables and things like piping. If we want to execute a module using a shell, use the 'shell' module instead. Read more about the differences on the :doc:`modules` page. Using the :ref:`shell` module looks like this:: $ ansible raleigh -m shell -a 'echo $TERM' When running any command with the Ansible *ad hoc* CLI (as opposed to :doc:`Playbooks `), pay particular attention to shell quoting rules, so the local shell doesn't eat a variable before it gets passed to Ansible. For example, using double vs single quotes in the above example would evaluate the variable on the box you were on. So far we've been demoing simple command execution, but most Ansible modules usually do not work like simple scripts. They make the remote system look like you state, and run the commands necessary to get it there. This is commonly referred to as 'idempotence', and is a core design goal of Ansible. However, we also recognize that running arbitrary commands is equally important, so Ansible easily supports both. .. _file_transfer: File Transfer ````````````` Here's another use case for the `/usr/bin/ansible` command line. Ansible can SCP lots of files to multiple machines in parallel. To transfer a file directly to many servers:: $ ansible atlanta -m copy -a "src=/etc/hosts dest=/tmp/hosts" If you use playbooks, you can also take advantage of the ``template`` module, which takes this another step further. (See module and playbook documentation). The ``file`` module allows changing ownership and permissions on files. These same options can be passed directly to the ``copy`` module as well:: $ ansible webservers -m file -a "dest=/srv/foo/a.txt mode=600" $ ansible webservers -m file -a "dest=/srv/foo/b.txt mode=600 owner=mdehaan group=mdehaan" The ``file`` module can also create directories, similar to ``mkdir -p``:: $ ansible webservers -m file -a "dest=/path/to/c mode=755 owner=mdehaan group=mdehaan state=directory" As well as delete directories (recursively) and delete files:: $ ansible webservers -m file -a "dest=/path/to/c state=absent" .. _managing_packages: Managing Packages ````````````````` There are modules available for yum and apt. Here are some examples with yum. Ensure a package is installed, but don't update it:: $ ansible webservers -m yum -a "name=acme state=installed" Ensure a package is installed to a specific version:: $ ansible webservers -m yum -a "name=acme-1.5 state=installed" Ensure a package is at the latest version:: $ ansible webservers -m yum -a "name=acme state=latest" Ensure a package is not installed:: $ ansible webservers -m yum -a "name=acme state=removed" Ansible has modules for managing packages under many platforms. If your package manager does not have a module available for it, you can install for other packages using the command module or (better!) contribute a module for other package managers. Stop by the mailing list for info/details. .. _users_and_groups: Users and Groups ```````````````` The 'user' module allows easy creation and manipulation of existing user accounts, as well as removal of user accounts that may exist:: $ ansible all -m user -a "name=foo password=" $ ansible all -m user -a "name=foo state=absent" See the :doc:`modules` section for details on all of the available options, including how to manipulate groups and group membership. .. _from_source_control: Deploying From Source Control ````````````````````````````` Deploy your webapp straight from git:: $ ansible webservers -m git -a "repo=git://foo.example.org/repo.git dest=/srv/myapp version=HEAD" Since Ansible modules can notify change handlers it is possible to tell Ansible to run specific tasks when the code is updated, such as deploying Perl/Python/PHP/Ruby directly from git and then restarting apache. .. _managing_services: Managing Services ````````````````` Ensure a service is started on all webservers:: $ ansible webservers -m service -a "name=httpd state=started" Alternatively, restart a service on all webservers:: $ ansible webservers -m service -a "name=httpd state=restarted" Ensure a service is stopped:: $ ansible webservers -m service -a "name=httpd state=stopped" .. _time_limited_background_operations: Time Limited Background Operations `````````````````````````````````` Long running operations can be backgrounded, and their status can be checked on later. The same job ID is given to the same task on all hosts, so you won't lose track. If you kick hosts and don't want to poll, it looks like this:: $ ansible all -B 3600 -a "/usr/bin/long_running_operation --do-stuff" If you do decide you want to check on the job status later, you can:: $ ansible all -m async_status -a "jid=123456789" Polling is built-in and looks like this:: $ ansible all -B 1800 -P 60 -a "/usr/bin/long_running_operation --do-stuff" The above example says "run for 30 minutes max (``-B``: 30*60=1800), poll for status (``-P``) every 60 seconds". Poll mode is smart so all jobs will be started before polling will begin on any machine. Be sure to use a high enough ``--forks`` value if you want to get all of your jobs started very quickly. After the time limit (in seconds) runs out (``-B``), the process on the remote nodes will be terminated. Typically you'll only be backgrounding long-running shell commands or software upgrades only. Backgrounding the copy module does not do a background file transfer. :doc:`Playbooks ` also support polling, and have a simplified syntax for this. .. _checking_facts: Gathering Facts ``````````````` Facts are described in the playbooks section and represent discovered variables about a system. These can be used to implement conditional execution of tasks but also just to get ad-hoc information about your system. You can see all facts via:: $ ansible all -m setup Its also possible to filter this output to just export certain facts, see the "setup" module documentation for details. Read more about facts at :doc:`playbooks_variables` once you're ready to read up on :doc:`Playbooks `. .. seealso:: :doc:`intro_configuration` All about the Ansible config file :doc:`modules` A list of available modules :doc:`playbooks` Using Ansible for configuration management & deployment `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/intro_configuration.rst000066400000000000000000000544361241061774000222320ustar00rootroot00000000000000The Ansible Configuration File ++++++++++++++++++++++++++++++ .. contents:: Topics .. highlight:: bash Certain settings in Ansible are adjustable via a configuration file. The stock configuration should be sufficient for most users, but there may be reasons you would want to change them. Changes can be made and used in a configuration file which will be processed in the following order:: * ANSIBLE_CONFIG (an environment variable) * ansible.cfg (in the current directory) * .ansible.cfg (in the home directory) * /etc/ansible/ansible.cfg Prior to 1.5 the order was:: * ansible.cfg (in the current directory) * ANSIBLE_CONFIG (an environment variable) * .ansible.cfg (in the home directory) * /etc/ansible/ansible.cfg Ansible will process the above list and use the first file found. Settings in files are not merged. .. _getting_the_latest_configuration: Getting the latest configuration ```````````````````````````````` If installing ansible from a package manager, the latest ansible.cfg should be present in /etc/ansible, possibly as a ".rpmnew" file (or other) as appropriate in the case of updates. If you have installed from pip or from source, however, you may want to create this file in order to override default settings in Ansible. You may wish to consult the `ansible.cfg in source control `_ for all of the possible latest values. .. _environmental_configuration: Environmental configuration ``````````````````````````` Ansible also allows configuration of settings via environment variables. If these environment variables are set, they will override any setting loaded from the configuration file. These variables are for brevity not defined here, but look in 'constants.py' in the source tree if you want to use these. They are mostly considered to be a legacy system as compared to the config file, but are equally valid. .. _config_values_by_section: Explanation of values by section ```````````````````````````````` The configuration file is broken up into sections. Most options are in the "general" section but some sections of the file are specific to certain connection types. .. _general_defaults: General defaults ---------------- In the [defaults] section of ansible.cfg, the following settings are tunable: .. _action_plugins: action_plugins ============== Actions are pieces of code in ansible that enable things like module execution, templating, and so forth. This is a developer-centric feature that allows low-level extensions around Ansible to be loaded from different locations:: action_plugins = /usr/share/ansible_plugins/action_plugins Most users will not need to use this feature. See :doc:`developing_plugins` for more details. .. _ansible_managed: ansible_managed =============== Ansible-managed is a string that can be inserted into files written by Ansible's config templating system, if you use a string like:: {{ ansible_managed }} The default configuration shows who modified a file and when:: ansible_managed = Ansible managed: {file} modified on %Y-%m-%d %H:%M:%S by {uid} on {host} This is useful to tell users that a file has been placed by Ansible and manual changes are likely to be overwritten. Note that if using this feature, and there is a date in the string, the template will be reported changed each time as the date is updated. .. _ask_pass: ask_pass ======== This controls whether an Ansible playbook should prompt for a password by default. The default behavior is no:: #ask_pass=True If using SSH keys for authentication, it's probably not needed to change this setting. .. _ask_sudo_pass: ask_sudo_pass ============= Similar to ask_pass, this controls whether an Ansible playbook should prompt for a sudo password by default when sudoing. The default behavior is also no:: #ask_sudo_pass=True Users on platforms where sudo passwords are enabled should consider changing this setting. .. _callback_plugins: callback_plugins ================ This is a developer-centric feature that allows low-level extensions around Ansible to be loaded from different locations:: callback_plugins = /usr/share/ansible_plugins/callback_plugins Most users will not need to use this feature. See :doc:`developing_plugins` for more details .. _connection_plugins: connection_plugins ================== This is a developer-centric feature that allows low-level extensions around Ansible to be loaded from different locations:: connection_plugins = /usr/share/ansible_plugins/connection_plugins Most users will not need to use this feature. See :doc:`developing_plugins` for more details .. _deprecation_warnings: deprecation_warnings ==================== .. versionadded:: 1.3 Allows disabling of deprecating warnings in ansible-playbook output:: deprecation_warnings = True Deprecation warnings indicate usage of legacy features that are slated for removal in a future release of Ansible. .. _display_skipped_hosts: display_skipped_hosts ===================== If set to `False`, ansible will not display any status for a task that is skipped. The default behavior is to display skipped tasks:: #display_skipped_hosts=True Note that Ansible will always show the task header for any task, regardless of whether or not the task is skipped. .. _error_on_undefined_vars: error_on_undefined_vars ======================= On by default since Ansible 1.3, this causes ansible to fail steps that reference variable names that are likely typoed:: #error_on_undefined_vars=True If set to False, any '{{ template_expression }}' that contains undefined variables will be rendered in a template or ansible action line exactly as written. .. _executable: executable ========== This indicates the command to use to spawn a shell under a sudo environment. Users may need to change this in rare instances to /bin/bash in rare instances when sudo is constrained, but in most cases it may be left as is:: #executable = /bin/bash .. _filter_plugins: filter_plugins ============== This is a developer-centric feature that allows low-level extensions around Ansible to be loaded from different locations:: filter_plugins = /usr/share/ansible_plugins/filter_plugins Most users will not need to use this feature. See :doc:`developing_plugins` for more details .. _forks: forks ===== This is the default number of parallel processes to spawn when communicating with remote hosts. Since Ansible 1.3, the fork number is automatically limited to the number of possible hosts, so this is really a limit of how much network and CPU load you think you can handle. Many users may set this to 50, some set it to 500 or more. If you have a large number of hosts, higher values will make actions across all of those hosts complete faster. The default is very very conservative:: forks=5 .. _gathering: gathering ========= New in 1.6, the 'gathering' setting controls the default policy of facts gathering (variables discovered about remote systems). The value 'implicit' is the default, meaning facts will be gathered per play unless 'gather_facts: False' is set in the play. The value 'explicit' is the inverse, facts will not be gathered unless directly requested in the play. The value 'smart' means each new host that has no facts discovered will be scanned, but if the same host is addressed in multiple plays it will not be contacted again in the playbook run. This option can be useful for those wishing to save fact gathering time. hash_behaviour ============== Ansible by default will override variables in specific precedence orders, as described in :doc:`playbooks_variables`. When a variable of higher precedence wins, it will replace the other value. Some users prefer that variables that are hashes (aka 'dictionaries' in Python terms) are merged. This setting is called 'merge'. This is not the default behavior and it does not affect variables whose values are scalars (integers, strings) or arrays. We generally recommend not using this setting unless you think you have an absolute need for it, and playbooks in the official examples repos do not use this setting:: #hash_behaviour=replace The valid values are either 'replace' (the default) or 'merge'. .. _hostfile: hostfile ======== This is the default location of the inventory file, script, or directory that Ansible will use to determine what hosts it has available to talk to:: hostfile = /etc/ansible/hosts .. _host_key_checking: host_key_checking ================= As described in :doc:`intro_getting_started`, host key checking is on by default in Ansible 1.3 and later. If you understand the implications and wish to disable it, you may do so here by setting the value to False:: host_key_checking=True .. _jinja2_extensions: jinja2_extensions ================= This is a developer-specific feature that allows enabling additional Jinja2 extensions:: jinja2_extensions = jinja2.ext.do,jinja2.ext.i18n If you do not know what these do, you probably don't need to change this setting :) .. _legacy_playbook_variables: legacy_playbook_variables ========================= Ansible prefers to use Jinja2 syntax '{{ like_this }}' to indicate a variable should be substituted in a particular string. However, older versions of playbooks used a more Perl-style syntax. This syntax was undesirable as it frequently conflicted with bash and was hard to explain to new users when referencing complicated variable hierarchies, so we have standardized on the '{{ jinja2 }}' way. To ensure a string like '$foo' is not inadvertently replaced in a Perl or Bash script template, the old form of templating (which is still enabled as of Ansible 1.4) can be disabled like so :: legacy_playbook_variables = no .. _library: library ======= This is the default location Ansible looks to find modules:: library = /usr/share/ansible Ansible knows how to look in multiple locations if you feed it a colon separated path, and it also will look for modules in the "./library" directory alongside a playbook. .. _log_path: log_path ======== If present and configured in ansible.cfg, Ansible will log information about executions at the designated location. Be sure the user running Ansible has permissions on the logfile:: log_path=/var/log/ansible.log This behavior is not on by default. Note that ansible will, without this setting, record module arguments called to the syslog of managed machines. Password arguments are excluded. For Enterprise users seeking more detailed logging history, you may be interested in :doc:`tower`. .. _lookup_plugins: lookup_plugins ============== This is a developer-centric feature that allows low-level extensions around Ansible to be loaded from different locations:: lookup_plugins = /usr/share/ansible_plugins/lookup_plugins Most users will not need to use this feature. See :doc:`developing_plugins` for more details .. _module_lang: module_lang =========== This is to set the default language to communicate between the module and the system. By default, the value is 'C'. .. _module_name: module_name =========== This is the default module name (-m) value for /usr/bin/ansible. The default is the 'command' module. Remember the command module doesn't support shell variables, pipes, or quotes, so you might wish to change it to 'shell':: module_name = command .. _nocolor: nocolor ======= By default ansible will try to colorize output to give a better indication of failure and status information. If you dislike this behavior you can turn it off by setting 'nocolor' to 1:: nocolor=0 .. _nocows: nocows ====== By default ansible will take advantage of cowsay if installed to make /usr/bin/ansible-playbook runs more exciting. Why? We believe systems management should be a happy experience. If you do not like the cows, you can disable them by setting 'nocows' to 1:: nocows=0 .. _pattern: pattern ======= This is the default group of hosts to talk to in a playbook if no "hosts:" stanza is supplied. The default is to talk to all hosts. You may wish to change this to protect yourself from surprises:: hosts=* Note that /usr/bin/ansible always requires a host pattern and does not use this setting, only /usr/bin/ansible-playbook. .. _poll_interval: poll_interval ============= For asynchronous tasks in Ansible (covered in :doc:`playbooks_async`), this is how often to check back on the status of those tasks when an explicit poll interval is not supplied. The default is a reasonably moderate 15 seconds which is a tradeoff between checking in frequently and providing a quick turnaround when something may have completed:: poll_interval=15 .. _private_key_file: private_key_file ================ If you are using a pem file to authenticate with machines rather than SSH agent or passwords, you can set the default value here to avoid re-specifying ``--ansible-private-keyfile`` with every invocation:: private_key_file=/path/to/file.pem .. _remote_port: remote_port =========== This sets the default SSH port on all of your systems, for systems that didn't specify an alternative value in inventory. The default is the standard 22:: remote_port = 22 .. _remote_tmp: remote_tmp ========== Ansible works by transferring modules to your remote machines, running them, and then cleaning up after itself. In some cases, you may not wish to use the default location and would like to change the path. You can do so by altering this setting:: remote_tmp = $HOME/.ansible/tmp The default is to use a subdirectory of the user's home directory. Ansible will then choose a random directory name inside this location. .. _remote_user: remote_user =========== This is the default username ansible will connect as for /usr/bin/ansible-playbook. Note that /usr/bin/ansible will always default to the current user if this is not defined:: remote_user = root .. _roles_path: roles_path ========== .. versionadded: '1.4' The roles path indicate additional directories beyond the 'roles/' subdirectory of a playbook project to search to find Ansible roles. For instance, if there was a source control repository of common roles and a different repository of playbooks, you might choose to establish a convention to checkout roles in /opt/mysite/roles like so:: roles_path = /opt/mysite/roles Additional paths can be provided separated by colon characters, in the same way as other pathstrings:: roles_path = /opt/mysite/roles:/opt/othersite/roles Roles will be first searched for in the playbook directory. Should a role not be found, it will indicate all the possible paths that were searched. .. _sudo_exe: sudo_exe ======== If using an alternative sudo implementation on remote machines, the path to sudo can be replaced here provided the sudo implementation is matching CLI flags with the standard sudo:: sudo_exe=sudo .. _sudo_flags: sudo_flags ========== Additional flags to pass to sudo when engaging sudo support. The default is '-H' which preserves the environment of the original user. In some situations you may wish to add or remote flags, but in general most users will not need to change this setting:: sudo_flags=-H .. _sudo_user: sudo_user ========= This is the default user to sudo to if ``--sudo-user`` is not specified or 'sudo_user' is not specified in an Ansible playbook. The default is the most logical: 'root':: sudo_user=root .. _system_warnings: system_warnings =============== .. versionadded:: 1.6 Allows disabling of warnings related to potential issues on the system running ansible itself (not on the managed hosts):: system_warnings = True These may include warnings about 3rd party packages or other conditions that should be resolved if possible. .. _timeout: timeout ======= This is the default SSH timeout to use on connection attempts:: timeout = 10 .. _transport: transport ========= This is the default transport to use if "-c " is not specified to /usr/bin/ansible or /usr/bin/ansible-playbook. The default is 'smart', which will use 'ssh' (OpenSSH based) if the local operating system is new enough to support ControlPersist technology, and then will otherwise use 'paramiko'. Other transport options include 'local', 'chroot', 'jail', and so on. Users should usually leave this setting as 'smart' and let their playbooks choose an alternate setting when needed with the 'connection:' play parameter. .. _vars_plugins: vars_plugins ============ This is a developer-centric feature that allows low-level extensions around Ansible to be loaded from different locations:: vars_plugins = /usr/share/ansible_plugins/vars_plugins Most users will not need to use this feature. See :doc:`developing_plugins` for more details .. _paramiko_settings: Paramiko Specific Settings -------------------------- Paramiko is the default SSH connection implementation on Enterprise Linux 6 or earlier, and is not used by default on other platforms. Settings live under the [paramiko] header. .. _record_host_keys: record_host_keys ================ The default setting of yes will record newly discovered and approved (if host key checking is enabled) hosts in the user's hostfile. This setting may be inefficient for large numbers of hosts, and in those situations, using the ssh transport is definitely recommended instead. Setting it to False will improve performance and is recommended when host key checking is disabled:: record_host_keys=True .. _openssh_settings: OpenSSH Specific Settings ------------------------- Under the [ssh_connection] header, the following settings are tunable for SSH connections. OpenSSH is the default connection type for Ansible on OSes that are new enough to support ControlPersist. (This means basically all operating systems except Enterprise Linux 6 or earlier). .. _ssh_args: ssh_args ======== If set, this will pass a specific set of options to Ansible rather than Ansible's usual defaults:: ssh_args = -o ControlMaster=auto -o ControlPersist=60s In particular, users may wish to raise the ControlPersist time to encourage performance. A value of 30 minutes may be appropriate. .. _control_path: control_path ============ This is the location to save ControlPath sockets. This defaults to:: control_path=%(directory)s/ansible-ssh-%%h-%%p-%%r On some systems with very long hostnames or very long path names (caused by long user names or deeply nested home directories) this can exceed the character limit on file socket names (108 characters for most platforms). In that case, you may wish to shorten the string to something like the below:: control_path = %(directory)s/%%h-%%r Ansible 1.4 and later will instruct users to run with "-vvvv" in situations where it hits this problem and if so it is easy to tell there is too long of a Control Path filename. This may be frequently encountered on EC2. .. _scp_if_ssh: scp_if_ssh ========== Occasionally users may be managing a remote system that doesn't have SFTP enabled. If set to True, we can cause scp to be used to transfer remote files instead:: scp_if_ssh=False There's really no reason to change this unless problems are encountered, and then there's also no real drawback to managing the switch. Most environments support SFTP by default and this doesn't usually need to be changed. .. _pipelining: pipelining ========== Enabling pipelining reduces the number of SSH operations required to execute a module on the remote server, by executing many ansible modules without actual file transfer. This can result in a very significant performance improvement when enabled, however when using "sudo:" operations you must first disable 'requiretty' in /etc/sudoers on all managed hosts. By default, this option is disabled to preserve compatibility with sudoers configurations that have requiretty (the default on many distros), but is highly recommended if you can enable it, eliminating the need for :doc:`playbooks_acceleration`:: pipelining=False .. _accelerate_settings: Accelerate Mode Settings ------------------------ Under the [accelerate] header, the following settings are tunable for :doc:`playbooks_acceleration`. Acceleration is a useful performance feature to use if you cannot enable :ref:`pipelining` in your environment, but is probably not needed if you can. .. _accelerate_port: accelerate_port =============== .. versionadded:: 1.3 This is the port to use for accelerate mode:: accelerate_port = 5099 .. _accelerate_timeout: accelerate_timeout ================== .. versionadded:: 1.4 This setting controls the timeout for receiving data from a client. If no data is received during this time, the socket connection will be closed. A keepalive packet is sent back to the controller every 15 seconds, so this timeout should not be set lower than 15 (by default, the timeout is 30 seconds):: accelerate_timeout = 30 .. _accelerate_connect_timeout: accelerate_connect_timeout ========================== .. versionadded:: 1.4 This setting controls the timeout for the socket connect call, and should be kept relatively low. The connection to the `accelerate_port` will be attempted 3 times before Ansible will fall back to ssh or paramiko (depending on your default connection setting) to try and start the accelerate daemon remotely. The default setting is 1.0 seconds:: accelerate_connect_timeout = 1.0 Note, this value can be set to less than one second, however it is probably not a good idea to do so unless you're on a very fast and reliable LAN. If you're connecting to systems over the internet, it may be necessary to increase this timeout. .. _accelerate_daemon_timeout: accelerate_daemon_timeout ========================= .. versionadded:: 1.6 This setting controls the timeout for the accelerated daemon, as measured in minutes. The default daemon timeout is 30 minutes:: accelerate_daemon_timeout = 30 Note, prior to 1.6, the timeout was hard-coded from the time of the daemon's launch. For version 1.6+, the timeout is now based on the last activity to the daemon and is configurable via this option. .. _accelerate_multi_key: accelerate_multi_key ==================== .. versionadded:: 1.6 If enabled, this setting allows multiple private keys to be uploaded to the daemon. Any clients connecting to the daemon must also enable this option:: accelerate_multi_key = yes New clients first connect to the target node over SSH to upload the key, which is done via a local socket file, so they must have the same access as the user that launched the daemon originally. ansible-1.7.2/docsite/rst/intro_dynamic_inventory.rst000066400000000000000000000265631241061774000231240ustar00rootroot00000000000000.. _dynamic_inventory: Dynamic Inventory ================= .. contents:: Topics Often a user of a configuration management system will want to keep inventory in a different software system. Ansible provides a basic text-based system as described in :doc:`intro_inventory` but what if you want to use something else? Frequent examples include pulling inventory from a cloud provider, LDAP, `Cobbler `_, or a piece of expensive enterprisey CMDB software. Ansible easily supports all of these options via an external inventory system. The plugins directory contains some of these already -- including options for EC2/Eucalyptus, Rackspace Cloud, and OpenStack, examples of some of which will be detailed below. :doc:`tower` also provides a database to store inventory results that is both web and REST Accessible. Tower syncs with all Ansible dynamic inventory sources you might be using, and also includes a graphical inventory editor. By having a database record of all of your hosts, it's easy to correlate past event history and see which ones have had failures on their last playbook runs. For information about writing your own dynamic inventory source, see :doc:`developing_inventory`. .. _cobbler_example: Example: The Cobbler External Inventory Script `````````````````````````````````````````````` It is expected that many Ansible users with a reasonable amount of physical hardware may also be `Cobbler `_ users. (note: Cobbler was originally written by Michael DeHaan and is now lead by James Cammarata, who also works for Ansible, Inc). While primarily used to kickoff OS installations and manage DHCP and DNS, Cobbler has a generic layer that allows it to represent data for multiple configuration management systems (even at the same time), and has been referred to as a 'lightweight CMDB' by some admins. To tie Ansible's inventory to Cobbler (optional), copy `this script `_ to /etc/ansible and `chmod +x` the file. cobblerd will now need to be running when you are using Ansible and you'll need to use Ansible's ``-i`` command line option (e.g. ``-i /etc/ansible/cobbler.py``). This particular script will communicate with Cobbler using Cobbler's XMLRPC API. First test the script by running ``/etc/ansible/cobbler.py`` directly. You should see some JSON data output, but it may not have anything in it just yet. Let's explore what this does. In cobbler, assume a scenario somewhat like the following:: cobbler profile add --name=webserver --distro=CentOS6-x86_64 cobbler profile edit --name=webserver --mgmt-classes="webserver" --ksmeta="a=2 b=3" cobbler system edit --name=foo --dns-name="foo.example.com" --mgmt-classes="atlanta" --ksmeta="c=4" cobbler system edit --name=bar --dns-name="bar.example.com" --mgmt-classes="atlanta" --ksmeta="c=5" In the example above, the system 'foo.example.com' will be addressable by ansible directly, but will also be addressable when using the group names 'webserver' or 'atlanta'. Since Ansible uses SSH, we'll try to contact system foo over 'foo.example.com', only, never just 'foo'. Similarly, if you try "ansible foo" it wouldn't find the system... but "ansible 'foo*'" would, because the system DNS name starts with 'foo'. The script doesn't just provide host and group info. In addition, as a bonus, when the 'setup' module is run (which happens automatically when using playbooks), the variables 'a', 'b', and 'c' will all be auto-populated in the templates:: # file: /srv/motd.j2 Welcome, I am templated with a value of a={{ a }}, b={{ b }}, and c={{ c }} Which could be executed just like this:: ansible webserver -m setup ansible webserver -m template -a "src=/tmp/motd.j2 dest=/etc/motd" .. note:: The name 'webserver' came from cobbler, as did the variables for the config file. You can still pass in your own variables like normal in Ansible, but variables from the external inventory script will override any that have the same name. So, with the template above (motd.j2), this would result in the following data being written to /etc/motd for system 'foo':: Welcome, I am templated with a value of a=2, b=3, and c=4 And on system 'bar' (bar.example.com):: Welcome, I am templated with a value of a=2, b=3, and c=5 And technically, though there is no major good reason to do it, this also works too:: ansible webserver -m shell -a "echo {{ a }}" So in other words, you can use those variables in arguments/actions as well. .. _aws_example: Example: AWS EC2 External Inventory Script `````````````````````````````````````````` If you use Amazon Web Services EC2, maintaining an inventory file might not be the best approach, because hosts may come and go over time, be managed by external applications, or you might even be using AWS autoscaling. For this reason, you can use the `EC2 external inventory `_ script. You can use this script in one of two ways. The easiest is to use Ansible's ``-i`` command line option and specify the path to the script after marking it executable:: ansible -i ec2.py -u ubuntu us-east-1d -m ping The second option is to copy the script to `/etc/ansible/hosts` and `chmod +x` it. You will also need to copy the `ec2.ini `_ file to `/etc/ansible/ec2.ini`. Then you can run ansible as you would normally. To successfully make an API call to AWS, you will need to configure Boto (the Python interface to AWS). There are a `variety of methods `_ available, but the simplest is just to export two environment variables:: export AWS_ACCESS_KEY_ID='AK123' export AWS_SECRET_ACCESS_KEY='abc123' You can test the script by itself to make sure your config is correct:: cd plugins/inventory ./ec2.py --list After a few moments, you should see your entire EC2 inventory across all regions in JSON. Since each region requires its own API call, if you are only using a small set of regions, feel free to edit ``ec2.ini`` and list only the regions you are interested in. There are other config options in ``ec2.ini`` including cache control, and destination variables. At their heart, inventory files are simply a mapping from some name to a destination address. The default ``ec2.ini`` settings are configured for running Ansible from outside EC2 (from your laptop for example) -- and this is not the most efficient way to manage EC2. If you are running Ansible from within EC2, internal DNS names and IP addresses may make more sense than public DNS names. In this case, you can modify the ``destination_variable`` in ``ec2.ini`` to be the private DNS name of an instance. This is particularly important when running Ansible within a private subnet inside a VPC, where the only way to access an instance is via its private IP address. For VPC instances, `vpc_destination_variable` in ``ec2.ini`` provides a means of using which ever `boto.ec2.instance variable `_ makes the most sense for your use case. The EC2 external inventory provides mappings to instances from several groups: Global All instances are in group ``ec2``. Instance ID These are groups of one since instance IDs are unique. e.g. ``i-00112233`` ``i-a1b1c1d1`` Region A group of all instances in an AWS region. e.g. ``us-east-1`` ``us-west-2`` Availability Zone A group of all instances in an availability zone. e.g. ``us-east-1a`` ``us-east-1b`` Security Group Instances belong to one or more security groups. A group is created for each security group, with all characters except alphanumerics, dashes (-) converted to underscores (_). Each group is prefixed by ``security_group_`` e.g. ``security_group_default`` ``security_group_webservers`` ``security_group_Pete_s_Fancy_Group`` Tags Each instance can have a variety of key/value pairs associated with it called Tags. The most common tag key is 'Name', though anything is possible. Each key/value pair is its own group of instances, again with special characters converted to underscores, in the format ``tag_KEY_VALUE`` e.g. ``tag_Name_Web`` ``tag_Name_redis-master-001`` ``tag_aws_cloudformation_logical-id_WebServerGroup`` When the Ansible is interacting with a specific server, the EC2 inventory script is called again with the ``--host HOST`` option. This looks up the HOST in the index cache to get the instance ID, and then makes an API call to AWS to get information about that specific instance. It then makes information about that instance available as variables to your playbooks. Each variable is prefixed by ``ec2_``. Here are some of the variables available: - ec2_architecture - ec2_description - ec2_dns_name - ec2_id - ec2_image_id - ec2_instance_type - ec2_ip_address - ec2_kernel - ec2_key_name - ec2_launch_time - ec2_monitored - ec2_ownerId - ec2_placement - ec2_platform - ec2_previous_state - ec2_private_dns_name - ec2_private_ip_address - ec2_public_dns_name - ec2_ramdisk - ec2_region - ec2_root_device_name - ec2_root_device_type - ec2_security_group_ids - ec2_security_group_names - ec2_spot_instance_request_id - ec2_state - ec2_state_code - ec2_state_reason - ec2_status - ec2_subnet_id - ec2_tag_Name - ec2_tenancy - ec2_virtualization_type - ec2_vpc_id Both ``ec2_security_group_ids`` and ``ec2_security_group_names`` are comma-separated lists of all security groups. Each EC2 tag is a variable in the format ``ec2_tag_KEY``. To see the complete list of variables available for an instance, run the script by itself:: cd plugins/inventory ./ec2.py --host ec2-12-12-12-12.compute-1.amazonaws.com Note that the AWS inventory script will cache results to avoid repeated API calls, and this cache setting is configurable in ec2.ini. To explicitly clear the cache, you can run the ec2.py script with the ``--refresh-cache`` parameter. .. _other_inventory_scripts: Other inventory scripts ``````````````````````` In addition to Cobbler and EC2, inventory scripts are also available for:: BSD Jails Digital Ocean Google Compute Engine Linode OpenShift OpenStack Nova Red Hat's SpaceWalk Vagrant (not to be confused with the provisioner in vagrant, which is preferred) Zabbix Sections on how to use these in more detail will be added over time, but by looking at the "plugins/" directory of the Ansible checkout it should be very obvious how to use them. The process for the AWS inventory script is the same. If you develop an interesting inventory script that might be general purpose, please submit a pull request -- we'd likely be glad to include it in the project. .. _using_multiple_sources: Using Multiple Inventory Sources ```````````````````````````````` If the location given to -i in Ansible is a directory (or as so configured in ansible.cfg), Ansible can use multiple inventory sources at the same time. When doing so, it is possible to mix both dynamic and statically managed inventory sources in the same ansible run. Instant hybrid cloud! .. seealso:: :doc:`intro_inventory` All about static inventory files `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/intro_getting_started.rst000066400000000000000000000154371241061774000225500ustar00rootroot00000000000000Getting Started =============== .. contents:: Topics .. _gs_about: Foreword ```````` Now that you've read :doc:`intro_installation` and installed Ansible, it's time to dig in and get started with some commands. What we are showing first are not the powerful configuration/deployment/orchestration of Ansible, called playbooks. Playbooks are covered in a separate section. This section is about how to get going initially. Once you have these concepts down, read :doc:`intro_adhoc` for some more detail, and then you'll be ready to dive into playbooks and explore the most interesting parts! .. _remote_connection_information: Remote Connection Information ````````````````````````````` Before we get started, it's important to understand how Ansible is communicating with remote machines over SSH. By default, Ansible 1.3 and later will try to use native OpenSSH for remote communication when possible. This enables both ControlPersist (a performance feature), Kerberos, and options in ~/.ssh/config such as Jump Host setup. When using Enterprise Linux 6 operating systems as the control machine (Red Hat Enterprise Linux and derivatives such as CentOS), however, the version of OpenSSH may be too old to support ControlPersist. On these operating systems, Ansible will fallback into using a high-quality Python implementation of OpenSSH called 'paramiko'. If you wish to use features like Kerberized SSH and more, consider using Fedora, OS X, or Ubuntu as your control machine until a newer version of OpenSSH is available for your platform -- or engage 'accelerated mode' in Ansible. See :doc:`playbooks_acceleration`. In Ansible 1.2 and before, the default was strictly paramiko and native SSH had to be explicitly selected with -c ssh or set in the configuration file. Occasionally you'll encounter a device that doesn't do SFTP. This is rare, but if talking with some remote devices that don't support SFTP, you can switch to SCP mode in :doc:`intro_configuration`. When speaking with remote machines, Ansible will by default assume you are using SSH keys -- which we encourage -- but passwords are fine too. To enable password auth, supply the option ``--ask-pass`` where needed. If using sudo features and when sudo requires a password, also supply ``--ask-sudo-pass`` as appropriate. While it may be common sense, it is worth sharing: Any management system benefits from being run near the machines being managed. If running in a cloud, consider running Ansible from a machine inside that cloud. It will work better than on the open internet in most cases. As an advanced topic, Ansible doesn't just have to connect remotely over SSH. The transports are pluggable, and there are options for managing things locally, as well as managing chroot, lxc, and jail containers. A mode called 'ansible-pull' can also invert the system and have systems 'phone home' via scheduled git checkouts to pull configuration directives from a central repository. .. _your_first_commands: Your first commands ``````````````````` Now that you've installed Ansible, it's time to get started with some basics. Edit (or create) /etc/ansible/hosts and put one or more remote systems in it, for which you have your SSH key in ``authorized_keys``:: 192.168.1.50 aserver.example.org bserver.example.org This is an inventory file, which is also explained in greater depth here: :doc:`intro_inventory`. We'll assume you are using SSH keys for authentication. To set up SSH agent to avoid retyping passwords, you can do: .. code-block:: bash $ ssh-agent bash $ ssh-add ~/.ssh/id_rsa (Depending on your setup, you may wish to use Ansible's ``--private-key`` option to specify a pem file instead) Now ping all your nodes: .. code-block:: bash $ ansible all -m ping Ansible will attempt to remote connect to the machines using your current user name, just like SSH would. To override the remote user name, just use the '-u' parameter. If you would like to access sudo mode, there are also flags to do that: .. code-block:: bash # as bruce $ ansible all -m ping -u bruce # as bruce, sudoing to root $ ansible all -m ping -u bruce --sudo # as bruce, sudoing to batman $ ansible all -m ping -u bruce --sudo --sudo-user batman (The sudo implementation is changeable in Ansible's configuration file if you happen to want to use a sudo replacement. Flags passed to sudo (like -H) can also be set there.) Now run a live command on all of your nodes: .. code-block:: bash $ ansible all -a "/bin/echo hello" Congratulations. You've just contacted your nodes with Ansible. It's soon going to be time to read some of the more real-world :doc:`intro_adhoc`, and explore what you can do with different modules, as well as the Ansible :doc:`playbooks` language. Ansible is not just about running commands, it also has powerful configuration management and deployment features. There's more to explore, but you already have a fully working infrastructure! .. _a_note_about_host_key_checking: Host Key Checking ````````````````` Ansible 1.2.1 and later have host key checking enabled by default. If a host is reinstalled and has a different key in 'known_hosts', this will result in an error message until corrected. If a host is not initially in 'known_hosts' this will result in prompting for confirmation of the key, which results in an interactive experience if using Ansible, from say, cron. You might not want this. If you wish to disable this behavior and understand the implications, you can do so by editing /etc/ansible/ansible.cfg or ~/.ansible.cfg:: [defaults] host_key_checking = False Alternatively this can be set by an environment variable: .. code-block:: bash $ export ANSIBLE_HOST_KEY_CHECKING=False Also note that host key checking in paramiko mode is reasonably slow, therefore switching to 'ssh' is also recommended when using this feature. .. _a_note_about_logging: Ansible will log some information about module arguments on the remote system in the remote syslog. To enable basic logging on the control machine see :doc:`intro_configuration` document and set the 'log_path' configuration file setting. Enterprise users may also be interested in :doc:`tower`. Tower provides a very robust database logging feature where it is possible to drill down and see history based on hosts, projects, and particular inventories over time -- explorable both graphically and through a REST API. .. seealso:: :doc:`intro_inventory` More information about inventory :doc:`intro_adhoc` Examples of basic commands :doc:`playbooks` Learning Ansible's configuration management language `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/intro_installation.rst000066400000000000000000000221421241061774000220510ustar00rootroot00000000000000Installation ============ .. contents:: Topics .. _getting_ansible: Getting Ansible ``````````````` You may also wish to follow the `Github project `_ if you have a github account. This is also where we keep the issue tracker for sharing bugs and feature ideas. .. _what_will_be_installed: Basics / What Will Be Installed ``````````````````````````````` Ansible by default manages machines over the SSH protocol. Once Ansible is installed, it will not add a database, and there will be no daemons to start or keep running. You only need to install it on one machine (which could easily be a laptop) and it can manage an entire fleet of remote machines from that central point. When Ansible manages remote machines, it does not leave software installed or running on them, so there's no real question about how to upgrade Ansible when moving to a new version. .. _what_version: What Version To Pick? ````````````````````` Because it runs so easily from source and does not require any installation of software on remote machines, many users will actually track the development version. Ansible's release cycles are usually about two months long. Due to this short release cycle, minor bugs will generally be fixed in the next release versus maintaining backports on the stable branch. Major bugs will still have maintenance releases when needed, though these are infrequent. If you are wishing to run the latest released version of Ansible and you are running Red Hat Enterprise Linux (TM), CentOS, Fedora, Debian, or Ubuntu, we recommend using the OS package manager. For other installation options, we recommend installing via "pip", which is the Python package manager, though other options are also available. If you wish to track the development release to use and test the latest features, we will share information about running from source. It's not necessary to install the program to run from source. .. _control_machine_requirements: Control Machine Requirements ```````````````````````````` Currently Ansible can be run from any machine with Python 2.6 installed (Windows isn't supported for the control machine). This includes Red Hat, Debian, CentOS, OS X, any of the BSDs, and so on. .. _managed_node_requirements: Managed Node Requirements ````````````````````````` On the managed nodes, you only need Python 2.4 or later, but if you are running less than Python 2.5 on the remotes, you will also need: * ``python-simplejson`` .. note:: Ansible's "raw" module (for executing commands in a quick and dirty way) and the script module don't even need that. So technically, you can use Ansible to install python-simplejson using the raw module, which then allows you to use everything else. (That's jumping ahead though.) .. note:: If you have SELinux enabled on remote nodes, you will also want to install libselinux-python on them before using any copy/file/template related functions in Ansible. You can of course still use the yum module in Ansible to install this package on remote systems that do not have it. .. note:: Python 3 is a slightly different language than Python 2 and most Python programs (including Ansible) are not switching over yet. However, some Linux distributions (Gentoo, Arch) may not have a Python 2.X interpreter installed by default. On those systems, you should install one, and set the 'ansible_python_interpreter' variable in inventory (see :doc:`intro_inventory`) to point at your 2.X Python. Distributions like Red Hat Enterprise Linux, CentOS, Fedora, and Ubuntu all have a 2.X interpreter installed by default and this does not apply to those distributions. This is also true of nearly all Unix systems. If you need to bootstrap these remote systems by installing Python 2.X, using the 'raw' module will be able to do it remotely. .. _installing_the_control_machine: Installing the Control Machine `````````````````````````````` .. _from_source: Running From Source +++++++++++++++++++ Ansible is trivially easy to run from a checkout, root permissions are not required to use it and there is no software to actually install for Ansible itself. No daemons or database setup are required. Because of this, many users in our community use the development version of Ansible all of the time, so they can take advantage of new features when they are implemented, and also easily contribute to the project. Because there is nothing to install, following the development version is significantly easier than most open source projects. To install from source. .. code-block:: bash $ git clone git://github.com/ansible/ansible.git $ cd ./ansible $ source ./hacking/env-setup If you don't have pip installed in your version of Python, install pip:: $ sudo easy_install pip Ansible also uses the following Python modules that need to be installed:: $ sudo pip install paramiko PyYAML jinja2 httplib2 Once running the env-setup script you'll be running from checkout and the default inventory file will be /etc/ansible/hosts. You can optionally specify an inventory file (see :doc:`intro_inventory`) other than /etc/ansible/hosts: .. code-block:: bash $ echo "127.0.0.1" > ~/ansible_hosts $ export ANSIBLE_HOSTS=~/ansible_hosts You can read more about the inventory file in later parts of the manual. Now let's test things with a ping command: .. code-block:: bash $ ansible all -m ping --ask-pass You can also use "sudo make install" if you wish. .. _from_yum: Latest Release Via Yum ++++++++++++++++++++++ RPMs are available from yum for `EPEL `_ 6, 7, and currently supported Fedora distributions. Ansible itself can manage earlier operating systems that contain Python 2.4 or higher (so also EL5). Fedora users can install Ansible directly, though if you are using RHEL or CentOS and have not already done so, `configure EPEL `_ .. code-block:: bash # install the epel-release RPM if needed on CentOS, RHEL, or Scientific Linux $ sudo yum install ansible You can also build an RPM yourself. From the root of a checkout or tarball, use the ``make rpm`` command to build an RPM you can distribute and install. Make sure you have ``rpm-build``, ``make``, and ``python2-devel`` installed. .. code-block:: bash $ git clone git://github.com/ansible/ansible.git $ cd ./ansible $ make rpm $ sudo rpm -Uvh ~/rpmbuild/ansible-*.noarch.rpm .. _from_apt: Latest Releases Via Apt (Ubuntu) ++++++++++++++++++++++++++++++++ Ubuntu builds are available `in a PPA here `_. To configure the PPA on your machine and install ansible run these commands: .. code-block:: bash $ sudo apt-get install software-properties-common $ sudo apt-add-repository ppa:ansible/ansible $ sudo apt-get update $ sudo apt-get install ansible .. note:: On older Ubuntu distributions, "software-properties-common" is called "python-software-properties". Debian/Ubuntu packages can also be built from the source checkout, run: .. code-block:: bash $ make deb You may also wish to run from source to get the latest, which is covered above. .. _from_pkg: Latest Releases Via pkg (FreeBSD) +++++++++++++++++++++++++++++++++ .. code-block:: bash $ sudo pkg install ansible You may also wish to install from ports, run: .. code-block:: bash $ sudo make -C /usr/ports/sysutils/ansible install .. _from_brew: Latest Releases Via Homebrew (Mac OSX) ++++++++++++++++++++++++++++++++++++++ To install on a Mac, make sure you have Homebrew, then run: .. code-block:: bash $ brew update $ brew install ansible .. _from_pip: Latest Releases Via Pip +++++++++++++++++++++++ Ansible can be installed via "pip", the Python package manager. If 'pip' isn't already available in your version of Python, you can get pip by:: $ sudo easy_install pip Then install Ansible with:: $ sudo pip install ansible If you are installing on OS X Mavericks, you may encounter some noise from your compiler. A workaround is to do the following:: $ sudo CFLAGS=-Qunused-arguments CPPFLAGS=-Qunused-arguments pip install ansible Readers that use virtualenv can also install Ansible under virtualenv, though we'd recommend to not worry about it and just install Ansible globally. Do not use easy_install to install ansible directly. .. _tagged_releases: Tarballs of Tagged Releases +++++++++++++++++++++++++++ Packaging Ansible or wanting to build a local package yourself, but don't want to do a git checkout? Tarballs of releases are available on the `Ansible downloads `_ page. These releases are also tagged in the `git repository `_ with the release version. .. seealso:: :doc:`intro_adhoc` Examples of basic commands :doc:`playbooks` Learning ansible's configuration management language `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/intro_inventory.rst000066400000000000000000000207631241061774000214140ustar00rootroot00000000000000.. _inventory: Inventory ========= .. contents:: Topics Ansible works against multiple systems in your infrastructure at the same time. It does this by selecting portions of systems listed in Ansible's inventory file, which defaults to being saved in the location /etc/ansible/hosts. Not only is this inventory configurable, but you can also use multiple inventory files at the same time (explained below) and also pull inventory from dynamic or cloud sources, as described in :doc:`intro_dynamic_inventory`. .. _inventoryformat: Hosts and Groups ++++++++++++++++ The format for /etc/ansible/hosts is an INI format and looks like this:: mail.example.com [webservers] foo.example.com bar.example.com [dbservers] one.example.com two.example.com three.example.com The things in brackets are group names, which are used in classifying systems and deciding what systems you are controlling at what times and for what purpose. It is ok to put systems in more than one group, for instance a server could be both a webserver and a dbserver. If you do, note that variables will come from all of the groups they are a member of, and variable precedence is detailed in a later chapter. If you have hosts that run on non-standard SSH ports you can put the port number after the hostname with a colon. Ports listed in your SSH config file won't be used with the paramiko connection but will be used with the openssh connection. To make things explicit, it is suggested that you set them if things are not running on the default port:: badwolf.example.com:5309 Suppose you have just static IPs and want to set up some aliases that don't live in your host file, or you are connecting through tunnels. You can do things like this:: jumper ansible_ssh_port=5555 ansible_ssh_host=192.168.1.50 In the above example, trying to ansible against the host alias "jumper" (which may not even be a real hostname) will contact 192.168.1.50 on port 5555. Note that this is using a feature of the inventory file to define some special variables. Generally speaking this is not the best way to define variables that describe your system policy, but we'll share suggestions on doing this later. We're just getting started. Adding a lot of hosts? If you have a lot of hosts following similar patterns you can do this rather than listing each hostname:: [webservers] www[01:50].example.com For numeric patterns, leading zeros can be included or removed, as desired. Ranges are inclusive. You can also define alphabetic ranges:: [databases] db-[a:f].example.com You can also select the connection type and user on a per host basis:: [targets] localhost ansible_connection=local other1.example.com ansible_connection=ssh ansible_ssh_user=mpdehaan other2.example.com ansible_connection=ssh ansible_ssh_user=mdehaan As mentioned above, setting these in the inventory file is only a shorthand, and we'll discuss how to store them in individual files in the 'host_vars' directory a bit later on. .. _host_variables: Host Variables ++++++++++++++ As alluded to above, it is easy to assign variables to hosts that will be used later in playbooks:: [atlanta] host1 http_port=80 maxRequestsPerChild=808 host2 http_port=303 maxRequestsPerChild=909 .. _group_variables: Group Variables +++++++++++++++ Variables can also be applied to an entire group at once:: [atlanta] host1 host2 [atlanta:vars] ntp_server=ntp.atlanta.example.com proxy=proxy.atlanta.example.com .. _subgroups: Groups of Groups, and Group Variables +++++++++++++++++++++++++++++++++++++ It is also possible to make groups of groups and assign variables to groups. These variables can be used by /usr/bin/ansible-playbook, but not /usr/bin/ansible:: [atlanta] host1 host2 [raleigh] host2 host3 [southeast:children] atlanta raleigh [southeast:vars] some_server=foo.southeast.example.com halon_system_timeout=30 self_destruct_countdown=60 escape_pods=2 [usa:children] southeast northeast southwest northwest If you need to store lists or hash data, or prefer to keep host and group specific variables separate from the inventory file, see the next section. .. _splitting_out_vars: Splitting Out Host and Group Specific Data ++++++++++++++++++++++++++++++++++++++++++ The preferred practice in Ansible is actually not to store variables in the main inventory file. In addition to storing variables directly in the INI file, host and group variables can be stored in individual files relative to the inventory file. These variable files are in YAML format. See :doc:`YAMLSyntax` if you are new to YAML. Assuming the inventory file path is:: /etc/ansible/hosts If the host is named 'foosball', and in groups 'raleigh' and 'webservers', variables in YAML files at the following locations will be made available to the host:: /etc/ansible/group_vars/raleigh /etc/ansible/group_vars/webservers /etc/ansible/host_vars/foosball For instance, suppose you have hosts grouped by datacenter, and each datacenter uses some different servers. The data in the groupfile '/etc/ansible/group_vars/raleigh' for the 'raleigh' group might look like:: --- ntp_server: acme.example.org database_server: storage.example.org It is ok if these files do not exist, as this is an optional feature. Tip: In Ansible 1.2 or later the group_vars/ and host_vars/ directories can exist in either the playbook directory OR the inventory directory. If both paths exist, variables in the playbook directory will be loaded second. Tip: Keeping your inventory file and variables in a git repo (or other version control) is an excellent way to track changes to your inventory and host variables. .. _behavioral_parameters: List of Behavioral Inventory Parameters +++++++++++++++++++++++++++++++++++++++ As alluded to above, setting the following variables controls how ansible interacts with remote hosts. Some we have already mentioned:: ansible_ssh_host The name of the host to connect to, if different from the alias you wish to give to it. ansible_ssh_port The ssh port number, if not 22 ansible_ssh_user The default ssh user name to use. ansible_ssh_pass The ssh password to use (this is insecure, we strongly recommend using --ask-pass or SSH keys) ansible_sudo_pass The sudo password to use (this is insecure, we strongly recommend using --ask-sudo-pass) ansible_connection Connection type of the host. Candidates are local, ssh or paramiko. The default is paramiko before Ansible 1.2, and 'smart' afterwards which detects whether usage of 'ssh' would be feasible based on whether ControlPersist is supported. ansible_ssh_private_key_file Private key file used by ssh. Useful if using multiple keys and you don't want to use SSH agent. ansible_shell_type The shell type of the target system. By default commands are formatted using 'sh'-style syntax by default. Setting this to 'csh' or 'fish' will cause commands executed on target systems to follow those shell's syntax instead. ansible_python_interpreter The target host python path. This is useful for systems with more than one Python or not located at "/usr/bin/python" such as \*BSD, or where /usr/bin/python is not a 2.X series Python. We do not use the "/usr/bin/env" mechanism as that requires the remote user's path to be set right and also assumes the "python" executable is named python, where the executable might be named something like "python26". ansible\_\*\_interpreter Works for anything such as ruby or perl and works just like ansible_python_interpreter. This replaces shebang of modules which will run on that host. Examples from a host file:: some_host ansible_ssh_port=2222 ansible_ssh_user=manager aws_host ansible_ssh_private_key_file=/home/example/.ssh/aws.pem freebsd_host ansible_python_interpreter=/usr/local/bin/python ruby_module_host ansible_ruby_interpreter=/usr/bin/ruby.1.9.3 .. seealso:: :doc:`intro_dynamic_inventory` Pulling inventory from dynamic sources, such as cloud providers :doc:`intro_adhoc` Examples of basic commands :doc:`playbooks` Learning ansible's configuration management language `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/intro_patterns.rst000066400000000000000000000062271241061774000212160ustar00rootroot00000000000000Patterns ++++++++ .. contents:: Topics Patterns in Ansible are how we decide which hosts to manage. This can mean what hosts to communicate with, but in terms of :doc:`playbooks` it actually means what hosts to apply a particular configuration or IT process to. We'll go over how to use the command line in :doc:`intro_adhoc` section, however, basically it looks like this:: ansible -m -a Such as:: ansible webservers -m service -a "name=httpd state=restarted" A pattern usually refers to a set of groups (which are sets of hosts) -- in the above case, machines in the "webservers" group. Anyway, to use Ansible, you'll first need to know how to tell Ansible which hosts in your inventory to talk to. This is done by designating particular host names or groups of hosts. The following patterns are equivalent and target all hosts in the inventory:: all * It is also possible to address a specific host or set of hosts by name:: one.example.com one.example.com:two.example.com 192.168.1.50 192.168.1.* The following patterns address one or more groups. Groups separated by a colon indicate an "OR" configuration. This means the host may be in either one group or the other:: webservers webservers:dbservers You can exclude groups as well, for instance, all machines must be in the group webservers but not in the group phoenix:: webservers:!phoenix You can also specify the intersection of two groups. This would mean the hosts must be in the group webservers and the host must also be in the group staging:: webservers:&staging You can do combinations:: webservers:dbservers:&staging:!phoenix The above configuration means "all machines in the groups 'webservers' and 'dbservers' are to be managed if they are in the group 'staging' also, but the machines are not to be managed if they are in the group 'phoenix' ... whew! You can also use variables if you want to pass some group specifiers via the "-e" argument to ansible-playbook, but this is uncommonly used:: webservers:!{{excluded}}:&{{required}} You also don't have to manage by strictly defined groups. Individual host names, IPs and groups, can also be referenced using wildcards:: *.example.com *.com It's also ok to mix wildcard patterns and groups at the same time:: one*.com:dbservers Most people don't specify patterns as regular expressions, but you can. Just start the pattern with a '~':: ~(web|db).*\.example\.com While we're jumping a bit ahead, additionally, you can add an exclusion criteria just by supplying the ``--limit`` flag to /usr/bin/ansible or /usr/bin/ansible-playbook:: ansible-playbook site.yml --limit datacenter2 Easy enough. See :doc:`intro_adhoc` and then :doc:`playbooks` for how to apply this knowledge. .. seealso:: :doc:`intro_adhoc` Examples of basic commands :doc:`playbooks` Learning ansible's configuration management language `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/intro_windows.rst000066400000000000000000000226661241061774000210550ustar00rootroot00000000000000Windows Support =============== .. contents:: Topics .. _windows_how_does_it_work: Windows: How Does It Work ````````````````````````` As you may have already read, Ansible manages Linux/Unix machines using SSH by default. Starting in version 1.7, Ansible also contains support for managing Windows machines. This uses native powershell remoting, rather than SSH. Ansible will still be run from a Linux control machine, and uses the "winrm" Python module to talk to remote hosts. No additional software needs to be installed on the remote machines for Ansible to manage them, it still maintains the agentless properties that make it popular on Linux/Unix. Note that it is expected you have a basic understanding of Ansible prior to jumping into this section, so if you haven't written a Linux playbook first, it might be worthwhile to dig in there first. .. _windows_installing: Installing on the Control Machine `````````````````````````````````` On a Linux control machine:: pip install http://github.com/diyan/pywinrm/archive/master.zip#egg=pywinrm .. _windows_inventory: Inventory ````````` Ansible's windows support relies on a few standard variables to indicate the username, password, and connection type (windows) of the remote hosts. These variables are most easily set up in inventory. This is used instead of SSH-keys or passwords as normally fed into Ansible:: [windows] winserver1.example.com winserver2.example.com In group_vars/windows.yml, define the following inventory variables:: # it is suggested that these be encrypted with ansible-vault: # ansible-vault edit group_vars/windows.yml ansible_ssh_user: Administrator ansible_ssh_pass: SekritPasswordGoesHere ansible_ssh_port: 5986 ansible_connection: winrm Notice that the ssh_port is not actually for SSH, but this is a holdover variable name from how Ansible is mostly an SSH-oriented system. Again, Windows management will not happen over SSH. When using your playbook, don't forget to specify --ask-vault-pass to provide the password to unlock the file. Test your configuration like so, by trying to contact your Windows nodes. Note this is not an ICMP ping, but tests the Ansible communication channel that leverages Windows remoting:: ansible windows [-i inventory] -m win_ping --ask-vault-pass If you haven't done anything to prep your systems yet, this won't work yet. This is covered in a later section about how to enable powershell remoting - and if neccessary - how to upgrade powershell to a version that is 3 or higher. You'll run this command again later though, to make sure everything is working. .. _windows_system_prep: Windows System Prep ``````````````````` In order for Ansible to manage your windows machines, you will have to enable Powershell remoting configured. To automate setup of WinRM, you can run `this powershell script `_ on the remote machine. Admins may wish to modify this setup slightly, for instance to increase the timeframe of the certificate. .. _getting_to_powershell_three_or_higher: Getting to Powershell 3.0 or higher ``````````````````````````````````` Powershell 3.0 or higher is needed for most provided Ansible modules for Windows, and is also required to run the above setup script. Looking at an ansible checkout, copy the `examples/scripts/upgrade_to_ps3.ps1 `_ script onto the remote host and run a powershell console as an administrator. You will now be running Powershell 3 and can try connectivity again using the win_ping technique referenced above. .. _what_windows_modules_are_available: What modules are available `````````````````````````` Most of the Ansible modules in core Ansible are written for a combination of Linux/Unix machines and arbitrary web services, though there are various Windows modules as listed in the `"windows" subcategory of the Ansible module index `_. Browse this index to see what is available. In many cases, it may not be neccessary to even write or use an Ansible module. In particular, the "script" module can be used to run arbitrary powershell scripts, allowing Windows administrators familiar with powershell a very native way to do things, as in the following playbook:: - hosts: windows tasks: - script: foo.ps1 --argument --other-argument Note there are a few other Ansible modules that don't start with "win" that also function, including "slurp", "raw", and "setup" (which is how fact gathering works). .. _developers_developers_developers: Developers: Supported modules and how it works `````````````````````````````````````````````` Developing ansible modules are covered in a `later section of the documentation `_, with a focus on Linux/Unix. What if you want to write Windows modules for ansible though? For Windows, ansible modules are implemented in Powershell. Skim those Linux/Unix module development chapters before proceeding. Windows modules live in a "windows/" subfolder in the Ansible "library/" subtree. For example, if a module is named "library/windows/win_ping", there will be embedded documentation in the "win_ping" file, and the actual powershell code will live in a "win_ping.ps1" file. Take a look at the sources and this will make more sense. Modules (ps1 files) should start as follows:: #!powershell # # WANT_JSON # POWERSHELL_COMMON # code goes here, reading in stdin as JSON and outputting JSON The above magic is neccessary to tell Ansible to mix in some common code and also know how to push modules out. The common code contains some nice wrappers around working with hash data structures and emitting JSON results, and possibly a few mpmore useful things. Regular Ansible has this same concept for reusing Python code - this is just the windows equivalent. What modules you see in windows/ are just a start. Additional modules may be submitted as pull requests to github. .. _windows_and_linux_control_machine: Reminder: You Must Have a Linux Control Machine ``````````````````````````````````````````````` Note running Ansible from a Windows control machine is NOT a goal of the project. Refrain from asking for this feature, as it limits what technologies, features, and code we can use in the main project in the future. A Linux control machine will be required to manage Windows hosts. Cygwin is not supported, so please do not ask questions about Ansible running from Cygwin. .. _windows_facts: Windows Facts ````````````` Just as with Linux/Unix, facts can be gathered for windows hosts, which will return things such as the operating system version. To see what variables are available about a windows host, run the following:: ansible winhost.example.com -m setup Note that this command invocation is exactly the same as the Linux/Unix equivalent. .. _windows_playbook_example: Windows Playbook Examples ````````````````````````` Look to the list of windows modules for most of what is possible, though also some modules like "raw" and "script" also work on Windows, as do "fetch" and "slurp". Here is an example of pushing and running a powershell script:: - name: test script module hosts: windows tasks: - name: run test script script: files/test_script.ps1 Running individual commands uses the 'raw' module, as opposed to the shell or command module as is common on Linux/Unix operating systems:: - name: test raw module hosts: windows tasks: - name: run ipconfig raw: ipconfig register: ipconfig - debug: var=ipconfig And for a final example, here's how to use the win_stat module to test for file existance. Note that the data returned byt he win_stat module is slightly different than what is provided by the Linux equivalent:: - name: test stat module hosts: windows tasks: - name: test stat module on file win_stat: path="C:/Windows/win.ini" register: stat_file - debug: var=stat_file - name: check stat_file result assert: that: - "stat_file.stat.exists" - "not stat_file.stat.isdir" - "stat_file.stat.size > 0" - "stat_file.stat.md5" Again, recall that the Windows modules are all listed in the Windows category of modules, with the exception that the "raw", "script", and "fetch" modules are also available. These modules do not start with a "win" prefix. .. _windows_contributions: Windows Contributions ````````````````````` Windows support in Ansible is still very new, and contributions are quite welcome, whether this is in the form of new modules, tweaks to existing modules, documentation, or something else. Please stop by the ansible-devel mailing list if you would like to get involved and say hi. .. seealso:: :doc:`developing_modules` How to write modules :doc:`playbooks` Learning ansible's configuration management language `List of Windows Modules `_ Windows specific module list, all implemented in powershell `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/modules.rst000066400000000000000000000044401241061774000176060ustar00rootroot00000000000000About Modules ============= .. toctree:: :maxdepth: 4 .. _modules_intro: Introduction ```````````` Ansible ships with a number of modules (called the 'module library') that can be executed directly on remote hosts or through :doc:`Playbooks `. Users can also write their own modules. These modules can control system resources, like services, packages, or files (anything really), or handle executing system commands. Let's review how we execute three different modules from the command line:: ansible webservers -m service -a "name=httpd state=started" ansible webservers -m ping ansible webservers -m command -a "/sbin/reboot -t now" Each module supports taking arguments. Nearly all modules take ``key=value`` arguments, space delimited. Some modules take no arguments, and the command/shell modules simply take the string of the command you want to run. From playbooks, Ansible modules are executed in a very similar way:: - name: reboot the servers action: command /sbin/reboot -t now Which can be abbreviated to:: - name: reboot the servers command: /sbin/reboot -t now All modules technically return JSON format data, though if you are using the command line or playbooks, you don't really need to know much about that. If you're writing your own module, you care, and this means you do not have to write modules in any particular language -- you get to choose. Modules are `idempotent`, meaning they will seek to avoid changes to the system unless a change needs to be made. When using Ansible playbooks, these modules can trigger 'change events' in the form of notifying 'handlers' to run additional tasks. Documentation for each module can be accessed from the command line with the ansible-doc tool:: ansible-doc yum .. seealso:: :doc:`intro_adhoc` Examples of using modules in /usr/bin/ansible :doc:`playbooks` Examples of using modules with /usr/bin/ansible-playbook :doc:`developing_modules` How to write your own modules :doc:`developing_api` Examples of using modules with the Python API `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/modules/000077500000000000000000000000001241061774000170525ustar00rootroot00000000000000ansible-1.7.2/docsite/rst/modules/.gitdir000066400000000000000000000000001241061774000203230ustar00rootroot00000000000000ansible-1.7.2/docsite/rst/playbooks.rst000066400000000000000000000026221241061774000201410ustar00rootroot00000000000000Playbooks ````````` Playbooks are Ansible's configuration, deployment, and orchestration language. They can describe a policy you want your remote systems to enforce, or a set of steps in a general IT process. If Ansible modules are the tools in your workshop, playbooks are your design plans. At a basic level, playbooks can be used to manage configurations of and deployments to remote machines. At a more advanced level, they can sequence multi-tier rollouts involving rolling updates, and can delegate actions to other hosts, interacting with monitoring servers and load balancers along the way. While there's a lot of information here, there's no need to learn everything at once. You can start small and pick up more features over time as you need them. Playbooks are designed to be human-readable and are developed in a basic text language. There are multiple ways to organize playbooks and the files they include, and we'll offer up some suggestions on that and making the most out of Ansible. It is recommended to look at `Example Playbooks `_ while reading along with the playbook documentation. These illustrate best practices as well as how to put many of the various concepts together. .. toctree:: :maxdepth: 1 playbooks_intro playbooks_roles playbooks_variables playbooks_conditionals playbooks_loops playbooks_best_practices ansible-1.7.2/docsite/rst/playbooks_acceleration.rst000066400000000000000000000102041241061774000226450ustar00rootroot00000000000000Accelerated Mode ================ .. versionadded:: 1.3 You Might Not Need This! ```````````````````````` Are you running Ansible 1.5 or later? If so, you may not need accelerate mode due to a new feature called "SSH pipelining" and should read the :ref:`pipelining` section of the documentation. For users on 1.5 and later, accelerate mode only makes sense if you (A) are managing from an Enterprise Linux 6 or earlier host and still are on paramiko, or (B) can't enable TTYs with sudo as described in the pipelining docs. If you can use pipelining, Ansible will reduce the amount of files transferred over the wire, making everything much more efficient, and performance will be on par with accelerate mode in nearly all cases, possibly excluding very large file transfer. Because less moving parts are involved, pipelining is better than accelerate mode for nearly all use cases. Accelerate mode remains around in support of EL6 control machines and other constrained environments. Accelerate Mode Details ``````````````````````` While OpenSSH using the ControlPersist feature is quite fast and scalable, there is a certain small amount of overhead involved in using SSH connections. While many people will not encounter a need, if you are running on a platform that doesn't have ControlPersist support (such as an EL6 control machine), you'll probably be even more interested in tuning options. Accelerate mode is there to help connections work faster, but still uses SSH for initial secure key exchange. There is no additional public key infrastructure to manage, and this does not require things like NTP or even DNS. Accelerated mode can be anywhere from 2-6x faster than SSH with ControlPersist enabled, and 10x faster than paramiko. Accelerated mode works by launching a temporary daemon over SSH. Once the daemon is running, Ansible will connect directly to it via a socket connection. Ansible secures this communication by using a temporary AES key that is exchanged during the SSH connection (this key is different for every host, and is also regenerated periodically). By default, Ansible will use port 5099 for the accelerated connection, though this is configurable. Once running, the daemon will accept connections for 30 minutes, after which time it will terminate itself and need to be restarted over SSH. Accelerated mode offers several improvements over the (deprecated) original fireball mode from which it was based: * No bootstrapping is required, only a single line needs to be added to each play you wish to run in accelerated mode. * Support for sudo commands (see below for more details and caveats) is available. * There are fewer requirements. ZeroMQ is no longer required, nor are there any special packages beyond python-keyczar * python 2.5 or higher is required. In order to use accelerated mode, simply add `accelerate: true` to your play:: --- - hosts: all accelerate: true tasks: - name: some task command: echo {{ item }} with_items: - foo - bar - baz If you wish to change the port Ansible will use for the accelerated connection, just add the `accelerated_port` option:: --- - hosts: all accelerate: true # default port is 5099 accelerate_port: 10000 The `accelerate_port` option can also be specified in the environment variable ACCELERATE_PORT, or in your `ansible.cfg` configuration:: [accelerate] accelerate_port = 5099 As noted above, accelerated mode also supports running tasks via sudo, however there are two important caveats: * You must remove requiretty from your sudoers options. * Prompting for the sudo password is not yet supported, so the NOPASSWD option is required for sudo'ed commands. As of Ansible version `1.6`, you can also allow the use of multiple keys for connections from multiple Ansible management nodes. To do so, add the following option to your `ansible.cfg` configuration:: accelerate_multi_key = yes When enabled, the daemon will open a UNIX socket file (by default `$ANSIBLE_REMOTE_TEMP/.ansible-accelerate/.local.socket`). New connections over SSH can use this socket file to upload new keys to the daemon. ansible-1.7.2/docsite/rst/playbooks_async.rst000066400000000000000000000040111241061774000213300ustar00rootroot00000000000000Asynchronous Actions and Polling ================================ By default tasks in playbooks block, meaning the connections stay open until the task is done on each node. This may not always be desirable, or you may be running operations that take longer than the SSH timeout. The easiest way to do this is to kick them off all at once and then poll until they are done. You will also want to use asynchronous mode on very long running operations that might be subject to timeout. To launch a task asynchronously, specify its maximum runtime and how frequently you would like to poll for status. The default poll value is 10 seconds if you do not specify a value for `poll`:: --- - hosts: all remote_user: root tasks: - name: simulate long running op (15 sec), wait for up to 45 sec, poll every 5 sec command: /bin/sleep 15 async: 45 poll: 5 .. note:: There is no default for the async time limit. If you leave off the 'async' keyword, the task runs synchronously, which is Ansible's default. Alternatively, if you do not need to wait on the task to complete, you may "fire and forget" by specifying a poll value of 0:: --- - hosts: all remote_user: root tasks: - name: simulate long running op, allow to run for 45 sec, fire and forget command: /bin/sleep 15 async: 45 poll: 0 .. note:: You shouldn't "fire and forget" with operations that require exclusive locks, such as yum transactions, if you expect to run other commands later in the playbook against those same resources. .. note:: Using a higher value for ``--forks`` will result in kicking off asynchronous tasks even faster. This also increases the efficiency of polling. .. seealso:: :doc:`playbooks` An introduction to playbooks `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/playbooks_best_practices.rst000066400000000000000000000321601241061774000232130ustar00rootroot00000000000000Best Practices ============== Here are some tips for making the most of Ansible playbooks. You can find some example playbooks illustrating these best practices in our `ansible-examples repository `_. (NOTE: These may not use all of the features in the latest release, but are still an excellent reference!). .. contents:: Topics .. _content_organization: Content Organization ++++++++++++++++++++++ The following section shows one of many possible ways to organize playbook content. Your usage of Ansible should fit your needs, however, not ours, so feel free to modify this approach and organize as you see fit. (One thing you will definitely want to do though, is use the "roles" organization feature, which is documented as part of the main playbooks page. See :doc:`playbooks_roles`). .. _directory_layout: Directory Layout ```````````````` The top level of the directory would contain files and directories like so:: production # inventory file for production servers stage # inventory file for stage environment group_vars/ group1 # here we assign variables to particular groups group2 # "" host_vars/ hostname1 # if systems need specific variables, put them here hostname2 # "" site.yml # master playbook webservers.yml # playbook for webserver tier dbservers.yml # playbook for dbserver tier roles/ common/ # this hierarchy represents a "role" tasks/ # main.yml # <-- tasks file can include smaller files if warranted handlers/ # main.yml # <-- handlers file templates/ # <-- files for use with the template resource ntp.conf.j2 # <------- templates end in .j2 files/ # bar.txt # <-- files for use with the copy resource foo.sh # <-- script files for use with the script resource vars/ # main.yml # <-- variables associated with this role meta/ # main.yml # <-- role dependencies webtier/ # same kind of structure as "common" was above, done for the webtier role monitoring/ # "" fooapp/ # "" .. _stage_vs_prod: How to Arrange Inventory, Stage vs Production ````````````````````````````````````````````` In the example below, the *production* file contains the inventory of all of your production hosts. Of course you can pull inventory from an external data source as well, but this is just a basic example. It is suggested that you define groups based on purpose of the host (roles) and also geography or datacenter location (if applicable):: # file: production [atlanta-webservers] www-atl-1.example.com www-atl-2.example.com [boston-webservers] www-bos-1.example.com www-bos-2.example.com [atlanta-dbservers] db-atl-1.example.com db-atl-2.example.com [boston-dbservers] db-bos-1.example.com # webservers in all geos [webservers:children] atlanta-webservers boston-webservers # dbservers in all geos [dbservers:children] atlanta-dbservers boston-dbservers # everything in the atlanta geo [atlanta:children] atlanta-webservers atlanta-dbservers # everything in the boston geo [boston:children] boston-webservers boston-dbservers .. _groups_and_hosts: Group And Host Variables ```````````````````````` Now, groups are nice for organization, but that's not all groups are good for. You can also assign variables to them! For instance, atlanta has its own NTP servers, so when setting up ntp.conf, we should use them. Let's set those now:: --- # file: group_vars/atlanta ntp: ntp-atlanta.example.com backup: backup-atlanta.example.com Variables aren't just for geographic information either! Maybe the webservers have some configuration that doesn't make sense for the database servers:: --- # file: group_vars/webservers apacheMaxRequestsPerChild: 3000 apacheMaxClients: 900 If we had any default values, or values that were universally true, we would put them in a file called group_vars/all:: --- # file: group_vars/all ntp: ntp-boston.example.com backup: backup-boston.example.com We can define specific hardware variance in systems in a host_vars file, but avoid doing this unless you need to:: --- # file: host_vars/db-bos-1.example.com foo_agent_port: 86 bar_agent_port: 99 .. _split_by_role: Top Level Playbooks Are Separated By Role ````````````````````````````````````````` In site.yml, we include a playbook that defines our entire infrastructure. Note this is SUPER short, because it's just including some other playbooks. Remember, playbooks are nothing more than lists of plays:: --- # file: site.yml - include: webservers.yml - include: dbservers.yml In a file like webservers.yml (also at the top level), we simply map the configuration of the webservers group to the roles performed by the webservers group. Also notice this is incredibly short. For example:: --- # file: webservers.yml - hosts: webservers roles: - common - webtier .. _role_organization: Task And Handler Organization For A Role ```````````````````````````````````````` Below is an example tasks file that explains how a role works. Our common role here just sets up NTP, but it could do more if we wanted:: --- # file: roles/common/tasks/main.yml - name: be sure ntp is installed yum: pkg=ntp state=installed tags: ntp - name: be sure ntp is configured template: src=ntp.conf.j2 dest=/etc/ntp.conf notify: - restart ntpd tags: ntp - name: be sure ntpd is running and enabled service: name=ntpd state=running enabled=yes tags: ntp Here is an example handlers file. As a review, handlers are only fired when certain tasks report changes, and are run at the end of each play:: --- # file: roles/common/handlers/main.yml - name: restart ntpd service: name=ntpd state=restarted See :doc:`playbooks_roles` for more information. .. _organization_examples: What This Organization Enables (Examples) ````````````````````````````````````````` Above we've shared our basic organizational structure. Now what sort of use cases does this layout enable? Lots! If I want to reconfigure my whole infrastructure, it's just:: ansible-playbook -i production site.yml What about just reconfiguring NTP on everything? Easy.:: ansible-playbook -i production site.yml --tags ntp What about just reconfiguring my webservers?:: ansible-playbook -i production webservers.yml What about just my webservers in Boston?:: ansible-playbook -i production webservers.yml --limit boston What about just the first 10, and then the next 10?:: ansible-playbook -i production webservers.yml --limit boston[0-10] ansible-playbook -i production webservers.yml --limit boston[10-20] And of course just basic ad-hoc stuff is also possible.:: ansible boston -i production -m ping ansible boston -i production -m command -a '/sbin/reboot' And there are some useful commands to know (at least in 1.1 and higher):: # confirm what task names would be run if I ran this command and said "just ntp tasks" ansible-playbook -i production webservers.yml --tags ntp --list-tasks # confirm what hostnames might be communicated with if I said "limit to boston" ansible-playbook -i production webservers.yml --limit boston --list-hosts .. _dep_vs_config: Deployment vs Configuration Organization ```````````````````````````````````````` The above setup models a typical configuration topology. When doing multi-tier deployments, there are going to be some additional playbooks that hop between tiers to roll out an application. In this case, 'site.yml' may be augmented by playbooks like 'deploy_exampledotcom.yml' but the general concepts can still apply. Consider "playbooks" as a sports metaphor -- you don't have to just have one set of plays to use against your infrastructure all the time -- you can have situational plays that you use at different times and for different purposes. Ansible allows you to deploy and configure using the same tool, so you would likely reuse groups and just keep the OS configuration in separate playbooks from the app deployment. .. _stage_vs_production: Stage vs Production +++++++++++++++++++ As also mentioned above, a good way to keep your stage (or testing) and production environments separate is to use a separate inventory file for stage and production. This way you pick with -i what you are targeting. Keeping them all in one file can lead to surprises! Testing things in a stage environment before trying in production is always a great idea. Your environments need not be the same size and you can use group variables to control the differences between those environments. .. _rolling_update: Rolling Updates +++++++++++++++ Understand the 'serial' keyword. If updating a webserver farm you really want to use it to control how many machines you are updating at once in the batch. See :doc:`playbooks_delegation`. .. _mention_the_state: Always Mention The State ++++++++++++++++++++++++ The 'state' parameter is optional to a lot of modules. Whether 'state=present' or 'state=absent', it's always best to leave that parameter in your playbooks to make it clear, especially as some modules support additional states. .. _group_by_roles: Group By Roles ++++++++++++++ A system can be in multiple groups. See :doc:`intro_inventory` and :doc:`intro_patterns`. Having groups named after things like *webservers* and *dbservers* is repeated in the examples because it's a very powerful concept. This allows playbooks to target machines based on role, as well as to assign role specific variables using the group variable system. See :doc:`playbooks_roles`. .. _os_variance: Operating System and Distribution Variance ++++++++++++++++++++++++++++++++++++++++++ When dealing with a parameter that is different between two different operating systems, the best way to handle this is by using the group_by module. This makes a dynamic group of hosts matching certain criteria, even if that group is not defined in the inventory file:: --- # talk to all hosts just so we can learn about them - hosts: all tasks: - group_by: key={{ ansible_distribution }} # now just on the CentOS hosts... - hosts: CentOS gather_facts: False tasks: - # tasks that only happen on CentOS go here If group-specific settings are needed, this can also be done. For example:: --- # file: group_vars/all asdf: 10 --- # file: group_vars/CentOS asdf: 42 In the above example, CentOS machines get the value of '42' for asdf, but other machines get '10'. .. _ship_modules_with_playbooks: Bundling Ansible Modules With Playbooks +++++++++++++++++++++++++++++++++++++++ .. versionadded:: 0.5 If a playbook has a "./library" directory relative to its YAML file, this directory can be used to add ansible modules that will automatically be in the ansible module path. This is a great way to keep modules that go with a playbook together. .. _whitespace: Whitespace and Comments +++++++++++++++++++++++ Generous use of whitespace to break things up, and use of comments (which start with '#'), is encouraged. .. _name_tasks: Always Name Tasks +++++++++++++++++ It is possible to leave off the 'name' for a given task, though it is recommended to provide a description about why something is being done instead. This name is shown when the playbook is run. .. _keep_it_simple: Keep It Simple ++++++++++++++ When you can do something simply, do something simply. Do not reach to use every feature of Ansible together, all at once. Use what works for you. For example, you will probably not need ``vars``, ``vars_files``, ``vars_prompt`` and ``--extra-vars`` all at once, while also using an external inventory file. .. _version_control: Version Control +++++++++++++++ Use version control. Keep your playbooks and inventory file in git (or another version control system), and commit when you make changes to them. This way you have an audit trail describing when and why you changed the rules that are automating your infrastructure. .. seealso:: :doc:`YAMLSyntax` Learn about YAML syntax :doc:`playbooks` Review the basic playbook features :doc:`modules` Learn about available modules :doc:`developing_modules` Learn how to extend Ansible by writing your own modules :doc:`intro_patterns` Learn about how to select hosts `Github examples directory `_ Complete playbook files from the github project source `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups ansible-1.7.2/docsite/rst/playbooks_checkmode.rst000066400000000000000000000042071241061774000221440ustar00rootroot00000000000000Check Mode ("Dry Run") ====================== .. versionadded:: 1.1 .. contents:: Topics When ansible-playbook is executed with ``--check`` it will not make any changes on remote systems. Instead, any module instrumented to support 'check mode' (which contains most of the primary core modules, but it is not required that all modules do this) will report what changes they would have made rather than making them. Other modules that do not support check mode will also take no action, but just will not report what changes they might have made. Check mode is just a simulation, and if you have steps that use conditionals that depend on the results of prior commands, it may be less useful for you. However it is great for one-node-at-time basic configuration management use cases. Example:: ansible-playbook foo.yml --check .. _forcing_to_run_in_check_mode: Running a task in check mode ```````````````````````````` .. versionadded:: 1.3 Sometimes you may want to have a task to be executed even in check mode. To achieve this, use the `always_run` clause on the task. Its value is a Jinja2 expression, just like the `when` clause. In simple cases a boolean YAML value would be sufficient as a value. Example:: tasks: - name: this task is run even in check mode command: /something/to/run --even-in-check-mode always_run: yes As a reminder, a task with a `when` clause evaluated to false, will still be skipped even if it has a `always_run` clause evaluated to true. .. _diff_mode: Showing Differences with ``--diff`` ``````````````````````````````````` .. versionadded:: 1.1 The ``--diff`` option to ansible-playbook works great with ``--check`` (detailed above) but can also be used by itself. When this flag is supplied, if any templated files on the remote system are changed, and the ansible-playbook CLI will report back the textual changes made to the file (or, if used with ``--check``, the changes that would have been made). Since the diff feature produces a large amount of output, it is best used when checking a single host at a time, like so:: ansible-playbook foo.yml --check --diff --limit foo.example.com ansible-1.7.2/docsite/rst/playbooks_conditionals.rst000066400000000000000000000234521241061774000227130ustar00rootroot00000000000000Conditionals ============ .. contents:: Topics Often the result of a play may depend on the value of a variable, fact (something learned about the remote system), or previous task result. In some cases, the values of variables may depend on other variables. Further, additional groups can be created to manage hosts based on whether the hosts match other criteria. There are many options to control execution flow in Ansible. Let's dig into what they are. The When Statement `````````````````` Sometimes you will want to skip a particular step on a particular host. This could be something as simple as not installing a certain package if the operating system is a particular version, or it could be something like performing some cleanup steps if a filesystem is getting full. This is easy to do in Ansible, with the `when` clause, which contains a Jinja2 expression (see :doc:`playbooks_variables`). It's actually pretty simple:: tasks: - name: "shutdown Debian flavored systems" command: /sbin/shutdown -t now when: ansible_os_family == "Debian" A number of Jinja2 "filters" can also be used in when statements, some of which are unique and provided by Ansible. Suppose we want to ignore the error of one statement and then decide to do something conditionally based on success or failure:: tasks: - command: /bin/false register: result ignore_errors: True - command: /bin/something when: result|failed - command: /bin/something_else when: result|success - command: /bin/still/something_else when: result|skipped Note that was a little bit of foreshadowing on the 'register' statement. We'll get to it a bit later in this chapter. As a reminder, to see what facts are available on a particular system, you can do:: ansible hostname.example.com -m setup Tip: Sometimes you'll get back a variable that's a string and you'll want to do a math operation comparison on it. You can do this like so:: tasks: - shell: echo "only on Red Hat 6, derivatives, and later" when: ansible_os_family == "RedHat" and ansible_lsb.major_release|int >= 6 .. note:: the above example requires the lsb_release package on the target host in order to return the ansible_lsb.major_release fact. Variables defined in the playbooks or inventory can also be used. An example may be the execution of a task based on a variable's boolean value:: vars: epic: true Then a conditional execution might look like:: tasks: - shell: echo "This certainly is epic!" when: epic or:: tasks: - shell: echo "This certainly isn't epic!" when: not epic If a required variable has not been set, you can skip or fail using Jinja2's `defined` test. For example:: tasks: - shell: echo "I've got '{{ foo }}' and am not afraid to use it!" when: foo is defined - fail: msg="Bailing out. this play requires 'bar'" when: bar is not defined This is especially useful in combination with the conditional import of vars files (see below). Note that when combining `when` with `with_items` (see :doc:`playbooks_loops`), be aware that the `when` statement is processed separately for each item. This is by design:: tasks: - command: echo {{ item }} with_items: [ 0, 2, 4, 6, 8, 10 ] when: item > 5 Loading in Custom Facts ``````````````````````` It's also easy to provide your own facts if you want, which is covered in :doc:`developing_modules`. To run them, just make a call to your own custom fact gathering module at the top of your list of tasks, and variables returned there will be accessible to future tasks:: tasks: - name: gather site specific fact data action: site_facts - command: /usr/bin/thingy when: my_custom_fact_just_retrieved_from_the_remote_system == '1234' Applying 'when' to roles and includes ````````````````````````````````````` Note that if you have several tasks that all share the same conditional statement, you can affix the conditional to a task include statement as below. Note this does not work with playbook includes, just task includes. All the tasks get evaluated, but the conditional is applied to each and every task:: - include: tasks/sometasks.yml when: "'reticulating splines' in output" Or with a role:: - hosts: webservers roles: - { role: debian_stock_config, when: ansible_os_family == 'Debian' } You will note a lot of 'skipped' output by default in Ansible when using this approach on systems that don't match the criteria. Read up on the 'group_by' module in the :doc:`modules` docs for a more streamlined way to accomplish the same thing. Conditional Imports ``````````````````` .. note:: This is an advanced topic that is infrequently used. You can probably skip this section. Sometimes you will want to do certain things differently in a playbook based on certain criteria. Having one playbook that works on multiple platforms and OS versions is a good example. As an example, the name of the Apache package may be different between CentOS and Debian, but it is easily handled with a minimum of syntax in an Ansible Playbook:: --- - hosts: all remote_user: root vars_files: - "vars/common.yml" - [ "vars/{{ ansible_os_family }}.yml", "vars/os_defaults.yml" ] tasks: - name: make sure apache is running service: name={{ apache }} state=running .. note:: The variable 'ansible_os_family' is being interpolated into the list of filenames being defined for vars_files. As a reminder, the various YAML files contain just keys and values:: --- # for vars/CentOS.yml apache: httpd somethingelse: 42 How does this work? If the operating system was 'CentOS', the first file Ansible would try to import would be 'vars/CentOS.yml', followed by '/vars/os_defaults.yml' if that file did not exist. If no files in the list were found, an error would be raised. On Debian, it would instead first look towards 'vars/Debian.yml' instead of 'vars/CentOS.yml', before falling back on 'vars/os_defaults.yml'. Pretty simple. To use this conditional import feature, you'll need facter or ohai installed prior to running the playbook, but you can of course push this out with Ansible if you like:: # for facter ansible -m yum -a "pkg=facter ensure=installed" ansible -m yum -a "pkg=ruby-json ensure=installed" # for ohai ansible -m yum -a "pkg=ohai ensure=installed" Ansible's approach to configuration -- separating variables from tasks, keeps your playbooks from turning into arbitrary code with ugly nested ifs, conditionals, and so on - and results in more streamlined & auditable configuration rules -- especially because there are a minimum of decision points to track. Selecting Files And Templates Based On Variables ```````````````````````````````````````````````` .. note:: This is an advanced topic that is infrequently used. You can probably skip this section. Sometimes a configuration file you want to copy, or a template you will use may depend on a variable. The following construct selects the first available file appropriate for the variables of a given host, which is often much cleaner than putting a lot of if conditionals in a template. The following example shows how to template out a configuration file that was very different between, say, CentOS and Debian:: - name: template a file template: src={{ item }} dest=/etc/myapp/foo.conf with_first_found: - files: - {{ ansible_distribution }}.conf - default.conf paths: - search_location_one/somedir/ - /opt/other_location/somedir/ Register Variables `````````````````` Often in a playbook it may be useful to store the result of a given command in a variable and access it later. Use of the command module in this way can in many ways eliminate the need to write site specific facts, for instance, you could test for the existence of a particular program. The 'register' keyword decides what variable to save a result in. The resulting variables can be used in templates, action lines, or *when* statements. It looks like this (in an obviously trivial example):: - name: test play hosts: all tasks: - shell: cat /etc/motd register: motd_contents - shell: echo "motd contains the word hi" when: motd_contents.stdout.find('hi') != -1 As shown previously, the registered variable's string contents are accessible with the 'stdout' value. The registered result can be used in the "with_items" of a task if it is converted into a list (or already is a list) as shown below. "stdout_lines" is already available on the object as well though you could also call "home_dirs.stdout.split()" if you wanted, and could split by other fields:: - name: registered variable usage as a with_items list hosts: all tasks: - name: retrieve the list of home directories command: ls /home register: home_dirs - name: add home dirs to the backup spooler file: path=/mnt/bkspool/{{ item }} src=/home/{{ item }} state=link with_items: home_dirs.stdout_lines # same as with_items: home_dirs.stdout.split() .. seealso:: :doc:`playbooks` An introduction to playbooks :doc:`playbooks_roles` Playbook organization by roles :doc:`playbooks_best_practices` Best practices in playbooks :doc:`playbooks_conditionals` Conditional statements in playbooks :doc:`playbooks_variables` All about variables `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/playbooks_delegation.rst000066400000000000000000000152311241061774000223340ustar00rootroot00000000000000Delegation, Rolling Updates, and Local Actions ============================================== .. contents:: Topics Being designed for multi-tier deployments since the beginning, Ansible is great at doing things on one host on behalf of another, or doing local steps with reference to some remote hosts. This in particular is very applicable when setting up continuous deployment infrastructure or zero downtime rolling updates, where you might be talking with load balancers or monitoring systems. Additional features allow for tuning the orders in which things complete, and assigning a batch window size for how many machines to process at once during a rolling update. This section covers all of these features. For examples of these items in use, `please see the ansible-examples repository `_. There are quite a few examples of zero-downtime update procedures for different kinds of applications. You should also consult the :doc:`modules` section, various modules like 'ec2_elb', 'nagios', and 'bigip_pool', and 'netscaler' dovetail neatly with the concepts mentioned here. You'll also want to read up on :doc:`playbooks_roles`, as the 'pre_task' and 'post_task' concepts are the places where you would typically call these modules. .. _rolling_update_batch_size: Rolling Update Batch Size ````````````````````````` .. versionadded:: 0.7 By default, Ansible will try to manage all of the machines referenced in a play in parallel. For a rolling updates use case, you can define how many hosts Ansible should manage at a single time by using the ''serial'' keyword:: - name: test play hosts: webservers serial: 3 In the above example, if we had 100 hosts, 3 hosts in the group 'webservers' would complete the play completely before moving on to the next 3 hosts. .. _maximum_failure_percentage: Maximum Failure Percentage `````````````````````````` .. versionadded:: 1.3 By default, Ansible will continue executing actions as long as there are hosts in the group that have not yet failed. In some situations, such as with the rolling updates described above, it may be desirable to abort the play when a certain threshold of failures have been reached. To achieve this, as of version 1.3 you can set a maximum failure percentage on a play as follows:: - hosts: webservers max_fail_percentage: 30 serial: 10 In the above example, if more than 3 of the 10 servers in the group were to fail, the rest of the play would be aborted. .. note:: The percentage set must be exceeded, not equaled. For example, if serial were set to 4 and you wanted the task to abort when 2 of the systems failed, the percentage should be set at 49 rather than 50. .. _delegation: Delegation `````````` .. versionadded:: 0.7 This isn't actually rolling update specific but comes up frequently in those cases. If you want to perform a task on one host with reference to other hosts, use the 'delegate_to' keyword on a task. This is ideal for placing nodes in a load balanced pool, or removing them. It is also very useful for controlling outage windows. Using this with the 'serial' keyword to control the number of hosts executing at one time is also a good idea:: --- - hosts: webservers serial: 5 tasks: - name: take out of load balancer pool command: /usr/bin/take_out_of_pool {{ inventory_hostname }} delegate_to: 127.0.0.1 - name: actual steps would go here yum: name=acme-web-stack state=latest - name: add back to load balancer pool command: /usr/bin/add_back_to_pool {{ inventory_hostname }} delegate_to: 127.0.0.1 These commands will run on 127.0.0.1, which is the machine running Ansible. There is also a shorthand syntax that you can use on a per-task basis: 'local_action'. Here is the same playbook as above, but using the shorthand syntax for delegating to 127.0.0.1:: --- # ... tasks: - name: take out of load balancer pool local_action: command /usr/bin/take_out_of_pool {{ inventory_hostname }} # ... - name: add back to load balancer pool local_action: command /usr/bin/add_back_to_pool {{ inventory_hostname }} A common pattern is to use a local action to call 'rsync' to recursively copy files to the managed servers. Here is an example:: --- # ... tasks: - name: recursively copy files from management server to target local_action: command rsync -a /path/to/files {{ inventory_hostname }}:/path/to/target/ Note that you must have passphrase-less SSH keys or an ssh-agent configured for this to work, otherwise rsync will need to ask for a passphrase. .. _run_once: Run Once ```````` In some cases there may be a need to only run a task one time and only on one host. This can be achieved by configuring "run_once" on a task:: --- # ... tasks: # ... - command: /opt/application/upgrade_db.py run_once: true # ... This can be optionally paired with "delegate_to" to specify an individual host to execute on:: - command: /opt/application/upgrade_db.py run_once: true delegate_to: web01.example.org When "run_once" is not used with "delegate_to" it will execute on the first host, as defined by inventory, in the group(s) of hosts targeted by the play. e.g. webservers[0] if the play targeted "hosts: webservers". This aproach is similar, although more concise and cleaner than applying a conditional to a task such as:: - command: /opt/application/upgrade_db.py when: inventory_hostname == webservers[0] .. _local_playbooks: Local Playbooks ``````````````` It may be useful to use a playbook locally, rather than by connecting over SSH. This can be useful for assuring the configuration of a system by putting a playbook on a crontab. This may also be used to run a playbook inside an OS installer, such as an Anaconda kickstart. To run an entire playbook locally, just set the "hosts:" line to "hosts:127.0.0.1" and then run the playbook like so:: ansible-playbook playbook.yml --connection=local Alternatively, a local connection can be used in a single playbook play, even if other plays in the playbook use the default remote connection type:: - hosts: 127.0.0.1 connection: local .. seealso:: :doc:`playbooks` An introduction to playbooks `Ansible Examples on GitHub `_ Many examples of full-stack deployments `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/playbooks_environment.rst000066400000000000000000000033271241061774000225700ustar00rootroot00000000000000Setting the Environment (and Working With Proxies) ================================================== .. versionadded:: 1.1 It is quite possible that you may need to get package updates through a proxy, or even get some package updates through a proxy and access other packages not through a proxy. Or maybe a script you might wish to call may also need certain environment variables set to run properly. Ansible makes it easy for you to configure your environment by using the 'environment' keyword. Here is an example:: - hosts: all remote_user: root tasks: - apt: name=cobbler state=installed environment: http_proxy: http://proxy.example.com:8080 The environment can also be stored in a variable, and accessed like so:: - hosts: all remote_user: root # here we make a variable named "proxy_env" that is a dictionary vars: proxy_env: http_proxy: http://proxy.example.com:8080 tasks: - apt: name=cobbler state=installed environment: proxy_env While just proxy settings were shown above, any number of settings can be supplied. The most logical place to define an environment hash might be a group_vars file, like so:: --- # file: group_vars/boston ntp_server: ntp.bos.example.com backup: bak.bos.example.com proxy_env: http_proxy: http://proxy.bos.example.com:8080 https_proxy: http://proxy.bos.example.com:8080 .. seealso:: :doc:`playbooks` An introduction to playbooks `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/playbooks_error_handling.rst000066400000000000000000000063461241061774000232250ustar00rootroot00000000000000Error Handling In Playbooks =========================== .. contents:: Topics Ansible normally has defaults that make sure to check the return codes of commands and modules and it fails fast -- forcing an error to be dealt with unless you decide otherwise. Sometimes a command that returns 0 isn't an error. Sometimes a command might not always need to report that it 'changed' the remote system. This section describes how to change the default behavior of Ansible for certain tasks so output and error handling behavior is as desired. .. _ignoring_failed_commands: Ignoring Failed Commands ```````````````````````` .. versionadded:: 0.6 Generally playbooks will stop executing any more steps on a host that has a failure. Sometimes, though, you want to continue on. To do so, write a task that looks like this:: - name: this will not be counted as a failure command: /bin/false ignore_errors: yes Note that the above system only governs the failure of the particular task, so if you have an undefined variable used, it will still raise an error that users will need to address. .. _controlling_what_defines_failure: Controlling What Defines Failure ```````````````````````````````` .. versionadded:: 1.4 Suppose the error code of a command is meaningless and to tell if there is a failure what really matters is the output of the command, for instance if the string "FAILED" is in the output. Ansible in 1.4 and later provides a way to specify this behavior as follows:: - name: this command prints FAILED when it fails command: /usr/bin/example-command -x -y -z register: command_result failed_when: "'FAILED' in command_result.stderr" In previous version of Ansible, this can be still be accomplished as follows:: - name: this command prints FAILED when it fails command: /usr/bin/example-command -x -y -z register: command_result ignore_errors: True - name: fail the play if the previous command did not succeed fail: msg="the command failed" when: "'FAILED' in command_result.stderr" .. _override_the_changed_result: Overriding The Changed Result ````````````````````````````` .. versionadded:: 1.3 When a shell/command or other module runs it will typically report "changed" status based on whether it thinks it affected machine state. Sometimes you will know, based on the return code or output that it did not make any changes, and wish to override the "changed" result such that it does not appear in report output or does not cause handlers to fire:: tasks: - shell: /usr/bin/billybass --mode="take me to the river" register: bass_result changed_when: "bass_result.rc != 2" # this will never report 'changed' status - shell: wall 'beep' changed_when: False .. seealso:: :doc:`playbooks` An introduction to playbooks :doc:`playbooks_best_practices` Best practices in playbooks :doc:`playbooks_conditionals` Conditional statements in playbooks :doc:`playbooks_variables` All about variables `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/playbooks_intro.rst000066400000000000000000000333361241061774000213620ustar00rootroot00000000000000Intro to Playbooks ================== .. _about_playbooks: About Playbooks ``````````````` Playbooks are a completely different way to use ansible than in adhoc task execution mode, and are particularly powerful. Simply put, playbooks are the basis for a really simple configuration management and multi-machine deployment system, unlike any that already exist, and one that is very well suited to deploying complex applications. Playbooks can declare configurations, but they can also orchestrate steps of any manual ordered process, even as different steps must bounce back and forth between sets of machines in particular orders. They can launch tasks synchronously or asynchronously. While you might run the main /usr/bin/ansible program for ad-hoc tasks, playbooks are more likely to be kept in source control and used to push out your configuration or assure the configurations of your remote systems are in spec. There are also some full sets of playbooks illustrating a lot of these techniques in the `ansible-examples repository `_. We'd recommend looking at these in another tab as you go along. There are also many jumping off points after you learn playbooks, so hop back to the documentation index after you're done with this section. .. _playbook_language_example: Playbook Language Example ````````````````````````` Playbooks are expressed in YAML format (see :doc:`YAMLSyntax`) and have a minimum of syntax, which intentionally tries to not be a programming language or script, but rather a model of a configuration or a process. Each playbook is composed of one or more 'plays' in a list. The goal of a play is to map a group of hosts to some well defined roles, represented by things ansible calls tasks. At a basic level, a task is nothing more than a call to an ansible module, which you should have learned about in earlier chapters. By composing a playbook of multiple 'plays', it is possible to orchestrate multi-machine deployments, running certain steps on all machines in the webservers group, then certain steps on the database server group, then more commands back on the webservers group, etc. "plays" are more or less a sports analogy. You can have quite a lot of plays that affect your systems to do different things. It's not as if you were just defining one particular state or model, and you can run different plays at different times. For starters, here's a playbook that contains just one play:: --- - hosts: webservers vars: http_port: 80 max_clients: 200 remote_user: root tasks: - name: ensure apache is at the latest version yum: pkg=httpd state=latest - name: write the apache config file template: src=/srv/httpd.j2 dest=/etc/httpd.conf notify: - restart apache - name: ensure apache is running service: name=httpd state=started handlers: - name: restart apache service: name=httpd state=restarted Below, we'll break down what the various features of the playbook language are. .. _playbook_basics: Basics `````` .. _playbook_hosts_and_users: Hosts and Users +++++++++++++++ For each play in a playbook, you get to choose which machines in your infrastructure to target and what remote user to complete the steps (called tasks) as. The `hosts` line is a list of one or more groups or host patterns, separated by colons, as described in the :doc:`intro_patterns` documentation. The `remote_user` is just the name of the user account:: --- - hosts: webservers remote_user: root .. note:: The `remote_user` parameter was formerly called just `user`. It was renamed in Ansible 1.4 to make it more distinguishable from the `user` module (used to create users on remote systems). Remote users can also be defined per task:: --- - hosts: webservers remote_user: root tasks: - name: test connection ping: remote_user: yourname .. note:: The `remote_user` parameter for tasks was added in 1.4. Support for running things from sudo is also available:: --- - hosts: webservers remote_user: yourname sudo: yes You can also use sudo on a particular task instead of the whole play:: --- - hosts: webservers remote_user: yourname tasks: - service: name=nginx state=started sudo: yes You can also login as you, and then sudo to different users than root:: --- - hosts: webservers remote_user: yourname sudo: yes sudo_user: postgres If you need to specify a password to sudo, run `ansible-playbook` with ``--ask-sudo-pass`` (`-K`). If you run a sudo playbook and the playbook seems to hang, it's probably stuck at the sudo prompt. Just `Control-C` to kill it and run it again with `-K`. .. important:: When using `sudo_user` to a user other than root, the module arguments are briefly written into a random tempfile in /tmp. These are deleted immediately after the command is executed. This only occurs when sudoing from a user like 'bob' to 'timmy', not when going from 'bob' to 'root', or logging in directly as 'bob' or 'root'. If this concerns you that this data is briefly readable (not writable), avoid transferring uncrypted passwords with `sudo_user` set. In other cases, '/tmp' is not used and this does not come into play. Ansible also takes care to not log password parameters. .. _tasks_list: Tasks list ++++++++++ Each play contains a list of tasks. Tasks are executed in order, one at a time, against all machines matched by the host pattern, before moving on to the next task. It is important to understand that, within a play, all hosts are going to get the same task directives. It is the purpose of a play to map a selection of hosts to tasks. When running the playbook, which runs top to bottom, hosts with failed tasks are taken out of the rotation for the entire playbook. If things fail, simply correct the playbook file and rerun. The goal of each task is to execute a module, with very specific arguments. Variables, as mentioned above, can be used in arguments to modules. Modules are 'idempotent', meaning if you run them again, they will make only the changes they must in order to bring the system to the desired state. This makes it very safe to rerun the same playbook multiple times. They won't change things unless they have to change things. The `command` and `shell` modules will typically rerun the same command again, which is totally ok if the command is something like 'chmod' or 'setsebool', etc. Though there is a 'creates' flag available which can be used to make these modules also idempotent. Every task should have a `name`, which is included in the output from running the playbook. This is output for humans, so it is nice to have reasonably good descriptions of each task step. If the name is not provided though, the string fed to 'action' will be used for output. Tasks can be declared using the legacy "action: module options" format, but it is recommended that you use the more conventional "module: options" format. This recommended format is used throughout the documentation, but you may encounter the older format in some playbooks. Here is what a basic task looks like, as with most modules, the service module takes key=value arguments:: tasks: - name: make sure apache is running service: name=httpd state=running The `command` and `shell` modules are the only modules that just take a list of arguments and don't use the key=value form. This makes them work as simply as you would expect:: tasks: - name: disable selinux command: /sbin/setenforce 0 The command and shell module care about return codes, so if you have a command whose successful exit code is not zero, you may wish to do this:: tasks: - name: run this command and ignore the result shell: /usr/bin/somecommand || /bin/true Or this:: tasks: - name: run this command and ignore the result shell: /usr/bin/somecommand ignore_errors: True If the action line is getting too long for comfort you can break it on a space and indent any continuation lines:: tasks: - name: Copy ansible inventory file to client copy: src=/etc/ansible/hosts dest=/etc/ansible/hosts owner=root group=root mode=0644 Variables can be used in action lines. Suppose you defined a variable called 'vhost' in the 'vars' section, you could do this:: tasks: - name: create a virtual host file for {{ vhost }} template: src=somefile.j2 dest=/etc/httpd/conf.d/{{ vhost }} Those same variables are usable in templates, which we'll get to later. Now in a very basic playbook all the tasks will be listed directly in that play, though it will usually make more sense to break up tasks using the 'include:' directive. We'll show that a bit later. .. _action_shorthand: Action Shorthand ```````````````` .. versionadded:: 0.8 Ansible prefers listing modules like this in 0.8 and later:: template: src=templates/foo.j2 dest=/etc/foo.conf You will notice in earlier versions, this was only available as:: action: template src=templates/foo.j2 dest=/etc/foo.conf The old form continues to work in newer versions without any plan of deprecation. .. _handlers: Handlers: Running Operations On Change `````````````````````````````````````` As we've mentioned, modules are written to be 'idempotent' and can relay when they have made a change on the remote system. Playbooks recognize this and have a basic event system that can be used to respond to change. These 'notify' actions are triggered at the end of each block of tasks in a playbook, and will only be triggered once even if notified by multiple different tasks. For instance, multiple resources may indicate that apache needs to be restarted because they have changed a config file, but apache will only be bounced once to avoid unnecessary restarts. Here's an example of restarting two services when the contents of a file change, but only if the file changes:: - name: template configuration file template: src=template.j2 dest=/etc/foo.conf notify: - restart memcached - restart apache The things listed in the 'notify' section of a task are called handlers. Handlers are lists of tasks, not really any different from regular tasks, that are referenced by name. Handlers are what notifiers notify. If nothing notifies a handler, it will not run. Regardless of how many things notify a handler, it will run only once, after all of the tasks complete in a particular play. Here's an example handlers section:: handlers: - name: restart memcached service: name=memcached state=restarted - name: restart apache service: name=apache state=restarted Handlers are best used to restart services and trigger reboots. You probably won't need them for much else. .. note:: Notify handlers are always run in the order written. Roles are described later on. It's worthwhile to point out that handlers are automatically processed between 'pre_tasks', 'roles', 'tasks', and 'post_tasks' sections. If you ever want to flush all the handler commands immediately though, in 1.2 and later, you can:: tasks: - shell: some tasks go here - meta: flush_handlers - shell: some other tasks In the above example any queued up handlers would be processed early when the 'meta' statement was reached. This is a bit of a niche case but can come in handy from time to time. .. _executing_a_playbook: Executing A Playbook ```````````````````` Now that you've learned playbook syntax, how do you run a playbook? It's simple. Let's run a playbook using a parallelism level of 10:: ansible-playbook playbook.yml -f 10 .. _ansible-pull: Ansible-Pull ```````````` Should you want to invert the architecture of Ansible, so that nodes check in to a central location, instead of pushing configuration out to them, you can. Ansible-pull is a small script that will checkout a repo of configuration instructions from git, and then run ansible-playbook against that content. Assuming you load balance your checkout location, ansible-pull scales essentially infinitely. Run ``ansible-pull --help`` for details. There's also a `clever playbook `_ available to configure ansible-pull via a crontab from push mode. .. _tips_and_tricks: Tips and Tricks ``````````````` Look at the bottom of the playbook execution for a summary of the nodes that were targeted and how they performed. General failures and fatal "unreachable" communication attempts are kept separate in the counts. If you ever want to see detailed output from successful modules as well as unsuccessful ones, use the ``--verbose`` flag. This is available in Ansible 0.5 and later. Ansible playbook output is vastly upgraded if the cowsay package is installed. Try it! To see what hosts would be affected by a playbook before you run it, you can do this:: ansible-playbook playbook.yml --list-hosts .. seealso:: :doc:`YAMLSyntax` Learn about YAML syntax :doc:`playbooks_best_practices` Various tips about managing playbooks in the real world :doc:`index` Hop back to the documentation index for a lot of special topics about playbooks :doc:`modules` Learn about available modules :doc:`developing_modules` Learn how to extend Ansible by writing your own modules :doc:`intro_patterns` Learn about how to select hosts `Github examples directory `_ Complete end-to-end playbook examples `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups ansible-1.7.2/docsite/rst/playbooks_lookups.rst000066400000000000000000000134071241061774000217200ustar00rootroot00000000000000Using Lookups ============= Lookup plugins allow access of data in Ansible from outside sources. These plugins are evaluated on the Ansible control machine, and can include reading the filesystem but also contacting external datastores and services. These values are then made available using the standard templating system in Ansible, and are typically used to load variables or templates with information from those systems. .. note:: This is considered an advanced feature, and many users will probably not rely on these features. .. note:: Lookups occur on the local computer, not on the remote computer. .. contents:: Topics .. _getting_file_contents: Intro to Lookups: Getting File Contents ``````````````````````````````````````` The file lookup is the most basic lookup type. Contents can be read off the filesystem as follows:: - hosts: all vars: contents: "{{ lookup('file', '/etc/foo.txt') }}" tasks: - debug: msg="the value of foo.txt is {{ contents }}" .. _password_lookup: The Password Lookup ``````````````````` .. note:: A great alternative to the password lookup plugin, if you don't need to generate random passwords on a per-host basis, would be to use :doc:`playbooks_vault`. Read the documentation there and consider using it first, it will be more desirable for most applications. ``password`` generates a random plaintext password and stores it in a file at a given filepath. (Docs about crypted save modes are pending) If the file exists previously, it will retrieve its contents, behaving just like with_file. Usage of variables like "{{ inventory_hostname }}" in the filepath can be used to set up random passwords per host (what simplifies password management in 'host_vars' variables). Generated passwords contain a random mix of upper and lowercase ASCII letters, the numbers 0-9 and punctuation (". , : - _"). The default length of a generated password is 20 characters. This length can be changed by passing an extra parameter:: --- - hosts: all tasks: # create a mysql user with a random password: - mysql_user: name={{ client }} password="{{ lookup('password', 'credentials/' + client + '/' + tier + '/' + role + '/mysqlpassword length=15') }}" priv={{ client }}_{{ tier }}_{{ role }}.*:ALL (...) .. note:: If the file already exists, no data will be written to it. If the file has contents, those contents will be read in as the password. Empty files cause the password to return as an empty string Starting in version 1.4, password accepts a "chars" parameter to allow defining a custom character set in the generated passwords. It accepts comma separated list of names that are either string module attributes (ascii_letters,digits, etc) or are used literally:: --- - hosts: all tasks: # create a mysql user with a random password using only ascii letters: - mysql_user: name={{ client }} password="{{ lookup('password', '/tmp/passwordfile chars=ascii_letters') }}" priv={{ client }}_{{ tier }}_{{ role }}.*:ALL # create a mysql user with a random password using only digits: - mysql_user: name={{ client }} password="{{ lookup('password', '/tmp/passwordfile chars=digits') }}" priv={{ client }}_{{ tier }}_{{ role }}.*:ALL # create a mysql user with a random password using many different char sets: - mysql_user: name={{ client }} password="{{ lookup('password', '/tmp/passwordfile chars=ascii_letters,digits,hexdigits,punctuation') }}" priv={{ client }}_{{ tier }}_{{ role }}.*:ALL (...) To enter comma use two commas ',,' somewhere - preferably at the end. Quotes and double quotes are not supported. .. _more_lookups: More Lookups ```````````` .. note:: This feature is very infrequently used in Ansible. You may wish to skip this section. .. versionadded:: 0.8 Various *lookup plugins* allow additional ways to iterate over data. In :doc:`Loops ` you will learn how to use them to walk over collections of numerous types. However, they can also be used to pull in data from remote sources, such as shell commands or even key value stores. This section will cover lookup plugins in this capacity. Here are some examples:: --- - hosts: all tasks: - debug: msg="{{ lookup('env','HOME') }} is an environment variable" - debug: msg="{{ item }} is a line from the result of this command" with_lines: - cat /etc/motd - debug: msg="{{ lookup('pipe','date') }} is the raw result of running this command" - debug: msg="{{ lookup('redis_kv', 'redis://localhost:6379,somekey') }} is value in Redis for somekey" - debug: msg="{{ lookup('dnstxt', 'example.com') }} is a DNS TXT record for example.com" - debug: msg="{{ lookup('template', './some_template.j2') }} is a value from evaluation of this template" As an alternative you can also assign lookup plugins to variables or use them elsewhere. This macros are evaluated each time they are used in a task (or template):: vars: motd_value: "{{ lookup('file', '/etc/motd') }}" tasks: - debug: msg="motd value is {{ motd_value }}" .. seealso:: :doc:`playbooks` An introduction to playbooks :doc:`playbooks_conditionals` Conditional statements in playbooks :doc:`playbooks_variables` All about variables :doc:`playbooks_loops` Looping in playbooks `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/playbooks_loops.rst000066400000000000000000000341411241061774000213560ustar00rootroot00000000000000Loops ===== Often you'll want to do many things in one task, such as create a lot of users, install a lot of packages, or repeat a polling step until a certain result is reached. This chapter is all about how to use loops in playbooks. .. contents:: Topics .. _standard_loops: Standard Loops `````````````` To save some typing, repeated tasks can be written in short-hand like so:: - name: add several users user: name={{ item }} state=present groups=wheel with_items: - testuser1 - testuser2 If you have defined a YAML list in a variables file, or the 'vars' section, you can also do:: with_items: somelist The above would be the equivalent of:: - name: add user testuser1 user: name=testuser1 state=present groups=wheel - name: add user testuser2 user: name=testuser2 state=present groups=wheel The yum and apt modules use with_items to execute fewer package manager transactions. Note that the types of items you iterate over with 'with_items' do not have to be simple lists of strings. If you have a list of hashes, you can reference subkeys using things like:: - name: add several users user: name={{ item.name }} state=present groups={{ item.groups }} with_items: - { name: 'testuser1', groups: 'wheel' } - { name: 'testuser2', groups: 'root' } .. _nested_loops: Nested Loops ```````````` Loops can be nested as well:: - name: give users access to multiple databases mysql_user: name={{ item[0] }} priv={{ item[1] }}.*:ALL append_privs=yes password=foo with_nested: - [ 'alice', 'bob' ] - [ 'clientdb', 'employeedb', 'providerdb' ] As with the case of 'with_items' above, you can use previously defined variables. Just specify the variable's name without templating it with '{{ }}':: - name: here, 'users' contains the above list of employees mysql_user: name={{ item[0] }} priv={{ item[1] }}.*:ALL append_privs=yes password=foo with_nested: - users - [ 'clientdb', 'employeedb', 'providerdb' ] .. _looping_over_hashes: Looping over Hashes ``````````````````` .. versionadded:: 1.5 Suppose you have the following variable:: --- users: alice: name: Alice Appleworth telephone: 123-456-7890 bob: name: Bob Bananarama telephone: 987-654-3210 And you want to print every user's name and phone number. You can loop through the elements of a hash using ``with_dict`` like this:: tasks: - name: Print phone records debug: msg="User {{ item.key }} is {{ item.value.name }} ({{ item.value.telephone }})" with_dict: users .. _looping_over_fileglobs: Looping over Fileglobs `````````````````````` ``with_fileglob`` matches all files in a single directory, non-recursively, that match a pattern. It can be used like this:: --- - hosts: all tasks: # first ensure our target directory exists - file: dest=/etc/fooapp state=directory # copy each file over that matches the given pattern - copy: src={{ item }} dest=/etc/fooapp/ owner=root mode=600 with_fileglob: - /playbooks/files/fooapp/* .. note:: When using a relative path with ``with_fileglob`` in a role, Ansible resolves the path relative to the `roles//files` directory. Looping over Parallel Sets of Data `````````````````````````````````` .. note:: This is an uncommon thing to want to do, but we're documenting it for completeness. You probably won't be reaching for this one often. Suppose you have the following variable data was loaded in via somewhere:: --- alpha: [ 'a', 'b', 'c', 'd' ] numbers: [ 1, 2, 3, 4 ] And you want the set of '(a, 1)' and '(b, 2)' and so on. Use 'with_together' to get this:: tasks: - debug: msg="{{ item.0 }} and {{ item.1 }}" with_together: - alpha - numbers Looping over Subelements ```````````````````````` Suppose you want to do something like loop over a list of users, creating them, and allowing them to login by a certain set of SSH keys. How might that be accomplished? Let's assume you had the following defined and loaded in via "vars_files" or maybe a "group_vars/all" file:: --- users: - name: alice authorized: - /tmp/alice/onekey.pub - /tmp/alice/twokey.pub - name: bob authorized: - /tmp/bob/id_rsa.pub It might happen like so:: - user: name={{ item.name }} state=present generate_ssh_key=yes with_items: users - authorized_key: "user={{ item.0.name }} key='{{ lookup('file', item.1) }}'" with_subelements: - users - authorized Subelements walks a list of hashes (aka dictionaries) and then traverses a list with a given key inside of those records. The authorized_key pattern is exactly where it comes up most. .. _looping_over_integer_sequences: Looping over Integer Sequences `````````````````````````````` ``with_sequence`` generates a sequence of items in ascending numerical order. You can specify a start, end, and an optional step value. Arguments should be specified in key=value pairs. If supplied, the 'format' is a printf style string. Numerical values can be specified in decimal, hexadecimal (0x3f8) or octal (0600). Negative numbers are not supported. This works as follows:: --- - hosts: all tasks: # create groups - group: name=evens state=present - group: name=odds state=present # create some test users - user: name={{ item }} state=present groups=evens with_sequence: start=0 end=32 format=testuser%02x # create a series of directories with even numbers for some reason - file: dest=/var/stuff/{{ item }} state=directory with_sequence: start=4 end=16 stride=2 # a simpler way to use the sequence plugin # create 4 groups - group: name=group{{ item }} state=present with_sequence: count=4 .. _random_choice: Random Choices `````````````` The 'random_choice' feature can be used to pick something at random. While it's not a load balancer (there are modules for those), it can somewhat be used as a poor man's loadbalancer in a MacGyver like situation:: - debug: msg={{ item }} with_random_choice: - "go through the door" - "drink from the goblet" - "press the red button" - "do nothing" One of the provided strings will be selected at random. At a more basic level, they can be used to add chaos and excitement to otherwise predictable automation environments. .. _do_until_loops: Do-Until Loops `````````````` .. versionadded: 1.4 Sometimes you would want to retry a task until a certain condition is met. Here's an example:: - action: shell /usr/bin/foo register: result until: result.stdout.find("all systems go") != -1 retries: 5 delay: 10 The above example run the shell module recursively till the module's result has "all systems go" in its stdout or the task has been retried for 5 times with a delay of 10 seconds. The default value for "retries" is 3 and "delay" is 5. The task returns the results returned by the last task run. The results of individual retries can be viewed by -vv option. The registered variable will also have a new key "attempts" which will have the number of the retries for the task. .. _with_first_found: Finding First Matched Files ``````````````````````````` .. note:: This is an uncommon thing to want to do, but we're documenting it for completeness. You probably won't be reaching for this one often. This isn't exactly a loop, but it's close. What if you want to use a reference to a file based on the first file found that matches a given criteria, and some of the filenames are determined by variable names? Yes, you can do that as follows:: - name: INTERFACES | Create Ansible header for /etc/network/interfaces template: src={{ item }} dest=/etc/foo.conf with_first_found: - "{{ansible_virtualization_type}}_foo.conf" - "default_foo.conf" This tool also has a long form version that allows for configurable search paths. Here's an example:: - name: some configuration template template: src={{ item }} dest=/etc/file.cfg mode=0444 owner=root group=root with_first_found: - files: - "{{inventory_hostname}}/etc/file.cfg" paths: - ../../../templates.overwrites - ../../../templates - files: - etc/file.cfg paths: - templates .. _looping_over_the_results_of_a_program_execution: Iterating Over The Results of a Program Execution ````````````````````````````````````````````````` .. note:: This is an uncommon thing to want to do, but we're documenting it for completeness. You probably won't be reaching for this one often. Sometimes you might want to execute a program, and based on the output of that program, loop over the results of that line by line. Ansible provides a neat way to do that, though you should remember, this is always executed on the control machine, not the local machine:: - name: Example of looping over a command result shell: /usr/bin/frobnicate {{ item }} with_lines: /usr/bin/frobnications_per_host --param {{ inventory_hostname }} Ok, that was a bit arbitrary. In fact, if you're doing something that is inventory related you might just want to write a dynamic inventory source instead (see :doc:`intro_dynamic_inventory`), but this can be occasionally useful in quick-and-dirty implementations. Should you ever need to execute a command remotely, you would not use the above method. Instead do this:: - name: Example of looping over a REMOTE command result shell: /usr/bin/something register: command_result - name: Do something with each result shell: /usr/bin/something_else --param {{ item }} with_items: command_result.stdout_lines .. _indexed_lists: Looping Over A List With An Index ````````````````````````````````` .. note:: This is an uncommon thing to want to do, but we're documenting it for completeness. You probably won't be reaching for this one often. .. versionadded: 1.3 If you want to loop over an array and also get the numeric index of where you are in the array as you go, you can also do that. It's uncommonly used:: - name: indexed loop demo debug: msg="at array position {{ item.0 }} there is a value {{ item.1 }}" with_indexed_items: some_list .. _flattening_a_list: Flattening A List ````````````````` .. note:: This is an uncommon thing to want to do, but we're documenting it for completeness. You probably won't be reaching for this one often. In rare instances you might have several lists of lists, and you just want to iterate over every item in all of those lists. Assume a really crazy hypothetical datastructure:: ---- # file: roles/foo/vars/main.yml packages_base: - [ 'foo-package', 'bar-package' ] packages_apps: - [ ['one-package', 'two-package' ]] - [ ['red-package'], ['blue-package']] As you can see the formatting of packages in these lists is all over the place. How can we install all of the packages in both lists?:: - name: flattened loop demo yum: name={{ item }} state=installed with_flattened: - packages_base - packages_apps That's how! .. _using_register_with_a_loop: Using register with a loop `````````````````````````` When using ``register`` with a loop the data structure placed in the variable during a loop, will contain a ``results`` attribute, that is a list of all responses from the module. Here is an example of using ``register`` with ``with_items``:: - shell: echo "{{ item }}" with_items: - one - two register: echo This differs from the data structure returned when using ``register`` without a loop:: { "changed": true, "msg": "All items completed", "results": [ { "changed": true, "cmd": "echo \"one\" ", "delta": "0:00:00.003110", "end": "2013-12-19 12:00:05.187153", "invocation": { "module_args": "echo \"one\"", "module_name": "shell" }, "item": "one", "rc": 0, "start": "2013-12-19 12:00:05.184043", "stderr": "", "stdout": "one" }, { "changed": true, "cmd": "echo \"two\" ", "delta": "0:00:00.002920", "end": "2013-12-19 12:00:05.245502", "invocation": { "module_args": "echo \"two\"", "module_name": "shell" }, "item": "two", "rc": 0, "start": "2013-12-19 12:00:05.242582", "stderr": "", "stdout": "two" } ] } Subsequent loops over the registered variable to inspect the results may look like:: - name: Fail if return code is not 0 fail: msg: "The command ({{ item.cmd }}) did not have a 0 return code" when: item.rc != 0 with_items: echo.results .. _writing_your_own_iterators: Writing Your Own Iterators `````````````````````````` While you ordinarily shouldn't have to, should you wish to write your own ways to loop over arbitrary datastructures, you can read :doc:`developing_plugins` for some starter information. Each of the above features are implemented as plugins in ansible, so there are many implementations to reference. .. seealso:: :doc:`playbooks` An introduction to playbooks :doc:`playbooks_roles` Playbook organization by roles :doc:`playbooks_best_practices` Best practices in playbooks :doc:`playbooks_conditionals` Conditional statements in playbooks :doc:`playbooks_variables` All about variables `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/playbooks_prompts.rst000066400000000000000000000055661241061774000217370ustar00rootroot00000000000000Prompts ======= When running a playbook, you may wish to prompt the user for certain input, and can do so with the 'vars_prompt' section. A common use for this might be for asking for sensitive data that you do not want to record. This has uses beyond security, for instance, you may use the same playbook for all software releases and would prompt for a particular release version in a push-script. Here is a most basic example:: --- - hosts: all remote_user: root vars: from: "camelot" vars_prompt: name: "what is your name?" quest: "what is your quest?" favcolor: "what is your favorite color?" If you have a variable that changes infrequently, it might make sense to provide a default value that can be overridden. This can be accomplished using the default argument:: vars_prompt: - name: "release_version" prompt: "Product release version" default: "1.0" An alternative form of vars_prompt allows for hiding input from the user, and may later support some other options, but otherwise works equivalently:: vars_prompt: - name: "some_password" prompt: "Enter password" private: yes - name: "release_version" prompt: "Product release version" private: no If `Passlib `_ is installed, vars_prompt can also crypt the entered value so you can use it, for instance, with the user module to define a password:: vars_prompt: - name: "my_password2" prompt: "Enter password2" private: yes encrypt: "md5_crypt" confirm: yes salt_size: 7 You can use any crypt scheme supported by 'Passlib': - *des_crypt* - DES Crypt - *bsdi_crypt* - BSDi Crypt - *bigcrypt* - BigCrypt - *crypt16* - Crypt16 - *md5_crypt* - MD5 Crypt - *bcrypt* - BCrypt - *sha1_crypt* - SHA-1 Crypt - *sun_md5_crypt* - Sun MD5 Crypt - *sha256_crypt* - SHA-256 Crypt - *sha512_crypt* - SHA-512 Crypt - *apr_md5_crypt* - Apache’s MD5-Crypt variant - *phpass* - PHPass’ Portable Hash - *pbkdf2_digest* - Generic PBKDF2 Hashes - *cta_pbkdf2_sha1* - Cryptacular’s PBKDF2 hash - *dlitz_pbkdf2_sha1* - Dwayne Litzenberger’s PBKDF2 hash - *scram* - SCRAM Hash - *bsd_nthash* - FreeBSD’s MCF-compatible nthash encoding However, the only parameters accepted are 'salt' or 'salt_size'. You can use your own salt using 'salt', or have one generated automatically using 'salt_size'. If nothing is specified, a salt of size 8 will be generated. .. seealso:: :doc:`playbooks` An introduction to playbooks :doc:`playbooks_conditionals` Conditional statements in playbooks :doc:`playbooks_variables` All about variables `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/playbooks_roles.rst000066400000000000000000000356571241061774000213630ustar00rootroot00000000000000Playbook Roles and Include Statements ===================================== .. contents:: Topics Introduction ```````````` While it is possible to write a playbook in one very large file (and you might start out learning playbooks this way), eventually you'll want to reuse files and start to organize things. At a basic level, including task files allows you to break up bits of configuration policy into smaller files. Task includes pull in tasks from other files. Since handlers are tasks too, you can also include handler files from the 'handlers:' section. See :doc:`playbooks` if you need a review of these concepts. Playbooks can also include plays from other playbook files. When that is done, the plays will be inserted into the playbook to form a longer list of plays. When you start to think about it -- tasks, handlers, variables, and so on -- begin to form larger concepts. You start to think about modeling what something is, rather than how to make something look like something. It's no longer "apply this handful of THINGS to these hosts", you say "these hosts are dbservers" or "these hosts are webservers". In programming, we might call that "encapsulating" how things work. For instance, you can drive a car without knowing how the engine works. Roles in Ansible build on the idea of include files and combine them to form clean, reusable abstractions -- they allow you to focus more on the big picture and only dive down into the details when needed. We'll start with understanding includes so roles make more sense, but our ultimate goal should be understanding roles -- roles are great and you should use them every time you write playbooks. See the `ansible-examples `_ repository on GitHub for lots of examples of all of this put together. You may wish to have this open in a separate tab as you dive in. Task Include Files And Encouraging Reuse ```````````````````````````````````````` Suppose you want to reuse lists of tasks between plays or playbooks. You can use include files to do this. Use of included task lists is a great way to define a role that system is going to fulfill. Remember, the goal of a play in a playbook is to map a group of systems into multiple roles. Let's see what this looks like... A task include file simply contains a flat list of tasks, like so:: --- # possibly saved as tasks/foo.yml - name: placeholder foo command: /bin/foo - name: placeholder bar command: /bin/bar Include directives look like this, and can be mixed in with regular tasks in a playbook:: tasks: - include: tasks/foo.yml You can also pass variables into includes. We call this a 'parameterized include'. For instance, if deploying multiple wordpress instances, I could contain all of my wordpress tasks in a single wordpress.yml file, and use it like so:: tasks: - include: wordpress.yml user=timmy - include: wordpress.yml user=alice - include: wordpress.yml user=bob If you are running Ansible 1.4 and later, include syntax is streamlined to match roles, and also allows passing list and dictionary parameters:: tasks: - { include: wordpress.yml, user: timmy, ssh_keys: [ 'keys/one.txt', 'keys/two.txt' ] } Using either syntax, variables passed in can then be used in the included files. We've already covered them a bit in :doc:`playbooks_variables`. You can reference them like this:: {{ user }} (In addition to the explicitly passed-in parameters, all variables from the vars section are also available for use here as well.) Starting in 1.0, variables can also be passed to include files using an alternative syntax, which also supports structured variables:: tasks: - include: wordpress.yml vars: remote_user: timmy some_list_variable: - alpha - beta - gamma Playbooks can include other playbooks too, but that's mentioned in a later section. .. note:: As of 1.0, task include statements can be used at arbitrary depth. They were previously limited to a single level, so task includes could not include other files containing task includes. Includes can also be used in the 'handlers' section, for instance, if you want to define how to restart apache, you only have to do that once for all of your playbooks. You might make a handlers.yml that looks like:: --- # this might be in a file like handlers/handlers.yml - name: restart apache service: name=apache state=restarted And in your main playbook file, just include it like so, at the bottom of a play:: handlers: - include: handlers/handlers.yml You can mix in includes along with your regular non-included tasks and handlers. Includes can also be used to import one playbook file into another. This allows you to define a top-level playbook that is composed of other playbooks. For example:: - name: this is a play at the top level of a file hosts: all remote_user: root tasks: - name: say hi tags: foo shell: echo "hi..." - include: load_balancers.yml - include: webservers.yml - include: dbservers.yml Note that you cannot do variable substitution when including one playbook inside another. .. note:: You can not conditionally path the location to an include file, like you can with 'vars_files'. If you find yourself needing to do this, consider how you can restructure your playbook to be more class/role oriented. This is to say you cannot use a 'fact' to decide what include file to use. All hosts contained within the play are going to get the same tasks. ('*when*' provides some ability for hosts to conditionally skip tasks). .. _roles: Roles ````` .. versionadded:: 1.2 Now that you have learned about vars_files, tasks, and handlers, what is the best way to organize your playbooks? The short answer is to use roles! Roles are ways of automatically loading certain vars_files, tasks, and handlers based on a known file structure. Grouping content by roles also allows easy sharing of roles with other users. Roles are just automation around 'include' directives as described above, and really don't contain much additional magic beyond some improvements to search path handling for referenced files. However, that can be a big thing! Example project structure:: site.yml webservers.yml fooservers.yml roles/ common/ files/ templates/ tasks/ handlers/ vars/ meta/ webservers/ files/ templates/ tasks/ handlers/ vars/ meta/ In a playbook, it would look like this:: --- - hosts: webservers roles: - common - webservers This designates the following behaviors, for each role 'x': - If roles/x/tasks/main.yml exists, tasks listed therein will be added to the play - If roles/x/handlers/main.yml exists, handlers listed therein will be added to the play - If roles/x/vars/main.yml exists, variables listed therein will be added to the play - If roles/x/meta/main.yml exists, any role dependencies listed therein will be added to the list of roles (1.3 and later) - Any copy tasks can reference files in roles/x/files/ without having to path them relatively or absolutely - Any script tasks can reference scripts in roles/x/files/ without having to path them relatively or absolutely - Any template tasks can reference files in roles/x/templates/ without having to path them relatively or absolutely - Any include tasks can reference files in roles/x/tasks/ without having to path them relatively or absolutely In Ansible 1.4 and later you can configure a roles_path to search for roles. Use this to check all of your common roles out to one location, and share them easily between multiple playbook projects. See :doc:`intro_configuration` for details about how to set this up in ansible.cfg. .. note:: Role dependencies are discussed below. If any files are not present, they are just ignored. So it's ok to not have a 'vars/' subdirectory for the role, for instance. Note, you are still allowed to list tasks, vars_files, and handlers "loose" in playbooks without using roles, but roles are a good organizational feature and are highly recommended. If there are loose things in the playbook, the roles are evaluated first. Also, should you wish to parameterize roles, by adding variables, you can do so, like this:: --- - hosts: webservers roles: - common - { role: foo_app_instance, dir: '/opt/a', port: 5000 } - { role: foo_app_instance, dir: '/opt/b', port: 5001 } While it's probably not something you should do often, you can also conditionally apply roles like so:: --- - hosts: webservers roles: - { role: some_role, when: "ansible_os_family == 'RedHat'" } This works by applying the conditional to every task in the role. Conditionals are covered later on in the documentation. Finally, you may wish to assign tags to the roles you specify. You can do so inline::: --- - hosts: webservers roles: - { role: foo, tags: ["bar", "baz"] } If the play still has a 'tasks' section, those tasks are executed after roles are applied. If you want to define certain tasks to happen before AND after roles are applied, you can do this:: --- - hosts: webservers pre_tasks: - shell: echo 'hello' roles: - { role: some_role } tasks: - shell: echo 'still busy' post_tasks: - shell: echo 'goodbye' .. note:: If using tags with tasks (described later as a means of only running part of a playbook), be sure to also tag your pre_tasks and post_tasks and pass those along as well, especially if the pre and post tasks are used for monitoring outage window control or load balancing. Role Default Variables `````````````````````` .. versionadded:: 1.3 Role default variables allow you to set default variables for included or dependent roles (see below). To create defaults, simply add a `defaults/main.yml` file in your role directory. These variables will have the lowest priority of any variables available, and can be easily overridden by any other variable, including inventory variables. Role Dependencies ````````````````` .. versionadded:: 1.3 Role dependencies allow you to automatically pull in other roles when using a role. Role dependencies are stored in the `meta/main.yml` file contained within the role directory. This file should contain a list of roles and parameters to insert before the specified role, such as the following in an example `roles/myapp/meta/main.yml`:: --- dependencies: - { role: common, some_parameter: 3 } - { role: apache, port: 80 } - { role: postgres, dbname: blarg, other_parameter: 12 } Role dependencies can also be specified as a full path, just like top level roles:: --- dependencies: - { role: '/path/to/common/roles/foo', x: 1 } Roles dependencies are always executed before the role that includes them, and are recursive. By default, roles can also only be added as a dependency once - if another role also lists it as a dependency it will not be run again. This behavior can be overridden by adding `allow_duplicates: yes` to the `meta/main.yml` file. For example, a role named 'car' could add a role named 'wheel' to its dependencies as follows:: --- dependencies: - { role: wheel, n: 1 } - { role: wheel, n: 2 } - { role: wheel, n: 3 } - { role: wheel, n: 4 } And the `meta/main.yml` for wheel contained the following:: --- allow_duplicates: yes dependencies: - { role: tire } - { role: brake } The resulting order of execution would be as follows:: tire(n=1) brake(n=1) wheel(n=1) tire(n=2) brake(n=2) wheel(n=2) ... car .. note:: Variable inheritance and scope are detailed in the :doc:`playbooks_variables`. Embedding Modules In Roles `````````````````````````` This is an advanced topic that should not be relevant for most users. If you write a custom module (see :doc:`developing_modules`) you may wish to distribute it as part of a role. Generally speaking, Ansible as a project is very interested in taking high-quality modules into ansible core for inclusion, so this shouldn't be the norm, but it's quite easy to do. A good example for this is if you worked at a company called AcmeWidgets, and wrote an internal module that helped configure your internal software, and you wanted other people in your organization to easily use this module -- but you didn't want to tell everyone how to configure their Ansible library path. Alongside the 'tasks' and 'handlers' structure of a role, add a directory named 'library'. In this 'library' directory, then include the module directly inside of it. Assuming you had this:: roles/ my_custom_modules/ library/ module1 module2 The module will be usable in the role itself, as well as any roles that are called *after* this role, as follows:: - hosts: webservers roles: - my_custom_modules - some_other_role_using_my_custom_modules - yet_another_role_using_my_custom_modules This can also be used, with some limitations, to modify modules in Ansible's core distribution, such as to use development versions of modules before they are released in production releases. This is not always advisable as API signatures may change in core components, however, and is not always guaranteed to work. It can be a handy way of carrying a patch against a core module, however, should you have good reason for this. Naturally the project prefers that contributions be directed back to github whenever possible via a pull request. Ansible Galaxy `````````````` `Ansible Galaxy `_ is a free site for finding, downloading, rating, and reviewing all kinds of community developed Ansible roles and can be a great way to get a jumpstart on your automation projects. You can sign up with social auth, and the download client 'ansible-galaxy' is included in Ansible 1.4.2 and later. Read the "About" page on the Galaxy site for more information. .. seealso:: :doc:`YAMLSyntax` Learn about YAML syntax :doc:`playbooks` Review the basic Playbook language features :doc:`playbooks_best_practices` Various tips about managing playbooks in the real world :doc:`playbooks_variables` All about variables in playbooks :doc:`playbooks_conditionals` Conditionals in playbooks :doc:`playbooks_loops` Loops in playbooks :doc:`modules` Learn about available modules :doc:`developing_modules` Learn how to extend Ansible by writing your own modules `GitHub Ansible examples `_ Complete playbook files from the GitHub project source `Mailing List `_ Questions? Help? Ideas? Stop by the list on Google Groups ansible-1.7.2/docsite/rst/playbooks_special_topics.rst000066400000000000000000000011701241061774000232170ustar00rootroot00000000000000Playbooks: Special Topics ````````````````````````` Here are some playbook features that not everyone may need to learn, but can be quite useful for particular applications. Browsing these topics is recommended as you may find some useful tips here, but feel free to learn the basics of Ansible first and adopt these only if they seem relevant or useful to your environment. .. toctree:: :maxdepth: 1 playbooks_acceleration playbooks_async playbooks_checkmode playbooks_delegation playbooks_environment playbooks_error_handling playbooks_lookups playbooks_prompts playbooks_tags playbooks_vault ansible-1.7.2/docsite/rst/playbooks_tags.rst000066400000000000000000000027061241061774000211620ustar00rootroot00000000000000Tags ==== If you have a large playbook it may become useful to be able to run a specific part of the configuration without running the whole playbook. Both plays and tasks support a "tags:" attribute for this reason. Example:: tasks: - yum: name={{ item }} state=installed with_items: - httpd - memcached tags: - packages - template: src=templates/src.j2 dest=/etc/foo.conf tags: - configuration If you wanted to just run the "configuration" and "packages" part of a very long playbook, you could do this:: ansible-playbook example.yml --tags "configuration,packages" On the other hand, if you want to run a playbook *without* certain tasks, you could do this:: ansible-playbook example.yml --skip-tags "notification" You may also apply tags to roles:: roles: - { role: webserver, port: 5000, tags: [ 'web', 'foo' ] } And you may also tag basic include statements:: - include: foo.yml tags=web,foo Both of these have the function of tagging every single task inside the include statement. .. seealso:: :doc:`playbooks` An introduction to playbooks :doc:`playbooks_roles` Playbook organization by roles `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/playbooks_variables.rst000066400000000000000000001176531241061774000222040ustar00rootroot00000000000000Variables ========= .. contents:: Topics While automation exists to make it easier to make things repeatable, all of your systems are likely not exactly alike. All of your systems are likely not the same. On some systems you may want to set some behavior or configuration that is slightly different from others. Also, some of the observed behavior or state of remote systems might need to influence how you configure those systems. (Such as you might need to find out the IP address of a system and even use it as a configuration value on another system). You might have some templates for configuration files that are mostly the same, but slightly different based on those variables. Variables in Ansible are how we deal with differences between systems. Once understanding variables you'll also want to dig into :doc:`playbooks_conditionals` and :doc:`playbooks_loops`. Useful things like the "group_by" module and the "when" conditional can also be used with variables, and to help manage differences between systems. It's highly recommended that you consult the ansible-examples github repository to see a lot of examples of variables put to use. .. _valid_variable_names: What Makes A Valid Variable Name ```````````````````````````````` Before we start using variables it's important to know what are valid variable names. Variable names should be letters, numbers, and underscores. Variables should always start with a letter. "foo_port" is a great variable. "foo5" is fine too. "foo-port", "foo port", "foo.port" and "12" are not valid variable names. Easy enough, let's move on. .. _variables_in_inventory: Variables Defined in Inventory `````````````````````````````` We've actually already covered a lot about variables in another section, so far this shouldn't be terribly new, but a bit of a refresher. Often you'll want to set variables based on what groups a machine is in. For instance, maybe machines in Boston want to use 'boston.ntp.example.com' as an NTP server. See the :doc:`intro_inventory` document for multiple ways on how to define variables in inventory. .. _playbook_variables: Variables Defined in a Playbook ``````````````````````````````` In a playbook, it's possible to define variables directly inline like so:: - hosts: webservers vars: http_port: 80 This can be nice as it's right there when you are reading the playbook. .. _included_variables: Variables defined from included files and roles ``````````````````````````````````````````````` It turns out we've already talked about variables in another place too. As described in :doc:`playbooks_roles`, variables can also be included in the playbook via include files, which may or may not be part of an "Ansible Role". Usage of roles is preferred as it provides a nice organizational system. .. _about_jinja2: Using Variables: About Jinja2 ````````````````````````````` It's nice enough to know about how to define variables, but how do you use them? Ansible allows you to reference variables in your playbooks using the Jinja2 templating system. While you can do a lot of complex things in Jinja, only the basics are things you really need to learn at first. For instance, in a simple template, you can do something like:: My amp goes to {{ max_amp_value }} And that will provide the most basic form of variable substitution. This is also valid directly in playbooks, and you'll occasionally want to do things like:: template: src=foo.cfg.j2 dest={{ remote_install_path }}/foo.cfg In the above example, we used a variable to help decide where to place a file. Inside a template you automatically have access to all of the variables that are in scope for a host. Actually it's more than that -- you can also read variables about other hosts. We'll show how to do that in a bit. .. note:: ansible allows Jinja2 loops and conditionals in templates, but in playbooks, we do not use them. Ansible playbooks are pure machine-parseable YAML. This is a rather important feature as it means it is possible to code-generate pieces of files, or to have other ecosystem tools read Ansible files. Not everyone will need this but it can unlock possibilities. .. _jinja2_filters: Jinja2 Filters `````````````` .. note:: These are infrequently utilized features. Use them if they fit a use case you have, but this is optional knowledge. Filters in Jinja2 are a way of transforming template expressions from one kind of data into another. Jinja2 ships with many of these. See `builtin filters`_ in the official Jinja2 template documentation. In addition to those, Ansible supplies many more. .. _filters_for_formatting_data: Filters For Formatting Data --------------------------- The following filters will take a data structure in a template and render it in a slightly different format. These are occasionally useful for debugging:: {{ some_variable | to_nice_json }} {{ some_variable | to_nice_yaml }} .. _filters_used_with_conditionals: Filters Often Used With Conditionals ------------------------------------ The following tasks are illustrative of how filters can be used with conditionals:: tasks: - shell: /usr/bin/foo register: result ignore_errors: True - debug: msg="it failed" when: result|failed # in most cases you'll want a handler, but if you want to do something right now, this is nice - debug: msg="it changed" when: result|changed - debug: msg="it succeeded" when: result|success - debug: msg="it was skipped" when: result|skipped .. _forcing_variables_to_be_defined: Forcing Variables To Be Defined ------------------------------- The default behavior from ansible and ansible.cfg is to fail if variables are undefined, but you can turn this off. This allows an explicit check with this feature off:: {{ variable | mandatory }} The variable value will be used as is, but the template evaluation will raise an error if it is undefined. .. _defaulting_undefined_variables: Defaulting Undefined Variables ------------------------------ Jinja2 provides a useful 'default' filter, that is often a better approach to failing if a variable is not defined:: {{ some_variable | default(5) }} In the above example, if the variable 'some_variable' is not defined, the value used will be 5, rather than an error being raised. .. _set_theory_filters: Set Theory Filters -------------------- All these functions return a unique set from sets or lists. .. versionadded:: 1.4 To get a unique set from a list:: {{ list1 | unique }} To get a union of two lists:: {{ list1 | union(list2) }} To get the intersection of 2 lists (unique list of all items in both):: {{ list1 | intersect(list2) }} To get the difference of 2 lists (items in 1 that don't exist in 2):: {{ list1 | difference(list2) }} To get the symmetric difference of 2 lists (items exclusive to each list):: {{ list1 | symmetric_difference(list2) }} .. _version_comparison_filters: Version Comparison Filters -------------------------- .. versionadded:: 1.6 To compare a version number, such as checking if the ``ansible_distribution_version`` version is greater than or equal to '12.04', you can use the ``version_compare`` filter. The ``version_compare`` filter can also be used to evaluate the ``ansible_distribution_version``:: {{ ansible_distribution_version | version_compare('12.04', '>=') }} If ``ansible_distribution_version`` is greater than or equal to 12, this filter will return True, otherwise it will return False. The ``version_compare`` filter accepts the following operators:: <, lt, <=, le, >, gt, >=, ge, ==, =, eq, !=, <>, ne This filter also accepts a 3rd parameter, ``strict`` which defines if strict version parsing should be used. The default is ``False``, and if set as ``True`` will use more strict version parsing:: {{ sample_version_var | version_compare('1.0', operator='lt', strict=True) }} .. _random_filter: Random Number Filter -------------------- .. versionadded:: 1.6 This filter can be used similar to the default jinja2 random filter (returning a random item from a sequence of items), but can also generate a random number based on a range. To get a random item from a list:: {{ ['a','b','c']|random }} => 'c' To get a random number from 0 to supplied end:: {{ 59 |random}} * * * * root /script/from/cron Get a random number from 0 to 100 but in steps of 10:: {{ 100 |random(step=10) }} => 70 Get a random number from 1 to 100 but in steps of 10:: {{ 100 |random(1, 10) }} => 31 {{ 100 |random(start=1, step=10) }} => 51 .. _other_useful_filters: Other Useful Filters -------------------- To concatenate a list into a string:: {{ list | join(" ") }} To get the last name of a file path, like 'foo.txt' out of '/etc/asdf/foo.txt':: {{ path | basename }} To get the directory from a path:: {{ path | dirname }} To expand a path containing a tilde (`~`) character (new in version 1.5):: {{ path | expanduser }} To work with Base64 encoded strings:: {{ encoded | b64decode }} {{ decoded | b64encode }} To take an md5sum of a filename:: {{ filename | md5 }} To cast values as certain types, such as when you input a string as "True" from a vars_prompt and the system doesn't know it is a boolean value:: - debug: msg=test when: some_string_value | bool To match strings against a regex, use the "match" or "search" filter:: vars: url: "http://example.com/users/foo/resources/bar" tasks: - shell: "msg='matched pattern 1'" when: url | match("http://example.com/users/.*/resources/.*") - debug: "msg='matched pattern 2'" when: url | search("/users/.*/resources/.*") 'match' will require a complete match in the string, while 'search' will require a match inside of the string. To replace text in a string with regex, use the "regex_replace" filter:: # convert "ansible" to "able" {{ 'ansible' | regex_replace('^a.*i(.*)$', 'a\\1') }} # convert "foobar" to "bar" {{ 'foobar' | regex_replace('^f.*o(.*)$', '\\1') }} A few useful filters are typically added with each new Ansible release. The development documentation shows how to extend Ansible filters by writing your own as plugins, though in general, we encourage new ones to be added to core so everyone can make use of them. .. _yaml_gotchas: Hey Wait, A YAML Gotcha ``````````````````````` YAML syntax requires that if you start a value with {{ foo }} you quote the whole line, since it wants to be sure you aren't trying to start a YAML dictionary. This is covered on the :doc:`YAMLSyntax` page. This won't work:: - hosts: app_servers vars: app_path: {{ base_path }}/22 Do it like this and you'll be fine:: - hosts: app_servers vars: app_path: "{{ base_path }}/22" .. _vars_and_facts: Information discovered from systems: Facts `````````````````````````````````````````` There are other places where variables can come from, but these are a type of variable that are discovered, not set by the user. Facts are information derived from speaking with your remote systems. An example of this might be the ip address of the remote host, or what the operating system is. To see what information is available, try the following:: ansible hostname -m setup This will return a ginormous amount of variable data, which may look like this, as taken from Ansible 1.4 on a Ubuntu 12.04 system:: "ansible_all_ipv4_addresses": [ "REDACTED IP ADDRESS" ], "ansible_all_ipv6_addresses": [ "REDACTED IPV6 ADDRESS" ], "ansible_architecture": "x86_64", "ansible_bios_date": "09/20/2012", "ansible_bios_version": "6.00", "ansible_cmdline": { "BOOT_IMAGE": "/boot/vmlinuz-3.5.0-23-generic", "quiet": true, "ro": true, "root": "UUID=4195bff4-e157-4e41-8701-e93f0aec9e22", "splash": true }, "ansible_date_time": { "date": "2013-10-02", "day": "02", "epoch": "1380756810", "hour": "19", "iso8601": "2013-10-02T23:33:30Z", "iso8601_micro": "2013-10-02T23:33:30.036070Z", "minute": "33", "month": "10", "second": "30", "time": "19:33:30", "tz": "EDT", "year": "2013" }, "ansible_default_ipv4": { "address": "REDACTED", "alias": "eth0", "gateway": "REDACTED", "interface": "eth0", "macaddress": "REDACTED", "mtu": 1500, "netmask": "255.255.255.0", "network": "REDACTED", "type": "ether" }, "ansible_default_ipv6": {}, "ansible_devices": { "fd0": { "holders": [], "host": "", "model": null, "partitions": {}, "removable": "1", "rotational": "1", "scheduler_mode": "deadline", "sectors": "0", "sectorsize": "512", "size": "0.00 Bytes", "support_discard": "0", "vendor": null }, "sda": { "holders": [], "host": "SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 01)", "model": "VMware Virtual S", "partitions": { "sda1": { "sectors": "39843840", "sectorsize": 512, "size": "19.00 GB", "start": "2048" }, "sda2": { "sectors": "2", "sectorsize": 512, "size": "1.00 KB", "start": "39847934" }, "sda5": { "sectors": "2093056", "sectorsize": 512, "size": "1022.00 MB", "start": "39847936" } }, "removable": "0", "rotational": "1", "scheduler_mode": "deadline", "sectors": "41943040", "sectorsize": "512", "size": "20.00 GB", "support_discard": "0", "vendor": "VMware," }, "sr0": { "holders": [], "host": "IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)", "model": "VMware IDE CDR10", "partitions": {}, "removable": "1", "rotational": "1", "scheduler_mode": "deadline", "sectors": "2097151", "sectorsize": "512", "size": "1024.00 MB", "support_discard": "0", "vendor": "NECVMWar" } }, "ansible_distribution": "Ubuntu", "ansible_distribution_release": "precise", "ansible_distribution_version": "12.04", "ansible_domain": "", "ansible_env": { "COLORTERM": "gnome-terminal", "DISPLAY": ":0", "HOME": "/home/mdehaan", "LANG": "C", "LESSCLOSE": "/usr/bin/lesspipe %s %s", "LESSOPEN": "| /usr/bin/lesspipe %s", "LOGNAME": "root", "LS_COLORS": "rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:", "MAIL": "/var/mail/root", "OLDPWD": "/root/ansible/docsite", "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "PWD": "/root/ansible", "SHELL": "/bin/bash", "SHLVL": "1", "SUDO_COMMAND": "/bin/bash", "SUDO_GID": "1000", "SUDO_UID": "1000", "SUDO_USER": "mdehaan", "TERM": "xterm", "USER": "root", "USERNAME": "root", "XAUTHORITY": "/home/mdehaan/.Xauthority", "_": "/usr/local/bin/ansible" }, "ansible_eth0": { "active": true, "device": "eth0", "ipv4": { "address": "REDACTED", "netmask": "255.255.255.0", "network": "REDACTED" }, "ipv6": [ { "address": "REDACTED", "prefix": "64", "scope": "link" } ], "macaddress": "REDACTED", "module": "e1000", "mtu": 1500, "type": "ether" }, "ansible_form_factor": "Other", "ansible_fqdn": "ubuntu2", "ansible_hostname": "ubuntu2", "ansible_interfaces": [ "lo", "eth0" ], "ansible_kernel": "3.5.0-23-generic", "ansible_lo": { "active": true, "device": "lo", "ipv4": { "address": "127.0.0.1", "netmask": "255.0.0.0", "network": "127.0.0.0" }, "ipv6": [ { "address": "::1", "prefix": "128", "scope": "host" } ], "mtu": 16436, "type": "loopback" }, "ansible_lsb": { "codename": "precise", "description": "Ubuntu 12.04.2 LTS", "id": "Ubuntu", "major_release": "12", "release": "12.04" }, "ansible_machine": "x86_64", "ansible_memfree_mb": 74, "ansible_memtotal_mb": 991, "ansible_mounts": [ { "device": "/dev/sda1", "fstype": "ext4", "mount": "/", "options": "rw,errors=remount-ro", "size_available": 15032406016, "size_total": 20079898624 } ], "ansible_os_family": "Debian", "ansible_pkg_mgr": "apt", "ansible_processor": [ "Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz" ], "ansible_processor_cores": 1, "ansible_processor_count": 1, "ansible_processor_threads_per_core": 1, "ansible_processor_vcpus": 1, "ansible_product_name": "VMware Virtual Platform", "ansible_product_serial": "REDACTED", "ansible_product_uuid": "REDACTED", "ansible_product_version": "None", "ansible_python_version": "2.7.3", "ansible_selinux": false, "ansible_ssh_host_key_dsa_public": "REDACTED KEY VALUE" "ansible_ssh_host_key_ecdsa_public": "REDACTED KEY VALUE" "ansible_ssh_host_key_rsa_public": "REDACTED KEY VALUE" "ansible_swapfree_mb": 665, "ansible_swaptotal_mb": 1021, "ansible_system": "Linux", "ansible_system_vendor": "VMware, Inc.", "ansible_user_id": "root", "ansible_userspace_architecture": "x86_64", "ansible_userspace_bits": "64", "ansible_virtualization_role": "guest", "ansible_virtualization_type": "VMware" In the above the model of the first harddrive may be referenced in a template or playbook as:: {{ ansible_devices.sda.model }} Similarly, the hostname as the system reports it is:: {{ ansible_hostname }} Facts are frequently used in conditionals (see :doc:`playbooks_conditionals`) and also in templates. Facts can be also used to create dynamic groups of hosts that match particular criteria, see the :doc:`modules` documentation on 'group_by' for details, as well as in generalized conditional statements as discussed in the :doc:`playbooks_conditionals` chapter. .. _disabling_facts: Turning Off Facts ````````````````` If you know you don't need any fact data about your hosts, and know everything about your systems centrally, you can turn off fact gathering. This has advantages in scaling Ansible in push mode with very large numbers of systems, mainly, or if you are using Ansible on experimental platforms. In any play, just do this:: - hosts: whatever gather_facts: no .. _local_facts: Local Facts (Facts.d) ````````````````````` .. versionadded:: 1.3 As discussed in the playbooks chapter, Ansible facts are a way of getting data about remote systems for use in playbook variables. Usually these are discovered automatically by the 'setup' module in Ansible. Users can also write custom facts modules, as described in the API guide. However, what if you want to have a simple way to provide system or user provided data for use in Ansible variables, without writing a fact module? For instance, what if you want users to be able to control some aspect about how their systems are managed? "Facts.d" is one such mechanism. .. note:: Perhaps "local facts" is a bit of a misnomer, it means "locally supplied user values" as opposed to "centrally supplied user values", or what facts are -- "locally dynamically determined values". If a remotely managed system has an "/etc/ansible/facts.d" directory, any files in this directory ending in ".fact", can be JSON, INI, or executable files returning JSON, and these can supply local facts in Ansible. For instance assume a /etc/ansible/facts.d/preferences.fact:: [general] asdf=1 bar=2 This will produce a hash variable fact named "general" with 'asdf' and 'bar' as members. To validate this, run the following:: ansible -m setup -a "filter=ansible_local" And you will see the following fact added:: "ansible_local": { "preferences": { "general": { "asdf" : "1", "bar" : "2" } } } And this data can be accessed in a template/playbook as:: {{ ansible_local.preferences.general.asdf }} The local namespace prevents any user supplied fact from overriding system facts or variables defined elsewhere in the playbook. If you have a playbook that is copying over a custom fact and then running it, making an explicit call to re-run the setup module can allow that fact to be used during that particular play. Otherwise, it will be available in the next play that gathers fact information. Here is an example of what that might look like:: - hosts: webservers tasks: - name: create directory for ansible custom facts file: state=directory recurse=yes path=/etc/ansible/facts.d - name: install custom impi fact copy: src=ipmi.fact dest=/etc/ansible/facts.d - name: re-read facts after adding custom fact setup: filter=ansible_local In this pattern however, you could also write a fact module as well, and may wish to consider this as an option. .. _registered_variables: Registered Variables ```````````````````` Another major use of variables is running a command and using the result of that command to save the result into a variable. Results will vary from module to module. Use of -v when executing playbooks will show possible values for the results. The value of a task being executed in ansible can be saved in a variable and used later. See some examples of this in the :doc:`playbooks_conditionals` chapter. While it's mentioned elsewhere in that document too, here's a quick syntax example:: - hosts: web_servers tasks: - shell: /usr/bin/foo register: foo_result ignore_errors: True - shell: /usr/bin/bar when: foo_result.rc == 5 Registered variables are valid on the host the remainder of the playbook run, which is the same as the lifetime of "facts" in Ansible. Effectively registered variables are just like facts. .. _accessing_complex_variable_data: Accessing Complex Variable Data ``````````````````````````````` We already talked about facts a little higher up in the documentation. Some provided facts, like networking information, are made available as nested data structures. To access them a simple {{ foo }} is not sufficient, but it is still easy to do. Here's how we get an IP address:: {{ ansible_eth0["ipv4"]["address"] }} OR alternatively:: {{ ansible_eth0.ipv4.address }} Similarly, this is how we access the first element of an array:: {{ foo[0] }} .. _magic_variables_and_hostvars: Magic Variables, and How To Access Information About Other Hosts ```````````````````````````````````````````````````````````````` Even if you didn't define them yourself, Ansible provides a few variables for you automatically. The most important of these are 'hostvars', 'group_names', and 'groups'. Users should not use these names themselves as they are reserved. 'environment' is also reserved. Hostvars lets you ask about the variables of another host, including facts that have been gathered about that host. If, at this point, you haven't talked to that host yet in any play in the playbook or set of playbooks, you can get at the variables, but you will not be able to see the facts. If your database server wants to use the value of a 'fact' from another node, or an inventory variable assigned to another node, it's easy to do so within a template or even an action line:: {{ hostvars['test.example.com']['ansible_distribution'] }} Additionally, *group_names* is a list (array) of all the groups the current host is in. This can be used in templates using Jinja2 syntax to make template source files that vary based on the group membership (or role) of the host:: {% if 'webserver' in group_names %} # some part of a configuration file that only applies to webservers {% endif %} *groups* is a list of all the groups (and hosts) in the inventory. This can be used to enumerate all hosts within a group. For example:: {% for host in groups['app_servers'] %} # something that applies to all app servers. {% endfor %} A frequently used idiom is walking a group to find all IP addresses in that group:: {% for host in groups['app_servers'] %} {{ hostvars[host]['ansible_eth0']['ipv4']['address'] }} {% endfor %} An example of this could include pointing a frontend proxy server to all of the app servers, setting up the correct firewall rules between servers, etc. Additionally, *inventory_hostname* is the name of the hostname as configured in Ansible's inventory host file. This can be useful for when you don't want to rely on the discovered hostname `ansible_hostname` or for other mysterious reasons. If you have a long FQDN, *inventory_hostname_short* also contains the part up to the first period, without the rest of the domain. *play_hosts* is available as a list of hostnames that are in scope for the current play. This may be useful for filling out templates with multiple hostnames or for injecting the list into the rules for a load balancer. Don't worry about any of this unless you think you need it. You'll know when you do. Also available, *inventory_dir* is the pathname of the directory holding Ansible's inventory host file, *inventory_file* is the pathname and the filename pointing to the Ansible's inventory host file. .. _variable_file_seperation_details: Variable File Separation ```````````````````````` It's a great idea to keep your playbooks under source control, but you may wish to make the playbook source public while keeping certain important variables private. Similarly, sometimes you may just want to keep certain information in different files, away from the main playbook. You can do this by using an external variables file, or files, just like this:: --- - hosts: all remote_user: root vars: favcolor: blue vars_files: - /vars/external_vars.yml tasks: - name: this is just a placeholder command: /bin/echo foo This removes the risk of sharing sensitive data with others when sharing your playbook source with them. The contents of each variables file is a simple YAML dictionary, like this:: --- # in the above example, this would be vars/external_vars.yml somevar: somevalue password: magic .. note:: It's also possible to keep per-host and per-group variables in very similar files, this is covered in :doc:`intro_patterns`. .. _passing_variables_on_the_command_line: Passing Variables On The Command Line ````````````````````````````````````` In addition to `vars_prompt` and `vars_files`, it is possible to send variables over the Ansible command line. This is particularly useful when writing a generic release playbook where you may want to pass in the version of the application to deploy:: ansible-playbook release.yml --extra-vars "version=1.23.45 other_variable=foo" This is useful, for, among other things, setting the hosts group or the user for the playbook. Example:: --- - hosts: '{{ hosts }}' remote_user: '{{ user }}' tasks: - ... ansible-playbook release.yml --extra-vars "hosts=vipers user=starbuck" As of Ansible 1.2, you can also pass in extra vars as quoted JSON, like so:: --extra-vars '{"pacman":"mrs","ghosts":["inky","pinky","clyde","sue"]}' The key=value form is obviously simpler, but it's there if you need it! As of Ansible 1.3, extra vars can be loaded from a JSON file with the "@" syntax:: --extra-vars "@some_file.json" Also as of Ansible 1.3, extra vars can be formatted as YAML, either on the command line or in a file as above. .. _conditional_imports: Conditional Imports ``````````````````` .. note:: This behavior is infrequently used in Ansible. You may wish to skip this section. The 'group_by' module as described in the module documentation is a better way to achieve this behavior in most cases. Sometimes you will want to do certain things differently in a playbook based on certain criteria. Having one playbook that works on multiple platforms and OS versions is a good example. As an example, the name of the Apache package may be different between CentOS and Debian, but it is easily handled with a minimum of syntax in an Ansible Playbook:: --- - hosts: all remote_user: root vars_files: - "vars/common.yml" - [ "vars/{{ ansible_os_family }}.yml", "vars/os_defaults.yml" ] tasks: - name: make sure apache is running service: name={{ apache }} state=running .. note:: The variable 'ansible_os_family' is being interpolated into the list of filenames being defined for vars_files. As a reminder, the various YAML files contain just keys and values:: --- # for vars/CentOS.yml apache: httpd somethingelse: 42 How does this work? If the operating system was 'CentOS', the first file Ansible would try to import would be 'vars/CentOS.yml', followed by '/vars/os_defaults.yml' if that file did not exist. If no files in the list were found, an error would be raised. On Debian, it would instead first look towards 'vars/Debian.yml' instead of 'vars/CentOS.yml', before falling back on 'vars/os_defaults.yml'. Pretty simple. To use this conditional import feature, you'll need facter or ohai installed prior to running the playbook, but you can of course push this out with Ansible if you like:: # for facter ansible -m yum -a "pkg=facter ensure=installed" ansible -m yum -a "pkg=ruby-json ensure=installed" # for ohai ansible -m yum -a "pkg=ohai ensure=installed" Ansible's approach to configuration -- separating variables from tasks, keeps your playbooks from turning into arbitrary code with ugly nested ifs, conditionals, and so on - and results in more streamlined & auditable configuration rules -- especially because there are a minimum of decision points to track. .. _variable_precedence: Variable Precedence: Where Should I Put A Variable? ``````````````````````````````````````````````````` A lot of folks may ask about how variables override another. Ultimately it's Ansible's philosophy that it's better you know where to put a variable, and then you have to think about it a lot less. Avoid defining the variable "x" in 47 places and then ask the question "which x gets used". Why? Because that's not Ansible's Zen philosophy of doing things. There is only one Empire State Building. One Mona Lisa, etc. Figure out where to define a variable, and don't make it complicated. However, let's go ahead and get precedence out of the way! It exists. It's a real thing, and you might have a use for it. If multiple variables of the same name are defined in different places, they win in a certain order, which is:: * -e variables always win * then comes "most everything else" * then comes variables defined in inventory * then comes facts discovered about a system * then "role defaults", which are the most "defaulty" and lose in priority to everything. .. note:: In versions prior to 1.5.4, facts discovered about a system were in the "most everything else" category above. That seems a little theoretical. Let's show some examples and where you would choose to put what based on the kind of control you might want over values. First off, group variables are super powerful. Site wide defaults should be defined as a 'group_vars/all' setting. Group variables are generally placed alongside your inventory file. They can also be returned by a dynamic inventory script (see :doc:`intro_dynamic_inventory`) or defined in things like :doc:`tower` from the UI or API:: --- # file: /etc/ansible/group_vars/all # this is the site wide default ntp_server: default-time.example.com Regional information might be defined in a 'group_vars/region' variable. If this group is a child of the 'all' group (which it is, because all groups are), it will override the group that is higher up and more general:: --- # file: /etc/ansible/group_vars/boston ntp_server: boston-time.example.com If for some crazy reason we wanted to tell just a specific host to use a specific NTP server, it would then override the group variable!:: --- # file: /etc/ansible/host_vars/xyz.boston.example.com ntp_server: override.example.com So that covers inventory and what you would normally set there. It's a great place for things that deal with geography or behavior. Since groups are frequently the entity that maps roles onto hosts, it is sometimes a shortcut to set variables on the group instead of defining them on a role. You could go either way. Remember: Child groups override parent groups, and hosts always override their groups. Next up: learning about role variable precedence. We'll pretty much assume you are using roles at this point. You should be using roles for sure. Roles are great. You are using roles aren't you? Hint hint. Ok, so if you are writing a redistributable role with reasonable defaults, put those in the 'roles/x/defaults/main.yml' file. This means the role will bring along a default value but ANYTHING in Ansible will override it. It's just a default. That's why it says "defaults" :) See :doc:`playbooks_roles` for more info about this:: --- # file: roles/x/defaults/main.yml # if not overridden in inventory or as a parameter, this is the value that will be used http_port: 80 if you are writing a role and want to ensure the value in the role is absolutely used in that role, and is not going to be overridden by inventory, you should put it in roles/x/vars/main.yml like so, and inventory values cannot override it. -e however, still will:: --- # file: roles/x/vars/main.yml # this will absolutely be used in this role http_port: 80 So the above is a great way to plug in constants about the role that are always true. If you are not sharing your role with others, app specific behaviors like ports is fine to put in here. But if you are sharing roles with others, putting variables in here might be bad. Nobody will be able to override them with inventory, but they still can by passing a parameter to the role. Parameterized roles are useful. If you are using a role and want to override a default, pass it as a parameter to the role like so:: roles: - { name: apache, http_port: 8080 } This makes it clear to the playbook reader that you've made a conscious choice to override some default in the role, or pass in some configuration that the role can't assume by itself. It also allows you to pass something site-specific that isn't really part of the role you are sharing with others. This can often be used for things that might apply to some hosts multiple times, like so:: roles: - { role: app_user, name: Ian } - { role: app_user, name: Terry } - { role: app_user, name: Graham } - { role: app_user, name: John } That's a bit arbitrary, but you can see how the same role was invoked multiple Times. In that example it's quite likely there was no default for 'name' supplied at all. Ansible can yell at you when variables aren't defined -- it's the default behavior in fact. So that's a bit about roles. There are a few bonus things that go on with roles. Generally speaking, variables set in one role are available to others. This means if you have a "roles/common/vars/main.yml" you can set variables in there and make use of them in other roles and elsewhere in your playbook:: roles: - { role: common_settings } - { role: something, foo: 12 } - { role: something_else } .. note:: There are some protections in place to avoid the need to namespace variables. In the above, variables defined in common_settings are most definitely available to 'something' and 'something_else' tasks, but if "something's" guaranteed to have foo set at 12, even if somewhere deep in common settings it set foo to 20. So, that's precedence, explained in a more direct way. Don't worry about precedence, just think about if your role is defining a variable that is a default, or a "live" variable you definitely want to use. Inventory lies in precedence right in the middle, and if you want to forcibly override something, use -e. If you found that a little hard to understand, take a look at the `ansible-examples`_ repo on our github for a bit more about how all of these things can work together. .. _ansible-examples: https://github.com/ansible/ansible-examples .. _builtin filters: http://jinja.pocoo.org/docs/templates/#builtin-filters .. seealso:: :doc:`playbooks` An introduction to playbooks :doc:`playbooks_conditionals` Conditional statements in playbooks :doc:`playbooks_loops` Looping in playbooks :doc:`playbooks_roles` Playbook organization by roles :doc:`playbooks_best_practices` Best practices in playbooks `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/playbooks_vault.rst000066400000000000000000000106661241061774000213630ustar00rootroot00000000000000Vault ===== .. contents:: Topics New in Ansible 1.5, "Vault" is a feature of ansible that allows keeping encrypted data in source control. To enable this feature, a command line tool, `ansible-vault` is used to edit files, and a command line flag `--ask-vault-pass` or `--vault-password-file` is used. .. _what_can_be_encrypted_with_vault: What Can Be Encrypted With Vault ```````````````````````````````` The vault feature can encrypt any structured data file used by Ansible. This can include "group_vars/" or "host_vars/" inventory variables, variables loaded by "include_vars" or "vars_files", or variable files passed on the ansible-playbook command line with "-e @file.yml" or "-e @file.json". Role variables and defaults are also included! Because Ansible tasks, handlers, and so on are also data, these can also be encrypted with vault. If you'd like to not betray what variables you are even using, you can go as far to keep an individual task file entirely encrypted. However, that might be a little much and could annoy your coworkers :) .. _creating_files: Creating Encrypted Files ```````````````````````` To create a new encrypted data file, run the following command:: ansible-vault create foo.yml First you will be prompted for a password. The password used with vault currently must be the same for all files you wish to use together at the same time. After providing a password, the tool will launch whatever editor you have defined with $EDITOR, and defaults to vim. Once you are done with the editor session, the file will be saved as encrypted data. The default cipher is AES (which is shared-secret based). .. _editing_encrypted_files: Editing Encrypted Files ``````````````````````` To edit an encrypted file in place, use the `ansible-vault edit` command. This command will decrypt the file to a temporary file and allow you to edit the file, saving it back when done and removing the temporary file:: ansible-vault edit foo.yml .. _rekeying_files: Rekeying Encrypted Files ```````````````````````` Should you wish to change your password on a vault-encrypted file or files, you can do so with the rekey command:: ansible-vault rekey foo.yml bar.yml baz.yml This command can rekey multiple data files at once and will ask for the original password and also the new password. .. _encrypting_files: Encrypting Unencrypted Files ```````````````````````````` If you have existing files that you wish to encrypt, use the `ansible-vault encrypt` command. This command can operate on multiple files at once:: ansible-vault encrypt foo.yml bar.yml baz.yml .. _decrypting_files: Decrypting Encrypted Files `````````````````````````` If you have existing files that you no longer want to keep encrypted, you can permanently decrypt them by running the `ansible-vault decrypt` command. This command will save them unencrypted to the disk, so be sure you do not want `ansible-vault edit` instead:: ansible-vault decrypt foo.yml bar.yml baz.yml .. _running_a_playbook_with_vault: Running a Playbook With Vault ````````````````````````````` To run a playbook that contains vault-encrypted data files, you must pass one of two flags. To specify the vault-password interactively:: ansible-playbook site.yml --ask-vault-pass This prompt will then be used to decrypt (in memory only) any vault encrypted files that are accessed. Currently this requires that all passwords be encrypted with the same password. Alternatively, passwords can be specified with a file or a script, the script version will require Ansible 1.7 or later. When using this flag, ensure permissions on the file are such that no one else can access your key and do not add your key to source control:: ansible-playbook site.yml --vault-password-file ~/.vault_pass.txt ansible-playbook site.yml --vault-password-file ~/.vault_pass.py The password should be a string stored as a single line in the file. If you are using a script instead of a flat file, ensure that it is marked as executable, and that the password is printed to standard output. If your script needs to prompt for data, prompts can be sent to standard error. This is something you may wish to do if using Ansible from a continuous integration system like Jenkins. (The `--vault-password-file` option can also be used with the :ref:`ansible-pull` command if you wish, though this would require distributing the keys to your nodes, so understand the implications -- vault is more intended for push mode). ansible-1.7.2/docsite/rst/quickstart.rst000066400000000000000000000006161241061774000203310ustar00rootroot00000000000000Quickstart Video ```````````````` We've recorded a short video that shows how to get started with Ansible that you may like to use alongside the documentation. The `quickstart video `_ is about 20 minutes long and will show you some of the basics about your first steps with Ansible. Enjoy, and be sure to visit the rest of the documentation to learn more. ansible-1.7.2/docsite/rst/test_strategies.rst000066400000000000000000000266621241061774000213610ustar00rootroot00000000000000Testing Strategies ================== .. _testing_intro: Integrating Testing With Ansible Playbooks `````````````````````````````````````````` Many times, people ask, "how can I best integrate testing with Ansible playbooks?" There are many options. Ansible is actually designed to be a "fail-fast" and ordered system, therefore it makes it easy to embed testing directly in Ansible playbooks. In this chapter, we'll go into some patterns for integrating tests of infrastructure and discuss the right level of testing that may be appropriate. .. note:: This is a chapter about testing the application you are deploying, not the chapter on how to test Ansible modules during development. For that content, please hop over to the Development section. By incorporating a degree of testing into your deployment workflow, there will be fewer surprises when code hits production and, in many cases, tests can be leveraged in production to prevent failed updates from migrating across an entire installation. Since it's push-based, it's also very easy to run the steps on thelocalhost or testing servers. Ansible lets you insert as many checks and balances into your upgrade workflow as you would like to have. The Right Level of Testing `````````````````````````` Ansible resources are models of desired-state. As such, it should not be neccessary to test that services are running, packages are installed, or other such things. Ansible is the system that will ensure these things are declaratively true. Instead, assert these things in your playbooks. .. code-block:: yaml tasks: - service: name=foo state=running enabled=yes If you think the service may not be running, the best thing to do is request it to be running. If the service fails to start, Ansible will yell appropriately. (This should not be confused with whether the service is doing something functional, which we'll show more about how to do later). Check Mode As A Drift Test `````````````````````````` In the above setup, `--check` mode in Ansible can be used as a layer of testing as well. If running a deployment playbook against an existing system, using the `--check` flag to the `ansible` command will report if Ansible thinks it would have had to have made any changes to bring the system into a desired state. This can let you know up front if there is any need to deploy onto the given system. Ordinarily scripts and commands don't run in check mode, so if you want certain steps to always execute in check mode, such as calls to the script module, add the 'always_run' flag:: roles: - webserver tasks: - script: verify.sh always_run: True Modules That Are Useful for Testing ``````````````````````````````````` Certain playbook modules are particularly good for testing. Below is an example that ensures a port is open:: tasks: - wait_for: host={{ inventory_hostname }} port=22 delegate_to: localhost Here's an example of using the URI module to make sure a web service returns:: tasks: - action: uri url=http://www.example.com return_content=yes register: webpage - fail: msg='service is not happy' when: "'AWESOME' not in webpage.content" It's easy to push an arbitrary script (in any language) on a remote host and the script will automatically fail if it has a non-zero return code:: tasks: - script: test_script1 - script: test_script2 --parameter value --parameter2 value If using roles (you should be, roles are great!), scripts pushed by the script module can live in the 'files/' directory of a role. And the assert module makes it very easy to validate various kinds of truth:: tasks: - shell: /usr/bin/some-command --parameter value register: cmd_result - assert: that: - "'not ready' not in cmd_result.stderr" - "'gizmo enabled' in cmd_result.stdout" Should you feel the need to test for existance of files that are not declaratively set by your Ansible configuration, the 'stat' module is a great choice:: tasks: - stat: path=/path/to/something register: p - assert: that: - p.stat.exists and p.stat.isdir As mentioned above, there's no need to check things like the return codes of commands. Ansible is checking them automatically. Rather than checking for a user to exist, consider using the user module to make it exist. Ansible is a fail-fast system, so when there is an error creating that user, it will stop the playbook run. You do not have to check up behind it. Testing Lifecycle ````````````````` If writing some degree of basic validation of your application into your playbooks, they will run every time you deploy. As such, deploying into a local development VM and a stage environment will both validate that things are according to plan ahead of your production deploy. Your workflow may be something like this:: - Use the same playbook all the time with embedded tests in development - Use the playbook to deploy to a stage environment (with the same playbooks) that simulates production - Run an integration test battery written by your QA team against stage - Deploy to production, with the same integrated tests. Something like an integration test battery should be written by your QA team if you are a production webservice. This would include things like Selenium tests or automated API tests and would usually not be something embedded into your Ansible playbooks. However, it does make sense to include some basic health checks into your playbooks, and in some cases it may be possible to run a subset of the QA battery against remote nodes. This is what the next section covers. Integrating Testing With Rolling Updates ```````````````````````````````````````` If you have read into :doc:`playbooks_delegation` it may quickly become apparent that the rolling update pattern can be extended, and you can use the success or failure of the playbook run to decide whether to add a machine into a load balancer or not. This is the great culmination of embedded tests:: --- - hosts: webservers serial: 5 pre_tasks: - name: take out of load balancer pool command: /usr/bin/take_out_of_pool {{ inventory_hostname }} delegate_to: 127.0.0.1 roles: - common - webserver - apply_testing_checks post_tasks: - name: add back to load balancer pool command: /usr/bin/add_back_to_pool {{ inventory_hostname }} delegate_to: 127.0.0.1 Of course in the above, the "take out of the pool" and "add back" steps would be replaced with a call to a Ansible load balancer module or appropriate shell command. You might also have steps that use a monitoring module to start and end an outage window for the machine. However, what you can see from the above is that tests are used as a gate -- if the "apply_testing_checks" step is not performed, the machine will not go back into the pool. Read the delegation chapter about "max_fail_percentage" and you can also control how many failing tests will stop a rolling update from proceeding. This above approach can also be modified to run a step from a testing machine remotely against a machine:: --- - hosts: webservers serial: 5 pre_tasks: - name: take out of load balancer pool command: /usr/bin/take_out_of_pool {{ inventory_hostname }} delegate_to: 127.0.0.1 roles: - common - webserver tasks: - script: /srv/qa_team/app_testing_script.sh --server {{ inventory_hostname }} delegate_to: testing_server post_tasks: - name: add back to load balancer pool command: /usr/bin/add_back_to_pool {{ inventory_hostname }} delegate_to: 127.0.0.1 In the above example, a script is run from the testing server against a remote node prior to bringing it back into the pool. In the event of a problem, fix the few servers that fail using Ansible's automatically generated retry file to repeat the deploy on just those servers. Achieving Continous Deployment `````````````````````````````` If desired, the above techniques may be extended to enable continuous deployment practices. The workflow may look like this:: - Write and use automation to deploy local development VMs - Have a CI system like Jenkins deploy to a stage environment on every code change - The deploy job calls testing scripts to pass/fail a build on every deploy - If the deploy job succeeds, it runs the same deploy playbook against production inventory Some Ansible users use the above approach to deploy a half-dozen or dozen times an hour without taking all of their infrastructure offline. A culture of automated QA is vital if you wish to get to this level. If you are still doing a large amount of manual QA, you should still make the decision on whether to deploy manually as well, but it can still help to work in the rolling update patterns of the previous section and encorporate some basic health checks using modules like 'script', 'stat', 'uri', and 'assert'. Conclusion `````````` Ansible believes you should not need another framework to validate basic things of your infrastructure is true. This is the case because Ansible is an order-based system that will fail immediately on unhandled errors for a host, and prevent further configuration of that host. This forces errors to the top and shows them in a summary at the end of the Ansible run. However, as Ansible is designed as a multi-tier orchestration system, it makes it very easy to incorporate tests into the end of a playbook run, either using loose tasks or roles. When used with rolling updates, testing steps can decide whether to put a machine back into a load balanced pool or not. Finally, because Ansible errors propogate all the way up to the return code of the Ansible program itself, and Ansible by default runs in an easy push-based mode, Ansible is a great step to put into a build environment if you wish to use it to roll out systems as part of a Continous Integration/Continous Delivery pipeline, as is covered in sections above. The focus should not be on infrastructure testing, but on application testing, so we strongly encourage getting together with your QA team and ask what sort of tests would make sense to run every time you deploy development VMs, and which sort of tests they would like to run against the stage environment on every deploy. Obviously at the development stage, unit tests are great too. But don't unit test your playbook. Ansible describes states of resources declaratively, so you don't have to. If there are cases where you want to be sure of something though, that's great, and things like stat/assert are great go-to modules for that purpose. In all, testing is a very organizational and site-specific thing. Everybody should be doing it, but what makes the most sense for your environment will vary with what you are deploying and who is using it -- but everyone benefits from a more robust and reliable deployment system. .. seealso:: :doc:`modules` All the documentation for Ansible modules :doc:`playbooks` An introduction to playbooks :doc:`playbooks_delegation` Delegation, useful for working with loud balancers, clouds, and locally executed steps. `User Mailing List `_ Have a question? Stop by the google group! `irc.freenode.net `_ #ansible IRC chat channel ansible-1.7.2/docsite/rst/tower.rst000066400000000000000000000017761241061774000173070ustar00rootroot00000000000000Ansible Tower ````````````` `Ansible Tower `_ (formerly 'AWX') is a web-based solution that makes Ansible even more easy to use for IT teams of all kinds. It's designed to be the hub for all of your automation tasks. Tower allows you to control access to who can access what, even allowing sharing of SSH credentials without someone being able to transfer those credentials. Inventory can be graphically managed or synced with a wide variety of cloud sources. It logs all of your jobs, integrates well with LDAP, and has an amazing browsable REST API. Command line tools are available for easy integration with Jenkins as well. Provisioning callbacks provide great support for autoscaling topologies. Find out more about Tower features and how to download it on the `Ansible Tower webpage `_. Tower is free for usage for up to 10 nodes, and comes bundled with amazing support from Ansible, Inc. As you would expect, Tower is installed using Ansible playbooks! ansible-1.7.2/docsite/variables.dot000066400000000000000000000023621241061774000172550ustar00rootroot00000000000000digraph G { subgraph cluster_0 { "command line variables" -> "--extra-args" } subgraph cluster_1 { "role variables" -> "roles/rolename/vars.yml" -> "parameters passed to role" -> "parameters from dependent roles" } subgraph cluster_2 { "top-level playbook variables" -> "vars: directives" -> "vars_files: directives"; } subgraph cluster_3 { "inventory variables" -> "group_vars/all" -> "group_vars/grandparent1" -> "group_vars/parent1" -> "host_vars/myhostname"; "group_vars/all" -> "group_vars/grandparent2"; "group_vars/grandparent1" -> "group_vars/parent2" "group_vars/grandparent2" -> "host_vars/myhostname"; "group_vars/parent2" -> "host_vars/myhostname" } subgraph cluster_4 { "facts" -> "gathered host facts" "facts" -> "host facts from /etc/ansible/facts.d" "facts" -> "set_fact" "facts" -> "include_vars" } subgraph cluster_5 { "role defaults" -> "roles/rolename/defaults.yml" } "command line variables" -> "role variables" -> "top-level playbook variables" -> "inventory variables" -> "role defaults" -> "facts" } ansible-1.7.2/examples/000077500000000000000000000000001241061774000147565ustar00rootroot00000000000000ansible-1.7.2/examples/DOCUMENTATION.yml000066400000000000000000000015511241061774000175140ustar00rootroot00000000000000--- # If a key doesn't apply to your module (ex: choices, default, or # aliases) you can use the word 'null', or an empty list, [], where # appropriate. module: modulename short_description: This is a sentence describing the module description: - Longer description of the module - You might include instructions version_added: "X.Y" author: Your AWESOME name here notes: - Other things consumers of your module should know requirements: - list of required things - like the factor package - or a specic platform options: # One or more of the following option_name: description: - Words go here - that describe - this option required: true or false default: a string or the word null choices: [list, of, choices] aliases: [list, of, aliases] version_added: 1.X ansible-1.7.2/examples/ansible.cfg000066400000000000000000000160041241061774000170550ustar00rootroot00000000000000# config file for ansible -- http://ansible.com/ # ============================================== # nearly all parameters can be overridden in ansible-playbook # or with command line flags. ansible will read ANSIBLE_CONFIG, # ansible.cfg in the current working directory, .ansible.cfg in # the home directory or /etc/ansible/ansible.cfg, whichever it # finds first [defaults] # some basic default values... hostfile = /etc/ansible/hosts library = /usr/share/ansible remote_tmp = $HOME/.ansible/tmp pattern = * forks = 5 poll_interval = 15 sudo_user = root #ask_sudo_pass = True #ask_pass = True transport = smart remote_port = 22 module_lang = C # plays will gather facts by default, which contain information about # the remote system. # # smart - gather by default, but don't regather if already gathered # implicit - gather by default, turn off with gather_facts: False # explicit - do not gather by default, must say gather_facts: True gathering = implicit # additional paths to search for roles in, colon separated #roles_path = /etc/ansible/roles # uncomment this to disable SSH key host checking #host_key_checking = False # change this for alternative sudo implementations sudo_exe = sudo # what flags to pass to sudo #sudo_flags = -H # SSH timeout timeout = 10 # default user to use for playbooks if user is not specified # (/usr/bin/ansible will use current user as default) #remote_user = root # logging is off by default unless this path is defined # if so defined, consider logrotate #log_path = /var/log/ansible.log # default module name for /usr/bin/ansible #module_name = command # use this shell for commands executed under sudo # you may need to change this to bin/bash in rare instances # if sudo is constrained #executable = /bin/sh # if inventory variables overlap, does the higher precedence one win # or are hash values merged together? The default is 'replace' but # this can also be set to 'merge'. #hash_behaviour = replace # list any Jinja2 extensions to enable here: #jinja2_extensions = jinja2.ext.do,jinja2.ext.i18n # if set, always use this private key file for authentication, same as # if passing --private-key to ansible or ansible-playbook #private_key_file = /path/to/file # format of string {{ ansible_managed }} available within Jinja2 # templates indicates to users editing templates files will be replaced. # replacing {file}, {host} and {uid} and strftime codes with proper values. ansible_managed = Ansible managed: {file} modified on %Y-%m-%d %H:%M:%S by {uid} on {host} # by default, ansible-playbook will display "Skipping [host]" if it determines a task # should not be run on a host. Set this to "False" if you don't want to see these "Skipping" # messages. NOTE: the task header will still be shown regardless of whether or not the # task is skipped. #display_skipped_hosts = True # by default (as of 1.3), Ansible will raise errors when attempting to dereference # Jinja2 variables that are not set in templates or action lines. Uncomment this line # to revert the behavior to pre-1.3. #error_on_undefined_vars = False # by default (as of 1.6), Ansible may display warnings based on the configuration of the # system running ansible itself. This may include warnings about 3rd party packages or # other conditions that should be resolved if possible. # to disable these warnings, set the following value to False: #system_warnings = True # by default (as of 1.4), Ansible may display deprecation warnings for language # features that should no longer be used and will be removed in future versions. # to disable these warnings, set the following value to False: #deprecation_warnings = True # set plugin path directories here, separate with colons action_plugins = /usr/share/ansible_plugins/action_plugins callback_plugins = /usr/share/ansible_plugins/callback_plugins connection_plugins = /usr/share/ansible_plugins/connection_plugins lookup_plugins = /usr/share/ansible_plugins/lookup_plugins vars_plugins = /usr/share/ansible_plugins/vars_plugins filter_plugins = /usr/share/ansible_plugins/filter_plugins # don't like cows? that's unfortunate. # set to 1 if you don't want cowsay support or export ANSIBLE_NOCOWS=1 #nocows = 1 # don't like colors either? # set to 1 if you don't want colors, or export ANSIBLE_NOCOLOR=1 #nocolor = 1 # the CA certificate path used for validating SSL certs. This path # should exist on the controlling node, not the target nodes # common locations: # RHEL/CentOS: /etc/pki/tls/certs/ca-bundle.crt # Fedora : /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem # Ubuntu : /usr/share/ca-certificates/cacert.org/cacert.org.crt #ca_file_path = # the http user-agent string to use when fetching urls. Some web server # operators block the default urllib user agent as it is frequently used # by malicious attacks/scripts, so we set it to something unique to # avoid issues. #http_user_agent = ansible-agent [paramiko_connection] # uncomment this line to cause the paramiko connection plugin to not record new host # keys encountered. Increases performance on new host additions. Setting works independently of the # host key checking setting above. #record_host_keys=False # by default, Ansible requests a pseudo-terminal for commands executed under sudo. Uncomment this # line to disable this behaviour. #pty=False [ssh_connection] # ssh arguments to use # Leaving off ControlPersist will result in poor performance, so use # paramiko on older platforms rather than removing it #ssh_args = -o ControlMaster=auto -o ControlPersist=60s # The path to use for the ControlPath sockets. This defaults to # "%(directory)s/ansible-ssh-%%h-%%p-%%r", however on some systems with # very long hostnames or very long path names (caused by long user names or # deeply nested home directories) this can exceed the character limit on # file socket names (108 characters for most platforms). In that case, you # may wish to shorten the string below. # # Example: # control_path = %(directory)s/%%h-%%r #control_path = %(directory)s/ansible-ssh-%%h-%%p-%%r # Enabling pipelining reduces the number of SSH operations required to # execute a module on the remote server. This can result in a significant # performance improvement when enabled, however when using "sudo:" you must # first disable 'requiretty' in /etc/sudoers # # By default, this option is disabled to preserve compatibility with # sudoers configurations that have requiretty (the default on many distros). # #pipelining = False # if True, make ansible use scp if the connection type is ssh # (default is sftp) #scp_if_ssh = True [accelerate] accelerate_port = 5099 accelerate_timeout = 30 accelerate_connect_timeout = 5.0 # The daemon timeout is measured in minutes. This time is measured # from the last activity to the accelerate daemon. accelerate_daemon_timeout = 30 # If set to yes, accelerate_multi_key will allow multiple # private keys to be uploaded to it, though each user must # have access to the system via SSH to add a new key. The default # is "no". #accelerate_multi_key = yes ansible-1.7.2/examples/hosts000066400000000000000000000017051241061774000160440ustar00rootroot00000000000000# This is the default ansible 'hosts' file. # # It should live in /etc/ansible/hosts # # - Comments begin with the '#' character # - Blank lines are ignored # - Groups of hosts are delimited by [header] elements # - You can enter hostnames or ip addresses # - A hostname/ip can be a member of multiple groups # Ex 1: Ungrouped hosts, specify before any group headers. green.example.com blue.example.com 192.168.100.1 192.168.100.10 # Ex 2: A collection of hosts belonging to the 'webservers' group [webservers] alpha.example.org beta.example.org 192.168.1.100 192.168.1.110 # If you have multiple hosts following a pattern you can specify # them like this: www[001:006].example.com # Ex 3: A collection of database servers in the 'dbservers' group [dbservers] db01.intranet.mydomain.net db02.intranet.mydomain.net 10.25.1.56 10.25.1.57 # Here's another example of host ranges, this time there are no # leading 0s: db-[99:101]-node.example.com ansible-1.7.2/examples/issues/000077500000000000000000000000001241061774000162715ustar00rootroot00000000000000ansible-1.7.2/examples/issues/ISSUE_TEMPLATE.md000066400000000000000000000042661241061774000210060ustar00rootroot00000000000000##### Issue Type: Can you help us out in labelling this by telling us what kind of ticket this this? You can say “Bug Reportâ€, “Feature Ideaâ€, “Feature Pull Requestâ€, “New Module Pull Requestâ€, “Bugfix Pull Requestâ€, “Documentation Reportâ€, or “Docs Pull Requestâ€. ##### Ansible Version: Let us know what version of Ansible you are using. Please supply the verbatim output from running “ansible --versionâ€. If you're filing a ticket on a version of Ansible which is not the latest, we'd greatly appreciate it if you could retest on the latest version first. We don't expect you to test against the development branch most of the time, but we may ask for that if you have cycles. Thanks! ##### Environment: What OS are you running Ansible from and what OS are you managing? Examples include RHEL 5/6, Centos 5/6, Ubuntu 12.04/13.10, *BSD, Solaris. If this is a generic feature request or it doesn’t apply, just say “N/Aâ€. Not all tickets may be about operating system related things and we understand that. ##### Summary: Please summarize your request in this space. You will earn bonus points for being succinct, but please add enough detail so we can understand the request. Thanks! ##### Steps To Reproduce: If this is a bug ticket, please enter the steps you use to reproduce the problem in the space below. If this is a feature request, please enter the steps you would use to use the feature. If an example playbook is useful, please include a short reproducer inline, indented by four spaces. If a longer one is necessary, linking to one uploaded to gist.github.com would be great. Much appreciated! ##### Expected Results: Please enter your expected results in this space. When running the steps supplied above in the previous section, what did you expect to happen? If showing example output, please indent your output by four spaces so it will render correctly in GitHub's viewer thingy. ##### Actual Results: Please enter your actual results in this space. When running the steps supplied above, what actually happened? If you are showing example output, please indent your output by four spaces so it will render correctly in GitHub. Thanks again! ansible-1.7.2/examples/playbooks/000077500000000000000000000000001241061774000167615ustar00rootroot00000000000000ansible-1.7.2/examples/playbooks/README.md000066400000000000000000000002231241061774000202350ustar00rootroot00000000000000Playbook Examples ================= Playbook examples have moved. See [the Ansible-Examples repo](https://github.com/ansible/ansible-examples). ansible-1.7.2/examples/scripts/000077500000000000000000000000001241061774000164455ustar00rootroot00000000000000ansible-1.7.2/examples/scripts/ConfigureRemotingForAnsible.ps1000066400000000000000000000130131241061774000244630ustar00rootroot00000000000000# Script to set a windows computer up for remoting # The script checks the current WinRM/Remoting configuration and makes the necessary changes # set $VerbosePreference="Continue" before running the script in order to see the output of the script # # Written by Trond Hindenes # # Version 1.0 - July 6th, 2014 Param ( [string]$SubjectName = $env:COMPUTERNAME, [int]$CertValidityDays = 365, $CreateSelfSignedCert = $true ) #region function defs Function New-LegacySelfSignedCert { Param ( [string]$SubjectName, [int]$ValidDays = 365 ) $name = new-object -com "X509Enrollment.CX500DistinguishedName.1" $name.Encode("CN=$SubjectName", 0) $key = new-object -com "X509Enrollment.CX509PrivateKey.1" $key.ProviderName = "Microsoft RSA SChannel Cryptographic Provider" $key.KeySpec = 1 $key.Length = 1024 $key.SecurityDescriptor = "D:PAI(A;;0xd01f01ff;;;SY)(A;;0xd01f01ff;;;BA)(A;;0x80120089;;;NS)" $key.MachineContext = 1 $key.Create() $serverauthoid = new-object -com "X509Enrollment.CObjectId.1" $serverauthoid.InitializeFromValue("1.3.6.1.5.5.7.3.1") $ekuoids = new-object -com "X509Enrollment.CObjectIds.1" $ekuoids.add($serverauthoid) $ekuext = new-object -com "X509Enrollment.CX509ExtensionEnhancedKeyUsage.1" $ekuext.InitializeEncode($ekuoids) $cert = new-object -com "X509Enrollment.CX509CertificateRequestCertificate.1" $cert.InitializeFromPrivateKey(2, $key, "") $cert.Subject = $name $cert.Issuer = $cert.Subject $cert.NotBefore = (get-date).addDays(-1) $cert.NotAfter = $cert.NotBefore.AddDays($ValidDays) $cert.X509Extensions.Add($ekuext) $cert.Encode() $enrollment = new-object -com "X509Enrollment.CX509Enrollment.1" $enrollment.InitializeFromRequest($cert) $certdata = $enrollment.CreateRequest(0) $enrollment.InstallResponse(2, $certdata, 0, "") #return the thumprint of the last installed cert ls "Cert:\LocalMachine\my"| Sort-Object notbefore -Descending | select -First 1 | select -expand Thumbprint } #endregion #Start script $ErrorActionPreference = "Stop" #Detect PowerShell version if ($PSVersionTable.PSVersion.Major -lt 3) { Write-Error "PowerShell/Windows Management Framework needs to be updated to 3 or higher. Stopping script" } #Detect OS $Win32_OS = Get-WmiObject Win32_OperatingSystem switch ($Win32_OS.Version) { "6.2.9200" {$OSVersion = "Windows Server 2012"} "6.1.7601" {$OSVersion = "Windows Server 2008R2"} } #Set up remoting Write-verbose "Verifying WS-MAN" if (!(get-service "WinRM")) { Write-Error "I couldnt find the winRM service on this computer. Stopping" } Elseif ((get-service "WinRM").Status -ne "Running") { Write-Verbose "Starting WinRM" Start-Service -Name "WinRM" -ErrorAction Stop } #At this point, winrm should be running #Check that we have a ps session config if (!(Get-PSSessionConfiguration -verbose:$false) -or (!(get-childitem WSMan:\localhost\Listener))) { Write-Verbose "PS remoting is not enabled. Activating" try { Enable-PSRemoting -Force -ErrorAction SilentlyContinue } catch{} } Else { Write-Verbose "PS remoting is already active and running" } #At this point, test a remoting connection to localhost, which should work $result = invoke-command -ComputerName localhost -ScriptBlock {$env:computername} -ErrorVariable localremotingerror -ErrorAction SilentlyContinue $options = New-PSSessionOption -SkipCACheck -SkipCNCheck -SkipRevocationCheck $resultssl = New-PSSession -UseSSL -ComputerName "localhost" -SessionOption $options -ErrorVariable localremotingsslerror -ErrorAction SilentlyContinue if (!$result -and $resultssl) { Write-Verbose "HTTP-based sessions not enabled, HTTPS based sessions enabled" } ElseIf (!$result -and !$resultssl) { Write-error "Could not establish session on either HTTP or HTTPS. Breaking" } #at this point, make sure there is a SSL-based listener $listeners = dir WSMan:\localhost\Listener if (!($listeners | where {$_.Keys -like "TRANSPORT=HTTPS"})) { #HTTPS-based endpoint does not exist. if (($CreateSelfSignedCert) -and ($OSVersion -notmatch "2012")) { $thumprint = New-LegacySelfSignedCert -SubjectName $env:COMPUTERNAME } if (($CreateSelfSignedCert) -and ($OSVersion -match "2012")) { $cert = New-SelfSignedCertificate -DnsName $env:COMPUTERNAME -CertStoreLocation "Cert:\LocalMachine\My" $thumprint = $cert.Thumbprint } # Create the hashtables of settings to be used. $valueset = @{} $valueset.add('Hostname',$env:COMPUTERNAME) $valueset.add('CertificateThumbprint',$thumprint) $selectorset = @{} $selectorset.add('Transport','HTTPS') $selectorset.add('Address','*') Write-Verbose "Enabling SSL-based remoting" New-WSManInstance -ResourceURI 'winrm/config/Listener' -SelectorSet $selectorset -ValueSet $valueset } Else { Write-Verbose "SSL-based remoting already active" } #Check for basic authentication $basicauthsetting = Get-ChildItem WSMan:\localhost\Service\Auth | where {$_.Name -eq "Basic"} if (($basicauthsetting.Value) -eq $false) { Write-Verbose "Enabling basic auth" Set-Item -Path "WSMan:\localhost\Service\Auth\Basic" -Value $true } Else { Write-verbose "basic auth already enabled" } #FIrewall netsh advfirewall firewall add rule Profile=public name="Allow WinRM HTTPS" dir=in localport=5986 protocol=TCP action=allow Write-Verbose "PS Remoting successfully setup for Ansible" ansible-1.7.2/examples/scripts/upgrade_to_ps3.ps1000066400000000000000000000043511241061774000220130ustar00rootroot00000000000000 # Powershell script to upgrade a PowerShell 2.0 system to PowerShell 3.0 # based on http://occasionalutility.blogspot.com/2013/11/everyday-powershell-part-7-powershell.html # # some Ansible modules that may use Powershell 3 features, so systems may need # to be upgraded. This may be used by a sample playbook. Refer to the windows # documentation on docs.ansible.com for details. # # - hosts: windows # tasks: # - script: upgrade_to_ps3.ps1 # Get version of OS # 6.0 is 2008 # 6.1 is 2008 R2 # 6.2 is 2012 # 6.3 is 2012 R2 if ($PSVersionTable.psversion.Major -ge 3) { write-host "Powershell 3 Installed already; You don't need this" Exit } $powershellpath = "C:\powershell" function download-file { param ([string]$path, [string]$local) $client = new-object system.net.WebClient $client.Headers.Add("user-agent", "PowerShell") $client.downloadfile($path, $local) } if (!(test-path $powershellpath)) { New-Item -ItemType directory -Path $powershellpath } # .NET Framework 4.0 is necessary. #if (($PSVersionTable.CLRVersion.Major) -lt 2) #{ # $DownloadUrl = "http://download.microsoft.com/download/B/A/4/BA4A7E71-2906-4B2D-A0E1-80CF16844F5F/dotNetFx45_Full_x86_x64.exe" # $FileName = $DownLoadUrl.Split('/')[-1] # download-file $downloadurl "$powershellpath\$filename" # ."$powershellpath\$filename" /quiet /norestart #} #You may need to reboot after the .NET install if so just run the script again. # If the Operating System is above 6.2, then you already have PowerShell Version > 3 if ([Environment]::OSVersion.Version.Major -gt 6) { write-host "OS is new; upgrade not needed." Exit } $osminor = [environment]::OSVersion.Version.Minor if ($osminor -eq 1) { $DownloadUrl = "http://download.microsoft.com/download/E/7/6/E76850B8-DA6E-4FF5-8CCE-A24FC513FD16/Windows6.1-KB2506143-x64.msu" } elseif ($osminor -eq 0) { $DownloadUrl = "http://download.microsoft.com/download/E/7/6/E76850B8-DA6E-4FF5-8CCE-A24FC513FD16/Windows6.0-KB2506146-x64.msu" } else { # Nothing to do; In theory this point will never be reached. Exit } $FileName = $DownLoadUrl.Split('/')[-1] download-file $downloadurl "$powershellpath\$filename" Start-Process -FilePath ".$powershellpath\$filename" -ArgumentList /quiet ansible-1.7.2/examples/scripts/uptime.py000077500000000000000000000015321241061774000203260ustar00rootroot00000000000000#!/usr/bin/python # (c) 2012, Michael DeHaan # example of getting the uptime of all hosts, 10 at a time import ansible.runner import sys # construct the ansible runner and execute on all hosts results = ansible.runner.Runner( pattern='*', forks=10, module_name='command', module_args='/usr/bin/uptime', ).run() if results is None: print "No hosts found" sys.exit(1) print "UP ***********" for (hostname, result) in results['contacted'].items(): if not 'failed' in result: print "%s >>> %s" % (hostname, result['stdout']) print "FAILED *******" for (hostname, result) in results['contacted'].items(): if 'failed' in result: print "%s >>> %s" % (hostname, result['msg']) print "DOWN *********" for (hostname, result) in results['dark'].items(): print "%s >>> %s" % (hostname, result) ansible-1.7.2/examples/scripts/yaml_to_ini.py000077500000000000000000000166711241061774000213400ustar00rootroot00000000000000# (c) 2012, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . import ansible.constants as C from ansible.inventory.host import Host from ansible.inventory.group import Group from ansible import errors from ansible import utils import os import yaml import sys class InventoryParserYaml(object): ''' Host inventory parser for ansible ''' def __init__(self, filename=C.DEFAULT_HOST_LIST): sys.stderr.write("WARNING: YAML inventory files are deprecated in 0.6 and will be removed in 0.7, to migrate" + " download and run https://github.com/ansible/ansible/blob/devel/examples/scripts/yaml_to_ini.py\n") fh = open(filename) data = fh.read() fh.close() self._hosts = {} self._parse(data) def _make_host(self, hostname): if hostname in self._hosts: return self._hosts[hostname] else: host = Host(hostname) self._hosts[hostname] = host return host # see file 'test/yaml_hosts' for syntax def _parse(self, data): # FIXME: refactor into subfunctions all = Group('all') ungrouped = Group('ungrouped') all.add_child_group(ungrouped) self.groups = dict(all=all, ungrouped=ungrouped) grouped_hosts = [] yaml = utils.parse_yaml(data) # first add all groups for item in yaml: if type(item) == dict and 'group' in item: group = Group(item['group']) for subresult in item.get('hosts',[]): if type(subresult) in [ str, unicode ]: host = self._make_host(subresult) group.add_host(host) grouped_hosts.append(host) elif type(subresult) == dict: host = self._make_host(subresult['host']) vars = subresult.get('vars',{}) if type(vars) == list: for subitem in vars: for (k,v) in subitem.items(): host.set_variable(k,v) elif type(vars) == dict: for (k,v) in subresult.get('vars',{}).items(): host.set_variable(k,v) else: raise errors.AnsibleError("unexpected type for variable") group.add_host(host) grouped_hosts.append(host) vars = item.get('vars',{}) if type(vars) == dict: for (k,v) in item.get('vars',{}).items(): group.set_variable(k,v) elif type(vars) == list: for subitem in vars: if type(subitem) != dict: raise errors.AnsibleError("expected a dictionary") for (k,v) in subitem.items(): group.set_variable(k,v) self.groups[group.name] = group all.add_child_group(group) # add host definitions for item in yaml: if type(item) in [ str, unicode ]: host = self._make_host(item) if host not in grouped_hosts: ungrouped.add_host(host) elif type(item) == dict and 'host' in item: host = self._make_host(item['host']) vars = item.get('vars', {}) if type(vars)==list: varlist, vars = vars, {} for subitem in varlist: vars.update(subitem) for (k,v) in vars.items(): host.set_variable(k,v) groups = item.get('groups', {}) if type(groups) in [ str, unicode ]: groups = [ groups ] if type(groups)==list: for subitem in groups: if subitem in self.groups: group = self.groups[subitem] else: group = Group(subitem) self.groups[group.name] = group all.add_child_group(group) group.add_host(host) grouped_hosts.append(host) if host not in grouped_hosts: ungrouped.add_host(host) # make sure ungrouped.hosts is the complement of grouped_hosts ungrouped_hosts = [host for host in ungrouped.hosts if host not in grouped_hosts] if __name__ == "__main__": if len(sys.argv) != 2: print "usage: yaml_to_ini.py /path/to/ansible/hosts" sys.exit(1) result = "" original = sys.argv[1] yamlp = InventoryParserYaml(filename=sys.argv[1]) dirname = os.path.dirname(original) group_names = [ g.name for g in yamlp.groups.values() ] for group_name in sorted(group_names): record = yamlp.groups[group_name] if group_name == 'all': continue hosts = record.hosts result = result + "[%s]\n" % record.name for h in hosts: result = result + "%s\n" % h.name result = result + "\n" groupfiledir = os.path.join(dirname, "group_vars") if not os.path.exists(groupfiledir): print "* creating: %s" % groupfiledir os.makedirs(groupfiledir) groupfile = os.path.join(groupfiledir, group_name) print "* writing group variables for %s into %s" % (group_name, groupfile) groupfh = open(groupfile, 'w') groupfh.write(yaml.dump(record.get_variables())) groupfh.close() for (host_name, host_record) in yamlp._hosts.iteritems(): hostfiledir = os.path.join(dirname, "host_vars") if not os.path.exists(hostfiledir): print "* creating: %s" % hostfiledir os.makedirs(hostfiledir) hostfile = os.path.join(hostfiledir, host_record.name) print "* writing host variables for %s into %s" % (host_record.name, hostfile) hostfh = open(hostfile, 'w') hostfh.write(yaml.dump(host_record.get_variables())) hostfh.close() # also need to keep a hash of variables per each host # and variables per each group # and write those to disk newfilepath = os.path.join(dirname, "hosts.new") fdh = open(newfilepath, 'w') fdh.write(result) fdh.close() print "* COMPLETE: review your new inventory file and replace your original when ready" print "* new inventory file saved as %s" % newfilepath print "* edit group specific variables in %s/group_vars/" % dirname print "* edit host specific variables in %s/host_vars/" % dirname # now need to write this to disk as (oldname).new # and inform the user ansible-1.7.2/hacking/000077500000000000000000000000001241061774000145445ustar00rootroot00000000000000ansible-1.7.2/hacking/README.md000066400000000000000000000025471241061774000160330ustar00rootroot00000000000000'Hacking' directory tools ========================= Env-setup --------- The 'env-setup' script modifies your environment to allow you to run ansible from a git checkout using python 2.6+. (You may not use python 3 at this time). First, set up your environment to run from the checkout: $ source ./hacking/env-setup You will need some basic prerequisites installed. If you do not already have them and do not wish to install them from your operating system package manager, you can install them from pip $ easy_install pip # if pip is not already available $ pip install pyyaml jinja2 nose passlib pycrypto From there, follow ansible instructions on docs.ansible.com as normal. Test-module ----------- 'test-module' is a simple program that allows module developers (or testers) to run a module outside of the ansible program, locally, on the current machine. Example: $ ./hacking/test-module -m library/commands/shell -a "echo hi" This is a good way to insert a breakpoint into a module, for instance. Module-formatter ---------------- The module formatter is a script used to generate manpages and online module documentation. This is used by the system makefiles and rarely needs to be run directly. Authors ------- 'authors' is a simple script that generates a list of everyone who has contributed code to the ansible repository. ansible-1.7.2/hacking/authors.sh000077500000000000000000000006521241061774000165730ustar00rootroot00000000000000#!/bin/sh # script from http://stackoverflow.com/questions/12133583 set -e # Get a list of authors ordered by number of commits # and remove the commit count column AUTHORS=$(git --no-pager shortlog -nse | cut -f 2- | sort -f) if [ -z "$AUTHORS" ] ; then echo "Authors list was empty" exit 1 fi # Display the authors list and write it to the file echo "$AUTHORS" | tee "$(git rev-parse --show-toplevel)/AUTHORS.TXT" ansible-1.7.2/hacking/env-setup000077500000000000000000000027161241061774000164260ustar00rootroot00000000000000#!/bin/bash # usage: source ./hacking/env-setup [-q] # modifies environment for running Ansible from checkout # When run using source as directed, $0 gets set to bash, so we must use $BASH_SOURCE if [ -n "$BASH_SOURCE" ] ; then HACKING_DIR=`dirname $BASH_SOURCE` elif [ $(basename $0) = "env-setup" ]; then HACKING_DIR=`dirname $0` else HACKING_DIR="$PWD/hacking" fi # The below is an alternative to readlink -fn which doesn't exist on OS X # Source: http://stackoverflow.com/a/1678636 FULL_PATH=`python -c "import os; print(os.path.realpath('$HACKING_DIR'))"` ANSIBLE_HOME=`dirname "$FULL_PATH"` PREFIX_PYTHONPATH="$ANSIBLE_HOME/lib" PREFIX_PATH="$ANSIBLE_HOME/bin" PREFIX_MANPATH="$ANSIBLE_HOME/docs/man" [[ $PYTHONPATH != ${PREFIX_PYTHONPATH}* ]] && export PYTHONPATH=$PREFIX_PYTHONPATH:$PYTHONPATH [[ $PATH != ${PREFIX_PATH}* ]] && export PATH=$PREFIX_PATH:$PATH unset ANSIBLE_LIBRARY export ANSIBLE_LIBRARY="$ANSIBLE_HOME/library:`python $HACKING_DIR/get_library.py`" [[ $MANPATH != ${PREFIX_MANPATH}* ]] && export MANPATH=$PREFIX_MANPATH:$MANPATH # Print out values unless -q is set if [ $# -eq 0 -o "$1" != "-q" ] ; then echo "" echo "Setting up Ansible to run out of checkout..." echo "" echo "PATH=$PATH" echo "PYTHONPATH=$PYTHONPATH" echo "ANSIBLE_LIBRARY=$ANSIBLE_LIBRARY" echo "MANPATH=$MANPATH" echo "" echo "Remember, you may wish to specify your host file with -i" echo "" echo "Done!" echo "" fi ansible-1.7.2/hacking/env-setup.fish000066400000000000000000000026551241061774000173550ustar00rootroot00000000000000#!/usr/bin/env fish # usage: . ./hacking/env-setup [-q] # modifies environment for running Ansible from checkout set HACKING_DIR (dirname (status -f)) set FULL_PATH (python -c "import os; print(os.path.realpath('$HACKING_DIR'))") set ANSIBLE_HOME (dirname $FULL_PATH) set PREFIX_PYTHONPATH $ANSIBLE_HOME/lib set PREFIX_PATH $ANSIBLE_HOME/bin set PREFIX_MANPATH $ANSIBLE_HOME/docs/man # Set PYTHONPATH if not set -q PYTHONPATH set -gx PYTHONPATH $PREFIX_PYTHONPATH else switch PYTHONPATH case "$PREFIX_PYTHONPATH*" case "*" echo "Appending PYTHONPATH" set -gx PYTHONPATH $PREFIX_PYTHONPATH:$PYTHONPATH end end # Set PATH if not contains $PREFIX_PATH $PATH set -gx PATH $PREFIX_PATH $PATH end # Set MANPATH if not contains $PREFIX_MANPATH $MANPATH if not set -q MANPATH set -gx MANPATH $PREFIX_MANPATH else set -gx MANPATH $PREFIX_MANPATH $MANPATH end end set -gx ANSIBLE_LIBRARY $ANSIBLE_HOME/library if set -q argv switch $argv case '-q' '--quiet' case '*' echo "" echo "Setting up Ansible to run out of checkout..." echo "" echo "PATH=$PATH" echo "PYTHONPATH=$PYTHONPATH" echo "ANSIBLE_LIBRARY=$ANSIBLE_LIBRARY" echo "MANPATH=$MANPATH" echo "" echo "Remember, you may wish to specify your host file with -i" echo "" echo "Done!" echo "" end end ansible-1.7.2/hacking/get_library.py000077500000000000000000000015501241061774000174250ustar00rootroot00000000000000#!/usr/bin/env python # (c) 2014, Will Thames # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . # import ansible.constants as C import sys def main(): print C.DEFAULT_MODULE_PATH return 0 if __name__ == '__main__': sys.exit(main()) ansible-1.7.2/hacking/module_formatter.py000077500000000000000000000261031241061774000204730ustar00rootroot00000000000000#!/usr/bin/env python # (c) 2012, Jan-Piet Mens # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . # import os import glob import sys import yaml import codecs import json import ast import re import optparse import time import datetime import subprocess import cgi from jinja2 import Environment, FileSystemLoader import ansible.utils import ansible.utils.module_docs as module_docs ##################################################################################### # constants and paths # if a module is added in a version of Ansible older than this, don't print the version added information # in the module documentation because everyone is assumed to be running something newer than this already. TO_OLD_TO_BE_NOTABLE = 1.0 # Get parent directory of the directory this script lives in MODULEDIR=os.path.abspath(os.path.join( os.path.dirname(os.path.realpath(__file__)), os.pardir, 'library' )) # The name of the DOCUMENTATION template EXAMPLE_YAML=os.path.abspath(os.path.join( os.path.dirname(os.path.realpath(__file__)), os.pardir, 'examples', 'DOCUMENTATION.yml' )) _ITALIC = re.compile(r"I\(([^)]+)\)") _BOLD = re.compile(r"B\(([^)]+)\)") _MODULE = re.compile(r"M\(([^)]+)\)") _URL = re.compile(r"U\(([^)]+)\)") _CONST = re.compile(r"C\(([^)]+)\)") ##################################################################################### def rst_ify(text): ''' convert symbols like I(this is in italics) to valid restructured text ''' t = _ITALIC.sub(r'*' + r"\1" + r"*", text) t = _BOLD.sub(r'**' + r"\1" + r"**", t) t = _MODULE.sub(r'``' + r"\1" + r"``", t) t = _URL.sub(r"\1", t) t = _CONST.sub(r'``' + r"\1" + r"``", t) return t ##################################################################################### def html_ify(text): ''' convert symbols like I(this is in italics) to valid HTML ''' t = cgi.escape(text) t = _ITALIC.sub("" + r"\1" + "", t) t = _BOLD.sub("" + r"\1" + "", t) t = _MODULE.sub("" + r"\1" + "", t) t = _URL.sub("" + r"\1" + "", t) t = _CONST.sub("" + r"\1" + "", t) return t ##################################################################################### def rst_fmt(text, fmt): ''' helper for Jinja2 to do format strings ''' return fmt % (text) ##################################################################################### def rst_xline(width, char="="): ''' return a restructured text line of a given length ''' return char * width ##################################################################################### def write_data(text, options, outputname, module): ''' dumps module output to a file or the screen, as requested ''' if options.output_dir is not None: f = open(os.path.join(options.output_dir, outputname % module), 'w') f.write(text.encode('utf-8')) f.close() else: print text ##################################################################################### def list_modules(module_dir): ''' returns a hash of categories, each category being a hash of module names to file paths ''' categories = dict(all=dict()) files = glob.glob("%s/*" % module_dir) for d in files: if os.path.isdir(d): files2 = glob.glob("%s/*" % d) for f in files2: if f.endswith(".ps1"): # windows powershell modules have documentation stubs in python docstring # format (they are not executed) so skip the ps1 format files continue tokens = f.split("/") module = tokens[-1] category = tokens[-2] if not category in categories: categories[category] = {} categories[category][module] = f categories['all'][module] = f return categories ##################################################################################### def generate_parser(): ''' generate an optparse parser ''' p = optparse.OptionParser( version='%prog 1.0', usage='usage: %prog [options] arg1 arg2', description='Generate module documentation from metadata', ) p.add_option("-A", "--ansible-version", action="store", dest="ansible_version", default="unknown", help="Ansible version number") p.add_option("-M", "--module-dir", action="store", dest="module_dir", default=MODULEDIR, help="Ansible library path") p.add_option("-T", "--template-dir", action="store", dest="template_dir", default="hacking/templates", help="directory containing Jinja2 templates") p.add_option("-t", "--type", action='store', dest='type', choices=['rst'], default='rst', help="Document type") p.add_option("-v", "--verbose", action='store_true', default=False, help="Verbose") p.add_option("-o", "--output-dir", action="store", dest="output_dir", default=None, help="Output directory for module files") p.add_option("-I", "--includes-file", action="store", dest="includes_file", default=None, help="Create a file containing list of processed modules") p.add_option('-V', action='version', help='Show version number and exit') return p ##################################################################################### def jinja2_environment(template_dir, typ): env = Environment(loader=FileSystemLoader(template_dir), variable_start_string="@{", variable_end_string="}@", trim_blocks=True, ) env.globals['xline'] = rst_xline if typ == 'rst': env.filters['convert_symbols_to_format'] = rst_ify env.filters['html_ify'] = html_ify env.filters['fmt'] = rst_fmt env.filters['xline'] = rst_xline template = env.get_template('rst.j2') outputname = "%s_module.rst" else: raise Exception("unknown module format type: %s" % typ) return env, template, outputname ##################################################################################### def process_module(module, options, env, template, outputname, module_map): print "rendering: %s" % module fname = module_map[module] # ignore files with extensions if "." in os.path.basename(fname): return # use ansible core library to parse out doc metadata YAML and plaintext examples doc, examples = ansible.utils.module_docs.get_docstring(fname, verbose=options.verbose) # crash if module is missing documentation and not explicitly hidden from docs index if doc is None and module not in ansible.utils.module_docs.BLACKLIST_MODULES: sys.stderr.write("*** ERROR: CORE MODULE MISSING DOCUMENTATION: %s, %s ***\n" % (fname, module)) sys.exit(1) if doc is None: return "SKIPPED" all_keys = [] if not 'version_added' in doc: sys.stderr.write("*** ERROR: missing version_added in: %s ***\n" % module) sys.exit(1) added = 0 if doc['version_added'] == 'historical': del doc['version_added'] else: added = doc['version_added'] # don't show version added information if it's too old to be called out if added: added_tokens = str(added).split(".") added = added_tokens[0] + "." + added_tokens[1] added_float = float(added) if added and added_float < TO_OLD_TO_BE_NOTABLE: del doc['version_added'] for (k,v) in doc['options'].iteritems(): all_keys.append(k) all_keys = sorted(all_keys) doc['option_keys'] = all_keys doc['filename'] = fname doc['docuri'] = doc['module'].replace('_', '-') doc['now_date'] = datetime.date.today().strftime('%Y-%m-%d') doc['ansible_version'] = options.ansible_version doc['plainexamples'] = examples #plain text # here is where we build the table of contents... text = template.render(doc) write_data(text, options, outputname, module) ##################################################################################### def process_category(category, categories, options, env, template, outputname): module_map = categories[category] category_file_path = os.path.join(options.output_dir, "list_of_%s_modules.rst" % category) category_file = open(category_file_path, "w") print "*** recording category %s in %s ***" % (category, category_file_path) # TODO: start a new category file category = category.replace("_"," ") category = category.title() modules = module_map.keys() modules.sort() category_header = "%s Modules" % (category.title()) underscores = "`" * len(category_header) category_file.write("""\ %s %s .. toctree:: :maxdepth: 1 """ % (category_header, underscores)) for module in modules: result = process_module(module, options, env, template, outputname, module_map) if result != "SKIPPED": category_file.write(" %s_module\n" % module) category_file.close() # TODO: end a new category file ##################################################################################### def validate_options(options): ''' validate option parser options ''' if not options.module_dir: print >>sys.stderr, "--module-dir is required" sys.exit(1) if not os.path.exists(options.module_dir): print >>sys.stderr, "--module-dir does not exist: %s" % options.module_dir sys.exit(1) if not options.template_dir: print "--template-dir must be specified" sys.exit(1) ##################################################################################### def main(): p = generate_parser() (options, args) = p.parse_args() validate_options(options) env, template, outputname = jinja2_environment(options.template_dir, options.type) categories = list_modules(options.module_dir) last_category = None category_names = categories.keys() category_names.sort() category_list_path = os.path.join(options.output_dir, "modules_by_category.rst") category_list_file = open(category_list_path, "w") category_list_file.write("Module Index\n") category_list_file.write("============\n") category_list_file.write("\n\n") category_list_file.write(".. toctree::\n") category_list_file.write(" :maxdepth: 1\n\n") for category in category_names: category_list_file.write(" list_of_%s_modules\n" % category) process_category(category, categories, options, env, template, outputname) category_list_file.close() if __name__ == '__main__': main() ansible-1.7.2/hacking/templates/000077500000000000000000000000001241061774000165425ustar00rootroot00000000000000ansible-1.7.2/hacking/templates/rst.j2000066400000000000000000000043431241061774000176130ustar00rootroot00000000000000.. _@{ module }@: {% if short_description %} {% set title = module + ' - ' + short_description|convert_symbols_to_format %} {% else %} {% set title = module %} {% endif %} {% set title_len = title|length %} @{ title }@ @{ '+' * title_len }@ {% if author %} :Author: @{ author }@ {% endif %} .. contents:: :local: :depth: 1 {# ------------------------------------------ # # Please note: this looks like a core dump # but it isn't one. # --------------------------------------------#} Synopsis -------- {% if version_added is defined -%} .. versionadded:: @{ version_added }@ {% endif %} {% for desc in description -%} @{ desc | convert_symbols_to_format }@ {% endfor %} {% if options -%} Options ------- .. raw:: html {% for k in option_keys %} {% set v = options[k] %} {% if v.get('type', 'not_bool') == 'bool' %} {% else %} {% endif %} {% endfor %}
    parameter required default choices comments
    @{ k }@ {% if v.get('required', False) %}yes{% else %}no{% endif %} {% if v['default'] %}@{ v['default'] }@{% endif %}
    • yes
    • no
      {% for choice in v.get('choices',[]) -%}
    • @{ choice }@
      • {% endfor -%}
    		{% for desc in v.description -%}@{ desc | html_ify }@{% endfor -%}{% if v['version_added'] %} (added in Ansible @{v['version_added']}@){% endif %}
    {% endif %} {% if requirements %} {% for req in requirements %} .. note:: Requires @{ req | convert_symbols_to_format }@ {% endfor %} {% endif %} {% if examples or plainexamples %} Examples -------- .. raw:: html {% for example in examples %} {% if example['description'] %}

    @{ example['description'] | html_ify }@

    {% endif %} 

    @{ example['code'] | escape | indent(4, True) }@

    {% endfor %}
    {% if plainexamples %} :: @{ plainexamples | indent(4, True) }@ {% endif %} {% endif %} {% if notes %} {% for note in notes %} .. note:: @{ note | convert_symbols_to_format }@ {% endfor %} {% endif %} ansible-1.7.2/hacking/test-module000077500000000000000000000150501241061774000167350ustar00rootroot00000000000000#!/usr/bin/env python # (c) 2012, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . # # this script is for testing modules without running through the # entire guts of ansible, and is very helpful for when developing # modules # # example: # test-module -m ../library/commands/command -a "/bin/sleep 3" # test-module -m ../library/system/service -a "name=httpd ensure=restarted" # test-module -m ../library/system/service -a "name=httpd ensure=restarted" --debugger /usr/bin/pdb # test-modulr -m ../library/file/lineinfile -a "dest=/etc/exports line='/srv/home hostname1(rw,sync)'" --check import sys import base64 import os import subprocess import traceback import optparse import ansible.utils as utils import ansible.module_common as module_common import ansible.constants as C try: import json except ImportError: import simplejson as json def parse(): """parse command line :return : (options, args)""" parser = optparse.OptionParser() parser.usage = "%prog -[options] (-h for help)" parser.add_option('-m', '--module-path', dest='module_path', help="REQUIRED: full path of module source to execute") parser.add_option('-a', '--args', dest='module_args', default="", help="module argument string") parser.add_option('-D', '--debugger', dest='debugger', help="path to python debugger (e.g. /usr/bin/pdb)") parser.add_option('-I', '--interpreter', dest='interpreter', help="path to interpeter to use for this module (e.g. ansible_python_interpreter=/usr/bin/python)", metavar='INTERPRETER_TYPE=INTERPRETER_PATH') parser.add_option('-c', '--check', dest='check', action='store_true', help="run the module in check mode") options, args = parser.parse_args() if not options.module_path: parser.print_help() sys.exit(1) else: return options, args def write_argsfile(argstring, json=False): """ Write args to a file for old-style module's use. """ argspath = os.path.expanduser("~/.ansible_test_module_arguments") argsfile = open(argspath, 'w') if json: args = utils.parse_kv(argstring) argstring = utils.jsonify(args) argsfile.write(argstring) argsfile.close() return argspath def boilerplate_module(modfile, args, interpreter, check): """ simulate what ansible does with new style modules """ #module_fh = open(modfile) #module_data = module_fh.read() #module_fh.close() replacer = module_common.ModuleReplacer() #included_boilerplate = module_data.find(module_common.REPLACER) != -1 or module_data.find("import ansible.module_utils") != -1 complex_args = {} if args.startswith("@"): # Argument is a YAML file (JSON is a subset of YAML) complex_args = utils.combine_vars(complex_args, utils.parse_yaml_from_file(args[1:])) args='' elif args.startswith("{"): # Argument is a YAML document (not a file) complex_args = utils.combine_vars(complex_args, utils.parse_yaml(args)) args='' inject = {} if interpreter: if '=' not in interpreter: print 'interpeter must by in the form of ansible_python_interpreter=/usr/bin/python' sys.exit(1) interpreter_type, interpreter_path = interpreter.split('=') if not interpreter_type.startswith('ansible_'): interpreter_type = 'ansible_%s' % interpreter_type if not interpreter_type.endswith('_interpreter'): interpreter_type = '%s_interpreter' % interpreter_type inject[interpreter_type] = interpreter_path if check: complex_args['CHECKMODE'] = True (module_data, module_style, shebang) = replacer.modify_module( modfile, complex_args, args, inject ) modfile2_path = os.path.expanduser("~/.ansible_module_generated") print "* including generated source, if any, saving to: %s" % modfile2_path print "* this may offset any line numbers in tracebacks/debuggers!" modfile2 = open(modfile2_path, 'w') modfile2.write(module_data) modfile2.close() modfile = modfile2_path return (modfile2_path, module_style) def runtest( modfile, argspath): """Test run a module, piping it's output for reporting.""" os.system("chmod +x %s" % modfile) invoke = "%s" % (modfile) if argspath is not None: invoke = "%s %s" % (modfile, argspath) cmd = subprocess.Popen(invoke, shell=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE) (out, err) = cmd.communicate() try: print "***********************************" print "RAW OUTPUT" print out print err results = utils.parse_json(out) except: print "***********************************" print "INVALID OUTPUT FORMAT" print out traceback.print_exc() sys.exit(1) print "***********************************" print "PARSED OUTPUT" print utils.jsonify(results,format=True) def rundebug(debugger, modfile, argspath): """Run interactively with console debugger.""" if argspath is not None: subprocess.call("%s %s %s" % (debugger, modfile, argspath), shell=True) else: subprocess.call("%s %s" % (debugger, modfile), shell=True) def main(): options, args = parse() (modfile, module_style) = boilerplate_module(options.module_path, options.module_args, options.interpreter, options.check) argspath=None if module_style != 'new': if module_style == 'non_native_want_json': argspath = write_argsfile(options.module_args, json=True) elif module_style == 'old': argspath = write_argsfile(options.module_args, json=False) else: raise Exception("internal error, unexpected module style: %s" % module_style) if options.debugger: rundebug(options.debugger, modfile, argspath) else: runtest(modfile, argspath) if __name__ == "__main__": main() ansible-1.7.2/legacy/000077500000000000000000000000001241061774000144045ustar00rootroot00000000000000ansible-1.7.2/legacy/gce_tests.py000066400000000000000000001275531241061774000167530ustar00rootroot00000000000000#!/usr/bin/env python # Copyright 2013 Google Inc. # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . # This is a custom functional test script for the Google Compute Engine # ansible modules. In order to run these tests, you must: # 1) Create a Google Cloud Platform account and enable the Google # Compute Engine service and billing # 2) Download, install, and configure 'gcutil' # see [https://developers.google.com/compute/docs/gcutil/] # 3) Convert your GCE Service Account private key from PKCS12 to PEM format # $ openssl pkcs12 -in pkey.pkcs12 -passin pass:notasecret \ # > -nodes -nocerts | openssl rsa -out pkey.pem # 4) Make sure you have libcloud 0.13.3 or later installed. # 5) Make sure you have a libcloud 'secrets.py' file in your PYTHONPATH # 6) Set GCE_PARAMS and GCE_KEYWORD_PARMS in your 'secrets.py' file. # 7) Set up a simple hosts file # $ echo 127.0.0.1 > ~/ansible_hosts # $ echo "export ANSIBLE_HOSTS='~/ansible_hosts'" >> ~/.bashrc # $ . ~/.bashrc # 8) Set up your ansible 'hacking' environment # $ cd ~/ansible # $ . hacking/env-setup # $ export ANSIBLE_HOST_KEY_CHECKING=no # $ ansible all -m ping # 9) Set your PROJECT variable below # 10) Run and time the tests and log output, take ~30 minutes to run # $ time stdbuf -oL python test/gce_tests.py 2>&1 | tee log # # Last update: gcutil-1.11.0 and v1beta16 # Set this to your test Project ID PROJECT="google.com:erjohnso" # debugging DEBUG=False # lots of debugging output VERBOSE=True # on failure, display ansible command and expected/actual result # location - note that some tests rely on the module's 'default' # region/zone, which should match the settings below. REGION="us-central1" ZONE="%s-a" % REGION # Peeking is a way to trigger looking at a specified set of resources # before and/or after a test run. The 'test_cases' data structure below # has a few tests with 'peek_before' and 'peek_after'. When those keys # are set and PEEKING_ENABLED is True, then these steps will be executed # to aid in debugging tests. Normally, this is not needed. PEEKING_ENABLED=False # disks DNAME="aaaaa-ansible-disk" DNAME2="aaaaa-ansible-disk2" DNAME6="aaaaa-ansible-inst6" DNAME7="aaaaa-ansible-inst7" USE_PD="true" KERNEL="https://www.googleapis.com/compute/v1beta16/projects/google/global/kernels/gce-no-conn-track-v20130813" # instances INAME="aaaaa-ansible-inst" INAME2="aaaaa-ansible-inst2" INAME3="aaaaa-ansible-inst3" INAME4="aaaaa-ansible-inst4" INAME5="aaaaa-ansible-inst5" INAME6="aaaaa-ansible-inst6" INAME7="aaaaa-ansible-inst7" TYPE="n1-standard-1" IMAGE="https://www.googleapis.com/compute/v1beta16/projects/debian-cloud/global/images/debian-7-wheezy-v20131014" NETWORK="default" SCOPES="https://www.googleapis.com/auth/userinfo.email,https://www.googleapis.com/auth/compute,https://www.googleapis.com/auth/devstorage.full_control" # networks / firewalls NETWK1="ansible-network1" NETWK2="ansible-network2" NETWK3="ansible-network3" CIDR1="10.240.16.0/24" CIDR2="10.240.32.0/24" CIDR3="10.240.64.0/24" GW1="10.240.16.1" GW2="10.240.32.1" FW1="ansible-fwrule1" FW2="ansible-fwrule2" FW3="ansible-fwrule3" FW4="ansible-fwrule4" # load-balancer tests HC1="ansible-hc1" HC2="ansible-hc2" HC3="ansible-hc3" LB1="ansible-lb1" LB2="ansible-lb2" from commands import getstatusoutput as run import sys test_cases = [ {'id': '01', 'desc': 'Detach / Delete disk tests', 'setup': ['gcutil addinstance "%s" --wait_until_running --zone=%s --machine_type=%s --network=%s --service_account_scopes="%s" --image="%s" --persistent_boot_disk=%s' % (INAME, ZONE, TYPE, NETWORK, SCOPES, IMAGE, USE_PD), 'gcutil adddisk "%s" --size_gb=2 --zone=%s --wait_until_complete' % (DNAME, ZONE)], 'tests': [ {'desc': 'DETACH_ONLY but disk not found [success]', 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s detach_only=yes state=absent' % ("missing-disk", INAME, ZONE), 'r': '127.0.0.1 | success >> {"changed": false, "detach_only": true, "detached_from_instance": "%s", "name": "missing-disk", "state": "absent", "zone": "%s"}' % (INAME, ZONE), }, {'desc': 'DETACH_ONLY but instance not found [success]', 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s detach_only=yes state=absent' % (DNAME, "missing-instance", ZONE), 'r': '127.0.0.1 | success >> {"changed": false, "detach_only": true, "detached_from_instance": "missing-instance", "name": "%s", "size_gb": 2, "state": "absent", "zone": "%s"}' % (DNAME, ZONE), }, {'desc': 'DETACH_ONLY but neither disk nor instance exists [success]', 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s detach_only=yes state=absent' % ("missing-disk", "missing-instance", ZONE), 'r': '127.0.0.1 | success >> {"changed": false, "detach_only": true, "detached_from_instance": "missing-instance", "name": "missing-disk", "state": "absent", "zone": "%s"}' % (ZONE), }, {'desc': 'DETACH_ONLY but disk is not currently attached [success]', 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s detach_only=yes state=absent' % (DNAME, INAME, ZONE), 'r': '127.0.0.1 | success >> {"changed": false, "detach_only": true, "detached_from_instance": "%s", "name": "%s", "size_gb": 2, "state": "absent", "zone": "%s"}' % (INAME, DNAME, ZONE), }, {'desc': 'DETACH_ONLY disk is attached and should be detached [success]', 'setup': ['gcutil attachdisk --disk="%s,mode=READ_ONLY" --zone=%s %s' % (DNAME, ZONE, INAME), 'sleep 10'], 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s detach_only=yes state=absent' % (DNAME, INAME, ZONE), 'r': '127.0.0.1 | success >> {"attached_mode": "READ_ONLY", "attached_to_instance": "%s", "changed": true, "detach_only": true, "detached_from_instance": "%s", "name": "%s", "size_gb": 2, "state": "absent", "zone": "%s"}' % (INAME, INAME, DNAME, ZONE), 'teardown': ['gcutil detachdisk --zone=%s --device_name=%s %s' % (ZONE, DNAME, INAME)], }, {'desc': 'DETACH_ONLY but not instance specified [FAIL]', 'm': 'gce_pd', 'a': 'name=%s zone=%s detach_only=yes state=absent' % (DNAME, ZONE), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Must specify an instance name when detaching a disk"}', }, {'desc': 'DELETE but disk not found [success]', 'm': 'gce_pd', 'a': 'name=%s zone=%s state=absent' % ("missing-disk", ZONE), 'r': '127.0.0.1 | success >> {"changed": false, "name": "missing-disk", "state": "absent", "zone": "%s"}' % (ZONE), }, {'desc': 'DELETE but disk is attached [FAIL]', 'setup': ['gcutil attachdisk --disk="%s,mode=READ_ONLY" --zone=%s %s' % (DNAME, ZONE, INAME), 'sleep 10'], 'm': 'gce_pd', 'a': 'name=%s zone=%s state=absent' % (DNAME, ZONE), 'r': "127.0.0.1 | FAILED >> {\"changed\": false, \"failed\": true, \"msg\": \"The disk resource 'projects/%s/zones/%s/disks/%s' is already being used by 'projects/%s/zones/%s/instances/%s'\"}" % (PROJECT, ZONE, DNAME, PROJECT, ZONE, INAME), 'teardown': ['gcutil detachdisk --zone=%s --device_name=%s %s' % (ZONE, DNAME, INAME)], }, {'desc': 'DELETE disk [success]', 'm': 'gce_pd', 'a': 'name=%s zone=%s state=absent' % (DNAME, ZONE), 'r': '127.0.0.1 | success >> {"changed": true, "name": "%s", "size_gb": 2, "state": "absent", "zone": "%s"}' % (DNAME, ZONE), }, ], 'teardown': ['gcutil deleteinstance -f "%s" --zone=%s' % (INAME, ZONE), 'sleep 15', 'gcutil deletedisk -f "%s" --zone=%s' % (INAME, ZONE), 'sleep 10', 'gcutil deletedisk -f "%s" --zone=%s' % (DNAME, ZONE), 'sleep 10'], }, {'id': '02', 'desc': 'Create disk but do not attach (e.g. no instance_name param)', 'setup': [], 'tests': [ {'desc': 'CREATE_NO_ATTACH "string" for size_gb [FAIL]', 'm': 'gce_pd', 'a': 'name=%s size_gb="foo" zone=%s' % (DNAME, ZONE), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Must supply a size_gb larger than 1 GB"}', }, {'desc': 'CREATE_NO_ATTACH negative size_gb [FAIL]', 'm': 'gce_pd', 'a': 'name=%s size_gb=-2 zone=%s' % (DNAME, ZONE), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Must supply a size_gb larger than 1 GB"}', }, {'desc': 'CREATE_NO_ATTACH size_gb exceeds quota [FAIL]', 'm': 'gce_pd', 'a': 'name=%s size_gb=9999 zone=%s' % ("big-disk", ZONE), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Requested disk size exceeds quota"}', }, {'desc': 'CREATE_NO_ATTACH create the disk [success]', 'm': 'gce_pd', 'a': 'name=%s zone=%s' % (DNAME, ZONE), 'r': '127.0.0.1 | success >> {"changed": true, "name": "%s", "size_gb": 10, "state": "present", "zone": "%s"}' % (DNAME, ZONE), }, {'desc': 'CREATE_NO_ATTACH but disk already exists [success]', 'm': 'gce_pd', 'a': 'name=%s zone=%s' % (DNAME, ZONE), 'r': '127.0.0.1 | success >> {"changed": false, "name": "%s", "size_gb": 10, "state": "present", "zone": "%s"}' % (DNAME, ZONE), }, ], 'teardown': ['gcutil deletedisk -f "%s" --zone=%s' % (DNAME, ZONE), 'sleep 10'], }, {'id': '03', 'desc': 'Create and attach disk', 'setup': ['gcutil addinstance "%s" --zone=%s --machine_type=%s --network=%s --service_account_scopes="%s" --image="%s" --persistent_boot_disk=%s' % (INAME2, ZONE, TYPE, NETWORK, SCOPES, IMAGE, USE_PD), 'gcutil addinstance "%s" --zone=%s --machine_type=%s --network=%s --service_account_scopes="%s" --image="%s" --persistent_boot_disk=%s' % (INAME, ZONE, "g1-small", NETWORK, SCOPES, IMAGE, USE_PD), 'gcutil adddisk "%s" --size_gb=2 --zone=%s' % (DNAME, ZONE), 'gcutil adddisk "%s" --size_gb=2 --zone=%s --wait_until_complete' % (DNAME2, ZONE),], 'tests': [ {'desc': 'CREATE_AND_ATTACH "string" for size_gb [FAIL]', 'm': 'gce_pd', 'a': 'name=%s size_gb="foo" instance_name=%s zone=%s' % (DNAME, INAME, ZONE), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Must supply a size_gb larger than 1 GB"}', }, {'desc': 'CREATE_AND_ATTACH negative size_gb [FAIL]', 'm': 'gce_pd', 'a': 'name=%s size_gb=-2 instance_name=%s zone=%s' % (DNAME, INAME, ZONE), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Must supply a size_gb larger than 1 GB"}', }, {'desc': 'CREATE_AND_ATTACH size_gb exceeds quota [FAIL]', 'm': 'gce_pd', 'a': 'name=%s size_gb=9999 instance_name=%s zone=%s' % ("big-disk", INAME, ZONE), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Requested disk size exceeds quota"}', }, {'desc': 'CREATE_AND_ATTACH missing instance [FAIL]', 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s' % (DNAME, "missing-instance", ZONE), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Instance %s does not exist in zone %s"}' % ("missing-instance", ZONE), }, {'desc': 'CREATE_AND_ATTACH disk exists but not attached [success]', 'peek_before': ["gcutil --format=csv listinstances --zone=%s --filter=\"name eq 'aaaa.*'\"" % (ZONE)], 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s' % (DNAME, INAME, ZONE), 'r': '127.0.0.1 | success >> {"attached_mode": "READ_ONLY", "attached_to_instance": "%s", "changed": true, "name": "%s", "size_gb": 2, "state": "present", "zone": "%s"}' % (INAME, DNAME, ZONE), 'peek_after': ["gcutil --format=csv listinstances --zone=%s --filter=\"name eq 'aaaa.*'\"" % (ZONE)], }, {'desc': 'CREATE_AND_ATTACH disk exists already attached [success]', 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s' % (DNAME, INAME, ZONE), 'r': '127.0.0.1 | success >> {"attached_mode": "READ_ONLY", "attached_to_instance": "%s", "changed": false, "name": "%s", "size_gb": 2, "state": "present", "zone": "%s"}' % (INAME, DNAME, ZONE), }, {'desc': 'CREATE_AND_ATTACH attached RO, attempt RO to 2nd inst [success]', 'peek_before': ["gcutil --format=csv listinstances --zone=%s --filter=\"name eq 'aaaa.*'\"" % (ZONE)], 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s' % (DNAME, INAME2, ZONE), 'r': '127.0.0.1 | success >> {"attached_mode": "READ_ONLY", "attached_to_instance": "%s", "changed": true, "name": "%s", "size_gb": 2, "state": "present", "zone": "%s"}' % (INAME2, DNAME, ZONE), 'peek_after': ["gcutil --format=csv listinstances --zone=%s --filter=\"name eq 'aaaa.*'\"" % (ZONE)], }, {'desc': 'CREATE_AND_ATTACH attached RO, attach RW to self [FAILED no-op]', 'peek_before': ["gcutil --format=csv listinstances --zone=%s --filter=\"name eq 'aaaa.*'\"" % (ZONE)], 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s mode=READ_WRITE' % (DNAME, INAME, ZONE), 'r': '127.0.0.1 | success >> {"attached_mode": "READ_ONLY", "attached_to_instance": "%s", "changed": false, "name": "%s", "size_gb": 2, "state": "present", "zone": "%s"}' % (INAME, DNAME, ZONE), }, {'desc': 'CREATE_AND_ATTACH attached RW, attach RW to other [FAIL]', 'setup': ['gcutil attachdisk --disk=%s,mode=READ_WRITE --zone=%s %s' % (DNAME2, ZONE, INAME), 'sleep 10'], 'peek_before': ["gcutil --format=csv listinstances --zone=%s --filter=\"name eq 'aaaa.*'\"" % (ZONE)], 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s mode=READ_WRITE' % (DNAME2, INAME2, ZONE), 'r': "127.0.0.1 | FAILED >> {\"changed\": false, \"failed\": true, \"msg\": \"Unexpected response: HTTP return_code[200], API error code[RESOURCE_IN_USE] and message: The disk resource 'projects/%s/zones/%s/disks/%s' is already being used in read-write mode\"}" % (PROJECT, ZONE, DNAME2), 'peek_after': ["gcutil --format=csv listinstances --zone=%s --filter=\"name eq 'aaaa.*'\"" % (ZONE)], }, {'desc': 'CREATE_AND_ATTACH attach too many disks to inst [FAIL]', 'setup': ['gcutil adddisk aa-disk-dummy --size_gb=2 --zone=%s' % (ZONE), 'gcutil adddisk aa-disk-dummy2 --size_gb=2 --zone=%s --wait_until_complete' % (ZONE), 'gcutil attachdisk --disk=aa-disk-dummy --zone=%s %s' % (ZONE, INAME), 'sleep 5'], 'peek_before': ["gcutil --format=csv listinstances --zone=%s --filter=\"name eq 'aaaa.*'\"" % (ZONE)], 'm': 'gce_pd', 'a': 'name=%s instance_name=%s zone=%s' % ("aa-disk-dummy2", INAME, ZONE), 'r': "127.0.0.1 | FAILED >> {\"changed\": false, \"failed\": true, \"msg\": \"Unexpected response: HTTP return_code[200], API error code[LIMIT_EXCEEDED] and message: Exceeded limit 'maximum_persistent_disks' on resource 'projects/%s/zones/%s/instances/%s'. Limit: 4\"}" % (PROJECT, ZONE, INAME), 'teardown': ['gcutil detachdisk --device_name=aa-disk-dummy --zone=%s %s' % (ZONE, INAME), 'sleep 3', 'gcutil deletedisk -f aa-disk-dummy --zone=%s' % (ZONE), 'sleep 10', 'gcutil deletedisk -f aa-disk-dummy2 --zone=%s' % (ZONE), 'sleep 10'], }, ], 'teardown': ['gcutil deleteinstance -f "%s" --zone=%s' % (INAME2, ZONE), 'sleep 15', 'gcutil deleteinstance -f "%s" --zone=%s' % (INAME, ZONE), 'sleep 15', 'gcutil deletedisk -f "%s" --zone=%s' % (INAME, ZONE), 'sleep 10', 'gcutil deletedisk -f "%s" --zone=%s' % (INAME2, ZONE), 'sleep 10', 'gcutil deletedisk -f "%s" --zone=%s' % (DNAME, ZONE), 'sleep 10', 'gcutil deletedisk -f "%s" --zone=%s' % (DNAME2, ZONE), 'sleep 10'], }, {'id': '04', 'desc': 'Delete / destroy instances', 'setup': ['gcutil addinstance "%s" --zone=%s --machine_type=%s --image="%s" --persistent_boot_disk=false' % (INAME, ZONE, TYPE, IMAGE), 'gcutil addinstance "%s" --zone=%s --machine_type=%s --image="%s" --persistent_boot_disk=false' % (INAME2, ZONE, TYPE, IMAGE), 'gcutil addinstance "%s" --zone=%s --machine_type=%s --image="%s" --persistent_boot_disk=false' % (INAME3, ZONE, TYPE, IMAGE), 'gcutil addinstance "%s" --zone=%s --machine_type=%s --image="%s" --persistent_boot_disk=false' % (INAME4, ZONE, TYPE, IMAGE), 'gcutil addinstance "%s" --wait_until_running --zone=%s --machine_type=%s --image="%s" --persistent_boot_disk=false' % (INAME5, ZONE, TYPE, IMAGE)], 'tests': [ {'desc': 'DELETE instance, bad zone param [FAIL]', 'm': 'gce', 'a': 'name=missing-inst zone=bogus state=absent', 'r': '127.0.0.1 | FAILED >> {"failed": true, "msg": "value of zone must be one of: us-central1-a,us-central1-b,us-central2-a,europe-west1-a,europe-west1-b, got: bogus"}', }, {'desc': 'DELETE non-existent instance, no-op [success]', 'm': 'gce', 'a': 'name=missing-inst zone=%s state=absent' % (ZONE), 'r': '127.0.0.1 | success >> {"changed": false, "name": "missing-inst", "state": "absent", "zone": "%s"}' % (ZONE), }, {'desc': 'DELETE an existing named instance [success]', 'm': 'gce', 'a': 'name=%s zone=%s state=absent' % (INAME, ZONE), 'r': '127.0.0.1 | success >> {"changed": true, "name": "%s", "state": "absent", "zone": "%s"}' % (INAME, ZONE), }, {'desc': 'DELETE list of instances with a non-existent one [success]', 'm': 'gce', 'a': 'instance_names=%s,missing,%s zone=%s state=absent' % (INAME2,INAME3, ZONE), 'r': '127.0.0.1 | success >> {"changed": true, "instance_names": ["%s", "%s"], "state": "absent", "zone": "%s"}' % (INAME2, INAME3, ZONE), }, {'desc': 'DELETE list of instances all pre-exist [success]', 'm': 'gce', 'a': 'instance_names=%s,%s zone=%s state=absent' % (INAME4,INAME5, ZONE), 'r': '127.0.0.1 | success >> {"changed": true, "instance_names": ["%s", "%s"], "state": "absent", "zone": "%s"}' % (INAME4, INAME5, ZONE), }, ], 'teardown': ['gcutil deleteinstance -f "%s" --zone=%s' % (INAME, ZONE), 'gcutil deleteinstance -f "%s" --zone=%s' % (INAME2, ZONE), 'gcutil deleteinstance -f "%s" --zone=%s' % (INAME3, ZONE), 'gcutil deleteinstance -f "%s" --zone=%s' % (INAME4, ZONE), 'gcutil deleteinstance -f "%s" --zone=%s' % (INAME5, ZONE), 'sleep 10'], }, {'id': '05', 'desc': 'Create instances', 'setup': ['gcutil adddisk --source_image=%s --zone=%s %s --wait_until_complete' % (IMAGE, ZONE, DNAME7), 'gcutil addinstance boo --wait_until_running --zone=%s --machine_type=%s --network=%s --disk=%s,mode=READ_WRITE,boot --kernel=%s' % (ZONE,TYPE,NETWORK,DNAME7,KERNEL), ], 'tests': [ {'desc': 'CREATE_INSTANCE invalid image arg [FAIL]', 'm': 'gce', 'a': 'name=foo image=foo', 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Missing required create instance variable"}', }, {'desc': 'CREATE_INSTANCE metadata a list [FAIL]', 'strip_numbers': True, 'm': 'gce', 'a': 'name=%s zone=%s metadata=\'[\\"foo\\":\\"bar\\",\\"baz\\":1]\'' % (INAME,ZONE), 'r': '127.0.0.1 | FAILED >> {"failed": true, "msg": "bad metadata syntax"}', }, {'desc': 'CREATE_INSTANCE metadata not a dict [FAIL]', 'strip_numbers': True, 'm': 'gce', 'a': 'name=%s zone=%s metadata=\\"foo\\":\\"bar\\",\\"baz\\":1' % (INAME,ZONE), 'r': '127.0.0.1 | FAILED >> {"failed": true, "msg": "bad metadata syntax"}', }, {'desc': 'CREATE_INSTANCE with metadata form1 [FAIL]', 'strip_numbers': True, 'm': 'gce', 'a': 'name=%s zone=%s metadata=\'{"foo":"bar","baz":1}\'' % (INAME,ZONE), 'r': '127.0.0.1 | FAILED >> {"failed": true, "msg": "bad metadata: malformed string"}', }, {'desc': 'CREATE_INSTANCE with metadata form2 [FAIL]', 'strip_numbers': True, 'm': 'gce', 'a': 'name=%s zone=%s metadata={\'foo\':\'bar\',\'baz\':1}' % (INAME,ZONE), 'r': '127.0.0.1 | FAILED >> {"failed": true, "msg": "bad metadata: malformed string"}', }, {'desc': 'CREATE_INSTANCE with metadata form3 [FAIL]', 'strip_numbers': True, 'm': 'gce', 'a': 'name=%s zone=%s metadata="foo:bar" '% (INAME,ZONE), 'r': '127.0.0.1 | FAILED >> {"failed": true, "msg": "bad metadata syntax"}', }, {'desc': 'CREATE_INSTANCE with metadata form4 [FAIL]', 'strip_numbers': True, 'm': 'gce', 'a': 'name=%s zone=%s metadata="{\'foo\':\'bar\'}"'% (INAME,ZONE), 'r': '127.0.0.1 | FAILED >> {"failed": true, "msg": "bad metadata: malformed string"}', }, {'desc': 'CREATE_INSTANCE invalid image arg [FAIL]', 'm': 'gce', 'a': 'instance_names=foo,bar image=foo', 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Missing required create instance variable"}', }, {'desc': 'CREATE_INSTANCE single inst, using defaults [success]', 'strip_numbers': True, 'm': 'gce', 'a': 'name=%s' % (INAME), 'r': '127.0.0.1 | success >> {"changed": true, "instance_data": [{"image": "debian-7-wheezy-v20130816", "machine_type": "n1-standard-1", "metadata": {}, "name": "%s", "network": "default", "private_ip": "10.240.175.15", "public_ip": "173.255.120.190", "status": "RUNNING", "tags": [], "zone": "%s"}], "name": "%s", "state": "present", "zone": "%s"}' % (INAME, ZONE, INAME, ZONE), }, {'desc': 'CREATE_INSTANCE the same instance again, no-op [success]', 'strip_numbers': True, 'm': 'gce', 'a': 'name=%s' % (INAME), 'r': '127.0.0.1 | success >> {"changed": false, "instance_data": [{"image": "debian-7-wheezy-v20130816", "machine_type": "n1-standard-1", "metadata": {}, "name": "%s", "network": "default", "private_ip": "10.240.175.15", "public_ip": "173.255.120.190", "status": "RUNNING", "tags": [], "zone": "%s"}], "name": "%s", "state": "present", "zone": "%s"}' % (INAME, ZONE, INAME, ZONE), }, {'desc': 'CREATE_INSTANCE instance with alt type [success]', 'strip_numbers': True, 'm': 'gce', 'a': 'name=%s machine_type=n1-standard-2' % (INAME2), 'r': '127.0.0.1 | success >> {"changed": true, "instance_data": [{"image": "debian-7-wheezy-v20130816", "machine_type": "n1-standard-2", "metadata": {}, "name": "%s", "network": "default", "private_ip": "10.240.192.227", "public_ip": "173.255.121.233", "status": "RUNNING", "tags": [], "zone": "%s"}], "name": "%s", "state": "present", "zone": "%s"}' % (INAME2, ZONE, INAME2, ZONE), }, {'desc': 'CREATE_INSTANCE instance with root pd [success]', 'strip_numbers': True, 'm': 'gce', 'a': 'name=%s persistent_boot_disk=yes' % (INAME3), 'r': '127.0.0.1 | success >> {"changed": true, "instance_data": [{"image": null, "machine_type": "n1-standard-1", "metadata": {}, "name": "%s", "network": "default", "private_ip": "10.240.178.140", "public_ip": "173.255.121.176", "status": "RUNNING", "tags": [], "zone": "%s"}], "name": "%s", "state": "present", "zone": "%s"}' % (INAME3, ZONE, INAME3, ZONE), }, {'desc': 'CREATE_INSTANCE instance with root pd, that already exists [success]', 'setup': ['gcutil adddisk --source_image=%s --zone=%s %s --wait_until_complete' % (IMAGE, ZONE, DNAME6),], 'strip_numbers': True, 'm': 'gce', 'a': 'name=%s zone=%s persistent_boot_disk=yes' % (INAME6, ZONE), 'r': '127.0.0.1 | success >> {"changed": true, "instance_data": [{"image": null, "machine_type": "n1-standard-1", "metadata": {}, "name": "%s", "network": "default", "private_ip": "10.240.178.140", "public_ip": "173.255.121.176", "status": "RUNNING", "tags": [], "zone": "%s"}], "name": "%s", "state": "present", "zone": "%s"}' % (INAME6, ZONE, INAME6, ZONE), }, {'desc': 'CREATE_INSTANCE instance with root pd attached to other inst [FAIL]', 'm': 'gce', 'a': 'name=%s zone=%s persistent_boot_disk=yes' % (INAME7, ZONE), 'r': '127.0.0.1 | FAILED >> {"failed": true, "msg": "Unexpected error attempting to create instance %s, error: The disk resource \'projects/%s/zones/%s/disks/%s\' is already being used in read-write mode"}' % (INAME7,PROJECT,ZONE,DNAME7), }, {'desc': 'CREATE_INSTANCE use *all* the options! [success]', 'strip_numbers': True, 'm': 'gce', 'a': 'instance_names=%s,%s metadata=\'{\\"foo\\":\\"bar\\", \\"baz\\":1}\' tags=t1,t2,t3 zone=%s image=centos-6-v20130731 persistent_boot_disk=yes' % (INAME4,INAME5,ZONE), 'r': '127.0.0.1 | success >> {"changed": true, "instance_data": [{"image": null, "machine_type": "n1-standard-1", "metadata": {"baz": "1", "foo": "bar"}, "name": "%s", "network": "default", "private_ip": "10.240.130.4", "public_ip": "173.255.121.97", "status": "RUNNING", "tags": ["t1", "t2", "t3"], "zone": "%s"}, {"image": null, "machine_type": "n1-standard-1", "metadata": {"baz": "1", "foo": "bar"}, "name": "%s", "network": "default", "private_ip": "10.240.207.226", "public_ip": "173.255.121.85", "status": "RUNNING", "tags": ["t1", "t2", "t3"], "zone": "%s"}], "instance_names": ["%s", "%s"], "state": "present", "zone": "%s"}' % (INAME4, ZONE, INAME5, ZONE, INAME4, INAME5, ZONE), }, ], 'teardown': ['gcutil deleteinstance -f "%s" --zone=%s' % (INAME, ZONE), 'gcutil deleteinstance -f "%s" --zone=%s' % (INAME2, ZONE), 'gcutil deleteinstance -f "%s" --zone=%s' % (INAME3, ZONE), 'gcutil deleteinstance -f "%s" --zone=%s' % (INAME4, ZONE), 'gcutil deleteinstance -f "%s" --zone=%s' % (INAME5, ZONE), 'gcutil deleteinstance -f "%s" --zone=%s' % (INAME6, ZONE), 'gcutil deleteinstance -f "%s" --zone=%s' % (INAME7, ZONE), 'gcutil deleteinstance -f boo --zone=%s' % (ZONE), 'sleep 10', 'gcutil deletedisk -f "%s" --zone=%s' % (INAME3, ZONE), 'gcutil deletedisk -f "%s" --zone=%s' % (INAME4, ZONE), 'gcutil deletedisk -f "%s" --zone=%s' % (INAME5, ZONE), 'gcutil deletedisk -f "%s" --zone=%s' % (INAME6, ZONE), 'gcutil deletedisk -f "%s" --zone=%s' % (INAME7, ZONE), 'sleep 10'], }, {'id': '06', 'desc': 'Delete / destroy networks and firewall rules', 'setup': ['gcutil addnetwork --range="%s" --gateway="%s" %s' % (CIDR1, GW1, NETWK1), 'gcutil addnetwork --range="%s" --gateway="%s" %s' % (CIDR2, GW2, NETWK2), 'sleep 5', 'gcutil addfirewall --allowed="tcp:80" --network=%s %s' % (NETWK1, FW1), 'gcutil addfirewall --allowed="tcp:80" --network=%s %s' % (NETWK2, FW2), 'sleep 5'], 'tests': [ {'desc': 'DELETE bogus named firewall [success]', 'm': 'gce_net', 'a': 'fwname=missing-fwrule state=absent', 'r': '127.0.0.1 | success >> {"changed": false, "fwname": "missing-fwrule", "state": "absent"}', }, {'desc': 'DELETE bogus named network [success]', 'm': 'gce_net', 'a': 'name=missing-network state=absent', 'r': '127.0.0.1 | success >> {"changed": false, "name": "missing-network", "state": "absent"}', }, {'desc': 'DELETE named firewall rule [success]', 'm': 'gce_net', 'a': 'fwname=%s state=absent' % (FW1), 'r': '127.0.0.1 | success >> {"changed": true, "fwname": "%s", "state": "absent"}' % (FW1), 'teardown': ['sleep 5'], # pause to give GCE time to delete fwrule }, {'desc': 'DELETE unused named network [success]', 'm': 'gce_net', 'a': 'name=%s state=absent' % (NETWK1), 'r': '127.0.0.1 | success >> {"changed": true, "name": "%s", "state": "absent"}' % (NETWK1), }, {'desc': 'DELETE named network *and* fwrule [success]', 'm': 'gce_net', 'a': 'name=%s fwname=%s state=absent' % (NETWK2, FW2), 'r': '127.0.0.1 | success >> {"changed": true, "fwname": "%s", "name": "%s", "state": "absent"}' % (FW2, NETWK2), }, ], 'teardown': ['gcutil deletenetwork -f %s' % (NETWK1), 'gcutil deletenetwork -f %s' % (NETWK2), 'sleep 5', 'gcutil deletefirewall -f %s' % (FW1), 'gcutil deletefirewall -f %s' % (FW2)], }, {'id': '07', 'desc': 'Create networks and firewall rules', 'setup': ['gcutil addnetwork --range="%s" --gateway="%s" %s' % (CIDR1, GW1, NETWK1), 'sleep 5', 'gcutil addfirewall --allowed="tcp:80" --network=%s %s' % (NETWK1, FW1), 'sleep 5'], 'tests': [ {'desc': 'CREATE network without specifying ipv4_range [FAIL]', 'm': 'gce_net', 'a': 'name=fail', 'r': "127.0.0.1 | FAILED >> {\"changed\": false, \"failed\": true, \"msg\": \"Missing required 'ipv4_range' parameter\"}", }, {'desc': 'CREATE network with specifying bad ipv4_range [FAIL]', 'm': 'gce_net', 'a': 'name=fail ipv4_range=bad_value', 'r': "127.0.0.1 | FAILED >> {\"changed\": false, \"failed\": true, \"msg\": \"Unexpected response: HTTP return_code[400], API error code[None] and message: Invalid value for field 'resource.IPv4Range': 'bad_value'. Must be a CIDR address range that is contained in the RFC1918 private address blocks: [10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16]\"}", }, {'desc': 'CREATE existing network, not changed [success]', 'm': 'gce_net', 'a': 'name=%s ipv4_range=%s' % (NETWK1, CIDR1), 'r': '127.0.0.1 | success >> {"changed": false, "ipv4_range": "%s", "name": "%s", "state": "present"}' % (CIDR1, NETWK1), }, {'desc': 'CREATE new network, changed [success]', 'm': 'gce_net', 'a': 'name=%s ipv4_range=%s' % (NETWK2, CIDR2), 'r': '127.0.0.1 | success >> {"changed": true, "ipv4_range": "10.240.32.0/24", "name": "%s", "state": "present"}' % (NETWK2), }, {'desc': 'CREATE new fw rule missing params [FAIL]', 'm': 'gce_net', 'a': 'name=%s fwname=%s' % (NETWK1, FW1), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Missing required firewall rule parameter(s)"}', }, {'desc': 'CREATE new fw rule bad params [FAIL]', 'm': 'gce_net', 'a': 'name=%s fwname=broken allowed=blah src_tags="one,two"' % (NETWK1), 'r': "127.0.0.1 | FAILED >> {\"changed\": false, \"failed\": true, \"msg\": \"Unexpected response: HTTP return_code[400], API error code[None] and message: Invalid value for field 'resource.allowed[0].IPProtocol': 'blah'. Must be one of [\\\"tcp\\\", \\\"udp\\\", \\\"icmp\\\"] or an IP protocol number between 0 and 255\"}", }, {'desc': 'CREATE existing fw rule [success]', 'm': 'gce_net', 'a': 'name=%s fwname=%s allowed="tcp:80" src_tags="one,two"' % (NETWK1, FW1), 'r': '127.0.0.1 | success >> {"allowed": "tcp:80", "changed": false, "fwname": "%s", "ipv4_range": "%s", "name": "%s", "src_range": null, "src_tags": ["one", "two"], "state": "present"}' % (FW1, CIDR1, NETWK1), }, {'desc': 'CREATE new fw rule [success]', 'm': 'gce_net', 'a': 'name=%s fwname=%s allowed="tcp:80" src_tags="one,two"' % (NETWK1, FW3), 'r': '127.0.0.1 | success >> {"allowed": "tcp:80", "changed": true, "fwname": "%s", "ipv4_range": "%s", "name": "%s", "src_range": null, "src_tags": ["one", "two"], "state": "present"}' % (FW3, CIDR1, NETWK1), }, {'desc': 'CREATE new network *and* fw rule [success]', 'm': 'gce_net', 'a': 'name=%s ipv4_range=%s fwname=%s allowed="tcp:80" src_tags="one,two"' % (NETWK3, CIDR3, FW4), 'r': '127.0.0.1 | success >> {"allowed": "tcp:80", "changed": true, "fwname": "%s", "ipv4_range": "%s", "name": "%s", "src_range": null, "src_tags": ["one", "two"], "state": "present"}' % (FW4, CIDR3, NETWK3), }, ], 'teardown': ['gcutil deletefirewall -f %s' % (FW1), 'gcutil deletefirewall -f %s' % (FW2), 'gcutil deletefirewall -f %s' % (FW3), 'gcutil deletefirewall -f %s' % (FW4), 'sleep 5', 'gcutil deletenetwork -f %s' % (NETWK1), 'gcutil deletenetwork -f %s' % (NETWK2), 'gcutil deletenetwork -f %s' % (NETWK3), 'sleep 5'], }, {'id': '08', 'desc': 'Create load-balancer resources', 'setup': ['gcutil addinstance "%s" --zone=%s --machine_type=%s --network=%s --service_account_scopes="%s" --image="%s" --nopersistent_boot_disk' % (INAME, ZONE, TYPE, NETWORK, SCOPES, IMAGE), 'gcutil addinstance "%s" --wait_until_running --zone=%s --machine_type=%s --network=%s --service_account_scopes="%s" --image="%s" --nopersistent_boot_disk' % (INAME2, ZONE, TYPE, NETWORK, SCOPES, IMAGE), ], 'tests': [ {'desc': 'Do nothing [FAIL]', 'm': 'gce_lb', 'a': 'httphealthcheck_port=7', 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Nothing to do, please specify a \\\"name\\\" or \\\"httphealthcheck_name\\\" parameter"}', }, {'desc': 'CREATE_HC create basic http healthcheck [success]', 'm': 'gce_lb', 'a': 'httphealthcheck_name=%s' % (HC1), 'r': '127.0.0.1 | success >> {"changed": true, "httphealthcheck_healthy_count": 2, "httphealthcheck_host": null, "httphealthcheck_interval": 5, "httphealthcheck_name": "%s", "httphealthcheck_path": "/", "httphealthcheck_port": 80, "httphealthcheck_timeout": 5, "httphealthcheck_unhealthy_count": 2, "name": null, "state": "present"}' % (HC1), }, {'desc': 'CREATE_HC (repeat, no-op) create basic http healthcheck [success]', 'm': 'gce_lb', 'a': 'httphealthcheck_name=%s' % (HC1), 'r': '127.0.0.1 | success >> {"changed": false, "httphealthcheck_healthy_count": 2, "httphealthcheck_host": null, "httphealthcheck_interval": 5, "httphealthcheck_name": "%s", "httphealthcheck_path": "/", "httphealthcheck_port": 80, "httphealthcheck_timeout": 5, "httphealthcheck_unhealthy_count": 2, "name": null, "state": "present"}' % (HC1), }, {'desc': 'CREATE_HC create custom http healthcheck [success]', 'm': 'gce_lb', 'a': 'httphealthcheck_name=%s httphealthcheck_port=1234 httphealthcheck_path="/whatup" httphealthcheck_host="foo" httphealthcheck_interval=300' % (HC2), 'r': '127.0.0.1 | success >> {"changed": true, "httphealthcheck_healthy_count": 2, "httphealthcheck_host": "foo", "httphealthcheck_interval": 300, "httphealthcheck_name": "%s", "httphealthcheck_path": "/whatup", "httphealthcheck_port": 1234, "httphealthcheck_timeout": 5, "httphealthcheck_unhealthy_count": 2, "name": null, "state": "present"}' % (HC2), }, {'desc': 'CREATE_HC create (broken) custom http healthcheck [FAIL]', 'm': 'gce_lb', 'a': 'httphealthcheck_name=%s httphealthcheck_port="string" httphealthcheck_path=7' % (HC3), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Unexpected response: HTTP return_code[400], API error code[None] and message: Invalid value for: Expected a signed integer, got \'string\' (class java.lang.String)"}', }, {'desc': 'CREATE_LB create lb, missing region [FAIL]', 'm': 'gce_lb', 'a': 'name=%s' % (LB1), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Missing required region name"}', }, {'desc': 'CREATE_LB create lb, bogus region [FAIL]', 'm': 'gce_lb', 'a': 'name=%s region=bogus' % (LB1), 'r': '127.0.0.1 | FAILED >> {"changed": false, "failed": true, "msg": "Unexpected response: HTTP return_code[404], API error code[None] and message: The resource \'projects/%s/regions/bogus\' was not found"}' % (PROJECT), }, {'desc': 'CREATE_LB create lb, minimal params [success]', 'strip_numbers': True, 'm': 'gce_lb', 'a': 'name=%s region=%s' % (LB1, REGION), 'r': '127.0.0.1 | success >> {"changed": true, "external_ip": "173.255.123.245", "httphealthchecks": [], "members": [], "name": "%s", "port_range": "1-65535", "protocol": "tcp", "region": "%s", "state": "present"}' % (LB1, REGION), }, {'desc': 'CREATE_LB create lb full params [success]', 'strip_numbers': True, 'm': 'gce_lb', 'a': 'httphealthcheck_name=%s httphealthcheck_port=5055 httphealthcheck_path="/howami" name=%s port_range=8000-8888 region=%s members=%s/%s,%s/%s' % (HC3,LB2,REGION,ZONE,INAME,ZONE,INAME2), 'r': '127.0.0.1 | success >> {"changed": true, "external_ip": "173.255.126.81", "httphealthcheck_healthy_count": 2, "httphealthcheck_host": null, "httphealthcheck_interval": 5, "httphealthcheck_name": "%s", "httphealthcheck_path": "/howami", "httphealthcheck_port": 5055, "httphealthcheck_timeout": 5, "httphealthcheck_unhealthy_count": 2, "httphealthchecks": ["%s"], "members": ["%s/%s", "%s/%s"], "name": "%s", "port_range": "8000-8888", "protocol": "tcp", "region": "%s", "state": "present"}' % (HC3,HC3,ZONE,INAME,ZONE,INAME2,LB2,REGION), }, ], 'teardown': [ 'gcutil deleteinstance --zone=%s -f %s %s' % (ZONE, INAME, INAME2), 'gcutil deleteforwardingrule --region=%s -f %s %s' % (REGION, LB1, LB2), 'sleep 10', 'gcutil deletetargetpool --region=%s -f %s-tp %s-tp' % (REGION, LB1, LB2), 'sleep 10', 'gcutil deletehttphealthcheck -f %s %s %s' % (HC1, HC2, HC3), ], }, {'id': '09', 'desc': 'Destroy load-balancer resources', 'setup': ['gcutil addhttphealthcheck %s' % (HC1), 'sleep 5', 'gcutil addhttphealthcheck %s' % (HC2), 'sleep 5', 'gcutil addtargetpool --health_checks=%s --region=%s %s-tp' % (HC1, REGION, LB1), 'sleep 5', 'gcutil addforwardingrule --target=%s-tp --region=%s %s' % (LB1, REGION, LB1), 'sleep 5', 'gcutil addtargetpool --region=%s %s-tp' % (REGION, LB2), 'sleep 5', 'gcutil addforwardingrule --target=%s-tp --region=%s %s' % (LB2, REGION, LB2), 'sleep 5', ], 'tests': [ {'desc': 'DELETE_LB: delete a non-existent LB [success]', 'm': 'gce_lb', 'a': 'name=missing state=absent', 'r': '127.0.0.1 | success >> {"changed": false, "name": "missing", "state": "absent"}', }, {'desc': 'DELETE_LB: delete a non-existent LB+HC [success]', 'm': 'gce_lb', 'a': 'name=missing httphealthcheck_name=alsomissing state=absent', 'r': '127.0.0.1 | success >> {"changed": false, "httphealthcheck_name": "alsomissing", "name": "missing", "state": "absent"}', }, {'desc': 'DELETE_LB: destroy standalone healthcheck [success]', 'm': 'gce_lb', 'a': 'httphealthcheck_name=%s state=absent' % (HC2), 'r': '127.0.0.1 | success >> {"changed": true, "httphealthcheck_name": "%s", "name": null, "state": "absent"}' % (HC2), }, {'desc': 'DELETE_LB: destroy standalone balancer [success]', 'm': 'gce_lb', 'a': 'name=%s state=absent' % (LB2), 'r': '127.0.0.1 | success >> {"changed": true, "name": "%s", "state": "absent"}' % (LB2), }, {'desc': 'DELETE_LB: destroy LB+HC [success]', 'm': 'gce_lb', 'a': 'name=%s httphealthcheck_name=%s state=absent' % (LB1, HC1), 'r': '127.0.0.1 | success >> {"changed": true, "httphealthcheck_name": "%s", "name": "%s", "state": "absent"}' % (HC1,LB1), }, ], 'teardown': [ 'gcutil deleteforwardingrule --region=%s -f %s %s' % (REGION, LB1, LB2), 'sleep 10', 'gcutil deletetargetpool --region=%s -f %s-tp %s-tp' % (REGION, LB1, LB2), 'sleep 10', 'gcutil deletehttphealthcheck -f %s %s' % (HC1, HC2), ], }, ] def main(tests_to_run=[]): for test in test_cases: if tests_to_run and test['id'] not in tests_to_run: continue print "=> starting/setup '%s:%s'"% (test['id'], test['desc']) if DEBUG: print "=debug>", test['setup'] for c in test['setup']: (s,o) = run(c) test_i = 1 for t in test['tests']: if DEBUG: print "=>debug>", test_i, t['desc'] # run any test-specific setup commands if t.has_key('setup'): for setup in t['setup']: (status, output) = run(setup) # run any 'peek_before' commands if t.has_key('peek_before') and PEEKING_ENABLED: for setup in t['peek_before']: (status, output) = run(setup) # run the ansible test if 'a' exists, otherwise # an empty 'a' directive allows test to run # setup/teardown for a subsequent test. if t['a']: if DEBUG: print "=>debug>", t['m'], t['a'] acmd = "ansible all -o -m %s -a \"%s\"" % (t['m'],t['a']) #acmd = "ANSIBLE_KEEP_REMOTE_FILES=1 ansible all -vvv -m %s -a \"%s\"" % (t['m'],t['a']) (s,o) = run(acmd) # check expected output if DEBUG: print "=debug>", o.strip(), "!=", t['r'] print "=> %s.%02d '%s':" % (test['id'], test_i, t['desc']), if t.has_key('strip_numbers'): # strip out all numbers so we don't trip over different # IP addresses is_good = (o.strip().translate(None, "0123456789") == t['r'].translate(None, "0123456789")) else: is_good = (o.strip() == t['r']) if is_good: print "PASS" else: print "FAIL" if VERBOSE: print "=>", acmd print "=> Expected:", t['r'] print "=> Got:", o.strip() # run any 'peek_after' commands if t.has_key('peek_after') and PEEKING_ENABLED: for setup in t['peek_after']: (status, output) = run(setup) # run any test-specific teardown commands if t.has_key('teardown'): for td in t['teardown']: (status, output) = run(td) test_i += 1 print "=> completing/teardown '%s:%s'" % (test['id'], test['desc']) if DEBUG: print "=debug>", test['teardown'] for c in test['teardown']: (s,o) = run(c) if __name__ == '__main__': tests_to_run = [] if len(sys.argv) == 2: if sys.argv[1] in ["--help", "--list"]: print "usage: %s [id1,id2,...,idN]" % sys.argv[0] print " * An empty argument list will execute all tests" print " * Do not need to specify tests in numerical order" print " * List test categories with --list or --help" print "" for test in test_cases: print "\t%s:%s" % (test['id'], test['desc']) sys.exit(0) else: tests_to_run = sys.argv[1].split(',') main(tests_to_run) ansible-1.7.2/lib/000077500000000000000000000000001241061774000137065ustar00rootroot00000000000000ansible-1.7.2/lib/ansible/000077500000000000000000000000001241061774000153235ustar00rootroot00000000000000ansible-1.7.2/lib/ansible/__init__.py000066400000000000000000000013751241061774000174420ustar00rootroot00000000000000# (c) 2012-2014, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . __version__ = '1.7.2' __author__ = 'Michael DeHaan' ansible-1.7.2/lib/ansible/callback_plugins/000077500000000000000000000000001241061774000206205ustar00rootroot00000000000000ansible-1.7.2/lib/ansible/callback_plugins/__init__.py000066400000000000000000000000001241061774000227170ustar00rootroot00000000000000ansible-1.7.2/lib/ansible/callback_plugins/noop.py000066400000000000000000000047351241061774000221560ustar00rootroot00000000000000# (C) 2012-2014, Michael DeHaan, # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . class CallbackModule(object): """ this is an example ansible callback file that does nothing. You can drop other classes in the same directory to define your own handlers. Methods you do not use can be omitted. If self.disabled is set to True, the plugin methods will not be called. example uses include: logging, emailing, storing info, etc """ def __init__(self): #if foo: # self.disabled = True pass def on_any(self, *args, **kwargs): pass def runner_on_failed(self, host, res, ignore_errors=False): pass def runner_on_ok(self, host, res): pass def runner_on_skipped(self, host, item=None): pass def runner_on_unreachable(self, host, res): pass def runner_on_no_hosts(self): pass def runner_on_async_poll(self, host, res, jid, clock): pass def runner_on_async_ok(self, host, res, jid): pass def runner_on_async_failed(self, host, res, jid): pass def playbook_on_start(self): pass def playbook_on_notify(self, host, handler): pass def playbook_on_no_hosts_matched(self): pass def playbook_on_no_hosts_remaining(self): pass def playbook_on_task_start(self, name, is_conditional): pass def playbook_on_vars_prompt(self, varname, private=True, prompt=None, encrypt=None, confirm=False, salt_size=None, salt=None, default=None): pass def playbook_on_setup(self): pass def playbook_on_import_for_host(self, host, imported_file): pass def playbook_on_not_import_for_host(self, host, missing_file): pass def playbook_on_play_start(self, name): pass def playbook_on_stats(self, stats): pass ansible-1.7.2/lib/ansible/callbacks.py000066400000000000000000000615431241061774000176250ustar00rootroot00000000000000# (C) 2012-2014, Michael DeHaan, # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . import utils import sys import getpass import os import subprocess import random import fnmatch import tempfile import fcntl import constants from ansible.color import stringc import logging if constants.DEFAULT_LOG_PATH != '': path = constants.DEFAULT_LOG_PATH if (os.path.exists(path) and not os.access(path, os.W_OK)) and not os.access(os.path.dirname(path), os.W_OK): sys.stderr.write("log file at %s is not writeable, aborting\n" % path) sys.exit(1) logging.basicConfig(filename=path, level=logging.DEBUG, format='%(asctime)s %(name)s %(message)s') mypid = str(os.getpid()) user = getpass.getuser() logger = logging.getLogger("p=%s u=%s | " % (mypid, user)) callback_plugins = [] def load_callback_plugins(): global callback_plugins callback_plugins = [x for x in utils.plugins.callback_loader.all()] def get_cowsay_info(): if constants.ANSIBLE_NOCOWS: return (None, None) cowsay = None if os.path.exists("/usr/bin/cowsay"): cowsay = "/usr/bin/cowsay" elif os.path.exists("/usr/games/cowsay"): cowsay = "/usr/games/cowsay" elif os.path.exists("/usr/local/bin/cowsay"): # BSD path for cowsay cowsay = "/usr/local/bin/cowsay" elif os.path.exists("/opt/local/bin/cowsay"): # MacPorts path for cowsay cowsay = "/opt/local/bin/cowsay" noncow = os.getenv("ANSIBLE_COW_SELECTION",None) if cowsay and noncow == 'random': cmd = subprocess.Popen([cowsay, "-l"], stdout=subprocess.PIPE, stderr=subprocess.PIPE) (out, err) = cmd.communicate() cows = out.split() cows.append(False) noncow = random.choice(cows) return (cowsay, noncow) cowsay, noncow = get_cowsay_info() def log_lockfile(): # create the path for the lockfile and open it tempdir = tempfile.gettempdir() uid = os.getuid() path = os.path.join(tempdir, ".ansible-lock.%s" % uid) lockfile = open(path, 'w') # use fcntl to set FD_CLOEXEC on the file descriptor, # so that we don't leak the file descriptor later lockfile_fd = lockfile.fileno() old_flags = fcntl.fcntl(lockfile_fd, fcntl.F_GETFD) fcntl.fcntl(lockfile_fd, fcntl.F_SETFD, old_flags | fcntl.FD_CLOEXEC) return lockfile LOG_LOCK = log_lockfile() def log_flock(runner): if runner is not None: try: fcntl.lockf(runner.output_lockfile, fcntl.LOCK_EX) except OSError: # already got closed? pass else: try: fcntl.lockf(LOG_LOCK, fcntl.LOCK_EX) except OSError: pass def log_unflock(runner): if runner is not None: try: fcntl.lockf(runner.output_lockfile, fcntl.LOCK_UN) except OSError: # already got closed? pass else: try: fcntl.lockf(LOG_LOCK, fcntl.LOCK_UN) except OSError: pass def set_playbook(callback, playbook): ''' used to notify callback plugins of playbook context ''' callback.playbook = playbook for callback_plugin in callback_plugins: callback_plugin.playbook = playbook def set_play(callback, play): ''' used to notify callback plugins of context ''' callback.play = play for callback_plugin in callback_plugins: callback_plugin.play = play def set_task(callback, task): ''' used to notify callback plugins of context ''' callback.task = task for callback_plugin in callback_plugins: callback_plugin.task = task def display(msg, color=None, stderr=False, screen_only=False, log_only=False, runner=None): # prevent a very rare case of interlaced multiprocess I/O log_flock(runner) msg2 = msg if color: msg2 = stringc(msg, color) if not log_only: if not stderr: try: print msg2 except UnicodeEncodeError: print msg2.encode('utf-8') else: try: print >>sys.stderr, msg2 except UnicodeEncodeError: print >>sys.stderr, msg2.encode('utf-8') if constants.DEFAULT_LOG_PATH != '': while msg.startswith("\n"): msg = msg.replace("\n","") if not screen_only: if color == 'red': logger.error(msg) else: logger.info(msg) log_unflock(runner) def call_callback_module(method_name, *args, **kwargs): for callback_plugin in callback_plugins: # a plugin that set self.disabled to True will not be called # see osx_say.py example for such a plugin if getattr(callback_plugin, 'disabled', False): continue methods = [ getattr(callback_plugin, method_name, None), getattr(callback_plugin, 'on_any', None) ] for method in methods: if method is not None: method(*args, **kwargs) def vv(msg, host=None): return verbose(msg, host=host, caplevel=1) def vvv(msg, host=None): return verbose(msg, host=host, caplevel=2) def vvvv(msg, host=None): return verbose(msg, host=host, caplevel=3) def verbose(msg, host=None, caplevel=2): msg = utils.sanitize_output(msg) if utils.VERBOSITY > caplevel: if host is None: display(msg, color='blue') else: display("<%s> %s" % (host, msg), color='blue') class AggregateStats(object): ''' holds stats about per-host activity during playbook runs ''' def __init__(self): self.processed = {} self.failures = {} self.ok = {} self.dark = {} self.changed = {} self.skipped = {} def _increment(self, what, host): ''' helper function to bump a statistic ''' self.processed[host] = 1 prev = (getattr(self, what)).get(host, 0) getattr(self, what)[host] = prev+1 def compute(self, runner_results, setup=False, poll=False, ignore_errors=False): ''' walk through all results and increment stats ''' for (host, value) in runner_results.get('contacted', {}).iteritems(): if not ignore_errors and (('failed' in value and bool(value['failed'])) or ('failed_when_result' in value and [value['failed_when_result']] or ['rc' in value and value['rc'] != 0])[0]): self._increment('failures', host) elif 'skipped' in value and bool(value['skipped']): self._increment('skipped', host) elif 'changed' in value and bool(value['changed']): if not setup and not poll: self._increment('changed', host) self._increment('ok', host) else: if not poll or ('finished' in value and bool(value['finished'])): self._increment('ok', host) for (host, value) in runner_results.get('dark', {}).iteritems(): self._increment('dark', host) def summarize(self, host): ''' return information about a particular host ''' return dict( ok = self.ok.get(host, 0), failures = self.failures.get(host, 0), unreachable = self.dark.get(host,0), changed = self.changed.get(host, 0), skipped = self.skipped.get(host, 0) ) ######################################################################## def regular_generic_msg(hostname, result, oneline, caption): ''' output on the result of a module run that is not command ''' if not oneline: return "%s | %s >> %s\n" % (hostname, caption, utils.jsonify(result,format=True)) else: return "%s | %s >> %s\n" % (hostname, caption, utils.jsonify(result)) def banner_cowsay(msg): if ": [" in msg: msg = msg.replace("[","") if msg.endswith("]"): msg = msg[:-1] runcmd = [cowsay,"-W", "60"] if noncow: runcmd.append('-f') runcmd.append(noncow) runcmd.append(msg) cmd = subprocess.Popen(runcmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE) (out, err) = cmd.communicate() return "%s\n" % out def banner_normal(msg): width = 78 - len(msg) if width < 3: width = 3 filler = "*" * width return "\n%s %s " % (msg, filler) def banner(msg): if cowsay: try: return banner_cowsay(msg) except OSError: # somebody cleverly deleted cowsay or something during the PB run. heh. return banner_normal(msg) return banner_normal(msg) def command_generic_msg(hostname, result, oneline, caption): ''' output the result of a command run ''' rc = result.get('rc', '0') stdout = result.get('stdout','') stderr = result.get('stderr', '') msg = result.get('msg', '') hostname = hostname.encode('utf-8') caption = caption.encode('utf-8') if not oneline: buf = "%s | %s | rc=%s >>\n" % (hostname, caption, result.get('rc',0)) if stdout: buf += stdout if stderr: buf += stderr if msg: buf += msg return buf + "\n" else: if stderr: return "%s | %s | rc=%s | (stdout) %s (stderr) %s" % (hostname, caption, rc, stdout, stderr) else: return "%s | %s | rc=%s | (stdout) %s" % (hostname, caption, rc, stdout) def host_report_msg(hostname, module_name, result, oneline): ''' summarize the JSON results for a particular host ''' failed = utils.is_failed(result) msg = ('', None) if module_name in [ 'command', 'shell', 'raw' ] and 'ansible_job_id' not in result and result.get('parsed',True) != False: if not failed: msg = (command_generic_msg(hostname, result, oneline, 'success'), 'green') else: msg = (command_generic_msg(hostname, result, oneline, 'FAILED'), 'red') else: if not failed: msg = (regular_generic_msg(hostname, result, oneline, 'success'), 'green') else: msg = (regular_generic_msg(hostname, result, oneline, 'FAILED'), 'red') return msg ############################################### class DefaultRunnerCallbacks(object): ''' no-op callbacks for API usage of Runner() if no callbacks are specified ''' def __init__(self): pass def on_failed(self, host, res, ignore_errors=False): call_callback_module('runner_on_failed', host, res, ignore_errors=ignore_errors) def on_ok(self, host, res): call_callback_module('runner_on_ok', host, res) def on_skipped(self, host, item=None): call_callback_module('runner_on_skipped', host, item=item) def on_unreachable(self, host, res): call_callback_module('runner_on_unreachable', host, res) def on_no_hosts(self): call_callback_module('runner_on_no_hosts') def on_async_poll(self, host, res, jid, clock): call_callback_module('runner_on_async_poll', host, res, jid, clock) def on_async_ok(self, host, res, jid): call_callback_module('runner_on_async_ok', host, res, jid) def on_async_failed(self, host, res, jid): call_callback_module('runner_on_async_failed', host, res, jid) def on_file_diff(self, host, diff): call_callback_module('runner_on_file_diff', host, diff) ######################################################################## class CliRunnerCallbacks(DefaultRunnerCallbacks): ''' callbacks for use by /usr/bin/ansible ''' def __init__(self): # set by /usr/bin/ansible later self.options = None self._async_notified = {} def on_failed(self, host, res, ignore_errors=False): self._on_any(host,res) super(CliRunnerCallbacks, self).on_failed(host, res, ignore_errors=ignore_errors) def on_ok(self, host, res): # hide magic variables used for ansible-playbook res.pop('verbose_override', None) res.pop('verbose_always', None) self._on_any(host,res) super(CliRunnerCallbacks, self).on_ok(host, res) def on_unreachable(self, host, res): if type(res) == dict: res = res.get('msg','') display("%s | FAILED => %s" % (host, res), stderr=True, color='red', runner=self.runner) if self.options.tree: utils.write_tree_file( self.options.tree, host, utils.jsonify(dict(failed=True, msg=res),format=True) ) super(CliRunnerCallbacks, self).on_unreachable(host, res) def on_skipped(self, host, item=None): display("%s | skipped" % (host), runner=self.runner) super(CliRunnerCallbacks, self).on_skipped(host, item) def on_no_hosts(self): display("no hosts matched\n", stderr=True, runner=self.runner) super(CliRunnerCallbacks, self).on_no_hosts() def on_async_poll(self, host, res, jid, clock): if jid not in self._async_notified: self._async_notified[jid] = clock + 1 if self._async_notified[jid] > clock: self._async_notified[jid] = clock display(" polling, %ss remaining" % (jid, clock), runner=self.runner) super(CliRunnerCallbacks, self).on_async_poll(host, res, jid, clock) def on_async_ok(self, host, res, jid): display(" finished on %s => %s"%(jid, host, utils.jsonify(res,format=True)), runner=self.runner) super(CliRunnerCallbacks, self).on_async_ok(host, res, jid) def on_async_failed(self, host, res, jid): display(" FAILED on %s => %s"%(jid, host, utils.jsonify(res,format=True)), color='red', stderr=True, runner=self.runner) super(CliRunnerCallbacks, self).on_async_failed(host,res,jid) def _on_any(self, host, result): result2 = result.copy() result2.pop('invocation', None) (msg, color) = host_report_msg(host, self.options.module_name, result2, self.options.one_line) display(msg, color=color, runner=self.runner) if self.options.tree: utils.write_tree_file(self.options.tree, host, utils.jsonify(result2,format=True)) def on_file_diff(self, host, diff): display(utils.get_diff(diff), runner=self.runner) super(CliRunnerCallbacks, self).on_file_diff(host, diff) ######################################################################## class PlaybookRunnerCallbacks(DefaultRunnerCallbacks): ''' callbacks used for Runner() from /usr/bin/ansible-playbook ''' def __init__(self, stats, verbose=None): if verbose is None: verbose = utils.VERBOSITY self.verbose = verbose self.stats = stats self._async_notified = {} def on_unreachable(self, host, results): delegate_to = self.runner.module_vars.get('delegate_to') if delegate_to: host = '%s -> %s' % (host, delegate_to) item = None if type(results) == dict: item = results.get('item', None) if item: msg = "fatal: [%s] => (item=%s) => %s" % (host, item, results) else: msg = "fatal: [%s] => %s" % (host, results) display(msg, color='red', runner=self.runner) super(PlaybookRunnerCallbacks, self).on_unreachable(host, results) def on_failed(self, host, results, ignore_errors=False): delegate_to = self.runner.module_vars.get('delegate_to') if delegate_to: host = '%s -> %s' % (host, delegate_to) results2 = results.copy() results2.pop('invocation', None) item = results2.get('item', None) parsed = results2.get('parsed', True) module_msg = '' if not parsed: module_msg = results2.pop('msg', None) stderr = results2.pop('stderr', None) stdout = results2.pop('stdout', None) returned_msg = results2.pop('msg', None) if item: msg = "failed: [%s] => (item=%s) => %s" % (host, item, utils.jsonify(results2)) else: msg = "failed: [%s] => %s" % (host, utils.jsonify(results2)) display(msg, color='red', runner=self.runner) if stderr: display("stderr: %s" % stderr, color='red', runner=self.runner) if stdout: display("stdout: %s" % stdout, color='red', runner=self.runner) if returned_msg: display("msg: %s" % returned_msg, color='red', runner=self.runner) if not parsed and module_msg: display("invalid output was: %s" % module_msg, color='red', runner=self.runner) if ignore_errors: display("...ignoring", color='cyan', runner=self.runner) super(PlaybookRunnerCallbacks, self).on_failed(host, results, ignore_errors=ignore_errors) def on_ok(self, host, host_result): delegate_to = self.runner.module_vars.get('delegate_to') if delegate_to: host = '%s -> %s' % (host, delegate_to) item = host_result.get('item', None) host_result2 = host_result.copy() host_result2.pop('invocation', None) verbose_always = host_result2.pop('verbose_always', False) changed = host_result.get('changed', False) ok_or_changed = 'ok' if changed: ok_or_changed = 'changed' # show verbose output for non-setup module results if --verbose is used msg = '' if (not self.verbose or host_result2.get("verbose_override",None) is not None) and not verbose_always: if item: msg = "%s: [%s] => (item=%s)" % (ok_or_changed, host, item) else: if 'ansible_job_id' not in host_result or 'finished' in host_result: msg = "%s: [%s]" % (ok_or_changed, host) else: # verbose ... if item: msg = "%s: [%s] => (item=%s) => %s" % (ok_or_changed, host, item, utils.jsonify(host_result2, format=verbose_always)) else: if 'ansible_job_id' not in host_result or 'finished' in host_result2: msg = "%s: [%s] => %s" % (ok_or_changed, host, utils.jsonify(host_result2, format=verbose_always)) if msg != '': if not changed: display(msg, color='green', runner=self.runner) else: display(msg, color='yellow', runner=self.runner) super(PlaybookRunnerCallbacks, self).on_ok(host, host_result) def on_skipped(self, host, item=None): delegate_to = self.runner.module_vars.get('delegate_to') if delegate_to: host = '%s -> %s' % (host, delegate_to) if constants.DISPLAY_SKIPPED_HOSTS: msg = '' if item: msg = "skipping: [%s] => (item=%s)" % (host, item) else: msg = "skipping: [%s]" % host display(msg, color='cyan', runner=self.runner) super(PlaybookRunnerCallbacks, self).on_skipped(host, item) def on_no_hosts(self): display("FATAL: no hosts matched or all hosts have already failed -- aborting\n", color='red', runner=self.runner) super(PlaybookRunnerCallbacks, self).on_no_hosts() def on_async_poll(self, host, res, jid, clock): if jid not in self._async_notified: self._async_notified[jid] = clock + 1 if self._async_notified[jid] > clock: self._async_notified[jid] = clock msg = " polling, %ss remaining"%(jid, clock) display(msg, color='cyan', runner=self.runner) super(PlaybookRunnerCallbacks, self).on_async_poll(host,res,jid,clock) def on_async_ok(self, host, res, jid): msg = " finished on %s"%(jid, host) display(msg, color='cyan', runner=self.runner) super(PlaybookRunnerCallbacks, self).on_async_ok(host, res, jid) def on_async_failed(self, host, res, jid): msg = " FAILED on %s" % (jid, host) display(msg, color='red', stderr=True, runner=self.runner) super(PlaybookRunnerCallbacks, self).on_async_failed(host,res,jid) def on_file_diff(self, host, diff): display(utils.get_diff(diff), runner=self.runner) super(PlaybookRunnerCallbacks, self).on_file_diff(host, diff) ######################################################################## class PlaybookCallbacks(object): ''' playbook.py callbacks used by /usr/bin/ansible-playbook ''' def __init__(self, verbose=False): self.verbose = verbose def on_start(self): call_callback_module('playbook_on_start') def on_notify(self, host, handler): call_callback_module('playbook_on_notify', host, handler) def on_no_hosts_matched(self): display("skipping: no hosts matched", color='cyan') call_callback_module('playbook_on_no_hosts_matched') def on_no_hosts_remaining(self): display("\nFATAL: all hosts have already failed -- aborting", color='red') call_callback_module('playbook_on_no_hosts_remaining') def on_task_start(self, name, is_conditional): msg = "TASK: [%s]" % name if is_conditional: msg = "NOTIFIED: [%s]" % name if hasattr(self, 'start_at'): if name == self.start_at or fnmatch.fnmatch(name, self.start_at): # we found out match, we can get rid of this now del self.start_at elif self.task.role_name: # handle tasks prefixed with rolenames actual_name = name.split('|', 1)[1].lstrip() if actual_name == self.start_at or fnmatch.fnmatch(actual_name, self.start_at): del self.start_at if hasattr(self, 'start_at'): # we still have start_at so skip the task self.skip_task = True elif hasattr(self, 'step') and self.step: msg = ('Perform task: %s (y/n/c): ' % name).encode(sys.stdout.encoding) resp = raw_input(msg) if resp.lower() in ['y','yes']: self.skip_task = False display(banner(msg)) elif resp.lower() in ['c', 'continue']: self.skip_task = False self.step = False display(banner(msg)) else: self.skip_task = True else: self.skip_task = False display(banner(msg)) call_callback_module('playbook_on_task_start', name, is_conditional) def on_vars_prompt(self, varname, private=True, prompt=None, encrypt=None, confirm=False, salt_size=None, salt=None, default=None): if prompt and default is not None: msg = "%s [%s]: " % (prompt, default) elif prompt: msg = "%s: " % prompt else: msg = 'input for %s: ' % varname def prompt(prompt, private): msg = prompt.encode(sys.stdout.encoding) if private: return getpass.getpass(msg) return raw_input(msg) if confirm: while True: result = prompt(msg, private) second = prompt("confirm " + msg, private) if result == second: break display("***** VALUES ENTERED DO NOT MATCH ****") else: result = prompt(msg, private) # if result is false and default is not None if not result and default: result = default if encrypt: result = utils.do_encrypt(result,encrypt,salt_size,salt) call_callback_module( 'playbook_on_vars_prompt', varname, private=private, prompt=prompt, encrypt=encrypt, confirm=confirm, salt_size=salt_size, salt=None, default=default ) return result def on_setup(self): display(banner("GATHERING FACTS")) call_callback_module('playbook_on_setup') def on_import_for_host(self, host, imported_file): msg = "%s: importing %s" % (host, imported_file) display(msg, color='cyan') call_callback_module('playbook_on_import_for_host', host, imported_file) def on_not_import_for_host(self, host, missing_file): msg = "%s: not importing file: %s" % (host, missing_file) display(msg, color='cyan') call_callback_module('playbook_on_not_import_for_host', host, missing_file) def on_play_start(self, name): display(banner("PLAY [%s]" % name)) call_callback_module('playbook_on_play_start', name) def on_stats(self, stats): call_callback_module('playbook_on_stats', stats) ansible-1.7.2/lib/ansible/color.py000066400000000000000000000045231241061774000170170ustar00rootroot00000000000000# (c) 2012-2014, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . import sys import constants ANSIBLE_COLOR=True if constants.ANSIBLE_NOCOLOR: ANSIBLE_COLOR=False elif not hasattr(sys.stdout, 'isatty') or not sys.stdout.isatty(): ANSIBLE_COLOR=False else: try: import curses curses.setupterm() if curses.tigetnum('colors') < 0: ANSIBLE_COLOR=False except ImportError: # curses library was not found pass except curses.error: # curses returns an error (e.g. could not find terminal) ANSIBLE_COLOR=False if constants.ANSIBLE_FORCE_COLOR: ANSIBLE_COLOR=True # --- begin "pretty" # # pretty - A miniature library that provides a Python print and stdout # wrapper that makes colored terminal text easier to use (eg. without # having to mess around with ANSI escape sequences). This code is public # domain - there is no license except that you must leave this header. # # Copyright (C) 2008 Brian Nez # # http://nezzen.net/2008/06/23/colored-text-in-python-using-ansi-escape-sequences/ codeCodes = { 'black': '0;30', 'bright gray': '0;37', 'blue': '0;34', 'white': '1;37', 'green': '0;32', 'bright blue': '1;34', 'cyan': '0;36', 'bright green': '1;32', 'red': '0;31', 'bright cyan': '1;36', 'purple': '0;35', 'bright red': '1;31', 'yellow': '0;33', 'bright purple': '1;35', 'dark gray': '1;30', 'bright yellow': '1;33', 'normal': '0' } def stringc(text, color): """String in color.""" if ANSIBLE_COLOR: return "\033["+codeCodes[color]+"m"+text+"\033[0m" else: return text # --- end "pretty" ansible-1.7.2/lib/ansible/constants.py000066400000000000000000000267361241061774000177270ustar00rootroot00000000000000# (c) 2012-2014, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . import os import pwd import sys import ConfigParser from string import ascii_letters, digits # copied from utils, avoid circular reference fun :) def mk_boolean(value): if value is None: return False val = str(value) if val.lower() in [ "true", "t", "y", "1", "yes" ]: return True else: return False def get_config(p, section, key, env_var, default, boolean=False, integer=False, floating=False, islist=False): ''' return a configuration variable with casting ''' value = _get_config(p, section, key, env_var, default) if boolean: return mk_boolean(value) if value and integer: return int(value) if value and floating: return float(value) if value and islist: return [x.strip() for x in value.split(',')] return value def _get_config(p, section, key, env_var, default): ''' helper function for get_config ''' if env_var is not None: value = os.environ.get(env_var, None) if value is not None: return value if p is not None: try: return p.get(section, key, raw=True) except: return default return default def load_config_file(): ''' Load Config File order(first found is used): ENV, CWD, HOME, /etc/ansible ''' p = ConfigParser.ConfigParser() path0 = os.getenv("ANSIBLE_CONFIG", None) if path0 is not None: path0 = os.path.expanduser(path0) path1 = os.getcwd() + "/ansible.cfg" path2 = os.path.expanduser("~/.ansible.cfg") path3 = "/etc/ansible/ansible.cfg" for path in [path0, path1, path2, path3]: if path is not None and os.path.exists(path): p.read(path) return p return None def shell_expand_path(path): ''' shell_expand_path is needed as os.path.expanduser does not work when path is None, which is the default for ANSIBLE_PRIVATE_KEY_FILE ''' if path: path = os.path.expanduser(path) return path p = load_config_file() active_user = pwd.getpwuid(os.geteuid())[0] # Needed so the RPM can call setup.py and have modules land in the # correct location. See #1277 for discussion if getattr(sys, "real_prefix", None): # in a virtualenv DIST_MODULE_PATH = os.path.join(sys.prefix, 'share/ansible/') else: DIST_MODULE_PATH = '/usr/share/ansible/' # check all of these extensions when looking for yaml files for things like # group variables -- really anything we can load YAML_FILENAME_EXTENSIONS = [ "", ".yml", ".yaml", ".json" ] # sections in config file DEFAULTS='defaults' # configurable things DEFAULT_HOST_LIST = shell_expand_path(get_config(p, DEFAULTS, 'hostfile', 'ANSIBLE_HOSTS', '/etc/ansible/hosts')) DEFAULT_MODULE_PATH = get_config(p, DEFAULTS, 'library', 'ANSIBLE_LIBRARY', DIST_MODULE_PATH) DEFAULT_ROLES_PATH = shell_expand_path(get_config(p, DEFAULTS, 'roles_path', 'ANSIBLE_ROLES_PATH', '/etc/ansible/roles')) DEFAULT_REMOTE_TMP = shell_expand_path(get_config(p, DEFAULTS, 'remote_tmp', 'ANSIBLE_REMOTE_TEMP', '$HOME/.ansible/tmp')) DEFAULT_MODULE_NAME = get_config(p, DEFAULTS, 'module_name', None, 'command') DEFAULT_PATTERN = get_config(p, DEFAULTS, 'pattern', None, '*') DEFAULT_FORKS = get_config(p, DEFAULTS, 'forks', 'ANSIBLE_FORKS', 5, integer=True) DEFAULT_MODULE_ARGS = get_config(p, DEFAULTS, 'module_args', 'ANSIBLE_MODULE_ARGS', '') DEFAULT_MODULE_LANG = get_config(p, DEFAULTS, 'module_lang', 'ANSIBLE_MODULE_LANG', 'en_US.UTF-8') DEFAULT_TIMEOUT = get_config(p, DEFAULTS, 'timeout', 'ANSIBLE_TIMEOUT', 10, integer=True) DEFAULT_POLL_INTERVAL = get_config(p, DEFAULTS, 'poll_interval', 'ANSIBLE_POLL_INTERVAL', 15, integer=True) DEFAULT_REMOTE_USER = get_config(p, DEFAULTS, 'remote_user', 'ANSIBLE_REMOTE_USER', active_user) DEFAULT_ASK_PASS = get_config(p, DEFAULTS, 'ask_pass', 'ANSIBLE_ASK_PASS', False, boolean=True) DEFAULT_PRIVATE_KEY_FILE = shell_expand_path(get_config(p, DEFAULTS, 'private_key_file', 'ANSIBLE_PRIVATE_KEY_FILE', None)) DEFAULT_SUDO_USER = get_config(p, DEFAULTS, 'sudo_user', 'ANSIBLE_SUDO_USER', 'root') DEFAULT_ASK_SUDO_PASS = get_config(p, DEFAULTS, 'ask_sudo_pass', 'ANSIBLE_ASK_SUDO_PASS', False, boolean=True) DEFAULT_REMOTE_PORT = get_config(p, DEFAULTS, 'remote_port', 'ANSIBLE_REMOTE_PORT', None, integer=True) DEFAULT_ASK_VAULT_PASS = get_config(p, DEFAULTS, 'ask_vault_pass', 'ANSIBLE_ASK_VAULT_PASS', False, boolean=True) DEFAULT_VAULT_PASSWORD_FILE = shell_expand_path(get_config(p, DEFAULTS, 'vault_password_file', 'ANSIBLE_VAULT_PASSWORD_FILE', None)) DEFAULT_TRANSPORT = get_config(p, DEFAULTS, 'transport', 'ANSIBLE_TRANSPORT', 'smart') DEFAULT_SCP_IF_SSH = get_config(p, 'ssh_connection', 'scp_if_ssh', 'ANSIBLE_SCP_IF_SSH', False, boolean=True) DEFAULT_MANAGED_STR = get_config(p, DEFAULTS, 'ansible_managed', None, 'Ansible managed: {file} modified on %Y-%m-%d %H:%M:%S by {uid} on {host}') DEFAULT_SYSLOG_FACILITY = get_config(p, DEFAULTS, 'syslog_facility', 'ANSIBLE_SYSLOG_FACILITY', 'LOG_USER') DEFAULT_KEEP_REMOTE_FILES = get_config(p, DEFAULTS, 'keep_remote_files', 'ANSIBLE_KEEP_REMOTE_FILES', False, boolean=True) DEFAULT_SUDO = get_config(p, DEFAULTS, 'sudo', 'ANSIBLE_SUDO', False, boolean=True) DEFAULT_SUDO_EXE = get_config(p, DEFAULTS, 'sudo_exe', 'ANSIBLE_SUDO_EXE', 'sudo') DEFAULT_SUDO_FLAGS = get_config(p, DEFAULTS, 'sudo_flags', 'ANSIBLE_SUDO_FLAGS', '-H') DEFAULT_HASH_BEHAVIOUR = get_config(p, DEFAULTS, 'hash_behaviour', 'ANSIBLE_HASH_BEHAVIOUR', 'replace') DEFAULT_JINJA2_EXTENSIONS = get_config(p, DEFAULTS, 'jinja2_extensions', 'ANSIBLE_JINJA2_EXTENSIONS', None) DEFAULT_EXECUTABLE = get_config(p, DEFAULTS, 'executable', 'ANSIBLE_EXECUTABLE', '/bin/sh') DEFAULT_SU_EXE = get_config(p, DEFAULTS, 'su_exe', 'ANSIBLE_SU_EXE', 'su') DEFAULT_SU = get_config(p, DEFAULTS, 'su', 'ANSIBLE_SU', False, boolean=True) DEFAULT_SU_FLAGS = get_config(p, DEFAULTS, 'su_flags', 'ANSIBLE_SU_FLAGS', '') DEFAULT_SU_USER = get_config(p, DEFAULTS, 'su_user', 'ANSIBLE_SU_USER', 'root') DEFAULT_ASK_SU_PASS = get_config(p, DEFAULTS, 'ask_su_pass', 'ANSIBLE_ASK_SU_PASS', False, boolean=True) DEFAULT_GATHERING = get_config(p, DEFAULTS, 'gathering', 'ANSIBLE_GATHERING', 'implicit').lower() DEFAULT_ACTION_PLUGIN_PATH = get_config(p, DEFAULTS, 'action_plugins', 'ANSIBLE_ACTION_PLUGINS', '/usr/share/ansible_plugins/action_plugins') DEFAULT_CALLBACK_PLUGIN_PATH = get_config(p, DEFAULTS, 'callback_plugins', 'ANSIBLE_CALLBACK_PLUGINS', '/usr/share/ansible_plugins/callback_plugins') DEFAULT_CONNECTION_PLUGIN_PATH = get_config(p, DEFAULTS, 'connection_plugins', 'ANSIBLE_CONNECTION_PLUGINS', '/usr/share/ansible_plugins/connection_plugins') DEFAULT_LOOKUP_PLUGIN_PATH = get_config(p, DEFAULTS, 'lookup_plugins', 'ANSIBLE_LOOKUP_PLUGINS', '/usr/share/ansible_plugins/lookup_plugins') DEFAULT_VARS_PLUGIN_PATH = get_config(p, DEFAULTS, 'vars_plugins', 'ANSIBLE_VARS_PLUGINS', '/usr/share/ansible_plugins/vars_plugins') DEFAULT_FILTER_PLUGIN_PATH = get_config(p, DEFAULTS, 'filter_plugins', 'ANSIBLE_FILTER_PLUGINS', '/usr/share/ansible_plugins/filter_plugins') DEFAULT_LOG_PATH = shell_expand_path(get_config(p, DEFAULTS, 'log_path', 'ANSIBLE_LOG_PATH', '')) ANSIBLE_FORCE_COLOR = get_config(p, DEFAULTS, 'force_color', 'ANSIBLE_FORCE_COLOR', None, boolean=True) ANSIBLE_NOCOLOR = get_config(p, DEFAULTS, 'nocolor', 'ANSIBLE_NOCOLOR', None, boolean=True) ANSIBLE_NOCOWS = get_config(p, DEFAULTS, 'nocows', 'ANSIBLE_NOCOWS', None, boolean=True) DISPLAY_SKIPPED_HOSTS = get_config(p, DEFAULTS, 'display_skipped_hosts', 'DISPLAY_SKIPPED_HOSTS', True, boolean=True) DEFAULT_UNDEFINED_VAR_BEHAVIOR = get_config(p, DEFAULTS, 'error_on_undefined_vars', 'ANSIBLE_ERROR_ON_UNDEFINED_VARS', True, boolean=True) HOST_KEY_CHECKING = get_config(p, DEFAULTS, 'host_key_checking', 'ANSIBLE_HOST_KEY_CHECKING', True, boolean=True) SYSTEM_WARNINGS = get_config(p, DEFAULTS, 'system_warnings', 'ANSIBLE_SYSTEM_WARNINGS', True, boolean=True) DEPRECATION_WARNINGS = get_config(p, DEFAULTS, 'deprecation_warnings', 'ANSIBLE_DEPRECATION_WARNINGS', True, boolean=True) DEFAULT_CALLABLE_WHITELIST = get_config(p, DEFAULTS, 'callable_whitelist', 'ANSIBLE_CALLABLE_WHITELIST', [], islist=True) # CONNECTION RELATED ANSIBLE_SSH_ARGS = get_config(p, 'ssh_connection', 'ssh_args', 'ANSIBLE_SSH_ARGS', None) ANSIBLE_SSH_CONTROL_PATH = get_config(p, 'ssh_connection', 'control_path', 'ANSIBLE_SSH_CONTROL_PATH', "%(directory)s/ansible-ssh-%%h-%%p-%%r") ANSIBLE_SSH_PIPELINING = get_config(p, 'ssh_connection', 'pipelining', 'ANSIBLE_SSH_PIPELINING', False, boolean=True) PARAMIKO_RECORD_HOST_KEYS = get_config(p, 'paramiko_connection', 'record_host_keys', 'ANSIBLE_PARAMIKO_RECORD_HOST_KEYS', True, boolean=True) # obsolete -- will be formally removed in 1.6 ZEROMQ_PORT = get_config(p, 'fireball_connection', 'zeromq_port', 'ANSIBLE_ZEROMQ_PORT', 5099, integer=True) ACCELERATE_PORT = get_config(p, 'accelerate', 'accelerate_port', 'ACCELERATE_PORT', 5099, integer=True) ACCELERATE_TIMEOUT = get_config(p, 'accelerate', 'accelerate_timeout', 'ACCELERATE_TIMEOUT', 30, integer=True) ACCELERATE_CONNECT_TIMEOUT = get_config(p, 'accelerate', 'accelerate_connect_timeout', 'ACCELERATE_CONNECT_TIMEOUT', 1.0, floating=True) ACCELERATE_DAEMON_TIMEOUT = get_config(p, 'accelerate', 'accelerate_daemon_timeout', 'ACCELERATE_DAEMON_TIMEOUT', 30, integer=True) ACCELERATE_KEYS_DIR = get_config(p, 'accelerate', 'accelerate_keys_dir', 'ACCELERATE_KEYS_DIR', '~/.fireball.keys') ACCELERATE_KEYS_DIR_PERMS = get_config(p, 'accelerate', 'accelerate_keys_dir_perms', 'ACCELERATE_KEYS_DIR_PERMS', '700') ACCELERATE_KEYS_FILE_PERMS = get_config(p, 'accelerate', 'accelerate_keys_file_perms', 'ACCELERATE_KEYS_FILE_PERMS', '600') ACCELERATE_MULTI_KEY = get_config(p, 'accelerate', 'accelerate_multi_key', 'ACCELERATE_MULTI_KEY', False, boolean=True) PARAMIKO_PTY = get_config(p, 'paramiko_connection', 'pty', 'ANSIBLE_PARAMIKO_PTY', True, boolean=True) # characters included in auto-generated passwords DEFAULT_PASSWORD_CHARS = ascii_letters + digits + ".,:-_" # non-configurable things DEFAULT_SUDO_PASS = None DEFAULT_REMOTE_PASS = None DEFAULT_SUBSET = None DEFAULT_SU_PASS = None VAULT_VERSION_MIN = 1.0 VAULT_VERSION_MAX = 1.0 ansible-1.7.2/lib/ansible/errors.py000066400000000000000000000022521241061774000172120ustar00rootroot00000000000000# (c) 2012-2014, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . class AnsibleError(Exception): ''' The base Ansible exception from which all others should subclass ''' def __init__(self, msg): self.msg = msg def __str__(self): return self.msg class AnsibleFileNotFound(AnsibleError): pass class AnsibleConnectionFailed(AnsibleError): pass class AnsibleYAMLValidationFailed(AnsibleError): pass class AnsibleUndefinedVariable(AnsibleError): pass class AnsibleFilterError(AnsibleError): pass ansible-1.7.2/lib/ansible/inventory/000077500000000000000000000000001241061774000173605ustar00rootroot00000000000000ansible-1.7.2/lib/ansible/inventory/__init__.py000066400000000000000000000620341241061774000214760ustar00rootroot00000000000000# (c) 2012-2014, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . ############################################# import fnmatch import os import sys import re import subprocess import ansible.constants as C from ansible.inventory.ini import InventoryParser from ansible.inventory.script import InventoryScript from ansible.inventory.dir import InventoryDirectory from ansible.inventory.group import Group from ansible.inventory.host import Host from ansible import errors from ansible import utils class Inventory(object): """ Host inventory for ansible. """ __slots__ = [ 'host_list', 'groups', '_restriction', '_also_restriction', '_subset', 'parser', '_vars_per_host', '_vars_per_group', '_hosts_cache', '_groups_list', '_pattern_cache', '_vault_password', '_vars_plugins', '_playbook_basedir'] def __init__(self, host_list=C.DEFAULT_HOST_LIST, vault_password=None): # the host file file, or script path, or list of hosts # if a list, inventory data will NOT be loaded self.host_list = host_list self._vault_password=vault_password # caching to avoid repeated calculations, particularly with # external inventory scripts. self._vars_per_host = {} self._vars_per_group = {} self._hosts_cache = {} self._groups_list = {} self._pattern_cache = {} # to be set by calling set_playbook_basedir by playbook code self._playbook_basedir = None # the inventory object holds a list of groups self.groups = [] # a list of host(names) to contain current inquiries to self._restriction = None self._also_restriction = None self._subset = None if isinstance(host_list, basestring): if "," in host_list: host_list = host_list.split(",") host_list = [ h for h in host_list if h and h.strip() ] if host_list is None: self.parser = None elif isinstance(host_list, list): self.parser = None all = Group('all') self.groups = [ all ] ipv6_re = re.compile('\[([a-f:A-F0-9]*[%[0-z]+]?)\](?::(\d+))?') for x in host_list: m = ipv6_re.match(x) if m: all.add_host(Host(m.groups()[0], m.groups()[1])) else: if ":" in x: tokens = x.rsplit(":", 1) # if there is ':' in the address, then this is a ipv6 if ':' in tokens[0]: all.add_host(Host(x)) else: all.add_host(Host(tokens[0], tokens[1])) else: all.add_host(Host(x)) elif os.path.exists(host_list): if os.path.isdir(host_list): # Ensure basedir is inside the directory self.host_list = os.path.join(self.host_list, "") self.parser = InventoryDirectory(filename=host_list) self.groups = self.parser.groups.values() else: # check to see if the specified file starts with a # shebang (#!/), so if an error is raised by the parser # class we can show a more apropos error shebang_present = False try: inv_file = open(host_list) first_line = inv_file.readlines()[0] inv_file.close() if first_line.startswith('#!'): shebang_present = True except: pass if utils.is_executable(host_list): try: self.parser = InventoryScript(filename=host_list) self.groups = self.parser.groups.values() except: if not shebang_present: raise errors.AnsibleError("The file %s is marked as executable, but failed to execute correctly. " % host_list + \ "If this is not supposed to be an executable script, correct this with `chmod -x %s`." % host_list) else: raise else: try: self.parser = InventoryParser(filename=host_list) self.groups = self.parser.groups.values() except: if shebang_present: raise errors.AnsibleError("The file %s looks like it should be an executable inventory script, but is not marked executable. " % host_list + \ "Perhaps you want to correct this with `chmod +x %s`?" % host_list) else: raise utils.plugins.vars_loader.add_directory(self.basedir(), with_subdir=True) else: raise errors.AnsibleError("Unable to find an inventory file, specify one with -i ?") self._vars_plugins = [ x for x in utils.plugins.vars_loader.all(self) ] # get group vars from group_vars/ files and vars plugins for group in self.groups: group.vars = utils.combine_vars(group.vars, self.get_group_variables(group.name, vault_password=self._vault_password)) # get host vars from host_vars/ files and vars plugins for host in self.get_hosts(): host.vars = utils.combine_vars(host.vars, self.get_variables(host.name, vault_password=self._vault_password)) def _match(self, str, pattern_str): try: if pattern_str.startswith('~'): return re.search(pattern_str[1:], str) else: return fnmatch.fnmatch(str, pattern_str) except Exception, e: raise errors.AnsibleError('invalid host pattern: %s' % pattern_str) def _match_list(self, items, item_attr, pattern_str): results = [] try: if not pattern_str.startswith('~'): pattern = re.compile(fnmatch.translate(pattern_str)) else: pattern = re.compile(pattern_str[1:]) except Exception, e: raise errors.AnsibleError('invalid host pattern: %s' % pattern_str) for item in items: if pattern.match(getattr(item, item_attr)): results.append(item) return results def get_hosts(self, pattern="all"): """ find all host names matching a pattern string, taking into account any inventory restrictions or applied subsets. """ # process patterns if isinstance(pattern, list): pattern = ';'.join(pattern) patterns = pattern.replace(";",":").split(":") hosts = self._get_hosts(patterns) # exclude hosts not in a subset, if defined if self._subset: subset = self._get_hosts(self._subset) hosts = [ h for h in hosts if h in subset ] # exclude hosts mentioned in any restriction (ex: failed hosts) if self._restriction is not None: hosts = [ h for h in hosts if h.name in self._restriction ] if self._also_restriction is not None: hosts = [ h for h in hosts if h.name in self._also_restriction ] return hosts def _get_hosts(self, patterns): """ finds hosts that match a list of patterns. Handles negative matches as well as intersection matches. """ # Host specifiers should be sorted to ensure consistent behavior pattern_regular = [] pattern_intersection = [] pattern_exclude = [] for p in patterns: if p.startswith("!"): pattern_exclude.append(p) elif p.startswith("&"): pattern_intersection.append(p) elif p: pattern_regular.append(p) # if no regular pattern was given, hence only exclude and/or intersection # make that magically work if pattern_regular == []: pattern_regular = ['all'] # when applying the host selectors, run those without the "&" or "!" # first, then the &s, then the !s. patterns = pattern_regular + pattern_intersection + pattern_exclude hosts = [] for p in patterns: # avoid resolving a pattern that is a plain host if p in self._hosts_cache: hosts.append(self.get_host(p)) else: that = self.__get_hosts(p) if p.startswith("!"): hosts = [ h for h in hosts if h not in that ] elif p.startswith("&"): hosts = [ h for h in hosts if h in that ] else: to_append = [ h for h in that if h.name not in [ y.name for y in hosts ] ] hosts.extend(to_append) return hosts def __get_hosts(self, pattern): """ finds hosts that postively match a particular pattern. Does not take into account negative matches. """ if pattern in self._pattern_cache: return self._pattern_cache[pattern] (name, enumeration_details) = self._enumeration_info(pattern) hpat = self._hosts_in_unenumerated_pattern(name) result = self._apply_ranges(pattern, hpat) self._pattern_cache[pattern] = result return result def _enumeration_info(self, pattern): """ returns (pattern, limits) taking a regular pattern and finding out which parts of it correspond to start/stop offsets. limits is a tuple of (start, stop) or None """ # Do not parse regexes for enumeration info if pattern.startswith('~'): return (pattern, None) # The regex used to match on the range, which can be [x] or [x-y]. pattern_re = re.compile("^(.*)\[([-]?[0-9]+)(?:(?:-)([0-9]+))?\](.*)$") m = pattern_re.match(pattern) if m: (target, first, last, rest) = m.groups() first = int(first) if last: if first < 0: raise errors.AnsibleError("invalid range: negative indices cannot be used as the first item in a range") last = int(last) else: last = first return (target, (first, last)) else: return (pattern, None) def _apply_ranges(self, pat, hosts): """ given a pattern like foo, that matches hosts, return all of hosts given a pattern like foo[0:5], where foo matches hosts, return the first 6 hosts """ # If there are no hosts to select from, just return the # empty set. This prevents trying to do selections on an empty set. # issue#6258 if not hosts: return hosts (loose_pattern, limits) = self._enumeration_info(pat) if not limits: return hosts (left, right) = limits if left == '': left = 0 if right == '': right = 0 left=int(left) right=int(right) try: if left != right: return hosts[left:right] else: return [ hosts[left] ] except IndexError: raise errors.AnsibleError("no hosts matching the pattern '%s' were found" % pat) def _create_implicit_localhost(self, pattern): new_host = Host(pattern) new_host.set_variable("ansible_python_interpreter", sys.executable) new_host.set_variable("ansible_connection", "local") ungrouped = self.get_group("ungrouped") if ungrouped is None: self.add_group(Group('ungrouped')) ungrouped = self.get_group('ungrouped') ungrouped.add_host(new_host) return new_host def _hosts_in_unenumerated_pattern(self, pattern): """ Get all host names matching the pattern """ results = [] hosts = [] hostnames = set() # ignore any negative checks here, this is handled elsewhere pattern = pattern.replace("!","").replace("&", "") def __append_host_to_results(host): if host not in results and host.name not in hostnames: hostnames.add(host.name) results.append(host) groups = self.get_groups() for group in groups: if pattern == 'all': for host in group.get_hosts(): __append_host_to_results(host) else: if self._match(group.name, pattern): for host in group.get_hosts(): __append_host_to_results(host) else: matching_hosts = self._match_list(group.get_hosts(), 'name', pattern) for host in matching_hosts: __append_host_to_results(host) if pattern in ["localhost", "127.0.0.1"] and len(results) == 0: new_host = self._create_implicit_localhost(pattern) results.append(new_host) return results def clear_pattern_cache(self): ''' called exclusively by the add_host plugin to allow patterns to be recalculated ''' self._pattern_cache = {} def groups_for_host(self, host): if host in self._hosts_cache: return self._hosts_cache[host].get_groups() else: return [] def groups_list(self): if not self._groups_list: groups = {} for g in self.groups: groups[g.name] = [h.name for h in g.get_hosts()] ancestors = g.get_ancestors() for a in ancestors: if a.name not in groups: groups[a.name] = [h.name for h in a.get_hosts()] self._groups_list = groups return self._groups_list def get_groups(self): return self.groups def get_host(self, hostname): if hostname not in self._hosts_cache: self._hosts_cache[hostname] = self._get_host(hostname) return self._hosts_cache[hostname] def _get_host(self, hostname): if hostname in ['localhost','127.0.0.1']: for host in self.get_group('all').get_hosts(): if host.name in ['localhost', '127.0.0.1']: return host return self._create_implicit_localhost(hostname) else: for group in self.groups: for host in group.get_hosts(): if hostname == host.name: return host return None def get_group(self, groupname): for group in self.groups: if group.name == groupname: return group return None def get_group_variables(self, groupname, update_cached=False, vault_password=None): if groupname not in self._vars_per_group or update_cached: self._vars_per_group[groupname] = self._get_group_variables(groupname, vault_password=vault_password) return self._vars_per_group[groupname] def _get_group_variables(self, groupname, vault_password=None): group = self.get_group(groupname) if group is None: raise Exception("group not found: %s" % groupname) vars = {} # plugin.get_group_vars retrieves just vars for specific group vars_results = [ plugin.get_group_vars(group, vault_password=vault_password) for plugin in self._vars_plugins if hasattr(plugin, 'get_group_vars')] for updated in vars_results: if updated is not None: vars = utils.combine_vars(vars, updated) # get group variables set by Inventory Parsers vars = utils.combine_vars(vars, group.get_variables()) # Read group_vars/ files vars = utils.combine_vars(vars, self.get_group_vars(group)) return vars def get_variables(self, hostname, update_cached=False, vault_password=None): if hostname not in self._vars_per_host or update_cached: self._vars_per_host[hostname] = self._get_variables(hostname, vault_password=vault_password) return self._vars_per_host[hostname] def _get_variables(self, hostname, vault_password=None): host = self.get_host(hostname) if host is None: raise errors.AnsibleError("host not found: %s" % hostname) vars = {} # special case for ungrouped hosts, make sure group_vars/all is loaded if len(host.groups) == 1 and host.groups[0].name == 'ungrouped': vars = self.get_group_variables('all', vault_password=self._vault_password) # plugin.run retrieves all vars (also from groups) for host vars_results = [ plugin.run(host, vault_password=vault_password) for plugin in self._vars_plugins if hasattr(plugin, 'run')] for updated in vars_results: if updated is not None: vars = utils.combine_vars(vars, updated) # plugin.get_host_vars retrieves just vars for specific host vars_results = [ plugin.get_host_vars(host, vault_password=vault_password) for plugin in self._vars_plugins if hasattr(plugin, 'get_host_vars')] for updated in vars_results: if updated is not None: vars = utils.combine_vars(vars, updated) # get host variables set by Inventory Parsers vars = utils.combine_vars(vars, host.get_variables()) # still need to check InventoryParser per host vars # which actually means InventoryScript per host, # which is not performant if self.parser is not None: vars = utils.combine_vars(vars, self.parser.get_host_variables(host)) # Read host_vars/ files vars = utils.combine_vars(vars, self.get_host_vars(host)) return vars def add_group(self, group): if group.name not in self.groups_list(): self.groups.append(group) self._groups_list = None # invalidate internal cache else: raise errors.AnsibleError("group already in inventory: %s" % group.name) def list_hosts(self, pattern="all"): """ return a list of hostnames for a pattern """ result = [ h.name for h in self.get_hosts(pattern) ] if len(result) == 0 and pattern in ["localhost", "127.0.0.1"]: result = [pattern] return result def list_groups(self): return sorted([ g.name for g in self.groups ], key=lambda x: x) # TODO: remove this function def get_restriction(self): return self._restriction def restrict_to(self, restriction): """ Restrict list operations to the hosts given in restriction. This is used to exclude failed hosts in main playbook code, don't use this for other reasons. """ if not isinstance(restriction, list): restriction = [ restriction ] self._restriction = restriction def also_restrict_to(self, restriction): """ Works like restict_to but offers an additional restriction. Playbooks use this to implement serial behavior. """ if not isinstance(restriction, list): restriction = [ restriction ] self._also_restriction = restriction def subset(self, subset_pattern): """ Limits inventory results to a subset of inventory that matches a given pattern, such as to select a given geographic of numeric slice amongst a previous 'hosts' selection that only select roles, or vice versa. Corresponds to --limit parameter to ansible-playbook """ if subset_pattern is None: self._subset = None else: subset_pattern = subset_pattern.replace(',',':') subset_pattern = subset_pattern.replace(";",":").split(":") results = [] # allow Unix style @filename data for x in subset_pattern: if x.startswith("@"): fd = open(x[1:]) results.extend(fd.read().split("\n")) fd.close() else: results.append(x) self._subset = results def lift_restriction(self): """ Do not restrict list operations """ self._restriction = None def lift_also_restriction(self): """ Clears the also restriction """ self._also_restriction = None def is_file(self): """ did inventory come from a file? """ if not isinstance(self.host_list, basestring): return False return os.path.exists(self.host_list) def basedir(self): """ if inventory came from a file, what's the directory? """ if not self.is_file(): return None dname = os.path.dirname(self.host_list) if dname is None or dname == '' or dname == '.': cwd = os.getcwd() return os.path.abspath(cwd) return os.path.abspath(dname) def src(self): """ if inventory came from a file, what's the directory and file name? """ if not self.is_file(): return None return self.host_list def playbook_basedir(self): """ returns the directory of the current playbook """ return self._playbook_basedir def set_playbook_basedir(self, dir): """ sets the base directory of the playbook so inventory can use it as a basedir for host_ and group_vars, and other things. """ # Only update things if dir is a different playbook basedir if dir != self._playbook_basedir: self._playbook_basedir = dir # get group vars from group_vars/ files for group in self.groups: group.vars = utils.combine_vars(group.vars, self.get_group_vars(group, new_pb_basedir=True)) # get host vars from host_vars/ files for host in self.get_hosts(): host.vars = utils.combine_vars(host.vars, self.get_host_vars(host, new_pb_basedir=True)) # invalidate cache self._vars_per_host = {} self._vars_per_group = {} def get_host_vars(self, host, new_pb_basedir=False): """ Read host_vars/ files """ return self._get_hostgroup_vars(host=host, group=None, new_pb_basedir=new_pb_basedir) def get_group_vars(self, group, new_pb_basedir=False): """ Read group_vars/ files """ return self._get_hostgroup_vars(host=None, group=group, new_pb_basedir=new_pb_basedir) def _get_hostgroup_vars(self, host=None, group=None, new_pb_basedir=False): """ Loads variables from group_vars/ and host_vars/ in directories parallel to the inventory base directory or in the same directory as the playbook. Variables in the playbook dir will win over the inventory dir if files are in both. """ results = {} scan_pass = 0 _basedir = self.basedir() # look in both the inventory base directory and the playbook base directory # unless we do an update for a new playbook base dir if not new_pb_basedir: basedirs = [_basedir, self._playbook_basedir] else: basedirs = [self._playbook_basedir] for basedir in basedirs: # this can happen from particular API usages, particularly if not run # from /usr/bin/ansible-playbook if basedir is None: continue scan_pass = scan_pass + 1 # it's not an eror if the directory does not exist, keep moving if not os.path.exists(basedir): continue # save work of second scan if the directories are the same if _basedir == self._playbook_basedir and scan_pass != 1: continue if group and host is None: # load vars in dir/group_vars/name_of_group base_path = os.path.join(basedir, "group_vars/%s" % group.name) results = utils.load_vars(base_path, results, vault_password=self._vault_password) elif host and group is None: # same for hostvars in dir/host_vars/name_of_host base_path = os.path.join(basedir, "host_vars/%s" % host.name) results = utils.load_vars(base_path, results, vault_password=self._vault_password) # all done, results is a dictionary of variables for this particular host. return results ansible-1.7.2/lib/ansible/inventory/dir.py000066400000000000000000000244171241061774000205200ustar00rootroot00000000000000# (c) 2013, Daniel Hokka Zakrisson # (c) 2014, Serge van Ginderachter # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . ############################################# import os import ansible.constants as C from ansible.inventory.host import Host from ansible.inventory.group import Group from ansible.inventory.ini import InventoryParser from ansible.inventory.script import InventoryScript from ansible import utils from ansible import errors class InventoryDirectory(object): ''' Host inventory parser for ansible using a directory of inventories. ''' def __init__(self, filename=C.DEFAULT_HOST_LIST): self.names = os.listdir(filename) self.names.sort() self.directory = filename self.parsers = [] self.hosts = {} self.groups = {} for i in self.names: # Skip files that end with certain extensions or characters if any(i.endswith(ext) for ext in ("~", ".orig", ".bak", ".ini", ".retry", ".pyc", ".pyo")): continue # Skip hidden files if i.startswith('.') and not i.startswith('./'): continue # These are things inside of an inventory basedir if i in ("host_vars", "group_vars", "vars_plugins"): continue fullpath = os.path.join(self.directory, i) if os.path.isdir(fullpath): parser = InventoryDirectory(filename=fullpath) elif utils.is_executable(fullpath): parser = InventoryScript(filename=fullpath) else: parser = InventoryParser(filename=fullpath) self.parsers.append(parser) # retrieve all groups and hosts form the parser and add them to # self, don't look at group lists yet, to avoid # recursion trouble, but just make sure all objects exist in self newgroups = parser.groups.values() for group in newgroups: for host in group.hosts: self._add_host(host) for group in newgroups: self._add_group(group) # now check the objects lists so they contain only objects from # self; membership data in groups is already fine (except all & # ungrouped, see later), but might still reference objects not in self for group in self.groups.values(): # iterate on a copy of the lists, as those lists get changed in # the loop # list with group's child group objects: for child in group.child_groups[:]: if child != self.groups[child.name]: group.child_groups.remove(child) group.child_groups.append(self.groups[child.name]) # list with group's parent group objects: for parent in group.parent_groups[:]: if parent != self.groups[parent.name]: group.parent_groups.remove(parent) group.parent_groups.append(self.groups[parent.name]) # list with group's host objects: for host in group.hosts[:]: if host != self.hosts[host.name]: group.hosts.remove(host) group.hosts.append(self.hosts[host.name]) # also check here that the group that contains host, is # also contained in the host's group list if group not in self.hosts[host.name].groups: self.hosts[host.name].groups.append(group) # extra checks on special groups all and ungrouped # remove hosts from 'ungrouped' if they became member of other groups if 'ungrouped' in self.groups: ungrouped = self.groups['ungrouped'] # loop on a copy of ungrouped hosts, as we want to change that list for host in ungrouped.hosts[:]: if len(host.groups) > 1: host.groups.remove(ungrouped) ungrouped.hosts.remove(host) # remove hosts from 'all' if they became member of other groups # all should only contain direct children, not grandchildren # direct children should have dept == 1 if 'all' in self.groups: allgroup = self.groups['all' ] # loop on a copy of all's child groups, as we want to change that list for group in allgroup.child_groups[:]: # groups might once have beeen added to all, and later be added # to another group: we need to remove the link wit all then if len(group.parent_groups) > 1 and allgroup in group.parent_groups: # real children of all have just 1 parent, all # this one has more, so not a direct child of all anymore group.parent_groups.remove(allgroup) allgroup.child_groups.remove(group) elif allgroup not in group.parent_groups: # this group was once added to all, but doesn't list it as # a parent any more; the info in the group is the correct # info allgroup.child_groups.remove(group) def _add_group(self, group): """ Merge an existing group or add a new one; Track parent and child groups, and hosts of the new one """ if group.name not in self.groups: # it's brand new, add him! self.groups[group.name] = group if self.groups[group.name] != group: # different object, merge self._merge_groups(self.groups[group.name], group) def _add_host(self, host): if host.name not in self.hosts: # Papa's got a brand new host self.hosts[host.name] = host if self.hosts[host.name] != host: # different object, merge self._merge_hosts(self.hosts[host.name], host) def _merge_groups(self, group, newgroup): """ Merge all of instance newgroup into group, update parent/child relationships group lists may still contain group objects that exist in self with same name, but was instanciated as a different object in some other inventory parser; these are handled later """ # name if group.name != newgroup.name: raise errors.AnsibleError("Cannot merge group %s with %s" % (group.name, newgroup.name)) # depth group.depth = max([group.depth, newgroup.depth]) # hosts list (host objects are by now already added to self.hosts) for host in newgroup.hosts: grouphosts = dict([(h.name, h) for h in group.hosts]) if host.name in grouphosts: # same host name but different object, merge self._merge_hosts(grouphosts[host.name], host) else: # new membership, add host to group from self # group from self will also be added again to host.groups, but # as different object group.add_host(self.hosts[host.name]) # now remove this the old object for group in host.groups for hostgroup in [g for g in host.groups]: if hostgroup.name == group.name and hostgroup != self.groups[group.name]: self.hosts[host.name].groups.remove(hostgroup) # group child membership relation for newchild in newgroup.child_groups: # dict with existing child groups: childgroups = dict([(g.name, g) for g in group.child_groups]) # check if child of new group is already known as a child if newchild.name not in childgroups: self.groups[group.name].add_child_group(newchild) # group parent membership relation for newparent in newgroup.parent_groups: # dict with existing parent groups: parentgroups = dict([(g.name, g) for g in group.parent_groups]) # check if parent of new group is already known as a parent if newparent.name not in parentgroups: if newparent.name not in self.groups: # group does not exist yet in self, import him self.groups[newparent.name] = newparent # group now exists but not yet as a parent here self.groups[newparent.name].add_child_group(group) # variables group.vars = utils.combine_vars(group.vars, newgroup.vars) def _merge_hosts(self,host, newhost): """ Merge all of instance newhost into host """ # name if host.name != newhost.name: raise errors.AnsibleError("Cannot merge host %s with %s" % (host.name, newhost.name)) # group membership relation for newgroup in newhost.groups: # dict with existing groups: hostgroups = dict([(g.name, g) for g in host.groups]) # check if new group is already known as a group if newgroup.name not in hostgroups: if newgroup.name not in self.groups: # group does not exist yet in self, import him self.groups[newgroup.name] = newgroup # group now exists but doesn't have host yet self.groups[newgroup.name].add_host(host) # variables host.vars = utils.combine_vars(host.vars, newhost.vars) def get_host_variables(self, host): """ Gets additional host variables from all inventories """ vars = {} for i in self.parsers: vars.update(i.get_host_variables(host)) return vars ansible-1.7.2/lib/ansible/inventory/expand_hosts.py000066400000000000000000000103431241061774000224320ustar00rootroot00000000000000# (c) 2012, Zettar Inc. # Written by Chin Fang # # This file is part of Ansible # # This module is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # This software is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this software. If not, see . # ''' This module is for enhancing ansible's inventory parsing capability such that it can deal with hostnames specified using a simple pattern in the form of [beg:end], example: [1:5], [a:c], [D:G]. If beg is not specified, it defaults to 0. If beg is given and is left-zero-padded, e.g. '001', it is taken as a formatting hint when the range is expanded. e.g. [001:010] is to be expanded into 001, 002 ...009, 010. Note that when beg is specified with left zero padding, then the length of end must be the same as that of beg, else a exception is raised. ''' import string from ansible import errors def detect_range(line = None): ''' A helper function that checks a given host line to see if it contains a range pattern descibed in the docstring above. Returnes True if the given line contains a pattern, else False. ''' if 0 <= line.find("[") < line.find(":") < line.find("]"): return True else: return False def expand_hostname_range(line = None): ''' A helper function that expands a given line that contains a pattern specified in top docstring, and returns a list that consists of the expanded version. The '[' and ']' characters are used to maintain the pseudo-code appearance. They are replaced in this function with '|' to ease string splitting. References: http://ansible.github.com/patterns.html#hosts-and-groups ''' all_hosts = [] if line: # A hostname such as db[1:6]-node is considered to consists # three parts: # head: 'db' # nrange: [1:6]; range() is a built-in. Can't use the name # tail: '-node' # Add support for multiple ranges in a host so: # db[01:10:3]node-[01:10] # - to do this we split off at the first [...] set, getting the list # of hosts and then repeat until none left. # - also add an optional third parameter which contains the step. (Default: 1) # so range can be [01:10:2] -> 01 03 05 07 09 # FIXME: make this work for alphabetic sequences too. (head, nrange, tail) = line.replace('[','|',1).replace(']','|',1).split('|') bounds = nrange.split(":") if len(bounds) != 2 and len(bounds) != 3: raise errors.AnsibleError("host range incorrectly specified") beg = bounds[0] end = bounds[1] if len(bounds) == 2: step = 1 else: step = bounds[2] if not beg: beg = "0" if not end: raise errors.AnsibleError("host range end value missing") if beg[0] == '0' and len(beg) > 1: rlen = len(beg) # range length formatting hint if rlen != len(end): raise errors.AnsibleError("host range format incorrectly specified!") fill = lambda _: str(_).zfill(rlen) # range sequence else: fill = str try: i_beg = string.ascii_letters.index(beg) i_end = string.ascii_letters.index(end) if i_beg > i_end: raise errors.AnsibleError("host range format incorrectly specified!") seq = string.ascii_letters[i_beg:i_end+1] except ValueError: # not a alpha range seq = range(int(beg), int(end)+1, int(step)) for rseq in seq: hname = ''.join((head, fill(rseq), tail)) if detect_range(hname): all_hosts.extend( expand_hostname_range( hname ) ) else: all_hosts.append(hname) return all_hosts ansible-1.7.2/lib/ansible/inventory/group.py000066400000000000000000000065031241061774000210720ustar00rootroot00000000000000# (c) 2012-2014, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . class Group(object): ''' a group of ansible hosts ''' __slots__ = [ 'name', 'hosts', 'vars', 'child_groups', 'parent_groups', 'depth', '_hosts_cache' ] def __init__(self, name=None): self.depth = 0 self.name = name self.hosts = [] self.vars = {} self.child_groups = [] self.parent_groups = [] self._hosts_cache = None #self.clear_hosts_cache() if self.name is None: raise Exception("group name is required") def add_child_group(self, group): if self == group: raise Exception("can't add group to itself") # don't add if it's already there if not group in self.child_groups: self.child_groups.append(group) # update the depth of the child group.depth = max([self.depth+1, group.depth]) # update the depth of the grandchildren group._check_children_depth() # now add self to child's parent_groups list, but only if there # isn't already a group with the same name if not self.name in [g.name for g in group.parent_groups]: group.parent_groups.append(self) self.clear_hosts_cache() def _check_children_depth(self): for group in self.child_groups: group.depth = max([self.depth+1, group.depth]) group._check_children_depth() def add_host(self, host): self.hosts.append(host) host.add_group(self) self.clear_hosts_cache() def set_variable(self, key, value): self.vars[key] = value def clear_hosts_cache(self): self._hosts_cache = None for g in self.parent_groups: g.clear_hosts_cache() def get_hosts(self): if self._hosts_cache is None: self._hosts_cache = self._get_hosts() return self._hosts_cache def _get_hosts(self): hosts = [] seen = {} for kid in self.child_groups: kid_hosts = kid.get_hosts() for kk in kid_hosts: if kk not in seen: seen[kk] = 1 hosts.append(kk) for mine in self.hosts: if mine not in seen: seen[mine] = 1 hosts.append(mine) return hosts def get_variables(self): return self.vars.copy() def _get_ancestors(self): results = {} for g in self.parent_groups: results[g.name] = g results.update(g._get_ancestors()) return results def get_ancestors(self): return self._get_ancestors().values() ansible-1.7.2/lib/ansible/inventory/host.py000066400000000000000000000040441241061774000207110ustar00rootroot00000000000000# (c) 2012-2014, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . import ansible.constants as C from ansible import utils class Host(object): ''' a single ansible host ''' __slots__ = [ 'name', 'vars', 'groups' ] def __init__(self, name=None, port=None): self.name = name self.vars = {} self.groups = [] if port and port != C.DEFAULT_REMOTE_PORT: self.set_variable('ansible_ssh_port', int(port)) if self.name is None: raise Exception("host name is required") def add_group(self, group): self.groups.append(group) def set_variable(self, key, value): self.vars[key]=value def get_groups(self): groups = {} for g in self.groups: groups[g.name] = g ancestors = g.get_ancestors() for a in ancestors: groups[a.name] = a return groups.values() def get_variables(self): results = {} groups = self.get_groups() for group in sorted(groups, key=lambda g: g.depth): results = utils.combine_vars(results, group.get_variables()) results = utils.combine_vars(results, self.vars) results['inventory_hostname'] = self.name results['inventory_hostname_short'] = self.name.split('.')[0] results['group_names'] = sorted([ g.name for g in groups if g.name != 'all']) return results ansible-1.7.2/lib/ansible/inventory/ini.py000066400000000000000000000167141241061774000205220ustar00rootroot00000000000000# (c) 2012-2014, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . ############################################# import ansible.constants as C from ansible.inventory.host import Host from ansible.inventory.group import Group from ansible.inventory.expand_hosts import detect_range from ansible.inventory.expand_hosts import expand_hostname_range from ansible import errors from ansible import utils import shlex import re import ast class InventoryParser(object): """ Host inventory for ansible. """ def __init__(self, filename=C.DEFAULT_HOST_LIST): with open(filename) as fh: self.lines = fh.readlines() self.groups = {} self.hosts = {} self._parse() def _parse(self): self._parse_base_groups() self._parse_group_children() self._add_allgroup_children() self._parse_group_variables() return self.groups @staticmethod def _parse_value(v): if "#" not in v: try: return ast.literal_eval(v) # Using explicit exceptions. # Likely a string that literal_eval does not like. We wil then just set it. except ValueError: # For some reason this was thought to be malformed. pass except SyntaxError: # Is this a hash with an equals at the end? pass return v # [webservers] # alpha # beta:2345 # gamma sudo=True user=root # delta asdf=jkl favcolor=red def _add_allgroup_children(self): for group in self.groups.values(): if group.depth == 0 and group.name != 'all': self.groups['all'].add_child_group(group) def _parse_base_groups(self): # FIXME: refactor ungrouped = Group(name='ungrouped') all = Group(name='all') all.add_child_group(ungrouped) self.groups = dict(all=all, ungrouped=ungrouped) active_group_name = 'ungrouped' for line in self.lines: line = utils.before_comment(line).strip() if line.startswith("[") and line.endswith("]"): active_group_name = line.replace("[","").replace("]","") if ":vars" in line or ":children" in line: active_group_name = active_group_name.rsplit(":", 1)[0] if active_group_name not in self.groups: new_group = self.groups[active_group_name] = Group(name=active_group_name) active_group_name = None elif active_group_name not in self.groups: new_group = self.groups[active_group_name] = Group(name=active_group_name) elif line.startswith(";") or line == '': pass elif active_group_name: tokens = shlex.split(line) if len(tokens) == 0: continue hostname = tokens[0] port = C.DEFAULT_REMOTE_PORT # Three cases to check: # 0. A hostname that contains a range pesudo-code and a port # 1. A hostname that contains just a port if hostname.count(":") > 1: # Possible an IPv6 address, or maybe a host line with multiple ranges # IPv6 with Port XXX:XXX::XXX.port # FQDN foo.example.com if hostname.count(".") == 1: (hostname, port) = hostname.rsplit(".", 1) elif ("[" in hostname and "]" in hostname and ":" in hostname and (hostname.rindex("]") < hostname.rindex(":")) or ("]" not in hostname and ":" in hostname)): (hostname, port) = hostname.rsplit(":", 1) hostnames = [] if detect_range(hostname): hostnames = expand_hostname_range(hostname) else: hostnames = [hostname] for hn in hostnames: host = None if hn in self.hosts: host = self.hosts[hn] else: host = Host(name=hn, port=port) self.hosts[hn] = host if len(tokens) > 1: for t in tokens[1:]: if t.startswith('#'): break try: (k,v) = t.split("=", 1) except ValueError, e: raise errors.AnsibleError("Invalid ini entry: %s - %s" % (t, str(e))) host.set_variable(k, self._parse_value(v)) self.groups[active_group_name].add_host(host) # [southeast:children] # atlanta # raleigh def _parse_group_children(self): group = None for line in self.lines: line = line.strip() if line is None or line == '': continue if line.startswith("[") and ":children]" in line: line = line.replace("[","").replace(":children]","") group = self.groups.get(line, None) if group is None: group = self.groups[line] = Group(name=line) elif line.startswith("#") or line.startswith(";"): pass elif line.startswith("["): group = None elif group: kid_group = self.groups.get(line, None) if kid_group is None: raise errors.AnsibleError("child group is not defined: (%s)" % line) else: group.add_child_group(kid_group) # [webservers:vars] # http_port=1234 # maxRequestsPerChild=200 def _parse_group_variables(self): group = None for line in self.lines: line = line.strip() if line.startswith("[") and ":vars]" in line: line = line.replace("[","").replace(":vars]","") group = self.groups.get(line, None) if group is None: raise errors.AnsibleError("can't add vars to undefined group: %s" % line) elif line.startswith("#") or line.startswith(";"): pass elif line.startswith("["): group = None elif line == '': pass elif group: if "=" not in line: raise errors.AnsibleError("variables assigned to group must be in key=value form") else: (k, v) = [e.strip() for e in line.split("=", 1)] group.set_variable(k, self._parse_value(v)) def get_host_variables(self, host): return {} ansible-1.7.2/lib/ansible/inventory/script.py000066400000000000000000000115331241061774000212410ustar00rootroot00000000000000# (c) 2012-2014, Michael DeHaan # # This file is part of Ansible # # Ansible is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # Ansible is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with Ansible. If not, see . ############################################# import os import subprocess import ansible.constants as C from ansible.inventory.host import Host from ansible.inventory.group import Group from ansible import utils from ansible import errors import sys class InventoryScript(object): ''' Host inventory parser for ansible using external inventory scripts. ''' def __init__(self, filename=C.DEFAULT_HOST_LIST): # Support inventory scripts that are not prefixed with some # path information but happen to be in the current working # directory when '.' is not in PATH. self.filename = os.path.abspath(filename) cmd = [ self.filename, "--list" ] try: sp = subprocess.Popen(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE) except OSError, e: raise errors.AnsibleError("problem running %s (%s)" % (' '.join(cmd), e)) (stdout, stderr) = sp.communicate() self.data = stdout # see comment about _meta below self.host_vars_from_top = None self.groups = self._parse(stderr) def _parse(self, err): all_hosts = {} # not passing from_remote because data from CMDB is trusted self.raw = utils.parse_json(self.data) all = Group('all') groups = dict(all=all) group = None if 'failed' in self.raw: sys.stderr.write(err + "\n") raise errors.AnsibleError("failed to parse executable inventory script results: %s" % self.raw) for (group_name, data) in self.raw.items(): # in Ansible 1.3 and later, a "_meta" subelement may contain # a variable "hostvars" which contains a hash for each host # if this "hostvars" exists at all then do not call --host for each # host. This is for efficiency and scripts should still return data # if called with --host for backwards compat with 1.2 and earlier. if group_name == '_meta': if 'hostvars' in data: self.host_vars_from_top = data['hostvars'] continue if group_name != all.name: group = groups[group_name] = Group(group_name) else: group = all host = None if not isinstance(data, dict): data = {'hosts': data} elif not any(k in data for k in ('hosts','vars')): data = {'hosts': [group_name], 'vars': data} if 'hosts' in data: for hostname in data['hosts']: if not hostname in all_hosts: all_hosts[hostname] = Host(hostname) host = all_hosts[hostname] group.add_host(host) if 'vars' in data: for k, v in data['vars'].iteritems(): if group.name == all.name: all.set_variable(k, v) else: group.set_variable(k, v) # Separate loop to ensure all groups are defined for (group_name, data) in self.raw.items(): if group_name == '_meta': continue if isinstance(data, dict) and 'children' in data: for child_name in data['children']: if child_name in groups: groups[group_name].add_child_group(groups[child_name]) for group in groups.values(): if group.depth == 0 and group.name != 'all': all.add_child_group(group) return groups def get_host_variables(self, host): """ Runs