maas-devel team mailing list archive

[Gavin Panella <gavin.panella@xxxxxxxxxxxxx>]

On 19 July 2012 11:31, Raphaël Badin <raphael.badin@xxxxxxxxxxxxx> wrote:
...
> Note that a node will be without a hostname until an IP has been allocated
> for that node.  We will need a way to display (in the UI) a name for that
> node even before a proper hostname is set.  I suggest we revisit our
> decision not to display the (auto-generated) node's system_id and use that
> in the UI until a hostname is set.

If we're auto-generating the hostname, and it's read-only, does this
matter? On reflection, isn't MAAS meant to be uninterested in the
preciousness of a single machine? We /could/ forego DNS altogether...

... but I don't that's right either.

I need to better understand exactly why we need DNS support.

Maybe what we want is a way for an external user to refer to their own
allocated nodes that, when they deallocate their node, no longer
works. In other words, if someone else allocates that node, the first
user doesn't have a reference to it (in the form of a hostname). A
scheme like ${system-id}.${username}.${maas-domain} might be one way
to achieve this.

And, as Raphael has already said, none of this actually solves the
problem that started this conversation, classful/classless networks :)