New charm proposal: txstatsd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Juju Charms Collection |
Wishlist
|
Unassigned |
Bug Description
Hi,
Here's my proposed first charm: txstatsd.
I'm sure it needs a lot of work, and it should be packaged, but I wanted to push it up for review.
lp:~james-w/charm/oneiric/txstatsd/initial
It requires graphite as well for the "carbon" relation. I have an even crappier version of that charm
here.
Thanks,
James
Mark Mims (mark-mims) wrote : | #1 |
Changed in charm: | |
status: | New → Incomplete |
Mark Mims (mark-mims) wrote : | #2 |
removing new-charm tag
please add this back when the charm is updated and it'll automatically get put in the review queue again.
Thanks!
tags: | removed: new-charm |
Jorge Castro (jorge) wrote : | #3 |
Hi James, any update on this? Need help with anything?
On Mon, 19 Dec 2011 18:31:46 -0000, "Jorge O. Castro" <email address hidden> wrote:
> Hi James, any update on this? Need help with anything?
Hi,
I hear u1 have this puppetised now, so I was thinking about reworking
these charms to be based on that.
I'll take some time over the vacation to pick these up again and try and
get them to an acceptable state.
Thanks,
James
Launchpad Janitor (janitor) wrote : | #5 |
[Expired for Juju Charms Collection because there has been no activity for 60 days.]
Changed in charms: | |
status: | Incomplete → Expired |
James Westby (james-w) wrote : | #6 |
Hi,
I've done another pass at this charm and fixed most of the things that Mark suggested,
as well as fixing it for upstream changes and adding some other improvements.
Thanks,
James
Changed in charms: | |
status: | Expired → New |
James Westby (james-w) wrote : | #7 |
Changed in charms: | |
importance: | Undecided → Wishlist |
stopper:
- needs some sort of license (I just grab them from other charms)
maybe a stopper(?):
- metadata says requires carbon, but there're no hooks for that relation. Sorry, I don't know if that's a stopper for actual promulgation or not. Does the charm do a whole lot without that hook?
recommendations /discussion:
- metadata: description. .. we should copy the summary again at the very least. maybe even blank?
- no need to open internal ports (8125) unless you intend for them to be external someday. Everything's open internally for the foreseeable future.
- maybe use an upstart script for your service to survive reboots?
- maybe pick some standard place to install the service (/usr/local, /opt, or even /usr)? It'd make it easier for someone else to come along and see the branch, scripts, pid-files, logs, etc when debugging.