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 16d5f67ba7020701edbbf09a747f5683b0840c21
started using a dedicated account configured with values
climate_username, climate_password, and climate_tenant_name. Commit
c9b7307cf3c97d3b48878aca6eda5b7fbc4dcfa7 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
16d5f67ba7020701edbbf09a747f5683b0840c21, 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
Blazar uses os_auth_host, os_auth_port and os_auth_version to the auth
uri for now. However, current approach can not be applied to uri with some
prefixes such like "http://127.0.0.1/identity".
In this patch, authentification is executed by using "keystone_authtoken"
configs. This patch enables us to use any forms of auth uri.
Closes-Bug: #1681419
Change-Id: I7c8728593ecf503b23d742a5f464af8a2a6e5253
Link for bug-tracker in "Virtual instance reservation" section is
displayed improperly.
Correct it by adding new line before it.
Change-Id: Idda9f655ec58cefac3953e6b1f42846e97223647
Blazar does not terminate runnning instances at the end of a lease for
now. That can cause a failure of the other lease. This patch change the
on_end action to force-delete all running instances.
This change is the step1 of the on-end-options Blueprint.
Change-Id: Iaaed5de710ecdb8131cb9323dc41b78d2a43743b
Implements: blueprint on-end-options
The Blazar project doesn't have a separate specs repository. If Blazar
users want to know details of new features, they need to follow IRC
discussions or track Git commits.
This patch creates a directory to keep specifications publicly visible.
Change-Id: I34918fe34d331d690b18b27a7d470f093d211cf7
Closes-Bug: #1670956
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
This patch updates overview documents. It also adds settings required
for publishing documents under doc directory on the readthedocs.io.
Change-Id: I89fd24cc538d09cdcfbe9a1cfb9986a4bf724266
Closes-Bug: #1662739
This patch adds necessary spaces into tables of the v1 API document to
resolve malformed table errors.
Change-Id: I3235a21ec595f2198fc94c619fdb1490c3489abc
Partial-Bug: #1662741
Add simple script to setup mysql and postgresql databases, this script
can be run by users during testing and will be run by CI systems for
specific setup before running unit tests.
This allows to change in project-config the python-db jobs to
python-jobs since python-jobs will call this script initially.
Update devref for this.
See also
http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html
Change-Id: I845c04b32c6b2bba055829cb2100f5beba94de4d
Needed-By: I4f2ce44f9e28c94d6562d5c520c00c35207f7123
The Blazar code base is not yet compatible with Python 3. Having tox
environments for them is a first step towards fixing it.
Change-Id: I04441e4881eb7fe9b4c12d65392796c1020b41df
There's no RST file that uses ".. math" and thus
the pngmath Sphinx extension is not used and can
get removed.
Change-Id: I3ea4b529025c8ac3c4092f3720124647861e6668
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
With the rename of Climate to Blazar the devstack instructions were no
longer valid. I've updated the references to changed files and service
names where appropriate to make these instructions work again.
Change-Id: I52ce96eb6cc09998d671fb3554ec386807421d44
Controllers (and API endpoints) should be able to be selected using
configuration flags, as we do for plugins
TODO:
- Extra Hooks to be configured using stevedore
Implements blueprint: pecan-wsme
Implements blueprint: api-extensions
Change-Id: I12f1bc1accbc870aacb0d1e08c9e0d08223c4b18
Refernces from tenant to project were made in several
places, including DB, HTTP Headers, configuration items,
json in responses and devstack integration. Additionally,
a migration script using Alembic was included.
Implements: blueprint tenant-to-project-ref
Change-Id: I4b21182f555ccd412a4ca4e0ce753f07edcd07f8
Routing either V1 or V2 using a Facade. By default, V1 is enabled
but can be deactivated by a confflag.
Pecan controller for Lease created using WSME i/o validation
Implements blueprint: pecan-wsme
Change-Id: I9047abece78632daa13fdebfea9fb8aaa3c60981
* add common introduction and architecture information
* create more appropriate structure for REST API docs
Change-Id: I27b95aa76814f5d6bf6737c56594c7e5ba9d667c
Partially implements: blueprint climate-docs
We explore, that sys.path magic in docs/conf.py is unecessary now. Also,
removing this strings provides compatibility with future Sphinx
releases.
Change-Id: I7028297f89b2ec0a1ab7007ad2594eec2c9000c0
closes-bug: #1285036
