Re: LXC Container Support

Thanks guys. I do a lot of work with the juju ecosystem and lxc containers to deploy workloads with that, for example multi node big top clusters etc. It's far more flexible using LXC system containers than pre configured app containers. This works on cloud and bare metal but I'd also like to be

Re: 1.0.2 release

Release dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329719 I'm waiting for 2 issues to be resolved. Once that's done, I'll start prepping the release. On Wed, Oct 5, 2016 at 4:11 PM, Vinod Kone wrote: > Hi, > > As the Release Manager for

Re: LXC Container Support

Tom, I'm looking to add LXC/LXD support, POC initially then hopefully bake it > into some Mesos libraries. From what I can tell Mesos doesn't have hooks > for LXC in the new container setup and also the External Shim that was > underdevelopment is Deprecated. Sound roughly accurate so far? Yup.

Re: LXC Container Support

Hi Tom, Your description of the current state of art is on point. Regarding support for LXC/LXD, what exactly does it mean? Is there an image spec for those that you want Mesos to support? What's your use case? Thanks, On Wed, Oct 5, 2016 at 3:10 PM, Tom Barber wrote:

1.0.2 release

Hi, As the Release Manager for 1.0, I'm responsible for all subsequent patch releases. I'm planning to cut the next patch release (1.0.2) within a week. So, if you have any patches that need to get into 1.0.2 make sure that either it is already in the 1.0.x branch or the corresponding ticket has

LXC Container Support

Hello folks, I've been Googling Mesos container support a bit recently, I see support for Mesos(AppC) and Docker in the latest versions. I'm looking to add LXC/LXD support, POC initially then hopefully bake it into some Mesos libraries. From what I can tell Mesos doesn't have hooks for LXC in

Notification: Community Meeting @ Thu Oct 6, 2016 3pm - 4pm PST (Apache Mesos)

[GitHub] mesos pull request #168: Update contributors.yaml for gradywang.

Github user vinodkone commented on a diff in the pull request: https://github.com/apache/mesos/pull/168#discussion_r82063596 --- Diff: docs/contributors.yaml --- @@ -402,13 +402,14 @@ jira_user: yanyanhu reviewboard_user: yanyanhu -- name: Yong Qiao Wang

Re: Separate Compilation of Tests

@mpark Can you clarify if your goal is to: 1) refactor the source code (maybe including things like cluster.hpp) so that general compilation of any file is faster. Examples include allowing non-header-only stout, splitting out some files, moving some more stuff to cpps. or 2) splitting out the

Re: Mapped diagnostics context - Adding internal Mesos IDs as context to the logs

> > This is technically feasible: > // > // Specify an "extension" added to the filename specified via > // SetLogDestination. This applies to all severity levels. It's > // often used to append the port we're listening on to the logfile > // name. Thread-safe. > // > GOOGLE_GLOG_DLL_DECL void

[GitHub] mesos pull request #168: Update contributors.yaml for gradywang.

Github user gradywang commented on a diff in the pull request: https://github.com/apache/mesos/pull/168#discussion_r81929327 --- Diff: docs/contributors.yaml --- @@ -402,13 +402,14 @@ jira_user: yanyanhu reviewboard_user: yanyanhu -- name: Yong Qiao Wang