Merge lp:~james-page/charms/trusty/rabbitmq-server/network-splits into lp:~openstack-charmers-archive/charms/trusty/rabbitmq-server/next
| Status: | Merged |
|---|---|
| Merged at revision: | 80 |
| Proposed branch: | lp:~james-page/charms/trusty/rabbitmq-server/network-splits |
| Merge into: | lp:~openstack-charmers-archive/charms/trusty/rabbitmq-server/next |
| Diff against target: |
144 lines (+39/-9) 5 files modified
Makefile (+3/-3) config.yaml (+9/-0) hooks/rabbitmq_server_relations.py (+19/-4) test-requirements.txt (+2/-0) unit_tests/test_rabbitmq_server_relations.py (+6/-2) |
| To merge this branch: | bzr merge lp:~james-page/charms/trusty/rabbitmq-server/network-splits |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Liam Young | Approve on 2015-01-23 | ||
| Review Queue | automated testing | 2015-01-23 | Pending |
| James Page | Pending | ||
| Tim Van Steenburgh | 2015-01-23 | Pending | |
| Cory Johns | 2015-01-23 | Pending | |
|
Review via email:
|
|||
This proposal supersedes a proposal from 2014-07-24.
Description of the Change
Add support for separate 'access-network' configuration.
| James Page (james-page) wrote : | # |
Hi Tim
https:/
RE the charm proof warning; not touching those - not having a default key is intentional 'unset' being a valid state. The code works on the fact that a config-get on unset keys returns None in JSON.
| Cory Johns (johnsca) wrote : | # |
James,
I believe that Tim's point was that the policy was that you still need to provide a default value, even if that value is an empty string. No warnings on `charm proof` is listed on the policy: https:/
Also, my understanding of the "Resubmit" status was that the review was rejected and would need to be resubmitted to be approved; is that not the case?
| James Page (james-page) wrote : | # |
charm proof is wrong - sorry I've discussed this numerous times with Marco - not providing a default value is a perfectly acceptable situation and is used extensively in my charms - Marco did at least drop this to a warning rather than an error but I'm not re-writing all of my charms to comply with a policy that I believe is wrong in this case.
| James Page (james-page) wrote : | # |
I've raised https:/
| James Page (james-page) wrote : | # |
After some discussion with Marco on IRC, he's provided me with a way to have the key, but still leave the default unset; I've updated the charm to reflect this.
charm_lint_check #195 trusty-
LINT OK: passed
charm_unit_test #224 trusty-
UNIT FAIL: unit-test missing
UNIT Results (max last 2 lines):
INFO:root:Search string not found in makefile target commands.
ERROR:root:No make target was executed.
Full unit test output: http://
Build: http://
charm_amulet_test #244 trusty-
AMULET FAIL: amulet-test missing
AMULET Results (max last 2 lines):
INFO:root:Search string not found in makefile target commands.
ERROR:root:No make target was executed.
Full amulet test output: http://
Build: http://
| Review Queue (review-queue) wrote : | # |
This items has failed automated testing! Results available here http://
| Cory Johns (johnsca) wrote : | # |
Test failure is due to a merge conflict, mainly in charmhelpers sync, but there are a couple in the charm itself, as well. I tried my hand at resolving, but there was a bit more than I felt comfortable with making decisions on without deeper knowledge of the charm.
- 73. By James Page on 2015-01-23
-
Optimize calls
- 74. By James Page on 2015-01-23
-
Re-instate configuration
- 75. By James Page on 2015-01-23
-
Aligment on config
- 76. By James Page on 2015-01-23
-
Run flake8 from venv as well

Hi James,
Thanks for this. Code review looks good, but I'm unsure how to do a functional test of this, can you provide instructions?
Also, there are some charm-proof warnings to clean up:
W: config.yaml: option access-network does not have the keys: default
W: config.yaml: option key does not have the keys: default
W: config.yaml: option source does not have the keys: default
Thanks!