initial commit

.gitignore

@@ -0,0 +1,4 @@
+*.py[co]
+*.swp
+*.swo
+*.bak

.travis.yml

@@ -0,0 +1,29 @@
+---
+language: python
+python: "2.7"
+
+# Use the new container infrastructure
+sudo: false
+
+# Install ansible
+addons:
+  apt:
+    packages:
+    - python-pip
+
+install:
+  # Install ansible
+  - pip install ansible
+
+  # Check ansible version
+  - ansible --version
+
+  # Create ansible.cfg with correct roles_path
+  - printf '[defaults]\nroles_path=../' >ansible.cfg
+
+script:
+  # Basic role syntax check
+  - ansible-playbook tests/test.yml -i tests/inventory --syntax-check
+
+notifications:
+  webhooks: https://galaxy.ansible.com/api/v1/notifications/

CONTRIBUTING.md

@@ -0,0 +1,79 @@
+# Developer Guide
+This role is developed and mantained by the Ansible Network Working Group.
+Contributions to this role are welcomed.  This document will provide inviduals
+with information about how to contribute to the further development of this
+role.
+
+## Contributing
+There are many ways you can contribute to this role.  Adding new artifacts such
+as modules and plugins, testing and/or reviewing and updating documentation.
+
+### Adding support for a new platform
+To add support for a new platform to this role, there are a couple of things
+that need to be done.
+
+1) Create the module for the platform specific implementation in Ansible.  The
+module can be contributed directly to Ansible core, distributed through Ansible
+Galaxy or added to this role.
+
+2) Optional Steps
+
+a) If adding the module code directly to this role, add the module
+to ```library/```
+
+b) If the new platform module is distributed through another Galaxy
+role, please update [README](README.md) Dependencies section to include the 
+name of the Galaxy role that includes the module.
+
+3) Once the module has been created, the add a new task in ```tasks/``` for the
+specific platform to be supported.  Use any of the existing platform
+implementations as a guide.
+
+4) (Optional) If a configuration parameter is not supported, then the
+implementation in tasks should detect that and provide a warning message.
+
+5) Update the ```meta/main.yaml``` file to add the newly provided platform to
+the ```platforms``` meta data.
+
+### Adding platform specific arguments
+Sometimes there is a need to add platform specific arguments to a role for use
+by a platform specific module.  This can be accomplished by adding the adding
+the arguments under a platform specific key.  
+
+Note: It is the responsibility of the task writer to handle the implementation
+of the platform specific arguments.  
+
+Here is an example that implements a platform specific argument:
+
+```
+tasks:
+  - name: configure network device resource
+    include_role:
+      name: net_system
+    vars:
+      resource:
+        foo: bar
+      ios:
+        foo: baz
+```
+
+### Adding documentation for a platform specific implementation
+While not required, there are times when providing implementation nodes are
+advantageous to instructing the playbook writer how to implement platform
+specific arguments.  In order to provide platform specific documentation,
+create a file in the docs directory using Github Markdown.  The file name
+should be the platform name. 
+
+For instance, let's assume we want to create implementation nodes for a
+fictitious platform call `foo`.  Create a new file in docs/ called `foo.md` and
+then add a link to [README](README.md) pointing to `docs/foo.md` in the `PLATFORM
+NOTES` section.
+
+## Bug Reporting
+If you have found a bug in the with the current role please open a [Github
+issue](../../issues)  
+
+## Contact
+* [#ansible-network IRC channel](https://webchat.freenode.net/?channels=ansible-network) on Freenode.net
+
+