OpenStack - User contributions [en]

Category:Connect

2016-12-21T19:52:32Z

Smaffulli: Protected "Category:Connect" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))

== Get in touch with OpenStack community ==

[[Category:Home]]

Category:Connect

2016-12-21T19:51:51Z

Smaffulli: Reverted edits by Charles.csweat (talk) to last revision by Smaffulli

== Get in touch with OpenStack community ==

[[Category:Home]]

Interop Challenge

2016-10-11T23:07:04Z

Smaffulli: /* How to Join */

== Interop Challenge ==
''Status: Collecting workload scripts, milestone-1 (as of Aug 8, 2016)''

=== Scope ===
The interop challenge was started in July 2016 to create a set of common workloads/tests to be executed across multiple OpenStack distributions and/or cloud deployment models. The participants in this challenge will work together to prove once and for all that OpenStack-Powered clouds are interoperable.

Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off]

=== Duration ===
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation.

=== Meeting Information ===
Schedule: Wednesdays at 1400 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-cp</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&iso=20161012T14&p1=%3A Wednesday, October 12th, 2016 at 1400 UTC]'''
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-10-12 2016-10-12]'''
'''Agenda'''
* see the etherpad
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-09-28 2016-10-05]

==== Communication methods====
* Members will meet regularly using the OpenStack DefCore channel on IRC
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and add the [interop] tag to the subject of messages related to the interop challenge.
* The team may also have discussions in Gerrit on specific tools/workloads

=== Milestones ===
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create interop challenge and team'' || || ''Completed''
|-
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' || || ''Completed''
|-
| 3 || Execute tests, resolve/document any issues, and share results || || ''In-Progress''
|-
| 4 || Create read-out for Interop Challenge || || Pending
|-
| 5 || Share findings at the OpenStack Summit in Barcelona || || Pending
|-
|}

=== How to Join ===
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag "[interop]" in the subject line. Please identify one business and technical leader from your organization in the introductory email. Welcome aboard!

Current Participants Alphabetical Order

{| class="wikitable"
|-
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner
|-
| AT&T || || || || || Elise Eiden
|-
| Canonical || Mitaka and Newton || || || || Mark Baker
|-
| Cisco || Liberty || || Success || Rohit Agarwalla || Rohit Agarwalla
|-
| Fujitsu || Kilo || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler
|-
| Hitachi || || || || ||
|-
| HPE || Mitaka || RefStack Pass. Tested with Ansible || Success || Ghe Rivero || ||
|-
| Huawei || Juno || DockerSwarm tested with Terraform, LAMPStack tested with Ansible || Success || Jichun Liu(Huawei) || Zhenyu Zheng||
|-
| DT OTC (public cloud) || || || || ||Daniela Ebert ||
|-
| IBM || Liberty and Mitaka || || Success || Tong Li (IBM) || Tong Li (IBM)
|-
| Linaro || Newton on AArch64 || || Success || Gema Gomez (Linaro) || Gema Gomez ||
|-
| Mirantis || Mitaka || || || ||
|-
| NetApp || || || || ||
|-
| Osic (Intel+Rackspace) || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares
|-
| OVH || Juno/Kilo || || Success || Tong Li (IBM) || pilgrimstack
|-
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler
|-
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado
|-
| SUSE || Liberty and Mitaka || Tested with Terraform || Success || contact Roman Arcea (SUSE) || Pete Chadwick - placeholder
|-
| VMware || Mitaka || || Success || Xiangfei Zhu/Mark Voelker ||Mark Voelker ||
|-
| DreamHost || Mitaka || LAMPstack Ansible || Success || || Stefano Maffuli
|-
|}

=== Scripts/Tools used for Interop Challenge ===
The interop challenge requires that we use common testing scripts and validation methods across multiple clouds. The team has agreed to post all scripts to the [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository since the templates/scripts used for the Interop Challenge are also useful outside of this context and could serve as examples on how to use various tools to deploy applications on OpenStack-Powered Clouds.

The current list of proposed tooling includes:
* Ansible
* Terraform
* OpenStack Heat

The current list of workloads includes:
* LAMP (Linux, Apache, MySQL, PHP) Stack
* Dockerswarm-coreos
* NFV

==== How to Propose/Submit new tools/workloads ====
Any participating member of the Interop Challenge can submit additional scripts/workloads for review by the team. The script to leverage the new tool and/or deploy the new workload should be posted to the [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository. Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].

Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: "[interop] New tool/workload proposal: <code>brief description</code>" and provide a link to the code review page for the change along with an overview of the tool or where people can find more information. The proposal will be reviewed by the team and, if necessary, added to the agenda for an upcoming meeting.

==== Directory Structure ====
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib
Directory structure is proposed below:
/heat - use heat template to create workload
lampstack
dockerswarm-coreo
...
/terraform - use terraform to create workload
lampstack
dockerswarme-coreos
...
/xxx - use xxx to create workload

=== Test Candidate Process ===
(Proposed; subject to change after 08-10-2016 meeting)
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)
** We may need to talk about the content of each work load, use lamp stack as an example.
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?
* LAMP stack workload (created by Tong Li/IBM)
** https://review.openstack.org/#/c/351879/
** Currently developed using terraform to deploy workload, looking into Ansible
* HEAT template (submitted by Craig Sterrett & Leong/Intel)
** https://review.openstack.org/#/c/351799/

For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )

=== RefStack Testing and Results Upload ===
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.

Once tests are run, test results can be uploaded to the official [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.
*RefStack team highly recommends to upload test results with signatures and not anonymously. By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.

For Interop Challenge, DefCore team recommends to run complete API tests (not just the must-pass tests). Following is the command to run the tests:
./refstack-client test -c <Path of the tempest configuration file to use> -v

For questions, please contact us at IRC channels #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]

=== Where/How to Share Test Results ===
Rather than collecting binary "pass/fail" results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not. Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with "[interop-challenge] Workload Results" in the subject line.

1.) Your name:
2.) Your email:
3.) Reporting on behalf of Company/Organization:
4.) Name and version (if applicable) of the product you tested:
5.) Version of OpenStack the product uses:
6.) Link to RefStack results for this product:
7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)
A.) Did the workload run successfully?
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?
8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)
A.) Did the workload run successfully?
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?
9.) Workload 3: NFV (URL TBD)
A.) Did the workload run successfully?
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?

Here's a fictional example of what the email template might look like when filled out:

1.) Your name: Jane Doe
2.) Your email: jdoe@supercoolsoftware.com
3.) Reporting on behalf of Company/Organization: XYZ, Inc.
4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5
5.) Version of OpenStack the product uses: Liberty
6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d
7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)
A.) Did the workload run successfully? No
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.

"Error in fetching the floating IP's: no floating IP addresses available"

C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.

SuperCoolCloud doesn't use floating IP addresses. Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.

D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?

Not very. Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says "if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead").

8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)
A.) Did the workload run successfully? Yes
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.

N/A

C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.

N/A

D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?

N/A

9.) Workload 3: NFV (URL TBD)
A.) Did the workload run successfully? Yes
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.

N/A

C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.

N/A

D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?

N/A

Interop Challenge

2016-10-11T23:05:58Z

Smaffulli: /* How to Join */

== Interop Challenge ==
''Status: Collecting workload scripts, milestone-1 (as of Aug 8, 2016)''

=== Scope ===
The interop challenge was started in July 2016 to create a set of common workloads/tests to be executed across multiple OpenStack distributions and/or cloud deployment models. The participants in this challenge will work together to prove once and for all that OpenStack-Powered clouds are interoperable.

Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off]

=== Duration ===
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation.

=== Meeting Information ===
Schedule: Wednesdays at 1400 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-cp</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&iso=20161012T14&p1=%3A Wednesday, October 12th, 2016 at 1400 UTC]'''
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-10-12 2016-10-12]'''
'''Agenda'''
* see the etherpad
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-09-28 2016-10-05]

==== Communication methods====
* Members will meet regularly using the OpenStack DefCore channel on IRC
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and add the [interop] tag to the subject of messages related to the interop challenge.
* The team may also have discussions in Gerrit on specific tools/workloads

=== Milestones ===
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create interop challenge and team'' || || ''Completed''
|-
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' || || ''Completed''
|-
| 3 || Execute tests, resolve/document any issues, and share results || || ''In-Progress''
|-
| 4 || Create read-out for Interop Challenge || || Pending
|-
| 5 || Share findings at the OpenStack Summit in Barcelona || || Pending
|-
|}

=== How to Join ===
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag "[interop]" in the subject line. Please identify one business and technical leader from your organization in the introductory email. Welcome aboard!

Current Participants Alphabetical Order

{| class="wikitable"
|-
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner
|-
| AT&T || || || || || Elise Eiden
|-
| Canonical || Mitaka and Newton || || || || Mark Baker
|-
| Cisco || Liberty || || Success || Rohit Agarwalla || Rohit Agarwalla
|-
| Fujitsu || Kilo || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler
|-
| Hitachi || || || || ||
|-
| HPE || Mitaka || RefStack Pass. Tested with Ansible || Success || Ghe Rivero || ||
|-
| Huawei || Juno || DockerSwarm tested with Terraform, LAMPStack tested with Ansible || Success || Jichun Liu(Huawei) || Zhenyu Zheng||
|-
| DT OTC (public cloud) || || || || ||Daniela Ebert ||
|-
| IBM || Liberty and Mitaka || || Success || Tong Li (IBM) || Tong Li (IBM)
|-
| Linaro || Newton on AArch64 || || Success || Gema Gomez (Linaro) || Gema Gomez ||
|-
| Mirantis || Mitaka || || || ||
|-
| NetApp || || || || ||
|-
| Osic (Intel+Rackspace) || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares
|-
| OVH || Juno/Kilo || || Success || Tong Li (IBM) || pilgrimstack
|-
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler
|-
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado
|-
| SUSE || Liberty and Mitaka || Tested with Terraform || Success || contact Roman Arcea (SUSE) || Pete Chadwick - placeholder
|-
| VMware || Mitaka || || Success || Xiangfei Zhu/Mark Voelker ||Mark Voelker ||
|-
| DreamHost || Mitaka || || Pass LAMPstack Ansible || || Stefano Maffuli
|-
|}

=== Scripts/Tools used for Interop Challenge ===
The interop challenge requires that we use common testing scripts and validation methods across multiple clouds. The team has agreed to post all scripts to the [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository since the templates/scripts used for the Interop Challenge are also useful outside of this context and could serve as examples on how to use various tools to deploy applications on OpenStack-Powered Clouds.

The current list of proposed tooling includes:
* Ansible
* Terraform
* OpenStack Heat

The current list of workloads includes:
* LAMP (Linux, Apache, MySQL, PHP) Stack
* Dockerswarm-coreos
* NFV

==== How to Propose/Submit new tools/workloads ====
Any participating member of the Interop Challenge can submit additional scripts/workloads for review by the team. The script to leverage the new tool and/or deploy the new workload should be posted to the [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository. Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].

Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: "[interop] New tool/workload proposal: <code>brief description</code>" and provide a link to the code review page for the change along with an overview of the tool or where people can find more information. The proposal will be reviewed by the team and, if necessary, added to the agenda for an upcoming meeting.

==== Directory Structure ====
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib
Directory structure is proposed below:
/heat - use heat template to create workload
lampstack
dockerswarm-coreo
...
/terraform - use terraform to create workload
lampstack
dockerswarme-coreos
...
/xxx - use xxx to create workload

=== Test Candidate Process ===
(Proposed; subject to change after 08-10-2016 meeting)
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)
** We may need to talk about the content of each work load, use lamp stack as an example.
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?
* LAMP stack workload (created by Tong Li/IBM)
** https://review.openstack.org/#/c/351879/
** Currently developed using terraform to deploy workload, looking into Ansible
* HEAT template (submitted by Craig Sterrett & Leong/Intel)
** https://review.openstack.org/#/c/351799/

For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )

=== RefStack Testing and Results Upload ===
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.

Once tests are run, test results can be uploaded to the official [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.
*RefStack team highly recommends to upload test results with signatures and not anonymously. By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.

For Interop Challenge, DefCore team recommends to run complete API tests (not just the must-pass tests). Following is the command to run the tests:
./refstack-client test -c <Path of the tempest configuration file to use> -v

For questions, please contact us at IRC channels #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]

=== Where/How to Share Test Results ===
Rather than collecting binary "pass/fail" results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not. Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with "[interop-challenge] Workload Results" in the subject line.

1.) Your name:
2.) Your email:
3.) Reporting on behalf of Company/Organization:
4.) Name and version (if applicable) of the product you tested:
5.) Version of OpenStack the product uses:
6.) Link to RefStack results for this product:
7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)
A.) Did the workload run successfully?
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?
8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)
A.) Did the workload run successfully?
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?
9.) Workload 3: NFV (URL TBD)
A.) Did the workload run successfully?
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.
C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.
D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?

Here's a fictional example of what the email template might look like when filled out:

1.) Your name: Jane Doe
2.) Your email: jdoe@supercoolsoftware.com
3.) Reporting on behalf of Company/Organization: XYZ, Inc.
4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5
5.) Version of OpenStack the product uses: Liberty
6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d
7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)
A.) Did the workload run successfully? No
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.

"Error in fetching the floating IP's: no floating IP addresses available"

C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.

SuperCoolCloud doesn't use floating IP addresses. Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.

D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?

Not very. Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says "if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead").

8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)
A.) Did the workload run successfully? Yes
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.

N/A

C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.

N/A

D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?

N/A

9.) Workload 3: NFV (URL TBD)
A.) Did the workload run successfully? Yes
B.) If not, did you encounter any end-user visible error messages? Please copy/paste them here and provide any context you think would help us understand what happened.

N/A

C.) Were you able to determine why the workload failed on this product? If so, please describe. Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.

N/A

D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product? Can you describe what would need to be done?

N/A

HowToUpdateCorporateCLA

2016-04-11T18:21:27Z

Smaffulli:

= How To Update Corporate CLA =

Corporations that sign the [[HowToContribute#Contributors_License_Agreement|Corporate Contributors License Agreement]] submit the initial list of employees authorized to commit code to OpenStack projects using Schedule A of the CCLA.

To update the list of authorized employees, please fill and sign the [https://openstack.echosign.com/public/hostedForm?formid=56JUVP6K4Z6P4C Updated Schedule A] module providing the actual list of employees.

Please do not provide only the changes, provide the full list current with all additions/removals.

If you need help, please contact [mailto:communitymngr@openstack.org communitymngr@openstack.org].

AddingYourBlog

2016-04-04T16:41:56Z

Smaffulli: added info for help

= Adding Your Blog To Planet OpenStack =

The config for the planet aggregator is kept in a git repo and managed by Gerrit. To add your feed to [http://planet.openstack.org Planet OpenStack], simply clone git://github.com/openstack/openstack-planet.git and then follow the normal [[OpenStack]] [http://docs.openstack.org/infra/manual/developers.html#development-workflow development workflow] to submit your change.

== Separating Content ==
You may want to tag or label individual posts or categorize only some posts to be aggregated in Planet [[OpenStack]]. Different blogging software have different ways of providing feeds that will only aggregate posts you mark or tag under an "openstack" category, for example.

* In '''Blogger''': the feed URL for a specific label would be '''http://xxx.blogspot.com/feeds/posts/default/-/labelname'''
* In '''WordPress''': You can provide feeds to only specific categories on your site by adding the following to the end of the feed URL link: '''http://example.com/wp-rss2.php?cat=42''' or '''http://example.com/category/categoryname/feed''' . Also see: http://codex.wordpress.org/WordPress_Feeds
** '''WordPress.com users:''' RSS2 feeds have a small problem, so you need to use your Atom feed ('''http://username.wordpress.com/feed/atom''') or add '''?mrss=off''' to the end of the RSS2 feed. Example '''http://blog.site.com/category/ubuntu/feed/?mrss=off'''
** '''WordPress 2.7 users:''' RSS2 feeds for a specific category doesn't work with the example feed link above when Permalink's set to Default. Use '''http://example.com/?cat=4&feed=rss2''' instead. See [http://wordpress.org/support/topic/225303 forum discussion] for details. For those who hosted their blogs on the official Wordpress.com site, which means you are not hosting wordpress on your own server, the latest stable release of WordPress is Version 3.8, so it should be safe to assume that this version specific problem does not affect you. (added 19 Dec 2013)
* In '''Drupal''': you can use taxonomies to tag your content and have RSS feeds generated from those taxonomies. See [http://learnbythedrop.com/drop/45 this blog post] under "Taxonomy Generated Feeds" for more information.
* In '''LiveJournal''': the feed URL for a specific tag would be '''http://example.livejournal.com/data/rss?tag=foobar'''
* In '''Habari''': the feed URL for a specific tag would be '''http://example.com/tag/foobar/atom'''
* In '''Tumblr''': the feed URL for a specific tag would be '''http://example.tumblr.com/tagged/foobar/rss'''
* For others with no filtering support: You can use [http://pipes.yahoo.com/pipes/ Yahoo Pipes] to filter your feed, but the links to your blog from the right Planet Ubuntu sidebar and from your face image will point to the feed also.

== Adding Your Feed ==

Check out the configuration files from git:



<pre><nowiki>
$ git clone git://git.openstack.org/openstack/openstack-planet
$ cd openstack-planet
</nowiki></pre>

Next, place your hackergotchi<<[[FootNote]](Your hackergotchi should be scaled to roughly 100x100 pixels, give or take.)>> into the <code><nowiki>images/</nowiki></code> subdirectory:

<pre><nowiki>
$ cp ~/hackergotchi.png images/yourusername.png
$ git add images/yourusername.png
</nowiki></pre>

If you don't have a hackergotchi to add right away, comment out the line (using # at the beginning) or leave the entire line out.

Once you've done that, add a stanza like the following to the end of the <code><nowiki>planet.ini</nowiki></code> file:

<pre><nowiki>
[http://blog.example.com/~yourusername/feed?category=openstack]
name = Your Name Here
face = yourusername.png
nick = yourusername
</nowiki></pre>

/!\ Please use your real name at least somewhere in the 'name' field.

When you are satisfied that your entry is correct, it's time to check in your changes:

<pre><nowiki>
$ git commit -a -m "Added <yourusername> to Planet OpenStack"
$ git review
</nowiki></pre>

= Something's wrong? =

Contact OpenStack Infra team on IRC #openstack-infra or mailing list openstack-infra@lists.openstack.org.

[[category: contribute]]

Category:Home

2016-02-11T15:30:25Z

Smaffulli: Reverted edits by Tech vega (talk) to last revision by Smaffulli

Root of all categories in OpenStack wiki. Every category should be contained in the Home category.

=== Category Tree ===

{{#categorytree:Home|hideroot|mode=pages}}

Application Ecosystem Working Group

2015-12-10T03:13:24Z

Smaffulli: /* Members */

'''Status''': Active

'''Organizers''': [mailto:william.franklin@hp.com Bill Franklin]

==Purpose==

To create an ecosystem where a diverse array of applications built for OpenStack can thrive.

Objectives:
* Grow the number of active OpenStack applications globally, for both private and public cloud use
* Make it simpler to create applications for OpenStack by:
** Improving introductory material
** Ensuring appropriate tools and technical information is available, correct and easy to find
* Further facilitating the association of those creating applications for OpenStack clouds with the OpenStack technical community by:
** Improving developer.openstack.org, a portal for application creators
** Analyzing and improving the 6-monthly conference, particularly the "Targeting OpenStack" track, and other more feedback-style sessions
** Educating OpenStack's active technical community on the issues faced by those who are targeting OpenStack clouds

==Mail List==
Email: We use the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list] and prefix the subject line with [app]. 

==Team Meetings==
The team meets weekly, on Wednesdays at 1700 UTC 
Skype Info: https://join.ucrtc.hpe.com/meet/john.callaghan/5H1L8N0S 
Call-in Info:
{| class="wikitable"
|-
| Number || Country/Region
|-
| +1-978-289-4114 || Andover, MA, USA
|-
| +1-678-367-0003 || Atlanta, GA, USA
|-
| +1-512-865-6123 || Austin, TX, USA
|-
| +1-208-629-2920 || Boise, ID, USA
|-
| +1-970-672-4888 || Fort Collins. CO, USA
|-
| +1-281-377-1991 || Houston, TX, USA
|-
| +1-650-300-4050 || Palo Alto, CA, USA
|-
| 1-855-493-4983 || USA and Canada
|-
| Other Local Numbers || https://join.ucrtc.hpe.com/dialin
|-
|} 

Current Etherpad: https://etherpad.openstack.org/p/2015_Dec_16_App_Ecosystem_Workgroup 

Previous Etherpad links can be found here: https://etherpad.openstack.org/p/AppEcoSystemWG_Archives

==Deliverables==

1. Application Ecosystem Feedback

Anyone in the application ecosystem needs a way to give feedback to the OpenStack community at large. This can be a daunting task for those outside of the community. The members of this working group need to gather and channel this feedback into one place where the people building OpenStack itself can consume it. We should be accepting of feedback in all its forms: conversations, email, IRC, blog posts, etc. The point is to act as a conduit and provide a way to get that feedback to the community.

2. Communicate Actionable Items

This working group has a large and diverse group of stakeholders. It's our responsibility to engage these stakeholders, keep them up to date, and communicate actionable items to them. Specifically the [[Application_Ecosystem_Working_Group#Liaisons|Liaisons]] are responsible for ensuring this happens.

3. Content

The content necessary to grow an application ecosystem comes in many forms. Some examples are:

* Content for events (eg hackathons)
* White papers
* Code examples
* Application examples
* Application architectures
** e.g. [http://support.rightscale.com/12-Guides/Designers_Guide/Cloud_Solution_Architectures/Cloud_Computing_System_Architecture_Diagrams Cloud Computing System Architecture Diagrams] but with OpenStack services
* Presentations
* Anything else you can think of

Where a particular piece of content lives will likely depend on the nature of the content.

==How to Contribute==

Contributions come in the form of the deliverables above.

1. To contribute feedback:

2. To communicate actionable items:

The [[Application_Ecosystem_Working_Group#Liaisons|Liaisons]] will know best how to communicate with their respective stakeholders.

3. To contribute content:

# Email your idea for content to the User Committee mailing list
# Discuss the content and where it should live
# Execute on that idea

4. Participate in the discussions at the weekly TODO (see [[Meetings]]).

==Scope==

There is the related [[API_Working_Group]] (API WG). The Application Ecosystem Working Group (AE WG) is complementary to the API WG. The AE WG is focused on anyone creating or running an application on OpenStack whereas the API WG is focused on guidelines for the APIs. The place where these groups meet in the middle is the API, which forms the contract between the two. Members of the AE WG are encouraged to be members of the API WG and vice versa.

== Liaisons ==

* [[Win_the_Enterprise|Win the Enterprise]]
** Carol Barrett
* [[API_Working_Group|API Working Group]]
** Everett Toews
** Lance Bragstad
* [[Governance/Foundation/UserCommittee|User Committee]]
** Jonathan Proulx
* [[Governance/TechnicalCommittee|Technical Committee]]
** Anne Gentle
** Rags Srinivas
* [[Governance/DefCoreCommittee|DefCore]]
** Jonathan Bryce
* [[CrossProjectLiaisons|Cross-Project Liaisons]]
** TODO

==How to Join==

Join the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list], watch for emails that are prefixed by [app], and join the discussion. Start contributing to the deliverables.

==Members==

Please add yourself to this list if you are committed to growing the Application Ecosystem for OpenStack.

* [mailto:tom@openstack.org Tom Fifield]
* [mailto:evan@hp.com Evan Scheessele]
* [mailto:Shilla.Saebi@gmail.com Shilla Saebi]
* [mailto:victor.r.howard@gmail.com Victor Howard]
* [mailto:carol.l.barrett̊intel.com Carol Barrett]
* [mailto:ksa@slac.stanford.edu Karl Amrhein]
* [mailto:bmorel@internap.com Bruno Morel]
* [mailto:dff.openstack@gmail.com David F. Flanders] @DFFlanders
* [mailto:patricia.montenegro@intel.com Patricia Montenegro]
* [mailto:stefano@removethis-openstack.org Stefano Maffulli]

[[Category:Working_Groups]]
[[Category:UserCommittee]]

Outreachy

2015-09-07T17:01:41Z

Smaffulli: /* Volunteer administrators */

== Welcome to OpenStack Outreachy ==

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 program [https://www.gnome.org/outreachy/ Outreachy].

Outreachy helps people from groups underrepresented in free and open source software get involved, by providing a supportive community for beginning to contribute any time throughout the year and offering focused internship opportunities twice a year with a number of free software organizations.

The current round of internships is open to women (cis and trans), trans men, genderqueer people, and all participants of the [http://ascendproject.org/ Ascend Project] regardless of gender. We are planning to expand the program to more participants from underrepresented backgrounds in the future.

== 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 3% [1], [2] 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 Outreachy program is an excellent way to meet that inclusion goal. At the October 2013 OpenStack Summit, mentors and interns presented about their experiences in "[[https://www.openstack.org/summit/portland-2013/session-videos/presentation/what-everyone-ought-to-know-about-openstack-internships|What Everyone Ought to Know about OpenStack Internships]]"

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 $6,250 from OpenStack sponsors or by the Foundation. The Foundation is happy to help companies with sponsorship, and more funding is always welcomed. Please contact stefano at openstack dot org through email if you would like to sponsor.

1. http://www.eskar.dk/andreas/output/PersonalProfile.HTM
2. http://survey.perlfoundation.org/Data-PerlSurvey-2010/R/

== Schedule ==

The application deadline for the December-March Outreachy term has passed, but you can look for a new application period opening in mid-February for May 25 to August 25 internships.

* February 17: participating organizations are announced
* March 3 - March 24: applicants need to get in touch with at least one project and make a contribution to it
* March 3: application system opens
* March 24 - April 27: applicants are encouraged to continue making contributions for the project they applied for;
submitted applications are open for editing
* March 24: application deadline at 7pm UTC
* April 27: accepted participants announced at 7pm UTC on the GNOME web site
* May 25 to August 25: internship period

== 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.

[[File: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 several 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 many companies.
* 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 [[Neutron|"Neutron"]]) 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.
* Telemetry Service (codenamed [[Ceilometer|"Ceilometer"]]) aggregates usage and performance data across the services deployed in an OpenStack cloud. This powerful capability provides visibility and insight into the usage of the cloud across dozens of data points and allows cloud operators to view metrics globally or by individual deployed resources.
* Orchestration Service (codenamed [[Heat|"Heat"]]) is a template-driven engine that allows application developers to describe and automate the deployment of infrastructure. The flexible template language can specify compute, storage and networking configurations as well as detailed post-deployment activity to automate the full provisioning of infrastructure as well as services and applications. Through integration with the Telemetry service, the Orchestration engine can also perform auto-scaling of certain infrastructure elements.
* and more projects!

OpenStack stages integrated releases every six months, named according to a voted-upon geographic location nearest to the next Summit. 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.

As a prospective applicant, you should consider joining the #openstack-opw channel, where you can meet mentors, interns past and present, as well as other helpful members of the community.

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 in the [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].

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.

=== How do I apply? ===

The application process is described in detail at https://wiki.gnome.org/OutreachProgramForWomen#Send_in_an_Application. A contribution is required and you answer questions when you apply. You are expected to work full-time on the internship although you can indicate any pre-planned time off in your application.
Please be available and responsive throughout the application period so we can work with you on improving your application.

=== 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, contact the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-internships Internship coordinator mailing list] you have any questions during the application process. There are other 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]]. Mentors should login and apply for a mentor role for OpenStack on https://outreachy.gnome.org/ (the [https://openstackid.org OpenStackID provider] can be used).

The identified volunteer mentors are:

* Ladislav Smola, Developer, Red Hat. Email: lsmola at redhat dot com. IRC: lsmola
* Flavio Percoco, Developer, Red Hat. Email: flavio at redhat dot com. IRC: flaper87
* Liz Blanchard, Senior Interaction Designer, Red Hat. Email: lblanchard at redhat dot com. IRC: lblanchard
* Ju Lim, Member of the Technical Staff, Red Hat. Email: julim at redhat dot com. IRC: julim
* Nikhil Komawar, Software Developer, Rackspace. Email: nikhil.komawar at rackspace dot com IRC: nikhil_k
* Rossella Sblendido, Software Developer, SUSE, Email: rsblendido at suse dot com IRC: rossella_s
* Iccha Sethi, Software Developer, Rackspace, Email: iccha.sethi at rackspace dot com IRC: iccha
* Mike Perez, Senior software engineer, Datera, Email: thingee at gmail dot com IRC: thingee
* Henry Nash, "Wild Duck", IBM. Email: henryn at linux dot vnet dot ibm dot com
* Dina Belova, Software Engineer, Mirantis. Email: dbelova@mirantis.com, IRC: DinaBelova
* John Dickinson, Director of Technology, SwiftStack. Email: me@not.mn, IRC: notmyname
* Victoria Martínez de la Cruz, Developer, Red Hat. Email: victoria at redhat dot com. IRC: vkmc
* Davanum Srinivas, Mirantis. Email: davanum at gmail dot com. IRC: dims
* Alexandra Settle, Rackspace. Email: alexandra.settle(at)rackspace(dot)com. IRC: asettle
* Ed Leafe, IBM. Email: ed(at)openstack(dot)org IRC: edleafe
* Jeremy Stanley, Systems Engineer, OpenStack Foundation. E-mail: fungi@yuggoth.org IRC: fungi
* Elizabeth K. Joseph, Systems Administrator, HP, E-mail: lyz@princessleia.com IRC: pleia2
* Jonathan Harker, Operations Developer, HP, E-mail: jesusaurus at gentlydownthe dot net IRC: jesusaurus

== Volunteer administrators ==

* Victoria Martínez de la Cruz, Developer, Red Hat. Email: victoria at redhat dot com. IRC: vkmc
* Lana Brindley, Tech writing manager, Rackspace. Email: lana.brindley(at)rackspace(dot)com. IRC: loquacities

More resources for [[Outreachy/resources_for_administrators|Outreachy administrators]].

== Projects ==

Please see the [[Internship_ideas|Ideas page]].

[[Category: Internship]]

Outreachy

2015-09-07T17:01:28Z

Smaffulli: /* Mentors */ removed stefano maffulli

== Welcome to OpenStack Outreachy ==

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 program [https://www.gnome.org/outreachy/ Outreachy].

Outreachy helps people from groups underrepresented in free and open source software get involved, by providing a supportive community for beginning to contribute any time throughout the year and offering focused internship opportunities twice a year with a number of free software organizations.

The current round of internships is open to women (cis and trans), trans men, genderqueer people, and all participants of the [http://ascendproject.org/ Ascend Project] regardless of gender. We are planning to expand the program to more participants from underrepresented backgrounds in the future.

== 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 3% [1], [2] 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 Outreachy program is an excellent way to meet that inclusion goal. At the October 2013 OpenStack Summit, mentors and interns presented about their experiences in "[[https://www.openstack.org/summit/portland-2013/session-videos/presentation/what-everyone-ought-to-know-about-openstack-internships|What Everyone Ought to Know about OpenStack Internships]]"

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 $6,250 from OpenStack sponsors or by the Foundation. The Foundation is happy to help companies with sponsorship, and more funding is always welcomed. Please contact stefano at openstack dot org through email if you would like to sponsor.

1. http://www.eskar.dk/andreas/output/PersonalProfile.HTM
2. http://survey.perlfoundation.org/Data-PerlSurvey-2010/R/

== Schedule ==

The application deadline for the December-March Outreachy term has passed, but you can look for a new application period opening in mid-February for May 25 to August 25 internships.

* February 17: participating organizations are announced
* March 3 - March 24: applicants need to get in touch with at least one project and make a contribution to it
* March 3: application system opens
* March 24 - April 27: applicants are encouraged to continue making contributions for the project they applied for;
submitted applications are open for editing
* March 24: application deadline at 7pm UTC
* April 27: accepted participants announced at 7pm UTC on the GNOME web site
* May 25 to August 25: internship period

== 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.

[[File: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 several 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 many companies.
* 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 [[Neutron|"Neutron"]]) 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.
* Telemetry Service (codenamed [[Ceilometer|"Ceilometer"]]) aggregates usage and performance data across the services deployed in an OpenStack cloud. This powerful capability provides visibility and insight into the usage of the cloud across dozens of data points and allows cloud operators to view metrics globally or by individual deployed resources.
* Orchestration Service (codenamed [[Heat|"Heat"]]) is a template-driven engine that allows application developers to describe and automate the deployment of infrastructure. The flexible template language can specify compute, storage and networking configurations as well as detailed post-deployment activity to automate the full provisioning of infrastructure as well as services and applications. Through integration with the Telemetry service, the Orchestration engine can also perform auto-scaling of certain infrastructure elements.
* and more projects!

OpenStack stages integrated releases every six months, named according to a voted-upon geographic location nearest to the next Summit. 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.

As a prospective applicant, you should consider joining the #openstack-opw channel, where you can meet mentors, interns past and present, as well as other helpful members of the community.

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 in the [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].

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.

=== How do I apply? ===

The application process is described in detail at https://wiki.gnome.org/OutreachProgramForWomen#Send_in_an_Application. A contribution is required and you answer questions when you apply. You are expected to work full-time on the internship although you can indicate any pre-planned time off in your application.
Please be available and responsive throughout the application period so we can work with you on improving your application.

=== 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, contact the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-internships Internship coordinator mailing list] you have any questions during the application process. There are other 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]]. Mentors should login and apply for a mentor role for OpenStack on https://outreachy.gnome.org/ (the [https://openstackid.org OpenStackID provider] can be used).

The identified volunteer mentors are:

* Ladislav Smola, Developer, Red Hat. Email: lsmola at redhat dot com. IRC: lsmola
* Flavio Percoco, Developer, Red Hat. Email: flavio at redhat dot com. IRC: flaper87
* Liz Blanchard, Senior Interaction Designer, Red Hat. Email: lblanchard at redhat dot com. IRC: lblanchard
* Ju Lim, Member of the Technical Staff, Red Hat. Email: julim at redhat dot com. IRC: julim
* Nikhil Komawar, Software Developer, Rackspace. Email: nikhil.komawar at rackspace dot com IRC: nikhil_k
* Rossella Sblendido, Software Developer, SUSE, Email: rsblendido at suse dot com IRC: rossella_s
* Iccha Sethi, Software Developer, Rackspace, Email: iccha.sethi at rackspace dot com IRC: iccha
* Mike Perez, Senior software engineer, Datera, Email: thingee at gmail dot com IRC: thingee
* Henry Nash, "Wild Duck", IBM. Email: henryn at linux dot vnet dot ibm dot com
* Dina Belova, Software Engineer, Mirantis. Email: dbelova@mirantis.com, IRC: DinaBelova
* John Dickinson, Director of Technology, SwiftStack. Email: me@not.mn, IRC: notmyname
* Victoria Martínez de la Cruz, Developer, Red Hat. Email: victoria at redhat dot com. IRC: vkmc
* Davanum Srinivas, Mirantis. Email: davanum at gmail dot com. IRC: dims
* Alexandra Settle, Rackspace. Email: alexandra.settle(at)rackspace(dot)com. IRC: asettle
* Ed Leafe, IBM. Email: ed(at)openstack(dot)org IRC: edleafe
* Jeremy Stanley, Systems Engineer, OpenStack Foundation. E-mail: fungi@yuggoth.org IRC: fungi
* Elizabeth K. Joseph, Systems Administrator, HP, E-mail: lyz@princessleia.com IRC: pleia2
* Jonathan Harker, Operations Developer, HP, E-mail: jesusaurus at gentlydownthe dot net IRC: jesusaurus

== Volunteer administrators ==

* Victoria Martínez de la Cruz, Developer, Red Hat. Email: victoria at redhat dot com. IRC: vkmc
* Stefano Maffulli, Community Manager, OpenStack Foundation. Reed on IRC. Email: stefano at openstack dot org
* Lana Brindley, Tech writing manager, Rackspace. Email: lana.brindley(at)rackspace(dot)com. IRC: loquacities

More resources for [[Outreachy/resources_for_administrators|Outreachy administrators]].

== Projects ==

Please see the [[Internship_ideas|Ideas page]].

[[Category: Internship]]

Outreachy

2015-09-07T17:01:07Z

Smaffulli: /* What if I have a question about OpenStack? */

== Welcome to OpenStack Outreachy ==

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 program [https://www.gnome.org/outreachy/ Outreachy].

Outreachy helps people from groups underrepresented in free and open source software get involved, by providing a supportive community for beginning to contribute any time throughout the year and offering focused internship opportunities twice a year with a number of free software organizations.

The current round of internships is open to women (cis and trans), trans men, genderqueer people, and all participants of the [http://ascendproject.org/ Ascend Project] regardless of gender. We are planning to expand the program to more participants from underrepresented backgrounds in the future.

== 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 3% [1], [2] 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 Outreachy program is an excellent way to meet that inclusion goal. At the October 2013 OpenStack Summit, mentors and interns presented about their experiences in "[[https://www.openstack.org/summit/portland-2013/session-videos/presentation/what-everyone-ought-to-know-about-openstack-internships|What Everyone Ought to Know about OpenStack Internships]]"

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 $6,250 from OpenStack sponsors or by the Foundation. The Foundation is happy to help companies with sponsorship, and more funding is always welcomed. Please contact stefano at openstack dot org through email if you would like to sponsor.

1. http://www.eskar.dk/andreas/output/PersonalProfile.HTM
2. http://survey.perlfoundation.org/Data-PerlSurvey-2010/R/

== Schedule ==

The application deadline for the December-March Outreachy term has passed, but you can look for a new application period opening in mid-February for May 25 to August 25 internships.

* February 17: participating organizations are announced
* March 3 - March 24: applicants need to get in touch with at least one project and make a contribution to it
* March 3: application system opens
* March 24 - April 27: applicants are encouraged to continue making contributions for the project they applied for;
submitted applications are open for editing
* March 24: application deadline at 7pm UTC
* April 27: accepted participants announced at 7pm UTC on the GNOME web site
* May 25 to August 25: internship period

== 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.

[[File: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 several 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 many companies.
* 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 [[Neutron|"Neutron"]]) 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.
* Telemetry Service (codenamed [[Ceilometer|"Ceilometer"]]) aggregates usage and performance data across the services deployed in an OpenStack cloud. This powerful capability provides visibility and insight into the usage of the cloud across dozens of data points and allows cloud operators to view metrics globally or by individual deployed resources.
* Orchestration Service (codenamed [[Heat|"Heat"]]) is a template-driven engine that allows application developers to describe and automate the deployment of infrastructure. The flexible template language can specify compute, storage and networking configurations as well as detailed post-deployment activity to automate the full provisioning of infrastructure as well as services and applications. Through integration with the Telemetry service, the Orchestration engine can also perform auto-scaling of certain infrastructure elements.
* and more projects!

OpenStack stages integrated releases every six months, named according to a voted-upon geographic location nearest to the next Summit. 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.

As a prospective applicant, you should consider joining the #openstack-opw channel, where you can meet mentors, interns past and present, as well as other helpful members of the community.

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 in the [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].

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.

=== How do I apply? ===

The application process is described in detail at https://wiki.gnome.org/OutreachProgramForWomen#Send_in_an_Application. A contribution is required and you answer questions when you apply. You are expected to work full-time on the internship although you can indicate any pre-planned time off in your application.
Please be available and responsive throughout the application period so we can work with you on improving your application.

=== 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, contact the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-internships Internship coordinator mailing list] you have any questions during the application process. There are other 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]]. Mentors should login and apply for a mentor role for OpenStack on https://outreachy.gnome.org/ (the [https://openstackid.org OpenStackID provider] can be used).

The identified volunteer mentors are:

* Ladislav Smola, Developer, Red Hat. Email: lsmola at redhat dot com. IRC: lsmola
* Flavio Percoco, Developer, Red Hat. Email: flavio at redhat dot com. IRC: flaper87
* Stefano Maffulli, Community Manager, OpenStack Foundation. Reed on IRC. Email: stefano at openstack dot org IRC: reed
* Liz Blanchard, Senior Interaction Designer, Red Hat. Email: lblanchard at redhat dot com. IRC: lblanchard
* Ju Lim, Member of the Technical Staff, Red Hat. Email: julim at redhat dot com. IRC: julim
* Nikhil Komawar, Software Developer, Rackspace. Email: nikhil.komawar at rackspace dot com IRC: nikhil_k
* Rossella Sblendido, Software Developer, SUSE, Email: rsblendido at suse dot com IRC: rossella_s
* Iccha Sethi, Software Developer, Rackspace, Email: iccha.sethi at rackspace dot com IRC: iccha
* Mike Perez, Senior software engineer, Datera, Email: thingee at gmail dot com IRC: thingee
* Henry Nash, "Wild Duck", IBM. Email: henryn at linux dot vnet dot ibm dot com
* Dina Belova, Software Engineer, Mirantis. Email: dbelova@mirantis.com, IRC: DinaBelova
* John Dickinson, Director of Technology, SwiftStack. Email: me@not.mn, IRC: notmyname
* Victoria Martínez de la Cruz, Developer, Red Hat. Email: victoria at redhat dot com. IRC: vkmc
* Davanum Srinivas, Mirantis. Email: davanum at gmail dot com. IRC: dims
* Alexandra Settle, Rackspace. Email: alexandra.settle(at)rackspace(dot)com. IRC: asettle
* Ed Leafe, IBM. Email: ed(at)openstack(dot)org IRC: edleafe
* Jeremy Stanley, Systems Engineer, OpenStack Foundation. E-mail: fungi@yuggoth.org IRC: fungi
* Elizabeth K. Joseph, Systems Administrator, HP, E-mail: lyz@princessleia.com IRC: pleia2
* Jonathan Harker, Operations Developer, HP, E-mail: jesusaurus at gentlydownthe dot net IRC: jesusaurus

== Volunteer administrators ==

* Victoria Martínez de la Cruz, Developer, Red Hat. Email: victoria at redhat dot com. IRC: vkmc
* Stefano Maffulli, Community Manager, OpenStack Foundation. Reed on IRC. Email: stefano at openstack dot org
* Lana Brindley, Tech writing manager, Rackspace. Email: lana.brindley(at)rackspace(dot)com. IRC: loquacities

More resources for [[Outreachy/resources_for_administrators|Outreachy administrators]].

== Projects ==

Please see the [[Internship_ideas|Ideas page]].

[[Category: Internship]]

OldMentorListing

2015-09-07T16:59:19Z

Smaffulli: removed stefano maffulli from the list

Good mentorship is a cornerstone of this program. These resources are very useful for prospective mentors to review prior to adding their name to the table below:

* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/index.html Federico Mena-Quintero's Mentoring HOWTO]
* [https://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Advice for Google Summer of Code mentors]
* [https://flossmanuals.net/GSoCMentoring/ Google Summer of Code Mentor's Guide]

{| class="wikitable sortable"
|-
! Name !! Area of expertise !! Availability !! Contact !! Program
|-
| Davanum Srinivas || Oslo, Nova || 1 or 2 hours per week (EDT) || IRC nick - dims ||
|-
| Joshua Harlow || TaskFlow, Oslo, Anvil, Cloud-Init; Parts of Cinder, Doc8, ... || 3 or 4 hours per week (PDT) || IRC nick - harlowja ||
|-
| Ajaya Agrawal || Keystone || 1 or 2 hours per week (IST) || IRC nick - ajayaa ||
|-
| Rossella Sblendido || Neutron || 2 hours per week (CET) || IRC nick - rossella_s ||
|-
| Baohua Yang || Neutron, Oslo || 2 hours per week (CCT) || IRC nick - baohua ||
|-
| Ghe Rivero || TripleO, Ironic || 3 or 4 hours per week (CEST) || IRC nick - GheRivero ||
|-
| Sean Roberts || Training, Congress, General || 3 or 4 hours per week (PDT) || IRC nick - sarob ||
|-
| Ilya Sviridov || MagnetoDB || 3 or 4 hours per week (EEST) || IRC nick - isviridov ||
|-
| Joshua Hesketh || Infrastructure, 3rd party CI || Australian time || IRC nick - jhesketh ||
|-
| Fawad Khaliq || Neutron, Designate, 3rd party CI || 2 hours per week (PST) || IRC nick - fawadkhaliq ||
|-
| Boris Pavlovic || Rally || 3 or 4 hours per week (All TZ) || IRC nick - boris-42 ||
|-
| Edgar Magana || Neutron, Nova, 3rd party CI || 1 or 2 hours per week (PST) || IRC nick - emagana ||
|-
| Dolph Mathews || Keystone || 1 or 2 hours per week (CT) || IRC nick - dolphm ||
|-
| Sylvain Bauza || Nova || 1 hour per week (CET) || IRC nick - bauzas || Upstream
|-
| John Garbutt || Nova || UK time || IRC nick - johnthetubaguy ||
|-
| Lana Brindley || Documentation || Australian time || IRC nick - loquacities ||
|-
| Brian Moss || Documentation || Australian time || IRC nick - bmoss ||
|-
| Spencer Krum || Infra, Puppet || Pacific Time || IRC nick - nibalizer ||
|-
| Victoria Martínez de la Cruz || Zaqar, Trove || 4 hours per week (ART) || IRC nick - vkmc || GSoC, Outreachy, Upstream
|-
| David Lyle || Horizon || Mountain Time, US || IRC nick - david-lyle ||
|-
| Jeremy Stanley || Project Infrastructure || Americas/Eastern (EST/EDT) || IRC nick - fungi || All
|-
| Elizabeth K. Joseph || Project Infrastructure || Americas/Pacific (PST/PDT) || IRC nick - pleia2 || Outreachy
|-
| Jonathan Harker || Project Infrastructure || Americas/Pacific (PST/PDT) || IRC nick - jesusaurus ||
|-
| François Bureau || Translation || 1 hour per week (FR Time) || IRC nick - Fdot || Upstream
|-
| Christian Berendt || Documentation || CET || IRC nick - berendt ||
|-
| Matthew Treinish || QA || Americas/Eastern (EST/EDT) || IRC nick - mtreinish ||

|}

New comers are welcome to ask questions in irc://irc.freenode.net/#openstack-101

= How to identify newcomers =

The easiest thing to do at the moment is to look at the reviews done by the special agent "[http://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jeepyb/cmd/welcome_message.py Welcome new contributor]":

* [https://review.openstack.org/#/q/reviewer:%22Welcome%252C+new+contributor!%22+status:open,p,00312ead0001b310 open reviews]
* [https://review.openstack.org/#/q/reviewer:%22Welcome%252C+new+contributor!%22+status:abandoned,p,00312ead0001b310 abandoned reviews]

[[Category: Internship]]

SDKs

2015-08-03T23:53:58Z

Smaffulli: /* Python */

= Software Development Kits =

SDKs are a vital part of the OpenStack ecosystem, they help developers write applications for OpenStack and other clouds. For a list of the official OpenStack Python client libraries, see [[OpenStackClients]].

__TOC__

= Definition =

# A set of language bindings that provide a language-level API for accessing OpenStack in a manner consistent with language standards.
# A Getting Started document that shows how to use the API to access OpenStack powered clouds.
# Detailed API reference documentation.
# Tested sample code that you can use as a "starter kit" for your own OpenStack applications.
# SDKs treat OpenStack as a blackbox and only interact with the REST/HTTP API.
# Must be [http://opensource.com/life/14/1/evaluate-sustainability-open-source-project sustainable].
# License must be compatible with Apache License v2.

= Additional Criteria =

What criteria is used to determine whether or not an SDK can be considered an OpenStack SDK has not been formalized. This has been initially discussed at the OpenStack Grizzly Summit ([https://etherpad.openstack.org/sdk-documentation etherpad]). Naturally the SDK will need to meet the definition above. In addition we thought the OpenStack Foundation may want to consider a compatibility test suite that will validate whether or not an SDK supports OpenStack.

These are items that could be used as criteria to define an SDK but themselves require further definition w.r.t. SDKs.

# Handle extensions in some way.
# Backwards compatibility.
# Compatibility with test suite.

= Official OpenStack Clients =

The [[OpenStackClients]] are the native Python bindings for the OpenStack APIs. They are used to implement the command-line interfaces (which ship with the library).

= Known SDKs =

What follows is a list of known SDKs that support OpenStack. This is not a list of official OpenStack SDKs. What constitutes an official OpenStack SDK has not been determined. This is an area the needs more work (see Criteria section).

To date, SDKs that support OpenStack fall into two categories. SDKs that support multiple clouds including OpenStack (aka multi-cloud toolkits) and SDKs that support OpenStack only. If you're aware of any other SDKs, please add them to the lists below.

= [[OpenStack]] Toolkits =

== C ==
* [https://github.com/ukyg9e5r6k7gubiekd6 Keystone and Swift libraries] C library bindings to the OpenStack Keystone and Swift APIs.
* [https://github.com/RedHatEMEA/c-keystoneclient c-keystoneclient] c-keystoneclient is a C-based client library for OpenStack Keystone authentication.
== C++ ==
[https://github.com/bshafiee/Swift_CPP_SDK SWIFT_CPP_SDK] is a C++ binding for accessing the Swift REST API.
== Clojure ==
* [https://github.com/oubiwann/clj-openstack clj-openstack] is a pure Clojure Binding for OpenStack Clouds
== Erlang ==
* [https://github.com/oubiwann/lfe-openstack lfe-openstack] is a pure LFE (Lisp Flavored Erlang) language binding for OpenStack Clouds.
== Go ==
* [https://launchpad.net/goose Goose] provides comprehensive Go binding to Openstack including nova, glance, keystone, swift, and neutron apis.
* [https://github.com/rackspace/gophercloud Gophercloud] provides a Go binding to OpenStack cloud APIs.
* [https://wiki.openstack.org/wiki/OpenStack-SDK-Go golang-client] is a proposed OpenStack project that is designed to improve the experience of OpenStack end-users who are using the Go programming language by providing them with everything they need to develop applications against OpenStack.
* [https://github.com/ncw/swift swift] implements Swift client on Go. Keystone v1,v2,v3 is supported

== Java ==
* [http://jclouds.apache.org/ Apache jclouds] is an open source library that helps you get started in the cloud and utilizes your Java or Clojure development skills. The jclouds API gives you the freedom to use portable abstractions or cloud-specific features.
* [http://www.openstack4j.com OpenStack4j] A fluent Java OpenStack API.
* [https://github.com/woorea/openstack-java-sdk OpenStack Java SDK] is a Java binding for the OpenStack APIs.
* [https://github.com/bluebossa63/openstack-server-apps User Registration Service] is a server side user registration service based on openstack-java-sdk.
* [http://joss.javaswift.org/ Java OpenStack Storage aka JOSS] is a dedicated Java binding for accessing the Swift REST API.

== Android ==
* [https://github.com/bluebossa63/OpenStackIntegration OpenStackIntegration] is a Android Implementation based on openstack-java-sdk.

== JavaScript ==
* [http://ging.github.com/jstack/ jstack] is a JavaScript implementation of the OpenStack API.
* [https://github.com/gabrielhurley/js-openclient js-openclient] is a very opinionated core client which can be used in either Node.js or in the browser (browser support not yet complete) to communicate with a RESTful APIs, including but not limited to any OpenStack-compatible API.
== .NET ==
* [https://wiki.openstack.org/wiki/OpenStack-SDK-DotNet OpenStack-SDK-DotNet] is a software development kit (SDK) for working with OpenStack.
* [https://github.com/rackspace/openstack.net OpenStack.NET] is a .NET SDK for OpenStack.
* [https://github.com/abettadapur/marconiclient MarconiClient.NET] is a .NET client for Marconi

== Node.js ==
* [https://github.com/nodejitsu/pkgcloud pkgcloud] is a standard library for Node.js that abstracts away differences among multiple cloud providers.
== Perl ==
* [https://github.com/ironcamel/Net-OpenStack-Compute Net::OpenStack::Compute] provides Perl bindings for the OpenStack Compute API. It also provides a command line tool oscompute for interacting with an OpenStack deployment.
== PHP ==
* [https://github.com/rackspace/php-opencloud php-opencloud] is a software development kit (SDK) to help developers using PHP to work with OpenStack and other open clouds.
* [https://github.com/zendframework/ZendService_OpenStack ZendService_OpenStack] is a PHP library that implements the last versions of the OpenStack API. It's 100% compliant with the specification of OpenStack.
* [https://wiki.openstack.org/wiki/OpenStack-SDK-PHP OpenStack-SDK-PHP] is a proposed OpenStack project that is designed to improve the experience of OpenStack end-users who are using the PHP programming language by providing them with everything they need to develop applications against OpenStack.

== Python ==
* The [[OpenStackClients]] are the native Python bindings for the OpenStack APIs. They are used to implement the command-line interfaces (which ship with the library).
* The [[SDK-Development/PythonOpenStackSDK]] project is a proposed solution to offering an SDK that provides a single point of entry for consumers, and a base from which other tools can be built upon, such as command-line interfaces.
* [https://github.com/rackspace/pyrax pyrax] should work with most OpenStack-based cloud deployments, though it specifically targets the Rackspace public cloud.
* [http://libcloud.apache.org/ Apache libcloud] is a standard Python library that abstracts away differences among multiple cloud provider APIs.
* [http://git.openstack.org/cgit/openstack-infra/shade/tree/ OpenStack Shade] shade is a simple client library for operating OpenStack clouds.

== Ruby ==
* [http://aviator.github.io/www/ Aviator] An elegantly designed OpenStack SDK for Ruby
* [http://fog.io/ fog] provides an accessible entry point and facilitates cross service compatibility.

== Yaml ==
* [https://github.com/sahid/warm/ Warm] Provides a template based solution to deploy environments.

Contact

2015-06-22T17:51:10Z

Smaffulli: removed Stefano from the list /* General Help */

= General Help =

For any question about the OpenStack project, see:

* Our [https://ask.openstack.org/questions/ Ask OpenStack] site, for your questions about installing, using, or contributing to OpenStack
* Our [[MailingLists|Mailing Lists]]
* Our [[IRC|IRC Channels]]
* [[TomFifield|Tom Fifield]], Community Manager

= Wiki administrators =

You can contact [[AnneGentle|Anne Gentle]] or [[ThierryCarrez|Thierry Carrez]] with any technical question you have on the wiki.

= OpenStack Foundation =

Questions, comments and feedback about the governance of the OpenStack project can be directed to [mailto:info@openstack.org the staff of the OpenStack Foundation]. You may also find useful updates on the [http://www.openstack.org/foundation/ main foundation website.]

Meetings/Community

2015-06-22T17:50:37Z

Smaffulli: removing stefano from the host list

= Weekly Community Office Hours =

The Community team offers two spots weekly to welcome new people, offer help, listen to users and developers for suggestions, ideas and anything going around OpenStack.

* Tuesdays at 0800 UTC on [[IRC|<code><nowiki>#openstack-community</nowiki></code>]], usually hosted by Tom Fifield (nickname fifieldt)
* Fridays at 1800 UTC on [[IRC|<code><nowiki>#openstack-community</nowiki></code>]], looking for a host
One-on-one private conversations are also possible, on IRC or ad-hoc channels (just let us know).

= Weekly Community Software Services Meetings =

The Community team is responsible for quite a lot of software, from [https://ask.openstack.org Ask OpenStack] to [https://groups.openstack.org Groups Portal] to [http://activity.openstack.org Activity Board] and other systems. This meeting is to coordinate the development and maintenance of such services.

* Mondays at 1700 UTC on [[IRC|<code><nowiki>#openstack-meeting-alt</nowiki></code>]], usually hosted by Stefano Maffulli (nickname reed)
* [[Community/MeetingAgenda]]
* [http://eavesdrop.openstack.org/meetings/community/ Meeting logs]

StefanoMaffulli

2015-06-22T17:49:50Z

Smaffulli:

Stefano Maffulli is former OpenStack technical community manager. He goes by reed on IRC. Read more about him at http://maffulli.net/.

AcademicInitiative

2015-06-13T16:57:59Z

Smaffulli: made this group visibly silent and looking for driver

= OpenStack Academic Initiative =

'''This group is silent and needs a person responsible to drive its progress.'''

== Mission: ==
* provide a place for all research academics efforts can be advertised and found, about and around OpenStack (not generic about IaaS or PaaS)
** a list of papers published and ongoing research
** a list of conferences about cloud computing
* maintain a list of ideas for the companies to sponsor research,like a "market"
* a place for the companies to say what they need and research can execute
** undergrad level, gsoc-style, time starved but there are many of them. it's important to be easy for them to contribute
** masters level, more in depth work, empirical studies like performance evaluation
** phd level, exploratory type of research
* handle the funding, hr tasks, mentoring: who's going to manage this?
** mentoring is intense and time consuming, but crucial for the success of research
* provide resources, like hardware for tests, for researchers
* advertise this initiative among researchers
** Example: setup OpenStack tracks at a couple of relevant conferences

== Research Areas ==

Openstack is a very nice platform that could be leveraged by Academia for various research projects. Areas include:
* (General) Distributed Systems
* Scalable data layer
** CS.Princeton (Arpan Ghosh)
* Software Defined Networking
* Policy and languages
* Algorithms
** Resource Allocation
** Scheduling
** Network optimization
* Data mining and machine learning
** Monitoring and data collection of large data centers
** Mining patterns from collected data and applications e.g. anomaly detection etc.

== Next steps: ==
Identify the group responsible for this initiative and define action items, deadlines and deliverables. Contact the [[Governance/Foundation/UserCommittee|User Committee]] to volunteer.

[[Category:Working_Groups]]

Contributors/Corporate

2015-06-11T14:41:09Z

Smaffulli:

The list of Corporate CLAs allowed to contribute to OpenStack projects. (Individual developers still need to fill out the Individual [[HowToContribute#Contributors_License_Agreement|Contributors_License_Agreement]]). If you need to update the list of employees authorized to commit code to OpenStack, please read [[HowToUpdateCorporateCLA | How To Update Corporate CLA]].

{| class="wikitable sortable"
|-
! Company name !! Date CCLA
|-
| ADII Research and Applications || 2010-07-19
|-
| All To Success Inc || 2010-09-01
|-
| Alyseo || 2012-11-18
|-
| American Megatrends, Inc || 2011-03-25
|-
| ANEXIA Internetdlenstlestungs GmbH || 2010-07-19
|-
| ANSO Labs || 2010-08-14
|-
| ArrayNetworks || 2012-11-20
|-
| EMC Corp. || 2012-11-12
|-
| Atlanta Cloud Technology, Inc || 2010-10-26
|-
| Atomia || 2012-01-30
|-
| Attune Infocom Pvt Ltd || 2010-08-05
|-
| Austin Software Foundry, Inc || 2011-01-21
|-
| B1 Systems GmbH || 2011-02-02
|-
| Bash IT || 2011-05-23
|-
| Bayoda GmbH || 2010-07-20
|-
| Brocade Communications || 2011-04-11
|-
| Caleb Tennis || 2010-08-14
|-
| Canonical ||
|-
| CERN || 2012-01-23
|-
| ChuanhowTech || 2011-08-23
|-
| Cisco || 2011-03-31
|-
| Citrix || 2010-08-16
|-
| Citrix R&D || 2011-08-02
|-
| Cloud Central Pty Ltd || 2010-07-19
|-
| Cloud.com || 2010-07-27
|-
| CloudFlow, Inc || 2010-10-26
|-
| CloudNucleus || 2010-07-22
|-
| CloudScaling || 2010-07-22
|-
| CloudSoft || 2010-09-23
|-
| Cloud Technology Partners - cloudTP || 2012-06-14
|-
| Colloquium || 2010-08-20
|-
| Consultorpc || 2010-08-26
|-
| Creationline, Inc || 2010-11-01
|-
| Cybera, Inc || 2011-08-25
|-
| Dell, Inc || 2011-11-27
|-
| Delta Electronics || 2011-08-29
|-
| DreamHost || 2011-06-21
|-
| Egon Technologies, LLC || 2010-07-19
|-
| Enterprise DB || 2010-11-16
|-
| Esprit || 2010-11-29
|-
| ForLinux || 2010-08-31
|-
| Fourth Paradigm Development || 2011-06-17
|-
| German Cloud || 2011-03-19
|-
| Grid Dynamics || 2011-07-05
|-
| GridCentric, Inc || 2010-08-03
|-
| GridGain Systems || 2011-06-22
|-
| Guardian News and Media Ltd. || 2012-11-28
|-
| hastexo || 2012-05-24
|-
| Hewlett-Packard || 2011-08-03
|-
| IBM || 2012-02-02
|-
| InfraStacks LLC || 2011-07-26
|-
| Intalio, Inc || 2010-08-10
|-
| Intel Corp. || 2011-09-20
|-
| Internap || 2010-10-26
|-
| Intridea || 2011-06-21
|-
| IVO Networks, Inc || 2011-07-27
|-
| LC9 || 2010-08-11
|-
| LeaseWeb BV || 2010-09-09
|-
| Linagora || 2012-09-06
|-
| LinMin Corp || 2010-07-21
|-
| Locaweb || 2012-06-13
|-
| Logic Surge, Inc || 2010-07-19
|-
| Make a Byte, Inc || 2010-08-16
|-
| Media Temple Inc || 2010-08-16
|-
| Metacloud, Inc. || 2012-04-17
|-
| Memset Ltd || 2011-01-21
|-
| Midokura Co., Ltd. || 2010-07-30
|-
| Mirantis || 2011-06-15
|-
| Morphlabs K.K. || 2010-11-01
|-
| Morphlabs, Inc. || 2010-07-22
|-
| MOVE-IT || 2010-09-20
|-
| National Institute of Informatics || 2010-12-21
|-
| NEC Corporation || 2011-08-09
|-
| NetApp, Inc || 2011-04-25
|-
| Netmagic Solutions Pvt. Ltd. || 2012-05-04
|-
| Nexenta Systems || 2011-08-24
|-
| Nicira Networks, Inc || 2010-10-28
|-
| Nimbis Services, Inc. || 2011-29-11
|-
| Nimbula, Inc. || 2012-10-01
|-
| NTT Cyber Space Laboratories || 2010-11-16
|-
| NTT Data AgileNet || 2010-11-07
|-
| NTT Data Corporation || 2010-11-18
|-
| NTT DOCOMO, Inc || 2012-06-13
|-
| NTT PF Labs || 2010-12-21
|-
| Open Solutions || 2011-07-13
|-
| Open-V || 2011-08-20
|-
| Openfiler || 2010-07-19
|-
| Opscode, Inc || 2010-07-15
|-
| Peartree Media Limited || 2010-07-19
|-
| Philips Technology || 2011-04-19
|-
| Piston Cloud Computing, Inc || 2011-01-21
|-
| Persistent Systems Ltd || 2011-05-12
|-
| Qihoo 360 Technology Co. Ltd || 2013-01-08
|-
| Qinnova Technology Egypt || 2010-08-06
|-
| Rackspace || 2010-07-15
|-
| Radon Systems || 2010-09-02
|-
| Riverbed Technology || 2011-08-15
|-
| Saba Software, Inc || 2010-10-28
|-
| Samsung Electronics || 2010-08-25
|-
| Samsung SDS || 2011-12-13
|-
| Scalr Inc || 2011-06-07
|-
| Server Corps, LLC || 2010-07-24
|-
| SGI || 2010-08-29
|-
| SilverKey Technologies, LCC || 2010-07-26
|-
| SINA Corporation || 2012-01-17
|-
| SIOS Technology Corporation || 2010-08-18
|-
| Skydera Inc || 2011-08-09
|-
| StackOps Technologies S.L. || 2012-09-19
|-
| SUSE || 2011-09-30
|-
| SwiftStack, Inc || 2012-02-16
|-
| Symplified, Inc || 2010-07-28
|-
| TeXalute Inc || 2011-03-22
|-
| Third Eye Consulting Services and Solutions LLC || 2011-05-23
|-
| TISSAT || 2011-07-25
|-
| Ultra Serve Internet Pty Ltd || 2010-08-09
|-
| VA Linux || 2011-04-01
|-
| Vertex Software Pvt Ltd || 2011-05-03
|-
| Virima Technologies || 2010-08-27
|-
| Warsaw Data Center || 2010-10-26
|-
| WINK Streaming || 2010-07-19
|-
| Wolfram Research Inc || 2011-02-11
|-
| Yahoo! Inc. || 2011-11-01
|-
| Zadara Storage || 2011-06-17
|-
| Zentific LLC || 2011-06-11
|-
| Zergsoft || 2011-06-07
|-
| ABT Limitel || 2013-09-28
|-
| Ambrella Ltd || 2013-07-22
|-
| Apple Inc. || 2013-10-24
|-
| Aptira || 2013-08-20
|-
| Basho Technologies Inc. || 2013-07-17
|-
| Bull SAS || 2013-10-10
|-
| Checkpoint || 2013-11-11
|-
| Cloud Conjure LLC || 2013-04-23
|-
| Cloudbase Srl || 2013-06-10
|-
| Cloudian Inc. || 2013-09-25
|-
| Cloudwatt || 2013-09-11
|-
| Comcast || 2012-09-25
|-
| Coraid Inc. || 2013-03-14
|-
| Ebay Software Foundation || 2012-03-04
|-
| Embrane || 2013-03-23
|-
| Enovance || 2011-12-29
|-
| Ericsson || 2012-02-07
|-
| Evault || 2013-04-09
|-
| Forgerock Inc. || 2013-04-01
|-
| Fujitsu Limited || 2012-08-06
|-
| Global Logic Inc. || 2013-08-05
|-
| Green and Secure IT Ltd. || 2013-04-03
|-
| Hetzner Pty Ltd. || 2013-10-23
|-
| HGST Inc. || 2013-11-20
|-
| Hitachi Data Systems || 2013-05-03
|-
| Inktank.com || 2013-05-13
|-
| Institute for System Programming Russian Academy of Science (ISP-RAS) || 2013-04-22
|-
| IOData Centers LLC || 2013-10-14
|-
| iPlant Collaborative || 2013-05-01
|-
| iWeb Technologies Inc. || 2013-04-16
|-
| Komola GmbH || 2013-05-10
|-
| Kylinos || 2013-09-10
|-
| Mediasift Ltd. || 2013-04-16
|-
| Microchild Technlogies || 2013-07-16
|-
| Netease || 2013-05-30
|-
| NTT Software Corporation || 2013-06-27
|-
| NTT Software Innovation Center || 2013-05-20
|-
| Objectif Libre || 2013-03-11
|-
| Orange || 2013-08-01
|-
| Osones || 2013-11-20
|-
| PDF Complete || 2013-05-20
|-
| Plumgrid || 2013-01-16
|-
| Quantcast Corp. || 2013-05-01
|-
| Radware Ltd. || 2011-10-23
|-
| RJIL || 2013-10-26
|-
| Safenet Inc. || 2013-04-23
|-
| Semihalf || 2013-11-07
|-
| Sohonet Ltd. || 2013-10-31
|-
| Stackinsider Technology || 2013-08-22
|-
| SWITCH || 2013-05-06
|-
| Symantec || 2013-10-10
|-
| Tata Consultancy Services || 2013-07-28
|-
| Thales || 2013-07-15
|-
| Unitedstack Inc. || 2013-05-22
|-
| University of Oregon || 2012-04-30
|-
| University of South China || 2012-07-19
|-
| Violin Memory Inc. || 2013-06-06
|-
| Virtual Bridges Inc. || 2013-09-06
|-
| VmWare || 2013-08-31
|-
| Yahele LLC || 2013-09-05
|-
| Ysance || 2013-06-28
|-
| Zelin.io || 2013-05-13
|-
| Oracle || 2013-12-08
|-
| Parelastic || 2013-12-20
|-
| Docker, Inc. || 2013-12-16
|-
| Silicom, Ltd. || 2013-12-25
|-
| Awcloud || 2012-04-12
|-
| Izel Technologies || 2014-01-01
|-
| SpclOps, Inc. || 2014-01-08
|-
| Numergy || 2014-01-14
|-
| Reliance Jio Infocom || 2014-01-19
|-
| StackStorm Inc. || 2014-01-24
|-
| Ryussi Technologies || 2014-02-14
|-
| OneCloud Consulting, Inc. || 2014-02-13
|-
| Eurogiciel Ingenierie || 2014-02-26
|-
| Inocybe Technologies Inc. || 2014-02-26
|-
| Fujitsu Limited || 2014-03-04
|-
| NovoTel Ltd. || 2014-03-05
|-
| OSNEXUS || 2014-04-09
|-
| Izel Technologies || 2014-04-09
|-
| Vimeo LLC || 2014-04-08
|-
| Tektronix Communications || 2013-04-07
|-
| Symantec || 2014-03-29
|-
| Workday, Inc. || 2014-03-26
|-
| Cray Inc. || 2014-03-25
|-
| THSTACK || 2014-03-21
|-
| Datera, Inc. || 2014-03-18
|-
| Just One Data, Inc. || 2014-03-17
|-
| Kili.io, Inc. || 2014-03-11
|-
| Sony Mobile Communications AB || 2014-03-07
|-
| Jawa Talent || 2014-04-12
|-
| University of Western Ontario || 2014-04-15
|-
| CYSO || 2014-04-29
|-
| Gigaspaces || 2014-05-01
|-
| Fusion.io || 2014-05-05
|-
| Versa Networks || 2014-05-07
|-
| Nimbus Data || 2014-05-15
|-
| Nine Internet Solutions AG || 2014-05-16
|-
| [[Quobyte]] Inc. || 2014-05-19
|-
| Red Hat, Inc. || 2014-05-21
|-
| SCALITY SA || 2014-06-05
|-
| Hitachi America, Ltd. || 2014-06-04
|-
| Alcatel Lucent || 2014-06-09
|-
| AT&T || 2014-07-17
|-
| OlinData || 2014-7-16
|-
| it-novum GmbH || 2014-07-14
|-
| B<>COM || 2014-07-11
|-
| cloudsigma.com || 2014-06-27
|-
| ThoughtWorks, Inc || 2014-06-26
|-
| Risk Management Solutions, Inc. || 2014-06-20
|-
| Infoblox || 2014-06-04
|-
| DEK Technologies || 2014-09-20
|-
| Wikimedia Foundation, Inc. || 2014-09-18
|-
| Time Warner Cable || 2014-07-21
|-
| H3C || 2014-07-23
|-
| Bloomberg Finance LP || 2014-07-25
|-
| Zetta.IO Technology AS || 2014-08-05
|-
| SysEleven GmbH || 2014-08-08
|-
| CREATE-NET || 2014-08-08
|-
| MapR Technologies || 2014-08-08
|-
| InWin Inc. || 2014-08-11
|-
| StorPool Bulgaria OOD || 2014-08-13
|-
| Letv Cloud Computing || 2014-08-14
|-
| KVH Co., Ltd. || 2014-08-18
|-
| Stratoscale Ltd. || 2014-08-25
|-
| Anchor Systems Pty Ltd || 2014-09-02
|-
| Codethink Ltd || 2014-09-10
|-
| CodiLime, Inc. || 2014-09-10
|-
| Parallels International GmbH || 2014-09-10
|-
| Calsoft ||2014-09-11
|-
| Emulex Corporation || 2014-12-01
|-
| SAP || 2014-07-03
|-
| SAS Institute Inc. || 2015-02-25
|-
| Battelle LLC || 2015-03-03
|-
| CLOUDDON LLC || 2014-07-03
|-
| cPanel, Inc. || 2014-10-01
|-
| DigiCert, Inc. || 2014-10-03
|-
| Metaswitch Networks Ltd || 2014-10-06
|-
| Oodrive || 2014-10-09
|-
| LINARO LIMITED || 2014-10-17
|-
| CloudFounders || 2014-10-20
|-
| GoodData || 2014-10-20
|-
| Hitachi India Pvt. Ltd. || 2014-10-22
|-
| OVH || 2014-10-28
|-
| CD Cloudenablers Private Limited || 2014-10-19
|-
| Percona LLC || 2014-11-12
|-
| x-ion GmbH || 2014-11-14
|-
| Linux Foundation || 2014-11-18
|-
| xFlow Research Inc. || 2014-11-18
|-
| Nokia Solutions and Networks Oy || 2014-11-19
|-
| Chelsio Communications Inc. || 2014-11-19
|-
| 6WIND || 2014-11-20
|-
| Ammeon || 2014-12-09
|-
| Twitter || 2014-12-12
|-
| MIT Lincoln Laboratory || 2014-12-14
|-
| CenturyLink || 2014-12-23
|-
| Anuta Networks International LLC || 2015-01-06
|-
| Acelio || 2015-01-08
|-
| Wipro Ltd. || 2014-01-14
|-
| KEMP TECHNOLOGIES, INC || 2015-01-27
|-
| pluribus networks || 2015-01-30
|-
| N5 Tech, Inc || 2015-02-08
|-
| OneCloud Consulting || 2015-02-21
|-
| The Johns Hopkins University Applied Physics Laboratory LLC || 2015-02-24
|-
| SVA Gmbh || 2015-02-27
|-
| University of Chicago || 2015-03-30
|-
| LENOVO || 2015-03-20
|-
| Swisscom || 2015-03-23
|-
| PowerTech Information Systems AS || 2015-03-30
|-
| Virtustream || 2015-04-01
|-
| Rabbit Inc || 2015-04-03
|-
| Tintri, Inc. || 2015-04-20
|-
| Dot Hill || 2015-04-28
|-
| HGST, Inc || 2015-05-06
|-
| Huron Technologies || 2015-05-09
|-
| Apcera || 2015-05-12
|-
| Inocybe Technologies || 2015-05-12
|-
| Blockbridge Networks LLC || 2015-05-15
|-
| BMW Car IT GmbH || 2015-05-21
|-
| Nestlé Nespresso SA || 2015-05-22
|-
| Quantomic, LLC || 2015-05-22
|-
| Siaras Inc. || 2015-06-05
|-
| Ceske Radiokomunikace a.s. || 2015-06-05
|-
| Air Computing Inc. || 2015-06-05
|-
| Endurance International Group || 2015-06-09
|-
| Blackboard Inc. || 2015-06-09
|-
| || 2015-0
|-
|}

Diversity

2015-06-02T22:57:25Z

Smaffulli:

Diversity Working Group

This is a work in progress for Diversity Working Group page.

Proposed Charter at the board meeting in Vancouver, May 15th link.

[[Category: Working_Groups]]

OpenStack Upstream Institute

2015-05-16T16:44:56Z

Smaffulli: /* Staff */

<languages />
<translate>

With over 1000 developers from 130 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.


We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.


[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training = 


Next session of the [http://www.eventbrite.com/e/openstack-upstream-training-vancouver-tickets-15649117933 OpenStack Upstream Training will be in Vancouver], before the OpenStack Summit.


Meeting Room 10, 11 & 12

VANCOUVER CONVENTION CENTRE

EAST BUILDING

1055 Canada Place, Vancouver, Canada, BC V6C 0C3

Note that the East Building is also a hotel, the Pan Pacific Hotel. Take the elevator to the convention floor and you'll find the rooms.

See [https://www.openstack.org/assets/vancouver-summit/maps/OSYVR-WEB-COMP-FINAL-REV2-5.jpg this map for reference].


Saturday, May 16, 2015 at 9:30 AM to 5:00 PM - Sunday, May 17, 2015 at 9:30 AM to 5:00 PM (PDT)


Bring a laptop with wifi + 4GB RAM Ubuntu virtual machine

= How to prepare = 


* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine
* Check that apt-get install works from within the virtual machine
* Get in touch with the team <upstream-training@openstack.org> to pick a contribution to work on.
</translate>

= Staff =

Stefano Maffulli, Chris Ricker, Tim Freund and Sylvain Bauza will lead the next training in Vancouver, in English. Add yourself to the list of [[mentors]], too. Tools and processes for mentors and staff are kept on the [[OpenStack_Upstream_Training/Admin| admin]] page.

'''Still looking for help: please add yourself to the list below.'''

* Tim Freund <tim@freunds.net> (training, assistant, english)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, training, french, english)
* Lana Brindley (assistant, mentoring, English)
* Rossella Sblendido (assistant, Italian, English)
* Victoria Martínez de la Cruz <victoria@vmartinezdelacruz.com> (assistant, english)
* Takashi Torii <t-torii@ce.jp.nec.com> (assistant, japanese)
* KATO Tomoyuki <kato.tomoyuki@jp.fujitsu.com> (assistant, Japanese)
* macJack <macjacktw@hotmail.com> (assistant, English, Chinese)
* François Bureau <francois.bureau@cloudwatt> (assistant, french, english) - irc : Fdot

[https://etherpad.openstack.org/p/upstream-training-vancouver Etherpad for Vancouver]

OpenStack Upstream Institute

2015-05-15T01:36:15Z

Smaffulli:

OpenStack Upstream Institute

2015-05-15T01:35:10Z

Smaffulli:

<languages />
<translate>

With over 1000 developers from 130 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.


We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.


[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training = 


Next session of the [http://www.eventbrite.com/e/openstack-upstream-training-vancouver-tickets-15649117933 OpenStack Upstream Training will be in Vancouver], before the OpenStack Summit.


Meeting Room 10, 11 & 12
VANCOUVER CONVENTION CENTRE
EAST BUILDING
1055 Canada Place, Vancouver, Canada, BC V6C 0C3

Note that the East Building is also a hotel, the Pan Pacific Hotel. Take the elevator to the convention floor and you'll find the rooms.

See [https://www.openstack.org/assets/vancouver-summit/maps/OSYVR-WEB-COMP-FINAL-REV2-5.jpg this map for reference].


Saturday, May 16, 2015 at 9:30 AM to 5:00 PM - Sunday, May 17, 2015 at 9:30 AM to 5:00 PM (PDT)


Bring a laptop with wifi + 4GB RAM Ubuntu virtual machine

= How to prepare = 


* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine
* Check that apt-get install works from within the virtual machine
* Get in touch with the team <upstream-training@openstack.org> to pick a contribution to work on.
</translate>

= Staff =

Stefano Maffulli, Chris Ricker, Tim Freund and Sylvain Bauza will lead the next training in Vancouver, in English. Add yourself to the list of [[mentors]], too. Tools and processes for mentors and staff are kept on the [[OpenStack_Upstream_Training/Admin| admin]] page.

'''Still looking for help: please add yourself to the list below.'''

* Tim Freund <tim@freunds.net> (training, assistant, english)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, training, french, english)
* Lana Brindley (assistant, mentoring, English)
* Rossella Sblendido (assistant, Italian, English)
* Victoria Martínez de la Cruz <victoria@vmartinezdelacruz.com> (assistant, english)
* Takashi Torii <t-torii@ce.jp.nec.com> (assistant, japanese)
* KATO Tomoyuki <kato.tomoyuki@jp.fujitsu.com> (assistant, Japanese)
* macJack <macjacktw@hotmail.com> (assistant, English, Chinese)
* François Bureau <francois.bureau@cloudwatt> (assistant, french, english) - irc : Fdot

OpenStack Upstream Institute

2015-05-14T21:59:16Z

Smaffulli:

<languages />
<translate>

With over 1000 developers from 130 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.


We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.


[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training = 


Next session of the [http://www.eventbrite.com/e/openstack-upstream-training-vancouver-tickets-15649117933 OpenStack Upstream Training will be in Vancouver], before the OpenStack Summit.


Meeting Room 10, 11 & 12, VANCOUVER CONVENTION CENTRE, 1055 Canada Place, Vancouver, Canada, BC V6C 0C3


Saturday, May 16, 2015 at 9:30 AM to 5:00 PM - Sunday, May 17, 2015 at 9:30 AM to 5:00 PM (PDT)


Bring a laptop with wifi + 4GB RAM Ubuntu virtual machine

= How to prepare = 


* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine
* Check that apt-get install works from within the virtual machine
* Get in touch with the team <upstream-training@openstack.org> to pick a contribution to work on.
</translate>

= Staff =

Stefano Maffulli, Chris Ricker, Tim Freund and Sylvain Bauza will lead the next training in Vancouver, in English. Add yourself to the list of [[mentors]], too. Tools and processes for mentors and staff are kept on the [[OpenStack_Upstream_Training/Admin| admin]] page.

'''Still looking for help: please add yourself to the list below.'''

* Tim Freund <tim@freunds.net> (training, assistant, english)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, training, french, english)
* Lana Brindley (assistant, mentoring, English)
* Rossella Sblendido (assistant, Italian, English)
* Victoria Martínez de la Cruz <victoria@vmartinezdelacruz.com> (assistant, english)
* Takashi Torii <t-torii@ce.jp.nec.com> (assistant, japanese)
* KATO Tomoyuki <kato.tomoyuki@jp.fujitsu.com> (assistant, Japanese)
* macJack <macjacktw@hotmail.com> (assistant, English, Chinese)
* François Bureau <francois.bureau@cloudwatt> (assistant, french, english) - irc : Fdot

OpenStack Upstream Institute

2015-05-14T21:57:13Z

Smaffulli: /* Staff */

<languages />
<translate>

With over 1000 developers from 130 different companies worldwide, OpenStack is one of the largest collaborative software-development projects. Because of its size, it is characterized by a huge diversity in '''social norms''' and '''technical conventions'''. These can significantly slow down the speed at which changes by newcomers are integrated in the OpenStack project.


We've designed a training program to accelerate the speed at which new OpenStack developers are successful at integrating their own roadmap into that of the OpenStack project. The program shows developers how to ensure their bug fix or feature is accepted in the OpenStack project in a minimum amount of time. Students are required to work on real-life bug fixes or new features during two days of real-life classes and online mentoring, until the work is accepted by OpenStack. The live two-day class teaches them to navigate the intricacies of the project's technical tools and social interactions. In followup sessions, the students benefit from individual online sessions to help them resolve any remaining problems they might have.


[[OpenStack_Upstream_Training/Info|More details]]

= When & Where to get OpenStack Upstream Training = 


Next session of the [http://www.eventbrite.com/e/openstack-upstream-training-vancouver-tickets-15649117933 OpenStack Upstream Training will be in Vancouver], before the OpenStack Summit.


Meeting Room 10, 11 & 12, VANCOUVER CONVENTION CENTRE, 1055 Canada Place, Vancouver, Canada, BC V6C 0C3


Saturday, May 16, 2015 at 9:30 AM to 5:00 PM - Sunday, May 17, 2015 at 9:30 AM to 5:00 PM (PDT)


Bring a laptop with wifi + 4GB RAM Ubuntu virtual machine

= How to prepare = 


* Make sure you have a wifi enabled laptop with you.
* Create a virtual machine on the laptop with Ubuntu 12.04 or 14.04 installed and 4GB of RAM.
* Check that a you can ssh from your laptop to the virtual machine. Check that apt-get install works from within the virtual machine.
* Get in touch with Loic Dachary <loic@dachary.org> to pick a contribution to work on.
</translate>

= Staff =

Stefano Maffulli, Chris Ricker, Tim Freund and Sylvain Bauza will lead the next training in Vancouver, in English. Add yourself to the list of [[mentors]], too. Tools and processes for mentors and staff are kept on the [[OpenStack_Upstream_Training/Admin| admin]] page.

'''Still looking for help: please add yourself to the list below.'''

* Tim Freund <tim@freunds.net> (training, assistant, english)
* Chris Ricker <chris.ricker@gmail.com> (training, mentoring, assistant, english)
* Sylvain Bauza <sbauza@redhat.com> (assistant, mentoring, training, french, english)
* Lana Brindley (assistant, mentoring, English)
* Rossella Sblendido (assistant, Italian, English)
* Victoria Martínez de la Cruz <victoria@vmartinezdelacruz.com> (assistant, english)
* Takashi Torii <t-torii@ce.jp.nec.com> (assistant, japanese)
* KATO Tomoyuki <kato.tomoyuki@jp.fujitsu.com> (assistant, Japanese)
* macJack <macjacktw@hotmail.com> (assistant, English, Chinese)
* François Bureau <francois.bureau@cloudwatt> (assistant, french, english) - irc : Fdot

Contributors/Corporate

2015-05-08T16:35:41Z

Smaffulli: HGST

Website

2015-05-06T23:01:18Z

Smaffulli: /* Providing Website Feedback */

== Contributing to [http://www.openstack.org OpenStack.org] ==

'''Website Manager''': Todd Morey
* Email Address: todd@openstack.org
* skype / irc: toddmorey

=== Providing Website Feedback ===

To provide general feedback about the openstack.org website or to submit bugs, please log a bug or request at http://bugs.launchpad.net/openstack-org and tag it with "website". The framework for the www.openstack.org site is maintained at https://github.com/OpenStackweb/ until it's fully integrated in OpenStack Infra project, and patches are welcome. For content requests or bugs against the framework, log a bug or request at http://bugs.launchpad.net/openstack-org.

=== Getting Involved In Website Content ===

We welcome participation in creating great content on openstack.org to help evangelize the [[OpenStack]] projects and the community. Please email todd@openstack.org if you'd like to be involved in marketing [[OpenStack]] through our web properties. The [[OpenStack]] blog especially welcomes community contributions.

=== Posting To The Blog ===

If you would like something mentioned on the [[OpenStack]] blog or you'd like to submit a blog entry of your own, please reach out to the community manager communitymngr@openstack.org.

=== [[OpenStack]] Online Documentation ===

[[OpenStack]] documentation is available online at docs.openstack.org. This openstack subdomain is a Webhelp build of the OpenStack manuals project on [https://launchpad.net/openstack-manuals Launchpad]. To participate in [[OpenStack]] documentation, please reach out to Anne Gentle (anne@openstack.org).

Governance/InteropWG

2015-05-06T18:10:47Z

Smaffulli: added to working groups

This Committee was formed during the OpenStack Ice House Summit in Hong Kong by Board Resolution on 11/4.

''DefCore sets base requirements by defining 1) capabilities, 2) code and 3) must-pass tests for all OpenStack products. This definition uses community resources and involvement to drive interoperability by creating the minimum standards for products labeled "OpenStack."''

Our mission is to define "OpenStack Core" as chartered by the by-laws.

== Important Artifacts ==
# [https://github.com/openstack/defcore/blob/master/process/Lexicon.rst Terms Definition]
# [https://github.com/openstack/defcore/blob/master/process/CoreDefinition.rst 10 Core Principles] (board approved Hong Kong Summit)
# [https://github.com/openstack/defcore/blob/master/process/PlatformCap.rst Capability Levels: Component and Platform] (board approved October 2014)
# [https://github.com/openstack/defcore/blob/master/process/CoreCriteria.rst 12 Scoring Criteria] (board approved Atlanta Summit)
# [https://github.com/openstack/defcore/blob/master/process/DesignatedSections.rst 10 Designed Sections Principles] (board approved December 2014)
# [https://github.com/openstack/defcore/blob/master/process/GovernanceProcess.rst DefCore Governance:]
# [https://github.com/openstack/defcore/blob/master/process/2015A.rst DefCore Process]
# Capabilities & Sections
## [https://github.com/openstack/defcore/blob/master/2015.03.rst 2015.03] (review [https://github.com/openstack/defcore/blob/master/2015.03.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/2015.04.rst 2015.04] (review [https://github.com/openstack/defcore/blob/master/2015.04.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/2015.next.json 2015.next ]

== Objective / Scope ==

The DefCore charter is around how the OpenStack brand is applied for commercial uses. Initially, this focus is on "what is core" and sustaining that definition over time. The scope will likely expand since brand is an ongoing concern related to specialized marks and other use cases.

There are three ways in which the community uses the OpenStack brand including referring to projects.
# General community use of the mark
# Project-specific use associated with development activity
# DefCore-governed commercial use

While the top two of these uses are out of scope for DefCore, the committee has a need to participate in the discussion to ensure consistent and clear use.

== How to Engage? ==

* Join the [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee defcore-committee] list
* Join #defcore on Freenode IRC
* Follow the code at https://github.com/openstack/defcore
* Join our weekly [[Governance/DefCoreCommittee#Meetings|meetings]]

== Meetings ==
DefCore Scale Cycle Meetings (weekly on Wednesdays, 9:00AM Pacific Time, see etherpad links for join.me info):

* [https://etherpad.openstack.org/p/DefCoreScale.15 Scale.15 - May 6, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.14 Scale.14 - April 29, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.13 Scale.13 - April 22, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.12 Scale.12 - April 15, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.11 Scale.11- April 8, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.10 Scale.10 - April 1, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.9 Scale.9 - March 25, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.8 Scale.8 - March 18, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.7 Scale.7 - March 13, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.6 Scale.6 - February 25, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.5 Scale.5 - February 18, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.4 Scale.4 - February 11, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.3 Scale.3 - February 4, 2015]
* [https://etherpad.openstack.org/p/DefCoreScale.2 Scale.2 - January 23, 2015]

Capabilities Meetings (weekly on Wednesdays, 11:00AM Pacific Time, dialin: 1-855-600-7225, code 4625040):
* [https://etherpad.openstack.org/p/defcore-capabilities-may-06-2015 May 6, 2015]
* [https://etherpad.openstack.org/p/defcore-capabilities-apr-29-2015 April 29, 2015]
* [https://etherpad.openstack.org/p/defcore-capabilities-apr-22-2015 April 22, 2015]
* [https://etherpad.openstack.org/p/defcore-capabilities-apr-15-2015 April 15, 2015]
* [https://etherpad.openstack.org/p/defcore-capabilities-apr-08-2015 April 8, 2015]
* [https://etherpad.openstack.org/p/defcore-capabilities-apr-01-2015 April 1, 2015]
* [https://etherpad.openstack.org/p/defcore-capabilities-mar-25-2015 March 25, 2015]
* [https://etherpad.openstack.org/p/defcore-capabilities-mar-11-2015 March 11, 2015]
* [https://etherpad.openstack.org/p/defcore-capabilities-mar-04-2015 March 4, 2015]
* [https://etherpad.openstack.org/p/defcore-capabilities-feb-18-2015 February 18, 2015]
* [https://etherpad.openstack.org/p/defcore-capabilities-feb-04-2015 February 4, 2015]
* [https://etherpad.openstack.org/p/defcore-capabilities-jan-28-2015 January 28, 2015]

== Process Cycles ==

Defining OpenStack Core is a long term process and we are doing the work in progressive cycles. For reference, we have named the cycles. This helps describe concrete deliverables for a cycle while allowing discussion of the broader long term issues. For example, we may say that "item X is important to DefCore but out of scope for Elephant." We have found that this approach to breaking down the problem is necessary to maintain community consensus because we are taking smaller bites of the larger challenge (aka eating the elephant).

See [https://github.com/openstack/defcore/blob/master/process/ProcessCycles.rst Process Cycles]

The current cycle is named the '''''Scale Cycle'''''.

== Current Committee Participants ==
Current Participants
* [http://www.openstack.org/community/members/profile/221 Rob Hirschfeld] (board member, co-chair)
* [http://www.openstack.org/community/members/profile/3106 Egle Sigler] (board member, co-chair)
* [http://www.openstack.org/community/members/profile/5869 Will Auld]
* [http://www.openstack.org/community/members/profile/13748 Carol Barrett]
* Vince Brunssen
* [http://www.openstack.org/community/members/profile/272 Russell Bryant]
* [http://www.openstack.org/community/members/profile/9572 Kevin Carter]
* Catherine Diep
* [http://www.openstack.org/community/members/profile/10273 Rocky Grober]
* [http://www.openstack.org/community/members/profile/10331 Chris Hoge]
* [http://www.openstack.org/community/members/profile/31354 Chris Lee]
* [http://www.openstack.org/community/members/profile/76 Van Lindberg] (board member)
* [http://www.openstack.org/community/members/profile/18704 Jim Meyer]
* [http://www.openstack.org/community/members/profile/1657 Adrian Otto]
* [http://www.openstack.org/community/members/profile/164 Sean Roberts]
* [http://www.openstack.org/community/members/profile/12876 Shamail Tahir]
* [https://www.openstack.org/community/members/profile/54 Mark T. Voelker]

[[category: defcore]]
[[Category: Working_Groups]]

OpenStack Upstream Training/Admin

2015-05-06T17:19:14Z

Smaffulli: updated with latest content of 'get ready email'

= Administration tasks for Upstream Training =

== Engagement ==

Used to create the event. The signup process requires applicants to specify their intentions, which areas to focus on.

Engage with applicants at regular intervals to make sure they are fully engaged and understand what they sign up for. 4 weeks before the event send them a notification to start engaging with teachers and mentors. 2 weeks before the event, remind them to pick a bug and setup their development environment.

Volunteer staff ask to be added to the [https://trello.com/b/iuJab0VH Trello board]. From the board, staff picks one card from the '''Applicants''' list, move the card to next list '''Mentor picked''' and send the applicant the engagement email (suggested text below).

Mentors should help the applicants select a simple bug to fix or another very simple work item, based on the interests and objectives of the applicant. The work item will be executed '''after''' the training in classroom.

=== Email messages ===

===== Welcome email, at signup =====
<pre>
Subject: Welcome to OpenStack Upstream Training

Nice to e-meet you and thanks for subscribing to the OpenStack Upstream Training. The objective of the two day session is to improve your understanding of OpenStack's contribution process and help you become more effective at merging code in OpenStack. The training is designed to be practical, it begins *now* before and will continue after, with mentoring sessions until your first contribution is completed.

If you haven't done it already, get familiar with OpenStack Upstream Training [OpenStack_Upstream_Training/Info#Objectives objectives], [OpenStack_Upstream_Training/Info#Course_Outline schedule] and [OpenStack_Upstream_Training/Info#Prerequisites pre-requisites].

Please start engaging with your mentor by replying to this message, explaining what you would like to work on and what your personal objectives are for this class. The mentor will help you select a low hanging fruit bug to fix and send you further instructions.

Don't hesitate to ask if you have questions regarding the training program.
</pre>

===== Engagement email, sent by mentor =====

<pre>
TL;DR: Pick three bugs from the list below and setup your laptop for the training.

The OpenStack Upstream Training is just a few days away, in Vancouver Convention Centre. We will meet on Saturday, May 16, 2015 at 9:30am and will continue on Sunday May 17, until 5pm.

To make the best out of the training, please select three bugs from the list OpenStack's known bugs that are simple to fix (Low Hanging Fruit): https://goo.gl/HX9Nxa and assign to you at least one that you feel comfortable working on, based on your interests and experience.

The goal of the training will be to get your work accepted upstream. It is best to chose a contribution that is easy so you can focus on learning the contribution process, tools and social rules of OpenStack community. Remember that Upstream Training will continue with mentoring sessions online after the class until the work you choose is complete.

If you have doubts on how to pick and assign a bug to you, please reply to this email and we'll help you out.

Setup your laptop to be able to follow the training. You will need:

* A laptop capable of connecting to wireless networks and at least 8GB RAM for next point
* A virtual machine running Ubuntu (or any other operating system you feel confortable with when working on OpenStack)

It is worth double checking that this works well in advance. If you feel adventorous you can start reading how to setup the OpenStack development environment (devstack) in a virtual machine http://docs.openstack.org/developer/devstack/guides/single-vm.html

Cheers
The OpenStack Upstream Training Staff
https://wiki.openstack.org/wiki/OpenStack_Upstream_Training

note: If your laptop is not powerful enough to run devstack we'll try to provide openstack-based virtual machines in public clouds.

</pre>

A link to all [https://bugs.launchpad.net/openstack/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=low-hanging-fruit&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on Low Hanging Fruit bugs]

== Lego management ==

The Lego need to be shipped weeks ahead of time to volunteers near the convention center. They will help assemble the buildings and bring them to the facility the morning when the training starts, or the evening before, as soon as the rooms are ready.

After the class, the Lego can be displayed in the expo floor.

After the show, the Lego need to be packaged and shipped back to FNTech facilities.

=== Lego material ===

* estimate per student 750g of assorted bulk Lego bricks for the creative session
* at least two buildings per classroom of the Lego City series

Currently the Foundation owns London Bridge, Sidney Opera House, Pet Store, Cinema, French Restaurant.

Contributors/Corporate

2015-05-04T18:58:44Z

Smaffulli: dot hill

Internship ideas

2015-04-28T19:08:27Z

Smaffulli: /* Coding */

To submit new ideas please consider creating a new page and use the [[Template:InternshipIdea]] (instructions are provided on that page) and you can see how a [[Test idea|sample idea page]] would look like. The pages created with such template are listed on [[:Category:Internship_idea]].

= List of Ideas for Internships =

The OpenStack Foundation has multiple sources for internships, from [[Outreachy]] to [[:Category:GSoC|Google Summer of Code]] and other opportunities. This page collects the ideas for candidate interns to work on.

Applicants may not have ever worked on FLOSS before and have different levels of competence. Since we have different programs, add here ideas that can be completed by inexperienced contributors, developers or other fields (marketing, communication, graphic design, and anything that may be useful for OpenStack and to include new people in this community).

== Documentation ==

Mentors:
** loquacities on IRC / openstack at lanabrindley dot com
** asettle on IRC/ alexandra dot settle at rackspace dot com

* Assist with the RST conversion of the Admin User Guide

* Help with the Networking Guide: either with content, copyediting, or the RST conversion.

* General bug work (find something interesting and work on it). This would look great on her resume as it's a solid visible contribution, but would also hopefully pay down some of our technical debt.

* Choose a book/section of interest, and research and update that section. A good candidate here would be the API guides.

== Community ==

''To be announced''

Mentors:
** hodepodge on IRC / chris at openstack org
** EmilienM on IRC / emilien at redhat com
** reed in IRC / stefano at openstack org

== Coding ==

See also [[:Category:Internship_idea|Ideas pages]].

=== Neutron - metering agent add port statistics ===

Description:

In Neutron the metering agent [https://wiki.openstack.org/wiki/Neutron/Metering/Bandwidth] collects statistics regarding bandwidth usage. Right now it only measure the bandwidth used by routers. The idea is to extend it and provide statistics also for ports. In the first implementation only openvswitch will be supported, since we will use openvswitch tools to get the port statistics.
The first step will be getting familiar with the metering agent and with Neutron in general. Then you will approach openvswitch tools and think about how to use them for this project. After that you can reach out to the community to collect and discuss ideas. Neutron folks are pretty active on #openstack-neutron channel most of the time and would be willing to share their opinions on this or any other project. You'll submit your code upstream and address the comments you get till your patch gets merged.

Related blueprint: https://blueprints.launchpad.net/neutron/+spec/port-statistics

Expected results: Patchsets submitted for review, reviewed by community members.

Knowledge prerequisites: programming knowledge

Nice-to-have knowledge: Python, Openvswitch

Mentors: [[User:Rossella|Rossella Sblendido]]

=== Redis jobboards ===

The spec @ https://review.openstack.org/#/c/105298/ basically explains all of this (the why, what and where).

{| class="wikitable"
|-
| Difficulty ||
|-
| Topics || [[TaskFlow|TaskFlow]], Distributed Systems
|-
| Required skills || Python
|-
| Extra skills || Distributed Systems
|-
| Mentor || Joshua Harlow (harlowja)
|}

=== Policy | Policy enforcement in OpenStack: Nova Scheduling and Policy integration ===

{| class="wikitable"
|-
| Difficulty ||
|-
| Topics || [[GroupBasedPolicy|Policy]], [[Nova|Nova]]
|-
| Required skills ||
|-
| Extra skills ||
|-
| Mentor ||
|}

=== Test results dashboard ===

Tasks:
* Create an infra hosted dashboard view of testing results (both check/gate and periodic)

{| class="wikitable"
|-
| Difficulty ||
|-
| Topics ||
|-
| Required skills ||
|-
| Extra skills ||
|-
| Mentor ||
|}

=== Policy | Policy-based intent-driven OpenStack Cloud Infrastructure ===

See an example case study here: [http://www.openstack.org/vote-vancouver/presentation/meta-data-driven-cloud-running-openstack-scale-using-a-policy-framework-intel Meta-data Driven Cloud - Running OpenStack @ Scale Using a Policy Framework]

Tasks:
* Extension of intent-based policy framework to Compute and Storage
* Policy-based service composition integration with OpenDaylight

{| class="wikitable"
|-
| Difficulty || Moderate to Advanced
|-
| Topics || Functional and scenario testing framework
|-
| Required skills || OpenStack, Python
|-
| Extra skills ||
|-
| Mentor || Sumit Naiksatam, Magesh GV
|}

=== Rich Network Services in a Federated OpenStack Public Cloud ===

L4-7 Services' integration, NFV, service function chaining, OpenDaylight

{| class="wikitable"
|-
| Difficulty || Moderate to Advanced
|-
| Topics || Functional and scenario testing framework
|-
| Required skills || OpenStack, Python
|-
| Extra skills ||
|-
| Mentor || Sumit Naiksatam, Magesh GV
|}

=== Understand OpenStack Operations via Insights from Logs and Metrics: A Data Science Perspective ===

Tasks:
* How do we make sense out of logs?
* How do we set up alarms based on specific events (identify events)
* Anomaly detection from Logs

{| class="wikitable"
|-
| Difficulty ||
|-
| Topics ||
|-
| Required skills || Experience/interest in algorithms
|-
| Extra skills ||
|-
| Mentor ||
|}

=== Keystone | Dynamic Policy ===

The general idea is described at the blog post [http://adam.younglogic.com/2014/11/dynamic-policy-in-keystone/ Dynamic Policy in Keystone], by Adam Young.

{| class="wikitable"
|-
| Difficulty || Medium
|-
| Topics || [[Keystone|Keystone]]
|-
| Required skills || Python
|-
| Extra skills ||
|-
| Mentor || David Stanek (dstanek), Samuel de Medeiros Queiroz (samueldmq)
|}

=== Keystone | Tokenless Operations ===

The general idea is described at the blog post [http://adam.younglogic.com/2014/10/who-can-sign-for-what/ Who can sign for what?], by Adam Young.
In few words, the fact of the signature on a document be valid does not mean that the signer was authorized to sign it.

The proposed challenge is to create, based on existing mechanisms, an extension to Keystone client able to check if the the signer of a token was effectively authorized to sign tokens.

Tasks:
* Extract signer data out of the certificates;
* Fetch the complete list of certificate from Keystone using the OS-SIMPLE-CERT extension;
* Match the signer to the cert to validate the signature and extract the domain data for the token;
* Fetch the mapping info from the Federation extension;
* Use the mapping info to convert from the signing cert to a keystone user and groups;
* Fetch the effective roles from Keystone for the user/groups for that domain;
* Fetch policy from Keystone;
* Execute the policy check to validate that the signer could sign for the data.

{| class="wikitable"
|-
| Difficulty || Medium
|-
| Topics || [[Keystone|Keystone]]
|-
| Required skills || Python
|-
| Extra skills ||
|-
| Mentor || David Stanek (dstanek), Samuel de Medeiros Queiroz (samueldmq)
|}

=== Ceilometer ===

Mentor: [[DinaBelova|Dina Belova]]

Ceilometer team is currently working on new Time-Series storage concept for metrics. For now Gnocchi (Telemetry Stackforge project where we're trying to implement this kind of effort) lacks of the backend support (only Swift in place, InfluxDB and OpenTSDB still in progress). There is some interest to use Ceph directly instead of it. So we need direct-to-ceph usage from
Gnocchi, possibly via the rados gateway REST API (as opposed to ceph-sitting-behind-swift-proxy as an alternative storage driver for Swift itself).

=== Zaqar: Split data/control planes ===

Mentor: [[User:flaper87|Flavio Percoco]]

Zaqar has 2 different logical "data-planes". One is used to control the state of the system and other administrative operations - pools, flavors, etc - and the other is used for the actual data going through Zaqar - queues, messages, etc. These 2 data planes currently share lots of things like config options, modules and more. The team has been willing to split these 2 logically different planes into isolated modules and configs.

This task will give the mentee great insights on Zaqar's architecture, logic and also more general information on how some messaging patterns are implemented in the system. This task is a great intro to Zaqar, to OpenStack and to messaging technologies with enough complexity to help the mentee grow.

* Expected Results: Both planes should be completely separate
* Required Knowedge: Python

=== Trove ===

Mentor: [[User:iccha-sethi|Iccha Sethi]]

Description: MySQL replication enhancements

Work on trove enhancements for mysql replication.

=== Glance - Swift ranged uploads ===

Note(nikhil_k): This is a really challenging project. It would need a lot of research and motivation from candidate to perform the tasks. The tasks would also need to be defined by the candidate themselves to have a good "concurrent" distributed system as a end-result.

Description: We currently retry the entire upload process if it fails. Need to add the ranged uploads logic from swift store to improve performance. Target repo - openstack/glance_store

Glance folks are pretty active on #openstack-glance channel most of the time and would be willing to share their opinions on this or any other project.
Please reach out on IRC to get a detailed information on this.

Related blueprint: TBA

Expected results: Patchsets submitted for review, reviewed by community members.

Knowledge prerequisites: programming knowledge

Nice-to-have knowledge: Python

Mentors: [[User:nikhil|Nikhil Komawar]]

=== Swift - storage server OPTIONS support and checker tool ===

Many times new deployers get mysterious errors after first setting up their Swift clusters. Most of the time, the errors are because the values in the ring are incorrect (e.g. a bad port number). We need a way to validate that the rings actually match the deployment.

http://tools.ietf.org/html/rfc7231#section-4.3.7 talks about the OPTIONS verb. Swift's proxy server already supports OPTIONS, but the storage nodes do not. The first task is to implement OPTIONS on the account, container, and object servers.

Once the "OPTIONS *" functionality is implemented, swift-recon can be updated to include a ring checker. This checker would look at the ring and validate that there is something running on the server endpoints listed in the ring. Furthermore it would be able to actually check that the endpoint, if it's a real endpoint, is the right kind of endpoint (e.g. actually check that it's an object server). swift-recon would then generate a report of any found issues in the cluster.

Expected results: patches written, submitted for review, and reviewed by the community

Knowledge prerequisites: Python programming knowledge

Nice-to-have knowledge: familiarity with HTTP protocols

Mentors: [[User:notmyname|John Dickinson]]

WIP Schedule: https://etherpad.openstack.org/p/iaR4TQZ7NP

=== Swift - Improving the security of Swift's internal network ===

Today all internal messages within a Swift cluster are unencrypted and unsigned. This means that all Swift deployments must be configured with a private, secure network for internal requests. This project is to add a cryptographic signature to all messages sent between Swift processes.

Blueprint: https://blueprints.launchpad.net/swift/+spec/secure-internal-network-requests

Expected results: patches written, submitted for review, and reviewed by the community

Knowledge prerequisites: good Python programming knowledge, Swift's architecture, familiarity with HTTP

Nice-to-have knowledge: familiarity with PKI

Mentors: [[User:notmyname|John Dickinson]]

WIP Schedule: https://etherpad.openstack.org/p/Wp3Hn7YY8p

=== Swift/Swift3 - Improve S3 compatibility layer ===

Improve the Swift3 middleware to get better S3 API coverage

https://github.com/stackforge/swift3

Mentors: [[User:notmyname|John Dickinson]]

=== Proposed by applicants ===

==== Keystone - Implementation of Attribute and Graph Based Access Control Model (AGBAC) for Openstack ====

Proposed by: Tahmina Ahmed - Tahmina

Description: The Core Openstack Access Control Module according to identity API V3 (user, token,project, domain, group, role association) [0] can be abstracted as a graph:
 

[[File:OSACFinal.jpg|Openstack Access Control According to Identity API V3 ]]
 

Attribute of different entities and the relationship between them and attribute of the relationship can be expressed through property graph [2] where entities are nodes and relationships are edges and both nodes and edges has attribute. Using entities and their attributes and relationship between entities and attribute of relationship to specify authorization policy will allow a system to have more finer grained access control model. For this representation, OpenStack entities (user, group, role, project, domain) are represented as nodes in the graph and the attributes and association between any two of them can be depicted as attributed edges. Given that a role is associated with a user and a project where the association is temporal, if we can say that the association is only active from 8am to 5pm this is something to say about the user- project- role association. We can express this as an attribute of the user- project and project - role association edge and use this for authorization to findout active roles.

This implementation plan is to make minimum impact on services outside keystone.So the plan is to like computing authorization path specification for a certain time when user requests for a token and and return a list of active roles. In that case this extension to the authorization model is transparent to all other openstack services like nova, glance, cynder etc.

Steps to Implement AGBAC in Openstack

1. Define API and Storage for Specifying Attributes of different entities
2. Define storage Assignment Attributes.
3. Define API to set the entity attributes
4. Define API to set the association attributes
5. A Policy specification storage that would specify path based policy to compute roles.
6. A Compute function that would compute the roles using entites, their attributes relationship between entities attribute of relationships and policy.

[0] Bo Tang and Ravi Sandhu, Extending Openstack Access Control With Domain Trust. In Proceedings 8th International Conference on Network and System Security (NSS 2014), Xi'an, China, October 15-17, 2014, 15 pages

[1] http://neo4j.com/

[2] Rodriguez, Marko A., and Peter Neubauer. "Constructions from dots and lines." Bulletin of the American Society for Information Science and Technology 36.6 (2010): 35-41.

== Design ==

=== Persona research and design for Horizon UI ===

Description:
There has been some initial work done in a few different areas around generating Personas for the Horizon UI. This task/project would allow someone to lead the effort to pull the research together, perhaps perform further end-user interviews or surveys, analyze data, form groups of personas, and put together an initial set of target Horizon personas that we can use during requirements gathering, design phases, and general discussion.

Related blueprint: https://blueprints.launchpad.net/openstack-ux/+spec/horizon-personas

Expected results: Initial set of Personas for people to use during requirements gathering, design phases, and general discussion of our target Horizon users.

Knowledge prerequisites: basic interviewing skills, willingness to talk with a lot of new people, readiness to listen and report back findings

Nice-to-have knowledge: User Experience Design basics

Mentors: [[User:julim|Ju Lim]]

=== Redesign for the Object Storage -> Containers section in Horizon ===

Description:

Currently, there is a section under the Object Storage panel that allows users (e.g. Consumers and/or Project Administrators) to Create, Delete, and Edit Containers. It would be great to do a little bit of research into identifying the use cases around these features and then proposing a redesign of these features based on the findings. This will include learning some basic Usability best practices and applying them to a design. The design would be done in wireframe format, so it could be done in any tool that allows for this. The design would be reviewed on the UX AskBot site, a new blueprint would need to be created as well. This would take a new designer through the process that currently exists for proposing an updated design to a current feature in Horizon.

Related blueprint: N/A (To be created by intern as part of process)

Expected results: Redesign of "Containers" section in Object Storage panel proposed and approved by Horizon community.

Knowledge prerequisites: basic sketching or wireframing skills

Nice-to-have knowledge: User Experience Design basics

Mentors: [[User:julim|Ju Lim]], [[User:lblanchard|Liz Blanchard]]

=== Horizon Concept Review and Usability Testing ===

Description: There has been very little work done around Horizon UI concept reviews and usability testing. This task/project would allow someone to lead the effort to put together a test plan, identify customers as test participants, conduct (contextual) inquiry / interview, survey users, analyze data to share results / findings with the community findings regarding how current production OpenStack users are using the software, their use cases, and whether the Horizon UI meets their needs. Along the way, you may identify areas of improvement, concepts that need further refinement, and new use cases or opportunities that have not yet been addressed.

Related blueprint: https://blueprints.launchpad.net/openstack-ux/+spec/ux-users-community-testing

Expected results: (1) Identify a community of users willing to participate in Horizon UI usability testing and participate in various OpenStack concept reviews. (2) Share usability test findings with the community that will be used for design and general Horizon discussions.

Knowledge prerequisites: usability testing skills, basic interviewing skills, willingness to talk with a lot of new people, readiness to listen and report back findings, ability to analyze data to find patterns.

Nice-to-have knowledge: User Experience Design and/or User Research basics

Mentors: [[User:julim|Ju Lim]], [[User:lblanchard|Liz Blanchard]]

[[Category: Internship]]

Running hound on Infra

2015-04-28T19:05:33Z

Smaffulli:

{{InternshipIdea|
TITLE=Implement livegrep service for Infra|
DESCRIPTION=Running a livegrep service to search for code across OpenStack git repositories |
DIFFICULTY=Low|
TOPICS=Infra|
SKILLS=Puppet, Ruby|
EXTRA_SKILLS=Go|
MENTORS=Elizabeth K. Joseph (pleia2), Jeremy Stanley (fungi), Jonathan Harker (jesusaurus)|
STATUS=Assigned to Taron(Emma) for Outreachy May 2015|
PROGRAM=Outreach May-Aug 2015
}}

Run livegrep in infra: https://review.openstack.org/#/c/96877/ https://review.openstack.org/#/c/129726/ (actually Monty had suggested to me to run Hound instead, as it is able to update the index for the git repos which livegrep doesnt': https://github.com/etsy/hound) but either way a grep service (yah - hound is like a 5 minute task - would be a great first task for someone) setting up hound is a 5 minute task, writing the parser to parse the yaml files so it knows which repos to index might take longer than 5 minutes

== Development notes ==

[[Category: OutreachyMay2015]]

Internship ideas

2015-04-28T18:58:36Z

Smaffulli: removed the ideas that have been moved to category: OutreachyMay2015

To submit new ideas please consider creating a new page and use the [[Template:InternshipIdea]] (instructions are provided on that page) and you can see how a [[Test idea|sample idea page]] would look like. The pages created with such template are listed on [[:Category:Internship_idea]].

= List of Ideas for Internships =

The OpenStack Foundation has multiple sources for internships, from [[Outreachy]] to [[:Category:GSoC|Google Summer of Code]] and other opportunities. This page collects the ideas for candidate interns to work on.

Applicants may not have ever worked on FLOSS before and have different levels of competence. Since we have different programs, add here ideas that can be completed by inexperienced contributors, developers or other fields (marketing, communication, graphic design, and anything that may be useful for OpenStack and to include new people in this community).

== Documentation ==

Mentors:
** loquacities on IRC / openstack at lanabrindley dot com
** asettle on IRC/ alexandra dot settle at rackspace dot com

* Assist with the RST conversion of the Admin User Guide

* Help with the Networking Guide: either with content, copyediting, or the RST conversion.

* General bug work (find something interesting and work on it). This would look great on her resume as it's a solid visible contribution, but would also hopefully pay down some of our technical debt.

* Choose a book/section of interest, and research and update that section. A good candidate here would be the API guides.

== Community ==

''To be announced''

Mentors:
** hodepodge on IRC / chris at openstack org
** EmilienM on IRC / emilien at redhat com
** reed in IRC / stefano at openstack org

== Coding ==

See also [Category:Internship_idea Ideas pages].

=== Neutron - metering agent add port statistics ===

Description:

In Neutron the metering agent [https://wiki.openstack.org/wiki/Neutron/Metering/Bandwidth] collects statistics regarding bandwidth usage. Right now it only measure the bandwidth used by routers. The idea is to extend it and provide statistics also for ports. In the first implementation only openvswitch will be supported, since we will use openvswitch tools to get the port statistics.
The first step will be getting familiar with the metering agent and with Neutron in general. Then you will approach openvswitch tools and think about how to use them for this project. After that you can reach out to the community to collect and discuss ideas. Neutron folks are pretty active on #openstack-neutron channel most of the time and would be willing to share their opinions on this or any other project. You'll submit your code upstream and address the comments you get till your patch gets merged.

Related blueprint: https://blueprints.launchpad.net/neutron/+spec/port-statistics

Expected results: Patchsets submitted for review, reviewed by community members.

Knowledge prerequisites: programming knowledge

Nice-to-have knowledge: Python, Openvswitch

Mentors: [[User:Rossella|Rossella Sblendido]]

=== Redis jobboards ===

The spec @ https://review.openstack.org/#/c/105298/ basically explains all of this (the why, what and where).

{| class="wikitable"
|-
| Difficulty ||
|-
| Topics || [[TaskFlow|TaskFlow]], Distributed Systems
|-
| Required skills || Python
|-
| Extra skills || Distributed Systems
|-
| Mentor || Joshua Harlow (harlowja)
|}

=== Policy | Policy enforcement in OpenStack: Nova Scheduling and Policy integration ===

{| class="wikitable"
|-
| Difficulty ||
|-
| Topics || [[GroupBasedPolicy|Policy]], [[Nova|Nova]]
|-
| Required skills ||
|-
| Extra skills ||
|-
| Mentor ||
|}

=== Test results dashboard ===

Tasks:
* Create an infra hosted dashboard view of testing results (both check/gate and periodic)

{| class="wikitable"
|-
| Difficulty ||
|-
| Topics ||
|-
| Required skills ||
|-
| Extra skills ||
|-
| Mentor ||
|}

=== Policy | Policy-based intent-driven OpenStack Cloud Infrastructure ===

See an example case study here: [http://www.openstack.org/vote-vancouver/presentation/meta-data-driven-cloud-running-openstack-scale-using-a-policy-framework-intel Meta-data Driven Cloud - Running OpenStack @ Scale Using a Policy Framework]

Tasks:
* Extension of intent-based policy framework to Compute and Storage
* Policy-based service composition integration with OpenDaylight

{| class="wikitable"
|-
| Difficulty || Moderate to Advanced
|-
| Topics || Functional and scenario testing framework
|-
| Required skills || OpenStack, Python
|-
| Extra skills ||
|-
| Mentor || Sumit Naiksatam, Magesh GV
|}

=== Rich Network Services in a Federated OpenStack Public Cloud ===

L4-7 Services' integration, NFV, service function chaining, OpenDaylight

{| class="wikitable"
|-
| Difficulty || Moderate to Advanced
|-
| Topics || Functional and scenario testing framework
|-
| Required skills || OpenStack, Python
|-
| Extra skills ||
|-
| Mentor || Sumit Naiksatam, Magesh GV
|}

=== Understand OpenStack Operations via Insights from Logs and Metrics: A Data Science Perspective ===

Tasks:
* How do we make sense out of logs?
* How do we set up alarms based on specific events (identify events)
* Anomaly detection from Logs

{| class="wikitable"
|-
| Difficulty ||
|-
| Topics ||
|-
| Required skills || Experience/interest in algorithms
|-
| Extra skills ||
|-
| Mentor ||
|}

=== Keystone | Dynamic Policy ===

The general idea is described at the blog post [http://adam.younglogic.com/2014/11/dynamic-policy-in-keystone/ Dynamic Policy in Keystone], by Adam Young.

{| class="wikitable"
|-
| Difficulty || Medium
|-
| Topics || [[Keystone|Keystone]]
|-
| Required skills || Python
|-
| Extra skills ||
|-
| Mentor || David Stanek (dstanek), Samuel de Medeiros Queiroz (samueldmq)
|}

=== Keystone | Tokenless Operations ===

The general idea is described at the blog post [http://adam.younglogic.com/2014/10/who-can-sign-for-what/ Who can sign for what?], by Adam Young.
In few words, the fact of the signature on a document be valid does not mean that the signer was authorized to sign it.

The proposed challenge is to create, based on existing mechanisms, an extension to Keystone client able to check if the the signer of a token was effectively authorized to sign tokens.

Tasks:
* Extract signer data out of the certificates;
* Fetch the complete list of certificate from Keystone using the OS-SIMPLE-CERT extension;
* Match the signer to the cert to validate the signature and extract the domain data for the token;
* Fetch the mapping info from the Federation extension;
* Use the mapping info to convert from the signing cert to a keystone user and groups;
* Fetch the effective roles from Keystone for the user/groups for that domain;
* Fetch policy from Keystone;
* Execute the policy check to validate that the signer could sign for the data.

{| class="wikitable"
|-
| Difficulty || Medium
|-
| Topics || [[Keystone|Keystone]]
|-
| Required skills || Python
|-
| Extra skills ||
|-
| Mentor || David Stanek (dstanek), Samuel de Medeiros Queiroz (samueldmq)
|}

=== Ceilometer ===

Mentor: [[DinaBelova|Dina Belova]]

Ceilometer team is currently working on new Time-Series storage concept for metrics. For now Gnocchi (Telemetry Stackforge project where we're trying to implement this kind of effort) lacks of the backend support (only Swift in place, InfluxDB and OpenTSDB still in progress). There is some interest to use Ceph directly instead of it. So we need direct-to-ceph usage from
Gnocchi, possibly via the rados gateway REST API (as opposed to ceph-sitting-behind-swift-proxy as an alternative storage driver for Swift itself).

=== Zaqar: Split data/control planes ===

Mentor: [[User:flaper87|Flavio Percoco]]

Zaqar has 2 different logical "data-planes". One is used to control the state of the system and other administrative operations - pools, flavors, etc - and the other is used for the actual data going through Zaqar - queues, messages, etc. These 2 data planes currently share lots of things like config options, modules and more. The team has been willing to split these 2 logically different planes into isolated modules and configs.

This task will give the mentee great insights on Zaqar's architecture, logic and also more general information on how some messaging patterns are implemented in the system. This task is a great intro to Zaqar, to OpenStack and to messaging technologies with enough complexity to help the mentee grow.

* Expected Results: Both planes should be completely separate
* Required Knowedge: Python

=== Trove ===

Mentor: [[User:iccha-sethi|Iccha Sethi]]

Description: MySQL replication enhancements

Work on trove enhancements for mysql replication.

=== Glance - Swift ranged uploads ===

Note(nikhil_k): This is a really challenging project. It would need a lot of research and motivation from candidate to perform the tasks. The tasks would also need to be defined by the candidate themselves to have a good "concurrent" distributed system as a end-result.

Description: We currently retry the entire upload process if it fails. Need to add the ranged uploads logic from swift store to improve performance. Target repo - openstack/glance_store

Glance folks are pretty active on #openstack-glance channel most of the time and would be willing to share their opinions on this or any other project.
Please reach out on IRC to get a detailed information on this.

Related blueprint: TBA

Expected results: Patchsets submitted for review, reviewed by community members.

Knowledge prerequisites: programming knowledge

Nice-to-have knowledge: Python

Mentors: [[User:nikhil|Nikhil Komawar]]

=== Swift - storage server OPTIONS support and checker tool ===

Many times new deployers get mysterious errors after first setting up their Swift clusters. Most of the time, the errors are because the values in the ring are incorrect (e.g. a bad port number). We need a way to validate that the rings actually match the deployment.

http://tools.ietf.org/html/rfc7231#section-4.3.7 talks about the OPTIONS verb. Swift's proxy server already supports OPTIONS, but the storage nodes do not. The first task is to implement OPTIONS on the account, container, and object servers.

Once the "OPTIONS *" functionality is implemented, swift-recon can be updated to include a ring checker. This checker would look at the ring and validate that there is something running on the server endpoints listed in the ring. Furthermore it would be able to actually check that the endpoint, if it's a real endpoint, is the right kind of endpoint (e.g. actually check that it's an object server). swift-recon would then generate a report of any found issues in the cluster.

Expected results: patches written, submitted for review, and reviewed by the community

Knowledge prerequisites: Python programming knowledge

Nice-to-have knowledge: familiarity with HTTP protocols

Mentors: [[User:notmyname|John Dickinson]]

WIP Schedule: https://etherpad.openstack.org/p/iaR4TQZ7NP

=== Swift - Improving the security of Swift's internal network ===

Today all internal messages within a Swift cluster are unencrypted and unsigned. This means that all Swift deployments must be configured with a private, secure network for internal requests. This project is to add a cryptographic signature to all messages sent between Swift processes.

Blueprint: https://blueprints.launchpad.net/swift/+spec/secure-internal-network-requests

Expected results: patches written, submitted for review, and reviewed by the community

Knowledge prerequisites: good Python programming knowledge, Swift's architecture, familiarity with HTTP

Nice-to-have knowledge: familiarity with PKI

Mentors: [[User:notmyname|John Dickinson]]

WIP Schedule: https://etherpad.openstack.org/p/Wp3Hn7YY8p

=== Swift/Swift3 - Improve S3 compatibility layer ===

Improve the Swift3 middleware to get better S3 API coverage

https://github.com/stackforge/swift3

Mentors: [[User:notmyname|John Dickinson]]

=== Proposed by applicants ===

==== Keystone - Implementation of Attribute and Graph Based Access Control Model (AGBAC) for Openstack ====

Proposed by: Tahmina Ahmed - Tahmina

Description: The Core Openstack Access Control Module according to identity API V3 (user, token,project, domain, group, role association) [0] can be abstracted as a graph:
 

[[File:OSACFinal.jpg|Openstack Access Control According to Identity API V3 ]]
 

Attribute of different entities and the relationship between them and attribute of the relationship can be expressed through property graph [2] where entities are nodes and relationships are edges and both nodes and edges has attribute. Using entities and their attributes and relationship between entities and attribute of relationship to specify authorization policy will allow a system to have more finer grained access control model. For this representation, OpenStack entities (user, group, role, project, domain) are represented as nodes in the graph and the attributes and association between any two of them can be depicted as attributed edges. Given that a role is associated with a user and a project where the association is temporal, if we can say that the association is only active from 8am to 5pm this is something to say about the user- project- role association. We can express this as an attribute of the user- project and project - role association edge and use this for authorization to findout active roles.

This implementation plan is to make minimum impact on services outside keystone.So the plan is to like computing authorization path specification for a certain time when user requests for a token and and return a list of active roles. In that case this extension to the authorization model is transparent to all other openstack services like nova, glance, cynder etc.

Steps to Implement AGBAC in Openstack

1. Define API and Storage for Specifying Attributes of different entities
2. Define storage Assignment Attributes.
3. Define API to set the entity attributes
4. Define API to set the association attributes
5. A Policy specification storage that would specify path based policy to compute roles.
6. A Compute function that would compute the roles using entites, their attributes relationship between entities attribute of relationships and policy.

[0] Bo Tang and Ravi Sandhu, Extending Openstack Access Control With Domain Trust. In Proceedings 8th International Conference on Network and System Security (NSS 2014), Xi'an, China, October 15-17, 2014, 15 pages

[1] http://neo4j.com/

[2] Rodriguez, Marko A., and Peter Neubauer. "Constructions from dots and lines." Bulletin of the American Society for Information Science and Technology 36.6 (2010): 35-41.

== Design ==

=== Persona research and design for Horizon UI ===

Description:
There has been some initial work done in a few different areas around generating Personas for the Horizon UI. This task/project would allow someone to lead the effort to pull the research together, perhaps perform further end-user interviews or surveys, analyze data, form groups of personas, and put together an initial set of target Horizon personas that we can use during requirements gathering, design phases, and general discussion.

Related blueprint: https://blueprints.launchpad.net/openstack-ux/+spec/horizon-personas

Expected results: Initial set of Personas for people to use during requirements gathering, design phases, and general discussion of our target Horizon users.

Knowledge prerequisites: basic interviewing skills, willingness to talk with a lot of new people, readiness to listen and report back findings

Nice-to-have knowledge: User Experience Design basics

Mentors: [[User:julim|Ju Lim]]

=== Redesign for the Object Storage -> Containers section in Horizon ===

Description:

Currently, there is a section under the Object Storage panel that allows users (e.g. Consumers and/or Project Administrators) to Create, Delete, and Edit Containers. It would be great to do a little bit of research into identifying the use cases around these features and then proposing a redesign of these features based on the findings. This will include learning some basic Usability best practices and applying them to a design. The design would be done in wireframe format, so it could be done in any tool that allows for this. The design would be reviewed on the UX AskBot site, a new blueprint would need to be created as well. This would take a new designer through the process that currently exists for proposing an updated design to a current feature in Horizon.

Related blueprint: N/A (To be created by intern as part of process)

Expected results: Redesign of "Containers" section in Object Storage panel proposed and approved by Horizon community.

Knowledge prerequisites: basic sketching or wireframing skills

Nice-to-have knowledge: User Experience Design basics

Mentors: [[User:julim|Ju Lim]], [[User:lblanchard|Liz Blanchard]]

=== Horizon Concept Review and Usability Testing ===

Description: There has been very little work done around Horizon UI concept reviews and usability testing. This task/project would allow someone to lead the effort to put together a test plan, identify customers as test participants, conduct (contextual) inquiry / interview, survey users, analyze data to share results / findings with the community findings regarding how current production OpenStack users are using the software, their use cases, and whether the Horizon UI meets their needs. Along the way, you may identify areas of improvement, concepts that need further refinement, and new use cases or opportunities that have not yet been addressed.

Related blueprint: https://blueprints.launchpad.net/openstack-ux/+spec/ux-users-community-testing

Expected results: (1) Identify a community of users willing to participate in Horizon UI usability testing and participate in various OpenStack concept reviews. (2) Share usability test findings with the community that will be used for design and general Horizon discussions.

Knowledge prerequisites: usability testing skills, basic interviewing skills, willingness to talk with a lot of new people, readiness to listen and report back findings, ability to analyze data to find patterns.

Nice-to-have knowledge: User Experience Design and/or User Research basics

Mentors: [[User:julim|Ju Lim]], [[User:lblanchard|Liz Blanchard]]

[[Category: Internship]]

Glance tasks scrubber

2015-04-28T18:53:39Z

Smaffulli:

{{InternshipIdea|
TITLE= Implement Tasks scrubber for Glance|
DESCRIPTION=Glance Tasks are currently never deleted. This project would involve writing a scrubber logic for soft-deleting tasks as a part of Glance codebase |
DIFFICULTY=High, Medium, Low (judge if the idea can be accomplished by a totally new developer or someone already skilled in OpenStack or distributed systems)|
TOPICS=Comma separated list of topics, like the OpenStack projects involved|
SKILLS=Python|
EXTRA_SKILLS=|
MENTORS= [[User:nikhil|Nikhil Komawar]] |
STATUS=Assigned to Geetika for Outreachy May 2015|
PROGRAM=Outreach May-Aug 2015
}}

Glance folks are pretty active on #openstack-glance channel most of the time and would be willing to share their opinions on this or any other project.
Please reach out on [[IRC]] to get a detailed information on this.

[https://blueprints.launchpad.net/glance/+spec/async-glance-workers Initial blueprint]. A new BP would be needed to get this implemented. It would also be a responsibility of the candidate.

Expected results: Patchsets submitted for review, reviewed by community members.

== Development notes ==

[[category: OutreachyMay2015]]

Glance tasks scrubber

2015-04-28T18:52:49Z

Smaffulli: Created page with "{{InternshipIdea| TITLE=Glance Tasks are currently never deleted. This project would involve writing a scrubber logic for soft-deleting tasks as a part of Glance codebase| D..."

{{InternshipIdea|
TITLE=Glance Tasks are currently never deleted. This project would involve writing a scrubber logic for soft-deleting tasks as a part of Glance codebase|
DESCRIPTION=A brief description of this idea, one line would be enough |
DIFFICULTY=High, Medium, Low (judge if the idea can be accomplished by a totally new developer or someone already skilled in OpenStack or distributed systems)|
TOPICS=Comma separated list of topics, like the OpenStack projects involved|
SKILLS=Python|
EXTRA_SKILLS=|
MENTORS= [[User:nikhil|Nikhil Komawar]] |
STATUS=Assigned to Geetika for Outreachy May 2015|
PROGRAM=Outreach May-Aug 2015
}}

Glance folks are pretty active on #openstack-glance channel most of the time and would be willing to share their opinions on this or any other project.
Please reach out on [[IRC]] to get a detailed information on this.

[https://blueprints.launchpad.net/glance/+spec/async-glance-workers Initial blueprint]. A new BP would be needed to get this implemented. It would also be a responsibility of the candidate.

Expected results: Patchsets submitted for review, reviewed by community members.

== Development notes ==

[[category: OutreachyMay2015]]

Template:InternshipIdea

2015-04-28T18:49:22Z

Smaffulli: /* Usage */

<noinclude>
== Usage ==

Use this template to create ideas for internships. To use this template create a new page, give it as title the name of your idea and insert the code below, substituting where appropriate.

<pre>
{{InternshipIdea|
TITLE=My Awesome Internship Idea|
DESCRIPTION=A brief description of this idea, one line would be enough |
DIFFICULTY=High, Medium, Low (judge if the idea can be accomplished by a totally new developer or someone already skilled in OpenStack or distributed systems)|
TOPICS=Comma separated list of topics, like the OpenStack projects involved|
SKILLS=List of required programming skills, like Python, Java, AngularJS|
EXTRA_SKILLS=State which other skills are needed, like networking or master special tools|
MENTORS=Add the details to contact the mentor(s) for this idea|
STATUS=Add information about the program, for example: Assigned to $intern for Outreachy May 2015 or Looking for candidates.|
PROGRAM=Outreach May-Aug 2015 or GSoC2016
}}

</pre>

The snippet above will be rendered in the new page as below, more or less.

</noinclude>

= {{{TITLE|Title of the idea}}} =

{{{DESCRIPTION|A brief description of this idea, one line would be enough}}}

{| class="wikitable"
|-
| Difficulty || {{{DIFFICULTY|High, Medium, Low}}}
|-
| Topics || {{{TOPICS|Comma separated list of topics}}}
|-
| Required skills || {{{SKILLS|List of required programming skills}}}
|-
| Extra skills || {{{EXTRA|State which other skills are needed}}}
|-
| Mentor || {{{MENTORS|Details about the mentor(s)}}}
|-
| Status || {{{STATUS|Add information about the program, for example: Assigned to $intern or Looking for candidates.}}}
|-
| Program || {{{PROGRAM|Name of the internship program.}}}
|}

[[Category: internship_idea]]

Running hound on Infra

2015-04-28T18:48:27Z

Smaffulli:

Running hound on Infra

2015-04-28T18:47:36Z

Smaffulli: placeholder

Template:InternshipIdea

2015-04-28T18:44:00Z

Smaffulli: /* Usage */

<noinclude>
== Usage ==

Use this template to create ideas for internships. To use this template create a new page, give it as title the name of your idea and insert the code below, substituting where appropriate.

<pre>
{{InternshipIdea|
TITLE=My Awesome Internship Idea|
DESCRIPTION=A brief description of this idea, one line would be enough |
DIFFICULTY=High, Medium, Low (judge if the idea can be accomplished by a totally new developer or someone already skilled in OpenStack or distributed systems)|
TOPICS=Comma separated list of topics, like the OpenStack projects involved|
SKILLS=List of required programming skills, like Python, Java, AngularJS|
EXTRA_SKILLS=State which other skills are needed, like networking or master special tools|
MENTORS=Add the details to contact the mentor(s) for this idea|
STATUS=Add information about the program, for example: Assigned to $intern for Outreachy May 2015 or Looking for candidates.||
PROGRAM=Outreach May-Aug 2015 or GSoC2016
}}

</pre>

The snippet above will be rendered in the new page as below, more or less.

</noinclude>

= {{{TITLE|Title of the idea}}} =

{{{DESCRIPTION|A brief description of this idea, one line would be enough}}}

{| class="wikitable"
|-
| Difficulty || {{{DIFFICULTY|High, Medium, Low}}}
|-
| Topics || {{{TOPICS|Comma separated list of topics}}}
|-
| Required skills || {{{SKILLS|List of required programming skills}}}
|-
| Extra skills || {{{EXTRA|State which other skills are needed}}}
|-
| Mentor || {{{MENTORS|Details about the mentor(s)}}}
|-
| Status || {{{STATUS|Add information about the program, for example: Assigned to $intern or Looking for candidates.}}}
|-
| Program || {{{PROGRAM|Name of the internship program.}}}
|}

[[Category: internship_idea]]

User:Smaffulli

2015-04-28T18:42:00Z

Smaffulli:

insert the test idea page?

<translate>


Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer consequat sem eu mauris lobortis pretium. Vivamus posuere ut dui eget sodales. Donec urna ligula, tempus non aliquet quis, venenatis eu magna. Quisque quis rutrum augue. Sed egestas enim commodo tempus congue. Morbi sed imperdiet nisl, ac vestibulum lorem. Proin vel nunc purus. Praesent vulputate neque lacus, sit amet consequat purus sollicitudin in. Ut iaculis tortor vitae vestibulum porttitor. Nullam est lorem, congue pellentesque vulputate nec, blandit in sapien.


Proin sed molestie dui, eget ornare risus. Nunc ut dolor imperdiet, molestie augue non, volutpat est. Mauris convallis eget dolor et sagittis. Aenean suscipit porta libero quis gravida. Donec aliquam est id mauris consectetur hendrerit. Pellentesque mollis consectetur ligula, at pretium sapien dapibus in. Quisque quis porta ipsum.


Vestibulum a facilisis nisl. Vestibulum non venenatis nisl. Aenean laoreet ligula sit amet sapien semper, nec tempus nunc consequat. Donec et mattis nisi. Integer bibendum tristique imperdiet. Aliquam augue erat, convallis vel sapien ac, consectetur porta velit. Morbi mollis interdum arcu, eu ultricies ante interdum non. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae;


Etiam ac aliquam ligula, sit amet consequat nisl. Aliquam non orci nibh. Fusce vulputate, diam lobortis faucibus convallis, nisi dolor posuere justo, aliquet fermentum dolor arcu ut massa. Integer aliquet aliquet nunc, sed posuere tortor tincidunt eu. Nunc a erat ut nisl aliquam blandit. Duis at rhoncus urna. Aliquam a dapibus nulla. Phasellus consectetur urna accumsan consectetur hendrerit. Vivamus id purus vel mi faucibus rutrum. Nullam laoreet placerat lorem sit amet ultricies. In luctus eros sit amet interdum fringilla. Vivamus sodales elit aliquam, posuere metus vitae, consequat elit. Fusce congue lectus vel ultrices cursus. Nullam molestie, sapien ac laoreet mattis, nisi mi gravida diam, et interdum orci tellus in tortor.


Integer non posuere orci. Donec adipiscing congue suscipit. Praesent egestas sagittis tortor, sit amet porta lorem porttitor sed. Vivamus varius posuere scelerisque. Suspendisse viverra lacus volutpat orci tincidunt mollis. In vestibulum magna nibh. Morbi imperdiet mi mauris. In vulputate iaculis laoreet. Donec vel nisl ac leo ullamcorper tempor id sed orci. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos.

</translate>

Zaqar panel for Horizon

2015-04-28T18:40:39Z

Smaffulli: Created page with " {{InternshipIdea| TITLE=Create a panel on Horizon for Zaqar| DESCRIPTION=Right now the only way to use Zaqar is through the API. The creation of a panel for Horizon would m..."

{{InternshipIdea|
TITLE=Create a panel on Horizon for Zaqar|
DESCRIPTION=Right now the only way to use Zaqar is through the API. The creation of a panel for Horizon would make Zaqar more user friendly. This task would require to learn and understand how panels are created in Horizon, to select Zaqar features to expose, to create a UI for it and do the implementation afterwards. |
DIFFICULTY=High|
TOPICS=Zaqar, Horizon|
SKILLS=Python, Django, Javascript, AngularJS|
EXTRA_SKILLS=State which other skills are needed, like networking or master special tools|
MENTORS= [[User:vkmc| Victoria Martinez de la Cruz]]|
STATUS=Looking for candidates.|
PROGRAM=Not selected yet
}}

== Development notes ==

This idea has not been selected for execution yet.

Category:Internship idea

2015-04-27T22:17:16Z

Smaffulli:

This category lists all of possible ideas for internships with OpenStack. Includes ideas that are already implemented or currently being worked on.

[[Category: Internship]]

Zaqar client support API v1.1

2015-04-27T22:15:16Z

Smaffulli:

{{InternshipIdea|
TITLE=zaqar-pythonclient support for Zaqar API v1.1|
DESCRIPTION=Currently there are three versions of Zaqar API: v1, v1.1 and v2.0 (under heavy development). zaqar-pythonclient has full support for all the features in API v1, but its missing support for some features in API v1.1. This task would require to learn and understand the new features provided in API v1.1 and add support for them client side. |

DIFFICULTY=Medium |
TOPICS=zaqar, client|
SKILLS=Python|
EXTRA_SKILLS=none|
MENTORS=[[User:vkmc|Victoria Martinez de la Cruz]] |
STATUS=Assigned to $intern for Outreachy May 2015 |
PROGRAM=Outreachy May-Aug 2015
}}

== Development progress ==

TBD

[[Category: OutreachyMay2015]]

Template:InternshipIdea

2015-04-27T22:13:51Z

Smaffulli:

<noinclude>
== Usage ==

Use this template to create ideas for internships. To use this template create a new page, give it as title the name of your idea and insert the code below, substituting where appropriate.

<pre>
{{InternshipIdea|
TITLE=My Awesome Internship Idea|
DESCRIPTION=A brief description of this idea, one line would be enough |
DIFFICULTY=High, Medium, Low (judge if the idea can be accomplished by a totally new developer or someone already skilled in OpenStack or distributed systems)|
TOPICS=Comma separated list of topics, like the OpenStack projects involved|
SKILLS=List of required programming skills, like Python, Java, AngularJS|
EXTRA_SKILLS=State which other skills are needed, like networking or master special tools|
MENTORS=Add the details to contact the mentor(s) for this idea
STATUS=Add information about the program, for example: Assigned to $intern for Outreachy May 2015 or Looking for candidates.
PROGRAM=Outreach May-Aug 2015 or GSoC2016
}}

</pre>

The snippet above will be rendered in the new page as below, more or less.

</noinclude>

= {{{TITLE|Title of the idea}}} =

{{{DESCRIPTION|A brief description of this idea, one line would be enough}}}

{| class="wikitable"
|-
| Difficulty || {{{DIFFICULTY|High, Medium, Low}}}
|-
| Topics || {{{TOPICS|Comma separated list of topics}}}
|-
| Required skills || {{{SKILLS|List of required programming skills}}}
|-
| Extra skills || {{{EXTRA|State which other skills are needed}}}
|-
| Mentor || {{{MENTORS|Details about the mentor(s)}}}
|-
| Status || {{{STATUS|Add information about the program, for example: Assigned to $intern or Looking for candidates.}}}
|-
| Program || {{{PROGRAM|Name of the internship program.}}}
|}

[[Category: internship_idea]]

Template:InternshipIdea

2015-04-27T22:13:22Z

Smaffulli:

<noinclude>
== Usage ==

Use this template to create ideas for internships. To use this template create a new page, give it as title the name of your idea and insert the code below, substituting where appropriate.

<pre>
{{InternshipIdea|
TITLE=My Awesome Internship Idea|
DESCRIPTION=A brief description of this idea, one line would be enough |
DIFFICULTY=High, Medium, Low (judge if the idea can be accomplished by a totally new developer or someone already skilled in OpenStack or distributed systems)|
TOPICS=Comma separated list of topics, like the OpenStack projects involved|
SKILLS=List of required programming skills, like Python, Java, AngularJS|
EXTRA_SKILLS=State which other skills are needed, like networking or master special tools|
MENTOR=Add the details to contact the mentor(s) for this idea
STATUS=Add information about the program, for example: Assigned to $intern for Outreachy May 2015 or Looking for candidates.
PROGRAM=Outreach May-Aug 2015 or GSoC2016
}}

</pre>

The snippet above will be rendered in the new page as below, more or less.

</noinclude>

= {{{TITLE|Title of the idea}}} =

{{{DESCRIPTION|A brief description of this idea, one line would be enough}}}

{| class="wikitable"
|-
| Difficulty || {{{DIFFICULTY|High, Medium, Low}}}
|-
| Topics || {{{TOPICS|Comma separated list of topics}}}
|-
| Required skills || {{{SKILLS|List of required programming skills}}}
|-
| Extra skills || {{{EXTRA|State which other skills are needed}}}
|-
| Mentor || {{{MENTOR|Details about the mentor(s)}}}
|-
| Status || {{{STATUS|Add information about the program, for example: Assigned to $intern or Looking for candidates.}}}
|-
| Program || {{{PROGRAM|Name of the internship program.}}}
|}

[[Category: internship_idea]]

Category:OutreachyMay2015

2015-04-27T22:09:43Z

Smaffulli: Created page with "List of ideas assigned to Outreachy session for May-August 2015"

List of ideas assigned to Outreachy session for May-August 2015

Zaqar client support API v1.1

2015-04-27T22:04:27Z

Smaffulli:

{{InternshipIdea|
TITLE=zaqar-pythonclient support for Zaqar API v1.1|
DESCRIPTION=Currently there are three versions of Zaqar API: v1, v1.1 and v2.0 (under heavy development). zaqar-pythonclient has full support for all the features in API v1, but its missing support for some features in API v1.1. This task would require to learn and understand the new features provided in API v1.1 and add support for them client side. |

DIFFICULTY=Medium |
TOPICS=zaqar, client|
SKILLS=Python|
EXTRA_SKILLS=none|
MENTORS=Victoria Martinez de la Cruz |
STATUS=Assigned to $intern for Outreachy May 2015 |
PROGRAM=Outreachy May-Aug 2015
}}

== Development progress ==

TBD

[[Category: OutreachyMay2015]]

Zaqar client support API v1.1

2015-04-27T22:03:36Z

Smaffulli: Created page with "{{InternshipIdea| TITLE=zaqar-pythonclient support for Zaqar API v1.1| DESCRIPTION=Currently there are three versions of Zaqar API: v1, v1.1 and v2.0 (under heavy developmen..."

{{InternshipIdea|
TITLE=zaqar-pythonclient support for Zaqar API v1.1|
DESCRIPTION=Currently there are three versions of Zaqar API: v1, v1.1 and v2.0 (under heavy development). zaqar-pythonclient has full support for all the features in API v1, but its missing support for some features in API v1.1. This task would require to learn and understand the new features provided in API v1.1 and add support for them client side. |

DIFFICULTY=Medium |
TOPICS=zaqar, client|
SKILLS=Python|
EXTRA_SKILLS=none|
MENTORS=Victoria Martinez de la Cruz |
STATUS=Assigned to $intern for Outreachy May 2015 |
PROGRAM=Outreachy May-Aug 2015
}}

== Development progress ==

Test idea

2015-04-27T21:58:42Z

Smaffulli:

{{InternshipIdea|TITLE=My Awesome Internship Idea| DESCRIPTION=A brief description of this idea, one line would be enough | DIFFICULTY=High, Medium, Low (judge if the idea can be accomplished by a totally new developer or someone already skilled in OpenStack or distributed systems)| TOPICS=Comma separated list of topics, like the OpenStack projects involved| SKILLS=List of required programming skills, like Python, Java, AngularJS| EXTRA_SKILLS=State if the candidate needs to have other skills like networking or master special tools| MENTORS=Add the details to contact the mentor(s) for this idea |
STATUS=Looking for candidates |
PROGRAM=Outreachy May-Aug 2015
}}

== Here you can complete the description of the ideas with more details, with images and any other thing you'd add to a wiki page. ==

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam feugiat dolor sed nisl consectetur varius. Donec facilisis ultrices odio, sed convallis magna mattis vel. Sed justo erat, eleifend quis ornare at, eleifend sit amet leo. Etiam vulputate nulla sit amet feugiat congue. Nullam ac nisl bibendum, placerat augue sed, dignissim enim. Nunc rutrum lacus ut urna ultricies consequat. Donec id mi nunc. Pellentesque velit lorem, sodales eu dui vitae, semper consectetur nibh. Donec vitae ex vel arcu vulputate fermentum id ac tortor. Duis tempus varius molestie. Proin sit amet consectetur leo, vitae accumsan ante. Morbi vulputate mattis sagittis. Pellentesque dui lectus, maximus sed elementum sit amet, maximus at purus. Vestibulum viverra tortor enim, et porta est tincidunt sit amet.

Donec in tellus lacus. Etiam dapibus maximus dapibus. Nunc tincidunt porta mi. In hac habitasse platea dictumst. Suspendisse molestie purus ac neque dictum venenatis. Praesent id velit et eros venenatis vehicula. Mauris congue fermentum nibh, ut iaculis ligula. In malesuada nulla id quam dapibus, vel pretium neque volutpat. Pellentesque accumsan fringilla efficitur. Pellentesque consequat velit eu pharetra sodales. Nulla ullamcorper pretium tellus, vel venenatis nisi fringilla eget.

Praesent id neque molestie, volutpat mi sit amet, luctus mi. Nam consequat eu mauris sit amet vestibulum. Cras ac ex ex. Praesent bibendum imperdiet ultrices. Etiam non nisl felis. Vestibulum turpis velit, malesuada in lacus sit amet, lobortis bibendum neque. Maecenas vel tempor justo, vitae fermentum ante. In porttitor justo non augue bibendum, eu hendrerit nisi suscipit. Curabitur ex quam, scelerisque et nisi id, egestas auctor urna. Phasellus a ultrices massa, eu facilisis lectus.

Template:InternshipIdea

2015-04-27T21:58:05Z

Smaffulli:

<noinclude>
== Usage ==

Use this template to create ideas for internships. To use this template create a new page, give it as title the name of your idea and insert the code below, substituting where appropriate.

<pre>
{{InternshipIdea|
TITLE=My Awesome Internship Idea|
DESCRIPTION=A brief description of this idea, one line would be enough |
DIFFICULTY=High, Medium, Low (judge if the idea can be accomplished by a totally new developer or someone already skilled in OpenStack or distributed systems)|
TOPICS=Comma separated list of topics, like the OpenStack projects involved|
SKILLS=List of required programming skills, like Python, Java, AngularJS|
EXTRA_SKILLS=State which other skills are needed, like networking or master special tools|
MENTORS=Add the details to contact the mentor(s) for this idea
STATUS=Add information about the program, for example: Assigned to $intern for Outreachy May 2015 or Looking for candidates.
PROGRAM=Outreach May-Aug 2015 or GSoC2016
}}

</pre>

The snippet above will be rendered in the new page as below, more or less.

</noinclude>

= {{{TITLE|Title of the idea}}} =

{{{DESCRIPTION|A brief description of this idea, one line would be enough}}}

{| class="wikitable"
|-
| Difficulty || {{{DIFFICULTY|High, Medium, Low}}}
|-
| Topics || {{{TOPICS|Comma separated list of topics}}}
|-
| Required skills || {{{SKILLS|List of required programming skills}}}
|-
| Extra skills || {{{EXTRA|State which other skills are needed}}}
|-
| Mentor || {{{MENTOR|Details about the mentor(s)}}}
|-
| Status || {{{STATUS|Add information about the program, for example: Assigned to $intern or Looking for candidates.}}}
|-
| Program || {{{PROGRAM|Name of the internship program.}}}
|}

[[Category: internship_idea]]

Test idea

2015-04-27T21:51:17Z

Smaffulli:

{{InternshipIdea|TITLE=My Awesome Internship Idea| DESCRIPTION=A brief description of this idea, one line would be enough | DIFFICULTY=High, Medium, Low (judge if the idea can be accomplished by a totally new developer or someone already skilled in OpenStack or distributed systems)| TOPICS=Comma separated list of topics, like the OpenStack projects involved| SKILLS=List of required programming skills, like Python, Java, AngularJS| EXTRA_SKILLS=State if the candidate needs to have other skills like networking or master special tools| MENTORS=Add the details to contact the mentor(s) for this idea | STATUS=Looking for candidates }}

== Here you can complete the description of the ideas with more details, with images and any other thing you'd add to a wiki page. ==

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam feugiat dolor sed nisl consectetur varius. Donec facilisis ultrices odio, sed convallis magna mattis vel. Sed justo erat, eleifend quis ornare at, eleifend sit amet leo. Etiam vulputate nulla sit amet feugiat congue. Nullam ac nisl bibendum, placerat augue sed, dignissim enim. Nunc rutrum lacus ut urna ultricies consequat. Donec id mi nunc. Pellentesque velit lorem, sodales eu dui vitae, semper consectetur nibh. Donec vitae ex vel arcu vulputate fermentum id ac tortor. Duis tempus varius molestie. Proin sit amet consectetur leo, vitae accumsan ante. Morbi vulputate mattis sagittis. Pellentesque dui lectus, maximus sed elementum sit amet, maximus at purus. Vestibulum viverra tortor enim, et porta est tincidunt sit amet.

Donec in tellus lacus. Etiam dapibus maximus dapibus. Nunc tincidunt porta mi. In hac habitasse platea dictumst. Suspendisse molestie purus ac neque dictum venenatis. Praesent id velit et eros venenatis vehicula. Mauris congue fermentum nibh, ut iaculis ligula. In malesuada nulla id quam dapibus, vel pretium neque volutpat. Pellentesque accumsan fringilla efficitur. Pellentesque consequat velit eu pharetra sodales. Nulla ullamcorper pretium tellus, vel venenatis nisi fringilla eget.

Praesent id neque molestie, volutpat mi sit amet, luctus mi. Nam consequat eu mauris sit amet vestibulum. Cras ac ex ex. Praesent bibendum imperdiet ultrices. Etiam non nisl felis. Vestibulum turpis velit, malesuada in lacus sit amet, lobortis bibendum neque. Maecenas vel tempor justo, vitae fermentum ante. In porttitor justo non augue bibendum, eu hendrerit nisi suscipit. Curabitur ex quam, scelerisque et nisi id, egestas auctor urna. Phasellus a ultrices massa, eu facilisis lectus.