Hi,
I have some problems with neutron network. I've configured Openstack
according to instructions (I hope :) with gre tunnels and everything
looks fine, like in my similar RDO installation. All vswitch bridges
look like are connected together, with tunnels and routers. The only
problem is,
look like are connected together, with tunnels and routers. The only
problem is, that there is no comminication between virtual machines and
routers in networks :)
Do you have any sugestions, how to debug my problem or where it could
be? If necessary, I can attach some output and configuration
Thanks for the reply, it was really helpful.
In my case the problem was exactly where Felix said - nova-network left
some rules in iptables.
And yeap (might help someone in debug), redirect to metadata service
happens on network node in qrouter namespace:
# ip netns exec
Hi everyone!
I just switched from nova-network to neutron, and I'm trying to figure out
what I'm missing in config.
I was following official documentation for Icehouse (on Ubuntu 14.04), and
the result is a partially working installation. There are 3 basic problems
- first one is MTU (I'm using
Sergey Motovilovets motovilovets.ser...@gmail.com wrote on 06/14/2014
11:00:09 AM:
...
Another problem is metadata service. I've tried like everything I
found regarding neutron-metadata configuration, without any
success. I just can't connect to 169.254.169.254 from virtual
machines,
Hi, Mike.
There are no routes in my VM's except for the default one. Private subnet
I'm using is 192.168.0.0/24 with neutron router on 192.168.0.1.
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0 192.168.0.1
This can probably be useful too:
From network node
# ip netns ls
qdhcp-1b982b98-62db-4c87-867b-0490bac8fb52
qrouter-c7e7ea00-a362-4f4f-9a1c-a54ac86eb3be
# ps -x | grep metadata
1469 ?S 0:00 /usr/bin/python
/usr/bin/neutron-ns-metadata-proxy
OK, it looks like you are not suffering the bad route problems I have
seen. Beyond that I can not help, but I suppose the details you gave
might enable someone else to help.
Regards,
Mike___
Mailing list:
Hi, Sergey,
I remember I had similar problem when I switched to quantum(neutron's
previous name) from nova-network.
But, I can't recall how I solved it exactly, it would be something like
previous nova-network NAT caused the problem, so, if you switched to
neutron from nova-network at the same
On 15/06/14 03:00, Sergey Motovilovets wrote:
Another problem is metadata service. I've tried like everything I found
regarding neutron-metadata configuration, without any success. I just
can't connect to 169.254.169.254 from virtual machines, though they get
configured by dhcp, can ping each
10 matches
Mail list logo
