currently.
l3_agent designed as serve all tenant's traffic or
per router per l3_agent by specify router_id in l3_agent.ini
so in current architecture. if you want deploy as production scale.
I think l3_agent must be dedicated to one router
or the another solution is needed(nvp, midonet, cisco
Thanks for that - the namspace thing is starting to make sense.
So I see this rule in there now:
Chain quantum-l3-agent-PREROUTING (1 references)
pkts bytes target prot opt in out source
destination
62 3720 DNAT tcp -- * * 0.0.0.0/0
169.254.169.254 tcp
Hi,
On Thu, 2012-11-08 at 10:02 +, Kevin Jackson wrote:
Thanks for that - the namspace thing is starting to make sense.
So I see this rule in there now:
Chain quantum-l3-agent-PREROUTING (1 references)
pkts bytes target prot opt in out source
destination
62
Hi Stephen,
This is what I get... (note change of namespace etc as this machine is a VM
that was recreated).
root@openstack:~# ip netns list
qdhcp-3f0a3d53-f3a4-4da8-a5e0-1a97b6e51424
qrouter-f26858db-3ae8-431b-86a7-edab80834586
root@openstack:~# ip netns exec
"I followed the instructions to add a
route from http://docs.openstack.org/trunk/openstack-network/admin/content/adv_cfg_l3_agent_metadata.html
but I don't immediately see how the route add helped here - but it
has raised an eyebrow."
Tell me about it!
Hello all,
I thought I would give quantum a
shot and I've got a 50-60% working configuration, but having
trouble understanding where to go from here as the docs
are pretty sparse.
Ubuntu 12.04.1
- DNAT rule to metadata server is done by l3_agent. but your node configuration
has no l3_agent
- and metadata_ip configuration can find l3_agent.ini.
2012. 11. 7., 오후 9:15, Sina Sadeghi s...@aptira.com 작성:
Hello all,
I thought I would give quantum a shot and I've got a 50-60% working
Heyup good folk of OpenStack,
I'm having the same issue as Sina. My configuration seems to look OK (I
have an instance, with IP that can ping its default route to on an internal
network) but I get the failure to contact the metadata server with the
explanation that Sina gave.
In my
On Wed, 2012-11-07 at 16:02 +, Kevin Jackson wrote:
Heyup good folk of OpenStack,
I'm having the same issue as Sina. My configuration seems to look OK
(I have an instance, with IP that can ping its default route to on an
internal network) but I get the failure to contact the metadata
Kevin is correct; as your're running IP namespaces, you'll need to look for
iptables in that namespace.
The metadata settings however are visible in the log extract you posted.
It seems your metadata server is sitting at 172.16.0.201:8775
I guess you've already ensured that endpoint is reachable
Hi-
I have set up a controller- node setup with openstack, quantum and
OpenVswitch.
I'm able to create the virtual machines in the node.
The eth1 interface of controller and node are attached to the OVS br-int.
In the node, 'ovs-vsctl show' show the port and interface binding of the
newly
Hi Trinath,
Have you checked that your quantum is making related gw and tap
interfaces when your vm goes up.
When you create a network and create first vm associated with it,
there should be a gw and tap interface created and
first ip of your new network is assigned to that gw interface.
if you
Hi-
Thanks a lot for the reply..
Its working now...
On Jul 18, 2012 6:35 PM, Nirbhay Tomar nirbhaysinghto...@gmail.com
wrote:
Hi Trinath,
Have you checked that your quantum is making related gw and tap
interfaces when your vm goes up.
When you create a network and create first vm
13 matches
Mail list logo
