OpenStack - User contributions [en]

Stackforge Namespace Retirement

2015-09-28T07:52:14Z

Fghaas: /* Inactive Projects to Retire */ Add kickstack

=== Background ===

The stackforge/ git namespace is being retired, and active projects are being moved to the openstack/ namespace. See this mailing list post for [http://lists.openstack.org/pipermail/openstack-dev/2015-August/071816.html full background]. These changes are scheduled to occur on October 17, 2015.

There are two lists below, one for active projects that should be moved, and a second for inactive projects that should become read-only. Please update them to add your project to the correct list.

=== Active Projects to Move ===
Active stackforge projects that wish to move into the openstack/ namespace should be added to this list. Projects in this list will be automatically moved by the Infrastructure team to openstack/ on October 17. Please note that no other renames can happen during this move -- projects will strictly be moved from stackforge/ to openstack/ with their existing names.

* aeromancer
* anvil
* bansho
* blazar
* blazar-nova
* ceilometer-powervm
* ceilometer-zvm
* cerberus
* cerberus-dashboard
* cl-openstack-client
* cloud-init
* cloudbase-init
* clouddocs-maven-plugin
* cloudkitty
* cloudkitty-dashboard
* cloudpulse
* cognitive
* compass-adapters
* compass-core
* compass-specs
* compass-web
* compute-hyperv
* devstack-plugin-glusterfs
* devstack-plugin-sheepdog
* doc8
* dox
* drbd-devstack
* driverlog
* ec2-api
* faafo
* freezer
* freezer-api
* freezer-web-ui
* fuel-agent
* fuel-astute
* fuel-dev-tools
* fuel-devops
* fuel-docs
* fuel-library
* fuel-main
* fuel-mirror
* fuel-nailgun-agent
* fuel-octane
* fuel-ostf
* fuel-ostf-plugin
* fuel-plugin-calamari
* fuel-plugin-calico
* fuel-plugin-ceilometer-redis
* fuel-plugin-cinder-netapp
* fuel-plugin-cisco-aci
* fuel-plugin-contrail
* fuel-plugin-dbaas-trove
* fuel-plugin-detach-database
* fuel-plugin-detach-keystone
* fuel-plugin-detach-rabbitmq
* fuel-plugin-elasticsearch-kibana
* fuel-plugin-external-emc
* fuel-plugin-external-glusterfs
* fuel-plugin-external-zabbix
* fuel-plugin-glance-nfs
* fuel-plugin-ha-fencing
* fuel-plugin-influxdb-grafana
* fuel-plugin-ironic
* fuel-plugin-ldap
* fuel-plugin-lma-collector
* fuel-plugin-lma-infrastructure-alerting
* fuel-plugin-mellanox
* fuel-plugin-midonet
* fuel-plugin-neutron-fwaas
* fuel-plugin-neutron-lbaas
* fuel-plugin-neutron-vpnaas
* fuel-plugin-nova-nfs
* fuel-plugin-nsxv
* fuel-plugin-opendaylight
* fuel-plugin-saltstack
* fuel-plugin-solidfire-cinder
* fuel-plugin-swiftstack
* fuel-plugin-tintri-cinder
* fuel-plugin-tls
* fuel-plugin-vmware-dvs
* fuel-plugin-vxlan
* fuel-plugin-zabbix-monitoring-emc
* fuel-plugin-zabbix-monitoring-extreme-networks
* fuel-plugin-zabbix-snmptrapd
* fuel-plugins
* fuel-provision
* fuel-qa
* fuel-specs
* fuel-stats
* fuel-tasklib
* fuel-upgrade
* fuel-web
* gce-api
* gerrit-dash-creator
* git-upstream
* golang-client
* group-based-policy
* group-based-policy-automation
* group-based-policy-specs
* group-based-policy-ui
* intel-nfv-ci-tests
* merlin
* monasca-agent
* monasca-api
* monasca-ceilometer
* monasca-common
* monasca-log-api
* monasca-notification
* monasca-persister
* monasca-statsd
* monasca-thresh
* monasca-ui
* monasca-vagrant
* monitoring-for-openstack
* namos
* nerd-reviewer
* networking-6wind
* networking-hyperv
* networking-ovs-dpdk
* networking-zvm
* nova-docker
* nova-powervm
* nova-solver-scheduler
* nova-zvm-virt-driver
* ops-tags-team
* osprofiler
* ospurge
* packstack
* puppet-autossh
* puppet-ceph
* puppet-n1k-vsm
* puppet-setproxy
* puppet-surveil
* python-blazarclient
* python-cerberusclient
* python-cloudkittyclient
* python-cloudpulseclient
* python-cognitiveclient
* python-fuelclient
* python-group-based-policy-client
* python-jenkins
* python-monascaclient
* python-openstacksdk
* python-rackclient
* python-senlinclient
* python-sticksclient
* python-surveilclient
* python-tackerclient
* python-watcherclient
* rack
* requests-mock
* senlin
* senlin-dashboard
* shaker
* sqlalchemy-migrate
* surveil
* surveil-specs
* stackalytics
* sticks
* sticks-dashboard
* swift3
* swiftonfile
* tacker
* tacker-horizon
* tacker-specs
* tap-as-a-service
* telcowg-usecases
* terracotta
* third-party-ci-tools
* tricircle
* vmtp
* watcher
* wsme
* xenapi-os-testing
* xstatic-d3
* xstatic-angular-sanitize
* xstatic-bootstrap-datepicker
* xstatic-angular-gettext
* xstatic-bootswatch
* xstatic-angular-cookies
* xstatic-bootstrap-scss
* xstatic-angular-smart-table
* xstatic-angular-fileupload
* xstatic-angular-bootstrap
* xstatic-angular
* xstatic-angular-mock
* xstatic-angular-lrdragndrop
* xstatic-roboto-fontface
* xstatic-jquery.quicksearch
* xstatic-mdi
* xstatic-rickshaw
* xstatic-magic-search
* xstatic-font-awesome
* xstatic-hogan
* xstatic-spin
* xstatic-jasmine
* xstatic-jquery-migrate
* xstatic-jquery-migrate
* xstatic-jsencrypt
* yaql

=== Inactive Projects to Retire ===
Inactive projects that should be retired should be added to this list. These projects will have a commit merged removing their content and replacing it with a message indicating the project is no longer maintained and will become read-only in Gerrit.

* compass-monit
* fuel-plugin-availability-zones
* mercador-pub
* mercador-sub
* MRaaS
* networking-portforwarding
* openstackdroid
* python-mercadorclient
* rubick
* sahara-guestagent
* libra
* logaas
* python-libraclient
* python-rallyclient
* cookbook-pacemaker
* puppet-openstack_dev_env
* puppet_openstack_builder
* puppet-openstack-cloud
* tripleo-ansible
* kickstack

Mellanox-Neutron-Havana

2013-12-17T12:33:15Z

Fghaas: /* Configuration */ With Havana, the vnic_type option "direct" has changed to "mlnx_direct"

= Overview =
== Mellanox Neutron Plugin ==
The Openstack Mellanox Neutron plugin supports Mellanox embedded switch functionality as part of the VPI (Ethernet/InfiniBand) HCA.
Mellanox Neutron Plugin allows hardware vNICs (based on SR-IOV virtual functions) per each Virtual Machine vNIC to have its unique
connectivity, security, and QoS attributes. Hardware vNICs can be mapped to the guest VMs through para-virtualization (using a Tap device), or directly as a Virtual PCI device to the guest, allowing higher performance and advanced features such as RDMA (remote direct memory access).

Hardware-based switching, provides better performance, functionality, and security/isolation for virtual cloud environments.
Future versions of the plug-in will include OpenFlow API to control and monitor the embedded switch and vNICs functionality

This plugin is implemented according to Plugin-Agent pattern.

+-----------------+ +--------------+
| Controller node | | Compute node |
+-----------------------------------+ +-----------------------------------+
| +-----------+ +----------+ | | +----------+ +----------+ |
| | | | | | | | | zmq | | |
| | Openstack | v2.0 | Mellanox | | RPC | | Mellanox |REQ/REP| Mellanox | |
| | Neutron +------+ Neutron +-----------+ Neutron +-------+ Embedded | |
| | | | Plugin | | | | Agent | | Switch | |
| | | | | | | | | | (NIC) | |
| +-----------+ +----------+ | | +----------+ +----------+ |
+-----------------------------------+ +-----------------------------------+

* Openstack Mellanox Neutron Plugin implements the Neutron v2.0 API.
* Mellanox Neutron Plugin processes the Neutron API calls and manages network segmentation ID allocation.
* The plugin uses databases to store configuration and allocation mapping.
* The plugin maintains compatibility to Linux Bridge Plugin, supports DHCP and L3 Agents by running L2 Linux Bridge Agent on Network Node.
* Mellanox Openstack Neutron Agent (L2 Agent) runs on each compute node.
* Agent should apply VIF connectivity based on mapping between a VIF (VM vNIC) and Embedded Switch port.

== Mellanox Nova VIF Driver ==
The Mellanox Nova VIF driver should be used when running Mellanox Neutron Plugin. This driver supports the VIF plugin by binding vNIC (para-virtualized or SR-IOV with optional RDMA guest access) to the embedded switch port.
VIF Driver for Para Virtualized mode is included in Nova. For SR-IOV pass-through one needs to use VIF driver from Mellanox git repository or RPM.

== Prerequisites ==

Make use you have RHOS or RDO repositories installed on all nodes in your cluster.

For RHOS installation refer to [http://www.redhat.com/resourcelibrary/reference-architectures/deploying-and-using-red-hat-openstack-rhos-2-dot-1 RHOS reference document]

For RDO installation, refer to [http://openstack.redhat.com/Quickstart RDO QuickStart]

'''Neutron server'''

No special prerequisites needed.

'''Compute Note'''

1. The software package python-zmq ([https://github.com/zeromq/pyzmq github]) must be installed. EPEL repository can be used as well.

2. python-setuptools (use "yum install python-setuptools")

3. python-pip (use "yum install python-pip")

4. Compute nodes should be equipped with Mellanox ConnectX®-3 Network Adapter ([http://www.mellanox.com/page/infiniband_cards_overview link])

5. Mellanox OFED 2.0.3 is installed.Refer to Mellanox website for the latest OFED ([http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers])

6. Enable SR-IOV on ConnectX-3 card. Refer to [http://community.mellanox.com/docs/DOC-1317 Mellanox Community]

7. The software package iproute2 - ([https://www.kernel.org/pub/linux/utils/net/iproute2/ Code] [http://www.policyrouting.org/iproute2.doc.html Documentation]) must be installed. Required only to be installed on compute nodes

8. The software package ethtool ([http://www.kernel.org/pub/software/network/ethtool/ Code]) must be installed (version 3.8 or higher). Required only to be installed on compute nodes.

9. oslo.config (use "pip-python install oslo.config"). Reuired only to be installed on compute nodes.

10. python-ethtool and python-zmq packages

'''Network Node'''

1. Compute nodes should be equipped with Mellanox ConnectX®-3 Network Adapter ([http://www.mellanox.com/page/infiniband_cards_overview link])

2. Mellanox OFED 2.0.3 is installed. Refer to Mellanox website for the latest OFED ([http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers])

'''Installation with Red Hat Enterprise Linux OpenStack Platform'''

For each section refer to 'Installation via RPMs'. No additional Prerequisites except for those required by Red Hat Enterprise Linux OpenStack Platform. Please refer to https://access.redhat.com/products/Cloud/OpenStack/ for additional information regarding this product.

= Ethernet Network =
== Controller Node ==
In /etc/nova/nova.conf ensure you have the following line:
security_group_api=nova

If you changed it - restart the nova services (e.g. cd /etc/init.d && for i in $( ls openstack-nova-*); do service $i restart; done)

== Neutron Server Node ==

=== Installation ===

Note: In case you are using Red Hat Enterprise Linux OpenStack (RHOS) Platform, RH6.4 is a minimum requirement.

1. Neutron server uses MySQL database. Make sure you have running MySQL database for neutron.

If Neutron server is already running, you should stop it.
#/etc/init.d/neutron-server stop

If you want to use a database that was created you have to drop it and create another one. For example:
mysql -u root -ppassword <<EOF
drop database if exists neutron;
create database neutron;
EOF

If you want to create a new one:

mysql -u root -ppassword <<EOF
drop database if exists neutron;
create database neutron;
GRANT ALL PRIVILEGES ON neutron.* TO 'neutron'@'localhost' IDENTIFIED BY 'password';
GRANT ALL PRIVILEGES ON neutron.* TO 'neutron' IDENTIFIED BY 'password';
FLUSH PRIVILEGES;
EOF

2. Install the required RPM for the Mellanox Neutron plugin:
#yum install openstack-neutron-mellanox

3. Modify the /etc/neutron/neutron.conf file.
core_plugin = neutron.plugins.mlnx.mlnx_plugin.MellanoxEswitchPlugin

4. Modify the /etc/neutron/plugins/mlnx/mlnx_conf.ini file to reflect your environment. Click [[Mellanox-Neutron #Mellanox_Neutron_Plugin_Configuration | here]] for configuration options.

5. Change the soft link to the plugin configuration (plugin.ini)

#unlink /etc/neutron/plugin.ini
#ln -s /etc/neutron/plugins/mlnx/mlnx_conf.ini /etc/neutron/plugin.ini

=== Configuration ===

1. Make the Mellanox plugin the current Neutron plugin by editing neutron.conf and changing core_plugin.
core_plugin = neutron.plugins.mlnx.mlnx_plugin.MellanoxEswitchPlugin

2. Plugin configuration:
Edit the configuration file: /etc/neutron/plugins/mlnx/mlnx_conf.ini

[DATABASE]
'''sql_connection''' - The parameter should be changed to the connection of the Neutron DB used by the plugin.
It must match the mysql configuration. For example:
"mysql://neutron:password@127.0.0.1:3306/neutron"
'''reconnect_interval''' = 2 (default)

[MLNX]
'''tenant_network_type''' - must be set on of supported tenant network types.
Possible values: 'vlan' for Ethernet or 'ib' for Infiniband.'vlan' is the default.
'''network_vlan_ranges''' - must be configured to specify the names of the physical networks
managed by the mellanox plugin, along with the ranges of VLAN IDs
available on each physical network for allocation to virtual networks.
Possible range is vlan range is 1-4093.
The default is "default:1:100"
<fabric name >:<vlan range start>:<vlan end range>

[agent]
# Agent's polling interval in seconds
# polling_interval = 2
# (BoolOpt) Enable server RPC compatibility with old (pre-havana)
# agents.
#
'''rpc_support_old_agents''' = True

'''Note''': rpc_support_old_agents should be set to 'True' (non default).

=== Start Services ===
Start (or restart) the Neutron server
#/etc/init.d/neutron-server start

== Compute Nodes ==

=== Installation ===
1. If you didn't download Mellanox OpenStack repo file download it :
#wget http://www.mellanox.com/downloads/solutions/openstack/havana/repo/mlnx-havana/mlnx-havana.repo -O /etc/yum.repos.d/mlnx-havana.repo

2. Install the eswitchd RPM:
#yum install eswitchd

3. In case you would like to use Ethernet in para-virtualized mode the VIF driver is already included in Nova package. Otherwise, Install Mellanox VIF driver (Make sure nova is installed on your server)
#yum install mlnxvif

4. Install the required RPM for the Neutron agent:
#yum install openstack-neutron-mellanox

=== Configuration ===

1. Configure /etc/eswitchd/eswitchd.conf if needed

Please Refer to Mellanox Community for the eSwitchd installation notes ( click [http://community.mellanox.com/docs/DOC-1126 here])

2. Modify /etc/nova/nova.conf

compute_driver=nova.virt.libvirt.driver.LibvirtDriver
libvirt_vif_driver=mlnxvif.vif.MlxEthVIFDriver
security_group_api=nova
connection_type=libvirt

In case you didn't install the Mellanox VIF driver, and you plan to use Ethernet only in paravirtualized ,mode: change the following:
libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtGenericVIFDriver

3. Modify the /etc/neutron/plugins/mlnx/mlnx_conf.ini file to reflect your environment.

[AGENT]
'''polling_interval''' - Polling interval (in seconds) for existing vNICs. The default is 2 seconds.
'''rpc''' - must be set to 'True'

[ESWITCH]
'''physical_interface_mapping''' - the network_interface_mappings maps each physical network name to the physical interface (on top of Mellanox Adapter) connecting the node to that physical network. The format of this paramter is: <fabric name>:< PF name> (Only releavant on Compute node). PF Name can either be the PF (Physical Function) Name or 'autoeth' for automatic Ethernet configuration,'autoib' for automatic Infiniband configuration.The default is "default:autoeth".
'''vnic_type''' - type of VM network interface: 'direct' or 'hostdev' according to libvirt terminology.
hostdev: this is the traditional method of assigning any generic PCI device to a guest (SR-IOV).
mlnx_direct: this is a method to provide macvtap device on top of the PCI device (default).
bridge: - When using Linux Bridge Plugin on top of eIPoIB device
'''daemon_endpoint''' - eswitch daemon end point connection (URL) (default value='tcp://127.0.0.1:5001')
daemon_endpoint should be changed to tcp://127.0.0.1:60001
'''request_timeout''' - the number of milliseconds the agent will wait for response on request to daemon. (default=3000 msec)

'''Note''': daemon_endpoint should be changed to tcp://127.0.0.1:60001

For a plugin configuration file example (Havana), please refer to [https://github.com/openstack/neutron/blob/stable/havana/etc/neutron/plugins/mlnx/mlnx_conf.inii Mellanox config *ini file].

4. Enable DHCP server to allow VMs to acquire IPs.
neutron_use_dhcp=true

=== Start Services ===

1. Restart Nova.
#/etc/init.d/openstack-nova-compute restart

2. Start eswitch Daemon
#/etc/init.d/eswitchd start

3. Start the Neutron agent
#/etc/init.d/neutron-mlnx-agent start

Note: eswitch Daemon should be running before the Neutron Agent is started.

== Network Node ==
Network node equipped with Mellanox Connectx-3 adapter card should be configured as follows:

1. Install Neutron linux bridge plugin and Neutron dhcp l3-agent:

#yum install openstack-neutron-linuxbridge

2. Change the following configuration of the ini file (/etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini)
physical_interface_mappings = default:eth2 (when eth2 is normally the name for Ethernet interface of Mellanox adapters)

3. Configure the DHCP server accodring to the following guidelines

http://docs.openstack.org/trunk/openstack-network/admin/content/adv_cfg_dhcp_agent.html

4. Start the DHCP server
#/etc/init.d/neutron-dhcp-agent start
#/etc/init.d/neutron-linuxbridge-agent start

= InfiniBand Network =
The Mellanox Neutron Plugin use InfiniBand Partitions (PKeys) to seperate Networks.

== SM Configuration ==

All the PKeys should be predefined in the partitions.conf file (/etc/opensm/partitions.conf)
(Automatic cofiguration is planned in future phase)

Add/Change the following in the partitions.conf file
management=0xffff,ipoib, sl=0, defmember=both : ALL, ALL_SWITCHES=full,SELF=full;

For every network you want to configure in Neutron you have to configure the pkey assisicated with the VLAN of this network (defined in Neutron).
vlan1=0x1, ipoib, sl=0, defmember=full : SELF;

For example:
If we have 10 VLANs defined in configuration in /etc/neutron/plugins/mlnx/mlnx_conf.ini

[MLNX]
network_vlan_ranges = default:1:10

We'll have the following configuration of the the partitions.conf file:

management=0x7fff,ipoib, sl=0, defmember=full : ALL, ALL_SWITCHES=full,SELF=full;
vlan1=0x1, ipoib, sl=0, defmember=full : ALL;
vlan2=0x2, ipoib, sl=0, defmember=full : ALL;
vlan3=0x3, ipoib, sl=0, defmember=full : ALL;
vlan4=0x4, ipoib, sl=0, defmember=full : ALL;
vlan5=0x5, ipoib, sl=0, defmember=full : ALL;
vlan6=0x6, ipoib, sl=0, defmember=full : ALL;
vlan7=0x7, ipoib, sl=0, defmember=full : ALL;
vlan8=0x8, ipoib, sl=0, defmember=full : ALL;
vlan9=0x9, ipoib, sl=0, defmember=full : ALL;
vlan10=0xa, ipoib, sl=0, defmember=full : ALL;

Change the following in /etc/opensm/opensm.conf:
allow_both_pkeys TRUE

Restart the openSM
#/etc/init.d/opensmd restart

== Neutron Server Node==

=== SR-IOV ===
SR-IOV is a passthrough mode.
Change the following in the file /etc/neutron/plugins/mlnx/mlnx_conf.ini
tenant_network_type = ib
vnic_type = hostdev
network_vlan_ranges = default:1:10
(sql_connection and reconnect_interval can be configured as described above)

The mapping between VLAN and PKEY is as follows: VLAN X = PKEY 0x8000 + X. For example: vlan 2 is pkey 0x8002

=== Para-Virtualized ===

On the controller, configure the file /etc/neutron/plugins/mlnx/mlnx_conf.ini
tenant_network_type = ib
vnic_type = bridge

== Compute Nodes ==

=== SR-IOV ===
SR-IOV is a passthrough mode.
Perform the following changes:
In The file /etc/neutron/plugins/mlnx/mlnx_conf.ini
physical_interface_mapping = default:autoib

Tenant_network_type , vnic_type and network_vlan_ranges parameters should be configured as the controller.

autoib can be replaced by the name of the PF.

Change the file /etc/eswitchd/eswitchd.conf
fabrics = default:autoib (or default:ib0)

eswitch should be started and then Neutron agent should be started
/etc/init.d/eswitchd restart
/etc/init.d/neutron-mlnx-agent restart

Verify Mellanox VIF driver is configured in /etc/nova/nova.conf
libvirt_vif_driver=mlnxvif.vif.MlxEthVIFDriver

Restart nova
#/etc/init.d/openstack-nova-compute restart

=== Para-Virtualized ===
Here we use the Linux Bridge plugin.

eIPoIB module should be up and configured.In /etc/infiniband/openib.conf:
E_IPOIB_LOAD=yes

And restart openibd:
#/etc/init.d/openibd restart

Please refer to eIPoIB configuration in Mellanox OFED User Manual<br />

Once we have the eIPoIB interface, we use it in the linux bridge agent configuration:

For Example:
Assuming eth1 is the eIPoIB interface:

To check that the interface type is eIPoIB run the command (verify that the driver is "eth_ipoib")
#ethtool -i <interface>
'''driver: eth_ipoib'''
version: 1.0.0
firmware-version: 1
bus-info: ib0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

Change the file /etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini

[linux_bridge]
physical_interface_mappings = default:eth1

Configure the Linux Bridge VIF Driver in /etc/nova/nova.conf
#libvirt_vif_driver=nova.virt.libvirt.vif.NeutronLinuxBridgeVIFDriver

Restart nova
#/etc/init.d/openstack-nova-compute restart

After confiuration Linux Bridge agent should be restarted.
#/etc/init.d/neutron-linuxbridge-agent restart

== Network Node ==

Configure the Linux bridge plugin as described in InfiniBand Para-Virtualized section (above)
To make use of DHCP in Paravitualized mode (with Linux Bridge) you have to make sure 'bootp-broadcast-always' option is configured in the Instance dhclient.conf file.

=== DHCP Server ===

For DHCP support – The Network node should use the Mellanox Dnsmasq driver as the DHCP driver.
# yum install mlnx-dnsmasq

Change the following in /etc/neutron/dhcp_agent.ini
dhcp_driver = mlnx_dhcp.MlnxDnsmasq

Copy ipoibd and override /sbin/ipoibd
#wget http://www.mellanox.com/downloads/solutions/openstack/havana/ipoibd
#cp ipoibd /sbin/ipoibd

Download and apply a patch for Linux Bridge Agent:

#wget http://www.mellanox.com/downloads/solutions/openstack/havana/patches/linux_bridge_agent.py.patch
#cd /usr/lib/python2.6/site-packages/neutron/plugins/linuxbridge/agent
#patch -p1 < linux_bridge_agent.py.patch

Restart openibd
#/etc/init.d/openibd restart

Start linux bridge agent
/etc/init.d/neutron-linuxbridge-agent restart

Start dhcp server
/etc/init.d/neutron-dhcp-agent restart

= Usage Examples =
* In order to create SR-IOV interface refer to [http://www.mellanox.com/sdn/stage/pdf/Mellanox-OpenStack-OpenFlow-Solution.pdf Mellanox OpenStack solution document "Creating an SR-IOV Instance" chapter]
* In order to create Para-Virtualized interface refer to [http://www.mellanox.com/sdn/stage/pdf/Mellanox-OpenStack-OpenFlow-Solution.pdf Mellanox OpenStack solution document "Creating a Para-Virtualized vNIC Instance" chapter]

= Known issues and Troubleshooting =

For known issues and troubleshooting options refer to [http://community.mellanox.com/docs/DOC-1127 Mellanox OpenStack Troubleshooting].

= References =
1. [http://www.mellanox.com/openstack/ http://www.mellanox.com/openstack/]

2. [https://github.com/mellanox-openstack Source repository]

3. [http://www.mellanox.com/page/products_dyn?product_family=26 Mellanox OFED]

4. [http://www.mellanox.com/sdn/stage/pdf/Mellanox-OpenStack-OpenFlow-Solution.pdf Mellanox OpenStack Solution Reference Architecture]

5. [http://community.mellanox.com/docs/DOC-1127 Mellanox OpenStack Troubleshooting]

For more details, please refer your question to [mailto:openstack@mellanox.com openstack@mellanox.com]

Return to [https://wiki.openstack.org/wiki/Mellanox-OpenStack Mellanox-OpenStack] wiki page.

OpenStack User Groups

2013-07-09T14:45:00Z

Fghaas: /* Europe */ Add OpenStack DACH meetup group to Austria and Switzerland

__NOTOC__

The OpenStack International Community team is the main contact point for anybody running a local OpenStack User Group.

Join [http://lists.openstack.org/cgi-bin/mailman/listinfo/community the mailing list] if you are hosting or want to start a user group with meetups, hackatons and other social events talking about OpenStack and free/libre open source software for the cloud.

Check the [[OpenStackUserGroups/HowTo]] if you decide that you need to start a new OpenStack User Group in your geographical area.
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
* '''[[#North America|North America]]'''
** [[#Atlanta|Atlanta]]
** [[#Austin|Austin]]
** [[#Boston|Boston]]
** [[#Canada|Canada]]
** [[#Chicago|Chicago]]
** [[#Colorado|Colorado]]
** [[#District_of_Columbia_:_Washington.2C_DC_Metro_Area|District of Columbia : Washington, DC Metro]]
** [[#Florida|Florida]]
** [[#Indiana|Indiana]]
** [[#Michigan|Michigan]]
** [[#Minnesota|Minnesota]]
** [[#Los Angeles|Los Angeles]]
** [[#New York City|New York City]]
** [[#North Carolina|North Carolina]]
** [[#San_Antonio.2C_Texas|San Antonio, Texas]]
** [[#San Francisco Bay Area|San Francisco Bay Area]]
** [[#Seattle|Seattle]]
* '''[[#Africa|Africa]]'''
** [[#Kenya|Kenya]]
** [[#Nigeria|Nigeria]]
* '''[[#Asia_.2F_Pacific|Asia / Pacific]]'''
** [[#Australia|Australia]]
*** [[#Canberra_.28ACT.29|Canberra]]
** [[#China|China]]
** [[#Hong Kong|Hong Kong]]
** [[#India|India]]
** [[#Indonesia|Indonesia]]
** [[#Japan|Japan]]
** [[#Malaysia|Malaysia]]
** [[#Singapore|Singapore]]
** [[#South Korea|South Korea]]
** [[#Taiwan|Taiwan]]
** [[#Thailand|Thailand]]
** [[#Vietnam|Vietnam]]
* '''[[#Latin America|Latin America]]'''
** [[#Argentina|Argentina]]
** [[#Brazil|Brazil]]
** [[#Ecuador|Ecuador]]
** [[#Venezuela|Venezuela]]
* '''[[#Europe|Europe]]'''
** [[#Belgium|Belgium]]
** [[#Finland|Finland]]
** [[#France|France]]
** [[#Germany|Germany]]
** [[#Hungary|Hungary]]
** [[#Nordics_.28Scandinavia.29|Nordics (Scandinavia)]]
** [[#Ireland|Ireland]]
** [[#Italy|Italy]]
** [[#Poland|Poland]]
** [[#Russia|Russia]]
** [[#Serbia|Serbia]]
** [[#Slovenia|Slovenia]]
** [[#South Eastern Europe|South Eastern Europe]]
** [[#Spain|Spain]]
** [[#Sweden|Sweden]]
** [[#Switzerland|Switzerland]]
** [[#UK|UK]]
* '''[[#Middle East|Middle East]]'''
** [[#Cyprus|Cyprus]]
** [[#Egypt|Egypt]]
** [[#Israel|Israel]]
** [[#Morocco|Morocco]]
** [[#Turkey|Turkey]]
** [[#UAE|UAE]]
* '''[[#Language specific|Language specific]]'''
</div>

== North America ==
=== Atlanta ===
* Meet-up details here: http://www.meetup.com/openstack-atlanta/
* IRC Channel: [[irc://irc.freenode.net/openstack-atlanta|#openstack-atlanta]] on Freenode
* Coordinators: Doug Hellmann, Mark McClain

=== Austin ===
* Meet-up details here: [http://www.meetup.com/openstack-austin/ http://www.meetup.com/openstack-austin/]

=== Boston ===
* Meet-up details here: http://www.meetup.com/Openstack-Boston/

=== '''Canada''' ===
* Meetup: http://www.meetup.com/Canadian-OpenStack-Users-Group/
* Website: http://canstack.ca
* Twitter: http://twitter.com/canstack
* Blog: http://blog.canstack.ca
* IRC: #canstack on freenode
* Meetup: http://www.meetup.com/OpenStackTO/
* Google Groups: http://groups.google.com/group/canada-openstack-user-group/
* LinkedIn Group: http://www.linkedin.com/groups/OpenStack-Canada-4151460
* Google Group: http://groups.google.com/group/openstack-canada

=== Chicago ===
* Meet-up details here: http://www.meetup.com/meetup-group-NjZdcegA/
* Coordinator: Steven Loving

=== Colorado ===
(primarily Northern Colorado)

* Meet-up details here: http://www.meetup.com/OpenStack-Colorado/

(primarily Denver Metro/South Denver)

* Meet-up details here: http://www.meetup.com/OpenStack-Denver/
* Twitter hashtag: #OSROCK
* Coordinator: Shannon McFarland and Scott Lowe

=== District of Columbia : Washington, DC Metro Area ===
* Meet-up details here: http://www.meetup.com/OpenStackDC/
* Meet-up details here: http://www.linkedin.com/groups?gid=4207039

=== Florida ===
* LinkedIn: http://www.linkedin.com/groups?gid=4762393
* FaceBook: http://www.facebook.com/FloridaOpenstack
* Google Group: https://groups.google.com/d/forum/openstack-florida
* Coordinator: [mailto:Trevor.Lowing@gmail.com Trevor Lowing]
=== Indiana ===
* Meet-up details: http://tinyurl.com/7k8b7mr
* Forum: https://portal.futuregrid.org/forums/fg-user-services-forum/openstack
* Contact: Gregor von Laszewski

=== Michigan ===
* Google Group: https://groups.google.com/d/forum/openstack-mi
* Google Community: https://plus.google.com/communities/104709877702253658956
* LinkedIn user group: http://www.linkedin.com/groups?home=&gid=4755132
* Coordinator: Eric Detterman

=== Minnesota ===
* Meet-up details: http://www.meetup.com/Minnesota-OpenStack-Meetup//
* Twitter hashtag: #MNOS
* Contact/Coordinator: Kyle Mestery

=== Los Angeles ===
* Meetup details here: http://www.meetup.com/OpenStack-LA
* LinkedIn user group: http://www.linkedin.com/groups?gid=4327316
* Twitter hashtag: #OSLAX
* Coordinator: Mike Perez, Matthew Wodrich

=== New York City ===
*Home Page: http://www.meetup.com/OpenStack-New-York-Meetup/
*Next Meetup: Wednesday, June 12th, 2013 (OpenStack Summit Recap) - http://www.meetup.com/OpenStack-New-York-Meetup/events/118590712/
*Twitter Handle: @OpenStackNYC
*Twitter Hashtag: #OpenStackNYC
*E-mail: openstacknyc@gmail.com
*Organizers: AppFirst, Jason Edelman, Denis Guyadeen, Kenneth Hui, Judd Maltin

=== North Carolina ===
* Meetup March 7, 2013: http://www.meetup.com/Triangle-OpenStack-Meetup/events/100075312/
* Coordinators: Mark Voelker, Arvind Somya, Amy Lewis

=== San Antonio, Texas ===
* Next meeting: Tuesday 21 May, 2013 @ Rackspace (also a Hangout will be hosted on the G+ community page)
* Meetup details here: http://www.meetup.com/SA-Open-Stackers/
* Community Page at https://plus.google.com/communities/104303691151444174690
* Coordinator(s): Wendel Hope

=== San Francisco Bay Area ===
* Meet-up details here: http://www.meetup.com/openstack/

=== Seattle ===
* Meet-up details here: http://www.meetup.com/OpenStack-Seattle/
* Calendar: http://www.meetup.com/OpenStack-Seattle/events/calendar/
* Coordinator: Mark Atwood of HP Cloud and Joseph Heck of Nebula

== Africa ==
* OpenStack Africa Google+ Community: https://plus.google.com/u/0/communities/106463180296945913906
* Coordinator: Adam Nelson (adam@kili.io)

=== Kenya ===
* Meetup: http://www.meetup.com/OpenStack-Nairobi
* Coordinator: Adam Nelson (adam@kili.io)

=== Nigeria ===
* Coordinator: Abayomi Ayoola (a 'dot' ayoola 'at' gmail 'dot' com)

== Asia / Pacific ==

=== Australia ===
* Meet-up details here: http://aosug.openstack.org.au
* Coordinator: Tristan Goode
* Google Group: http://groups.google.com/group/openstack-au

==== Canberra (ACT) ====
* Meetup: http://www.meetup.com/Canberra-OpenStack-Users-Group/
* LinkedIn Group: http://www.linkedin.com/groups?gid=4323576
* Coordinator: Kristoffer Sheather

=== China ===
* [http://trystack.cn/ Trystack] Google Group: https://groups.google.com/d/forum/trystack-china
* Twitter: [https://twitter.com/openstackchina @OpenStackChina] [http://www.slideshare.net/ben_duyujie/ Slideshare]
* Weibo: [http://weibo.com/cosug @COSUG](China OpenStack User Group) or [http://weibo.com/trystack @trystack]
* http://groups.google.com/group/china-openstack-user-group
* LinkedIn Group: [http://www.linkedin.com/groups/openstackchina-4034145?home=&gid=4034145&trk=anet_ug_hm openstack-china]
* Twitter: @OpenStackCN
* Weibo: [http://weibo.com/openstack @OpenStack]
* Coordinator: Hui Cheng< freedomhui@gmail.com >, ben( duyujie[dot]dyj[at]gmail[dot]com/[http://weibo.com/u/1716287123 Weibo:@ben_杜玉杰])

=== Hong Kong ===
* Google Group: https://groups.google.com/d/forum/hong-kong-cloud-technology-sig
* Facebook Group: https://www.facebook.com/groups/HKOSUG/
* Coordinator: [mailto:brucelok@cyberport.hk Bruce Lok | HK Cyberport ]; [mailto:raymondchan@cyberport.hk Raymond Chan | HK Cyberport ]

=== India ===
* Meetup Page: http://www.meetup.com/Indian-OpenStack-User-Group
* Subscribe to community mailing list sending an email to openstackindia@librelist.com
* Facebook Page: http://www.facebook.com/groups/328814400511881/
* LinkedIn: http://www.linkedin.com/groups/OpenStack-India-4005742
* Twitter: https://twitter.com/openstackindia
* Slideshare: http://www.slideshare.net/openstackindia
* Coordinators: Deepak Garg ( Email: deepakgarg[dot]iitg[at]gmail[dot]com Launchpad Id: deepak.garg ] Kavit Munshi(@kavitaptira) Ritesh Nanda(@riteshnanda09) Syed Armani(@syedarmani) Sajid Akhtar(@mail2fashion ) Atul Jha(@koolhead17 , "Malyadri Beegala" <malyadri[dot]beegala[at]gmail.com> (Hyderabad events), "Srikanth Minnam" <srikanth[dot]minnam[at]gmail.com> (Hyderabad events)

=== Indonesia ===
* Home page: http://www.openstack-id.org
* Mailing list/forum: openstack-id@googlegroups.com
* Coordinator: Frans Thamura ( frans@meruvian.org ) and (b-frans)

=== Japan ===
* Home Page: http://openstack.jp/
* Mailing List : http://groups.google.com/group/openstack-ja
* Coordinator: Masanori Itoh (thatsdone)

=== Malaysia ===
* Home page: http://www.openstack.my
* Mailing list/forum: https://www.facebook.com/groups/openstackmy
* Coordinator: Khairul Aizat ( fenris@ubuntu.com ) and Mohammad Hafiz ( mypapit@gmail.com )

===Singapore===
*Facebook: https://www.facebook.com/groups/sgopenstack
*Homepage: http://openstack-sg.org
*Google Groups: http://groups.google.com/group/openstack-singapore-users-group
*IRC Channel: #openstack-sg on Freenode
*Launchpad: https://launchpad.net/~openstack-sg
*Coordinator: [https://launchpad.net/~wickedpuppy wickedpuppy]

=== South Korea ===
* Home Page: http://www.openstack.or.kr
* Facebook Group: http://www.facebook.com/groups/openstack.kr/
* Coordinator: [https://launchpad.net/~bluejay-ahn Jaesuk Ahn]

=== Taiwan ===
* Home page: http://groups.google.com/group/twosug2011?hl=zh-TW
* Mailing list: twosug2011@googlegroups.com
* Coordinator: Yoyo Chiang

=== Thailand ===
* Home page: http://blog.sushicloud.cs.tu.ac.th/?cat=14
* Coordinator: Kasidit Chanchio ( kasiditchanchio@gmail.com , kasidit@cs.tu.ac.th )

=== Vietnam ===
* Facebook page: https://www.facebook.com/VietOpenStack
* Official Mailing list: [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-vi Subscribe online], [http://lists.openstack.org/pipermail/openstack-vi/ Archives]
* Coordinator: Hang Tran ( hang.tran@dtt.vn )

==Latin America==

=== Argentina ===
* Google Group: http://groups.google.com/group/openstack-argentina/
* Contact: Leandro Reox of [[MercadoLibre]]
* Official mailing list in Spanish: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-es [http://lists.openstack.org/pipermail/openstack-es/ Archives]

=== Brazil ===
* Google Groups: http://groups.google.com/group/openstack-br
* Facebook Page: http://www.facebook.com/openstackbr
* Twitter: @openstackbr
* Coordinator: [http://wiki.openstack.org/Alexandre%20Haguiar Alexandre Aguiar]

=== Ecuador ===
* Google community: https://plus.google.com/communities/102070666375831873027?hl=es
* Linkedin: http://www.linkedin.com/groups/OpenStack-Ecuador-5012947/about
*Twitter: https://twitter.com/OpenStackEC
* Coordinator: Daniel Núñez
* Official mailing list in Spanish: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-es [http://lists.openstack.org/pipermail/openstack-es/ Archives]

=== Venezuela ===
* Google+: https://plus.google.com/communities/118105990522935078913
* Forum: https://groups.google.com/d/forum/openstack-ve
* Twitter: @openstackve
* Coordinator: Ender Mujica ( emujicad at gmail.com )
* Official mailing list in Spanish: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-es [http://lists.openstack.org/pipermail/openstack-es/ Archives]

==Europe==

=== Austria ===
* Meetup group: http://www.meetup.com/OpenStack-DACH/
* Coordinator: Martin Loschwitz (madkiss)

=== Belgium ===
* LinkedIn Group: http://www.linkedin.com/groups?gid=4817141
* Coordinators: Karel Striegel, Tom Degroote

=== Finland ===
* LinkedIn Group - http://tinyurl.com/openstackfinland
* Twitter - @OpenstackFIN
* Coordinator: Ilkka Turunen - [firstname].[lastname]@jamk.fi
* Mailing list: TBD

=== France ===
* Meetup: http://www.meetup.com/OpenStack-France
* French User Group : http://openstack.fr
* http://cloud-oss-fr.blogspot.com/
* Google Groups: http://groups.google.com/group/openstack-france?hl=fr
* LinkedIn: [http://www.linkedin.com/groups/OpenStack-France-3993018?home=&gid=3993018&trk=anet_ug_hm&goback=.anp_3993018_1310075735312_1 http://www.linkedin.com/groups/OpenStack-France-3993018?home=&gid=3993018&trk=anet_ug_hm&goback=%2Eanp_3993018_1310075735312_1]

=== Germany ===
* OpenStack Germany
:* Meet-up details here: https://www.xing.com/net/pri3642a8x/openstack-germany/
:* Coordinator: Christian Berendt (berendt on launchpad, berendt 'at' b1-systems 'dot' de)
* OpenStack DACH
:* Meetup group: http://www.meetup.com/OpenStack-DACH/
:* Coordinator: Martin Loschwitz (madkiss)

=== Greece ===
* Meetup: http://www.meetup.com/Athens-OpenStack-User-Group
* Coordinator: Thanassis Parathyras

=== Hungary ===
* Meet-up details here: http://www.meetup.com/OpenStack-Hungary-Meetup-Group/
* Coordinator: Marton Kiss (marton 'dot' kiss 'at' xemeti 'dot' com)

=== Nordics (Scandinavia) ===
* Twitter: http://twitter.com/OSNordics
* Meet-up: http://www.meetup.com/OpenStack-User-Group-Nordics/
* LinkedIn: http://www.linkedin.com/groups/OpenStack-Nordics-4764289
* Coordinator - See each Country for it's coordinator.

=== Ireland ===
* Meetup details here: http://www.meetup.com/OpenStack-Ireland
* Twitter - @OpenstackIRL
* Coordinator: Tim Horgan - [firstname].[lastname]@cit.ie

=== Italy ===
* Meetup: http://www.meetup.com/OpenStack-User-Group-Italia/
* Official mailing list: [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-it Subscribe online], [http://lists.openstack.org/pipermail/openstack-it/ Archives]
* Coordinators: Davide Guerri ( davide.guerri@gmail.com ), Martina, Flavio Percoco Premoli, Mariano Cunietti, Mariano Iumiento

=== Poland ===
* Home page: [http://www.openstack.org.pl/ www.openstack.org.pl]
* LinkedIn: [http://www.linkedin.com/groups?home=&gid=4950277&trk=anet_ug_hm OpenStack-Poland]
* Meetup: [http://www.meetup.com/OpenStack-User-Group-Poland/ OpenStack-User-Group-Poland Meetup]
*Google Hangout: [https://www.youtube.com/user/OpenStackPoland www.youtube.com/user/OpenStackPoland]
*Coordinators: Marcin Wiciński (m.wicinski@openstack-poland.org), Rafael Knuth (rafael.knuth@openstack-poland.org)

=== Russia ===
* Home page: http://www.oscloud.ru/
* Facebook: https://www.facebook.com/groups/openstack.russia/
* LinkedIn: http://www.linkedin.com/groups?gid=4109150
* Coordinator: [http://wiki.openstack.org/IlyaAlekseyev Ilya Alekseyev]

=== Serbia ===
* Home page: http://www.openstack.rs
* Coordinator: [https://launchpad.net/~gerzic gerzic]

=== Slovenia ===
* Forum: https://groups.google.com/forum/?fromgroups#!forum/openstack-slovenija
* LinkedIn: http://www.linkedin.com/groups/OpenStack-Slovenija-4793209?trk=myg_ugrp_ovr

=== South Eastern Europe ===
* Forum: https://groups.google.com/forum/#!forum/openstack-south-eastern-europe
* LinkedIn: http://www.linkedin.com/groups/OpenStack-South-Eastern-Europe-4884630?trk=myg_ugrp_ovr

=== Spain ===
* https://plus.google.com/u/0/communities/102652393437279778000
* http://groups.google.com/group/spain-openstack-user-group
* Official mailing list in Spanish: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-es [http://lists.openstack.org/pipermail/openstack-es/ Archives]
* http://twitter.com/openstackspain

=== Sweden ===
* Meetup page: http://www.meetup.com/OpenStack-User-Group-Nordics/
* Twitter: http://twitter.com/OpenStackSE
* Coordinator: [https://launchpad.net/~n-paladi Nicolae Paladi]

=== Switzerland ===
* Home page: http://openstack.ch/
* Coordinator: Thomas Michael Bohnert, [https://launchpad.net/~andy-edmonds Andy Edmonds], [https://launchpad.net/~al-maisan Muharem Hrnjadovic]

=== UK ===
* http://www.meetup.com/OpenStack-London

==Middle East==

=== Cyprus ===
* [http://www.meetup.com/OpenStack-Cyprus-Community/ Meetup Group]
* http://www.meetup.com/OpenStack-Cyprus-Community/
* Coordinator: Sergios Charalambous

=== Egypt ===
* http://groups.google.com/group/egypt-openstack-user-group
* Mailing list: egypt-openstack-user-group@googlegroups.com
* Coordinator: Mohamed El-Refaey ( mohamed@egyptcloudforum.com )

=== Israel ===
* Home page: http://www.openstack-israel.org/
* Meetup details here: http://www.meetup.com/igtcloud/
* Twitter: https://twitter.com/OpenStackIL
* Coordinator: Nati Shalom @natishalom

=== Morocco ===
* Meet-up details here: http://www.meetup.com/Morocco-OpenStack-Users-Group
* Coordinators: Youssef LARGOU

=== Turkey ===
* Coordinator: Ali Bugdayci ( Borsoftware )
* Twitter: https://twitter.com/OpenStackTurkey

=== UAE ===
* Meetup Page: http://www.meetup.com/U-A-E-OpenStack-User-Group/
* Facebook Page: https://www.facebook.com/groups/280298292070983/
* LinkedIn: http://www.linkedin.com/groups/OpenStack-UAE-4653922?gid=4653922
* Twitter: https://twitter.com/OpenStackUAE

== Language specific ==
* Official mailing list in Spanish: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-es [http://lists.openstack.org/pipermail/openstack-es/ Archives]