[RFE] sriov vxlan network support

Bug #1518581 reported by dutiegang
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
neutron
Won't Fix
Wishlist
hongbin

Bug Description

1 problem

now the vxlan can only support ovs vxlan network but donot support sr-iov vxlan network

if support the sr-iov vxlan network, it's need to support create a network with parameter [--provider: physical netwrok], the create network should be as following:

neutron net-create ext_net -provider:network_type vxlan --provider:physical_network physnet1 --provider:segmentation_id 1000

the current neutron DB don't has physical network for vxlan network.

if support the ovs vxlan network, there is no need parm [--provider: physical netwrok]

so the parm [--provider: physical netwrok] is a optional parm forcreating vxlan network

2 how to find this problem
We do a project which need to deploy a sr-iov vxlan network and find that cannot assign the physcial network for vxlan network.
It seems that the neutron don't support sr-iov vxlan network and only support OVS vxlan network

3 how to support sr-iov vxlan network
(1) first it need to create vxlan network associating with physical network

(2) second it need get the mapping relationship between VNI and vlan

4 how this problem is going?
Now we have modified the neuron code and support this question, we hope share our code and commit to neutron project.

5 significance
As everyone knows that the sr-iov performance is better than the ovs.if the SR-IOV support vxlan network, it has a widely potentiall for vxlan network application,

Gary Kotton (garyk)
Changed in neutron:
status: New → Confirmed
importance: Undecided → Wishlist
summary: - sriov vxlan network support
+ [RFE] sriov vxlan network support
Revision history for this message
dutiegang (dutg2002) wrote : Re:[Bug 1518581] Re: sriov vxlan network support

Hi,
    Thank you for your reply.
     As for this issue, I don't know how it will going in the future.
      If possilbe, I hope I can commit the code to slove this question.

Thanks.
Tiegang Du

At 2015-11-22 15:01:21, "Gary Kotton" <email address hidden> wrote:
>** Changed in: neutron
> Status: New => Confirmed
>
>** Changed in: neutron
> Importance: Undecided => Wishlist
>
>** Summary changed:
>
>- sriov vxlan network support
>+ [RFE] sriov vxlan network support
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1518581
>
>Title:
> [RFE] sriov vxlan network support
>
>Status in neutron:
> Confirmed
>
>Bug description:
> 1 problem
>
> now the vxlan can only support ovs vxlan network but donot support sr-
> iov vxlan network
>
> if support the sr-iov vxlan network, it's need to support create a
> network with parameter [--provider: physical netwrok], the create
> network should be as following:
>
> neutron net-create ext_net -provider:network_type vxlan
> --provider:physical_network physnet1 --provider:segmentation_id 1000
>
> the current neutron DB don't has physical network for vxlan network.
>
> if support the ovs vxlan network, there is no need parm [--provider:
> physical netwrok]
>
> so the parm [--provider: physical netwrok] is a optional parm
> forcreating vxlan network
>
>
> 2 how to find this problem
> We do a project which need to deploy a sr-iov vxlan network and find that cannot assign the physcial network for vxlan network.
> It seems that the neutron don't support sr-iov vxlan network and only support OVS vxlan network
>
> 3 how to support sr-iov vxlan network
> (1) first it need to create vxlan network associating with physical network
>
> (2) second it need get the mapping relationship between VNI and vlan
>
> 4 how this problem is going?
> Now we have modified the neuron code and support this question, we hope share our code and commit to neutron project.
>
> 5 significance
> As everyone knows that the sr-iov performance is better than the ovs.if the SR-IOV support vxlan network, it has a widely potentiall for vxlan network application,
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/neutron/+bug/1518581/+subscriptions

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 180 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
Miguel Lavalle (minsel)
Changed in neutron:
status: Expired → Confirmed
Miguel Lavalle (minsel)
Changed in neutron:
assignee: nobody → hongbin (hongbin034)
Revision history for this message
Liansen Zhai (zhailiansen) wrote :

Hi, is it resloved in openstack?

Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

Bug closed due to lack of activity, please feel free to reopen if needed.

Changed in neutron:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.