Difficulty: Intermediate
Estimated Time: 10 minutes

Rook Rook is an open source cloud-native storage orchestrator, providing the platform, framework, and support for a diverse set of storage solutions to natively integrate with cloud-native environments.

Rook turns storage software into self-managing, self-scaling, and self-healing storage services. It does this by automating deployment, bootstrapping, configuration, provisioning, scaling, upgrading, migration, disaster recovery, monitoring, and resource management. Rook uses the facilities provided by the underlying cloud-native container management, scheduling and orchestration platform to perform its duties.

Rook integrates deeply into cloud native environments leveraging extension points and providing a seamless experience for scheduling, lifecycle management, resource management, security, monitoring, and user experience.

For more details about the status of storage solutions currently supported by Rook, please refer to the project status section of the Rook repository. We plan to continue adding support for other storage systems and environments based on community demand and engagement in future releases.

Getting Started

Starting Rook in your cluster is as simple as two kubectl commands. See our Quickstart guide for the details on what you need to get going.

Once you have a Rook cluster running, walk through the guides for block, object, and file to start consuming the storage in your cluster:

  • Block: Create block storage to be consumed by a pod
  • Object: Create an object store that is accessible inside or outside the Kubernetes cluster
  • Shared File System: Create a file system to be shared across multiple pods

Architecture

With Rook running in the Kubernetes cluster, Kubernetes applications can mount block devices and filesystems managed by Rook, or can use the S3/Swift API for object storage. The Rook operator automates configuration of storage components and monitors the cluster to ensure the storage remains available and healthy.

The Rook operator is a simple container that has all that is needed to bootstrap and monitor the storage cluster. The operator will start and monitor ceph monitor pods and a daemonset for the OSDs, which provides basic RADOS storage. The operator manages CRDs for pools, object stores (S3/Swift), and file systems by initializing the pods and other artifacts necessary to run the services.

The operator will monitor the storage daemons to ensure the cluster is healthy. Ceph mons will be started or failed over when necessary, and other adjustments are made as the cluster grows or shrinks. The operator will also watch for desired state changes requested by the api service and apply the changes.

The Rook operator also creates the Rook agents. These agents are pods deployed on every Kubernetes node. Each agent configures a Flexvolume plugin that integrates with Kubernetes’ volume controller framework. All storage operations required on the node are handled such as attaching network storage devices, mounting volumes, and formating the filesystem.

alt text

Thank you for trying the playground. To view all our scenarios, go here

To learn more about Portworx, below are some useful references.

Don’t stop now! The next scenario will only take about 10 minutes to complete.

Cassandra Stateful Set on Kubernetes with Rook

Step 1 of 8

Ceph Storage Quickstart

First we need to wait for Kubernetes and Rook to be ready. Be patient, this is not a very high performance environment, just a place to learn something :-

Step: Wait for Kubernetes to be ready

Click the below section which waits for all Kubernetes nodes to be ready.

watch kubectl get nodes

When all nodes (master, node01) show status Running then hit clear to ctrl-c and clear the screen.

verify the rook-ceph-operator, rook-ceph-agent, and rook-discover pods are in the Running state before proceeding

watch kubectl -n rook-ceph-system get pod

When all pods show status Running then hit clear to ctrl-c and clear the screen.

Use kubectl to list pods in the rook-ceph namespace. You should be able to see the following pods rook-ceph-mgr, rook-ceph-mon, rook-ceph-osd* once they are all running. The number of osd pods will depend on the number of nodes in the cluster and the number of devices and directories configured.

watch kubectl -n rook-ceph get pod

When all pods show status Running then hit clear to ctrl-c and clear the screen.

Now that we have the Rook cluster up, let's proceed to the next step !