Originally, Blazar was using its service user to manage objects for
physical host reservation, e.g. host aggregates, which by default
requires admin rights. Commit 16d5f67ba7
started using a dedicated account configured with values
climate_username, climate_password, and climate_tenant_name. Commit
c9b7307cf3 removed this dedicated account
and started using trusts instead, so that operations were performed on
behalf of the user creating the lease (with the trustee being the blazar
service user).
While this works well if users creating leases are admins, non-admin
users will get errors because the default Nova policy prevents them from
running required operations associated with aggregates and hypervisors.
Since it is not clear why a dedicated account for admin operations was
required, this patch brings back the approach used before commit
16d5f67ba7, which was to use the service
account for admin operations. This allows non-admin users to create
Blazar leases.
The nova client setup is updated to authenticate against Keystone v3.
Change-Id: Iad86bb549aec13edd662965d2f91b68c856ae06c
Closes-Bug: #1663204
Although the Climate project was renamed to Blazar in 2014, the code has
still been using the climate namespace.
This patch moves all code to the blazar directory and allows users and
operators to use the 'blazar' command namespace. The 'climate' namespace
remains O release to allow users of Blazar time to move their own
code to the blazar namespace, but will be removed in P release
development cycle.
Change-Id: Icbe6fab1051aae4ac819982a1fa4f323cb0bf2d0
Partial-Bug: #1662734
References to climate in the docs have been renamed to blazar reflect the new name and enable uploadig docs to readthedocs. Also updated the docs to reference the new architecture image.
Change-Id: I594849afb6268892a03cc716a1707dcde835fa52
Closes-Bug: 1324581
Add notes about Keystone v3 endpoint creation to README.rst. It's simple
instructions which can help everyone who wants to test Climate.
Change-Id: I469c28ec03994fffad14bfb77bb82257b0c406f2
Service user used by Climate should not create objects such as
host aggregates. Consequently, until we migrate the code by using
trusts, we need to use a dedicated user for operations
Change-Id: I35878e178dea7eb10a52ad2419e191d8d683b35c
Closes-bug: #1270765
liushuobj