Install cio

A convenience script installs the community edition of cio software into your development environments quickly and non-interactively. The use of convenience scripts is recommended for dev environments only, as root permissions are required to run them. This script will detect your Linux distribution and version, and install all dependencies and suggestions of the package manager without asking for confirmation.

Storidge's cio software currently supports CentOS 7.5, 7.6 (3.10 kernel), RHEL 7 (3.10 kernel), Ubuntu 16.04LTS (4.4 kernel), and Ubuntu 18.04LTS (4.15 kernel).

Note that the desktop edition of Ubuntu 16.04 lists a 4.15 kernel. Use the server edition of Ubuntu 18.04 instead for 4.15 kernel support.

After verifying you have a supported distribution, run the convenience script below to begin installation.

curl -fsSL | sudo bash


root@demo:~# curl -fsSL | sudo bash
Started installing release 2859 at Tue Jul  9 13:05:15 PDT 2019
Loading cio software for: u16  (4.4.0-148-generic)
Reading package lists... Done
Building dependency tree
Finished at Tue Jul  9 13:08:39 PDT 2019

Installation completed. cio requires a minimum of 3 local drives per node for data redundancy.

To start a cluster, run 'cioctl create' on primary node. To add a node, generate a join token
with 'cioctl join-token' on sds node. Then run the 'cioctl node add ...' output on this node.


The installation requires access to system devices so sudo access or root user is needed

Add More Nodes

The cio software will run with just one node in the cluster. This is great if you just want to get a flavor of the capabilities of the software, and do not need high availability or advanced features like automatic data locality.

On the other hand, cio allows you to add more nodes to the cluster to increase performance, capacity and enable high availability for your applications. Repeat the convenience script installation on all nodes that will be included in the cluster. Run:

curl -fsSL | sudo bash

A multi-node configuration requires a minimum of three nodes. Currently two node configurations are not supported.

For production deployments and high availability support, a minimum of four nodes is recommended.

Last Updated: 10/1/2019, 3:40:19 PM