OpenStack SIGs

The OpenStack SIGs (Special Interest Groups) are a form of working group in OpenStack that is not directly responsible for producing a part of the OpenStack software release. As such, they do not require the same level of accountability that project teams do.

SIGs are a good match for an activity that centers around a topic or practice that spans all the community (developers, operators, end users…), by forming a guild of people with a shared interest.

SIGs can own code repositories and produce software (independently of the OpenStack software release itself). Contributions to a SIG grant voting rights for the Technical Committee elections, in the same way contributing to an OpenStack project team does.

Name	Status	Chairs	Scope
API	advisory	Dmitry Tantsur (dtantsur, dtantsur@protonmail.com) Michael McCune (elmiko, msm@redhat.com)	Formerly known as the API-WG, the API SIG scope is to improve the developer experience of API users by converging the OpenStack API to a consistent and pragmatic RESTful design. The working group creates guidelines that all OpenStack projects should follow for new development, and promotes convergence of new APIs and future versions of existing APIs.
Ansible	active	Sagi Shnaidman (sshnaidm, sshnaidm@redhat.com) Kevin Carter (cloudnull, kecarter@redhat.com)	Ansible is an orchestration tool that is becoming increasingly common in usage across many parts of OpenStack. There are a few deployment projects that are using it, alongside many of our CI systems. This SIG exists to help create a colloborative space between different interested parties to share Ansible code under one group. It is also responsible of the OpenStack namespace on Ansible’s galaxy.
Automation	advisory	Rico Lin (ricolin, ricolin@ricolky.com)	Automation SIG scope is to improve experience on develop, operate, and use all automation (includes auto-scaling and self-healing) and its related features (like metering, cluster schedule, life cycle management) and to coordinate across projects and communities (like k8s cluster autoscaling on OpenStack). Also provide a central place to put tests, documentations, and even common libraries for auto-scaling and self-healing features.
Bare Metal	active	Arne Wiebalck (arne_wiebalck, arne.wiebalck@cern.ch) Dmitry Tantsur (dtantsur, dtantsur@protonmail.com)	The scope of the Bare Metal Sig is to promote the development and use of Ironic and other OpenStack bare metal software. This will include marketing efforts like case studies of Ironic clusters in industry and academia, supporting integration of Ironic with projects like Airship and the Kubernetes Cluster API, coordinating presentations for industry events, developing documentation and tutorials, gathering feedback from the community on usage and feature gaps, and other broader community-facing efforts to encourage the adoption of Ironic as a bare-metal management tool.
Cloud Research	active	Mohamed Elsakhawy (melsakhawy, m2elsakha@gmail.com)	The Cloud Research SIG aims to bridge the gap between Academic Research in Cloud Computing and Technology projects within OpenStack. The group’s purpose is to establish a collaboration space for Cloud researchers to discuss advancements in Cloud research and methodologies and to implement them in OpenStack. The group is also a communication space for researchers looking for guidance on how to evaluate their research work ( e.g., placement algorithms, model-free frameworks…etc.) in Openstack.
Edge Computing	active	Ildiko Vancsa (ildikov, ildiko@openstack.org) Gergely Csatari (csatari, gergely.csatari@nokia.com)	The Edge Computing group is a OSF-level special interest group focused on defining infrastructure systems needed to support applications distributed over a broad geographic area, with potentially thousands of sites, located as close as possible to discrete data sources, physical elements or end users.
First Contact	active	Kendall Nelson (diablo_rojo, knelson@openstack.org) Matt Oliver (mattoliverau, matt@oliver.net.au)	To provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community.
Hardware Vendor	active	Sean McGinnis (smcginnis, sean.mcginnis@gmail.com) Jay Bryant (jungleboyj, jsbryant@electronicjungle.net)	The goals of this SIG are to provide a place where vendors, and those interested in vendor specific things like drivers and supporting libs, can work together and collaborate openly to enable OpenStack services to integrate and work well on all hardware platforms.
K8s	advisory	Feilong Wang (flwang, feilong@catalyst.net.nz) Kendall Nelson (diablo_rojo, kennelson11@gmail.com)	Community-local counterpart to the k8s-sig-openstack group, focused on cross community communication and collaboration. Where k8s-sig-openstack spends a good deal of time managing upstream provider code, sig-k8s would likewise be focused on code to support and enable K8s deployments within the OpenStack community. This SIG is directly intertwined with k8s-sig-openstack within the Kubernetes community, with the same sig leadership and meetings.
Large Scale	active	Belmiro Moreira (belmoreira, belmiro.moreira@cern.ch) Pengju Jiao (jiaopengju, jiaopengju@cmss.chinamobile.com) Thierry Carrez (ttx, thierry@openstack.org)	The aim of the group is to facilitate running OpenStack at large scale, and help address some of the limitations operators encounter in large OpenStack clusters.
Multi-Arch	active	Rico Lin (ricolin, ricolin@ricolky.com) Seongsoo Cho (seongsoocho, ppiyakk2@printf.kr)	This SIG tracks and encourages efforts towards better support for OpenStack on CPU architectures other than x86_64. This includes providing documents, building test jobs, tracking issues, and building ecosystem for multiple architectures.
Operation Docs and Tooling	active	Chris Morgan (mihalis68, mihalis68@gmail.com) Sean McGinnis (smcginnis, sean.mcginnis@gmail.com)	The Operation Docs and Tooling SIG is for those interested in operator guide documentation and tools, scripts, and other code to make running OpenStack clouds easier and more efficient.
Packaging	active	Javier Peña (jpena, jpena@redhat.com) Dirk Mueller (dirk, dirk@dmllr.de)	To make OpenStack easier to update and consume by operators and provide tooling to package all OpenStack projects directly for (at first) all RPM based distributions.
PowerVMStacker	active	Ramakrishnan Ramasubbu (SriRamaSan, RR00462393@techmahindra.com) Anurag Mahanto (anuragmahanto67, Anurag.Mahanto@TechMahindra.com)	The scope of the PowerVMStacker is to provide OpenStack support for the POWER CPU architecture on the PowerVM hypervisor. This enables support of Linux, AIX and IBM i for PowerVM systems. There are currently three supported components of the PowerVM driver - nova-powervm – Support for Nova use cases. ceilometer-powervm – Gathers instance/VM statistics. networking-powervm – An optional Neutron ML2 agent that supports PowerVM Shared Ethernet Adapters (SEAs). Users should utilize this if their environment requires Shared Ethernet. However, they may also use the standard Open vSwitch agent from the Neutron project to support advanced functions such as Security Groups, Quality of Service (QoS), overlay networks (VXLANs) and more.
Public Cloud	advisory	Tobias Rydberg (tobberydberg, tobias.rydberg@citynetwork.eu) Howard Huang (zhipeng, huangzhipeng@huawei.com)	The aim of this sig is to represent the interests of the OpenStack public cloud provider community, and to further adoption of OpenStack public cloud usage.
Resource Management	forming	Howard Huang (zhipeng, huangzhipeng@huawei.com)	The Resource Management SIG provides a gathering of similar interested parties and establish an official channel cross different communities, such as Kubernetes (Resource Management WG), Apache Mesos, Open Compute Project and so forth, to focus on alignment of resource management related functionalities.
Scientific	active	Blair Bethwaite (b1airo, blair.bethwaite@gmail.com) Stig Telfer (oneswig, stig.openstack@telfer.org) Martial Michel (martial_, martialmichel@datamachines.io)	The Scientific SIG (formerly Scientific Working Group) is dedicated to representing and advancing the use-cases and needs of research and high-performance computing atop OpenStack. It’s also a great forum for cross-institutional collaboration. If you are (or would like to) run OpenStack to support researchers/scientists/academics and/or HPC/HTC, then please join!
Security	active	Jeremy Stanley (fungi, fungi@yuggoth.org)	The Security SIG (formerly Security Project) responsibilities include aiming to improve overall security of the various OpenStack projects, maintaining the list of security notices in OpenStack, and ensuring that security incidents are handled in a coordinated fashion. This involves maintaining the OSSN (OpenStack Security Notes) and OSSA (OpenStack Security Advisories), which are primarily handled under the OpenStack Vulnerability Managment Team (VMT), a more autonomous subgroup of the Security SIG.
Stable Maintenance	advisory	Elõd Illés (elod, elod.illes@est.tech)	Defining, enforcing and accompanying project teams in the application of a common stable branch policy. Keeping CI working on stable branches. Creating and improving related tooling and automation.
Testing and Collaboration Tools	active	Jeremy Stanley (fungi, fungi@yuggoth.org)	The Testing and Collaboration Tools (TaCT) SIG maintains, in cooperation with the OpenDev project, the tooling and infrastructure needed to support the development process and testing of the OpenStack project.
i18n	active	Ian Y. Choi (ianychoi, ianyrchoi@gmail.com)	To make OpenStack ubiquitously accessible to people of all language backgrounds.

• Guidelines for OpenStack SIGs (Special Interest Groups)
  • SIGs lifecycle
    • Before creating a SIG
    • Creating a SIG
    • Keeping SIG status up to date
      • forming
      • active
      • advisory
      • unknown
      • completed
      • archived
    • Retiring a SIG
      • Before retiring
      • Retire a mission completed SIG
      • Retire an archived SIG
  • Best practices for running a SIG
    • SIG chairs role
    • SIG communications
      • Mailing List
      • IRC
      • IRC meetings
      • Post SIG news regularly
      • Attend events
    • SIG resources
      • Git repositories
      • Doc repository
      • StoryBoard task tracker

Retired SIGs

Archived SIGs

These SIGs are retired but have not yet completed their mission.

Name	Status	Chairs	Scope	Reason
Containers	archived	Jean-Philippe Evrard (evrardjp, jean-philippe@evrard.me)	The scope of the Containers SIG is to share practices for the build, deploy, and operate of OpenStack using application containers. This is not another deployment tool of containers. Instead, this SIG should have as members people from the different projects in the business of dealing with OpenStack in application containers. The participants should be interested in container building, willing to share their practices, and/or define common practices for use within all OpenStack projects. One example of the deliverables of the SIG would be a common series of “rules” for the bindep files relevant for container image building. These rules would then be applied consistenty across all the OpenStack projects, but also maintained over time by this group. Another example of common ground would be sharing how deployment projects are writing their container “check probes”, and figure out what can be re-used. In other words, defining together what are application containers “readiness” and “aliveness” for each service project.	There’s currently no one available to drive Containers SIG and this SIG’s previous status is still forming and no repository associated. Mailing List notification for retirement discussion can be found in http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021297.html

Completed SIGs

These SIGs are retired and have completed their mission.

Name	Status	Chairs	Scope	Reason
Technical Writing	completed	Stephen Finucane (stephenfin, sfinucan@redhat.com)	The technical writing SIG provides guidance, assistance, tooling, and style guides enabling OpenStack project teams to produce consistent, accurate, and high-quality documentation.	The technical writing SIG has provided the guidelines and tooling to move the documentation ownership to the projects. Now we have significantly less amount of work under this SIG and having fewer or maintainer for this SIG in the Yoga cycle, we decided to merge this SIG into the Technical Committee. Contact OpenStack Technical Committee for any query related to this SIG.
Upgrade	completed	James Page (jamespage, james.page@canonical.com) Lujin Luo (lujinluo, luo.lujin@jp.fujitsu.com)	The objective of the Upgrade SIG is to improve the overall upgrade process for OpenStack Clouds, covering both offline ‘fast-forward’ upgrades and online ‘rolling’ upgrades, by providing a forum for cross-project collaboration between operators and developers to document and codify best practice for upgrading OpenStack.	OpenStack is considered valid for both offline ‘fast-forward’ upgrades and online ‘rolling’ upgrades. Therefore, we consider mission for Upgrade SIG is completed.