Charm needed: loggerhead
Bug #907021 reported by
Jelmer Vernooij
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juju Charms Collection |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
I'm working on a charm for loggerhead.
Related branches
| Changed in charm: | |
| status: | New → In Progress |
| assignee: | nobody → Jelmer Vernooij (jelmer) |
| Changed in charms: | |
| assignee: | Jelmer Vernooij (jelmer) → nobody |
| status: | In Progress → Confirmed |
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #1 |
| Changed in charms: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Hi Jelmer. The charm looks good. The only issue I would take is that the 'base' option has no default, and if the charm is deployed, will result in a non-useful loggerhead.
It also doesn't do open/close port so it won't be usable on EC2.
I went ahead and added a default of branching lp:juju into /mnt just to show the capabilities, and then other methods can be used (subordinates most likely) to get write capabilities.
Since the charm was fundamentally sound and the things I added were just minors, I went ahead and promulgated this. lp:charms/loggerhead.