2c17f9becd
* vmware_guest: various fixes, improvements & additions * Add template_flag attribute to define if the destination machine is a template * Add helper class to create: * SCSI controller * Disks * Network devices * New feature: create VM without using templates * New feature: multiple NIC * New feature: multiple disks * New feature: custom SCSI controller types (default: paravirtual) * New feature: NIC can now be E1000 or VMXNet3 (default) * New feature: customize NIC mac address * New feature: new disk option autoselect_datastore permit to select the less used datastore. If datastore field is provided, filter the datastore list before selection * New feature: Implement disk resizing + addition when state=present and VM exists * New feature: when state=present and vm exists, modify the current CPU, Memory and disk space * New feature: add guest_id support permitting to customize & change current VM guest ID in VMWare * New feature: resource pool support * New feature: change VM configuration without recreating it (CPU, memory, disks, network, guest ID, resource pool) * Add 'gatherfacts' state to gather facts on a VM instead of previous 'present' state ('present' ensure the VM configuration) * Add PyVmomiCache class to cache read only object * Various python code fixes * Various documentation fixes * esxi_hostname & cluster are now exclusive * Drop ips attribute & set ip directly into networks * Little performance fixes by removing some duplicate calls to VMWare API * Python 3 portability fixes * Create many functions to make the code maintainable * Cleanup some useless attributes * Add 'suspended' as desired state for VM * Make guest_id, memory & CPU number optional in reconfiguration mode * Note: guest_id is now mandatory to create a VM from scratch (not templating) * Bux fixes + Do network IP optinal + Add network vlan option |
||
---|---|---|
.github | ||
bin | ||
contrib | ||
docs/man | ||
docs-api | ||
docsite | ||
examples | ||
hacking | ||
lib/ansible | ||
packaging | ||
test | ||
ticket_stubs | ||
.coveragerc | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.mailmap | ||
.yamllint | ||
ansible-core-sitemap.xml | ||
CHANGELOG.md | ||
CODING_GUIDELINES.md | ||
CONTRIBUTING.md | ||
COPYING | ||
Makefile | ||
MANIFEST.in | ||
MODULE_GUIDELINES.md | ||
README.md | ||
RELEASES.txt | ||
ROADMAP.rst | ||
setup.py | ||
shippable.yml | ||
tox.ini | ||
VERSION |
Ansible
Ansible is a radically simple IT automation system. It handles configuration-management, application deployment, cloud provisioning, ad-hoc task-execution, and multinode orchestration - including trivializing things like zero downtime rolling updates with load balancers.
Read the documentation and more at https://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 for a variety of platforms.
If you want to download a tarball of a release, go to releases.ansible.com, though most users use yum
(using the EPEL instructions linked above), apt
(using the PPA instructions linked above), or pip install ansible
.
Design Principles
- Have a dead simple setup process and a minimal learning curve
- Manage machines very quickly and in parallel
- Avoid custom-agents and additional open ports, be agentless by leveraging the existing SSH daemon
- Describe infrastructure in a language that is both machine and human friendly
- Focus on security and easy auditability/review/rewriting of content
- Manage new remote machines instantly, without bootstrapping any software
- 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 Community Information 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
vsgit 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. - Users list: ansible-project
- Development list: ansible-devel
- Announcement list: ansible-announce - read only
- irc.freenode.net: #ansible
Branch Info
- Releases are named after Led Zeppelin songs. (Releases prior to 2.0 were named after Van Halen songs.)
- The devel branch corresponds to the release actively under development.
- For releases 1.8 - 2.2, modules are kept in different repos, you'll want to follow core and extras
- Various release-X.Y branches exist for previous releases.
- We'd love to have your contributions, read Community Information for notes on how to get started.
Authors
Ansible was created by Michael DeHaan (michael.dehaan/gmail/com) and has contributions from over 1000 users (and growing). Thanks everyone!
Ansible is sponsored by Ansible, Inc
Licence
GNU Click on the Link to see the full text.