yahoo-eng-team team mailing list archive

[David Juran <djuran@xxxxxxxxxx>]

Public bug reported:

Hello

In my opinion, the --floating-ip-address option to "neutron floatingip-
create" should by default not be restricted to the admin user.

I notice that we now have the option, when creating a floating ip, to
specify which IP to create as opposed to only getting a (semi-)random IP
from the pool.

netron floatingip-create --floating-ip-address xx.xx.xx.xx external

 Which is very nice. But I also noticed that this option, by default is limited to an admin user. So why is this? If a user really want an IP which is free, he can likely get it by creating and deleting addresses
until the one he wants comes up.

In my opinion, we should therefore relax the default policy, allowing
ordinary users to specify which floating IP to use.

** 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/1592396

Title:
  Specifying which floatingip to create should not be a restricted
  operation

Status in neutron:
  New

Bug description:
  Hello

  In my opinion, the --floating-ip-address option to "neutron
  floatingip-create" should by default not be restricted to the admin
  user.

  I notice that we now have the option, when creating a floating ip, to
  specify which IP to create as opposed to only getting a (semi-)random
  IP from the pool.

  netron floatingip-create --floating-ip-address xx.xx.xx.xx external

   Which is very nice. But I also noticed that this option, by default is limited to an admin user. So why is this? If a user really want an IP which is free, he can likely get it by creating and deleting addresses
  until the one he wants comes up.

  In my opinion, we should therefore relax the default policy, allowing
  ordinary users to specify which floating IP to use.

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