<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="">Ok, let’s first try to fix the inter-VM communication, then let’s look at the external network.<div class=""><br class=""></div><div class="">Question: </div><div class="">1) What kind of segmentation are you attempting? VLAN?</div><div class=""> I would recommend you to try VXLAN or GRE first.</div><div class=""> </div><div class=""> In such case you won’t need to modify your local eth0.xx, just specify</div><div class="">the local_ip on the ovs agent configuration, and of course all the other VXLAN bits (that’s </div><div class="">generally done automatically by packsack)</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">For the external network</div><div class=""><br class=""></div><div class="">you could plug your eth1 directly to the br-ex bridge, (without vlan tagged), and then specify:</div><div class=""><br class=""></div><div class=""><a href="http://docs.openstack.org/havana/install-guide/install/apt/content/install-neutron.configure-networks.plug-in-specific.ovs.vlan.html" class="">http://docs.openstack.org/havana/install-guide/install/apt/content/install-neutron.configure-networks.plug-in-specific.ovs.vlan.html</a></div><div class=""><pre class="screen" style="color: rgb(35, 48, 45); font-family: Monaco, 'Courier New', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace; overflow-x: scroll; width: 1100px; font-size: 12px; widows: 1; border-bottom-color: rgb(222, 222, 222) !important; border-bottom-style: solid !important; border-bottom-width: 1px !important; border-top-color: rgb(222, 222, 222) !important; border-top-style: solid !important; border-top-width: 1px !important; padding: 0.5em !important;">--provider:network_type vlan --provider:physical_network physnet1 --provider:segmentation_id SEG_ID </pre><div class="">Make sure “physnet1” is the mapping that connects to your br-ex (bridge mappings on the packstack config, that’s</div></div><div class="">installed to the ovs agent configuration file).</div><div class=""><br class=""></div><div class="">This way neutron would handle the vlan tagging/untagging from/to your external network.</div><div class=""><br class=""></div><div class="">Alternatively, if you want to provide your network node/controller with an external IP address you can try to plug in eth1:1 instead</div><div class="">and keep eth1 for the system (warning, I haven’t tried this specifically, but I guess it may work).</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Miguel Ángel Ajo</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On 14/4/2015, at 11:48, pauline phaure <<a href="mailto:phaurep@gmail.com" class="">phaurep@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">i turned down the br-ex and br-int and returned the eth0, eth0.xx, eth1,eth1.xx to their original state. Now i can ssh to my servers. But when I spawn a VM it can't reach the dhcp agent.<br class=""><br class=""><pre class="">Starting acpid: OK
cirros-ds 'local' up at 0.84
no results found for mode=local. up 0.87. searched: nocloud configdrive ec2
Starting network...
udhcpc (v1.20.1) started
Sending discover...
Sending discover...
Sending discover...
Usage: /sbin/cirros-dhcpc <up|down>
No lease, failing
WARN: /etc/rc3.d/S40-network failed
cirros-ds 'net' up at 181.06
checking <a href="http://169.254.169.254/2009-04-04/instance-id" class="">http://169.254.169.254/2009-04-04/instance-id</a>
failed 1/20: up 181.07. request failed
failed 2/20: up 183.09. request failed
failed 3/20: up 185.10. request failed
failed 4/20: up 187.10. request failed
failed 5/20: up 189.11. request failed
failed 6/20: up 191.11. request failed
failed 7/20: up 193.12. request failed
failed 8/20: up 195.12. request failed
failed 9/20: up 197.13. request failed
failed 10/20: up 199.13. request failed
failed 11/20: up 201.14. request failed
failed 12/20: up 203.14. request failed
failed 13/20: up 205.15. request failed
failed 14/20: up 207.15. request failed
failed 15/20: up 209.16. request failed
failed 16/20: up 211.16. request failed
failed 17/20: up 213.17. request failed
failed 18/20: up 215.17. request failed
failed 19/20: up 217.18. request failed
failed 20/20: up 219.18. request failed
failed to read iid from metadata. tried 20
no results found for mode=net. up 221.19. searched: nocloud configdrive ec2
failed to get instance-id of datasource</pre><br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">2015-04-14 10:23 GMT+02:00 pauline phaure <span dir="ltr" class=""><<a href="mailto:phaurep@gmail.com" target="_blank" class="">phaurep@gmail.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">no actually, packstack just added two files which were empty. Besides my VMs couldn't reach the dhcp agent and it was clear that all the br-ex br-int and br-tun were down.<div class=""><br class=""></div><div class="">In order to fill my ifcfg-br-ex file i followed this tuto here <a href="https://www.rdoproject.org/Neutron_with_existing_external_network" target="_blank" class="">https://www.rdoproject.org/Neutron_with_existing_external_network</a>. for the br-int i followed this one <a href="https://www.rdoproject.org/forum/discussion/196/quantum-basic-setup/p1" target="_blank" class="">https://www.rdoproject.org/forum/discussion/196/quantum-basic-setup/p1</a>. I did exactly the same but i didn't work for me. I think that the problem is related to my interfaces eth0 and eth1 placed in vlans on the physical switch. any idea on how i could fix things?</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br class=""><div class="gmail_quote">2015-04-14 10:04 GMT+02:00 Miguel Angel Ajo Pelayo <span dir="ltr" class=""><<a href="mailto:mangelajo@redhat.com" target="_blank" class="">mangelajo@redhat.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It's been a while since I'm not doing it, but isn't packstack supposed to do that for you?.<br class="">
<br class="">
What guide steps are you following to modify such files?<br class="">
<div class=""><div class=""><br class="">
----- Original Message -----<br class="">
><br class="">
><br class="">
><br class="">
> ok, i will but how should i configure this ifcfg-files? should i put the<br class="">
> br-ex and br-int in the same vlans as eth0 and eth1?<br class="">
><br class="">
> 2015-04-14 10:00 GMT+02:00 Miguel Angel Ajo Pelayo < <a href="mailto:mangelajo@redhat.com" target="_blank" class="">mangelajo@redhat.com</a> > :<br class="">
><br class="">
><br class="">
> Hi Pauline,<br class="">
><br class="">
> I’m afraid that at this point you may need to connect via a KVM or direct<br class="">
> monitor / keyboard to<br class="">
> properly reconfigure the ifcfg files.<br class="">
><br class="">
><br class="">
> > On 14/4/2015, at 9:48, pauline phaure < <a href="mailto:phaurep@gmail.com" target="_blank" class="">phaurep@gmail.com</a> > wrote:<br class="">
> ><br class="">
> > Hi everyone,<br class="">
> > I recently installed Openstack with RDO packstack on two servers. on each<br class="">
> > server I have 2 interfaces eth0 and eth1 each one of this interfaces is on<br class="">
> > a seperate vlans. As the VMs spawened by NOVA couldn't get an IP address,<br class="">
> > I saw in a tutorial that I should edit the files ifcfg-br-ex and<br class="">
> > ifcfg-br-int and when I did I lost my connection and couldn't anymore ssh<br class="">
> > to my servers.<br class="">
> > Do you have any idea how i can solve this?<br class="">
> > thank you in advance,<br class="">
> > Pauline,<br class="">
> > _______________________________________________<br class="">
> > Rdo-list mailing list<br class="">
> > <a href="mailto:Rdo-list@redhat.com" target="_blank" class="">Rdo-list@redhat.com</a><br class="">
> > <a href="https://www.redhat.com/mailman/listinfo/rdo-list" target="_blank" class="">https://www.redhat.com/mailman/listinfo/rdo-list</a><br class="">
> ><br class="">
> > To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com" target="_blank" class="">rdo-list-unsubscribe@redhat.com</a><br class="">
><br class="">
> Miguel Angel Ajo<br class="">
><br class="">
><br class="">
><br class="">
><br class="">
><br class="">
><br class="">
> _______________________________________________<br class="">
> Rdo-list mailing list<br class="">
> <a href="mailto:Rdo-list@redhat.com" target="_blank" class="">Rdo-list@redhat.com</a><br class="">
> <a href="https://www.redhat.com/mailman/listinfo/rdo-list" target="_blank" class="">https://www.redhat.com/mailman/listinfo/rdo-list</a><br class="">
><br class="">
> To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com" target="_blank" class="">rdo-list-unsubscribe@redhat.com</a><br class="">
</div></div></blockquote></div><br class=""></div>
</div></div></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""><div class="">
<div class="">Miguel Angel Ajo</div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""></div></body></html>