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

Proposed by Alberto Donato on 2020-02-11
Status: Needs review
Proposed branch: ~ack/ubuntu/+source/maas:transitional-snap
Merge into: ubuntu/+source/maas:ubuntu/devel
Diff against target: 584052 lines (+219/-11890)
12 files modified
debian/changelog (+3/-2784)
debian/compat (+1/-1)
debian/control (+47/-295)
debian/copyright (+0/-38)
debian/maas.install (+1/-0)
debian/maas.lintian-overrides (+1/-0)
debian/maas.preinst (+114/-0)
debian/maas.templates (+32/-0)
debian/rules (+2/-49)
debian/source/format (+1/-1)
dev/null (+0/-8722)
maas (+17/-0)
Reviewer Review Type Date Requested Status
Julian Andres Klode (community) 2020-02-11 Approve on 2020-02-18
Review via email: mp+378890@code.launchpad.net

Commit message

Transitional package to install and migrate to snap

Description of the change

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.

To post a comment you must log in.
Julian Andres Klode (juliank) wrote :

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) wrote :

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) wrote :

@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) wrote :

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) wrote :

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

Julian Andres Klode (juliank) wrote :

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) wrote :

> 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) wrote :

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) wrote :

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

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.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1diff --git a/.babelrc b/.babelrc
2deleted file mode 100644
3index 5d9a7c9..0000000
4--- a/.babelrc
5+++ /dev/null
6@@ -1,7 +0,0 @@
7-{
8- "presets": ["@babel/preset-env"],
9- "plugins": [
10- ["angularjs-annotate", { "explicitOnly" : true }],
11- "@babel/plugin-proposal-class-properties"
12- ]
13-}
14diff --git a/.coveragerc b/.coveragerc
15deleted file mode 100644
16index f00deba..0000000
17--- a/.coveragerc
18+++ /dev/null
19@@ -1,21 +0,0 @@
20-[run]
21-branch = True
22-source = src
23-omit =
24- */testing.py
25- */testing/*
26- */tests/*
27-
28-[report]
29-omit =
30- src/*/migrations/*
31- src/maastesting/*
32-exclude_lines =
33- # Have to re-enable the standard pragma
34- pragma: no cover
35- # Don't complain if tests don't hit defensive assertion code:
36- raise NotImplementedError
37-
38-[html]
39-directory = coverage
40-title = Coverage for MAAS
41diff --git a/.ctags b/.ctags
42deleted file mode 100644
43index 0eb9382..0000000
44--- a/.ctags
45+++ /dev/null
46@@ -1,4 +0,0 @@
47---python-kinds=-iv
48---exclude=*.js
49---extra=+f
50---links=yes
51diff --git a/.eslintrc.js b/.eslintrc.js
52deleted file mode 100644
53index bded01a..0000000
54--- a/.eslintrc.js
55+++ /dev/null
56@@ -1,24 +0,0 @@
57-module.exports = {
58- "env": {
59- "browser": true,
60- "es6": true,
61- "jasmine": true
62- },
63- "extends": ["angular", "eslint:recommended"],
64- "globals": {
65- "__dirname": false,
66- "angular": false,
67- "Atomics": "readonly",
68- "inject": false,
69- "setTimeout": false,
70- "SharedArrayBuffer": "readonly"
71- },
72- "parserOptions": {
73- "ecmaVersion": 2018,
74- "sourceType": "module"
75- },
76- "rules": {
77- "angular/di": [2, "function", { "matchNames": true }],
78- "no-unused-vars": [2, { "args": "none" }]
79- }
80-};
81diff --git a/.flake8 b/.flake8
82deleted file mode 100644
83index 247c850..0000000
84--- a/.flake8
85+++ /dev/null
86@@ -1,2 +0,0 @@
87-[flake8]
88-ignore = E123,E305,E402,E731
89diff --git a/CHANGELOG b/CHANGELOG
90deleted file mode 120000
91index 6f0024c..0000000
92--- a/CHANGELOG
93+++ /dev/null
94@@ -1 +0,0 @@
95-docs/changelog.rst
96\ No newline at end of file
97diff --git a/HACKING.rst b/HACKING.rst
98deleted file mode 100644
99index 8f1c0b9..0000000
100--- a/HACKING.rst
101+++ /dev/null
102@@ -1,707 +0,0 @@
103-.. -*- mode: rst -*-
104-
105-************
106-Hacking MAAS
107-************
108-
109-
110-Coding style
111-============
112-
113-MAAS follows the `Launchpad Python Style Guide`_, except where it gets
114-Launchpad specific, and where it talks about `method naming`_. MAAS
115-instead adopts `PEP-8`_ naming in all cases, so method names should
116-usually use the ``lowercase_with_underscores`` form.
117-
118-.. _Launchpad Python Style Guide:
119- https://dev.launchpad.net/PythonStyleGuide
120-
121-.. _method naming:
122- https://dev.launchpad.net/PythonStyleGuide#Naming
123-
124-.. _PEP-8:
125- http://www.python.org/dev/peps/pep-0008/
126-
127-
128-Prerequisites
129-=============
130-
131-Container
132-^^^^^^^^^
133-
134-There's a configure-lxd-profile script in utilities, that will set
135-up a LXD profile that is configured properly.
136-
137-
138-Dependencies
139-^^^^^^^^^^^^
140-
141-You can grab MAAS's code manually from Launchpad but Git_ makes it
142-easy to fetch the last version of the code. First of all, install
143-Git::
144-
145- $ sudo apt install git
146-
147-.. _Git: https://git-scm.com/
148-
149-Then go into the directory where you want the code to reside and run::
150-
151- $ git clone https://git.launchpad.net/maas && cd maas
152-
153-MAAS depends on Postgres, isc-dhcp, bind9, and many other packages. To install
154-everything that's needed for running and developing MAAS, run::
155-
156- $ make install-dependencies
157-
158-Careful: this will ``apt-get install`` many packages on your system,
159-via ``sudo``. It may prompt you for your password.
160-
161-This will install ``bind9``. As a result you will have an extra daemon
162-running. If you are a developer and don't intend to run BIND locally,
163-you can disable the daemon by inserting ``exit 1`` at the top of
164-``/etc/default/bind9``. The package still needs to be installed for
165-tests though.
166-
167-Python development dependencies are pulled automatically from
168-`PyPI`_ when ``buildout`` runs. (``buildout`` will be automatically
169-configured to create a cache, in order to improve build times.
170-See ``utilities/configure-buildout``.)
171-
172-Javascript development dependencies are pulled automatically from
173-`npm`_ when ``make`` runs. (``npm`` will be automatically
174-configured to use a cache, in order to improve build times.)
175-
176-.. _PyPI:
177- http://pypi.python.org/
178-.. _npm:
179- https://www.npmjs.com/
180-
181-
182-Git Workflow
183-^^^^^^^^^^^^
184-
185-You will want to adjust your git repository of lp:maas some before you start
186-making changes to the code. This includes setting up your own copy of
187-the repository and making your changes in branches.
188-
189-First you will want to rename the origin remote to upstream and create a new
190-origin in your namespace.
191-
192- $ git remote rename origin upstream
193- $ git remote add origin git+ssh://{launchpad-id}@git.launchpad.net/~{launchpad-id}/maas
194-
195-Now you can make a branch and start making changes.
196-
197- $ git checkout -b new-branch
198-
199-Once you have made the changes you want, you should commit and push the branch
200-to your origin.
201-
202- $ git commit -m "My change" -a
203- $ git push origin new-branch
204-
205-Now you can view that branch on Launchpad and propose it to the maas
206-repository.
207-
208-Once the branch has been merged and your done with it you can update your
209-git repository to remove the branch.
210-
211- $ git fetch upstream
212- $ git checkout master
213- $ git merge upstream/master
214- $ git branch -d new-branch
215-
216-
217-Optional
218-^^^^^^^^
219-
220-The PyCharm_ IDE is a useful tool when developing MAAS. The MAAS team does not
221-endorse any particular IDE, but ``.idea`` `project files are included with
222-MAAS`_, so PyCharm_ is an easy choice.
223-
224-.. _PyCharm:
225- https://www.jetbrains.com/pycharm/
226-
227-.. _project files are included with MAAS:
228- https://intellij-support.jetbrains.com/entries/23393067-How-to-manage-projects-under-Version-Control-Systems
229-
230-Running tests
231-=============
232-
233-To run the whole suite::
234-
235- $ make test
236-
237-To run tests at a lower level of granularity::
238-
239- $ ./bin/test.region src/maasserver/tests/test_api.py
240- $ ./bin/test.region src/maasserver/tests/test_api.py:AnonymousEnlistmentAPITest
241-
242-The test runner is `nose`_, so you can pass in options like
243-``--with-coverage`` and ``--nocapture`` (short option: ``-s``). The
244-latter is essential when using ``pdb`` so that stdout is not
245-adulterated.
246-
247-.. _nose: http://readthedocs.org/docs/nose/en/latest/
248-
249-.. Note::
250-
251- When running ``make test`` through ssh from a machine with locales
252- that are not set up on the machine that runs the tests, some tests
253- will fail with a ``MismatchError`` and an "unsupported locale
254- setting" message. Running ``locale-gen`` for the missing locales or
255- changing your locales on your workstation to ones present on the
256- server will solve the issue.
257-
258-
259-Emitting subunit
260-^^^^^^^^^^^^^^^^
261-
262-Pass the ``--with-subunit`` flag to any of the test runners (e.g.
263-``bin/test.rack``) to produce a `subunit`_ stream of test results. This
264-may be useful for parallelising test runs, or to allow later analysis of
265-a test run. The optional ``--subunit-fd`` flag can be used to direct the
266-results to a different file descriptor, to ensure a clean stream.
267-
268-.. _subunit: https://launchpad.net/subunit/
269-
270-
271-Running JavaScript tests
272-^^^^^^^^^^^^^^^^^^^^^^^^
273-
274-The JavaScript tests are run using Karma_. Chromium and PhantomJS are the
275-default browser but any browser supported by Karma can be used to run the
276-tests.::
277-
278- $ make test-js
279-
280-If you want to run the JavaScript tests in debug mode so you can inspect the
281-code inside of a running browser you can launch Karma_ manually.::
282-
283- $ ./bin/karma start src/maastesting/karma.conf.js --browsers Chrome --no-single-run
284-
285-.. _Karma: http://karma-runner.github.io/
286-
287-
288-Frontend development
289-====================
290-
291-For faster development, Webpack watch mode can be run with::
292-
293- $ make watch-javascript
294-
295-JavaScript debugging
296-^^^^^^^^^^^^^^^^^^^^
297-
298-Angularjs debugInfo, which provides hooks for browser debugging tools
299-like Batarang, is disabled by default. To re-enable debugInfo,
300-run ``angular.reloadWithDebugInfo();`` in the browser console.
301-
302-See https://docs.angularjs.org/guide/production#disabling-debug-data for details.
303-
304-
305-JavaScript linting and formatting
306-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
307-
308-JSLint can be run with::
309-
310- $ make lint-js
311-
312-This will also run `prettier-check` which will notify you
313-if there are formatting issues.
314-
315-Prettier can be run in write mode to correct formatting with::
316-
317- $ make format
318-
319-ESLint is also available (the intention is to eventually replace JSLint),
320-and can be run with::
321-
322- $ ./bin/yarn lint
323-
324-
325-Production MAAS server debugging
326-================================
327-
328-When MAAS is installed from packaging it can help to enable debugging features
329-to triage issues.
330-
331-Log all API and UI exceptions
332-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
333-
334-By default MAAS only logs HTTP 500 - INTERNAL_SERVER_ERROR into the
335-regiond.log. To enable logging of all exceptions even exceptions where MAAS
336-will return the correct HTTP status code.::
337-
338- $ sudo sed -i 's/DEBUG = False/DEBUG = True/g' \
339- > /usr/lib/python3/dist-packages/maasserver/djangosettings/settings.py
340- $ sudo service maas-regiond restart
341-
342-Run regiond in foreground
343-^^^^^^^^^^^^^^^^^^^^^^^^^
344-
345-It can help when debugging to run regiond a foreground process so you can
346-interact with the regiond by placing a breakpoint in the code. Once you have
347-placed a breakpoint into the code you want to inspect you can start the regiond
348-process in the foreground.::
349-
350- $ sudo service maas-regiond stop
351- $ sudo -u maas -H \
352- > DJANGO_SETTINGS_MODULE=maasserver.djangosettings.settings \
353- > twistd3 --nodaemon --pidfile= maas-regiond
354-
355-
356-.. Note::
357-
358- By default a MAAS installation runs 4 regiond processes at the same time.
359- This will change it to only run 1 process in the foreground. This should
360- only be used for debugging. Once finished the breakpoint should be removed
361- and maas-regiond service should be started.
362-
363-Run rackd in foreground
364-^^^^^^^^^^^^^^^^^^^^^^^^^
365-
366-It can help when debugging to run rackd a foreground process so you can
367-interact with the rackd by placing a breakpoint in the code. Once you have
368-placed a breakpoint into the code you want to inspect you can start the rackd
369-process in the foreground.::
370-
371- $ sudo service maas-rackd stop
372- $ sudo -u maas -H /usr/bin/authbind --deep /usr/bin/twistd3 --nodaemon --pidfile= maas-rackd
373-
374-
375-Development MAAS server setup
376-=============================
377-
378-Access to the database is configured in
379-``src/maasserver/djangosettings/development.py``.
380-
381-The ``Makefile`` or the test suite sets up a development database
382-cluster inside your branch. It lives in the ``db`` directory, which
383-gets created on demand. You'll want to shut it down before deleting a
384-branch; see below.
385-
386-First, set up the project. This fetches all the required dependencies
387-and sets up some useful commands in ``bin/``::
388-
389- $ make
390-
391-Create the database cluster and initialise the development database::
392-
393- $ make syncdb
394-
395-Optionally, if all you want to do is to take a look around the UI and
396-API, without interacting with real machines or VMs, populate your
397-database with the sample data::
398-
399- $ make sampledata
400-
401-You can login as a simple user using the test account (username: 'test',
402-password: 'test') or the admin account (username: 'admin', password: 'test').
403-
404-If you want to interact with real machines or VMs, it's better to use
405-the snap. Instead of building a real snap, though, you can use
406-'snapcraft prime' to create the prime directory. That has all the
407-contents of the snap, but it's in a plain directory insted of in a
408-squashfs image. Using a directory is better for testing, since you can
409-change the files in there and not rebuild the snap.
410-
411-There's a ``sync-dev-snap`` make target to automate this:
412-
413- $ make sync-dev-snap
414-
415-The ``sync-dev-snap`` target creates a clean copy of your working tree (so
416-that you don't have to run 'make clean' before building the snap) in
417-build/dev-snap and creates the snap directory in build/dev-snap/prime.
418-
419-You can now install the snap:
420-
421- $ sudo snap try --devmode build/dev-snap/prime
422-
423-Note that 'snap try' is used instead of 'snap install'. The maas snap
424-should now be installed:
425-
426- $ snap list
427- Name Version Rev Developer Notes
428- core 16-2.27.5 2774 canonical core
429- maas 2.3.0~alpha3-6225-gaa05ba6-snap x1 devmode,try
430-
431-Next you need to initialize the snap, just like you would normally do:
432-
433- $ sudo maas init
434-
435-And now you're ready to make changes to the code. After you've change
436-some source files and want to test them out, run the ``sync-dev-snap``
437-target again:
438-
439- $ make sync-dev-snap
440-
441-You should now see that you files were synced to the prime directory. If
442-you changed JS and HTML files only, you should see that changes straight
443-away by just reloading the browser. If you changed Python files, you
444-need to restart MAAS:
445-
446- $ sudo service snap.maas.supervisor restart
447-
448-VMs or even real machines can now PXE boot off your development snap.
449-But of course, you need to set up the networking first. If you want to
450-do some simple testing, the easiest is to create a networking in
451-virt-manager that has NAT, but doesn't provide DHCP. If the name of
452-the bridge that got created is `virbr1`, you can expose it to your
453-container as eth1 using the following config:
454-
455- eth1:
456- name: eth1
457- nictype: bridged
458- parent: virbr1
459- type: nic
460-
461-Of course, you also need to configure that eth1 interface. Since MAAS is
462-the one providing DHCP, you need to give it a static address on the
463-network you created. For example::
464-
465- auto eth1
466- iface eth1 inet static
467- address 192.168.100.2
468- netmask 255.255.255.0
469-
470-Note that your LXD host will have the .1 address and will act as a
471-gateway for your VMs.
472-
473-To shut down the database cluster and clean up all other generated files in
474-your branch::
475-
476- $ make clean
477-
478-
479-Downloading PXE boot resources
480-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
481-
482-To use PXE booting, each cluster controller needs to download several
483-files relating to PXE booting. This process is automated, but it does
484-not start by default.
485-
486-First create a superuser and start all MAAS services::
487-
488- $ bin/maas-region createadmin
489- $ make run
490-
491-Substitute your own email. The command will prompt for a choice of password.
492-
493-Next, get the superuser's API key on the `account preferences`_ page in the
494-web UI, and use it to log into MAAS at the command-line::
495-
496- $ bin/maas login dev http://localhost:5240/MAAS/
497-
498-.. _`account preferences`: http://localhost:5240/MAAS/account/prefs/
499-
500-Start downloading PXE boot resources::
501-
502- $ bin/maas dev node-groups import-boot-images
503-
504-This sends jobs to each cluster controller, asking each to download
505-the boot resources they require. This may download dozens or hundreds
506-of megabytes, so it may take a while. To save bandwidth, set an HTTP
507-proxy beforehand::
508-
509- $ bin/maas dev maas set-config name=http_proxy value=http://...
510-
511-
512-Running the built-in TFTP server
513-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
514-
515-You will need to run the built-in TFTP server on the real TFTP port (69) if
516-you want to boot some real hardware. By default, it's set to start up on
517-port 5244 for testing purposes. To make it run on port 69, set the
518-MAAS_TFTP_PORT environment variable before running make run/start::
519-
520- export MAAS_TFTP_PORT=69
521-
522-
523-Then you need install and configure the authbind, so that your user can
524-bind to port 69::
525-
526- * Install the ``authbind``package:
527-
528- $ sudo apt install authbind
529-
530- * Create a file ``/etc/authbind/byport/69`` that is *executable* by the
531- user running MAAS.
532-
533- $ sudo touch /etc/authbind/byport/69
534- $ sudo chown $USER /etc/authbind/byport/69
535- $ sudo chmod u+x /etc/authbind/byport/69
536-
537-Now when starting up the MAAS development webserver, "make run" and "make
538-start" will detect authbind's presence and use it automatically.
539-
540-
541-Running the BIND daemon for real
542-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
543-
544-There's a BIND daemon that is started up as part of the development service
545-but it runs on port 5246 by default. If you want to make it run as a real
546-DNS server on the box then set the MAAS_BIND_PORT environment variable
547-before running make run/start::
548-
549- export MAAS_BIND_PORT=53
550-
551-Then as for TFTP above, create an authbind authorisation::
552-
553- $ sudo touch /etc/authbind/byport/53
554- $ sudo chown $USER /etc/authbind/byport/53
555- $ sudo chmod u+x /etc/authbind/byport/53
556-
557-and run as normal.
558-
559-
560-Running the cluster worker
561-^^^^^^^^^^^^^^^^^^^^^^^^^^
562-
563-The cluster also needs authbind as it needs to bind a socket on UDP port
564-68 for DHCP probing::
565-
566- $ sudo touch /etc/authbind/byport/68
567- $ sudo chown $USER /etc/authbind/byport/68
568- $ sudo chmod u+x /etc/authbind/byport/68
569-
570-If you omit this, nothing else will break, but you will get an error in
571-the cluster log because it can't bind to the port.
572-
573-
574-Configuring DHCP
575-^^^^^^^^^^^^^^^^
576-
577-MAAS requires a properly configured DHCP server so it can boot machines using
578-PXE. MAAS can work with its own instance of the ISC DHCP server, if you
579-install the maas-dhcp package::
580-
581- $ sudo apt install maas-dhcp
582-
583-Note that maas-dhcpd service definition referencese the maas-rackd
584-service, which won't be present if you run a development service. To
585-workaround edit /lib/systemd/system/maas-dhcp.service and comment out
586-this line:
587-
588- BindsTo=maas-rackd.service
589-
590-
591-Non-interactive configuration of RBAC service authentication
592-============================================================
593-
594-For development and automating testing purposes, it's possible to configure
595-maas with the RBAC service in a non-interactive way, with the following::
596-
597- $ sudo MAAS_CANDID_CREDENTIALS=user1:password1 maas configauth --rbac-url http://<url-of-rbac>:5000 --rbac-sevice-name <maas-service-name-in-RBAC>
598-
599-This will automatically handle logging in with Candid, without requiring the
600-user to fill in the authentication form via browser.
601-
602-
603-Development services
604-====================
605-
606-The development environment uses *daemontools* to manage the various
607-services that are required. These are all defined in subdirectories in
608-``services/``.
609-
610-There are familiar service-like commands::
611-
612- $ make start
613- $ make status
614- $ make restart
615- $ make stop
616-
617-The latter is a dependency of ``distclean`` so just running ``make
618-distclean`` when you've finished with your branch is enough to stop
619-everything.
620-
621-Individual services can be manipulated too::
622-
623- $ make services/rackd/@start
624-
625-The ``@<action>`` pattern works for any of the services.
626-
627-There's an additional special action, ``run``::
628-
629- $ make run
630-
631-This starts all services up and tails their log files. When you're
632-done, kill ``tail`` (e.g. Ctrl-c), and all the services will be
633-stopped.
634-
635-However, when used with individual services::
636-
637- $ make services/regiond/@run
638-
639-it does something even cooler. First it shuts down the service, then
640-it restarts it in the foreground so you can see the logs in the
641-console. More importantly, it allows you to use ``pdb``, for example.
642-
643-A note of caution: some of the services have slightly different
644-behaviour when run in the foreground:
645-
646-* regiond (the *webapp* service) will be run with its auto-reloading
647- enabled.
648-
649-There's a convenience target for hacking regiond that starts everything
650-up, but with regiond in the foreground::
651-
652- $ make run+regiond
653-
654-Apparently Django needs a lot of debugging ;)
655-
656-
657-Adding new dependencies
658-=======================
659-
660-Since MAAS is distributed mainly as an Ubuntu package, all runtime
661-dependencies should be packaged, and we should develop with the
662-packaged version if possible. All dependencies, from a package or not,
663-need to be added to ``setup.py`` and ``buildout.cfg``, and the version
664-specified in ``versions.cfg`` (``allowed-picked-version`` is disabled,
665-hence ``buildout`` must be given precise version information).
666-
667-If it is a development-only dependency (i.e. only needed for the test suite, or
668-for developers' convenience), simply running ``buildout`` like this will make
669-the necessary updates to ``versions.cfg``::
670-
671- $ ./bin/buildout -v buildout:allow-picked-versions=true
672-
673-
674-Adding new source files
675-=======================
676-
677-When creating a new source file, a Python module or test for example,
678-always start with the appropriate template from the ``templates``
679-directory.
680-
681-
682-Database information
683-====================
684-
685-MAAS uses Django_ to manage changes to the database schema.
686-
687-.. _Django: https://www.djangoproject.com/
688-
689-Be sure to have a look at `Django's migration documentation`_ before you make
690-any change.
691-
692-.. _Django's migration documentation:
693- https://docs.djangoproject.com/en/1.8/topics/migrations/
694-
695-
696-Changing the schema
697-^^^^^^^^^^^^^^^^^^^
698-
699-Once you've made a model change (i.e. a change to a file in
700-``src/<application>/models/*.py``) you have to run Django's `makemigrations`_
701-command to create a migration file that will be stored in
702-``src/<application>/migrations/builtin/``.
703-
704-Note that if you want to add a new model class you'll need to import it
705-in ``src/<application>/models/__init__.py``
706-
707-.. _makemigrations: https://docs.djangoproject.com/en/1.8/ref/django-admin/#django-admin-makemigrations
708-
709-Generate the migration script with::
710-
711- $ ./bin/maas-region makemigrations --name description_of_the_change maasserver
712-
713-This will generate a migration module named
714-``src/maasserver/migrations/builtin/<auto_number>_description_of_the_change.py``.
715-Don't forget to add that file to the project with::
716-
717- $ git add src/maasserver/migrations/builtin/<auto_number>_description_of_the_change.py
718-
719-To apply that migration, run::
720-
721- $ make syncdb
722-
723-
724-Performing data migration
725-^^^^^^^^^^^^^^^^^^^^^^^^^
726-
727-If you need to perform data migration, very much in the same way, you will need
728-to run Django's `makemigrations`_ command. For instance, if you want to perform
729-changes to the ``maasserver`` application, run::
730-
731- $ ./bin/maas-region makemigrations --empty --name description_of_the_change maasserver
732-
733-This will generate a migration module named
734-``src/maasserver/migrations/builtin/<auto_number>_description_of_the_change.py``.
735-You will need to edit that file and fill the ``operations`` list with the
736-options that need to be performed. Again, don't forget to add that file to the
737-project::
738-
739- $ git add src/maasserver/migrations/builtin/<auto_number>_description_of_the_change.py
740-
741-Once the operations have been added, apply that migration with::
742-
743- $ make syncdb
744-
745-
746-Examining the database manually
747-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
748-
749-If you need to get an interactive ``psql`` prompt, you can use `dbshell`_::
750-
751- $ bin/maas-region dbshell
752-
753-.. _dbshell: https://docs.djangoproject.com/en/dev/ref/django-admin/#dbshell
754-
755-If you need to do the same thing with a version of MAAS you have installed
756-from the package, you can use::
757-
758- $ sudo maas-region dbshell --installed
759-
760-You can use the ``\dt`` command to list the tables in the MAAS database. You
761-can also execute arbitrary SQL. For example:::
762-
763- maasdb=# select system_id, hostname from maasserver_node;
764- system_id | hostname
765- -------------------------------------------+--------------------
766- node-709703ec-c304-11e4-804c-00163e32e5b5 | gross-debt.local
767- node-7069401a-c304-11e4-a64e-00163e32e5b5 | round-attack.local
768- (2 rows)
769-
770-
771-Viewing SQL queries during tests
772-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
773-
774-If you need to view the SQL queries that are performed during a test, the
775-`LogSQL` fixture can be used to output all the queries during the test.::
776-
777- from maasserver.fixture import LogSQL
778- self.useFixture(LogSQL())
779-
780-Sometimes you need to see where in the code that query was performed.::
781-
782- from maasserver.fixture import LogSQL
783- self.useFixture(LogSQL(include_stacktrace=True))
784-
785-
786-Documentation
787-=============
788-
789-Use `reST`_ with the `convention for headings as used in the Python
790-documentation`_.
791-
792-.. _reST: http://sphinx.pocoo.org/rest.html
793-
794-.. _convention for headings as used in the Python documentation:
795- http://sphinx.pocoo.org/rest.html#sections
796-
797-
798-Updating copyright notices
799-^^^^^^^^^^^^^^^^^^^^^^^^^^
800-
801-Use the `Bazaar Copyright Updater`_::
802-
803- bzr branch lp:bzr-update-copyright ~/.bazaar/plugins/update_copyright
804- make copyright
805-
806-Then commit any changes.
807-
808-.. _Bazaar Copyright Updater:
809- https://launchpad.net/bzr-update-copyright
810diff --git a/INSTALL.txt b/INSTALL.txt
811deleted file mode 100644
812index 86ac315..0000000
813--- a/INSTALL.txt
814+++ /dev/null
815@@ -1,418 +0,0 @@
816-.. -*- mode: rst -*-
817-
818-
819-Installing MAAS
820-===============
821-
822-There are two main ways to install MAAS:
823-
824- * :ref:`From a package repository. <pkg-install>`
825- * :ref:`As a fresh install from Ubuntu Server install
826- media. <disc-install>`
827- * :ref:`Install MAAS in a LXC Container. <container-install>`
828-
829-
830-MAAS Packages and Repositories
831-------------------------------
832-
833-MAAS Packages
834-^^^^^^^^^^^^^
835-
836-Installing MAAS from packages is straightforward. There are actually
837-several packages that go into making up a working MAAS install, but
838-for convenience, many of these have been gathered into a virtual
839-package called 'maas' which will install the necessary components
840-for a 'seed cloud', that is a single server that will directly
841-control a group of nodes. The main packages are:
842-
843- * ``maas`` - seed cloud setup, which includes both the region
844- controller and the rack controller below.
845- * ``maas-region-controller`` - includes the web UI, API and database.
846- * ``maas-rack-controller`` - controls a group of machines under a
847- rack or multiple racks, including DHCP management.
848- * ``maas-dhcp``/``maas-dns`` - required when managing dhcp/dns.
849- * ``maas-proxy`` - required to provide a MAAS proxy.
850-
851-If you need to separate these services or want to deploy an additional
852-rack controller, you should install the corresponding packages
853-individually (see :ref:`the description of a typical setup <setup>`
854-for more background on how a typical hardware setup might be
855-arranged).
856-
857-There are two suggested additional packages 'maas-dhcp' and
858-'maas-dns'. These set up MAAS-controlled DHCP and DNS services which
859-greatly simplify deployment if you are running a typical setup where
860-the MAAS controller can run the network (Note: These **must** be
861-installed if you later set the options in the web interface to have
862-MAAS manage DHCP/DNS).
863-
864-MAAS Package Repositories
865-^^^^^^^^^^^^^^^^^^^^^^^^^
866-
867-While MAAS is available in the Ubuntu Archives per each release of
868-Ubuntu, the version might not be the latest. However, if you would like
869-to install a newer version of MAAS (the latest stable release), this is
870-available in the following PPA:
871-
872- * `ppa:maas/stable`_
873-
874-.. Note::
875- The MAAS team also releases the latest development release of MAAS.
876- The development release is available in `ppa:maas/next`_. However, this
877- is meant to be used for testing and at your own risk.
878-
879-Adding MAAS package repository is simple. At the command line, type::
880-
881- $ sudo add-apt-repository ppa:maas/stable
882-
883-You will be asked to confirm whether you would like to add this repository,
884-and its key. Upon configumation, the following needs to be typed at the
885-command line::
886-
887- $ sudo apt-get update
888-
889-.. _ppa:maas/stable:
890- https://launchpad.net/~maas/+archive/ubuntu/stable
891-.. _ppa:maas/next:
892- https://launchpad.net/~maas/+archive/ubuntu/next
893-
894-.. _pkg-install:
895-
896-Installing MAAS from the command line
897--------------------------------------
898-
899-Installing a Single Node MAAS
900-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
901-
902-At the command line, type::
903-
904- $ sudo apt-get install maas
905-
906-This will install both the MAAS Region Controller and the MAAS Rack
907-Controller, and will select sane defaults for the communication between
908-the Rack Controller and the Region Controller. After installation,
909-you can access the Web Interface. Then, there are just a few more setup
910-steps :ref:`post_install`
911-
912-Reconfiguring a MAAS Installation
913-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
914-
915-You will see a list of packages and a confirmation message to
916-proceed. The exact list will obviously depend on what you already have
917-installed on your server, but expect to add about 200MB of files.
918-
919-The configuration for the MAAS controller will automatically run and
920-pop up this config screen:
921-
922-.. image:: media/install_cluster-config.*
923-
924-Here you will need to enter the hostname for where the region
925-controller can be contacted. In many scenarios, you may be running the
926-region controller (i.e. the web and API interface) from a different
927-network address, for example where a server has several network
928-interfaces.
929-
930-Adding Rack Controllers
931-^^^^^^^^^^^^^^^^^^^^^^^
932-
933-If you would like to add additional MAAS Rack Controllers to your
934-MAAS setup, you can do so by following the instructions in
935-:doc:`rack-configuration`.
936-
937-.. _disc-install:
938-
939-Installing MAAS from Ubuntu Server boot media
940----------------------------------------------
941-
942-If you are installing MAAS as part of a fresh install it is easiest to
943-choose the "Multiple Server install with MAAS" option from the
944-installer and have pretty much everything set up for you. Boot from
945-the Ubuntu Server media and you will be greeted with the usual
946-language selection screen:
947-
948-.. image:: media/install_01.*
949-
950-On the next screen, you will see there is an entry in the menu called
951-"Multiple server install with MAAS". Use the cursor keys to select
952-this and then press Enter.
953-
954-.. image:: media/install_02.*
955-
956-The installer then runs through the usual language and keyboard
957-options. Make your selections using Tab/Cursor keys/Enter to proceed
958-through the install. The installer will then load various drivers,
959-which may take a moment or two.
960-
961-.. image:: media/install_03.*
962-
963-The next screen asks for the hostname for this server. Choose
964-something appropriate for your network.
965-
966-.. image:: media/install_04.*
967-
968-Finally we get to the MAAS part! Here there are just two options. We
969-want to "Create a new MAAS on this server" so go ahead and choose that
970-one.
971-
972-.. image:: media/install_05.*
973-
974-The install now continues as usual. Next you will be prompted to enter
975-a username. This will be the admin user for the actual server that
976-MAAS will be running on (not the same as the MAAS admin user!)
977-
978-.. image:: media/install_06.*
979-
980-As usual you will have the chance to encrypt your home
981-directory. Continue to make selections based on whatever settings suit
982-your usage.
983-
984-.. image:: media/install_07.*
985-
986-After making selections and partitioning storage, the system software
987-will start to be installed. This part should only take a few minutes.
988-
989-.. image:: media/install_09.*
990-
991-Various packages will now be configured, including the package manager
992-and update manager. It is important to set these up appropriately so
993-you will receive timely updates of the MAAS server software, as well
994-as other essential services that may run on this server.
995-
996-.. image:: media/install_10.*
997-
998-The configuration for MAAS will ask you to configure the host address
999-of the server. This should be the IP address you will use to connect
1000-to the server (you may have additional interfaces e.g. to run node
1001-subnets)
1002-
1003-.. image:: media/install_cluster-config.*
1004-
1005-The next screen will confirm the web address that will be used to the
1006-web interface.
1007-
1008-.. image:: media/install_controller-config.*
1009-
1010-After configuring any other packages the installer will finally come
1011-to and end. At this point you should eject the boot media.
1012-
1013-.. image:: media/install_14.*
1014-
1015-After restarting, you should be able to login to the new server with
1016-the information you supplied during the install. The MAAS software
1017-will run automatically.
1018-
1019-.. image:: media/install_15.*
1020-
1021-**NOTE:** The maas-dhcp and maas-dns packages should be installed by
1022-default, but on older releases of MAAS they won't be. If you want to
1023-have MAAS run DHCP and DNS services, you should install these packages.
1024-Check whether they are installed with::
1025-
1026- $ dpkg -l maas-dhcp maas-dns
1027-
1028-If they are missing, then::
1029-
1030- $ sudo apt-get install maas-dhcp maas-dns
1031-
1032-And then proceed to the post-install setup.
1033-
1034-.. _container-install:
1035-
1036-Installing MAAS in a LXC container
1037-----------------------------------
1038-
1039-Installing MAAS in a container is a typical setup for those users who
1040-would like to take advantange of their machine for other users at the
1041-same time of using MAAS.
1042-
1043-In order to setup MAAS, you need some requirements:
1044-
1045- * Create a bridge (for example, it can be br0).
1046- * Install LXD and ZFS.
1047- * Create a Container profile for MAAS
1048-
1049-Install LXD and ZFS
1050-^^^^^^^^^^^^^^^^^^^
1051-
1052-The first thing to do is to install LXD and ZFS::
1053-
1054- $ sudo apt-get install lxd zfsutils-linux
1055- $ sudo modprobe zfs
1056- $ sudo lxd init
1057-
1058-Create a LXC profile for MAAS
1059-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1060-
1061-First, create a container profile for MAAS::
1062-
1063- $ lxc profile create maas
1064-
1065-Second, bind the NIC inside the container (eth0) against the bridge on the
1066-physical host (br0)::
1067-
1068- $ lxc profile device set maas eth0 parent br0
1069-
1070-Finally, create a root disk for the container to use::
1071-
1072- $ lxc profile device add maas root disk path=/ pool=default
1073-
1074-Launch LXD container
1075-^^^^^^^^^^^^^^^^^^^^
1076-
1077-Once the profile has been created, you can now launch the LXC container::
1078-
1079- $ lxc launch -p maas ubuntu-daily:18.04 bionic-maas
1080-
1081-Install MAAS
1082-^^^^^^^^^^^^
1083-
1084-Once the container is running, you can now install MAAS. First you need
1085-to access the container with::
1086-
1087- $ lxc exec bionic-maas bash
1088-
1089-And you can proceed with the installation as above, :ref:`From a package repository. <pkg-install>`
1090-
1091-.. _post_install:
1092-
1093-Post-Install tasks
1094-==================
1095-
1096-Your MAAS is now installed, but there are a few more things to be done.
1097-If you now use a web browser to connect to the region controller, you
1098-should see that MAAS is running, but there will also be some errors on
1099-the screen:
1100-
1101-.. image:: media/install_web-init.*
1102-
1103-The on screen messages will tell you that there are no boot images
1104-present, and that you can't login because there is no admin user.
1105-
1106-
1107-Create a superuser account
1108---------------------------
1109-
1110-Once MAAS is installed, you'll need to create an administrator
1111-account::
1112-
1113- $ sudo maas createadmin --username=root --email=MYEMAIL@EXAMPLE.COM
1114-
1115-Substitute your own email address for MYEMAIL@EXAMPLE.COM. You may also
1116-use a different username for your administrator account, but "root" is a
1117-common convention and easy to remember. The command will prompt for a
1118-password to assign to the new user.
1119-
1120-You can run this command again for any further administrator accounts you
1121-may wish to create, but you need at least one.
1122-
1123-
1124-Log in on the server
1125---------------------
1126-
1127-Looking at the region controller's main web page again, you should now see
1128-a login screen. Log in using the user name and password which you have just
1129-created.
1130-
1131-.. image:: media/install-login.*
1132-
1133-
1134-Import the boot images
1135-----------------------
1136-
1137-Since version 1.7, MAAS stores the boot images in the region controller's
1138-database, from where the rack controllers will synchronise with the region
1139-and pull images from the region to the rack's local disk. This process
1140-is automatic and MAAS will check for and download new Ubuntu images every hour.
1141-
1142-However, on a new installation you'll need to start the import process manually
1143-once you have set up your MAAS region controller. There are two ways to start
1144-the import: through the web user interface, or through the remote API.
1145-
1146-To do it in the web user interface, go to the Images tab, check the boxes to
1147-say which images you want to import, and click the "Import images" button at
1148-the bottom of the Ubuntu section.
1149-
1150-.. image:: media/import-images.*
1151-
1152-A message will appear to let you know that the import has started, and after a
1153-while, the warnings about the lack of boot images will disappear.
1154-
1155-It may take a long time, depending on the speed of your Internet connection for
1156-import process to complete, as the images are several hundred megabytes. The
1157-import process will only download images that have changed since last import.
1158-You can check the progress of the import by hovering over the spinner next to
1159-each image.
1160-
1161-The other way to start the import is through the
1162-:ref:`region-controller API <region-controller-api>`, which you can invoke most
1163-conveniently through the :ref:`command-line interface <cli>`.
1164-
1165-To do this, connect to the MAAS API using the "maas" command-line client.
1166-See :ref:`Logging in <api-key>` for how to get set up with this tool. Then,
1167-run the command::
1168-
1169- $ maas my-maas-session boot-resources import
1170-
1171-(Substitute a different profile name for 'my-maas-session' if you have named
1172-yours something else.) This will initiate the download, just as if you had
1173-clicked "Import images" in the web user interface.
1174-
1175-By default, the import is configured to download the most recent LTS release
1176-only for the amd64 architecture. Although this should suit most needs, you can
1177-change the selections on the Images tab, or over the API. Read
1178-:doc:`customise boot sources </bootsources>` to see examples on how to do that.
1179-
1180-
1181-Speeding up repeated image imports by using a local mirror
1182-----------------------------------------------------------
1183-See :doc:`sstreams-mirror` for information on how to set up a mirror and
1184-configure MAAS to use it.
1185-
1186-
1187-Configure DHCP
1188---------------
1189-
1190-To enable MAAS to control DHCP, you can either:
1191-
1192-#. Follow the instructions at :doc:`rack-configuration` to
1193- use the web UI to set up your rack controller.
1194-
1195-#. Use the command line interface `maas` by first
1196- :ref:`logging in to the API <api-key>` and then
1197- :ref:`following this procedure <cli-dhcp>`
1198-
1199-
1200-Configure switches on the network
1201----------------------------------
1202-
1203-Some switches use Spanning-Tree Protocol (STP) to negotiate a loop-free path
1204-through a root bridge. While scanning, it can make each port wait up to 50
1205-seconds before data is allowed to be sent on the port. This delay in turn can
1206-cause problems with some applications/protocols such as PXE, DHCP and DNS, of
1207-which MAAS makes extensive use.
1208-
1209-To alleviate this problem, you should enable `Portfast`_ for Cisco switches
1210-or its equivalent on other vendor equipment, which enables the ports to come
1211-up almost immediately.
1212-
1213-.. _Portfast:
1214- https://www.symantec.com/business/support/index?page=content&id=HOWTO6019
1215-
1216-
1217-Traffic between the region contoller and rack controllers
1218-------------------------------------------------------------
1219-
1220-* Each rack controller must be able to:
1221-
1222- * Initiate TCP connections (for HTTP) to each region controller on
1223- port 80 or port 5240, the choice of which depends on the setting of
1224- the MAAS URL.
1225-
1226- * Initiate TCP connections (for RPC) to each region controller between
1227- port 5250 and 5259 inclusive. This permits up to 10 ``maas-regiond``
1228- processes on each region controller host. At present this is not
1229- configurable.
1230-
1231-
1232-Once everything is set up and running, you are ready to :doc:`start
1233-enlisting nodes <nodes>`
1234diff --git a/LICENSE b/LICENSE
1235deleted file mode 100644
1236index e8ef214..0000000
1237--- a/LICENSE
1238+++ /dev/null
1239@@ -1,676 +0,0 @@
1240-MAAS is Copyright 2012-2018 Canonical Ltd.
1241-
1242-Canonical Ltd ("Canonical") distributes the MAAS source code
1243-under the GNU Affero General Public License, version 3 ("AGPLv3").
1244-The full text of this licence is given below.
1245-
1246-Third-party copyright in this distribution is noted where applicable.
1247-
1248-All rights not expressly granted are reserved.
1249-
1250-=========================================================================
1251-
1252- GNU AFFERO GENERAL PUBLIC LICENSE
1253- Version 3, 19 November 2007
1254- (http://www.gnu.org/licenses/agpl.html)
1255-
1256- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
1257- Everyone is permitted to copy and distribute verbatim copies
1258- of this license document, but changing it is not allowed.
1259-
1260- Preamble
1261-
1262- The GNU Affero General Public License is a free, copyleft license for
1263-software and other kinds of works, specifically designed to ensure
1264-cooperation with the community in the case of network server software.
1265-
1266- The licenses for most software and other practical works are designed
1267-to take away your freedom to share and change the works. By contrast,
1268-our General Public Licenses are intended to guarantee your freedom to
1269-share and change all versions of a program--to make sure it remains free
1270-software for all its users.
1271-
1272- When we speak of free software, we are referring to freedom, not
1273-price. Our General Public Licenses are designed to make sure that you
1274-have the freedom to distribute copies of free software (and charge for
1275-them if you wish), that you receive source code or can get it if you
1276-want it, that you can change the software or use pieces of it in new
1277-free programs, and that you know you can do these things.
1278-
1279- Developers that use our General Public Licenses protect your rights
1280-with two steps: (1) assert copyright on the software, and (2) offer
1281-you this License which gives you legal permission to copy, distribute
1282-and/or modify the software.
1283-
1284- A secondary benefit of defending all users' freedom is that
1285-improvements made in alternate versions of the program, if they
1286-receive widespread use, become available for other developers to
1287-incorporate. Many developers of free software are heartened and
1288-encouraged by the resulting cooperation. However, in the case of
1289-software used on network servers, this result may fail to come about.
1290-The GNU General Public License permits making a modified version and
1291-letting the public access it on a server without ever releasing its
1292-source code to the public.
1293-
1294- The GNU Affero General Public License is designed specifically to
1295-ensure that, in such cases, the modified source code becomes available
1296-to the community. It requires the operator of a network server to
1297-provide the source code of the modified version running there to the
1298-users of that server. Therefore, public use of a modified version, on
1299-a publicly accessible server, gives the public access to the source
1300-code of the modified version.
1301-
1302- An older license, called the Affero General Public License and
1303-published by Affero, was designed to accomplish similar goals. This is
1304-a different license, not a version of the Affero GPL, but Affero has
1305-released a new version of the Affero GPL which permits relicensing under
1306-this license.
1307-
1308- The precise terms and conditions for copying, distribution and
1309-modification follow.
1310-
1311- TERMS AND CONDITIONS
1312-
1313- 0. Definitions.
1314-
1315- "This License" refers to version 3 of the GNU Affero General Public License.
1316-
1317- "Copyright" also means copyright-like laws that apply to other kinds of
1318-works, such as semiconductor masks.
1319-
1320- "The Program" refers to any copyrightable work licensed under this
1321-License. Each licensee is addressed as "you". "Licensees" and
1322-"recipients" may be individuals or organizations.
1323-
1324- To "modify" a work means to copy from or adapt all or part of the work
1325-in a fashion requiring copyright permission, other than the making of an
1326-exact copy. The resulting work is called a "modified version" of the
1327-earlier work or a work "based on" the earlier work.
1328-
1329- A "covered work" means either the unmodified Program or a work based
1330-on the Program.
1331-
1332- To "propagate" a work means to do anything with it that, without
1333-permission, would make you directly or secondarily liable for
1334-infringement under applicable copyright law, except executing it on a
1335-computer or modifying a private copy. Propagation includes copying,
1336-distribution (with or without modification), making available to the
1337-public, and in some countries other activities as well.
1338-
1339- To "convey" a work means any kind of propagation that enables other
1340-parties to make or receive copies. Mere interaction with a user through
1341-a computer network, with no transfer of a copy, is not conveying.
1342-
1343- An interactive user interface displays "Appropriate Legal Notices"
1344-to the extent that it includes a convenient and prominently visible
1345-feature that (1) displays an appropriate copyright notice, and (2)
1346-tells the user that there is no warranty for the work (except to the
1347-extent that warranties are provided), that licensees may convey the
1348-work under this License, and how to view a copy of this License. If
1349-the interface presents a list of user commands or options, such as a
1350-menu, a prominent item in the list meets this criterion.
1351-
1352- 1. Source Code.
1353-
1354- The "source code" for a work means the preferred form of the work
1355-for making modifications to it. "Object code" means any non-source
1356-form of a work.
1357-
1358- A "Standard Interface" means an interface that either is an official
1359-standard defined by a recognized standards body, or, in the case of
1360-interfaces specified for a particular programming language, one that
1361-is widely used among developers working in that language.
1362-
1363- The "System Libraries" of an executable work include anything, other
1364-than the work as a whole, that (a) is included in the normal form of
1365-packaging a Major Component, but which is not part of that Major
1366-Component, and (b) serves only to enable use of the work with that
1367-Major Component, or to implement a Standard Interface for which an
1368-implementation is available to the public in source code form. A
1369-"Major Component", in this context, means a major essential component
1370-(kernel, window system, and so on) of the specific operating system
1371-(if any) on which the executable work runs, or a compiler used to
1372-produce the work, or an object code interpreter used to run it.
1373-
1374- The "Corresponding Source" for a work in object code form means all
1375-the source code needed to generate, install, and (for an executable
1376-work) run the object code and to modify the work, including scripts to
1377-control those activities. However, it does not include the work's
1378-System Libraries, or general-purpose tools or generally available free
1379-programs which are used unmodified in performing those activities but
1380-which are not part of the work. For example, Corresponding Source
1381-includes interface definition files associated with source files for
1382-the work, and the source code for shared libraries and dynamically
1383-linked subprograms that the work is specifically designed to require,
1384-such as by intimate data communication or control flow between those
1385-subprograms and other parts of the work.
1386-
1387- The Corresponding Source need not include anything that users
1388-can regenerate automatically from other parts of the Corresponding
1389-Source.
1390-
1391- The Corresponding Source for a work in source code form is that
1392-same work.
1393-
1394- 2. Basic Permissions.
1395-
1396- All rights granted under this License are granted for the term of
1397-copyright on the Program, and are irrevocable provided the stated
1398-conditions are met. This License explicitly affirms your unlimited
1399-permission to run the unmodified Program. The output from running a
1400-covered work is covered by this License only if the output, given its
1401-content, constitutes a covered work. This License acknowledges your
1402-rights of fair use or other equivalent, as provided by copyright law.
1403-
1404- You may make, run and propagate covered works that you do not
1405-convey, without conditions so long as your license otherwise remains
1406-in force. You may convey covered works to others for the sole purpose
1407-of having them make modifications exclusively for you, or provide you
1408-with facilities for running those works, provided that you comply with
1409-the terms of this License in conveying all material for which you do
1410-not control copyright. Those thus making or running the covered works
1411-for you must do so exclusively on your behalf, under your direction
1412-and control, on terms that prohibit them from making any copies of
1413-your copyrighted material outside their relationship with you.
1414-
1415- Conveying under any other circumstances is permitted solely under
1416-the conditions stated below. Sublicensing is not allowed; section 10
1417-makes it unnecessary.
1418-
1419- 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
1420-
1421- No covered work shall be deemed part of an effective technological
1422-measure under any applicable law fulfilling obligations under article
1423-11 of the WIPO copyright treaty adopted on 20 December 1996, or
1424-similar laws prohibiting or restricting circumvention of such
1425-measures.
1426-
1427- When you convey a covered work, you waive any legal power to forbid
1428-circumvention of technological measures to the extent such circumvention
1429-is effected by exercising rights under this License with respect to
1430-the covered work, and you disclaim any intention to limit operation or
1431-modification of the work as a means of enforcing, against the work's
1432-users, your or third parties' legal rights to forbid circumvention of
1433-technological measures.
1434-
1435- 4. Conveying Verbatim Copies.
1436-
1437- You may convey verbatim copies of the Program's source code as you
1438-receive it, in any medium, provided that you conspicuously and
1439-appropriately publish on each copy an appropriate copyright notice;
1440-keep intact all notices stating that this License and any
1441-non-permissive terms added in accord with section 7 apply to the code;
1442-keep intact all notices of the absence of any warranty; and give all
1443-recipients a copy of this License along with the Program.
1444-
1445- You may charge any price or no price for each copy that you convey,
1446-and you may offer support or warranty protection for a fee.
1447-
1448- 5. Conveying Modified Source Versions.
1449-
1450- You may convey a work based on the Program, or the modifications to
1451-produce it from the Program, in the form of source code under the
1452-terms of section 4, provided that you also meet all of these conditions:
1453-
1454- a) The work must carry prominent notices stating that you modified
1455- it, and giving a relevant date.
1456-
1457- b) The work must carry prominent notices stating that it is
1458- released under this License and any conditions added under section
1459- 7. This requirement modifies the requirement in section 4 to
1460- "keep intact all notices".
1461-
1462- c) You must license the entire work, as a whole, under this
1463- License to anyone who comes into possession of a copy. This
1464- License will therefore apply, along with any applicable section 7
1465- additional terms, to the whole of the work, and all its parts,
1466- regardless of how they are packaged. This License gives no
1467- permission to license the work in any other way, but it does not
1468- invalidate such permission if you have separately received it.
1469-
1470- d) If the work has interactive user interfaces, each must display
1471- Appropriate Legal Notices; however, if the Program has interactive
1472- interfaces that do not display Appropriate Legal Notices, your
1473- work need not make them do so.
1474-
1475- A compilation of a covered work with other separate and independent
1476-works, which are not by their nature extensions of the covered work,
1477-and which are not combined with it such as to form a larger program,
1478-in or on a volume of a storage or distribution medium, is called an
1479-"aggregate" if the compilation and its resulting copyright are not
1480-used to limit the access or legal rights of the compilation's users
1481-beyond what the individual works permit. Inclusion of a covered work
1482-in an aggregate does not cause this License to apply to the other
1483-parts of the aggregate.
1484-
1485- 6. Conveying Non-Source Forms.
1486-
1487- You may convey a covered work in object code form under the terms
1488-of sections 4 and 5, provided that you also convey the
1489-machine-readable Corresponding Source under the terms of this License,
1490-in one of these ways:
1491-
1492- a) Convey the object code in, or embodied in, a physical product
1493- (including a physical distribution medium), accompanied by the
1494- Corresponding Source fixed on a durable physical medium
1495- customarily used for software interchange.
1496-
1497- b) Convey the object code in, or embodied in, a physical product
1498- (including a physical distribution medium), accompanied by a
1499- written offer, valid for at least three years and valid for as
1500- long as you offer spare parts or customer support for that product
1501- model, to give anyone who possesses the object code either (1) a
1502- copy of the Corresponding Source for all the software in the
1503- product that is covered by this License, on a durable physical
1504- medium customarily used for software interchange, for a price no
1505- more than your reasonable cost of physically performing this
1506- conveying of source, or (2) access to copy the
1507- Corresponding Source from a network server at no charge.
1508-
1509- c) Convey individual copies of the object code with a copy of the
1510- written offer to provide the Corresponding Source. This
1511- alternative is allowed only occasionally and noncommercially, and
1512- only if you received the object code with such an offer, in accord
1513- with subsection 6b.
1514-
1515- d) Convey the object code by offering access from a designated
1516- place (gratis or for a charge), and offer equivalent access to the
1517- Corresponding Source in the same way through the same place at no
1518- further charge. You need not require recipients to copy the
1519- Corresponding Source along with the object code. If the place to
1520- copy the object code is a network server, the Corresponding Source
1521- may be on a different server (operated by you or a third party)
1522- that supports equivalent copying facilities, provided you maintain
1523- clear directions next to the object code saying where to find the
1524- Corresponding Source. Regardless of what server hosts the
1525- Corresponding Source, you remain obligated to ensure that it is
1526- available for as long as needed to satisfy these requirements.
1527-
1528- e) Convey the object code using peer-to-peer transmission, provided
1529- you inform other peers where the object code and Corresponding
1530- Source of the work are being offered to the general public at no
1531- charge under subsection 6d.
1532-
1533- A separable portion of the object code, whose source code is excluded
1534-from the Corresponding Source as a System Library, need not be
1535-included in conveying the object code work.
1536-
1537- A "User Product" is either (1) a "consumer product", which means any
1538-tangible personal property which is normally used for personal, family,
1539-or household purposes, or (2) anything designed or sold for incorporation
1540-into a dwelling. In determining whether a product is a consumer product,
1541-doubtful cases shall be resolved in favor of coverage. For a particular
1542-product received by a particular user, "normally used" refers to a
1543-typical or common use of that class of product, regardless of the status
1544-of the particular user or of the way in which the particular user
1545-actually uses, or expects or is expected to use, the product. A product
1546-is a consumer product regardless of whether the product has substantial
1547-commercial, industrial or non-consumer uses, unless such uses represent
1548-the only significant mode of use of the product.
1549-
1550- "Installation Information" for a User Product means any methods,
1551-procedures, authorization keys, or other information required to install
1552-and execute modified versions of a covered work in that User Product from
1553-a modified version of its Corresponding Source. The information must
1554-suffice to ensure that the continued functioning of the modified object
1555-code is in no case prevented or interfered with solely because
1556-modification has been made.
1557-
1558- If you convey an object code work under this section in, or with, or
1559-specifically for use in, a User Product, and the conveying occurs as
1560-part of a transaction in which the right of possession and use of the
1561-User Product is transferred to the recipient in perpetuity or for a
1562-fixed term (regardless of how the transaction is characterized), the
1563-Corresponding Source conveyed under this section must be accompanied
1564-by the Installation Information. But this requirement does not apply
1565-if neither you nor any third party retains the ability to install
1566-modified object code on the User Product (for example, the work has
1567-been installed in ROM).
1568-
1569- The requirement to provide Installation Information does not include a
1570-requirement to continue to provide support service, warranty, or updates
1571-for a work that has been modified or installed by the recipient, or for
1572-the User Product in which it has been modified or installed. Access to a
1573-network may be denied when the modification itself materially and
1574-adversely affects the operation of the network or violates the rules and
1575-protocols for communication across the network.
1576-
1577- Corresponding Source conveyed, and Installation Information provided,
1578-in accord with this section must be in a format that is publicly
1579-documented (and with an implementation available to the public in
1580-source code form), and must require no special password or key for
1581-unpacking, reading or copying.
1582-
1583- 7. Additional Terms.
1584-
1585- "Additional permissions" are terms that supplement the terms of this
1586-License by making exceptions from one or more of its conditions.
1587-Additional permissions that are applicable to the entire Program shall
1588-be treated as though they were included in this License, to the extent
1589-that they are valid under applicable law. If additional permissions
1590-apply only to part of the Program, that part may be used separately
1591-under those permissions, but the entire Program remains governed by
1592-this License without regard to the additional permissions.
1593-
1594- When you convey a copy of a covered work, you may at your option
1595-remove any additional permissions from that copy, or from any part of
1596-it. (Additional permissions may be written to require their own
1597-removal in certain cases when you modify the work.) You may place
1598-additional permissions on material, added by you to a covered work,
1599-for which you have or can give appropriate copyright permission.
1600-
1601- Notwithstanding any other provision of this License, for material you
1602-add to a covered work, you may (if authorized by the copyright holders of
1603-that material) supplement the terms of this License with terms:
1604-
1605- a) Disclaiming warranty or limiting liability differently from the
1606- terms of sections 15 and 16 of this License; or
1607-
1608- b) Requiring preservation of specified reasonable legal notices or
1609- author attributions in that material or in the Appropriate Legal
1610- Notices displayed by works containing it; or
1611-
1612- c) Prohibiting misrepresentation of the origin of that material, or
1613- requiring that modified versions of such material be marked in
1614- reasonable ways as different from the original version; or
1615-
1616- d) Limiting the use for publicity purposes of names of licensors or
1617- authors of the material; or
1618-
1619- e) Declining to grant rights under trademark law for use of some
1620- trade names, trademarks, or service marks; or
1621-
1622- f) Requiring indemnification of licensors and authors of that
1623- material by anyone who conveys the material (or modified versions of
1624- it) with contractual assumptions of liability to the recipient, for
1625- any liability that these contractual assumptions directly impose on
1626- those licensors and authors.
1627-
1628- All other non-permissive additional terms are considered "further
1629-restrictions" within the meaning of section 10. If the Program as you
1630-received it, or any part of it, contains a notice stating that it is
1631-governed by this License along with a term that is a further
1632-restriction, you may remove that term. If a license document contains
1633-a further restriction but permits relicensing or conveying under this
1634-License, you may add to a covered work material governed by the terms
1635-of that license document, provided that the further restriction does
1636-not survive such relicensing or conveying.
1637-
1638- If you add terms to a covered work in accord with this section, you
1639-must place, in the relevant source files, a statement of the
1640-additional terms that apply to those files, or a notice indicating
1641-where to find the applicable terms.
1642-
1643- Additional terms, permissive or non-permissive, may be stated in the
1644-form of a separately written license, or stated as exceptions;
1645-the above requirements apply either way.
1646-
1647- 8. Termination.
1648-
1649- You may not propagate or modify a covered work except as expressly
1650-provided under this License. Any attempt otherwise to propagate or
1651-modify it is void, and will automatically terminate your rights under
1652-this License (including any patent licenses granted under the third
1653-paragraph of section 11).
1654-
1655- However, if you cease all violation of this License, then your
1656-license from a particular copyright holder is reinstated (a)
1657-provisionally, unless and until the copyright holder explicitly and
1658-finally terminates your license, and (b) permanently, if the copyright
1659-holder fails to notify you of the violation by some reasonable means
1660-prior to 60 days after the cessation.
1661-
1662- Moreover, your license from a particular copyright holder is
1663-reinstated permanently if the copyright holder notifies you of the
1664-violation by some reasonable means, this is the first time you have
1665-received notice of violation of this License (for any work) from that
1666-copyright holder, and you cure the violation prior to 30 days after
1667-your receipt of the notice.
1668-
1669- Termination of your rights under this section does not terminate the
1670-licenses of parties who have received copies or rights from you under
1671-this License. If your rights have been terminated and not permanently
1672-reinstated, you do not qualify to receive new licenses for the same
1673-material under section 10.
1674-
1675- 9. Acceptance Not Required for Having Copies.
1676-
1677- You are not required to accept this License in order to receive or
1678-run a copy of the Program. Ancillary propagation of a covered work
1679-occurring solely as a consequence of using peer-to-peer transmission
1680-to receive a copy likewise does not require acceptance. However,
1681-nothing other than this License grants you permission to propagate or
1682-modify any covered work. These actions infringe copyright if you do
1683-not accept this License. Therefore, by modifying or propagating a
1684-covered work, you indicate your acceptance of this License to do so.
1685-
1686- 10. Automatic Licensing of Downstream Recipients.
1687-
1688- Each time you convey a covered work, the recipient automatically
1689-receives a license from the original licensors, to run, modify and
1690-propagate that work, subject to this License. You are not responsible
1691-for enforcing compliance by third parties with this License.
1692-
1693- An "entity transaction" is a transaction transferring control of an
1694-organization, or substantially all assets of one, or subdividing an
1695-organization, or merging organizations. If propagation of a covered
1696-work results from an entity transaction, each party to that
1697-transaction who receives a copy of the work also receives whatever
1698-licenses to the work the party's predecessor in interest had or could
1699-give under the previous paragraph, plus a right to possession of the
1700-Corresponding Source of the work from the predecessor in interest, if
1701-the predecessor has it or can get it with reasonable efforts.
1702-
1703- You may not impose any further restrictions on the exercise of the
1704-rights granted or affirmed under this License. For example, you may
1705-not impose a license fee, royalty, or other charge for exercise of
1706-rights granted under this License, and you may not initiate litigation
1707-(including a cross-claim or counterclaim in a lawsuit) alleging that
1708-any patent claim is infringed by making, using, selling, offering for
1709-sale, or importing the Program or any portion of it.
1710-
1711- 11. Patents.
1712-
1713- A "contributor" is a copyright holder who authorizes use under this
1714-License of the Program or a work on which the Program is based. The
1715-work thus licensed is called the contributor's "contributor version".
1716-
1717- A contributor's "essential patent claims" are all patent claims
1718-owned or controlled by the contributor, whether already acquired or
1719-hereafter acquired, that would be infringed by some manner, permitted
1720-by this License, of making, using, or selling its contributor version,
1721-but do not include claims that would be infringed only as a
1722-consequence of further modification of the contributor version. For
1723-purposes of this definition, "control" includes the right to grant
1724-patent sublicenses in a manner consistent with the requirements of
1725-this License.
1726-
1727- Each contributor grants you a non-exclusive, worldwide, royalty-free
1728-patent license under the contributor's essential patent claims, to
1729-make, use, sell, offer for sale, import and otherwise run, modify and
1730-propagate the contents of its contributor version.
1731-
1732- In the following three paragraphs, a "patent license" is any express
1733-agreement or commitment, however denominated, not to enforce a patent
1734-(such as an express permission to practice a patent or covenant not to
1735-sue for patent infringement). To "grant" such a patent license to a
1736-party means to make such an agreement or commitment not to enforce a
1737-patent against the party.
1738-
1739- If you convey a covered work, knowingly relying on a patent license,
1740-and the Corresponding Source of the work is not available for anyone
1741-to copy, free of charge and under the terms of this License, through a
1742-publicly available network server or other readily accessible means,
1743-then you must either (1) cause the Corresponding Source to be so
1744-available, or (2) arrange to deprive yourself of the benefit of the
1745-patent license for this particular work, or (3) arrange, in a manner
1746-consistent with the requirements of this License, to extend the patent
1747-license to downstream recipients. "Knowingly relying" means you have
1748-actual knowledge that, but for the patent license, your conveying the
1749-covered work in a country, or your recipient's use of the covered work
1750-in a country, would infringe one or more identifiable patents in that
1751-country that you have reason to believe are valid.
1752-
1753- If, pursuant to or in connection with a single transaction or
1754-arrangement, you convey, or propagate by procuring conveyance of, a
1755-covered work, and grant a patent license to some of the parties
1756-receiving the covered work authorizing them to use, propagate, modify
1757-or convey a specific copy of the covered work, then the patent license
1758-you grant is automatically extended to all recipients of the covered
1759-work and works based on it.
1760-
1761- A patent license is "discriminatory" if it does not include within
1762-the scope of its coverage, prohibits the exercise of, or is
1763-conditioned on the non-exercise of one or more of the rights that are
1764-specifically granted under this License. You may not convey a covered
1765-work if you are a party to an arrangement with a third party that is
1766-in the business of distributing software, under which you make payment
1767-to the third party based on the extent of your activity of conveying
1768-the work, and under which the third party grants, to any of the
1769-parties who would receive the covered work from you, a discriminatory
1770-patent license (a) in connection with copies of the covered work
1771-conveyed by you (or copies made from those copies), or (b) primarily
1772-for and in connection with specific products or compilations that
1773-contain the covered work, unless you entered into that arrangement,
1774-or that patent license was granted, prior to 28 March 2007.
1775-
1776- Nothing in this License shall be construed as excluding or limiting
1777-any implied license or other defenses to infringement that may
1778-otherwise be available to you under applicable patent law.
1779-
1780- 12. No Surrender of Others' Freedom.
1781-
1782- If conditions are imposed on you (whether by court order, agreement or
1783-otherwise) that contradict the conditions of this License, they do not
1784-excuse you from the conditions of this License. If you cannot convey a
1785-covered work so as to satisfy simultaneously your obligations under this
1786-License and any other pertinent obligations, then as a consequence you may
1787-not convey it at all. For example, if you agree to terms that obligate you
1788-to collect a royalty for further conveying from those to whom you convey
1789-the Program, the only way you could satisfy both those terms and this
1790-License would be to refrain entirely from conveying the Program.
1791-
1792- 13. Remote Network Interaction; Use with the GNU General Public License.
1793-
1794- Notwithstanding any other provision of this License, if you modify the
1795-Program, your modified version must prominently offer all users
1796-interacting with it remotely through a computer network (if your version
1797-supports such interaction) an opportunity to receive the Corresponding
1798-Source of your version by providing access to the Corresponding Source
1799-from a network server at no charge, through some standard or customary
1800-means of facilitating copying of software. This Corresponding Source
1801-shall include the Corresponding Source for any work covered by version 3
1802-of the GNU General Public License that is incorporated pursuant to the
1803-following paragraph.
1804-
1805- Notwithstanding any other provision of this License, you have
1806-permission to link or combine any covered work with a work licensed
1807-under version 3 of the GNU General Public License into a single
1808-combined work, and to convey the resulting work. The terms of this
1809-License will continue to apply to the part which is the covered work,
1810-but the work with which it is combined will remain governed by version
1811-3 of the GNU General Public License.
1812-
1813- 14. Revised Versions of this License.
1814-
1815- The Free Software Foundation may publish revised and/or new versions of
1816-the GNU Affero General Public License from time to time. Such new versions
1817-will be similar in spirit to the present version, but may differ in detail to
1818-address new problems or concerns.
1819-
1820- Each version is given a distinguishing version number. If the
1821-Program specifies that a certain numbered version of the GNU Affero General
1822-Public License "or any later version" applies to it, you have the
1823-option of following the terms and conditions either of that numbered
1824-version or of any later version published by the Free Software
1825-Foundation. If the Program does not specify a version number of the
1826-GNU Affero General Public License, you may choose any version ever published
1827-by the Free Software Foundation.
1828-
1829- If the Program specifies that a proxy can decide which future
1830-versions of the GNU Affero General Public License can be used, that proxy's
1831-public statement of acceptance of a version permanently authorizes you
1832-to choose that version for the Program.
1833-
1834- Later license versions may give you additional or different
1835-permissions. However, no additional obligations are imposed on any
1836-author or copyright holder as a result of your choosing to follow a
1837-later version.
1838-
1839- 15. Disclaimer of Warranty.
1840-
1841- THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
1842-APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
1843-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
1844-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
1845-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
1846-PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
1847-IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
1848-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
1849-
1850- 16. Limitation of Liability.
1851-
1852- IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
1853-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
1854-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
1855-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
1856-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
1857-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
1858-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
1859-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
1860-SUCH DAMAGES.
1861-
1862- 17. Interpretation of Sections 15 and 16.
1863-
1864- If the disclaimer of warranty and limitation of liability provided
1865-above cannot be given local legal effect according to their terms,
1866-reviewing courts shall apply local law that most closely approximates
1867-an absolute waiver of all civil liability in connection with the
1868-Program, unless a warranty or assumption of liability accompanies a
1869-copy of the Program in return for a fee.
1870-
1871- END OF TERMS AND CONDITIONS
1872-
1873- How to Apply These Terms to Your New Programs
1874-
1875- If you develop a new program, and you want it to be of the greatest
1876-possible use to the public, the best way to achieve this is to make it
1877-free software which everyone can redistribute and change under these terms.
1878-
1879- To do so, attach the following notices to the program. It is safest
1880-to attach them to the start of each source file to most effectively
1881-state the exclusion of warranty; and each file should have at least
1882-the "copyright" line and a pointer to where the full notice is found.
1883-
1884- <one line to give the program's name and a brief idea of what it does.>
1885- Copyright (C) <year> <name of author>
1886-
1887- This program is free software: you can redistribute it and/or modify
1888- it under the terms of the GNU Affero General Public License as published by
1889- the Free Software Foundation, either version 3 of the License, or
1890- (at your option) any later version.
1891-
1892- This program is distributed in the hope that it will be useful,
1893- but WITHOUT ANY WARRANTY; without even the implied warranty of
1894- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
1895- GNU Affero General Public License for more details.
1896-
1897- You should have received a copy of the GNU Affero General Public License
1898- along with this program. If not, see <http://www.gnu.org/licenses/>.
1899-
1900-Also add information on how to contact you by electronic and paper mail.
1901-
1902- If your software can interact with users remotely through a computer
1903-network, you should also make sure that it provides a way for users to
1904-get its source. For example, if your program is a web application, its
1905-interface could display a "Source" link that leads users to an archive
1906-of the code. There are many ways you could offer source, and different
1907-solutions will be better for different programs; see section 13 for the
1908-specific requirements.
1909-
1910- You should also get your employer (if you work as a programmer) or school,
1911-if any, to sign a "copyright disclaimer" for the program, if necessary.
1912-For more information on this, and how to apply and follow the GNU AGPL, see
1913-<http://www.gnu.org/licenses/>.
1914-
1915-=========================================================================
1916diff --git a/MANIFEST.in b/MANIFEST.in
1917deleted file mode 100644
1918index 089f313..0000000
1919--- a/MANIFEST.in
1920+++ /dev/null
1921@@ -1,7 +0,0 @@
1922-graft src/maasserver/static
1923-graft src/maasserver/templates
1924-graft src/metadataserver/fixtures
1925-graft src/metadataserver/user_data/templates
1926-graft src/provisioningserver/templates
1927-include src/provisioningserver/drivers/power/*.xml
1928-include src/metadataserver/builtin_scripts/*.sh
1929diff --git a/Makefile b/Makefile
1930deleted file mode 100644
1931index 17d7507..0000000
1932--- a/Makefile
1933+++ /dev/null
1934@@ -1,846 +0,0 @@
1935-python := python3
1936-snapcraft := snapcraft
1937-
1938-# pkg_resources makes some incredible noise about version numbers. They
1939-# are not indications of bugs in MAAS so we silence them everywhere.
1940-export PYTHONWARNINGS = \
1941- ignore:You have iterated over the result:RuntimeWarning:pkg_resources:
1942-
1943-# Network activity can be suppressed by setting offline=true (or any
1944-# non-empty string) at the command-line.
1945-ifeq ($(offline),)
1946-buildout := bin/buildout
1947-else
1948-buildout := bin/buildout buildout:offline=true
1949-endif
1950-
1951-# If offline has been selected, attempt to further block HTTP/HTTPS
1952-# activity by setting bogus proxies in the environment.
1953-ifneq ($(offline),)
1954-export http_proxy := broken
1955-export https_proxy := broken
1956-endif
1957-
1958-# MAAS SASS stylesheets. The first input file (maas-styles.css) imports
1959-# the others, so is treated specially in the target definitions.
1960-scss_input := src/maasserver/static/scss/build.scss
1961-scss_deps := $(wildcard src/maasserver/static/scss/_*.scss)
1962-scss_output := src/maasserver/static/css/build.css
1963-
1964-javascript_deps := \
1965- $(shell find src -name '*.js' -not -path '*/maasserver/static/js/bundle/*') \
1966- package.json \
1967- webpack.config.js \
1968- yarn.lock
1969-
1970-javascript_output := \
1971- src/maasserver/static/js/bundle/maas-min.js \
1972- src/maasserver/static/js/bundle/maas-min.js.map \
1973- src/maasserver/static/js/bundle/vendor-min.js \
1974- src/maasserver/static/js/bundle/vendor-min.js.map
1975-
1976-# Prefix commands with this when they need access to the database.
1977-# Remember to add a dependency on bin/database from the targets in
1978-# which those commands appear.
1979-dbrun := bin/database --preserve run --
1980-
1981-# Path to install local nodejs.
1982-mkfile_dir := $(shell dirname $(realpath $(lastword $(MAKEFILE_LIST))))
1983-nodejs_path := $(mkfile_dir)/include/nodejs/bin
1984-
1985-export PATH := $(nodejs_path):$(PATH)
1986-
1987-# For things that care, postgresfixture for example, we always want to
1988-# use the "maas" databases.
1989-export PGDATABASE := maas
1990-
1991-# For anything we start, we want to hint as to its root directory.
1992-export MAAS_ROOT := $(CURDIR)/.run
1993-
1994-build: \
1995- bin/buildout \
1996- bin/database \
1997- bin/maas \
1998- bin/maas-common \
1999- bin/maas-rack \
2000- bin/maas-region \
2001- bin/rackd \
2002- bin/regiond \
2003- bin/test.cli \
2004- bin/test.rack \
2005- bin/test.region \
2006- bin/test.region.legacy \
2007- bin/test.testing \
2008- bin/test.js \
2009- bin/test.e2e \
2010- bin/test.parallel \
2011- bin/py bin/ipy \
2012- pycharm
2013-
2014-all: build doc
2015-
2016-# Install all packages required for MAAS development & operation on
2017-# the system. This may prompt for a password.
2018-install-dependencies: release := $(shell lsb_release -c -s)
2019-install-dependencies:
2020- sudo DEBIAN_FRONTEND=noninteractive apt-get -y \
2021- --no-install-recommends install $(shell sort -u \
2022- $(addprefix required-packages/,base build dev doc) | sed '/^\#/d')
2023- sudo DEBIAN_FRONTEND=noninteractive apt-get -y \
2024- purge $(shell sort -u required-packages/forbidden | sed '/^\#/d')
2025- if [ -x /usr/bin/snap ]; then sudo snap install --classic snapcraft; fi
2026-
2027-.gitignore:
2028- sed 's:^[.]/:/:' $^ > $@
2029-
2030-configure-buildout:
2031- utilities/configure-buildout
2032-
2033-sudoers:
2034- utilities/install-sudoers
2035- utilities/grant-nmap-permissions
2036-
2037-bin/buildout: bootstrap-buildout.py
2038- @utilities/configure-buildout --quiet
2039- $(python) bootstrap-buildout.py --allow-site-packages
2040- @touch --no-create $@ # Ensure it's newer than its dependencies.
2041-
2042-# buildout.cfg refers to .run and .run-e2e.
2043-buildout.cfg: .run .run-e2e
2044-
2045-bin/database: bin/buildout buildout.cfg versions.cfg setup.py
2046- $(buildout) install database
2047- @touch --no-create $@
2048-
2049-bin/test.parallel: \
2050- bin/buildout buildout.cfg versions.cfg setup.py
2051- $(buildout) install parallel-test
2052- @touch --no-create $@
2053-
2054-bin/maas-region bin/regiond: \
2055- bin/buildout buildout.cfg versions.cfg setup.py \
2056- $(scss_output) $(javascript_output)
2057- $(buildout) install region
2058- @touch --no-create $@
2059-
2060-bin/test.region: \
2061- bin/buildout buildout.cfg versions.cfg setup.py \
2062- bin/maas-region bin/maas-rack bin/maas-common
2063- $(buildout) install region-test
2064- @touch --no-create $@
2065-
2066-bin/test.region.legacy: \
2067- bin/buildout buildout.cfg versions.cfg setup.py
2068- $(buildout) install region-test-legacy
2069- @touch --no-create $@
2070-
2071-bin/maas: bin/buildout buildout.cfg versions.cfg setup.py
2072- $(buildout) install cli
2073- @touch --no-create $@
2074-
2075-bin/test.cli: bin/buildout buildout.cfg versions.cfg setup.py bin/maas
2076- $(buildout) install cli-test
2077- @touch --no-create $@
2078-
2079-bin/test.js: bin/karma bin/buildout buildout.cfg versions.cfg setup.py
2080- $(buildout) install js-test
2081- @touch --no-create $@
2082-
2083-bin/test.e2e: \
2084- bin/protractor bin/buildout buildout.cfg versions.cfg setup.py
2085- $(buildout) install e2e-test
2086- @touch --no-create $@
2087-
2088-# bin/flake8 is needed for checking lint and bin/node-sass is needed for
2089-# checking css.
2090-bin/test.testing: \
2091- bin/flake8 bin/node-sass bin/buildout \
2092- buildout.cfg versions.cfg setup.py
2093- $(buildout) install testing-test
2094- @touch --no-create $@
2095-
2096-bin/maas-rack bin/rackd bin/maas-common: \
2097- bin/buildout buildout.cfg versions.cfg setup.py
2098- $(buildout) install rack
2099- @touch --no-create $@
2100-
2101-bin/test.rack: \
2102- bin/buildout buildout.cfg versions.cfg setup.py bin/maas-rack bin/py
2103- $(buildout) install rack-test
2104- @touch --no-create $@
2105-
2106-bin/flake8: bin/buildout buildout.cfg versions.cfg setup.py
2107- $(buildout) install flake8
2108- @touch --no-create $@
2109-
2110-bin/sphinx bin/sphinx-build: bin/buildout buildout.cfg versions.cfg setup.py
2111- $(buildout) install sphinx
2112- @touch --no-create $@
2113-
2114-bin/py bin/ipy: bin/buildout buildout.cfg versions.cfg setup.py
2115- $(buildout) install repl
2116- @touch --no-create bin/py bin/ipy
2117-
2118-bin/coverage: bin/buildout buildout.cfg versions.cfg setup.py
2119- $(buildout) install coverage
2120- @touch --no-create bin/coverage
2121-
2122-include/nodejs/bin/node:
2123- mkdir -p include/nodejs
2124- wget -O include/nodejs/nodejs.tar.gz https://nodejs.org/dist/v8.10.0/node-v8.10.0-linux-x64.tar.gz
2125- tar -C include/nodejs/ -xf include/nodejs/nodejs.tar.gz --strip-components=1
2126-
2127-include/nodejs/yarn.tar.gz:
2128- mkdir -p include/nodejs
2129- wget -O include/nodejs/yarn.tar.gz https://yarnpkg.com/latest.tar.gz
2130-
2131-include/nodejs/bin/yarn: include/nodejs/yarn.tar.gz
2132- tar -C include/nodejs/ -xf include/nodejs/yarn.tar.gz --strip-components=1
2133- @touch --no-create $@
2134-
2135-bin/yarn: include/nodejs/bin/yarn
2136- @mkdir -p bin
2137- ln -sf ../include/nodejs/bin/yarn $@
2138- @touch --no-create $@
2139-
2140-node_modules: include/nodejs/bin/node bin/yarn
2141- bin/yarn --frozen-lockfile
2142- @touch --no-create $@
2143-
2144-define js_bins
2145- bin/karma
2146- bin/protractor
2147- bin/node-sass
2148- bin/webpack
2149-endef
2150-
2151-$(strip $(js_bins)): node_modules
2152- ln -sf ../node_modules/.bin/$(notdir $@) $@
2153- @touch --no-create $@
2154-
2155-define node_packages
2156- @babel/core
2157- @babel/preset-react
2158- @babel/preset-es2015
2159- @types/prop-types
2160- @types/react
2161- @types/react-dom
2162- babel-polyfill
2163- babel-loader@^8.0.0-beta.0
2164- glob
2165- jasmine-core@=2.99.1
2166- karma
2167- karma-chrome-launcher
2168- karma-failed-reporter
2169- karma-firefox-launcher
2170- karma-jasmine
2171- karma-ng-html2js-preprocessor
2172- karma-opera-launcher
2173- karma-phantomjs-launcher
2174- karma-sourcemap-loader
2175- macaroon-bakery
2176- node-sass
2177- phantomjs-prebuilt
2178- prop-types
2179- protractor
2180- react
2181- react-dom
2182- react2angular
2183- uglifyjs-webpack-plugin
2184- vanilla-framework
2185- vanilla-framework-react
2186- webpack
2187- webpack-cli
2188- webpack-merge
2189-endef
2190-
2191-force-yarn-update: bin/yarn
2192- $(RM) package.json yarn.lock
2193- bin/yarn add -D $(strip $(node_packages))
2194-
2195-define test-scripts
2196- bin/test.cli
2197- bin/test.rack
2198- bin/test.region
2199- bin/test.region.legacy
2200- bin/test.testing
2201- bin/test.js
2202-endef
2203-
2204-lxd:
2205- utilities/configure-lxd-profile
2206- utilities/create-lxd-bionic-image
2207-
2208-test: bin/test.parallel bin/coverage
2209- @$(RM) .coverage .coverage.*
2210- @bin/test.parallel --with-coverage --subprocess-per-core
2211- @bin/coverage combine
2212-
2213-test-js: bin/test.js javascript
2214- @bin/test.js
2215-
2216-test-serial: $(strip $(test-scripts))
2217- @bin/maas-region makemigrations --dry-run --exit && exit 1 ||:
2218- @$(RM) .coverage .coverage.* .failed
2219- $(foreach test,$^,$(test-template);)
2220- @test ! -f .failed
2221-
2222-test-failed: $(strip $(test-scripts))
2223- @bin/maas-region makemigrations --dry-run --exit && exit 1 ||:
2224- @$(RM) .coverage .coverage.* .failed
2225- $(foreach test,$^,$(test-template-failed);)
2226- @test ! -f .failed
2227-
2228-clean-failed:
2229- $(RM) .noseids
2230-
2231-src/maasserver/testing/initial.maas_test.sql: bin/maas-region bin/database
2232- # Run migrations without any triggers created.
2233- $(dbrun) bin/maas-region dbupgrade --internal-no-triggers
2234- # Data migration will create a notification, that will break tests. Want the
2235- # database to be a clean schema.
2236- $(dbrun) bin/maas-region shell -c "from maasserver.models.notification import Notification; Notification.objects.all().delete()"
2237- bin/database --preserve run -- \
2238- pg_dump maas --no-owner --no-privileges \
2239- --format=plain > $@
2240-
2241-test-initial-data: src/maasserver/testing/initial.maas_test.sql
2242-
2243-define test-template
2244-$(test) --with-xunit --xunit-file=xunit.$(notdir $(test)).xml || touch .failed
2245-endef
2246-
2247-define test-template-failed
2248- $(test) --with-xunit --xunit-file=xunit.$(notdir $(test)).xml --failed || \
2249- $(test) --with-xunit --xunit-file=xunit.$(notdir $(test)).xml --failed || \
2250- touch .failed
2251-endef
2252-
2253-smoke: lint bin/maas-region bin/test.rack
2254- @bin/maas-region makemigrations --dry-run --exit && exit 1 ||:
2255- @bin/test.rack --stop
2256-
2257-test-serial+coverage: export NOSE_WITH_COVERAGE = 1
2258-test-serial+coverage: test-serial
2259-
2260-coverage-report: coverage/index.html
2261- sensible-browser $< > /dev/null 2>&1 &
2262-
2263-coverage.xml: bin/coverage .coverage
2264- bin/coverage xml -o $@
2265-
2266-coverage/index.html: revno = $(or $(shell git rev-parse HEAD 2>/dev/null),???)
2267-coverage/index.html: bin/coverage .coverage
2268- @$(RM) -r $(@D)
2269- bin/coverage html \
2270- --title "Coverage for MAAS rev $(revno)" \
2271- --directory $(@D)
2272-
2273-.coverage:
2274- @$(error Use `$(MAKE) test` to generate coverage)
2275-
2276-lint: \
2277- lint-py lint-py-complexity lint-py-imports \
2278- lint-js lint-doc lint-rst
2279- # Only Unix line ends should be accepted
2280- @find src/ -type f -exec file "{}" ";" | \
2281- awk '/CRLF/ { print $0; count++ } END {exit count}' || \
2282- (echo "Lint check failed; run make format to fix DOS linefeeds."; false)
2283-
2284-pocketlint = $(call available,pocketlint,python-pocket-lint)
2285-
2286-# XXX jtv 2014-02-25: Clean up this lint, then make it part of "make lint".
2287-lint-css: sources = src/maasserver/static/css
2288-lint-css:
2289- @find $(sources) -type f \
2290- -print0 | xargs -r0 $(pocketlint) --max-length=120
2291-
2292-# Python lint checks are time-intensive, but flake8 now knows how to run
2293-# parallel jobs, and does so by default.
2294-lint-py: sources = setup.py src
2295-lint-py: bin/flake8
2296- @find $(sources) -name '*.py' \
2297- ! -path '*/migrations/*' -print0 | xargs -r0 bin/flake8 --config=.flake8
2298-
2299-# Ignore tests when checking complexity. The maximum complexity ought to
2300-# be close to 10 but MAAS has many functions that are over that so we
2301-# start with a much higher number. Over time we can ratchet it down.
2302-lint-py-complexity: maximum=26
2303-lint-py-complexity: sources = setup.py src
2304-lint-py-complexity: bin/flake8
2305- @find $(sources) -name '*.py' \
2306- ! -path '*/migrations/*' \
2307- ! -path '*/tests/*' ! -path '*/testing/*' ! -name 'testing.py' \
2308- -print0 | xargs -r0 bin/flake8 --config=.flake8 --max-complexity=$(maximum)
2309-
2310-# Statically check imports against policy.
2311-lint-py-imports: sources = setup.py src
2312-lint-py-imports:
2313- @utilities/check-imports
2314- @find $(sources) -name '*.py' \
2315- ! -path '*/migrations/*' \
2316- -print0 | xargs -r0 utilities/find-early-imports
2317-
2318-lint-doc:
2319- @utilities/doc-lint
2320-
2321-# JavaScript lint is checked in parallel for speed. The -n20 -P4 setting
2322-# worked well on a multicore SSD machine with the files cached, roughly
2323-# doubling the speed, but it may need tuning for slower systems or cold caches.
2324-lint-js: sources = src/maasserver/static/js
2325-lint-js:
2326- @find $(sources) -type f -not -path '*/angular/3rdparty/*' -a \
2327- -not -path '*-min.js' -a \
2328- '(' -name '*.html' -o -name '*.js' ')' -print0 \
2329- | xargs -r0 -n20 -P4 $(pocketlint)
2330- bin/yarn prettier-check
2331-
2332-# Apply automated formatting to all Python, Sass and Javascript files.
2333-format: sources = $(wildcard *.py contrib/*.py) src utilities etc
2334-format: bin/yarn
2335- @find $(sources) -name '*.py' -print0 | xargs -r0 utilities/format-imports
2336- @find src/ -type f -exec file "{}" ";" | grep CRLF | cut -d ':' -f1 | xargs dos2unix
2337- bin/yarn prettier
2338-
2339-check: clean test
2340-
2341-docs/api.rst: bin/maas-region src/maasserver/api/doc_handler.py syncdb
2342- bin/maas-region generate_api_doc > $@
2343-
2344-sampledata: bin/maas-region bin/database syncdb
2345- $(dbrun) bin/maas-region generate_sample_data
2346-
2347-doc: bin/sphinx docs/api.rst
2348- bin/sphinx
2349-
2350-docs/_build/html/index.html: doc
2351-
2352-doc-browse: docs/_build/html/index.html
2353- sensible-browser $< > /dev/null 2>&1 &
2354-
2355-doc-with-versions: bin/sphinx docs/api.rst
2356- $(MAKE) -C docs/_build SPHINXOPTS="-A add_version_switcher=true" html
2357-
2358-man: $(patsubst docs/man/%.rst,man/%,$(wildcard docs/man/*.rst))
2359-
2360-man/%: docs/man/%.rst | bin/sphinx-build
2361- bin/sphinx-build -b man docs man $^
2362-
2363-.run .run-e2e: run-skel
2364- @cp --archive --verbose $^ $@
2365-
2366-.idea: contrib/pycharm
2367- @cp --archive --verbose $^ $@
2368-
2369-pycharm: .idea
2370-
2371-styles: $(scss_output)
2372-
2373-force-styles: clean-styles $(scss_output)
2374-
2375-$(scss_output): bin/node-sass $(scss_input) $(scss_deps)
2376- bin/node-sass --include-path=src/maasserver/static/scss \
2377- --output-style compressed $(scss_input) -o $(dir $@)
2378-
2379-clean-styles:
2380- $(RM) $(scss_output)
2381-
2382-javascript: node_modules $(javascript_output)
2383-
2384-force-javascript: clean-javascript node_modules $(javascript_output)
2385-
2386-lander-javascript: force-javascript
2387- git update-index -q --no-assume-unchanged $(strip $(javascript_output)) 2> /dev/null || true
2388- git add -f $(strip $(javascript_output)) 2> /dev/null || true
2389-
2390-lander-styles: force-styles node_modules $(scss_output)
2391- git update-index -q --no-assume-unchanged $(strip $(scss_output)) 2> /dev/null || true
2392- git add -f $(strip $(scss_output)) 2> /dev/null || true
2393-
2394-# The $(subst ...) uses a pattern rule to ensure Webpack runs just once,
2395-# even if all four output files are out-of-date.
2396-$(subst .,%,$(javascript_output)): $(javascript_deps)
2397- bin/yarn build
2398- @touch --no-create $(strip $(javascript_output))
2399- @git update-index -q --assume-unchanged $(strip $(javascript_output)) 2> /dev/null || true
2400-
2401-clean-javascript:
2402- $(RM) -r src/maasserver/static/js/bundle
2403-
2404-watch-javascript:
2405- bin/yarn watch
2406-
2407-clean: stop clean-failed
2408- find . -type f -name '*.py[co]' -print0 | xargs -r0 $(RM)
2409- find . -type d -name '__pycache__' -print0 | xargs -r0 $(RM) -r
2410- find . -type f -name '*~' -print0 | xargs -r0 $(RM)
2411- $(RM) -r media/demo/* media/development media/development.*
2412- $(RM) src/maasserver/data/templates.py
2413- $(RM) *.log
2414- $(RM) docs/api.rst
2415- $(RM) -r docs/_autosummary docs/_build
2416- $(RM) -r man/.doctrees
2417- $(RM) .coverage .coverage.* coverage.xml
2418- $(RM) -r coverage
2419- $(RM) -r .hypothesis
2420- $(RM) -r bin include lib local node_modules
2421- $(RM) -r eggs develop-eggs
2422- $(RM) -r build dist logs/* parts
2423- $(RM) tags TAGS .installed.cfg
2424- $(RM) -r *.egg *.egg-info src/*.egg-info
2425- $(RM) -r services/*/supervise
2426- $(RM) -r .run .run-e2e
2427- $(RM) -r .idea
2428- $(RM) xunit.*.xml
2429- $(RM) .failed
2430-
2431-clean+db: clean
2432- while fuser db --kill -TERM; do sleep 1; done
2433- $(RM) -r db
2434- $(RM) .db.lock
2435-
2436-distclean: clean
2437- $(warning 'distclean' is deprecated; use 'clean')
2438-
2439-harness: bin/maas-region bin/database
2440- $(dbrun) bin/maas-region shell \
2441- --settings=maasserver.djangosettings.demo
2442-
2443-dbharness: bin/database
2444- bin/database --preserve shell
2445-
2446-syncdb: bin/maas-region bin/database
2447- $(dbrun) bin/maas-region dbupgrade
2448-
2449-define phony_targets
2450- build
2451- check
2452- clean
2453- clean+db
2454- clean-failed
2455- clean-javascript
2456- clean-styles
2457- configure-buildout
2458- coverage-report
2459- dbharness
2460- distclean
2461- doc
2462- doc-browse
2463- force-styles
2464- force-javascript
2465- force-yarn-update
2466- format
2467- harness
2468- install-dependencies
2469- javascript
2470- lander-javascript
2471- lander-styles
2472- lint
2473- lint-css
2474- lint-doc
2475- lint-js
2476- lint-py
2477- lint-py-complexity
2478- lint-py-imports
2479- lint-rst
2480- lxd
2481- man
2482- print-%
2483- sampledata
2484- smoke
2485- styles
2486- sudoers
2487- syncdb
2488- sync-dev-snap
2489- test
2490- test+lxd
2491- test-failed
2492- test-initial-data
2493- test-serial
2494- test-serial+coverage
2495-endef
2496-
2497-#
2498-# Development services.
2499-#
2500-
2501-service_names_region := database dns regiond reloader
2502-service_names_rack := http rackd reloader
2503-service_names_all := $(service_names_region) $(service_names_rack)
2504-
2505-# The following template is intended to be used with `call`, and it
2506-# accepts a single argument: a target name. The target name must
2507-# correspond to a service action (see "Pseudo-magic targets" below). A
2508-# region- and rack-specific variant of the target will be created, in
2509-# addition to the target itself. These can be used to apply the service
2510-# action to the region services, the rack services, or all services, at
2511-# the same time.
2512-define service_template
2513-$(1)-region: $(patsubst %,services/%/@$(1),$(service_names_region))
2514-$(1)-rack: $(patsubst %,services/%/@$(1),$(service_names_rack))
2515-$(1): $(1)-region $(1)-rack
2516-phony_services_targets += $(1)-region $(1)-rack $(1)
2517-endef
2518-
2519-# Expand out aggregate service targets using `service_template`.
2520-$(eval $(call service_template,pause))
2521-$(eval $(call service_template,restart))
2522-$(eval $(call service_template,start))
2523-$(eval $(call service_template,status))
2524-$(eval $(call service_template,stop))
2525-$(eval $(call service_template,supervise))
2526-
2527-# The `run` targets do not fit into the mould of the others.
2528-run-region:
2529- @services/run $(service_names_region)
2530-run-rack:
2531- @services/run $(service_names_rack)
2532-run:
2533- @services/run $(service_names_all)
2534-
2535-phony_services_targets += run-region run-rack run
2536-
2537-phony_services_targets += run+regiond
2538-
2539-# Convenient variables and functions for service control.
2540-
2541-setlock = $(call available,setlock,daemontools)
2542-supervise = $(call available,supervise,daemontools)
2543-svc = $(call available,svc,daemontools)
2544-svok = $(call available,svok,daemontools)
2545-svstat = $(call available,svstat,daemontools)
2546-
2547-service_lock = $(setlock) -n /run/lock/maas.dev.$(firstword $(1))
2548-
2549-# Pseudo-magic targets for controlling individual services.
2550-
2551-services/%/@run: services/%/@stop services/%/@deps
2552- @$(call service_lock, $*) services/$*/run
2553-
2554-services/%/@start: services/%/@supervise
2555- @$(svc) -u $(@D)
2556-
2557-services/%/@pause: services/%/@supervise
2558- @$(svc) -d $(@D)
2559-
2560-services/%/@status:
2561- @$(svstat) $(@D)
2562-
2563-services/%/@restart: services/%/@supervise
2564- @$(svc) -du $(@D)
2565-
2566-services/%/@stop:
2567- @if $(svok) $(@D); then $(svc) -dx $(@D); fi
2568- @while $(svok) $(@D); do sleep 0.1; done
2569-
2570-services/%/@supervise: services/%/@deps
2571- @mkdir -p logs/$*
2572- @touch $(@D)/down
2573- @if ! $(svok) $(@D); then \
2574- logdir=$(CURDIR)/logs/$* \
2575- $(call service_lock, $*) $(supervise) $(@D) & fi
2576- @while ! $(svok) $(@D); do sleep 0.1; done
2577-
2578-# Dependencies for individual services.
2579-
2580-services/dns/@deps: bin/py bin/maas-common
2581-
2582-services/database/@deps: bin/database
2583-
2584-services/http/@deps: bin/py
2585-
2586-services/rackd/@deps: bin/rackd bin/maas-rack bin/maas-common
2587-
2588-services/reloader/@deps:
2589-
2590-services/regiond/@deps: bin/maas-region bin/maas-rack bin/maas-common
2591-
2592-#
2593-# Package building
2594-#
2595-
2596-# This ought to be as simple as using
2597-# gbp buildpackage --git-debian-branch=packaging
2598-# but it is not: without investing more time, we manually pre-build the source
2599-# tree and run debuild.
2600-
2601-packaging-repo = https://git.launchpad.net/maas/
2602-packaging-branch = "packaging"
2603-
2604-packaging-build-area := $(abspath ../build-area)
2605-packaging-version = $(shell \
2606- utilities/calc-snap-version | sed s/[-]snap//)
2607-tmp_changelog := $(shell tempfile)
2608-packaging-dir := maas_$(packaging-version)
2609-packaging-orig-targz := $(packaging-dir).orig.tar.gz
2610-
2611--packaging-clean:
2612- rm -rf $(packaging-build-area)
2613- mkdir -p $(packaging-build-area)
2614-
2615--packaging-export-orig: $(packaging-build-area)
2616- git archive --format=tar.gz $(packaging-export-extra) \
2617- --prefix=$(packaging-dir)/ \
2618- -o $(packaging-build-area)/$(packaging-orig-targz) HEAD
2619-
2620--packaging-export-orig-uncommitted: $(packaging-build-area)
2621- git ls-files --others --exclude-standard --cached | grep -v '^debian' | \
2622- xargs tar --transform 's,^,$(packaging-dir)/,' -czf $(packaging-build-area)/$(packaging-orig-targz)
2623-
2624--packaging-export: -packaging-export-orig$(if $(export-uncommitted),-uncommitted,)
2625-
2626--package-tree: -packaging-export
2627- (cd $(packaging-build-area) && tar xfz $(packaging-orig-targz))
2628- (cp -r debian $(packaging-build-area)/$(packaging-dir))
2629- echo "maas ($(packaging-version)-0ubuntu1) UNRELEASED; urgency=medium" \
2630- > $(tmp_changelog)
2631- tail -n +2 debian/changelog >> $(tmp_changelog)
2632- mv $(tmp_changelog) $(packaging-build-area)/$(packaging-dir)/debian/changelog
2633-
2634-package: javascript -packaging-clean -package-tree
2635- (cd $(packaging-build-area)/$(packaging-dir) && debuild -uc -us)
2636- @echo Binary packages built, see $(packaging-build-area).
2637-
2638-# To build binary packages from uncommitted changes call "make package-dev".
2639-package-dev:
2640- make export-uncommitted=yes package
2641-
2642-source-package: -package-tree
2643- (cd $(packaging-build-area)/$(packaging-dir) && debuild -S -uc -us)
2644- @echo Source package built, see $(packaging-build-area).
2645-
2646-# To build source packages from uncommitted changes call "make package-dev".
2647-source-package-dev:
2648- make export-uncommitted=yes source-package
2649-
2650-# To rebuild packages (i.e. from a clean slate):
2651-package-rebuild: package-clean package
2652-
2653-package-dev-rebuild: package-clean package-dev
2654-
2655-source-package-rebuild: source-package-clean source-package
2656-
2657-source-package-dev-rebuild: source-package-clean source-package-dev
2658-
2659-# To clean built packages away:
2660-package-clean: patterns := *.deb *.udeb *.dsc *.build *.changes
2661-package-clean: patterns += *.debian.tar.xz *.orig.tar.gz
2662-package-clean:
2663- @$(RM) -v $(addprefix $(packaging-build-area)/,$(patterns))
2664-
2665-source-package-clean: patterns := *.dsc *.build *.changes
2666-source-package-clean: patterns += *.debian.tar.xz *.orig.tar.gz
2667-source-package-clean:
2668- @$(RM) -v $(addprefix $(packaging-build-area)/,$(patterns))
2669-
2670-
2671-# Debugging target. Allows printing of any variable.
2672-# As an example, try:
2673-# make print-scss_input
2674-print-%:
2675- @echo $* = $($*)
2676-
2677-define phony_package_targets
2678- -packaging-export-orig
2679- -packaging-export-orig-uncommitted
2680- -packaging-export
2681- -packaging-fetch
2682- -packaging-pull
2683- -packaging-refresh
2684- -package-tree
2685- package
2686- package-clean
2687- package-dev
2688- package-dev-rebuild
2689- package-rebuild
2690- source-package
2691- source-package-clean
2692- source-package-dev
2693- source-package-dev-rebuild
2694- source-package-rebuild
2695-endef
2696-
2697-#
2698-# Snap building
2699-#
2700-
2701-snap-clean:
2702- $(snapcraft) clean
2703-
2704-snap:
2705- $(snapcraft)
2706-
2707-define phony_snap_targets
2708- snap
2709- snap-clean
2710-endef
2711-
2712-
2713-#
2714-# Helpers for using the snap for development testing.
2715-#
2716-
2717-
2718-build/dev-snap: ## Check out a clean version of the working tree.
2719- git checkout-index -a --prefix build/dev-snap/
2720-
2721-build/dev-snap/prime: build/dev-snap
2722- cd build/dev-snap && $(snapcraft) prime --destructive-mode
2723-
2724-sync-dev-snap: build/dev-snap/prime
2725- rsync -v --exclude 'maastesting' --exclude 'tests' --exclude 'testing' \
2726- --exclude '*.pyc' --exclude '__pycache__' -r -u -l -t -W -L \
2727- src/ build/dev-snap/prime/lib/python3.6/site-packages/
2728- rsync -v -r -u -l -t -W -L \
2729- src/maasserver/static/ build/dev-snap/prime/usr/share/maas/web/static/
2730-
2731-#
2732-# Phony stuff.
2733-#
2734-
2735-define phony
2736- $(phony_package_targets)
2737- $(phony_services_targets)
2738- $(phony_snap_targets)
2739- $(phony_targets)
2740-endef
2741-
2742-phony := $(sort $(strip $(phony)))
2743-
2744-.PHONY: $(phony) FORCE
2745-
2746-#
2747-# Secondary stuff.
2748-#
2749-# These are intermediate files that we want to keep around in the event
2750-# that they get built. By declaring them here we're also telling Make
2751-# that their absense is okay if a rule target is newer than the rule's
2752-# other prerequisites; i.e. don't build them.
2753-#
2754-# For example, converting foo.scss to foo.css might require bin/node-sass. If
2755-# foo.css is newer than foo.scss we know that we don't need to perform that
2756-# conversion, and hence don't need bin/node-sass. We declare bin/node-sass as
2757-# secondary so that Make knows this too.
2758-#
2759-
2760-define secondary_binaries
2761- bin/py bin/buildout
2762- bin/node-sass
2763- bin/sphinx bin/sphinx-build
2764-endef
2765-
2766-secondary = $(sort $(strip $(secondary_binaries)))
2767-
2768-.SECONDARY: $(secondary)
2769-
2770-#
2771-# Functions.
2772-#
2773-
2774-# Check if a command is found on PATH. Raise an error if not, citing
2775-# the package to install. Return the command otherwise.
2776-# Usage: $(call available,<command>,<package>)
2777-define available
2778- $(if $(shell which $(1)),$(1),$(error $(1) not found; \
2779- install it with 'sudo apt-get install $(2)'))
2780-endef
2781diff --git a/README.rst b/README.rst
2782deleted file mode 100644
2783index df14155..0000000
2784--- a/README.rst
2785+++ /dev/null
2786@@ -1,30 +0,0 @@
2787-************************
2788-MAAS: Metal as a Service
2789-************************
2790-
2791-Metal as a Service -- MAAS -- lets you treat physical servers like
2792-virtual machines in the cloud. Rather than having to manage each
2793-server individually, MAAS turns your bare metal into an elastic
2794-cloud-like resource.
2795-
2796-What does that mean in practice? Tell MAAS about the machines you want
2797-it to manage and it will boot them, check the hardware's okay, and
2798-have them waiting for when you need them. You can then pull nodes up,
2799-tear them down and redeploy them at will; just as you can with virtual
2800-machines in the cloud.
2801-
2802-When you're ready to deploy a service, MAAS gives Juju the nodes it
2803-needs to power that service. It's as simple as that: no need to
2804-manually provision, check and, afterwards, clean-up. As your needs
2805-change, you can easily scale services up or down. Need more power for
2806-your Hadoop cluster for a few hours? Simply tear down one of your Nova
2807-compute nodes and redeploy it to Hadoop. When you're done, it's just
2808-as easy to give the node back to Nova.
2809-
2810-MAAS is ideal where you want the flexibility of the cloud, and the
2811-hassle-free power of Juju charms, but you need to deploy to bare
2812-metal.
2813-
2814-For more information see the `MAAS guide`_.
2815-
2816-.. _MAAS guide: http://maas.io/
2817diff --git a/bootstrap-buildout.py b/bootstrap-buildout.py
2818deleted file mode 100644
2819index 69bf941..0000000
2820--- a/bootstrap-buildout.py
2821+++ /dev/null
2822@@ -1,210 +0,0 @@
2823-##############################################################################
2824-#
2825-# Copyright (c) 2006 Zope Foundation and Contributors.
2826-# All Rights Reserved.
2827-#
2828-# This software is subject to the provisions of the Zope Public License,
2829-# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution.
2830-# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED
2831-# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2832-# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
2833-# FOR A PARTICULAR PURPOSE.
2834-#
2835-##############################################################################
2836-"""Bootstrap a buildout-based project
2837-
2838-Simply run this script in a directory containing a buildout.cfg.
2839-The script accepts buildout command-line options, so you can
2840-use the -c option to specify an alternate configuration file.
2841-"""
2842-
2843-from optparse import OptionParser
2844-import os
2845-import shutil
2846-import sys
2847-import tempfile
2848-
2849-
2850-__version__ = '2015-07-01'
2851-# See zc.buildout's changelog if this version is up to date.
2852-
2853-tmpeggs = tempfile.mkdtemp(prefix='bootstrap-')
2854-
2855-usage = '''\
2856-[DESIRED PYTHON FOR BUILDOUT] bootstrap.py [options]
2857-
2858-Bootstraps a buildout-based project.
2859-
2860-Simply run this script in a directory containing a buildout.cfg, using the
2861-Python that you want bin/buildout to use.
2862-
2863-Note that by using --find-links to point to local resources, you can keep
2864-this script from going over the network.
2865-'''
2866-
2867-parser = OptionParser(usage=usage)
2868-parser.add_option("--version",
2869- action="store_true", default=False,
2870- help=("Return bootstrap.py version."))
2871-parser.add_option("-t", "--accept-buildout-test-releases",
2872- dest='accept_buildout_test_releases',
2873- action="store_true", default=False,
2874- help=("Normally, if you do not specify a --version, the "
2875- "bootstrap script and buildout gets the newest "
2876- "*final* versions of zc.buildout and its recipes and "
2877- "extensions for you. If you use this flag, "
2878- "bootstrap and buildout will get the newest releases "
2879- "even if they are alphas or betas."))
2880-parser.add_option("-c", "--config-file",
2881- help=("Specify the path to the buildout configuration "
2882- "file to be used."))
2883-parser.add_option("-f", "--find-links",
2884- help=("Specify a URL to search for buildout releases"))
2885-parser.add_option("--allow-site-packages",
2886- action="store_true", default=False,
2887- help=("Let bootstrap.py use existing site packages"))
2888-parser.add_option("--buildout-version",
2889- help="Use a specific zc.buildout version")
2890-parser.add_option("--setuptools-version",
2891- help="Use a specific setuptools version")
2892-parser.add_option("--setuptools-to-dir",
2893- help=("Allow for re-use of existing directory of "
2894- "setuptools versions"))
2895-
2896-options, args = parser.parse_args()
2897-if options.version:
2898- print("bootstrap.py version %s" % __version__)
2899- sys.exit(0)
2900-
2901-
2902-######################################################################
2903-# load/install setuptools
2904-
2905-try:
2906- from urllib.request import urlopen
2907-except ImportError:
2908- from urllib2 import urlopen
2909-
2910-ez = {}
2911-if os.path.exists('ez_setup.py'):
2912- exec(open('ez_setup.py').read(), ez)
2913-else:
2914- exec(urlopen('https://bootstrap.pypa.io/ez_setup.py').read(), ez)
2915-
2916-if not options.allow_site_packages:
2917- # ez_setup imports site, which adds site packages
2918- # this will remove them from the path to ensure that incompatible versions
2919- # of setuptools are not in the path
2920- import site
2921- # inside a virtualenv, there is no 'getsitepackages'.
2922- # We can't remove these reliably
2923- if hasattr(site, 'getsitepackages'):
2924- for sitepackage_path in site.getsitepackages():
2925- # Strip all site-packages directories from sys.path that
2926- # are not sys.prefix; this is because on Windows
2927- # sys.prefix is a site-package directory.
2928- if sitepackage_path != sys.prefix:
2929- sys.path[:] = [x for x in sys.path
2930- if sitepackage_path not in x]
2931-
2932-setup_args = dict(to_dir=tmpeggs, download_delay=0)
2933-
2934-if options.setuptools_version is not None:
2935- setup_args['version'] = options.setuptools_version
2936-if options.setuptools_to_dir is not None:
2937- setup_args['to_dir'] = options.setuptools_to_dir
2938-
2939-ez['use_setuptools'](**setup_args)
2940-import setuptools
2941-import pkg_resources
2942-
2943-# This does not (always?) update the default working set. We will
2944-# do it.
2945-for path in sys.path:
2946- if path not in pkg_resources.working_set.entries:
2947- pkg_resources.working_set.add_entry(path)
2948-
2949-######################################################################
2950-# Install buildout
2951-
2952-ws = pkg_resources.working_set
2953-
2954-setuptools_path = ws.find(
2955- pkg_resources.Requirement.parse('setuptools')).location
2956-
2957-# Fix sys.path here as easy_install.pth added before PYTHONPATH
2958-cmd = [sys.executable, '-c',
2959- 'import sys; sys.path[0:0] = [%r]; ' % setuptools_path +
2960- 'from setuptools.command.easy_install import main; main()',
2961- '-mZqNxd', tmpeggs]
2962-
2963-find_links = os.environ.get(
2964- 'bootstrap-testing-find-links',
2965- options.find_links or
2966- ('http://downloads.buildout.org/'
2967- if options.accept_buildout_test_releases else None)
2968- )
2969-if find_links:
2970- cmd.extend(['-f', find_links])
2971-
2972-requirement = 'zc.buildout'
2973-version = options.buildout_version
2974-if version is None and not options.accept_buildout_test_releases:
2975- # Figure out the most recent final version of zc.buildout.
2976- import setuptools.package_index
2977- _final_parts = '*final-', '*final'
2978-
2979- def _final_version(parsed_version):
2980- try:
2981- return not parsed_version.is_prerelease
2982- except AttributeError:
2983- # Older setuptools
2984- for part in parsed_version:
2985- if (part[:1] == '*') and (part not in _final_parts):
2986- return False
2987- return True
2988-
2989- index = setuptools.package_index.PackageIndex(
2990- search_path=[setuptools_path])
2991- if find_links:
2992- index.add_find_links((find_links,))
2993- req = pkg_resources.Requirement.parse(requirement)
2994- if index.obtain(req) is not None:
2995- best = []
2996- bestv = None
2997- for dist in index[req.project_name]:
2998- distv = dist.parsed_version
2999- if _final_version(distv):
3000- if bestv is None or distv > bestv:
3001- best = [dist]
3002- bestv = distv
3003- elif distv == bestv:
3004- best.append(dist)
3005- if best:
3006- best.sort()
3007- version = best[-1].version
3008-if version:
3009- requirement = '=='.join((requirement, version))
3010-cmd.append(requirement)
3011-
3012-import subprocess
3013-if subprocess.call(cmd) != 0:
3014- raise Exception(
3015- "Failed to execute command:\n%s" % repr(cmd)[1:-1])
3016-
3017-######################################################################
3018-# Import and run buildout
3019-
3020-ws.add_entry(tmpeggs)
3021-ws.require(requirement)
3022-import zc.buildout.buildout
3023-
3024-if not [a for a in args if '=' not in a]:
3025- args.append('bootstrap')
3026-
3027-# if -c was provided, we push it back into args for buildout' main function
3028-if options.config_file is not None:
3029- args[0:0] = ['-c', options.config_file]
3030-
3031-zc.buildout.buildout.main(args)
3032-shutil.rmtree(tmpeggs)
3033diff --git a/buildout.cfg b/buildout.cfg
3034deleted file mode 100644
3035index 40110f9..0000000
3036--- a/buildout.cfg
3037+++ /dev/null
3038@@ -1,403 +0,0 @@
3039-[buildout]
3040-parts =
3041- cli
3042- cli-test
3043- config-test
3044- coverage
3045- flake8
3046- parallel-test
3047- rack
3048- rack-test
3049- region
3050- region-test
3051- region-test-legacy
3052- repl
3053- sphinx
3054- testing-test
3055-versions = versions
3056-extends = versions.cfg
3057-offline = false
3058-newest = false
3059-
3060-# Uncomment the following two lines and set allow-picked-versions=true
3061-# to automatically update versions.cfg when building recipes.
3062-# extensions = buildout-versions
3063-# buildout_versions_file = versions.cfg
3064-
3065-prefer-final = true
3066-allow-picked-versions = false
3067-
3068-[common]
3069-extra-paths =
3070- ${buildout:directory}/etc
3071- ${buildout:directory}/src
3072- ${buildout:directory}
3073-test-eggs =
3074- blessings
3075- coverage
3076- fixtures
3077- hypothesis
3078- ipdb
3079- junitxml
3080- nose
3081- nose-timer
3082- postgresfixture
3083- python-subunit
3084- testresources
3085- testscenarios
3086- testtools
3087-initialization =
3088- ${common:path-munge}
3089- ${common:warnings}
3090- ${common:environment}
3091-path-munge =
3092- import pathlib, sys
3093- # Eliminate argparse usage outside of the standard library. This is
3094- # needed because some deps <cough>unittest2<cough> explicitly require
3095- # argparse, which zc.buildout then dutifully installs. Unfortunately
3096- # argparse 1.1 from PyPI differs substantially to argparse 1.1 in the
3097- # standard library. For consistency we want the latter.
3098- p_argparse_egg = lambda path: pathlib.Path(path).match("*/argparse-*.egg")
3099- sys.path[:] = [path for path in sys.path if not p_argparse_egg(path)]
3100- # Sort system paths towards the end of sys.path so that deps defined
3101- # here are used in preference to those installed system-wide.
3102- p_sys_prefix = lambda path, p=pathlib.Path: p(sys.prefix) in p(path).parents
3103- sys.path.sort(key=p_sys_prefix)
3104-environment =
3105- from os import environ
3106- environ.setdefault("MAAS_ROOT", "${buildout:directory}/.run")
3107-warnings =
3108- from warnings import filterwarnings
3109- filterwarnings("ignore", category=RuntimeWarning, module="pkg_resources")
3110-asyncio-reactor =
3111- # Install the asyncio reactor with uvloop.
3112- import asyncio
3113- import uvloop
3114- from twisted.internet import asyncioreactor, error
3115- asyncio.set_event_loop_policy(uvloop.EventLoopPolicy())
3116- try:
3117- asyncioreactor.install()
3118- except error.ReactorAlreadyInstalledError:
3119- pass
3120-inject-test-options =
3121- # When running tests from a console show only dots, but when running
3122- # headless increase verbosity so we can see the test being run from a
3123- # log file. An `options` list must be defined ahead of the use of this
3124- # snippet.
3125- options += (
3126- ["--verbosity=1"]
3127- if sys.stdout.isatty() else
3128- ["--verbosity=2"]
3129- )
3130- sys.argv[1:1] = options
3131-
3132-[database]
3133-recipe = zc.recipe.egg
3134-eggs = postgresfixture
3135-extra-paths =
3136- ${common:extra-paths}
3137-initialization =
3138- ${common:path-munge}
3139-interpreter =
3140-entry-points = database=postgresfixture.main:main
3141-scripts = database
3142-
3143-[parallel-test]
3144-recipe = zc.recipe.egg
3145-eggs =
3146- ${common:test-eggs}
3147-entry-points =
3148- test.parallel=maastesting.parallel:main
3149-scripts = test.parallel
3150-extra-paths =
3151- ${common:extra-paths}
3152-initialization =
3153- ${common:initialization}
3154- ${common:asyncio-reactor}
3155-
3156-[region]
3157-recipe = zc.recipe.egg
3158-test-eggs =
3159- ${common:test-eggs}
3160- selenium
3161-eggs =
3162- ${region:test-eggs}
3163-entry-points =
3164- maas-region=maasserver:execute_from_command_line
3165- regiond=maasserver.server:run
3166-initialization =
3167- ${common:initialization}
3168- environ.setdefault("DJANGO_SETTINGS_MODULE", "maasserver.djangosettings.development")
3169- environ.setdefault("MAAS_DEBUG_QUERIES", "1")
3170-scripts =
3171- maas-region
3172- regiond
3173-extra-paths =
3174- ${common:extra-paths}
3175-
3176-[region-test]
3177-recipe = zc.recipe.egg
3178-eggs =
3179- ${region:eggs}
3180- ${common:test-eggs}
3181-entry-points =
3182- test.region=maastesting.noseplug:main
3183-initialization =
3184- ${region:initialization}
3185- ${common:asyncio-reactor}
3186- # Prevent query logging as it affects the tests.
3187- if 'MAAS_DEBUG_QUERIES' in environ:
3188- del environ['MAAS_DEBUG_QUERIES']
3189- options = [
3190- "--with-crochet",
3191- "--with-resources",
3192- "--with-scenarios",
3193- "--with-select",
3194- "--select-dir=src/maasserver",
3195- "--select-dir=src/metadataserver",
3196- "--cover-package=maas,maasserver,metadataserver",
3197- "--cover-branches",
3198- # Reduce the logging level to INFO here as
3199- # DebuggingLoggerMiddleware logs the content of all the
3200- # requests at DEBUG level: we don't want this in the
3201- # tests as it's too verbose.
3202- "--logging-level=INFO",
3203- "--logging-clear-handlers",
3204- # Do not run tests tagged "legacy".
3205- "-a", "!legacy",
3206- ]
3207- ${common:inject-test-options}
3208- # Configure logging. TODO: Do this in a plugin.
3209- from provisioningserver import logger
3210- logger.configure(mode=logger.LoggingMode.COMMAND)
3211- # Limit concurrency in all thread-pools to ONE.
3212- from maasserver.utils import threads
3213- threads.install_default_pool(maxthreads=1)
3214- threads.install_database_unpool(maxthreads=1)
3215- # Disable all database connections in the reactor.
3216- from maasserver.utils import orm
3217- from twisted.internet import reactor
3218- assert not reactor.running, "The reactor has been started too early."
3219- reactor.callFromThread(orm.disable_all_database_connections)
3220- # Last and least, configure Django.
3221- import django; django.setup()
3222-scripts = test.region
3223-extra-paths =
3224- ${region:extra-paths}
3225-
3226-[region-test-legacy]
3227-recipe = zc.recipe.egg
3228-eggs =
3229- ${region:eggs}
3230-entry-points =
3231- test.region.legacy=maasserver:execute_from_command_line
3232-initialization =
3233- ${region:initialization}
3234- ${common:asyncio-reactor}
3235- environ.setdefault("MAAS_PREVENT_MIGRATIONS", "1")
3236- # Prevent query logging as it affects the tests.
3237- if 'MAAS_DEBUG_QUERIES' in environ:
3238- del environ['MAAS_DEBUG_QUERIES']
3239- options = [
3240- "test",
3241- "--noinput",
3242- "--with-crochet",
3243- "--with-scenarios",
3244- "--with-select",
3245- "--select-dir=src/maasserver",
3246- "--select-dir=src/metadataserver",
3247- "--cover-package=maas,maasserver,metadataserver",
3248- "--cover-branches",
3249- # Reduce the logging level to INFO here as
3250- # DebuggingLoggerMiddleware logs the content of all the
3251- # requests at DEBUG level: we don't want this in the
3252- # tests as it's too verbose.
3253- "--logging-level=INFO",
3254- "--logging-clear-handlers",
3255- # Run only tests tagged "legacy".
3256- "-a", "legacy",
3257- ]
3258- ${common:inject-test-options}
3259-scripts = test.region.legacy
3260-extra-paths =
3261- ${region:extra-paths}
3262-
3263-[cli]
3264-recipe = zc.recipe.egg
3265-eggs =
3266- ${region:eggs}
3267-initialization =
3268- ${common:path-munge}
3269-entry-points =
3270- maas=maascli:main
3271-extra-paths =
3272- ${common:extra-paths}
3273-scripts =
3274- maas
3275-
3276-[cli-test]
3277-recipe = zc.recipe.egg
3278-eggs =
3279- ${cli:eggs}
3280- ${common:test-eggs}
3281-entry-points =
3282- test.cli=maastesting.noseplug:main
3283-initialization =
3284- ${common:path-munge}
3285- ${common:warnings}
3286- options = [
3287- "--with-resources",
3288- "--with-scenarios",
3289- "--with-select",
3290- "--select-dir=src/apiclient",
3291- "--select-dir=src/maascli",
3292- "--cover-package=apiclient,maascli",
3293- "--cover-branches",
3294- ]
3295- ${common:inject-test-options}
3296-extra-paths = ${cli:extra-paths}
3297-scripts =
3298- test.cli
3299-
3300-[js-test]
3301-recipe = zc.recipe.egg
3302-eggs =
3303- ${common:test-eggs}
3304-entry-points =
3305- test.js=maastesting.karma:run_karma
3306-extra-paths =
3307- ${common:extra-paths}
3308-scripts =
3309- test.js
3310-initialization =
3311- ${common:initialization}
3312-
3313-[testing-test]
3314-recipe = zc.recipe.egg
3315-eggs =
3316- ${common:test-eggs}
3317-entry-points =
3318- test.testing=maastesting.noseplug:main
3319-initialization =
3320- ${common:path-munge}
3321- ${common:warnings}
3322- ${common:asyncio-reactor}
3323- options = [
3324- "--with-resources",
3325- "--with-scenarios",
3326- "--with-select",
3327- "--select-dir=src/maastesting",
3328- "--cover-package=maastesting",
3329- "--cover-branches",
3330- ]
3331- ${common:inject-test-options}
3332-extra-paths =
3333- ${common:extra-paths}
3334-scripts =
3335- test.testing
3336-
3337-[rack]
3338-recipe = zc.recipe.egg
3339-eggs =
3340- ${common:test-eggs}
3341-entry-points =
3342- maas-rack=provisioningserver.__main__:main
3343- maas-common=provisioningserver.__main__:main
3344- rackd=provisioningserver.server:run
3345-extra-paths =
3346- ${common:extra-paths}
3347-scripts =
3348- maas-rack
3349- maas-common
3350- rackd
3351-initialization =
3352- ${common:initialization}
3353-
3354-[rack-test]
3355-recipe = zc.recipe.egg
3356-eggs =
3357- ${rack:eggs}
3358- ${common:test-eggs}
3359-entry-points =
3360- test.rack=maastesting.noseplug:main
3361-initialization =
3362- ${common:initialization}
3363- ${common:asyncio-reactor}
3364- options = [
3365- "--with-crochet",
3366- "--crochet-no-setup",
3367- "--with-resources",
3368- "--with-scenarios",
3369- "--with-select",
3370- "--select-dir=src/provisioningserver",
3371- "--cover-package=provisioningserver",
3372- "--cover-branches",
3373- ]
3374- ${common:inject-test-options}
3375-extra-paths = ${rack:extra-paths}
3376-scripts =
3377- test.rack
3378-
3379-[e2e-test]
3380-recipe = zc.recipe.egg
3381-eggs =
3382- ${region:test-eggs}
3383-entry-points =
3384- test.e2e=maastesting.protractor.runner:run_protractor
3385-extra-paths =
3386- ${common:extra-paths}
3387-scripts =
3388- test.e2e
3389-initialization =
3390- ${common:path-munge}
3391- from os import environ
3392- environ.setdefault("MAAS_ROOT", "${buildout:directory}/.run-e2e")
3393- environ.setdefault("DJANGO_SETTINGS_MODULE", "maasserver.djangosettings.development")
3394- environ.setdefault("DEV_DB_NAME", "test_maas_e2e")
3395- environ.setdefault("MAAS_PREVENT_MIGRATIONS", "1")
3396-
3397-[flake8]
3398-recipe = zc.recipe.egg
3399-eggs =
3400- flake8
3401-entry-points =
3402- flake8=flake8.main.cli:main
3403-initialization =
3404- ${common:path-munge}
3405- ${common:warnings}
3406-
3407-[coverage]
3408-recipe = zc.recipe.egg
3409-eggs =
3410- coverage
3411-entry-points =
3412- coverage=coverage.cmdline:main
3413-initialization =
3414- ${common:path-munge}
3415- ${common:warnings}
3416-scripts =
3417- coverage
3418-
3419-[sphinx]
3420-recipe = collective.recipe.sphinxbuilder
3421-source = ${buildout:directory}/docs
3422-build = ${buildout:directory}/docs/_build
3423-extra-paths = ${common:extra-paths}
3424-eggs =
3425- ${region:eggs}
3426- ${rack:eggs}
3427-
3428-# Convenient REPLs with all eggs available.
3429-[repl]
3430-recipe = zc.recipe.egg
3431-eggs =
3432- ${region:eggs}
3433- ${rack:eggs}
3434- ${common:test-eggs}
3435-extra-paths = ${common:extra-paths}
3436-interpreter = py
3437-scripts = ipy
3438-entry-points =
3439- ipy=IPython.terminal.ipapp:launch_new_instance
3440-initialization =
3441- ${common:initialization}
3442diff --git a/contrib/maas-http.conf b/contrib/maas-http.conf
3443deleted file mode 100644
3444index 9ba82f6..0000000
3445--- a/contrib/maas-http.conf
3446+++ /dev/null
3447@@ -1,39 +0,0 @@
3448-<IfModule mod_ssl.c>
3449- <VirtualHost *:443>
3450- SSLEngine On
3451- # Do not rely on these certificates, generate your own.
3452- SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem
3453- SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key
3454- </VirtualHost>
3455-</IfModule>
3456-
3457-<IfModule mod_expires.c>
3458- <Location /MAAS/>
3459- ExpiresActive On
3460- ExpiresByType text/javascript "access plus 1 hours"
3461- ExpiresByType application/javascript "access plus 1 hours"
3462- ExpiresByType application/x-javascript "access plus 1 hours"
3463- ExpiresByType text/css "access plus 1 hours"
3464- ExpiresByType image/gif "access plus 1 hours"
3465- ExpiresByType image/jpeg "access plus 1 hours"
3466- ExpiresByType image/png "access plus 1 hours"
3467- </Location>
3468-</IfModule>
3469-
3470-<IfModule alias_module>
3471- Alias /MAAS/static/ /usr/share/maas/web/static/
3472-</IfModule>
3473-
3474-<IfModule proxy_module>
3475- ProxyPreserveHost on
3476- ProxyPass /MAAS/ws "ws://localhost:5240/MAAS/ws"
3477- ProxyPass /MAAS/static/ !
3478- ProxyPass /MAAS/ http://localhost:5240/MAAS/
3479- ProxyPass /MAAS http://localhost:5240/MAAS/
3480-</IfModule>
3481-
3482-<IfModule rewrite_module>
3483- RewriteEngine On
3484- # Redirect (permanently) requests for /MAAS to /MAAS/.
3485- RewriteRule ^/MAAS$ %{REQUEST_URI}/ [R=301,L]
3486-</IfModule>
3487diff --git a/contrib/preseeds_v2/commissioning b/contrib/preseeds_v2/commissioning
3488deleted file mode 100644
3489index aa8043e..0000000
3490--- a/contrib/preseeds_v2/commissioning
3491+++ /dev/null
3492@@ -1 +0,0 @@
3493-{{preseed_data}}
3494diff --git a/contrib/preseeds_v2/curtin b/contrib/preseeds_v2/curtin
3495deleted file mode 100644
3496index aa8043e..0000000
3497--- a/contrib/preseeds_v2/curtin
3498+++ /dev/null
3499@@ -1 +0,0 @@
3500-{{preseed_data}}
3501diff --git a/contrib/preseeds_v2/curtin_userdata b/contrib/preseeds_v2/curtin_userdata
3502deleted file mode 100644
3503index 4caddc4..0000000
3504--- a/contrib/preseeds_v2/curtin_userdata
3505+++ /dev/null
3506@@ -1,42 +0,0 @@
3507-#cloud-config
3508-debconf_selections:
3509- maas: |
3510- {{for line in str(curtin_preseed).splitlines()}}
3511- {{line}}
3512- {{endfor}}
3513-early_commands:
3514-{{if third_party_drivers and driver}}
3515- {{py: key_string = ''.join(['\\x%x' % x for x in driver['key_binary']])}}
3516- {{if driver['key_binary'] and driver['repository'] and driver['package']}}
3517- driver_00_get_key: /bin/echo -en '{{key_string}}' > /tmp/maas-{{driver['package']}}.gpg
3518- driver_01_add_key: ["apt-key", "add", "/tmp/maas-{{driver['package']}}.gpg"]
3519- {{endif}}
3520- {{if driver['repository']}}
3521- driver_02_add: ["add-apt-repository", "-y", "deb {{driver['repository']}} {{node.get_distro_series()}} main"]
3522- {{endif}}
3523- {{if driver['package']}}
3524- driver_03_update_install: ["sh", "-c", "apt-get update --quiet && apt-get --assume-yes install {{driver['package']}}"]
3525- {{endif}}
3526- {{if driver['module']}}
3527- driver_04_load: ["sh", "-c", "depmod && modprobe {{driver['module']}} || echo 'Warning: Failed to load module: {{driver['module']}}'"]
3528- {{endif}}
3529-{{else}}
3530- driver_00: ["sh", "-c", "echo third party drivers not installed or necessary."]
3531-{{endif}}
3532-late_commands:
3533- maas: [wget, '--no-proxy', {{node_disable_pxe_url|escape.json}}, '--post-data', {{node_disable_pxe_data|escape.json}}, '-O', '/dev/null']
3534-{{if third_party_drivers and driver}}
3535- {{if driver['key_binary'] and driver['repository'] and driver['package']}}
3536- driver_00_key_get: curtin in-target -- sh -c "/bin/echo -en '{{key_string}}' > /tmp/maas-{{driver['package']}}.gpg"
3537- driver_02_key_add: ["curtin", "in-target", "--", "apt-key", "add", "/tmp/maas-{{driver['package']}}.gpg"]
3538- {{endif}}
3539- {{if driver['repository']}}
3540- driver_03_add: ["curtin", "in-target", "--", "add-apt-repository", "-y", "deb {{driver['repository']}} {{node.get_distro_series()}} main"]
3541- {{endif}}
3542- driver_04_update_install: ["curtin", "in-target", "--", "apt-get", "update", "--quiet"]
3543- {{if driver['package']}}
3544- driver_05_install: ["curtin", "in-target", "--", "apt-get", "-y", "install", "{{driver['package']}}"]
3545- {{endif}}
3546- driver_06_depmod: ["curtin", "in-target", "--", "depmod"]
3547- driver_07_update_initramfs: ["curtin", "in-target", "--", "update-initramfs", "-u"]
3548-{{endif}}
3549diff --git a/contrib/preseeds_v2/curtin_userdata_centos b/contrib/preseeds_v2/curtin_userdata_centos
3550deleted file mode 100644
3551index 3de9c99..0000000
3552--- a/contrib/preseeds_v2/curtin_userdata_centos
3553+++ /dev/null
3554@@ -1,9 +0,0 @@
3555-#cloud-config
3556-debconf_selections:
3557- maas: |
3558- {{for line in str(curtin_preseed).splitlines()}}
3559- {{line}}
3560- {{endfor}}
3561-
3562-late_commands:
3563- maas: [wget, '--no-proxy', '{{node_disable_pxe_url}}', '--post-data', '{{node_disable_pxe_data}}', '-O', '/dev/null']
3564diff --git a/contrib/preseeds_v2/curtin_userdata_custom b/contrib/preseeds_v2/curtin_userdata_custom
3565deleted file mode 100644
3566index 3de9c99..0000000
3567--- a/contrib/preseeds_v2/curtin_userdata_custom
3568+++ /dev/null
3569@@ -1,9 +0,0 @@
3570-#cloud-config
3571-debconf_selections:
3572- maas: |
3573- {{for line in str(curtin_preseed).splitlines()}}
3574- {{line}}
3575- {{endfor}}
3576-
3577-late_commands:
3578- maas: [wget, '--no-proxy', '{{node_disable_pxe_url}}', '--post-data', '{{node_disable_pxe_data}}', '-O', '/dev/null']
3579diff --git a/contrib/preseeds_v2/curtin_userdata_suse b/contrib/preseeds_v2/curtin_userdata_suse
3580deleted file mode 100644
3581index 3de9c99..0000000
3582--- a/contrib/preseeds_v2/curtin_userdata_suse
3583+++ /dev/null
3584@@ -1,9 +0,0 @@
3585-#cloud-config
3586-debconf_selections:
3587- maas: |
3588- {{for line in str(curtin_preseed).splitlines()}}
3589- {{line}}
3590- {{endfor}}
3591-
3592-late_commands:
3593- maas: [wget, '--no-proxy', '{{node_disable_pxe_url}}', '--post-data', '{{node_disable_pxe_data}}', '-O', '/dev/null']
3594diff --git a/contrib/preseeds_v2/curtin_userdata_windows b/contrib/preseeds_v2/curtin_userdata_windows
3595deleted file mode 100644
3596index 77e4a65..0000000
3597--- a/contrib/preseeds_v2/curtin_userdata_windows
3598+++ /dev/null
3599@@ -1,11 +0,0 @@
3600-#cloud-config
3601-debconf_selections:
3602- maas: |
3603- {{for line in str(curtin_preseed).splitlines()}}
3604- {{line}}
3605- {{endfor}}
3606-
3607-late_commands:
3608- maas: [wget, '--no-proxy', '{{node_disable_pxe_url}}', '--post-data', '{{node_disable_pxe_data}}', '-O', '/dev/null']
3609-
3610-license_key: {{node.get_effective_license_key()}}
3611diff --git a/contrib/preseeds_v2/enlist b/contrib/preseeds_v2/enlist
3612deleted file mode 100644
3613index aa8043e..0000000
3614--- a/contrib/preseeds_v2/enlist
3615+++ /dev/null
3616@@ -1 +0,0 @@
3617-{{preseed_data}}
3618diff --git a/contrib/pycharm/codeStyleSettings.xml b/contrib/pycharm/codeStyleSettings.xml
3619deleted file mode 100644
3620index 7fb8ed0..0000000
3621--- a/contrib/pycharm/codeStyleSettings.xml
3622+++ /dev/null
3623@@ -1,13 +0,0 @@
3624-<?xml version="1.0" encoding="UTF-8"?>
3625-<project version="4">
3626- <component name="ProjectCodeStyleSettingsManager">
3627- <option name="PER_PROJECT_SETTINGS">
3628- <value>
3629- <XML>
3630- <option name="XML_LEGACY_SETTINGS_IMPORTED" value="true" />
3631- </XML>
3632- </value>
3633- </option>
3634- <option name="PREFERRED_PROJECT_CODE_STYLE" value="Default (1)" />
3635- </component>
3636-</project>
3637\ No newline at end of file
3638diff --git a/contrib/pycharm/encodings.xml b/contrib/pycharm/encodings.xml
3639deleted file mode 100644
3640index f758959..0000000
3641--- a/contrib/pycharm/encodings.xml
3642+++ /dev/null
3643@@ -1,6 +0,0 @@
3644-<?xml version="1.0" encoding="UTF-8"?>
3645-<project version="4">
3646- <component name="Encoding" useUTFGuessing="true" native2AsciiForPropertiesFiles="false">
3647- <file url="PROJECT" charset="UTF-8" />
3648- </component>
3649-</project>
3650\ No newline at end of file
3651diff --git a/contrib/pycharm/inspectionProfiles/Project_Default.xml b/contrib/pycharm/inspectionProfiles/Project_Default.xml
3652deleted file mode 100644
3653index 1b6d837..0000000
3654--- a/contrib/pycharm/inspectionProfiles/Project_Default.xml
3655+++ /dev/null
3656@@ -1,19 +0,0 @@
3657-<component name="InspectionProjectProfileManager">
3658- <profile version="1.0">
3659- <option name="myName" value="Project Default" />
3660- <option name="myLocal" value="true" />
3661- <inspection_tool class="PyUnresolvedReferencesInspection" enabled="true" level="WARNING" enabled_by_default="true">
3662- <option name="ignoredIdentifiers">
3663- <list>
3664- <option value="maasserver.models.node.NodeQueriesMixin.filter" />
3665- <option value="maasserver.models.node.NodeQueriesMixin.exclude" />
3666- <option value="maasserver.models.subnet.SubnetQueriesMixin.filter" />
3667- <option value="maasserver.models.subnet.SubnetQueriesMixin.exclude" />
3668- <option value="maasserver.utils.orm.MAASQueriesMixin.filter" />
3669- <option value="maasserver.utils.orm.MAASQueriesMixin.exclude" />
3670- <option value="maasserver.utils.orm.MAASQueriesMixin.model" />
3671- </list>
3672- </option>
3673- </inspection_tool>
3674- </profile>
3675-</component>
3676\ No newline at end of file
3677diff --git a/contrib/pycharm/inspectionProfiles/profiles_settings.xml b/contrib/pycharm/inspectionProfiles/profiles_settings.xml
3678deleted file mode 100644
3679index 3b31283..0000000
3680--- a/contrib/pycharm/inspectionProfiles/profiles_settings.xml
3681+++ /dev/null
3682@@ -1,7 +0,0 @@
3683-<component name="InspectionProjectProfileManager">
3684- <settings>
3685- <option name="PROJECT_PROFILE" value="Project Default" />
3686- <option name="USE_PROJECT_PROFILE" value="true" />
3687- <version value="1.0" />
3688- </settings>
3689-</component>
3690\ No newline at end of file
3691diff --git a/contrib/pycharm/maas.iml b/contrib/pycharm/maas.iml
3692deleted file mode 100644
3693index b6908c0..0000000
3694--- a/contrib/pycharm/maas.iml
3695+++ /dev/null
3696@@ -1,36 +0,0 @@
3697-<?xml version="1.0" encoding="UTF-8"?>
3698-<module type="PYTHON_MODULE" version="4">
3699- <component name="FacetManager">
3700- <facet type="buildout-python" name="Buildout Support">
3701- <configuration>
3702- <option name="script" value="bin/py" />
3703- </configuration>
3704- </facet>
3705- </component>
3706- <component name="NewModuleRootManager">
3707- <content url="file://$MODULE_DIR$">
3708- <sourceFolder url="file://$MODULE_DIR$/src" isTestSource="false" />
3709- <excludeFolder url="file://$MODULE_DIR$/bin" />
3710- <excludeFolder url="file://$MODULE_DIR$/build_pkg" />
3711- <excludeFolder url="file://$MODULE_DIR$/coverage" />
3712- <excludeFolder url="file://$MODULE_DIR$/local" />
3713- <excludeFolder url="file://$MODULE_DIR$/logs" />
3714- <excludeFolder url="file://$MODULE_DIR$/stage" />
3715- <excludeFolder url="file://$MODULE_DIR$/prime" />
3716- <excludeFolder url="file://$MODULE_DIR$/parts" />
3717- </content>
3718- <orderEntry type="jdk" jdkName="Python 3.5.1+ (/usr/bin/python3)" jdkType="Python SDK" />
3719- <orderEntry type="sourceFolder" forTests="false" />
3720- <orderEntry type="library" name="Buildout Eggs" level="project" />
3721- <orderEntry type="library" name="Buildout Eggs" level="project" />
3722- </component>
3723- <component name="TemplatesService">
3724- <option name="TEMPLATE_CONFIGURATION" value="Django" />
3725- <option name="TEMPLATE_FOLDERS">
3726- <list>
3727- <option value="$MODULE_DIR$/templates" />
3728- <option value="$MODULE_DIR$/src/maasserver/templates" />
3729- </list>
3730- </option>
3731- </component>
3732-</module>
3733diff --git a/contrib/pycharm/misc.xml b/contrib/pycharm/misc.xml
3734deleted file mode 100644
3735index cbd05d0..0000000
3736--- a/contrib/pycharm/misc.xml
3737+++ /dev/null
3738@@ -1,14 +0,0 @@
3739-<?xml version="1.0" encoding="UTF-8"?>
3740-<project version="4">
3741- <component name="ProjectLevelVcsManager" settingsEditedManually="false">
3742- <OptionsSetting value="true" id="Add" />
3743- <OptionsSetting value="true" id="Remove" />
3744- <OptionsSetting value="true" id="Checkout" />
3745- <OptionsSetting value="true" id="Update" />
3746- <OptionsSetting value="true" id="Status" />
3747- <OptionsSetting value="true" id="Edit" />
3748- <ConfirmationsSetting value="0" id="Add" />
3749- <ConfirmationsSetting value="0" id="Remove" />
3750- </component>
3751- <component name="ProjectRootManager" version="2" project-jdk-name="Python 3.5.1+ (/usr/bin/python3)" project-jdk-type="Python SDK" />
3752-</project>
3753diff --git a/contrib/pycharm/modules.xml b/contrib/pycharm/modules.xml
3754deleted file mode 100644
3755index 8f50088..0000000
3756--- a/contrib/pycharm/modules.xml
3757+++ /dev/null
3758@@ -1,8 +0,0 @@
3759-<?xml version="1.0" encoding="UTF-8"?>
3760-<project version="4">
3761- <component name="ProjectModuleManager">
3762- <modules>
3763- <module fileurl="file://$PROJECT_DIR$/.idea/maas.iml" filepath="$PROJECT_DIR$/.idea/maas.iml" />
3764- </modules>
3765- </component>
3766-</project>
3767\ No newline at end of file
3768diff --git a/contrib/pycharm/sqldialects.xml b/contrib/pycharm/sqldialects.xml
3769deleted file mode 100644
3770index 1962b9b..0000000
3771--- a/contrib/pycharm/sqldialects.xml
3772+++ /dev/null
3773@@ -1,6 +0,0 @@
3774-<?xml version="1.0" encoding="UTF-8"?>
3775-<project version="4">
3776- <component name="SqlDialectMappings">
3777- <file url="file://$PROJECT_DIR$" dialect="PostgreSQL" />
3778- </component>
3779-</project>
3780\ No newline at end of file
3781diff --git a/contrib/tgt.conf b/contrib/tgt.conf
3782deleted file mode 100644
3783index 1b5f332..0000000
3784--- a/contrib/tgt.conf
3785+++ /dev/null
3786@@ -1 +0,0 @@
3787-include /var/lib/maas/ephemeral/tgt.conf.d/*.conf
3788diff --git a/debian/changelog b/debian/changelog
3789index 08cbd6b..c400e34 100644
3790--- a/debian/changelog
3791+++ b/debian/changelog
3792@@ -1,2786 +1,5 @@
3793-maas (2.6.0-7802-g59416a869-0ubuntu1) eoan; urgency=medium
3794+maas (1:0.1) focal; urgency=medium
3795
3796- * New upstream release, MAAS 2.6.0.
3797+ * Install MAAS from the snap, migrating existing install if needed
3798
3799- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 11 Jun 2019 13:57:36 -0400
3800-
3801-maas (2.6.0~rc2-7802-g59416a869-0ubuntu1) eoan; urgency=medium
3802-
3803- * New upstream release, MAAS 2.6.0 RC 2.
3804-
3805- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 03 Jun 2019 10:08:01 -0400
3806-
3807-maas (2.6.0~rc1-7799-g70b0fe161-0ubuntu1) eoan; urgency=medium
3808-
3809- * New upstream release, MAAS 2.6.0 RC 1.
3810-
3811- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 30 May 2019 08:45:21 -0400
3812-
3813-maas (2.6.0~beta4-7743-g27b04aaf3-0ubuntu1) eoan; urgency=medium
3814-
3815- * New upstream release, MAAS 2.6.0 beta 4.
3816-
3817- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 10 May 2019 16:50:45 -0400
3818-
3819-maas (2.6.0~beta3-7711-gb79157e92-0ubuntu1) eoan; urgency=medium
3820-
3821- * New upstream release, MAAS 2.6.0 beta 3.
3822-
3823- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 03 May 2019 17:37:32 -0400
3824-
3825-maas (2.6.0~beta2-7695-g691e14ea3-0ubuntu1) disco; urgency=medium
3826-
3827- * New upstream release, MAAS 2.6.0 beta 2.
3828-
3829- -- Andres Rodriguez <andreserl@ubuntu.com> Sat, 27 Apr 2019 16:45:32 -0400
3830-
3831-maas (2.6.0~beta1-7673-g850a92f90-0ubuntu1) disco; urgency=medium
3832-
3833- * New upstream release, MAAS 2.6.0 beta 1.
3834-
3835- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 17 Apr 2019 16:24:55 -0400
3836-
3837-maas (2.6.0~alpha2-7640-g9c8072b21-0ubuntu1~19.04.1) disco; urgency=medium
3838-
3839- * New upstream release, MAAS 2.6.0 alpha 2
3840-
3841- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 28 Mar 2019 10:41:15 -0400
3842-
3843-maas (2.6.0~alpha1-7593-gcca18b743-0ubuntu1~18.10.1) cosmic; urgency=medium
3844-
3845- * New upstream release, MAAS 2.6.0 alpha 1
3846-
3847- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 12 Mar 2019 21:42:01 -0400
3848-
3849-maas (2.5.0-7442-gdf68e30a5-0ubuntu1) cosmic; urgency=medium
3850-
3851- * New upstream release. MAAS 2.5.0 introduces:
3852- - Proxy MAAS communication through the rack controller.
3853- - HA - Rack to region communication no longer needs VIPs.
3854- - KVM (pod) - Support for networking.
3855- - KVM (pod) - Re-designed WebUI.
3856- - CentOS storage support.
3857- - ESXi deployment support.
3858- - Machine listing - Re-designed UI.
3859- - Enlistment - now runs commissioning scripts.
3860- - Add machines by only specifying IPMI credentials.
3861-
3862- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 11 Dec 2018 15:15:30 -0500
3863-
3864-maas (2.5.0~rc2-7433-gea48d302e-0ubuntu1~18.10.1) cosmic; urgency=medium
3865-
3866- * New upstream release.
3867-
3868- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 30 Nov 2018 14:00:22 -0500
3869-
3870-maas (2.5.0~rc1-7419-ge0d239532-0ubuntu1~18.10.1) cosmic; urgency=medium
3871-
3872- * New upstream bugfix release.
3873-
3874- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 21 Nov 2018 12:02:18 -0500
3875-
3876-maas (2.5.0~beta4-7361-g401d6c73d-0ubuntu1~18.10.1) cosmic; urgency=medium
3877-
3878- * New upstream bugfix release.
3879-
3880- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 26 Oct 2018 14:22:03 -0600
3881-
3882-maas (2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.10.1) cosmic; urgency=medium
3883-
3884- * New upstream bugfix release.
3885-
3886- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 15 Oct 2018 09:33:40 -0400
3887-
3888-maas (2.5.0~beta2-7291-gd0345ced5-0ubuntu1) cosmic; urgency=medium
3889-
3890- * New upstream release. (LP: #1796937)
3891- * debian/maas-dhcp.maas-{dhcpd,dhcpd6}.service: Require dhcpd stop
3892- in 8 seconds, if not kill it with 'mixed' mode.
3893- * debian/control: Drop python3-jinja2 as it is no longer needed to
3894- generate documentation.
3895- * debian/maas-common.prerm: Add & handle stop of maas-syslog.service.
3896- * debian/maas-common.postrm:
3897- - Run debhelper handling before manual removal actions.
3898- - Purge maas-syslog related files.
3899- * debian/maas-rack-controller.prerm: Add & handle stop of
3900- maas-rackd.service.
3901- * debian/maas-rack-controller.postrm: Purge http and rpc.state files.
3902- * debian/maas-region-api.postrm: Purge maas-regiond socket file.
3903-
3904- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 02 Oct 2018 22:55:12 -0400
3905-
3906-maas (2.5.0~beta1-7225-g817fb216d-0ubuntu1) cosmic; urgency=medium
3907-
3908- * New upstream release (LP: #1792389)
3909- * debian/control: Depend on python3-jinja2
3910- * MAAS now manages its own rsyslog daemon:
3911- - d/maas-common.maas-syslog.service: Add service.
3912- - d/extras/99-maas-common-sudoers: start/stop/status for maas-rsyslog.
3913- - d/rules: Handle installation of maas-rsyslog.
3914- - d/extras/20-maas.conf: Drop as MAAS now generates its own config.
3915- - d/maas-region-api.install: Drop install of 20-maas.conf.
3916- - d/maas-region-api.postinst: Drop restart of rsyslog.
3917- - d/maas-common.install: Drop install of maas-rsyslog.conf.
3918- - d/maas-common.{preinst,postinst}: Handle upgrades.
3919-
3920- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 17 Sep 2018 05:30:25 -0400
3921-
3922-maas (2.5.0~alpha2-7175-gab01a63f2-0ubuntu1) bionic; urgency=medium
3923-
3924- * New upstream release.
3925- * Don't autostart maas-rackd on install to avoid initialization errors.
3926- - debian/rules: add --no-start for maas-rackd.
3927- - debian/maas-rack-controller.postinst: enable/start maas-rackd.
3928- * Make package more lintian clean:
3929- - debian/*.postinst: Remove of use of systemctl for deb-system-*
3930- - debian/*.lintin-overrides: Add overrides for a few warnings.
3931- * debian/rules: Do not override dh_installinit as we are using systemd.
3932-
3933- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 23 Aug 2018 08:04:57 -0400
3934-
3935-maas (2.5.0~alpha1-7104-g18ae9e407-0ubuntu1) bionic; urgency=medium
3936-
3937- * New upstream release.
3938-
3939- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 16 Jul 2018 14:30:06 -0400
3940-
3941-maas (2.4.0~rc2-6980-gc5ebdd7b1-0ubuntu1) bionic; urgency=medium
3942-
3943- * New upstream release.
3944-
3945- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 18 May 2018 17:48:22 -0400
3946-
3947-maas (2.4.0~rc1-6959-gd7a158fc3-0ubuntu1) bionic; urgency=medium
3948-
3949- * New upstream release.
3950-
3951- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 11 May 2018 14:34:52 -0400
3952-
3953-maas (2.4.0~beta3-6929-g62682abf5-0ubuntu1) bionic; urgency=medium
3954-
3955- * New upstream release.
3956-
3957- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 03 May 2018 03:31:14 -0400
3958-
3959-maas (2.4.0~beta2-6865-gec43e47e6-0ubuntu1) bionic; urgency=medium
3960-
3961- * New upstream release. (LP: #1754697)
3962-
3963- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 16 Apr 2018 09:12:38 -0400
3964-
3965-maas (2.4.0~beta1-6799-g391e5f16d-0ubuntu1) bionic; urgency=medium
3966-
3967- * New upstream release. (LP: #1754697)
3968- * debian/*: Integrate maas-dns into maas-region-api; make maas-dns a
3969- transitional package
3970-
3971- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 30 Mar 2018 15:32:38 -0400
3972-
3973-maas (2.4.0~alpha2-6717-gffaddd526-0ubuntu1~18.04.1) bionic; urgency=medium
3974-
3975- * New upstream release. (LP: #1754697)
3976- * debian/*: Replace ntp in favor of chrony.
3977-
3978- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 09 Mar 2018 11:01:52 -0500
3979-
3980-maas (2.4.0~alpha1-6573-g12ee2331b-0ubuntu1) bionic; urgency=medium
3981-
3982- * New upstream release
3983- * debian/*: Drop usage of apache2. It has long been used to maintain
3984- backwards compat for 1.x versions of MAAS, but starting from 2.4, it
3985- will no longer be supported.
3986- * debian/maas-{dhcp,proxy}.lintian-overrides: Add lintin overrides.
3987- * debian/control:
3988- - Bump Standards-Version.
3989- - Add depends on python3-uvloop, python3-macaroonbakery.
3990- - Drop depends on ubuntu-cloudimage-keyring in favor of ubuntu-keyring.
3991- - Drop depends on dh-systemd as it is now deprecated. Newer debhelper
3992- integrates it, as such, bump dep version.
3993-
3994- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 09 Feb 2018 18:50:10 -0500
3995-
3996-maas (2.3.0-6434-gd354690-0ubuntu1) bionic; urgency=medium
3997-
3998- * New upstream release, MAAS 2.3.0:
3999- - Add support for CentOS & Windows networking.
4000- - Add support for Upstream Proxy.
4001- - Add the ability to deploy rack controllers.
4002- - Add the ability to report controller versions.
4003- - Add HTTP boot for ephemeral images, instead of 'tgt'.
4004- - Add django 1.11 support.
4005- - Introduce beaconing for better network discovery.
4006- - Improve hardware testing for better usage and feedback.
4007- - Improves performance by improving DNS reloading performance.
4008- - Machine, devices & controller page re-design.
4009-
4010- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 20 Nov 2017 14:08:22 -0500
4011-
4012-maas (2.3.0~rc2-6412-g410b453-0ubuntu1) artful; urgency=medium
4013-
4014- * New upstream release, 2.3.0 rc2.
4015-
4016- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 09 Nov 2017 20:36:29 -0500
4017-
4018-maas (2.3.0~rc1-6393-g8103f0a-0ubuntu1) artful; urgency=medium
4019-
4020- * New upstream release, 2.3.0 rc1.
4021-
4022- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 06 Nov 2017 13:23:31 -0500
4023-
4024-maas (2.3.0~beta3-6368-g03ca7f4-0ubuntu1) artful; urgency=medium
4025-
4026- * New upstream release, 2.3.0 beta3.
4027- * debian/control: Add missing deps for python3-maas-client (LP: #1724181)
4028-
4029- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 11 Oct 2017 16:42:41 -0400
4030-
4031-maas (2.3.0~beta2-6327-gdd05aa2-0ubuntu1) artful; urgency=medium
4032-
4033- * New upstream release, 2.3.0 beta2 (LP: #1717543).
4034-
4035- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 11 Oct 2017 12:22:51 -0400
4036-
4037-maas (2.3.0~beta1-6301-gca25180-0ubuntu1) artful; urgency=medium
4038-
4039- * New upstream release, 2.3.0 beta1 (LP: #1717543):
4040- - Update the UI to surface hardware testing.
4041- - Rack Controller deployment for all machines via the API.
4042- - UI Improvements: Use new design for node details page and address
4043- various other UX issues.
4044- - API improvements: Introduce API output for volume_groups, raids,
4045- cache_sets and baches to the machines output. Used to support libmaas.
4046-
4047- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 04 Oct 2017 09:38:40 -0400
4048-
4049-maas (2.3.0~alpha3-6250-g58f83f3-0ubuntu1) artful; urgency=medium
4050-
4051- * New upstream release, 2.3.0 alpha3 (LP: #1717543):
4052- - Hardware Testing:
4053- + Ability to test and gather results per individual component
4054- (e.g. per disks).
4055- + Add 7z CPU performance test.
4056- + Add fio storage performance test.
4057- + Add ability to define YAML metadata for custom testing scripts,
4058- allowing MAAS to parse and utilize such metadata.
4059- - Rack Controller deployment for Whitebox Switches.
4060- - Improved DNS reloading.
4061- - UI - Controller Versions & Notifications.
4062- - UI - Refactor Zones page in Angular away from YUI.
4063- * Move scripts to maas-common that are used by the MAAS region controller
4064- in addition to the rack.
4065- - Add /usr/lib/maas/maas-common script.
4066- * Bump debhelper compat level 9.
4067- * debian/maas-common.links: Drop as it created a link for a binary that
4068- was already deprecated.
4069-
4070- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 15 Sep 2017 10:37:57 -0500
4071-
4072-maas (2.3.0~alpha2-6194-g7fb23b0-0ubuntu1) artful; urgency=medium
4073-
4074- * New upstream release, 2.3.0 alpha2:
4075- - Support for CentOS & Windows netwok configuration
4076- - Add Switch model
4077- - Add better Network Discovery & Beaconing
4078- - Minor UI improvements
4079-
4080- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 22 Aug 2017 13:49:24 -0400
4081-
4082-maas (2.3.0~alpha1-6165-geae082b-0ubuntu1) artful; urgency=medium
4083-
4084- * New upstream release, 2.3.0 alpha1:
4085- - Support for django 1.11.
4086- - Support for upstream proxy.
4087- - Support ephemeral image via HTTP instead of iSCSI.
4088- * Add "maas-rack observe-beacons" to list of commands capable of
4089- running as the "maas" user.
4090- * Add /usr/lib/maas/maas-beacon-monitor script.
4091- * Add maas-beacon-monitor script to sudoers file.
4092- (Allows observation of UDP traffic sent to port 5240.)
4093- * Conflicts with python3-googleapi
4094-
4095- -- Andres Rodriguez <andreserl@ubuntu.com> Sat, 29 Jul 2017 10:56:23 +0100
4096-
4097-maas (2.2.0+bzr6054-0ubuntu2) artful; urgency=medium
4098-
4099- * debian/rules: Fix FTBFS in artful.
4100-
4101- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 08 Jun 2017 18:57:01 -0400
4102-
4103-maas (2.2.0+bzr6054-0ubuntu1) artful; urgency=medium
4104-
4105- * New upstream release, MAAS 2.2.0.
4106-
4107- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 18 May 2017 11:08:43 -0400
4108-
4109-maas (2.2.0~rc4+bzr6048-0ubuntu1) zesty; urgency=medium
4110-
4111- * New upstream release, MAAS 2.2.0 RC 4.
4112-
4113- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 27 Apr 2017 16:10:06 -0400
4114-
4115-maas (2.2.0~rc3+bzr6025-0ubuntu1) artful; urgency=medium
4116-
4117- * New upstream release, MAAS 2.2.0 RC 3.
4118-
4119- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 21 Apr 2017 09:49:58 -0400
4120-
4121-maas (2.2.0~rc2+bzr5983-0ubuntu1) zesty; urgency=medium
4122-
4123- * New upstream release, MAAS 2.2.0 RC 2.
4124-
4125- -- Andres Rodriguez <andreserl@ubuntu.com> Sat, 15 Apr 2017 00:17:22 -0400
4126-
4127-maas (2.2.0~rc1+bzr5922-0ubuntu2) zesty; urgency=medium
4128-
4129- * Bump depends version on python3-curtin. (LP: #1680175)
4130-
4131- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 05 Apr 2017 13:51:58 -0400
4132-
4133-maas (2.2.0~rc1+bzr5922-0ubuntu1) zesty; urgency=medium
4134-
4135- * New upstream release, MAAS 2.2.0 RC 1. (FFe LP: #1667141)
4136- * debian/maas-common.logrotate: Rotate maas.log weekly, instead of daily.
4137- Store logs for 8 weeks. (LP: #1677005)
4138-
4139- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 28 Mar 2017 11:08:38 -0400
4140-
4141-maas (2.2.0~beta4+bzr5856-0ubuntu1) zesty; urgency=medium
4142-
4143- * New upstream release, MAAS 2.2.0 Beta 4. (FFe LP: #1667141)
4144- - Add support to disable components.
4145- - Improve RSD details page. Show composed machines and power tab.
4146- - Add NTP & Internet connectivity tests.
4147- - UX improvements - Change to new tab system to improve navigation.
4148- - Error surfacing - For interfaces of Machines & Devices.
4149- - Windows deployments - support to select the root/boot disk.
4150-
4151- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 16 Mar 2017 16:10:26 +0000
4152-
4153-maas (2.2.0~beta3+bzr5815-0ubuntu1) zesty; urgency=medium
4154-
4155- * New upstream release. MAAS 2.2.0 Beta 3 (FFe LP: #1667141):
4156- - Introduce storage verification smoke tests.
4157- - Introduce notifications API.
4158- - Add device details page.
4159- - Introduce Wedge BMC discovery during commissioning.
4160- - Add pod listing & details page.
4161- - Add dynamic composition for virsh devices.
4162-
4163- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 15 Feb 2017 08:37:25 -0500
4164-
4165-maas (2.2.0~beta2+bzr5717-0ubuntu1) zesty; urgency=medium
4166-
4167- * New upstream release. MAAS 2.2.0 Beta 2 (bzr5717):
4168- - Introduce initial support for Intel RSD.
4169- - Introduce IPv6 IPMI auto-discovery.
4170- - Introduce notifications.
4171-
4172- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 30 Jan 2017 15:55:02 -0500
4173-
4174-maas (2.2.0~beta1+bzr5675-0ubuntu1) zesty; urgency=medium
4175-
4176- * New upstream release. MAAS 2.2.0 Beta 1 (bzr5675):
4177- - Changing the concept of Spaces to a L2 layer.
4178- - Support for DHCP relays.
4179- - Introduce the concept of UNMANAGED subnets.
4180-
4181- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 11 Jan 2017 13:34:46 +0200
4182-
4183-maas (2.2.0~alpha1+bzr5614-0ubuntu1) zesty; urgency=medium
4184-
4185- * New upstream release. MAAS 2.2.0 Alpha 1 (bzr5614):
4186- - Don't install Django settings into /usr/share/maas/maas. For
4187- regiond these were squatting the `maas` namespace, preventing its
4188- use elsewhere (LP: #1646748)
4189-
4190- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 21 Nov 2016 20:01:31 -0500
4191-
4192-maas (2.1.1+bzr5501-0ubuntu1) zesty; urgency=medium
4193-
4194- * MAAS new upstream bugfix release. MAAS 2.1.1 bzr 5544.
4195-
4196- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 24 Oct 2016 11:28:59 -0400
4197-
4198-maas (2.1.0+bzr5480-0ubuntu1) yakkety; urgency=medium
4199-
4200- * MAAS new upstream bugfix release. MAAS 2.1.0 (0-day SRU LP: #1633064):
4201- - TestPartition.test_get_partition_number_returns_starting_at_2_for_ppc64el
4202- fails spuriously (LP: #1569365)
4203- - "Deployed" and "Deploying" are too similar (LP: #1598470)
4204- - Users' maas api keys do not have a name (LP: #1536354)
4205- - [2.1] Incorrect logging message - showing SERVICE_STATE.ON (LP: #1631358)
4206- - [2.1 UI] Images page "Queued for download" is confusing when selections
4207- are not saved (LP: #1631420)
4208- - [2.1b1] Dashboard column widths for discovered items are
4209- wonky (LP: #1631024)
4210- - [2.1b1] 'Registering existing rack controller' (LP: #1631022)
4211- - [2.1] Command 'interface link-subnet' does not work (LP: #1629604)
4212- - [FUJ] SSH input field not indicated for invalid username & the error
4213- is incomprehensible (LP: #1628114)
4214- - [2.1 ipv6] DHCP generation should not fail when address-family
4215- conflicts are present (LP: #1629475)
4216- - [2.0rc2] Commissioning node with gateway_link_v4 set fails. (LP: #1603466)
4217- - [2.1, 2.0 UI] Error when using dhcp range with pre-existing dynamic
4218- reservation (LP: #1608555)
4219- - [2.1b2] Node failed to be released, because of the following error:
4220- 'NoneType' object has no attribute 'addErrback' (LP: #1632815)
4221- - [2.1, Yakkety, UI] UI error when adding a chassis (LP: #1632395)
4222- - [2.0, 2.1 UI] Other reserved IP ranges disappear when one of them is
4223- deleted on Subnet details page. (LP: #1631079)
4224- - [2.1b1] MAAS fails to deploy systems with 3+ TB disks (LP: #1630667)
4225- - [2.1 Yakkety UI] Unable to select nodes (LP: #1630633)
4226- - [2.0, 2.1] Release and list IPs reserved by another user (LP: #1629061)
4227- - [2.0rc2] Changing DNSSEC validation does not trigger configuration
4228- file update (LP: #1605476)
4229- - [2.1] Failed to mount a partition and it doesn't surface error. (LP: #1631152)
4230- - [2.1. Yakkety] "Map subnet" action doesn't work. (LP: #1632862)
4231-
4232- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 05 Oct 2016 21:47:25 -0400
4233-
4234-maas (2.1.0~beta2+bzr5454-0ubuntu1) yakkety; urgency=medium
4235-
4236- * MAAS new upstream bugfix release. MAAS 2.1.0 beta 2 (bzr5454):
4237- - [2.1] Bootloaders not downloaded on initial import (LP: #1630394)
4238- - Cryptic error when PXE-boot requires an image not yet imported (LP: #1611949)
4239- - [2.0, 2.1, UI] MAAS webui allows boot disk to be changed on an
4240- already deployed node (LP: #1625676)
4241- - [2.1] Rename "Networks" tab to "Subnets" (LP: #1630591)
4242- - [2.1] netaddr assumes MAC OUI is ascii (LP: #1628761)
4243- - [2.1, 2.0] Can't input dynamic range on "Enable DHCP" after I deleted
4244- the dynamic range (LP: #1619262)
4245- - Machine unable to pxe with no-such-image while non-related images are
4246- being imported (LP: #1612203)
4247- - External DHCP detection is broken for a variety of reasons (LP: #1628645)
4248- - [2.1] expected string or bytes-like object (LP: #1627362)
4249- - [2.1] When trying to release a node, it gets stuck in releasing if
4250- there is no rack controller to power control (LP: #1614659)
4251- - WebUI needs a filter for deployed OS (LP: #1445941)
4252-
4253- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 05 Oct 2016 10:59:45 -0400
4254-
4255-maas (2.1.0~beta1+bzr5433-0ubuntu1) yakkety; urgency=medium
4256-
4257- * MAAS new upstream release. MAAS 2.1.0 beta 1 (bzr5433):
4258- - Support for new version of streams.
4259- - Bootloaders are now downloaded from the streams.
4260- - Support for Low Latency kernels.
4261- - Support for new hardware enablement kernels.
4262- - Device discovery
4263- - UI ability to Map a network as an action.
4264- - Ability to select interval of active discovery.
4265- - Ability to enable active discovery per subnet.
4266- * Remove old template files on package removal.
4267-
4268- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 27 Sep 2016 14:44:26 -0400
4269-
4270-maas (2.1.0~alpha4+bzr5397-0ubuntu1) yakkety; urgency=medium
4271-
4272- * MAAS new upstream release, MAAS 2.1.0 alpha 4 (bzr5397):
4273- - Complete First User Journey (Ability to import keys from GH/LP).
4274- - User profile has ability to import keys from GH/LP as well.
4275- - Device discovery:
4276- - Ability to clear records that may be incorrect.
4277- - Ability to 'Map networks' via the API.
4278- - Import NTP configuration via vendor-data and DHCP.
4279-
4280- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 19 Sep 2016 17:21:47 -0400
4281-
4282-maas (2.1.0~alpha3+bzr5368-0ubuntu1) yakkety; urgency=medium
4283-
4284- * New upstream release, MAAS 2.1.0 Alpha 3 (bzr5363):
4285- - First user journey (SSH key import not yet available).
4286- - Allow the user to import SSH keys from LP or GH (only API/CLI).
4287- - Provide NTP services. Region and Rack Controllers now provide NTP
4288- services. Machines are also deployed with NTP configuration via.
4289- + Add cloud-init vendor data to support configuring the machine with
4290- NTP settings.
4291- - Images page complete redesign and transition to AngularJS.
4292-
4293- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 19 Sep 2016 17:21:20 -0400
4294-
4295-maas (2.1.0~alpha2+bzr5321-0ubuntu1) yakkety; urgency=medium
4296-
4297- * New upstream release, MAAS 2.1.0 Alpha 2 (bzr5321):
4298- - Commissioning user data and PXE templates no longer user configs.
4299- They are no longer shipped on /etc/maas.
4300- - Adds support for Device Discovery (Backend and API).
4301- - [UI] Better error surfacing for DHCP snippets and Package Repositories.
4302- * Add depends on avahi-utils, ntp, and tcpdump.
4303- * Old templates still exist. Move them so users know they are no longer
4304- user (LP: #1619202)
4305- * Create the /etc/ntp directory. MAAS writes custom NTP configuration
4306- to /etc/ntp/maas.conf because ntpd is allowed by AppArmor to read
4307- configuration only from /etc/ntp.conf and /etc/ntp/**.
4308-
4309- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 31 Aug 2016 20:25:17 +0100
4310-
4311-maas (2.1.0~alpha1+bzr5300-0ubuntu1) yakkety; urgency=medium
4312-
4313- * New upstream release, MAAS 2.1.0 Alpha 1 (bzr5300):
4314- - Advanced networking - static routes.
4315- - Machine networking - bridge configuration.
4316- - Machine networking - UI redesign and tags.
4317- - Derived (mirrors) and additional repositories.
4318- - Maintenance - Rescue Mode.
4319- - Device discovery - backend.
4320- - NTP support - backend.
4321- * Give MAAS on both region and rack the ability to start, restart, and
4322- get the status of the local NTP service.
4323- * Depend on python3-attr for the region and rack controllers.
4324-
4325- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 03 Aug 2016 10:51:50 -0400
4326-
4327-maas (2.0.0~rc3+bzr5180-0ubuntu2) yakkety; urgency=medium
4328-
4329- * Really fix by the determination of the default gateway, otherwise
4330- automatically chose localhost. (LP: #1607112)
4331-
4332- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 27 Jul 2016 22:20:09 -0400
4333-
4334-maas (2.0.0~rc3+bzr5180-0ubuntu1) yakkety; urgency=medium
4335-
4336- * New upstream release, 2.0.0 RC3 bzr5180:
4337- - CLI version command doesn't work (2.0) (LP: #1557434)
4338- - [2.0rc1] MAAS does not respect default subnet's DNS server when
4339- choosing default DNS (LP: #1576116)
4340- - [2.0RC1] MAAS displays every power query on the summarized view of
4341- node event log (LP: #1594991)
4342- - [2.0] Loading latest machine events can make web browser
4343- unresponsive (LP: #1598028)
4344- - [2.0rc1] MAAS doesn't honor DNS settings for a subnet for
4345- DHCP (LP: #1600720)
4346- - [2.0rc1] drop arm64/efi grub module workaround (LP: #1600285)
4347- - maas login yields "ImportError: No module named
4348- 'maasserver'" (LP: #1604169)
4349- - [doc] events API limit,before, after options not
4350- documented (LP: #1604901)
4351- - RackController.get_image_sync_status causes huge load
4352- on regiond process (LP: #1604465)
4353- - [2.0b8] MAAS is automatically monitoring timeouts. (LP: #1598149)
4354- - [2.0] Error messaging about monitor expiry has been
4355- dropped (LP: #1605252)
4356- - [2.0rc2] Can't get node-results via cli/api (LP: #1602721)
4357- - node set to "failed deployment" for no visible reason (LP: #1604962)
4358- - Event log should always include a reason why a node was
4359- marked Failed Deployment (LP: #1604987)
4360- * If no default route is present in the system, configure maas_url on
4361- regiond.conf to localhost to allow the user to tell MAAS what IP to use.
4362-
4363- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 22 Jul 2016 18:05:45 -0400
4364-
4365-maas (2.0.0~rc2+bzr5156-0ubuntu1) yakkety; urgency=medium
4366-
4367- * New upstream release, 2.0.0 RC2 bzr5156:
4368- - Pick up wrong grub.cfg if another filesystem exists (LP: #1582070)
4369- - [2.0] confusing reverse DNS lookups because MAAS creates multiple
4370- PTR records (LP: #1599223)
4371- - [2.0] reverse DNS sometimes assigns FQDN where it should assign
4372- IFACE.FQDN (LP: #1600259)
4373- - [2.0rc1] after upgrade from 2.0b3, Error on request (13)
4374- subnet.list: 'NoneType' object is not iterable (LP: #1599997)
4375- - [2.0rc1] Image import dates are inconsistent (LP: #1598461)
4376- - [2.0rc1] Following fresh install maas command fails
4377- PermissionError: [Errno 13] Permission denied:
4378- '/home/ubuntu/.maascli.db' (LP: #1598937)
4379- - [1.9.3,2.0] cannot create more than 4 partitions when disk is
4380- configured with mbr (LP: #1597787)
4381- - [1.9,2.0,UX] Can't add aliases when parent interface is set to
4382- 'DCHP' (LP: #1600267)
4383- - [1.9,2.0,UX] Creating a Bcache disk is not prevented when is not
4384- created in partition (LP: #1600198)
4385-
4386- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 06 Jul 2016 09:49:41 -0400
4387-
4388-maas (2.0.0~rc1+bzr5143-0ubuntu1) xenial; urgency=medium
4389-
4390- * New upstream release, 2.0.0 RC1 bzr5143:
4391- - Determine a method for how to reconnect a deleted rack controller (LP: #1576357)
4392- - [2.0b7, regression] maas-rack register makes up a new hostname (LP: #1592246)
4393- - [2.0b8] HMC power driver regression -- Not able to connect via SSH. (LP: #1595753)
4394- - [2.0b7] Date and time format should be consistent accross logs (LP: #1592885)
4395- - [2.0b8] Unable to set default gateway interface (LP: #1597324)
4396- - [1.9] VMware power management fails when VMs are organized in nested subfolders (LP: #1515188)
4397- - [2.0] maas 2.0 pxeboot fails on PowerNV (LP: #1596046)
4398-
4399- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 28 Jun 2016 16:58:20 -0400
4400-
4401-maas (2.0.0~beta8+bzr5134-0ubuntu1) xenial; urgency=medium
4402-
4403- * New upstream release, 2.0.0 beta8 bzr5134:
4404- - Allow ed25519 and ecdsa ssh keys (LP: #1590081)
4405- - [2.0b2, UI] Can't add a device and it does not show why. (LP: #1462078)
4406- - [2.0b3] Interfaces on region controllers are not
4407- discovered (LP: #1573626)
4408- - [2.0b4, UI] No feedback when failing to assign static IP address on
4409- the Node Details Page (LP: #1562107)
4410- - [2.0b5] No way to read settings, like proxy, for non-admin
4411- users (LP: #1583670)
4412- - [2.0b5] Commissing with LVM breaks deployments (LP: #1585016)
4413- - [2.0b5] dns templates still in /etc/maas/templates (LP: #1581729)
4414- - [2.0b6] django.db.utils.IntegrityError: insert or update on
4415- table "piston3_consumer" (LP: #1588907)
4416- - [2.0b6] Image status stays out-of-sync after adding custom image (LP: #1581130)
4417- - [2.0b6] core count not updated during commissioning if MAAS
4418- previously stored a higher core count (LP: #1590144)
4419- - [2.0b7] Adding rack controller instructions could be in the
4420- GUI (LP: #1592282)
4421- - [2.0b7] Enlisting output returns objects (LP: #1592132)
4422- - [2.0b7, UI] Can't sort IP addresses under a subnet details
4423- page (LP: #1592137)
4424- - [2.0b7] Nodes API doesn't show regions (LP: #1593789)
4425- * /etc/maas/templates/dns is obsolete. (LP: #1581729)
4426- * Switch to OpenSSH for SSH public key validation. Previously
4427- Twisted's conch was used but it does not yet support the newer ecdsa
4428- and ed25519 key types. (LP: #1590081)
4429- * debian/control: maas-region-api depends on maas-cli.
4430- * debian/maas-region-api.postinst: Ensure rsyslog is restarted.
4431- * debian/maas-region-controller.postinst: Ensure maas_url ends with 5240.
4432- * Versioned Depend on squid
4433- * debian/maas-region-controller.config: Ensure dbc_go is not run when
4434- dbconfig common is not yet installed.
4435- * Wait for squid to finish starting before returning from the start command.
4436- LP: #1592954
4437-
4438- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 14 Jun 2016 17:08:48 -0400
4439-
4440-maas (2.0.0~beta7+bzr5112-0ubuntu1) xenial; urgency=medium
4441-
4442- * New upstream release, 2.0.0 beta 7 bzr5112:
4443- - [2.0b5] p.refresh.get_swap_size misconverting units (LP: #1587896)
4444- - get_interfaces_definition is not thread-safe (LP: #1587896)
4445- - [2.0] Cannot create an IP reservation with a hostname (LP: #1590021)
4446- - [2.0b5] request to http://.../MAAS/metadata/status/<systemdid>/latest
4447- failed (LP: #1581723)
4448- - [2.0b4] Rack Controller fail to update commissioning info? (LP: #1577953)
4449- - [2.0b6, UI] When I delete a fabric, it takes me back to the
4450- Node listing page (LP: #1589562)
4451- - [2.0b6, UI] When I delete a space, it takes me back to the
4452- Node listing page (LP: #1589596)
4453- - [2.0b5, UI] No form validation when adding a subnet, space,
4454- fabric or vlan (LP: #1588298)
4455- - [2.0b6, UI] Message "No IP ranges have been reserved for this subnet."
4456- doesn't go away after adding IP Range (LP: #1589606)
4457- - [2.0b6, UI] Can't add a VLAN over the WebUI (LP: #1589583)
4458- - [2.6b6, UI] Adding a fabric with an optional name ends up with a new
4459- fabric with automatically assigned name (LP: #1589560)
4460- - [2.6b6, UI] Adding a space with an optional name ends up with a new
4461- space with automatically assigned name (LP: #1589595)
4462- - Auto detection of running virtual environment during commissioning
4463- almost always fails (LP: #1590946)
4464- - [2.0b6] Cannot allocate a node based on its system_id (LP: #1590991)
4465- - [2.0,1.9] 3rd party HP drivers (archive hostname renamed) - deployment
4466- fails (LP: #1591093)
4467- - [2.0b4 UI] MAAS WebUI doesn't quickly refresh when deleting
4468- machines (LP: #1581219)
4469- - [2.0b4] Can attempt to commission enlisted nodes without chosen
4470- power type (LP: #1579215)
4471- - [2.0b6] Can edit fabric and subnet on deployed node (LP: #1590499)
4472- - [2.0b6] some arm64 systems need ipmi_ssif module in addition to
4473- ipmi_si (LP: #1591395)
4474- - [2.0] maas createadmin fails (LP: #1591346)
4475- - [2.0b6] Attempting to delete a VLAN that cannot be deleted, shows
4476- traceback in regiond.log (LP: #1589587)
4477- - [2.0b6] Commisioning fails on machines without HW
4478- virtualization (LP: #1591958)
4479-
4480- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 06 Jun 2016 18:54:19 -0400
4481-
4482-maas (2.0.0~beta6+bzr5073-0ubuntu1) xenial; urgency=medium
4483-
4484- * New upstream release, 2.0.0 beta 6 bzr5073:
4485- - Spurious failures in test_regionservice (LP: #1572646)
4486- - use http for stream mirror, not https (LP: #1582836)
4487- - MAAS version API call should not require authentication (LP: #1583715)
4488- - Detect and identify NIC SR-IOV capability (LP: #1572740)
4489- - [1.9,2.0]Commissioning fails when BIOS reports floppy drive,
4490- but there is none installed (LP: #1584211)
4491- - [1.9,2.0] DNS record created against IPv6 address when it is not
4492- on the PXE interface (LP: #1584850)
4493- - [2.0] MaaS 2.0 BMC information not removed when nodes are removed (LP: #1586555)
4494- - [2.0] IPMI driver does not handle timeouts correctly (LP: #1508741)
4495- - [2.0] Display RAM amount to the first decimal place in the UI (LP: #1585759)
4496- - [2.0] Expose the refresh rack controller action over the UI (LP: #1585760)
4497- - [2.0] Rename maas-nodegrou-worker to MAAS (LP: #1585768)
4498- - [2.0a1] MAAS should ensure that BMC password is correct before
4499- saving (LP: #1553841)
4500- - [2.0b2] DNS zone serials are not stable (LP: #1571645)
4501- - [2.0b2] If you deploy a machine in MAAS, and manually install a
4502- rack controller in it, it disappears from the machine list" (LP: #1570985)
4503- - [2.0b3] rack / region controllers are visible to non-admins (LP: #1576417)
4504- - [2.0b4] external maas-rack-controller logs to syslog instead of
4505- maas.log (LP: #1577972)
4506- - [2.0b4] twisted.internet.error.ConnectionDone: Connection was
4507- closed cleanly. (LP: #1580817)
4508- - [2.0b4 UI/API] No notifications rack controller is disconnected.
4509- No power type available (LP: #1581318)
4510- - [2.0b5] AMT machines using wsman do not netboot (LP: #1580350)
4511- - [2.0b5] When installing secondary region controller on its on,
4512- last image sync is never (LP: #1581737)
4513- - [2.0b5] Can't force the import of images per Rack Controller (LP: #1583685)
4514- - [2.0b5] After changing proxy, MAAS cannot install images (LP: #1585649)
4515- - [2.0b5] MAAS doesn't import default images automatically (LP: #1584936)
4516- - [2.0b5] Trying to assign an IP address statically to a device results
4517- in builtins.AttributeError: 'NoneType' object has no attribute
4518- 'link_subnet' (LP: #1558635)
4519- - [2.0b5] duplicate key on startup: Key (vid, fabric_id)=(2, 0)
4520- already exists. (LP: #1583333)
4521- - [2.0b5] Deployed regions should be able to transistion back to
4522- machines (LP: #1588531)
4523- - [2.0b5] domain details page does not update as the domain contents
4524- change (LP: #1581224)
4525- - [2.0b5] Cannot disable DHCP if you remove the subnet first ("Cannot
4526- configure DHCP: At least one dynamic range is required.") (LP: #1583392)
4527- - [2.0b5] builtins.ValueError: invalid literal for int() with base 10 (LP: #1588846)
4528- - [2.0, UI] Bulk actions-Nodes action doesn’t apply should be red (LP: #1585628)
4529- - [2.0, UI] Add fabric, VLAN, Space show's badly place form (LP: #1587936)
4530- - [2.0, UI] 'Commission' a node under the Node Listing Page shows actions
4531- not correctly formatted. (LP: #1587939)
4532- - [2.0, UI] Add domain show's badly place form (LP: #1587998)
4533- - [2.0, UI] There's no spacing between combo boxes under the Machine
4534- Details page (LP: #1588000)
4535-
4536- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 03 Jun 2016 18:05:32 -0400
4537-
4538-maas (2.0.0~beta5+bzr5026-0ubuntu1) xenial; urgency=medium
4539-
4540- * New upstream release, 2.0.0 beta 5 bzr5026:
4541- - [UI 2.0b1] Impossible to change subnet CIDR or gateway with
4542- instant editing (LP: #1572076)
4543- - [UI 2.0b1] Network details page doesn't have CSS for
4544- editting (LP: #1568102)
4545- - [UI 2.0b2] Can't edit fabric's, vlans, subnets from the
4546- WebUI (LP: #1571670)
4547- - [UI 2.0b2] Can't add/edit/delete IP ranges through UI (LP: #1571672)
4548- - [UI/Backend 2.0b2] Can't delete a rack controller from the Rack
4549- Details Page (LP: #1570990)
4550- - [UI 2.0b3] interface addresses on rack controller details page
4551- not updated automatically (LP: #1576267)
4552- - [UI 2.0b4] Actions list is unordered (LP: #1577386)
4553- - [UI 2.0b4] I can 'add special filesystem' when the machine is
4554- deployed (LP: #1580827)
4555- - [1.9] wrong subnet in DHCP answer when multiple networks are
4556- present (LP: #1521618)
4557- - [2.0] include maas resetMachine() API primitive (LP: #1536346)
4558- - [2.0] Re-commissioning doesn't detect storage changes (LP: #1575567)
4559- - [2.0] Expose custom network in non ubuntu deployments (LP: #1570002)
4560- - [2.0a4] Reserved IP ranges should be allowed to be created by
4561- standard users (LP: #1580260)
4562- - [2.0b2] 6 Core system is listed as having a single CPU (LP: #1542353)
4563- - [2.0b2] Cannot delete a rack controller that was previously a
4564- 'machine' (LP: #1570995)
4565- - [2.0b3] IP Ranges section on the subnet page should be shown
4566- even if no ranges (LP: #1576758)
4567- - [2.0b3] Tag changes depend on rack / cluster connection (LP: #1372544)
4568- - [2.0b4] Rack Controller fail to update commissioning info? (LP: #1577953)
4569- - [2.0b4] Rack Controller mark-broken / mark-fixed (LP: #1577954)
4570- - [2.0b4] Registering external rack controller tracebacks (LP: #1577970)
4571- - [2.0b4] RackControllerService flooding log with:
4572- 'RegionAdvertisingService' object has no attribute 'processId' (LP: #1578800)
4573- - [2.0b4] set_initial_networking_configuration shouldn't raise
4574- ValidationError (LP: #1580405)
4575- - [2.0b4] Disks less than 4MB in size cause a traceback on the
4576- MAAS server (LP: #1580280)
4577- - [2.0b4] Rack Controller details page shows "never" under last
4578- image sync (LP: #1577974)
4579- - [2.0b4] Machines successfully commission but don't get marked
4580- 'Ready' (LP: #1580285)
4581- - [2.0b4] Region RPC losing connection and raising exception (LP: #1581654)
4582- - [2.0b4] unregisterConnection() missing 1 required positional
4583- argument: 'host' (LP: #1580771)
4584- * debian/maas-dhcp.posinst: Pipe error messages correctly to not show
4585- messages when disabling isc-dhcp-server init scripts. (LP: #1570911)
4586-
4587- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 06 May 2016 09:56:40 -0500
4588-
4589-maas (2.0.0~beta4+bzr4985-0ubuntu1) xenial; urgency=medium
4590-
4591- * New upstream release, 2.0.0 beta 4 bzr4985:
4592- - Disk erasing with Xenial results it abnormal poweroff (LP: #1527634)
4593- - UI Nodes page shows 'ascii' codec can't decode byte (LP: #1555864)
4594- - When power_type changed to manual "power_state" was not set to "unknown" (LP: #1574003)
4595- - MAAS Rack Controller doesn't log when it is importing images. (LP: #1571007)
4596- - rackd fails to register vlan interfaces with "vlan" naming scheme (LP: #1575945)
4597- - Traceback deleting fabric (LP: #1573492)
4598- - adding files with paths in the filename confuses maas (LP: #1566108)
4599- - MAAS does not add node to DNS Domain (LP: #1571621)
4600- - tag only supports 'nodes' and and not 'machines' or 'controller's (LP: #1573644)
4601- - enlistment fails: /tmp/sh.UZ7qJT/bin/maas-enlist: archdetect: not found (LP: #1573264)
4602- - creating a dnsresource-record at the root of a zone should allow fqdn= (LP: #1562919)
4603- - In the domain details pages, sometimes names have links to nodes when they should not (LP: #1573690)
4604- - Can't power on/off Rack Controller (LP: #1576854)
4605- - ipranges create raises incorrect error for missing type (LP: #1573660)
4606- - fabric and space pages fail to update automatically (LP: #1557597)
4607- - Subnet page doesn't show which machine or device owns an IP address (LP: #1567150)
4608- - MAAS Controller listing page doesn't indicate whne a rack is downloading images (LP: #1571680)
4609- - Deleting user in UI leads to 500 (LP: #1573219)
4610- - maas enlistment of power8 found ipmi 1.5 should do ipmi 2.0 (LP: #1556219)
4611- * debian/extras/20-maas.conf: Better organize rsyslog logs.
4612-
4613- -- Andres Rodriguez <andreserl@ubuntu.com> Sat, 30 Apr 2016 18:40:26 -0400
4614-
4615-maas (2.0.0~beta3+bzr4941-0ubuntu1) xenial; urgency=medium
4616-
4617- * New upstream release, 2.0.0 beta 3 bzr4941 (Standing FFe LP: #1553261)
4618- * Remove some leftover references to Cluster.
4619- * Run debconf-updatepo.
4620-
4621- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 15 Apr 2016 22:27:56 -0400
4622-
4623-maas (2.0.0~beta2+bzr4920-0ubuntu2) xenial; urgency=medium
4624-
4625- * debian/control: Add missing dep on python3-httplib2
4626-
4627- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 15 Apr 2016 22:23:55 -0400
4628-
4629-maas (2.0.0~beta2+bzr4920-0ubuntu1) xenial; urgency=medium
4630-
4631- * New upstream release, 2.0.0 beta 2 bzr4920 (Standing FFe LP: #1553261)
4632- * Only create the squid cache if we have a configuration file.
4633- LP: #1568847
4634- * Re-add shared debconf templates.
4635-
4636- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 07 Apr 2016 18:22:00 -0400
4637-
4638-maas (2.0.0~beta1+bzr4873-0ubuntu2) xenial; urgency=medium
4639-
4640- * Add maas-region-udeb and maas-rack-udeb to be used as part of the
4641- Ubuntu Server Installer (LP: #1561954)
4642- - ensure maas-rack-controller and maas-region-controller can be fully
4643- preseeded.
4644-
4645- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 05 Apr 2016 17:02:32 -0400
4646-
4647-maas (2.0.0~beta1+bzr4873-0ubuntu1) xenial; urgency=medium
4648-
4649- * New upstream release, 2.0.0 beta 1 bzr4873 (Standing FFe LP: #1553261)
4650- - DHCP Snippets WebUI.
4651- - Ensure proxy configuration ACL's subnets MAAS knows about.
4652- - DNS High Availability.
4653- * debian/control: Move 'maascli' package install to
4654- python3-maas-client (LP: #1563859)
4655- * Improve way on how upgrades ensures correct permissions
4656- and ownership (LP: #1563799 , LP: #1563779)
4657- * Improve the way how removals clean the system (LP: #1563337)
4658- * Reflect new names and website for systemd units (LP: #1563807)
4659- * maas-proxy now uses a custom-built config, instead of a boilerplate.
4660- LP: #1379567
4661-
4662- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 28 Mar 2016 16:47:58 -0400
4663-
4664-maas (2.0.0~alpha4+bzr4843-0ubuntu1) xenial; urgency=medium
4665-
4666- * New upstream release, 2.0.0 alpha 4 bzr4843 (Standing FFe LP: #1553261)
4667- - DHCP Snippets backend and API.
4668- - Rack controller WebUI Served VLANs & Service Tracking
4669- - Rsyslog during enlistment/commissioning.
4670- * Ensure /etc/maas/templates/power gets removed on upgrade
4671- * debian/control: Update homepage and package descriptions.
4672- (LP: #1562036, LP: #1562034, LP: #1562062)
4673- * Rename maas-reigon-controller-min to maas-region-api (LP: #1562069)
4674-
4675- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 23 Mar 2016 12:27:27 -0400
4676-
4677-maas (2.0.0~alpha3+bzr4810-0ubuntu1) xenial; urgency=medium
4678-
4679- * New upstream release, 2.0.0 bzr 4810 (Standing FFe LP: #1553261)
4680- - New Networks WebUI
4681- + Add Fabrics and Spaces details page.
4682- + Actions to Add/Remove Fabrics, VLANs, Spaces, Subnets.
4683- - Storage WebUI
4684- + Mount options
4685- + Swap Partitions
4686- - WebUI to change a Machine's domain.
4687- - Rack Controller details page now shows 'Server VLANs'
4688- - Add maas-rack support-dump command.
4689- - Fixes:
4690- + python3-maas-client API 2.0 no loger use op but MAASClient.post
4691- requires it (LP: #1555393)
4692- + Fail to commission when Fabric on Machine Interface doesn't match
4693- Rack Controller Fabric. (LP: #1554566)
4694- + TFTP back-end crashes (LP: #1553848)
4695- + Can't deploy a node, no interfaces on rack controller (LP: #1554999)
4696- * Update dhcpd permissions to conform with most recent paranoia described
4697- on LP: 1543794, so capability dac_override is not granted.
4698- * Update versioned depend on isc-dhcp-server
4699-
4700- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 14 Mar 2016 18:34:53 -0400
4701-
4702-maas (2.0.0~alpha2+bzr4776-0ubuntu1) xenial; urgency=medium
4703-
4704- * New usptream release, 2.0.0 bzr 4776 (LP: #1553261).
4705- * maas-dns Depends: bind9 >= 1:9.10.3.dfsg.P2-5 for better system time.
4706- LP: #1553176.
4707- * debian/extras/maas-{region,rack}: Replace maas-region-admin
4708- and maas-provision, respectively (LP: #1553791)
4709- * debian/maas-region-controller.postrm: Correctly handle removal by
4710- dbconfig-common. (LP: #1553648)
4711- * debian/extras/99-maas-region-sudoers: Allow running systemctl for
4712- bind9 and maas-proxy to support service tracking. (LP: #1555308)
4713-
4714- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 01 Feb 2016 18:18:52 +0100
4715-
4716-maas (2.0.0~alpha1+bzr4736-0ubuntu1) xenial; urgency=medium
4717-
4718- * New usptream release, 2.0.0 bzr 4736 (LP: #1553261):
4719- - Deprecate Cluster Controllers in favor of Rack Controllers.
4720- - Deprecate API 1.0 in favor if API 2.0.
4721- - DHCP & Rack Controller High Availability.
4722- - Networking - IP Ranges.
4723- - Networking - DNS.
4724- - BMC Model.
4725- * Rename maas-cluster* to maas-rack* and handle the upgrade path.
4726- * Fix installation of init scripts and daemon systemd units.
4727- * Allow 'dhcpd' to access /usr/sbin/maas-provision via
4728- sudoers file (LP: #1552775)
4729- * debian/extras/maas: Replace shell wrapper with python. (LP: #1553605)
4730- * debian/control: Depends on iproute2 instead. (LP: #1553647)
4731-
4732- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 01 Feb 2016 18:18:52 +0100
4733-
4734-maas (1.10.0+bzr4572-0ubuntu2) xenial; urgency=medium
4735-
4736- * debian/maas-region-controller.config: Ensure we truly preseed db
4737- setting so we always use localhost and it never asks the user.
4738- * debian/control: Suggests on python3-pyvmomi
4739-
4740- -- Andres Rodriguez <andreserl@ubuntu.com> Mon, 01 Feb 2016 17:04:27 +0100
4741-
4742-maas (1.10.0+bzr4572-0ubuntu1) xenial; urgency=medium
4743-
4744- * New upstram release, 1.10.0 bzr 4572:
4745- - Support python3, drop support for python2.
4746- - Support django 1.8+.
4747- * debian/control:
4748- - Remove all Upstart related services.
4749- - Remove python-django16 dependency.
4750- - Add python-petname dependency.
4751- - Change dependency python-django-piston to python-django-piston3.
4752- - Depends on dbconfig-pgsql instead of dbconfig-common.
4753- * debian/maas-region-controller.config:
4754- - Preseed dbconfig common to not ask for PG server to use.
4755- * debian/maas-region-controller-min.maas-regiond-worker@.service: Don't
4756- depend on postgresql.service anymore, as it would prevent regiond
4757- to run on machines with a remote PostgreSQL.
4758- * debian/rules: Refactor installation of init scripts so that they are
4759- correctly handled, and maas-regiond is not started on install.
4760-
4761- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 13 Nov 2015 13:13:42 +0000
4762-
4763-maas (1.9.0~rc1+bzr4496-0ubuntu1) wily; urgency=medium
4764-
4765- * New upstream release, 1.9.0 rc1, bzr4496
4766- - MAAS uses wrong IP for DNS record (creates against the
4767- bond). (LP: #LP: #1515498)
4768- - Local archive ignored for deployment. Works for commissioning
4769- and enlistment. (LP: #1515671)
4770- - Fix handling of multiple StaticIPAddress rows with empty IP
4771- addresses. (LP: #1513485)
4772- - Lease parser failure - doesn't update IP on the PXE
4773- NIC. (LP: #1513485)
4774- - Cannot claim sticky IP address for device with
4775- parent. (LP: #1514486)
4776- - Cluster downloads boot-images from managed network (pxe) instead
4777- of network used to connect to Region. (LP: #1514883)
4778- - Updating/modifying/assigning vlans, spaces, fabrics, subnets
4779- doesn't allow specifying names and lock to ID's. (LP: #1510917)
4780- - MAAS should prevent deploying nodes with PXE interface
4781- 'unconfigured'. (LP: #1513095)
4782- - MTU should be a set on the VLAN, and able to override on the
4783- interface. (LP: #1508056)
4784- - Internal Server Error when creating/editing cluster interface
4785- when the Cluster is disconnected. (LP: #1439476)
4786- - Non-interactive way to change password. (LP: #1510224)
4787- - When a bond is created all IP address associated with the bond
4788- members should be removed. (LP: #1513111)
4789- - MAAS does not provide a dump of the config it passes to curtin for
4790- networking and storage. (LP: #1487135)
4791- - MAAS should not offer EXT3, rather VFAT, EXT2, EXT4. (LP: #1512959)
4792- - Network constraints for juju. (LP: #1505031)
4793- - Creating a partition or a Volume Group on the whole disk leaves
4794- free space. (LP: #1509535)
4795- - Should not allow partitions to be created on bcache
4796- device. (LP: #1511493)
4797- - Storage section should only be editable when Ready or
4798- Allocated. (LP: #1503475)
4799- - maasserver.api.tests.test_fannetworks.TestFanNetworksAPI.test_read
4800- fails randomly. (LP: #1512832)
4801- - creating a logical volume on a partition that is too small almost
4802- works, resulting in strange error messages. (LP: #1508754)
4803- - [UI] Keep selected nodes selected after action. (LP: #1503925)
4804- - [UI] Refresh UI cache after an upgrade to avoid seeing
4805- garbage. (LP: #1515380)
4806- - [UI] Boot disk is not lighted nor can be changed. (LP: #1510106)
4807- - [UI] Can't remove / delete a partition with a filesystem under
4808- 'Available disks and partitions'. (LP: #1510118)
4809- - [UI] Creating a partition should allow to select filesystem and
4810- mountpoint. (LP: #1510153)
4811- - [UI] When selecting a device, ensure padding between buttons is
4812- 20px. (LP: #1510468)
4813- - [UI] Misaligned mount point column on used disks table. (LP: #1510455)
4814- - [UI] Align the individual storage actions with the name field,
4815- rather than the tickbox. (LP: #1510469)
4816- - [UI] can't add physical interface. (LP: #1503479)
4817- - [UI] Containers (lxc, kvm) data missing on node details. (LP: #1503474)
4818- - [UI] Unable to unmount a filesystem in the UI. (LP: #1513271)
4819- - [UI] Animation missing on show members and select node. (LP: #1503536)
4820- - [UI] Add tooltips to icons. (LP: #1510482)
4821- - [UI] Add tooltips to inactive buttons. (LP: #1510486)
4822-
4823- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 05 Nov 2015 08:29:06 -0500
4824-
4825-maas (1.9.0~beta2+bzr4456-0ubuntu1) wily; urgency=medium
4826-
4827- * New upstream release, 1.9.0 beta2, bzr4456:
4828- - New capabilities for subnets, vlan, spaces and
4829- fabrics. (LP: #LP: #1511257)
4830- - Upgrade left a PXE NIC"s on nodes without a subnet associated
4831- causing deploy issues. (LP: #LP: #1509077)
4832- - DNS record doesn't get created against the PXE
4833- interface (LP: #1512109)
4834- - bcache cache_mode setting not configured on
4835- servers (LP: #1510334)
4836- - Administrators unable to delete users using the API (LP: #1510210)
4837- - Can create a VolumeGroup (vg0) without having created
4838- a partition on the boot disk (LP: #1509536)
4839- - set-boot-disk yields in a machine not being able to
4840- deploy (LP: #1501400)
4841- - Deploying Other OS' (CentOS, Windows) should not configure
4842- custom storage (LP: #1504956)
4843- - Add RAID 10 support (LP: #1509164)
4844- - MAAS should download grub from grub-efi-amd64-signed package
4845- instead of the archive path (LP: #1511437)
4846- - Fails to deploy with UEFI (LP: #1510120)
4847- - previous owner of node can use oauth creds to retrieve current
4848- owner's user-data (LP: #1507586)
4849- - IP range validation for too small ranges (LP: #1507630)
4850- - test__calls_update_host_maps_for_next_ip_managed_subnet
4851- can fail randomly (LP: #1507630)
4852- - No way to disable maas-proxy (LP: #1511071)
4853- - [UI] HWE naming needs to be clearer (LP: #1505034))
4854- - [UI] Angular $digest loop issue on node details page (LP: #1509476)
4855- - [UI] New nodes interfaces doesn't show which interface is the
4856- PXE interface (LP: #1509473)
4857- - [UI] When partitioning, there should be 20px padding between
4858- the sizing fields (LP: #1510471)
4859- - [UI] On the available table, add model and serial to the
4860- name column (LP: #1510467)
4861- - [UI] On the available table, change “available space” to
4862- “size” for consistency (LP: #1510466)
4863- - [UI] when formatting/mounting, the button says “Format & Mount”
4864- this should just be “Mount” (LP: #1510472)
4865- - [UI] Tickbox on create bond networking (LP: #1503533)
4866- - [UI] On the file system table, change name to “File system”
4867- (lower case S) (LP: #1510447)
4868- - [UI] When creating bcache and raid, remove the empty column
4869- between the config fields. (LP: #1510474)
4870- - [UI] On the available table, make sure all buttons are
4871- lowercase (LP: #1510488)
4872- - [UI] Subnets filter doesn't show network, it shows name
4873- instead (LP: #1511174)
4874- - [UI] can't edit / add storage tags (LP: #1509417)
4875- - [UI] Hover state for networking doesn't work (LP: #1510891)
4876- - [UI] change "edit tag" link to icon storage (LP: #1510458)
4877- - [UI] Can no longer see the IP address PXE interface gets
4878- on commissioning (LP: #1510629)
4879- * debian/control: Bump Dep on python-curtin to > 0.1.0~bzr275.
4880-
4881- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 28 Oct 2015 21:20:39 -0400
4882-
4883-maas (1.9.0~beta1+bzr4417-0ubuntu1) wily; urgency=medium
4884-
4885- * New upstream release, 1.9.0 beta1, bzr4415:
4886- - Various UI fixes and improvements
4887- - Add ability to create LVM.
4888- - Add ability to create RAID.
4889-
4890- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 22 Oct 2015 14:05:50 -0400
4891-
4892-maas (1.9.0~alpha5+bzr4398-0ubuntu1) wily; urgency=medium
4893-
4894- * New upstream release, 1.9.0 Alpha 5, bzr4398:
4895- - Various UI fixes and improvements.
4896- - Add ability to create partitions in the UI.
4897- - Add ability to create Bcache (create cache sets and backing devices).
4898- - Check and warns users about missing power driver tools (LP: #1381000).
4899- - Add fabric class_type.
4900-
4901- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 15 Oct 2015 21:22:44 -0700
4902-
4903-maas (1.9.0~alpha4+bzr4371-0ubuntu1) wily; urgency=medium
4904-
4905- * New upstream release, 1.9.0 Alpha 4, bzr4371:
4906- - Various UI fixes and improvements.
4907- - Various concurrency issues fixed.
4908- - Do not create MBR bigger than 2 TiB, otherwise MAAS will fail to
4909- deploy on disks larger than 2 TiB.
4910- - Fix broken migration due to missing import (LP: #1504340)
4911-
4912- -- Andres Rodriguez <andreserl@ubuntu.com> Wed, 07 Oct 2015 13:02:53 -0700
4913-
4914-maas (1.9.0~alpha3+bzr4355-0ubuntu1) wily; urgency=medium
4915-
4916- * New upstream release, 1.9.0 Alpha 3, bzr4355
4917- - Node network configuration (VLAN, aliases, bond's).
4918- - Subnets page.
4919- - Mount, Unmount filesystems. Formatting, unformatting.
4920- - Create partitions.
4921- - Checks for missing power drivers tool and warns the users.
4922- * debian/control: Recommends on apache2.
4923-
4924- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 29 Sep 2015 12:53:36 -0400
4925-
4926-maas (1.9.0~alpha2+bzr4322-0ubuntu1) wily; urgency=medium
4927-
4928- * New upstream release, 1.9.0 Alpha 2, bzr4322:
4929- - Native support for Network Configuration (IP assignment, VLANs, bonds)
4930- - First class support for CentOS
4931- - Status updates from curtin/cloud-init
4932- - Support for fabrics, spaces, subnets and fans.
4933- - Support for commissioning actions.
4934-
4935- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 01 Sep 2015 19:04:39 -0400
4936-
4937-maas (1.9.0~alpha1+bzr4221-0ubuntu1) wily; urgency=medium
4938-
4939- * New upstream release, 1.9.0 Alpha 1, bzr4218:
4940- - Native storage support (Flat, LVM, bcache, RAID).
4941- - New config files (regiond.conf, clusterd.conf)
4942- - New Python Power Drivers.
4943- - Better support for HWE Kernels.
4944-
4945- [ Scott Moser ]
4946- * maas-proxy: sync apt specific squid config with squid-deb-proxy
4947- (LP: #1474417)
4948-
4949- [ Raphaël Badin ]
4950- * Enable proxy_wstunnel module.
4951- * Drop dependency on python-iscpy: the code has been integrated into
4952- MAAS. (LP: #1413388).
4953-
4954- [ Gavin Panella ]
4955- * Use new local configuration support for the cluster.
4956-
4957- [ Andres Rodriguez ]
4958- * Refactor maas-dns upgrade code so it doesn't break local DNS config
4959- and it gets migrated (LP: #1413388)
4960- - debian/maas-region-controller.postinst: Ensure DNS config
4961- migration is always run.
4962- * debian/control: Make maas-dns a Dependy of maas-region-controller.
4963- * Update the location of dhcpd.conf and dhcpd6.conf to be /var/lib/maas/
4964- and handle upgrades. (LP: #1482857)
4965- * Move /etc/maas/maas-proxy.conf to /usr/share/maas/maas-proxy.conf as
4966- this is not a config we want users to modify. (LP: #1482859)
4967- * Move /etc/maas/maas-http.conf to /usr/share/maas/maas-http.conf as
4968- this is not a config we want users to modify. (LP: #1482858)
4969- * debian/control:
4970- - Add missing dependency on python-curtin.
4971- - Drop python-lockfile as it is no longer used.
4972- - Depend on python-curtin >= 0.1.0~bzr247.
4973-
4974- -- Andres Rodriguez <andreserl@ubuntu.com> Fri, 12 Jun 2015 14:16:47 -0400
4975-
4976-maas (1.8.0+bzr4001-0ubuntu1) trusty; urgency=medium
4977-
4978- * New upstream release, 1.8.0.
4979-
4980- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 09 Jun 2015 20:57:42 -0400
4981-
4982-maas (1.8.0~rc3+bzr4000-0ubuntu1) trusty; urgency=medium
4983-
4984- * New upstream release, 1.8.0 RC3 bzr4000.
4985-
4986- [ Raphaël Badin ]
4987- * Remove unused dependencies: python-amqp and python-txamqp.
4988-
4989- -- Andres Rodriguez <andreserl@ubuntu.com> Thu, 04 Jun 2015 16:32:02 -0400
4990-
4991-maas (1.8.0~rc2+bzr3989-0ubuntu1) trusty; urgency=medium
4992-
4993- * New upstream release, 1.8.0 RC2 bzr3983.
4994-
4995- -- Andres Rodriguez <andreserl@ubuntu.com> Tue, 02 Jun 2015 09:27:54 -0400
4996-
4997-maas (1.8.0~rc1+bzr3972-0ubuntu1) trusty; urgency=medium
4998-
4999- * New upstream release, 1.8.0 RC1 bzr3972.
5000- * debian/copyright: Add copyright headers for ng-tags-input.js.
The diff has been truncated for viewing.

Subscribers

People subscribed via source and target branches