support for rendering and enabling website for hosting WSGI API service
Bug #1796926 reported by
Frode Nordahl
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack API Layer |
Triaged
|
Wishlist
|
Unassigned | ||
charms.openstack |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
I believe this is a common task for all OpenStack API charms.
Two examples of charm usage:
https:/
Changed in layer-openstack-api: | |
status: | New → Triaged |
Changed in charms.openstack: | |
status: | New → Triaged |
Changed in layer-openstack-api: | |
importance: | Undecided → Wishlist |
Changed in charms.openstack: | |
importance: | Undecided → Wishlist |
To post a comment you must log in.
I guess this bug belongs to charms.openstack, keeping both tasks until it is clear what needs to be done.
charms.openstack does already contain code for the WSGIWorkerConfi gContext which can be used in conjunction with the template from charmhelpers but it is not clear to me that there exists any code for actually enabling the vhost itself.