8409e006c5
Since all authentication plugins should be stored in Keystone, there is no
need to share responsibility for authentication stuff with Keystone team.
Let's use convinient and the right way to use keystone - keystone sessions.
We have own adapter for it - novaclient.client.Session which can be used in
100% cases of novaclient usage. Let's create session object if it is not
transmitted via arguments and get rid of novaclient.client.HTTPClient
implementation.
NOTE: novaclient.client.HTTPClient and all related code will be removed
separately.
Co-Authored-By: Clenimar Filemon <clenimar@lsd.ufcg.edu.br>
Change-Id: Ibb99fdafbf02b3e92f1a5d04d168151b3400b901
11 lines
481 B
YAML
11 lines
481 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
When using novaclient as a library (via novaclient.client.Client
|
|
entry-point), an internal implementation of HTTPClient was used if a
|
|
session object is not specified. For better user experience we switched
|
|
to using SessionClient which uses keystoneauth (Keystone folks maintain
|
|
this library) for all auth stuff.
|
|
The SessionClient interface is similar to HTTPClient, but there is a
|
|
small possibility that you will notice a difference.
|