OpenStack Blazar

openstack Coordination serviceopenstack-blazar

Reservation service that leases virtual instances, physical hosts, floating IPs and flavor-based instances for a future time window.

Provider: openstack
Kind: Coordination service
Category: Operations
Official docs: https://docs.openstack.org/blazar/latest/
Also known as: Resource Reservation service

Properties · 2 set by this component

property	type	values	required	kind default	this component
consensus	enum	none \| raft \| paxos \| zab	no	none	inherited
leaseBased · component property	boolean	—	no	true	inherited
managed	boolean	—	no	false	▸ false
nodes	integer	—	no	—	inherited
replicated	boolean	—	no	false	inherited
reservationType · component property	enum	virtual-instance \| physical-host \| floating-ip \| flavor-instance	no	—	inherited
role	enum	metadata \| lock \| discovery \| placement \| sharding \| leader-election \| config	yes	—	▸ placement

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Shared dependency without redundancyerror

shared-dependency-without-redundancy

The design requires redundant discovery, but this DNS or coordination service, which everything depends on, runs on a single provider or a single replica. Its failure is the whole system's failure.

— all of these hold:
— the design requirement `availability.discoveryRedundant` is true
— any of these hold:
— the node's `redundantProviders` is false
— the node's `replicated` is false

Stateful engine pinned to a single zoneerror

stateful-engine-pinned-to-single-zone

A matching engine, coordination service or event store living in exactly one availability zone, with no failover and no replication, is lost with that zone. Everything that depends on it stops with it.

— all of these hold:
— the node sits inside exactly 1 availability-zone group
— any of these hold:
— the node's `failover` is "none"
— the node's `replicated` is false
— the node's `replication` is "none"

Use it in a design

nodes:
  - { id: "blazar", component: "openstack-blazar" }

Other Coordination service products · 17

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# OpenStack Blazar: resource reservation service. Per "Blazar, the OpenStack Reservation Service" users lease
3# cloud capacity in advance - virtual instance, physical host, floating IP and flavor-based instance
4# reservations - so Blazar decides where and when reserved resources are placed. It holds leases, not consensus
5# state, so no replication or quorum behaviour is claimed.
6schemaVersion: "1"
7type: "component"
8id: "openstack-blazar"
9kind: "coordination-service"
10provider: "openstack"
11docs: "https://docs.openstack.org/blazar/latest/"
12aliases: ["Resource Reservation service"]
13defaults:
14  role: "placement"
15  managed: false
16properties:
17  reservationType:
18    type: "enum"
19    values: ["virtual-instance", "physical-host", "floating-ip", "flavor-instance"]
20  leaseBased:
21    type: "boolean"
22    default: true

The same page as markdown, for an agent: /catalogue/components/openstack-blazar.md