This section covers the core concepts of the cephlet project.
The cephlet is an implementor of the onmetal runtime interface (ORI) for Volumes and Buckets.
+It consists of the cephlet-volume and cephlet-bucket in order to implement the VolumeRuntime respectively the BucketRuntime.
A cephlet is usually deployed along with a poollet.
+A poollet resolves dependencies, e.g. an encryption secret, and calls with the consolidated resource the cephlet.
+The cephlet persists the required state and reconciles the resource in an asynchronous manner.
The cephlet-volume interacts directly with a defined ceph cluster.
+A Volume is provisioned by creating a ceph image. If needed, an image is created with a pre-defined os image.
The following diagram visualizes the interplay of the different components: +
graph TD
+ C([cephlet-volume])
+ P([volumepoollet])
+
+ P -- announces --> VP[VolumePool]
+ P -- watches --> V[Volumes]
+
+ P -- uses ORI --> C
+
+ C -- creates --> I[Ceph Image]
+ C -- defines --> VC[Supported VolumeClasses]The cephlet-bucket utilizes rook CRD's to back the onmetal Bucket resource.
+Rook ensures that a ObjectBucketClaim (and an access secret) is being reconciled.
The following diagram visualizes the interplay of the different components: +
graph TD
+ C([cephlet-bucket])
+ P([bucketpoollet])
+ R([rook])
+
+ P -- announces --> BP[BucketPool]
+ P -- watches --> B[Buckets]
+
+ P -- uses ORI --> C
+
+ C -- defines --> VC[Supported BucketClasses]
+ C -- creates --> OBC[ObjectBucketClaim]
+ R -- reconciles --> OBC