charms.openstack

support for rendering and enabling website for hosting WSGI API service

Bug #1796926 reported by Frode Nordahl on 2018-10-09

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://github.com/openstack/charm-gnocchi/blob/d702f8458c1b653b788130b39c824aeafe78bc2d/src/lib/charm/openstack/gnocchi.py#L244

https://github.com/openstack-charmers/charm-octavia/blob/975e80d99f810c1230cc23e8c2ce2afb3c3736b7/src/lib/charm/openstack/octavia.py#L87

Revision history for this message

Frode Nordahl (fnordahl) wrote on 2018-10-10:

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 WSGIWorkerConfigContext 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.

James Page (james-page) on 2018-10-18

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

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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