~rvb/maas/vlan-to-network2

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
About this documentation
========================

This is the documentation for Canonical's MAAS software. If you aren't
sure what that is, you should probably skip everything else and head
straight to the :ref:`orientation` section where it is explained.
Like any software though, it can be frustrating if you don't know how
bits of it work, how to achieve certain goals or what to do when
things go wrong. Amongst its various sections, this manual aims to
answer all those questions and plenty more you haven't even thought of
yet.


Getting it
----------

In a cunning move, the current documentation always lives, and is
built from, the main MAAS source code. That means that whatever MAAS
package you have installed, or even if you are really living life on
the edge and have checked out a development version from Launchpad,
this documentation should be the latest and most appropriate version
for the software you are running.  However, it is also possible that
there have been further sections or more helpful, or clearer bits
added since the package you are using was made. For this reason you
can always find the latest documentation online here:
http://maas.ubuntu.com


Contributing
------------

If you have some extra information to add, or think you have spotted
an error or something out of date, we really want to hear about
it.  Please `File a bug report`_ or `contact us directly`_.  In addition
you can talk to us on the Freenode IRC channel #maas.

.. _File a bug report:
  https://bugs.launchpad.net/maas/+filebug

.. _contact us directly:
  https://launchpad.net/~maas-maintainers/+contactuser

If you see something wrong with this documentation, you can help us fix it.
Download the source to MAAS by following the instructions in
:doc:`the hacking guide <hacking>`, make your changes, and propose a merge
against lp:maas on Launchpad.  The documentation source lives in the top-level
``doc/`` directory.