Looks like there is a bunch of discussion around MESOS-4370 and RB# 43093. Kapil, as the shepherd, what is your take on the priority and readiness of this?
On Mon, Mar 7, 2016 at 1:16 PM, Daniel Osborne < daniel.osbo...@metaswitch.com> wrote: > -1 > > If it doesn’t cause too much pain, I'm hoping we can squeeze a relatively > small patch which restores Mesos' ability to extract Docker assigned IPs. > This has been broken with Docker 1.10's release over a month ago, and > prevents service discovery and DNS from working. > > Mesos-4370: https://issues.apache.org/jira/browse/MESOS-4370 > RB# 43093: https://reviews.apache.org/r/43093/ > > I've built 0.28.0-rc1 with this patch and can confirm that it fixes it as > expected. > > Apologies for not bringing this to attention earlier. > > Thanks all, > Dan > > -----Original Message----- > From: Vinod Kone [mailto:vinodk...@apache.org] > Sent: Thursday, March 3, 2016 5:44 PM > To: dev <dev@mesos.apache.org>; user <u...@mesos.apache.org> > Subject: [VOTE] Release Apache Mesos 0.28.0 (rc1) > > Hi all, > > > Please vote on releasing the following candidate as Apache Mesos 0.28.0. > > > 0.28.0 includes the following: > > > -------------------------------------------------------------------------------- > > * [MESOS-4343] - A new cgroups isolator for enabling the net_cls > subsystem in > > Linux. The cgroups/net_cls isolator allows operators to provide network > > > performance isolation and network segmentation for containers within a > Mesos > > cluster. To enable the cgroups/net_cls isolator, append > `cgroups/net_cls` to > > the `--isolation` flag when starting the slave. Please refer to > > > docs/mesos-containerizer.md for more details. > > > > > > * [MESOS-4687] - The implementation of scalar resource values (e.g., "2.5 > > > CPUs") has changed. Mesos now reliably supports resources with up to > three > > decimal digits of precision (e.g., "2.501 CPUs"); resources with more > than > > three decimal digits of precision will be rounded. Internally, > resource math > > is now done using a fixed-point format that supports three decimal > digits of > > precision, and then converted to/from floating point for input and > output, > > respectively. Frameworks that do their own resource math and manipulate > > > fractional resources may observe differences in roundoff error and > numerical > > precision. > > > > > > * [MESOS-4479] - Reserved resources can now optionally include "labels". > > > Labels are a set of key-value pairs that can be used to associate > metadata > > with a reserved resource. For example, frameworks can use this feature > to > > distinguish between two reservations for the same role at the same > agent > > that are intended for different purposes. > > > > > > * [MESOS-2840] - **Experimental** support for container images in Mesos > > > containerizer (a.k.a. Unified Containerizer). This allows frameworks to > > > launch Docker/Appc containers using Mesos containerizer without > relying on > > docker daemon (engine) or rkt. The isolation of the containers is done > using > > isolators. Please refer to docs/container-image.md for currently > supported > > features and limitations. > > > > > > * [MESOS-4793] - **Experimental** support for v1 Executor HTTP API. This > > > allows executors to send HTTP requests to the /api/v1/executor agent > > > endpoint without the need for an executor driver. Please refer to > > > docs/executor-http-api.md for more details. > > > > > > Additional API Changes: > > > * [MESOS-4066] - Agent should not return partial state when a request is > made to /state endpoint during recovery. > > * [MESOS-4547] - Introduce TASK_KILLING state. > > > * [MESOS-4712] - Remove 'force' field from the Subscribe Call in v1 > Scheduler API. > > * [MESOS-4591] - Change the object of ReserveResources and CreateVolume > ACLs to `roles`. > > * [MESOS-4712] - Remove 'force' field from the Subscribe Call in v1 > Scheduler API. > > * [MESOS-4591] - Change the object of ReserveResources and CreateVolume > ACLs to `roles`. > > * [MESOS-3583] - Add stream IDs for HTTP schedulers. > > > The CHANGELOG for the release is available at: > > > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.0-rc1 > > > -------------------------------------------------------------------------------- > > > The candidate for Mesos 0.28.0 release is available at: > > https://dist.apache.org/repos/dist/dev/mesos/0.28.0-rc1/mesos-0.28.0.tar.gz > > > The tag to be voted on is 0.28.0-rc1: > > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.28.0-rc1 > > > The MD5 checksum of the tarball can be found at: > > > https://dist.apache.org/repos/dist/dev/mesos/0.28.0-rc1/mesos-0.28.0.tar.gz.md5 > > > The signature of the tarball can be found at: > > > https://dist.apache.org/repos/dist/dev/mesos/0.28.0-rc1/mesos-0.28.0.tar.gz.asc > > > The PGP key used to sign the release is here: > > https://dist.apache.org/repos/dist/release/mesos/KEYS > > > The JAR is up in Maven in a staging repository here: > > https://repository.apache.org/content/repositories/orgapachemesos-1112 > > > Please vote on releasing this package as Apache Mesos 0.28.0! > > > The vote is open until Tue Mar 10 17:00:00 PST 2016 and passes if a > majority of at least 3 +1 PMC votes are cast. > > > [ ] +1 Release this package as Apache Mesos 0.28.0 > > [ ] -1 Do not release this package because ... > > > Thanks, >
