Jump to: navigation, search

Difference between revisions of "Blazar"

m (Service Architecture Design)
m (Operators: fixed a missing blank)
(47 intermediate revisions by 8 users not shown)
Line 1: Line 1:
== Climate ==
+
Blazar is a resource reservation service for OpenStack. Blazar enables users to reserve a specific type/amount of resources for a specific time period and it leases these resources to users based on their reservations.
  
Welcome to Climate, OpenStack reservation service.
+
The following two resource types are currently supported:
At the moment all docs are placed here, they’ll be moved to readthedocs.org soon.
 
  
* [[https://github.com/stackforge/climate Source code]]
+
* Compute host: reserve and lease with a unit of a whole host
* [[https://bugs.launchpad.net/climate Bug tracker]]
+
* Instance: reserve and lease with a unit of a flavor
* [[https://blueprints.launchpad.net/climate Blueprints]]
 
  
 +
Please see the following resources to learn more.
  
==== Old Wiki resources: ====
+
=== API ===
* [[Resource-reservation-service|https://wiki.openstack.org/wiki/Resource-reservation-service]]
 
* [[Blueprint-nova-planned-resource-reservation-api|https://wiki.openstack.org/wiki/Blueprint-nova-planned-resource-reservation-api]]
 
  
== Introduction ==
+
See [https://docs.openstack.org/blazar/latest/restapi/api-v1.html Blazar API reference].
  
Idea of creating Climate originated with two different use cases:
+
=== Operators ===
* Compute host reservation (when user with admin privileges can reserve hardware resources that are dedicated to the sole use of a tenant)
 
* Virtual machine (instance) reservation (when user may ask reservation service to provide him working VM not necessary now, but also in the future)
 
  
 +
To learn how to deploy and configure Blazar, see [https://docs.openstack.org/blazar/latest/install/index.html the installation guide].
  
Now these ideas have been transformed to more general view: with Climate user can request the resources of cloud environment to be provided (“leased”) to his project for specific amount on time, immediately or in future.
+
=== Developers ===
  
Both virtual (Instances, Volumes, Networks) and hardware (full hosts with specific characteristics of RAM, CPU and etc) resources can be allocated via “lease”.
+
To learn how to deploy and configure Blazar, see [https://docs.openstack.org/blazar/latest/install/index.html the installation guide].
  
In terms of benefits added, Resource Reservation Service will:
+
=== Other Resources ===
* improve visibility of cloud resources consumption (current and planned for future);
 
* enable cloud resource planning based on current and future demand from end users;
 
* automate the processes of resource allocation and reclaiming;
 
* provide energy efficiency for physical hosts (both compute and storage ones);
 
* potentially provide leases as billable items for which customers can be charged a flat fee or a premium price depending on amount of reserved cloud resources and their usage
 
  
=== Glossary of terms ===
+
{| border="1" cellpaddings="2"
 
+
| Documents
'''Reservation''' is an allocation of certain cloud resource (Nova instance, Cinder volume, compute host, etc.) to particular project. Speaking about virtual reservations, we may have not only simple, solid ones (like already mentioned instances and volumes), but also complex ones - like Heat stacks and Savanna clusters. Reservation is characterized by ''status'', ''resource type'' and ''identifier'' and lease it belongs to.
+
| https://docs.openstack.org/blazar/latest/
 
+
|-
'''Lease''' is a negotiation agreement between the provider (Climate, using OpenStack resources) and the consumer (user) where the former agrees to make some kind of resources (both virtual and physical) available to latter, based on a set of lease terms presented by the consumer. Here lease may be described as contract between user and reservation service about cloud resources to be provided right now or later. Technically speaking, lease is a group of reservations granted to particular project upon request. Lease is characterized by ''start time'', ''end time'', set of individual ''reservations'' and associated ''events''.
+
| Release notes
 
+
| https://releases.openstack.org/teams/blazar.html
'''Event''' is simply something that may happen to lease. In most simple case event might describe lease start and lease end. Also it might be notification to user (e.g. about soon lease expiration) and some extra actions.
+
|-
 
+
| Source code
== Rationale ==
+
| https://git.openstack.org/cgit/openstack/blazar
 
+
|-
Climate is created to:
+
| Nova filters and extensions
* manage cloud resources not only right now, but also in the future;
+
| https://git.openstack.org/cgit/openstack/blazar-nova
* have dedicated recourses on certain amount of time;
+
|-
* prepare for the peak loads and perform capacity planning;
+
| Blazar client
* optimise energy consumption.
+
| https://git.openstack.org/cgit/openstack/python-blazarclient
 
+
|-
== Service Architecture Design ==
+
| Blazar dashboard
 
+
| https://git.openstack.org/cgit/openstack/blazar-dashboard
 
+
|-
[[File:Climate_architecture.png]]
+
| Bug tracker
 
+
| https://bugs.launchpad.net/blazar
 
+
|-
'''climate-client''' - provides the opportunity to communicate with Climate via REST API (climate-api service).
+
| Feature tracker
 
+
| https://blueprints.launchpad.net/blazar
'''climate-api''' - waits for the REST calls from the outside world to redirect them to the manager. climate-api communicates with climate-manager via RPC. Runs as a separated process.
+
|-
 
+
| Reviews
'''climate-manager''' - implements all logic and operations with leases, reservations and events. Communicates with Climate DB and stores there data structure of connected leases, reservations (both physical and virtual) and events. climate-manager service is responsible for running events created for lease and process all actions that should be done this moment. Manager uses resource-plugins to work with concrete resources (instances, volumes, compute hosts).  climate-manager uses Keystone trusts to commit actions on behalf of user who has created lease before.
+
| https://review.openstack.org/#/q/blazar
 
+
|}
'''resource-plugin''' - responsible for exact actions to do with reserved resources (VMs, volumes, etc.) When working knows only about resource ID and token to use. All resource plugins work in the same process as climate-manager.
 
 
 
=== Virtual instance reservation ===
 
 
 
Virtual instance reservation mostly looks like usual instance booting for user - he/she only passes special hints to Nova containing information about future lease - lease start and end dates, its name, etc. Special Nova API extensions parse these parameter and use them to call Climate, passing to it ID of just created instance. If there is a need to reserve all instances in cloud (like in developer labs to automate process of resource reclaiming), default reservation extension might be used. By default it starts lease at the moment of request and gives it one month of lifetime.
 
 
 
During the time lease has not started yet, instance will be in shelved.
 
 
 
=== Compute host reservation ===
 
 
 
Now process of compute hosts reserving contains two steps:
 
 
 
* admin marks hosts from common pool as possible to be reserved. That is implemented by moving these hosts to special aggregate.
 
* user asks for reserving of host with specified characteristics like:
 
** the region
 
** the availability zone
 
** the host capabilities extra specs (scoped and non-scoped format should be accepted)
 
** the number of CPU cores
 
** the amount of free RAM
 
** the amount of free disk space
 
** the number of hosts
 
 
 
 
 
Technically speaking, resource ID here will be not host ID, because there might be many of them wanted, resource itself here will be new aggregate containing reserved hosts. The time lease starts, user may use reserved compute capacity to run his/her instances on it passing special scheduler hint to Nova. When host is reserved, it’s not used for usual instance running, it might be used only when lease starts and only by passing reservation ID to Nova.
 
 
 
== Lease types ==
 
 
 
TBD
 
 
 
== REST API ==
 
 
 
TBD
 

Revision as of 09:02, 13 February 2018

Blazar is a resource reservation service for OpenStack. Blazar enables users to reserve a specific type/amount of resources for a specific time period and it leases these resources to users based on their reservations.

The following two resource types are currently supported:

  • Compute host: reserve and lease with a unit of a whole host
  • Instance: reserve and lease with a unit of a flavor

Please see the following resources to learn more.

API

See Blazar API reference.

Operators

To learn how to deploy and configure Blazar, see the installation guide.

Developers

To learn how to deploy and configure Blazar, see the installation guide.

Other Resources

Documents https://docs.openstack.org/blazar/latest/
Release notes https://releases.openstack.org/teams/blazar.html
Source code https://git.openstack.org/cgit/openstack/blazar
Nova filters and extensions https://git.openstack.org/cgit/openstack/blazar-nova
Blazar client https://git.openstack.org/cgit/openstack/python-blazarclient
Blazar dashboard https://git.openstack.org/cgit/openstack/blazar-dashboard
Bug tracker https://bugs.launchpad.net/blazar
Feature tracker https://blueprints.launchpad.net/blazar
Reviews https://review.openstack.org/#/q/blazar