Database connections should be made as appserver specific aliases on production
Bug #353598 reported by
Stuart Bishop
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
Medium
|
Stuart Bishop | ||
Bug Description
The appservers should connect as unique database users so it is possible to identify an individual failing appserver. This is currently done with the main store. It is not done with the auth store, or the two SSO database users.
The aliases need to be created.
We need a way of maintaining these aliases - adding new ones when new appservers come online or creating all of them when a new replica is brought online.
The production launchpad-lazr.conf files need to be updated.
| Changed in launchpad-foundations: | |
| assignee: | nobody → stub |
| importance: | Undecided → Medium |
| milestone: | none → 2.2.4 |
| status: | New → Triaged |
| Changed in launchpad-foundations: | |
| milestone: | 2.2.4 → 2.2.5 |
| Changed in launchpad-foundations: | |
| milestone: | 2.2.5 → 2.2.6 |
| Changed in launchpad-foundations: | |
| milestone: | 2.2.6 → 2.2.7 |
| Changed in launchpad-foundations: | |
| milestone: | 2.2.7 → 3.0 |
| Changed in launchpad-foundations: | |
| milestone: | 3.0 → 3.1.11 |
| Changed in launchpad-foundations: | |
| milestone: | 3.1.11 → 3.1.13 |
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in launchpad-foundations: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
No point worrying about this as the sso service is being seperated entirely from Launchpad.