<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
thank you, Uwe. our provider network actually is untagged, but I did specified VLAN ID when I create our external network and everything still works. will this cause issue later on?
<div class=""><br class="">
</div>
<div class="">
<div class="" style="font-family: Menlo; font-size: 11px; margin: 0px;">eutron net-create --provider:network_type=vlan —provider:segmentation_id=<vlan id> --provider:physical_network=physnet1 --router:external=true public</div>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class="">Yang<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jun 27, 2015, at 11:17 AM, Uwe Sauter <<a href="mailto:uwe.sauter.de@gmail.com" class="">uwe.sauter.de@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">Hi Yang,<br class="">
<br class="">
it depends on whether your provider network is tagged or untagged. If it is untagged (the switch port is an "access"<br class="">
port) then you don't specify the VLAN ID for the external network (as it will get tagged by the switch). If the provider<br class="">
network is tagged (the switch port is a "trunk" port) then you have to configure the VLAN ID because the switch might<br class="">
refuse the traffic (depending if there is a default VLAN ID defined on the switch's port).<br class="">
<br class="">
Regards,<br class="">
<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>Uwe<br class="">
<br class="">
<br class="">
<br class="">
Am 27.06.2015 um 13:47 schrieb YANG LI:<br class="">
<blockquote type="cite" class="">Thank you so much, James! This is so helpful. Another confusion I have is about network_vlan_ranges. Is this network<br class="">
VLAN id range? If so, does it has to match external network? For example, we only have one external VLAN we can use as<br class="">
Our provider network and that VLAN id is 775 (xxx.xxx.xxx.0/26). Should I define network_vlan_ranges as following?<br class="">
<br class="">
[ml2]<br class="">
type_drivers=vlan<br class="">
tenant_network_types = vlan<br class="">
mechanism_drivers=openvswitch<br class="">
#<br class="">
[ml2_type_vlan]<br class="">
#thistellsOpenstackthattheinternalname"physnet1"providesthevlanrange100-199<br class="">
network_vlan_ranges=physnet1:775<br class="">
#<br class="">
<br class="">
Thanks,<br class="">
Yang<br class="">
Sent from my iPhone<br class="">
<br class="">
On Jun 26, 2015, at 8:54 AM, "James Denton" <<a href="mailto:james.denton@rackspace.com" class="">james.denton@rackspace.com</a> <<a href="mailto:james.denton@rackspace.com" class="">mailto:james.denton@rackspace.com</a>>> wrote:<br class="">
<br class="">
<blockquote type="cite" class="">You can absolutely have instances in the same network span different compute nodes. As an admin, you can run ‘nova<br class="">
show <instanceid>’ and see the host in the output:<br class="">
<br class="">
root@controller01:~# nova show 7bb18175-87da-4d1f-8dca-2ef07fee9d21 | grep host<br class="">
| OS-EXT-SRV-ATTR:host | compute02 |<br class="">
<br class="">
That info is not available to non-admin users by default.<br class="">
<br class="">
James <br class="">
<br class="">
<blockquote type="cite" class="">On Jun 26, 2015, at 7:38 AM, YANG LI <<a href="mailto:yangli@clemson.edu" class="">yangli@clemson.edu</a> <<a href="mailto:yangli@clemson.edu" class="">mailto:yangli@clemson.edu</a>>> wrote:<br class="">
<br class="">
Thanks, James for the explanation. it make more sense now. <<a href="http://now.it/" class="">http://now.it/</a>> it is possible that a instances on same<br class="">
tenant network reside on different compute nodes right? how do I tell which compute node a instance is on?
<br class="">
<br class="">
Thanks,<br class="">
Yang<br class="">
<br class="">
<blockquote type="cite" class="">On Jun 24, 2015, at 10:27 AM, James Denton <<a href="mailto:james.denton@rackspace.com" class="">james.denton@rackspace.com</a> <<a href="mailto:james.denton@rackspace.com" class="">mailto:james.denton@rackspace.com</a>>> wrote:<br class="">
<br class="">
Hello.<br class="">
<br class="">
<blockquote type="cite" class="">all three nodes will have eth0 on management/api network. since I am using ml2 plugin with vlan for tenant network,<br class="">
I think all compute node should have eth1 as the second nic on provider network. Is this correct? I understand<br class="">
provider network is for instance to get external access to internet, but how is instance live on compute1<br class="">
communicate with instance live on compute2? are they also go through provider network?<br class="">
</blockquote>
<br class="">
In short, yes. If you’re connecting instances to vlan “provider” networks, traffic between instances on different<br class="">
compute nodes will traverse the “provider bridge”, get tagged out eth1, and hit the physical switching fabric. Your<br class="">
external gateway device could also sit in that vlan, and the default route on the instance would direct external<br class="">
traffic to that device.<br class="">
<br class="">
In reality, every network has ‘provider’ attributes that describe the network type, segmentation id, and bridge<br class="">
interface (for vlan/flat only). So tenant networks that leverage vlans would have provider attributes set by Neutron<br class="">
automatically based on the configuration set in the ML2 config file. If you use Neutron routers that connect to both<br class="">
‘tenant’ vlan-based networks and external ‘provider’ networks, all of that traffic could traverse the same provider<br class="">
bridge on the controller/network node, but would be tagged accordingly based on the network (ie. vlan 100 for<br class="">
external network, vlan 200 for tenant network).<br class="">
<br class="">
Hope that’s not too confusing!<br class="">
<br class="">
James<br class="">
<br class="">
<blockquote type="cite" class="">On Jun 24, 2015, at 8:54 AM, YANG LI <<a href="mailto:yangli@clemson.edu" class="">yangli@clemson.edu</a> <<a href="mailto:yangli@clemson.edu" class="">mailto:yangli@clemson.edu</a>>> wrote:<br class="">
<br class="">
I am working on install openstack from scratch, but get confused with network part. I want to have one controller<br class="">
node, two compute nodes.<br class="">
<br class="">
the controller node will only handle following services:<br class="">
glance-api<br class="">
glance-registry<br class="">
keystone<br class="">
nova-api<br class="">
nova-cert<br class="">
nova-conductor<br class="">
nova-consoleauth<br class="">
nova-novncproxy<br class="">
nova-scheduler<br class="">
qpid<br class="">
mysql<br class="">
neutron-server<br class="">
<br class="">
compute nodes will have following services:<br class="">
neutron-dhcp-agent<br class="">
neutron-l3-agent<br class="">
neutron-metadata-agent<br class="">
neutron-openvswitch-agent<br class="">
neutron-ovs-cleanup<br class="">
openvswtich<br class="">
nova-compute<br class="">
<br class="">
all three nodes will have eth0 on management/api network. since I am using ml2 plugin with vlan for tenant network,<br class="">
I think all compute node should have eth1 as the second nic on provider network. Is this correct? I understand<br class="">
provider network is for instance to get external access to internet, but how is instance live on compute1<br class="">
communicate with instance live on compute2? are they also go through provider network?<br class="">
_______________________________________________<br class="">
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" class="">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br class="">
Post to : <a href="mailto:openstack@lists.openstack.org" class="">openstack@lists.openstack.org</a> <<a href="mailto:openstack@lists.openstack.org" class="">mailto:openstack@lists.openstack.org</a>><br class="">
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" class="">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br class="">
</blockquote>
<br class="">
</blockquote>
<br class="">
</blockquote>
<br class="">
</blockquote>
<br class="">
<br class="">
_______________________________________________<br class="">
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" class="">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br class="">
Post to : <a href="mailto:openstack@lists.openstack.org" class="">openstack@lists.openstack.org</a><br class="">
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" class="">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br class="">
<br class="">
</blockquote>
<br class="">
_______________________________________________<br class="">
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" class="">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br class="">
Post to : <a href="mailto:openstack@lists.openstack.org" class="">openstack@lists.openstack.org</a><br class="">
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" class="">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>