Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
A
ansible
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
OpenEdx
ansible
Commits
6b433239
Commit
6b433239
authored
Feb 25, 2012
by
Michael DeHaan
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update README.md
parent
a5039eec
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
8 deletions
+23
-8
README.md
+23
-8
No files found.
README.md
View file @
6b433239
...
...
@@ -145,29 +145,44 @@ than "/usr/share/ansible". This means anyone can use Ansible, even without
root permissions.
There is potential for a sizeable community to build
up around the library scripts.
up around the library scripts
, and you can easily write your own
.
M
odules include:
Current m
odules include:
*
command -- runs commands, giving output, return codes, and run time info
*
ping - just returns if the system is up or not
*
facter - retrieves facts about the host OS
*
ohai - similar to facter, but returns structured data
*
copy - add files to remote systems
*
setup - pushes key/value data onto the system for use in templating
*
template - takes a local template file and saves a templated version remotely
Service, package, and user modules, supporting puppet-like ensure semantics
are coming soon.
Playbooks
=========
Playbooks are loosely equivalent to recipes or manifests in most configuration
management or deployment tools and describe a set of operations to run on
a set of hosts. Some tasks can choose to only fire when certain
conditions are true, and if a task in a chain fails the dependent tasks
will not proceed. Playbooks are described in (YAML)
[
http://yaml.org
]
format.
Playbooks are particularly awesome. Playbooks can batch ansible commands
together, and run some commands only when ansible modifies certain higher
level resources -- such as restarting apache when a configuration file is
replaced. They generate detailed reports of what happend on each node.
See examples/playbook.yml for what the syntax looks like.
To run a playbook:
ansible -r playbook.yml
An ansible-playbook CLI command is pending. Until then, remember that when
using playbooks, the pattern and host list options come from the playbook
and are ignored. Other options still apply.
Future plans
============
*
see
TODO.md
*
see
github's issue tracker for what we're thinking about
License
=======
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment