On Thu, 2012-06-21 at 14:56 +0300, Gary Kotton wrote:
> > However, I would probably use a slightly different syntax for associating
> > IPs:
> >
> > POST /v2.0/ips
> >
> > {
> > "subnet_id": "<some_uuid>",
> > "port_id": "<some_other_uuid>",
> > "ip": "<{ipv4 | ipv6}>",
> > }
>
> This entails that a port will have had to be created prior. I like the
> fact that with the port creation one or more ip's can be allocated or
> configured.
>
> I think that having an additional step for IP configuration could be
> cumbersome for the user. Is there any option of say adding the table
> that you have suggested for read only purposes?
I agree I'd like to avoid an extra HTTP call to allocate IP's
(specifically for nova vm creation). I would expect that a plugin would
allocate an ip to a port if there is a subnet associated with the
network the port is on. Adding additional ips past that 1st auto
allocated would require a post to /ips. But the method of operation is
really up to plugin vendors.
Happy Hacking!
7-11
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
