OpenStack - User contributions [en]

Documentation/HA Guide Update

2015-01-23T18:14:38Z

Sriramhere: /* Things to Note */

= HA Guide Update =

== What ==

Let's update the OpenStack HA Guide. Based on direction from Anne Gentile, we will follow a similar path as the Security Guide -- subject matter experts working with core docs team members for reviews.

In addition to addressing the bug list (https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide), this effort will update all aspects of the guide to be more current and provide richer information and advice about OpenStack HA.

We've created an [https://etherpad.openstack.org/p/openstack-haguide-update etherpad] to capture ideas and start to form a plan for what is going to be updated, in what way, and who is responsible.

Meetings take place in #openstack-meeting-3. Team members may communicate on relevant topics via the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs OpenStack Docs] mailing list by using "[ha-guide]" at the beginning of the subject line.

== Next Meeting ==
Thursday, January 29 at 9:00 pm UTC on #openstack-meeting-3

Agenda
# Bug bash results
# [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide Outstanding bugs]

== Past Meetings ==
Thursday, January 22 at 9:00 pm UTC on #openstack-meeting-3 ([https://etherpad.openstack.org/p/20150122-ha-guide-update-meeting irc log])

Agenda
# Update on ACTION items from last meeting
## DONE ACTION (All): Update wiki with the project that you are investigating
## IN PROGRESS ACTION (Sriram): Check how we can get this meeting on the OpenStack Calendar
## DONE ACTION (Sriram): Can we move meetings to an official IRC channel
# Bug bash on January 23 focused on [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide existing bugs]

Thursday, January 15 on #openstack-haguide ([https://etherpad.openstack.org/p/20150115-ha-guide-update-meeting irc log])
# Regular meeting time
# [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide Existing bugs] - Plan to resolve
# Need an owner for finding out from PTLs which projects work in a/a or a/p

Wednesday, October 29 on #openstack-haguide ([https://etherpad.openstack.org/p/20141029-ha-guide-update-meeting irc log])

== Where ==
Join the group in #openstack-haguide to chat about this effort. Regular meetings are for 30 minutes on each Thursday at 3pm US Central.

== Project HA Status Tracker ==
This section is intended to be used by the HA Guide Update team to track HA considerations for OpenStack integrated projects (created due to a request during the 01/15/15 meeting). This information will be used as we build an updated TOC and also help determine content for each project. Integrated projects information obtained from [https://github.com/openstack/governance/blob/master/reference/programs.yaml programs.yaml].
{| class="wikitable sortable"
|-
! OpenStack Project !! Core Members (Italic = PTL) !! API HA Status !! Service HA Status !! Metadata HA Status !! Additional Comments !! Section Completed By
|-
| Sample || John Doe, ''Jane Doe'' || Active/Active || Active/Passive || Not Applicable || Leverages HA Proxy for API HA || Shamail T.
|-
| Nova || Andrew Laski, Christopher Yeoh, Dan Smith, Daniel Berrange, Jay Pipes, Joe Gordon, John Garbutt, Ken'ichi Ohmichi, Kevin L. Mitchell, Matt Dietz, Matt Riedemann, ''Michael Still'', Nikola Dipanov, OpenStack Hudson, Russell Bryant, Sean Dague || TBD || TBD || TBD || -- || TBD
|-
| Swift || Alistair Coles, Chmouel Boudjnah, Christian Schwede, Chuck Thier, Clay Gerrard, Darrell Bishop, David Goetz, Greg Lange, ''John Dickinson'', Michael Barton, OpenStack Hudson, Pete Zaitcev, Peter Portante, Samuel Merritt, gholt, paul luse || TBD || TBD || TBD || -- || TBD
|-
| Glance || Alex Meade, Alexander Tivelkov, Arnaud Legendre, Brian Lamar, Brian Waldon, Dan Prince, Eoghan Glynn, Erno Kuvaja, Fei Long Wang, Flavio Percoco, John Bresnahan, Mark Washenberger, OpenStack Hudson, Stuart McLaren, Zhi Yan Liu, Iccha Sethi, ''Nikhil Komawar'' || TBD || TBD || TBD || -- || TBD
|-
| Keystone || Brant Knudson, David Stanek, Dolph Mathews, Jamie Lennox, Lance Bragstad, ''Morgan Fainberg'', OpenStack Hudson, Steve Martinelli, A. Young, Guang Yee, Henry Nash || TBD || TBD || TBD || -- || TBD
|-
| Horizon || Akihiro Motoki, Ana Krivokapic, Cindy Lu, ''David Lyle'', Gabriel Hurley, Julie Pichon, Kieran Spear, Lin Hua Cheng, Matthias Runge, Radomir Dopieralski, Tatiana Ovchinnikova, Thai Tran, Tihomir Trifonov, Zhenguo Niu || TBD || TBD || TBD || -- || TBD
|-
| Neutron || Aaron Rosen, Akihiro Motoki, Armando Migliaccio, Carl Baldwin, Edgar Magana, Henry Gessau, Kevin Benton, ''Kyle Mestery'', Maru Newby, Oleg Bondarev, Salvatore Orlando, Gary Kotton, Mark McClain || TBD || TBD || TBD || -- || TBD
|-
| Cinder || Avishay Traeger, Duncan Thomas, Eric Harney, Huang Zhiteng, Jay Bryant, John Griffith, ''Mike Perez'', Walter A. Boring IV, Xing Yang || TBD || TBD || TBD || -- || TBD
|-
| Ceilometer || Angus Salkeld, Dina Belova, Doug Hellmann, ''Eoghan Glynn'', Ildiko Vancsa, Julien Danjou, Lianhao Lu, Mehdi Abaakouk, Nadya Privalova, Nejc Saje, Nick Barcet, Gordon Chung || TBD || TBD || TBD || -- || TBD
|-
| Heat || ''Angus Salkeld'', Bartosz Górski, Clint 'SpamapS' Byrum, Jason Dunsmore, Jeff Peeler, Pavlo Shchelokovskyy, Randall Burt, Sergey Kraynev, Steve Baker, Steven Hardy, Thomas Herve, Thomas Spatzier, Zane Bitter || TBD || TBD || TBD || -- || TBD
|-
| Trove || Auston McReynolds, Craig Vyvial, Michael Basnight, ''Nikhil Manchanda'', Tim Simpson, Vipul Sabhaya, Amrith (Tesora), Iccha Sethi || TBD || TBD || TBD || -- || TBD
|-
| Ironic || Chris Krelle, David Shrewsbury, ''Devananda van der Veen'', Dmitry Tantsur, Haomeng,Wang, Jim Rollenhagen, Lucas Alvares, Ruby Loo, Yuriy Zveryanskyy, Lifeless || TBD || TBD || TBD || -- || TBD
|-
| Sahara || Alexander Ignatov, Andrew Lazarev, John Speidel, Matthew Farrellee, Michael McCune, ''Sergey Lukjanov'', Sergey Reshetnyak, Trevor McKay || TBD || TBD || TBD || -- || TBD
|}
----
[[Category:Documentation]]

== Bug Bash ==
#Whenː 01/23/2014
#Whereː online
=== Logistics ===

Open Bugsː [https://bugs.launchpad.net/openstack/+bugs?field.tag=ha-guide Link]
# Tag to useː ha-guide
# Version of Book to file bugs againstː [http://docs.openstack.org/high-availability-guide/content/index.html HTML] Version

=== Suggested Priority ===
#Pri0ː Stale/ Incorrect info (for instance wrong config, incorrect settings etc)
#Pri1ː Missing Info (like new chapters to add, topics to cover etc)
#Pri2ː Cosmetic Errors/ Sentence formation etc

=== Things to Note ===
#Use the little 'bug' icon to auto-magically create a bug entry with relevant info such as chapter name, page, url. You can add more details like tag, description as required.
#Include as many details as possible, chapter #, location etc in the book.
#Include OpenStack Versions if applicable

Documentation/HA Guide Update

2015-01-23T17:40:24Z

Sriramhere: /* Logistics */

= HA Guide Update =

== What ==

Let's update the OpenStack HA Guide. Based on direction from Anne Gentile, we will follow a similar path as the Security Guide -- subject matter experts working with core docs team members for reviews.

In addition to addressing the bug list (https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide), this effort will update all aspects of the guide to be more current and provide richer information and advice about OpenStack HA.

We've created an [https://etherpad.openstack.org/p/openstack-haguide-update etherpad] to capture ideas and start to form a plan for what is going to be updated, in what way, and who is responsible.

Meetings take place in #openstack-meeting-3. Team members may communicate on relevant topics via the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs OpenStack Docs] mailing list by using "[ha-guide]" at the beginning of the subject line.

== Next Meeting ==
Thursday, January 29 at 9:00 pm UTC on #openstack-meeting-3

Agenda
# Bug bash results
# [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide Outstanding bugs]

== Past Meetings ==
Thursday, January 22 at 9:00 pm UTC on #openstack-meeting-3 ([https://etherpad.openstack.org/p/20150122-ha-guide-update-meeting irc log])

Agenda
# Update on ACTION items from last meeting
## DONE ACTION (All): Update wiki with the project that you are investigating
## IN PROGRESS ACTION (Sriram): Check how we can get this meeting on the OpenStack Calendar
## DONE ACTION (Sriram): Can we move meetings to an official IRC channel
# Bug bash on January 23 focused on [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide existing bugs]

Thursday, January 15 on #openstack-haguide ([https://etherpad.openstack.org/p/20150115-ha-guide-update-meeting irc log])
# Regular meeting time
# [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide Existing bugs] - Plan to resolve
# Need an owner for finding out from PTLs which projects work in a/a or a/p

Wednesday, October 29 on #openstack-haguide ([https://etherpad.openstack.org/p/20141029-ha-guide-update-meeting irc log])

== Where ==
Join the group in #openstack-haguide to chat about this effort. Regular meetings are for 30 minutes on each Thursday at 3pm US Central.

== Project HA Status Tracker ==
This section is intended to be used by the HA Guide Update team to track HA considerations for OpenStack integrated projects (created due to a request during the 01/15/15 meeting). This information will be used as we build an updated TOC and also help determine content for each project. Integrated projects information obtained from [https://github.com/openstack/governance/blob/master/reference/programs.yaml programs.yaml].
{| class="wikitable sortable"
|-
! OpenStack Project !! Core Members (Italic = PTL) !! API HA Status !! Service HA Status !! Metadata HA Status !! Additional Comments !! Section Completed By
|-
| Sample || John Doe, ''Jane Doe'' || Active/Active || Active/Passive || Not Applicable || Leverages HA Proxy for API HA || Shamail T.
|-
| Nova || Andrew Laski, Christopher Yeoh, Dan Smith, Daniel Berrange, Jay Pipes, Joe Gordon, John Garbutt, Ken'ichi Ohmichi, Kevin L. Mitchell, Matt Dietz, Matt Riedemann, ''Michael Still'', Nikola Dipanov, OpenStack Hudson, Russell Bryant, Sean Dague || TBD || TBD || TBD || -- || TBD
|-
| Swift || Alistair Coles, Chmouel Boudjnah, Christian Schwede, Chuck Thier, Clay Gerrard, Darrell Bishop, David Goetz, Greg Lange, ''John Dickinson'', Michael Barton, OpenStack Hudson, Pete Zaitcev, Peter Portante, Samuel Merritt, gholt, paul luse || TBD || TBD || TBD || -- || TBD
|-
| Glance || Alex Meade, Alexander Tivelkov, Arnaud Legendre, Brian Lamar, Brian Waldon, Dan Prince, Eoghan Glynn, Erno Kuvaja, Fei Long Wang, Flavio Percoco, John Bresnahan, Mark Washenberger, OpenStack Hudson, Stuart McLaren, Zhi Yan Liu, Iccha Sethi, ''Nikhil Komawar'' || TBD || TBD || TBD || -- || TBD
|-
| Keystone || Brant Knudson, David Stanek, Dolph Mathews, Jamie Lennox, Lance Bragstad, ''Morgan Fainberg'', OpenStack Hudson, Steve Martinelli, A. Young, Guang Yee, Henry Nash || TBD || TBD || TBD || -- || TBD
|-
| Horizon || Akihiro Motoki, Ana Krivokapic, Cindy Lu, ''David Lyle'', Gabriel Hurley, Julie Pichon, Kieran Spear, Lin Hua Cheng, Matthias Runge, Radomir Dopieralski, Tatiana Ovchinnikova, Thai Tran, Tihomir Trifonov, Zhenguo Niu || TBD || TBD || TBD || -- || TBD
|-
| Neutron || Aaron Rosen, Akihiro Motoki, Armando Migliaccio, Carl Baldwin, Edgar Magana, Henry Gessau, Kevin Benton, ''Kyle Mestery'', Maru Newby, Oleg Bondarev, Salvatore Orlando, Gary Kotton, Mark McClain || TBD || TBD || TBD || -- || TBD
|-
| Cinder || Avishay Traeger, Duncan Thomas, Eric Harney, Huang Zhiteng, Jay Bryant, John Griffith, ''Mike Perez'', Walter A. Boring IV, Xing Yang || TBD || TBD || TBD || -- || TBD
|-
| Ceilometer || Angus Salkeld, Dina Belova, Doug Hellmann, ''Eoghan Glynn'', Ildiko Vancsa, Julien Danjou, Lianhao Lu, Mehdi Abaakouk, Nadya Privalova, Nejc Saje, Nick Barcet, Gordon Chung || TBD || TBD || TBD || -- || TBD
|-
| Heat || ''Angus Salkeld'', Bartosz Górski, Clint 'SpamapS' Byrum, Jason Dunsmore, Jeff Peeler, Pavlo Shchelokovskyy, Randall Burt, Sergey Kraynev, Steve Baker, Steven Hardy, Thomas Herve, Thomas Spatzier, Zane Bitter || TBD || TBD || TBD || -- || TBD
|-
| Trove || Auston McReynolds, Craig Vyvial, Michael Basnight, ''Nikhil Manchanda'', Tim Simpson, Vipul Sabhaya, Amrith (Tesora), Iccha Sethi || TBD || TBD || TBD || -- || TBD
|-
| Ironic || Chris Krelle, David Shrewsbury, ''Devananda van der Veen'', Dmitry Tantsur, Haomeng,Wang, Jim Rollenhagen, Lucas Alvares, Ruby Loo, Yuriy Zveryanskyy, Lifeless || TBD || TBD || TBD || -- || TBD
|-
| Sahara || Alexander Ignatov, Andrew Lazarev, John Speidel, Matthew Farrellee, Michael McCune, ''Sergey Lukjanov'', Sergey Reshetnyak, Trevor McKay || TBD || TBD || TBD || -- || TBD
|}
----
[[Category:Documentation]]

== Bug Bash ==
#Whenː 01/23/2014
#Whereː online
=== Logistics ===

Open Bugsː [https://bugs.launchpad.net/openstack/+bugs?field.tag=ha-guide Link]
# Tag to useː ha-guide
# Version of Book to file bugs againstː [http://docs.openstack.org/high-availability-guide/content/index.html HTML] Version

=== Suggested Priority ===
#Pri0ː Stale/ Incorrect info (for instance wrong config, incorrect settings etc)
#Pri1ː Missing Info (like new chapters to add, topics to cover etc)
#Pri2ː Cosmetic Errors/ Sentence formation etc

=== Things to Note ===
#Use the little 'bug' icon to auto-magically create a bug entry with tag auto-populated and some more relevant info. You can add more details as required.
#Include as many details as possible, chapter #, location etc in the book.
#Include OpenStack Versions if applicable

Documentation/HA Guide Update

2015-01-23T17:39:16Z

Sriramhere: /* Things to Note */

= HA Guide Update =

== What ==

Let's update the OpenStack HA Guide. Based on direction from Anne Gentile, we will follow a similar path as the Security Guide -- subject matter experts working with core docs team members for reviews.

In addition to addressing the bug list (https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide), this effort will update all aspects of the guide to be more current and provide richer information and advice about OpenStack HA.

We've created an [https://etherpad.openstack.org/p/openstack-haguide-update etherpad] to capture ideas and start to form a plan for what is going to be updated, in what way, and who is responsible.

Meetings take place in #openstack-meeting-3. Team members may communicate on relevant topics via the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs OpenStack Docs] mailing list by using "[ha-guide]" at the beginning of the subject line.

== Next Meeting ==
Thursday, January 29 at 9:00 pm UTC on #openstack-meeting-3

Agenda
# Bug bash results
# [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide Outstanding bugs]

== Past Meetings ==
Thursday, January 22 at 9:00 pm UTC on #openstack-meeting-3 ([https://etherpad.openstack.org/p/20150122-ha-guide-update-meeting irc log])

Agenda
# Update on ACTION items from last meeting
## DONE ACTION (All): Update wiki with the project that you are investigating
## IN PROGRESS ACTION (Sriram): Check how we can get this meeting on the OpenStack Calendar
## DONE ACTION (Sriram): Can we move meetings to an official IRC channel
# Bug bash on January 23 focused on [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide existing bugs]

Thursday, January 15 on #openstack-haguide ([https://etherpad.openstack.org/p/20150115-ha-guide-update-meeting irc log])
# Regular meeting time
# [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide Existing bugs] - Plan to resolve
# Need an owner for finding out from PTLs which projects work in a/a or a/p

Wednesday, October 29 on #openstack-haguide ([https://etherpad.openstack.org/p/20141029-ha-guide-update-meeting irc log])

== Where ==
Join the group in #openstack-haguide to chat about this effort. Regular meetings are for 30 minutes on each Thursday at 3pm US Central.

== Project HA Status Tracker ==
This section is intended to be used by the HA Guide Update team to track HA considerations for OpenStack integrated projects (created due to a request during the 01/15/15 meeting). This information will be used as we build an updated TOC and also help determine content for each project. Integrated projects information obtained from [https://github.com/openstack/governance/blob/master/reference/programs.yaml programs.yaml].
{| class="wikitable sortable"
|-
! OpenStack Project !! Core Members (Italic = PTL) !! API HA Status !! Service HA Status !! Metadata HA Status !! Additional Comments !! Section Completed By
|-
| Sample || John Doe, ''Jane Doe'' || Active/Active || Active/Passive || Not Applicable || Leverages HA Proxy for API HA || Shamail T.
|-
| Nova || Andrew Laski, Christopher Yeoh, Dan Smith, Daniel Berrange, Jay Pipes, Joe Gordon, John Garbutt, Ken'ichi Ohmichi, Kevin L. Mitchell, Matt Dietz, Matt Riedemann, ''Michael Still'', Nikola Dipanov, OpenStack Hudson, Russell Bryant, Sean Dague || TBD || TBD || TBD || -- || TBD
|-
| Swift || Alistair Coles, Chmouel Boudjnah, Christian Schwede, Chuck Thier, Clay Gerrard, Darrell Bishop, David Goetz, Greg Lange, ''John Dickinson'', Michael Barton, OpenStack Hudson, Pete Zaitcev, Peter Portante, Samuel Merritt, gholt, paul luse || TBD || TBD || TBD || -- || TBD
|-
| Glance || Alex Meade, Alexander Tivelkov, Arnaud Legendre, Brian Lamar, Brian Waldon, Dan Prince, Eoghan Glynn, Erno Kuvaja, Fei Long Wang, Flavio Percoco, John Bresnahan, Mark Washenberger, OpenStack Hudson, Stuart McLaren, Zhi Yan Liu, Iccha Sethi, ''Nikhil Komawar'' || TBD || TBD || TBD || -- || TBD
|-
| Keystone || Brant Knudson, David Stanek, Dolph Mathews, Jamie Lennox, Lance Bragstad, ''Morgan Fainberg'', OpenStack Hudson, Steve Martinelli, A. Young, Guang Yee, Henry Nash || TBD || TBD || TBD || -- || TBD
|-
| Horizon || Akihiro Motoki, Ana Krivokapic, Cindy Lu, ''David Lyle'', Gabriel Hurley, Julie Pichon, Kieran Spear, Lin Hua Cheng, Matthias Runge, Radomir Dopieralski, Tatiana Ovchinnikova, Thai Tran, Tihomir Trifonov, Zhenguo Niu || TBD || TBD || TBD || -- || TBD
|-
| Neutron || Aaron Rosen, Akihiro Motoki, Armando Migliaccio, Carl Baldwin, Edgar Magana, Henry Gessau, Kevin Benton, ''Kyle Mestery'', Maru Newby, Oleg Bondarev, Salvatore Orlando, Gary Kotton, Mark McClain || TBD || TBD || TBD || -- || TBD
|-
| Cinder || Avishay Traeger, Duncan Thomas, Eric Harney, Huang Zhiteng, Jay Bryant, John Griffith, ''Mike Perez'', Walter A. Boring IV, Xing Yang || TBD || TBD || TBD || -- || TBD
|-
| Ceilometer || Angus Salkeld, Dina Belova, Doug Hellmann, ''Eoghan Glynn'', Ildiko Vancsa, Julien Danjou, Lianhao Lu, Mehdi Abaakouk, Nadya Privalova, Nejc Saje, Nick Barcet, Gordon Chung || TBD || TBD || TBD || -- || TBD
|-
| Heat || ''Angus Salkeld'', Bartosz Górski, Clint 'SpamapS' Byrum, Jason Dunsmore, Jeff Peeler, Pavlo Shchelokovskyy, Randall Burt, Sergey Kraynev, Steve Baker, Steven Hardy, Thomas Herve, Thomas Spatzier, Zane Bitter || TBD || TBD || TBD || -- || TBD
|-
| Trove || Auston McReynolds, Craig Vyvial, Michael Basnight, ''Nikhil Manchanda'', Tim Simpson, Vipul Sabhaya, Amrith (Tesora), Iccha Sethi || TBD || TBD || TBD || -- || TBD
|-
| Ironic || Chris Krelle, David Shrewsbury, ''Devananda van der Veen'', Dmitry Tantsur, Haomeng,Wang, Jim Rollenhagen, Lucas Alvares, Ruby Loo, Yuriy Zveryanskyy, Lifeless || TBD || TBD || TBD || -- || TBD
|-
| Sahara || Alexander Ignatov, Andrew Lazarev, John Speidel, Matthew Farrellee, Michael McCune, ''Sergey Lukjanov'', Sergey Reshetnyak, Trevor McKay || TBD || TBD || TBD || -- || TBD
|}
----
[[Category:Documentation]]

== Bug Bash ==
#Whenː 01/23/2014
#Whereː online
=== Logistics ===

Open Bugsː [https://bugs.launchpad.net/openstack/+bugs?field.tag=ha-guide Link]
# Tag to useː ha-guide

=== Suggested Priority ===
#Pri0ː Stale/ Incorrect info (for instance wrong config, incorrect settings etc)
#Pri1ː Missing Info (like new chapters to add, topics to cover etc)
#Pri2ː Cosmetic Errors/ Sentence formation etc

=== Things to Note ===
#Use the little 'bug' icon to auto-magically create a bug entry with tag auto-populated and some more relevant info. You can add more details as required.
#Include as many details as possible, chapter #, location etc in the book.
#Include OpenStack Versions if applicable

Documentation/HA Guide Update

2015-01-22T21:09:19Z

Sriramhere: /* Logistics */

= HA Guide Update =

== What ==

Let's update the OpenStack HA Guide. Based on direction from Anne Gentile, we will follow a similar path as the Security Guide -- subject matter experts working with core docs team members for reviews.

In addition to addressing the bug list (https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide), this effort will update all aspects of the guide to be more current and provide richer information and advice about OpenStack HA.

We've created an [https://etherpad.openstack.org/p/openstack-haguide-update etherpad] to capture ideas and start to form a plan for what is going to be updated, in what way, and who is responsible.

== Next Meeting ==
Thursday, January 22 at 9:00 pm UTC on #openstack-meeting-3

Agenda
# Update on ACTION items from last meeting
## ACTION (All): Update wiki with the project that you are investigating
## ACTION (Sriram): Check how we can get this meeting on the OpenStack Calendar
## ACTION (Sriram): Can we move meetings to an official IRC channel
# Bug bash on January 23 focused on [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide existing bugs]

== Past Meetings ==
Thursday, January 15 on #openstack-haguide ([https://etherpad.openstack.org/p/20150115-ha-guide-update-meeting irc log])
# Regular meeting time
# [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide Existing bugs] - Plan to resolve
# Need an owner for finding out from PTLs which projects work in a/a or a/p

Wednesday, October 29 on #openstack-haguide ([https://etherpad.openstack.org/p/20141029-ha-guide-update-meeting irc log])

== Where ==
Join the group in #openstack-haguide to chat about this effort. Regular meetings are for 30 minutes on each Thursday at 3pm US Central.

== Project HA Status Tracker ==
This section is intended to be used by the HA Guide Update team to track HA considerations for OpenStack integrated projects (created due to a request during the 01/15/15 meeting). This information will be used as we build an updated TOC and also help determine content for each project. Integrated projects information obtained from [https://github.com/openstack/governance/blob/master/reference/programs.yaml programs.yaml].
{| class="wikitable sortable"
|-
! OpenStack Project !! Core Members (Italic = PTL) !! API HA Status !! Service HA Status !! Metadata HA Status !! Additional Comments !! Section Completed By
|-
| Sample || John Doe, ''Jane Doe'' || Active/Active || Active/Passive || Not Applicable || Leverages HA Proxy for API HA || Shamail T.
|-
| Nova || Andrew Laski, Christopher Yeoh, Dan Smith, Daniel Berrange, Jay Pipes, Joe Gordon, John Garbutt, Ken'ichi Ohmichi, Kevin L. Mitchell, Matt Dietz, Matt Riedemann, ''Michael Still'', Nikola Dipanov, OpenStack Hudson, Russell Bryant, Sean Dague || TBD || TBD || TBD || -- || TBD
|-
| Swift || Alistair Coles, Chmouel Boudjnah, Christian Schwede, Chuck Thier, Clay Gerrard, Darrell Bishop, David Goetz, Greg Lange, ''John Dickinson'', Michael Barton, OpenStack Hudson, Pete Zaitcev, Peter Portante, Samuel Merritt, gholt, paul luse || TBD || TBD || TBD || -- || TBD
|-
| Glance || Alex Meade, Alexander Tivelkov, Arnaud Legendre, Brian Lamar, Brian Waldon, Dan Prince, Eoghan Glynn, Erno Kuvaja, Fei Long Wang, Flavio Percoco, John Bresnahan, Mark Washenberger, OpenStack Hudson, Stuart McLaren, Zhi Yan Liu, Iccha Sethi, ''Nikhil Komawar'' || TBD || TBD || TBD || -- || TBD
|-
| Keystone || Brant Knudson, David Stanek, Dolph Mathews, Jamie Lennox, Lance Bragstad, ''Morgan Fainberg'', OpenStack Hudson, Steve Martinelli, A. Young, Guang Yee, Henry Nash || TBD || TBD || TBD || -- || TBD
|-
| Horizon || Akihiro Motoki, Ana Krivokapic, Cindy Lu, ''David Lyle'', Gabriel Hurley, Julie Pichon, Kieran Spear, Lin Hua Cheng, Matthias Runge, Radomir Dopieralski, Tatiana Ovchinnikova, Thai Tran, Tihomir Trifonov, Zhenguo Niu || TBD || TBD || TBD || -- || TBD
|-
| Neutron || Aaron Rosen, Akihiro Motoki, Armando Migliaccio, Carl Baldwin, Edgar Magana, Henry Gessau, Kevin Benton, ''Kyle Mestery'', Maru Newby, Oleg Bondarev, Salvatore Orlando, Gary Kotton, Mark McClain || TBD || TBD || TBD || -- || TBD
|-
| Cinder || Avishay Traeger, Duncan Thomas, Eric Harney, Huang Zhiteng, Jay Bryant, John Griffith, ''Mike Perez'', Walter A. Boring IV, Xing Yang || TBD || TBD || TBD || -- || TBD
|-
| Ceilometer || Angus Salkeld, Dina Belova, Doug Hellmann, ''Eoghan Glynn'', Ildiko Vancsa, Julien Danjou, Lianhao Lu, Mehdi Abaakouk, Nadya Privalova, Nejc Saje, Nick Barcet, Gordon Chung || TBD || TBD || TBD || -- || TBD
|-
| Heat || ''Angus Salkeld'', Bartosz Górski, Clint 'SpamapS' Byrum, Jason Dunsmore, Jeff Peeler, Pavlo Shchelokovskyy, Randall Burt, Sergey Kraynev, Steve Baker, Steven Hardy, Thomas Herve, Thomas Spatzier, Zane Bitter || TBD || TBD || TBD || -- || TBD
|-
| Trove || Auston McReynolds, Craig Vyvial, Michael Basnight, ''Nikhil Manchanda'', Tim Simpson, Vipul Sabhaya, Amrith (Tesora), Iccha Sethi || TBD || TBD || TBD || -- || TBD
|-
| Ironic || Chris Krelle, David Shrewsbury, ''Devananda van der Veen'', Dmitry Tantsur, Haomeng,Wang, Jim Rollenhagen, Lucas Alvares, Ruby Loo, Yuriy Zveryanskyy, Lifeless || TBD || TBD || TBD || -- || TBD
|-
| Sahara || Alexander Ignatov, Andrew Lazarev, John Speidel, Matthew Farrellee, Michael McCune, ''Sergey Lukjanov'', Sergey Reshetnyak, Trevor McKay || TBD || TBD || TBD || -- || TBD
|}
----
[[Category:Documentation]]

== Bug Bash ==
#Whenː 01/23/2014
#Whereː online
=== Logistics ===

Open Bugsː [https://bugs.launchpad.net/openstack/+bugs?field.tag=ha-guide Link]
# Tag to useː ha-guide

=== Suggested Priority ===
#Pri0ː Stale/ Incorrect info (for instance wrong config, incorrect settings etc)
#Pri1ː Missing Info (like new chapters to add, topics to cover etc)
#Pri2ː Cosmetic Errors/ Sentence formation etc

=== Things to Note ===
#Include as many details as possible, chapter #, location etc in the book.
#Include OpenStack Versions if applicable

Documentation/HA Guide Update

2015-01-22T21:04:26Z

Sriramhere: /* Logistics */

= HA Guide Update =

== What ==

Let's update the OpenStack HA Guide. Based on direction from Anne Gentile, we will follow a similar path as the Security Guide -- subject matter experts working with core docs team members for reviews.

In addition to addressing the bug list (https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide), this effort will update all aspects of the guide to be more current and provide richer information and advice about OpenStack HA.

We've created an [https://etherpad.openstack.org/p/openstack-haguide-update etherpad] to capture ideas and start to form a plan for what is going to be updated, in what way, and who is responsible.

== Next Meeting ==
Thursday, January 22 at 9:00 pm UTC on #openstack-meeting-3

Agenda
# Update on ACTION items from last meeting
## ACTION (All): Update wiki with the project that you are investigating
## ACTION (Sriram): Check how we can get this meeting on the OpenStack Calendar
## ACTION (Sriram): Can we move meetings to an official IRC channel
# Bug bash on January 23 focused on [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide existing bugs]

== Past Meetings ==
Thursday, January 15 on #openstack-haguide ([https://etherpad.openstack.org/p/20150115-ha-guide-update-meeting irc log])
# Regular meeting time
# [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide Existing bugs] - Plan to resolve
# Need an owner for finding out from PTLs which projects work in a/a or a/p

Wednesday, October 29 on #openstack-haguide ([https://etherpad.openstack.org/p/20141029-ha-guide-update-meeting irc log])

== Where ==
Join the group in #openstack-haguide to chat about this effort. Regular meetings are for 30 minutes on each Thursday at 3pm US Central.

== Project HA Status Tracker ==
This section is intended to be used by the HA Guide Update team to track HA considerations for OpenStack integrated projects (created due to a request during the 01/15/15 meeting). This information will be used as we build an updated TOC and also help determine content for each project. Integrated projects information obtained from [https://github.com/openstack/governance/blob/master/reference/programs.yaml programs.yaml].
{| class="wikitable sortable"
|-
! OpenStack Project !! Core Members (Italic = PTL) !! API HA Status !! Service HA Status !! Metadata HA Status !! Additional Comments !! Section Completed By
|-
| Sample || John Doe, ''Jane Doe'' || Active/Active || Active/Passive || Not Applicable || Leverages HA Proxy for API HA || Shamail T.
|-
| Nova || Andrew Laski, Christopher Yeoh, Dan Smith, Daniel Berrange, Jay Pipes, Joe Gordon, John Garbutt, Ken'ichi Ohmichi, Kevin L. Mitchell, Matt Dietz, Matt Riedemann, ''Michael Still'', Nikola Dipanov, OpenStack Hudson, Russell Bryant, Sean Dague || TBD || TBD || TBD || -- || TBD
|-
| Swift || Alistair Coles, Chmouel Boudjnah, Christian Schwede, Chuck Thier, Clay Gerrard, Darrell Bishop, David Goetz, Greg Lange, ''John Dickinson'', Michael Barton, OpenStack Hudson, Pete Zaitcev, Peter Portante, Samuel Merritt, gholt, paul luse || TBD || TBD || TBD || -- || TBD
|-
| Glance || Alex Meade, Alexander Tivelkov, Arnaud Legendre, Brian Lamar, Brian Waldon, Dan Prince, Eoghan Glynn, Erno Kuvaja, Fei Long Wang, Flavio Percoco, John Bresnahan, Mark Washenberger, OpenStack Hudson, Stuart McLaren, Zhi Yan Liu, Iccha Sethi, ''Nikhil Komawar'' || TBD || TBD || TBD || -- || TBD
|-
| Keystone || Brant Knudson, David Stanek, Dolph Mathews, Jamie Lennox, Lance Bragstad, ''Morgan Fainberg'', OpenStack Hudson, Steve Martinelli, A. Young, Guang Yee, Henry Nash || TBD || TBD || TBD || -- || TBD
|-
| Horizon || Akihiro Motoki, Ana Krivokapic, Cindy Lu, ''David Lyle'', Gabriel Hurley, Julie Pichon, Kieran Spear, Lin Hua Cheng, Matthias Runge, Radomir Dopieralski, Tatiana Ovchinnikova, Thai Tran, Tihomir Trifonov, Zhenguo Niu || TBD || TBD || TBD || -- || TBD
|-
| Neutron || Aaron Rosen, Akihiro Motoki, Armando Migliaccio, Carl Baldwin, Edgar Magana, Henry Gessau, Kevin Benton, ''Kyle Mestery'', Maru Newby, Oleg Bondarev, Salvatore Orlando, Gary Kotton, Mark McClain || TBD || TBD || TBD || -- || TBD
|-
| Cinder || Avishay Traeger, Duncan Thomas, Eric Harney, Huang Zhiteng, Jay Bryant, John Griffith, ''Mike Perez'', Walter A. Boring IV, Xing Yang || TBD || TBD || TBD || -- || TBD
|-
| Ceilometer || Angus Salkeld, Dina Belova, Doug Hellmann, ''Eoghan Glynn'', Ildiko Vancsa, Julien Danjou, Lianhao Lu, Mehdi Abaakouk, Nadya Privalova, Nejc Saje, Nick Barcet, Gordon Chung || TBD || TBD || TBD || -- || TBD
|-
| Heat || ''Angus Salkeld'', Bartosz Górski, Clint 'SpamapS' Byrum, Jason Dunsmore, Jeff Peeler, Pavlo Shchelokovskyy, Randall Burt, Sergey Kraynev, Steve Baker, Steven Hardy, Thomas Herve, Thomas Spatzier, Zane Bitter || TBD || TBD || TBD || -- || TBD
|-
| Trove || Auston McReynolds, Craig Vyvial, Michael Basnight, ''Nikhil Manchanda'', Tim Simpson, Vipul Sabhaya, Amrith (Tesora), Iccha Sethi || TBD || TBD || TBD || -- || TBD
|-
| Ironic || Chris Krelle, David Shrewsbury, ''Devananda van der Veen'', Dmitry Tantsur, Haomeng,Wang, Jim Rollenhagen, Lucas Alvares, Ruby Loo, Yuriy Zveryanskyy, Lifeless || TBD || TBD || TBD || -- || TBD
|-
| Sahara || Alexander Ignatov, Andrew Lazarev, John Speidel, Matthew Farrellee, Michael McCune, ''Sergey Lukjanov'', Sergey Reshetnyak, Trevor McKay || TBD || TBD || TBD || -- || TBD
|}
----
[[Category:Documentation]]

== Bug Bash ==
#Whenː 01/23/2014
#Whereː online
=== Logistics ===

Open Bugsː [https://bugs.launchpad.net/openstack/+bugs?field.tag=ha-guide Link]
# Tag to useː ha-guide

Suggested Priority

Documentation/HA Guide Update

2015-01-22T21:02:26Z

Sriramhere: /* HA Guide Update */

= HA Guide Update =

== What ==

Let's update the OpenStack HA Guide. Based on direction from Anne Gentile, we will follow a similar path as the Security Guide -- subject matter experts working with core docs team members for reviews.

In addition to addressing the bug list (https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide), this effort will update all aspects of the guide to be more current and provide richer information and advice about OpenStack HA.

We've created an [https://etherpad.openstack.org/p/openstack-haguide-update etherpad] to capture ideas and start to form a plan for what is going to be updated, in what way, and who is responsible.

== Next Meeting ==
Thursday, January 22 at 9:00 pm UTC on #openstack-meeting-3

Agenda
# Update on ACTION items from last meeting
## ACTION (All): Update wiki with the project that you are investigating
## ACTION (Sriram): Check how we can get this meeting on the OpenStack Calendar
## ACTION (Sriram): Can we move meetings to an official IRC channel
# Bug bash on January 23 focused on [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide existing bugs]

== Past Meetings ==
Thursday, January 15 on #openstack-haguide ([https://etherpad.openstack.org/p/20150115-ha-guide-update-meeting irc log])
# Regular meeting time
# [https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=ha-guide Existing bugs] - Plan to resolve
# Need an owner for finding out from PTLs which projects work in a/a or a/p

Wednesday, October 29 on #openstack-haguide ([https://etherpad.openstack.org/p/20141029-ha-guide-update-meeting irc log])

== Where ==
Join the group in #openstack-haguide to chat about this effort. Regular meetings are for 30 minutes on each Thursday at 3pm US Central.

== Project HA Status Tracker ==
This section is intended to be used by the HA Guide Update team to track HA considerations for OpenStack integrated projects (created due to a request during the 01/15/15 meeting). This information will be used as we build an updated TOC and also help determine content for each project. Integrated projects information obtained from [https://github.com/openstack/governance/blob/master/reference/programs.yaml programs.yaml].
{| class="wikitable sortable"
|-
! OpenStack Project !! Core Members (Italic = PTL) !! API HA Status !! Service HA Status !! Metadata HA Status !! Additional Comments !! Section Completed By
|-
| Sample || John Doe, ''Jane Doe'' || Active/Active || Active/Passive || Not Applicable || Leverages HA Proxy for API HA || Shamail T.
|-
| Nova || Andrew Laski, Christopher Yeoh, Dan Smith, Daniel Berrange, Jay Pipes, Joe Gordon, John Garbutt, Ken'ichi Ohmichi, Kevin L. Mitchell, Matt Dietz, Matt Riedemann, ''Michael Still'', Nikola Dipanov, OpenStack Hudson, Russell Bryant, Sean Dague || TBD || TBD || TBD || -- || TBD
|-
| Swift || Alistair Coles, Chmouel Boudjnah, Christian Schwede, Chuck Thier, Clay Gerrard, Darrell Bishop, David Goetz, Greg Lange, ''John Dickinson'', Michael Barton, OpenStack Hudson, Pete Zaitcev, Peter Portante, Samuel Merritt, gholt, paul luse || TBD || TBD || TBD || -- || TBD
|-
| Glance || Alex Meade, Alexander Tivelkov, Arnaud Legendre, Brian Lamar, Brian Waldon, Dan Prince, Eoghan Glynn, Erno Kuvaja, Fei Long Wang, Flavio Percoco, John Bresnahan, Mark Washenberger, OpenStack Hudson, Stuart McLaren, Zhi Yan Liu, Iccha Sethi, ''Nikhil Komawar'' || TBD || TBD || TBD || -- || TBD
|-
| Keystone || Brant Knudson, David Stanek, Dolph Mathews, Jamie Lennox, Lance Bragstad, ''Morgan Fainberg'', OpenStack Hudson, Steve Martinelli, A. Young, Guang Yee, Henry Nash || TBD || TBD || TBD || -- || TBD
|-
| Horizon || Akihiro Motoki, Ana Krivokapic, Cindy Lu, ''David Lyle'', Gabriel Hurley, Julie Pichon, Kieran Spear, Lin Hua Cheng, Matthias Runge, Radomir Dopieralski, Tatiana Ovchinnikova, Thai Tran, Tihomir Trifonov, Zhenguo Niu || TBD || TBD || TBD || -- || TBD
|-
| Neutron || Aaron Rosen, Akihiro Motoki, Armando Migliaccio, Carl Baldwin, Edgar Magana, Henry Gessau, Kevin Benton, ''Kyle Mestery'', Maru Newby, Oleg Bondarev, Salvatore Orlando, Gary Kotton, Mark McClain || TBD || TBD || TBD || -- || TBD
|-
| Cinder || Avishay Traeger, Duncan Thomas, Eric Harney, Huang Zhiteng, Jay Bryant, John Griffith, ''Mike Perez'', Walter A. Boring IV, Xing Yang || TBD || TBD || TBD || -- || TBD
|-
| Ceilometer || Angus Salkeld, Dina Belova, Doug Hellmann, ''Eoghan Glynn'', Ildiko Vancsa, Julien Danjou, Lianhao Lu, Mehdi Abaakouk, Nadya Privalova, Nejc Saje, Nick Barcet, Gordon Chung || TBD || TBD || TBD || -- || TBD
|-
| Heat || ''Angus Salkeld'', Bartosz Górski, Clint 'SpamapS' Byrum, Jason Dunsmore, Jeff Peeler, Pavlo Shchelokovskyy, Randall Burt, Sergey Kraynev, Steve Baker, Steven Hardy, Thomas Herve, Thomas Spatzier, Zane Bitter || TBD || TBD || TBD || -- || TBD
|-
| Trove || Auston McReynolds, Craig Vyvial, Michael Basnight, ''Nikhil Manchanda'', Tim Simpson, Vipul Sabhaya, Amrith (Tesora), Iccha Sethi || TBD || TBD || TBD || -- || TBD
|-
| Ironic || Chris Krelle, David Shrewsbury, ''Devananda van der Veen'', Dmitry Tantsur, Haomeng,Wang, Jim Rollenhagen, Lucas Alvares, Ruby Loo, Yuriy Zveryanskyy, Lifeless || TBD || TBD || TBD || -- || TBD
|-
| Sahara || Alexander Ignatov, Andrew Lazarev, John Speidel, Matthew Farrellee, Michael McCune, ''Sergey Lukjanov'', Sergey Reshetnyak, Trevor McKay || TBD || TBD || TBD || -- || TBD
|}
----
[[Category:Documentation]]

== Bug Bash ==
#Whenː 01/23/2014
#Whereː online
=== Logistics ===

Meetings

2015-01-19T17:35:29Z

Sriramhere: /* HA Guide Update Meeting */

The OpenStack project holds its various public meetings on '''IRC''', in the <code><nowiki>#openstack-meeting</nowiki></code>, <code><nowiki>#openstack-meeting-alt</nowiki></code>, <code><nowiki>#openstack-meeting-3</nowiki></code>, and <code><nowiki>#openstack-meeting-4</nowiki></code> channels on Freenode. Everyone is encouraged to attend. [http://webchat.freenode.net?randomnick=1&channels=%23openstack-meeting%2C%23openstack-meeting-alt%2C%23openstack-meeting-3%2C%23openstack-meeting-4&prompt=1&uio=d4 Connect to IRC via webclient].

Some guidance on how to create a meeting can be found here: [[Meetings/CreateaMeeting]]

You can also access the [https://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4@group.calendar.google.com/public/basic.ics iCal feed for all OpenStack meetings].

== OpenStack Cross-Project meeting ==
* Weekly on Tuesdays at 2100 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[ThierryCarrez]]
* See [[Meetings/CrossProjectMeeting]] for details

== Technical Committee meeting ==
* Weekly on Tuesdays at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[ThierryCarrez]]
* See [[Meetings/TechnicalCommittee]] for details

== OpenStack Compute (Nova) ==
=== Nova team Meeting ===
* Weekly on Thursdays, alternating times - 1400 UTC and 2100 UTC
** For 2014 - odd weeks at 1400, even weeks at 2100 (date "+%U")
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Michael Still (even weeks), John Garbutt (odd weeks)
* See [[Meetings/Nova]] for an agenda

=== Nova Bug Scrub Meeting ===
* Weekly on Wednesday at 1630 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more information): Tracy Jones
* See [[Meetings/NovaBugScrub]] for an agenda

=== XenAPI team meeting ===
* Weekly on Wednesdays at 1500 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by: [[JohnGarbutt]]
* See [[Meetings/XenAPI]] for agenda

=== Nova Hyper-V team meeting ===
* Weekly on Tuesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by primeministerp (Peter Pouliot)
* See [[Meetings/Hyper-V|Meetings/Hyper-V]] for agenda and details

=== Gantt (Scheduler) team meeting ===
* Weekly on Tuesdays at 1500 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): n0ano (Don Dugger)
* See [[Meetings/Scheduler]] for details

=== VMwareAPI team meeting ===
* Weekly on Wednesdays at 1700 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: [[TracyJones]]
* See [[Meetings/VMwareAPI]] for details

=== PCI Passthrough Meeting ===
* Weekly on Tuesday at [http://www.worldclock.com/world_clock.html 1300 UTC]
* Will change back to once weekly after agreements are reached.
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: baoli (Robert Li)
* See [[Meetings/Passthrough]] for details

=== Nova API meeting ===
* Weekly on Friday at 00:00 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: Chris Yeoh
* See [[Meetings/NovaAPI]] for details

=== Libvirt Meeting ===
* Weekly on Tuesday at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=00&sec=0p1=0 15:00 UTC]
* IRC channel <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: Daniel Berrange (IRC: danpb)
* See [[Meetings/Libvirt]] for details

=== Nova Cellsv2 Meeting ===
* Weekly on Wednesdays, alternating times - [http://www.timeanddate.com/worldclock/fixedtime.html?hour=17&min=00&sec=0p1=0 17:00 UTC] and [http://www.timeanddate.com/worldclock/fixedtime.html?hour=22&min=00&sec=0p1=0 22:00 UTC]
* IRC channel <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: Andrew Laski (IRC: alaski)
* See [[Meetings/NovaCellsv2]] for details

== Documentation team meeting ==
* Every other Wednesday at alternating times, see [[Meetings/DocTeamMeeting]]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[AnneGentle]]
* See [[Meetings/DocTeamMeeting]] for an agenda

===HA Guide Update Meeting ===
* Every Thursday at 21:00 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more information): [[MattGriffin]]
* see [https://etherpad.openstack.org/p/openstack-haguide-update Etherpad] for an agenda

== Project Infrastructure team meeting ==
* Weekly on Tuesdays at 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[User:Corvus|James E. Blair (jeblair)]]
* See [[Meetings/InfraTeamMeeting]] for an agenda

== QA team meeting ==
* Weekly on Thursdays at 1700/2200 UTC (alternating)
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Matt Treinish
* See [[Meetings/QATeamMeeting]] for an agenda

== DefCore / RefStack Development Meeting ==
* Weekly on Mondays at 1100 Pacific / 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* PTL: David Lenwell
* DefCore Chairs (to contact for more information): Rob "zehicle" Hirschfeld & Joshua McKenty
* See [[Meetings/DefCore]] for an agenda

== DefCore Progress Update Meeting ==
* 4/1 DefCore meeting, 2pm PST, 90 minutes
* Agenda & Connection Details at https://etherpad.openstack.org/p/DefCoreElephant.7
* Chairs (to contact for more information): Rob "@zehicle" Hirschfeld & Joshua McKenty
* 6/12/2014 DefCore.lighthouseF2F 10am-3pm Details at https://etherpad.openstack.org/p/DefCoreLighthouse.F2F

== State management team meeting ==
* Weekly on Thursdays at 1900 UTC (http://weatherarc.com/utc-time-conversion)
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[Harlowja]]
* See [[Meetings/StateManagement]] for an agenda

== Keystone team meeting ==
* Weekly on Tuesdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Morgan Fainberg (morganfainberg)
* See [[Meetings/KeystoneMeeting]] for an agenda

== Ironic (Bare Metal) team meeting ==
* Alternating weeks on Mondays at 1700 UTC or Tuesday at 0500 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more infomation) Devananda van der Veen (devananda)
* see [[Meetings/Ironic]] for agenda

== TripleO team meeting ==
* Weekly on Tuesdays at 1900 UTC or Wednesdays at 0800 UTC (alternate weeks) (see the [https://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4@group.calendar.google.com/public/basic.ics iCal feed] to check the time this week)
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more infomation) Clint Byrum (spamaps)
* see [[Meetings/TripleO]] for agenda

== TripleO/Kolla team meeting ==
* Weekly on Mondays at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more infomation) Steven Dake (sdake)
* see [[Meetings/Kolla]] for agenda

== OpenStack Networking (Neutron) ==
=== Neutron team meeting ===
* Weekly alternating between Mondays at 2100 UTC and Tuesdays at 1400 UTC.
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> Mondays, <code><nowiki>#openstack-meeting</nowiki></code> Tuesdays
* Chair (to contact for more information) Kyle Mestery (mestery)
* see [[Network/Meetings]] for agenda

=== LBaaS meeting ===
* Weekly on Tuesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair (to contact for more information) mestery (Kyle Mestery)
* see [[Network/LBaaS]] for agenda

=== Octavia meeting ===
* Weekly on Wednesdays at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information) sbalukoff (Stephen Balukoff)
* see [[Octavia/Weekly Meeting Agenda]] for agenda

=== ML2 Network sub-team meeting ===
* Weekly on Wednesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): rkukura/Suhkdev (Bob Kukura / Sukhdev Kapur)
* See [[Meetings/ML2]] for details

=== Firewall as a Service (FWaaS) team meeting ===
* Weekly on Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenStack+Neutron+FWaaS+IRC&iso=20140326T1830&p1=1440&ah=1 1830 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: snaiksat (Sumit Naiksatam)
* See [[Meetings/FWaaS]] for details

=== Neutron Advanced Services' team meeting ===
* Weekly on Tuesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Neutron+Advanced+Services&iso=20141111T17&p1=1440 1700 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: snaiksat (Sumit Naiksatam)
* See [[Meetings/AdvancedServices]] for details

=== Neutron IPv6 sub-team Meeting ===
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: sc68cal (Sean M. Collins)
* See [[Meetings/Neutron-IPv6-Subteam]] for details

=== Neutron Group Policy Sub-Team Meeting ===
* Weekly on Thursdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: SumitNaiksatam (Sumit Naiksatam)
* See [[Meetings/Neutron_Group_Policy]] for details

=== Neutron Distributed Virtual Router meeting ===
* Weekly on Wednesdays at [http://www.worldclock.com/world_clock.html 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair:Swami (Swaminathan Vasudevan)
* See [[Meetings/Distributed-Virtual-Router]] for details

=== Neutron blueprint ovs-firewall-driver Meeting ===
* Tentative: Monday, December 16 at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: asadoughi (Amir Sadoughi)
* Agenda: See [[Meetings/Neutron_blueprint_ovs-firewall-driver]]

=== Neutron L3 Sub Team Meeting ===
* Weekly on Thursday at 1500 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: carl_baldwin (Carl Baldwin)
* Agenda: See [[Meetings/Neutron-L3-Subteam]]

=== Neutron ServiceVM framework Sub Team Meeting ===
* Weekly on Wednesdays at 1700UTC from Nov 19, 2014
(Time slot/channel was changed from Nov 19, 2014.)
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: yamahata (Isaku Yamahata)
* Agenda: See [[Meetings/ServiceVM]]

=== neutron-drivers weekly IRC meeting ===
* Weekly on Wednesdays at 1530-1630 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: mestery (Kyle Mestery)
* Agenda: See [[Meetings/NeutronDrivers]]

=== VPN as a Service (VPNaaS) team meeting ===
* Weekly on Tuesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenStack+Neutron+VPNaaS+IRC&iso=20140326T1500&p1=1440&ah=1 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: pc_m (Paul Michali)
* See [[Meetings/VPNaaS]] for details

=== Networking L2 Gateway meeting ===
* Bi-weekly on Mondays (Every other Monday starting from January 5, 2015) at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): armax/Suhkdev (Armando Migliaccio / Sukhdev Kapur)
* See [[Meetings/L2Gateway]] for details

=== Nova-net to Neutron Migration meeting ===
* Weekly Tuesdays at 0900 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> Tuesdays
* Chair (to contact for more information) Anita Kuno (anteaya)
* see [[Meetings/Nova-nettoNeutronMigration]] for agenda

== Cinder team meeting ==
* Weekly on Wednesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by [[JohnGriffith]]
* see [[CinderMeetings]] for agenda

== Ceilometer team meeting ==
* '''Every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by eglynn (Eoghan Glynn)
* see [[Meetings/Ceilometer]] for details

== Designate (DNSaaS) meeting ==
* Weekly Wednesdays at 1700 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): Kiall Mac Innes (kiall)
* See [[Meetings/Designate]] for details

== Trove (DBaaS) meeting ==
* Weekly on Wednesdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): [https://launchpad.net/~slicknik Nikhil Manchanda] (SlickNik) / [https://launchpad.net/~hubcap Michael Basnight] (hub_cap) / [https://launchpad.net/~vipuls Vipul Sabhaya] (vipul) / [https://launchpad.net/~tim-simpson Tim Simpson] (grapex) / [https://launchpad.net/~amcrn Auston McReynolds] (amcrn) / [https://launchpad.net/~cp16net Craig Vyvial] (cp16net)
* See [[Meetings/TroveMeeting]] for details
* For BP Meeting, please see [[Meetings/TroveBPMeeting]] for more details

== Zaqar (Messaging and Notification) team meeting ==
* Weekly on Mondays, alternating between 2100 UTC and 1500 UTC (starting with 2100 UTC on 8/4)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more information): Flavio Percoco (flaper87), Kurt Griffiths (kgriffs)
* See [[Meetings/Zaqar]] for details

== OpenStack Data Processing (Sahara) team meeting ==
* Weekly on Thursdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more info): SergeyLukjanov (Sergey Lukjanov)
* See [[Meetings/SaharaAgenda]] for details

== Mistral meeting ==
* Weekly on Mondays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: rakhmerov (Renat Akhmerov)
* See [[Meetings/MistralAgenda]] for details

== Murano meeting ==
* Weekly on Tuesday at 1700 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: Serg Melikyan (sergmelikyan)
* See [[Meetings/MuranoAgenda]] for details

== Heat (orchestration) team meeting ==
* Weekly on Wednesdays at 2000 UTC or 1200 UTC (on alternate weeks)
* IRC Channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Zane Bitter (zaneb)
* See [[Meetings/HeatAgenda]] for details

== Horizon team meeting ==
* Weekly on Wednesdays at 2000 UTC or 1200 UTC (on alternate weeks)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: David Lyle (david-lyle)
* See [[Meetings/Horizon]] for details

== Swift team meeting ==
* Weekly on Wednesdays at 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: notmyname (John Dickinson)
* See [[Meetings/Swift]] for details

== OpenStack Security Group (OSSG) meeting ==
* Weekly on Thursdays at 1700 UTC (1 hour duration)
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): hyakuhei (Rob Clark)
* See [[Meetings/OpenStackSecurity]] for an agenda

== Python3 Compatibility Team meeting ==
* Not planned anymore
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): jd_ (Julien Danjou)
* See [[Meetings/Python3]] for details

== Glance Team meeting ==
* Weekly on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=14&min=0&sec=0 1400]/[http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC] (alternating)
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair (to contact for more information): nikhil_k (Nikhil Komawar)
* See [[Meetings/Glance]] for details

== Oslo Team meeting ==

* Juno
** Every Friday at 1600 UTC ([http://www.timeanddate.com/worldclock/converted.html?iso=20140425T16&p1=0&p2=2133&p3=195&p4=224 timeanddate.com])
** IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
** Chair (to contact for more information): dhellmann (Doug Hellmann)
** See [[Meetings/Oslo]] for details
* Kilo (beginning 17 Nov 2014)
** Every Monday at 1600 UTC ([http://www.timeanddate.com/worldclock/converted.html?iso=20141117T16&p1=0&p2=2133&p3=195&p4=224 timeanddate.com])
** IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
** Chair (to contact for more information): dhellmann (Doug Hellmann)
** See [[Meetings/Oslo]] for details

== OpenStack Community Office Hours ==
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 0800 UTC] and on Fridays at [http://www.worldclock.com/world_clock.html 1800 UTC]
* IRC channel: <code><nowiki>#openstack-community</nowiki></code>
* Chair: fifieldt ([http://www.openstack.org/community/members/profile/369 Tom Fifield]) and reed ([http://www.openstack.org/community/members/profile/1372 Stefano Maffulli])
* See [[Meetings/Community]] for details

== I18N Team meeting ==
* Bi-weekly on Thursday, at 0800 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: daisy
* See [[Meetings/I18nTeamMeeting]] for details

== Training-guides Team meeting ==
* Weekly on Monday at [http://www.timeanddate.com/time/zone/usa/san-francisco 1700 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: sarob
* See [[Meetings/training-guides]] for details

== Trainers Team meeting ==
* Weekly on Wednesday at [http://www.timeanddate.com/time/zone/usa/san-francisco 1800 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: sarob
* See [[Meetings/trainers]] for details

== Manila Team meeting ==
* Weekly on Thursday at [http://www.worldclock.com/current-local-time-in-san-francisco_598.htm 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: bswartz
* See [[Manila/Meetings]] for details

== Blazar (Reservations) team meeting ==
* Weekly on Fridays at [http://www.worldclock.com/world_clock.html 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: bauzas (Sylvain Bauza), DinaBelova (Dina Belova)
* See [[Meetings/Blazar]] for details

== Rally meeting ==
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1700 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair:boris-42 (Boris Pavlovic)
* See [[Meetings/Rally]] for details

== Solum Team Meeting ==
* Weekly on Tuesdays at 2100 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: adrian_otto (Adrian Otto)
* See [[Meetings/Solum]] for details

== Congress Team Meeting ==
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1700 UTC], e.g. Feb 25, 2014
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: pballand (Pete Balland) or thinrichs (Tim Hinrichs)
* See [[Meetings/Congress]] for details

== Barbican Meeting ==
* Weekly on Mondays at [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130502T2000 2000 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): jraim (#openstack-barbican @ Freenode)
* See [[Meetings/Barbican]] for an agenda

== Chef Cookbook meetings ==
* Google Hangout Weekly on Mondays at 1530 UTC
* IRC channel Weekly on Fridays at 1530 UTC: <code><nowiki>#openstack-chef</nowiki></code>
* Chair: JJ Asghar
* See [[Meetings/ChefCookbook]] for details

== StoryBoard Meeting ==
* Weekly on Mondays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: krotscheck, ttx, or NikitaKonovalov
* See [[StoryBoard]] for details

== Hierarchical Multitenancy Meeting ==
* Weekly on Friday at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: vishy/schwicke
* See [[Meetings/HierarchicalMultitenancyMeeting]] for details

== python-openstacksdk Meeting ==
* Weekly on Tuesdays at [http://www.worldtimebuddy.com/?qm=1&lid=6,0,4726206,100&h=6&date=2014-2-11&sln=13-14 1900 UTC] starting 2/19/2014
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: jnoller
* See [[PythonOpenStackSDK]] for details

== Satori Team Meeting ==
* Weekly on Mondays at [http://www.worldtimebuddy.com/?qm=1&lid=6,0,4726206,100&h=6&date=2014-2-11&sln=9-10 1500 UTC] starting Feb 24, 2014
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: Ziad_Sawalha
* See [[Meetings/Satori]] for details

== Fuel Team Meeting ==
* Weekly on Thursdays at [http://www.worldtimebuddy.com/?qm=1&lid=100&h=100&date=2014-3-27&sln=16-17 1600 UTC] starting Feb 27, 2014
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: vkozhukalov
* See [[Meetings/Fuel]] for details

== Third Party Meeting ==
Meeting for any component to address Third Party needs
** Two times weekly: Mondays at 1500 UTC as well as Tuesdays at 0800 UTC
** IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
** Chair: anteaya
** See [[Meetings/ThirdParty]] for details
* Working Group: improve the consumability of CI components and documentation (starting January 7th, 2015)
** Weekly on Wednesdays at 1500/0400 UTC (alternating)
** IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
** Chair: krtaylor
** See [[Meetings/ThirdParty]] for details

== MagnetoDB Team meeting ==
* Weekly on Thursdays at 1400 UTC
* IRC channel: <code><nowiki>#magnetodb</nowiki></code>
* Chair: isviridov

== Telco Working Group Meeting ==
* Weekly alternating on Wednesdays alternating between 1400 UTC and 2200 UTC.
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code> (@ 1400 UTC) and <code><nowiki>#openstack-meeting</nowiki></code> (@ 2200 UTC)
* Chair: Stephen Gordon (steveg)
* See [[https://wiki.openstack.org/wiki/TelcoWorkingGroup]] or join #openstack-nfv for details.

== Containers Team Meeting ==
* Weekly on Tuesdays at 1600/2200 UTC (alternating)
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: adrian_otto (Adrian Otto)
* See [[Meetings/Containers]] for details

== User Experience (UX) Team Meeting ==
* Every second week on Mondays at 1700 UTC starting July 7th, 2014 (even weeks)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: jcoufal (Jaromir Coufal)
* See [[Meetings/UX]] for details

== Tetris Team Meeting ==
* Bi-Weely at 0100 UTC
* IRC channel: <code><nowiki>#tetris</nowiki></code>
* Chair: Jay (liugya@cn.ibm.com jay.lau.513@gmail.com)
* See [[Meetings/Tetris]] for details

== Poppy Team Meeting ==
* Weekly on Thursdays at 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code> starting August 7, 2014
* Chair: amitgandhinz (amit.gandhi@rackspace.com)
* See [[Meetings/Poppy]] for details

== Puppet OpenStack Team Meeting ==
* Weekly on Monday at 1400 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> starting October 27, 2014
* Chair: crinkle (colleen@puppetlabs.com)
* See [[Meetings/PuppetOpenStack]] for details

== API Work Group Team Meeting ==
* Weekly on Thursdays at 16:00UTC/00:00 UTC (alternating)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code> starting October 30, 2014
* Chair:
* See [[Meetings/API-WG]] for details

== Swift-on-File ==
* Weekly on Thursday at 1400 UTC
* IRC channel: <code><nowiki>#swiftonfile</nowiki></code>
* Chair: tdasilva (Thiago da Silva)
* See [[Meetings/swiftonfile]] for details

== Openstack Operators Team Meeting ==
* Weekly on Wednesday at 1800 UTC (next meeting is January 7)
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: mfisch (Matt Fischer)
* See [[Meetings/openstack-operators]] for details

== OpenStack Ambassadors Meeting ==
* Alternating Weekly on first, third, fifth Tuesdays at [http://www.timeanddate.com/time/zone/usa/san-francisco 08:00 GMT] and second and fourth Fridays at [http://www.timeanddate.com/time/zone/usa/san-francisco 18:00 GMT]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: sarob
* See [[Meetings/ambassadors]] for details

== Openstack Ansible Deployment ==
* Weekly on Thursday at [http://www.timeanddate.com/time/zone/usa/san-antonio 1600 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: cloudnull (Kevin Carter)
* See [[Meetings/openstack-ansible]] for details

[[Category:Contribute]]
[[Category:Connect]]
[[Category:Resources]]

Meetings

2015-01-19T17:34:43Z

Sriramhere: /* HA Guide Update Meeting */

The OpenStack project holds its various public meetings on '''IRC''', in the <code><nowiki>#openstack-meeting</nowiki></code>, <code><nowiki>#openstack-meeting-alt</nowiki></code>, <code><nowiki>#openstack-meeting-3</nowiki></code>, and <code><nowiki>#openstack-meeting-4</nowiki></code> channels on Freenode. Everyone is encouraged to attend. [http://webchat.freenode.net?randomnick=1&channels=%23openstack-meeting%2C%23openstack-meeting-alt%2C%23openstack-meeting-3%2C%23openstack-meeting-4&prompt=1&uio=d4 Connect to IRC via webclient].

Some guidance on how to create a meeting can be found here: [[Meetings/CreateaMeeting]]

You can also access the [https://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4@group.calendar.google.com/public/basic.ics iCal feed for all OpenStack meetings].

== OpenStack Cross-Project meeting ==
* Weekly on Tuesdays at 2100 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[ThierryCarrez]]
* See [[Meetings/CrossProjectMeeting]] for details

== Technical Committee meeting ==
* Weekly on Tuesdays at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[ThierryCarrez]]
* See [[Meetings/TechnicalCommittee]] for details

== OpenStack Compute (Nova) ==
=== Nova team Meeting ===
* Weekly on Thursdays, alternating times - 1400 UTC and 2100 UTC
** For 2014 - odd weeks at 1400, even weeks at 2100 (date "+%U")
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Michael Still (even weeks), John Garbutt (odd weeks)
* See [[Meetings/Nova]] for an agenda

=== Nova Bug Scrub Meeting ===
* Weekly on Wednesday at 1630 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more information): Tracy Jones
* See [[Meetings/NovaBugScrub]] for an agenda

=== XenAPI team meeting ===
* Weekly on Wednesdays at 1500 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by: [[JohnGarbutt]]
* See [[Meetings/XenAPI]] for agenda

=== Nova Hyper-V team meeting ===
* Weekly on Tuesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by primeministerp (Peter Pouliot)
* See [[Meetings/Hyper-V|Meetings/Hyper-V]] for agenda and details

=== Gantt (Scheduler) team meeting ===
* Weekly on Tuesdays at 1500 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): n0ano (Don Dugger)
* See [[Meetings/Scheduler]] for details

=== VMwareAPI team meeting ===
* Weekly on Wednesdays at 1700 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: [[TracyJones]]
* See [[Meetings/VMwareAPI]] for details

=== PCI Passthrough Meeting ===
* Weekly on Tuesday at [http://www.worldclock.com/world_clock.html 1300 UTC]
* Will change back to once weekly after agreements are reached.
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: baoli (Robert Li)
* See [[Meetings/Passthrough]] for details

=== Nova API meeting ===
* Weekly on Friday at 00:00 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: Chris Yeoh
* See [[Meetings/NovaAPI]] for details

=== Libvirt Meeting ===
* Weekly on Tuesday at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=00&sec=0p1=0 15:00 UTC]
* IRC channel <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: Daniel Berrange (IRC: danpb)
* See [[Meetings/Libvirt]] for details

=== Nova Cellsv2 Meeting ===
* Weekly on Wednesdays, alternating times - [http://www.timeanddate.com/worldclock/fixedtime.html?hour=17&min=00&sec=0p1=0 17:00 UTC] and [http://www.timeanddate.com/worldclock/fixedtime.html?hour=22&min=00&sec=0p1=0 22:00 UTC]
* IRC channel <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: Andrew Laski (IRC: alaski)
* See [[Meetings/NovaCellsv2]] for details

== Documentation team meeting ==
* Every other Wednesday at alternating times, see [[Meetings/DocTeamMeeting]]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[AnneGentle]]
* See [[Meetings/DocTeamMeeting]] for an agenda

===HA Guide Update Meeting ===
* Every Thursday at 21:00 UTC, see [https://etherpad.openstack.org/p/openstack-haguide-update Etherpad]
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more information): [[MattGriffin]]
* See [[Meetings/DocTeamMeeting]] for an agenda

== Project Infrastructure team meeting ==
* Weekly on Tuesdays at 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[User:Corvus|James E. Blair (jeblair)]]
* See [[Meetings/InfraTeamMeeting]] for an agenda

== QA team meeting ==
* Weekly on Thursdays at 1700/2200 UTC (alternating)
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Matt Treinish
* See [[Meetings/QATeamMeeting]] for an agenda

== DefCore / RefStack Development Meeting ==
* Weekly on Mondays at 1100 Pacific / 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* PTL: David Lenwell
* DefCore Chairs (to contact for more information): Rob "zehicle" Hirschfeld & Joshua McKenty
* See [[Meetings/DefCore]] for an agenda

== DefCore Progress Update Meeting ==
* 4/1 DefCore meeting, 2pm PST, 90 minutes
* Agenda & Connection Details at https://etherpad.openstack.org/p/DefCoreElephant.7
* Chairs (to contact for more information): Rob "@zehicle" Hirschfeld & Joshua McKenty
* 6/12/2014 DefCore.lighthouseF2F 10am-3pm Details at https://etherpad.openstack.org/p/DefCoreLighthouse.F2F

== State management team meeting ==
* Weekly on Thursdays at 1900 UTC (http://weatherarc.com/utc-time-conversion)
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[Harlowja]]
* See [[Meetings/StateManagement]] for an agenda

== Keystone team meeting ==
* Weekly on Tuesdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Morgan Fainberg (morganfainberg)
* See [[Meetings/KeystoneMeeting]] for an agenda

== Ironic (Bare Metal) team meeting ==
* Alternating weeks on Mondays at 1700 UTC or Tuesday at 0500 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more infomation) Devananda van der Veen (devananda)
* see [[Meetings/Ironic]] for agenda

== TripleO team meeting ==
* Weekly on Tuesdays at 1900 UTC or Wednesdays at 0800 UTC (alternate weeks) (see the [https://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4@group.calendar.google.com/public/basic.ics iCal feed] to check the time this week)
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more infomation) Clint Byrum (spamaps)
* see [[Meetings/TripleO]] for agenda

== TripleO/Kolla team meeting ==
* Weekly on Mondays at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more infomation) Steven Dake (sdake)
* see [[Meetings/Kolla]] for agenda

== OpenStack Networking (Neutron) ==
=== Neutron team meeting ===
* Weekly alternating between Mondays at 2100 UTC and Tuesdays at 1400 UTC.
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> Mondays, <code><nowiki>#openstack-meeting</nowiki></code> Tuesdays
* Chair (to contact for more information) Kyle Mestery (mestery)
* see [[Network/Meetings]] for agenda

=== LBaaS meeting ===
* Weekly on Tuesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair (to contact for more information) mestery (Kyle Mestery)
* see [[Network/LBaaS]] for agenda

=== Octavia meeting ===
* Weekly on Wednesdays at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information) sbalukoff (Stephen Balukoff)
* see [[Octavia/Weekly Meeting Agenda]] for agenda

=== ML2 Network sub-team meeting ===
* Weekly on Wednesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): rkukura/Suhkdev (Bob Kukura / Sukhdev Kapur)
* See [[Meetings/ML2]] for details

=== Firewall as a Service (FWaaS) team meeting ===
* Weekly on Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenStack+Neutron+FWaaS+IRC&iso=20140326T1830&p1=1440&ah=1 1830 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: snaiksat (Sumit Naiksatam)
* See [[Meetings/FWaaS]] for details

=== Neutron Advanced Services' team meeting ===
* Weekly on Tuesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Neutron+Advanced+Services&iso=20141111T17&p1=1440 1700 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: snaiksat (Sumit Naiksatam)
* See [[Meetings/AdvancedServices]] for details

=== Neutron IPv6 sub-team Meeting ===
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: sc68cal (Sean M. Collins)
* See [[Meetings/Neutron-IPv6-Subteam]] for details

=== Neutron Group Policy Sub-Team Meeting ===
* Weekly on Thursdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: SumitNaiksatam (Sumit Naiksatam)
* See [[Meetings/Neutron_Group_Policy]] for details

=== Neutron Distributed Virtual Router meeting ===
* Weekly on Wednesdays at [http://www.worldclock.com/world_clock.html 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair:Swami (Swaminathan Vasudevan)
* See [[Meetings/Distributed-Virtual-Router]] for details

=== Neutron blueprint ovs-firewall-driver Meeting ===
* Tentative: Monday, December 16 at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: asadoughi (Amir Sadoughi)
* Agenda: See [[Meetings/Neutron_blueprint_ovs-firewall-driver]]

=== Neutron L3 Sub Team Meeting ===
* Weekly on Thursday at 1500 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: carl_baldwin (Carl Baldwin)
* Agenda: See [[Meetings/Neutron-L3-Subteam]]

=== Neutron ServiceVM framework Sub Team Meeting ===
* Weekly on Wednesdays at 1700UTC from Nov 19, 2014
(Time slot/channel was changed from Nov 19, 2014.)
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: yamahata (Isaku Yamahata)
* Agenda: See [[Meetings/ServiceVM]]

=== neutron-drivers weekly IRC meeting ===
* Weekly on Wednesdays at 1530-1630 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: mestery (Kyle Mestery)
* Agenda: See [[Meetings/NeutronDrivers]]

=== VPN as a Service (VPNaaS) team meeting ===
* Weekly on Tuesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenStack+Neutron+VPNaaS+IRC&iso=20140326T1500&p1=1440&ah=1 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: pc_m (Paul Michali)
* See [[Meetings/VPNaaS]] for details

=== Networking L2 Gateway meeting ===
* Bi-weekly on Mondays (Every other Monday starting from January 5, 2015) at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): armax/Suhkdev (Armando Migliaccio / Sukhdev Kapur)
* See [[Meetings/L2Gateway]] for details

=== Nova-net to Neutron Migration meeting ===
* Weekly Tuesdays at 0900 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> Tuesdays
* Chair (to contact for more information) Anita Kuno (anteaya)
* see [[Meetings/Nova-nettoNeutronMigration]] for agenda

== Cinder team meeting ==
* Weekly on Wednesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by [[JohnGriffith]]
* see [[CinderMeetings]] for agenda

== Ceilometer team meeting ==
* '''Every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by eglynn (Eoghan Glynn)
* see [[Meetings/Ceilometer]] for details

== Designate (DNSaaS) meeting ==
* Weekly Wednesdays at 1700 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): Kiall Mac Innes (kiall)
* See [[Meetings/Designate]] for details

== Trove (DBaaS) meeting ==
* Weekly on Wednesdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): [https://launchpad.net/~slicknik Nikhil Manchanda] (SlickNik) / [https://launchpad.net/~hubcap Michael Basnight] (hub_cap) / [https://launchpad.net/~vipuls Vipul Sabhaya] (vipul) / [https://launchpad.net/~tim-simpson Tim Simpson] (grapex) / [https://launchpad.net/~amcrn Auston McReynolds] (amcrn) / [https://launchpad.net/~cp16net Craig Vyvial] (cp16net)
* See [[Meetings/TroveMeeting]] for details
* For BP Meeting, please see [[Meetings/TroveBPMeeting]] for more details

== Zaqar (Messaging and Notification) team meeting ==
* Weekly on Mondays, alternating between 2100 UTC and 1500 UTC (starting with 2100 UTC on 8/4)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more information): Flavio Percoco (flaper87), Kurt Griffiths (kgriffs)
* See [[Meetings/Zaqar]] for details

== OpenStack Data Processing (Sahara) team meeting ==
* Weekly on Thursdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more info): SergeyLukjanov (Sergey Lukjanov)
* See [[Meetings/SaharaAgenda]] for details

== Mistral meeting ==
* Weekly on Mondays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: rakhmerov (Renat Akhmerov)
* See [[Meetings/MistralAgenda]] for details

== Murano meeting ==
* Weekly on Tuesday at 1700 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: Serg Melikyan (sergmelikyan)
* See [[Meetings/MuranoAgenda]] for details

== Heat (orchestration) team meeting ==
* Weekly on Wednesdays at 2000 UTC or 1200 UTC (on alternate weeks)
* IRC Channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Zane Bitter (zaneb)
* See [[Meetings/HeatAgenda]] for details

== Horizon team meeting ==
* Weekly on Wednesdays at 2000 UTC or 1200 UTC (on alternate weeks)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: David Lyle (david-lyle)
* See [[Meetings/Horizon]] for details

== Swift team meeting ==
* Weekly on Wednesdays at 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: notmyname (John Dickinson)
* See [[Meetings/Swift]] for details

== OpenStack Security Group (OSSG) meeting ==
* Weekly on Thursdays at 1700 UTC (1 hour duration)
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): hyakuhei (Rob Clark)
* See [[Meetings/OpenStackSecurity]] for an agenda

== Python3 Compatibility Team meeting ==
* Not planned anymore
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): jd_ (Julien Danjou)
* See [[Meetings/Python3]] for details

== Glance Team meeting ==
* Weekly on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=14&min=0&sec=0 1400]/[http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC] (alternating)
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair (to contact for more information): nikhil_k (Nikhil Komawar)
* See [[Meetings/Glance]] for details

== Oslo Team meeting ==

* Juno
** Every Friday at 1600 UTC ([http://www.timeanddate.com/worldclock/converted.html?iso=20140425T16&p1=0&p2=2133&p3=195&p4=224 timeanddate.com])
** IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
** Chair (to contact for more information): dhellmann (Doug Hellmann)
** See [[Meetings/Oslo]] for details
* Kilo (beginning 17 Nov 2014)
** Every Monday at 1600 UTC ([http://www.timeanddate.com/worldclock/converted.html?iso=20141117T16&p1=0&p2=2133&p3=195&p4=224 timeanddate.com])
** IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
** Chair (to contact for more information): dhellmann (Doug Hellmann)
** See [[Meetings/Oslo]] for details

== OpenStack Community Office Hours ==
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 0800 UTC] and on Fridays at [http://www.worldclock.com/world_clock.html 1800 UTC]
* IRC channel: <code><nowiki>#openstack-community</nowiki></code>
* Chair: fifieldt ([http://www.openstack.org/community/members/profile/369 Tom Fifield]) and reed ([http://www.openstack.org/community/members/profile/1372 Stefano Maffulli])
* See [[Meetings/Community]] for details

== I18N Team meeting ==
* Bi-weekly on Thursday, at 0800 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: daisy
* See [[Meetings/I18nTeamMeeting]] for details

== Training-guides Team meeting ==
* Weekly on Monday at [http://www.timeanddate.com/time/zone/usa/san-francisco 1700 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: sarob
* See [[Meetings/training-guides]] for details

== Trainers Team meeting ==
* Weekly on Wednesday at [http://www.timeanddate.com/time/zone/usa/san-francisco 1800 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: sarob
* See [[Meetings/trainers]] for details

== Manila Team meeting ==
* Weekly on Thursday at [http://www.worldclock.com/current-local-time-in-san-francisco_598.htm 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: bswartz
* See [[Manila/Meetings]] for details

== Blazar (Reservations) team meeting ==
* Weekly on Fridays at [http://www.worldclock.com/world_clock.html 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: bauzas (Sylvain Bauza), DinaBelova (Dina Belova)
* See [[Meetings/Blazar]] for details

== Rally meeting ==
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1700 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair:boris-42 (Boris Pavlovic)
* See [[Meetings/Rally]] for details

== Solum Team Meeting ==
* Weekly on Tuesdays at 2100 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: adrian_otto (Adrian Otto)
* See [[Meetings/Solum]] for details

== Congress Team Meeting ==
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1700 UTC], e.g. Feb 25, 2014
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: pballand (Pete Balland) or thinrichs (Tim Hinrichs)
* See [[Meetings/Congress]] for details

== Barbican Meeting ==
* Weekly on Mondays at [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130502T2000 2000 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): jraim (#openstack-barbican @ Freenode)
* See [[Meetings/Barbican]] for an agenda

== Chef Cookbook meetings ==
* Google Hangout Weekly on Mondays at 1530 UTC
* IRC channel Weekly on Fridays at 1530 UTC: <code><nowiki>#openstack-chef</nowiki></code>
* Chair: JJ Asghar
* See [[Meetings/ChefCookbook]] for details

== StoryBoard Meeting ==
* Weekly on Mondays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: krotscheck, ttx, or NikitaKonovalov
* See [[StoryBoard]] for details

== Hierarchical Multitenancy Meeting ==
* Weekly on Friday at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: vishy/schwicke
* See [[Meetings/HierarchicalMultitenancyMeeting]] for details

== python-openstacksdk Meeting ==
* Weekly on Tuesdays at [http://www.worldtimebuddy.com/?qm=1&lid=6,0,4726206,100&h=6&date=2014-2-11&sln=13-14 1900 UTC] starting 2/19/2014
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: jnoller
* See [[PythonOpenStackSDK]] for details

== Satori Team Meeting ==
* Weekly on Mondays at [http://www.worldtimebuddy.com/?qm=1&lid=6,0,4726206,100&h=6&date=2014-2-11&sln=9-10 1500 UTC] starting Feb 24, 2014
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: Ziad_Sawalha
* See [[Meetings/Satori]] for details

== Fuel Team Meeting ==
* Weekly on Thursdays at [http://www.worldtimebuddy.com/?qm=1&lid=100&h=100&date=2014-3-27&sln=16-17 1600 UTC] starting Feb 27, 2014
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: vkozhukalov
* See [[Meetings/Fuel]] for details

== Third Party Meeting ==
Meeting for any component to address Third Party needs
** Two times weekly: Mondays at 1500 UTC as well as Tuesdays at 0800 UTC
** IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
** Chair: anteaya
** See [[Meetings/ThirdParty]] for details
* Working Group: improve the consumability of CI components and documentation (starting January 7th, 2015)
** Weekly on Wednesdays at 1500/0400 UTC (alternating)
** IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
** Chair: krtaylor
** See [[Meetings/ThirdParty]] for details

== MagnetoDB Team meeting ==
* Weekly on Thursdays at 1400 UTC
* IRC channel: <code><nowiki>#magnetodb</nowiki></code>
* Chair: isviridov

== Telco Working Group Meeting ==
* Weekly alternating on Wednesdays alternating between 1400 UTC and 2200 UTC.
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code> (@ 1400 UTC) and <code><nowiki>#openstack-meeting</nowiki></code> (@ 2200 UTC)
* Chair: Stephen Gordon (steveg)
* See [[https://wiki.openstack.org/wiki/TelcoWorkingGroup]] or join #openstack-nfv for details.

== Containers Team Meeting ==
* Weekly on Tuesdays at 1600/2200 UTC (alternating)
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: adrian_otto (Adrian Otto)
* See [[Meetings/Containers]] for details

== User Experience (UX) Team Meeting ==
* Every second week on Mondays at 1700 UTC starting July 7th, 2014 (even weeks)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: jcoufal (Jaromir Coufal)
* See [[Meetings/UX]] for details

== Tetris Team Meeting ==
* Bi-Weely at 0100 UTC
* IRC channel: <code><nowiki>#tetris</nowiki></code>
* Chair: Jay (liugya@cn.ibm.com jay.lau.513@gmail.com)
* See [[Meetings/Tetris]] for details

== Poppy Team Meeting ==
* Weekly on Thursdays at 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code> starting August 7, 2014
* Chair: amitgandhinz (amit.gandhi@rackspace.com)
* See [[Meetings/Poppy]] for details

== Puppet OpenStack Team Meeting ==
* Weekly on Monday at 1400 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> starting October 27, 2014
* Chair: crinkle (colleen@puppetlabs.com)
* See [[Meetings/PuppetOpenStack]] for details

== API Work Group Team Meeting ==
* Weekly on Thursdays at 16:00UTC/00:00 UTC (alternating)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code> starting October 30, 2014
* Chair:
* See [[Meetings/API-WG]] for details

== Swift-on-File ==
* Weekly on Thursday at 1400 UTC
* IRC channel: <code><nowiki>#swiftonfile</nowiki></code>
* Chair: tdasilva (Thiago da Silva)
* See [[Meetings/swiftonfile]] for details

== Openstack Operators Team Meeting ==
* Weekly on Wednesday at 1800 UTC (next meeting is January 7)
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: mfisch (Matt Fischer)
* See [[Meetings/openstack-operators]] for details

== OpenStack Ambassadors Meeting ==
* Alternating Weekly on first, third, fifth Tuesdays at [http://www.timeanddate.com/time/zone/usa/san-francisco 08:00 GMT] and second and fourth Fridays at [http://www.timeanddate.com/time/zone/usa/san-francisco 18:00 GMT]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: sarob
* See [[Meetings/ambassadors]] for details

== Openstack Ansible Deployment ==
* Weekly on Thursday at [http://www.timeanddate.com/time/zone/usa/san-antonio 1600 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: cloudnull (Kevin Carter)
* See [[Meetings/openstack-ansible]] for details

[[Category:Contribute]]
[[Category:Connect]]
[[Category:Resources]]

Meetings

2015-01-19T17:33:58Z

Sriramhere: /* Documentation team meeting */

The OpenStack project holds its various public meetings on '''IRC''', in the <code><nowiki>#openstack-meeting</nowiki></code>, <code><nowiki>#openstack-meeting-alt</nowiki></code>, <code><nowiki>#openstack-meeting-3</nowiki></code>, and <code><nowiki>#openstack-meeting-4</nowiki></code> channels on Freenode. Everyone is encouraged to attend. [http://webchat.freenode.net?randomnick=1&channels=%23openstack-meeting%2C%23openstack-meeting-alt%2C%23openstack-meeting-3%2C%23openstack-meeting-4&prompt=1&uio=d4 Connect to IRC via webclient].

Some guidance on how to create a meeting can be found here: [[Meetings/CreateaMeeting]]

You can also access the [https://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4@group.calendar.google.com/public/basic.ics iCal feed for all OpenStack meetings].

== OpenStack Cross-Project meeting ==
* Weekly on Tuesdays at 2100 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[ThierryCarrez]]
* See [[Meetings/CrossProjectMeeting]] for details

== Technical Committee meeting ==
* Weekly on Tuesdays at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[ThierryCarrez]]
* See [[Meetings/TechnicalCommittee]] for details

== OpenStack Compute (Nova) ==
=== Nova team Meeting ===
* Weekly on Thursdays, alternating times - 1400 UTC and 2100 UTC
** For 2014 - odd weeks at 1400, even weeks at 2100 (date "+%U")
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Michael Still (even weeks), John Garbutt (odd weeks)
* See [[Meetings/Nova]] for an agenda

=== Nova Bug Scrub Meeting ===
* Weekly on Wednesday at 1630 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more information): Tracy Jones
* See [[Meetings/NovaBugScrub]] for an agenda

=== XenAPI team meeting ===
* Weekly on Wednesdays at 1500 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by: [[JohnGarbutt]]
* See [[Meetings/XenAPI]] for agenda

=== Nova Hyper-V team meeting ===
* Weekly on Tuesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by primeministerp (Peter Pouliot)
* See [[Meetings/Hyper-V|Meetings/Hyper-V]] for agenda and details

=== Gantt (Scheduler) team meeting ===
* Weekly on Tuesdays at 1500 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): n0ano (Don Dugger)
* See [[Meetings/Scheduler]] for details

=== VMwareAPI team meeting ===
* Weekly on Wednesdays at 1700 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: [[TracyJones]]
* See [[Meetings/VMwareAPI]] for details

=== PCI Passthrough Meeting ===
* Weekly on Tuesday at [http://www.worldclock.com/world_clock.html 1300 UTC]
* Will change back to once weekly after agreements are reached.
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: baoli (Robert Li)
* See [[Meetings/Passthrough]] for details

=== Nova API meeting ===
* Weekly on Friday at 00:00 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: Chris Yeoh
* See [[Meetings/NovaAPI]] for details

=== Libvirt Meeting ===
* Weekly on Tuesday at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=00&sec=0p1=0 15:00 UTC]
* IRC channel <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: Daniel Berrange (IRC: danpb)
* See [[Meetings/Libvirt]] for details

=== Nova Cellsv2 Meeting ===
* Weekly on Wednesdays, alternating times - [http://www.timeanddate.com/worldclock/fixedtime.html?hour=17&min=00&sec=0p1=0 17:00 UTC] and [http://www.timeanddate.com/worldclock/fixedtime.html?hour=22&min=00&sec=0p1=0 22:00 UTC]
* IRC channel <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: Andrew Laski (IRC: alaski)
* See [[Meetings/NovaCellsv2]] for details

== Documentation team meeting ==
* Every other Wednesday at alternating times, see [[Meetings/DocTeamMeeting]]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[AnneGentle]]
* See [[Meetings/DocTeamMeeting]] for an agenda

===HA Guide Update Meeting ===
* Every Thursday at 21:00 UTC, see [[Meetings/DocTeamMeeting]]
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more information): [[MattGriffin]]
* See [[Meetings/DocTeamMeeting]] for an agenda

== Project Infrastructure team meeting ==
* Weekly on Tuesdays at 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[User:Corvus|James E. Blair (jeblair)]]
* See [[Meetings/InfraTeamMeeting]] for an agenda

== QA team meeting ==
* Weekly on Thursdays at 1700/2200 UTC (alternating)
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Matt Treinish
* See [[Meetings/QATeamMeeting]] for an agenda

== DefCore / RefStack Development Meeting ==
* Weekly on Mondays at 1100 Pacific / 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* PTL: David Lenwell
* DefCore Chairs (to contact for more information): Rob "zehicle" Hirschfeld & Joshua McKenty
* See [[Meetings/DefCore]] for an agenda

== DefCore Progress Update Meeting ==
* 4/1 DefCore meeting, 2pm PST, 90 minutes
* Agenda & Connection Details at https://etherpad.openstack.org/p/DefCoreElephant.7
* Chairs (to contact for more information): Rob "@zehicle" Hirschfeld & Joshua McKenty
* 6/12/2014 DefCore.lighthouseF2F 10am-3pm Details at https://etherpad.openstack.org/p/DefCoreLighthouse.F2F

== State management team meeting ==
* Weekly on Thursdays at 1900 UTC (http://weatherarc.com/utc-time-conversion)
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): [[Harlowja]]
* See [[Meetings/StateManagement]] for an agenda

== Keystone team meeting ==
* Weekly on Tuesdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Morgan Fainberg (morganfainberg)
* See [[Meetings/KeystoneMeeting]] for an agenda

== Ironic (Bare Metal) team meeting ==
* Alternating weeks on Mondays at 1700 UTC or Tuesday at 0500 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more infomation) Devananda van der Veen (devananda)
* see [[Meetings/Ironic]] for agenda

== TripleO team meeting ==
* Weekly on Tuesdays at 1900 UTC or Wednesdays at 0800 UTC (alternate weeks) (see the [https://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4@group.calendar.google.com/public/basic.ics iCal feed] to check the time this week)
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more infomation) Clint Byrum (spamaps)
* see [[Meetings/TripleO]] for agenda

== TripleO/Kolla team meeting ==
* Weekly on Mondays at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more infomation) Steven Dake (sdake)
* see [[Meetings/Kolla]] for agenda

== OpenStack Networking (Neutron) ==
=== Neutron team meeting ===
* Weekly alternating between Mondays at 2100 UTC and Tuesdays at 1400 UTC.
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> Mondays, <code><nowiki>#openstack-meeting</nowiki></code> Tuesdays
* Chair (to contact for more information) Kyle Mestery (mestery)
* see [[Network/Meetings]] for agenda

=== LBaaS meeting ===
* Weekly on Tuesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair (to contact for more information) mestery (Kyle Mestery)
* see [[Network/LBaaS]] for agenda

=== Octavia meeting ===
* Weekly on Wednesdays at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information) sbalukoff (Stephen Balukoff)
* see [[Octavia/Weekly Meeting Agenda]] for agenda

=== ML2 Network sub-team meeting ===
* Weekly on Wednesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): rkukura/Suhkdev (Bob Kukura / Sukhdev Kapur)
* See [[Meetings/ML2]] for details

=== Firewall as a Service (FWaaS) team meeting ===
* Weekly on Wednesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenStack+Neutron+FWaaS+IRC&iso=20140326T1830&p1=1440&ah=1 1830 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: snaiksat (Sumit Naiksatam)
* See [[Meetings/FWaaS]] for details

=== Neutron Advanced Services' team meeting ===
* Weekly on Tuesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Neutron+Advanced+Services&iso=20141111T17&p1=1440 1700 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: snaiksat (Sumit Naiksatam)
* See [[Meetings/AdvancedServices]] for details

=== Neutron IPv6 sub-team Meeting ===
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: sc68cal (Sean M. Collins)
* See [[Meetings/Neutron-IPv6-Subteam]] for details

=== Neutron Group Policy Sub-Team Meeting ===
* Weekly on Thursdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: SumitNaiksatam (Sumit Naiksatam)
* See [[Meetings/Neutron_Group_Policy]] for details

=== Neutron Distributed Virtual Router meeting ===
* Weekly on Wednesdays at [http://www.worldclock.com/world_clock.html 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair:Swami (Swaminathan Vasudevan)
* See [[Meetings/Distributed-Virtual-Router]] for details

=== Neutron blueprint ovs-firewall-driver Meeting ===
* Tentative: Monday, December 16 at 2000 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: asadoughi (Amir Sadoughi)
* Agenda: See [[Meetings/Neutron_blueprint_ovs-firewall-driver]]

=== Neutron L3 Sub Team Meeting ===
* Weekly on Thursday at 1500 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: carl_baldwin (Carl Baldwin)
* Agenda: See [[Meetings/Neutron-L3-Subteam]]

=== Neutron ServiceVM framework Sub Team Meeting ===
* Weekly on Wednesdays at 1700UTC from Nov 19, 2014
(Time slot/channel was changed from Nov 19, 2014.)
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: yamahata (Isaku Yamahata)
* Agenda: See [[Meetings/ServiceVM]]

=== neutron-drivers weekly IRC meeting ===
* Weekly on Wednesdays at 1530-1630 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: mestery (Kyle Mestery)
* Agenda: See [[Meetings/NeutronDrivers]]

=== VPN as a Service (VPNaaS) team meeting ===
* Weekly on Tuesdays at [http://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenStack+Neutron+VPNaaS+IRC&iso=20140326T1500&p1=1440&ah=1 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: pc_m (Paul Michali)
* See [[Meetings/VPNaaS]] for details

=== Networking L2 Gateway meeting ===
* Bi-weekly on Mondays (Every other Monday starting from January 5, 2015) at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): armax/Suhkdev (Armando Migliaccio / Sukhdev Kapur)
* See [[Meetings/L2Gateway]] for details

=== Nova-net to Neutron Migration meeting ===
* Weekly Tuesdays at 0900 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> Tuesdays
* Chair (to contact for more information) Anita Kuno (anteaya)
* see [[Meetings/Nova-nettoNeutronMigration]] for agenda

== Cinder team meeting ==
* Weekly on Wednesdays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by [[JohnGriffith]]
* see [[CinderMeetings]] for agenda

== Ceilometer team meeting ==
* '''Every''' week on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC].
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chaired by eglynn (Eoghan Glynn)
* see [[Meetings/Ceilometer]] for details

== Designate (DNSaaS) meeting ==
* Weekly Wednesdays at 1700 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): Kiall Mac Innes (kiall)
* See [[Meetings/Designate]] for details

== Trove (DBaaS) meeting ==
* Weekly on Wednesdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): [https://launchpad.net/~slicknik Nikhil Manchanda] (SlickNik) / [https://launchpad.net/~hubcap Michael Basnight] (hub_cap) / [https://launchpad.net/~vipuls Vipul Sabhaya] (vipul) / [https://launchpad.net/~tim-simpson Tim Simpson] (grapex) / [https://launchpad.net/~amcrn Auston McReynolds] (amcrn) / [https://launchpad.net/~cp16net Craig Vyvial] (cp16net)
* See [[Meetings/TroveMeeting]] for details
* For BP Meeting, please see [[Meetings/TroveBPMeeting]] for more details

== Zaqar (Messaging and Notification) team meeting ==
* Weekly on Mondays, alternating between 2100 UTC and 1500 UTC (starting with 2100 UTC on 8/4)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair (to contact for more information): Flavio Percoco (flaper87), Kurt Griffiths (kgriffs)
* See [[Meetings/Zaqar]] for details

== OpenStack Data Processing (Sahara) team meeting ==
* Weekly on Thursdays at 1800 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more info): SergeyLukjanov (Sergey Lukjanov)
* See [[Meetings/SaharaAgenda]] for details

== Mistral meeting ==
* Weekly on Mondays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: rakhmerov (Renat Akhmerov)
* See [[Meetings/MistralAgenda]] for details

== Murano meeting ==
* Weekly on Tuesday at 1700 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: Serg Melikyan (sergmelikyan)
* See [[Meetings/MuranoAgenda]] for details

== Heat (orchestration) team meeting ==
* Weekly on Wednesdays at 2000 UTC or 1200 UTC (on alternate weeks)
* IRC Channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): Zane Bitter (zaneb)
* See [[Meetings/HeatAgenda]] for details

== Horizon team meeting ==
* Weekly on Wednesdays at 2000 UTC or 1200 UTC (on alternate weeks)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: David Lyle (david-lyle)
* See [[Meetings/Horizon]] for details

== Swift team meeting ==
* Weekly on Wednesdays at 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: notmyname (John Dickinson)
* See [[Meetings/Swift]] for details

== OpenStack Security Group (OSSG) meeting ==
* Weekly on Thursdays at 1700 UTC (1 hour duration)
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): hyakuhei (Rob Clark)
* See [[Meetings/OpenStackSecurity]] for an agenda

== Python3 Compatibility Team meeting ==
* Not planned anymore
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair (to contact for more information): jd_ (Julien Danjou)
* See [[Meetings/Python3]] for details

== Glance Team meeting ==
* Weekly on Thursdays at [http://www.timeanddate.com/worldclock/fixedtime.html?hour=14&min=0&sec=0 1400]/[http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=0&sec=0 1500 UTC] (alternating)
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair (to contact for more information): nikhil_k (Nikhil Komawar)
* See [[Meetings/Glance]] for details

== Oslo Team meeting ==

* Juno
** Every Friday at 1600 UTC ([http://www.timeanddate.com/worldclock/converted.html?iso=20140425T16&p1=0&p2=2133&p3=195&p4=224 timeanddate.com])
** IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
** Chair (to contact for more information): dhellmann (Doug Hellmann)
** See [[Meetings/Oslo]] for details
* Kilo (beginning 17 Nov 2014)
** Every Monday at 1600 UTC ([http://www.timeanddate.com/worldclock/converted.html?iso=20141117T16&p1=0&p2=2133&p3=195&p4=224 timeanddate.com])
** IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
** Chair (to contact for more information): dhellmann (Doug Hellmann)
** See [[Meetings/Oslo]] for details

== OpenStack Community Office Hours ==
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 0800 UTC] and on Fridays at [http://www.worldclock.com/world_clock.html 1800 UTC]
* IRC channel: <code><nowiki>#openstack-community</nowiki></code>
* Chair: fifieldt ([http://www.openstack.org/community/members/profile/369 Tom Fifield]) and reed ([http://www.openstack.org/community/members/profile/1372 Stefano Maffulli])
* See [[Meetings/Community]] for details

== I18N Team meeting ==
* Bi-weekly on Thursday, at 0800 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: daisy
* See [[Meetings/I18nTeamMeeting]] for details

== Training-guides Team meeting ==
* Weekly on Monday at [http://www.timeanddate.com/time/zone/usa/san-francisco 1700 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: sarob
* See [[Meetings/training-guides]] for details

== Trainers Team meeting ==
* Weekly on Wednesday at [http://www.timeanddate.com/time/zone/usa/san-francisco 1800 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: sarob
* See [[Meetings/trainers]] for details

== Manila Team meeting ==
* Weekly on Thursday at [http://www.worldclock.com/current-local-time-in-san-francisco_598.htm 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: bswartz
* See [[Manila/Meetings]] for details

== Blazar (Reservations) team meeting ==
* Weekly on Fridays at [http://www.worldclock.com/world_clock.html 1500 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: bauzas (Sylvain Bauza), DinaBelova (Dina Belova)
* See [[Meetings/Blazar]] for details

== Rally meeting ==
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1700 UTC]
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair:boris-42 (Boris Pavlovic)
* See [[Meetings/Rally]] for details

== Solum Team Meeting ==
* Weekly on Tuesdays at 2100 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: adrian_otto (Adrian Otto)
* See [[Meetings/Solum]] for details

== Congress Team Meeting ==
* Weekly on Tuesdays at [http://www.worldclock.com/world_clock.html 1700 UTC], e.g. Feb 25, 2014
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: pballand (Pete Balland) or thinrichs (Tim Hinrichs)
* See [[Meetings/Congress]] for details

== Barbican Meeting ==
* Weekly on Mondays at [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130502T2000 2000 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair (to contact for more information): jraim (#openstack-barbican @ Freenode)
* See [[Meetings/Barbican]] for an agenda

== Chef Cookbook meetings ==
* Google Hangout Weekly on Mondays at 1530 UTC
* IRC channel Weekly on Fridays at 1530 UTC: <code><nowiki>#openstack-chef</nowiki></code>
* Chair: JJ Asghar
* See [[Meetings/ChefCookbook]] for details

== StoryBoard Meeting ==
* Weekly on Mondays at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: krotscheck, ttx, or NikitaKonovalov
* See [[StoryBoard]] for details

== Hierarchical Multitenancy Meeting ==
* Weekly on Friday at 1600 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
* Chair: vishy/schwicke
* See [[Meetings/HierarchicalMultitenancyMeeting]] for details

== python-openstacksdk Meeting ==
* Weekly on Tuesdays at [http://www.worldtimebuddy.com/?qm=1&lid=6,0,4726206,100&h=6&date=2014-2-11&sln=13-14 1900 UTC] starting 2/19/2014
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: jnoller
* See [[PythonOpenStackSDK]] for details

== Satori Team Meeting ==
* Weekly on Mondays at [http://www.worldtimebuddy.com/?qm=1&lid=6,0,4726206,100&h=6&date=2014-2-11&sln=9-10 1500 UTC] starting Feb 24, 2014
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: Ziad_Sawalha
* See [[Meetings/Satori]] for details

== Fuel Team Meeting ==
* Weekly on Thursdays at [http://www.worldtimebuddy.com/?qm=1&lid=100&h=100&date=2014-3-27&sln=16-17 1600 UTC] starting Feb 27, 2014
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: vkozhukalov
* See [[Meetings/Fuel]] for details

== Third Party Meeting ==
Meeting for any component to address Third Party needs
** Two times weekly: Mondays at 1500 UTC as well as Tuesdays at 0800 UTC
** IRC channel: <code><nowiki>#openstack-meeting</nowiki></code>
** Chair: anteaya
** See [[Meetings/ThirdParty]] for details
* Working Group: improve the consumability of CI components and documentation (starting January 7th, 2015)
** Weekly on Wednesdays at 1500/0400 UTC (alternating)
** IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
** Chair: krtaylor
** See [[Meetings/ThirdParty]] for details

== MagnetoDB Team meeting ==
* Weekly on Thursdays at 1400 UTC
* IRC channel: <code><nowiki>#magnetodb</nowiki></code>
* Chair: isviridov

== Telco Working Group Meeting ==
* Weekly alternating on Wednesdays alternating between 1400 UTC and 2200 UTC.
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code> (@ 1400 UTC) and <code><nowiki>#openstack-meeting</nowiki></code> (@ 2200 UTC)
* Chair: Stephen Gordon (steveg)
* See [[https://wiki.openstack.org/wiki/TelcoWorkingGroup]] or join #openstack-nfv for details.

== Containers Team Meeting ==
* Weekly on Tuesdays at 1600/2200 UTC (alternating)
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: adrian_otto (Adrian Otto)
* See [[Meetings/Containers]] for details

== User Experience (UX) Team Meeting ==
* Every second week on Mondays at 1700 UTC starting July 7th, 2014 (even weeks)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code>
* Chair: jcoufal (Jaromir Coufal)
* See [[Meetings/UX]] for details

== Tetris Team Meeting ==
* Bi-Weely at 0100 UTC
* IRC channel: <code><nowiki>#tetris</nowiki></code>
* Chair: Jay (liugya@cn.ibm.com jay.lau.513@gmail.com)
* See [[Meetings/Tetris]] for details

== Poppy Team Meeting ==
* Weekly on Thursdays at 1900 UTC
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code> starting August 7, 2014
* Chair: amitgandhinz (amit.gandhi@rackspace.com)
* See [[Meetings/Poppy]] for details

== Puppet OpenStack Team Meeting ==
* Weekly on Monday at 1400 UTC
* IRC channel: <code><nowiki>#openstack-meeting</nowiki></code> starting October 27, 2014
* Chair: crinkle (colleen@puppetlabs.com)
* See [[Meetings/PuppetOpenStack]] for details

== API Work Group Team Meeting ==
* Weekly on Thursdays at 16:00UTC/00:00 UTC (alternating)
* IRC channel: <code><nowiki>#openstack-meeting-3</nowiki></code> starting October 30, 2014
* Chair:
* See [[Meetings/API-WG]] for details

== Swift-on-File ==
* Weekly on Thursday at 1400 UTC
* IRC channel: <code><nowiki>#swiftonfile</nowiki></code>
* Chair: tdasilva (Thiago da Silva)
* See [[Meetings/swiftonfile]] for details

== Openstack Operators Team Meeting ==
* Weekly on Wednesday at 1800 UTC (next meeting is January 7)
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: mfisch (Matt Fischer)
* See [[Meetings/openstack-operators]] for details

== OpenStack Ambassadors Meeting ==
* Alternating Weekly on first, third, fifth Tuesdays at [http://www.timeanddate.com/time/zone/usa/san-francisco 08:00 GMT] and second and fourth Fridays at [http://www.timeanddate.com/time/zone/usa/san-francisco 18:00 GMT]
* IRC channel: <code><nowiki>#openstack-meeting-alt</nowiki></code>
* Chair: sarob
* See [[Meetings/ambassadors]] for details

== Openstack Ansible Deployment ==
* Weekly on Thursday at [http://www.timeanddate.com/time/zone/usa/san-antonio 1600 UTC]
* IRC channel: <code><nowiki>#openstack-meeting-4</nowiki></code>
* Chair: cloudnull (Kevin Carter)
* See [[Meetings/openstack-ansible]] for details

[[Category:Contribute]]
[[Category:Connect]]
[[Category:Resources]]

GSoC2014/Student/Manishanker

2014-03-20T18:27:19Z

Sriramhere:

'''Personal Details'''

Name : Manishanker Talusani 
Email : shanker.mani0@gmail.com 
Name of the University: Birla Institute of Technology & Science Pilani - K.K.Birla Goa Campus,Goa,India 
Education : Master Of Science (Technology) 
IRC nickname[freenode] : Manishanker 
Other contact methods (mobile no) : (+91) 9503395344 

'''Project Description'''

Project Idea url : https://wiki.openstack.org/wiki/GSoC2014/Testing/Fuzz

Project Goals :
* Design and Implement Fuzz testing framework that can fuzz OpenStack APIs by generating configurable combinations (random or pattern based)
* Enable fuzz testing on at least one OpenStack project (OpenStack Nova for example)
* Integrate above fuzz test framework with OpenStack Tempest test framework

'''Project Plan'''

* Task 1: Identify the best open source Fuzzing framework to fuzz Openstack API's
There are many open source fuzzing tools like BED, SFUZZ, SICKFUZZ, SPIKE. Frameworks will be evaluated based on the following criteria:
# Whether it can perform API fuzzing ?
# Can it do HTTP fuzzing?
# Can it be invoked using Tempest?

After finding the appropriate fuzzing tool, few fuzzing iterations will be run using different types of inputs using Tempest as a POC.

Inputs for fuzzing can be random by defining the mandatory input parameters and randomizing the other parameters or they can be pattern based by defining a protocol which serves as a black box which is used to create them. For example Backtrack 5 R3 can be used to run different types of the fuzzing programs like BED program to test OpenStack Horizon's HTTP service. BED program can be used to send fuzz packets to HTTP HEAD,GET,POST etc. In the similar way sfuzz program can be used to fuzz the OpenStack Horizon's HTTP service by providing configuration files. Depending on the results obtained by the different fuzzing programs, fuzzing tool will be used to test OpenStack service.

* Task 2: Implement Fuzzing for one OpenStack project, say OpenStack Nova
After selecting the best fuzzing tool, it will be used to fuzz OpenStack APIs for one of the projects/ services, such as OpenStack Nova. This will be further broken down to several sub tasks i.e fuzzing the main components of that service which may lead to any security vulnerabilities. To begin with, API fuzzing and HTTP fuzzing will be completed.

During this stage, appropriate reporting mechanism would also be finalized in order to report the vulnerabilities effectively. The [https://launchpad.net/~openstack-ossg OpenStack Security Group] will be consulted for this step.

* Task 3 : Integrate with OpenStack testing framework - Tempest
Next task would be integrating with Tempest.Tempest should be able to run fuzzing iterations on OpenStack service. Tempest currently supports API testing to some extent, but by integrating fuzzing with Tempest, fuzzing can be run directly from it.

'''How will i achieve these goals:'''

Successful completion of the project involves thorough understanding of Fuzzing tools, Fuzzing techniques, Penetration tools and also in depth knowledge of the OpenStack service internals on which fuzzing is to be done. I am familiar and have experience with architecture of the OpenStack and its services. I also have experience in deploying OpenStack using Devstack and in 3 node setup with different Hypervisors. I plan to learn and work with the different fuzzing tools and techniques before coding starts so that I could start using fuzzing techniques as the coding period starts. I have discussed with my mentor Sriram Subramanian, he has given me material which has all the information on how fuzzing and other penetration tests were done in OpenStack Essex cloud software. In the meantime i will also work on a specific OpenStack services,Tempest and gain in depth knowledge of it so that i can implement fuzzing on it.

'''What are my milestones'''

* My first milestone would be identifying the appropriate fuzzing tool which can be used to fuzz OpenStack service based on the prerequisites mentioned in task 1
* Second milestone would be, after the identification and implementation of the fuzzing tool and techniques, using it to fuzz OpenStack service
* Third milestone would be, integrating the fuzzing tool with the Tempest which could be used to run fuzzing tests directly and enabling automated reporting of security vulnerabilities to the OpenStack Security Group.

'''Project Timeline'''

This is my tentative project timeline based on the discussion with my mentor.

* Before April 20
* Familiarize myself with different types of Fuzzing techniques and Fuzzing tools like BED,SPIKE, SFUZZ, SICKFUZZ.
* Familiarize myself with OpenStack services,Tempest and OpenStack code base.
* I will be in constant touch with my mentor to improve my knowledge and get better, deeper understanding of Fuzzing and OpenStack services.

* April 21 - May 4 (Before the actual coding time)
* Identifying the best open source fuzzing tool which can be used for API ,HTTP fuzzing
* Creating a working draft on which fuzzing tool can serve the purpose
* Discussing with mentor on using the fuzzing tool for the further project and changes to the tool(if required)

* May 5 - May 18
* Implementing the fuzzing tool to fuzz on one of the OpenStack service API
* Creating exhaustive fuzzers and trying to automate the fuzzing tool to create inputs(random or pattern based) to the fuzzing tool
* Based on the complexity of the OpenStack service ,fuzzing can be done on separate parts of the service

* May 19 - June 1
* Implementing other penetration tests which may lead to threats like Memory leaks and Buffer overflows

* June 2 - June 15
* Improving the code functionality ,removing bugs and exception handling

* June 16 - June 29 (Mid term Evaluation)
* By the Mid-term, a fully functional fuzzing on one of the OpenStack service

* June 30 - July 13
* Integrating fuzzing tool with the tempest so that tempest can directly be used to run fuzz test

* July 14 - July 27
* Testing Tempest to see if it can run the fuzzing test on OpenStack service

* July 28 - Aug 10
* Making further changes in the code to improve functionality,bug removals,exception handling

* Aug 11 - Aug 24
* Discussion about the documentation with mentor and wrapping up
* Most of the time will be used for bug fixes and testing
* Final documentation which includes complete details about all the methods and their usage.

'''Technical Background'''

*'''Open Source contribution'''
I haven't contributed to open source but i want to start my contribution to open source through OpenStack.

*'''Academic background'''
I am an Undergraduate student pursuing MSC.(Tech.) Information Systems at BITS Pilani K K Birla Goa Campus.Currently i am working as an intern.I have been working on OpenStack for couple of months and i am involved in deployment of OpenStack services in the Data center. I am responsible for deployment of multi-hypervisor cloud which is used to test different products of the company and fixing errors for the other teams who are using the OpenStack services.I am also responsible for Baremetal and Ironic deployment which are currently in progress.Prior to this i have worked on different projects in Android, Hadoop, Matlab

*'''Programming language'''
C, Java, Python

GSoC2014/Student/Manishanker

2014-03-20T18:25:19Z

Sriramhere:

'''Personal Details'''

Name : Manishanker Talusani 
Email : shanker.mani0@gmail.com 
Name of the University: Birla Institute of Technology & Science Pilani - K.K.Birla Goa Campus,Goa,India 
Education : Master Of Science (Technology) 
IRC nickname[freenode] : Manishanker 
Other contact methods (mobile no) : (+91) 9503395344 

'''Project Description'''

Project Idea url : https://wiki.openstack.org/wiki/GSoC2014/Testing/Fuzz

Project Goals :
* Design and Implement Fuzz testing framework that can fuzz OpenStack APIs by generating configurable combinations (random or pattern based)
* Enable fuzz testing on at least one OpenStack project (OpenStack Nova for example)
* Integrate above fuzz test framework with OpenStack Tempest test framework

'''Project Plan'''

* Task 1: Identify the best open source Fuzzing framework to fuzz Openstack API's
There are many open source fuzzing tools like BED, SFUZZ, SICKFUZZ, SPIKE. Frameworks will be evaluated based on the following criteria:
#1. Whether it can perform API fuzzing ?
# 2. Can it do HTTP fuzzing?
# 3. Can it be invoked using Tempest?

After finding the appropriate fuzzing tool, few fuzzing iterations will be run using different types of inputs using Tempest as a POC.

Inputs for fuzzing can be random by defining the mandatory input parameters and randomizing the other parameters or they can be pattern based by defining a protocol which serves as a black box which is used to create them. For example Backtrack 5 R3 can be used to run different types of the fuzzing programs like BED program to test OpenStack Horizon's HTTP service. BED program can be used to send fuzz packets to HTTP HEAD,GET,POST etc. In the similar way sfuzz program can be used to fuzz the OpenStack Horizon's HTTP service by providing configuration files. Depending on the results obtained by the different fuzzing programs, fuzzing tool will be used to test OpenStack service.

* Task 2: Implement Fuzzing for one OpenStack project, say OpenStack Nova
After selecting the best fuzzing tool, it will be used to fuzz OpenStack APIs for one of the projects/ services, such as OpenStack Nova. This will be further broken down to several sub tasks i.e fuzzing the main components of that service which may lead to any security vulnerabilities. To begin with, API fuzzing and HTTP fuzzing will be completed.

During this stage, appropriate reporting mechanism would also be finalized in order to report the vulnerabilities effectively. The [https://launchpad.net/~openstack-ossg OpenStack Security Group] will be consulted for this step.

* Task 3 : Integrate with OpenStack testing framework - Tempest
Next task would be integrating with Tempest.Tempest should be able to run fuzzing iterations on OpenStack service. Tempest currently supports API testing to some extent, but by integrating fuzzing with Tempest, fuzzing can be run directly from it.

'''How will i achieve these goals:'''

Successful completion of the project involves thorough understanding of Fuzzing tools, Fuzzing techniques, Penetration tools and also in depth knowledge of the OpenStack service internals on which fuzzing is to be done. I am familiar and have experience with architecture of the OpenStack and its services. I also have experience in deploying OpenStack using Devstack and in 3 node setup with different Hypervisors. I plan to learn and work with the different fuzzing tools and techniques before coding starts so that I could start using fuzzing techniques as the coding period starts. I have discussed with my mentor Sriram Subramanian, he has given me material which has all the information on how fuzzing and other penetration tests were done in OpenStack Essex cloud software. In the meantime i will also work on a specific OpenStack services,Tempest and gain in depth knowledge of it so that i can implement fuzzing on it.

'''What are my milestones'''

* My first milestone would be identifying the appropriate fuzzing tool which can be used to fuzz OpenStack service based on the prerequisites mentioned in task 1
* Second milestone would be, after the identification and implementation of the fuzzing tool and techniques, using it to fuzz OpenStack service
* Third milestone would be, integrating the fuzzing tool with the Tempest which could be used to run fuzzing tests directly and enabling automated reporting of security vulnerabilities to the OpenStack Security Group.

'''Project Timeline'''

This is my tentative project timeline based on the discussion with my mentor.

* Before April 20
* Familiarize myself with different types of Fuzzing techniques and Fuzzing tools like BED,SPIKE, SFUZZ, SICKFUZZ.
* Familiarize myself with OpenStack services,Tempest and OpenStack code base.
* I will be in constant touch with my mentor to improve my knowledge and get better, deeper understanding of Fuzzing and OpenStack services.

* April 21 - May 4 (Before the actual coding time)
* Identifying the best open source fuzzing tool which can be used for API ,HTTP fuzzing
* Creating a working draft on which fuzzing tool can serve the purpose
* Discussing with mentor on using the fuzzing tool for the further project and changes to the tool(if required)

* May 5 - May 18
* Implementing the fuzzing tool to fuzz on one of the OpenStack service API
* Creating exhaustive fuzzers and trying to automate the fuzzing tool to create inputs(random or pattern based) to the fuzzing tool
* Based on the complexity of the OpenStack service ,fuzzing can be done on separate parts of the service

* May 19 - June 1
* Implementing other penetration tests which may lead to threats like Memory leaks and Buffer overflows

* June 2 - June 15
* Improving the code functionality ,removing bugs and exception handling

* June 16 - June 29 (Mid term Evaluation)
* By the Mid-term, a fully functional fuzzing on one of the OpenStack service

* June 30 - July 13
* Integrating fuzzing tool with the tempest so that tempest can directly be used to run fuzz test

* July 14 - July 27
* Testing Tempest to see if it can run the fuzzing test on OpenStack service

* July 28 - Aug 10
* Making further changes in the code to improve functionality,bug removals,exception handling

* Aug 11 - Aug 24
* Discussion about the documentation with mentor and wrapping up
* Most of the time will be used for bug fixes and testing
* Final documentation which includes complete details about all the methods and their usage.

'''Technical Background'''

*'''Open Source contribution'''
I haven't contributed to open source but i want to start my contribution to open source through OpenStack.

*'''Academic background'''
I am an Undergraduate student pursuing MSC.(Tech.) Information Systems at BITS Pilani K K Birla Goa Campus.Currently i am working as an intern.I have been working on OpenStack for couple of months and i am involved in deployment of OpenStack services in the Data center. I am responsible for deployment of multi-hypervisor cloud which is used to test different products of the company and fixing errors for the other teams who are using the OpenStack services.I am also responsible for Baremetal and Ironic deployment which are currently in progress.Prior to this i have worked on different projects in Android, Hadoop, Matlab

*'''Programming language'''
C, Java, Python

GSoC2014/Student/Manishanker

2014-03-20T18:23:04Z

Sriramhere:

'''Personal Details'''

Name : Manishanker Talusani 
Email : shanker.mani0@gmail.com 
Name of the University: Birla Institute of Technology & Science Pilani - K.K.Birla Goa Campus,Goa,India 
Education : Master Of Science (Technology) 
IRC nickname[freenode] : Manishanker 
Other contact methods (mobile no) : (+91) 9503395344 

'''Project Description'''

Project Idea url : https://wiki.openstack.org/wiki/GSoC2014/Testing/Fuzz

Project Goals :
* Design and Implement Fuzz testing framework that can fuzz OpenStack APIs by generating configurable combinations (random or pattern based)
* Enable fuzz testing on at least one OpenStack project (OpenStack Nova for example)
* Integrate above fuzz test framework with OpenStack Tempest test framework

'''Project Plan'''

* Task 1: Identify the best open source Fuzzing framework to fuzz Openstack API's
There are many open source fuzzing tools like BED, SFUZZ, SICKFUZZ, SPIKE. Frameworks will be evaluated based on the following criteria:
#1. Whether it can perform API fuzzing ?
# 2. Can it do HTTP fuzzing?
# 3. Can it be invoked using Tempest?

After finding the appropriate fuzzing tool, few fuzzing iterations will be run using different types of inputs using Tempest as a POC.

Inputs for fuzzing can be random by defining the mandatory input parameters and randomizing the other parameters or they can be pattern based by defining a protocol which serves as a black box which is used to create them. For example Backtrack 5 R3 can be used to run different types of the fuzzing programs like BED program to test OpenStack Horizon's HTTP service. BED program can be used to send fuzz packets to HTTP HEAD,GET,POST etc. In the similar way sfuzz program can be used to fuzz the OpenStack Horizon's HTTP service by providing configuration files. Depending on the results obtained by the different fuzzing programs, fuzzing tool will be used to test OpenStack service.

* Task 2: Implement Fuzzing for one OpenStack project, say OpenStack Nova
After selecting the best fuzzing tool, it will be used to fuzz OpenStack APIs for one of the projects/ services, such as OpenStack Nova. This will be further broken down to several sub tasks i.e fuzzing the main components of that service which may lead to any security vulnerabilities. To begin with, API fuzzing and HTTP fuzzing will be completed.

During this stage, appropriate reporting mechanism would also be finalized in order to report the vulnerabilities effectively. The [https://launchpad.net/~openstack-ossg OpenStack Security Group] will be consulted for this step.

* Task 3 : Integrate with OpenStack testing framework - Tempest
Next task would be integrating with Tempest.Tempest should be able to run fuzzing iterations on OpenStack service. Tempest currently supports API testing to some extent, but by integrating fuzzing with Tempest, fuzzing can be run directly from it.

'''How will i achieve these goals:'''

Successful completion of the project involves thorough understanding of Fuzzing tools, Fuzzing techniques, Penetration tools and also in depth knowledge of the OpenStack service internals on which fuzzing is to be done. I am familiar and have experience with architecture of the OpenStack and its services. I also have experience in deploying OpenStack using Devstack and in 3 node setup with different Hypervisors. I plan to learn and work with the different fuzzing tools and techniques before coding starts so that I could start using fuzzing techniques as the coding period starts. I have discussed with my mentor Sriram Subramanian, he has given me material which has all the information on how fuzzing and other penetration tests were done in OpenStack Essex cloud software. In the meantime i will also work on a specific Openstack services,Tempest and gain in depth knowledge of it so that i can implement fuzzing on it.

'''What are my milestones'''

* My first milestone would be identifying the appropriate fuzzing tool which can be used to fuzz Openstack service based on the prerequisites mentioned in task 1
* Second milestone would be, after the identification and implementation of the fuzzing tool and techniques ,using it to fuzz Openstack service
* Third milestone would be, integrating the fuzzing tool with the Tempest which could be used to run fuzzing tests directly and enabling automated reporting of security vulnerabilities to the OpenStack Security Group.

'''Project Timeline'''

This is my tentative project timeline based on the discussion with my mentor.

* Before April 20
* Familiarize myself with different types of Fuzzing techniques and Fuzzing tools like BED,SPIKE,SFUZZ,SICKFUZZ.
* Familiarize myself with Openstack services,Tempest and Openstack code base.
* I will be in constant touch with my mentor to improve my knowledge and get better ,deeper understanding of Fuzzing and Openstack services.

* April 21 - May 4(Before the actual coding time)
* Identifying the best open source fuzzing tool which can be used for API ,HTTP fuzzing
* Creating a working draft on which fuzzing tool can serve the purpose
* Discussing with mentor on using the fuzzing tool for the further project and changes to the tool(if required)

* May 5 - May 18
* Implementing the fuzzing tool to fuzz on one of the Openstack service API
* Creating exhaustive fuzzers and trying to automate the fuzzing tool to create inputs(random or pattern based) to the fuzzing tool
* Based on the complexity of the openstack service ,fuzzing can be done on separate parts of the service

* May 19 - June 1
* Implementing other penetration tests which may lead to threats like Memory leaks and Buffer overflows

* June 2 - June 15
* Improving the code functionality ,removing bugs and exception handling

* June 16 - June 29 (Mid term Evaluation)
* By the Mid-term, a fully functional fuzzing on one of the Openstack service

* June 30 - July 13
* Integrating fuzzing tool with the tempest so that tempest can directly be used to run fuzz test

* July 14 - July 27
* Testing Tempest to see if it can run the fuzzing test on openstack service

* July 28 - Aug 10
* Making further changes in the code to improve functionality,bug removals,exception handling

* Aug 11 - Aug 24
* Discussion about the documentation with mentor and wrapping up
* Most of the time will be used for bug fixes and testing
* Final documentation which includes complete details about all the methods and their usage.

'''Technical Background'''

*'''Open Source contribution'''
I haven't contributed to open source but i want to start my contribution to open source through Openstack.

*'''Academic background'''
I am an Undergraduate student pursuing MSC.(Tech.) Information Systems at BITS Pilani K K Birla Goa Campus.Currently i am working as an intern.I have been working on Openstack for couple of months and i am involved in deployment of Openstack services in the Data center. I am responsible for deployment of multi-hypervisor cloud which is used to test different products of the company and fixing errors for the other teams who are using the Openstack services.I am also responsible for Baremetal and Ironic deployment which are currently in progress.Prior to this i have worked on different projects in Android ,Hadoop, Matlab

*'''Programming language'''
C,Java,Python

GSoC2014/Student/Manishanker

2014-03-20T18:13:56Z

Sriramhere:

'''Personal Details'''

Name : Manishanker Talusani 
Email : shanker.mani0@gmail.com 
Name of the University: Birla Institute of Technology & Science Pilani - K.K.Birla Goa Campus,Goa,India 
Education : Master Of Science (Technology) 
IRC nickname[freenode] : Manishanker 
Other contact methods (mobile no) : (+91) 9503395344 

'''Project Description'''

Project Idea url : https://wiki.openstack.org/wiki/GSoC2014/Testing/Fuzz

Project Goals :
* Design and Implement Fuzz testing framework that can fuzz OpenStack APIs by generating configurable combinations (random or pattern based)
* Enable fuzz testing on at least one OpenStack project (OpenStack Nova for example)
* Integrate above fuzz test framework with OpenStack Tempest test framework

'''Project Plan'''

* Task 1: Identify the best open source Fuzzing framework to fuzz Openstack API's
There are many open source fuzzing tools like BED, SFUZZ, SICKFUZZ, SPIKE. Frameworks will be evaluated based on the following criteria:
1. Whether it can perform API fuzzing ?
2. Can it do HTTP fuzzing?
3. Can it be invoked using Tempest?

After finding the appropriate fuzzing tool, few fuzzing iterations will be run using different types of inputs using Tempest as a POC.

Inputs for fuzzing can be random by defining the mandatory input parameters and randomizing the other parameters or they can be pattern based by defining a protocol which serves as a black box which is used to create them. For example Backtrack 5 R3 can be used to run different types of the fuzzing programs like BED program to test Openstack Horizon's HTTP service. BED program can be used to send fuzz packets to HTTP HEAD,GET,POST etc. In the similar way sfuzz program can be used to fuzz the Openstack Horizon's HTTP service by providing configuration files. Depending on the results obtained by the different fuzzing programs, fuzzing tool will be used to test OpenStack service.

* Task 2: Implement Fuzzing for one OpenStack project, say OpenStack Nova
After selecting the best fuzzing tool, it will be used to fuzz Openstack APIs. Fuzzing tool can be then used to fuzz on one of the OpenStack service. Based on the OpenStack service, fuzzing can be still broken down to several sub tasks i.e fuzzing the main components of that service which may lead to any security vulnerabilities.Fuzzing will be done mostly to identify security vulnerabilities in API's and HTTP. Other vulnerabilities like Memory leaks,Buffer overflow can also be checked.

* Task3 : Integrate with OpenStack testing framework - Tempest
Next task would be integrating with Tempest.Tempest should be able to run fuzzing iterations on Openstack service.Tempest currently supports API testing to some extent ,but by integrating fuzzing with Tempest ,fuzzing can be run directly from it.

'''How will i achieve these goals:'''

Successful completion of the project involves thorough understanding of Fuzzing tools, Fuzzing techniques ,Penetration tools and also in depth knowledge of the Openstack service internals on which fuzzing is to be done.I am familiar and i have experience with architecture of the Openstack and its services. I also have experience in deploying Openstack using Devstack and in 3 node setup with different Hypervisors. I plan to learn and work with the different fuzzing tools and techniques before coding starts so that i could start using fuzzing techniques as the coding period starts. I have discussed with my mentor Sriram Subramanian, he has given me material which has all the information on how fuzzing and other penetration tests were done in Openstack Essex cloud software.In the meantime i will also work on a specific Openstack services,Tempest and gain in depth knowledge of it so that i can implement fuzzing on it.

'''What are my milestones'''

* My first milestone would be identifying the appropriate fuzzing tool which can be used to fuzz Openstack service based on the prerequisites mentioned in task 1
* Second milestone would be, after the identification and implementation of the fuzzing tool and techniques ,using it to fuzz Openstack service
* Third milestone would be, integrating the fuzzing tool with the Tempest which could be used to run fuzzing tests directly and enabling automated reporting of security vulnerabilities to the OpenStack Security Group.

'''Project Timeline'''

This is my tentative project timeline based on the discussion with my mentor.

* Before April 20
* Familiarize myself with different types of Fuzzing techniques and Fuzzing tools like BED,SPIKE,SFUZZ,SICKFUZZ.
* Familiarize myself with Openstack services,Tempest and Openstack code base.
* I will be in constant touch with my mentor to improve my knowledge and get better ,deeper understanding of Fuzzing and Openstack services.

* April 21-May4(Before the actual coding time)
* Identifying the best open source fuzzing tool which can be used for API ,HTTP fuzzing
* Creating a working draft on which fuzzing tool can serve the purpose
* Discussing with mentor on using the fuzzing tool for the further project and changes to the tool(if required)

* May5-May18
* Implementing the fuzzing tool to fuzz on one of the Openstack service API
* Creating exhaustive fuzzers and trying to automate the fuzzing tool to create inputs(random or pattern based) to the fuzzing tool
* Based on the complexity of the openstack service ,fuzzing can be done on separate parts of the service

* May19-June 1
* Implementing other penetration tests which may lead to threats like Memory leaks and Buffer overflows

* June 2-June 15
* Improving the code functionality ,removing bugs and exception handling

* June 16-June 29 (Mid term Evaluation)
* By the Mid-term, a fully functional fuzzing on one of the Openstack service

* June30-July 13
* Integrating fuzzing tool with the tempest so that tempest can directly be used to run fuzz test

* July14-July27
* Testing Tempest to see if it can run the fuzzing test on openstack service

* July 28-Aug10
* Making further changes in the code to improve functionality,bug removals,exception handling

* Aug11-Aug24
* Discussion about the documentation with mentor and wrapping up
* Most of the time will be used for bug fixes and testing
* Final documentation which includes complete details about all the methods and their usage.

'''Technical Background'''

*'''Open Source contribution'''
I haven't contributed to open source but i want to start my contribution to open source through Openstack.

*'''Academic background'''
I am an Undergraduate student pursuing MSC.(Tech.) Information Systems at BITS Pilani K K Birla Goa Campus.Currently i am working as an intern.I have been working on Openstack for couple of months and i am involved in deployment of Openstack services in the Data center. I am responsible for deployment of multi-hypervisor cloud which is used to test different products of the company and fixing errors for the other teams who are using the Openstack services.I am also responsible for Baremetal and Ironic deployment which are currently in progress.Prior to this i have worked on different projects in Android ,Hadoop, Matlab

*'''Programming language'''
C,Java,Python

OSSN/OSSN-0008

2014-03-07T22:37:31Z

Sriramhere: /* Recommended Actions */

__NOTOC__
== DoS style attack on noVNC server can lead to service interruption or disruption ==

=== Summary ===
There is currently no limitation on the number of VNC sessions that can be established for a single user's VNC token. This enables one to cause a Denial of Service (DoS) style attack by establishing many VNC sessions against a single instance through a noVNC proxy. This can cause timeouts for other users who are trying to access the same instance through VNC.

=== Affected Services / Software ===
Horizon (VNC Console through browser), Nova (noVNC proxy), Grizzly & Havana

=== Discussion ===
Once a user gets a token to access an instance's VNC console, there is no restriction on the frequency that the user can attempt to connect to the instance's VNC console using that token. There is also no restriction on the number of simultaneous VNC sessions that the user can establish against the instance using a single token. If many connection requests are made, any subsequent connection requests made by other users may time out. This could also impact other user's currently established VNC sessions to the instance. The overall responsiveness of other Nova services running on the noVNC host.

By taking advantage of the lack of any VNC connection limiting, a single user could cause the noVNC proxy endpoint to be non-responsive or unreachable. This results in a DoS attack. It should be noted that there is no amplification effect.

=== Recommended Actions ===
For current stable releases (Grizzly, Havana), users need to workaround this vulnerability by using rate-limiting proxies to cover access to noVNC hosts. Rate-limiting is a common mechanism to prevent DoS/ Brute-Force attacks.

For example, if you are using proxy such as [http://www.openrepose.org/ '''Repose'''], one can enable rate limiting feature by following these [https://repose.atlassian.net/wiki/display/REPOSE/Rate+Limiting+Filter steps].

One can find more discussion on rate-limiting around OpenStack Networking Best practices [http://docs.openstack.org/security-guide/content/ch032_networking-best-practices.html here].

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/nova/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2014-03-07T22:22:32Z

Sriramhere: /* Recommended Actions */

__NOTOC__
== DoS style attack on noVNC server can lead to service interruption or disruption ==

=== Summary ===
There is currently no limitation on the number of VNC sessions that can be established for a single user's VNC token. This enables one to cause a Denial of Service (DoS) style attack by establishing many VNC sessions against a single instance through a noVNC proxy. This can cause timeouts for other users who are trying to access the same instance through VNC.

=== Affected Services / Software ===
Horizon (VNC Console through browser), Nova (noVNC proxy), Grizzly & Havana

=== Discussion ===
Once a user gets a token to access an instance's VNC console, there is no restriction on the frequency that the user can attempt to connect to the instance's VNC console using that token. There is also no restriction on the number of simultaneous VNC sessions that the user can establish against the instance using a single token. If many connection requests are made, any subsequent connection requests made by other users may time out. This could also impact other user's currently established VNC sessions to the instance. The overall responsiveness of other Nova services running on the noVNC host.

By taking advantage of the lack of any VNC connection limiting, a single user could cause the noVNC proxy endpoint to be non-responsive or unreachable. This results in a DoS attack. It should be noted that there is no amplification effect.

=== Recommended Actions ===
For current stable releases (Grizzly, Havana), users need to workaround this vulnerability by using rate-limiting proxies to cover access to noVNC hosts. Rate-limiting is a common mechanism to prevent DoS/ Brute-Force attacks. You can find more discussion on rate-limiting around OpenStack Networking Best practices [http://docs.openstack.org/security-guide/content/ch032_networking-best-practices.html here].

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/nova/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2014-03-07T22:22:17Z

Sriramhere: /* Affected Services / Software */

__NOTOC__
== DoS style attack on noVNC server can lead to service interruption or disruption ==

=== Summary ===
There is currently no limitation on the number of VNC sessions that can be established for a single user's VNC token. This enables one to cause a Denial of Service (DoS) style attack by establishing many VNC sessions against a single instance through a noVNC proxy. This can cause timeouts for other users who are trying to access the same instance through VNC.

=== Affected Services / Software ===
Horizon (VNC Console through browser), Nova (noVNC proxy), Grizzly & Havana

=== Discussion ===
Once a user gets a token to access an instance's VNC console, there is no restriction on the frequency that the user can attempt to connect to the instance's VNC console using that token. There is also no restriction on the number of simultaneous VNC sessions that the user can establish against the instance using a single token. If many connection requests are made, any subsequent connection requests made by other users may time out. This could also impact other user's currently established VNC sessions to the instance. The overall responsiveness of other Nova services running on the noVNC host.

By taking advantage of the lack of any VNC connection limiting, a single user could cause the noVNC proxy endpoint to be non-responsive or unreachable. This results in a DoS attack. It should be noted that there is no amplification effect.

=== Recommended Actions ===
For current stable releases (Grizzly), users need to workaround this vulnerability by using rate-limiting proxies to cover access to noVNC hosts. Rate-limiting is a common mechanism to prevent DoS/ Brute-Force attacks. You can find more discussion on rate-limiting around OpenStack Networking Best practices [http://docs.openstack.org/security-guide/content/ch032_networking-best-practices.html here].

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/nova/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2014-03-07T22:20:43Z

Sriramhere: /* Recommended Actions */

__NOTOC__
== DoS style attack on noVNC server can lead to service interruption or disruption ==

=== Summary ===
There is currently no limitation on the number of VNC sessions that can be established for a single user's VNC token. This enables one to cause a Denial of Service (DoS) style attack by establishing many VNC sessions against a single instance through a noVNC proxy. This can cause timeouts for other users who are trying to access the same instance through VNC.

=== Affected Services / Software ===
Horizon (VNC Console through browser), Nova (noVNC proxy), Grizzly

=== Discussion ===
Once a user gets a token to access an instance's VNC console, there is no restriction on the frequency that the user can attempt to connect to the instance's VNC console using that token. There is also no restriction on the number of simultaneous VNC sessions that the user can establish against the instance using a single token. If many connection requests are made, any subsequent connection requests made by other users may time out. This could also impact other user's currently established VNC sessions to the instance. The overall responsiveness of other Nova services running on the noVNC host.

By taking advantage of the lack of any VNC connection limiting, a single user could cause the noVNC proxy endpoint to be non-responsive or unreachable. This results in a DoS attack. It should be noted that there is no amplification effect.

=== Recommended Actions ===
For current stable releases (Grizzly), users need to workaround this vulnerability by using rate-limiting proxies to cover access to noVNC hosts. Rate-limiting is a common mechanism to prevent DoS/ Brute-Force attacks. You can find more discussion on rate-limiting around OpenStack Networking Best practices [http://docs.openstack.org/security-guide/content/ch032_networking-best-practices.html here].

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/nova/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2014-03-07T22:20:08Z

Sriramhere: /* Affected Services / Software */

__NOTOC__
== DoS style attack on noVNC server can lead to service interruption or disruption ==

=== Summary ===
There is currently no limitation on the number of VNC sessions that can be established for a single user's VNC token. This enables one to cause a Denial of Service (DoS) style attack by establishing many VNC sessions against a single instance through a noVNC proxy. This can cause timeouts for other users who are trying to access the same instance through VNC.

=== Affected Services / Software ===
Horizon (VNC Console through browser), Nova (noVNC proxy), Grizzly

=== Discussion ===
Once a user gets a token to access an instance's VNC console, there is no restriction on the frequency that the user can attempt to connect to the instance's VNC console using that token. There is also no restriction on the number of simultaneous VNC sessions that the user can establish against the instance using a single token. If many connection requests are made, any subsequent connection requests made by other users may time out. This could also impact other user's currently established VNC sessions to the instance. The overall responsiveness of other Nova services running on the noVNC host.

By taking advantage of the lack of any VNC connection limiting, a single user could cause the noVNC proxy endpoint to be non-responsive or unreachable. This results in a DoS attack. It should be noted that there is no amplification effect.

=== Recommended Actions ===
For current stable releases (Grizzly), users need to workaround this vulnerability by using rate-limiting proxies to cover access to NoVNC hosts. Rate-limiting is a common mechanism to prevent DoS/ Brute-Force attacks. You can find more discussion on rate-limiting around OpenStack Networking Best practices [http://docs.openstack.org/security-guide/content/ch032_networking-best-practices.html here].

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/nova/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2014-03-07T22:18:59Z

Sriramhere: /* Discussion */

__NOTOC__
== DoS style attack on noVNC server can lead to service interruption or disruption ==

=== Summary ===
There is currently no limitation on the number of VNC sessions that can be established for a single user's VNC token. This enables one to cause a Denial of Service (DoS) style attack by establishing many VNC sessions against a single instance through a noVNC proxy. This can cause timeouts for other users who are trying to access the same instance through VNC.

=== Affected Services / Software ===
Horizon (VNC Console through browser), Nova (NoVNC proxy), Grizzly

=== Discussion ===
Once a user gets a token to access an instance's VNC console, there is no restriction on the frequency that the user can attempt to connect to the instance's VNC console using that token. There is also no restriction on the number of simultaneous VNC sessions that the user can establish against the instance using a single token. If many connection requests are made, any subsequent connection requests made by other users may time out. This could also impact other user's currently established VNC sessions to the instance. The overall responsiveness of other Nova services running on the noVNC host.

By taking advantage of the lack of any VNC connection limiting, a single user could cause the noVNC proxy endpoint to be non-responsive or unreachable. This results in a DoS attack. It should be noted that there is no amplification effect.

=== Recommended Actions ===
For current stable releases (Grizzly), users need to workaround this vulnerability by using rate-limiting proxies to cover access to NoVNC hosts. Rate-limiting is a common mechanism to prevent DoS/ Brute-Force attacks. You can find more discussion on rate-limiting around OpenStack Networking Best practices [http://docs.openstack.org/security-guide/content/ch032_networking-best-practices.html here].

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/nova/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2014-03-07T22:17:53Z

Sriramhere: /* Summary */

__NOTOC__
== DoS style attack on noVNC server can lead to service interruption or disruption ==

=== Summary ===
There is currently no limitation on the number of VNC sessions that can be established for a single user's VNC token. This enables one to cause a Denial of Service (DoS) style attack by establishing many VNC sessions against a single instance through a noVNC proxy. This can cause timeouts for other users who are trying to access the same instance through VNC.

=== Affected Services / Software ===
Horizon (VNC Console through browser), Nova (NoVNC proxy), Grizzly

=== Discussion ===
NoVNC Proxy is explained well [http://docs.openstack.org/grizzly/openstack-compute/admin/content//getting-started-with-vnc-proxy.html here].

Once a user gets a token to access a VM's VNC console, there is no restriction on the number of times the user can try connecting to the VNC console using the same token. If multiple connection requests are made, any subsequent request could timeout. This could impact users already connected to the VNC sessions, or other users trying to make a new connection. This could also impact overall responsiveness of other nova services running on the noVNc host.

Thus, a user could make the noVNC proxy endpoint not responsive or reachable, thereby resulting in a DoS attack. However, it is to be noted there is no amplification effect.

=== Recommended Actions ===
For current stable releases (Grizzly), users need to workaround this vulnerability by using rate-limiting proxies to cover access to NoVNC hosts. Rate-limiting is a common mechanism to prevent DoS/ Brute-Force attacks. You can find more discussion on rate-limiting around OpenStack Networking Best practices [http://docs.openstack.org/security-guide/content/ch032_networking-best-practices.html here].

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/nova/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

GSoC2014

2014-02-14T18:18:44Z

Sriramhere: /* Fuzz Testing (various projects) */

== Google Summer of Code 2014 ==

[http://www.openstack.org/software/ OpenStack] is applying as a mentoring organization for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 2014 Google Summer of Code]. Check [https://developers.google.com/open-source/soc/ Google Developers site] for more information on how the program works.
We need to get in this time!

Link to call for participation: [http://google-opensource.blogspot.com/2014/02/mentoring-organization-applications-now.html here]

Link to FAQs: [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2014/help_page here]

=== What is Openstack? ===

[http://www.openstack.org/software/ Openstack] is an open-source IaaS cloud computing platform. Its mission is to provide a flexible solution for both public and private clouds of any size, and for this matter two basic requirements are considered: clouds must be simple to implement and massively scalable.

To meet these principles OpenStack is divided into different components that work together. It's [http://www.openstack.org/software/openstack-compute/ computing], [http://www.openstack.org/software/openstack-storage/ storage], [http://www.openstack.org/software/openstack-networking/ networking], and all the other bits that help make this project, '''The Cloud'''.

OpenStack is [http://i.imgur.com/gAyoiF8.png continuously growing] and new and exciting projects are being discussed everyday.

We encourage new contributors to participate and help us make OpenStack the most complete, reliable and flexible open-source cloud service!

=== Mentors ===

Due date: February 14, 19:00 UTC.

If you're interested in mentoring for this round, please add your name, email, IRC handle and the kind of projects you're interested in mentoring here:

* Davanum Srinivas - dims - Nova, Oslo
* Debo Dutta - dedutta - Nova, Ceilometer
* [[User:Alejandro_Cabrera|Alejandro Cabrera]] - alcabrera - Marconi, Oslo
* Yathiraj Udupi - Yathi - Nova, Ceilometer
* Fei Long Wang - flwang- Glance
* Boris Pavlovic - boris-42 - Rally
* [[User:Sergey_Lukjanov|Sergey Lukjanov]] - SergeyLukjanov - Savanna (proxy to help find mentor in Savanna community)
* [[User:colinmcnamara|Colin McNamara]] - colinmcnamara - OpenStack Docs, OpenStack Training and ToolChains
* [[User:sriramhere|Sriram Subramanian]] - Fuzz Testing, OpenStack Security
* Balint Kovacs - blint@balabit.hu - Zorp
* Szilard Pfeiffer - floss@pfeifferszilard.hu - Zorp

=== Students ===

Students application period opens March 21 and ends on April 21.

If you'd like to get started on your proposal early, go ahead and add your name, location, e-mail, IRC handle and the project you are interested in (if you already know about that!) here:

* Adnan Khan, Canada, khnd06@gmail.com [project not selected yet]
* Anastasios Andronidis, Greece, andronat_asf@hotmail.com. Proposed: [https://docs.google.com/document/d/1mWWSyftZYXxfXKzOBVeVma8KJbQRmYNPnns3oixHVMk/edit?usp=sharing Glance Scalable Image Precaching]
* Artem Shepelev, Russia, e-mail: shepelev.artem@gmail.com, ashepelev at irc.freenode.net, OpenStack Scheduler.
* Victoria Martínez de la Cruz - Argentina - victoria@vmartinezdelacruz.com - vkmc - OpenStack Message Queuing (Marconi)
* [[User:Damon_Wang|Wei Wang]], China, damon.devops@gmail.com, Neutron & Keystone
* Kumar Rishabh, India, email: shailrishabh@gmail.com [would fill more details later]

=== Communication ===

Get in touch with mentors and students through the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev openstack-dev mailing list].

Also, you can find us at IRC in #openstack-gsoc at irc.freenode.org.

=== Ideas ===

Here are some project suggestions students can choose for their applications. This doesn't mean students have to stick strictly to this list; don't hesitate in propose projects by your own. For the latter, it would be great if you could submit a draft proposal and a estimated timeline.

When writing your proposal, try to estimate your timeline to fit the 4 month period of GSoC coding. Also, take into account that '''GSoC does not consider other projects than coding''', so other ideas (like community tasks or i18n efforts) are not suitable for this internship.

Click on the proposed project that caught your attention to get the details about the assumed knowledge, the project goals and more details related to it.

==== Fuzz Testing (various projects) ====

Fuzz testing or fuzzing is a software testing technique, often automated or semi-automated, that involves providing invalid, unexpected, or random data to the inputs of a computer program. The program is then monitored for exceptions such as crashes, or failing built-in code assertions or for finding potential memory leaks. Fuzzing is commonly used to test for security problems in software or computer systems.

{| class="wikitable"
|-
| Difficulty || Hard
|-
| Topics || testing, tempest
|-
| Mentor || Sriram Subramanian
|}

Proposed ideas,

* [[GSoC2014/Testing/Fuzz|Implement a Fuzz testing framework that can be run on Tempest or a similar framework]]

==== OpenStack Scheduler (Gantt) ====

Gantt provides a common scheduler framework for use by various OpenStack components.

Check out more details about [https://github.com/openstack/gantt Gantt]!

{| class="wikitable"
|-
| Difficulty || Medium
|-
| Topics || schedulers, python, gantt
|-
| Mentor || Debo
|}

Proposed ideas,

* [[GSoC2014/Scheduler/StandAloneScheduler|Implement a stand-alone scheduler based on the scheduler forklift code]]
* [[GSoC2014/Scheduler/ScalableScheduler|Implement a scalable scheduler]]
* [[GSoC2014/Scheduler/CrossServicesScheduler|Implement a cross-services scheduler]]

==== OpenStack Message Queuing Service (Marconi) ====

Openstack Message Queuing Service (Marconi) provides a distributed queue. The basic concept is simple:

* Create a queue
* Post messages
* Read them or claim them

For full details on Marconi project, check out the [https://wiki.openstack.org/wiki/Marconi wiki]!

{| class="wikitable"
|-
| Difficulty || Medium
|-
| Topics || storage, python, marconi
|-
| Mentor || Alejandro Cabrera
|}

Proposed ideas,

* [[GSoC2014/Queues/Storage | Add a New Storage Backend]]

==== OpenStack Incubator (Oslo) ====

The Oslo program produces a set of python libraries containing infrastructure code shared by OpenStack projects. The APIs provided by these libraries should be high quality, stable, consistent and generally useful.

Check out more details about Oslo project on the [https://wiki.openstack.org/wiki/oslo wiki]

{| class="wikitable"
|-
| Difficulty ||
|-
| Topics || storage, python, oslo
|-
| Mentor || Alejandro Cabrera, Davanum Srinivas
|}

Proposed ideas,

* [[GSoC2014/Incubator/Storage|Add a new backend to oslo.cache (Redis, sqlite, etc.)]]
* [[GSoC2014/Incubator/SharedLib|Implement a re-usable shared library for vmware (oslo.vmware) to be consumed by various OpenStack projects like Nova, Cinder or Glance]]
* [[GSoC2014/Incubator/Plugin|Define a new layer/abstraction in Nova for plugging-in vCenter and ovirt (since they span multiple hosts)]]

==== OpenStack Benchmarking System (Rally) ====

OpenStack QA team mostly works on CI/CD that ensures that new patches don't break specific single node installation of OpenStack. On the other hand it's clear that such CI/CD is only an indication and does not cover all cases (e.g. if cloud works well on single node installation it doesn't mean that it will work good as well on 1k servers installation under high load).. Rally aims to fix this and help us to get answer on question "How OpenStack works at scale". To make it possible we are going to automate and unify all steps that are required for benchmarking OpenStack at scale: multi node OS deployment, verification, benchmarking & profiling.

[[File:Rally-Actions.png|500px|center]]

* Deploy is not yet another deployer of OpenStack it is just a plugable mechanism that allows to unify & simplify work with different deployers like: DevStack, Fuel, Anvil on hardware/VMs that you have.
* Verify - (work in progress) Use tempest to verify functionality of deployed openstack. In future Rally will support other OS verifiers.
* Benchmark - Smart combination of Framework, Load generation & Big repository of benchmarks.

For more details about Rally project, check out [https://wiki.openstack.org/wiki/rally wiki]

{| class="wikitable"
|-
| Difficulty || Medium
|-
| Topics || rally, benchmarks, deploying, python, tempest,
|-
| Mentor || Boris Pavlovic
|}

Proposed ideas,

* Benchmarking OpenStack
* Writing new benchmarks
* Integration of Rally & Tempest
* Processing Results
* Improving Rally deploying system

==== OpenStack Networking (Neutron) ====

Neutron is an OpenStack project to provide Networking-as-a-Service between interface devices (e.g., vNICs) managed by other Openstack services (e.g., Nova).

For full details about Neutron, check out the [https://wiki.openstack.org/wiki/Neutron wiki]

{| class="wikitable"
|-
| Difficulty || Medium
|-
| Topics || drivers, python, networking, fwaas, neutron
|-
| Mentor || Balint Kovacs, Szilard Pfeiffer
|}

Proposed ideas,

* [[GSoC2014/Network/Driver|Implement an application-level FWaaS driver]] ([https://github.com/balabit/zorp/wiki/zorp Zorp])

==== OpenStack Data Processing (Savanna) ====

Savanna aims to provide users with simple means to provision a Hadoop cluster by specifying several parameters like Hadoop version, cluster topology, nodes hardware details and a few more. The aim of this project is to enable users provision and management of Hadoop clusters on OpenStack.

Check out the [https://wiki.openstack.org/wiki/Savanna wiki] to learn more about Savanna

{| class="wikitable"
|-
| Difficulty ||
|-
| Topics || plugins, hadoop provision, savanna
|-
| Mentor ||
|}

Proposed ideas,

* [[GSoC2014/DataProcessing/Plugin|Develop a new plugin for Savanna to extend savanna.plugins.provisioning:ProvisioningPluginBase class and implement all the required methods.]]

=== Projects ===

Current mentors are willing to supervise students in the following projects:

* [https://wiki.openstack.org/wiki/Nova Openstack Compute (Nova)]
* [https://wiki.openstack.org/wiki/Climate OpenStack Reservation (Climate)]
* [https://github.com/openstack/gantt OpenStack Common Scheduler (Gantt)]
* [https://wiki.openstack.org/wiki/Marconi OpenStack Message Queuing (Marconi)]
* [https://wiki.openstack.org/wiki/Oslo OpenStack Common Libraries (Oslo)]
* [https://wiki.openstack.org/wiki/Neutron OpenStack Networking (Neutron)]
* [https://wiki.openstack.org/wiki/Swift OpenStack Object Storage (Swift)]
* [https://wiki.openstack.org/wiki/Cinder OpenStack Block Storage (Cinder)]
* [https://wiki.openstack.org/wiki/Heat OpenStack Orchestration (Heat)]
* [https://wiki.openstack.org/wiki/Savanna OpenStack Data Processing (Savanna)]
* [https://wiki.openstack.org/wiki/Ceilometer OpenStack Telemetry (Ceilometer)]
* [https://wiki.openstack.org/wiki/Rally OpenStack Benchmarking System (Rally) ]

GSoC2014/Testing/Fuzz

2014-02-14T18:16:13Z

Sriramhere: /* Implement a Fuzz testing framework that can be run on Tempest or a similar framework */

= Implement a Fuzz testing framework that can be run on Tempest or a similar framework =

{| class="wikitable"
|-
| Difficulty || Hard
|-
| Topics || testing, tempest
|-
| Mentor || Sriram Subramanian
|}

== Introduction ==
OpenStack project is getting larger and more complex. It's adoption has also increased significantly, with customers expecting it to be more secure. Currently, many efforts are underway to ensure OpenStack platform is secure. But, an automated mechanisms to test for vulnerabilities is not part of OpenStack testing/ gating process yet. This results in most of the vulnerabilities reported are discovered at the customer site.

There are different mechanisms to test for security vulnerabilities, [http://en.wikipedia.org/wiki/Fuzz_testing Fuzz testing] being most popular of them. This project aims at enabling fuzz testing of OpenStack APIs and integrating such tests with OpenStack test framework such as [http://docs.openstack.org/developer/tempest/ Tempest].

== Assumed Knowledge ==
* Python
* Introduction to OpenStack or Cloud Management Platforms is preferred, but not required
* Introduction to Fuzz testing/ Penetration testing is preferred, but not required

== Project Goals ==

* Design and Implement Fuzz testing framework that can fuzz OpenStack APIs by generating configurable combninarions (random or pattern based)
* Integrate above fuzz test framework with OpenStack Tempest test framework
* Enable fuzz testing on at least one OpenStack project (OpenStack Nova for example)

== Project Nice-to-Haves ==
* Enable on more than one OpenStack project (OpenStack Swift for example)
* Enable automated reporting of security vulnerabilities to the OpenStack Security Group

====== Suggestions ======

GSoC2014/Testing/Fuzz

2014-02-14T18:08:55Z

Sriramhere: /* Implement a Fuzz testing framework that can be run on Tempest or a similar framework */

= Implement a Fuzz testing framework that can be run on Tempest or a similar framework =

{| class="wikitable"
|-
| Difficulty || Hard
|-
| Topics || testing, tempest
|-
| Mentor || Sriram Subramanian
|}

Intro - Why we need it
OpenStack project is getting larger and more complex. It's adoption has also increased significantly, with customers expecting it to be more secure. Currently, many efforts are underway to ensure OpenStack platform is secure. But, an automated mechanisms to test for vulnerabilities is not part of OpenStack testing/ gating process yet. This results in most of the vulnerabilities reported are discovered at the customer site.

There are different mechanisms to test for security vulnerabilities, Fuzz testing being most popular of them. This project aims at enabling fuzz testing of OpenStack APIs and integrating such tests with OpenStack test framework such as Tempest.

== Assumed Knowledge ==
* Python
* Introduction to OpenStack or Cloud Management Platforms is preferred, but not required
* Introduction to Fuzz testing/ Penetration testing is preferred, but not required

== Project Goals ==

* Enable project by project, success being enabling on at least 1 complete project

== Project Nice-to-Haves ==

====== Suggestions ======

User:Sriramhere

2014-02-13T21:55:27Z

Sriramhere: Created page with "LaunchPad: https://launchpad.net/~sriramhere"

LaunchPad: https://launchpad.net/~sriramhere

GSoC2014

2014-02-13T21:53:00Z

Sriramhere: /* Mentors */

= Google Summer of Code 2014 =

[http://www.openstack.org/software/ OpenStack] is applying as a mentoring organization for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 2014 Google Summer of Code]. Check [https://developers.google.com/open-source/soc/ Google Developers site] for more information on how the program works.
We need to get in this time!

Link to call for participation: [http://google-opensource.blogspot.com/2014/02/mentoring-organization-applications-now.html here]

Link to FAQs: [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2014/help_page here]

== What is Openstack? ==

[http://www.openstack.org/software/ Openstack] is: an Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable.

It's [http://www.openstack.org/software/openstack-compute/ computing], [http://www.openstack.org/software/openstack-storage/ storage], [http://www.openstack.org/software/openstack-networking/ networking], and all the other bits that help make the cloud, '''The Cloud'''.

== Mentors ==

Due date: February 14, 19:00 UTC.

If you're interested in mentoring for this round, please add your name, email, IRC handle and the kind of projects you're interested in mentoring here:

* Debo Dutta
* Davanum Srinivas
* [[User:Alejandro_Cabrera|Alejandro Cabrera]]: (Queues, Oslo)
* Yathiraj Udupi
* Fei Long Wang (Glance)
* Boris Pavlovic aka boris-42 (Rally)
* [[User:Sergey_Lukjanov|Sergey Lukjanov]] (Savanna) - proxy to help find mentor in Savanna community
* [[User:colinmcnamara|Colin McNamara]] (OpenStack Docs) - OpenStack Training and ToolChains
* [[User:sriramhere|Sriram Subramanian]] (Fuzz Testing) - OpenStack Security

== Students ==

Students application period opens March 21 and ends on April 21.

If you'd like to get started on your proposal early, go ahead and add your name, location, e-mail, IRC handle and the project you are interested in (if you already know about that!) here:

* Adnan Khan, Canada, khnd06@gmail.com [project not selected yet]
* Anastasios Andronidis, Greece, andronat_asf@hotmail.com. Proposed: [https://docs.google.com/document/d/1mWWSyftZYXxfXKzOBVeVma8KJbQRmYNPnns3oixHVMk/edit?usp=sharing Glance Scalable Image Precaching]
* Artem Shepelev, Russia, e-mail: shepelev.artem@gmail.com, ashepelev at irc.freenode.net, OpenStack Scheduler.
* Victoria Martínez de la Cruz - Argentina - victoria@vmartinezdelacruz.com - vkmc - OpenStack Message Queue (Marconi)
* Wei Wang, China, damon.devops@gmail.com, Neutron & Keystone
* Kumar Rishabh, India, email: shailrishabh@gmail.com [would fill more details later]

== Communication ==

Get in touch with mentors and students through the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev openstack-dev mailing list].
Also, you can find us at IRC in #openstack-gsoc at irc.freenode.org.

== Ideas ==

Here are some project suggestions students can choose for their applications. This doesn't mean students have to stick strictly to this list; don't hesitate in propose projects by your own. For the latter, it would be great if you could submit a draft proposal and a estimated timeline.

When writing your proposal, try to estimate your timeline to fit the 4 month period of GSoC coding. Also, take into account that '''GSoC does not consider other projects than coding''', so other ideas (like community tasks or i18n efforts) are not suitable for this internship.

==== Fuzz Testing (various projects) ====
* Implement a Fuzz testing framework that can be run on Tempest or a similar framework
* Enable project by project, success being enabling on at least 1 complete project

==== OpenStack Scheduler (Gantt/Climate) ====

* Implement a stand-alone scheduler based on the scheduler forklift code
* Implement a scalable scheduler
* Implement a cross-services scheduler

==== OpenStack Queues (Marconi) ====

Openstack Queues provides a distributed queue. The basic concept is simple:

* Create a queue
* Post messages
* Read them or claim them

For full details on the Openstack Queues project, check out the [https://wiki.openstack.org/wiki/Marconi wiki]!

Project ideas are enumerated below.

* [[GSoC2014/Queues/Storage | Add a New Storage Backend]]

==== OpenStack Incubator (Oslo) ====

* Add a new backend to oslo.cache (Redis, sqlite, etc.)

==== OpenStack Benchmarking System (Rally) ====

* Benchmarking OpenStack
* Writing new benchmarks
* Integration of Rally & Tempest
* Processing Results
* Improving Rally deploying system

For more details ping me (boris-42 at freenode on #openstack-rally)
Wiki: [[Rally]]

==== OpenStack Networking (Neutron) ====

* Implement an application-level FWaaS driver ([http://freecode.com/projects/zorp Zorp])

== Projects ==

Current mentors are willing to supervise students in the following projects:

* [https://wiki.openstack.org/wiki/Nova Openstack Compute (Nova)]
* [https://wiki.openstack.org/wiki/Climate OpenStack Reservation (Climate)]
* OpenStack Common Scheduler (Gantt)
* [https://wiki.openstack.org/wiki/Marconi OpenStack Queues (Marconi)]
* [https://wiki.openstack.org/wiki/Oslo OpenStack Common Libraries (Oslo)]
* [https://wiki.openstack.org/wiki/Neutron OpenStack Networking (Neutron)]
* [https://wiki.openstack.org/wiki/Swift OpenStack Object Storage (Swift)]
* [https://wiki.openstack.org/wiki/Cinder OpenStack Block Storage (Cinder)]
* [https://wiki.openstack.org/wiki/Heat OpenStack Orchestration (Heat)]
* [https://wiki.openstack.org/wiki/Savanna OpenStack Data Processing (Savanna)]
* [https://wiki.openstack.org/wiki/Ceilometer OpenStack Telemetry (Ceilometer)]
* [https://wiki.openstack.org/wiki/Rally OpenStack Benchmarking system (Rally) ]
* Performance evaluation

GSoC2014

2014-02-13T21:50:10Z

Sriramhere: /* Ideas */

= Google Summer of Code 2014 =

[http://www.openstack.org/software/ OpenStack] is applying as a mentoring organization for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 2014 Google Summer of Code]. Check [https://developers.google.com/open-source/soc/ Google Developers site] for more information on how the program works.
We need to get in this time!

Link to call for participation: [http://google-opensource.blogspot.com/2014/02/mentoring-organization-applications-now.html here]

Link to FAQs: [http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2014/help_page here]

== What is Openstack? ==

[http://www.openstack.org/software/ Openstack] is: an Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable.

It's [http://www.openstack.org/software/openstack-compute/ computing], [http://www.openstack.org/software/openstack-storage/ storage], [http://www.openstack.org/software/openstack-networking/ networking], and all the other bits that help make the cloud, '''The Cloud'''.

== Mentors ==

Due date: February 14, 19:00 UTC.

If you're interested in mentoring for this round, please add your name, email, IRC handle and the kind of projects you're interested in mentoring here:

* Debo Dutta
* Davanum Srinivas
* [[User:Alejandro_Cabrera|Alejandro Cabrera]]: (Queues, Oslo)
* Yathiraj Udupi
* Fei Long Wang (Glance)
* Boris Pavlovic aka boris-42 (Rally)
* [[User:Sergey_Lukjanov|Sergey Lukjanov]] (Savanna) - proxy to help find mentor in Savanna community
* [[User:colinmcnamara|Colin McNamara]] (OpenStack Docs) - OpenStack Training and ToolChains

== Students ==

Students application period opens March 21 and ends on April 21.

If you'd like to get started on your proposal early, go ahead and add your name, location, e-mail, IRC handle and the project you are interested in (if you already know about that!) here:

* Adnan Khan, Canada, khnd06@gmail.com [project not selected yet]
* Anastasios Andronidis, Greece, andronat_asf@hotmail.com. Proposed: [https://docs.google.com/document/d/1mWWSyftZYXxfXKzOBVeVma8KJbQRmYNPnns3oixHVMk/edit?usp=sharing Glance Scalable Image Precaching]
* Artem Shepelev, Russia, e-mail: shepelev.artem@gmail.com, ashepelev at irc.freenode.net, OpenStack Scheduler.
* Victoria Martínez de la Cruz - Argentina - victoria@vmartinezdelacruz.com - vkmc - OpenStack Message Queue (Marconi)
* Wei Wang, China, damon.devops@gmail.com, Neutron & Keystone
* Kumar Rishabh, India, email: shailrishabh@gmail.com [would fill more details later]

== Communication ==

Get in touch with mentors and students through the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev openstack-dev mailing list].
Also, you can find us at IRC in #openstack-gsoc at irc.freenode.org.

== Ideas ==

Here are some project suggestions students can choose for their applications. This doesn't mean students have to stick strictly to this list; don't hesitate in propose projects by your own. For the latter, it would be great if you could submit a draft proposal and a estimated timeline.

When writing your proposal, try to estimate your timeline to fit the 4 month period of GSoC coding. Also, take into account that '''GSoC does not consider other projects than coding''', so other ideas (like community tasks or i18n efforts) are not suitable for this internship.

==== Fuzz Testing (various projects) ====
* Implement a Fuzz testing framework that can be run on Tempest or a similar framework
* Enable project by project, success being enabling on at least 1 complete project

==== OpenStack Scheduler (Gantt/Climate) ====

* Implement a stand-alone scheduler based on the scheduler forklift code
* Implement a scalable scheduler
* Implement a cross-services scheduler

==== OpenStack Queues (Marconi) ====

Openstack Queues provides a distributed queue. The basic concept is simple:

* Create a queue
* Post messages
* Read them or claim them

For full details on the Openstack Queues project, check out the [https://wiki.openstack.org/wiki/Marconi wiki]!

Project ideas are enumerated below.

* [[GSoC2014/Queues/Storage | Add a New Storage Backend]]

==== OpenStack Incubator (Oslo) ====

* Add a new backend to oslo.cache (Redis, sqlite, etc.)

==== OpenStack Benchmarking System (Rally) ====

* Benchmarking OpenStack
* Writing new benchmarks
* Integration of Rally & Tempest
* Processing Results
* Improving Rally deploying system

For more details ping me (boris-42 at freenode on #openstack-rally)
Wiki: [[Rally]]

==== OpenStack Networking (Neutron) ====

* Implement an application-level FWaaS driver ([http://freecode.com/projects/zorp Zorp])

== Projects ==

Current mentors are willing to supervise students in the following projects:

* [https://wiki.openstack.org/wiki/Nova Openstack Compute (Nova)]
* [https://wiki.openstack.org/wiki/Climate OpenStack Reservation (Climate)]
* OpenStack Common Scheduler (Gantt)
* [https://wiki.openstack.org/wiki/Marconi OpenStack Queues (Marconi)]
* [https://wiki.openstack.org/wiki/Oslo OpenStack Common Libraries (Oslo)]
* [https://wiki.openstack.org/wiki/Neutron OpenStack Networking (Neutron)]
* [https://wiki.openstack.org/wiki/Swift OpenStack Object Storage (Swift)]
* [https://wiki.openstack.org/wiki/Cinder OpenStack Block Storage (Cinder)]
* [https://wiki.openstack.org/wiki/Heat OpenStack Orchestration (Heat)]
* [https://wiki.openstack.org/wiki/Savanna OpenStack Data Processing (Savanna)]
* [https://wiki.openstack.org/wiki/Ceilometer OpenStack Telemetry (Ceilometer)]
* [https://wiki.openstack.org/wiki/Rally OpenStack Benchmarking system (Rally) ]
* Performance evaluation

OSSN/OSSN-0008

2013-12-19T19:03:24Z

Sriramhere: /* DoS style attack on noVNC server can lead to service interruption or disruption [WIP] */

== DoS style attack on noVNC server can lead to service interruption or disruption ==

=== Summary ===
Currently, there is no limiting on the number of VNC sessions that can be created for a single user's VNC token which enables one to cause a DoS attack on noVNC browser proxy by requesting multiple server. This prevents subsequent access to VM's VNC console.

=== Affected Services / Software ===
Horizon (VNC Console through browser), Nova (NoVNC proxy), Grizzly

=== Discussion ===
NoVNC Proxy is explained well [http://docs.openstack.org/grizzly/openstack-compute/admin/content//getting-started-with-vnc-proxy.html here].

Once a user gets token to access a VM's VNC console, there is no restriction in the number of times the user can try connecting to the VNC console using the same token. If multiple connection requests are made, any subsequent request could timeout. This could impact users already connected to the VNC sessions, or other users trying to make new connection. This could also impact overall responsiveness of other nova services running in the novnc host.

Thus, a user could make the NoVNC proxy endpoint not responsive/ reachable, thereby resulting in a DoS attack. However, it is to be noted there is no amplification effect.

=== Recommended Actions ===
For current stable releases (Grizzly), users need to workaround this vulnerability by using rate-limiting proxies to cover access to NoVNC hosts. Rate-limiting is a common mechanism to prevent DoS/ Brute-Force attacks. You can find more discussion on rate-limiting around OpenStack Networking Best practices [http://docs.openstack.org/security-guide/content/ch032_networking-best-practices.html here].

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/keystone/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2013-12-19T19:00:01Z

Sriramhere: /* Recommended Actions */

== DoS style attack on noVNC server can lead to service interruption or disruption [WIP] ==

=== Summary ===
Currently, there is no limiting on the number of VNC sessions that can be created for a single user's VNC token which enables one to cause a DoS attack on noVNC browser proxy by requesting multiple server. This prevents subsequent access to VM's VNC console.

=== Affected Services / Software ===
Horizon, Nova, Grizzly

=== Discussion ===
NoVNC Proxy is explained well [http://docs.openstack.org/grizzly/openstack-compute/admin/content//getting-started-with-vnc-proxy.html here].

Once a user gets token to access a VM's VNC console, there is no restriction in the number of times the user can try connecting to the VNC console using the same token. If multiple connection requests are made, any subsequent request could timeout. This could impact users already connected to the VNC sessions, or other users trying to make new connection. This could also impact overall responsiveness of other nova services running in the novnc host.

Thus, a user could make the NoVNC proxy endpoint not responsive/ reachable, thereby resulting in a DoS attack. However, it is to be noted there is no amplification effect.

=== Recommended Actions ===
For current stable releases (Grizzly), users need to workaround this vulnerability by using rate-limiting proxies to cover access to NoVNC hosts. Rate-limiting is a common mechanism to prevent DoS/ Brute-Force attacks. You can find more discussion on rate-limiting around OpenStack Networking Best practices [http://docs.openstack.org/security-guide/content/ch032_networking-best-practices.html here].

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/keystone/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2013-12-19T18:26:24Z

Sriramhere: /* Discussion */

== DoS style attack on noVNC server can lead to service interruption or disruption [WIP] ==

=== Summary ===
Currently, there is no limiting on the number of VNC sessions that can be created for a single user's VNC token which enables one to cause a DoS attack on noVNC browser proxy by requesting multiple server. This prevents subsequent access to VM's VNC console.

=== Affected Services / Software ===
Horizon, Nova, Grizzly

=== Discussion ===
NoVNC Proxy is explained well [http://docs.openstack.org/grizzly/openstack-compute/admin/content//getting-started-with-vnc-proxy.html here].

Once a user gets token to access a VM's VNC console, there is no restriction in the number of times the user can try connecting to the VNC console using the same token. If multiple connection requests are made, any subsequent request could timeout. This could impact users already connected to the VNC sessions, or other users trying to make new connection. This could also impact overall responsiveness of other nova services running in the novnc host.

Thus, a user could make the NoVNC proxy endpoint not responsive/ reachable, thereby resulting in a DoS attack. However, it is to be noted there is no amplification effect.

=== Recommended Actions ===

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/keystone/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2013-12-19T18:26:00Z

Sriramhere: /* Discussion */

== DoS style attack on noVNC server can lead to service interruption or disruption [WIP] ==

=== Summary ===
Currently, there is no limiting on the number of VNC sessions that can be created for a single user's VNC token which enables one to cause a DoS attack on noVNC browser proxy by requesting multiple server. This prevents subsequent access to VM's VNC console.

=== Affected Services / Software ===
Horizon, Nova, Grizzly

=== Discussion ===
NoVNC Proxy is explained well [[http://docs.openstack.org/grizzly/openstack-compute/admin/content//getting-started-with-vnc-proxy.html here]].

Once a user gets token to access a VM's VNC console, there is no restriction in the number of times the user can try connecting to the VNC console using the same token. If multiple connection requests are made, any subsequent request could timeout. This could impact users already connected to the VNC sessions, or other users trying to make new connection. This could also impact overall responsiveness of other nova services running in the novnc host.

Thus, a user could make the NoVNC proxy endpoint not responsive/ reachable, thereby resulting in a DoS attack. However, it is to be noted there is no amplification effect.

=== Recommended Actions ===

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/keystone/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2013-12-19T05:06:10Z

Sriramhere: /* Summary */

OSSN/OSSN-0008

2013-12-19T04:56:57Z

Sriramhere: /* Contacts / References */

== DoS style attack on noVNC server can lead to service interruption or disruption [WIP] ==

=== Summary ===

=== Affected Services / Software ===
Horizon, Nova, Grizzly

=== Discussion ===

=== Recommended Actions ===

=== Contacts / References ===
* This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
* Original LaunchPad Bug : https://bugs.launchpad.net/keystone/+bug/1227575
* OpenStack Security ML : openstack-security@lists.openstack.org
* OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2013-12-19T04:56:26Z

Sriramhere:

== DoS style attack on noVNC server can lead to service interruption or disruption [WIP] ==

=== Summary ===

=== Affected Services / Software ===
Horizon, Nova, Grizzly

=== Discussion ===

=== Recommended Actions ===

=== Contacts / References ===
This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
Original LaunchPad Bug : https://bugs.launchpad.net/keystone/+bug/1227575
OpenStack Security ML : openstack-security@lists.openstack.org
OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2013-12-19T04:55:20Z

Sriramhere:

=== DoS style attack on noVNC server can lead to service interruption or disruption [WIP] ===

=== Summary ===

=== Affected Services / Software ===
Horizon, Nova, Grizzly

=== Discussion ===

=== Recommended Actions ===

=== Contacts / References ===
This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
Original LaunchPad Bug : https://bugs.launchpad.net/keystone/+bug/1227575
OpenStack Security ML : openstack-security@lists.openstack.org
OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2013-12-19T04:54:15Z

Sriramhere:

===DoS style attack on noVNC server can lead to service interruption or disruption [WIP]===

===Summary===

===Affected Services / Software===
Horizon, Nova, Grizzly

===Discussion===

=== Recommended Actions===

===Contacts / References===
This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
Original LaunchPad Bug : https://bugs.launchpad.net/keystone/+bug/1227575
OpenStack Security ML : openstack-security@lists.openstack.org
OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2013-12-19T04:53:18Z

Sriramhere:

DoS style attack on noVNC server can lead to service interruption or disruption [WIP]

===Summary===

===Affected Services / Software===
Horizon, Nova, Grizzly

===Discussion===

=== Recommended Actions===

===Contacts / References===
This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
Original LaunchPad Bug : https://bugs.launchpad.net/keystone/+bug/1227575
OpenStack Security ML : openstack-security@lists.openstack.org
OpenStack Security Group : https://launchpad.net/~openstack-ossg

OSSN/OSSN-0008

2013-12-19T04:50:38Z

Sriramhere: Created page with "DoS style attack on noVNC server can lead to service interruption or disruption [WIP] ### Summary ### ### Affected Services / Software ### Horizon, Nova, Grizzly ### Disc..."

DoS style attack on noVNC server can lead to service interruption or disruption [WIP]

### Summary ###

### Affected Services / Software ###
Horizon, Nova, Grizzly

### Discussion ###

### Recommended Actions ###

### Contacts / References ###
This OSSN : https://bugs.launchpad.net/ossn/+bug/1227575
Original LaunchPad Bug : https://bugs.launchpad.net/keystone/+bug/1227575
OpenStack Security ML : openstack-security@lists.openstack.org
OpenStack Security Group : https://launchpad.net/~openstack-ossg

Security Notes

2013-12-19T04:45:42Z

Sriramhere: /* Published Security Notes */

The OpenStack Security Group (OSSG) publishes Security Notes to advise users of security related issues. Security notes are similar to advisories; they address vulnerabilities in 3rd party tools typically used within OpenStack deployments and provide guidance on common configuration mistakes that can result in an insecure operating environment.

=== Published Security Notes ===
* [[OSSN/1227575|1227575]] - DoS style attack on noVNC server can lead to service interruption or disruption (20 Dec 2013)
* [[OSSN/1226078|1226078]] - Glance allows sharing of images between projects without consumer project approval (11 Dec 2013)
* [[OSSN/1237989|1237989]] - Authenticated users are able to update passwords without providing their current password (22 Nov 2013)
* [[OSSN/1168252|1168252]] - Keystone configuration should not be world readable (13 May 2013)
* [[OSSN/1155566|1155566]] - HTTP POST limiting advised to avoid Essex/Folsom Keystone DoS (23 Apr 2013)
* [[OSSN/1098582|1098582]] - Selecting LXC as Nova Virtualization Driver can lead to data compromise (15 Mar 2013)