Merge lp:~jamesj/charms/trusty/haproxy/xenial-support into lp:charms/trusty/haproxy
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Merged at revision: | 104 | ||||
| Proposed branch: | lp:~jamesj/charms/trusty/haproxy/xenial-support | ||||
| Merge into: | lp:charms/trusty/haproxy | ||||
| Diff against target: |
662 lines (+379/-190) 7 files modified
files/nrpe/check_haproxy.sh (+1/-1) hooks/hooks.py (+8/-6) hooks/tests/test_install.py (+3/-1) metadata.yaml (+3/-0) tests/10_deploy_test.py (+0/-182) tests/11_deploy_test_trusty.py (+182/-0) tests/12_deploy_test_xenial.py (+182/-0) |
||||
| To merge this branch: | bzr merge lp:~jamesj/charms/trusty/haproxy/xenial-support | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Review Queue (community) | automated testing | Needs Fixing on 2016-09-11 | |
| Cory Johns | 2016-07-05 | Approve on 2016-07-14 | |
|
Review via email:
|
|||
Commit Message
Install python-apt for Xenial compatibility.
Included some initial fixes for Python3 compatibility.
Description of the Change
Install python-apt for Xenial compatibility.
Included some initial fixes for Python3 compatibility.
- 105. By James Jesudason on 2016-07-07
-
Change to the nagios check to handle versions > 1.5
- 106. By James Jesudason on 2016-07-08
-
Merge fixes to the tests
| James Jesudason (jamesj) wrote : | # |
> James,
>
> Thanks for this contribution! It will be great to see the haproxy charm get
> support for Xenial.
>
> This was missing a deploy test for Xenial, and I hit some errors while testing
> it. I created a MP against this proposed branch with a Xenial test, test
> fixes, and adding the series to the metadata:
> https:/
> support/
> proposed branch and it will automatically update this MR.
>
Done - thanks for doing that
> I tried to (trivially) add support for Precise as well, but ran into an error:
> http://
> delta was between the Precise version of this charm and this one.
>
> With those suggested fixes, I think this would be good. Because of the new
> process for promulgation, though, we will need one of the maintainers (Juan or
> Tom) to publish this charm into the store under their (or an appropriate
> group) namespace before we can move forward with merging and re-promulgation.
At least, if we can get the change merged, it can be used from LP. Getting the update into the store would be great as we seem to be behind in getting Xenial support there for a number of projects.
| Cory Johns (johnsca) wrote : | # |
This has my +1 to merge, but due to this now being multi-series and the new conventions regarding hte charm store and storing charms in Launchpad, the repo will need to move from lp:charms/trusty/haproxy to be a top-level project at lp:charm-haproxy and the listed owner of the charm on jujucharms.com will need to change to either one of the maintainers or an appropriate team (e.g., haproxy-team, which would need to be created), as decided by the maintainers.
| James Jesudason (jamesj) wrote : | # |
> This has my +1 to merge, but due to this now being multi-series and the new
> conventions regarding hte charm store and storing charms in Launchpad, the
> repo will need to move from lp:charms/trusty/haproxy to be a top-level project
> at lp:charm-haproxy and the listed owner of the charm on jujucharms.com will
> need to change to either one of the maintainers or an appropriate team (e.g.,
> haproxy-team, which would need to be created), as decided by the maintainers.
Is there any chance that we can get the first step of merging this done? The renaming of the branch can happen later, when everyone is ready. I'm having to use my own fork for deployment at the moment.
| Charles Butler (lazypower) wrote : | # |
For the purposes of an Audit trail:
I've pushed the branch to lp:~charmers/charms/trusty/haproxy/trunk
When the repository potentially moves location, we will need to ensure we've updated the store entry. This is also incomplete, as we have only merged the requested branch review.
We still need to address and triage the points brought up in:
| Review Queue (review-queue) wrote : | # |
The results (PASS) are in and available here: http://
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://
| Review Queue (review-queue) wrote : | # |
The results (PASS) are in and available here: http://
| Review Queue (review-queue) wrote : | # |
The results (PASS) are in and available here: http://
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://
| Review Queue (review-queue) wrote : | # |
The results (PASS) are in and available here: http://
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://
| Review Queue (review-queue) wrote : | # |
The results (PASS) are in and available here: http://
| Review Queue (review-queue) wrote : | # |
This item has failed automated testing! Results available here http://

James,
Thanks for this contribution! It will be great to see the haproxy charm get support for Xenial.
This was missing a deploy test for Xenial, and I hit some errors while testing it. I created a MP against this proposed branch with a Xenial test, test fixes, and adding the series to the metadata: https:/ /code.launchpad .net/~johnsca/ charms/ trusty/ haproxy/ xenial- support/ +merge/ 299470 If that looks good to you, please merge it into your proposed branch and it will automatically update this MR.
I tried to (trivially) add support for Precise as well, but ran into an error: http:// pastebin. ubuntu. com/18729639/ I didn't look any deeper into what the delta was between the Precise version of this charm and this one.
With those suggested fixes, I think this would be good. Because of the new process for promulgation, though, we will need one of the maintainers (Juan or Tom) to publish this charm into the store under their (or an appropriate group) namespace before we can move forward with merging and re-promulgation.