The following instructions describe how to run the SlipStream server locally, primarily for development. If you are interested in running SlipStream in production, you should install it from the generated packages following the instructions in the Administrator Guide.


SlipStream needs a JDBC friendly database. By default we use HSQLDB, but the persistence.xml file contains a number of other databases, including MySQL and PostgreSQL. SlipStream API server uses Elastic Search.

Database Configuration

Create an HSQLDB definition file in your home area:

$ cat > ~/sqltool.rc << EOF
urlid slipstream
url jdbc:hsqldb:hsql://localhost/slipstream
username SA

The default username is “SA” and the default password is blank.

Starting the Database

The HSQLDB database (a pure Java database) will have been downloaded to your local maven repository when you built SlipStream. You can run the database with the downloaded jar file:

$ java -cp ~/.m2/repository/org/hsqldb/hsqldb/2.3.4/hsqldb-2.3.4.jar \
       org.hsqldb.server.Server \
       --database.0 file:slipstreamdb \
       --dbname.0 slipstream &

Note that starting the database in this way should not be done in production. This is intended only for development testing.

Elastic Search installation

Follow instructions from Elastic Search documentation:

Please use same version as the one found used SlipStream server (see pom.xml in SlipStream project).

To start Elastic Search engine, just type (in the bin directory):

$ ./elasticsearch

SlipStream Services

SlipStream is composed of a number of services. This section describes how to start these services.

Starting the Ancillary SlipStream Service

This service should be started first and includes additional resources, such as event and usage resources. As opposed to the main service, which is written in Java, this service is written in Clojure. The service uses both HSQLDB and Elasticsearch, so they should be up and running prior to starting the service.

The service should be started from the ssclj/jar module of SlipStreamServer project.

$ cd SlipStreamServer/ssclj/jar

To run the service, export the required environment variables, start Clojure REPL with boot and in the REPL run the commands listed below:

$ boot server-repl
  boot.user=> (require '[ :as server :reload true])
  boot.user=> (def stop-fn (server/start 8201))
  boot.user=> ;; when needed, stop with
  boot.user=> ;; (server/stop stop-fn)

The services will be started on port 8201. You can set it as needed, taking into account that it will be required later during the startup of the main SlipStream service.

It is assumed that an instance of Elasticsearch is running on localhost:9300. If this is not the case, export the following environment variables defining the coordinates of Elasticsearch:

$ export ES_HOST=<es-host>
$ export ES_PORT=<es-port>

The service uses the configuration file defined by CONFIG_NAME environment variable. To be found by the service, the file should be on the service’s classpath. SlipStreamServer/ssclj/jar/ (the project’s configuration file) sets the service configuration file name and extends the classpath to include the default location containing the file. Typically, the file is named config-hsqldb-mem.edn and located in test-resources:

(environ :env {:config-name      "config-hsqldb-mem.edn"
(set-env! :source-paths #(set (concat % #{"test" "test-resources"})))

So, both the file name and its location can be modified in

Apart from other configuration parameters the configuration file contains HSQLDB configuration definition. Typical content looks like:

{:auth-db {
  :classname    "org.hsqldb.jdbc.JDBCDriver"
  :subprotocol  "hsqldb"
  :subname      "mem://localhost:9012/devresources"
  :make-pool?   true}}

The service’s log file can be found under logs/ssclj-.log.

You can add other dependencies to the classpath as needed. This can be done either by editing the list of dependencies in build.boot:

21   :dependencies
22   #(vec (concat %
23                 (merge-defaults
24                  ['sixsq/default-deps (get-env :version)]
25                  '[[org.clojure/clojure]
58                    [com.sixsq.slipstream/SlipStreamConnector-OpenStack-conf]
59                    ;; added OpenStack connector jar

or providing the dependencies to boot command as follows:

$ boot -d com.sixsq.slipstream/SlipStreamConnector-OpenStack-conf:3.17-SNAPSHOT repl

By adding connectors jar to the classpath of the service (as shown above) we allow the service to create the connector instances.

Starting Pricing and Ranking Service (PRS)

To start PRS service go to SlipStreamServer/jar-prs-service and run:

$ boot run

The service starts on localhost:3000 by default. Logs go to stdout/err.

Starting the Main SlipStream Service

To run the main server, drop into the war subdirectory in the SlipStreamServer project and then use Jetty to run the SlipStream web archive (war file).

$ cd SlipStreamServer/war
$ mvn jetty:run-war

If the last command returns an error like JettyRunWarMojo : Unsupported major.minor version 51.0 make sure you have Java 8 installed. You can find the appropriate download from the Java web site. You may also want to consult this article for setting up the environment.

As you can see, we run SlipStream as a war behind Jetty. Now that the server’s running, visit http://localhost:8080/ with your Web browser.

During development, especially when working on the UI with css and JavaScript files, to avoid the war building round trip, you can start the server pointing to source static location as following:

$ export ES_HOST=localhost
$ export ES_PORT=9300
$ mvn jetty:run-war \

The server makes use of Elasticsearch as database backend, therefore, you see the need to set the host and port of Elasticsearch. You can also change the main database backend connection using the persistence.unit. For example:




You will obviously need to have either MySQL or Postgresql running when configuring the server in this way.

To add cloud connectors you need to modify pom.xml. Below is an example of adding Exoscale connector that depends on CloudStack connector. Please note that both jar and conf artifacts should be added.


You are now ready to configure your new SlipStream server.


If you intend to configure your system from configuration files, do not start your service just yet and read on.