MAAS 2.1.0 Beta 1 Released!
Andres Rodriguez
andres.rodriguez at canonical.com
Tue Oct 4 21:56:10 UTC 2016
I'm happy to announce that MAAS 2.1.0 Beta 1 has been released.
*Availability*
MAAS 2.1.0 Beta 1 has been made available in:
*ppa:maas/next*
*Filing bugs*
Users can file bugs in [1], please use a prefix for the subject, such as [
2.1].
[1] https://bugs.launchpad.net/maas/+filebug
2.1.0 Beta 1
Important Announcements
-
New Hardware Enablement Kernels naming convention
Starting from MAAS 2.1 and Ubuntu Xenial, MAAS is adhering to a new naming
convention for hardware enablement kernels. On Xenial and above, MAAS will
not support HWE kernels with the old naming convention, but it will support
HWE kernel channel. For Ubuntu Xenial and Yakkety, currently available
kernels in MAAS now are:
-
ga-<version>
The GA, or general availability kernel is the kernel which the Ubuntu
release shipped with. For example ‘ga-16.04’ is the default 4.4 kernel
which shipped on Ubuntu Xenial. The ga kernel contains all bug and security
fixes provided by the Ubuntu archives. Deployments which use the ga kernel
will stay at the same kernel version through upgrades until the entire
release is upgraded with ‘do-release-upgrade.’
-
hwe-<version>
The latest Hardware Enablement Kernel currently available in a given Ubuntu
release. As new Hardware Enable Kernels are released with new Ubuntu
releases the hwe-<version> kernel will be upgraded up until the next LTS.
For example hwe-16.04 is currently the 16.04 GA kernel. Once 16.10 is
released the hwe-16.04 kernel will be upgraded to the 16.10 GA kernel. The
kernel will continue to be upgraded up until and including the 18.04 GA
kernel.
-
New Simplestreams Version - Update your images & your Image repositories
In order to support the new kernels, MAAS has updated the version of the
MAAS Image streams. Previously MAAS has been using the Streams Version 2,
and as of MAAS 2.1 it will use the MAAS Streams Version 3.
All users who upgrade from an earlier version of MAAS who have been using
the default image mirror, will be automatically migrated to the new version
of streams.
For all those users running a custom mirror, MAAS won’t make the migration
automatically. Users are requested to update their image mirror to match
the latest images. This image mirror is now available at
http://images.maas.io/ephemeral-v3/.
Major new features
-
Support for Low Latency kernels.
Starting from MAAS 2.1 Beta 1 and Ubuntu Xenial, MAAS will be making
available the ability to install low latency kernels. Low latency kernels
are available on i386 and amd64 for both GA and HWE kernels. The currently
available lowlatency kernels are
-
hwe-x-lowlatency - For using the Xenial Lowlatency kernel on Trusty
-
ga-16.04-lowlatency - For using the GA lowlatency kernel on Xenial
-
hwe-16.04-lowlatency - For using the HWE lowlatency kernel on Xenial.
-
Bootloaders are now provided in the SimpleStream.
Previously bootloaders where downloaded on the Rack Controller from the
Ubuntu archives for each architecture MAAS had images for. Starting with
MAAS 2.1 Beta 1 bootloaders are downloaded with the images from the
SimpleStream. All Rack Controllers retrieve all supported bootloaders from
the Region Controller. MAAS no longer directly interacts with the Ubuntu
archives.
In the case that bootloaders are missing from the SimpleStream MAAS will
attempt to locate previous downloads of the bootloader as well as package
installs of the bootloader.
Minor new features
-
Active Device Discovery - Map your subnet
To complete MAAS’ Active Discovery, starting from beta 1 MAAS 2.1 now
allows the user to ‘Map a subnet’, both automatically at regular intervals,
or manually:
-
Manually
Administrators can now Map a subnet manually from the Subnet Details page
under the ‘Take Action’ option. This will allow administrators to map their
subnet. By default, this will use ping but if nmap is installed, it will
automatically use nmap.
-
Automatically
Administrators can now chose to Map their subnets Automatically at regular
intervals. This allows administrators to have MAAS always probe on the
network to find new devices. By default, the automatic mechanism is
enabled, but no subnet is enabled by default.
To automatically map each subnet, please refer to the ‘Active Discovery’
section on the subnet details page.
Bugs fixed in this release
-
LP: #1392763 When changing sync-url via the UI, it's not obvious if
syncing starts on its own or not
-
LP: #1508975 maas deletes products/images locally that do not exist
remotely
-
LP: #1481285 1.8 Boot images tick boxes should be orange
-
LP: #1629402 [2.1] please cleanup log format for new interface
monitoring state
-
LP: #1629011 Missing punctuation in disk erasing options
-
LP: #1629008 Missing preposition sentence disk erasing options
-
LP: #1629004 Typo: "futher"
-
LP: #1628052 [2.1, FUJ] Help text in input fields is missing 'e.g'
-
LP: #1459888 Too much spacing between checkboxes/releases in the
'Images'
-
LP: #1627039 [2.1] Discovery object and view doesn't set a flag when
the device is the DHCP server
-
LP: #1627038 [2.1] SSH key import should use the specified HTTP proxy
if one exists
-
LP: #1625714 DHCP services on rack controllers only publishes
external NTP servers
-
LP: #1625711 Peer selection for NTP servers on region controllers is
broken
-
LP: #1593388 Changing a boot source URL while images are being
download doesn't interrupt current downloads to use the new URL
-
LP: #1623878 [2.1] mDNS label contains disallowed characters
-
LP: #1394792 MAAS could do a better job of reporting image download
status
-
LP: #1623110 [2.1] Networks page doesn't load fully on yakkety
-
LP: #1629896 [2.1] Deployment defaulting to hwe-16.04 instead of
ga-16.04
-
LP: #1629491 [2.1] After upgrade to latest trunk (pre-beta1) and
after updating images, machines fail to pxe boot due to missing hwe-x kernel
-
LP: #1629142 2.1 DHCP reported as enabled but not running
-
LP: #1629045 [2.1] When failing to download images, MAAS leaves old
files in the fs
-
LP: #1629022 [2.1, UI] Broken 'images page' link
-
LP: #1629019 [2.1 ipv6] log_host needs to be ipv6 when booting
ipv6-only
-
LP: #1628298 [2.1 UI] SSH keys not listed on user page and no button
to add keys
-
LP: #1628213 [2.1 yakkety UI] First user journey doesn't display and
can't be skipped
-
LP: #1627363 [2.1] 'NoneType' object has no attribute 'external_dhcp'
-
LP: #1627019 [2.1, rev5385] NTP services on region/rack keep showing
as ON/OFF constantly
-
LP: #1623634 [2.1, UX] Trying to cancel an image import from the new
Images page results on it not being cancelled on the backend.
-
LP: #1589640 [2.0b6] MAAS should validate a boot source path actually
provides images
Known issues and workarounds
-
Trusty images not available on fresh installs
The MAAS Images V3 streams do not yet have Ubuntu Trusty available. These
are currently being built to be made available.
User’s upgrading from a previous version of MAAS that had originally
imported Trusty images will continue to be able to deploy Trusty. Once the
images are made available, MAAS will automatically update (if so
configured).
-
LP: #1627362 - expected string or bytes-like object
In some situations after an upgrade, accessing the dashboard might yield
error above. This is a difficult to easily reproduce issue. If you come
across it please contact a MAAS developer immediately.
https://bugs.launchpad.net/maas/+bug/1627362
--
Andres Rodriguez
Engineering Manager, MAAS
Canonical USA, Inc.
--
Andres Rodriguez
Engineering Manager, MAAS
Canonical USA, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/maas-devel/attachments/20161004/2484592c/attachment-0001.html>
More information about the Maas-devel
mailing list