yahoo-eng-team team mailing list archive

[Milan Falešník <mfalesni@xxxxxxxxxx>]

Public bug reported:

I was trying to write a code that reuses allocated floating IPs using
python nova client api. The method I used was add_floating_ip but I was
worried of race conditions if multiple clients would try to associate
the same FIP with different machines, since that method does not check
whether the FIP is already associated. I then talked to dev who
suggested to use neutron, so I tried it directly with neutron, but
again, it does not check whether the FIP is associated, it just sets it
for that instance and done. I am aware that there is a possibility to
create and associate in one step, but there is the possible problem when
I want to pick and associate some of not associated FIPs.

So, if update_floatingip method could accept a parameter, eg.
"check_dissociated=False" which would enable neutron (and possibly nova
if the change gets propagated there) to raise an exception if the passed
FIP is already associated, making it it possible to handle the possible
race conditions.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1482556

Title:
  RFE - Missing possibility to check whether FIP is dissociated on
  association.

Status in neutron:
  New

Bug description:
  I was trying to write a code that reuses allocated floating IPs using
  python nova client api. The method I used was add_floating_ip but I
  was worried of race conditions if multiple clients would try to
  associate the same FIP with different machines, since that method does
  not check whether the FIP is already associated. I then talked to dev
  who suggested to use neutron, so I tried it directly with neutron, but
  again, it does not check whether the FIP is associated, it just sets
  it for that instance and done. I am aware that there is a possibility
  to create and associate in one step, but there is the possible problem
  when I want to pick and associate some of not associated FIPs.

  So, if update_floatingip method could accept a parameter, eg.
  "check_dissociated=False" which would enable neutron (and possibly
  nova if the change gets propagated there) to raise an exception if the
  passed FIP is already associated, making it it possible to handle the
  possible race conditions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1482556/+subscriptions