[MIR] juju, txaws, txzookeeper
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
txaws (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
txzookeeper (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
This is a MIR for juju, and two of its chief dependencies, txaws and txzookeeper. There will be a separate MIR for zookeeper since it is a substantial project and stands alone by itself.
== Availability ==
juju was called ensemble before, and entered universe during the oneiric dev cycle. txzookeeper is a twisted zookeeper plugin that was created specifically for juju, and also entered universe during the oneiric cycle. txaws has been available since lucid.
== Rationale ==
juju addresses a need not addressed by plain configuration management or "Platform as a service" offerings. Juju allows one to create and share sets of automated tools for managing services called charms. It has been identified as strategically important to help Ubuntu users take advantage of the cloud and also to create their own scale-out clouds.
== Security ==
juju has not had any "CVE"'s reported against it, and has not been recommended for production usage just yet. It does have a well defined security model that relies mostly on SSH and firewalls for transport layer security. The security model has been examined for weaknesses and bugs are open and tracked upstream to address those weaknesses.
https:/
== Quality assurance ==
Juju is a CLI tool and so does require a bit of documentation reading to understand it.
There are no major bugs open in Debian or Ubuntu for any of these packages.
Upstream uses a Test Driven Dev model, and so there is a rich and rigorous test suite which is run on package build and will fail the build if the test suite fails. Packages are built daily using launchpad daily build PPA's and most developers and interested users test these packages so quality remains high. There are also functional tests that are run on each commit upstream here:
txaws has a rich test suite, which is run and failed on during build.
txzookeeper also has a rich test suite, however, it is somewhat dangerous to run as it will completely delete a local zookeeper's contents, so until this bug is fixed, we can't run it on package build:
https:/
UI standards:
N/A
== Dependencies ==
These are the non-main deps/build-deps for the 3 libraries mentioned here:
Deps/Build_Deps:
zookeeper - being addressed in a seperate MIR
Recommends:
pydot - Used to produce "dot" output. Can be dropped to Suggests or added to this MIR. It is a very small python library. I think its worthwhile to add it, but would not want to see this MIR blocked because of it, as this is a very small bit of functionality. pydot also depends on pyparsing, which is in universe. pydot does not seem well maintained, having missed *many* upstream releases.
== Standards compliance ==
All 3 packages are very straightforward and use minimal dh7 rules. They have a few lintian warnings, but mostly due to out of date standards or minor formatting issues.
== Maintenance ==
The package is well maintained in Ubuntu directly. The server team is committed to making juju a big part of Ubuntu's cloud strategy. The package is not in Debian just yet, as its ties to Ubuntu are very strong, though at some point we'd like to make it available in Debian once things stop changing so rapidly.
== Background information ==
This MIR is a part of the following blueprint:
https:/
Changed in juju (Ubuntu): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in txaws (Ubuntu): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in txzookeeper (Ubuntu): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in juju (Ubuntu): | |
importance: | Undecided → High |
Changed in txaws (Ubuntu): | |
importance: | Undecided → High |
Changed in txzookeeper (Ubuntu): | |
importance: | Undecided → High |
txzookeeper review:
* no CVE history
* no sudo fragments, dbus services, setuid binaries, initscripts or daemons
* lintian clean
* has test suite, but not run (LP: #912508). Wrote QRT script for this for now
* code is very clean with more that 3x more test code than library code. I like that. :)
* build depends are all in main
* while the package is only in Ubuntu, it is supported by the server team and with upstream employed by Canonical
With the above review, txzookeeper looks good for main.