OpenStack - User contributions [en]

People

2014-03-12T15:15:11Z

Adrian Smith:

= Translation for IRC nicknames =
Each name is linked to a bio page for that individual. Please add yourself
{| border="1" cellpadding="2" cellspacing="0"
| '''IRC Nickname'''
| '''Real Name'''
| '''Company or Role'''
|-
| _0x44
| [[_0x44|Christopher MacGown]]
| Piston Cloud Founder, Nova Core Team member, Former Ozone developer
|-
| Vivek / VivekVC
| [[Vivek / VivekVC|Vivek Varghese Cherian]]
| Technical Specialist / Senior Project Lead - Syntel Inc, OpenStack Cloud Architect, DevOps Architect
|-
| adiantum
| [[IlyaAlekseyev]]
| Nova Developer
|-
| adrian17od
| [[Adrian Smith]]
| Software Engineer - Workday
|-
| akscram
| Ilya Kharin
| Software Engineer, Mirantis
|-
| alexpilotti
| Alessandro Pilotti
| CEO, Cloudbase Solutions
|-
| vitola
| [[Vitola|Alex Vitola]]
| System Administrator - DevOps , [http://www.deserv.eti.br/ Deserv - Tecnologia & Serviços]
|-
| ameade
| Alex Meade
| Ozone Developer
|-
| amotoki
| Akihiro Motoki
| Quantum developer, NEC
|-
| andrewbogott
| [[andrewbogott|Andrew Bogott]]
| Developer, Wikimedia Foundation
|-
| annegentle
| [[AnneGentle|Anne Gentle]]
| [[OpenStack]] Technical Writer, Casual nick arriety
|-
| anotherjesse
| [[JesseAndrews|Jesse Andrews]]
| [[AnsoLabs]] co-founder, Nebula chief architect
|-
| alekibango
| [[David Pravec]]
| Free and Open Source Software Specialist
|-
| [[ArseneRei]]
| Stephon Striplin
| Developer, DreamHost
|-
| [http://adam.younglogic.com ayoung]
| Adam Young
| Senior Software Engineer, Red Hat
|-
| cleverdevil
| [[JonathanLaCour|Jonathan LaCour]]
| Vice President, Software Development, DreamHost
|-
| bcwaldon
| Brian Waldon
| Rackspace Cloud Builders Developer
|-
| bencherian
| [[BenCherian|Ben Cherian]]
| General Manager, Emerging Technologies, DreamHost
|-
| berendt
| [[ChristianBerendt|Christian Berendt]]
| Consultant/Developer, B1 Systems
|-
| BK_man
| [[AndreyBrindeyev|Andrey Brindeyev]]
| Grid Dynamics International
|-
| blamar
| Brian Lamar
| Ozone Developer
|-
| btorch
| [[btorch|Marcelo Martins]]
| Swift System Engineer
|-
| carlp
| [[carlp|Carl Perry]]
| System Administrator, DreamHost (New Dream Network)
|-
| cerberus
| [[cerberus|Matt Dietz]]
| Ozone Developer
|-
| chemikadze
| [[NikolaySokolov|Nikolay Sokolov]]
| [[GridDynamics]] Developer
|-
| chidical
| [[chidical|Chidi Alams]]
| Systems Engineer
|-
| chmouel
| [[Chmouel|Chmouel Boudjnah]]
| Rackspace Developer
|-
| colinnich
| Colin Nicholson
| Software Developer, iomart group
|-
| comstud
| [[comstud|Chris Behrens]]
| Ozone Developer
|-
| creiht
| [[creiht|Chuck Thier]]
| Swift Developer
|-
| cwright
| [[CoryWright|Cory Wright]]
| Rackspace Operations
|-
| dabo
| [[dabo|Ed Leafe]]
| Ozone Developer
|-
| dachary
| [[dachary|Loic Dachary]]
| [http://enovance.com/ eNovance] CRO and [https://alioth.debian.org/projects/openstack/ Debian GNU/Linux packager]
|-
| davidhadas
| David Hadas
| Swift, IBM Research
|-
| danwent
| Dan Wendlandt
| Quantum developer, PTL
|-
| dendrobates
| [[RickClark|Rick Clark]]
| [[OpenStack]] Project Lead & Chief Architect
|-
| devananda
| [[Devananda|Devananda van der Veen]]
| Nova Baremetal Driver, Openstack-on-Openstack, HP Cloud
|-
| devcamcar
| [[DevinCarlen|Devin Carlen]]
| Founder of Nebula Inc, Nova Core Member, PTL Horizon, [[OpenStack]] POC
|-
| dhellmann
| [[DougHellmann|Doug Hellmann]]
| DreamHost
|-
| dtroyer
| Dean Troyer
| Rackspace Cloudbuilders
|-
| DuncanT
| Duncan Thomas
| HP - Nova and Nova-volume team
|-
| eday
| [[eday|Eric Day]]
| Open Source Architect / Developer
|-
| egallen
| [[egallen|Erwan Gallen]]
| Cloudwatt
|-
| eharney
| [[eharney|Eric Harney]]
| Red Hat
|-
| emagana
| Edgar Magana
| Technical Lead, Cisco - CTO Cloud Computing
|-
| exlt
| [[exlt|Michael Shuler]]
| Swift Systems Engineer
|-
| fifieldt
| [[User:Fifieldt|Tom Fifield]]
| NeCTAR, OpenStack Foundation
|-
| fungi
| [[User:fungi|Jeremy Stanley]]
| project infrastructure, developer community resources and continuous integration systems
|-
| garyk
| Gary Kotton
| VMware
|-
| gholt
| [[gholt|Greg Holt]]
| Swift Developer
|-
| glange
| [[glange|Greg Lange]]
| Swift Developer
|-
| glenc
| [[GlenCampbell|Glen Campbell]]
| Architect/Analyst
|-
| gongys
| Yong Sheng Gong
| IBM
|-
| guitarzan
| Cory Stone
| Rackspace
|-
| gundlach
| [[gundlach|Michael Gundlach]]
| Ozone Developer
|-
| h1nch
| [[h1nch|John Hincher]]
| Systems Engineer
|-
| heckj
| [[JosephHeck|Joe Heck]]
| Developer / Systems Engineer
|-
| hemna
| [[walter-boring|Walter A. Boring IV]]
| HP - Cinder core member
|-
| ironcamel
| Naveed Massjouni
| Ozone Developer
|-
| jaypipes
| [[jaypipes|Jay Pipes]]
| Open Source Architect / Developer
|-
| jc_smith
| [[jcsmith|Jean-Christophe "JC" Smith]]
| Architect
|-
| jeblair
| [[JamesBlair|James Blair]]
| Developer and CI Infrastructure
|-
| jgriffith
| [[JohnGriffith|John Griffith]]
| BlockStorage Technical Lead
|-
| jk0
| [[jk0|Josh Kearney]]
| Ozone Developer
|-
| jmeridth
| [[jmeridth|Jason Meridth (JM)]]
| Ozone Developer
|-
| johnthetubaguy
| [[johngarbutt|John Garbutt]]
| Senior Software Developer, Citrix Systems
|-
| johnpur
| [[JohnPurrier|John Purrier]]
| [[OpenStack]]/Rackspace liaison
|-
| joshuamckenty
| [[joshuamckenty|Joshua McKenty]]
| Piston Cloud Founder, Nova Core Team member, [[OpenStack]] POC, formerly NASA Nebula Architect
|-
| k4n0
| [[k4n0|Rohan Rhishikesh Kanade]]
| Izel Technologies, Senior Software Engineer
|-
| koolhead17
| Atul Jha
| App Specialist, Csscorp
|-
| kpepple
| [[KenPepple|Ken Pepple]]
| Consultant / Architect / Developer
|-
| KMarsh
| Kyle Marsh
| Developer, DreamHost
|-
| [[LinuxJedi]]
| [[LinuxJedi|Andrew Hutchings]]
| Developer Infrastructure and Software Engineer, HP
|-
| littleidea
| [[littleidea|Andrew Clay Shafer]]
| Cloudscaling
|-
| letterj
| [[letterj|Jay Payne]]
| Data Catalyst
|-
| lloydde
| [[lloydde|Lloyd Dewolf]]
| Piston Cloud, Director of Customer Care
|-
| lorin1
| [[LorinHochstein|Lorin Hochstein]]
| Lead Architect, Nimbis Services
|-
| Mandell
| [[mdegerne|Mandell Degerness]]
| Piston Cloud, Systems Analyst
|-
| maoy
| [[maoy|Yun Mao]]
| AT&T Labs - Research, Researcher
|-
| markmc
| [[markmc|Mark McLoughlin]]
| Principal Software Engineer, Red Hat
|-
| [[MarkAtwood]]
| [[MarkAtwood|Mark Atwood]]
| Director - Open Source Evangelism, HP
|-
| markvoelker
| [[markvoelker|Mark Voelker]]
| Software Development Manager, Cisco
|-
| markwash
| Mark Washenberger
| Ozone Developer
|-
| matiu
| [[matiu|Matthew Sherborne]]
| Nova Dev - Rackspace
|-
| mattt
| [[mattt|Matt Thompson]]
| Systems Engineer
|-
| mattray
| [[Matt Ray]]
| Senior Technical Evangelist, Opscode
|-
| mestery
| Kyle Mestery
| Quantum developer
|-
| mikal
| [[Michael Still]]
| Rackspace Australia
|-
| mnot
| [[mnottingham|Mark Nottingham]]
| Rackspace
|-
| morellon
| [[Thiago Morello]]
| Locaweb
|-
| mtaylor
| [[MontyTaylor|Monty Taylor]]
| Developer Infrastructure and CI Manager, HP
|-
| murkk
| [[murkk|Chris Blumentritt]]
| Ozone Systems Engineer
|-
| n0ano
| [[n0ano|Don Dugger]]
| Software engineer, Intel
|-
| ncode
| [[Juliano Martinez]]
| Locaweb
|-
| ndipanov
| Nikola Đipanov
| Red Hat
|-
| notmyname
| [[notmyname|John Dickinson]]
| Swift Developer
|-
| nelson
| [[nelson|Russ Nelson]]
| Wikipedia Contractor
|-
| oubiwann
| [[oubiwann|Duncan McGreggor]]
| Cloud Engineering Manager, DreamHost
|-
| ozstacker
| [[ozstacker|Tristan Goode]]
| Australian [[OpenStack]] User Group Co-Ordinator, CEO Aptira
|-
| pandemicsyn
| [[pandemicsyn|Florian Hines]]
| Swift Engineering Monkey
|-
| patrocinio
| Eduardo Patrocinio
| IBM
|-
| pixelbeat
| [[p-draigbrady|Pádraig Brady]]
| Red Hat, Nove core team member
|-
| pknouff
| Philip Knouff
| Ozone Developer
|-
| [[PotHix]]
| Willian Molinari
| Locaweb
|-
| pvo
| [[pvo|Paul Voccio]]
| Ozone Manager
|-
| blakeyeager
| [[blakeyeager|Blake Yeager]]
| Product Manager, Rackspace Cloud
|-
| rackerhacker
| [[major|Major Hayden]]
| Systems Engineer
|-
| rahmu
| [[rahmu|Joe Hakim Rahme]]
| eNovance
|-
| rainya
| Rainya Mosher
| Ozone SDLC Project Manager
|-
| Razique
| [[RaziqueMahroua|Razique Mahroua]]
| Nevrotic Openstacker and Technical Writer
|-
| rbergeron
| [[RobynBergeron|Robyn Bergeron]]
| Fedora Marketing & Cloud Person
|-
| redbo
| [[redbo|Michael Barton]]
| Swift Developer
|-
| reed
| [[StefanoMaffulli|Stefano Maffulli]]
| OpenStack Community Manager
|-
| reldan
| [[reldan|Eldar Nugaev]]
| Software Developer
|-
|-
| rohitk
| [[rohitk|Rohit Karajgi]]
| Technical Lead, NTT Data
|-
| russellb
| [[russellb|Russell Bryant]]
| Red Hat
|-
| salv-orlando
| [[SalvatoreOrlando|Salvatore Orlando]]
| Quantum Core Dev
|-
| sandywalsh
| [[sandywalsh|Sandy Walsh]]
| Core developer (Rackspace - Ozone)
|-
| sarob
| [[sarob|Sean Roberts]]
| Infrastructure Strategy Yahoo!
|-
| sdague
| [[sdague|Sean Dague]]
| Developer, IBM
|-
| sirp
| [[sirp|Rick Harris]]
| Ozone Developer
|-
| s0mik
| [[s0mik|Somik Behera]]
| [[OpenStack]] Quantum Founding Member, Quantum Core Developer, Product@Nicira, Former VMware Core Developer
|-
| SergeyLukjanov
| [[User:Sergey_Lukjanov|Sergey Lukjanov]]
| Tech Lead / Senior Software Engineer / Mirantis
|-
| soren
| [[soren|Soren Hansen]]
| Open Source Architect / Developer
|-
| spy
| [[ant|Antony Messerli]]
| Ozone Systems Engineer
|-
| termie
| [[termie|Andy Smith]]
| Nova Developer
|-
|thimble
| André Nähring
| Consultant, Developer, B1 Systems
|-
| thingee
| Mike Perez
| Developer, DreamHost
|-
| toanster
| Toan Nguyen
| [[OpenStack]] Software Development Manager, Rackspace
|-
| tonywolf
| [[Wolf|Tony Wolf]]
| Ozone Business Analyst
|-
| ttx
| [[ThierryCarrez|Thierry Carrez]]
| OpenStack Release Manager
|-
| tylesmit
| Tyler Smith
| Cisco Developer
|-
| vishy
| [[vishy|Vish Ishaya]]
| Nova Project Technical Lead
|-
| winston-d
| Zhiteng Huang
| Performance Engineer, Intel
|-
| wowdd1
| Zhao Dan
| Developer
|-
| loquacity
| Lana Brindley
| Technical Writer, Rackspace
|-
| osier
| Osier Yang
| Software Engineer, Red Hat
|-
| vrovachev
| Vadim Rovachev
| QA Engineer, Mirantis
|}

Neutron-Linux-Bridge-Plugin

2013-04-19T13:45:43Z

Adrian Smith: Fix: don't restart numbering in lists

* '''Git Branch''': https://github.com/openstack/quantum/tree/master/quantum/plugins/linuxbridge
* '''Created''': Dec 24 2011

'''''Update: This is now merged.'''''

= Quantum L2 Linux Bridge Plugin =

__TOC__

== Abstract ==
The proposal is to implement a Quantum L2 plugin that configures a Linux Bridge to realize Quantum's Network, Port, and Attachment abstractions. Each Quantum network would map to an independent VLAN managed by the plugin. Sub-interfaces corresponding to a VLAN would be created on each host, and a Linux Bridge would be created enslaving that sub-interface. One or more VIFs (VM Interfaces) in that network on that host would then plug into that Bridge. To a certain extent this effort will achieve the goal of creating a Basic VLAN Plugin (as discussed in the Essex Summit) for systems which support a Linux Bridge.

== Requirements ==

Support for Linux Bridge (brctl package).

== Design ==

Plugin manages VLANs. The actual network artifacts are created by an agent (daemon) running on each host on which the Quantum network has to be created. This agent-based approach is similar to the one employed by the OpenVSwitch plugin.

The diagram below explains the working of the plugin and the agent in the context of creating networks and ports, and plugging a VIF into the Quantum port.

[[File:quantum-linux-bridge-plugin-operation.png||Quantum L2 Linux Bridge Plugin Operation]]

# The tenant requests the creation of a Quantum network and a port on that network. The plugin creates a network resource and assigns a VLAN to this network. It then creates a Port resource and associates it with this network.
# The tenant requests the instantiation of a VM. Nova-compute will invoke the Linux-bridge VIF driver (this driver is different from the Linux bridge VIF driver that comes packaged with Nova) will create a tap device. Subsequently nova-compute will instantiate the VM such that the VM's VIF is associated with the tap device.
# The tenant will request plugging the above VIF into the Quantum port created earlier. The plugin will create the association of the VIF and the port in the DB.
# The agent daemon on each host in the network will pick up the association in created in Step 3.
# If a tap device exists on that host corresponding to that VIF, the agent will create a VLAN and a Linux Bridge on that host (if it does not already exist).
#: '''Note''': A convention to use the first 11 characters of the UUID is followed to name the tap device. The agent deciphers the name of the tap device from the VIF UUID using this convention.
# The agent will subsequently enslave the tap device to the Linux Bridge. The VM is now on the Quantum network.

=== Integration with Nova ===

# A nova-compute VIF driver is made available. This VIF driver is very similar to the one used by the OpenVSwitch plugin. This VIF driver is required on every compute node.
# Linux network driver (linux_net.py) extension is also required so as to be able to plug the gateway. As with the VIF driver, this driver also creates a tap device for plugging the Gateway interface. Some more processing happens in this driver with respect to the Gateway IP as explained below. This linux network/gateway driver is required on every nova-network host.

=== Handling the Gateway Interface ===

There is a bit of complexity involved with creating and initializing the Gateway interface. The following the set of operations are performed to achieve this:

# The aforementioned Gateway driver first creates a tap device and associates a MAC address provided by Nova with this device. This happens in the "plug" hook of the driver and executes within nova's process space. Subsequently once this plug method exits, the [[QuantumManager]] will associate a Gateway IP address with this tap device. However, since no VM plugs into this tap device, this tap device will not respond to this IP. To overcome this issue, we right away create the bridge for this network on this host in this plug method and also associate the same Gateway IP address with this bridge. The bridge will now respond to the Gateway IP.
#: '''Note''': We also associate the same MAC address as the Gateway tap device to the bridge. Although the Gateway tap device is not directly responding to the Gateway IP, it is required since for the bridge to work correctly at least one device on the bridge should have the same MAC address. This requirement is satisfied by the Gateway tap device in this case.
# The [[QuantumManager]] (network manager within nova that interfaces with Quantum) plugs the gateway tap device created earlier into a port on the network. This results in a logical binding between the gateway tap device interface ID and the Quantum port/network ([[LinuxBridge]] plugin handles this). This step executes in the Quantum server's process space.
# The agent running on the relevant host picks up the logical binding and also the presence of the gateway tap device. It enslaves the gateway tap device to the relevant bridge (note in this case that the bridge was already created in the linux network/gateway driver). This step executes in the agent's process space.
# The gateway initialization is done in the "initialize_gateway" hook of the linux network driver (linux_net.py). This, among other things, involves associating the DHCP IP address with the Gateway tap device and sending a gratuitous ARP for the gateway IP. This step executes in nova's process space.

(Contact: Sumit Naiksatam, Salvatore Orlando)

People

2013-02-21T09:06:19Z

Adrian Smith: /* Translation for IRC nicknames */

= Translation for IRC nicknames =
Each name is linked to a bio page for that individual. Please add yourself
{| border="1" cellpadding="2" cellspacing="0"
| '''IRC Nickname'''
| '''Real Name'''
| '''Company or Role'''
|-
| _0x44
| [[_0x44|Christopher MacGown]]
| Piston Cloud Founder, Nova Core Team member, Former Ozone developer
|-
| adiantum
| [[IlyaAlekseyev]]
| Nova Developer
|-
| adrian17od
| [[Adrian Smith]]
| Software Engineer - Dell
|-
| ameade
| Alex Meade
| Ozone Developer
|-
| amotoki
| Akihiro Motoki
| Quantum developer, NEC
|-
| andrewbogott
| [[andrewbogott|Andrew Bogott]]
| Developer, Wikimedia Foundation
|-
| annegentle
| [[AnneGentle|Anne Gentle]]
| [[OpenStack]] Technical Writer
|-
| anotherjesse
| [[JesseAndrews|Jesse Andrews]]
| [[AnsoLabs]] co-founder, Nebula chief architect
|-
| alekibango
| [[David Pravec]]
| Free and Open Source Software Specialist
|-
| armmer
| [[armmer|Jason Meridth (JM)]]
| Ozone Developer
|-
| [[ArseneRei]]
| Stephon Striplin
| Developer, DreamHost
|-
| [http://adam.younglogic.com ayoung]
| Adam Young
| Senior Software Engineer, Red Hat
|-
| cleverdevil
| [[JonathanLaCour|Jonathan LaCour]]
| Vice President, Software Development, DreamHost
|-
| bcwaldon
| Brian Waldon
| Rackspace Cloud Builders Developer
|-
| bencherian
| [[BenCherian|Ben Cherian]]
| General Manager, Emerging Technologies, DreamHost
|-
| berendt
| [[ChristianBerendt|Christian Berendt]]
| Consultant/Developer, B1 Systems
|-
| BK_man
| [[AndreyBrindeyev|Andrey Brindeyev]]
| Grid Dynamics International
|-
| blamar
| Brian Lamar
| Ozone Developer
|-
| btorch
| [[btorch|Marcelo Martins]]
| Swift System Engineer
|-
| carlp
| [[carlp|Carl Perry]]
| System Administrator, DreamHost (New Dream Network)
|-
| cerberus
| [[cerberus|Matt Dietz]]
| Ozone Developer
|-
| chemikadze
| [[NikolaySokolov|Nikolay Sokolov]]
| [[GridDynamics]] Developer
|-
| chidical
| [[chidical|Chidi Alams]]
| Systems Engineer
|-
| chmouel
| [[Chmouel|Chmouel Boudjnah]]
| Rackspace Developer
|-
| colinnich
| Colin Nicholson
| Software Developer, iomart group
|-
| comstud
| [[comstud|Chris Behrens]]
| Ozone Developer
|-
| creiht
| [[creiht|Chuck Thier]]
| Swift Developer
|-
| dabo
| [[dabo|Ed Leafe]]
| Ozone Developer
|-
| dachary
| [[dachary|Loic Dachary]]
| [http://enovance.com/ eNovance] CRO and [https://alioth.debian.org/projects/openstack/ Debian GNU/Linux packager]
|-
| davidhadas
| David Hadas
| Swift, IBM Research
|-
| danwent
| Dan Wendlandt
| Quantum developer, PTL
|-
| dendrobates
| [[RickClark|Rick Clark]]
| [[OpenStack]] Project Lead & Chief Architect
|-
| devcamcar
| [[DevinCarlen|Devin Carlen]]
| Founder of Nebula Inc, Nova Core Member, PTL Horizon, [[OpenStack]] POC
|-
| dhellmann
| [[DougHellmann|Doug Hellmann]]
| DreamHost
|-
| dtroyer
| Dean Troyer
| Rackspace Cloudbuilders
|-
| dubs
| [[CoryWright|Cory Wright]]
| Ozone Developer
|-
| DuncanT
| Duncan Thomas
| HP - Nova and Nova-volume team
|-
| eday
| [[eday|Eric Day]]
| Open Source Architect / Developer
|-
| egallen
| [[egallen|Erwan Gallen]]
| CTO, Zinux
|-
| emagana
| Edgar Magana
| Technical Lead, Cisco - CTO Cloud Computing
|-
| exlt
| [[exlt|Michael Shuler]]
| Swift Systems Engineer
|-
| fifieldt
| [[User:Fifieldt|Tom Fifield]]
| NeCTAR
|-
| garyk
| Gary Kotton
| Red Hat
|-
| gholt
| [[gholt|Greg Holt]]
| Swift Developer
|-
| glange
| [[glange|Greg Lange]]
| Swift Developer
|-
| glenc
| [[GlenCampbell|Glen Campbell]]
| Architect/Analyst
|-
| gongys
| Yong Sheng Gong
| IBM
|-
| gundlach
| [[gundlach|Michael Gundlach]]
| Ozone Developer
|-
| h1nch
| [[h1nch|John Hincher]]
| Systems Engineer
|-
| heckj
| [[JosephHeck|Joe Heck]]
| Developer / Systems Engineer
|-
| ironcamel
| Naveed Massjouni
| Ozone Developer
|-
| jaypipes
| [[jaypipes|Jay Pipes]]
| Open Source Architect / Developer
|-
| jc_smith
| [[jcsmith|Jean-Christophe "JC" Smith]]
| Architect
|-
| jeblair
| [[JamesBlair|James Blair]]
| Developer and CI Infrastructure
|-
| jk0
| [[jk0|Josh Kearney]]
| Ozone Developer
|-
| johnthetubaguy
| [[johngarbutt|John Garbutt]]
| Senior Software Developer, Citrix Systems
|-
| johnpur
| [[JohnPurrier|John Purrier]]
| [[OpenStack]]/Rackspace liaison
|-
| joshuamckenty
| [[joshuamckenty|Joshua McKenty]]
| Piston Cloud Founder, Nova Core Team member, [[OpenStack]] POC, formerly NASA Nebula Architect
|-
| koolhead17
| Atul Jha
| App Specialist, Csscorp
|-
| kpepple
| [[KenPepple|Ken Pepple]]
| Consultant / Architect / Developer
|-
| KMarsh
| Kyle Marsh
| Developer, DreamHost
|-
| [[LinuxJedi]]
| [[LinuxJedi|Andrew Hutchings]]
| Developer Infrastructure and Software Engineer, HP
|-
| littleidea
| [[littleidea|Andrew Clay Shafer]]
| Cloudscaling
|-
| letterj
| [[letterj|Jay Payne]]
| Data Catalyst
|-
| lloydde
| [[lloydde|Lloyd Dewolf]]
| Piston Cloud, Director of Customer Care
|-
| lorin1
| [[LorinHochstein|Lorin Hochstein]]
| Lead Architect, Nimbis Services
|-
| Mandell
| [[mdegerne|Mandell Degerness]]
| Piston Cloud, Systems Analyst
|-
| maoy
| [[maoy|Yun Mao]]
| AT&T Labs - Research, Researcher
|-
| markmc
| [[markmc|Mark McLoughlin]]
| Principal Software Engineer, Red Hat
|-
| [[MarkAtwood]]
| [[MarkAtwood|Mark Atwood]]
| Director - Open Source Evangelism, HP
|-
| markvoelker
| [[markvoelker|Mark Voelker]]
| Software Development Manager, Cisco
|-
| markwash
| Mark Washenberger
| Ozone Developer
|-
| matiu
| [[matiu|Matthew Sherborne]]
| Nova Dev - Rackspace
|-
| mattt
| [[mattt|Matt Thompson]]
| Systems Engineer
|-
| mattray
| [[Matt Ray]]
| Senior Technical Evangelist, Opscode
|-
| mestery
| Kyle Mestery
| Quantum developer
|-
| mikal
| [[Michael Still]]
| Canonical
|-
| mnot
| [[mnottingham|Mark Nottingham]]
| Rackspace
|-
| morellon
| [[Thiago Morello]]
| Locaweb
|-
| mtaylor
| [[MontyTaylor|Monty Taylor]]
| Developer Infrastructure and CI Manager, HP
|-
| murkk
| [[murkk|Chris Blumentritt]]
| Ozone Systems Engineer
|-
| n0ano
| [[n0ano|Don Dugger]]
| Software engineer, Intel
|-
| ncode
| [[Juliano Martinez]]
| Locaweb
|-
| ndipanov
| Nikola Đipanov
| Red Hat
|-
| notmyname
| [[notmyname|John Dickinson]]
| Swift Developer
|-
| nelson
| [[nelson|Russ Nelson]]
| Wikipedia Contractor
|-
| oubiwann
| [[oubiwann|Duncan McGreggor]]
| Cloud Engineering Manager, DreamHost
|-
| ozstacker
| [[ozstacker|Tristan Goode]]
| Australian [[OpenStack]] User Group Co-Ordinator, CEO Aptira
|-
| pandemicsyn
| [[pandemicsyn|Florian Hines]]
| Swift Engineering Monkey
|-
| patrocinio
| Eduardo Patrocinio
| IBM
|-
| pixelbeat
| [[p-draigbrady|Pádraig Brady]]
| Red Hat, Nove core team member
|-
| pknouff
| Philip Knouff
| Ozone Developer
|-
| [[PotHix]]
| Willian Molinari
| Locaweb
|-
| pvo
| [[pvo|Paul Voccio]]
| Ozone Manager
|-
| blakeyeager
| [[blakeyeager|Blake Yeager]]
| Product Manager, Rackspace Cloud
|-
| rackerhacker
| [[major|Major Hayden]]
| Systems Engineer
|-
| rainya
| Rainya Mosher
| Ozone SDLC Project Manager
|-
| Razique
| [[RaziqueMahroua|Razique Mahroua]]
| Nevrotic Openstacker and Technical Writer
|-
| rbergeron
| [[RobynBergeron|Robyn Bergeron]]
| Fedora Marketing & Cloud Person
|-
| redbo
| [[redbo|Michael Barton]]
| Swift Developer
|-
| reed
| [[StefanoMaffulli|Stefano Maffulli]]
| OpenStack Community Manager
|-
| reldan
| [[reldan|Eldar Nugaev]]
| Software Developer
|-
| russellb
| [[russellb|Russell Bryant]]
| Red Hat
|-
| salv-orlando
| [[SalvatoreOrlando|Salvatore Orlando]]
| Quantum Core Dev
|-
| sandywalsh
| [[sandywalsh|Sandy Walsh]]
| Core developer (Rackspace - Ozone)
|-
| sarob
| [[sarob|Sean Roberts]]
| Infrastructure Strategy Yahoo!
|-
| sdague
| [[sdague|Sean Dague]]
| Developer, IBM
|-
| sirp
| [[sirp|Rick Harris]]
| Ozone Developer
|-
| s0mik
| [[s0mik|Somik Behera]]
| [[OpenStack]] Quantum Founding Member, Quantum Core Developer, Product@Nicira, Former VMware Core Developer
|-
| soren
| [[soren|Soren Hansen]]
| Open Source Architect / Developer
|-
| spy
| [[ant|Antony Messerli]]
| Ozone Systems Engineer
|-
| termie
| [[termie|Andy Smith]]
| Nova Developer
|-
| thingee
| Mike Perez
| Developer, DreamHost
|-
| toanster
| Toan Nguyen
| [[OpenStack]] Software Development Manager, Rackspace
|-
| tonywolf
| [[Wolf|Tony Wolf]]
| Ozone Business Analyst
|-
| ttx
| [[ThierryCarrez|Thierry Carrez]]
| OpenStack Release Manager
|-
| tylesmit
| Tyler Smith
| Cisco Developer
|-
| vishy
| [[vishy|Vish Ishaya]]
| Nova Project Technical Lead
|-
| winston-d
| Zhiteng Huang
| Performance Engineer, Intel
|-
| wowdd1
| Zhao Dan
| Developer
|}

Outreachy

2013-02-21T09:03:27Z

Adrian Smith:

== Welcome to the Outreach Program for Women! ==

OpenStack provides open source software for building public and private clouds. We are constantly moving and growing and very excited to invite newcomers to our community. To this end, the OpenStack Foundation has joined the [https://live.gnome.org/OutreachProgramForWomen GNOME Outreach Program for Women].

== Background ==

GNOME Foundation has found that [https://live.gnome.org/OutreachProgramForWomen the program] has dramatically improved the participation by women in their community. For example, at GUADEC they went from having around 4% women to around 17% in just a few years. Representation of women among free and open source participants has been cited at 1.5% as contrasted with the percentages of computing degrees earned by women (all at over 10% higher) in the US. At the October 2012 OpenStack Summit, [[AnneGentle|Anne Gentle]] led an unconference session about including more women in OpenStack and identified one of the goals as bringing more newcomers to OpenStack. The GNOME Outreach program is an excellent way to meet that inclusion goal.

The program offers a good match for efforts to improve our community for women and all newcomers in OpenStack, making it more welcoming for all. The GNOME program specifically seems to be a perfect fit for OpenStack because it matches mentors with newcomers. Another expected effect is to increase women's attendance at the Summit, maybe in conjunction with scholarships and/or employer support. Contrary to Google Summer of Code, which is aimed only at developers, this program results in many strong applicants because it reaches and is suitable for many people with interests in coding, documentation, design, or marketing.

The [http://www.linkedin.com/groups/Women-OpenStack-WOS-4681909 Women in OpenStack group] has already found 4-6 mentors for the program. Each internship requires $5,000 from OpenStack sponsors or by the Foundation. We have funding from Rackspace and Red Hat for two participants, and the Foundation will sponsor one intern. More funding is welcomed.

== Schedule ==

The program will start in November 2012. The results of the internships will be ready by Spring 2013 OpenStack Summit.

* November 14: program announced and application form made available
* November 14 - December 3: applicants need to get in touch with at least one project and make a contribution to it
* December 3: application deadline
* December 11: accepted participants announced
* January 2 - April 2: internship period
* April 2013: OpenStack Summit

== Participants: What the heck is [[OpenStack]]? ==

In a sentence, OpenStack provides open source software for building public and private clouds. What does that mean? We're a collection of open source projects that integrate to help organizations deploy and run clouds for computing, networking, and storage (both block storage for providing volumes to VMs and object storage for storing objects such as images or music files). With OpenStack, you can control large pools of compute, storage, and networking resources throughout a data center, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface. The [http://www.openstack.org/software/start/ Start page] on openstack.org has more details.

We have in-person [[Summit|Summits]] in the fall and spring. We're a community of a lot of companies and individual contributors with a Foundation providing governance and oversight. We collaborate together to build cloud software that's free from vendor lock-in.

[[attachment:openstack_summit_spring2012.jpg]]

'''Community members at the spring 2012 Design Summit in the Developer Lounge ([https://secure.flickr.com/photos/annegentle/6945924486/in/photostream/ Flickr:thegentles])'''

With the help of a mentor, you can navigate these projects to find out more specifics on the types of work available.

There are currently seven core components of OpenStack: Compute, Object Storage, Identity, Dashboard, Block Storage, Network and Image Service. Let's look at each in turn.

* Block Storage (codenamed [[Cinder|"Cinder"]]) provides persistent block storage to guest VMs. This project was born from code originally in Nova (the nova-volume service described below). In the Folsom release, both the nova-volume service and the separate volume service are available.
* Compute (codenamed [[Nova|"Nova"]]) provides virtual servers upon demand. Rackspace and HP provide commercial compute services built on Nova and it is used internally at companies like Mercado Libre and NASA (where it originated).
* Dashboard (codenamed [[Horizon|"Horizon"]]) provides a modular web-based user interface for all the OpenStack services. With this web GUI, you can perform most operations on your cloud like launching an instance, assigning IP addresses and setting access controls.
* Identity (codenamed [[Keystone|"Keystone"]]) provides authentication and authorization for all the OpenStack services. It also provides a service catalog of services within a particular OpenStack cloud.
* Image (codenamed [[Glance|"Glance"]]) provides a catalog and repository for virtual disk images. These disk images are mostly commonly used in OpenStack Compute. While this service is technically optional, any cloud of size will require it.
* Network (codenamed [[Quantum|"Quantum"]]) provides "network connectivity as a service" between interface devices managed by other OpenStack services (most likely Nova). The service works by allowing users to create their own networks and then attach interfaces to them. Quantum has a pluggable architecture to support many popular networking vendors and technologies.
* Object Store (codenamed [[Swift|"Swift"]]) provides object storage. It allows you to store or retrieve files (but not mount directories like a fileserver). Several companies provide commercial storage services based on Swift. These include KT, Rackspace (from which Swift originated) and Internap. Swift is also used internally at many large companies to store their data.

OpenStack stages integrated releases every six months, named according to a voted-upon geographic location nearest to the next Summit. The most recent release is named Folsom with the one prior to that named Essex. The release we're working on now is named Grizzly. Don't let all these crazy names (release names, project names, oh my!) stop you from jumping in though. We have a lot of fun in the cloud with names and word play.

== Participants: How can I learn even more? ==

Read the project's page on Launchpad.

We communicate a lot on IRC and all the channels are listed at http://wiki.openstack.org/IRC. You can go to the project's IRC channel, such as #openstack-dev (where the developers are), #openstack (where the deployers are), and for each project you can also find channels with the project name like nova is at #openstack-nova, swift is at #openstack-swift, and so on. You can read the conversation there and jump in when you are ready.

If you are applying for a software development internship, run [http://devstack.org DevStack] in a VM on your laptop to run all the integrated projects in one location. Do ask your mentor or people on IRC for help if you encounter any problems running DevStack.

Look at the open bugs for the project Launchpad, the pattern is http://bugs.launchpad.net/nova where nova is the project name. There are many projects that are not completely code-related. For example, doc bugs are at http://bugs.launchpad.net/openstack-manuals, API doc bugs are at http://bugs.launchpad.net/openstack-api-site, continuous integration bugs are tracked at http://bugs.launchpad.net/openstack-ci, and quality assurance tooling bugs are at http://bugs.launchpad.net/tempest.

Look at the recent changes in the project's Git repository, for example https://github.com/openstack/glance/ shows the most recent changes to the Image service project, Glance.

Read about our use of Gerrit for code reviews at [[GerritWorkflow]].

Read the documentation at http://docs.openstack.org, which is built from https://github.com/openstack/openstack-manuals Git repository.

Read the recent discussion on the project's mailing list, such as http://lists.openstack.org/pipermail/openstack-dev/.

Read the blogs of the project's mentor and other project contributors (you can learn who they are when looking at the Git repository). Many contributor's blogs are collected at http://planet.openstack.org.

Introduce yourself to the project's mentor and discuss what your tasks during the internship program would be.

== Participants: How do I apply? ==

The application process is to send an application containing the following information to a mailing list set up just for reviewing applications.

Please fill out the answers to the following questions and e-mail them to opw-list@gnome.org with a subject line of "[APPLICATION - Organization Name] Your Name". You may optionally attach your resume or include any other information that is relevant to your application. All applications must be received by 11:59pm GMT on December 3, 2012.

Please don't send in the application form until you have completed the required initial contribution, unless it's less than a week to the application deadline and you are already working on your contribution. Once you have completed the initial contribution, send in your application right away, so that we have more time to follow up with you in case we need additional information. Please feel free to work on more contributions after that as your time allows. If you need to update your application, just send in an updated version to opw-list@gnome.org with the same subject line.

For developers, use the [[DevQuickstart]] page for step-by-step instructions on how to submit a contribution. The [[HowToContribute]] page shows the processes for all contributors.

<pre><nowiki>
Name:

E-mail address:

IRC Nick:

Web Page / Blog / Microblog:

Location:

Education completed or in progress (i.e., university, major/concentration, degree level, and graduation year):

How did you hear about this program?

Please describe your experience with the organization's product as a user and as a contributor (include the information about the contribution you made to the project you are interested in here):

Please describe your experience with any other FOSS (Free Open Source Software) projects as a user and as a contributor:

Please describe any relevant projects that you have worked on previously and what knowledge you gained from working on them:

What project(s) are you interested in (these can be in the same or different organizations)?

Please describe the details and the timeline of the work you plan to accomplish on the project you are most interested in (discuss these first with the mentor of the project):

Will you have any other time commitments, such as school work, another job, planned vacation, etc., between January 2 and April 2?

</nowiki></pre>

Please be available and responsive throughout the application period so we can work with you on improving your application.

== Participants: What if I have a question about [[OpenStack]]? ==

With a large collection of projects, just finding out where to ask (or who) can be intimidating. We want you to feel free to contact anyone in the community, and for direct contact, talk to Anne Gentle via email at anne at openstack dot org or Stefano Maffuli at stefano at openstack dot org if you have any questions during the application process. There are also mailing lists available at http://wiki.openstack.org/MailingLists with many purposes.

== Mentors ==
For information about expectations for mentors and to volunteer to be a mentor, see [[OutreachProgramForWomen/Mentors]].

The identified volunteer mentors are:
* Iccha Sethi, Software Developer, Rackspace. Email: iccha dot sethi at rackspace dot com
* Julie Pichon, Developer, Red Hat
* Russell Bryant, Red Hat
* Alex Maier, Nebula

Volunteer administrators are:
* Anne Gentle, Documentation Coordinator, Rackspace. Email: anne dot gentle at rackspace dot com
* Stefano Maffulli, Community Manager, OpenStack Foundation. Reed on IRC. Email: stefano at openstack dot org

== Projects ==

{| border="1" cellpadding="2" cellspacing="0"
| Title
| More details
|-
| Link Compute API samples so they are published to api.openstack.org
| [https://blueprints.launchpad.net/openstack-manuals/+spec/api-samples-to-api-site Blueprint]
|-
| Try it out on api.openstack.org
| [https://blueprints.launchpad.net/openstack-manuals/+spec/api-try-it-out Blueprint]
|-
| Build a supply-chain management system to distribute merchandising to [[OpenStack]] User Groups around the world
| [[Community/CollateralMgmt]]
|-
| Write a manual on how to start and manage user groups
| [[OpenStackUserGroups/HowTo]]
|-
| Write a mobile app for tablets to create a paperless kiosk for marketing collateral at events
|
|-
| Adding features to Python Clients of Various [[OpenStack]] Projects
|
|-
| Consistent Transaction ID across all projects
|
|}

Add your [[OutreachProgramForWomen/Ideas|ideas]] for projects.