[
https://issues.apache.org/jira/browse/MESOS-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402390#comment-15402390
]
Zhitao Li commented on MESOS-5933:
----------------------------------
[[email protected]], from my perspective, what I want is to refactor the part
of natively fetching images from a docker registry as a separate binary so that
we can easily test different registries and storages options around.
It seems like mesos_fetcher is designed is used for fetching `CommandInfo.URI`
to sandbox. It remains a question to me whether these two things should be in
the same binary. Usually, image fetching is stored into the image `Store`,
which we probably don't want executors to play with?
> 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)
