-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys,
i'm running in a problem if i associate a floating IP address to an instance. My system: * icehouse / Ubuntu * 2 different tenants * each tenant have his own router * each tenant have his own fixed net/subnet attached to his own router I've create a port on tenant A with a fixed_ip address and attach this port to tenant B router. In addition i've updated the subnet on tenant A and add the host routes to reach the tenant B network. That works perfectly. Now i'm spawning an instance on tenant A and i can reach them with the allocated fixed_ip. The next step is to associate a floating IP address to the spawned instance. That works without errors but the l3 agent will create the DNAT and SNAT rules on the tenant B router (wrong router). My assumption is that the l3 agent looks for router_interface and takes the first one. So the l3 agent gets the device_id (router id) where the SNAT and DNAT should be create. Is that a bug or do im something wrong ? Cheers Heiko P.S.: Sorry for double post (https://ask.openstack.org/en/question/48468/neutron-floating-ip-nat-on-wrong-router/) - -- anynines.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUJAhSAAoJELxFogM4ixOFSYcH/33P+S3us0h8EblPhh8Ctyuj b21tS1b/wmaz4tyJdCCWDBh61GHLT75aMcoriPa7lPm/nhT0eT79DG52NO1I5G3B lJqA6cPI+r1Da4fPB049g4OJ7izIKbUrinGlW/lZtf0Pf6ppV3x7BfedMZbl2U78 mWM5AYrfWWQwWcN9n1lG65cGtPR/v24QCbf9kkIBAdowdkzczk7K99DZ7/kynIT5 NiF3Dz6IhLUF4cblhDqoKOO2ClqvwTU17wqqt9OmLWiV6y1UOkRKpQY3gKiN6peb ggKQP0U6QIV6ynv4EPyD5S5OLEXjLDEJLcAUlDwFmGXRR6Hi/KEZOsnLtUaS9xI= =AAP3 -----END PGP SIGNATURE----- _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
