Maas Driver Download


MAAS Image Builder is an alternative to packer for creating MAAS images.

In order to use MAAS Image Builder, you must purchase Ubuntu Advantage for Infrastructure.

With the MAAS Image Builder, you can:

Tap and Drive with Maas Driver. For a Unique Driving Experience. ZeMaas promises you a “Smart & Convenient” journey with our Maas Driver app. A better way to earn at your own pace and availability, meet new people and drive around safely! IBM's technical support resource for all IBM products and services including downloads, fixes, drivers, APARs, product documentation, Redbooks, whitepapers and technotes.

  • install MAAS Image Builder via a private Canonical PPA (which you can request)
  1. Drive and earn with every request you get on the Maas Driver app! Maas Driver marks one of the main apps offered by ZeMaas Technologies. The app is designed for all drivers out there to fit their daily schedule and elevate driving experiences with added earnings, flexible working hours and fulfilment!
  2. Download File MAAS DX 5000 Discription -PROGRAMMING SOFTWARE Download File. CRT 279 DRIVERS Download File.

You can customize most images as much or as little as you wish, then use them to commission machines with MAAS.

Install MAAS Image Builder

To get MAAS Image Builder, you must be subscribed to a private PPA provided by Canonical Support to those customers who have purchased Ubuntu Advantage for Infrastructure. Note that the steps below will fail if you have not purchased Ubuntu Advantage and been subscribed to the private PPA by your Canonical support rep.

Once subscribed, you need to obtain your credentials at:

Also, you must add the repository with the add-apt-repository command. Note: Be sure to substitute your unique URL in the command below:

Once you have added the private PPA, you can install the Image Builder like this:

All done? Great! Now you can build and customize images for MAAS machines, as shown in the sections below.

Create custom CentOS images

MAAS already provides the latest available CentOS 6, CentOS 7, and CentOS 8 for automatic download. If you need something else, though, MAAS Image Builder supports the ability to create various CentOS images.

Network Requirements

Access to the Internet is required, since you will need to start with one of these:

  • - OS, updates, and extra repositories
  • - EPEL
  • - Canonical maintained cloud-init repository

Creating images behind a proxy

MAAS Image Builder can create CentOS images behind a proxy – just set the ‘http_proxy’ environment variable to your particular proxy. Once deployed, yum will use this MAAS-configured proxy.

Creating the images

maas-image-builder is designed to automate the process of generating the images for MAAS and curtin. Here are some specific examples:

Customizing CentOS images

Starting from MAAS Image Builder 1.0.4, customization of CentOS images is now supported. You can provide a custom kickstart, in addition to the kickstart that MAAS Image Builder uses to create the images. You can customize your image like this:

Uploading the image into MAAS

Custom CentOS images can be uploaded to MAAS as shown in the command below. Do note that the name must start with ‘centos’ and must be one line:

You can use the MAAS WebUI to check that your custom CentOS image is valid and selectable for deployment.

Building RHEL images

Currently, MAAS only supports RHEL as a custom image. In future versions of MAAS, RHEL will be natively supported.

Some Requirements

In order to create RHEL images, you will need access to:

  • A RHEL DVD ISO - Contains all RHEL archives which are not available without a license
  • - Access to the EPEL repository to install required deps
  • - Access to the Canonical maintained cloud-init copr repository

Creating images behind a proxy

MAAS image builder supports creating RHEL images behind a proxy. To use a proxy when building a RHEL image, just set the ‘http_proxy’ environment variable to your local proxy. Once deployed, yum will use the MAAS-configured proxy.

Creating the images

To generate a usable RHEL image, maas-image-builder automates image generation; these images can be used by MAAS and curtin.


Install into MAAS

Maas Driver Download Windows 7

The custom RHEL image can be uploaded to MAAS, but note that the name must start with ‘rhel’ and must be expressed as a single line, like this:

Building Windows Images

Since Windows is a proprietary operating system, MAAS can’t download these images. You need to manually generate images to use with MAAS. On the upside, the end result will be much simpler, since there are CLI and WebUI tools to upload a Windows ISO – which helps automate the process.

Hyper-V 2012 R2
In this example, Windows Hyper-V 2012 R2 is used, but rest assured that multiple versions are supported. Download the Hyper-V 2012 R2 ISO from Microsoft, so it can be used in the image generation process. You can obtain the download at:

Maas Driver Download Windows 10

Other supported versions include (for --windows-edition):

  • win2012
  • win2012r2
  • win2012hv
  • win2012hvr2
  • win2016
  • win2016hv

Image Builder


MAAS Image builder can automate the process of generating images for MAAS and curtin. In this instance, though, you need Windows drivers for your specific hardware. You can obtain these windows drivers with the following command:

As an example, consider:

Please note that this will not install any Windows updates. In order to obtain an up-to-date image of Windows, be sure provide the –windows-updates flag. This requires access to a bridged connection with a DHCP server, an interface that can be specified with -i.

Mass storage driver download windows 7

Also note that you may be required to have specific Windows drivers for this image to work in your hardware. Be sure you inject those drivers when installing them. Those drivers are the default *.inf files.


You can debug the Windows installation process by connecting to localhost:5901 using a VNC client.

Install into MAAS

The generated images need to be placed into the correct directories so MAAS can deploy them onto a node:

Now, using the MAAS WebUI, a node can be selected to use Windows Hyper-V 2012 R2. This selection gets reset when a node is stopped, so make sure to set it before starting nodes. You can also set the default operating system (and release) in the settings menu, which removes the need to set it per-node.

Dealing with other custom images

To install other custom images, use the following command sequence:

As an example: