maas-devel team mailing list archive

[Julian Edwards <julian.edwards@xxxxxxxxxxxxx>]

On Sunday 13 Jul 2014 22:19:31 Andres Rodriguez wrote:
> I've filed [0] to keep track of this.
> 
> @Julian, could you please take a look at it?

The original design (as discussed on this list and design docs) was not to do 
this, but to give an IP when allocating the node to a user.  This was so that 
(in the future) users can say things like "I want to use this VPN/bond IP" etc 
right from the start without wasting another IP.  It's very hard for MAAS to 
be able to change the IP on demand for a machine that is already booted unless 
we go down the Azure road and run a MAAS agent on the nodes.

There is a separate mechanism to permanently assign an IP to a node if the 
admin wishes (the API for that is not coded yet but the underlying basics are 
in place).  Is this what folks want now?

> On Sat, Jul 12, 2014 at 9:55 AM, Mark Shuttleworth <mark@xxxxxxxxxx> wrote:
> > I would suggest that once MAAS "owns" a machine, i.e. MAAS has PXE
> > booted the machine itself (credentials work), it is given a name and
> > static IP address which does not change unless edited by the user (it
> > should be possible for the user to put it on a difference, unused IP
> > address in the static range). Renaming the machine would update DNS,
> > editing the IP would update DNS.
> > 
> > This allows a user to "ping" a machine and see that it is off.

We can do this as things stand because if a user still "owns" a machine, it 
retains the static IP given at startup time.

Or to put it another way, a machine that is supposed to be up will always have 
an IP.  If you want to see whether it's really up or not we should probably do 
an API call to examine the power status (on the BMC); then if it's still not 
pingable you know there's a more serious problem.