You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<pclass="has-line-data" data-line-start="3" data-line-end="4">DirectPV is a CSI driver for <ahref="https://en.wikipedia.org/wiki/Direct-attached_storage">Direct Attached Storage</a>. In a simpler sense, it is a distributed persistent volume manager, and not a storage system like SAN or NAS. It is useful to <em>discover, format, mount, schedule and monitor</em> drives across servers. Since Kubernetes <code>hostPath</code> and <code>local</code> PVs are statically provisioned and limited in functionality, DirectPV was created to address this limitation.</p>
4
+
<pclass="has-line-data" data-line-start="5" data-line-end="6">Distributed data stores such as object storage, databases and message queues are designed for direct attached storage, and they handle high availability and data durability by themselves. Running them on traditional SAN or NAS based CSI drivers (Network PV) adds yet another layer of replication/erasure coding and extra network hops in the data path. This additional layer of disaggregation results in increased-complexity and poor performance.</p>
<pclass="has-line-data" data-line-start="11" data-line-end="12">DirectPV is designed to be lightweight and scalable to 10s of 1000s of drives. It is made up of three components - <strong>Controller, Node Driver, UI</strong></p>
<pclass="has-line-data" data-line-start="17" data-line-end="18">When a volume claim is made, the controller provisions volumes uniformly from a pool free drives. DirectPV is aware of pod’s affinity constraints, and allocates volumes from drives local to pods. Note that only one active instance of controller runs per cluster.</p>
<pclass="has-line-data" data-line-start="21" data-line-end="22">Node Driver implements the volume management functions such as discovery, format, mount, and monitoring of drives on the nodes. One instance of node driver runs on each of the storage servers.</p>
<pclass="has-line-data" data-line-start="25" data-line-end="26">Storage Administrators can use the kubectl CLI plugin to select, manage and monitor drives. Web based UI is currently under development.</p>
<spanclass="hljs-comment"># Use the plugin to install directpv in your kubernetes cluster</span>
20
+
kubectl directpv install
21
+
22
+
<spanclass="hljs-comment"># Ensure directpv has successfully started</span>
23
+
kubectl directpv info
24
+
25
+
<spanclass="hljs-comment"># List available drives in your cluster</span>
26
+
kubectl directpv drives ls
27
+
28
+
<spanclass="hljs-comment"># Select drives that directpv should manage and format</span>
29
+
kubectl directpv drives format --drives /dev/sd{a...f} --nodes directpv-{<spanclass="hljs-number">1</span>...<spanclass="hljs-number">4</span>}
30
+
31
+
<spanclass="hljs-comment"># 'directpv' can now be specified as the storageclass in PodSpec.VolumeClaimTemplates</span>
32
+
</code></pre>
33
+
<pclass="has-line-data" data-line-start="48" data-line-end="49">For air-gapped setups and advanced installations, please refer to the <ahref="./docs/installation.md">Installation Guide</a>.</p>
<pclass="has-line-data" data-line-start="52" data-line-end="53">DirectPV version upgrades are seameless and transparent. Simply uninstall an existing version of directpv and install with a newer version to upgrade.</p>
<pclass="has-line-data" data-line-start="67" data-line-end="68">Please review the <ahref="./security-checklist.md">security checklist</a> before deploying to production.</p>
47
+
<pclass="has-line-data" data-line-start="69" data-line-end="70"><strong>Important</strong>: Report security issues to <ahref="mailto:[email protected]">[email protected]</a>. Please do not report security issues here.</p>
<pclass="has-line-data" data-line-start="87" data-line-end="88">DirectPV is released under GNU AGPLv3 license. Please refer to the LICENSE document for a complete copy of the license.</p>
0 commit comments