No description
Find a file
dteach ca56a248d8 junos_facts: Add Hardware facts. (#30304)
* Add Routing Engine Facts

 - Map routing engine output information to routing_engines facts dict.
 - Add fact 'has_2RE', which is a quick way to determine how many REs
   the chassis has.

* Fix a typo

* Fix more typos

* Add slot number to routing_engine dict

* Add facts about the installed chassis modules

* Fix typo

* Fixed another typo

* Fix Path

* Change path again.

* More Typos

* Add some deubgging

* Add additional information for hardware components.

 - Return information about the Routing Engines.
 - Return a fact to easily determine if the device
   has two routing engines.
 - Return information about the hardware modules.

* Addressed pep8 stardard failures.

* Add unit test fixtures.

* Rename fixture.

* Fix unit test failures.

 - Rename the fixture file to what the unit test expects.
 - Strip out junos namespace attributes.
Rename file to match what the unit test expects.

* Scrubbed the routing engine serial numbers.

* Add unit test facts for new tests.

 - Add unit test for ansible_net_routing_engines fact
 - Add unit test for ansible_net_modules fact
 - Add unit test for ansible_net_has_2RE

* Fixed spacing.
2017-09-20 12:43:07 +05:30
.github Remove rabbitmq maintainer. (#30531) 2017-09-18 20:03:32 -04:00
bin nicer error on bad ansible config (#30461) 2017-09-19 10:50:28 -04:00
contrib Enable more pylint rules and fix reported issues. (#30539) 2017-09-18 23:20:32 -07:00
docs added missing feature info (#30560) 2017-09-19 17:43:15 -04:00
examples fixed typo 2017-08-29 11:49:29 -04:00
hacking Allow AWS image and snapshot creation/deletion 2017-09-19 23:12:50 -07:00
lib/ansible junos_facts: Add Hardware facts. (#30304) 2017-09-20 12:43:07 +05:30
packaging Set the release date. 2017-09-18 19:55:31 -07:00
test junos_facts: Add Hardware facts. (#30304) 2017-09-20 12:43:07 +05:30
ticket_stubs
.coveragerc
.gitattributes
.gitignore Generate plugin rst (#28901) 2017-09-19 11:14:27 -04:00
.gitmodules
.mailmap
.yamllint
ansible-core-sitemap.xml
CHANGELOG.md added missing feature info (#30560) 2017-09-19 17:43:15 -04:00
CODING_GUIDELINES.md
CONTRIBUTING.md
COPYING
docsite_requirements.txt
Makefile Fix make clean to remove test reports correctly 2017-09-18 16:49:16 -07:00
MANIFEST.in powershell setup fixes (#27516) 2017-07-31 12:16:26 -07:00
MODULE_GUIDELINES.md Update link to MAINTAINERS.txt 2017-09-14 16:21:00 +02:00
README.md devel usage README update (#30369) 2017-09-14 10:48:58 -07:00
RELEASES.txt Use a more convenient and standard date format 2017-09-14 16:12:57 +02:00
requirements.txt
ROADMAP.rst docs: fix community meetings link (#27264) 2017-07-25 09:23:01 -04:00
setup.py On Py3, nonexistent files raise OSError (#28899) 2017-08-31 17:47:26 -04:00
shippable.yml Update Windows CI groups from 2 to 3. 2017-09-14 23:54:28 -07:00
tox.ini
VERSION Bump the versions now that devel is 2.5 2017-09-06 13:13:57 -07:00

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/

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 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.
  • 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.