<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
</head>
<body>
<p dir="ltr">You seem to be imagining things. Or may be it was my way of explaining that confused you. You don't need IP address anywhere. Flat/vlan are things needed by neutron. You only have to just create the bridges and leave them there. The rest is done
by neutron.<br>
</p>
<p dir="ltr">Sent using <a href="https://cloudmagic.com/k/d/mailapp?ct=pa&cv=1.0.10.8&pv=4.2.2">
CloudMagic</a><a href="https://cloudmagic.com/k/d/mailapp?ct=pa&cv=1.0.10.8&pv=4.2.2">
</a></p>
<br>
<br>
<div class="cm_quote" style=" color: #787878">On Sat, Apr 05, 2014 at 11:16 AM, Erich Weiler <<a href="mailto:weiler@soe.ucsc.edu">weiler@soe.ucsc.edu</a>> wrote:</div>
<br>
<div id="oldcontent" style="background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: rgb(255, 255, 255); background-position: initial initial; background-repeat: initial initial; ">
<blockquote style="">
<p dir="ltr">Thanks, this is getting me closer! I still have a few questions: <br>
<br>
When I configure the bridges (for br-ex and br-int), do those bridges <br>
need to be configured with IP addressed? Or can I just configure the <br>
interfaces without IP addresses? I guess at least for the br-ex, it <br>
needs to know the gateway, netmask, etc for the external network, I <br>
assume you define that in /etc/sysconfig/network-scripts/ifcfg-br-ex? <br>
(assuming a redhat installation). No VLANs on br-ex, it's a flat network. <br>
<br>
And then I configure br-int without any ip/netmask info because it will <br>
use VLANs and do that dynamically as needed? <br>
<br>
And then, I can do (on the network node): <br>
<br>
ovs-vsctl add-br br-int <br>
ovs-vsctl add-br br-ex <br>
<br>
and then... <br>
<br>
ovs-vsctl add-port br-ex eth1 <br>
ovs-vsctl add-port br-int eth2 <br>
<br>
and in /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini on the <br>
network node I have: <br>
<br>
[ovs] <br>
tenant_network_type = vlan <br>
network_vlan_ranges = Intnet:100:200 <br>
bridge_mappings = Extnet:br-ex,Intnet:br-int <br>
<br>
Is that the right idea for a flat external network and using VLANs on <br>
the internal network? <br>
<br>
Thanks again, this is kind of tricky, but I feel I'm getting close to <br>
getting it straight... Sorry if I'm being slow, but I really appreciate <br>
the help! <br>
<br>
On 4/2/14, 11:05 PM, Ageeleshwar Kandavelu wrote: <br>
> Maruf was correct. <br>
> <br>
> Also in your plugin.ini you have associate each physical network to a <br>
> bridge. And each of those bridges should have one physical network <br>
> interface attached. <br>
> <br>
> In my previous mail i gave an example where I associated Extnet to <br>
> br-ex. Then add eth2 to br-ex. Then your external network(ext-net) would <br>
> be overlaid on top of Extnet, bridged to br-ex, then traffic flows <br>
> outside through eth2. <br>
> <br>
> Thank you, <br>
> Ageeleshwar K <br>
> ------------------------------------------------------------------------ <br>
> *From:* Md. Maruful Hassan [mrf.mnm@gmail.com] <br>
> *Sent:* Thursday, April 03, 2014 9:29 AM <br>
> *To:* Erich Weiler <br>
> *Cc:* Ageeleshwar Kandavelu; Alex Yang; openstack@lists.openstack.org <br>
> *Subject:* Re: [Openstack] Neutron network node setup <br>
> <br>
> You need to use 'flat' instead of 'local' and specify physical_network . <br>
> so modify <br>
> <br>
> neutron net-create ext-net --provider:network_type=local --shared <br>
> --router:external=True <br>
> <br>
> to <br>
> <br>
> neutron net-create ext-net --provider:network_type=flat <br>
> --provider:physical_network Extnet --shared --router:external=True <br>
> <br>
> Extnet is the name you configured in plugin.ini as bridge_mapping <br>
> <br>
> - Maruf <br>
> <br>
> -- <br>
> m@ruf <br>
> <br>
> <br>
> On Thu, Apr 3, 2014 at 9:37 AM, Erich Weiler <weiler@soe.ucsc.edu <br>
> <mailto:weiler@soe.ucsc.edu>> wrote: <br>
> <br>
> Hi Ageeleshwar, <br>
> <br>
> I *think* I see what you are saying - is this correct? First, I <br>
> create a flat external network: <br>
> <br>
> # neutron net-create ext-net --provider:network_type=local --shared <br>
> --router:external=True <br>
> <br>
> <br>
> Created a new network: <br>
> +---------------------------+-__------------------------------__-------+ <br>
> | Field | Value | <br>
> +---------------------------+-__------------------------------__-------+ <br>
> | admin_state_up | True | <br>
> | id | 71b4b5b9-e744-4c67-9b62-__4f64ab727e47 | <br>
> | name | ext-net | <br>
> | provider:network_type | local | <br>
> | provider:physical_network | | <br>
> | provider:segmentation_id | | <br>
> | router:external | True | <br>
> | shared | True | <br>
> <br>
> | status | ACTIVE | <br>
> | subnets | | <br>
> | tenant_id | 36687b1d611740bd9e7309432b22db__cd | <br>
> +---------------------------+-__------------------------------__-------+ <br>
> <br>
> # neutron subnet-create ext-net --allocation-pool <br>
> start=134.145.112.10,end=134.__145.112.100 --gateway=134.145.112.1 <br>
> --enable_dhcp=False 134.145.112.0/24 <http://134.145.112.0/24> <br>
> <br>
> Created a new subnet: <br>
> +------------------+----------__------------------------------__--------------+
<br>
> | Field | Value <br>
> | <br>
> +------------------+----------__------------------------------__--------------+
<br>
> | allocation_pools | {"start": "134.145.112.10", "end": <br>
> "134.145.112.100"} | <br>
> | cidr | 134.145.112.0/26 <http://134.145.112.0/26> <br>
> | <br>
> | dns_nameservers | <br>
> | <br>
> | enable_dhcp | False <br>
> | <br>
> | gateway_ip | 134.145.112.1 <br>
> | <br>
> | host_routes | <br>
> | <br>
> | id | 6082cdb3-98bc-4fbe-a0fb-__ff264ea7384f <br>
> | <br>
> | ip_version | 4 <br>
> | <br>
> | name | <br>
> | <br>
> | network_id | 71b4b5b9-e744-4c67-9b62-__4f64ab727e47 <br>
> | <br>
> | tenant_id | 36687b1d611740bd9e7309432b22db__cd <br>
> | <br>
> +------------------+----------__------------------------------__--------------+
<br>
> <br>
> Create a router from ext-to-int for my demo tenant: <br>
> <br>
> # neutron router-create ext-to-int --tenant-id <br>
> f7e61747885045d8b266a161310c00__94 <br>
> Created a new router: <br>
> +-----------------------+-----__------------------------------__---+ <br>
> | Field | Value | <br>
> +-----------------------+-----__------------------------------__---+ <br>
> | admin_state_up | True | <br>
> | external_gateway_info | | <br>
> | id | 4ca4292c-8954-4f21-acd6-__b0044e0d02cb | <br>
> | name | ext-to-int | <br>
> | status | ACTIVE | <br>
> | tenant_id | f7e61747885045d8b266a161310c00__94 | <br>
> +-----------------------+-----__------------------------------__---+ <br>
> <br>
> Set my router gateway: <br>
> <br>
> # neutron router-gateway-set 4ca4292c-8954-4f21-acd6-__b0044e0d02cb <br>
> 71b4b5b9-e744-4c67-9b62-__4f64ab727e47 <br>
> <br>
> Set gateway for router 4ca4292c-8954-4f21-acd6-__b0044e0d02cb <br>
> <br>
> Create a tenant-network with a VLAN: <br>
> <br>
> # neutron net-create --tenant-id f7e61747885045d8b266a161310c00__94 <br>
> demo-net --provider:network_type vlan --provider:physical_network <br>
> physnet1 --provider:segmentation_id 201 <br>
> <br>
> <br>
> Created a new network: <br>
> +---------------------------+-__------------------------------__-------+ <br>
> | Field | Value | <br>
> +---------------------------+-__------------------------------__-------+ <br>
> | admin_state_up | True | <br>
> | id | 37190389-df4b-49c0-81b9-__05aa6411a81b | <br>
> | name | demo-net | <br>
> <br>
> | provider:network_type | vlan | <br>
> | provider:physical_network | physnet1 | <br>
> | provider:segmentation_id | 201 | <br>
> <br>
> | shared | False | <br>
> | status | ACTIVE | <br>
> | subnets | | <br>
> | tenant_id | f7e61747885045d8b266a161310c00__94 | <br>
> +---------------------------+-__------------------------------__-------+ <br>
> <br>
> Create demo-net subnet: <br>
> <br>
> # neutron subnet-create --tenant-id <br>
> f7e61747885045d8b266a161310c00__94 demo-net 10.200.0.0/16 <br>
> <http://10.200.0.0/16> --gateway 10.200.0.1 <br>
> <br>
> Created a new subnet: <br>
> +------------------+----------__------------------------------__----------+
<br>
> | Field | Value | <br>
> +------------------+----------__------------------------------__----------+
<br>
> | allocation_pools | {"start": "10.200.0.2", "end": "10.200.255.254"} | <br>
> | cidr | 10.200.0.0/16 <http://10.200.0.0/16> <br>
> | <br>
> | dns_nameservers | | <br>
> | enable_dhcp | True | <br>
> | gateway_ip | 10.200.0.1 | <br>
> | host_routes | | <br>
> | id | da53e0df-fb00-46ad-a709-__6eaeda13e23f <br>
> | <br>
> | ip_version | 4 | <br>
> | name | | <br>
> | network_id | 37190389-df4b-49c0-81b9-__05aa6411a81b <br>
> | <br>
> | tenant_id | f7e61747885045d8b266a161310c00__94 <br>
> | <br>
> +------------------+----------__------------------------------__----------+
<br>
> <br>
> Set the router for demo-net: <br>
> <br>
> # neutron router-interface-add <br>
> 4ca4292c-8954-4f21-acd6-__b0044e0d02cb <br>
> da53e0df-fb00-46ad-a709-__6eaeda13e23f <br>
> <br>
> Added interface 250215bf-fe8b-40ed-aeb9-__e284427ec432 to router <br>
> 4ca4292c-8954-4f21-acd6-__b0044e0d02cb. <br>
> <br>
> And that should work yes? With a flat ext-net and a VLAN-based <br>
> internal net for my tenant net demo-net? <br>
> <br>
> Thanks so much for you help! The guides don't really go into this <br>
> kind of detail... <br>
> <br>
> -erich <br>
> <br>
> <br>
> On 4/2/14, 3:07 AM, Ageeleshwar Kandavelu wrote: <br>
> <br>
> Make your external network flat. If you do so there wont be any <br>
> vlan tag <br>
> on packets reaching your external network. <br>
> <br>
> in you plugin.ini you put something like this <br>
> network_vlan_ranges = Intnet1:100:200,Extnet <br>
> bridge_mappings = Intnet1:br-eth1,Extnet:br-ex <br>
> <br>
> This means you would use vlan id 100 to 200 on openstack networks <br>
> created on top of Intnet1. <br>
> <br>
> On Extnet you would not use any vlan. <br>
> <br>
> Then you say that to all traffic on network created on Intnet1 <br>
> should be <br>
> bridged to br-eth1. Then you would add eth1 to br-eth1. <br>
> <br>
> Then you say all traffic for Extnet should be bridged to br-ex. <br>
> Then you <br>
> have to add a physical interface say eth2 to br-ex. <br>
> <br>
> Finally you can create an external network in openstack with <br>
> physical_network=Extnet. <br>
> <br>
> You just said that all internal network shall be created and <br>
> Intnet1 and <br>
> allocated vlan from 100 to 200. <br>
> External network shall be overlaid on top of Extnet and no vlans. <br>
> <br>
> Hope it makes sense. <br>
> <br>
> Ageeleshwar K <br>
> <br>
> <br>
> ------------------------------__------------------------------__------------
<br>
> *From:* Alex Yang [alex890714@gmail.com <br>
> <mailto:alex890714@gmail.com>] <br>
> *Sent:* Wednesday, April 02, 2014 7:09 AM <br>
> *To:* Erich Weiler <br>
> *Cc:* openstack@lists.openstack.org <br>
> <mailto:openstack@lists.openstack.org> <br>
> *Subject:* Re: [Openstack] Neutron network node setup <br>
> <br>
> <br>
> Hi Erich, <br>
> <br>
> I think this following articles may helpful for you. <br>
> <br>
> http://developer.rackspace.__com/blog/categories/__networking/ <br>
> <http://developer.rackspace.com/blog/categories/networking/> <br>
> <br>
> <br>
> <br>
> 2014-04-02 5:59 GMT+08:00 Erich Weiler <weiler@soe.ucsc.edu <br>
> <mailto:weiler@soe.ucsc.edu> <br>
> <mailto:weiler@soe.ucsc.edu <mailto:weiler@soe.ucsc.edu>>>: <br>
> <br>
> <br>
> Hey Y'all, <br>
> <br>
> I'm setting up a dedicated neutron network node and I'm <br>
> having a bit <br>
> of trouble understanding the way the networks work. On the <br>
> network <br>
> node I have one interface on the public net (eth0), one <br>
> interface on <br>
> the private net (eth1) and I'm following these guides to <br>
> set it up. <br>
> <br>
> My plan is to have eth0 on the public network, no VLAN <br>
> magic there <br>
> or anything. eth1 will be the data interface, and it will be <br>
> connected to a trunk switchport so it can use VLANs for tenant <br>
> isolation (OVS VLAN plugin). <br>
> <br>
> I ran this command to set up ext-net: <br>
> <br>
> neutron net-create ext-net --router:external=True <br>
> <br>
> Created a new network: <br>
> <br>
> +---------------------------+-____----------------------------__--__-------+
<br>
> | Field | Value <br>
> | <br>
> <br>
> +---------------------------+-____----------------------------__--__-------+
<br>
> | admin_state_up | True <br>
> | <br>
> | id | <br>
> a5599b54-dbfc-42fa-b5b9-____e8ebd574ded0 | <br>
> <br>
> | name | ext-net <br>
> | <br>
> | provider:network_type | vlan <br>
> | <br>
> | provider:physical_network | physnet1 <br>
> | <br>
> | provider:segmentation_id | 200 <br>
> | <br>
> | router:external | True <br>
> | <br>
> | shared | False <br>
> | <br>
> | status | ACTIVE <br>
> | <br>
> | subnets | <br>
> | <br>
> | tenant_id | <br>
> 36687b1d611740bd9e7309432b22db____cd | <br>
> <br>
> +---------------------------+-____----------------------------__--__-------+
<br>
> <br>
> <br>
> <br>
> But, I don't think network_type=vlan right? As eth0 just <br>
> sits right <br>
> on a public network? Should network_type=local instead? Also, <br>
> should physical_network equal null, and also <br>
> segmentation_id equal <br>
> null as well? <br>
> <br>
> I would understand type=vlan and seg_id and such for a tenant <br>
> network, but for ext-net? <br>
> <br>
> Any hints would be greatly appreciated...! <br>
> <br>
> -erich <br>
> <br>
> ___________________________________________________ <br>
> Mailing list: <br>
> http://lists.openstack.org/____cgi-bin/mailman/listinfo/____openstack <br>
> <http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack> <br>
> <br>
> <br>
> <http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack <br>
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>> <br>
> Post to : openstack@lists.openstack.org <br>
> <mailto:openstack@lists.openstack.org> <br>
> <mailto:openstack@lists.__openstack.org <br>
> <mailto:openstack@lists.openstack.org>> <br>
> Unsubscribe : <br>
> http://lists.openstack.org/____cgi-bin/mailman/listinfo/____openstack <br>
> <http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack> <br>
> <br>
> <http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack <br>
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>> <br>
> <br>
> <br>
> <br>
> <br>
> -- <br>
> ÑîÓê <br>
> Email: alex890714@gmail.com <mailto:alex890714@gmail.com> <br>
> <mailto:alex890714@gmail.com <mailto:alex890714@gmail.com>> <br>
> <br>
> GitHub: https://github.com/AlexYangYu <br>
> Weibo: http://www.weibo.com/__alexyangyu <br>
> <http://www.weibo.com/alexyangyu> <br>
> http://www.csscorp.com/common/__email-disclaimer.php <br>
> <http://www.csscorp.com/common/email-disclaimer.php> <br>
> <br>
> <br>
> _________________________________________________ <br>
> Mailing list: <br>
> http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack <br>
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack> <br>
> Post to : openstack@lists.openstack.org <br>
> <mailto:openstack@lists.openstack.org> <br>
> Unsubscribe : <br>
> http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack <br>
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack> <br>
> <br>
> <br>
> http://www.csscorp.com/common/email-disclaimer.php <br>
</p>
</blockquote>
</div>
http://www.csscorp.com/common/email-disclaimer.php
</body>
</html>