[Bug 1500635] Re: Allow os-{type}-hostname to also override protocol

[Peter Sabaini]

** Tags added: canonical-bootstack

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to cinder in Juju Charms Collection.
Matching subscriptions: charm-bugs
https://bugs.launchpad.net/bugs/1500635

Title:
  Allow os-{type}-hostname to also override protocol

Status in Charm Helpers:
  In Progress
Status in ceilometer package in Juju Charms Collection:
  In Progress
Status in ceph-radosgw package in Juju Charms Collection:
  In Progress
Status in cinder package in Juju Charms Collection:
  In Progress
Status in glance package in Juju Charms Collection:
  In Progress
Status in heat package in Juju Charms Collection:
  In Progress
Status in keystone package in Juju Charms Collection:
  In Progress
Status in neutron-api package in Juju Charms Collection:
  In Progress
Status in nova-cloud-controller package in Juju Charms Collection:
  In Progress
Status in swift-proxy package in Juju Charms Collection:
  In Progress

Bug description:
  When deploying a proxy for OpenStack services the proxy itself may
  provide the SSL transport rather than the OpenStack services
  themselves. In such a deployment, SSL is not configured nor managed by
  the OpenStack service components (keystone, cinder, nova-compute, etc)
  and instead the proxy is handling the SSL traffic.

  Rather than introduce yet another config option, a simple change to
  the way the os-{endpoint_type}-hostname options is treated will allow
  the user to also specify that the endpoints should be advertised as
  SSL and that an external proxy will manage the SSL configuration for
  them.

  As such, this change would allow the user to specify the following
  options:

  1. Override the hostname advertised, let the charms themselves manage
  the SSL

      juju set <service> os-public-hostname='foobar.example.org'

  2. Override the hostname advertised and the URL scheme.

      juju set <service> os-public-hostname='https://foobar.example.org'

  In the second configuration option, the public endpoints for the
  service will be advertised using https for the scheme/protocol and
  foobar.example.org for the address. The path portion of the endpoint
  URL will continue to be provided by the specific charm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-helpers/+bug/1500635/+subscriptions