maas-devel team mailing list archive

[Michael Hughes <itismike@xxxxxxxxx>]

Hi Julian,

Agreed that a 'default' template would make scaling much faster, but
rather than assuming one would set up multiple subnets for different
hardware types I'd recommend looking into DMI queries to automatically
determine machine type.

The Capone plugin over at the FOG project is an excellent example of
how to implement this:
http://www.fogproject.org/wiki/index.php?title=Plugins:_Capone#Using_Capone

and
http://www.fogproject.org/wiki/index.php?title=Capone

-Mike

On Thu, May 24, 2012 at 5:27 AM, Julian Edwards
<julian.edwards@xxxxxxxxxxxxx> wrote:
> Hi all,
>
> There are some things coming up that will start to affect how we move forward
> with features and trying to keep them scalable.
>
> The most interesting one of these for me at the moment is doing sensible
> defaulting on enlisted nodes, to reduce (or eliminate) manual input.  At the
> moment, admins have to set the parameters on each enlisted node one by one.
> This is going to get rather painful when setting up power parameters, for
> example.
>
> I've suggested to a few people that we start having profiles like Cobbler does
> and apply them to nodes as defaults.  When we start having node groups (node
> groups are a set of nodes that need to share the same provisioning server,
> e.g. ones on the same subnet) those groups could have a default profile.  That
> would result in all nodes in a group getting a common default setting, which
> should hopefully work because they are all in the same subnet.
>
> Does anyone have any comments on this approach?
>
> Thanks.
>
> --
> Mailing list: https://launchpad.net/~maas-devel
> Post to     : maas-devel@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maas-devel
> More help   : https://help.launchpad.net/ListHelp