openstack
/
governance-sigs
Code Issues Proposed changes
Content about SIGs on governance.o.o
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
124 Commits
1 Branch
74 KiB
 
Branch: master
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'master'
${ noResults }
governance-sigs/sigs.yaml

387 lines
14 KiB
Raw Permalink Blame History 

  1. ---

  2. Ansible:

  3.   chairs:

  4.     - name: Sagi Shnaidman

  5.       irc: sshnaidm

  6.       email: sshnaidm@redhat.com

  7.     - name: Kevin Carter

  8.       irc: cloudnull

  9.       email: kecarter@redhat.com

  10.   scope: >

  11.     Ansible is an orchestration tool that is becoming increasingly common

  12.     in usage across many parts of OpenStack.  There are a few deployment

  13.     projects that are using it, alongside many of our CI systems.  This

  14.     SIG exists to help create a colloborative space between different

  15.     interested parties to share Ansible code under one group.

  16.     It is also responsible of the OpenStack namespace on Ansible's galaxy.

  17.   status: active

  18.   url: https://wiki.openstack.org/wiki/Ansible_SIG

  19. 

  20. API:

  21.   chairs:

  22.     - name: Dmitry Tantsur

  23.       irc: dtantsur

  24.       email: dtantsur@protonmail.com

  25.     - name: Michael McCune

  26.       irc: elmiko

  27.       email: msm@redhat.com

  28.   scope: >

  29.     Formerly known as the API-WG, the API SIG scope is to improve the developer

  30.     experience of API users by converging the OpenStack API to a consistent and

  31.     pragmatic RESTful design. The working group creates guidelines that all

  32.     OpenStack projects should follow for new development, and promotes

  33.     convergence of new APIs and future versions of existing APIs.

  34.   status: advisory

  35.   url: https://wiki.openstack.org/wiki/API_SIG

  36. 

  37. Automation:

  38.   chairs:

  39.     - name: Rico Lin

  40.       irc: ricolin

  41.       email: rico.lin.guanyu@gmail.com

  42.   scope: >

  43.     Automation SIG scope is to improve experience on develop, operate, and use

  44.     all automation (includes auto-scaling and self-healing) and its related

  45.     features (like metering, cluster schedule, life cycle management) and to

  46.     coordinate across projects and communities (like k8s cluster autoscaling

  47.     on OpenStack). Also provide a central place to put tests, documentations,

  48.     and even common libraries for auto-scaling and self-healing features.

  49.   status: active

  50.   url: https://etherpad.openstack.org/p/Automation

  51. 

  52. Bare Metal:

  53.   chairs:

  54.     - name: Arne Wiebalck

  55.       irc: arne_wiebalck

  56.       email: arne.wiebalck@cern.ch

  57.     - name: Dmitry Tantsur

  58.       irc: dtantsur

  59.       email: dtantsur@protonmail.com

  60.   scope: >

  61.     The scope of the Bare Metal Sig is to promote the development and use

  62.     of Ironic and other OpenStack bare metal software. This will include

  63.     marketing efforts like case studies of Ironic clusters in industry

  64.     and academia, supporting integration of Ironic with projects like

  65.     Airship and the Kubernetes Cluster API, coordinating presentations

  66.     for industry events, developing documentation and tutorials,

  67.     gathering feedback from the community on usage and feature gaps, and

  68.     other broader community-facing efforts to encourage the adoption of

  69.     Ironic as a bare-metal management tool.

  70.   status: active

  71.   url: https://etherpad.openstack.org/p/bare-metal-sig

  72. 

  73. Cloud Research:

  74.   chairs:

  75.     - name: Mohamed Elsakhawy

  76.       irc: melsakhawy

  77.       email: m2elsakha@gmail.com

  78.   scope: >

  79.     The Cloud Research SIG aims to bridge the gap between Academic

  80.     Research in Cloud Computing and Technology projects within OpenStack.

  81.     The group's purpose is to establish a collaboration space for Cloud

  82.     researchers to discuss advancements in Cloud research and methodologies

  83.     and to implement them in OpenStack. The group is also a communication

  84.     space for researchers looking for guidance on how to evaluate their

  85.     research work ( e.g., placement algorithms, model-free frameworks...etc.)

  86.     in Openstack.

  87.   status: forming

  88.   url: https://etherpad.opendev.org/p/cloud-research-sig

  89. 

  90. Containers:

  91.   chairs:

  92.     - name: Jean-Philippe Evrard

  93.       irc: evrardjp

  94.       email: jean-philippe@evrard.me

  95.   scope: >

  96.     The scope of the Containers SIG is to share practices for the

  97.     build, deploy, and operate of OpenStack using application

  98.     containers. This is not another deployment tool of containers.

  99.     Instead, this SIG should have as members people from the

  100.     different projects in the business of dealing with OpenStack

  101.     in application containers. The participants should be

  102.     interested in container building, willing to share their

  103.     practices, and/or define common practices for use within

  104.     all OpenStack projects. One example of the deliverables of

  105.     the SIG would be a common series of "rules" for the bindep

  106.     files relevant for container image building. These rules

  107.     would then be applied consistenty across all the OpenStack

  108.     projects, but also maintained over time by this group.

  109.     Another example of common ground would be sharing how

  110.     deployment projects are writing their container "check

  111.     probes", and figure out what can be re-used. In other words,

  112.     defining together what are application containers "readiness"

  113.     and "aliveness" for each service project.

  114.   status: forming

  115.   url: https://etherpad.openstack.org/p/containers-sig

  116. 

  117. Edge Computing:

  118.   chairs:

  119.     - name: Ildiko Vancsa

  120.       irc: ildikov

  121.       email: ildiko@openstack.org

  122.     - name: Gergely Csatari

  123.       irc: csatari

  124.       email: gergely.csatari@nokia.com

  125.   scope: >

  126.     The Edge Computing group is a OSF-level special interest group focused

  127.     on defining infrastructure systems needed to support applications

  128.     distributed over a broad geographic area, with potentially thousands of

  129.     sites, located as close as possible to discrete data sources, physical

  130.     elements or end users.

  131.   status: active

  132.   url: https://wiki.openstack.org/wiki/Edge_Computing_Group

  133. 

  134. Extended Maintenance:

  135.   chairs:

  136.     - name: Tony Breeds

  137.       irc: tonyb

  138.       email: tony@bakeyournoodle.com

  139.     - name: Elõd Illés

  140.       irc: elod

  141.       email: elod.illes@est.tech

  142.   scope: >

  143.     Defining, enforcing and accompanying project teams in the application

  144.     of a common stable branch policy. Keeping CI working on stable branches.

  145.     Creating and improving related tooling and automation.

  146.   status: advisory

  147.   url: https://docs.openstack.org/project-team-guide/stable-branches.html

  148. 

  149. First Contact:

  150.   chairs:

  151.     - name: Kendall Nelson

  152.       irc: diablo_rojo

  153.       email: knelson@openstack.org

  154.     - name: Matt Oliver

  155.       irc: mattoliverau

  156.       email: matt@oliver.net.au

  157.   scope: >

  158.     To provide a place for new contributors to come for information and advice.

  159.     This group will also analyze and document successful contribution models

  160.     while seeking out and providing information to new members of the community.

  161.   status: active

  162.   url: https://wiki.openstack.org/wiki/First_Contact_SIG

  163. 

  164. Hardware Vendor:

  165.   chairs:

  166.     - name: Sean McGinnis

  167.       irc: smcginnis

  168.       email: sean.mcginnis@gmail.com

  169.     - name: Jay Bryant

  170.       irc: jungleboyj

  171.       email: jsbryant@electronicjungle.net

  172.   scope: >

  173.     The goals of this SIG are to provide a place where vendors, and those

  174.     interested in vendor specific things like drivers and supporting libs,

  175.     can work together and collaborate openly to enable OpenStack services to

  176.     integrate and work well on all hardware platforms.

  177.   status: active

  178.   url: https://wiki.openstack.org/wiki/Hardware_Vendor_SIG

  179. 

  180. i18n:

  181.   chairs:

  182.     - name: Ian Y. Choi

  183.       irc: ianychoi

  184.       email: ianyrchoi@gmail.com

  185.   scope: >

  186.     To make OpenStack ubiquitously accessible to people of

  187.     all language backgrounds.

  188.   status: active

  189.   url: https://wiki.openstack.org/wiki/I18nTeam

  190. 

  191. K8s:

  192.   chairs:

  193.     - name: Chris Hoge

  194.       irc: hogepodge

  195.       email: chris@openstack.org

  196.     - name: David Lyle

  197.       irc: david-lyle

  198.       email: dklyle0@gmail.com

  199.     - name: Robert Morse

  200.       irc: rjmorse

  201.       email: robert.morse@ticketmaster.com

  202.   scope: >

  203.     Community-local counterpart to the k8s-sig-openstack group, focused on

  204.     cross community communication and collaboration. Where k8s-sig-openstack

  205.     spends a good deal of time managing upstream provider code, sig-k8s

  206.     would likewise be focused on code to support and enable K8s deployments

  207.     within the OpenStack community. This SIG is directly intertwined with

  208.     k8s-sig-openstack within the Kubernetes community, with the same sig

  209.     leadership and meetings.

  210.   status: advisory

  211.   url: https://github.com/kubernetes/cloud-provider-openstack/blob/master/README.md

  212. 

  213. Large Scale:

  214.   chairs:

  215.     - name: Belmiro Moreira

  216.       irc: belmoreira

  217.       email: belmiro.moreira@cern.ch

  218.     - name: Pengju Jiao

  219.       irc: jiaopengju

  220.       email: jiaopengju@cmss.chinamobile.com

  221.     - name: Thierry Carrez

  222.       irc: ttx

  223.       email: thierry@openstack.org

  224.   scope: >

  225.     The aim of the group is to facilitate running OpenStack at large scale,

  226.     and help address some of the limitations operators encounter in large

  227.     OpenStack clusters.

  228.   status: active

  229.   url: https://wiki.openstack.org/wiki/Large_Scale_SIG

  230. 

  231. Multi-Arch:

  232.   chairs:

  233.     - name: Rico Lin

  234.       irc: ricolin

  235.       email: rico.lin.guanyu@gmail.com

  236.     - name: Tony Breeds

  237.       irc: tonyb

  238.       email: tony@bakeyournoodle.com

  239.   scope: >

  240.     This SIG tracks and encourages efforts towards better support for OpenStack

  241.     on CPU architectures other than x86_64. This includes providing documents,

  242.     building test jobs, tracking issues, and building ecosystem for multiple

  243.     architectures.

  244.   status: forming

  245.   url: https://etherpad.openstack.org/p/Multi-arch

  246. 

  247. Operation Docs and Tooling:

  248.   chairs:

  249.     - name: Chris Morgan

  250.       irc: mihalis68

  251.       email: mihalis68@gmail.com

  252.     - name: Sean McGinnis

  253.       irc: smcginnis

  254.       email: sean.mcginnis@gmail.com

  255.   scope: >

  256.     The Operation Docs and Tooling SIG is for those interested in operator

  257.     guide documentation and tools, scripts, and other code to make running

  258.     OpenStack clouds easier and more efficient.

  259.   status: active

  260.   url: https://wiki.openstack.org/wiki/Operation_Docs_SIG

  261. 

  262. Packaging:

  263.   chairs:

  264.     - name: Javier Peña

  265.       irc: jpena

  266.       email: jpena@redhat.com

  267.   scope: >

  268.     To make OpenStack easier to update and consume by operators and

  269.     provide tooling to package all OpenStack projects directly for

  270.     (at first) all RPM based distributions.

  271.   status: active

  272.   url: https://wiki.openstack.org/wiki/Rpm-packaging

  273. 

  274. PowerVMStacker:

  275.   chairs:

  276.     - name: Ramakrishnan Ramasubbu

  277.       irc: SriRamaSan

  278.       email: RR00462393@techmahindra.com

  279.     - name: Anurag Mahanto

  280.       irc: anuragmahanto67

  281.       email: Anurag.Mahanto@TechMahindra.com

  282.   scope: >

  283.     The scope of the PowerVMStacker is to provide OpenStack support for the

  284.     POWER CPU architecture on the PowerVM hypervisor.

  285.     This enables support of Linux, AIX and IBM i for PowerVM systems.

  286.     There are currently three supported components of the PowerVM driver -

  287.     nova-powervm – Support for Nova use cases.

  288.     ceilometer-powervm – Gathers instance/VM statistics.

  289.     networking-powervm – An optional Neutron ML2 agent that supports PowerVM

  290.     Shared Ethernet Adapters (SEAs). Users should utilize this if their environment

  291.     requires Shared Ethernet. However, they may also use the standard Open vSwitch

  292.     agent from the Neutron project to support advanced functions such as Security Groups,

  293.     Quality of Service (QoS), overlay networks (VXLANs) and more.

  294.   status: active

  295.   url: https://wiki.openstack.org/wiki/PowerVM

  296. 

  297. Public Cloud:

  298.   chairs:

  299.     - name: Tobias Rydberg

  300.       irc: tobberydberg

  301.       email: tobias.rydberg@citynetwork.eu

  302.     - name: Howard Huang

  303.       irc: zhipeng

  304.       email: huangzhipeng@huawei.com

  305.   scope: >

  306.      The aim of this sig is to represent the interests of the OpenStack

  307.      public cloud provider community, and to further adoption of OpenStack

  308.      public cloud usage.

  309.   status: active

  310.   url: https://wiki.openstack.org/wiki/PublicCloudSIG

  311. 

  312. Resource Management:

  313.   chairs:

  314.     - name: Howard Huang

  315.       irc: zhipeng

  316.       email: huangzhipeng@huawei.com

  317.   scope: >

  318.     The Resource Management SIG provides a gathering of similar interested

  319.     parties and establish an official channel cross different communities,

  320.     such as Kubernetes (Resource Management WG), Apache Mesos, Open Compute

  321.     Project and so forth, to focus on alignment of resource management

  322.     related functionalities.

  323.   status: forming

  324.   url: https://wiki.openstack.org/wiki/Res_Mgmt_SIG

  325. 

  326. Scientific:

  327.   chairs:

  328.     - name: Blair Bethwaite

  329.       irc: b1airo

  330.       email: blair.bethwaite@gmail.com

  331.     - name: Stig Telfer

  332.       irc: oneswig

  333.       email: stig.openstack@telfer.org

  334.     - name: Martial Michel

  335.       irc: martial_

  336.       email: martialmichel@datamachines.io

  337.   scope: >

  338.     The Scientific SIG (formerly Scientific Working Group) is dedicated to

  339.     representing and advancing the use-cases and needs of research and

  340.     high-performance computing atop OpenStack. It's also a great forum for

  341.     cross-institutional collaboration. If you are (or would like to) run

  342.     OpenStack to support researchers/scientists/academics and/or HPC/HTC,

  343.     then please join!

  344.   status: active

  345.   url: https://wiki.openstack.org/wiki/Scientific_SIG

  346. 

  347. Security:

  348.   chairs:

  349.     - name: Gage Hugo

  350.       irc: gagehugo

  351.       email: gagehugo@gmail.com

  352.   scope: >

  353.     The Security SIG (formerly Security Project) responsibilities include

  354.     aiming to improve overall security of the various OpenStack projects,

  355.     maintaining the list of security notices in OpenStack, and ensuring

  356.     that security incidents are handled in a coordinated fashion. This

  357.     involves maintaining the OSSN (OpenStack Security Notes) and OSSA

  358.     (OpenStack Security Advisories), which are primarily handled under

  359.     the OpenStack Vulnerability Managment Team (VMT), a more

  360.     autonomous subgroup of the Security SIG.

  361.   status: active

  362.   url: https://wiki.openstack.org/wiki/Security-SIG

  363. 

  364. Technical Writing:

  365.   chairs:

  366.     - name: Stephen Finucane

  367.       irc: stephenfin

  368.       email: sfinucan@redhat.com

  369.   scope: >

  370.     The technical writing SIG provides guidance, assistance, tooling, and style

  371.     guides enabling OpenStack project teams to produce consistent, accurate,

  372.     and high-quality documentation.

  373.   url: https://wiki.openstack.org/wiki/Documentation

  374.   status: active

  375. 

  376. Testing and Collaboration Tools:

  377.   chairs:

  378.     - name: Jeremy Stanley

  379.       irc: fungi

  380.       email: fungi@yuggoth.org

  381.   scope: >

  382.     The Testing and Collaboration Tools (TaCT) SIG maintains, in cooperation

  383.     with the OpenDev project, the tooling and infrastructure needed to support

  384.     the development process and testing of the OpenStack project.

  385.   url: tact-sig.html

  386.   status: active