Hi,
Thanks for you patience Dan answering all the questions, I have solved all
the issues and got the thing working.
I could possibly add some content to the Quantum docs about my experience,
who should I contant in this regard?
Regards,
--janis
___
On Wed, Oct 10, 2012 at 8:57 AM, Jānis Ģeņģeris
janis.genge...@gmail.com wrote:
Hi,
Thanks for you patience Dan answering all the questions, I have solved all
the issues and got the thing working.
I could possibly add some content to the Quantum docs about my experience,
who should I
Hi,
I have managed to create the Quantum router so that all the VMs created on
provider network are going through it. I had to simply use
router-interface-add.
But I have now the problem with accessing metadata service. As L3 agent
adds DNAT rule in router, the packets are rewritten and arrives
Hello,
When using provider networks in Quantum, where should the metadata service
rule mapping (e.g. 169.254.169.254:80 - metadata_server:metadata_port)
must be set?
For example, for floating IPs l3-agent handles this, but for provider
networks router is not used. I tried to set custom iptables
On Mon, Oct 8, 2012 at 7:52 AM, Jānis Ģeņģeris janis.genge...@gmail.com wrote:
Hello,
When using provider networks in Quantum, where should the metadata service
rule mapping (e.g. 169.254.169.254:80 - metadata_server:metadata_port) must
be set?
For example, for floating IPs l3-agent handles
On Mon, Oct 8, 2012 at 6:24 PM, Dan Wendlandt d...@nicira.com wrote:
On Mon, Oct 8, 2012 at 7:52 AM, Jānis Ģeņģeris janis.genge...@gmail.com
wrote:
Hello,
When using provider networks in Quantum, where should the metadata
service
rule mapping (e.g. 169.254.169.254:80 -
Here is the output, with few details.
# quantum router-show router_vlan1501
+---+--+
| Field | Value|
+---+--+
| admin_state_up|
7 matches
Mail list logo
