No description
6fe0215c8f
* Add VnicProfileMapping to register VM Add vnic profile mappings to be supported in vm registration * Add VnicProfileMapping to register template Add vnic profile mappings to be supported in template registration * Add reassign bad macs to register VM Add reassign bad macs to be supported in vm registration. * Add additional mappings params for VM registration As part of the effort to support DR with oVirt the "Register" operation is being added with a new mapping parameter that describes the configuration of the registration. The idea of supporting DR site to site in oVirt is to have 2 active setups using storage replication between the primary setup and the secondary setup. Both setups will have active DCs, clusters, and hosts, although those will not be identical. The user can define a mapping which will be used to recover its setup. Each mapping can be used to map any VM's attribute stored in the OVF with its correlated entity. For example, there could be a primary setup with a VM configured on cluster A. We also keep an active secondary setup which only have cluster B. Cluster B is compatible for that VM and in case of a DR scenario theoretically the storage domain can be imported to the secondary setup and the use can register the VM to cluster B. In that case, we can automate the recovery process by defining a cluster mapping, so once the entity will be registered its OVF will indicate it belongs to cluster A but the mapping which will be sent will indicate that cluster B should be valid for every thing that is configured on cluster A. The engine should do the switch, and register the VM to cluster B in the secondary site. Cluster mapping is just one example. The following list describes the different mappings which were introduced: LUN mapping Role mapping Permissions mapping Affinity group mapping Affinity label mapping Each mapping will be used for its specific OVF's data once the register operation will take place in the engine. * Add additional mappings params for Template registration As part of the effort to support DR with oVirt the "Register" operation is being added with a new mapping parameter that describes the configuration of the registration. The idea of supporting DR site to site in oVirt is to have 2 active setups using storage replication between the primary setup and the secondary setup. Both setups will have active DCs, clusters, and hosts, although those will not be identical. The user can define a mapping which will be used to recover its setup. Each mapping can be used to map any Template's attribute stored in the OVF with its correlated entity. For example, there could be a primary setup with a Template configured on cluster A. We also keep an active secondary setup which only have cluster B. Cluster B is compatible for that Template and in case of a DR scenario theoretically the storage domain can be imported to the secondary setup and the use can register the Template to cluster B. In that case, we can automate the recovery process by defining a cluster mapping, so once the entity will be registered its OVF will indicate it belongs to cluster A but the mapping which will be sent will indicate that cluster B should be valid for every thing that is configured on cluster A. The engine should do the switch, and register the Template to cluster B in the secondary site. Cluster mapping is just one example. The following list describes the different mappings which were introduced: Role mapping Permissions mapping Each mapping will be used for its specific OVF's data once the register operation will take place in the engine. * Add support for update OVF store Add support for task of update OVF store in a storage domain. |
||
|---|---|---|
| .github | ||
| bin | ||
| contrib | ||
| docs | ||
| examples | ||
| hacking | ||
| lib/ansible | ||
| licenses | ||
| packaging | ||
| test | ||
| ticket_stubs | ||
| .coveragerc | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| .yamllint | ||
| ansible-core-sitemap.xml | ||
| CHANGELOG.md | ||
| CODING_GUIDELINES.md | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| docsite_requirements.txt | ||
| Makefile | ||
| MANIFEST.in | ||
| MODULE_GUIDELINES.md | ||
| README.md | ||
| RELEASES.txt | ||
| requirements.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/
You can find installation instructions here for a variety of platforms. Most users should probably install a released version of Ansible from pip, a package manager or our release repository. Officially supported builds of Ansible are also available. Some power users run directly from the development branch - while significant efforts are made to ensure that devel is reasonably stable, you're more likely to encounter breaking changes when running Ansible this way.
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 rebasevsgit mergefor 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.
- 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
License
GNU General Public License v3.0
See COPYING to see the full text.