Go to file
Robert Baldyga 35eb5682c9
Merge pull request #822 from Ostrokrzew/mq_fix
Fix adding core after core addition failure
2021-05-14 15:03:38 +02:00
.github/ISSUE_TEMPLATE Enumerate few types of devices in issue templates 2021-02-15 11:34:24 +01:00
casadm casadm: Error message for UUID_EXISTS error code 2021-04-14 20:15:14 +02:00
configure.d Set proper multiqueue flags 2021-04-16 22:52:18 -05:00
doc Merge pull request #691 from mmichal10/requirements 2021-02-19 17:10:46 +01:00
modules Typo fix 2021-05-13 17:02:05 +02:00
ocf@5b3a9606d3 Update ocf 2021-04-14 20:15:28 +02:00
test Merge pull request #774 from karolinavelkaja/fix_ioclass_pid_test 2021-05-10 15:29:01 +02:00
tools deb: Add tools required during modules compilation 2021-05-11 16:36:01 +02:00
utils opencas.py uses the f-string feature of python3.6+. 2021-03-29 18:17:11 +08:00
.gitignore Extending 'configure' script 2019-05-30 06:29:07 -04:00
.gitmodules Move OCL tests from test-framework repository 2019-10-18 15:27:21 +02:00
.pep8speaks.yml Add pep8speaks custom config 2019-07-30 08:42:12 +02:00
configure Move build system tools to separate directory 2021-03-19 15:37:55 +01:00
LICENSE Update copyright statements (2021) 2021-01-21 13:15:38 +01:00
Makefile Move build system tools to separate directory 2021-03-19 15:37:55 +01:00
README.md Update version referred by README to v21.3 2021-04-21 14:40:39 +02:00
version Bump master version to v21.6 2021-04-21 14:38:25 +02:00

Open CAS Linux

Build Status Tests Status Coverity status License

Open CAS accelerates Linux applications by caching active (hot) data to a local flash device inside servers. Open CAS implements caching at the server level, utilizing local high-performance flash media as the cache drive media inside the application server as close as possible to the CPU, thus reducing storage latency as much as possible. The Open Cache Acceleration Software installs into the GNU/Linux operating system itself, as a kernel module. The nature of the integration provides a cache solution that is transparent to users and applications, and your existing storage infrastructure. No storage migration effort or application changes are required.

Open CAS is distributed on BSD-3-Clause license (see https://opensource.org/licenses/BSD-3-Clause for full license texts).

Open CAS uses Safe string library (safeclib) that is MIT licensed.

Installation

To download latest Open CAS Linux release run following commands:

wget https://github.com/Open-CAS/open-cas-linux/releases/download/v21.3/open-cas-linux-21.03.0.0496.release.tar.gz
tar -xf open-cas-linux-21.03.0.0496.release.tar.gz
cd open-cas-linux-21.03.0.0496.release/

Alternatively, if you want recent development (unstable) version, you can clone GitHub repository:

git clone https://github.com/Open-CAS/open-cas-linux
cd open-cas-linux
git submodule update --init

To configure, build and install Open CAS Linux run following commands:

./configure
make
make install

The ./configure performs check for dependencies, so if some of them are missing, command will print their names in output. After installing missing dependencies you need to run ./configure once again - this time it should succeed.

NOTE: If after installing CAS, your system boots into emergency mode due to the "Failed to start opencas initialization service." error, you need to force SELinux relabelling in permissive mode on your filesystem.
Refer to the Open CAS documentation for details.

Getting Started

To quickly deploy Open CAS Linux in your system please follow the instructions available here.

Documentation

The complete documentation for Open CAS Linux is available in the Open CAS Linux Administration Guide.

Running Tests

Before running tests make sure you have a platform with at least 2 disks (one for cache and one for core). Be careful as these devices will be most likely overwritten with random data during tests. Tests can be either executed locally or on a remote platform (via ssh) specified in the dut_config.

  1. Go to test directory cd test/functional.
  2. Install dependencies with command pip3 install -r test-framework/requirements.txt.
  3. Create DUT config. See example here.
    a) Set disks params. You need at least two disks, of which at least one is an SSD drive.
    b) For remote execution uncomment and set the ip, user and password fields.
    c) For local execution just leave these fields commented.
  4. Run tests using command pytest-3 --dut-config=<CONFIG> where <CONFIG> is path to your config file, for example pytest-3 --dut-config="config/dut_config.yml".

Security

To report a potential security vulnerability please follow the instructions here.