lp:~smoser/maas-images

Owned by Scott Moser
Get this repository:
git clone https://git.launchpad.net/~smoser/maas-images
Only Scott Moser can upload to this repository. If you are Scott Moser please log in for upload directions.

Branches

Name Last Modified Last Commit
cleanup/file-output 2018-12-14 19:00:39 UTC
Cleanup: be more specific about what should be created.

Author: Scott Moser
Author Date: 2018-10-22 07:45:36 UTC

Cleanup: be more specific about what should be created.

This puts more information in the config files on what output is expected.
Previously we were relying on the input type format in some cases to
determine what output to create.

The desire to do this was really to safely add '--no-gzip'
to the maas-cloudimg2eph2 if we were going to throw away the root-image.gz.
The gzip of root-image.gz would typically take > 2 minutes and then
the output would be promptly thrown away.

Now, in the configs we have:
 meph-v2.yaml:
   squashfs: False
   root_image: True
   enable_di: True

 meph-v3.yaml:
   squashfs: True
   root_image: False
   enable_di: False

There is one inconsitency there that we've addressed with an 'if release'
section in the code. meph-v3.yaml will build a root image for trusty.

Also added here is information about 'known_callers' and the start of
a shell test suite. At very least it allowed me to manually verify the
output of a before and after run.

Ideally we'd have tests that assert files created and contents look good.

cleanup/no-errant-ls-output 2018-11-19 18:12:03 UTC
kpack-from-image: show less confusing error-like messages.

Author: Scott Moser
Author Date: 2018-11-19 18:07:50 UTC

kpack-from-image: show less confusing error-like messages.

A normal run of kpack-from-image will have the following output on stderr:
  dpkg-query: no path found matching pattern /boot/vmlinux
  verflav is 4.18.0-11-generic
  ls: cannot access '/boot/vmlinux-4.18.0-11-generic*signed': No such file or directory

When examining error logs, both the 'dpkg-query' and 'ls:' output look
like errors but they are not.

The changes here silence both those errors and give better messages.

fix/add-new-signing-key 2018-11-19 15:03:33 UTC
Add 2018-09-17 archive signing key to local keyring.gpg

Author: Scott Moser
Author Date: 2018-11-19 15:03:33 UTC

Add 2018-09-17 archive signing key to local keyring.gpg

maas images needs to validate signatures from trusty and later.
For that reason, we can't just use and assume that package provided
 /usr/share/keyrings/ubuntu-archive-keyring.gpg
as current versions (disco) will not include the signing key for trusty
(2012-05-11), and older versions do not include the most recent
signing key (2018-09-17).

Because we want to be able to verify data of archive content back
to trusty, we just maintain our own keyring here.

feature/add-release-disco 2018-11-02 01:19:12 UTC
Add disco / 19.04 / Disco.

Author: Scott Moser
Author Date: 2018-11-02 01:10:13 UTC

Add disco / 19.04 / Disco.

This just updates conf/ to know about Disco.

master 2018-09-19 20:59:56 UTC
img2squashfs: fix when 'image' was a directory.

Author: Scott Moser
Author Date: 2018-09-19 20:59:56 UTC

img2squashfs: fix when 'image' was a directory.

This fixes img2squashfs for both '--format=dir' and --format=auto
(the default) when input is a directory.

Now the following works:
 img2squashfs my-dir/ /tmp/my-squashfs

bzr-revno: 412

15 of 5 results
This repository contains Public information 
Everyone can see this information.

Subscribers