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
Robin Roth 5464b71561 Zypper repository rewrite (#1990)
* Remove support for ancient zypper versions

Even SLES11 has zypper 1.x.

* zypper_repository: don't silently ignore repo changes

So far when a repo URL changes this got silently ignored (leading to
incorrect package installations) due to this code:

    elif 'already exists. Please use another alias' in stderr:
        changed = False

Removing this reveals that we correctly detect that a repo definition
has changes (via repo_subset) but don't indicate this as change but as a
nonexistent repo. This makes us currenlty bail out silently in the above
statement.

To fix this distinguish between non existent and modified repos and
remove the repo first in case of modifications (since there is no force
option in zypper to overwrite it and 'zypper mr' uses different
arguments).

To do this we have to identify a repo by name, alias or url.

* Don't fail on empty values

This unbreaks deleting repositories

* refactor zypper_repository module

* add properties enabled and priority
* allow changing of one property and correctly report changed
* allow overwrite of multiple repositories by alias and URL
* cleanup of unused code and more structuring

* respect enabled option

* make zypper_repository conform to python2.4

* allow repo deletion only by alias

* check for non-existant url field and use alias instead

* remove empty notes and aliases

* add version_added for priority and overwrite_multiple

* add version requirement on zypper and distribution

* zypper 1.0 is enough and exists

* make suse versions note, not requirement

based on comment by @alxgu
8 years ago
.github Try to avoid module-related tickets in the core Ansible project (#17047) 8 years ago
bin functional updates to ansible-connection (#18574) 8 years ago
contrib Fix auth in collins.py inventory 8 years ago
docs/man Update ansible.1.asciidoc.in (#18464) 8 years ago
docs-api updated devel to 2.3 (#17884) 8 years ago
docsite Fix minor typo in roles doc (#18740) 8 years ago
examples change to ~ instead of $HOME to avoid undefined (#18551) 8 years ago
hacking Update the metadata tool (#18765) 8 years ago
lib/ansible Zypper repository rewrite (#1990) 8 years ago
packaging Updating release versions for release playbook 8 years ago
test add back reverted change to network_cli (#18761) 8 years ago
ticket_stubs Add ticket stub with info on reporting locale info (#16310) 8 years ago
.coveragerc Update coverage exclusions. (#18675) 8 years ago
.gitattributes
.gitignore Initial ansible-test implementation. (#18556) 8 years ago
.gitmodules removed core and extras submodules 8 years ago
.mailmap Add a .mailmap for 'shortlog' (#15588) 9 years ago
.yamllint Lint YAML files under test/ 8 years ago
CHANGELOG.md ansible_playbook_python (#18530) 8 years ago
CODING_GUIDELINES.md Migrate basestring to a python3 compatible type (#17199) 8 years ago
CONTRIBUTING.md Update CONTRIBUTING.md with more recent developments 9 years ago
COPYING
MANIFEST.in
Makefile Clean up shebangs for various files. 8 years ago
README.md Add link to licence file (COPYING) in README (#18521) 8 years ago
RELEASES.txt brought releases up to date 8 years ago
ROADMAP.rst updated devel to 2.3 (#17884) 8 years ago
VERSION Bumping devel version to 2.3.0 8 years ago
ansible-core-sitemap.xml Add debug strategy plugin (#15125) 9 years ago
setup.py Add ansible-connection to scripts in setup.py 8 years ago
shippable.yml Initial ansible-test implementation. (#18556) 8 years ago
tox.ini We've decided that python-3.5 is the minimum python version (#17270) 8 years ago

README.md

PyPI version Build Status

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 decide to go with the development branch, be sure to run git submodule update --init --recursive after doing a checkout.

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 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.
  • 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.
  • As of 1.8, 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.