Ansible SIG

Ansible SIG
Status: Active

Description: OpenStack's Ansible SIG is a community of practice and collaboration for developers, operators, and end users of OpenStack with Ansible. Its purpose is to facilitate cross-project collaboration among Ansible-related OpenStack projects and efforts, and to provide a broader feedback loop between operators and users of Ansible in OpenStack clouds and developers of Ansible-related tools for deploying, operating, and managing services in OpenStack Clouds. The Ansible SIG also facilitates awareness of improvements, project timelines, or issues relating to OpenStack in the Ansible project community, and aspires to grow the collective pool of contributors across both open source projects.

Goals

 * Provide a unified source of Ansible + OpenStack related information for developers, operators, and consumers of OpenStack cloud infrastructure
 * Build / consolidate knowledge around best practices and existing roles or playbooks for operators and users
 * Grow the pool of maintainers and knowledge around development for Ansible's OpenStack modules (and the Shade library) and better understand how they are used by operators / end users

Audience

 * Users of Ansible to deploy, manage, and/or consume OpenStack and OpenStack services
 * Contributors and/or users of various Ansible-related OpenStack projects, OpenStack modules in Ansible, and/or Ansible roles for use in or with OpenStack
 * Anyone curious about using Ansible and OpenStack together

SIG Chairs

 * Mohammed Naser (mnaser)
 * Kevin Carter (cloudnull)

Community Infrastructure

 * Wiki: https://wiki.openstack.org/wiki/Ansible_SIG
 * Etherpad: https://etherpad.openstack.org/p/ansible-sig
 * Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss; [ansible-sig] for the subject tag
 * IRC: #openstack-ansible-sig on freenode
 * Meetings: TBD

Other notes
This SIG is the same group as the OpenStack Working Group in the Ansible community. Most of the community-facilitating infrastructure / information will live in the OpenStack community space; however, pointers from one group to the other will be made as needed for clarity / necessity.