Fix the API for URIs

[ConnorDoyle]

In Mesos, command URIs can have some additional data, like whether to attempt to extract the downloaded file, and whether the downloaded file should have the executable permission bit set. The Marathon API doesn't adequately model these options, leading to awkward workarounds. (e.g. chmod ug+x myfile.sh && ./myfile.sh)

[abhay-agarwal]

Could we also check any downloaded URI against a SHA1 or MD5 that gets included in the json config?

[kolloch]

I like your suggestions, @abhay-agarwal and @ConnorDoyle.

If I understood @bernd-mesos correctly, the meson-fetcher supports setting permissions. It does not support checksums. So for the check sums we would need further support in mesos-fetcher.

[tarnfeld]

I'd love to see this! There's also fetcher configuration to avoid extracting tar.gz files if you don't want it extracted automatically. Perhaps something like;

{
  "urls": {
    "hdfs:///utils/my-thing": {
      "extract": true,
      "executable": true
    }
  }
}

Making this a dict would allow for easier backwards compatibility, too.

[bernd-mesos]

Once the Fetcher Cache MVP is committed (hopefully next week), checksums are on my plate in the next sprint.

[tarnfeld]

That's awesome to hear @bernd-mesos! I think the structure I posted above would work well with this as it'd be as simple as adding checksum field.

[ConnorDoyle]

Blocked by #1505, as we'd probably want to experiment with this for the v3 REST API.

On May 29, 2015, at 06:01, Tom Arnfeld notifications@github.com wrote:

That's awesome to hear @bernd-mesos! I think the structure I posted above would work well with this as it'd be as simple as adding checksum field.

—
Reply to this email directly or view it on GitHub.

[jasongilanfarr]

Don't we have fetch for this now?