Thanks Niklas, yes having the whole TaskInfo would be helpful. I was wondering if the external containerizer be able to inform Mesos how much resources are actually being used out of the allocated resources?
On Wed, Apr 23, 2014 at 5:12 PM, Niklas Nielsen <[email protected]>wrote: > Sounds great Diptanu, > > We do owe more documentation on the current state of the external > containerizer API. However, it has been in (heavy) flux and I think it > makes sense for us to give a thorough walk-trough when it lands. > The whole task info will be available to the external containerizer > (including the new container field which defines image and options for the > containerizer) - was this what you were looking for? > > Niklas > > > On 23 April 2014 16:58, Diptanu Choudhury <[email protected]> wrote: > >> Hi, >> >> I am working on a containerizer similar to Deimos, and uses that Docker >> as well. I rolled out a custom executor for supporting docker and also to >> do things like register services inside containers with our service >> discovery platform and get logs out of containers into stderr and stdout of >> the mesos task. The new APIs around containerization would make it easier >> to pass information to the executors and I want to adopt the new APIs when >> they are released. >> >> >> On Wed, Apr 23, 2014 at 4:37 PM, Adam Bordelon <[email protected]>wrote: >> >>> Also see https://gist.github.com/solidsnack/10944095 for SolidSnack's >>> getting-started-with-deimos if you want to try out Deimos (uses >>> Mesosphere's custom branch including r/17567) >>> >>> >>> On Wed, Apr 23, 2014 at 4:08 PM, Niklas Nielsen <[email protected]>wrote: >>> >>>> Hey Diptanu, >>>> >>>> MESOS-816 (and dependent patches) are still in the works but getting >>>> close to land. These reviews (https://reviews.apache.org/r/17567/ and >>>> https://reviews.apache.org/r/20080/) are (more or less) the last two >>>> outstanding pieces. The first external containerizer which use the new API >>>> can be found here: https://github.com/mesosphere/deimos >>>> >>>> Are you writing a new isolator in the context of the old isolation >>>> architecture, or targeted the new containerizer API? >>>> >>>> Cheers, >>>> Niklas >>>> >>>> >>>> >>>> On 23 April 2014 15:59, Diptanu Choudhury <[email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> With Mesos 18 release, has support for passing ContainerInfo[per >>>>> MESOS-816] to slaves etc been released in the Java API? >>>>> >>>>> I am working on a docker isolator right now, and the only way I can >>>>> pass information to the executor right now is via the executor data. I am >>>>> wondering if Mesos 18 had anything to offer around that? I see a >>>>> ContainerID protobuf message but not sure what that is for. >>>>> >>>>> -- >>>>> Thanks, >>>>> Diptanu Choudhury >>>>> Web - www.linkedin.com/in/diptanu >>>>> Twitter - @diptanu <http://twitter.com/diptanu> >>>>> >>>> >>>> >>> >> >> >> -- >> Thanks, >> Diptanu Choudhury >> Web - www.linkedin.com/in/diptanu >> Twitter - @diptanu <http://twitter.com/diptanu> >> > > -- Thanks, Diptanu Choudhury Web - www.linkedin.com/in/diptanu Twitter - @diptanu <http://twitter.com/diptanu>
