"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "docs/docsite/rst/network/getting_started/intermediate_concepts.rst" between
ansible-2.7.6.tar.gz and ansible-2.7.7.tar.gz

About: Ansible is a platform for configuring and managing computers combining multi-node software deployment, ad hoc task execution, and configuration management.

intermediate_concepts.rst  (ansible-2.7.6):intermediate_concepts.rst  (ansible-2.7.7)
****************************************** *****************
Beyond the Basics Beyond the basics
****************************************** *****************
This page introduces some concepts that help you manage your Ansible workflow: r oles, directory structure, and source control. Like the Basic Concepts at the be ginning of this guide, these intermediate concepts are common to all uses of Ans ible. This page also offers resources for learning more. This page introduces some concepts that help you manage your Ansible workflow wi th directory structure and source control. Like the Basic Concepts at the beginn ing of this guide, these intermediate concepts are common to all uses of Ansible .
.. contents:: Topics .. contents::
:local:
Beyond Playbooks: Moving Tasks and Variables into Roles A typical Ansible filetree
================================================================================ ==========================
Roles are sets of Ansible defaults, files, tasks, templates, variables, and othe
r Ansible components that work together. As you saw on the Working with Playbook
s page, moving from a command to a playbook makes it easy to run multiple tasks
and repeat the same tasks in the same order. Moving from a playbook to a role ma
kes it even easier to reuse and share your ordered tasks. For more details, see
the :doc:`documentation on roles<../../user_guide/playbooks_reuse_roles>`. You c
an also look at :doc:`Ansible Galaxy<../../reference_appendices/galaxy>`, which
lets you share your roles and use others' roles, either directly or as inspirati
on.
A Typical Ansible Filetree
================================================================================
Ansible expects to find certain files in certain places. As you expand your inve ntory and create and run more network playbooks, keep your files organized in yo ur working Ansible project directory like this: Ansible expects to find certain files in certain places. As you expand your inve ntory and create and run more network playbooks, keep your files organized in yo ur working Ansible project directory like this:
.. code-block:: console .. code-block:: console
. .
├── backup ├── backup
│   ├── vyos.example.net_config.2018-02-08@11:10:15 │   ├── vyos.example.net_config.2018-02-08@11:10:15
│   ├── vyos.example.net_config.2018-02-12@08:22:41 │   ├── vyos.example.net_config.2018-02-12@08:22:41
├── first_playbook.yml ├── first_playbook.yml
skipping to change at line 38 skipping to change at line 34
│   ├── vyos.yml │   ├── vyos.yml
│   └── eos.yml │   └── eos.yml
├── roles ├── roles
│   ├── static_route │   ├── static_route
│   └── system │   └── system
├── second_playbook.yml ├── second_playbook.yml
└── third_playbook.yml └── third_playbook.yml
The ``backup`` directory and the files in it get created when you run modules li ke ``vyos_config`` with the ``backup: yes`` parameter. The ``backup`` directory and the files in it get created when you run modules li ke ``vyos_config`` with the ``backup: yes`` parameter.
Tracking Changes to Inventory and Playbooks: Source Control with Git Tracking changes to inventory and playbooks: source control with git
================================================================================ ====================================================================
As you expand your inventory, roles and playbooks, you should place your Ansible projects under source control. We recommend ``git`` for source control. ``git`` provides an audit trail, letting you track changes, roll back mistakes, view hi story and share the workload of managing, maintaining and expanding your Ansible ecosystem. There are plenty of tutorials and guides to using ``git`` available. As you expand your inventory, roles and playbooks, you should place your Ansible projects under source control. We recommend ``git`` for source control. ``git`` provides an audit trail, letting you track changes, roll back mistakes, view hi story and share the workload of managing, maintaining and expanding your Ansible ecosystem. There are plenty of tutorials and guides to using ``git`` available.
Resources and Next Steps
================================================================================
Text
Read more about Ansible for Network Automation:
- Network Automation on the `Ansible website <https://www.ansible.com/overview/n
etworking>`_
- Ansible Network `Blog posts <https://www.ansible.com/blog/topic/networks>`_
Events (on Video and in Person)
All sessions at Ansible events are recorded and include many Network-related top
ics (use Filter by Category to view only Network topics). You can also join us f
or future events in your area. See:
- `Recorded AnsibleFests <https://www.ansible.com/resources/videos>`_
- `Recorded AnsibleAutomates <https://www.ansible.com/resources/webinars-trainin
g>`_
- `Upcoming Ansible Events <https://www.ansible.com/community/events>`_ page.
GitHub Repos
Ansible hosts module code, examples, demonstrations, and other content on GitHub
. Anyone with a GitHub account is able to create Pull Requests (PRs) or issues o
n these repos:
- `Network-Automation <https://github.com/network-automation>`_ is an open commu
nity for all things network automation. Have an idea, some playbooks, or roles t
o share? Email ansible-network@redhat.com and we will add you as a contributor t
o the repository.
- `Ansible <https://github.com/ansible/ansible>`_ is the main codebase, includin
g code for network modules
IRC
Join us on Freenode IRC:
- ``#ansible-network`` Freenode channel
 End of changes. 6 change blocks. 
22 lines changed or deleted 10 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)