maas-devel team mailing list archive

[Tycho Andersen <tycho.andersen@xxxxxxxxxxxxx>]

Hi Graham,

On Mon, Apr 14, 2014 at 05:01:42PM +0100, Graham Binns wrote:
> Hi all,
> 
> Julian's asked me to take charge of the work to rid us of the need to
> edit bootresources.yaml on the cluster controllers (or indeed get rid of
> the file altogether).
> 
> Here are my initial thoughts; I'd appreciate your feedback so that we
> can get cracking. All questions, comments and thoughts welcome.
> 
> bootresources.yaml
> ------------------
> 
> 1. bootresources.yaml's contents can be reasonably easily held in the
>    database.  A standard bootresources.yaml looks like this:
> 
>     boot:
>       storage: "/var/lib/maas/boot-resources/"
>       sources:
>         - path: "http://maas.ubuntu.com/images/ephemeral-v2/daily/";
>           keyring: "/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg"
>           selections:
>             - release: "trusty"
>               arches: ["i386", "amd64"]
>               subarches: ["generic"]
>               labels: ["daily"]
> 
> - The `storage` variable can easily be made a default.
> - The `sources` section is the meat of the file. ISTM that we can easily
>   turn what lives in this section into a Django model so that we can
>   have this configuration managed through the web UI and stored in the
>   database.
> 
> Keeping bootresources.yaml around
> ---------------------------------
> 
> We have a couple of options for how to do away with editing
> bootresources.yaml. We can:
> 
> 1. Get rid of the file altogether; maas-import-pxe-files would either
>    given explicit configuration when run by celery, or would request it
>    from the region on startup.
> 2. Keep the file – it's useful for being able to re-run
>    maas-import-pxe-files manually should the need arise, and have it
>    updated by a celery job or using the RPC mesh.
> 
> I favour option 2, but I'm open to suggestions.

I don't have a strong opinion on exactly how it is implemented, but
I agree I think being able to run it manually is a requirement.

Would these changes be going into trusty/1.5?

\t