<div dir="ltr"><div class="gmail_default" style="font-family:'times new roman',serif">By "defined a network space for your instances", does that mean going through the process as described in <a href="http://docs.openstack.org/icehouse/install-guide/install/yum/content/neutron-ml2-compute-node.html" target="_blank">http://docs.openstack.org/icehouse/install-guide/install/yum/content/neutron-ml2-compute-node.html</a>?</div>
<div class="gmail_default" style="font-family:'times new roman',serif"><br></div><div class="gmail_default" style="font-family:'times new roman',serif">I got part way through that when I realized that the procedure was going to bridge packets through neutron. That's not what I want. I want the packets to go directly to the physical router. For example, I have two tenants, with IP addresses <a href="http://10.50.15.80/24" target="_blank">10.50.15.80/24</a> and 10.50.18.15.90/24.and the router is at 10.50.15.1. There is a nice picture of what I am trying to do at <a href="http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#nova_network_traffic_in_cloud" target="_blank">http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#nova_network_traffic_in_cloud</a> . But if the hypervisor doesn't present a virtual device to the guests, then nothing else is going to happen. The network troubleshooting guide <a href="http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#nova_network_traffic_in_cloud" target="_blank">http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html#nova_network_traffic_in_cloud</a> does not explain what to do if the virtual NIC is missing.</div>
<div class="gmail_default" style="font-family:'times new roman',serif"><br></div><div class="gmail_default" style="font-family:'times new roman',serif"><br></div><div class="gmail_default" style="font-family:'times new roman',serif">
Thank you</div><div class="gmail_default" style="font-family:'times new roman',serif"><br></div><div class="gmail_default" style="font-family:'times new roman',serif">
Jeff</div><div class="gmail_default" style="font-family:'times new roman',serif"><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 15, 2014 at 9:38 AM, Abel Lopez <span dir="ltr"><<a href="mailto:alopgeek@gmail.com" target="_blank">alopgeek@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Curious if you’ve defined a network space for your instances. If you’re using the traditional flat_network, this is known as the ‘fixed_address’ space.<div>
If you’re using neutron, you would need to create a network and a subnet (and router with gateway, etc). You’d then assign the instance to a network at launch time.</div><div><br></div><div><br><div><div>On Aug 15, 2014, at 9:17 AM, Jeff Silverman <<a href="mailto:jeff@sweetlabs.com" target="_blank">jeff@sweetlabs.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><div class="gmail_default" style="font-family:times new roman,serif"><div><span><ip_a.png></span><br></div><br></div><div><div class="h5"><div class="gmail_default" style="font-family:times new roman,serif">
For those of you that can't see pictures:</div><div class="gmail_default"><font face="courier new, monospace">$ sudo ip a</font></div><div class="gmail_default"><font face="courier new, monospace">1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue</font></div>
<div class="gmail_default"><font face="courier new, monospace"> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00</font></div><div class="gmail_default"><font face="courier new, monospace"> inet <a href="http://127.0.0.1/8" target="_blank">127.0.0.1/8</a> scope host lo</font></div>
<div class="gmail_default"><font face="courier new, monospace"> inet6 ::1/128 scope host</font></div><div class="gmail_default"><font face="courier new, monospace"> valid_lft forever preferred_1ft forever</font></div>
<div class="gmail_default" style="font-family:times new roman,serif"><br></div><div class="gmail_default" style="font-family:times new roman,serif">I suspect that the issue is that the hypervisor is not presenting a virtual ethernet card.</div>
<div class="gmail_default" style="font-family:times new roman,serif"><br></div><div class="gmail_default" style="font-family:times new roman,serif">Thank you</div><div class="gmail_default" style="font-family:times new roman,serif">
<br></div><div class="gmail_default" style="font-family:times new roman,serif"><br></div><div class="gmail_default" style="font-family:times new roman,serif">Jeff</div><div class="gmail_default" style="font-family:times new roman,serif">
<br></div></div></div></div><div><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 14, 2014 at 6:57 PM, Nhan Cao <span dir="ltr"><<a href="mailto:nhanct92@gmail.com" target="_blank">nhanct92@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">can you show output of command:<div>ip a</div><div><br></div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2014-08-15 7:41 GMT+07:00 Jeff Silverman <span dir="ltr"><<a href="mailto:jeff@sweetlabs.com" target="_blank">jeff@sweetlabs.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div class="gmail_default" style="font-family:'times new roman',serif">People,</div>
<div class="gmail_default" style="font-family:'times new roman',serif">
<br></div><div class="gmail_default" style="font-family:'times new roman',serif">
I have brought up an instance, and I can connect to it using my browser! I am so pleased.</div><div class="gmail_default" style="font-family:'times new roman',serif"><br></div><div class="gmail_default" style="font-family:'times new roman',serif">
However, my instance doesn't have an ethernet device, only a loopback device. My management wants me to use a provider network, which I understand to mean that my instances will have IP addresses in the same space as the controller, block storage, and compute node administrative addresses. However, I think that discussing addressing is premature until I have a working virtual ethernet card.</div>
<div class="gmail_default" style="font-family:'times new roman',serif"><br></div><div class="gmail_default" style="font-family:'times new roman',serif">I am reading through <a href="http://docs.openstack.org/icehouse/install-guide/install/yum/content/neutron-ml2-compute-node.html" target="_blank">http://docs.openstack.org/icehouse/install-guide/install/yum/content/neutron-ml2-compute-node.html</a> and I think that the ML2 plugin is what I need. However, I think I do not want a network type of GRE, because that encapsulates the packets and I don't have anything to un-encapsulate them.</div>
<div class="gmail_default" style="font-family:'times new roman',serif"><br></div><div class="gmail_default" style="font-family:'times new roman',serif">Thank you</div><span><font color="#888888"><div class="gmail_default" style="font-family:'times new roman',serif">
<br></div><div class="gmail_default" style="font-family:'times new roman',serif"><br></div><div class="gmail_default" style="font-family:'times new roman',serif">Jeff</div><div class="gmail_default" style="font-family:'times new roman',serif">
<br></div><div><br></div>-- <br><div dir="ltr"><b>Jeff Silverman</b><div>Systems Engineer</div><div><a href="tel:%28253%29%20459-2318" value="+12534592318" target="_blank">(253) 459-2318</a> (c)</div><div><img src="https://dl.dropboxusercontent.com/u/16943296/SweetLabs-Signatures/New_2014/signature-logo.png"><br>
</div></div>
</font></span></div>
<br></div></div>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><b>Jeff Silverman</b><div>Systems Engineer</div><div><a href="tel:%28253%29%20459-2318" value="+12534592318" target="_blank">(253) 459-2318</a> (c)</div>
<div><img src="https://dl.dropboxusercontent.com/u/16943296/SweetLabs-Signatures/New_2014/signature-logo.png"><br>
</div></div>
</div>
_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</div></div></blockquote></div><br></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><b>Jeff Silverman</b><div>Systems Engineer</div><div>(253) 459-2318 (c)</div><div><img src="https://dl.dropboxusercontent.com/u/16943296/SweetLabs-Signatures/New_2014/signature-logo.png"><br>
</div></div>
</div>