After merged the patch I08c8b753972c27b4e6bbe07a8aa51e0e72fbc56d,
blazarclient can't be used with blazar_url and auth_token since this
patch only allows sessions for the initiation of client.
For backward compatibility, blazarclient should be initiated with
blazar_url and auth_token as before.
This patch enables using blazarclient with a set of blazar_url and
auth_token or session by reviving BaseClientManager class with adding
a logic to chose an auth method based on given params.
For authentication, the community recommends the use of keystoneauth1
instead of python-keystoneclient. Therefore, Blazar should follow
this trend and migrate to keystoneauth1.
This patch enables blazarclient to use keystoneauth1 for authentications
and REST API requests and also enables use of project_id, project_name,
project_domain_id, project_domain_name, user_domain_id and user_domain_name
This patch adds a before_end_date option to the lease-create command. It
also adds a before_end parameter to the physical_reservation option.
Partially Implements: blueprint on-end-options
lease-update CLI only accepts time delta to update start_time
or end_time of leases. It's hard for users to specify a specific
date as its argument since users need to caluclate the time delta
between the previous start/end time and the new date.
This patch enables users to update leases with date format
like --end-date "2017-06-05 17:15".
The python-blazarclient repository has been using the climateclient
This patch converts the climateclient namespace to the blazarclient
namespace. Additionally, some classes, methods and variables that
include 'climate' in their name are also changed to 'blazar'.