Calamari/api/hardware/storage¶

Summary
In a large distributed system things are always happening. We care more about the causes and the implications of these events than the constant stream of them.
This is a design to help connect the events happening to hardware and the Ceph constructs they affect.

Owners
Gregory Meno(Red Hat) Pacific
Joe Handzik(HP) Central

Interested Parties
If you are interested in contributing to this blueprint, or want to be a "speaker" during the Summit session, list your name here.
Name (Affiliation)
Name (Affiliation)
Name

Current Status
planning and implementation

Detailed Description
OSD.128 is down? That's in host foo_bar_5.... but what drive is that? Is the failure software or hardware? What do I replace it with? How long has it been failing?
These questions probably sound familiar if you are an operator of a Ceph cluster. We want to improve the facility to answer these questions by implementing a new storage hardware API.
OSDs have storage hardware
Storage hardware has events
Events can inform proper corrective action.

Storage hardware has attributes that help us decide what hardware to ship to the data-center in case of replacement. These same attributes can help us identify offline hardware.

Work items
This section should contain a list of work tasks created by this blueprint. Please include engineering tasks as well as related build/release and documentation work. If this blueprint requires cleanup of deprecated features, please list those tasks as well.

• https://github.com/ceph/ceph/pull/4699
• pull OSD hardware info in to calamari
• write checks for the storage hardware
• Task 3

Build / release tasks
Task 1
Task 2
Task 3

Documentation tasks
Task 1
Task 2
Task 3

Deprecation tasks
Task 1
Task 2
Task 3