optimize SSL terminated apache configuration
Bug #1684546 reported by
James Page
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Keystone Charm |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
When SSL termination is enabled, the charm configures separate vhosts for SSL and the actual openstack WSGI backend application, proxying between the two vhosts.
This creates a larger burden on the server and apache in terms of open sockets and worker processes; lets optimize the apache configuration to bake the SSL termination directly into the backend WSGI application vhosts, rather than having separate SSL vhosts + mod_proxy back to the WSGI vhost.
| tags: | added: sts |
| Changed in charm-keystone: | |
| milestone: | none → 17.08 |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: 4010 cpec |
| Changed in charm-keystone: | |
| milestone: | 17.08 → 17.11 |
| tags: |
added: cpe-onsite removed: cpec |
| Changed in charm-keystone: | |
| milestone: | 17.11 → 18.02 |
| Changed in charm-keystone: | |
| milestone: | 18.02 → 18.05 |
| Changed in charm-keystone: | |
| milestone: | 18.05 → 18.08 |
| Changed in charm-keystone: | |
| milestone: | 18.08 → 18.11 |
| Changed in charm-keystone: | |
| milestone: | 18.11 → 19.04 |
| Changed in charm-keystone: | |
| milestone: | 19.04 → 19.07 |
| Changed in charm-keystone: | |
| milestone: | 19.07 → 19.10 |
| Changed in charm-keystone: | |
| milestone: | 19.10 → 20.01 |
| Changed in charm-keystone: | |
| milestone: | 20.01 → 20.05 |
| Changed in charm-keystone: | |
| milestone: | 20.05 → 20.08 |
| Changed in charm-keystone: | |
| milestone: | 20.08 → none |
To post a comment you must log in.
