Thanks Kevin!

I'll dig into neutron.agent.linux.interface to see how it works. Before that, 
would you give me any previews about what steps should be taken to add a veth 
to a existed Neutron network?


Furthermore, is it Neutron who add a veth to ovs bridge or is it the Neutron 
caller? (such as Nova)


Who's adding flows to ovs bridge? Neutron or caller?


Regards,
Dastan 
 
------------------ Original ------------------
From:  "Kevin Benton"<[email protected]>;
Date:  Fri, May 12, 2017 10:45 AM
To:  "duhongwei"<[email protected]>; 
Cc:  "openstack"<[email protected]>; "Vallachorum 
Tyranorum"<[email protected]>; 
Subject:  Re: [Openstack] How to utilize Neutron independently with veths

 
You want to look in neutron.agent.linux.interface to see how things are plugged 
into OVS. That's the module used by the L3 agent to plug into OVS/linux 
bridge/etc. 

There is a well defined interface name format corresponding to the port ID and 
the port ID, Mac address, and a couple of other things I can't recall are set 
in ovsdb to help the agent identify the port as something it should care about. 


On May 9, 2017 04:49, "duhongwei" <[email protected]> wrote:


Thanks Dan!


I have to write a customized CNI plugin for our product, so it's better if I 
know more operation details about how to interact with Neutron manually 
(consider myself as Nova). Therefore Kuryr is not my best option right now, but 
it's cool!


Regards,
Dastan
 
------------------ Original ------------------
From:  "Vallachorum Tyranorum"<[email protected]>;
Date:  Tue, May 9, 2017 04:08 PM
To:  "duhongwei"<[email protected]>; 
"openstack"<[email protected]>; 

Subject:  Re: [Openstack] How to utilize Neutron independently with veths

 
Hi,

Please take a look at Kuryr. Maybe this is what you are looking for.


Dan. 


On Tue, May 9, 2017 at 10:17 AM duhongwei <[email protected]> wrote:

Hi everyone,


I'm new to OpenStack and currently interested in the Neutron part of it. What 
I'm seeking is some advice about how to utilize Neutron independently, to build 
a virtual network, for Docker containers maybe.


Suppose I've already got Neutron and Keystone installed on controller node and 
compute nodes. I guess the following steps are required to test a virtual 
network.


1) create a network
2) create a subnet
3) create two pairs of veths (each pair represents a vm)
for each pair of them:
4) create a port for one end of the veth pair (passing veth's mac address as a 
parameter)
5) attach another end of the veth pair to ovs bridge
6) ping from one veth pair to another


The above is my general idea, don't know if it is correct and don't know the 
operation details either.
Expecting your suggestions, any links are appreciated.


Regards,
Dastan


_______________________________________________
 Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
 Post to     : [email protected]
 Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
 
 


_______________________________________________
 Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
 Post to     : [email protected]
 Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to