maas-devel team mailing list archive

[Graham Binns <graham.binns@xxxxxxxxxxxxx>]

Hi all,

Just a quick update on how things are progressing w.r.t getting rid of
bootresources.yaml from the cluster:

 - boot image sources are now modelled in the database
 - maas-import-pxe-files and import_images celery job now* accept config
   as a blob. This is what we'll use to pass the DB-stored boot image
   sources to the job.
 - Raphäel has landed the API for creating, reading updating and
   deleting boot sources.
 - Jeroen has made sure that a sane configuration will be created for
   each cluster when the cluster is registered with the region.

Coming up:

 - Jeroen is working on paring back the structure of bootresources.yaml
   to its bare necessities. This is useful when someone needs to run the
   maas-import-pxe-files script manually, as you'll still need to pass
   it a config file. The new structure will reflect the structure of the DB
   models.
 - Raphäel is working on the UI, and Jeroen and I will join him on that
   once our current work items are complete.

In the future:

 - We'll remove any references to /etc/maas/bootresources.yaml and make
   sure that the file itself goes away.
 - We'll add code to monitor the progress of downloads.
 - We'll improve the code that reports when the import job is complete,
   so that there's not a period of time between its completion and and
   the boot images being reported in the UI.
 - We'll remove the maas-import-phte filxe-files script as a
   run-on-the-command-line option altogether, and make the job something
   that can be queried through the API (with download progress showing
   in the UI).

Questions, comments welcome.

Cheers,

~gmb

 * To land today