ceph-csi | Ceph CSI plugins implement an interface | Storage library

by ceph Go Version: v3.8.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | ceph-csi Summary

ceph-csi is a Go library typically used in Storage applications. ceph-csi has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Ceph CSI plugins implement an interface between CSI enabled Container Orchestrator (CO) and Ceph cluster. It allows dynamically provisioning Ceph volumes and attaching them to workloads. Independent CSI plugins are provided to support RBD and CephFS backed volumes,.

Support

Quality

Security

License

Reuse

Support

ceph-csi has a medium active ecosystem.

It has 962 star(s) with 482 fork(s). There are 49 watchers for this library.

It had no major release in the last 12 months.

There are 97 open issues and 1035 have been closed. On average issues are closed in 80 days. There are 8 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of ceph-csi is v3.8.0

Quality

ceph-csi has 0 bugs and 0 code smells.

Security

ceph-csi has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

ceph-csi code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

ceph-csi is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

ceph-csi releases are available to install and integrate.

It has 29296 lines of code, 964 functions and 151 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of ceph-csi

Get all kandi verified functions for this library.

ceph-csi Key Features

No Key Features are available at this moment for ceph-csi.

ceph-csi Examples and Code Snippets

No Code Snippets are available at this moment for ceph-csi.

Community Discussions

Trending Discussions on ceph-csi

How to share a cephfs volume between pods in different k8s namespaces

Rookv1.2 does not add labels on CrushMap

QUESTION

How to share a cephfs volume between pods in different k8s namespaces

Asked 2021-Dec-21 at 05:51

I'm trying to share a cephfs volumes between namespaces within k8s cluster. I'm using ceph-csi with cephfs.

Followed https://github.com/ceph/ceph-csi/blob/devel/docs/static-pvc.md#cephfs-static-pvc to create static pv+pvc in both namespaces. Works if I don't launch both pods on same node.

If both pods on same node, Second pod get stuck with error:

...

ANSWER

Answered 2021-Dec-18 at 10:09

you might need to provide ReadWriteMany option Reference link: https://kubernetes.io/docs/concepts/storage/persistent-volumes/

Source https://stackoverflow.com/questions/70402269

QUESTION

Rookv1.2 does not add labels on CrushMap

Asked 2020-Feb-04 at 09:29

I'm currently working with Rook v1.2.2 to create a Ceph Cluster on my Kubernetes Cluster (v1.16.3) and I'm failing to add a rack level on my CrushMap.

I want to go from :

...

ANSWER

Answered 2020-Feb-04 at 09:29

I talked with a Rook Dev about this issue on this post : https://groups.google.com/forum/#!topic/rook-dev/NIO16OZFeGY

He was able to reproduce the problem :

Yohan, I’m also able to reproduce this problem of the labels not being picked up by the OSDs even though the labels are detected in the OSD prepare pod as you see. Could you open a GitHub issue for this? I’m investigating the fix.

But it appears that the issue was only concerning OSDs using directories and the problem does not exist when you use devices (like RAW devices) :

Yohan, I found that this only affects OSDs created on directories. I would recommend you test creating the OSDs on raw devices to get the CRUSH map populated correctly. In the v1.3 release it is also important to note that support for directories on OSDs is being removed. It will be expected that OSDs will be created on raw devices or partitions after that release. See this issue for more details: https://github.com/rook/rook/issues/4724

Since the support for OSDs on directories is being removed in the next release I don’t anticipate fixing this issue.

As you see, the issue will not be fixed because the use of directories will be soon deprecated.

I restarted my tests with the use of RAW devices instead of directories and it worked like a charm.

I want to thanks Travis for the help he provided and his quick answers !

Source https://stackoverflow.com/questions/59973027

Community Discussions, Code Snippets contain sources that include Stack Exchange Network