You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
Dag Wieërs a96f681352 Allow groups to be defined on a per-host basis
This makes it possible to define on a per-host basis what groups a host is in.
When managing a large set of systems it makes it easier to ensure each of the
systems is defined in a set of groups (e.g. production/qa/development,
linux/solaris/aix) rather than having to add systems to multiple disconnected
groups.

----
  - host: system01

  - host: system02

  - host: system03

  - group: linux
    hosts:
    - system01
    - system02

  - group: solaris
    hosts:
    - system03

  - group: production
    hosts:
    - system01
    - system03

  - group: qa
    - system02

  - group: dbserver
    hosts:
    - system01

  - group: ntpserver
    hosts:
    - system02

  - group: webserver
    - system03
----

Can be redefined as:

----
  - host: system01
    groups: [ linux, production, dbserver ]

  - host: system02
    groups: [ linux, qa, ntpserver ]

  - host: system03
    groups: [ solaris, production, webserver ]
----
13 years ago
bin Remove the -D module debug flag, which no longer is functional due to sudo pty requirements, and replace with -v/--verbose. 13 years ago
docs/man Release bump to start development on 0.6 13 years ago
examples Playbook refactoring -- work in progress. 13 years ago
hacking Adding a missing '~' to use the user's home directory instead of the root file system for the module arguments 13 years ago
lib/ansible Allow groups to be defined on a per-host basis 13 years ago
library Merge pull request #571 from sfromm/group 13 years ago
packaging bump rpm spec to 0.6 13 years ago
test Remove the -D module debug flag, which no longer is functional due to sudo pty requirements, and replace with -v/--verbose. 13 years ago
.gitignore clean exec bits from lib/ansible/*.py, ignore Eclipse/PyDev files 13 years ago
CHANGELOG.md changelog update 13 years ago
COPYING license file should be in source tree 13 years ago
MANIFEST.in Include license file in MANIFEST.in. Fixes #284 13 years ago
Makefile debian packaging 13 years ago
README.md update versions mentioned in README.md 13 years ago
VERSION Release bump to start development on 0.6 13 years ago
setup.py Split connection code into submodules. 13 years ago

README.md

Ansible

Ansible is a radically simple configuration-management, deployment, task-execution, and multinode orchestration framework.

Read all about at it at (http://ansible.github.com)

Design Principles

  • Dead simple setup
  • Super fast & parallel by default
  • No server or client daemons; use existing SSHd
  • No additional software required on client boxes
  • Modules can be written in ANY language
  • Awesome API for creating very powerful distributed scripts
  • Be usable as non-root
  • The easiest config management system to use, ever.

Get Involved

Branch Info

  • Releases are named after Van Halen songs.
  • The master branch corresponds to release 0.5 "Amsterdam".
  • The devel branch corresponds to release 0.6 "Cabo".
  • All feature work happens on the development branch.
  • Major bug fixes will be made to the master branch, but not minor ones.
  • See CHANGELOG.md for release notes to track each release.

Patch Instructions

Contributions to the core and modules are greatly welcome.

  • Required Process:
    • Submit github pull requests to the "ansible/devel" branch for features
    • Fixes for bugs may be submitted to "ansible/master"
    • Make sure "make tests" passes before submitting any requests.
  • Bonus points:
    • Joining the mailing list
    • Fixing bugs instead of sending bug reports.
    • Using squash merges
    • Updating the "rst/*" files in the docs project and "docs/" manpage content
    • Adding more unit tests
  • Avoid:
    • Sending patches to the mailing list directly.
    • Sending feature pull requests to the 'master' branch instead of the devel branch
    • Sending pull requests to mpdehaan's personal ansible fork.

Author

Michael DeHaan -- michael.dehaan@gmail.com

http://michaeldehaan.net