330 lines
12 KiB
YAML
330 lines
12 KiB
YAML
---
|
||
Ansible:
|
||
chairs:
|
||
- name: Mohammed Naser
|
||
irc: mnaser
|
||
email: mnaser@vexxhost.com
|
||
- name: Kevin Carter
|
||
irc: cloudnull
|
||
email: kecarter@redhat.com
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://etherpad.openstack.org/p/ansible-sig
|
||
|
||
API:
|
||
chairs:
|
||
- name: Dmitry Tantsur
|
||
irc: dtantsur
|
||
email: dtantsur@protonmail.com
|
||
- name: Michael McCune
|
||
irc: elmiko
|
||
email: msm@redhat.com
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://wiki.openstack.org/wiki/API_SIG
|
||
|
||
Auto-scaling:
|
||
chairs:
|
||
- name: Rico Lin
|
||
irc: ricolin
|
||
email: rico.lin.guanyu@gmail.com
|
||
- name: Duc Truong
|
||
irc: dtruong
|
||
email: duc.openstack@gmail.com
|
||
- name: Zane Bitter
|
||
irc: zaneb
|
||
email: zbitter@redhat.com
|
||
scope: >
|
||
Auto-scaling SIG scope is to improve experience on develop, operate, and use
|
||
autoscaling 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
|
||
features.
|
||
status: active
|
||
url: https://docs.openstack.org/auto-scaling-sig
|
||
|
||
Bare Metal:
|
||
chairs:
|
||
- name: Arne Wiebalck
|
||
irc: arne_wiebalck
|
||
email: arne.wiebalck@cern.ch
|
||
- name: Dmitry Tantsur
|
||
irc: dtantsur
|
||
email: dtantsur@protonmail.com
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://etherpad.openstack.org/p/bare-metal-sig
|
||
|
||
Containers:
|
||
chairs:
|
||
- name: Jean-Philippe Evrard
|
||
irc: evrardjp
|
||
email: jean-philippe@evrard.me
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://etherpad.openstack.org/p/containers-sig
|
||
|
||
Edge Computing:
|
||
chairs:
|
||
- name: Ildiko Vancsa
|
||
irc: ildikov
|
||
email: ildiko@openstack.org
|
||
- name: Gergely Csatari
|
||
irc: csatari
|
||
email: gergely.csatari@nokia.com
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://wiki.openstack.org/wiki/Edge_Computing_Group
|
||
|
||
Extended Maintenance:
|
||
chairs:
|
||
- name: Tony Breeds
|
||
irc: tonyb
|
||
email: tony@bakeyournoodle.com
|
||
- name: Elõd Illés
|
||
irc: elod
|
||
email: elod.illes@est.tech
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://docs.openstack.org/project-team-guide/stable-branches.html
|
||
|
||
First Contact:
|
||
chairs:
|
||
- name: Kendall Nelson
|
||
irc: diablo_rojo
|
||
email: knelson@openstack.org
|
||
- name: Matt Oliver
|
||
irc: mattoliverau
|
||
email: matt@oliver.net.au
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://wiki.openstack.org/wiki/First_Contact_SIG
|
||
|
||
K8s:
|
||
chairs:
|
||
- name: Chris Hoge
|
||
irc: hogepodge
|
||
email: chris@openstack.org
|
||
- name: David Lyle
|
||
irc: david-lyle
|
||
email: dklyle0@gmail.com
|
||
- name: Robert Morse
|
||
irc: rjmorse
|
||
email: robert.morse@ticketmaster.com
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://github.com/kubernetes/community/tree/master/sig-openstack
|
||
|
||
Meta:
|
||
chairs:
|
||
- name: Amy Marrich
|
||
irc: spotz
|
||
email: amy@demarco.com
|
||
- name: Rico Lin
|
||
irc: ricolin
|
||
email: rico.lin.guanyu@gmail.com
|
||
scope: >
|
||
A SIG for SIGs so to speak. A SIG to discuss OpenStack SIGs themselves,
|
||
to encourage workgroups to become SIGs, accompany them along the way,
|
||
give them tools and processes to be efficient. More generally, this SIG
|
||
will discuss how to best close the loop between users and developers of
|
||
OpenStack.
|
||
status: active
|
||
url: https://governance.openstack.org/sigs/
|
||
|
||
Operation Docs:
|
||
chairs:
|
||
- name: Chris Morgan
|
||
irc: mihalis68
|
||
email: mihalis68@gmail.com
|
||
- name: Sean McGinnis
|
||
irc: smcginnis
|
||
email: sean.mcginnis@gmail.com
|
||
scope: >
|
||
The Operation Docs SIG is for those interested in operator guide
|
||
documentation to make running OpenStack clouds easier and more efficient.
|
||
status: active
|
||
url: https://wiki.openstack.org/wiki/Operation_Docs_SIG
|
||
|
||
PowerVMStacker:
|
||
chairs:
|
||
- name: Ramakrishnan Ramasubbu
|
||
irc: SriRamaSan
|
||
email: RR00462393@techmahindra.com
|
||
- name: Anurag Mahanto
|
||
irc: anuragmahanto67
|
||
email: Anurag.Mahanto@TechMahindra.com
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://wiki.openstack.org/wiki/PowerVM
|
||
|
||
Public Cloud:
|
||
chairs:
|
||
- name: Tobias Rydberg
|
||
irc: tobberydberg
|
||
email: tobias.rydberg@citynetwork.eu
|
||
- name: Howard Huang
|
||
irc: zhipeng
|
||
email: huangzhipeng@huawei.com
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://wiki.openstack.org/wiki/PublicCloudSIG
|
||
|
||
Resource Management:
|
||
chairs:
|
||
- name: Howard Huang
|
||
irc: zhipeng
|
||
email: huangzhipeng@huawei.com
|
||
- name: Chris Dent
|
||
irc: cdent
|
||
email: cdent+os@anticdent.org
|
||
- name: Jay Pipes
|
||
irc: jaypipes
|
||
email: jaypipes@gmail.com
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://wiki.openstack.org/wiki/Res_Mgmt_SIG
|
||
|
||
Scientific:
|
||
chairs:
|
||
- name: Blair Bethwaite
|
||
irc: b1airo
|
||
email: blair.bethwaite@gmail.com
|
||
- name: Stig Telfer
|
||
irc: oneswig
|
||
email: stig.openstack@telfer.org
|
||
- name: Martial Michel
|
||
irc: martial_
|
||
email: martialmichel@datamachines.io
|
||
scope: >
|
||
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!
|
||
status: active
|
||
url: https://wiki.openstack.org/wiki/Scientific_SIG
|
||
|
||
Security:
|
||
chairs:
|
||
- name: Gage Hugo
|
||
irc: gagehugo
|
||
email: gagehugo@gmail.com
|
||
scope: >
|
||
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.
|
||
status: active
|
||
url: https://wiki.openstack.org/wiki/Security-SIG
|
||
|
||
Self-healing:
|
||
chairs:
|
||
- name: Adam Spiers
|
||
irc: aspiers
|
||
email: aspiers@suse.com
|
||
- name: Eric Kao
|
||
irc: ekcs
|
||
email: ekcs.openstack@gmail.com
|
||
scope: >
|
||
Coordinate the use and development of several OpenStack projects which
|
||
can be combined in various ways to manage OpenStack infrastructure in a
|
||
policy-driven fashion, reacting to failures and other events by
|
||
automatically healing and optimising services.
|
||
status: active
|
||
url: https://wiki.openstack.org/wiki/Self-healing_SIG
|
||
|
||
Technical Writing:
|
||
chairs:
|
||
- name: Alexandra Settle
|
||
irc: asettle
|
||
email: asettle@suse.com
|
||
- name: Stephen Finucane
|
||
irc: stephenfin
|
||
email: sfinucan@redhat.com
|
||
scope: >
|
||
The technical writing SIG provides guidance, assistance, tooling, and style
|
||
guides enabling OpenStack project teams to produce consistent, accurate,
|
||
and high-quality documentation.
|
||
url: https://wiki.openstack.org/wiki/Documentation , https://docs.openstack.org/
|