mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Wu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-5933) Refactor the uri::Fetcher as a binary.
Date Mon, 01 Aug 2016 19:12:20 GMT

    [ https://issues.apache.org/jira/browse/MESOS-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402653#comment-15402653
] 

Joseph Wu commented on MESOS-5933:
----------------------------------

You can do that by scheduling a task :)

One of the motivations behind the URI fetcher is to get rid of the extra binary (harder to
maintain and has some odd undesirable behavior in some configurations).  By running the fetcher
separately, you'll end up testing a different code path.  This is especially true if the fetcher
becomes pluggable.

> Refactor the uri::Fetcher as a binary.
> --------------------------------------
>
>                 Key: MESOS-5933
>                 URL: https://issues.apache.org/jira/browse/MESOS-5933
>             Project: Mesos
>          Issue Type: Improvement
>          Components: fetcher
>            Reporter: Gilbert Song
>            Assignee: Zhitao Li
>              Labels: fetcher, mesosphere
>
> By refactoring the uri::Fetcher as a binary, the fetcher can be used independently. Not
only mesos, but also new fetcher plugin testing, mesos cli and many other new components in
the future can re-use the binary to fetch any URI with different schemes. Ideally, after this
change, mesos cli is able to re-use the uri::Fetcher binary to introduce new image pulling
commands, e.g., `mesos fetch -i <path>`.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message