[jira] [Updated] (MESOS-3857) Draft Design Doc for first Step External Volume MVP
[ https://issues.apache.org/jira/browse/MESOS-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neil Conway updated MESOS-3857: --- Shepherd: Michael Park (was: Mike Park) > Draft Design Doc for first Step External Volume MVP > --- > > Key: MESOS-3857 > URL: https://issues.apache.org/jira/browse/MESOS-3857 > Project: Mesos > Issue Type: Task >Reporter: Joerg Schad >Assignee: Joerg Schad > Labels: mesosphere > > As part of the overall design doc for global resources we would like to > introduce improvements for Docker Volume Driver isolator module > (https://github.com/emccode/mesos-module-dvdi). > Currently the isolator module is controlled by setting environment variables > as follows: {code} "env": { > "DVDI_VOLUME_NAME": "testing", > "DVDI_VOLUME_DRIVER": "platform1", > "DVDI_VOLUME_OPTS": > "size=5,iops=150,volumetype=io1,newfstype=ext4,overwritefs=false", > "DVDI_VOLUME_NAME1": "testing2", > "DVDI_VOLUME_DRIVER1": "platform2", > "DVDI_VOLUME_OPTS1": "size=6,volumetype=gp2,newfstype=xfs,overwritefs=true" > } {code} We should develop a more structured way for passing these settings > to the isolator module which is in line with the overall goal of global > resources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3857) Draft Design Doc for first Step External Volume MVP
[ https://issues.apache.org/jira/browse/MESOS-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Massenzio updated MESOS-3857: --- Sprint: Mesosphere Sprint 22, Mesosphere Sprint 23 (was: Mesosphere Sprint 22) > Draft Design Doc for first Step External Volume MVP > --- > > Key: MESOS-3857 > URL: https://issues.apache.org/jira/browse/MESOS-3857 > Project: Mesos > Issue Type: Task >Reporter: Joerg Schad >Assignee: Joerg Schad > Labels: mesosphere > > As part of the overall design doc for global resources we would like to > introduce improvements for Docker Volume Driver isolator module > (https://github.com/emccode/mesos-module-dvdi). > Currently the isolator module is controlled by setting environment variables > as follows: {code} "env": { > "DVDI_VOLUME_NAME": "testing", > "DVDI_VOLUME_DRIVER": "platform1", > "DVDI_VOLUME_OPTS": > "size=5,iops=150,volumetype=io1,newfstype=ext4,overwritefs=false", > "DVDI_VOLUME_NAME1": "testing2", > "DVDI_VOLUME_DRIVER1": "platform2", > "DVDI_VOLUME_OPTS1": "size=6,volumetype=gp2,newfstype=xfs,overwritefs=true" > } {code} We should develop a more structured way for passing these settings > to the isolator module which is in line with the overall goal of global > resources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3857) Draft Design Doc for first Step External Volume MVP
[ https://issues.apache.org/jira/browse/MESOS-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schad updated MESOS-3857: --- Description: As part of the overall design doc for global resources we would like to introduce improvements for Docker Volume Driver isolator module (https://github.com/emccode/mesos-module-dvdi). Currently the isolator module is controlled by setting environment variables as follows: {code} "env": { "DVDI_VOLUME_NAME": "testing", "DVDI_VOLUME_DRIVER": "platform1", "DVDI_VOLUME_OPTS": "size=5,iops=150,volumetype=io1,newfstype=ext4,overwritefs=false", "DVDI_VOLUME_NAME1": "testing2", "DVDI_VOLUME_DRIVER1": "platform2", "DVDI_VOLUME_OPTS1": "size=6,volumetype=gp2,newfstype=xfs,overwritefs=true" } {code} We should develop a more structured way for passing these settings to the isolator module which is in line with the overall goal of global resources. was: As part of the overall design doc for global resources we would like to introduce improvements for Docker Volume Driver isolator module (https://github.com/emccode/mesos-module-dvdi). Currently the isolator module is controlled by setting environment variables as follows: {code} "env": { "DVDI_VOLUME_NAME": "testing", "DVDI_VOLUME_DRIVER": "platform1", "DVDI_VOLUME_OPTS": "size=5,iops=150,volumetype=io1,newfstype=ext4,overwritefs=false", "DVDI_VOLUME_NAME1": "testing2", "DVDI_VOLUME_DRIVER1": "platform2", "DVDI_VOLUME_OPTS1": "size=6,volumetype=gp2,newfstype=xfs,overwritefs=true" } {code}. We should develop a more structured way for passing these settings to the isolator module which is in line with the overall goal of global resources. > Draft Design Doc for first Step External Volume MVP > --- > > Key: MESOS-3857 > URL: https://issues.apache.org/jira/browse/MESOS-3857 > Project: Mesos > Issue Type: Task >Reporter: Joerg Schad >Assignee: Joerg Schad > Labels: mesosphere > > As part of the overall design doc for global resources we would like to > introduce improvements for Docker Volume Driver isolator module > (https://github.com/emccode/mesos-module-dvdi). > Currently the isolator module is controlled by setting environment variables > as follows: {code} "env": { > "DVDI_VOLUME_NAME": "testing", > "DVDI_VOLUME_DRIVER": "platform1", > "DVDI_VOLUME_OPTS": > "size=5,iops=150,volumetype=io1,newfstype=ext4,overwritefs=false", > "DVDI_VOLUME_NAME1": "testing2", > "DVDI_VOLUME_DRIVER1": "platform2", > "DVDI_VOLUME_OPTS1": "size=6,volumetype=gp2,newfstype=xfs,overwritefs=true" > } {code} We should develop a more structured way for passing these settings > to the isolator module which is in line with the overall goal of global > resources. -- This message was sent by Atlassian JIRA (v6.3.4#6332)