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

MesosContainerizer support multiple image provisioners

    Details

    • Epic Name:
      Unified Container
    • Sprint:
      Mesosphere Sprint 12, Mesosphere Sprint 13, Mesosphere Sprint 14, Mesosphere Sprint 15, Mesosphere Sprint 16, Mesosphere Sprint 17

      Description

      We want to utilize the Appc integration interfaces to further make MesosContainerizers to support multiple image formats.
      This allows our future work on isolators to support any container image format.

      Design
      [open to public comments] ---- please use this document!
      https://docs.google.com/document/d/1oUpJNjJ0l51fxaYut21mKPwJUiAcAdgbdF7SAdAW2PA/edit?usp=sharing

      [original document requires permission]

        Issue Links

          Issues in Epic

            Activity

            Hide
            vinodkone Vinod Kone added a comment -

            Marco Massenzio Can you avoid putting epics into sprints? Mainly because epics labeled with "mesosphere" and "twitter" end up polluting our sprints. For example, Twitter cannot close its sprint because Mesosphere has an active sprint with a ticket that has "twitter" label. Meanwhile, I'll see if I can fix our sprints to not depend on the "twitter" label.

            Show
            vinodkone Vinod Kone added a comment - Marco Massenzio Can you avoid putting epics into sprints? Mainly because epics labeled with "mesosphere" and "twitter" end up polluting our sprints. For example, Twitter cannot close its sprint because Mesosphere has an active sprint with a ticket that has "twitter" label. Meanwhile, I'll see if I can fix our sprints to not depend on the "twitter" label.
            Hide
            marco-mesos Marco Massenzio added a comment -

            Sorry about that!
            I didn't even realize you could actually put an Epic into a Sprint (and the only reason Jira shows it was me, it's only because I closed the previous Sprint(s) and it automatically it moved to the next one).

            I'm taking this out of Sprint, it should totally not be there.

            Show
            marco-mesos Marco Massenzio added a comment - Sorry about that! I didn't even realize you could actually put an Epic into a Sprint (and the only reason Jira shows it was me, it's only because I closed the previous Sprint(s) and it automatically it moved to the next one). I'm taking this out of Sprint, it should totally not be there.
            Hide
            vinodkone Vinod Kone added a comment -

            Ian Downes Do you own the design doc linked in the description? If yes, can you move it to the public google domain (through your personal google account) instead of twitter's? It makes giving access to public easy.

            Show
            vinodkone Vinod Kone added a comment - Ian Downes Do you own the design doc linked in the description? If yes, can you move it to the public google domain (through your personal google account) instead of twitter's? It makes giving access to public easy.
            Hide
            stevenschlansker Steven Schlansker added a comment -

            Hi, I'm sorry I can't comment too much on the Mesos internals, but I just wanted to throw in my two cents as an end user. The Docker daemon is continually a thorn in our side, their "daemon forks the container process" model introduces an unnecessary single point of failure and just generally is not stable enough to be in that position. We are extremely excited to try out this work and look forward to being early adopters and finding all the bugs

            The design document looks well thought out and seems like an excellent approach.

            Show
            stevenschlansker Steven Schlansker added a comment - Hi, I'm sorry I can't comment too much on the Mesos internals, but I just wanted to throw in my two cents as an end user. The Docker daemon is continually a thorn in our side, their "daemon forks the container process" model introduces an unnecessary single point of failure and just generally is not stable enough to be in that position. We are extremely excited to try out this work and look forward to being early adopters and finding all the bugs The design document looks well thought out and seems like an excellent approach.
            Hide
            vinodkone Vinod Kone added a comment -

            IIUC, the MVP for this feature is complete? If yes, can you move the unresolved issues into a new epic and close this one?

            We also need a blurb for this in the CHANGELOG and user doc.

            Show
            vinodkone Vinod Kone added a comment - IIUC, the MVP for this feature is complete? If yes, can you move the unresolved issues into a new epic and close this one? We also need a blurb for this in the CHANGELOG and user doc.
            Hide
            xds2000 Deshi Xiao added a comment -

            i agree with Vinod Kone comment, anyone can update it?

            Show
            xds2000 Deshi Xiao added a comment - i agree with Vinod Kone comment, anyone can update it?

              People

              • Assignee:
                tnachen Timothy Chen
                Reporter:
                marco-mesos Marco Massenzio
                Shepherd:
                Benjamin Hindman
              • Votes:
                10 Vote for this issue
                Watchers:
                42 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Development

                    Agile