[Rdo-list] RDO with existing external network

Miguel Angel Ajo mangelajo at redhat.com
Fri Jun 5 15:41:16 UTC 2015


Check this guide:
https://www.rdoproject.org/Networking_in_too_much_detail

Around “Neutron host: Router (M,N)” it may give you hints on how to debug the virtual routers… those are the ones which should be exposing your FIPs

could you also dump:

# neutron net-show external_network   ?   

--  
Miguel Ángel Ajo


On Friday 5 June 2015 at 17:20, Maarten Hoes wrote:

> Hi,
>  
>  
> Yes I can ping 192.168.178.23.  
>  
> Ive added the rules with the dashboard/horizon.
>  
> - Maarten
>  
>  
> On Fri, Jun 5, 2015 at 5:14 PM, Miguel Angel Ajo <mangelajo at redhat.com (mailto:mangelajo at redhat.com)> wrote:
> > It looks good.
> >  
> > Can you ping 192.168.178.23 from your local network?  
> >  
> > I’d verify that the security groups allow ingress to ssh / ping or whatever you want to open.
> >  
> > https://www.rdoproject.org/Running_an_instance_with_Neutron (Step 2) as keystonrc_admin  
> >  
> > --  
> > Miguel Angel Ajo
> > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> >  
> >  
> > On Friday 5 June 2015 at 17:11, Maarten Hoes wrote:
> >  
> > > Hi,
> > >  
> > >  
> > > Here they are.
> > >  
> > >  
> > > - Maarten
> > >  
> > >  
> > >  
> > > On Fri, Jun 5, 2015 at 5:04 PM, Miguel Angel Ajo <mangelajo at redhat.com (mailto:mangelajo at redhat.com)> wrote:
> > > > Hmm :)
> > > >  
> > > > Ok, can you post the output of:
> > > >  
> > > > ovs-vsctl show
> > > >  
> > > > ip addr
> > > >  
> > > > ip link
> > > >  
> > > > and the /etc/sysconfig/network-script/ files ?  
> > > >  
> > > > Best,
> > > > Miguel Ángel
> > > >  
> > > >  
> > > >  
> > > >  
> > > > On Friday 5 June 2015 at 17:01, Maarten Hoes wrote:
> > > >  
> > > > > Hi,
> > > > >  
> > > > >  
> > > > > 192.168.178.0/24 (http://192.168.178.0/24) is the local network provided by my cable isp box. 192.168.178.23 is my vmware vm im running linux (and openstack) on. Other devices in the same range are ping-able from within that vm.
> > > > >  
> > > > >  
> > > > > - Maarten
> > > > >  
> > > > >  
> > > > >  
> > > > > On Fri, Jun 5, 2015 at 4:55 PM, Miguel Angel Ajo <mangelajo at redhat.com (mailto:mangelajo at redhat.com)> wrote:
> > > > > > Hmm “no route to host” indicates that the machine were you’re running  
> > > > > > ping or ssh has no route to 192.168.178.xx  .
> > > > > >  
> > > > > > That’s something specific to your setup.
> > > > > >  
> > > > > > Is that subnet connected to one of the interfaces of your machine or has routing to reach it?
> > > > > >  
> > > > > >  
> > > > > > --  
> > > > > > Miguel Angel Ajo
> > > > > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > > > > >  
> > > > > >  
> > > > > > On Friday 5 June 2015 at 16:53, Maarten Hoes wrote:
> > > > > >  
> > > > > > > Hi,
> > > > > > >  
> > > > > > >  
> > > > > > > Thanks again for the update and effort.
> > > > > > >  
> > > > > > > The guide works (produces no errors), but ...
> > > > > > >  
> > > > > > > When I try to connect to the launched instance with either ping or ssh, I get these errors:
> > > > > > >  
> > > > > > > # ping 192.168.178.52
> > > > > > > PING 192.168.178.52 (192.168.178.52) 56(84) bytes of data.
> > > > > > > From 192.168.178.23 icmp_seq=1 Destination Host Unreachable
> > > > > > >  
> > > > > > > # ssh 192.168.178.52
> > > > > > > ssh: connect to host 192.168.178.52 port 22: No route to host
> > > > > > >  
> > > > > > > I guess it has something to do with my setup ?
> > > > > > >  
> > > > > > >  
> > > > > > > - Maarten
> > > > > > >  
> > > > > > >  
> > > > > > >  
> > > > > > > On Fri, Jun 5, 2015 at 4:08 PM, Miguel Angel Ajo <mangelajo at redhat.com (mailto:mangelajo at redhat.com)> wrote:
> > > > > > > > Could you try now?,   
> > > > > > > >  
> > > > > > > > https://www.rdoproject.org/Neutron_with_existing_external_network  
> > > > > > > >  
> > > > > > > > Let me know if it works for you, here it does work.
> > > > > > > >  
> > > > > > > > On Friday 5 June 2015 at 15:36, Maarten Hoes wrote:
> > > > > > > >  
> > > > > > > > > Hi,
> > > > > > > > >  
> > > > > > > > >  
> > > > > > > > > Thanks, that would be great.  
> > > > > > > > >  
> > > > > > > > >  
> > > > > > > > > - Maarten
> > > > > > > > >  
> > > > > > > > >  
> > > > > > > > >  
> > > > > > > > > On Fri, Jun 5, 2015 at 3:17 PM, Miguel Angel Ajo <mangelajo at redhat.com (mailto:mangelajo at redhat.com)> wrote:
> > > > > > > > > > It’s a bit rusty,  
> > > > > > > > > >  
> > > > > > > > > > I’m working in an updated version,  
> > > > > > > > > >  
> > > > > > > > > > To start, I want to remove replication from the quickstart guide, so I’ll add a reference to Steps 1-2 from there, and then separate steps from there.
> > > > > > > > > >  
> > > > > > > > > >  
> > > > > > > > > >  
> > > > > > > > > > --  
> > > > > > > > > > Miguel Angel Ajo
> > > > > > > > > >  
> > > > > > > > > >  
> > > > > > > > > > On Thursday 4 June 2015 at 13:57, Maarten Hoes wrote:
> > > > > > > > > >  
> > > > > > > > > > > Hi,
> > > > > > > > > > >  
> > > > > > > > > > >  
> > > > > > > > > > > (like asked on irc)
> > > > > > > > > > >  
> > > > > > > > > > > Im struggling with getting RDO to work with my existing network. Ive tried to follow this guide:
> > > > > > > > > > >  
> > > > > > > > > > > https://www.rdoproject.org/Neutron_with_existing_external_network
> > > > > > > > > > >  
> > > > > > > > > > >  
> > > > > > > > > > > But cant seem to get it to work for me. Could you take a look at that guide and see if its still accurate ?
> > > > > > > > > > >  
> > > > > > > > > > >  
> > > > > > > > > > >  
> > > > > > > > > > > Thanks,
> > > > > > > > > > >  
> > > > > > > > > > >  
> > > > > > > > > > >  
> > > > > > > > > > > - Maarten Hoes.
> > > > > > > > > > >  
> > > > > > > > > >  
> > > > > > > > >  
> > > > > > > >  
> > > > > > >  
> > > > > >  
> > > > >  
> > > >  
> > >  
> >  
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20150605/89840634/attachment.html>


More information about the dev mailing list