|
|
| (5 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
| − | =Local environment without CCM and Devstack = | + | =Local environment without CCM and Devstack= |
| | | | |
| − | ==Environment Creation==
| + | '''This page is outdated. Please check the latest documentation here https://magnetodb.readthedocs.org/en/latest/''' |
| − | | |
| − | 1. Download [http://www.apache.org/dyn/closer.cgi?path=/cassandra/2.0.6/apache-cassandra-2.0.6-bin.tar.gz Cassandra 2.0.6]
| |
| − | | |
| − | 2. Run Cassandra single node instance
| |
| − | <pre>
| |
| − | $ cd apache-cassandra-2.0.6/bin
| |
| − | $ sudo ./cassandra -f
| |
| − | </pre>
| |
| − | | |
| − | 3. Run CQLSH
| |
| − | <pre>
| |
| − | $ cd apache-cassandra-2.0.6/bin
| |
| − | $ ./cqlsh
| |
| − | </pre>
| |
| − | create service keyspaces and table
| |
| − | <pre>
| |
| − | cqlsh> CREATE KEYSPACE magnetodb WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor' : 1 };
| |
| − | cqlsh> CREATE TABLE magnetodb.table_info(tenant text, name text, exists int, "schema" text, status text, internal_name text, PRIMARY KEY(tenant, name));
| |
| − | cqlsh> CREATE KEYSPACE user_default_tenant WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor' : 1 };
| |
| − | </pre>
| |
| − | | |
| − | 4. Clone MagnetoDB repo
| |
| − | <pre>
| |
| − | $ git clone https://github.com/stackforge/magnetodb.git
| |
| − | $ cd magnetodb
| |
| − | </pre>
| |
| − | | |
| − | ==Tests Running==
| |
| − | | |
| − | 5. Run tox with necessary parameters:
| |
| − |
| |
| − | * to start unit tests:
| |
| − | <pre>
| |
| − | $ tox
| |
| − | </pre>
| |
| − | | |
| − | * to start Cassandra implementation tests:
| |
| − | <pre>
| |
| − | $ tox -e cassandra-impl
| |
| − | </pre>
| |
| − | | |
| − | * to start '''''stable''''' tempest tests (this folder contains scenarios that verify already implemented functionality):
| |
| − | <pre>
| |
| − | $ tox -e tempest-stable
| |
| − | </pre>
| |
| − | | |
| − | * to start '''''in_progress''''' tempest tests (contains scenarios that are in progress (i.e. is being worked on) or the functionality that is a subject to changes (minor additions, refactoring, debugging)):
| |
| − | <pre>
| |
| − | $ tox -e tempest-in-progress
| |
| − | </pre>
| |
| − | | |
| − | * to start '''''not_ready''''' tempest tests (dedicated to the test scenarios that were created, but the appropriate functionality is not ready yet (not implemented or partially implemented)):
| |
| − | <pre>
| |
| − | $ tox -e tempest-not-ready
| |
| − | </pre>
| |
| − | <br />
| |
| − | | |
| − | '''Note:''' Each group of tests run in individual venv and will require some time to install dependencies (Python packages)
| |
