| 2019-08-21 09:44:38 |
Frode Nordahl |
bug |
|
|
added bug |
| 2019-08-21 09:45:21 |
Frode Nordahl |
description |
The TLS configuration helpers are a property of the ``OpenStackCharm`` class which is appropriate and make them available to non-API OpenStack services such as ``ceilometer`` as well as not strictly speaking OpenStack services such as ``rabbitmq``.
However, they were originally in the ``OpenStackAPICharm`` class and later moved [0], and unfortunately the helpers carried over assumptions about placement of certificate files.
I think the move was appropriate but the helpers could have been adapted to their new home by providing configurability of certificate placement in the ``OpenStackCharm`` helper and then overriding that to the present defaults in the inherited helper in ``OpenStackAPICharm``. |
The TLS configuration helpers are a property of the ``OpenStackCharm`` class which is appropriate and make them available to non-API OpenStack services such as ``ceilometer`` as well as not strictly speaking OpenStack services such as ``rabbitmq``.
However, they were originally in the ``OpenStackAPICharm`` class and later moved [0], and unfortunately the helpers carried over assumptions about placement of certificate files.
I think the move was appropriate but the helpers could have been adapted to their new home by providing configurability of certificate placement in the ``OpenStackCharm`` helper and then overriding that to the present defaults in the inherited helper in ``OpenStackAPICharm``.
0: https://review.opendev.org/#/c/623295/ |
|
| 2019-08-21 09:46:08 |
Frode Nordahl |
description |
The TLS configuration helpers are a property of the ``OpenStackCharm`` class which is appropriate and make them available to non-API OpenStack services such as ``ceilometer`` as well as not strictly speaking OpenStack services such as ``rabbitmq``.
However, they were originally in the ``OpenStackAPICharm`` class and later moved [0], and unfortunately the helpers carried over assumptions about placement of certificate files.
I think the move was appropriate but the helpers could have been adapted to their new home by providing configurability of certificate placement in the ``OpenStackCharm`` helper and then overriding that to the present defaults in the inherited helper in ``OpenStackAPICharm``.
0: https://review.opendev.org/#/c/623295/ |
The TLS configuration helpers are a property of the ``OpenStackCharm`` class which is appropriate and make them available to non-API OpenStack services such as ``ceilometer`` and ``neutron-dynamic-routing`` as well as not strictly speaking OpenStack services such as ``rabbitmq`` and others.
However, they were originally in the ``OpenStackAPICharm`` class and later moved [0], and unfortunately the helpers carried over assumptions about placement of certificate files.
I think the move was appropriate but the helpers could have been adapted to their new home by providing configurability of certificate placement in the ``OpenStackCharm`` helper and then overriding that to the present defaults in the inherited helper in ``OpenStackAPICharm``.
0: https://review.opendev.org/#/c/623295/ |
|
| 2019-08-23 10:23:54 |
Frode Nordahl |
description |
The TLS configuration helpers are a property of the ``OpenStackCharm`` class which is appropriate and make them available to non-API OpenStack services such as ``ceilometer`` and ``neutron-dynamic-routing`` as well as not strictly speaking OpenStack services such as ``rabbitmq`` and others.
However, they were originally in the ``OpenStackAPICharm`` class and later moved [0], and unfortunately the helpers carried over assumptions about placement of certificate files.
I think the move was appropriate but the helpers could have been adapted to their new home by providing configurability of certificate placement in the ``OpenStackCharm`` helper and then overriding that to the present defaults in the inherited helper in ``OpenStackAPICharm``.
0: https://review.opendev.org/#/c/623295/ |
The TLS configuration helpers are a property of the ``OpenStackCharm`` class which is appropriate and make them available to non-API OpenStack services such as ``ceilometer`` and ``neutron-dynamic-routing`` as well as not strictly speaking OpenStack services such as ``rabbitmq`` and others.
However, they were originally in the ``HAOpenStackCharm`` class and later moved [0], and unfortunately the helpers carried over assumptions about placement of certificate files.
I think the move was appropriate but the helpers could have been adapted to their new home by providing configurability of certificate placement in the ``OpenStackCharm`` helper and then overriding that to the present defaults in the inherited helper in ``HAOpenStackCharm``.
0: https://review.opendev.org/#/c/623295/ |
|
| 2019-08-26 06:08:57 |
Frode Nordahl |
bug task added |
|
layer-openstack-api |
|
| 2019-08-26 06:09:20 |
Frode Nordahl |
bug task added |
|
layer-openstack |
|
| 2019-09-03 07:54:21 |
OpenStack Infra |
charms.openstack: status |
New |
Fix Released |
|
| 2019-10-30 15:28:37 |
Alex Kavanagh |
layer-openstack: status |
New |
Triaged |
|
| 2019-10-30 15:28:40 |
Alex Kavanagh |
layer-openstack: importance |
Undecided |
Medium |
|
| 2019-10-30 15:28:42 |
Alex Kavanagh |
layer-openstack-api: status |
New |
Triaged |
|
| 2019-10-30 15:28:44 |
Alex Kavanagh |
layer-openstack-api: importance |
Undecided |
Medium |
|
