Merge lp:~stub/charms/precise/postgresql/manual-replication into lp:charms/postgresql
| Status: | Merged |
|---|---|
| Merged at revision: | 111 |
| Proposed branch: | lp:~stub/charms/precise/postgresql/manual-replication |
| Merge into: | lp:charms/postgresql |
| Diff against target: |
204 lines (+89/-19) 3 files modified
config.yaml (+16/-1) hooks/hooks.py (+43/-13) test.py (+30/-5) |
| To merge this branch: | bzr merge lp:~stub/charms/precise/postgresql/manual-replication |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Review Queue (community) | automated testing | Needs Fixing on 2015-01-14 | |
| Charles Butler (community) | 2014-11-04 | Approve on 2015-01-13 | |
| Adam Israel | Approve on 2014-12-04 | ||
|
Review via email:
|
|||
Description of the Change
Allow replication to be handled manually, rather than Juju controlling it.
The main use of this is to allow replication to be setup between non-Juju PostgreSQL databases and charmed databases, such as the pending migration of the Launchpad database from its legacy servers to new MaaS and Juju controlled servers.
I also have a work in progress for cascading replication, where a PostgreSQL service can be configured to replicate to/from another PostgreSQL service. This too could be used to integrate non-Juju and charmed databases (or cross Juju environment), but it is a much more complex setup and lacks the flexibility of just allowing an experienced admin to dive in and handle it themselves.
- 108. By Stuart Bishop on 2014-12-04
-
Merge trunk
- 109. By Stuart Bishop on 2014-12-04
-
delint and typo
| Stuart Bishop (stub) wrote : | # |
Thanks. The lint leaked in from trunk. I've fixed it and corrected a minor spelling error in a comment.
| Adam Israel (aisrael) wrote : | # |
Thanks for the quick fix! I've tested and confirmed that the tests now pass cleanly. +1 from me.
| Charles Butler (lazypower) wrote : | # |
+1
Thanks for the merge and diligence on getting this landed Stub. I'm approving and merging this - I left a note on IRC, and re-posting here for clarity.
<lazyPower> Looking over your merge against precise postgres charm - does this warrant additional action against the trusty charm as well when accepted for precise? https:/
<lazyPower> or is this scoped strictly to precise
| Review Queue (review-queue) wrote : | # |
This items has failed automated testing! Results available here http://
| Review Queue (review-queue) wrote : | # |
This items has failed automated testing! Results available here http://

Hey Stuart,
I had the opportunity to review this MP. The changes here look to be solid. Nice work, once again.
There is one minor lint error preventing me from marking this as approved, though. Once that is fixed, the test passes cleanly.
hooks/hooks. py:1148: 9: E128 continuation line under-indented for visual indent
Thanks again for submitting this!