Merge lp://staging/~niedbalski/charms/trusty/rabbitmq-server/fix-1442443 into lp://staging/charms/trusty/rabbitmq-server
Proposed by
Jorge Niedbalski
Status: | Superseded | ||||
---|---|---|---|---|---|
Proposed branch: | lp://staging/~niedbalski/charms/trusty/rabbitmq-server/fix-1442443 | ||||
Merge into: | lp://staging/charms/trusty/rabbitmq-server | ||||
Diff against target: |
746 lines (+373/-168) 11 files modified
config.yaml (+7/-1) hooks/rabbit_utils.py (+37/-39) hooks/rabbitmq_context.py (+125/-0) hooks/rabbitmq_server_relations.py (+7/-113) hooks/ssl_utils.py (+55/-0) templates/rabbitmq.config (+25/-11) tests/00_setup.sh (+3/-0) tests/50_test_cluster_partition.py (+31/-0) unit_tests/test_rabbit_utils.py (+1/-1) unit_tests/test_rabbitmq_context.py (+79/-0) unit_tests/test_rabbitmq_server_relations.py (+3/-3) |
||||
To merge this branch: | bzr merge lp://staging/~niedbalski/charms/trusty/rabbitmq-server/fix-1442443 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Billy Olsen | Needs Fixing | ||
OpenStack Charmers | Pending | ||
Review via email: mp+255770@code.staging.launchpad.net |
This proposal has been superseded by a proposal from 2015-04-10.
Description of the change
- Added the cluster_
- Refactored the ssl handling code.
- Added a generic config loader
To post a comment you must log in.
Unmerged revisions
- 98. By Jorge Niedbalski
-
Addressed @beisner comments
- 97. By Jorge Niedbalski
-
Addressed @beisner comments
- 96. By Jorge Niedbalski
-
addressing comments
- 95. By Jorge Niedbalski
-
addressing @dosaboy comments
- 94. By Jorge Niedbalski
-
addressing @dosaboy comments
- 93. By Jorge Niedbalski
-
addressing @dosaboy comments
- 92. By Jorge Niedbalski
-
Rebase
- 91. By Jorge Niedbalski
-
Rebase commit
Jorge,
I think some of the refactor in here is a definite improvement and makes things cleaner, thanks! I've got a few inline comments included, but the biggest thing is that the rabbitmq-server charm now has a /next and /trunk branch to match the rest of the flow of the openstack charms (since this has recently come under ownership of the ~openstack-charmers team). Can you retarget for /next?
Also, I think the README file should be updated with some discussions regarding high availability.
I'll run through some tests on this but wanted to drop some feedback now.