ansible/README.md

49 lines
2.4 KiB
Markdown
Raw Normal View History

[![PyPI version](https://badge.fury.io/py/ansible.png)](http://badge.fury.io/py/ansible)
2012-02-23 20:17:24 +01:00
Ansible
=======
2012-08-07 03:00:21 +02:00
Ansible is a radically simple configuration-management, deployment, task-execution, and
multinode orchestration framework.
2012-02-23 20:17:24 +01:00
2014-01-28 17:38:52 +01:00
Read the documentation and more at http://ansible.com/
2012-02-24 03:47:31 +01:00
2013-02-04 04:17:13 +01:00
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
2014-01-28 17:38:52 +01:00
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.
2013-02-04 04:17:13 +01:00
2012-02-24 03:47:31 +01:00
Design Principles
=================
2012-02-23 20:17:24 +01:00
2012-02-28 03:26:23 +01:00
* 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
2012-03-08 19:59:12 +01:00
* The easiest config management system to use, ever.
2012-02-23 20:17:24 +01:00
2012-03-08 19:59:12 +01:00
Get Involved
2012-02-23 20:17:24 +01:00
============
2013-12-15 17:50:18 +01:00
* 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.
* When submitting a bug report, include 1) the output of 'ansible --version', 2) what you expected to happen, 3) what actually happened, and 4) any relevant commands and output.
* 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
2012-02-29 19:58:46 +01:00
2012-04-26 03:23:50 +02:00
Branch Info
===========
2012-07-05 00:06:38 +02:00
* Releases are named after Van Halen songs.
2012-09-18 05:03:11 +02:00
* The devel branch corresponds to the release actively under development.
2012-08-07 03:15:39 +02:00
* Various release-X.Y branches exist for previous releases
2012-09-18 05:03:11 +02:00
* We'd love to have your contributions, read "CONTRIBUTING.md" for process notes.
2012-02-23 20:17:24 +01:00
Author
======
2014-01-28 17:38:52 +01:00
Michael DeHaan -- michael@ansible.com
2012-02-23 20:28:39 +01:00
2014-01-28 17:38:52 +01:00
[Ansible, Inc](http://ansible.com)
2013-11-22 08:22:48 +01:00