Skip to content

Conversation

enjenjenje
Copy link
Contributor

No description provided.

@enjenjenje enjenjenje requested a review from nahsi February 13, 2025 12:41
@enjenjenje enjenjenje requested a review from gurinderu February 13, 2025 12:56
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: spectrum-pool
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nahsi @gurinderu need to decide with the Storage Pool name here.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm, need to think about it.

Do we need storage pool for nvme, ssd and hdd disks separately?

If not I would just call it mayastore or something in case we will add some different storage tech after.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to these docs - we can create multiple pools that look to different disks.

We need to come up with standard names for every storage type (e.g. nvme-pool, ssd-pool, hdd-pool)

- ../../core/local-path-provisioner
- ../../core/metrics-server
- ../../core/kubelet-serving-cert-approver
- ../../core/openebs
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably a good idea to add a disk to ephemeral DO instance, install mayastore there and add that disk to mayastore.
Can be done in a separate PR I think.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants