maas-devel team mailing list archive

[Julian Edwards <julian.edwards@xxxxxxxxxxxxx>]

On 02/07/14 22:58, Gavin Panella wrote:
> On 2 July 2014 13:46, Julian Edwards <julian.edwards@xxxxxxxxxxxxx> wrote:
>> On Wednesday 02 Jul 2014 13:24:25 Gavin Panella wrote:
>>> On 2 July 2014 06:07, Julian Edwards <julian.edwards@xxxxxxxxxxxxx> wrote:
>>>> The IP reservation API exists as:
>>>>
>>>> POST /ipaddresses?op=reserve&network=<foonet/bits>
>>>> POST /ipaddresses?op=release&ip=<fooip>
>>>> GET /ipaddresses (to show all your own addresses in use)
>>>
>>> Does this allow nodes in one cluster to reserve addresses in another?
>>
>> I don't really understand what you mean.
>>
>> It allows users to request an IP on a network that MAAS knows about.
> 
> The two main use cases, as I remember them, were:
> 
> - Request an additional address for a node (e.g. for a container).
> 
> - Request an additional address in a network to be used as a floating address.
> 
> Is /ipaddresses intended only for the latter, or can an optional node
> be passed in too?

/ipaddresses is meant (at least at the moment) for the latter case.
These are explicitly tied to a user.

However there's no reason why it could not be used for the former case
too, since containers are not known as nodes in MAAS.

There is a separate mechanism for requesting an explicit IP for
additional MACs on a node.