Folks, you are welcome to review a spec: https://review.openstack.org/254796
On Fri, Nov 6, 2015 at 6:03 PM, Aleksey Kasatkin
> Mike, Vladimir,
> 1. We need to add IPs on-the-fly (need to add POST functionality) ,
> otherwise it will
Mike, that's exactly how you can use this VIPs allocation functionality.
Nailgun will save that VIP so it's not going to be auto-assigned to any
node and serialize it into astute.yaml (vip_name: IP). After that you can
get your VIP via Hiera and use it in your deployment scripts.
+1 to Mike
It would be awesome to get an API handler that allows one to actually add
an ip address to IP_addrs table. As well as an IP range to ip_ranges table.
On Fri, Nov 6, 2015 at 6:15 AM, Mike Scherbakov
> Is there a way to make it more generic, not "VIP"
1. We need to add IPs on-the-fly (need to add POST functionality) ,
otherwise it will be VIP-like way (change network roles in plugin or
2. We should allow to leave fields 'network_role', 'node_roles', 'namespace'
empty. So, validation should be changed.
Is there a way to make it more generic, not "VIP" specific? Let's say I
want to reserve address(-es) for something for whatever reason, and then I
want to use them by some tricky way.
More specifically, can we reserve IP address(-es) with some codename, and
use it later?
184.108.40.206 - my-shared-ip
> For VIP allocation we should use POST request. It's ok to use PUT for
setting (changing) IP address.
My proposal is about setting IP addresses for VIPs only (auto and manual).
No any other allocations.
Do you propose to use POST for first-time IP allocation and PUT for IP
Here is a resume of our recent discussion:
1. Add new URLs for processing VIPs:
/clusters//network_configuration/vips// (GET, PUT)
where is the id in ip_addrs table.
So, user can get all VIPS, get one VIP by id, change parameters (IP
I agree that we need a separate API call for VIP allocation, thought I
don't agree on some points you have proposed. See my comments below.
> use PUT to change VIPs addresses (set them manually or request
> to allocate them automatically)
PUT requests SHOULD NOT be used for VIP
I'm working on the following story :
API must allow VIP to be manually set to ANY valid IP address. If the IP on
update API is a member of any network in this environment then the address
should be put in the assignments table so that it can not be used in any