lp:~bladernr/maas-cert-server/add-lxd-images

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~hardware-certification/maas-cert-server/trunk at revision 75

Jeff Lane : Approve on 2017-04-12

Diff: 33 lines (+15/-1)

1 file modified

usr/sbin/maniacs-setup (+15/-1)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

74. By Jeff Lane  on 2017-01-24

add the LXD cloud images to retrieve_virtualization_images()

73. By Rod Smith on 2017-01-19

Fixes oldish but minor bug that caused maniacs-setup to complain about small MAAS API changes.

72. By Rod Smith on 2016-12-09

This merge adds automatic configuration of virtualization images to /etc/xdg/canonical-certification.conf via MAAS curtin userdata files. Specifically:

- The node uses wget to see what images are available in the gateway's
  (assumed to be MAAS server's, as in other curtin userdata functions)
  web server's /cloud directory.
- If one or more images with a filename of the form
  ".*$DISTRIB_CODENAME-server-cloudimg-$arch.*img" exists, the first of
  these is set in the conf file.
- If such an image does not exist, but image(s) of the form
  ".*server-cloudimg-$arch.*img" exists, the last of these is set in
  the conf file. (Presumably the last one will be the most recent
  Ubuntu version.)

71. By Rod Smith on 2016-12-09

Some simple formatting changes I noticed would be desirable when doing a MANIACS revision.

70. By Jeff Lane  on 2016-11-18

hotfix to address changes in curtin_userdata

69. By Rod Smith on 2016-11-17

Make maniacs-setup less aggressive in what it pulls down for cloud images for virtualization tests. This change enables the user to specify what Ubuntu releases and architectures to get (defaults to the latest LTS and amd64 ONLY), then grabs the .img files for those versions only, omitting other versions and unnecessary extra files from the cloud-images.ubuntu.com site. This greatly reduces bandwidth used and storage space required on the server.

68. By Rod Smith on 2016-11-17

This is not-quite-a-fix for bug #1641971 (using maniacs-setup fails to import i386 images by default under MAAS 2.1, resulting in error messages). Instead of addressing the issue head-on, this version returns the script to the behavior it had in the past (with MAAS 2.0): It imports i386 custom images if and only if standard MAAS i386 images already exist on the server. The error messages seem to be a result of pxelinux being split out into its own unique image in MAAS 2.1, which was not the case with MAAS 2.0. This results in the need for a more complex test to see if an i386 image is loaded. Note that, because this doesn't precisely address the issues in bug #1641971, I have not marked this as a fix for that bug.

67. By Jeff Lane  on 2016-11-16

Removes the code at the end of the curtin_userdata files. This code was causing the deployments to choke, the default MAAS Curtin_userdata files no longer include those lines, so removal should be safe.

To test, I did Xenial custom and stock deployments on 2.1, and Xenial and Trusty custom and stock deployments on 2.0 and all were successful with the modified curtin_userdata files.

Power was also tested successfully on 2.0 using modified curtin_userdata files.

66. By Rod Smith on 2016-10-17

Branch versions 66 and 67: Fix bug #1634211, which caused deployments of Yakkety (Ubuntu 16.10) to fail. The cause was use of the "apt-key" command to import APT keys; somehow this command seems to have been leaving a file open in /dev, which prevented it from being unmounted. This may be a bug in apt-key, which deserves more investigation; or we could look into other ways to import this key. As the import of this key simply quiets some warnings when using APT for system maintenance later, removing the offending command is a quick workaround, which is what this patch does.

65. By Jeff Lane  on 2016-09-14

Modifies maniacs-setup to download a mirror of cloud-images.ubuntu.com (it downloads ONLY the specified versions set up in GLOBALS and prompts the user for each one).

I've tested this on digital-ocean and it seems to work for both the case of a new server and a serve where we're re-running with -d.