Hi Gautaum. If you look at the console log for the VM (the full one),
you will see that it only received network interface config from
cloud-init for the second flat-lan-2 network. This network does not
have a router with an interface in the ext-net (and router interfaces
connected to the ext-net require another public addr from the floating
IP pool), so flat-lan-2 is not reachable from the public network. The
other issue is that you bound the VM's floating IP addr to flat-lan-1,
but that iface is not being configured on the VM. If you logged in and
ran dhclient on that unconfigured interface, I bet your VM would start
responding on the floating IP.
(I haven't done multihoming on openstack VMs for many years, but you
used to have to play tricks like editing the VM's network configuration
files a priori to ensure DHCP on all (relevant) interfaces. I'm not
sure how cloud-init selects the interface on which it reaches out to the
openstack metadata daemon, which is where it finds its configuration;
probably simply "first" by enumeration/carrier.)
> Gautam
David