Charm Needed: DataStax Opscenter

Bug #1279447 reported by Charles Butler
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juju Charms Collection
Incomplete
Low
Charles Butler

Bug Description

Changed in charms:
assignee: nobody → Charles Butler (lazypower)
status: New → In Progress
importance: Undecided → Low
Changed in charms:
status: In Progress → New
Changed in charms:
status: New → In Progress
status: In Progress → Incomplete
Revision history for this message
Marco Ceppi (marcoceppi) wrote :

Hi Chuck, see my review below and thanks for the submission!

# Proof

Nothing major, just a few INFO lines about missing hooks

# Review

- You need to have a fully qualified email address for the maintainer field.

- You're implementing the HTTP interface, but don't have the required hook for opscenter to provide the data for that interface, see: https://github.com/charms/wordpress/blob/master/hooks/website-relation-joined

- The README seems a bit light, but does cover most of the information required

- There has been a lot of work recently to add SSL support in a generic and repeatable way to charms, I'd consider following that convention https://code.launchpad.net/~hazmat/charms/precise/mysql/ssl-everywhere/+merge/207904 has an example

- Icon looks good!

- Tests need to use sudo for operations that require super user permissions

- The 100_deploy test doesn't seem to do much other than validate that the environment comes back with a started state. It'd be preferable to see exercising of relation information and validation of configuration values.

- repo_key URL is susceptible to MITM attacks, since datastax supports SSL, use https to fetch the key. Actually, I see you're also comparing a sha1sum of the key, which is great. Having both SSL and the sum won't hurt though.

- It might be worth generating a self-signed cert during config-changed just to keep going regardless of users input

Thanks for the submission!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.