<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="">
Thanks, James for the explanation. it make more sense <a href="http://now.it" class="">
now.</a> it is possible that a instances on same tenant network reside on different compute nodes right? how do I tell which compute node a instance is on?
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class="">Yang<br class="">
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jun 24, 2015, at 10:27 AM, James Denton <<a href="mailto:james.denton@rackspace.com" class="">james.denton@rackspace.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div 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, I think all compute node should have eth1 as the second nic on provider network. Is this correct? I understand
provider network is for instance to get external access to internet, but how is instance live on compute1 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 compute nodes will traverse the “provider bridge”, get tagged out eth1, and hit the physical switching fabric. Your external gateway device could
also sit in that vlan, and the default route on the instance would direct external traffic to that device.<br class="">
<br class="">
In reality, every network has ‘provider’ attributes that describe the network type, segmentation id, and bridge interface (for vlan/flat only). So tenant networks that leverage vlans would have provider attributes set by Neutron automatically based on the configuration
set in the ML2 config file. If you use Neutron routers that connect to both ‘tenant’ vlan-based networks and external ‘provider’ networks, all of that traffic could traverse the same provider bridge on the controller/network node, but would be tagged accordingly
based on the network (ie. vlan 100 for 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>> 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 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, I think all compute node should have eth1 as the second nic on provider network. Is this correct? I understand provider network is for instance
to get external access to internet, but how is instance live on compute1 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><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="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</body>
</html>