Merge lp:~evarlast/charms/trusty/elasticsearch/add-version-config into lp:~charmers/charms/trusty/elasticsearch/trunk
| Status: | Rejected |
|---|---|
| Rejected by: | Marco Ceppi on 2015-02-13 |
| Proposed branch: | lp:~evarlast/charms/trusty/elasticsearch/add-version-config |
| Merge into: | lp:~charmers/charms/trusty/elasticsearch/trunk |
| Diff against target: |
96 lines (+41/-7) 4 files modified
config.yaml (+13/-0) tasks/install-elasticsearch.yml (+13/-6) tests/01-config-changes (+8/-1) tests/helpers/__init__.py (+7/-0) |
| To merge this branch: | bzr merge lp:~evarlast/charms/trusty/elasticsearch/add-version-config |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Kevin W Monroe | Disapprove on 2015-02-13 | ||
| Whit Morriss (community) | Needs Fixing on 2015-01-20 | ||
| Review Queue (community) | automated testing | Needs Fixing on 2014-11-21 | |
| Michael Nelson (community) | Approve on 2014-10-24 | ||
| charmers | 2014-10-10 | Pending | |
|
Review via email:
|
|||
Description of the Change
Allow specifying the version of the elasticsearch package in charm config.
Use case: as an op, I must control what version of services I roll out to my production and other environments, so that I can test new versions while retaining the ability to roll out new old versions in both existing and new environments.
| Michael Nelson (michael.nelson) wrote : | # |
Hi Jay,
Thanks for the update. Just fyi, the reason this hasn't been an issue in our usage is that as an op, we configure our own repository (ie. we control the private repo we're using to install from).
I understand that's not useful for everyone, so another option is to instead provide the deb in the charm (files/
That said, +1 to your change.
I need to update the tests so that test deps are installed (nosetests), and the amulet tests run on trusty, not precise (I'll find out about that).
Thanks!
| Review Queue (review-queue) wrote : | # |
This items has failed automated testing! Results available here http://
| Michael Nelson (michael.nelson) wrote : | # |
You probably want to remerge trunk from
https:/
| Jay R. Wren (evarlast) wrote : | # |
Ah! Thanks for this.
I missed that the official charm is from ~onlineservices
On Sun, Nov 23, 2014 at 2:55 PM, Michael Nelson <
<email address hidden>> wrote:
> You probably want to remerge trunk from
>
>
> https:/
> --
>
> https:/
> You are the owner of
> lp:~evarlast/charms/trusty/elasticsearch/add-version-config.
>
| Whit Morriss (whitmo) wrote : | # |
Taking a look at this branch. lp:~evarlast/charms/trusty/elasticsearch/add-version-config does not merge cleanly into head of https:/
I'm also curious what the relationship of the charmer/charms version and the online services version (which is more active) is / should be. The online services copy is clearly the canonical one, but whose responsibility is it to keep the charmers copy synced?
| Whit Morriss (whitmo) wrote : | # |
Marking a need fixing until the merge/upstream resolution gets figured out. Thanks y'all!
| Kevin W Monroe (kwmonroe) wrote : | # |
Just spoke to Jay. This change was needed last year to be able to handle a specific elasticsearch minor rev. It hasn't been needed since.
If this version-config feature becomes needed in the future, Jay will refactor his changes to apply to the latest ~onlineservices
As a side note, if this feature does become active again, please watch out for immutable config. If the version config is changed post-deployment, the charm will need to handle that. Adding config-changed to the yml may be all you need to do this:
...
+ tags:
+ - config-changed
+ - install
+ - upgrade-charm
...
Unmerged revisions
- 36. By Jay R. Wren on 2014-10-10
-
Add version config option
Disabled install-recommends.
Disabled extra unneeded runs of apt-get update.

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