Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-3919

Design URI fetcher interfaces.

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • None

    Description

      The design doc can be found here:
      https://docs.google.com/document/d/1p8tmQrGtxG6keZVo19gvHPr9WHxeny6PHTVofcLWqco/edit?usp=sharing

      The main design goal here is to decouple artifacts fetching from artifacts cache management. This proposal describes the interfaces for fetching artifacts, which are designed to be extensible so that we can add custom fetching support. Artifacts cache management is orthogonal to artifacts fetching, and is not the goal of this doc.

      The existing Fetcher contains both artifacts fetching logics and cache management logics. The former can leverage the new artifacts fetching interfaces described in this doc (i.e., uri::Fetcher) to fetch artifacts, or stay the same (using mesos-fetcher binary). Eventually, the existing Fetcher will use uri::Fetcher to download artifacts and we’ll be retiring the ‘mesos-fetcher’ binary.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jieyu Jie Yu
            jieyu Jie Yu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment