[RFE] sriov vxlan network support
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:
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,
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
summary: |
- sriov vxlan network support + [RFE] sriov vxlan network support |
Changed in neutron: | |
status: | Expired → Confirmed |
Changed in neutron: | |
assignee: | nobody → hongbin (hongbin034) |
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: /bugs.launchpad .net/bugs/ 1518581 network_ type vxlan physical_ network physnet1 --provider: segmentation_ id 1000 /bugs.launchpad .net/neutron/ +bug/1518581/ +subscriptions
>** 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:/
>
>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:
> --provider:
>
> 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:/