Merge lp:~paulgear/charms/trusty/memcached/allow-rsync-firewall into lp:charms/trusty/memcached
| Status: | Merged |
|---|---|
| Merged at revision: | 68 |
| Proposed branch: | lp:~paulgear/charms/trusty/memcached/allow-rsync-firewall |
| Merge into: | lp:charms/trusty/memcached |
| Diff against target: |
33 lines (+13/-0) 2 files modified
README.md (+10/-0) hooks/memcached_hooks.py (+3/-0) |
| To merge this branch: | bzr merge lp:~paulgear/charms/trusty/memcached/allow-rsync-firewall |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Adam Israel | Approve on 2015-03-26 | ||
| Review Queue (community) | automated testing | Needs Fixing on 2015-03-03 | |
| charmers | 2015-02-24 | Pending | |
|
Review via email:
|
|||
Description of the Change
When fixing a couple of other bugs I realised that there is explicit support in the hooks for nrpe-external-
| Adam Israel (aisrael) wrote : | # |
Hi Paul,
Thanks again (and again) for your work on improving the memcached charm. This is a minor addition, but I'd like to see this new functionality added to the unit tests, and have the functionality documented in the README. It'll be good to see this added nagios work landed.
| Brad Marshall (brad-marshall) wrote : | # |
What new functionality are you talking about here? This is a simple addition of a firewall rule to make the existing functionality work after it was broken in the python rewrite. Without it, the existing code for nrpe-external-
| Adam Israel (aisrael) wrote : | # |
Hi Brad,
There are two other related merge proposals from Paul that I tested, along with this one. I wasn't able to get any of the nrpe functionality to work. There's nothing in the README about its usage, nor any unit tests to verify functionality across substrates. At the very least, I'd like to see some instructions on using nrpe with the memcached charm, so that I can fully test that functionality.
| Brad Marshall (brad-marshall) wrote : | # |
Ah, I see. This is functionality that has been in the charm since 2013, hence my surprise that you were regarding it as new. And I believe it was working until someone did a python rewrite, and broke it. I'll look at writing up some quick instructions on how to use nrpe-external-
| Adam Israel (aisrael) wrote : | # |
Hey Paul,
Thanks for the updated docs. Unfortunately, I'm still running into an issue.
`juju deploy nrpe-external-
Where are you deploying nrpe-external-
| Adam Israel (aisrael) wrote : | # |
Hi Paul,
Following up on my previous comment. There is a rewrite of the trusty/npre charm that includes the nrpe-external-
Thanks again for your work on this!
| Brad Marshall (brad-marshall) wrote : | # |
Adam,
> Where are you deploying nrpe-external-
We are using a local copy of the charm from precise, checked out into a trusty directory.
> If you can update the doc to reference nrpe instead of nrpe-external-
> we'll re-review this once the nrpe charm lands.
We have production instances of memcached (and other charms) using the nrpe-external-
relationship - both internally to Canonical and for customers. We need a working
nrpe-external-
shortcomings of the current code introduced in the python rewrite.
I have been talking to Liam about the upcoming nrpe rewrite and will be working with him to
get the charms on which we rely (at least) updated to support the new interface once it lands,
but it will probably be a phased approach to get rid of the nrpe-external-
Is there any reason not to fix the broken code now? Without this merge, we'll end up maintaining yet another separate branch for customers, which as you know is extra maintenance overhead.
Thanks,
Brad
| Adam Israel (aisrael) wrote : | # |
Hi Brad,
The problem I see is by promoting it to the charm store, we're expecting users to know that they need to manually fork the precise version of the nrpe-external-
If you could expand the README to demystify the process, I'd be happy to approve this in the interim.
| Brad Marshall (brad-marshall) wrote : | # |
Adam,
> The problem I see is by promoting it to the charm store, we're expecting
> users to know that they need to manually fork the precise version of the
> nrpe-external-
> intuitive process.
I agree, the whole n-e-m interface is one huge hack, since you have to have a copy of nagios running outside of Juju to use it. Its all working around not having cross environment relations. Its not pretty, but its what we have to work with for now.
> If you could expand the README to demystify the process, I'd be happy
> to approve this in the interim.
I've just added a quick description of how to use it - its a bit hacky, but its how we're using the charm for now. Once the nrpe rewrite gets landed we can update things to be neater.
Thanks,
Brad
| Adam Israel (aisrael) wrote : | # |
Thanks for all of the work, Paul and Brad! Looks good to me. +1

This items has failed automated testing! Results available here http:// reports. vapour. ws/charm- tests/charm- bundle- test-11064- results