Hello Team, I was just thinking of possible reasons for the floating IP pool flooding observed and one of the possible reasons is that the floating iP association logic in cloud-provisioning always creates a new floating IP in the pool and associates to the VM. Even though the VM deletion handles removing and deleting the associated floating IP, there might have been cases that the machine gets an floating IP associated and then the machine is deleted through some other flow, leaving the floating IP unused in the pool.
I have now modified the code to reuse any existing floating IPs in the pool, instead of requesting a new one every time. Now the logic would request a new floating ip only if the available floating IP list is empty, or all the floating IPs in the list are associated to VMs. I have verified that the maven build with the tests runs successfully and also tested the code for various possible scenarios. Link for pull request for this change is:- https://github.com/apache/airavata/pull/34 I request you to please review and consider merging this change in the codebase, so as to have better Floating IP management. Please let me know if you have any comments/ suggestions. Regards, Mangirish On Thu, May 12, 2016 at 7:09 PM, Suresh Marru <[email protected]> wrote: > Very nice summary, thanks for shepherding through the issue and following > up on the list Mangirish. > > Suresh > > On May 12, 2016, at 4:56 PM, Mangirish Wagle <[email protected]> > wrote: > > Hello, > > Dropping this mail for teams awareness about a network issue faced on > Jetstream Openstack. > > Pankaj and I were facing a problem with association of Floating IPs to the > VMs provisioned on Jetstream using scigap credentials, and thus the VMs > could not be accessed publicly. > > We also noticed further that the Network Topology in the Horizon UI > refused to load. > > After following up on this issue with Mike Lowe on Jetstream Slack > channel, it was realized that it was possibly because of a firewall rule > induced by some security update which blocked some traffic on the compute > nodes. > > The issue was then resolved by Mike and the topology loaded fine. > > Further, I noticed that the router configuration did not have an interface > for airavata network to be connected to public network. I added the > interface back and now the floating IP association seems to work fine. > > Thanks and Regards, > Mangirish Wagle > > > > > > >
