OpenStack Cyborg

openstack Coordination serviceopenstack-cyborg

Accelerator management framework that discovers FPGAs, GPUs, NICs, SSDs and AI chips, reports them to Placement and attaches them to instances.

Provider: openstack
Kind: Coordination service
Category: Operations
Official docs: https://docs.openstack.org/cyborg/latest/
Also known as: Accelerator Life Cycle Management

Properties · 2 set by this component

property	type	values	required	kind default	this component
acceleratorType · component property	enum	fpga \| gpu \| nic \| ssd \| ai-chip	no	—	inherited
consensus	enum	none \| raft \| paxos \| zab	no	none	inherited
deviceProfile · component property	boolean	—	no	true	inherited
managed	boolean	—	no	false	▸ false
nodes	integer	—	no	—	inherited
placementInventory · component property	boolean	—	no	true	inherited
replicated	boolean	—	no	false	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: "cyborg", component: "openstack-cyborg" }

Other Coordination service products · 17

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# OpenStack Cyborg: general management framework for accelerators. Per "OpenStack Accelerator (Cyborg)" the
3# cyborg-agent discovers local FPGAs, GPUs, NICs, SSDs and AI chips via drivers, reports inventory to the
4# conductor for Placement, and manages device programming and attachment to Nova instances through device
5# profiles: a placement role over the cloud, with no consensus protocol of its own.
6schemaVersion: "1"
7type: "component"
8id: "openstack-cyborg"
9kind: "coordination-service"
10provider: "openstack"
11docs: "https://docs.openstack.org/cyborg/latest/"
12aliases: ["Accelerator Life Cycle Management"]
13defaults:
14  role: "placement"
15  managed: false
16properties:
17  acceleratorType:
18    type: "enum"
19    values: ["fpga", "gpu", "nic", "ssd", "ai-chip"]
20  placementInventory:
21    type: "boolean"
22    default: true
23  deviceProfile:
24    type: "boolean"
25    default: true

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