2014 Stable Releases

v2.3.9 - 19 December 2014

New features and bug fixes

  • Bugfix of the service catalog on the welcome page.
  • Improvements in documentation around traoubleshooting of the user deployments.

v2.3.8 - 17 December 2014

Migration procedure

IMPORTANT: v2.3.8 requires data migration from v2.3.7. The following steps MUST be followed:

  1. Stop SlipStream
  2. Stop HSQLDB (or your DB engine)
  3. Execute the following SQL files located in /opt/slipstream/server/migrations:
  • 010_varchar_size_fix_3.sql
  1. Start HSQLDB (or your DB engine)
  2. Start SlipStream**

Command to stop HSQLDB:

java -jar /opt/hsqldb/lib/sqltool.jar --inlineRc=url=jdbc:hsqldb:hsql://localhost:9001/slipstream,user=sa,password= --sql 'SHUTDOWN;'

Example command to execute the migration script:

java -jar /opt/hsqldb/lib/sqltool.jar --autoCommit --inlineRc=url=jdbc:hsqldb:file:/opt/slipstream/SlipStreamDB/slipstreamdb,user=sa,password= /opt/slipstream/server/migrations/010_varchar_size_fix_3.sql

New features and bug fixes

  • Performance improvement for Runs with a big amount of VMs.
  • StratusLab connector was refactored.
  • Support Cloud images without wget preinstalled (fallback to curl).
  • Bug fixes.

v2.3.7 - 7 November 2014

New features and bug fixes

  • Refactored cloud connector base classes to simplify connector development and maintenance on both Java and Python parts.
  • EC2 connector: migrated to the AWS python-boto 2.32.
  • StratusLab connector: RPM name changed - slipstream-connector-stratuslab-python obsoletes stratuslab-slipstream-downloads.
  • Bug fixes.

Migration

No DB migration (from v2.3.6) is required.

v2.3.6 - 29 October 2014

New features and bug fixes

  • Removed all usage of the deprecated SSLv3
  • Prefer the usage of TLSv1 for secure communications.
  • Bug fixes

Migration

No DB migration (from v2.3.5) is required.

v2.3.5 - 23 October 2014

New features and bug fixes

  • Removed autocreation of the users test and sixsq.
  • Improvement of the logging.
  • Fixed a bug where the ownership of a module can be changed implicitly when editing the module (#14).
  • Fixed a bug in the orchestrator that can generate a error in a mutable run (#15).
  • Fixed a bug in the StratusLab connector that prevent to Run an Image with an extra disk (#16).
  • Fixed a bug in the vCloud connector that prevent it to work with SlipStream v2.3.4+ (#17).
  • Added support for building an image with ss-execute.

Migration

No DB migration (from v2.3.4) is required.

v2.3.4 - 3 October 2014

Migration procedure

IMPORTANT: v2.3.4 requires data migration from v2.3.0. The following steps MUST be followed:

  1. Stop SlipStream
  2. Stop HSQLDB (or your DB engine)
  3. Execute the following SQL files located in /opt/slipstream/server/migrations:
  • 008_runtimeparameter_new_name_column.sql
  • 009_embedded_authz_in_module.sql
  1. Start HSQLDB (or your DB engine)
  2. Start SlipStream**

Command to stop HSQLDB:

java -jar /opt/hsqldb/lib/sqltool.jar --inlineRc=url=jdbc:hsqldb:hsql://localhost:9001/slipstream,user=sa,password= --sql 'SHUTDOWN;'

Example command to execute the migration script:

java -jar /opt/hsqldb/lib/sqltool.jar --autoCommit --inlineRc=url=jdbc:hsqldb:file:/opt/slipstream/SlipStreamDB/slipstreamdb,user=sa,password= /opt/slipstream/server/migrations/008_runtimeparameter_new_name_column.sql

New features and bug fixes

  • Database performance improvement.
  • Added support of mutable Run in ss-execute.
  • All server-side connectors are now extracted in individual packages.
  • Added per-connector config files.
  • Improved XML importation.
  • Improved error reporting from SlipStream Clients to the SlipStream Server.
  • Increase the maximal size of runtime parameter values to 4096 bytes.
  • Fixed a bug which prevent to get the runtimeparameters ‘ids’ and ‘multiplicity’ with ss-get.
  • Fixed a bug where a failure in a deployment script might not be detected.
  • Fixed a bug where deployment refuse to start if the cloudservice is set to ‘default’.
  • Fixed a bug of circular reference in modules.
  • Updated the documentation.

v2.3.0 - 14 August 2014

New features and bug fixes

  • Mutable Run.
  • Some UI improvements related to the mutable run.
  • SlipStream Client is now tolerant to network fault.
  • Refactored the SlipStream Client. Connectors needs to be upgraded to work with this version.
  • Improved the security of all resources by generating a restricted cookie for each Run.
  • When Metering is disabled the data collection is now also disabled.
  • Overall performance improvements.

Migration

No DB migration (from v2.2.5) is required.

v2.2.5 - 18 June 2014

New features and bug fixes

  • Some UI improvements related to the new state machine.
  • In the UI when a Run page is loaded the delay of 10 seconds before the first update of the overview section was removed.
  • Added the ability for privileged users to see the vmstate in the Runs of other users.
  • Improved the migration of the garbage collector.
  • Improved the logging and the error handling of describeInstance.
  • Fixed an HTTP 500 when there is no user-agent in the request.
  • Fixed a bug where when you try to build an image, run a deployment or run an image, the latest version is always used even if you were not on the latest version when creating the Run.

v2.2.4 - 13 June 2014

Migration procedure

IMPORTANT: v2.2.4 requires data migration from v2.2.3. The following steps MUST be followed:

  1. Stop SlipStream
  2. Stop HSQLDB (or your DB engine)
  3. Execute the SQL files located in /opt/slipstream/server/migrations (files 006 and 007)
  4. Start HSQLDB (or your DB engine)
  5. Start SlipStream**

Example command to execute the migration script:

java -jar /opt/hsqldb/lib/sqltool.jar --debug --autoCommit --inlineRc=url=jdbc:hsqldb:file:/opt/slipstream/SlipStreamDB/slipstreamdb,user=sa,password= /opt/slipstream/server/migrations/006_run_states_fix.sql

New features and bug fixes

  • New State Machine.
  • New logic for the garbage collector.
  • Auto-discovery of connectors.
  • Fixed a bug where module parameters disappear of the old version when a new version is saved.
  • Improved some RuntimeParameters.
  • Fixed a bug where SSH login with keys doesn’t work on images with SELinux enabled.
  • Improved messages displayed during a Build.
  • Added target script termination when abort flag is raised.
  • Improved the detection of VMs not killed in a final state.

v2.2.3 - 2 June 2014

New features and bug fixes

  • Improved error handling of CloudStack connector

  • Fixed a bug with SSH (paramiko)

  • Updated RPM packaging of SlipStream client

  • Updated xFilesFactor of graphite. For local update run the following

    for f in $(find /var/lib/carbon/whisper/slipstream/ -name *.wsp); do whisper-resize $f –xFilesFactor=0 –aggregationMethod=max 10s:6h 1m:7d 10m:5y; done

v2.2.2 - 27 May 2014

New features and bug fixes

  • Updated CloudStack connector to use the new TasksRunner when terminating instances
  • Force draw on usage panel, since now default section

v2.2.1 - 26 May 2014

Migration procedure

IMPORTANT: v2.2.1 requires data migration from v2.2.0. The following steps MUST be followed:

  1. Stop SlipStream
  2. Stop HSQLDB (or your DB engine)
  3. Execute the SQL files located in /opt/slipstream/server/migrations (file 005)
  4. Start HSQLDB (or your DB engine)
  5. Start SlipStream**

New features and bug fixes

  • Multi-thread bulk VM creation can be limited for clouds that can’t cope
  • Added support for CloudStack Advanced Zones as a sub-connector
  • Fix issues related to API doc and xml processing
  • Made c3p0 optional (see jar-persistence/src/main/resources/META-INF/persistence.xml for details)
  • Add persistence support for MySQL and Postgres
  • Update the OpenStack connector to use the new OpenStack CLI
  • Update poms following SlipStreamParent -> SlipStream git repo rename
  • Upgrade c3p0 version
  • Now using Apache HTTP client connector unstead of default Restlet Client connector
  • Streamline log entries for asynchronous activity
  • Upgrade Restlet to v2.2.1
  • Metering update communicate via temporary file instead of stdin
  • Remove StratusLab from default configuration
  • Fix strange orm issue with JPA 2.0
  • A few more minor bug fixes

v2.2.0 - 10 May 2014

Migration procedure

IMPORTANT: v2.2.0 requires data migration from v2.1.x. The following steps MUST be followed:

  1. Stop SlipStream
  2. Stop HSQLDB (or your DB engine)
  3. Execute the SQL files located in /opt/slipstream/server/migrations (files 001..004)
  4. Start HSQLDB (or your DB engine)
  5. Start SlipStream**

New features and bug fixes

  • Fixed performance issue under heavy load due to HashMap causing infinite loop
  • Wrapping parameters of Parameterized into ConcurrentHashMap
  • Improved asynchronious behaviour
  • Improved metering feature
  • Removed dependency on jclouds-slf4j
  • Removed hibernate3 maven plugin
  • Added SQL migration scripts
  • Removed Nexus tasks for repo generation
  • Migrate to Hibernate 4.3.5
  • Fix checkbox not set correctly in edit mode for user
  • Enable c3p0 database connection pooling by default
  • Improve ergonomics of run dashboard
  • Fixed issue with the metering legend items ending with a parenthesis
  • Fix several minor bug