Ubuntu

Activity log for bug #966617

Date Who What changed Old value New value Message
2012-03-27 21:05:55 Jamie Strandboge bug added bug
2012-03-27 21:06:04 Jamie Strandboge nominated for series Ubuntu Precise
2012-03-27 21:06:04 Jamie Strandboge bug task added juju (Ubuntu Precise)
2012-03-27 21:06:04 Jamie Strandboge nominated for series Ubuntu Q-series
2012-03-27 21:06:04 Jamie Strandboge bug task added juju (Ubuntu Q-series)
2012-03-27 21:06:11 Jamie Strandboge juju (Ubuntu Q-series): status New Triaged
2012-04-10 17:45:26 Jamie Strandboge juju (Ubuntu Precise): importance Undecided High
2012-04-19 12:18:43 Jamie Strandboge 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 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). 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).
2012-07-12 20:24:33 Clint Byrum tags rls-p-tracking
2012-07-12 20:24:51 Clint Byrum bug task added juju
2012-07-12 20:24:59 Clint Byrum juju: importance Undecided High
2012-10-10 19:16:02 Clint Byrum juju (Ubuntu Quantal): status Triaged Won't Fix
2012-10-18 17:26:37 Clint Byrum juju: status New Triaged
2012-10-25 07:28:57 Martin Packman bug task added juju-core
2012-10-25 07:29:09 Martin Packman juju-core: importance Undecided High
2012-10-25 07:29:09 Martin Packman juju-core: status New Triaged
2012-10-25 07:49:41 Martin Packman bug task deleted juju-core
2013-10-12 02:34:23 Curtis Hovey juju: importance High Low