+1 (non-binding) Tested with ROOT and docker on debian jessie.
On Mon, Nov 7, 2016 at 2:19 PM, Vinod Kone <vinodk...@apache.org> wrote: > +1 (binding) > > Tested on ASF CI. > > *Revision*: a44b077ea0df54b77f05550979e1e97f39b15873 > > - refs/tags/1.1.0-rc3 > > Configuration Matrix gcc clang > centos:7 --verbose --enable-libevent --enable-ssl autotools > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20-- > enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1% > 20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C% > 7CHadoop)&&(!ubuntu-us1)/> > [image: Not run] > cmake > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=-- > verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT= > GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker% > 7C%7CHadoop)&&(!ubuntu-us1)/> > [image: Not run] > --verbose autotools > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose, > ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_ > exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/> > [image: Not run] > cmake > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=-- > verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos% > 3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/> > [image: Not run] > ubuntu:14.04 --verbose --enable-libevent --enable-ssl autotools > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20-- > enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1% > 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C% > 7CHadoop)&&(!ubuntu-us1)/> > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose%20-- > enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1% > 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C% > 7CHadoop)&&(!ubuntu-us1)/> > cmake > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=-- > verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT= > GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=( > docker%7C%7CHadoop)&&(!ubuntu-us1)/> > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=- > -verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT= > GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=( > docker%7C%7CHadoop)&&(!ubuntu-us1)/> > --verbose autotools > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose, > ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04, > label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/> > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose, > ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04, > label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/> > cmake > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=-- > verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu% > 3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/> > [image: Success] > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos- > Release/23/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=- > -verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu% > 3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/> > > On Mon, Nov 7, 2016 at 7:49 AM, Evers Benno <ben...@yandex-team.ru> wrote: > > > +1 (non-binding) > > > > Built and installed on Ubuntu 10.04 + 14.04 > > > > Configured with --disable-java --enable-python --disable-bundled-pip > > --disable-python-dependency-install > > > > On 04.11.2016 14:15, Till Toenshoff wrote: > > > Hi all, > > > > > > Please vote on releasing the following candidate as Apache Mesos 1.1.0. > > > > > > > > > 1.1.0 includes the following: > > > ------------------------------------------------------------ > > -------------------- > > > * [MESOS-2449] - **Experimental** support for launching a group of > > tasks > > > via a new `LAUNCH_GROUP` Offer operation. Mesos will guarantee that > > either > > > all tasks or none of the tasks in the group are delivered to the > > executor. > > > Executors receive the task group via a new `LAUNCH_GROUP` event. > > > > > > * [MESOS-2533] - **Experimental** support for HTTP and HTTPS health > > checks. > > > Executors may now use the updated `HealthCheck` protobuf to > implement > > > HTTP(S) health checks. Both default executors (command and docker) > > leverage > > > `curl` binary for sending HTTP(S) requests and connect to > > `127.0.0.1`, > > > hence a task must listen on all interfaces. On Linux, for BRIDGE > and > > USER > > > modes, docker executor enters the task's network namespace. > > > > > > * [MESOS-3421] - **Experimental** Support sharing of resources across > > > containers. Currently persistent volumes are the only resources > > allowed to > > > be shared. > > > > > > * [MESOS-3567] - **Experimental** support for TCP health checks. > > Executors > > > may now use the updated `HealthCheck` protobuf to implement TCP > > health > > > checks. Both default executors (command and docker) connect to > > `127.0.0.1`, > > > hence a task must listen on all interfaces. On Linux, for BRIDGE > and > > USER > > > modes, docker executor enters the task's network namespace. > > > > > > * [MESOS-4324] - Allow tasks to access persistent volumes in either a > > > read-only or read-write manner. Using a volume in read-only mode > can > > > simplify sharing that volume between multiple tasks on the same > > agent. > > > > > > * [MESOS-5275] - **Experimental** support for linux capabilities. > > Frameworks > > > or operators now have fine-grained control over the capabilities > > that a > > > container may have. This allows a container to run as root, but not > > have all > > > the privileges associated with the root user (e.g., CAP_SYS_ADMIN). > > > > > > * [MESOS-5344] - **Experimental** support for partition-aware Mesos > > > frameworks. In previous Mesos releases, when an agent is > partitioned > > from > > > the master and then reregisters with the cluster, all tasks running > > on the > > > agent are terminated and the agent is shutdown. In Mesos 1.1, > > partitioned > > > agents will no longer be shutdown when they reregister with the > > master. By > > > default, tasks running on such agents will still be killed (for > > backward > > > compatibility); however, frameworks can opt-in to the new > > PARTITION_AWARE > > > capability. If they do this, their tasks will not be killed when a > > partition > > > is healed. This allows frameworks to define their own policies for > > how to > > > handle partitioned tasks. Enabling the PARTITION_AWARE capability > > also > > > introduces a new set of task states: TASK_UNREACHABLE, > TASK_DROPPED, > > > TASK_GONE, TASK_GONE_BY_OPERATOR, and TASK_UNKNOWN. These new > states > > are > > > intended to eventually replace the TASK_LOST state. > > > > > > * [MESOS-5788] - **Experimental** support for Java scheduler adapter. > > This > > > adapter allows framework developers to toggle between the old/new > API > > > (driver/scheduler library) implementations, thereby allowing them > to > > easily > > > transition their frameworks to the new v1 Scheduler API. > > > > > > * [MESOS-6014] - **Experimental** A new port-mapper CNI plugin, the > > > `mesos-cni-port-mapper` has been introduced. For Mesos containers, > > with the > > > CNI port-mapper plugin, users can now expose container ports > through > > host > > > ports using DNAT. This is especially useful when Mesos containers > are > > > attached to isolated CNI networks such as private bridge networks, > > and the > > > services running in the container needs to be exposed outside these > > > isolated networks. > > > > > > * [MESOS-6077] - **Experimental** A new default executor is > introduced > > which > > > frameworks can use to launch task groups as nested containers. All > > the > > > nested containers share resources likes cpu, memory, network and > > volumes. > > > > > > 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=1.1.0-rc3 > > > ------------------------------------------------------------ > > -------------------- > > > > > > The candidate for Mesos 1.1.0 release is available at: > > > https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc3/ > > mesos-1.1.0.tar.gz > > > > > > The tag to be voted on is 1.1.0-rc3: > > > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a= > commit;h=1.1.0-rc3 > > > > > > The MD5 checksum of the tarball can be found at: > > > https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc3/ > > mesos-1.1.0.tar.gz.md5 > > > > > > The signature of the tarball can be found at: > > > https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc3/ > > mesos-1.1.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-1166 > > > > > > Please vote on releasing this package as Apache Mesos 1.1.0! > > > > > > The vote is open until Wednesday Nov 9 14:00:29 CET 2016 and passes if > a > > majority of at least 3 +1 PMC votes are cast. > > > > > > [ ] +1 Release this package as Apache Mesos 1.1.0 > > > [ ] -1 Do not release this package because ... > > > > > > Thanks, > > > Alex & Till > > > > > > -- Cheers, Zhitao Li
