utilize slave work_dir for mount list file location, instead of a dedicated isolator parameter
cantbewong opened this issue · comments
In the v0.23.0 version of Mesos, the slave work directory was not readily available to an isolator implemented as a module. It is expected that this (slave work directory) will be available in an upcoming version of Mesos. When it is available, the existing isolator parameter will be deprecated, and the slave work directory will automatically be used instead. This will simplify configuration of the isolator
This is a link to the Jira ticket for adding access to the agents command line flags to the isolator module interface:
https://issues.apache.org/jira/browse/MESOS-4003
This is currently targeted for Mesos 0.27.0 so resolution of this issue is retarget for isolator 0.4.1
Changing plan to this:
since the work_dir is defined at the command line every time the agent is run anyway, we will just give it to DockerVolumeDriverIsolator::create() via the JSON string passed to the —modules flag?
more specifically, the ‘Parameters’ passed to —modules flag
existing code using work_dir should be refactored to use stout::path
Closed by last PR