[Openstack] Introducing Mellanox Quantum Plugin

[Irena Berezovsky]

Hi all,
Mellanox Technologies, in our support of Openstack,  is releasing the Mellanox 
Quantum Plugin. This is following our previous announcement of Cinder Transport 
Acceleration via iSER (iSCSI over RDMA).
The Openstack Mellanox Quantum plugin supports Mellanox embedded switch 
(eSwitch) functionality as part of the VPI (Ethernet/InfiniBand) network 
adapter.
The Mellanox Quantum Plugin allows hardware vNICs (mapped to PCI 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 or 
directly as a Virtual PCI device to the guest, allowing higher performance and 
advanced features such as RDMA.
Hardware based switching, provides better performance, functionality, and 
security/isolation for virtual cloud environments.
The current, initial release, of the plugin supports VLAN and Flat networking. 
The plugin supports 'provider' and 'router' extension.
The plugin is implemented according to the Plugin-Agent pattern.
The plugin supports L3 functionality by maintaining compatibility with the 
Linux Bridge plugin to be executed by existing agents.
Nova Vif driver is included.
The plugin L2 Agent should be executed on the nodes equipped with Mellanox 
ConnectX-2 or ConnectX-3 adapters.
Mellanox Quantum Plugin repository:  http://www.github.com/mellanox/mlnx

Mellanox Quantum Plugin overview and configuration options: 
https://github.com/mellanox/mlnx/blob/master/README

A detailed installation guide: 
https://github.com/mellanox/mlnx/blob/master/install_guide

The current version works with Folsom Release. We are working on support for 
Grizzly.

Future version of the plugin will support IB networking, 'port-binding' 
extension and more advanced features as support for OpenFlow API to control 
granular QoS and Security, and monitor the embedded switch and vNICs 
functionality.

Any comments or suggestions are more than welcome.
We will be glad to assist anyone who would like to review or test. Contact me 
or use openst...@mellanox.com for support/tech 
questions.

Thanks,
Irena & Mellanox Openstack Team
Mellanox Technologies Ltd.
Follow us on Twitter and Facebook
http://twitter.com/mellanoxtech



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] How to Solve InfinitBand Adaptor Driver under Ubuntu 12.04?

[Irena Berezovsky]

Hi Vladimir,
The driver will provide support for both.
BR,
Irena

-Original Message-
From: Vladimir [mailto:vladi...@zadarastorage.com] 
Sent: Sunday, December 30, 2012 8:46 AM
To: Irena Berezovsky
Cc: Narayan Desai; changliwei07; openstack
Subject: Re: [Openstack] How to Solve InfinitBand Adaptor Driver under Ubuntu 
12.04?

Hi Irena,

Will you provide drivers for 12.04 as well? And does it support SR-IOV?

Thanks,
-Vladimir
Zadara Storage


On Dec 29, 2012, at 10:41 PM, Irena Berezovsky  wrote:

> Hi,
> We are going to provide a Cinder patch to enable iSER in the next few days, 
> it will allow users 5x faster bandwidth compared to using iSCSI TCP.
> The coming OFED 2.0 version (in couple of months) will allow Eth emulation 
> over IPoIB (called eIPoIB). If you want early access to it you can contact me 
> or openst...@mellanox.com.
> It will also include SR-IOV support allowing RDMA access and low-latency 
> access from guest VMs.
> We are planning  to publish a Mellanox Quantum plug-in soon that will 
> allow simple integration with our InfiniBand and Ethernet hardware 
> (and will have SR-IOV and NIC based IO Virtualization as part of it)
> 
> I hope this helps. In case you need more details, please drop me an email.
> BR,
> Irena
> 
> -Original Message-
> From: openstack-bounces+irenab=mellanox@lists.launchpad.net 
> [mailto:openstack-bounces+irenab=mellanox@lists.launchpad.net] On 
> Behalf Of Narayan Desai
> Sent: Tuesday, December 25, 2012 4:09 PM
> To: changliwei07
> Cc: openstack
> Subject: Re: [Openstack] How to Solve InfinitBand Adaptor Driver under Ubuntu 
> 12.04?
> 
> We're using IB (QDR connectX and connectX2) on our system. It turns out that 
> the drivers included in version 3.2 of the linux kernel are fine. I've built 
> a ppa for updated management tools though; all of those bits are ancient in 
> precise. The ppa is here:
> 
> http://launchpad.net/~narayan-desai/+archive/infiniband
> 
> One word of warning; you'll only be able to use IPOIB for connectivity 
> between the hypervisor nodes and the openstack service nodes; getting to VMs 
> requires full ethernet compatibility, which IPOIB doesn't provide. You will 
> be able to use the IPOIB for fast image transfers and really fast volume 
> storage if you have it. Turning on iSER helps a lot with volume bandwidth, 
> but requires a patch to nova compute.
> -nld
> 
> On Tue, Dec 25, 2012 at 7:03 AM,   wrote:
>> Hi,
>> Merry Christmas !
>> Have you even tried to use infinitband network in OpenStack  base on 
>> Ubuntu 12.04?
>> In recent two days, I  want to use IPoIB in  Ubuntu, but the big 
>> problem is the driver of IB, The OFED src is special for enterprise 
>> distribution only, such as (RHEL and SLES ), even the so called 
>> source code  archive is a rpmbuild-tree-like structure. Then the 
>> question is how to solve the driver problem  in ubuntu 12.04.
>> 
>> 
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] How to Solve InfinitBand Adaptor Driver under Ubuntu 12.04?

[Irena Berezovsky]

Hi,
We are going to provide a Cinder patch to enable iSER in the next few days, it 
will allow users 5x faster bandwidth compared to using iSCSI TCP.
The coming OFED 2.0 version (in couple of months) will allow Eth emulation over 
IPoIB (called eIPoIB). If you want early access to it you can contact me or 
openst...@mellanox.com.
It will also include SR-IOV support allowing RDMA access and low-latency access 
from guest VMs.
We are planning  to publish a Mellanox Quantum plug-in soon that will allow 
simple integration with our InfiniBand and Ethernet hardware (and will have 
SR-IOV and NIC based IO Virtualization as part of it)  

I hope this helps. In case you need more details, please drop me an email.
BR,
Irena

-Original Message-
From: openstack-bounces+irenab=mellanox@lists.launchpad.net 
[mailto:openstack-bounces+irenab=mellanox@lists.launchpad.net] On Behalf Of 
Narayan Desai
Sent: Tuesday, December 25, 2012 4:09 PM
To: changliwei07
Cc: openstack
Subject: Re: [Openstack] How to Solve InfinitBand Adaptor Driver under Ubuntu 
12.04?

We're using IB (QDR connectX and connectX2) on our system. It turns out that 
the drivers included in version 3.2 of the linux kernel are fine. I've built a 
ppa for updated management tools though; all of those bits are ancient in 
precise. The ppa is here:

http://launchpad.net/~narayan-desai/+archive/infiniband

One word of warning; you'll only be able to use IPOIB for connectivity between 
the hypervisor nodes and the openstack service nodes; getting to VMs requires 
full ethernet compatibility, which IPOIB doesn't provide. You will be able to 
use the IPOIB for fast image transfers and really fast volume storage if you 
have it. Turning on iSER helps a lot with volume bandwidth, but requires a 
patch to nova compute.
 -nld

On Tue, Dec 25, 2012 at 7:03 AM,   wrote:
> Hi,
> Merry Christmas !
> Have you even tried to use infinitband network in OpenStack  base on 
> Ubuntu 12.04?
> In recent two days, I  want to use IPoIB in  Ubuntu, but the big 
> problem is the driver of IB, The OFED src is special for enterprise 
> distribution only, such as (RHEL and SLES ), even the so called source 
> code  archive is a rpmbuild-tree-like structure. Then the question is 
> how to solve the driver problem  in ubuntu 12.04.
> 
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] VM network adapter hotplug

[Irena Berezovsky]

Hi,
I tried to find a way to add a network adapter to running VM without needing to 
restart it but could not find an API to apply it.
As I understand KVM allows such functionality : 
https://fedoraproject.org/wiki/Features/KVM_NIC_Hotplug
Is it supported or considered for Folsom?

Thanks a lot,
Irena
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Netstack] question on get_network_details api call

[Irena Berezovsky]

Dan, thank you very much for pointing to nova examples.
Following these examples and also 
http://wiki.openstack.org/WritingRequestExtensions guidelines I understand how 
to add extension to nova, but still has questions how to add it to Quantum.
Nova extensions make use of nova.api.openstack.extensions module and Quantum 
has its own implementation.
Can you please point to some documentation regarding writing Quantum extensions?
Thanks a lot,
Irena

From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Saturday, June 02, 2012 8:57 PM
To: Robert Kukura
Cc: Irena Berezovsky; Salvatore Orlando; netst...@lists.launchpad.net; 
openstack@lists.launchpad.net
Subject: Re: [Netstack] question on get_network_details api call

Hi Irena, Bob, Salvatore,

Just catching up the thread, and looping the netstack and openstack lists in as 
well, as this info is general useful in my opinion.

Our model with Quantum, like Nova, is that it is definitely ok to extend the 
content of a core object with additional attributes.  These attributes should 
be formatted properly as extended attribute, so that the "key" of the attribute 
is :

This is done pretty commonly within Nova.  Two simple examples are:
- nova/api/openstack/compute/contrib/scheduler_hints.py
- nova/api/openstack/compute/contrib/extended_status.py

I do not believe you need to (or should) modify the view-builder code for the 
core object when you want to add an extended attribute to it.  Instead, the 
extension framework has you write a wsgi controller specific to the extension 
that is inserted as its own stage into the wsgi request and response processing 
pipeline.  Thus, when the request is passed in, your code gets a chance to 
parse the data, and the the response is passed back, your code gets a chance to 
add data to it.

Using the Nova code as example is probably the best bet if you can find a good 
example within quantum.  Quantum's extension framework (and several other 
openstack projects) all use essentially the same model.

Dan


On Sat, Jun 2, 2012 at 8:43 AM, Robert Kukura 
mailto:rkuk...@redhat.com>> wrote:
On 06/02/2012 05:02 AM, Irena Berezovsky wrote:
> Hi,
> Bob, Dan,
> I ran into following wiki page:
> http://wiki.openstack.org/QuantumAPIExtensionsaction=AttachFile&do=view&target=quantum_api_extension.pdf
> 'port profile' is exactly what I was looking for to expose in the plugin.
> I would like to add the port profile retrieval capability and contribute the 
> implementation.
>
> Can you please advise if there is any disagreement on getting it into core 
> API? Shall I do it via extension?
> Bob, seems that you are dealing with similar issues.
> What do you suggest?
>
> Thanks a lot,
> Irena
Irena,

I'm not sure there is any consensus around using a "network profile" for
this. I did see that document as well as archived discussion about
defining "port profile" and "network profile" as extensible collections
of attributes. But the existing "port profile" extension looks to be
Cisco-specific, and seems to serve a somewhat different purpose.

My current thinking is that we'd be better off long term following the
lead of Nova and other projects in supporting "extension data" within
the existing resources instead of requiring introduction of a new
resource just to hold plugin-specific attributes.

But, in the short term, it might make the most sense for each extension
just to provide its own resource extension with its attributes. That's
what I'm tentatively planning to do for the provider-network blueprint,
but would reconsider if there was consensus that either the "extension
data" support or a more general "network profile" should be added now.

-Bob



--
~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com<http://www.nicira.com>
twitter: danwendlandt
~~~

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp