Design Documentation
-
Wanna have a glance at Curve? Click here for Intro to Curve!
-
Want more details about CurveBS? Our documentation for every component:
-
Application based on CurveBS
-
CurveFS documentations
-
CurveAdm
CurveBS quick start
In order to improve the operation and maintenance convenience of Curve, we designed and developed the CurveAdm project, which is mainly used for deploying and managing Curve clusters. Currently, it supports the deployment of CurveBS & CurveFS (scaleout, upgrade and other functions are under development), please refer to the CurveAdm User Manual for related documentation, and install the CurveAdm tool according to the manual before deploying the Curve cluster.
Deploy an All-in-one experience environment
Please refer to the CurveBS cluster deployment steps in the CurveAdm user manual. For standalone experience, please use the “Cluster Topology File - Standalone Deployment” template.
The command tools’ instructions
FIO Curve block storage engine
Fio Curve engine is added, you can clone https://github.com/opencurve/fio and compile the fio tool with our engine(depend on nebd lib), fio command line example:
$ ./fio --thread --rw=randwrite --bs=4k --ioengine=nebd --nebd=cbd:pool//pfstest_test_ --iodepth=10 --runtime=120 --numjobs=10 --time_based --group_reporting --name=curve-fio-test
If you have any questions during performance testing, please check the Curve block storage performance tuning guide.
CurveFS quick start
Please use CurveAdm tool to deploy CurveFS，see CurveFS Deployment Process, and the CurveFS Command Instructions.
Test environment configuration
Please refer to the Test environment configuration
Practical
Governance
See Governance.
Contribute us
Participation in the Curve project is described in the Curve Developers Guidelines and is subject to a contributor contract.
We welcome your contribution!
Code of Conduct
Curve follows the CNCF Code of Conduct.
LICENSE
Curve is distributed under the Apache 2.0 LICENSE.
Release Cycle
-
CURVE release cycle：Half a year for major version, 1~2 months for minor version
-
Versioning format: We use a sequence of three digits and a suffix (x.y.z{-suffix}), x is the major version, y is the minor version, and z is for bugfix. The suffix is for distinguishing beta (-beta), RC (-rc) and GA version (without any suffix). Major version x will increase 1 every half year, and y will increase every 1~2 months. After a version is released, number z will increase if there’s any bugfix.
Branch
All the developments will be done under master branch. If there’s any new version to establish, a new branch release-x.y will be pulled from the master, and the new version will be released from this branch.
Contributors
This project exists thanks to all the people who contribute.
Made with contrib.rocks.
Star History
- Github Issues：You are sincerely welcomed to issue any bugs you came across or any suggestions through Github issues. If you have any question you can refer to our FAQ or join our user group for more details.
- FAQ：Frequently asked question in our user group, and we’ll keep working on it.
- User group：We use Wechat group currently.
- Double Week Meetings: We have an online community meeting every two weeks which talk about what Curve is doing and planning to do. The time and links of the meeting are public in the user group and Double Week Meetings.
评论