@cantbewong cantbewong released this Aug 22, 2016 · 23 commits to master since this release

Assets 9

Features added since mesos-module-dvdi 0.4.4:

Added support for Mesos 1.0.0
mesos-module-dvdi now supports Mesos 0.23.1, 0.24.2, 0.25.1, 0.26.1, 0.27.2, 0.28.2, and 1.0.0

Former documented dev/build procedure used a Docker image containing a Mesos build to derive a second image for module development. These two Docker images have been reduced to a single improved version of the image containing the Mesos build. This image can be used to build the isolator module. It is anticipated that this same image will also be usable for generic isolator module development, including a future release of a libstorage isolator.

Change travis build to utilize the same Docker image provided for development. Formerly travis builds used a makefile running on an older Ubuntu release. This change makes the development and production build environments consistent.

@dvonthenen dvonthenen released this Jun 15, 2016 · 42 commits to master since this release

Assets 8

Addressed Issue #108 found in 0.4.3.

Users may see Mesos Agent crashes in the following conditions with the 0.4.3 release:

  • fresh install where the isolator has been installed but the agent has never been started previously
  • using a non-default working directory

Features added since mesos-module-dvdi 0.4.2:

  • Added support for Mesos 0.28.2
    mesos-module-dvdi now supports Mesos 0.23.1, 0.24.2, 0.25.1, 0.26.1, 0.27.2 and 0.28.2
  • Addressed Issue #94 - Isolator's checkpoint data (namely the mountlist) will be moved to the following directory: /var/run/mesos/isolators/mesos-module-dvdi/
  • Addressed Issue #97 - The isolator supports the explicit create flag in the docker volume driver interface. By default, the current behavior in the past release is unchanged (i.e. if the volume does not exist, the volume will be implicitly created). If the DVDI_VOLUME_EXPLICITCREATE is set to "true", if the volume does not exist prior to mounting, the task will fail.
  • Addressed Issue #99 - The isolator has functionality to allow the user to override the default path of the DVDCLI through the use of an environment variable called DVDI_VOLUME_DVDCLI.

@dvonthenen dvonthenen released this Jun 9, 2016 · 46 commits to master since this release

Assets 8

Features added since mesos-module-dvdi 0.4.2:

  • Added support for Mesos 0.28.2
    mesos-module-dvdi now supports Mesos 0.23.1, 0.24.2, 0.25.1, 0.26.1, 0.27.2 and 0.28.2
  • Addressed Issue #94 - Isolator's checkpoint data (namely the mountlist) will be moved to the following directory: /var/run/mesos/isolators/mesos-module-dvdi/
  • Addressed Issue #97 - The isolator supports the explicit create flag in the docker volume driver interface. By default, the current behavior in the past release is unchanged (i.e. if the volume does not exist, the volume will be implicitly created). If the DVDI_VOLUME_EXPLICITCREATE is set to "true", if the volume does not exist prior to mounting, the task will fail.
  • Addressed Issue #99 - The isolator has functionality to allow the user to override the default path of the DVDCLI through the use of an environment variable called DVDI_VOLUME_DVDCLI.

@cantbewong cantbewong released this Apr 18, 2016 · 56 commits to master since this release

Assets 8

Features added since mesos-module-dvdi 0.4.1:

  • Added support for Mesos 0.28.1
    mesos-module-dvdi now supports Mesos 0.23.1, 0.24.2, 0.25.1, 0.26.1, 027.2 and 0.28.1
  • Adapt to changed protobuf interface used in 0.28+ Mesos
  • Move from use of deprecated SVN which broke travis builds
  • fix broken volumes opts in prior commit

@cantbewong cantbewong released this Dec 16, 2015 · 103 commits to master since this release

Assets 5

This release supports Mesos 0.23.1, 0.24.1, and 0.25.0.

features:

  • Implement container isolation of mounted external volumes - allow utilization Linux namespace facility to limit visibility of volume mounts to a single task.
  • Support pre-emptive mounts when using rexray volume driver - when an agent node suffers an unplanned termination, mounts can be re-acquired on another agent cluster node.
  • Refactor mount journal to utilize google protocol buffer utilization Mesos checkpoint code for improved fault tolerance, and future extensibility.

This release closes the issues that listed milestones targets of 0.3.0 and 0.3.1

@cantbewong cantbewong released this Nov 12, 2015 · 146 commits to master since this release

Assets 3

This is a release aligned with Mesos 0.24.1

features added since 0.23.0-dvdi-0.1.0:

  • add support for Mesos 0.24.1
  • refactor code in response to a code review for compliance with Mesos style guidelines and conventions
  • refactor mount list to use Mesos checkpoint code. There is a Jira ticket to expose the Mesos checkpoint implementation as an API, but in the meantime this uses the template and inline code from a Mesos header file.
  • mount list saved in mesos metadata work directory