Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Sun, 3 Jul 2016 18:20:10 +0000 (UTC)
From: "Jie Yu (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12986481.1467569968000.14520.1467570010936@Atlassian.JIRA>
In-Reply-To: <JIRA.12986481.1467569968000@Atlassian.JIRA>
References: <JIRA.12986481.1467569968000@Atlassian.JIRA> <JIRA.12986481.1467569968246@arcas>
Subject: [jira] [Created] (MESOS-5775) Add a new CVMFS image type.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 03 Jul 2016 18:20:13 -0000

Jie Yu created MESOS-5775:
-----------------------------

             Summary: Add a new CVMFS image type.
                 Key: MESOS-5775
                 URL: https://issues.apache.org/jira/browse/MESOS-5775
             Project: Mesos
          Issue Type: Task
            Reporter: Jie Yu


One way to specify a CVMFS image is like the following. Using a combination of repository name and the path to the image in the repository.

If we were to support CVMFS image using a catalog, we needed to think about what's the best way to express that. Maybe we should make `Cvmfs` message more extensible with that in mind.

{code}
message Image {
  enum Type {
    APPC = 1;
    DOCKER = 2;
    CVMFS = 3;
  }
  
  message Cvmfs {
    required string repository = 1;
    required string path = 2;
  }

  optional Cvmfs cvmfs = 5;
}
{code}


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