Bug 1042167 - [RFE][heat]: Ability to specify SSL parameters for python-clients used
Summary: [RFE][heat]: Ability to specify SSL parameters for python-clients used
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ga
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/heat...
Whiteboard: upstream_milestone_icehouse-1 upstrea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:15 UTC by RHOS Integration
Modified: 2014-09-08 05:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
The Orchestration service now allows you to configure the SSL settings of each client independently. This will allow you greater flexibility in addressing security requirements unique to each client.
Clone Of:
Environment:
Last Closed: 2014-07-22 19:08:59 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 21:15:41 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/clients-ssl-options.

Description:

Heat uses client libraries for of OpenStack services. Those services may be configured to use HTTPS instead of HTTP. So to access them you need to pass SSL-related parameters to client constructor. Currently this is not possible with Heat.  The level of SSL support varies from client to client but there is a common set of options that can be possibly be for any given service. I want to have solution that would allow configure each client independently. I also want to have ability to define a shared configuration for all clients so that I wouldn't have to repeat all the settings for each client. Shared config section would act as a fallback if client-specific config section is not found (or setting is missing)

Specification URL (additional information):

None

Comment 2 Stephen Gordon 2014-01-23 20:48:03 UTC
Moving to POST based on upstream status (Implemented).


Note You need to log in before you can comment on or make changes to this bug.