mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
60f295f7a0
commit 4430ce3eefcdff0b0ceffea0ef66ea8e876a807d Merge: 631783b 649963c Author: Michael DeHaan <michael.dehaan@gmail.com> Date: Thu Jul 12 01:28:43 2012 -0400 Merge branch 'host-groups' of https://github.com/dagwieers/ansible into daggroups commit 649963ca2c2610b97a90d2449132a57ae6b39ec9 Author: Dag Wieërs <dag@wieers.com> Date: Thu Jul 12 23:01:00 2012 +0200 Added comments in the example yaml file as requested commit 7f9718f185ec991bc165c4a52b2468cf41f4c349 Author: Dag Wieërs <dag@wieers.com> Date: Thu Jul 12 22:49:38 2012 +0200 Add the default nose color too, to test specific overrides commit eb63b9e899318ce0c26902ca73af50135a6224e4 Author: Dag Wieërs <dag@wieers.com> Date: Thu Jul 12 22:44:35 2012 +0200 Introduce comics and cartoons to test yaml groups defined on a per-node basis commit aa13d233078b825a8057bebf35ed478342cf4e43 Author: Dag Wieërs <dag@wieers.com> Date: Thu Jul 12 19:33:15 2012 +0200 A small fix to revert to old state commit 264ebaa77c4243f2e9117e8d1168dc2f2eed7ee2 Author: Dag Wieërs <dag@wieers.com> Date: Thu Jul 12 19:31:51 2012 +0200 Combine both yaml unit tests into one example file commit 7db49a8048e78402c4c9a0a6cb2604689280fbbb Author: Dag Wieërs <dag@wieers.com> Date: Thu Jul 12 16:46:53 2012 +0200 Might as well fix this too commit f36c6c8c5b419865939c7e2b0b26f6c97255fdc8 Author: Dag Wieërs <dag@wieers.com> Date: Thu Jul 12 16:42:00 2012 +0200 Added unit tests for host-groups patch For the unit test I chose to keep the original yaml file in place as a reference. This patch also includes a fix. commit a96f6813522c5ae8b2be4514a2de56a775c6b7b0 Author: Dag Wieërs <dag@wieers.com> Date: Thu Jul 12 12:30:43 2012 +0200 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 ] ---- |
||
---|---|---|
bin | ||
docs/man | ||
examples | ||
hacking | ||
lib/ansible | ||
library | ||
packaging | ||
test | ||
.gitignore | ||
CHANGELOG.md | ||
COPYING | ||
Makefile | ||
MANIFEST.in | ||
README.md | ||
setup.py | ||
VERSION |
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
- ansible-project mailing list
- irc.freenode.net: #ansible
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