Merge ~ack/ubuntu/+source/maas:transitional-snap into ubuntu/+source/maas:ubuntu/devel

[Alberto Donato]

Transitional package to install and migrate to snap

This branch drops MAAS source code from the snap, and provides a transitional package which installs the snap and migrates existing deb-based installs to it.

[Julian Andres Klode (juliank)]

I thinl the Breaks should be unversioned Conflicts for all packages that are not transitional packages (keeping the Replaces, though), and the remaininng Breaks+Replaces should be (<< 1:0.1~).

Conflicts are needed for update-manager to correctly replace the packages.

[Julian Andres Klode (juliank)]

Ugh, submitted to early.

Also, the Makefile is superfluous, get rid of it.

review: Needs Fixing

fedd401... by Alberto Donato on 2020-02-11

add dependency on snapd, build only for architectures for which snap is available

22f45c9... by Alberto Donato on 2020-02-11

fix Breaks/Conflicts/Replaces per review

7372649... by Alberto Donato on 2020-02-11

remove extra files

[Alberto Donato (ack)]

@juliank Thanks, updated as suggested

b40d807... by Alberto Donato on 2020-02-11

drop gitignore too

9a1cb0f... by Alberto Donato on 2020-02-11

more fixes for dependencies, change architecture back to "all"

[Julian Andres Klode (juliank)]

Thanks, I'm going to abstain from approving that now, as I've not really had time to look at the actual preinst stuff yet, only focused on the packaging itself.

Maybe someone else does.

review: Abstain

[Julian Andres Klode (juliank)]

If not, I'll have another look tomorrow, of course.

[Julian Andres Klode (juliank)]

This looks ok I guess. I'm not sure if the apt-mark call in the postinst works - I don't think it should, apt should probably do some locking there to prevent it from being called while installing, as it writes that file after the install is done, but apart from that, it seems good to go.

review: Approve

[Alberto Donato (ack)]

> This looks ok I guess. I'm not sure if the apt-mark call in the postinst works
> - I don't think it should, apt should probably do some locking there to
> prevent it from being called while installing, as it writes that file after
> the install is done, but apart from that, it seems good to go.

I wasn't sure if that's allowed (or best practice) but it does seem to work fine.

I wonder if there's another way to do that without calling apt-mark.

[Julian Andres Klode (juliank)]

Let's go to needs information for now, as I need to make sure the apt-mark thing is actually legal and I'm not going to break it by making apt-mark acquire locks.

review: Needs Information

[Alberto Donato (ack)]

@Julian, given that apt-mark seems to be acceptable (per IRC discussion), is there anything else needed for this branch?

[Julian Andres Klode (juliank)]

review: Approve

Unmerged commits

9a1cb0f... by Alberto Donato on 2020-02-11

more fixes for dependencies, change architecture back to "all"

b40d807... by Alberto Donato on 2020-02-11

drop gitignore too

7372649... by Alberto Donato on 2020-02-11

remove extra files

22f45c9... by Alberto Donato on 2020-02-11

fix Breaks/Conflicts/Replaces per review

fedd401... by Alberto Donato on 2020-02-11

add dependency on snapd, build only for architectures for which snap is available

aed9bfe... by Alberto Donato on 2020-02-11

transitional deb to the snap

d470ab8... by Andres Rodriguez on 2019-06-11

Import patches-unapplied version 2.6.0-7802-g59416a869-0ubuntu1 to ubuntu/eoan-proposed

Imported using git-ubuntu import.

Changelog parent: df824755bcbdfc1ed2617c7783779788f963d322

New changelog entries:
  * New upstream release, MAAS 2.6.0.
  * New upstream release, MAAS 2.6.0 RC 2.
  * New upstream release, MAAS 2.6.0 RC 1.
  * New upstream release, MAAS 2.6.0 beta 4.
  * New upstream release, MAAS 2.6.0 beta 3.

df82475... by Andres Rodriguez on 2019-04-27

Import patches-unapplied version 2.6.0~beta2-7695-g691e14ea3-0ubuntu1 to ubuntu/eoan-proposed

Imported using git-ubuntu import.

Changelog parent: a9dd877664cd2c489aa5df52ecdbec7a6ad0c744

New changelog entries:
  * New upstream release, MAAS 2.6.0 beta 2.
  * New upstream release, MAAS 2.6.0 beta 1.
  * New upstream release, MAAS 2.6.0 alpha 2
  * New upstream release, MAAS 2.6.0 alpha 1

a9dd877... by Andres Rodriguez on 2018-12-11

Import patches-unapplied version 2.5.0-7442-gdf68e30a5-0ubuntu1 to ubuntu/disco-proposed

Imported using git-ubuntu import.

Changelog parent: 9907702f8a476dbaf3121cca495fa846cbee823a

New changelog entries:
  * New upstream release. MAAS 2.5.0 introduces:
    - Proxy MAAS communication through the rack controller.
    - HA - Rack to region communication no longer needs VIPs.
    - KVM (pod) - Support for networking.
    - KVM (pod) - Re-designed WebUI.
    - CentOS storage support.
    - ESXi deployment support.
    - Machine listing - Re-designed UI.
    - Enlistment - now runs commissioning scripts.
    - Add machines by only specifying IPMI credentials.
  * New upstream release.
  * New upstream bugfix release.
  * New upstream bugfix release.
  * New upstream bugfix release.

9907702... by Andres Rodriguez on 2018-10-03

Import patches-unapplied version 2.5.0~beta2-7291-gd0345ced5-0ubuntu1 to ubuntu/cosmic-proposed

Imported using git-ubuntu import.

Changelog parent: e6f85657b46b141c96c4a6f3939c0b875903628b

New changelog entries:
  * New upstream release. (LP: #1796937)
  * debian/maas-dhcp.maas-{dhcpd,dhcpd6}.service: Require dhcpd stop
    in 8 seconds, if not kill it with 'mixed' mode.
  * debian/control: Drop python3-jinja2 as it is no longer needed to
    generate documentation.
  * debian/maas-common.prerm: Add & handle stop of maas-syslog.service.
  * debian/maas-common.postrm:
    - Run debhelper handling before manual removal actions.
    - Purge maas-syslog related files.
  * debian/maas-rack-controller.prerm: Add & handle stop of
    maas-rackd.service.
  * debian/maas-rack-controller.postrm: Purge http and rpc.state files.
  * debian/maas-region-api.postrm: Purge maas-regiond socket file.

diff --git a/.babelrc b/.babelrc
deleted file mode 100644
index 5d9a7c9..0000000
--- a/.babelrc
+++ /dev/null
@@ -1,7 +0,0 @@
-{
-    "presets": ["@babel/preset-env"],
-    "plugins": [
-        ["angularjs-annotate", { "explicitOnly" : true }],
-        "@babel/plugin-proposal-class-properties"
-    ]
-}
diff --git a/.coveragerc b/.coveragerc
deleted file mode 100644
index f00deba..0000000
--- a/.coveragerc
+++ /dev/null
@@ -1,21 +0,0 @@
-[run]
-branch = True
-source = src
-omit =
-  */testing.py
-  */testing/*
-  */tests/*
-
-[report]
-omit =
-  src/*/migrations/*
-  src/maastesting/*
-exclude_lines =
-    # Have to re-enable the standard pragma
-    pragma: no cover
-    # Don't complain if tests don't hit defensive assertion code:
-    raise NotImplementedError
-
-[html]
-directory = coverage
-title = Coverage for MAAS
diff --git a/.ctags b/.ctags
deleted file mode 100644
index 0eb9382..0000000
--- a/.ctags
+++ /dev/null
@@ -1,4 +0,0 @@
---python-kinds=-iv
---exclude=*.js
---extra=+f
---links=yes
diff --git a/.eslintrc.js b/.eslintrc.js
deleted file mode 100644
index bded01a..0000000
--- a/.eslintrc.js
+++ /dev/null
@@ -1,24 +0,0 @@
-module.exports = {
-    "env": {
-        "browser": true,
-        "es6": true,
-        "jasmine": true
-    },
-    "extends": ["angular", "eslint:recommended"],
-    "globals": {
-        "__dirname": false,
-        "angular": false,
-        "Atomics": "readonly",
-        "inject": false,
-        "setTimeout": false,
-        "SharedArrayBuffer": "readonly"
-    },
-    "parserOptions": {
-        "ecmaVersion": 2018,
-        "sourceType": "module"
-    },
-    "rules": {
-        "angular/di": [2, "function", { "matchNames": true }],
-        "no-unused-vars": [2, { "args": "none" }]
-    }
-};
diff --git a/.flake8 b/.flake8
deleted file mode 100644
index 247c850..0000000
--- a/.flake8
+++ /dev/null
@@ -1,2 +0,0 @@
-[flake8]
-ignore = E123,E305,E402,E731
diff --git a/CHANGELOG b/CHANGELOG
deleted file mode 120000
index 6f0024c..0000000
--- a/CHANGELOG
+++ /dev/null
@@ -1 +0,0 @@
-docs/changelog.rst
\ No newline at end of file
diff --git a/HACKING.rst b/HACKING.rst
deleted file mode 100644
index 8f1c0b9..0000000
--- a/HACKING.rst
+++ /dev/null
@@ -1,707 +0,0 @@
-.. -*- mode: rst -*-
-
-************
-Hacking MAAS
-************
-
-
-Coding style
-============
-
-MAAS follows the `Launchpad Python Style Guide`_, except where it gets
-Launchpad specific, and where it talks about `method naming`_. MAAS
-instead adopts `PEP-8`_ naming in all cases, so method names should
-usually use the ``lowercase_with_underscores`` form.
-
-.. _Launchpad Python Style Guide:
-  https://dev.launchpad.net/PythonStyleGuide
-
-.. _method naming:
-  https://dev.launchpad.net/PythonStyleGuide#Naming
-
-.. _PEP-8:
-  http://www.python.org/dev/peps/pep-0008/
-
-
-Prerequisites
-=============
-
-Container
-^^^^^^^^^
-
-There's a configure-lxd-profile script in utilities, that will set
-up a LXD profile that is configured properly.
-
-
-Dependencies
-^^^^^^^^^^^^
-
-You can grab MAAS's code manually from Launchpad but Git_ makes it
-easy to fetch the last version of the code. First of all, install
-Git::
-
-    $ sudo apt install git
-
-.. _Git: https://git-scm.com/
-
-Then go into the directory where you want the code to reside and run::
-
-    $ git clone https://git.launchpad.net/maas && cd maas
-
-MAAS depends on Postgres, isc-dhcp, bind9, and many other packages. To install
-everything that's needed for running and developing MAAS, run::
-
-    $ make install-dependencies
-
-Careful: this will ``apt-get install`` many packages on your system,
-via ``sudo``. It may prompt you for your password.
-
-This will install ``bind9``. As a result you will have an extra daemon
-running. If you are a developer and don't intend to run BIND locally,
-you can disable the daemon by inserting ``exit 1`` at the top of
-``/etc/default/bind9``. The package still needs to be installed for
-tests though.
-
-Python development dependencies are pulled automatically from
-`PyPI`_ when ``buildout`` runs. (``buildout`` will be automatically
-configured to create a cache, in order to improve build times.
-See ``utilities/configure-buildout``.)
-
-Javascript development dependencies are pulled automatically from
-`npm`_ when ``make`` runs. (``npm`` will be automatically
-configured to use a cache, in order to improve build times.)
-
-.. _PyPI:
-  http://pypi.python.org/
-.. _npm:
-  https://www.npmjs.com/
-
-
-Git Workflow
-^^^^^^^^^^^^
-
-You will want to adjust your git repository of lp:maas some before you start
-making changes to the code. This includes setting up your own copy of
-the repository and making your changes in branches.
-
-First you will want to rename the origin remote to upstream and create a new
-origin in your namespace.
-
-    $ git remote rename origin upstream
-    $ git remote add origin git+ssh://{launchpad-id}@git.launchpad.net/~{launchpad-id}/maas
-
-Now you can make a branch and start making changes.
-
-    $ git checkout -b new-branch
-
-Once you have made the changes you want, you should commit and push the branch
-to your origin.
-
-    $ git commit -m "My change" -a
-    $ git push origin new-branch
-
-Now you can view that branch on Launchpad and propose it to the maas
-repository.
-
-Once the branch has been merged and your done with it you can update your
-git repository to remove the branch.
-
-    $ git fetch upstream
-    $ git checkout master
-    $ git merge upstream/master
-    $ git branch -d new-branch
-
-
-Optional
-^^^^^^^^
-
-The PyCharm_ IDE is a useful tool when developing MAAS. The MAAS team does not
-endorse any particular IDE, but ``.idea`` `project files are included with
-MAAS`_, so PyCharm_ is an easy choice.
-
-.. _PyCharm:
-  https://www.jetbrains.com/pycharm/
-
-.. _project files are included with MAAS:
-  https://intellij-support.jetbrains.com/entries/23393067-How-to-manage-projects-under-Version-Control-Systems
-
-Running tests
-=============
-
-To run the whole suite::
-
-    $ make test
-
-To run tests at a lower level of granularity::
-
-    $ ./bin/test.region src/maasserver/tests/test_api.py
-    $ ./bin/test.region src/maasserver/tests/test_api.py:AnonymousEnlistmentAPITest
-
-The test runner is `nose`_, so you can pass in options like
-``--with-coverage`` and ``--nocapture`` (short option: ``-s``). The
-latter is essential when using ``pdb`` so that stdout is not
-adulterated.
-
-.. _nose: http://readthedocs.org/docs/nose/en/latest/
-
-.. Note::
-
-   When running ``make test`` through ssh from a machine with locales
-   that are not set up on the machine that runs the tests, some tests
-   will fail with a ``MismatchError`` and an "unsupported locale
-   setting" message. Running ``locale-gen`` for the missing locales or
-   changing your locales on your workstation to ones present on the
-   server will solve the issue.
-
-
-Emitting subunit
-^^^^^^^^^^^^^^^^
-
-Pass the ``--with-subunit`` flag to any of the test runners (e.g.
-``bin/test.rack``) to produce a `subunit`_ stream of test results. This
-may be useful for parallelising test runs, or to allow later analysis of
-a test run. The optional ``--subunit-fd`` flag can be used to direct the
-results to a different file descriptor, to ensure a clean stream.
-
-.. _subunit: https://launchpad.net/subunit/
-
-
-Running JavaScript tests
-^^^^^^^^^^^^^^^^^^^^^^^^
-
-The JavaScript tests are run using Karma_. Chromium and PhantomJS are the
-default browser but any browser supported by Karma can be used to run the
-tests.::
-
-    $ make test-js
-
-If you want to run the JavaScript tests in debug mode so you can inspect the
-code inside of a running browser you can launch Karma_ manually.::
-
-    $ ./bin/karma start src/maastesting/karma.conf.js --browsers Chrome --no-single-run
-
-.. _Karma: http://karma-runner.github.io/
-
-
-Frontend development
-====================
-
-For faster development, Webpack watch mode can be run with::
-
-    $ make watch-javascript
-
-JavaScript debugging
-^^^^^^^^^^^^^^^^^^^^
-
-Angularjs debugInfo, which provides hooks for browser debugging tools
-like Batarang, is disabled by default. To re-enable debugInfo,
-run ``angular.reloadWithDebugInfo();`` in the browser console.
-
-See https://docs.angularjs.org/guide/production#disabling-debug-data for details.
-
-
-JavaScript linting and formatting
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-JSLint can be run with::
-
-    $ make lint-js
-
-This will also run `prettier-check` which will notify you
-if there are formatting issues.
-
-Prettier can be run in write mode to correct formatting with::
-
-    $ make format
-
-ESLint is also available (the intention is to eventually replace JSLint),
-and can be run with::
-
-    $ ./bin/yarn lint
-
-
-Production MAAS server debugging
-================================
-
-When MAAS is installed from packaging it can help to enable debugging features
-to triage issues.
-
-Log all API and UI exceptions
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-By default MAAS only logs HTTP 500 - INTERNAL_SERVER_ERROR into the
-regiond.log. To enable logging of all exceptions even exceptions where MAAS
-will return the correct HTTP status code.::
-
-  $ sudo sed -i 's/DEBUG = False/DEBUG = True/g' \
-  >   /usr/lib/python3/dist-packages/maasserver/djangosettings/settings.py
-  $ sudo service maas-regiond restart
-
-Run regiond in foreground
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-It can help when debugging to run regiond a foreground process so you can
-interact with the regiond by placing a breakpoint in the code. Once you have
-placed a breakpoint into the code you want to inspect you can start the regiond
-process in the foreground.::
-
-  $ sudo service maas-regiond stop
-  $ sudo -u maas -H \
-  >   DJANGO_SETTINGS_MODULE=maasserver.djangosettings.settings \
-  >   twistd3 --nodaemon --pidfile= maas-regiond
-
-
-.. Note::
-
-   By default a MAAS installation runs 4 regiond processes at the same time.
-   This will change it to only run 1 process in the foreground. This should
-   only be used for debugging. Once finished the breakpoint should be removed
-   and maas-regiond service should be started.
-
-Run rackd in foreground
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-It can help when debugging to run rackd a foreground process so you can
-interact with the rackd by placing a breakpoint in the code. Once you have
-placed a breakpoint into the code you want to inspect you can start the rackd
-process in the foreground.::
-
-   $ sudo service maas-rackd stop
-   $ sudo -u maas -H /usr/bin/authbind --deep /usr/bin/twistd3 --nodaemon --pidfile= maas-rackd
-
-
-Development MAAS server setup
-=============================
-
-Access to the database is configured in
-``src/maasserver/djangosettings/development.py``.
-
-The ``Makefile`` or the test suite sets up a development database
-cluster inside your branch. It lives in the ``db`` directory, which
-gets created on demand. You'll want to shut it down before deleting a
-branch; see below.
-
-First, set up the project. This fetches all the required dependencies
-and sets up some useful commands in ``bin/``::
-
-    $ make
-
-Create the database cluster and initialise the development database::
-
-    $ make syncdb
-
-Optionally, if all you want to do is to take a look around the UI and
-API, without interacting with real machines or VMs, populate your
-database with the sample data::
-
-    $ make sampledata
-
-You can login as a simple user using the test account (username: 'test',
-password: 'test') or the admin account (username: 'admin', password: 'test').
-
-If you want to interact with real machines or VMs, it's better to use
-the snap. Instead of building a real snap, though, you can use
-'snapcraft prime' to create the prime directory. That has all the
-contents of the snap, but it's in a plain directory insted of in a
-squashfs image. Using a directory is better for testing, since you can
-change the files in there and not rebuild the snap.
-
-There's a ``sync-dev-snap`` make target to automate this:
-
-    $ make sync-dev-snap
-
-The ``sync-dev-snap`` target creates a clean copy of your working tree (so
-that you don't have to run 'make clean' before building the snap) in
-build/dev-snap and creates the snap directory in build/dev-snap/prime.
-
-You can now install the snap:
-
-    $ sudo snap try --devmode build/dev-snap/prime
-
-Note that 'snap try' is used instead of 'snap install'. The maas snap
-should now be installed:
-
-    $ snap list
-    Name  Version                          Rev   Developer  Notes
-    core  16-2.27.5                        2774  canonical  core
-    maas  2.3.0~alpha3-6225-gaa05ba6-snap  x1               devmode,try
-
-Next you need to initialize the snap, just like you would normally do:
-
-    $ sudo maas init
-
-And now you're ready to make changes to the code. After you've change
-some source files and want to test them out, run the ``sync-dev-snap``
-target again:
-
-    $ make sync-dev-snap
-
-You should now see that you files were synced to the prime directory. If
-you changed JS and HTML files only, you should see that changes straight
-away by just reloading the browser. If you changed Python files, you
-need to restart MAAS:
-
-    $ sudo service snap.maas.supervisor restart
-
-VMs or even real machines can now PXE boot off your development snap.
-But of course, you need to set up the networking first. If you want to
-do some simple testing, the easiest is to create a networking in
-virt-manager that has NAT, but doesn't provide DHCP. If the name of
-the bridge that got created is `virbr1`, you can expose it to your
-container as eth1 using the following config:
-
-    eth1:
-      name: eth1
-      nictype: bridged
-      parent: virbr1
-      type: nic
-
-Of course, you also need to configure that eth1 interface. Since MAAS is
-the one providing DHCP, you need to give it a static address on the
-network you created. For example::
-
-    auto eth1
-    iface eth1 inet static
-      address 192.168.100.2
-      netmask 255.255.255.0
-
-Note that your LXD host will have the .1 address and will act as a
-gateway for your VMs.
-
-To shut down the database cluster and clean up all other generated files in
-your branch::
-
-    $ make clean
-
-
-Downloading PXE boot resources
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-To use PXE booting, each cluster controller needs to download several
-files relating to PXE booting. This process is automated, but it does
-not start by default.
-
-First create a superuser and start all MAAS services::
-
-    $ bin/maas-region createadmin
-    $ make run
-
-Substitute your own email.  The command will prompt for a choice of password.
-
-Next, get the superuser's API key on the `account preferences`_ page in the
-web UI, and use it to log into MAAS at the command-line::
-
-    $ bin/maas login dev http://localhost:5240/MAAS/
-
-.. _`account preferences`: http://localhost:5240/MAAS/account/prefs/
-
-Start downloading PXE boot resources::
-
-    $  bin/maas dev node-groups import-boot-images
-
-This sends jobs to each cluster controller, asking each to download
-the boot resources they require. This may download dozens or hundreds
-of megabytes, so it may take a while. To save bandwidth, set an HTTP
-proxy beforehand::
-
-    $ bin/maas dev maas set-config name=http_proxy value=http://...
-
-
-Running the built-in TFTP server
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-You will need to run the built-in TFTP server on the real TFTP port (69) if
-you want to boot some real hardware. By default, it's set to start up on
-port 5244 for testing purposes. To make it run on port 69, set the
-MAAS_TFTP_PORT environment variable before running make run/start::
-
-    export MAAS_TFTP_PORT=69
-
-
-Then you need install and configure the authbind, so that your user can
-bind to port 69::
-
-    * Install the ``authbind``package:
-
-      $ sudo apt install authbind
-
-    * Create a file ``/etc/authbind/byport/69`` that is *executable* by the
-      user running MAAS.
-
-      $ sudo touch /etc/authbind/byport/69
-      $ sudo chown $USER /etc/authbind/byport/69
-      $ sudo chmod u+x /etc/authbind/byport/69
-
-Now when starting up the MAAS development webserver, "make run" and "make
-start" will detect authbind's presence and use it automatically.
-
-
-Running the BIND daemon for real
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-There's a BIND daemon that is started up as part of the development service
-but it runs on port 5246 by default. If you want to make it run as a real
-DNS server on the box then set the MAAS_BIND_PORT environment variable
-before running make run/start::
-
-    export MAAS_BIND_PORT=53
-
-Then as for TFTP above, create an authbind authorisation::
-
-    $ sudo touch /etc/authbind/byport/53
-    $ sudo chown $USER /etc/authbind/byport/53
-    $ sudo chmod u+x /etc/authbind/byport/53
-
-and run as normal.
-
-
-Running the cluster worker
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The cluster also needs authbind as it needs to bind a socket on UDP port
-68 for DHCP probing::
-
-    $ sudo touch /etc/authbind/byport/68
-    $ sudo chown $USER /etc/authbind/byport/68
-    $ sudo chmod u+x /etc/authbind/byport/68
-
-If you omit this, nothing else will break, but you will get an error in
-the cluster log because it can't bind to the port.
-
-
-Configuring DHCP
-^^^^^^^^^^^^^^^^
-
-MAAS requires a properly configured DHCP server so it can boot machines using
-PXE. MAAS can work with its own instance of the ISC DHCP server, if you
-install the maas-dhcp package::
-
-    $ sudo apt install maas-dhcp
-
-Note that maas-dhcpd service definition referencese the maas-rackd
-service, which won't be present if you run a development service. To
-workaround edit /lib/systemd/system/maas-dhcp.service and comment out
-this line:
-
-    BindsTo=maas-rackd.service
-
-
-Non-interactive configuration of RBAC service authentication
-============================================================
-
-For development and automating testing purposes, it's possible to configure
-maas with the RBAC service in a non-interactive way, with the following::
-
-    $ sudo MAAS_CANDID_CREDENTIALS=user1:password1 maas configauth --rbac-url http://<url-of-rbac>:5000 --rbac-sevice-name <maas-service-name-in-RBAC>
-
-This will automatically handle logging in with Candid, without requiring the
-user to fill in the authentication form via browser.
-
-
-Development services
-====================
-
-The development environment uses *daemontools* to manage the various
-services that are required. These are all defined in subdirectories in
-``services/``.
-
-There are familiar service-like commands::
-
-  $ make start
-  $ make status
-  $ make restart
-  $ make stop
-
-The latter is a dependency of ``distclean`` so just running ``make
-distclean`` when you've finished with your branch is enough to stop
-everything.
-
-Individual services can be manipulated too::
-
-  $ make services/rackd/@start
-
-The ``@<action>`` pattern works for any of the services.
-
-There's an additional special action, ``run``::
-
-  $ make run
-
-This starts all services up and tails their log files. When you're
-done, kill ``tail`` (e.g. Ctrl-c), and all the services will be
-stopped.
-
-However, when used with individual services::
-
-  $ make services/regiond/@run
-
-it does something even cooler. First it shuts down the service, then
-it restarts it in the foreground so you can see the logs in the
-console. More importantly, it allows you to use ``pdb``, for example.
-
-A note of caution: some of the services have slightly different
-behaviour when run in the foreground:
-
-* regiond (the *webapp* service) will be run with its auto-reloading
-  enabled.
-
-There's a convenience target for hacking regiond that starts everything
-up, but with regiond in the foreground::
-
-  $ make run+regiond
-
-Apparently Django needs a lot of debugging ;)
-
-
-Adding new dependencies
-=======================
-
-Since MAAS is distributed mainly as an Ubuntu package, all runtime
-dependencies should be packaged, and we should develop with the
-packaged version if possible. All dependencies, from a package or not,
-need to be added to ``setup.py`` and ``buildout.cfg``, and the version
-specified in ``versions.cfg`` (``allowed-picked-version`` is disabled,
-hence ``buildout`` must be given precise version information).
-
-If it is a development-only dependency (i.e. only needed for the test suite, or
-for developers' convenience), simply running ``buildout`` like this will make
-the necessary updates to ``versions.cfg``::
-
-    $ ./bin/buildout -v buildout:allow-picked-versions=true
-
-
-Adding new source files
-=======================
-
-When creating a new source file, a Python module or test for example,
-always start with the appropriate template from the ``templates``
-directory.
-
-
-Database information
-====================
-
-MAAS uses Django_ to manage changes to the database schema.
-
-.. _Django: https://www.djangoproject.com/
-
-Be sure to have a look at `Django's migration documentation`_ before you make
-any change.
-
-.. _Django's migration documentation:
-    https://docs.djangoproject.com/en/1.8/topics/migrations/
-
-
-Changing the schema
-^^^^^^^^^^^^^^^^^^^
-
-Once you've made a model change (i.e. a change to a file in
-``src/<application>/models/*.py``) you have to run Django's `makemigrations`_
-command to create a migration file that will be stored in
-``src/<application>/migrations/builtin/``.
-
-Note that if you want to add a new model class you'll need to import it
-in ``src/<application>/models/__init__.py``
-
-.. _makemigrations: https://docs.djangoproject.com/en/1.8/ref/django-admin/#django-admin-makemigrations
-
-Generate the migration script with::
-
-    $ ./bin/maas-region makemigrations --name description_of_the_change maasserver
-
-This will generate a migration module named
-``src/maasserver/migrations/builtin/<auto_number>_description_of_the_change.py``.
-Don't forget to add that file to the project with::
-
-    $ git add src/maasserver/migrations/builtin/<auto_number>_description_of_the_change.py
-
-To apply that migration, run::
-
-    $ make syncdb
-
-
-Performing data migration
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-If you need to perform data migration, very much in the same way, you will need
-to run Django's `makemigrations`_ command. For instance, if you want to perform
-changes to the ``maasserver`` application, run::
-
-    $ ./bin/maas-region makemigrations --empty --name description_of_the_change maasserver
-
-This will generate a migration module named
-``src/maasserver/migrations/builtin/<auto_number>_description_of_the_change.py``.
-You will need to edit that file and fill the ``operations`` list with the
-options that need to be performed. Again, don't forget to add that file to the
-project::
-
-    $ git add src/maasserver/migrations/builtin/<auto_number>_description_of_the_change.py
-
-Once the operations have been added, apply that migration with::
-
-    $ make syncdb
-
-
-Examining the database manually
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-If you need to get an interactive ``psql`` prompt, you can use `dbshell`_::
-
-    $ bin/maas-region dbshell
-
-.. _dbshell: https://docs.djangoproject.com/en/dev/ref/django-admin/#dbshell
-
-If you need to do the same thing with a version of MAAS you have installed
-from the package, you can use::
-
-    $ sudo maas-region dbshell --installed
-
-You can use the ``\dt`` command to list the tables in the MAAS database. You
-can also execute arbitrary SQL. For example:::
-
-    maasdb=# select system_id, hostname from maasserver_node;
-                     system_id                 |      hostname
-    -------------------------------------------+--------------------
-     node-709703ec-c304-11e4-804c-00163e32e5b5 | gross-debt.local
-     node-7069401a-c304-11e4-a64e-00163e32e5b5 | round-attack.local
-    (2 rows)
-
-
-Viewing SQL queries during tests
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-If you need to view the SQL queries that are performed during a test, the
-`LogSQL` fixture can be used to output all the queries during the test.::
-
-    from maasserver.fixture import LogSQL
-    self.useFixture(LogSQL())
-
-Sometimes you need to see where in the code that query was performed.::
-
-    from maasserver.fixture import LogSQL
-    self.useFixture(LogSQL(include_stacktrace=True))
-
-
-Documentation
-=============
-
-Use `reST`_ with the `convention for headings as used in the Python
-documentation`_.
-
-.. _reST: http://sphinx.pocoo.org/rest.html
-
-.. _convention for headings as used in the Python documentation:
-  http://sphinx.pocoo.org/rest.html#sections
-
-
-Updating copyright notices
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Use the `Bazaar Copyright Updater`_::
-
-  bzr branch lp:bzr-update-copyright ~/.bazaar/plugins/update_copyright
-  make copyright
-
-Then commit any changes.
-
-.. _Bazaar Copyright Updater:
-  https://launchpad.net/bzr-update-copyright
diff --git a/INSTALL.txt b/INSTALL.txt
deleted file mode 100644
index 86ac315..0000000
--- a/INSTALL.txt
+++ /dev/null
@@ -1,418 +0,0 @@
-.. -*- mode: rst -*-
-
-
-Installing MAAS
-===============
-
-There are two main ways to install MAAS:
-
- * :ref:`From a package repository. <pkg-install>`
- * :ref:`As a fresh install from Ubuntu Server install
-   media. <disc-install>`
- * :ref:`Install MAAS in a LXC Container. <container-install>`
-
-
-MAAS Packages and Repositories
-------------------------------
-
-MAAS Packages
-^^^^^^^^^^^^^
-
-Installing MAAS from packages is straightforward. There are actually
-several packages that go into making up a working MAAS install, but
-for convenience, many of these have been gathered into a virtual
-package called 'maas' which will install the necessary components
-for a 'seed cloud', that is a single server that will directly
-control a group of nodes. The main packages are:
-
- * ``maas`` - seed cloud setup, which includes both the region
-   controller and the rack controller below.
- * ``maas-region-controller`` - includes the web UI, API and database.
- * ``maas-rack-controller`` - controls a group of machines under a
-   rack or multiple racks, including DHCP management.
- * ``maas-dhcp``/``maas-dns`` - required when managing dhcp/dns.
- * ``maas-proxy`` - required to provide a MAAS proxy.
-
-If you need to separate these services or want to deploy an additional
-rack controller, you should install the corresponding packages
-individually (see :ref:`the description of a typical setup <setup>`
-for more background on how a typical hardware setup might be
-arranged).
-
-There are two suggested additional packages 'maas-dhcp' and
-'maas-dns'. These set up MAAS-controlled DHCP and DNS services which
-greatly simplify deployment if you are running a typical setup where
-the MAAS controller can run the network (Note: These **must** be
-installed if you later set the options in the web interface to have
-MAAS manage DHCP/DNS).
-
-MAAS Package Repositories
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-While MAAS is available in the Ubuntu Archives per each release of
-Ubuntu, the version might not be the latest. However, if you would like
-to install a newer version of MAAS (the latest stable release), this is
-available in the following PPA:
-
- * `ppa:maas/stable`_
-
-.. Note::
-  The MAAS team also releases the latest development release of MAAS.
-  The development release is available in `ppa:maas/next`_. However, this
-  is meant to be used for testing and at your own risk.
-
-Adding MAAS package repository is simple. At the command line, type::
-
-  $ sudo add-apt-repository ppa:maas/stable
-
-You will be asked to confirm whether you would like to add this repository,
-and its key. Upon configumation, the following needs to be typed at the
-command line::
-
-  $ sudo apt-get update
-
-.. _ppa:maas/stable:
-  https://launchpad.net/~maas/+archive/ubuntu/stable
-.. _ppa:maas/next:
-  https://launchpad.net/~maas/+archive/ubuntu/next
-
-.. _pkg-install:
-
-Installing MAAS from the command line
--------------------------------------
-
-Installing a Single Node MAAS
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-At the command line, type::
-
-  $ sudo apt-get install maas
-
-This will install both the MAAS Region Controller and the MAAS Rack
-Controller, and will select sane defaults for the communication between
-the Rack Controller and the Region Controller. After installation,
-you can access the Web Interface. Then, there are just a few more setup
-steps :ref:`post_install`
-
-Reconfiguring a MAAS Installation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-You will see a list of packages and a confirmation message to
-proceed. The exact list will obviously depend on what you already have
-installed on your server, but expect to add about 200MB of files.
-
-The configuration for the MAAS controller will automatically run and
-pop up this config screen:
-
-.. image:: media/install_cluster-config.*
-
-Here you will need to enter the hostname for where the region
-controller can be contacted. In many scenarios, you may be running the
-region controller (i.e. the web and API interface) from a different
-network address, for example where a server has several network
-interfaces.
-
-Adding Rack Controllers
-^^^^^^^^^^^^^^^^^^^^^^^
-
-If you would like to add additional MAAS Rack Controllers to your
-MAAS setup, you can do so by following the instructions in
-:doc:`rack-configuration`.
-
-.. _disc-install:
-
-Installing MAAS from Ubuntu Server boot media
----------------------------------------------
-
-If you are installing MAAS as part of a fresh install it is easiest to
-choose the "Multiple Server install with MAAS" option from the
-installer and have pretty much everything set up for you.  Boot from
-the Ubuntu Server media and you will be greeted with the usual
-language selection screen:
-
-.. image:: media/install_01.*
-
-On the next screen, you will see there is an entry in the menu called
-"Multiple server install with MAAS". Use the cursor keys to select
-this and then press Enter.
-
-.. image:: media/install_02.*
-
-The installer then runs through the usual language and keyboard
-options. Make your selections using Tab/Cursor keys/Enter to proceed
-through the install.  The installer will then load various drivers,
-which may take a moment or two.
-
-.. image:: media/install_03.*
-
-The next screen asks for the hostname for this server. Choose
-something appropriate for your network.
-
-.. image:: media/install_04.*
-
-Finally we get to the MAAS part! Here there are just two options. We
-want to "Create a new MAAS on this server" so go ahead and choose that
-one.
-
-.. image:: media/install_05.*
-
-The install now continues as usual. Next you will be prompted to enter
-a username. This will be the admin user for the actual server that
-MAAS will be running on (not the same as the MAAS admin user!)
-
-.. image:: media/install_06.*
-
-As usual you will have the chance to encrypt your home
-directory. Continue to make selections based on whatever settings suit
-your usage.
-
-.. image:: media/install_07.*
-
-After making selections and partitioning storage, the system software
-will start to be installed. This part should only take a few minutes.
-
-.. image:: media/install_09.*
-
-Various packages will now be configured, including the package manager
-and update manager. It is important to set these up appropriately so
-you will receive timely updates of the MAAS server software, as well
-as other essential services that may run on this server.
-
-.. image:: media/install_10.*
-
-The configuration for MAAS will ask you to configure the host address
-of the server. This should be the IP address you will use to connect
-to the server (you may have additional interfaces e.g. to run node
-subnets)
-
-.. image:: media/install_cluster-config.*
-
-The next screen will confirm the web address that will be used to the
-web interface.
-
-.. image:: media/install_controller-config.*
-
-After configuring any other packages the installer will finally come
-to and end. At this point you should eject the boot media.
-
-.. image:: media/install_14.*
-
-After restarting, you should be able to login to the new server with
-the information you supplied during the install. The MAAS software
-will run automatically.
-
-.. image:: media/install_15.*
-
-**NOTE:** The maas-dhcp and maas-dns packages should be installed by
-default, but on older releases of MAAS they won't be. If you want to
-have MAAS run DHCP and DNS services, you should install these packages.
-Check whether they are installed with::
-
- $ dpkg -l maas-dhcp maas-dns
-
-If they are missing, then::
-
- $ sudo apt-get install maas-dhcp maas-dns
-
-And then proceed to the post-install setup.
-
-.. _container-install:
-
-Installing MAAS in a LXC container
-----------------------------------
-
-Installing MAAS in a container is a typical setup for those users who
-would like to take advantange of their machine for other users at the
-same time of using MAAS.
-
-In order to setup MAAS, you need some requirements:
-
- * Create a bridge (for example, it can be br0).
- * Install LXD and ZFS.
- * Create a Container profile for MAAS
-
-Install LXD and ZFS
-^^^^^^^^^^^^^^^^^^^
-
-The first thing to do is to install LXD and ZFS::
-
- $ sudo apt-get install lxd zfsutils-linux
- $ sudo modprobe zfs
- $ sudo lxd init
-
-Create a LXC profile for MAAS
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-First, create a container profile for MAAS::
-
- $ lxc profile create maas
-
-Second, bind the NIC inside the container (eth0) against the bridge on the
-physical host (br0)::
-
- $ lxc profile device set maas eth0 parent br0
-
-Finally, create a root disk for the container to use::
-
- $ lxc profile device add maas root disk path=/ pool=default
-
-Launch LXD container
-^^^^^^^^^^^^^^^^^^^^
-
-Once the profile has been created, you can now launch the LXC container::
-
-  $ lxc launch -p maas ubuntu-daily:18.04 bionic-maas
-
-Install MAAS
-^^^^^^^^^^^^
-
-Once the container is running, you can now install MAAS. First you need
-to access the container with::
-
-  $ lxc exec bionic-maas bash
-
-And you can proceed with the installation as above, :ref:`From a package repository. <pkg-install>`
-
-.. _post_install:
-
-Post-Install tasks
-==================
-
-Your MAAS is now installed, but there are a few more things to be done.
-If you now use a web browser to connect to the region controller, you
-should see that MAAS is running, but there will also be some errors on
-the screen:
-
-.. image:: media/install_web-init.*
-
-The on screen messages will tell you that there are no boot images
-present, and that you can't login because there is no admin user.
-
-
-Create a superuser account
---------------------------
-
-Once MAAS is installed, you'll need to create an administrator
-account::
-
-  $ sudo maas createadmin --username=root --email=[e-mail]
-
-Substitute your own email address for [e-mail].  You may also
-use a different username for your administrator account, but "root" is a
-common convention and easy to remember.  The command will prompt for a
-password to assign to the new user.
-
-You can run this command again for any further administrator accounts you
-may wish to create, but you need at least one.
-
-
-Log in on the server
---------------------
-
-Looking at the region controller's main web page again, you should now see
-a login screen.  Log in using the user name and password which you have just
-created.
-
-.. image:: media/install-login.*
-
-
-Import the boot images
-----------------------
-
-Since version 1.7, MAAS stores the boot images in the region controller's
-database, from where the rack controllers will synchronise with the region
-and pull images from the region to the rack's local disk.  This process
-is automatic and MAAS will check for and download new Ubuntu images every hour.
-
-However, on a new installation you'll need to start the import process manually
-once you have set up your MAAS region controller.  There are two ways to start
-the import: through the web user interface, or through the remote API.
-
-To do it in the web user interface, go to the Images tab, check the boxes to
-say which images you want to import, and click the "Import images" button at
-the bottom of the Ubuntu section.
-
-.. image:: media/import-images.*
-
-A message will appear to let you know that the import has started, and after a
-while, the warnings about the lack of boot images will disappear.
-
-It may take a long time, depending on the speed of your Internet connection for
-import process to complete, as the images are several hundred megabytes.  The
-import process will only download images that have changed since last import.
-You can check the progress of the import by hovering over the spinner next to
-each image.
-
-The other way to start the import is through the
-:ref:`region-controller API <region-controller-api>`, which you can invoke most
-conveniently through the :ref:`command-line interface <cli>`.
-
-To do this, connect to the MAAS API using the "maas" command-line client.
-See :ref:`Logging in <api-key>` for how to get set up with this tool.  Then,
-run the command::
-
-  $ maas my-maas-session boot-resources import
-
-(Substitute a different profile name for 'my-maas-session' if you have named
-yours something else.)  This will initiate the download, just as if you had
-clicked "Import images" in the web user interface.
-
-By default, the import is configured to download the most recent LTS release
-only for the amd64 architecture.  Although this should suit most needs, you can
-change the selections on the Images tab, or over the API.  Read
-:doc:`customise boot sources </bootsources>` to see examples on how to do that.
-
-
-Speeding up repeated image imports by using a local mirror
-----------------------------------------------------------
-See :doc:`sstreams-mirror` for information on how to set up a mirror and
-configure MAAS to use it.
-
-
-Configure DHCP
---------------
-
-To enable MAAS to control DHCP, you can either:
-
-#. Follow the instructions at :doc:`rack-configuration` to
-   use the web UI to set up your rack controller.
-
-#. Use the command line interface `maas` by first
-   :ref:`logging in to the API <api-key>` and then
-   :ref:`following this procedure <cli-dhcp>`
-
-
-Configure switches on the network
----------------------------------
-
-Some switches use Spanning-Tree Protocol (STP) to negotiate a loop-free path
-through a root bridge.  While scanning, it can make each port wait up to 50
-seconds before data is allowed to be sent on the port.  This delay in turn can
-cause problems with some applications/protocols such as PXE, DHCP and DNS, of
-which MAAS makes extensive use.
-
-To alleviate this problem, you should enable `Portfast`_ for Cisco switches
-or its equivalent on other vendor equipment, which enables the ports to come
-up almost immediately.
-
-.. _Portfast:
-  https://www.symantec.com/business/support/index?page=content&id=HOWTO6019
-
-
-Traffic between the region contoller and rack controllers
-------------------------------------------------------------
-
-* Each rack controller must be able to:
-
-  * Initiate TCP connections (for HTTP) to each region controller on
-    port 80 or port 5240, the choice of which depends on the setting of
-    the MAAS URL.
-
-  * Initiate TCP connections (for RPC) to each region controller between
-    port 5250 and 5259 inclusive. This permits up to 10 ``maas-regiond``
-    processes on each region controller host. At present this is not
-    configurable.
-
-
-Once everything is set up and running, you are ready to :doc:`start
-enlisting nodes <nodes>`
diff --git a/LICENSE b/LICENSE
deleted file mode 100644
index e8ef214..0000000
--- a/LICENSE
+++ /dev/null
@@ -1,676 +0,0 @@
-MAAS is Copyright 2012-2018 Canonical Ltd.
-
-Canonical Ltd ("Canonical") distributes the MAAS source code
-under the GNU Affero General Public License, version 3 ("AGPLv3").
-The full text of this licence is given below.
-
-Third-party copyright in this distribution is noted where applicable.
-
-All rights not expressly granted are reserved.
-
-=========================================================================
-
-                   GNU AFFERO GENERAL PUBLIC LICENSE
-                       Version 3, 19 November 2007
-                 (http://www.gnu.org/licenses/agpl.html)
-
- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                            Preamble
-
-  The GNU Affero General Public License is a free, copyleft license for
-software and other kinds of works, specifically designed to ensure
-cooperation with the community in the case of network server software.
-
-  The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works.  By contrast,
-our General Public Licenses are intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-  Developers that use our General Public Licenses protect your rights
-with two steps: (1) assert copyright on the software, and (2) offer
-you this License which gives you legal permission to copy, distribute
-and/or modify the software.
-
-  A secondary benefit of defending all users' freedom is that
-improvements made in alternate versions of the program, if they
-receive widespread use, become available for other developers to
-incorporate.  Many developers of free software are heartened and
-encouraged by the resulting cooperation.  However, in the case of
-software used on network servers, this result may fail to come about.
-The GNU General Public License permits making a modified version and
-letting the public access it on a server without ever releasing its
-source code to the public.
-
-  The GNU Affero General Public License is designed specifically to
-ensure that, in such cases, the modified source code becomes available
-to the community.  It requires the operator of a network server to
-provide the source code of the modified version running there to the
-users of that server.  Therefore, public use of a modified version, on
-a publicly accessible server, gives the public access to the source
-code of the modified version.
-
-  An older license, called the Affero General Public License and
-published by Affero, was designed to accomplish similar goals.  This is
-a different license, not a version of the Affero GPL, but Affero has
-released a new version of the Affero GPL which permits relicensing under
-this license.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                       TERMS AND CONDITIONS
-
-  0. Definitions.
-
-  "This License" refers to version 3 of the GNU Affero General Public License.
-
-  "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
-
-  To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
-  A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-  To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy.  Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-  To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies.  Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
-  An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License.  If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-  1. Source Code.
-
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
-form of a work.
-
-  A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-  The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form.  A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-  The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities.  However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work.  For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-  The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
-  The Corresponding Source for a work in source code form is that
-same work.
-
-  2. Basic Permissions.
-
-  All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met.  This License explicitly affirms your unlimited
-permission to run the unmodified Program.  The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work.  This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-  You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force.  You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright.  Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-  Conveying under any other circumstances is permitted solely under
-the conditions stated below.  Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-  No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-  When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-  4. Conveying Verbatim Copies.
-
-  You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-  You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-  5. Conveying Modified Source Versions.
-
-  You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-  A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit.  Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-  6. Conveying Non-Source Forms.
-
-  You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-
-  A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source.  The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-  If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information.  But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-  Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-  7. Additional Terms.
-
-  "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law.  If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-  When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it.  (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.)  You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-  Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-
-  All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10.  If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term.  If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-  If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-  Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-  8. Termination.
-
-  You may not propagate or modify a covered work except as expressly
-provided under this License.  Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-  However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-  Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-  Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License.  If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-  9. Acceptance Not Required for Having Copies.
-
-  You are not required to accept this License in order to receive or
-run a copy of the Program.  Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance.  However,
-nothing other than this License grants you permission to propagate or
-modify any covered work.  These actions infringe copyright if you do
-not accept this License.  Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-  10. Automatic Licensing of Downstream Recipients.
-
-  Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License.  You are not responsible
-for enforcing compliance by third parties with this License.
-
-  An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations.  If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-  You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License.  For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-  11. Patents.
-
-  A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based.  The
-work thus licensed is called the contributor's "contributor version".
-
-  A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version.  For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-  Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-  In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement).  To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-  If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients.  "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-  If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-  A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License.  You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-  Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-  12. No Surrender of Others' Freedom.
-
-  If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all.  For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-  13. Remote Network Interaction; Use with the GNU General Public License.
-
-  Notwithstanding any other provision of this License, if you modify the
-Program, your modified version must prominently offer all users
-interacting with it remotely through a computer network (if your version
-supports such interaction) an opportunity to receive the Corresponding
-Source of your version by providing access to the Corresponding Source
-from a network server at no charge, through some standard or customary
-means of facilitating copying of software.  This Corresponding Source
-shall include the Corresponding Source for any work covered by version 3
-of the GNU General Public License that is incorporated pursuant to the
-following paragraph.
-
-  Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU General Public License into a single
-combined work, and to convey the resulting work.  The terms of this
-License will continue to apply to the part which is the covered work,
-but the work with which it is combined will remain governed by version
-3 of the GNU General Public License.
-
-  14. Revised Versions of this License.
-
-  The Free Software Foundation may publish revised and/or new versions of
-the GNU Affero General Public License from time to time.  Such new versions
-will be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-  Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU Affero General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation.  If the Program does not specify a version number of the
-GNU Affero General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
-  If the Program specifies that a proxy can decide which future
-versions of the GNU Affero General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
-  Later license versions may give you additional or different
-permissions.  However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-  15. Disclaimer of Warranty.
-
-  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-  16. Limitation of Liability.
-
-  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
-  17. Interpretation of Sections 15 and 16.
-
-  If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-                     END OF TERMS AND CONDITIONS
-
-            How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU Affero General Public License as published by
-    the Free Software Foundation, either version 3 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU Affero General Public License for more details.
-
-    You should have received a copy of the GNU Affero General Public License
-    along with this program.  If not, see <http://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-  If your software can interact with users remotely through a computer
-network, you should also make sure that it provides a way for users to
-get its source.  For example, if your program is a web application, its
-interface could display a "Source" link that leads users to an archive
-of the code.  There are many ways you could offer source, and different
-solutions will be better for different programs; see section 13 for the
-specific requirements.
-
-  You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU AGPL, see
-<http://www.gnu.org/licenses/>.
-
-=========================================================================
diff --git a/MANIFEST.in b/MANIFEST.in
deleted file mode 100644
index 089f313..0000000
--- a/MANIFEST.in
+++ /dev/null
@@ -1,7 +0,0 @@
-graft src/maasserver/static
-graft src/maasserver/templates
-graft src/metadataserver/fixtures
-graft src/metadataserver/user_data/templates
-graft src/provisioningserver/templates
-include src/provisioningserver/drivers/power/*.xml
-include src/metadataserver/builtin_scripts/*.sh
diff --git a/Makefile b/Makefile
deleted file mode 100644
index 17d7507..0000000
--- a/Makefile
+++ /dev/null
@@ -1,846 +0,0 @@
-python := python3
-snapcraft := snapcraft
-
-# pkg_resources makes some incredible noise about version numbers. They
-# are not indications of bugs in MAAS so we silence them everywhere.
-export PYTHONWARNINGS = \
-  ignore:You have iterated over the result:RuntimeWarning:pkg_resources:
-
-# Network activity can be suppressed by setting offline=true (or any
-# non-empty string) at the command-line.
-ifeq ($(offline),)
-buildout := bin/buildout
-else
-buildout := bin/buildout buildout:offline=true
-endif
-
-# If offline has been selected, attempt to further block HTTP/HTTPS
-# activity by setting bogus proxies in the environment.
-ifneq ($(offline),)
-export http_proxy := broken
-export https_proxy := broken
-endif
-
-# MAAS SASS stylesheets. The first input file (maas-styles.css) imports
-# the others, so is treated specially in the target definitions.
-scss_input := src/maasserver/static/scss/build.scss
-scss_deps := $(wildcard src/maasserver/static/scss/_*.scss)
-scss_output := src/maasserver/static/css/build.css
-
-javascript_deps := \
-  $(shell find src -name '*.js' -not -path '*/maasserver/static/js/bundle/*') \
-  package.json \
-  webpack.config.js \
-  yarn.lock
-
-javascript_output := \
-  src/maasserver/static/js/bundle/maas-min.js \
-  src/maasserver/static/js/bundle/maas-min.js.map \
-  src/maasserver/static/js/bundle/vendor-min.js \
-  src/maasserver/static/js/bundle/vendor-min.js.map
-
-# Prefix commands with this when they need access to the database.
-# Remember to add a dependency on bin/database from the targets in
-# which those commands appear.
-dbrun := bin/database --preserve run --
-
-# Path to install local nodejs.
-mkfile_dir := $(shell dirname $(realpath $(lastword $(MAKEFILE_LIST))))
-nodejs_path := $(mkfile_dir)/include/nodejs/bin
-
-export PATH := $(nodejs_path):$(PATH)
-
-# For things that care, postgresfixture for example, we always want to
-# use the "maas" databases.
-export PGDATABASE := maas
-
-# For anything we start, we want to hint as to its root directory.
-export MAAS_ROOT := $(CURDIR)/.run
-
-build: \
-  bin/buildout \
-  bin/database \
-  bin/maas \
-  bin/maas-common \
-  bin/maas-rack \
-  bin/maas-region \
-  bin/rackd \
-  bin/regiond \
-  bin/test.cli \
-  bin/test.rack \
-  bin/test.region \
-  bin/test.region.legacy \
-  bin/test.testing \
-  bin/test.js \
-  bin/test.e2e \
-  bin/test.parallel \
-  bin/py bin/ipy \
-  pycharm
-
-all: build doc
-
-# Install all packages required for MAAS development & operation on
-# the system. This may prompt for a password.
-install-dependencies: release := $(shell lsb_release -c -s)
-install-dependencies:
-	sudo DEBIAN_FRONTEND=noninteractive apt-get -y \
-	    --no-install-recommends install $(shell sort -u \
-	        $(addprefix required-packages/,base build dev doc) | sed '/^\#/d')
-	sudo DEBIAN_FRONTEND=noninteractive apt-get -y \
-	    purge $(shell sort -u required-packages/forbidden | sed '/^\#/d')
-	if [ -x /usr/bin/snap ]; then sudo snap install --classic snapcraft; fi
-
-.gitignore:
-	sed 's:^[.]/:/:' $^ > $@
-
-configure-buildout:
-	utilities/configure-buildout
-
-sudoers:
-	utilities/install-sudoers
-	utilities/grant-nmap-permissions
-
-bin/buildout: bootstrap-buildout.py
-	@utilities/configure-buildout --quiet
-	$(python) bootstrap-buildout.py --allow-site-packages
-	@touch --no-create $@  # Ensure it's newer than its dependencies.
-
-# buildout.cfg refers to .run and .run-e2e.
-buildout.cfg: .run .run-e2e
-
-bin/database: bin/buildout buildout.cfg versions.cfg setup.py
-	$(buildout) install database
-	@touch --no-create $@
-
-bin/test.parallel: \
-  bin/buildout buildout.cfg versions.cfg setup.py
-	$(buildout) install parallel-test
-	@touch --no-create $@
-
-bin/maas-region bin/regiond: \
-    bin/buildout buildout.cfg versions.cfg setup.py \
-    $(scss_output) $(javascript_output)
-	$(buildout) install region
-	@touch --no-create $@
-
-bin/test.region: \
-  bin/buildout buildout.cfg versions.cfg setup.py \
-  bin/maas-region bin/maas-rack bin/maas-common
-	$(buildout) install region-test
-	@touch --no-create $@
-
-bin/test.region.legacy: \
-    bin/buildout buildout.cfg versions.cfg setup.py
-	$(buildout) install region-test-legacy
-	@touch --no-create $@
-
-bin/maas: bin/buildout buildout.cfg versions.cfg setup.py
-	$(buildout) install cli
-	@touch --no-create $@
-
-bin/test.cli: bin/buildout buildout.cfg versions.cfg setup.py bin/maas
-	$(buildout) install cli-test
-	@touch --no-create $@
-
-bin/test.js: bin/karma bin/buildout buildout.cfg versions.cfg setup.py
-	$(buildout) install js-test
-	@touch --no-create $@
-
-bin/test.e2e: \
-    bin/protractor bin/buildout buildout.cfg versions.cfg setup.py
-	$(buildout) install e2e-test
-	@touch --no-create $@
-
-# bin/flake8 is needed for checking lint and bin/node-sass is needed for
-# checking css.
-bin/test.testing: \
-  bin/flake8 bin/node-sass bin/buildout \
-  buildout.cfg versions.cfg setup.py
-	$(buildout) install testing-test
-	@touch --no-create $@
-
-bin/maas-rack bin/rackd bin/maas-common: \
-  bin/buildout buildout.cfg versions.cfg setup.py
-	$(buildout) install rack
-	@touch --no-create $@
-
-bin/test.rack: \
-  bin/buildout buildout.cfg versions.cfg setup.py bin/maas-rack bin/py
-	$(buildout) install rack-test
-	@touch --no-create $@
-
-bin/flake8: bin/buildout buildout.cfg versions.cfg setup.py
-	$(buildout) install flake8
-	@touch --no-create $@
-
-bin/sphinx bin/sphinx-build: bin/buildout buildout.cfg versions.cfg setup.py
-	$(buildout) install sphinx
-	@touch --no-create $@
-
-bin/py bin/ipy: bin/buildout buildout.cfg versions.cfg setup.py
-	$(buildout) install repl
-	@touch --no-create bin/py bin/ipy
-
-bin/coverage: bin/buildout buildout.cfg versions.cfg setup.py
-	$(buildout) install coverage
-	@touch --no-create bin/coverage
-
-include/nodejs/bin/node:
-	mkdir -p include/nodejs
-	wget -O include/nodejs/nodejs.tar.gz https://nodejs.org/dist/v8.10.0/node-v8.10.0-linux-x64.tar.gz
-	tar -C include/nodejs/ -xf include/nodejs/nodejs.tar.gz --strip-components=1
-
-include/nodejs/yarn.tar.gz:
-	mkdir -p include/nodejs
-	wget -O include/nodejs/yarn.tar.gz https://yarnpkg.com/latest.tar.gz
-
-include/nodejs/bin/yarn: include/nodejs/yarn.tar.gz
-	tar -C include/nodejs/ -xf include/nodejs/yarn.tar.gz --strip-components=1
-	@touch --no-create $@
-
-bin/yarn: include/nodejs/bin/yarn
-	@mkdir -p bin
-	ln -sf ../include/nodejs/bin/yarn $@
-	@touch --no-create $@
-
-node_modules: include/nodejs/bin/node bin/yarn
-	bin/yarn --frozen-lockfile
-	@touch --no-create $@
-
-define js_bins
-  bin/karma
-  bin/protractor
-  bin/node-sass
-  bin/webpack
-endef
-
-$(strip $(js_bins)): node_modules
-	ln -sf ../node_modules/.bin/$(notdir $@) $@
-	@touch --no-create $@
-
-define node_packages
-  @babel/core
-  @babel/preset-react
-  @babel/preset-es2015
-  @types/prop-types
-  @types/react
-  @types/react-dom
-  babel-polyfill
-  babel-loader@^8.0.0-beta.0
-  glob
-  jasmine-core@=2.99.1
-  karma
-  karma-chrome-launcher
-  karma-failed-reporter
-  karma-firefox-launcher
-  karma-jasmine
-  karma-ng-html2js-preprocessor
-  karma-opera-launcher
-  karma-phantomjs-launcher
-  karma-sourcemap-loader
-  macaroon-bakery
-  node-sass
-  phantomjs-prebuilt
-  prop-types
-  protractor
-  react
-  react-dom
-  react2angular
-  uglifyjs-webpack-plugin
-  vanilla-framework
-  vanilla-framework-react
-  webpack
-  webpack-cli
-  webpack-merge
-endef
-
-force-yarn-update: bin/yarn
-	$(RM) package.json yarn.lock
-	bin/yarn add -D $(strip $(node_packages))
-
-define test-scripts
-  bin/test.cli
-  bin/test.rack
-  bin/test.region
-  bin/test.region.legacy
-  bin/test.testing
-  bin/test.js
-endef
-
-lxd:
-	utilities/configure-lxd-profile
-	utilities/create-lxd-bionic-image
-
-test: bin/test.parallel bin/coverage
-	@$(RM) .coverage .coverage.*
-	@bin/test.parallel --with-coverage --subprocess-per-core
-	@bin/coverage combine
-
-test-js: bin/test.js javascript
-	@bin/test.js
-
-test-serial: $(strip $(test-scripts))
-	@bin/maas-region makemigrations --dry-run --exit && exit 1 ||:
-	@$(RM) .coverage .coverage.* .failed
-	$(foreach test,$^,$(test-template);)
-	@test ! -f .failed
-
-test-failed: $(strip $(test-scripts))
-	@bin/maas-region makemigrations --dry-run --exit && exit 1 ||:
-	@$(RM) .coverage .coverage.* .failed
-	$(foreach test,$^,$(test-template-failed);)
-	@test ! -f .failed
-
-clean-failed:
-	$(RM) .noseids
-
-src/maasserver/testing/initial.maas_test.sql: bin/maas-region bin/database
-  # Run migrations without any triggers created.
-	$(dbrun) bin/maas-region dbupgrade --internal-no-triggers
-	# Data migration will create a notification, that will break tests. Want the
-	# database to be a clean schema.
-	$(dbrun) bin/maas-region shell -c "from maasserver.models.notification import Notification; Notification.objects.all().delete()"
-	bin/database --preserve run -- \
-	    pg_dump maas --no-owner --no-privileges \
-	        --format=plain > $@
-
-test-initial-data: src/maasserver/testing/initial.maas_test.sql
-
-define test-template
-$(test) --with-xunit --xunit-file=xunit.$(notdir $(test)).xml || touch .failed
-endef
-
-define test-template-failed
-  $(test) --with-xunit --xunit-file=xunit.$(notdir $(test)).xml --failed || \
-  $(test) --with-xunit --xunit-file=xunit.$(notdir $(test)).xml --failed || \
-  touch .failed
-endef
-
-smoke: lint bin/maas-region bin/test.rack
-	@bin/maas-region makemigrations --dry-run --exit && exit 1 ||:
-	@bin/test.rack --stop
-
-test-serial+coverage: export NOSE_WITH_COVERAGE = 1
-test-serial+coverage: test-serial
-
-coverage-report: coverage/index.html
-	sensible-browser $< > /dev/null 2>&1 &
-
-coverage.xml: bin/coverage .coverage
-	bin/coverage xml -o $@
-
-coverage/index.html: revno = $(or $(shell git rev-parse HEAD 2>/dev/null),???)
-coverage/index.html: bin/coverage .coverage
-	@$(RM) -r $(@D)
-	bin/coverage html \
-	    --title "Coverage for MAAS rev $(revno)" \
-	    --directory $(@D)
-
-.coverage:
-	@$(error Use `$(MAKE) test` to generate coverage)
-
-lint: \
-    lint-py lint-py-complexity lint-py-imports \
-    lint-js lint-doc lint-rst
-        # Only Unix line ends should be accepted
-	@find src/ -type f -exec file "{}" ";" | \
-	    awk '/CRLF/ { print $0; count++ } END {exit count}' || \
-	    (echo "Lint check failed; run make format to fix DOS linefeeds."; false)
-
-pocketlint = $(call available,pocketlint,python-pocket-lint)
-
-# XXX jtv 2014-02-25: Clean up this lint, then make it part of "make lint".
-lint-css: sources = src/maasserver/static/css
-lint-css:
-	@find $(sources) -type f \
-	    -print0 | xargs -r0 $(pocketlint) --max-length=120
-
-# Python lint checks are time-intensive, but flake8 now knows how to run
-# parallel jobs, and does so by default.
-lint-py: sources = setup.py src
-lint-py: bin/flake8
-	@find $(sources) -name '*.py' \
-	  ! -path '*/migrations/*' -print0 | xargs -r0 bin/flake8 --config=.flake8
-
-# Ignore tests when checking complexity. The maximum complexity ought to
-# be close to 10 but MAAS has many functions that are over that so we
-# start with a much higher number. Over time we can ratchet it down.
-lint-py-complexity: maximum=26
-lint-py-complexity: sources = setup.py src
-lint-py-complexity: bin/flake8
-	@find $(sources) -name '*.py' \
-	  ! -path '*/migrations/*' \
-	  ! -path '*/tests/*' ! -path '*/testing/*' ! -name 'testing.py' \
-	  -print0 | xargs -r0 bin/flake8 --config=.flake8 --max-complexity=$(maximum)
-
-# Statically check imports against policy.
-lint-py-imports: sources = setup.py src
-lint-py-imports:
-	@utilities/check-imports
-	@find $(sources) -name '*.py' \
-	  ! -path '*/migrations/*' \
-	  -print0 | xargs -r0 utilities/find-early-imports
-
-lint-doc:
-	@utilities/doc-lint
-
-# JavaScript lint is checked in parallel for speed.  The -n20 -P4 setting
-# worked well on a multicore SSD machine with the files cached, roughly
-# doubling the speed, but it may need tuning for slower systems or cold caches.
-lint-js: sources = src/maasserver/static/js
-lint-js:
-	@find $(sources) -type f -not -path '*/angular/3rdparty/*' -a \
-		-not -path '*-min.js' -a \
-	    '(' -name '*.html' -o -name '*.js' ')' -print0 \
-		| xargs -r0 -n20 -P4 $(pocketlint)
-		bin/yarn prettier-check
-
-# Apply automated formatting to all Python, Sass and Javascript files.
-format: sources = $(wildcard *.py contrib/*.py) src utilities etc
-format: bin/yarn
-	@find $(sources) -name '*.py' -print0 | xargs -r0 utilities/format-imports
-	@find src/ -type f -exec file "{}" ";" | grep CRLF | cut -d ':' -f1 | xargs dos2unix
-	bin/yarn prettier
-
-check: clean test
-
-docs/api.rst: bin/maas-region src/maasserver/api/doc_handler.py syncdb
-	bin/maas-region generate_api_doc > $@
-
-sampledata: bin/maas-region bin/database syncdb
-	$(dbrun) bin/maas-region generate_sample_data
-
-doc: bin/sphinx docs/api.rst
-	bin/sphinx
-
-docs/_build/html/index.html: doc
-
-doc-browse: docs/_build/html/index.html
-	sensible-browser $< > /dev/null 2>&1 &
-
-doc-with-versions: bin/sphinx docs/api.rst
-	$(MAKE) -C docs/_build SPHINXOPTS="-A add_version_switcher=true" html
-
-man: $(patsubst docs/man/%.rst,man/%,$(wildcard docs/man/*.rst))
-
-man/%: docs/man/%.rst | bin/sphinx-build
-	bin/sphinx-build -b man docs man $^
-
-.run .run-e2e: run-skel
-	@cp --archive --verbose $^ $@
-
-.idea: contrib/pycharm
-	@cp --archive --verbose $^ $@
-
-pycharm: .idea
-
-styles: $(scss_output)
-
-force-styles: clean-styles $(scss_output)
-
-$(scss_output): bin/node-sass $(scss_input) $(scss_deps)
-	bin/node-sass --include-path=src/maasserver/static/scss \
-	    --output-style compressed $(scss_input) -o $(dir $@)
-
-clean-styles:
-	$(RM) $(scss_output)
-
-javascript: node_modules $(javascript_output)
-
-force-javascript: clean-javascript node_modules $(javascript_output)
-
-lander-javascript: force-javascript
-	git update-index -q --no-assume-unchanged $(strip $(javascript_output)) 2> /dev/null || true
-	git add -f $(strip $(javascript_output)) 2> /dev/null || true
-
-lander-styles: force-styles node_modules $(scss_output)
-	git update-index -q --no-assume-unchanged $(strip $(scss_output)) 2> /dev/null || true
-	git add -f $(strip $(scss_output)) 2> /dev/null || true
-
-# The $(subst ...) uses a pattern rule to ensure Webpack runs just once,
-# even if all four output files are out-of-date.
-$(subst .,%,$(javascript_output)): $(javascript_deps)
-	bin/yarn build
-	@touch --no-create $(strip $(javascript_output))
-	@git update-index -q --assume-unchanged $(strip $(javascript_output)) 2> /dev/null || true
-
-clean-javascript:
-	$(RM) -r src/maasserver/static/js/bundle
-
-watch-javascript:
-	bin/yarn watch
-
-clean: stop clean-failed
-	find . -type f -name '*.py[co]' -print0 | xargs -r0 $(RM)
-	find . -type d -name '__pycache__' -print0 | xargs -r0 $(RM) -r
-	find . -type f -name '*~' -print0 | xargs -r0 $(RM)
-	$(RM) -r media/demo/* media/development media/development.*
-	$(RM) src/maasserver/data/templates.py
-	$(RM) *.log
-	$(RM) docs/api.rst
-	$(RM) -r docs/_autosummary docs/_build
-	$(RM) -r man/.doctrees
-	$(RM) .coverage .coverage.* coverage.xml
-	$(RM) -r coverage
-	$(RM) -r .hypothesis
-	$(RM) -r bin include lib local node_modules
-	$(RM) -r eggs develop-eggs
-	$(RM) -r build dist logs/* parts
-	$(RM) tags TAGS .installed.cfg
-	$(RM) -r *.egg *.egg-info src/*.egg-info
-	$(RM) -r services/*/supervise
-	$(RM) -r .run .run-e2e
-	$(RM) -r .idea
-	$(RM) xunit.*.xml
-	$(RM) .failed
-
-clean+db: clean
-	while fuser db --kill -TERM; do sleep 1; done
-	$(RM) -r db
-	$(RM) .db.lock
-
-distclean: clean
-	$(warning 'distclean' is deprecated; use 'clean')
-
-harness: bin/maas-region bin/database
-	$(dbrun) bin/maas-region shell \
-	  --settings=maasserver.djangosettings.demo
-
-dbharness: bin/database
-	bin/database --preserve shell
-
-syncdb: bin/maas-region bin/database
-	$(dbrun) bin/maas-region dbupgrade
-
-define phony_targets
-  build
-  check
-  clean
-  clean+db
-  clean-failed
-  clean-javascript
-  clean-styles
-  configure-buildout
-  coverage-report
-  dbharness
-  distclean
-  doc
-  doc-browse
-  force-styles
-  force-javascript
-  force-yarn-update
-  format
-  harness
-  install-dependencies
-  javascript
-  lander-javascript
-  lander-styles
-  lint
-  lint-css
-  lint-doc
-  lint-js
-  lint-py
-  lint-py-complexity
-  lint-py-imports
-  lint-rst
-  lxd
-  man
-  print-%
-  sampledata
-  smoke
-  styles
-  sudoers
-  syncdb
-  sync-dev-snap
-  test
-  test+lxd
-  test-failed
-  test-initial-data
-  test-serial
-  test-serial+coverage
-endef
-
-#
-# Development services.
-#
-
-service_names_region := database dns regiond reloader
-service_names_rack := http rackd reloader
-service_names_all := $(service_names_region) $(service_names_rack)
-
-# The following template is intended to be used with `call`, and it
-# accepts a single argument: a target name. The target name must
-# correspond to a service action (see "Pseudo-magic targets" below). A
-# region- and rack-specific variant of the target will be created, in
-# addition to the target itself. These can be used to apply the service
-# action to the region services, the rack services, or all services, at
-# the same time.
-define service_template
-$(1)-region: $(patsubst %,services/%/@$(1),$(service_names_region))
-$(1)-rack: $(patsubst %,services/%/@$(1),$(service_names_rack))
-$(1): $(1)-region $(1)-rack
-phony_services_targets += $(1)-region $(1)-rack $(1)
-endef
-
-# Expand out aggregate service targets using `service_template`.
-$(eval $(call service_template,pause))
-$(eval $(call service_template,restart))
-$(eval $(call service_template,start))
-$(eval $(call service_template,status))
-$(eval $(call service_template,stop))
-$(eval $(call service_template,supervise))
-
-# The `run` targets do not fit into the mould of the others.
-run-region:
-	@services/run $(service_names_region)
-run-rack:
-	@services/run $(service_names_rack)
-run:
-	@services/run $(service_names_all)
-
-phony_services_targets += run-region run-rack run
-
-phony_services_targets += run+regiond
-
-# Convenient variables and functions for service control.
-
-setlock = $(call available,setlock,daemontools)
-supervise = $(call available,supervise,daemontools)
-svc = $(call available,svc,daemontools)
-svok = $(call available,svok,daemontools)
-svstat = $(call available,svstat,daemontools)
-
-service_lock = $(setlock) -n /run/lock/maas.dev.$(firstword $(1))
-
-# Pseudo-magic targets for controlling individual services.
-
-services/%/@run: services/%/@stop services/%/@deps
-	@$(call service_lock, $*) services/$*/run
-
-services/%/@start: services/%/@supervise
-	@$(svc) -u $(@D)
-
-services/%/@pause: services/%/@supervise
-	@$(svc) -d $(@D)
-
-services/%/@status:
-	@$(svstat) $(@D)
-
-services/%/@restart: services/%/@supervise
-	@$(svc) -du $(@D)
-
-services/%/@stop:
-	@if $(svok) $(@D); then $(svc) -dx $(@D); fi
-	@while $(svok) $(@D); do sleep 0.1; done
-
-services/%/@supervise: services/%/@deps
-	@mkdir -p logs/$*
-	@touch $(@D)/down
-	@if ! $(svok) $(@D); then \
-	    logdir=$(CURDIR)/logs/$* \
-	        $(call service_lock, $*) $(supervise) $(@D) & fi
-	@while ! $(svok) $(@D); do sleep 0.1; done
-
-# Dependencies for individual services.
-
-services/dns/@deps: bin/py bin/maas-common
-
-services/database/@deps: bin/database
-
-services/http/@deps: bin/py
-
-services/rackd/@deps: bin/rackd bin/maas-rack bin/maas-common
-
-services/reloader/@deps:
-
-services/regiond/@deps: bin/maas-region bin/maas-rack bin/maas-common
-
-#
-# Package building
-#
-
-# This ought to be as simple as using
-#   gbp buildpackage --git-debian-branch=packaging
-# but it is not: without investing more time, we manually pre-build the source
-# tree and run debuild.
-
-packaging-repo = https://git.launchpad.net/maas/
-packaging-branch = "packaging"
-
-packaging-build-area := $(abspath ../build-area)
-packaging-version = $(shell \
-    utilities/calc-snap-version | sed s/[-]snap//)
-tmp_changelog := $(shell tempfile)
-packaging-dir := maas_$(packaging-version)
-packaging-orig-targz := $(packaging-dir).orig.tar.gz
-
--packaging-clean:
-	rm -rf $(packaging-build-area)
-	mkdir -p $(packaging-build-area)
-
--packaging-export-orig: $(packaging-build-area)
-	git archive --format=tar.gz $(packaging-export-extra) \
-            --prefix=$(packaging-dir)/ \
-	    -o $(packaging-build-area)/$(packaging-orig-targz) HEAD
-
--packaging-export-orig-uncommitted: $(packaging-build-area)
-	git ls-files --others --exclude-standard --cached | grep -v '^debian' | \
-	    xargs tar --transform 's,^,$(packaging-dir)/,' -czf $(packaging-build-area)/$(packaging-orig-targz)
-
--packaging-export: -packaging-export-orig$(if $(export-uncommitted),-uncommitted,)
-
--package-tree: -packaging-export
-	(cd $(packaging-build-area) && tar xfz $(packaging-orig-targz))
-	(cp -r debian $(packaging-build-area)/$(packaging-dir))
-	echo "maas ($(packaging-version)-0ubuntu1) UNRELEASED; urgency=medium" \
-	    > $(tmp_changelog)
-	tail -n +2 debian/changelog >> $(tmp_changelog)
-	mv $(tmp_changelog) $(packaging-build-area)/$(packaging-dir)/debian/changelog
-
-package: javascript -packaging-clean -package-tree
-	(cd $(packaging-build-area)/$(packaging-dir) && debuild -uc -us)
-	@echo Binary packages built, see $(packaging-build-area).
-
-# To build binary packages from uncommitted changes call "make package-dev".
-package-dev:
-	make export-uncommitted=yes package
-
-source-package: -package-tree
-	(cd $(packaging-build-area)/$(packaging-dir) && debuild -S -uc -us)
-	@echo Source package built, see $(packaging-build-area).
-
-# To build source packages from uncommitted changes call "make package-dev".
-source-package-dev:
-	make export-uncommitted=yes source-package
-
-# To rebuild packages (i.e. from a clean slate):
-package-rebuild: package-clean package
-
-package-dev-rebuild: package-clean package-dev
-
-source-package-rebuild: source-package-clean source-package
-
-source-package-dev-rebuild: source-package-clean source-package-dev
-
-# To clean built packages away:
-package-clean: patterns := *.deb *.udeb *.dsc *.build *.changes
-package-clean: patterns += *.debian.tar.xz *.orig.tar.gz
-package-clean:
-	@$(RM) -v $(addprefix $(packaging-build-area)/,$(patterns))
-
-source-package-clean: patterns := *.dsc *.build *.changes
-source-package-clean: patterns += *.debian.tar.xz *.orig.tar.gz
-source-package-clean:
-	@$(RM) -v $(addprefix $(packaging-build-area)/,$(patterns))
-
-
-# Debugging target. Allows printing of any variable.
-# As an example, try:
-#     make print-scss_input
-print-%:
-	@echo $* = $($*)
-
-define phony_package_targets
-  -packaging-export-orig
-  -packaging-export-orig-uncommitted
-  -packaging-export
-  -packaging-fetch
-  -packaging-pull
-  -packaging-refresh
-  -package-tree
-  package
-  package-clean
-  package-dev
-  package-dev-rebuild
-  package-rebuild
-  source-package
-  source-package-clean
-  source-package-dev
-  source-package-dev-rebuild
-  source-package-rebuild
-endef
-
-#
-# Snap building
-#
-
-snap-clean:
-	$(snapcraft) clean
-
-snap:
-	$(snapcraft)
-
-define phony_snap_targets
-	snap
-	snap-clean
-endef
-
-
-#
-# Helpers for using the snap for development testing.
-#
-
-
-build/dev-snap: ## Check out a clean version of the working tree.
-	git checkout-index -a --prefix build/dev-snap/
-
-build/dev-snap/prime: build/dev-snap
-	cd build/dev-snap && $(snapcraft) prime --destructive-mode
-
-sync-dev-snap: build/dev-snap/prime
-	rsync -v --exclude 'maastesting' --exclude 'tests' --exclude 'testing' \
-		--exclude '*.pyc' --exclude '__pycache__' -r -u -l -t -W -L \
-		src/ build/dev-snap/prime/lib/python3.6/site-packages/
-	rsync -v -r -u -l -t -W -L \
-		src/maasserver/static/ build/dev-snap/prime/usr/share/maas/web/static/
-
-#
-# Phony stuff.
-#
-
-define phony
-  $(phony_package_targets)
-  $(phony_services_targets)
-  $(phony_snap_targets)
-  $(phony_targets)
-endef
-
-phony := $(sort $(strip $(phony)))
-
-.PHONY: $(phony) FORCE
-
-#
-# Secondary stuff.
-#
-# These are intermediate files that we want to keep around in the event
-# that they get built. By declaring them here we're also telling Make
-# that their absense is okay if a rule target is newer than the rule's
-# other prerequisites; i.e. don't build them.
-#
-# For example, converting foo.scss to foo.css might require bin/node-sass. If
-# foo.css is newer than foo.scss we know that we don't need to perform that
-# conversion, and hence don't need bin/node-sass. We declare bin/node-sass as
-# secondary so that Make knows this too.
-#
-
-define secondary_binaries
-  bin/py bin/buildout
-  bin/node-sass
-  bin/sphinx bin/sphinx-build
-endef
-
-secondary = $(sort $(strip $(secondary_binaries)))
-
-.SECONDARY: $(secondary)
-
-#
-# Functions.
-#
-
-# Check if a command is found on PATH. Raise an error if not, citing
-# the package to install. Return the command otherwise.
-# Usage: $(call available,<command>,<package>)
-define available
-  $(if $(shell which $(1)),$(1),$(error $(1) not found; \
-    install it with 'sudo apt-get install $(2)'))
-endef
diff --git a/README.rst b/README.rst
deleted file mode 100644
index df14155..0000000
--- a/README.rst
+++ /dev/null
@@ -1,30 +0,0 @@
-************************
-MAAS: Metal as a Service
-************************
-
-Metal as a Service -- MAAS -- lets you treat physical servers like
-virtual machines in the cloud. Rather than having to manage each
-server individually, MAAS turns your bare metal into an elastic
-cloud-like resource.
-
-What does that mean in practice? Tell MAAS about the machines you want
-it to manage and it will boot them, check the hardware's okay, and
-have them waiting for when you need them. You can then pull nodes up,
-tear them down and redeploy them at will; just as you can with virtual
-machines in the cloud.
-
-When you're ready to deploy a service, MAAS gives Juju the nodes it
-needs to power that service. It's as simple as that: no need to
-manually provision, check and, afterwards, clean-up. As your needs
-change, you can easily scale services up or down. Need more power for
-your Hadoop cluster for a few hours? Simply tear down one of your Nova
-compute nodes and redeploy it to Hadoop. When you're done, it's just
-as easy to give the node back to Nova.
-
-MAAS is ideal where you want the flexibility of the cloud, and the
-hassle-free power of Juju charms, but you need to deploy to bare
-metal.
-
-For more information see the `MAAS guide`_.
-
-.. _MAAS guide: http://maas.io/
diff --git a/bootstrap-buildout.py b/bootstrap-buildout.py
deleted file mode 100644
index 69bf941..0000000
--- a/bootstrap-buildout.py
+++ /dev/null
@@ -1,210 +0,0 @@
-##############################################################################
-#
-# Copyright (c) 2006 Zope Foundation and Contributors.
-# All Rights Reserved.
-#
-# This software is subject to the provisions of the Zope Public License,
-# Version 2.1 (ZPL).  A copy of the ZPL should accompany this distribution.
-# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED
-# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
-# FOR A PARTICULAR PURPOSE.
-#
-##############################################################################
-"""Bootstrap a buildout-based project
-
-Simply run this script in a directory containing a buildout.cfg.
-The script accepts buildout command-line options, so you can
-use the -c option to specify an alternate configuration file.
-"""
-
-from optparse import OptionParser
-import os
-import shutil
-import sys
-import tempfile
-
-
-__version__ = '2015-07-01'
-# See zc.buildout's changelog if this version is up to date.
-
-tmpeggs = tempfile.mkdtemp(prefix='bootstrap-')
-
-usage = '''\
-[DESIRED PYTHON FOR BUILDOUT] bootstrap.py [options]
-
-Bootstraps a buildout-based project.
-
-Simply run this script in a directory containing a buildout.cfg, using the
-Python that you want bin/buildout to use.
-
-Note that by using --find-links to point to local resources, you can keep
-this script from going over the network.
-'''
-
-parser = OptionParser(usage=usage)
-parser.add_option("--version",
-                  action="store_true", default=False,
-                  help=("Return bootstrap.py version."))
-parser.add_option("-t", "--accept-buildout-test-releases",
-                  dest='accept_buildout_test_releases',
-                  action="store_true", default=False,
-                  help=("Normally, if you do not specify a --version, the "
-                        "bootstrap script and buildout gets the newest "
-                        "*final* versions of zc.buildout and its recipes and "
-                        "extensions for you.  If you use this flag, "
-                        "bootstrap and buildout will get the newest releases "
-                        "even if they are alphas or betas."))
-parser.add_option("-c", "--config-file",
-                  help=("Specify the path to the buildout configuration "
-                        "file to be used."))
-parser.add_option("-f", "--find-links",
-                  help=("Specify a URL to search for buildout releases"))
-parser.add_option("--allow-site-packages",
-                  action="store_true", default=False,
-                  help=("Let bootstrap.py use existing site packages"))
-parser.add_option("--buildout-version",
-                  help="Use a specific zc.buildout version")
-parser.add_option("--setuptools-version",
-                  help="Use a specific setuptools version")
-parser.add_option("--setuptools-to-dir",
-                  help=("Allow for re-use of existing directory of "
-                        "setuptools versions"))
-
-options, args = parser.parse_args()
-if options.version:
-    print("bootstrap.py version %s" % __version__)
-    sys.exit(0)
-
-
-######################################################################
-# load/install setuptools
-
-try:
-    from urllib.request import urlopen
-except ImportError:
-    from urllib2 import urlopen
-
-ez = {}
-if os.path.exists('ez_setup.py'):
-    exec(open('ez_setup.py').read(), ez)
-else:
-    exec(urlopen('https://bootstrap.pypa.io/ez_setup.py').read(), ez)
-
-if not options.allow_site_packages:
-    # ez_setup imports site, which adds site packages
-    # this will remove them from the path to ensure that incompatible versions
-    # of setuptools are not in the path
-    import site
-    # inside a virtualenv, there is no 'getsitepackages'.
-    # We can't remove these reliably
-    if hasattr(site, 'getsitepackages'):
-        for sitepackage_path in site.getsitepackages():
-            # Strip all site-packages directories from sys.path that
-            # are not sys.prefix; this is because on Windows
-            # sys.prefix is a site-package directory.
-            if sitepackage_path != sys.prefix:
-                sys.path[:] = [x for x in sys.path
-                               if sitepackage_path not in x]
-
-setup_args = dict(to_dir=tmpeggs, download_delay=0)
-
-if options.setuptools_version is not None:
-    setup_args['version'] = options.setuptools_version
-if options.setuptools_to_dir is not None:
-    setup_args['to_dir'] = options.setuptools_to_dir
-
-ez['use_setuptools'](**setup_args)
-import setuptools
-import pkg_resources
-
-# This does not (always?) update the default working set.  We will
-# do it.
-for path in sys.path:
-    if path not in pkg_resources.working_set.entries:
-        pkg_resources.working_set.add_entry(path)
-
-######################################################################
-# Install buildout
-
-ws = pkg_resources.working_set
-
-setuptools_path = ws.find(
-    pkg_resources.Requirement.parse('setuptools')).location
-
-# Fix sys.path here as easy_install.pth added before PYTHONPATH
-cmd = [sys.executable, '-c',
-       'import sys; sys.path[0:0] = [%r]; ' % setuptools_path +
-       'from setuptools.command.easy_install import main; main()',
-       '-mZqNxd', tmpeggs]
-
-find_links = os.environ.get(
-    'bootstrap-testing-find-links',
-    options.find_links or
-    ('http://downloads.buildout.org/'
-     if options.accept_buildout_test_releases else None)
-    )
-if find_links:
-    cmd.extend(['-f', find_links])
-
-requirement = 'zc.buildout'
-version = options.buildout_version
-if version is None and not options.accept_buildout_test_releases:
-    # Figure out the most recent final version of zc.buildout.
-    import setuptools.package_index
-    _final_parts = '*final-', '*final'
-
-    def _final_version(parsed_version):
-        try:
-            return not parsed_version.is_prerelease
-        except AttributeError:
-            # Older setuptools
-            for part in parsed_version:
-                if (part[:1] == '*') and (part not in _final_parts):
-                    return False
-            return True
-
-    index = setuptools.package_index.PackageIndex(
-        search_path=[setuptools_path])
-    if find_links:
-        index.add_find_links((find_links,))
-    req = pkg_resources.Requirement.parse(requirement)
-    if index.obtain(req) is not None:
-        best = []
-        bestv = None
-        for dist in index[req.project_name]:
-            distv = dist.parsed_version
-            if _final_version(distv):
-                if bestv is None or distv > bestv:
-                    best = [dist]
-                    bestv = distv
-                elif distv == bestv:
-                    best.append(dist)
-        if best:
-            best.sort()
-            version = best[-1].version
-if version:
-    requirement = '=='.join((requirement, version))
-cmd.append(requirement)
-
-import subprocess
-if subprocess.call(cmd) != 0:
-    raise Exception(
-        "Failed to execute command:\n%s" % repr(cmd)[1:-1])
-
-######################################################################
-# Import and run buildout
-
-ws.add_entry(tmpeggs)
-ws.require(requirement)
-import zc.buildout.buildout
-
-if not [a for a in args if '=' not in a]:
-    args.append('bootstrap')
-
-# if -c was provided, we push it back into args for buildout' main function
-if options.config_file is not None:
-    args[0:0] = ['-c', options.config_file]
-
-zc.buildout.buildout.main(args)
-shutil.rmtree(tmpeggs)
diff --git a/buildout.cfg b/buildout.cfg
deleted file mode 100644
index 40110f9..0000000
--- a/buildout.cfg
+++ /dev/null
@@ -1,403 +0,0 @@
-[buildout]
-parts =
-  cli
-  cli-test
-  config-test
-  coverage
-  flake8
-  parallel-test
-  rack
-  rack-test
-  region
-  region-test
-  region-test-legacy
-  repl
-  sphinx
-  testing-test
-versions = versions
-extends = versions.cfg
-offline = false
-newest = false
-
-# Uncomment the following two lines and set allow-picked-versions=true
-# to automatically update versions.cfg when building recipes.
-# extensions = buildout-versions
-# buildout_versions_file = versions.cfg
-
-prefer-final = true
-allow-picked-versions = false
-
-[common]
-extra-paths =
-  ${buildout:directory}/etc
-  ${buildout:directory}/src
-  ${buildout:directory}
-test-eggs =
-  blessings
-  coverage
-  fixtures
-  hypothesis
-  ipdb
-  junitxml
-  nose
-  nose-timer
-  postgresfixture
-  python-subunit
-  testresources
-  testscenarios
-  testtools
-initialization =
-  ${common:path-munge}
-  ${common:warnings}
-  ${common:environment}
-path-munge =
-  import pathlib, sys
-  # Eliminate argparse usage outside of the standard library. This is
-  # needed because some deps <cough>unittest2<cough> explicitly require
-  # argparse, which zc.buildout then dutifully installs. Unfortunately
-  # argparse 1.1 from PyPI differs substantially to argparse 1.1 in the
-  # standard library. For consistency we want the latter.
-  p_argparse_egg = lambda path: pathlib.Path(path).match("*/argparse-*.egg")
-  sys.path[:] = [path for path in sys.path if not p_argparse_egg(path)]
-  # Sort system paths towards the end of sys.path so that deps defined
-  # here are used in preference to those installed system-wide.
-  p_sys_prefix = lambda path, p=pathlib.Path: p(sys.prefix) in p(path).parents
-  sys.path.sort(key=p_sys_prefix)
-environment =
-  from os import environ
-  environ.setdefault("MAAS_ROOT", "${buildout:directory}/.run")
-warnings =
-  from warnings import filterwarnings
-  filterwarnings("ignore", category=RuntimeWarning, module="pkg_resources")
-asyncio-reactor =
-  # Install the asyncio reactor with uvloop.
-  import asyncio
-  import uvloop
-  from twisted.internet import asyncioreactor, error
-  asyncio.set_event_loop_policy(uvloop.EventLoopPolicy())
-  try:
-      asyncioreactor.install()
-  except error.ReactorAlreadyInstalledError:
-      pass
-inject-test-options =
-  # When running tests from a console show only dots, but when running
-  # headless increase verbosity so we can see the test being run from a
-  # log file. An `options` list must be defined ahead of the use of this
-  # snippet.
-  options += (
-    ["--verbosity=1"]
-    if sys.stdout.isatty() else
-    ["--verbosity=2"]
-  )
-  sys.argv[1:1] = options
-
-[database]
-recipe = zc.recipe.egg
-eggs = postgresfixture
-extra-paths =
-  ${common:extra-paths}
-initialization =
-  ${common:path-munge}
-interpreter =
-entry-points = database=postgresfixture.main:main
-scripts = database
-
-[parallel-test]
-recipe = zc.recipe.egg
-eggs =
-  ${common:test-eggs}
-entry-points =
-  test.parallel=maastesting.parallel:main
-scripts = test.parallel
-extra-paths =
-  ${common:extra-paths}
-initialization =
-  ${common:initialization}
-  ${common:asyncio-reactor}
-
-[region]
-recipe = zc.recipe.egg
-test-eggs =
-  ${common:test-eggs}
-  selenium
-eggs =
-  ${region:test-eggs}
-entry-points =
-  maas-region=maasserver:execute_from_command_line
-  regiond=maasserver.server:run
-initialization =
-  ${common:initialization}
-  environ.setdefault("DJANGO_SETTINGS_MODULE", "maasserver.djangosettings.development")
-  environ.setdefault("MAAS_DEBUG_QUERIES", "1")
-scripts =
-  maas-region
-  regiond
-extra-paths =
-  ${common:extra-paths}
-
-[region-test]
-recipe = zc.recipe.egg
-eggs =
-  ${region:eggs}
-  ${common:test-eggs}
-entry-points =
-  test.region=maastesting.noseplug:main
-initialization =
-  ${region:initialization}
-  ${common:asyncio-reactor}
-  # Prevent query logging as it affects the tests.
-  if 'MAAS_DEBUG_QUERIES' in environ:
-      del environ['MAAS_DEBUG_QUERIES']
-  options = [
-    "--with-crochet",
-    "--with-resources",
-    "--with-scenarios",
-    "--with-select",
-    "--select-dir=src/maasserver",
-    "--select-dir=src/metadataserver",
-    "--cover-package=maas,maasserver,metadataserver",
-    "--cover-branches",
-    # Reduce the logging level to INFO here as
-    # DebuggingLoggerMiddleware logs the content of all the
-    # requests at DEBUG level: we don't want this in the
-    # tests as it's too verbose.
-    "--logging-level=INFO",
-    "--logging-clear-handlers",
-    # Do not run tests tagged "legacy".
-    "-a", "!legacy",
-  ]
-  ${common:inject-test-options}
-  # Configure logging. TODO: Do this in a plugin.
-  from provisioningserver import logger
-  logger.configure(mode=logger.LoggingMode.COMMAND)
-  # Limit concurrency in all thread-pools to ONE.
-  from maasserver.utils import threads
-  threads.install_default_pool(maxthreads=1)
-  threads.install_database_unpool(maxthreads=1)
-  # Disable all database connections in the reactor.
-  from maasserver.utils import orm
-  from twisted.internet import reactor
-  assert not reactor.running, "The reactor has been started too early."
-  reactor.callFromThread(orm.disable_all_database_connections)
-  # Last and least, configure Django.
-  import django; django.setup()
-scripts = test.region
-extra-paths =
-  ${region:extra-paths}
-
-[region-test-legacy]
-recipe = zc.recipe.egg
-eggs =
-  ${region:eggs}
-entry-points =
-  test.region.legacy=maasserver:execute_from_command_line
-initialization =
-  ${region:initialization}
-  ${common:asyncio-reactor}
-  environ.setdefault("MAAS_PREVENT_MIGRATIONS", "1")
-  # Prevent query logging as it affects the tests.
-  if 'MAAS_DEBUG_QUERIES' in environ:
-      del environ['MAAS_DEBUG_QUERIES']
-  options = [
-    "test",
-    "--noinput",
-    "--with-crochet",
-    "--with-scenarios",
-    "--with-select",
-    "--select-dir=src/maasserver",
-    "--select-dir=src/metadataserver",
-    "--cover-package=maas,maasserver,metadataserver",
-    "--cover-branches",
-    # Reduce the logging level to INFO here as
-    # DebuggingLoggerMiddleware logs the content of all the
-    # requests at DEBUG level: we don't want this in the
-    # tests as it's too verbose.
-    "--logging-level=INFO",
-    "--logging-clear-handlers",
-    # Run only tests tagged "legacy".
-    "-a", "legacy",
-  ]
-  ${common:inject-test-options}
-scripts = test.region.legacy
-extra-paths =
-  ${region:extra-paths}
-
-[cli]
-recipe = zc.recipe.egg
-eggs =
-  ${region:eggs}
-initialization =
-  ${common:path-munge}
-entry-points =
-  maas=maascli:main
-extra-paths =
-  ${common:extra-paths}
-scripts =
-  maas
-
-[cli-test]
-recipe = zc.recipe.egg
-eggs =
-  ${cli:eggs}
-  ${common:test-eggs}
-entry-points =
-  test.cli=maastesting.noseplug:main
-initialization =
-  ${common:path-munge}
-  ${common:warnings}
-  options = [
-    "--with-resources",
-    "--with-scenarios",
-    "--with-select",
-    "--select-dir=src/apiclient",
-    "--select-dir=src/maascli",
-    "--cover-package=apiclient,maascli",
-    "--cover-branches",
-  ]
-  ${common:inject-test-options}
-extra-paths = ${cli:extra-paths}
-scripts =
-  test.cli
-
-[js-test]
-recipe = zc.recipe.egg
-eggs =
-  ${common:test-eggs}
-entry-points =
-  test.js=maastesting.karma:run_karma
-extra-paths =
-  ${common:extra-paths}
-scripts =
-  test.js
-initialization =
-  ${common:initialization}
-
-[testing-test]
-recipe = zc.recipe.egg
-eggs =
-  ${common:test-eggs}
-entry-points =
-  test.testing=maastesting.noseplug:main
-initialization =
-  ${common:path-munge}
-  ${common:warnings}
-  ${common:asyncio-reactor}
-  options = [
-    "--with-resources",
-    "--with-scenarios",
-    "--with-select",
-    "--select-dir=src/maastesting",
-    "--cover-package=maastesting",
-    "--cover-branches",
-  ]
-  ${common:inject-test-options}
-extra-paths =
-  ${common:extra-paths}
-scripts =
-  test.testing
-
-[rack]
-recipe = zc.recipe.egg
-eggs =
-  ${common:test-eggs}
-entry-points =
-  maas-rack=provisioningserver.__main__:main
-  maas-common=provisioningserver.__main__:main
-  rackd=provisioningserver.server:run
-extra-paths =
-  ${common:extra-paths}
-scripts =
-  maas-rack
-  maas-common
-  rackd
-initialization =
-  ${common:initialization}
-
-[rack-test]
-recipe = zc.recipe.egg
-eggs =
-  ${rack:eggs}
-  ${common:test-eggs}
-entry-points =
-  test.rack=maastesting.noseplug:main
-initialization =
-  ${common:initialization}
-  ${common:asyncio-reactor}
-  options = [
-    "--with-crochet",
-    "--crochet-no-setup",
-    "--with-resources",
-    "--with-scenarios",
-    "--with-select",
-    "--select-dir=src/provisioningserver",
-    "--cover-package=provisioningserver",
-    "--cover-branches",
-  ]
-  ${common:inject-test-options}
-extra-paths = ${rack:extra-paths}
-scripts =
-  test.rack
-
-[e2e-test]
-recipe = zc.recipe.egg
-eggs =
-  ${region:test-eggs}
-entry-points =
-  test.e2e=maastesting.protractor.runner:run_protractor
-extra-paths =
-  ${common:extra-paths}
-scripts =
-  test.e2e
-initialization =
-  ${common:path-munge}
-  from os import environ
-  environ.setdefault("MAAS_ROOT", "${buildout:directory}/.run-e2e")
-  environ.setdefault("DJANGO_SETTINGS_MODULE", "maasserver.djangosettings.development")
-  environ.setdefault("DEV_DB_NAME", "test_maas_e2e")
-  environ.setdefault("MAAS_PREVENT_MIGRATIONS", "1")
-
-[flake8]
-recipe = zc.recipe.egg
-eggs =
-  flake8
-entry-points =
-  flake8=flake8.main.cli:main
-initialization =
-  ${common:path-munge}
-  ${common:warnings}
-
-[coverage]
-recipe = zc.recipe.egg
-eggs =
-  coverage
-entry-points =
-  coverage=coverage.cmdline:main
-initialization =
-  ${common:path-munge}
-  ${common:warnings}
-scripts =
-  coverage
-
-[sphinx]
-recipe = collective.recipe.sphinxbuilder
-source = ${buildout:directory}/docs
-build = ${buildout:directory}/docs/_build
-extra-paths = ${common:extra-paths}
-eggs =
-  ${region:eggs}
-  ${rack:eggs}
-
-# Convenient REPLs with all eggs available.
-[repl]
-recipe = zc.recipe.egg
-eggs =
-  ${region:eggs}
-  ${rack:eggs}
-  ${common:test-eggs}
-extra-paths = ${common:extra-paths}
-interpreter = py
-scripts = ipy
-entry-points =
-  ipy=IPython.terminal.ipapp:launch_new_instance
-initialization =
-  ${common:initialization}
diff --git a/contrib/maas-http.conf b/contrib/maas-http.conf
deleted file mode 100644
index 9ba82f6..0000000
--- a/contrib/maas-http.conf
+++ /dev/null
@@ -1,39 +0,0 @@
-<IfModule mod_ssl.c>
-    <VirtualHost *:443>
-        SSLEngine On
-        # Do not rely on these certificates, generate your own.
-        SSLCertificateFile    /etc/ssl/certs/ssl-cert-snakeoil.pem
-        SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key
-    </VirtualHost>
-</IfModule>
-
-<IfModule mod_expires.c>
-    <Location /MAAS/>
-        ExpiresActive On
-        ExpiresByType text/javascript "access plus 1 hours"
-        ExpiresByType application/javascript "access plus 1 hours"
-        ExpiresByType application/x-javascript "access plus 1 hours"
-        ExpiresByType text/css "access plus 1 hours"
-        ExpiresByType image/gif "access plus 1 hours"
-        ExpiresByType image/jpeg "access plus 1 hours"
-        ExpiresByType image/png "access plus 1 hours"
-    </Location>
-</IfModule>
-
-<IfModule alias_module>
-    Alias /MAAS/static/ /usr/share/maas/web/static/
-</IfModule>
-
-<IfModule proxy_module>
-    ProxyPreserveHost on
-    ProxyPass /MAAS/ws "ws://localhost:5240/MAAS/ws"
-    ProxyPass /MAAS/static/ !
-    ProxyPass /MAAS/ http://localhost:5240/MAAS/
-    ProxyPass /MAAS http://localhost:5240/MAAS/
-</IfModule>
-
-<IfModule rewrite_module>
-    RewriteEngine On
-    # Redirect (permanently) requests for /MAAS to /MAAS/.
-    RewriteRule ^/MAAS$ %{REQUEST_URI}/ [R=301,L]
-</IfModule>
diff --git a/contrib/preseeds_v2/commissioning b/contrib/preseeds_v2/commissioning
deleted file mode 100644
index aa8043e..0000000
--- a/contrib/preseeds_v2/commissioning
+++ /dev/null
@@ -1 +0,0 @@
-{{preseed_data}}
diff --git a/contrib/preseeds_v2/curtin b/contrib/preseeds_v2/curtin
deleted file mode 100644
index aa8043e..0000000
--- a/contrib/preseeds_v2/curtin
+++ /dev/null
@@ -1 +0,0 @@
-{{preseed_data}}
diff --git a/contrib/preseeds_v2/curtin_userdata b/contrib/preseeds_v2/curtin_userdata
deleted file mode 100644
index 4caddc4..0000000
--- a/contrib/preseeds_v2/curtin_userdata
+++ /dev/null
@@ -1,42 +0,0 @@
-#cloud-config
-debconf_selections:
- maas: |
-  {{for line in str(curtin_preseed).splitlines()}}
-  {{line}}
-  {{endfor}}
-early_commands:
-{{if third_party_drivers and driver}}
-  {{py: key_string = ''.join(['\\x%x' % x for x in driver['key_binary']])}}
-  {{if driver['key_binary'] and driver['repository'] and driver['package']}}
-  driver_00_get_key: /bin/echo -en '{{key_string}}' > /tmp/maas-{{driver['package']}}.gpg
-  driver_01_add_key: ["apt-key", "add", "/tmp/maas-{{driver['package']}}.gpg"]
-  {{endif}}
-  {{if driver['repository']}}
-  driver_02_add: ["add-apt-repository", "-y", "deb {{driver['repository']}} {{node.get_distro_series()}} main"]
-  {{endif}}
-  {{if driver['package']}}
-  driver_03_update_install: ["sh", "-c", "apt-get update --quiet && apt-get --assume-yes install {{driver['package']}}"]
-  {{endif}}
-  {{if driver['module']}}
-  driver_04_load: ["sh", "-c", "depmod && modprobe {{driver['module']}} || echo 'Warning: Failed to load module: {{driver['module']}}'"]
-  {{endif}}
-{{else}}
-  driver_00: ["sh", "-c", "echo third party drivers not installed or necessary."]
-{{endif}}
-late_commands:
-  maas: [wget, '--no-proxy', {{node_disable_pxe_url|escape.json}}, '--post-data', {{node_disable_pxe_data|escape.json}}, '-O', '/dev/null']
-{{if third_party_drivers and driver}}
-  {{if driver['key_binary'] and driver['repository'] and driver['package']}}
-  driver_00_key_get: curtin in-target -- sh -c "/bin/echo -en '{{key_string}}' > /tmp/maas-{{driver['package']}}.gpg"
-  driver_02_key_add: ["curtin", "in-target", "--", "apt-key", "add", "/tmp/maas-{{driver['package']}}.gpg"]
-  {{endif}}
-  {{if driver['repository']}}
-  driver_03_add: ["curtin", "in-target", "--", "add-apt-repository", "-y", "deb {{driver['repository']}} {{node.get_distro_series()}} main"]
-  {{endif}}
-  driver_04_update_install: ["curtin", "in-target", "--", "apt-get", "update", "--quiet"]
-  {{if driver['package']}}
-  driver_05_install: ["curtin", "in-target", "--", "apt-get", "-y", "install", "{{driver['package']}}"]
-  {{endif}}
-  driver_06_depmod: ["curtin", "in-target", "--", "depmod"]
-  driver_07_update_initramfs: ["curtin", "in-target", "--", "update-initramfs", "-u"]
-{{endif}}
diff --git a/contrib/preseeds_v2/curtin_userdata_centos b/contrib/preseeds_v2/curtin_userdata_centos
deleted file mode 100644
index 3de9c99..0000000
--- a/contrib/preseeds_v2/curtin_userdata_centos
+++ /dev/null
@@ -1,9 +0,0 @@
-#cloud-config
-debconf_selections:
- maas: |
-  {{for line in str(curtin_preseed).splitlines()}}
-  {{line}}
-  {{endfor}}
-
-late_commands:
-  maas: [wget, '--no-proxy', '{{node_disable_pxe_url}}', '--post-data', '{{node_disable_pxe_data}}', '-O', '/dev/null']
diff --git a/contrib/preseeds_v2/curtin_userdata_custom b/contrib/preseeds_v2/curtin_userdata_custom
deleted file mode 100644
index 3de9c99..0000000
--- a/contrib/preseeds_v2/curtin_userdata_custom
+++ /dev/null
@@ -1,9 +0,0 @@
-#cloud-config
-debconf_selections:
- maas: |
-  {{for line in str(curtin_preseed).splitlines()}}
-  {{line}}
-  {{endfor}}
-
-late_commands:
-  maas: [wget, '--no-proxy', '{{node_disable_pxe_url}}', '--post-data', '{{node_disable_pxe_data}}', '-O', '/dev/null']
diff --git a/contrib/preseeds_v2/curtin_userdata_suse b/contrib/preseeds_v2/curtin_userdata_suse
deleted file mode 100644
index 3de9c99..0000000
--- a/contrib/preseeds_v2/curtin_userdata_suse
+++ /dev/null
@@ -1,9 +0,0 @@
-#cloud-config
-debconf_selections:
- maas: |
-  {{for line in str(curtin_preseed).splitlines()}}
-  {{line}}
-  {{endfor}}
-
-late_commands:
-  maas: [wget, '--no-proxy', '{{node_disable_pxe_url}}', '--post-data', '{{node_disable_pxe_data}}', '-O', '/dev/null']
diff --git a/contrib/preseeds_v2/curtin_userdata_windows b/contrib/preseeds_v2/curtin_userdata_windows
deleted file mode 100644
index 77e4a65..0000000
--- a/contrib/preseeds_v2/curtin_userdata_windows
+++ /dev/null
@@ -1,11 +0,0 @@
-#cloud-config
-debconf_selections:
- maas: |
-  {{for line in str(curtin_preseed).splitlines()}}
-  {{line}}
-  {{endfor}}
-
-late_commands:
-  maas: [wget, '--no-proxy', '{{node_disable_pxe_url}}', '--post-data', '{{node_disable_pxe_data}}', '-O', '/dev/null']
-
-license_key: {{node.get_effective_license_key()}}
diff --git a/contrib/preseeds_v2/enlist b/contrib/preseeds_v2/enlist
deleted file mode 100644
index aa8043e..0000000
--- a/contrib/preseeds_v2/enlist
+++ /dev/null
@@ -1 +0,0 @@
-{{preseed_data}}
diff --git a/contrib/pycharm/codeStyleSettings.xml b/contrib/pycharm/codeStyleSettings.xml
deleted file mode 100644
index 7fb8ed0..0000000
--- a/contrib/pycharm/codeStyleSettings.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project version="4">
-  <component name="ProjectCodeStyleSettingsManager">
-    <option name="PER_PROJECT_SETTINGS">
-      <value>
-        <XML>
-          <option name="XML_LEGACY_SETTINGS_IMPORTED" value="true" />
-        </XML>
-      </value>
-    </option>
-    <option name="PREFERRED_PROJECT_CODE_STYLE" value="Default (1)" />
-  </component>
-</project>
\ No newline at end of file
diff --git a/contrib/pycharm/encodings.xml b/contrib/pycharm/encodings.xml
deleted file mode 100644
index f758959..0000000
--- a/contrib/pycharm/encodings.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project version="4">
-  <component name="Encoding" useUTFGuessing="true" native2AsciiForPropertiesFiles="false">
-    <file url="PROJECT" charset="UTF-8" />
-  </component>
-</project>
\ No newline at end of file
diff --git a/contrib/pycharm/inspectionProfiles/Project_Default.xml b/contrib/pycharm/inspectionProfiles/Project_Default.xml
deleted file mode 100644
index 1b6d837..0000000
--- a/contrib/pycharm/inspectionProfiles/Project_Default.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<component name="InspectionProjectProfileManager">
-  <profile version="1.0">
-    <option name="myName" value="Project Default" />
-    <option name="myLocal" value="true" />
-    <inspection_tool class="PyUnresolvedReferencesInspection" enabled="true" level="WARNING" enabled_by_default="true">
-      <option name="ignoredIdentifiers">
-        <list>
-          <option value="maasserver.models.node.NodeQueriesMixin.filter" />
-          <option value="maasserver.models.node.NodeQueriesMixin.exclude" />
-          <option value="maasserver.models.subnet.SubnetQueriesMixin.filter" />
-          <option value="maasserver.models.subnet.SubnetQueriesMixin.exclude" />
-          <option value="maasserver.utils.orm.MAASQueriesMixin.filter" />
-          <option value="maasserver.utils.orm.MAASQueriesMixin.exclude" />
-          <option value="maasserver.utils.orm.MAASQueriesMixin.model" />
-        </list>
-      </option>
-    </inspection_tool>
-  </profile>
-</component>
\ No newline at end of file
diff --git a/contrib/pycharm/inspectionProfiles/profiles_settings.xml b/contrib/pycharm/inspectionProfiles/profiles_settings.xml
deleted file mode 100644
index 3b31283..0000000
--- a/contrib/pycharm/inspectionProfiles/profiles_settings.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<component name="InspectionProjectProfileManager">
-  <settings>
-    <option name="PROJECT_PROFILE" value="Project Default" />
-    <option name="USE_PROJECT_PROFILE" value="true" />
-    <version value="1.0" />
-  </settings>
-</component>
\ No newline at end of file
diff --git a/contrib/pycharm/maas.iml b/contrib/pycharm/maas.iml
deleted file mode 100644
index b6908c0..0000000
--- a/contrib/pycharm/maas.iml
+++ /dev/null
@@ -1,36 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<module type="PYTHON_MODULE" version="4">
-  <component name="FacetManager">
-    <facet type="buildout-python" name="Buildout Support">
-      <configuration>
-        <option name="script" value="bin/py" />
-      </configuration>
-    </facet>
-  </component>
-  <component name="NewModuleRootManager">
-    <content url="file://$MODULE_DIR$">
-      <sourceFolder url="file://$MODULE_DIR$/src" isTestSource="false" />
-      <excludeFolder url="file://$MODULE_DIR$/bin" />
-      <excludeFolder url="file://$MODULE_DIR$/build_pkg" />
-      <excludeFolder url="file://$MODULE_DIR$/coverage" />
-      <excludeFolder url="file://$MODULE_DIR$/local" />
-      <excludeFolder url="file://$MODULE_DIR$/logs" />
-      <excludeFolder url="file://$MODULE_DIR$/stage" />
-      <excludeFolder url="file://$MODULE_DIR$/prime" />
-      <excludeFolder url="file://$MODULE_DIR$/parts" />
-    </content>
-    <orderEntry type="jdk" jdkName="Python 3.5.1+ (/usr/bin/python3)" jdkType="Python SDK" />
-    <orderEntry type="sourceFolder" forTests="false" />
-    <orderEntry type="library" name="Buildout Eggs" level="project" />
-    <orderEntry type="library" name="Buildout Eggs" level="project" />
-  </component>
-  <component name="TemplatesService">
-    <option name="TEMPLATE_CONFIGURATION" value="Django" />
-    <option name="TEMPLATE_FOLDERS">
-      <list>
-        <option value="$MODULE_DIR$/templates" />
-        <option value="$MODULE_DIR$/src/maasserver/templates" />
-      </list>
-    </option>
-  </component>
-</module>
diff --git a/contrib/pycharm/misc.xml b/contrib/pycharm/misc.xml
deleted file mode 100644
index cbd05d0..0000000
--- a/contrib/pycharm/misc.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project version="4">
-  <component name="ProjectLevelVcsManager" settingsEditedManually="false">
-    <OptionsSetting value="true" id="Add" />
-    <OptionsSetting value="true" id="Remove" />
-    <OptionsSetting value="true" id="Checkout" />
-    <OptionsSetting value="true" id="Update" />
-    <OptionsSetting value="true" id="Status" />
-    <OptionsSetting value="true" id="Edit" />
-    <ConfirmationsSetting value="0" id="Add" />
-    <ConfirmationsSetting value="0" id="Remove" />
-  </component>
-  <component name="ProjectRootManager" version="2" project-jdk-name="Python 3.5.1+ (/usr/bin/python3)" project-jdk-type="Python SDK" />
-</project>
diff --git a/contrib/pycharm/modules.xml b/contrib/pycharm/modules.xml
deleted file mode 100644
index 8f50088..0000000
--- a/contrib/pycharm/modules.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project version="4">
-  <component name="ProjectModuleManager">
-    <modules>
-      <module fileurl="file://$PROJECT_DIR$/.idea/maas.iml" filepath="$PROJECT_DIR$/.idea/maas.iml" />
-    </modules>
-  </component>
-</project>
\ No newline at end of file
diff --git a/contrib/pycharm/sqldialects.xml b/contrib/pycharm/sqldialects.xml
deleted file mode 100644
index 1962b9b..0000000
--- a/contrib/pycharm/sqldialects.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project version="4">
-  <component name="SqlDialectMappings">
-    <file url="file://$PROJECT_DIR$" dialect="PostgreSQL" />
-  </component>
-</project>
\ No newline at end of file
diff --git a/contrib/tgt.conf b/contrib/tgt.conf
deleted file mode 100644
index 1b5f332..0000000
--- a/contrib/tgt.conf
+++ /dev/null
@@ -1 +0,0 @@
-include /var/lib/maas/ephemeral/tgt.conf.d/*.conf
diff --git a/debian/changelog b/debian/changelog
index 08cbd6b..c400e34 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,2786 +1,5 @@
-maas (2.6.0-7802-g59416a869-0ubuntu1) eoan; urgency=medium
+maas (1:0.1) focal; urgency=medium
 
-  * New upstream release, MAAS 2.6.0.
+  * Install MAAS from the snap, migrating existing install if needed
 
- -- Andres Rodriguez <[e-mail]>  Tue, 11 Jun 2019 13:57:36 -0400
-
-maas (2.6.0~rc2-7802-g59416a869-0ubuntu1) eoan; urgency=medium
-
-  * New upstream release, MAAS 2.6.0 RC 2.
-
- -- Andres Rodriguez <[e-mail]>  Mon, 03 Jun 2019 10:08:01 -0400
-
-maas (2.6.0~rc1-7799-g70b0fe161-0ubuntu1) eoan; urgency=medium
-
-  * New upstream release, MAAS 2.6.0 RC 1.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 30 May 2019 08:45:21 -0400
-
-maas (2.6.0~beta4-7743-g27b04aaf3-0ubuntu1) eoan; urgency=medium
-
-  * New upstream release, MAAS 2.6.0 beta 4.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 10 May 2019 16:50:45 -0400
-
-maas (2.6.0~beta3-7711-gb79157e92-0ubuntu1) eoan; urgency=medium
-
-  * New upstream release, MAAS 2.6.0 beta 3.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 03 May 2019 17:37:32 -0400
-
-maas (2.6.0~beta2-7695-g691e14ea3-0ubuntu1) disco; urgency=medium
-
-  * New upstream release, MAAS 2.6.0 beta 2.
-
- -- Andres Rodriguez <[e-mail]>  Sat, 27 Apr 2019 16:45:32 -0400
-
-maas (2.6.0~beta1-7673-g850a92f90-0ubuntu1) disco; urgency=medium
-
-  * New upstream release, MAAS 2.6.0 beta 1.
-
- -- Andres Rodriguez <[e-mail]>  Wed, 17 Apr 2019 16:24:55 -0400
-
-maas (2.6.0~alpha2-7640-g9c8072b21-0ubuntu1~19.04.1) disco; urgency=medium
-
-  * New upstream release, MAAS 2.6.0 alpha 2
-
- -- Andres Rodriguez <[e-mail]>  Thu, 28 Mar 2019 10:41:15 -0400
-
-maas (2.6.0~alpha1-7593-gcca18b743-0ubuntu1~18.10.1) cosmic; urgency=medium
-
-  * New upstream release, MAAS 2.6.0 alpha 1
-
- -- Andres Rodriguez <[e-mail]>  Tue, 12 Mar 2019 21:42:01 -0400
-
-maas (2.5.0-7442-gdf68e30a5-0ubuntu1) cosmic; urgency=medium
-
-  * New upstream release. MAAS 2.5.0 introduces:
-    - Proxy MAAS communication through the rack controller.
-    - HA - Rack to region communication no longer needs VIPs.
-    - KVM (pod) - Support for networking.
-    - KVM (pod) - Re-designed WebUI.
-    - CentOS storage support.
-    - ESXi deployment support.
-    - Machine listing - Re-designed UI.
-    - Enlistment - now runs commissioning scripts.
-    - Add machines by only specifying IPMI credentials.
-
- -- Andres Rodriguez <[e-mail]>  Tue, 11 Dec 2018 15:15:30 -0500
-
-maas (2.5.0~rc2-7433-gea48d302e-0ubuntu1~18.10.1) cosmic; urgency=medium
-
-  * New upstream release.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 30 Nov 2018 14:00:22 -0500
-
-maas (2.5.0~rc1-7419-ge0d239532-0ubuntu1~18.10.1) cosmic; urgency=medium
-
-  * New upstream bugfix release.
-
- -- Andres Rodriguez <[e-mail]>  Wed, 21 Nov 2018 12:02:18 -0500
-
-maas (2.5.0~beta4-7361-g401d6c73d-0ubuntu1~18.10.1) cosmic; urgency=medium
-
-  * New upstream bugfix release.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 26 Oct 2018 14:22:03 -0600
-
-maas (2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.10.1) cosmic; urgency=medium
-
-  * New upstream bugfix release.
-
- -- Andres Rodriguez <[e-mail]>  Mon, 15 Oct 2018 09:33:40 -0400
-
-maas (2.5.0~beta2-7291-gd0345ced5-0ubuntu1) cosmic; urgency=medium
-
-  * New upstream release. (LP: #1796937)
-  * debian/maas-dhcp.maas-{dhcpd,dhcpd6}.service: Require dhcpd stop
-    in 8 seconds, if not kill it with 'mixed' mode.
-  * debian/control: Drop python3-jinja2 as it is no longer needed to
-    generate documentation.
-  * debian/maas-common.prerm: Add & handle stop of maas-syslog.service.
-  * debian/maas-common.postrm:
-    - Run debhelper handling before manual removal actions.
-    - Purge maas-syslog related files.
-  * debian/maas-rack-controller.prerm: Add & handle stop of
-    maas-rackd.service.
-  * debian/maas-rack-controller.postrm: Purge http and rpc.state files.
-  * debian/maas-region-api.postrm: Purge maas-regiond socket file.
-
- -- Andres Rodriguez <[e-mail]>  Tue, 02 Oct 2018 22:55:12 -0400
-
-maas (2.5.0~beta1-7225-g817fb216d-0ubuntu1) cosmic; urgency=medium
-
-  * New upstream release (LP: #1792389)
-  * debian/control: Depend on python3-jinja2
-  * MAAS now manages its own rsyslog daemon:
-    - d/maas-common.maas-syslog.service: Add service.
-    - d/extras/99-maas-common-sudoers: start/stop/status for maas-rsyslog.
-    - d/rules: Handle installation of maas-rsyslog.
-    - d/extras/20-maas.conf: Drop as MAAS now generates its own config.
-    - d/maas-region-api.install: Drop install of 20-maas.conf.
-    - d/maas-region-api.postinst: Drop restart of rsyslog.
-    - d/maas-common.install: Drop install of maas-rsyslog.conf.
-    - d/maas-common.{preinst,postinst}: Handle upgrades.
-
- -- Andres Rodriguez <[e-mail]>  Mon, 17 Sep 2018 05:30:25 -0400
-
-maas (2.5.0~alpha2-7175-gab01a63f2-0ubuntu1) bionic; urgency=medium
-
-  * New upstream release.
-  * Don't autostart maas-rackd on install to avoid initialization errors.
-    - debian/rules: add --no-start for maas-rackd.
-    - debian/maas-rack-controller.postinst: enable/start maas-rackd.
-  * Make package more lintian clean:
-    - debian/*.postinst: Remove of use of systemctl for deb-system-*
-    - debian/*.lintin-overrides: Add overrides for a few warnings.
-  * debian/rules: Do not override dh_installinit as we are using systemd.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 23 Aug 2018 08:04:57 -0400
-
-maas (2.5.0~alpha1-7104-g18ae9e407-0ubuntu1) bionic; urgency=medium
-
-  * New upstream release.
-
- -- Andres Rodriguez <[e-mail]>  Mon, 16 Jul 2018 14:30:06 -0400
-
-maas (2.4.0~rc2-6980-gc5ebdd7b1-0ubuntu1) bionic; urgency=medium
-
-  * New upstream release.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 18 May 2018 17:48:22 -0400
-
-maas (2.4.0~rc1-6959-gd7a158fc3-0ubuntu1) bionic; urgency=medium
-
-  * New upstream release.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 11 May 2018 14:34:52 -0400
-
-maas (2.4.0~beta3-6929-g62682abf5-0ubuntu1) bionic; urgency=medium
-
-  * New upstream release.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 03 May 2018 03:31:14 -0400
-
-maas (2.4.0~beta2-6865-gec43e47e6-0ubuntu1) bionic; urgency=medium
-
-  * New upstream release. (LP: #1754697)
-
- -- Andres Rodriguez <[e-mail]>  Mon, 16 Apr 2018 09:12:38 -0400
-
-maas (2.4.0~beta1-6799-g391e5f16d-0ubuntu1) bionic; urgency=medium
-
-  * New upstream release. (LP: #1754697)
-  * debian/*: Integrate maas-dns into maas-region-api; make maas-dns a
-    transitional package
-
- -- Andres Rodriguez <[e-mail]>  Fri, 30 Mar 2018 15:32:38 -0400
-
-maas (2.4.0~alpha2-6717-gffaddd526-0ubuntu1~18.04.1) bionic; urgency=medium
-
-  * New upstream release. (LP: #1754697)
-  * debian/*: Replace ntp in favor of chrony.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 09 Mar 2018 11:01:52 -0500
-
-maas (2.4.0~alpha1-6573-g12ee2331b-0ubuntu1) bionic; urgency=medium
-
-  * New upstream release
-  * debian/*: Drop usage of apache2. It has long been used to maintain
-    backwards compat for 1.x versions of MAAS, but starting from 2.4, it
-    will no longer be supported.
-  * debian/maas-{dhcp,proxy}.lintian-overrides: Add lintin overrides.
-  * debian/control:
-    - Bump Standards-Version.
-    - Add depends on python3-uvloop, python3-macaroonbakery.
-    - Drop depends on ubuntu-cloudimage-keyring in favor of ubuntu-keyring.
-    - Drop depends on dh-systemd as it is now deprecated. Newer debhelper
-      integrates it, as such, bump dep version.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 09 Feb 2018 18:50:10 -0500
-
-maas (2.3.0-6434-gd354690-0ubuntu1) bionic; urgency=medium
-
-  * New upstream release, MAAS 2.3.0:
-    - Add support for CentOS & Windows networking.
-    - Add support for Upstream Proxy.
-    - Add the ability to deploy rack controllers.
-    - Add the ability to report controller versions.
-    - Add HTTP boot for ephemeral images, instead of 'tgt'.
-    - Add django 1.11 support.
-    - Introduce beaconing for better network discovery.
-    - Improve hardware testing for better usage and feedback.
-    - Improves performance by improving DNS reloading performance.
-    - Machine, devices & controller page re-design.
-
- -- Andres Rodriguez <[e-mail]>  Mon, 20 Nov 2017 14:08:22 -0500
-
-maas (2.3.0~rc2-6412-g410b453-0ubuntu1) artful; urgency=medium
-
-  * New upstream release, 2.3.0 rc2.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 09 Nov 2017 20:36:29 -0500
-
-maas (2.3.0~rc1-6393-g8103f0a-0ubuntu1) artful; urgency=medium
-
-  * New upstream release, 2.3.0 rc1.
-
- -- Andres Rodriguez <[e-mail]>  Mon, 06 Nov 2017 13:23:31 -0500
-
-maas (2.3.0~beta3-6368-g03ca7f4-0ubuntu1) artful; urgency=medium
-
-  * New upstream release, 2.3.0 beta3.
-  * debian/control: Add missing deps for python3-maas-client (LP: #1724181)
-
- -- Andres Rodriguez <[e-mail]>  Wed, 11 Oct 2017 16:42:41 -0400
-
-maas (2.3.0~beta2-6327-gdd05aa2-0ubuntu1) artful; urgency=medium
-
-  * New upstream release, 2.3.0 beta2 (LP: #1717543).
-
- -- Andres Rodriguez <[e-mail]>  Wed, 11 Oct 2017 12:22:51 -0400
-
-maas (2.3.0~beta1-6301-gca25180-0ubuntu1) artful; urgency=medium
-
-  * New upstream release, 2.3.0 beta1 (LP: #1717543):
-    - Update the UI to surface hardware testing.
-    - Rack Controller deployment for all machines via the API.
-    - UI Improvements: Use new design for node details page and address
-      various other UX issues.
-    - API improvements: Introduce API output for volume_groups, raids,
-      cache_sets and baches to the machines output. Used to support libmaas.
-
- -- Andres Rodriguez <[e-mail]>  Wed, 04 Oct 2017 09:38:40 -0400
-
-maas (2.3.0~alpha3-6250-g58f83f3-0ubuntu1) artful; urgency=medium
-
-  * New upstream release, 2.3.0 alpha3 (LP: #1717543):
-    - Hardware Testing:
-      + Ability to test and gather results per individual component
-        (e.g. per disks).
-      + Add 7z CPU performance test.
-      + Add fio storage performance test.
-      + Add ability to define YAML metadata for custom testing scripts,
-        allowing MAAS to parse and utilize such metadata.
-    - Rack Controller deployment for Whitebox Switches.
-    - Improved DNS reloading.
-    - UI - Controller Versions & Notifications.
-    - UI - Refactor Zones page in Angular away from YUI.
-  * Move scripts to maas-common that are used by the MAAS region controller
-    in addition to the rack.
-    - Add /usr/lib/maas/maas-common script.
-  * Bump debhelper compat level 9.
-  * debian/maas-common.links: Drop as it created a link for a binary that
-    was already deprecated.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 15 Sep 2017 10:37:57 -0500
-
-maas (2.3.0~alpha2-6194-g7fb23b0-0ubuntu1) artful; urgency=medium
-
-  * New upstream release, 2.3.0 alpha2:
-    - Support for CentOS & Windows netwok configuration
-    - Add Switch model
-    - Add better Network Discovery & Beaconing
-    - Minor UI improvements
-
- -- Andres Rodriguez <[e-mail]>  Tue, 22 Aug 2017 13:49:24 -0400
-
-maas (2.3.0~alpha1-6165-geae082b-0ubuntu1) artful; urgency=medium
-
-  * New upstream release, 2.3.0 alpha1:
-    - Support for django 1.11.
-    - Support for upstream proxy.
-    - Support ephemeral image via HTTP instead of iSCSI.
-  * Add "maas-rack observe-beacons" to list of commands capable of
-    running as the "maas" user.
-  * Add /usr/lib/maas/maas-beacon-monitor script.
-  * Add maas-beacon-monitor script to sudoers file.
-    (Allows observation of UDP traffic sent to port 5240.)
-  * Conflicts with python3-googleapi
-
- -- Andres Rodriguez <[e-mail]>  Sat, 29 Jul 2017 10:56:23 +0100
-
-maas (2.2.0+bzr6054-0ubuntu2) artful; urgency=medium
-
-  * debian/rules: Fix FTBFS in artful.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 08 Jun 2017 18:57:01 -0400
-
-maas (2.2.0+bzr6054-0ubuntu1) artful; urgency=medium
-
-  * New upstream release, MAAS 2.2.0.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 18 May 2017 11:08:43 -0400
-
-maas (2.2.0~rc4+bzr6048-0ubuntu1) zesty; urgency=medium
-
-  * New upstream release, MAAS 2.2.0 RC 4.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 27 Apr 2017 16:10:06 -0400
-
-maas (2.2.0~rc3+bzr6025-0ubuntu1) artful; urgency=medium
-
-  * New upstream release, MAAS 2.2.0 RC 3.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 21 Apr 2017 09:49:58 -0400
-
-maas (2.2.0~rc2+bzr5983-0ubuntu1) zesty; urgency=medium
-
-  * New upstream release, MAAS 2.2.0 RC 2.
-
- -- Andres Rodriguez <[e-mail]>  Sat, 15 Apr 2017 00:17:22 -0400
-
-maas (2.2.0~rc1+bzr5922-0ubuntu2) zesty; urgency=medium
-
-  * Bump depends version on python3-curtin. (LP: #1680175)
-
- -- Andres Rodriguez <[e-mail]>  Wed, 05 Apr 2017 13:51:58 -0400
-
-maas (2.2.0~rc1+bzr5922-0ubuntu1) zesty; urgency=medium
-
-  * New upstream release, MAAS 2.2.0 RC 1. (FFe LP: #1667141)
-  * debian/maas-common.logrotate: Rotate maas.log weekly, instead of daily.
-    Store logs for 8 weeks. (LP: #1677005)
-
- -- Andres Rodriguez <[e-mail]>  Tue, 28 Mar 2017 11:08:38 -0400
-
-maas (2.2.0~beta4+bzr5856-0ubuntu1) zesty; urgency=medium
-
-  * New upstream release, MAAS 2.2.0 Beta 4. (FFe LP: #1667141)
-    - Add support to disable components.
-    - Improve RSD details page. Show composed machines and power tab.
-    - Add NTP & Internet connectivity tests.
-    - UX improvements - Change to new tab system to improve navigation.
-    - Error surfacing - For interfaces of Machines & Devices.
-    - Windows deployments - support to select the root/boot disk.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 16 Mar 2017 16:10:26 +0000
-
-maas (2.2.0~beta3+bzr5815-0ubuntu1) zesty; urgency=medium
-
-  * New upstream release. MAAS 2.2.0 Beta 3 (FFe LP: #1667141):
-    - Introduce storage verification smoke tests.
-    - Introduce notifications API.
-    - Add device details page.
-    - Introduce Wedge BMC discovery during commissioning.
-    - Add pod listing & details page.
-    - Add dynamic composition for virsh devices.
-
- -- Andres Rodriguez <[e-mail]>  Wed, 15 Feb 2017 08:37:25 -0500
-
-maas (2.2.0~beta2+bzr5717-0ubuntu1) zesty; urgency=medium
-
-  * New upstream release. MAAS 2.2.0 Beta 2 (bzr5717):
-    - Introduce initial support for Intel RSD.
-    - Introduce IPv6 IPMI auto-discovery.
-    - Introduce notifications.
-
- -- Andres Rodriguez <[e-mail]>  Mon, 30 Jan 2017 15:55:02 -0500
-
-maas (2.2.0~beta1+bzr5675-0ubuntu1) zesty; urgency=medium
-
-  * New upstream release. MAAS 2.2.0 Beta 1 (bzr5675):
-    - Changing the concept of Spaces to a L2 layer.
-    - Support for DHCP relays.
-    - Introduce the concept of UNMANAGED subnets.
-
- -- Andres Rodriguez <[e-mail]>  Wed, 11 Jan 2017 13:34:46 +0200
-
-maas (2.2.0~alpha1+bzr5614-0ubuntu1) zesty; urgency=medium
-
-  * New upstream release. MAAS 2.2.0 Alpha 1 (bzr5614):
-    - Don't install Django settings into /usr/share/maas/maas. For
-      regiond these were squatting the `maas` namespace, preventing its
-      use elsewhere (LP: #1646748)
-
- -- Andres Rodriguez <[e-mail]>  Mon, 21 Nov 2016 20:01:31 -0500
-
-maas (2.1.1+bzr5501-0ubuntu1) zesty; urgency=medium
-
-  * MAAS new upstream bugfix release. MAAS 2.1.1 bzr 5544.
-
- -- Andres Rodriguez <[e-mail]>  Mon, 24 Oct 2016 11:28:59 -0400
-
-maas (2.1.0+bzr5480-0ubuntu1) yakkety; urgency=medium
-
-  * MAAS new upstream bugfix release. MAAS 2.1.0 (0-day SRU LP: #1633064):
-    - TestPartition.test_get_partition_number_returns_starting_at_2_for_ppc64el
-      fails spuriously (LP: #1569365)
-    - "Deployed" and "Deploying" are too similar (LP: #1598470)
-    - Users' maas api keys do not have a name (LP: #1536354)
-    - [2.1] Incorrect logging message - showing SERVICE_STATE.ON (LP: #1631358)
-    - [2.1 UI] Images page "Queued for download" is confusing when selections
-      are not saved (LP: #1631420)
-    - [2.1b1] Dashboard column widths for discovered items are
-      wonky (LP: #1631024)
-    - [2.1b1] 'Registering existing rack controller' (LP: #1631022)
-    - [2.1] Command 'interface link-subnet' does not work (LP: #1629604)
-    - [FUJ] SSH input field not indicated for invalid username & the error
-      is incomprehensible (LP: #1628114)
-    - [2.1 ipv6] DHCP generation should not fail when address-family
-      conflicts are present (LP: #1629475)
-    - [2.0rc2] Commissioning node with gateway_link_v4 set fails. (LP: #1603466)
-    - [2.1, 2.0 UI] Error when using dhcp range with pre-existing dynamic
-      reservation (LP: #1608555)
-    - [2.1b2] Node failed to be released, because of the following error:
-      'NoneType' object has no attribute 'addErrback' (LP: #1632815)
-    - [2.1, Yakkety, UI] UI error when adding a chassis (LP: #1632395)
-    - [2.0, 2.1 UI] Other reserved IP ranges disappear when one of them is
-      deleted on Subnet details page. (LP: #1631079)
-    - [2.1b1] MAAS fails to deploy systems with 3+ TB disks (LP: #1630667)
-    - [2.1 Yakkety UI] Unable to select nodes (LP: #1630633)
-    - [2.0, 2.1] Release and list IPs reserved by another user (LP: #1629061)
-    - [2.0rc2] Changing DNSSEC validation does not trigger configuration
-      file update (LP: #1605476)
-    - [2.1] Failed to mount a partition and it doesn't surface error. (LP: #1631152)
-    - [2.1. Yakkety] "Map subnet" action doesn't work. (LP: #1632862)
-
- -- Andres Rodriguez <[e-mail]>  Wed, 05 Oct 2016 21:47:25 -0400
-
-maas (2.1.0~beta2+bzr5454-0ubuntu1) yakkety; urgency=medium
-
-  * MAAS new upstream bugfix release. MAAS 2.1.0 beta 2 (bzr5454):
-    - [2.1] Bootloaders not downloaded on initial import (LP: #1630394)
-    - Cryptic error when PXE-boot requires an image not yet imported (LP: #1611949)
-    - [2.0, 2.1, UI] MAAS webui allows boot disk to be changed on an
-      already deployed node (LP: #1625676)
-    - [2.1] Rename "Networks" tab to "Subnets" (LP: #1630591)
-    - [2.1] netaddr assumes MAC OUI is ascii (LP: #1628761)
-    - [2.1, 2.0] Can't input dynamic range on "Enable DHCP" after I deleted
-      the dynamic range (LP: #1619262)
-    - Machine unable to pxe with no-such-image while non-related images are
-      being imported (LP: #1612203)
-    - External DHCP detection is broken for a variety of reasons (LP: #1628645)
-    - [2.1] expected string or bytes-like object (LP: #1627362)
-    - [2.1] When trying to release a node, it gets stuck in releasing if
-      there is no rack controller to power control (LP: #1614659)
-    - WebUI needs a filter for deployed OS (LP: #1445941)
-
- -- Andres Rodriguez <[e-mail]>  Wed, 05 Oct 2016 10:59:45 -0400
-
-maas (2.1.0~beta1+bzr5433-0ubuntu1) yakkety; urgency=medium
-
-  * MAAS new upstream release. MAAS 2.1.0 beta 1 (bzr5433):
-    - Support for new version of streams.
-    - Bootloaders are now downloaded from the streams.
-    - Support for Low Latency kernels.
-    - Support for new hardware enablement kernels.
-    - Device discovery
-      - UI ability to Map a network as an action.
-      - Ability to select interval of active discovery.
-      - Ability to enable active discovery per subnet.
-  * Remove old template files on package removal.
-
- -- Andres Rodriguez <[e-mail]>  Tue, 27 Sep 2016 14:44:26 -0400
-
-maas (2.1.0~alpha4+bzr5397-0ubuntu1) yakkety; urgency=medium
-
-  * MAAS new upstream release, MAAS 2.1.0 alpha 4 (bzr5397):
-    - Complete First User Journey (Ability to import keys from GH/LP).
-    - User profile has ability to import keys from GH/LP as well.
-    - Device discovery:
-      - Ability to clear records that may be incorrect.
-      - Ability to 'Map networks' via the API.
-    - Import NTP configuration via vendor-data and DHCP.
-
- -- Andres Rodriguez <[e-mail]>  Mon, 19 Sep 2016 17:21:47 -0400
-
-maas (2.1.0~alpha3+bzr5368-0ubuntu1) yakkety; urgency=medium
-
-  * New upstream release, MAAS 2.1.0 Alpha 3 (bzr5363):
-    - First user journey (SSH key import not yet available).
-    - Allow the user to import SSH keys from LP or GH (only API/CLI).
-    - Provide NTP services. Region and Rack Controllers now provide NTP
-      services. Machines are also deployed with NTP configuration via.
-      + Add cloud-init vendor data to support configuring the machine with
-        NTP settings.
-    - Images page complete redesign and transition to AngularJS.
-
- -- Andres Rodriguez <[e-mail]>  Mon, 19 Sep 2016 17:21:20 -0400
-
-maas (2.1.0~alpha2+bzr5321-0ubuntu1) yakkety; urgency=medium
-
-  * New upstream release, MAAS 2.1.0 Alpha 2 (bzr5321):
-    - Commissioning user data and PXE templates no longer user configs.
-      They are no longer shipped on /etc/maas.
-    - Adds support for Device Discovery (Backend and API).
-    - [UI] Better error surfacing for DHCP snippets and Package Repositories.
-  * Add depends on avahi-utils, ntp, and tcpdump.
-  * Old templates still exist. Move them so users know they are no longer
-    user (LP: #1619202)
-  * Create the /etc/ntp directory. MAAS writes custom NTP configuration
-    to /etc/ntp/maas.conf because ntpd is allowed by AppArmor to read
-    configuration only from /etc/ntp.conf and /etc/ntp/**.
-
- -- Andres Rodriguez <[e-mail]>  Wed, 31 Aug 2016 20:25:17 +0100
-
-maas (2.1.0~alpha1+bzr5300-0ubuntu1) yakkety; urgency=medium
-
-  * New upstream release, MAAS 2.1.0 Alpha 1 (bzr5300):
-    - Advanced networking - static routes.
-    - Machine networking - bridge configuration.
-    - Machine networking - UI redesign and tags.
-    - Derived (mirrors) and additional repositories.
-    - Maintenance - Rescue Mode.
-    - Device discovery - backend.
-    - NTP support - backend.
-  * Give MAAS on both region and rack the ability to start, restart, and
-    get the status of the local NTP service.
-  * Depend on python3-attr for the region and rack controllers.
-
- -- Andres Rodriguez <[e-mail]>  Wed, 03 Aug 2016 10:51:50 -0400
-
-maas (2.0.0~rc3+bzr5180-0ubuntu2) yakkety; urgency=medium
-
-  * Really fix by the determination of the default gateway, otherwise
-    automatically chose localhost. (LP: #1607112)
-
- -- Andres Rodriguez <[e-mail]>  Wed, 27 Jul 2016 22:20:09 -0400
-
-maas (2.0.0~rc3+bzr5180-0ubuntu1) yakkety; urgency=medium
-
-  * New upstream release, 2.0.0 RC3 bzr5180:
-    - CLI version command doesn't work (2.0) (LP: #1557434)
-    - [2.0rc1] MAAS does not respect default subnet's DNS server when
-      choosing default DNS (LP: #1576116)
-    - [2.0RC1] MAAS displays every power query on the summarized view of
-      node event log (LP: #1594991)
-    - [2.0] Loading latest machine events can make web browser
-      unresponsive (LP: #1598028)
-    - [2.0rc1] MAAS doesn't honor DNS settings for a subnet for
-      DHCP (LP: #1600720)
-    - [2.0rc1] drop arm64/efi grub module workaround (LP: #1600285)
-    - maas login yields "ImportError: No module named
-      'maasserver'" (LP: #1604169)
-    - [doc] events API limit,before, after options not
-      documented (LP: #1604901)
-    - RackController.get_image_sync_status causes huge load
-      on regiond process (LP: #1604465)
-    - [2.0b8] MAAS is automatically monitoring timeouts. (LP: #1598149)
-    - [2.0] Error messaging about monitor expiry has been
-      dropped (LP: #1605252)
-    - [2.0rc2] Can't get node-results via cli/api (LP: #1602721)
-    - node set to "failed deployment" for no visible reason (LP: #1604962)
-    - Event log should always include a reason why a node was
-      marked Failed Deployment (LP: #1604987)
-  * If no default route is present in the system, configure maas_url on
-    regiond.conf to localhost to allow the user to tell MAAS what IP to use.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 22 Jul 2016 18:05:45 -0400
-
-maas (2.0.0~rc2+bzr5156-0ubuntu1) yakkety; urgency=medium
-
-  * New upstream release, 2.0.0 RC2 bzr5156:
-    - Pick up wrong grub.cfg if another filesystem exists (LP: #1582070)
-    - [2.0] confusing reverse DNS lookups because MAAS creates multiple
-      PTR records (LP: #1599223)
-    - [2.0] reverse DNS sometimes assigns FQDN where it should assign
-      IFACE.FQDN (LP: #1600259)
-    - [2.0rc1] after upgrade from 2.0b3, Error on request (13)
-      subnet.list: 'NoneType' object is not iterable (LP: #1599997)
-    - [2.0rc1] Image import dates are inconsistent (LP: #1598461)
-    - [2.0rc1] Following fresh install maas command fails
-      PermissionError: [Errno 13] Permission denied:
-      '/home/ubuntu/.maascli.db' (LP: #1598937)
-    - [1.9.3,2.0] cannot create more than 4 partitions when disk is
-      configured with mbr (LP: #1597787)
-    - [1.9,2.0,UX] Can't add aliases when parent interface is set to
-      'DCHP' (LP: #1600267)
-    - [1.9,2.0,UX] Creating a Bcache disk is not prevented when is not
-      created in partition (LP: #1600198)
-
- -- Andres Rodriguez <[e-mail]>  Wed, 06 Jul 2016 09:49:41 -0400
-
-maas (2.0.0~rc1+bzr5143-0ubuntu1) xenial; urgency=medium
-
-  * New upstream release, 2.0.0 RC1 bzr5143:
-    - Determine a method for how to reconnect a deleted rack controller (LP: #1576357)
-    - [2.0b7, regression] maas-rack register makes up a new hostname (LP: #1592246)
-    - [2.0b8] HMC power driver regression -- Not able to connect via SSH. (LP: #1595753)
-    - [2.0b7] Date and time format should be consistent accross logs (LP: #1592885)
-    - [2.0b8] Unable to set default gateway interface (LP: #1597324)
-    - [1.9] VMware power management fails when VMs are organized in nested subfolders (LP: #1515188)
-    - [2.0] maas 2.0 pxeboot fails on PowerNV (LP: #1596046)
-
- -- Andres Rodriguez <[e-mail]>  Tue, 28 Jun 2016 16:58:20 -0400
-
-maas (2.0.0~beta8+bzr5134-0ubuntu1) xenial; urgency=medium
-
-  * New upstream release, 2.0.0 beta8 bzr5134:
-    - Allow ed25519 and ecdsa ssh keys (LP: #1590081)
-    - [2.0b2, UI] Can't add a device and it does not show why. (LP: #1462078)
-    - [2.0b3] Interfaces on region controllers are not
-      discovered (LP: #1573626)
-    - [2.0b4, UI] No feedback when failing to assign static IP address on
-      the Node Details Page (LP: #1562107)
-    - [2.0b5] No way to read settings, like proxy, for non-admin
-      users (LP: #1583670)
-    - [2.0b5] Commissing with LVM breaks deployments (LP: #1585016)
-    - [2.0b5] dns templates still in /etc/maas/templates (LP: #1581729)
-    - [2.0b6] django.db.utils.IntegrityError: insert or update on
-      table "piston3_consumer" (LP: #1588907)
-    - [2.0b6] Image status stays out-of-sync after adding custom image (LP: #1581130)
-    - [2.0b6] core count not updated during commissioning if MAAS
-      previously stored a higher core count (LP: #1590144)
-    - [2.0b7] Adding rack controller instructions could be in the
-      GUI (LP: #1592282)
-    - [2.0b7] Enlisting output returns objects (LP: #1592132)
-    - [2.0b7, UI] Can't sort IP addresses under a subnet details
-      page (LP: #1592137)
-    - [2.0b7] Nodes API doesn't show regions (LP: #1593789)
-  * /etc/maas/templates/dns is obsolete. (LP: #1581729)
-  * Switch to OpenSSH for SSH public key validation. Previously
-    Twisted's conch was used but it does not yet support the newer ecdsa
-    and ed25519 key types. (LP: #1590081)
-  * debian/control: maas-region-api depends on maas-cli.
-  * debian/maas-region-api.postinst: Ensure rsyslog is restarted.
-  * debian/maas-region-controller.postinst: Ensure maas_url ends with 5240.
-  * Versioned Depend on squid
-  * debian/maas-region-controller.config: Ensure dbc_go is not run when
-    dbconfig common is not yet installed.
-  * Wait for squid to finish starting before returning from the start command.
-    LP: #1592954
-
- -- Andres Rodriguez <[e-mail]>  Tue, 14 Jun 2016 17:08:48 -0400
-
-maas (2.0.0~beta7+bzr5112-0ubuntu1) xenial; urgency=medium
-
-  * New upstream release, 2.0.0 beta 7 bzr5112:
-   - [2.0b5] p.refresh.get_swap_size misconverting units (LP: #1587896)
-   - get_interfaces_definition is not thread-safe (LP: #1587896)
-   - [2.0] Cannot create an IP reservation with a hostname (LP: #1590021)
-   - [2.0b5] request to http://.../MAAS/metadata/status/<systemdid>/latest
-     failed (LP: #1581723)
-   - [2.0b4] Rack Controller fail to update commissioning info? (LP: #1577953)
-   - [2.0b6, UI] When I delete a fabric, it takes me back to the
-     Node listing page (LP: #1589562)
-   - [2.0b6, UI] When I delete a space, it takes me back to the
-     Node listing page (LP: #1589596)
-   - [2.0b5, UI] No form validation when adding a subnet, space,
-     fabric or vlan (LP: #1588298)
-   - [2.0b6, UI] Message "No IP ranges have been reserved for this subnet."
-     doesn't go away after adding IP Range (LP: #1589606)
-   - [2.0b6, UI] Can't add a VLAN over the WebUI (LP: #1589583)
-   - [2.6b6, UI] Adding a fabric with an optional name ends up with a new
-     fabric with automatically assigned name (LP: #1589560)
-   - [2.6b6, UI] Adding a space with an optional name ends up with a new
-     space with automatically assigned name (LP: #1589595)
-   - Auto detection of running virtual environment during commissioning
-     almost always fails (LP: #1590946)
-   - [2.0b6] Cannot allocate a node based on its system_id (LP: #1590991)
-   - [2.0,1.9] 3rd party HP drivers (archive hostname renamed) - deployment
-     fails (LP: #1591093)
-   - [2.0b4 UI] MAAS WebUI doesn't quickly refresh when deleting
-     machines (LP: #1581219)
-   - [2.0b4] Can attempt to commission enlisted nodes without chosen
-     power type (LP: #1579215)
-   - [2.0b6] Can edit fabric and subnet on deployed node (LP: #1590499)
-   - [2.0b6] some arm64 systems need ipmi_ssif module in addition to
-     ipmi_si (LP: #1591395)
-   - [2.0] maas createadmin fails (LP: #1591346)
-   - [2.0b6] Attempting to delete a VLAN that cannot be deleted, shows
-     traceback in regiond.log (LP: #1589587)
-   - [2.0b6] Commisioning fails on machines without HW
-     virtualization (LP: #1591958)
-
- -- Andres Rodriguez <[e-mail]>  Mon, 06 Jun 2016 18:54:19 -0400
-
-maas (2.0.0~beta6+bzr5073-0ubuntu1) xenial; urgency=medium
-
-  * New upstream release, 2.0.0 beta 6 bzr5073:
-    - Spurious failures in test_regionservice (LP: #1572646)
-    - use http for stream mirror, not https (LP: #1582836)
-    - MAAS version API call should not require authentication (LP: #1583715)
-    - Detect and identify NIC SR-IOV capability (LP: #1572740)
-    - [1.9,2.0]Commissioning fails when BIOS reports floppy drive,
-      but there is none installed (LP: #1584211)
-    - [1.9,2.0] DNS record created against IPv6 address when it is not
-      on the PXE interface (LP: #1584850)
-    - [2.0] MaaS 2.0 BMC information not removed when nodes are removed (LP: #1586555)
-    - [2.0] IPMI driver does not handle timeouts correctly (LP: #1508741)
-    - [2.0] Display RAM amount to the first decimal place in the UI  (LP: #1585759)
-    - [2.0] Expose the refresh rack controller action over the UI (LP: #1585760)
-    - [2.0] Rename maas-nodegrou-worker to MAAS (LP: #1585768)
-    - [2.0a1] MAAS should ensure that BMC password is correct before
-      saving (LP: #1553841)
-    - [2.0b2] DNS zone serials are not stable (LP: #1571645)
-    - [2.0b2] If you deploy a machine in MAAS, and manually install a
-      rack controller in it, it disappears from the machine list" (LP: #1570985)
-    - [2.0b3] rack / region controllers are visible to non-admins (LP: #1576417)
-    - [2.0b4] external maas-rack-controller logs to syslog instead of
-      maas.log (LP: #1577972)
-    - [2.0b4] twisted.internet.error.ConnectionDone: Connection was
-      closed cleanly. (LP: #1580817)
-    - [2.0b4 UI/API] No notifications rack controller is disconnected.
-      No power type available (LP: #1581318)
-    - [2.0b5] AMT machines using wsman do not netboot (LP: #1580350)
-    - [2.0b5] When installing secondary region controller on its on,
-      last image sync is never (LP: #1581737)
-    - [2.0b5] Can't force the import of images per Rack Controller (LP: #1583685)
-    - [2.0b5] After changing proxy, MAAS cannot install images (LP: #1585649)
-    - [2.0b5] MAAS doesn't import default images automatically (LP: #1584936)
-    - [2.0b5] Trying to assign an IP address statically to a device results
-      in builtins.AttributeError: 'NoneType' object has no attribute
-      'link_subnet' (LP: #1558635)
-    - [2.0b5] duplicate key on startup: Key (vid, fabric_id)=(2, 0)
-      already exists. (LP: #1583333)
-    - [2.0b5] Deployed regions should be able to transistion back to
-      machines (LP: #1588531)
-    - [2.0b5] domain details page does not update as the domain contents
-      change (LP: #1581224)
-    - [2.0b5] Cannot disable DHCP if you remove the subnet first ("Cannot
-      configure DHCP: At least one dynamic range is required.") (LP: #1583392)
-    - [2.0b5] builtins.ValueError: invalid literal for int() with base 10 (LP: #1588846)
-    - [2.0, UI] Bulk actions-Nodes action doesn’t apply should be red (LP: #1585628)
-    - [2.0, UI] Add fabric, VLAN, Space show's badly place form (LP: #1587936)
-    - [2.0, UI] 'Commission' a node under the Node Listing Page shows actions
-      not correctly formatted.  (LP: #1587939)
-    - [2.0, UI] Add domain show's badly place form (LP: #1587998)
-    - [2.0, UI] There's no spacing between combo boxes under the Machine
-      Details page (LP: #1588000)
-
- -- Andres Rodriguez <[e-mail]>  Fri, 03 Jun 2016 18:05:32 -0400
-
-maas (2.0.0~beta5+bzr5026-0ubuntu1) xenial; urgency=medium
-
-  * New upstream release, 2.0.0 beta 5 bzr5026:
-    - [UI 2.0b1] Impossible to change subnet CIDR or gateway with
-      instant editing (LP: #1572076)
-    - [UI 2.0b1] Network details page doesn't have CSS for
-      editting (LP: #1568102)
-    - [UI 2.0b2] Can't edit fabric's, vlans, subnets from the
-      WebUI (LP: #1571670)
-    - [UI 2.0b2] Can't add/edit/delete IP ranges through UI  (LP: #1571672)
-    - [UI/Backend 2.0b2] Can't delete a rack controller from the Rack
-      Details Page  (LP: #1570990)
-    - [UI 2.0b3] interface addresses on rack controller details page
-      not updated automatically  (LP: #1576267)
-    - [UI 2.0b4] Actions list is unordered  (LP: #1577386)
-    - [UI 2.0b4] I can 'add special filesystem' when the machine is
-      deployed  (LP: #1580827)
-    - [1.9] wrong subnet in DHCP answer when multiple networks are
-      present  (LP: #1521618)
-    - [2.0] include maas resetMachine() API primitive  (LP: #1536346)
-    - [2.0] Re-commissioning doesn't detect storage changes (LP: #1575567)
-    - [2.0] Expose custom network in non ubuntu deployments (LP: #1570002)
-    - [2.0a4] Reserved IP ranges should be allowed to be created by
-      standard users  (LP: #1580260)
-    - [2.0b2] 6 Core system is listed as having a single CPU  (LP: #1542353)
-    - [2.0b2] Cannot delete a rack controller that was previously a
-      'machine' (LP: #1570995)
-    - [2.0b3] IP Ranges section on the subnet page should be shown
-      even if no ranges  (LP: #1576758)
-    - [2.0b3] Tag changes depend on rack / cluster connection  (LP: #1372544)
-    - [2.0b4] Rack Controller fail to update commissioning info?  (LP: #1577953)
-    - [2.0b4] Rack Controller mark-broken / mark-fixed  (LP: #1577954)
-    - [2.0b4] Registering external rack controller tracebacks  (LP: #1577970)
-    - [2.0b4] RackControllerService flooding log with:
-      'RegionAdvertisingService' object has no attribute 'processId'  (LP: #1578800)
-    - [2.0b4] set_initial_networking_configuration shouldn't raise
-      ValidationError  (LP: #1580405)
-    - [2.0b4] Disks less than 4MB in size cause a traceback on the
-      MAAS server  (LP: #1580280)
-    - [2.0b4] Rack Controller details page shows "never" under last
-      image sync  (LP: #1577974)
-    - [2.0b4] Machines successfully commission but don't get marked
-      'Ready'  (LP: #1580285)
-    - [2.0b4] Region RPC losing connection and raising exception (LP: #1581654)
-    - [2.0b4] unregisterConnection() missing 1 required positional
-      argument: 'host'  (LP: #1580771)
-  * debian/maas-dhcp.posinst: Pipe error messages correctly to not show
-    messages when disabling isc-dhcp-server init scripts. (LP: #1570911)
-
- -- Andres Rodriguez <[e-mail]>  Fri, 06 May 2016 09:56:40 -0500
-
-maas (2.0.0~beta4+bzr4985-0ubuntu1) xenial; urgency=medium
-
-  * New upstream release, 2.0.0 beta 4 bzr4985:
-    - Disk erasing with Xenial results it abnormal poweroff (LP: #1527634)
-    - UI Nodes page shows 'ascii' codec can't decode byte (LP: #1555864)
-    - When power_type changed to manual "power_state" was not set to "unknown" (LP: #1574003)
-    - MAAS Rack Controller doesn't log when it is importing images. (LP: #1571007)
-    - rackd fails to register vlan interfaces with "vlan" naming scheme (LP: #1575945)
-    - Traceback deleting fabric (LP: #1573492)
-    - adding files with paths in the filename confuses maas (LP: #1566108)
-    - MAAS does not add node to DNS Domain (LP: #1571621)
-    - tag only supports 'nodes' and and not 'machines' or 'controller's (LP: #1573644)
-    - enlistment fails: /tmp/sh.UZ7qJT/bin/maas-enlist: archdetect: not found (LP: #1573264)
-    - creating a dnsresource-record at the root of a zone should allow fqdn= (LP: #1562919)
-    - In the domain details pages, sometimes names have links to nodes when they should not (LP: #1573690)
-    - Can't power on/off Rack Controller (LP: #1576854)
-    - ipranges create raises incorrect error for missing type (LP: #1573660)
-    - fabric and space pages fail to update automatically (LP: #1557597)
-    - Subnet page doesn't show which machine or device owns an IP address (LP: #1567150)
-    - MAAS Controller listing page doesn't indicate whne a rack is downloading images (LP: #1571680)
-    - Deleting user in UI leads to 500 (LP: #1573219)
-    - maas enlistment of power8 found ipmi 1.5 should do ipmi 2.0 (LP: #1556219)
-  * debian/extras/20-maas.conf: Better organize rsyslog logs.
-
- -- Andres Rodriguez <[e-mail]>  Sat, 30 Apr 2016 18:40:26 -0400
-
-maas (2.0.0~beta3+bzr4941-0ubuntu1) xenial; urgency=medium
-
-  * New upstream release, 2.0.0 beta 3 bzr4941 (Standing FFe LP: #1553261)
-  * Remove some leftover references to Cluster.
-  * Run debconf-updatepo.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 15 Apr 2016 22:27:56 -0400
-
-maas (2.0.0~beta2+bzr4920-0ubuntu2) xenial; urgency=medium
-
-  * debian/control: Add missing dep on python3-httplib2
-
- -- Andres Rodriguez <[e-mail]>  Fri, 15 Apr 2016 22:23:55 -0400
-
-maas (2.0.0~beta2+bzr4920-0ubuntu1) xenial; urgency=medium
-
-  * New upstream release, 2.0.0 beta 2 bzr4920 (Standing FFe LP: #1553261)
-  * Only create the squid cache if we have a configuration file.
-    LP: #1568847
-  * Re-add shared debconf templates.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 07 Apr 2016 18:22:00 -0400
-
-maas (2.0.0~beta1+bzr4873-0ubuntu2) xenial; urgency=medium
-
-  * Add maas-region-udeb and maas-rack-udeb to be used as part of the
-    Ubuntu Server Installer (LP: #1561954)
-    - ensure maas-rack-controller and maas-region-controller can be fully
-      preseeded.
-
- -- Andres Rodriguez <[e-mail]>  Tue, 05 Apr 2016 17:02:32 -0400
-
-maas (2.0.0~beta1+bzr4873-0ubuntu1) xenial; urgency=medium
-
-  * New upstream release, 2.0.0 beta 1 bzr4873 (Standing FFe LP: #1553261)
-    - DHCP Snippets WebUI.
-    - Ensure proxy configuration ACL's subnets MAAS knows about.
-    - DNS High Availability.
-  * debian/control: Move 'maascli' package install to
-    python3-maas-client (LP: #1563859)
-  * Improve way on how upgrades ensures correct permissions
-    and ownership (LP: #1563799 , LP: #1563779)
-  * Improve the way how removals clean the system (LP: #1563337)
-  * Reflect new names and website for systemd units (LP: #1563807)
-  * maas-proxy now uses a custom-built config, instead of a boilerplate.
-    LP: #1379567
-
- -- Andres Rodriguez <[e-mail]>  Mon, 28 Mar 2016 16:47:58 -0400
-
-maas (2.0.0~alpha4+bzr4843-0ubuntu1) xenial; urgency=medium
-
-  * New upstream release, 2.0.0 alpha 4 bzr4843 (Standing FFe LP: #1553261)
-    - DHCP Snippets backend and API.
-    - Rack controller WebUI Served VLANs & Service Tracking
-    - Rsyslog during enlistment/commissioning.
-  * Ensure /etc/maas/templates/power gets removed on upgrade
-  * debian/control: Update homepage and package descriptions.
-    (LP: #1562036, LP: #1562034, LP: #1562062)
-  * Rename maas-reigon-controller-min to maas-region-api (LP: #1562069)
-
- -- Andres Rodriguez <[e-mail]>  Wed, 23 Mar 2016 12:27:27 -0400
-
-maas (2.0.0~alpha3+bzr4810-0ubuntu1) xenial; urgency=medium
-
-  * New upstream release, 2.0.0 bzr 4810 (Standing FFe LP: #1553261)
-    - New Networks WebUI
-      + Add Fabrics and Spaces details page.
-      + Actions to Add/Remove Fabrics, VLANs, Spaces, Subnets.
-    - Storage WebUI
-      + Mount options
-      + Swap Partitions
-    - WebUI to change a Machine's domain.
-    - Rack Controller details page now shows 'Server VLANs'
-    - Add maas-rack support-dump command.
-    - Fixes:
-      + python3-maas-client API 2.0 no loger use op but MAASClient.post
-        requires it (LP: #1555393)
-      + Fail to commission when Fabric on Machine Interface doesn't match
-        Rack Controller Fabric. (LP: #1554566)
-      + TFTP back-end crashes (LP: #1553848)
-      + Can't deploy a node, no interfaces on rack controller (LP: #1554999)
-  * Update dhcpd permissions to conform with most recent paranoia described
-    on LP: 1543794, so capability dac_override is not granted.
-  * Update versioned depend on isc-dhcp-server
-
- -- Andres Rodriguez <[e-mail]>  Mon, 14 Mar 2016 18:34:53 -0400
-
-maas (2.0.0~alpha2+bzr4776-0ubuntu1) xenial; urgency=medium
-
-  * New usptream release, 2.0.0 bzr 4776 (LP: #1553261).
-  * maas-dns Depends: bind9 >= 1:9.10.3.dfsg.P2-5 for better system time.
-    LP: #1553176.
-  * debian/extras/maas-{region,rack}: Replace maas-region-admin
-    and maas-provision, respectively (LP: #1553791)
-  * debian/maas-region-controller.postrm: Correctly handle removal by
-    dbconfig-common. (LP: #1553648)
-  * debian/extras/99-maas-region-sudoers: Allow running systemctl for
-    bind9 and maas-proxy to support service tracking. (LP: #1555308)
-
- -- Andres Rodriguez <[e-mail]>  Mon, 01 Feb 2016 18:18:52 +0100
-
-maas (2.0.0~alpha1+bzr4736-0ubuntu1) xenial; urgency=medium
-
-  * New usptream release, 2.0.0 bzr 4736 (LP: #1553261):
-    - Deprecate Cluster Controllers in favor of Rack Controllers.
-    - Deprecate API 1.0 in favor if API 2.0.
-    - DHCP & Rack Controller High Availability.
-    - Networking - IP Ranges.
-    - Networking - DNS.
-    - BMC Model.
-  * Rename maas-cluster* to maas-rack* and handle the upgrade path.
-  * Fix installation of init scripts and daemon systemd units.
-  * Allow 'dhcpd' to access /usr/sbin/maas-provision via
-    sudoers file (LP: #1552775)
-  * debian/extras/maas: Replace shell wrapper with python. (LP: #1553605)
-  * debian/control: Depends on iproute2 instead. (LP: #1553647)
-
- -- Andres Rodriguez <[e-mail]>  Mon, 01 Feb 2016 18:18:52 +0100
-
-maas (1.10.0+bzr4572-0ubuntu2) xenial; urgency=medium
-
-  * debian/maas-region-controller.config: Ensure we truly preseed db
-    setting so we always use localhost and it never asks the user.
-  * debian/control: Suggests on python3-pyvmomi
-
- -- Andres Rodriguez <[e-mail]>  Mon, 01 Feb 2016 17:04:27 +0100
-
-maas (1.10.0+bzr4572-0ubuntu1) xenial; urgency=medium
-
-  * New upstram release, 1.10.0 bzr 4572:
-    - Support python3, drop support for python2.
-    - Support django 1.8+.
-  * debian/control:
-    - Remove all Upstart related services.
-    - Remove python-django16 dependency.
-    - Add python-petname dependency.
-    - Change dependency python-django-piston to python-django-piston3.
-    - Depends on dbconfig-pgsql instead of dbconfig-common.
-  * debian/maas-region-controller.config:
-    - Preseed dbconfig common to not ask for PG server to use.
-  * debian/maas-region-controller-min.maas-regiond-worker@.service: Don't
-    depend on postgresql.service anymore, as it would prevent regiond
-    to run on machines with a remote PostgreSQL.
-  * debian/rules: Refactor installation of init scripts so that they are
-    correctly handled, and maas-regiond is not started on install.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 13 Nov 2015 13:13:42 +0000
-
-maas (1.9.0~rc1+bzr4496-0ubuntu1) wily; urgency=medium
-
-  * New upstream release, 1.9.0 rc1, bzr4496
-    - MAAS uses wrong IP for DNS record (creates against the
-      bond). (LP: #LP: #1515498)
-    - Local archive ignored for deployment. Works for commissioning
-      and enlistment. (LP: #1515671)
-    - Fix handling of multiple StaticIPAddress rows with empty IP
-      addresses. (LP: #1513485)
-    - Lease parser failure - doesn't update IP on the PXE
-      NIC. (LP: #1513485)
-    - Cannot claim sticky IP address for device with
-      parent. (LP: #1514486)
-    - Cluster downloads boot-images from managed network (pxe) instead
-      of network used to connect to Region. (LP: #1514883)
-    - Updating/modifying/assigning vlans, spaces, fabrics, subnets
-      doesn't allow specifying names and lock to ID's. (LP: #1510917)
-    - MAAS should prevent deploying nodes with PXE interface
-      'unconfigured'. (LP: #1513095)
-    - MTU should be a set on the VLAN, and able to override on the
-      interface. (LP: #1508056)
-    - Internal Server Error when creating/editing cluster interface
-      when the Cluster is disconnected. (LP: #1439476)
-    - Non-interactive way to change password. (LP: #1510224)
-    - When a bond is created all IP address associated with the bond
-      members should be removed. (LP: #1513111)
-    - MAAS does not provide a dump of the config it passes to curtin for
-      networking and storage. (LP: #1487135)
-    - MAAS should not offer EXT3, rather VFAT, EXT2, EXT4. (LP: #1512959)
-    - Network constraints for juju. (LP: #1505031)
-    - Creating a partition or a Volume Group on the whole disk leaves
-      free space. (LP: #1509535)
-    - Should not allow partitions to be created on bcache
-      device. (LP: #1511493)
-    - Storage section should only be editable when Ready or
-      Allocated. (LP: #1503475)
-    - maasserver.api.tests.test_fannetworks.TestFanNetworksAPI.test_read
-      fails randomly. (LP: #1512832)
-    - creating a logical volume on a partition that is too small almost
-      works, resulting in strange error messages. (LP: #1508754)
-    - [UI] Keep selected nodes selected after action. (LP: #1503925)
-    - [UI] Refresh UI cache after an upgrade to avoid seeing
-      garbage. (LP: #1515380)
-    - [UI] Boot disk is not lighted nor can be changed. (LP: #1510106)
-    - [UI] Can't remove / delete a partition with a filesystem under
-      'Available disks and partitions'. (LP: #1510118)
-    - [UI] Creating a partition should allow to select filesystem and
-      mountpoint. (LP: #1510153)
-    - [UI] When selecting a device, ensure padding between buttons is
-      20px. (LP: #1510468)
-    - [UI] Misaligned mount point column on used disks table. (LP: #1510455)
-    - [UI] Align the individual storage actions with the name field,
-      rather than the tickbox. (LP: #1510469)
-    - [UI] can't add physical interface. (LP: #1503479)
-    - [UI] Containers (lxc, kvm) data missing on node details. (LP: #1503474)
-    - [UI] Unable to unmount a filesystem in the UI. (LP: #1513271)
-    - [UI] Animation missing on show members and select node. (LP: #1503536)
-    - [UI] Add tooltips to icons. (LP: #1510482)
-    - [UI] Add tooltips to inactive buttons. (LP: #1510486)
-
- -- Andres Rodriguez <[e-mail]>  Thu, 05 Nov 2015 08:29:06 -0500
-
-maas (1.9.0~beta2+bzr4456-0ubuntu1) wily; urgency=medium
-
-  * New upstream release, 1.9.0 beta2, bzr4456:
-    - New capabilities for subnets, vlan, spaces and
-      fabrics. (LP: #LP: #1511257)
-    - Upgrade left a PXE NIC"s on nodes without a subnet associated
-      causing deploy issues. (LP: #LP: #1509077)
-    - DNS record doesn't get created against the PXE
-      interface (LP: #1512109)
-    - bcache cache_mode setting not configured on
-      servers (LP: #1510334)
-    - Administrators unable to delete users using the API (LP: #1510210)
-    - Can create a VolumeGroup (vg0) without having created
-      a partition on the boot disk (LP: #1509536)
-    - set-boot-disk yields in a machine not being able to
-      deploy (LP: #1501400)
-    - Deploying Other OS' (CentOS, Windows) should not configure
-      custom storage (LP: #1504956)
-    - Add RAID 10 support (LP: #1509164)
-    - MAAS should download grub from grub-efi-amd64-signed package
-      instead of the archive path (LP: #1511437)
-    - Fails to deploy with UEFI (LP: #1510120)
-    - previous owner of node can use oauth creds to retrieve current
-      owner's user-data (LP: #1507586)
-    - IP range validation for too small ranges (LP: #1507630)
-    - test__calls_update_host_maps_for_next_ip_managed_subnet
-      can fail randomly (LP: #1507630)
-    - No way to disable maas-proxy (LP: #1511071)
-    - [UI] HWE naming needs to be clearer (LP: #1505034))
-    - [UI] Angular $digest loop issue on node details page (LP: #1509476)
-    - [UI] New nodes interfaces doesn't show which interface is the
-      PXE interface (LP: #1509473)
-    - [UI] When partitioning, there should be 20px padding between
-      the sizing fields (LP: #1510471)
-    - [UI] On the available table, add model and serial to the
-      name column (LP: #1510467)
-    - [UI] On the available table, change “available space” to
-      “size” for consistency (LP: #1510466)
-    - [UI] when formatting/mounting, the button says “Format & Mount”
-      this should just be “Mount” (LP: #1510472)
-    - [UI] Tickbox on create bond networking (LP: #1503533)
-    - [UI] On the file system table, change name to “File system”
-      (lower case S) (LP: #1510447)
-    - [UI] When creating bcache and raid, remove the empty column
-      between the config fields. (LP: #1510474)
-    - [UI] On the available table, make sure all buttons are
-      lowercase (LP: #1510488)
-    - [UI] Subnets filter doesn't show network, it shows name
-      instead (LP: #1511174)
-    - [UI] can't edit / add storage tags (LP: #1509417)
-    - [UI] Hover state for networking doesn't work (LP: #1510891)
-    - [UI] change "edit tag" link to icon storage (LP: #1510458)
-    - [UI] Can no longer see the IP address PXE interface gets
-      on commissioning (LP: #1510629)
-  * debian/control: Bump Dep on python-curtin to > 0.1.0~bzr275.
-
- -- Andres Rodriguez <[e-mail]>  Wed, 28 Oct 2015 21:20:39 -0400
-
-maas (1.9.0~beta1+bzr4417-0ubuntu1) wily; urgency=medium
-
-  * New upstream release, 1.9.0 beta1, bzr4415:
-    - Various UI fixes and improvements
-    - Add ability to create LVM.
-    - Add ability to create RAID.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 22 Oct 2015 14:05:50 -0400
-
-maas (1.9.0~alpha5+bzr4398-0ubuntu1) wily; urgency=medium
-
-  * New upstream release, 1.9.0 Alpha 5, bzr4398:
-    - Various UI fixes and improvements.
-    - Add ability to create partitions in the UI.
-    - Add ability to create Bcache (create cache sets and backing devices).
-    - Check and warns users about missing power driver tools (LP: #1381000).
-    - Add fabric class_type.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 15 Oct 2015 21:22:44 -0700
-
-maas (1.9.0~alpha4+bzr4371-0ubuntu1) wily; urgency=medium
-
-  * New upstream release, 1.9.0 Alpha 4, bzr4371:
-    - Various UI fixes and improvements.
-    - Various concurrency issues fixed.
-    - Do not create MBR bigger than 2 TiB, otherwise MAAS will fail to
-      deploy on disks larger than 2 TiB.
-    - Fix broken migration due to missing import (LP: #1504340)
-
- -- Andres Rodriguez <[e-mail]>  Wed, 07 Oct 2015 13:02:53 -0700
-
-maas (1.9.0~alpha3+bzr4355-0ubuntu1) wily; urgency=medium
-
-  * New upstream release, 1.9.0 Alpha 3, bzr4355
-    - Node network configuration (VLAN, aliases, bond's).
-    - Subnets page.
-    - Mount, Unmount filesystems. Formatting, unformatting.
-    - Create partitions.
-    - Checks for missing power drivers tool and warns the users.
-  * debian/control: Recommends on apache2.
-
- -- Andres Rodriguez <[e-mail]>  Tue, 29 Sep 2015 12:53:36 -0400
-
-maas (1.9.0~alpha2+bzr4322-0ubuntu1) wily; urgency=medium
-
-  * New upstream release, 1.9.0 Alpha 2, bzr4322:
-    - Native support for Network Configuration (IP assignment, VLANs, bonds)
-    - First class support for CentOS
-    - Status updates from curtin/cloud-init
-    - Support for fabrics, spaces, subnets and fans.
-    - Support for commissioning actions.
-
- -- Andres Rodriguez <[e-mail]>  Tue, 01 Sep 2015 19:04:39 -0400
-
-maas (1.9.0~alpha1+bzr4221-0ubuntu1) wily; urgency=medium
-
-  * New upstream release, 1.9.0 Alpha 1, bzr4218:
-    - Native storage support (Flat, LVM, bcache, RAID).
-    - New config files (regiond.conf, clusterd.conf)
-    - New Python Power Drivers.
-    - Better support for HWE Kernels.
-
-  [ Scott Moser ]
-  * maas-proxy: sync apt specific squid config with squid-deb-proxy
-    (LP: #1474417)
-
-  [ Raphaël Badin ]
-  * Enable proxy_wstunnel module.
-  * Drop dependency on python-iscpy: the code has been integrated into
-    MAAS. (LP: #1413388).
-
-  [ Gavin Panella ]
-  * Use new local configuration support for the cluster.
-
-  [ Andres Rodriguez ]
-  * Refactor maas-dns upgrade code so it doesn't break local DNS config
-    and it gets migrated (LP: #1413388)
-    - debian/maas-region-controller.postinst: Ensure DNS config
-      migration is always run.
-  * debian/control: Make maas-dns a Dependy of maas-region-controller.
-  * Update the location of dhcpd.conf and dhcpd6.conf to be /var/lib/maas/
-    and handle upgrades. (LP: #1482857)
-  * Move /etc/maas/maas-proxy.conf to /usr/share/maas/maas-proxy.conf as
-    this is not a config we want users to modify. (LP: #1482859)
-  * Move /etc/maas/maas-http.conf to /usr/share/maas/maas-http.conf as
-    this is not a config we want users to modify. (LP: #1482858)
-  * debian/control:
-    - Add missing dependency on python-curtin.
-    - Drop python-lockfile as it is no longer used.
-    - Depend on python-curtin >= 0.1.0~bzr247.
-
- -- Andres Rodriguez <[e-mail]>  Fri, 12 Jun 2015 14:16:47 -0400
-
-maas (1.8.0+bzr4001-0ubuntu1) trusty; urgency=medium
-
-  * New upstream release, 1.8.0.
-
- -- Andres Rodriguez <[e-mail]>  Tue, 09 Jun 2015 20:57:42 -0400
-
-maas (1.8.0~rc3+bzr4000-0ubuntu1) trusty; urgency=medium
-
-  * New upstream release, 1.8.0 RC3 bzr4000.
-
-  [ Raphaël Badin ]
-  * Remove unused dependencies: python-amqp and python-txamqp.
-
- -- Andres Rodriguez <[e-mail]>  Thu, 04 Jun 2015 16:32:02 -0400
-
-maas (1.8.0~rc2+bzr3989-0ubuntu1) trusty; urgency=medium
-
-  * New upstream release, 1.8.0 RC2 bzr3983.
-
- -- Andres Rodriguez <[e-mail]>  Tue, 02 Jun 2015 09:27:54 -0400
-
-maas (1.8.0~rc1+bzr3972-0ubuntu1) trusty; urgency=medium
-
-  * New upstream release, 1.8.0 RC1 bzr3972.
-  * debian/copyright: Add copyright headers for ng-tags-input.js.