launchpad-reviewers team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

The proposal to merge lp:~smoser/maas/ephemeral-enlist into lp:maas has been updated.

Description changed to:

make enlistment use ephemeral environment via enlistment metadata service

The overall goal of these changes is to get enlistment done in the
ephemeral environment rather than from the netboot ISO.  This is done by
adding an enlistment datasource for cloud-init.

The "default" profile (which currently does enlistment) will be passed a
'url=' value that points to the rendered cloud-config content instructing
cloud-init to use the maas provided metadata service.

Then, the same path is taken by cloud-init as is done in the commissioning
environment, except for the fact that the metadata service that provides
the user-data will not require oauth.

Both cobbler and non-cobbler paths have been updated.

The thing remaining to do here is to actually get the enlistment to function.
That really should be the easy part, as Andres' 'maas-enlist' program is generally all that is necessary.  We just need to invoke it with the IP address of the maas server.

I have envisioned here that commissioning and enlistment are largely
different from the maas api server perspective.  Ie the url= parameter
on the "enlist" profile and on the "commission" profile will be different.
The source of that is that the environments do differ in that
 a.) commisioning has a valid node associated with the requests
 b.) commissioning has oauth tokens, enlistment cannot reasonably be authed.

These *could* be merged into one metadata service, but I've not done that
here, and think it not unreasonable to keep them separate.

For more details, see:
https://code.launchpad.net/~smoser/maas/ephemeral-enlist/+merge/117993
-- 
https://code.launchpad.net/~smoser/maas/ephemeral-enlist/+merge/117993
Your team Launchpad code reviewers is requested to review the proposed merge of lp:~smoser/maas/ephemeral-enlist into lp:maas.