Juju Charms Collection
postgresql package

combine pgbouncer charm as additional "role" for postgresql charm

Bug #1060110 reported by Mark Mims
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
postgresql (Juju Charms Collection)
Expired
Undecided
Unassigned

Bug Description

kinda like master-slave, but just make it a pgbouncer interface

Revision history for this message
Mark Mims (mark-mims) wrote :

The goal while it's still fresh in my head:

    juju deploy postgresql database-head
    juju deploy postgresql database-backend -n3
    juju add-relation database-head:pgbouncer database-backend:db-admin

    juju deploy --config=myapp.yaml django myapp
    juju add-relation myapp database-head:db

sanity check please

Revision history for this message
Stuart Bishop (stub) wrote :

I'm thinking it should be separate. Consider 'juju deploy -n 3 postgresql database-head'. You might now have three pgbouncers available for fault tolerance, but you also have three PostgreSQL databases running and replicated due to the peer relationship in the PostgreSQL charm.

Changed in postgresql (Juju Charms Collection):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for postgresql (Juju Charms Collection) because there has been no activity for 60 days.]

Changed in postgresql (Juju Charms Collection):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.