OpenStack - User contributions [en]

GSoC2015

2015-02-20T17:02:18Z

Marga: /* Mentors */

== Google Summer of Code 2015 ==

[http://www.openstack.org/software/ OpenStack] is applying as a mentoring organization for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 2015 Google Summer of Code]. Check [https://developers.google.com/open-source/soc/ Google Developers site] for more information on how the program works.

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

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

== What is OpenStack ==

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

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

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

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

== Mentors ==

If you're interested in mentoring for this round, please add your name, email, IRC handle and the kind of projects you're interested in mentoring below. Please ensure that the projects are official projects in OpenStack and are registered in the [https://github.com/openstack/governance/blob/master/reference/programs.yaml governance projects.yaml].

* Amit Saha - amsaha - Neutron. Specifically network diagnostics. https://www.openstack.org/vote-vancouver/presentation/don-diagnosing-ovs-in-neutron
* Debo Dutta - dedutta - Nova, Monasca, Ceilometer, Log/Metrics, Operations
* Michael Krotscheck - krotscheck - StoryBoard
* Davanum Srinivas - dims - Nova, Oslo-*
* Samuel de Medeiros Queiroz - samueldmq - keystone
* Boris Pavlovic - boris-42 - Rally
* Joshua Harlow - harlowja - taskflow, tooz, oslo, anvil, cloud-init
* David Stanek - dstanek - Keystone
* Yathiraj Udupi - yudupi - Nova, Scheduler, Gantt, Congress, Policy, Ceilometer, Monasca
* Matthew Treinish - mtreinish -
* Nikhil Manchanda - SlickNik - Trove
* Sumit Naiksatam - Policy (Group Based Policy), Networking (Neutron), L4-7 Services (FWaaS, VPNaaS, LBaaS)
* Ethan Gafford - egafford - Sahara
* Michael McCune - elmiko - Sahara
* Marga Millet - millet -

== Students ==

Students application period opens '''March 16''' and ends on '''March 27'''.

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

* Prabhjyot Singh Sodhi - India - prabhjyotsingh95@gmail.com - psd - Rally: Adding Cloud Info
* Himangi Saraogi - India - himangi774@gmail.com - himangi - Oslo, Rally
* Shaifali Agrawal - India - agrawalshaifali09@gmail.com - exploreshaifali - Rally: Generating Trends from N tasks
* Artem Shepelev - Russia - shepelev.artem@gmail.com - ashepelev - Nova, Gantt, Neutron, Fuel
* Telles Nobrega - Brazil - tellesnobrega@gmail.com - tellesnobrega - Sahara
* Henrique Truta - Brazil - henriquecostatruta@gmail.com - htruta - Monasca, Keystone, Nova

== Communication ==

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

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

Then, let's start to write your proposal! A proposal template can be seen at [[GSoC2015/StudentApplicationTemplate|GSoC2015/StudentApplicationTemplate]].

== References ==

* [[GSoC2014|OpenStack GSoC 2014 wiki]]
* [http://www.google-melange.com/gsoc/events/google/gsoc2015 Google's GSoC 2015 page]

== Ideas ==

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

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

=== Neutron | Diagnostics in Neutron ===

Neutron provides Networking-as-a-service in the OpenStack ecosystem. Networking functionalities are provided by plugins that implement well-defined Neutron APIs. Among many, the Open vSwitch plugin (OVS) is possibly the most widely used. Any practical OpenStack installation has complicated networking configuration and verifying it manually is time consuming and error prone. We count with a completely automated service for verifying and diagnosing the networking functionality provided by OVS. This service verifies (or points out deviations) that the user configuration is indeed reflected in the underlying infrastructure and presents the results in an intuitive graphical display.

Tasks:
* Does user configuration match system settings?
* Can we mine logs to see why system is misbehaving?

{| class="wikitable"
|-
| Difficulty ||
|-
| Topics || [[Neutron|Neutron]], Networking, Diagnostics
|-
| Required skills || Python
|-
| Extra skills || Networking
|-
| Mentor || Amit Saha (amsaha)
|}

=== 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 ||
|-
| Topics ||
|-
| Required skills ||
|-
| Extra skills ||
|-
| Mentor || Sumit Naiksatam
|}

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

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

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

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

Tasks:

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

=== 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)
|}

== More ideas ==

Check out for more project ideas in:

* Oslo - Look through specs being proposed (https://review.openstack.org/#/q/project:openstack/oslo-specs,n,z) and those that are in progress (https://git.openstack.org/cgit/openstack/oslo-specs/tree/specs/kilo)
* Nova - Look through specs being proposed (https://review.openstack.org/#/q/project:openstack/nova-specs,n,z)
* Keystone - Look through specs being proposed (https://review.openstack.org/#/q/project:openstack/keystone-specs,n,z)
* Rally - Look through specs being proposed (https://review.openstack.org/#/q/project:openstack/rally-specs,n,z)
* Cinder - Look through specs being proposed (https://review.openstack.org/#/q/project:openstack/cinder-specs,n,z)
* Swift - Look through specs being proposed (https://review.openstack.org/#/q/project:openstack/swift-specs,n,z)
* Zaqar - Look through specs being proposed (https://review.openstack.org/#/q/project:openstack/zaqar-specs,n,z)
* Trove - Look through specs being proposed (https://review.openstack.org/#/q/project:openstack/trove-specs,n,z)
* Neutron - Look through specs being proposed (https://review.openstack.org/#/q/project:openstack/neutron-specs,n,z)
* OPW Ideas page - https://wiki.openstack.org/wiki/OutreachProgramForWomen/Ideas

Cisco-n1kv-neutron

2014-10-20T05:02:18Z

Marga: Nexus1000v Neutron Plugin

= Nexus1000v Neutron Plugin =
----------------------------

== Overview ==

Nexus1000v Neutron Plugin v2 implements the Neutron v2.0 API.

== Requirements ==

* Cisco Nexus1000v for KVM Release 5.2(1)SK(2.2) (or higher)

== Configuration ==

=== Nexus1000v Neutron Plugin Configuration ===

* MySQL should be installed on the host. Initialize MySQL as follows (where $PASS = mysql password):

<pre><nowiki>
$ mysql -u root -p$PASS -e 'DROP DATABASE IF EXISTS cisco_neutron;'
$ mysql -u root -p$PASS -e 'CREATE DATABASE IF NOT EXISTS cisco_neutron;'
$ mysql -u root -p$PASS -e 'GRANT ALL ON cisco_neutron.* TO '$Neutron_User'@'%' IDENTIFIED BY '$Neutron_Pass';
</nowiki></pre>

* Edit /etc/neutron/neutron.conf and set provider as:

<pre><nowiki>
[DEFAULT]
core_plugin = neutron.plugins.cisco.network_plugin.PluginV2

[DATABASE]
sql_connection = mysql://<username>:<password>@<database_ip>:3306/cisco_neutron
</nowiki></pre>

* Edit the file /etc/neutron/plugins/cisco/cisco_plugins.ini and comment out as need it:

<pre><nowiki>

[CISCO_PLUGINS]

# (StrOpt) Period-separated module path to the plugin class to use for
# the Cisco Nexus switches.
#
#nexus_plugin = neutron.plugins.cisco.nexus.cisco_nexus_plugin_v2.NexusPlugin

# (StrOpt) Period-separated module path to the plugin class to use for
# the virtual switches on compute nodes.
#
vswitch_plugin = neutron.plugins.cisco.n1kv.n1kv_neutron_plugin.N1kvNeutronPluginV2

[cisco]

# Cisco Nexus Switch configurations.
# Each switch to be managed by Openstack Neutron must be configured here.
#
# Cisco Nexus Switch Format.
# [NEXUS_SWITCH:<IP address of switch>]
# <hostname>=<port> (1)
# ssh_port=<ssh port> (2)
# username=<credential username> (3)
# password=<credential password> (4)
#
# (1) For each host connected to a port on the switch, specify the hostname
# and the Nexus physical port (interface) it is connected to.
# (2) The TCP port for connecting via SSH to manage the switch. This is
# port number 22 unless the switch has been configured otherwise.
# (3) The username for logging into the switch to manage it.
# (4) The password for logging into the switch to manage it.
#
# Example:
# [NEXUS_SWITCH:1.1.1.1]
# compute1=1/1
# compute2=1/2
# ssh_port=22
# username=admin
# password=mySecretPassword

# [N1KV:<IP address of VSM>]
# username=<credential username>
# password=<credential password>
#
# Example:
# [N1KV:2.2.2.2]
# username=admin
# password=mySecretPassword

[cisco_n1k]

# (StrOpt) Specify the name of the integration bridge to which the VIFs are
# attached.
#
# Example: integration_bridge = br-int

# (StrOpt) Name of the policy profile to be associated with a port when no
# policy profile is specified during port creates.
#
# Example: default_policy_profile = service_profile

# (StrOpt) Name of the policy profile to be associated with a port owned by
# network node (dhcp, router).
#
# Example: network_node_policy_profile = dhcp_pp

# (StrOpt) Name of the network profile to be associated with a network when no
# network profile is specified during network creates. Admin should pre-create
# a network profile with this name.
#
# Example: default_network_profile = network_pool

# (StrOpt) Time in seconds for which the plugin polls the VSM for updates in
# policy profiles.
#
# Example: poll_duration = 180

[database]

# (StrOpt) Connection to the neutron_l2network database
#
# connection = mysql://<credential username>:<credential password>@127.0.0.1/cisco_neutron?charset=utf8
# Example: connection = mysql://root:mySecretPassword@127.0.0.1/cisco_neutron?charset=utf8
</nowiki></pre>

=== Configuration Example ===

<pre><nowiki>

[CISCO_PLUGINS]
vswitch_plugin = neutron.plugins.cisco.n1kv.n1kv_neutron_plugin.N1kvNeutronPluginV2

[CISCO]

[N1KV:10.10.10.10]
username = admin
password = mySecretPassword

[CISCO_N1K]

integration_bridge = br-int
default_policy_profile = service_pp
network_node_policy_profile = dhcp_pp
poll_duration = 10

[DATABASE]
connection = mysql://root:cisco@127.0.0.1/cisco_neutron?charset=utf8

Start the neutron service by providing the relevant configuration files:

cd <neutron_path> && python <neutron_path>/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/cisco/cisco_plugins.ini

</nowiki></pre>

== Devstack ==

Include in "localrc/local.conf" file the following variables:

Q_PLUGIN=cisco

Neutron

2014-10-20T04:52:54Z

Marga: /* Plugins */

[[Category:Networking]]
[[Category:Neutron]]
= OpenStack Networking ("Neutron") =

{| border="1" cellpadding="2" cellspacing="0"
| [http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html Administrator Guide ]
|-
| [http://docs.openstack.org/user-guide/content/neutron_client_sample_commands.html Neutron CLI Guide ]
|-
| [http://docs.openstack.org/api/openstack-network/2.0/content/ API Developer Doc (v2) ]
|-
| [https://github.com/openstack/neutron Source code ]
|-
| [https://bugs.launchpad.net/neutron Bug tracker ]
|-
| [https://blueprints.launchpad.net/neutron Blueprints ]
|}

== Neutron Mission Statement ==
To implement services and associated libraries to provide on-demand, scalable, and technology-agnostic network abstraction. [https://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml Source]

== What is Neutron? ==
Neutron is an [https://wiki.openstack.org OpenStack] project to provide "networking as a service" between interface devices (e.g., vNICs) managed by other Openstack services (e.g., nova).

Starting in the Folsom release, Neutron is a core and supported part of the [https://wiki.openstack.org OpenStack] platform (for Essex, we were an "incubated" project, which means use is suggested only for those who really know what they're doing with Neutron).

If you're a networking geek and like to hack on [https://wiki.openstack.org OpenStack], please join!

More Info:
* [http://www.slideshare.net/danwent/openstack-quantum-intro-os-meetup-32612 Overview of Neutron] (slides) (3/12)
* [https://www.youtube.com/watch?v=_I1SrO2QBpg Neutron Project Overview + Update from Grizzly Summit] (video) (10/12)
* [http://www.infoq.com/presentations/Quantum-Virtual-Networks-for-OpenStack Video Neutron Overview] (3/12)
* [http://sdrv.ms/YdnQYS Slides on Technical Architecture of Neutron] (2013-03-14)

== Related projects ==
* [https://launchpad.net/python-neutronclient Python Neutron client]
* Neutron Admin and API documentation in [https://launchpad.net/openstack-manuals OpenStack Manuals]
* Tempest testing project [http://docs.openstack.org/developer/tempest/ Tempest Manuals]. For the Icehouse cycle, the community is undertaking a focused effort to strengthen the suite of Tempest tests for Neutron. If you are interested on contributing to this effort, please go to [https://etherpad.openstack.org/p/icehouse-summit-qa-neutron Icehouse Neutron Tempest push] to see what is being done and to [https://wiki.openstack.org/wiki/Neutron/TempestAPITests TempestAPITests] for HOWTO instructions. Helping to develop Tempest tests (particularly API tests) is an excellent way for new contributors to learn Neutron.

== Sub Teams ==

Neutron uses a concept of "sub-teams" to help distribute the work of design reviews, bug triage, code reviews, progress updates, etc.

The [[NeutronSubTeams]] page lists current sub teams and provides links to find meeting times and status.

== Why Neutron? ==

* Give cloud tenants an API to build rich networking topologies, and configure advanced network policies in the cloud.
** Example: create multi-tier web application topology
* Enable innovation plugins (open and closed source) that introduce advanced network capabilities
** Example: use L2-in-L3 tunneling to avoid VLAN limits, provide end-to-end QoS guarantees, used monitoring protocols like [[NetFlow]].
* Let anyone build advanced network services (open and closed source) that plug into Openstack tenant networks.
** Examples: LB-aaS, VPN-aaS, firewall-aaS, IDS-aaS, data-center-interconnect-aaS.
* Horizon GUI support for:
** Neutron L2 and L3 network and subnet creation/deletion
** Booting VMs on specific Neutron networks.
* API Extensibility Framework, including extensions for:
** "provider network", which maps Neutron L2 networks to a specific VLAN in the physical data center

== Using Neutron ==

Follow the instructions in the [http://docs.openstack.org/admin-guide-cloud/content/ch_networking.html Neutron Administrator Guide], or use the installation documentation at http://docs.openstack.org to use Neutron with OpenStack Nova.

Forget documentation, I just want to get the code!: [https://launchpad.net/neutron/+download Neutron Downloads]

Detailed information for programming against v2.0 of the Neutron web services API is available in the [http://docs.openstack.org/api/openstack-network/2.0/content/ Neutron API Guide]

If you are looking for information on using Neutron with devstack, please see: [[NeutronDevstack]] .

Neutron lets you use a set of different backends called "plugins" that work with a growing variety of networking technologies. These plugins may be distributed as part of the main Neutron release, or separately.

== Plugins ==
The set of plugins included in the main Neutron distribution and supported by the Neutron community include:

* [http://www.openvswitch.org Open vSwitch] Plugin
* [http://wiki.openstack.org/cisco-neutron Cisco UCS/Nexus] Plugin
* [http://wiki.openstack.org/cisco-n1kv-neutron Cisco Nexus1000v] Plugin
* [http://wiki.openstack.org/Quantum-Linux-Bridge-Plugin Linux Bridge] Plugin
* [http://wiki.openstack.org/Neutron/ML2 Modular Layer 2] Plugin
* [http://www.nicira.com Nicira Network Virtualization Platform (NVP)] Plugin
* [http://www.osrg.net/ryu/using_with_openstack.html Ryu OpenFlow Controller] Plugin
* [[Neutron/NEC OpenFlow Plugin|NEC OpenFlow]] Plugin
* [http://docs.projectfloodlight.org/display/floodlightcontroller/Quantum+REST+Proxy+Plugin Big Switch Controller Plugin]
* [http://www.cloudbase.it/quantum-hyper-v-plugin/ Cloudbase Hyper-V] Plugin
* [https://wiki.openstack.org/wiki/MidoNet MidoNet] Plugin
* [https://github.com/brocade/brocade Brocade Neutron Plugin] Brocade Neutron Plugin
* [https://wiki.openstack.org/wiki/PLUMgrid-Neutron PLUMgrid] Plugin
* [https://wiki.openstack.org/wiki/Mellanox-Neutron Mellanox Neutron Plugin] Mellanox Neutron Plugin
* [https://wiki.openstack.org/wiki/Neutron/EmbraneNeutronPlugin Embrane Neutron Plugin]
* [https://wiki.openstack.org/wiki/IBM-Neutron IBM SDN-VE] Plugin
* [http://www.cplanenetworks.com/ CPLANE NETWORKS ] CPLANE NETWORKS
* [http://www.nuagenetworks.net/ Nuage Networks] Plugin

Additional plugins are available from other sources:
* [http://www.opencontrail.org OpenContrail] Plugin
* [http://www.extremenetworks.com Extreme Networks] Plugin
* [https://github.com/ruijie/rgos_quantum_plugin Ruijie Networks] Plugin
* [https://www.juniper.net/support/downloads/?p=qpluginopen#sw Juniper Networks] Neutron Plugin
If you have your own plugin, feel free to add it to this list.

== Havana Release and ML2 Plugin Update ==
Starting with Havana release, openvswitch and linuxbridge plugins are deprecated. Modular Layer 2 (ML2) plugin replaces these plugins.
L2 agents work with ML2 plugin and continue to work with the deprecated monolithic plugins.

ML2 plugin architecture facilitates the type drivers to support multiple networking technologies, and mechanism drivers to facilitate the access to the networking configuration in a transactional model. The details of these drivers is described [https://wiki.openstack.org/wiki/Neutron/ML2#ML2_Drivers here]. Long term goal is to transition all vendor specific plugins to the type and mechanism drivers.

Following [https://wiki.openstack.org/wiki/Neutron/ML2#Type_Drivers Type Drivers] are supported:
* Flat
* Local
* VLAN
* GRE
* VxLan

Following Vendor specific [https://wiki.openstack.org/wiki/Neutron/ML2#Mechanism_Drivers Mechanism Drivers] are supported:
* [https://wiki.openstack.org/wiki/Arista-neutron-ml2-driver Arista Driver]
* [https://wiki.openstack.org/wiki/Neutron/ML2/MechCiscoNexus Cisco Nexus Driver]
* [https://wiki.openstack.org/wiki/Neutron/ML2/Tail-f-NCS-neutron-ml2-driver Tail-f NCS Driver]

== Participate ==

To get code, ask questions, view blueprints, etc, see: [https://launchpad.net/neutron/ Neutron Launchpad Page]

See [[NeutronDevelopment]] for some (rough) guides on how to contribute code to Neutron, including how to add your own plugin.

If you would like to participate, please send mail to the main openstack-dev list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

You can also attend our regular IRC meetings, which start one hour after the main openstack meeting, on the same #openstack-meeting channel: http://wiki.openstack.org/Network/Meetings

Check out [[NeutronStarterBugs]] for ideas on easy bugs or starter projects you might tackle. Or just start playing with [[NeutronDevstack]] and come up with your own ideas!

== Related pages ==
=== Neutron/* ===
{{Special:PrefixIndex/Neutron}}

=== Network/* ===
{{Special:PrefixIndex/Network}}