supply high level design documents

Bug #966617 reported by Jamie Strandboge on 2012-03-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyjuju
Low
Unassigned
juju (Ubuntu)
High
Unassigned
Precise
High
Unassigned
Quantal
Undecided
Unassigned

Bug Description

This is a tracking bug for a dependency of the juju MIR (bug #912861).

Juju is a revolutionary technology and 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. This does not have to be a massive book or anything-- for the design document, just some high level stuff with a few diagrams for the different providers so that people understand the architecture, network topologies, use of the bootstrapping node, how zookeeper is used, how charms are deployed, how services are deployed/exposed, etc. The security design document would complement this and mention how ssh access works, environments.yaml, initial security groups, zookeeper ACLs, what juju does to limit access to the bootstrapping node, keeping systems up to date, how charms are run as root (and therefore must be guarded against tampering), how charms once on the bootstrapping node can't be subverted, the security issues we've discussed. The two could be in one document and could be in a man page or in juju.ubuntu.com/docs (ie part of the official documentation).

Changed in juju (Ubuntu Precise):
importance: Undecided → High
description: updated
tags: removed: rls-p-tracking
Changed in juju:
importance: Undecided → High
Changed in juju (Ubuntu Quantal):
status: Triaged → Won't Fix
Changed in juju:
status: New → Triaged
Martin Packman (gz) on 2012-10-25
Changed in juju-core:
importance: Undecided → High
status: New → Triaged
Martin Packman (gz) on 2012-10-25
no longer affects: juju-core
Curtis Hovey (sinzui) on 2013-10-12
Changed in juju:
importance: High → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers