yahoo-eng-team team mailing list archive

[OpenStack Infra <1666936@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/436475
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a377fc5988e9a6057bd14617879a7cbcc3c8bb81
Submitter: Jenkins
Branch:    master

commit a377fc5988e9a6057bd14617879a7cbcc3c8bb81
Author: Gyorgy Szombathelyi <gyurco@xxxxxxxxxxx>
Date:   Tue Feb 21 15:04:13 2017 +0100

    Use the keystone session loader in the placement reporting
    
    Using load_session_from_conf_options has the advantage that it honors
    session settings like cafile and insecure, to make use of non-system TLS
    certificates (or disable certificate checks at all). Also client
    certificates and timeout values can be specified, too.
    
    Closes-Bug: #1666936
    Change-Id: I510a2683958fc8c3aaca9293b4280f325b9551fc


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1666936

Title:
  Placment API client doesn't honor insecure nor cafile parameters

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  In Progress

Bug description:
  The connection to the Placement API from Nova doesn't allow to specify
  an insecure nor a cafile parameter. This could be a problem if those
  are used in the Keystone or Neutron clients, for example, then it is
  expected to use them in the Placement client, too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1666936/+subscriptions