add high level design document(s)

[Jamie Strandboge]

This is a tracking bug for a dependency of the maas MIR (bug #961344).

MAAS is something that enterprises will use to deploy services and machines that are reachable over the network so highlevel documentation would aid in more peer review and help adoption in the enterprise. For the design document, just some high level stuff with a few diagrams so that people understand the architecture, network topologies, how nodes are added/deleted/provisioned, the role of users, etc. The security design document would complement this and mention how ssh access works, the various daemon that are running on the server, the technologies used by the server, admin vs non-admin users, a node's default configuration, etc. The two could be in one document and could be in a man page or some part of the official documentation.

[Scott Moser (smoser)]

I dropped the precise and quantal tasks.
This is not going to make quantal. i someone wants to add these back, feel free to do so.

[Julian Edwards (julian-edwards)]

Nick, if you work on this I have a document that you could use as a starting point.

[Bryan Taylor (btaylor-b)]

Yeah would be nice to know how this thing works. I have never been able to get MAAS to work... EVER

In comparison and contrast I have used Dell Crowbar and can PXE provision ubuntu nodes all day long.

Bryan

[Julian Edwards (julian-edwards)]

Bryan, have you tried following the step-by-step instructions at
maas.ubuntu.com at all?

[Andres Rodriguez (andreserl)]

Dear user,

This is an automated message.

We believe this bug report is no longer an issue in the latest version of MAAS. For such reason, we are making this issue as Won't Fix. If you believe this issue is still present in the latest version of MAAS, please re-open this bug report.

[Adam Collard (adam-collard)]

https://maas.io/how-it-works