[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Massenzio updated MESOS-2074: --- Sprint: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1, Mesosphere Q1 Sprint 9 - 5/15, Mesosphere Sprint 10, Mesosphere Sprint 11 (was: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1, Mesosphere Q1 Sprint 9 - 5/15, Mesosphere Sprint 10) > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Mathiske updated MESOS-2074: -- Sprint: 3.2/4.2 Sprint > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-2074: -- Sprint: Mesosphere Q1 Sprint 3 - 2/20 (was: 3.2/4.2 Sprint) > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Quarfot Nielsen updated MESOS-2074: -- Target Version/s: 0.23.0 (was: 0.22.0) > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Quarfot Nielsen updated MESOS-2074: -- Sprint: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 3 - 3/6 (was: Mesosphere Q1 Sprint 3 - 2/20) > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Quarfot Nielsen updated MESOS-2074: -- Sprint: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20 (was: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6) > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Quarfot Nielsen updated MESOS-2074: -- Sprint: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3 (was: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20) > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Quarfot Nielsen updated MESOS-2074: -- Sprint: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17 (was: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3) > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Quarfot Nielsen updated MESOS-2074: -- Sprint: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q1 Sprint 8 - 5/1 (was: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17) > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Mathiske updated MESOS-2074: -- Sprint: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1, Mesosphere Q1 Sprint 9 - 5/15 (was: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1) > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Massenzio updated MESOS-2074: --- Story Points: 5 (was: 1) > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2074) Fetcher cache test fixture
[ https://issues.apache.org/jira/browse/MESOS-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam B updated MESOS-2074: -- Sprint: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1, Mesosphere Q1 Sprint 9 - 5/15, Mesosphere Q1 Sprint 10 - 5/30 (was: Mesosphere Q1 Sprint 3 - 2/20, Mesosphere Q1 Sprint 4 - 3/6, Mesosphere Q1 Sprint 5 - 3/20, Mesosphere Q1 Sprint 6 - 4/3, Mesosphere Q1 Sprint 7 - 4/17, Mesosphere Q2 Sprint 8 - 5/1, Mesosphere Q1 Sprint 9 - 5/15) > Fetcher cache test fixture > -- > > Key: MESOS-2074 > URL: https://issues.apache.org/jira/browse/MESOS-2074 > Project: Mesos > Issue Type: Improvement > Components: fetcher, slave >Reporter: Bernd Mathiske >Assignee: Bernd Mathiske > Original Estimate: 72h > Remaining Estimate: 72h > > To accelerate providing good test coverage for the fetcher cache (MESOS-336), > we can provide a framework that canonicalizes creating and running a number > of tasks and allows easy parametrization with combinations of the following: > - whether to cache or not > - whether make what has been downloaded executable or not > - whether to extract from an archive or not > - whether to download from a file system, http, or... > We can create a simple HHTP server in the test fixture to support the latter. > Furthermore, the tests need to be robust wrt. varying numbers of StatusUpdate > messages. An accumulating update message sink that reports the final state is > needed. > All this has already been programmed in this patch, just needs to be rebased: > https://reviews.apache.org/r/21316/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
