Merge lp:~thomnico/charms/precise/elasticsearch/canonical-se into lp:~charmers/charms/precise/elasticsearch/trunk
Proposed by
Nicolas Thomas
Status: | Work in progress |
---|---|
Proposed branch: | lp:~thomnico/charms/precise/elasticsearch/canonical-se |
Merge into: | lp:~charmers/charms/precise/elasticsearch/trunk |
Diff against target: |
148 lines (+30/-57) 5 files modified
hooks/config-changed (+2/-2) hooks/install (+24/-52) hooks/start (+2/-1) hooks/stop (+1/-1) revision (+1/-1) |
To merge this branch: | bzr merge lp:~thomnico/charms/precise/elasticsearch/canonical-se |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Stuart Bishop (community) | Abstain | ||
Whit Morriss (community) | Disapprove | ||
Review via email: mp+219110@code.launchpad.net |
Description of the change
Updated to use the repo provided by elasticsearch hence upgraded,
Adapted to new CLI/service .. much cleaner IMHO.
To post a comment you must log in.
Unmerged revisions
- 29. By Nicolas Thomas
-
move to use the repositories provided by elasticsearch hence upgrade version.
Adapt to the correct filesystem.
TODO test the EC2 autodetect feature.
Nicolas,
Thanks for your change submission. I do agree that this is much cleaner. However I see an issue with a user upgrading from revision 28 to this revision: since there is no upgrade-charm logic to handle the change in the location of the service, config, and possibly data files, a user attempting to upgrade this charm could end up in a state of conflict. Unfortunately, I can't give my +1 for this change unless an upgrade-charm hook is added to handle this.
Additionally, I believe there is an Ansible-based charm also being reviewed, which would be another route for cleaning up the elasticsearch charm. Please take a look at the discussion on https:/ /bugs.launchpad .net/charms/ +bug/822979 regarding the charm at https:/ /code.launchpad .net/~michael. nelson/ charms/ precise/ elasticsearch/ trunk to see if you might prefer to use your efforts to help with that.