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.

387 lines
14 KiB

  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. API:
  20. chairs:
  21. - name: Dmitry Tantsur
  22. irc: dtantsur
  23. email: dtantsur@protonmail.com
  24. - name: Michael McCune
  25. irc: elmiko
  26. email: msm@redhat.com
  27. scope: >
  28. Formerly known as the API-WG, the API SIG scope is to improve the developer
  29. experience of API users by converging the OpenStack API to a consistent and
  30. pragmatic RESTful design. The working group creates guidelines that all
  31. OpenStack projects should follow for new development, and promotes
  32. convergence of new APIs and future versions of existing APIs.
  33. status: advisory
  34. url: https://wiki.openstack.org/wiki/API_SIG
  35. Automation:
  36. chairs:
  37. - name: Rico Lin
  38. irc: ricolin
  39. email: rico.lin.guanyu@gmail.com
  40. scope: >
  41. Automation SIG scope is to improve experience on develop, operate, and use
  42. all automation (includes auto-scaling and self-healing) and its related
  43. features (like metering, cluster schedule, life cycle management) and to
  44. coordinate across projects and communities (like k8s cluster autoscaling
  45. on OpenStack). Also provide a central place to put tests, documentations,
  46. and even common libraries for auto-scaling and self-healing features.
  47. status: active
  48. url: https://etherpad.openstack.org/p/Automation
  49. Bare Metal:
  50. chairs:
  51. - name: Arne Wiebalck
  52. irc: arne_wiebalck
  53. email: arne.wiebalck@cern.ch
  54. - name: Dmitry Tantsur
  55. irc: dtantsur
  56. email: dtantsur@protonmail.com
  57. scope: >
  58. The scope of the Bare Metal Sig is to promote the development and use
  59. of Ironic and other OpenStack bare metal software. This will include
  60. marketing efforts like case studies of Ironic clusters in industry
  61. and academia, supporting integration of Ironic with projects like
  62. Airship and the Kubernetes Cluster API, coordinating presentations
  63. for industry events, developing documentation and tutorials,
  64. gathering feedback from the community on usage and feature gaps, and
  65. other broader community-facing efforts to encourage the adoption of
  66. Ironic as a bare-metal management tool.
  67. status: active
  68. url: https://etherpad.openstack.org/p/bare-metal-sig
  69. Cloud Research:
  70. chairs:
  71. - name: Mohamed Elsakhawy
  72. irc: melsakhawy
  73. email: m2elsakha@gmail.com
  74. scope: >
  75. The Cloud Research SIG aims to bridge the gap between Academic
  76. Research in Cloud Computing and Technology projects within OpenStack.
  77. The group's purpose is to establish a collaboration space for Cloud
  78. researchers to discuss advancements in Cloud research and methodologies
  79. and to implement them in OpenStack. The group is also a communication
  80. space for researchers looking for guidance on how to evaluate their
  81. research work ( e.g., placement algorithms, model-free frameworks...etc.)
  82. in Openstack.
  83. status: forming
  84. url: https://etherpad.opendev.org/p/cloud-research-sig
  85. Containers:
  86. chairs:
  87. - name: Jean-Philippe Evrard
  88. irc: evrardjp
  89. email: jean-philippe@evrard.me
  90. scope: >
  91. The scope of the Containers SIG is to share practices for the
  92. build, deploy, and operate of OpenStack using application
  93. containers. This is not another deployment tool of containers.
  94. Instead, this SIG should have as members people from the
  95. different projects in the business of dealing with OpenStack
  96. in application containers. The participants should be
  97. interested in container building, willing to share their
  98. practices, and/or define common practices for use within
  99. all OpenStack projects. One example of the deliverables of
  100. the SIG would be a common series of "rules" for the bindep
  101. files relevant for container image building. These rules
  102. would then be applied consistenty across all the OpenStack
  103. projects, but also maintained over time by this group.
  104. Another example of common ground would be sharing how
  105. deployment projects are writing their container "check
  106. probes", and figure out what can be re-used. In other words,
  107. defining together what are application containers "readiness"
  108. and "aliveness" for each service project.
  109. status: forming
  110. url: https://etherpad.openstack.org/p/containers-sig
  111. Edge Computing:
  112. chairs:
  113. - name: Ildiko Vancsa
  114. irc: ildikov
  115. email: ildiko@openstack.org
  116. - name: Gergely Csatari
  117. irc: csatari
  118. email: gergely.csatari@nokia.com
  119. scope: >
  120. The Edge Computing group is a OSF-level special interest group focused
  121. on defining infrastructure systems needed to support applications
  122. distributed over a broad geographic area, with potentially thousands of
  123. sites, located as close as possible to discrete data sources, physical
  124. elements or end users.
  125. status: active
  126. url: https://wiki.openstack.org/wiki/Edge_Computing_Group
  127. Extended Maintenance:
  128. chairs:
  129. - name: Tony Breeds
  130. irc: tonyb
  131. email: tony@bakeyournoodle.com
  132. - name: Elõd Illés
  133. irc: elod
  134. email: elod.illes@est.tech
  135. scope: >
  136. Defining, enforcing and accompanying project teams in the application
  137. of a common stable branch policy. Keeping CI working on stable branches.
  138. Creating and improving related tooling and automation.
  139. status: advisory
  140. url: https://docs.openstack.org/project-team-guide/stable-branches.html
  141. First Contact:
  142. chairs:
  143. - name: Kendall Nelson
  144. irc: diablo_rojo
  145. email: knelson@openstack.org
  146. - name: Matt Oliver
  147. irc: mattoliverau
  148. email: matt@oliver.net.au
  149. scope: >
  150. To provide a place for new contributors to come for information and advice.
  151. This group will also analyze and document successful contribution models
  152. while seeking out and providing information to new members of the community.
  153. status: active
  154. url: https://wiki.openstack.org/wiki/First_Contact_SIG
  155. Hardware Vendor:
  156. chairs:
  157. - name: Sean McGinnis
  158. irc: smcginnis
  159. email: sean.mcginnis@gmail.com
  160. - name: Jay Bryant
  161. irc: jungleboyj
  162. email: jsbryant@electronicjungle.net
  163. scope: >
  164. The goals of this SIG are to provide a place where vendors, and those
  165. interested in vendor specific things like drivers and supporting libs,
  166. can work together and collaborate openly to enable OpenStack services to
  167. integrate and work well on all hardware platforms.
  168. status: active
  169. url: https://wiki.openstack.org/wiki/Hardware_Vendor_SIG
  170. i18n:
  171. chairs:
  172. - name: Ian Y. Choi
  173. irc: ianychoi
  174. email: ianyrchoi@gmail.com
  175. scope: >
  176. To make OpenStack ubiquitously accessible to people of
  177. all language backgrounds.
  178. status: active
  179. url: https://wiki.openstack.org/wiki/I18nTeam
  180. K8s:
  181. chairs:
  182. - name: Chris Hoge
  183. irc: hogepodge
  184. email: chris@openstack.org
  185. - name: David Lyle
  186. irc: david-lyle
  187. email: dklyle0@gmail.com
  188. - name: Robert Morse
  189. irc: rjmorse
  190. email: robert.morse@ticketmaster.com
  191. scope: >
  192. Community-local counterpart to the k8s-sig-openstack group, focused on
  193. cross community communication and collaboration. Where k8s-sig-openstack
  194. spends a good deal of time managing upstream provider code, sig-k8s
  195. would likewise be focused on code to support and enable K8s deployments
  196. within the OpenStack community. This SIG is directly intertwined with
  197. k8s-sig-openstack within the Kubernetes community, with the same sig
  198. leadership and meetings.
  199. status: advisory
  200. url: https://github.com/kubernetes/cloud-provider-openstack/blob/master/README.md
  201. Large Scale:
  202. chairs:
  203. - name: Belmiro Moreira
  204. irc: belmoreira
  205. email: belmiro.moreira@cern.ch
  206. - name: Pengju Jiao
  207. irc: jiaopengju
  208. email: jiaopengju@cmss.chinamobile.com
  209. - name: Thierry Carrez
  210. irc: ttx
  211. email: thierry@openstack.org
  212. scope: >
  213. The aim of the group is to facilitate running OpenStack at large scale,
  214. and help address some of the limitations operators encounter in large
  215. OpenStack clusters.
  216. status: active
  217. url: https://wiki.openstack.org/wiki/Large_Scale_SIG
  218. Multi-Arch:
  219. chairs:
  220. - name: Rico Lin
  221. irc: ricolin
  222. email: rico.lin.guanyu@gmail.com
  223. - name: Tony Breeds
  224. irc: tonyb
  225. email: tony@bakeyournoodle.com
  226. scope: >
  227. This SIG tracks and encourages efforts towards better support for OpenStack
  228. on CPU architectures other than x86_64. This includes providing documents,
  229. building test jobs, tracking issues, and building ecosystem for multiple
  230. architectures.
  231. status: forming
  232. url: https://etherpad.openstack.org/p/Multi-arch
  233. Operation Docs and Tooling:
  234. chairs:
  235. - name: Chris Morgan
  236. irc: mihalis68
  237. email: mihalis68@gmail.com
  238. - name: Sean McGinnis
  239. irc: smcginnis
  240. email: sean.mcginnis@gmail.com
  241. scope: >
  242. The Operation Docs and Tooling SIG is for those interested in operator
  243. guide documentation and tools, scripts, and other code to make running
  244. OpenStack clouds easier and more efficient.
  245. status: active
  246. url: https://wiki.openstack.org/wiki/Operation_Docs_SIG
  247. Packaging:
  248. chairs:
  249. - name: Javier Peña
  250. irc: jpena
  251. email: jpena@redhat.com
  252. scope: >
  253. To make OpenStack easier to update and consume by operators and
  254. provide tooling to package all OpenStack projects directly for
  255. (at first) all RPM based distributions.
  256. status: active
  257. url: https://wiki.openstack.org/wiki/Rpm-packaging
  258. PowerVMStacker:
  259. chairs:
  260. - name: Ramakrishnan Ramasubbu
  261. irc: SriRamaSan
  262. email: RR00462393@techmahindra.com
  263. - name: Anurag Mahanto
  264. irc: anuragmahanto67
  265. email: Anurag.Mahanto@TechMahindra.com
  266. scope: >
  267. The scope of the PowerVMStacker is to provide OpenStack support for the
  268. POWER CPU architecture on the PowerVM hypervisor.
  269. This enables support of Linux, AIX and IBM i for PowerVM systems.
  270. There are currently three supported components of the PowerVM driver -
  271. nova-powervm – Support for Nova use cases.
  272. ceilometer-powervm – Gathers instance/VM statistics.
  273. networking-powervm – An optional Neutron ML2 agent that supports PowerVM
  274. Shared Ethernet Adapters (SEAs). Users should utilize this if their environment
  275. requires Shared Ethernet. However, they may also use the standard Open vSwitch
  276. agent from the Neutron project to support advanced functions such as Security Groups,
  277. Quality of Service (QoS), overlay networks (VXLANs) and more.
  278. status: active
  279. url: https://wiki.openstack.org/wiki/PowerVM
  280. Public Cloud:
  281. chairs:
  282. - name: Tobias Rydberg
  283. irc: tobberydberg
  284. email: tobias.rydberg@citynetwork.eu
  285. - name: Howard Huang
  286. irc: zhipeng
  287. email: huangzhipeng@huawei.com
  288. scope: >
  289. The aim of this sig is to represent the interests of the OpenStack
  290. public cloud provider community, and to further adoption of OpenStack
  291. public cloud usage.
  292. status: active
  293. url: https://wiki.openstack.org/wiki/PublicCloudSIG
  294. Resource Management:
  295. chairs:
  296. - name: Howard Huang
  297. irc: zhipeng
  298. email: huangzhipeng@huawei.com
  299. scope: >
  300. The Resource Management SIG provides a gathering of similar interested
  301. parties and establish an official channel cross different communities,
  302. such as Kubernetes (Resource Management WG), Apache Mesos, Open Compute
  303. Project and so forth, to focus on alignment of resource management
  304. related functionalities.
  305. status: forming
  306. url: https://wiki.openstack.org/wiki/Res_Mgmt_SIG
  307. Scientific:
  308. chairs:
  309. - name: Blair Bethwaite
  310. irc: b1airo
  311. email: blair.bethwaite@gmail.com
  312. - name: Stig Telfer
  313. irc: oneswig
  314. email: stig.openstack@telfer.org
  315. - name: Martial Michel
  316. irc: martial_
  317. email: martialmichel@datamachines.io
  318. scope: >
  319. The Scientific SIG (formerly Scientific Working Group) is dedicated to
  320. representing and advancing the use-cases and needs of research and
  321. high-performance computing atop OpenStack. It's also a great forum for
  322. cross-institutional collaboration. If you are (or would like to) run
  323. OpenStack to support researchers/scientists/academics and/or HPC/HTC,
  324. then please join!
  325. status: active
  326. url: https://wiki.openstack.org/wiki/Scientific_SIG
  327. Security:
  328. chairs:
  329. - name: Gage Hugo
  330. irc: gagehugo
  331. email: gagehugo@gmail.com
  332. scope: >
  333. The Security SIG (formerly Security Project) responsibilities include
  334. aiming to improve overall security of the various OpenStack projects,
  335. maintaining the list of security notices in OpenStack, and ensuring
  336. that security incidents are handled in a coordinated fashion. This
  337. involves maintaining the OSSN (OpenStack Security Notes) and OSSA
  338. (OpenStack Security Advisories), which are primarily handled under
  339. the OpenStack Vulnerability Managment Team (VMT), a more
  340. autonomous subgroup of the Security SIG.
  341. status: active
  342. url: https://wiki.openstack.org/wiki/Security-SIG
  343. Technical Writing:
  344. chairs:
  345. - name: Stephen Finucane
  346. irc: stephenfin
  347. email: sfinucan@redhat.com
  348. scope: >
  349. The technical writing SIG provides guidance, assistance, tooling, and style
  350. guides enabling OpenStack project teams to produce consistent, accurate,
  351. and high-quality documentation.
  352. url: https://wiki.openstack.org/wiki/Documentation
  353. status: active
  354. Testing and Collaboration Tools:
  355. chairs:
  356. - name: Jeremy Stanley
  357. irc: fungi
  358. email: fungi@yuggoth.org
  359. scope: >
  360. The Testing and Collaboration Tools (TaCT) SIG maintains, in cooperation
  361. with the OpenDev project, the tooling and infrastructure needed to support
  362. the development process and testing of the OpenStack project.
  363. url: tact-sig.html
  364. status: active