maas-images

Merge lp://staging/~ltrager/maas-images/v3_squashfs_only into lp://staging/maas-images

  1. v3_squashfs_only
  2. Merge into maas-ephemerals
Proposed by Lee Trager
Status: Merged
Merged at revision: 376
Proposed branch: lp://staging/~ltrager/maas-images/v3_squashfs_only
Merge into: lp://staging/maas-images
Prerequisite: lp://staging/~smoser/maas-images/lp1689557-build-squashfs-trusty
Diff against target: 48 lines (+18/-2)
1 file modified
meph2/stream.py (+18/-2)
To merge this branch: bzr merge lp://staging/~ltrager/maas-images/v3_squashfs_only
Reviewer Review Type Date Requested Status
Blake Rouse (community) Approve
Andres Rodriguez (community) Needs Information
Review via email: mp+326129@code.staging.launchpad.net

Commit message

If the squashfs config option is set produce streams only with SquashFS images.

Any image which is only available as a root-image will be automatically
converted.

Description of the change

Sample stream is up at http://162.213.35.187/squashfs/ it does not contain Precise as maas-images currently ignores unsupported releases and we do not plan to support in in MAAS 2.3+.

To post a comment you must log in.
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Why squashfs *only*? We should continue to produce the root tarballs for trusty. There are still a lot of users on older versions of MAAS that would potentially be broken if we make the switch.

review: Needs Information
Revision history for this message
Scott Moser (smoser) wrote :

I agree with Andres. You'll need to make both image types available.

Revision history for this message
Lee Trager (ltrager) wrote :

Any version of MAAS which can use the V3 stream can deploy SquashFS images. In the current V3 stream if a release has a SquashFS image we only publish the SquashFS image. The only reason Trusty and Precise have yet to goto a SquashFS image is because they aren't available on http://cloud-images.ubuntu.com. If MAAS detects a release in the stream contains both a root-image and a SquashFS image the SquashFS image will be downloaded and the root-image will be ignored[1]. If a SquashFS image is added to an existing release version the root-image will be deleted and the SquashFS image will be downloaded[2]. So once the Trusty SquashFS image is released to the V3 stream no version of MAAS will use the root-image, even if its available.

[1] https://git.launchpad.net/maas/tree/src/maasserver/bootresources.py#n1084
[2] https://git.launchpad.net/maas/tree/src/maasserver/bootresources.py#n652

lp://staging/~ltrager/maas-images/v3_squashfs_only updated
375. By Lee Trager

Merge trunk

376. By Lee Trager

If upstream contains a root-image publish it along side the SquashFS image.

Revision history for this message
Lee Trager (ltrager) wrote :

I've updated the MP to publish both the root-image.gz and SquashFS image for Trusty. As previously mentioned any version of MAAS which can use the V3 stream will ignore the root-image.gz. The only effect this should have is increasing the stream size.

Revision history for this message
Blake Rouse (blake-rouse) wrote :

Looks good. Thanks for the fixes.

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches