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 | |
Charles Butler (community) | Approve | ||
Adam Israel (community) | Approve | ||
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.
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!