Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

[Kapil Arya]

You can find the 1.0.0 rpm/deb packages at:

http://open.mesosphere.com/downloads/mesos/#apache-mesos-1.0.0


And here are the corresponding docker images based off of Ubuntu 14.04:

mesosphere/mesos:1.0.0
mesosphere/mesos-master:1.0.0
mesosphere/mesos-slave:1.0.0

Kapil

On Wed, Jul 27, 2016 at 2:52 PM, Jeff Schroeder 
wrote:

> Small nit but can you s/experimnental/experimental/ under the "Storage"
> header in the release post please?
>
> Great work otherwise everyone!
>
>
> On Wednesday, July 27, 2016, Vinod Kone  wrote:
>
>> Hi all,
>>
>> The vote for Mesos 1.0.0 (rc4) has passed with the following votes.
>>
>>
>> +1 (Binding)
>>
>> --
>>
>> Kapil Arya
>>
>> Jie Yu
>>
>> Benjamin Mahler
>>
>>
>> +1 (Non-binding)
>>
>> --
>>
>> Haosdent
>>
>> Greg Mann
>>
>> Zhitao Li
>>
>>
>> +0
>>
>> -
>>
>> Yan Xu
>>
>>
>> There were no  -1 votes.
>>
>>
>> *NOTE: There were a couple known issues [MESOS-5911
>> , MESOS-5913
>> ] that couldn't be fixed
>> in time for the 1.0. We plan to do a patch release to fix these ASAP.*
>>
>>
>> Please find the release at:
>>
>> https://dist.apache.org/repos/dist/release/mesos/1.0.0
>>
>>
>> It is recommended to use a mirror to download the release:
>>
>> http://www.apache.org/dyn/closer.cgi
>>
>>
>> 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.0.0
>>
>>
>> The mesos-1.0.0.jar has been released to:
>>
>> https://repository.apache.org
>>
>>
>> The website (http://mesos.apache.org) will be updated shortly to reflect
>> this release.
>>
>>
>> Thanks,
>>
>> On Fri, Jul 22, 2016 at 10:40 PM, Vinod Kone 
>> wrote:
>>
>>> Hi all,
>>>
>>>
>>> Please vote on releasing the following candidate as Apache Mesos 1.0.0.
>>>
>>> *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a
>>> majority of at least 3 +1 PMC votes are cast.*
>>>
>>> 1.0.0 includes the following:
>>>
>>>
>>> 
>>>
>>>   * Scheduler and Executor v1 HTTP APIs are now considered stable.
>>>
>>>
>>>
>>>
>>>
>>>   * [MESOS-4791] - **Experimental** support for v1 Master and Agent
>>> APIs. These
>>>
>>> APIs let operators and services (monitoring, load balancers) send
>>> HTTP
>>>
>>> requests to '/api/v1' endpoint on master or agent. See
>>>
>>>
>>> `docs/operator-http-api.md` for details.
>>>
>>>
>>>
>>>
>>>
>>>   * [MESOS-4828] - **Experimental** support for a new `disk/xfs'
>>> isolator
>>>
>>> has been added to isolate disk resources more efficiently. Please
>>> refer to
>>>
>>> docs/mesos-containerizer.md for more details.
>>>
>>>
>>>
>>>
>>>
>>>   * [MESOS-4355] - **Experimental** support for Docker volume plugin. We
>>> added a
>>>
>>> new isolator 'docker/volume' which allows users to use external
>>> volumes in
>>>
>>> Mesos containerizer. Currently, the isolator interacts with the
>>> Docker
>>>
>>> volume plugins using a tool called 'dvdcli'. By speaking the Docker
>>> volume
>>>
>>> plugin API, most of the Docker volume plugins are supported.
>>>
>>>
>>>
>>>
>>>
>>>   * [MESOS-4641] - **Experimental** A new network isolator, the
>>>
>>>
>>> `network/cni` isolator, has been introduced in the
>>> `MesosContainerizer`. The
>>>
>>> `network/cni` isolator implements the Container Network Interface
>>> (CNI)
>>>
>>> specification proposed by CoreOS.  With CNI the `network/cni`
>>> isolator is
>>>
>>> able to allocate a network namespace to Mesos containers and attach
>>> the
>>>
>>> container to different types of IP networks by invoking network
>>> drivers
>>>
>>> called CNI plugins.
>>>
>>>
>>>
>>>
>>>
>>>   * [MESOS-2948, MESOS-5403] - The authorizer interface has been
>>> refactored in
>>>
>>> order to decouple the ACLs definition language from the interface.
>>>
>>>
>>> It additionally includes the option of retrieving `ObjectApprover`.
>>> An
>>>
>>> `ObjectApprover` can be used to synchronously check authorizations
>>> for a
>>>
>>> given object and is hence useful when authorizing a large number of
>>> objects
>>>
>>> and/or large objects (which need to be copied using request based
>>>
>>>
>>> authorization). NOTE: This is a **breaking change** for authorizer
>>> modules.
>>>
>>>
>>>
>>>
>>>   * [MESOS-5405] - The `subject` and `object` fields in
>>> authorization::Request
>>>
>>> have been changed from required to optional. If either of these
>>> fields is
>>>
>>> not set, the request should only be authorized if any subject/object
>>> should
>>>
>>> be allowed.
>>>
>>>
>>> NOTE: This is a semantic change for authorizer modules.
>>>
>>>
>>>
>>>
>>>
>>>   * [MESOS-4931, MESOS-5709, 

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

[Jeff Schroeder]

Small nit but can you s/experimnental/experimental/ under the "Storage"
header in the release post please?

Great work otherwise everyone!

On Wednesday, July 27, 2016, Vinod Kone  wrote:

> Hi all,
>
> The vote for Mesos 1.0.0 (rc4) has passed with the following votes.
>
>
> +1 (Binding)
>
> --
>
> Kapil Arya
>
> Jie Yu
>
> Benjamin Mahler
>
>
> +1 (Non-binding)
>
> --
>
> Haosdent
>
> Greg Mann
>
> Zhitao Li
>
>
> +0
>
> -
>
> Yan Xu
>
>
> There were no  -1 votes.
>
>
> *NOTE: There were a couple known issues [MESOS-5911
> , MESOS-5913
> ] that couldn't be fixed
> in time for the 1.0. We plan to do a patch release to fix these ASAP.*
>
>
> Please find the release at:
>
> https://dist.apache.org/repos/dist/release/mesos/1.0.0
>
>
> It is recommended to use a mirror to download the release:
>
> http://www.apache.org/dyn/closer.cgi
>
>
> 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.0.0
>
>
> The mesos-1.0.0.jar has been released to:
>
> https://repository.apache.org
>
>
> The website (http://mesos.apache.org) will be updated shortly to reflect
> this release.
>
>
> Thanks,
>
> On Fri, Jul 22, 2016 at 10:40 PM, Vinod Kone  > wrote:
>
>> Hi all,
>>
>>
>> Please vote on releasing the following candidate as Apache Mesos 1.0.0.
>>
>> *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a
>> majority of at least 3 +1 PMC votes are cast.*
>>
>> 1.0.0 includes the following:
>>
>>
>> 
>>
>>   * Scheduler and Executor v1 HTTP APIs are now considered stable.
>>
>>
>>
>>
>>
>>   * [MESOS-4791] - **Experimental** support for v1 Master and Agent APIs.
>> These
>>
>> APIs let operators and services (monitoring, load balancers) send
>> HTTP
>>
>> requests to '/api/v1' endpoint on master or agent. See
>>
>>
>> `docs/operator-http-api.md` for details.
>>
>>
>>
>>
>>
>>   * [MESOS-4828] - **Experimental** support for a new `disk/xfs' isolator
>>
>>
>> has been added to isolate disk resources more efficiently. Please
>> refer to
>>
>> docs/mesos-containerizer.md for more details.
>>
>>
>>
>>
>>
>>   * [MESOS-4355] - **Experimental** support for Docker volume plugin. We
>> added a
>>
>> new isolator 'docker/volume' which allows users to use external
>> volumes in
>>
>> Mesos containerizer. Currently, the isolator interacts with the
>> Docker
>>
>> volume plugins using a tool called 'dvdcli'. By speaking the Docker
>> volume
>>
>> plugin API, most of the Docker volume plugins are supported.
>>
>>
>>
>>
>>
>>   * [MESOS-4641] - **Experimental** A new network isolator, the
>>
>>
>> `network/cni` isolator, has been introduced in the
>> `MesosContainerizer`. The
>>
>> `network/cni` isolator implements the Container Network Interface
>> (CNI)
>>
>> specification proposed by CoreOS.  With CNI the `network/cni`
>> isolator is
>>
>> able to allocate a network namespace to Mesos containers and attach
>> the
>>
>> container to different types of IP networks by invoking network
>> drivers
>>
>> called CNI plugins.
>>
>>
>>
>>
>>
>>   * [MESOS-2948, MESOS-5403] - The authorizer interface has been
>> refactored in
>>
>> order to decouple the ACLs definition language from the interface.
>>
>>
>> It additionally includes the option of retrieving `ObjectApprover`.
>> An
>>
>> `ObjectApprover` can be used to synchronously check authorizations
>> for a
>>
>> given object and is hence useful when authorizing a large number of
>> objects
>>
>> and/or large objects (which need to be copied using request based
>>
>>
>> authorization). NOTE: This is a **breaking change** for authorizer
>> modules.
>>
>>
>>
>>
>>   * [MESOS-5405] - The `subject` and `object` fields in
>> authorization::Request
>>
>> have been changed from required to optional. If either of these
>> fields is
>>
>> not set, the request should only be authorized if any subject/object
>> should
>>
>> be allowed.
>>
>>
>> NOTE: This is a semantic change for authorizer modules.
>>
>>
>>
>>
>>
>>   * [MESOS-4931, MESOS-5709, MESOS-5704] - Authorization based HTTP
>> endpoint
>>
>> filtering enables operators to restrict what part of the cluster
>> state a
>>
>> user is authorized to see.
>>
>>
>> Consider for example the `/state` master endpoint: an operator can
>> now
>>
>> authorize users to only see a subset of the running frameworks,
>> tasks, or
>>
>> Consider for example the `/state` master endpoint: an operator can
>> now
>>
>> authorize users to only see a subset of the running frameworks,
>> tasks, or
>>
>> executors. 

Re: [RESULT][VOTE] Release Apache Mesos 1.0.0 (rc4)

[Vinod Kone]

The 1.0 blog post is up: http://mesos.apache.org/blog/mesos-1-0-0-released/

Thank you all for making this possible!

@vinodkone

> On Jul 27, 2016, at 7:39 AM, Vinod Kone  wrote:
> 
> Hi all,
> 
> The vote for Mesos 1.0.0 (rc4) has passed with the following votes.
> 
> 
> 
> +1 (Binding)
> 
> --
> 
> Kapil Arya
> 
> Jie Yu
> 
> Benjamin Mahler
> 
> 
> 
> +1 (Non-binding)
> 
> --
> 
> Haosdent
> 
> Greg Mann
> 
> Zhitao Li
> 
> 
> 
> +0
> 
> -
> 
> Yan Xu
> 
> 
> 
> There were no  -1 votes.
> 
> 
> 
> NOTE: There were a couple known issues [MESOS-5911, MESOS-5913] that couldn't 
> be fixed in time for the 1.0. We plan to do a patch release to fix these ASAP.
> 
> 
> 
> Please find the release at:
> 
> https://dist.apache.org/repos/dist/release/mesos/1.0.0
> 
> 
> 
> It is recommended to use a mirror to download the release:
> 
> http://www.apache.org/dyn/closer.cgi
> 
> 
> 
> 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.0.0
> 
> 
> 
> The mesos-1.0.0.jar has been released to:
> 
> https://repository.apache.org
> 
> 
> 
> The website (http://mesos.apache.org) will be updated shortly to reflect this 
> release.
> 
> 
> 
> Thanks,
> 
> 
>> On Fri, Jul 22, 2016 at 10:40 PM, Vinod Kone  wrote:
>> Hi all,
>> 
>> 
>> 
>> Please vote on releasing the following candidate as Apache Mesos 1.0.0.
>> 
>> The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a majority 
>> of at least 3 +1 PMC votes are cast.
>> 
>> 
>> 1.0.0 includes the following:
>> 
>> 
>> 
>>   * Scheduler and Executor v1 HTTP APIs are now considered stable.   
>> 
>> 
>>  
>> 
>> 
>>   * [MESOS-4791] - **Experimental** support for v1 Master and Agent APIs. 
>> These  
>> 
>> APIs let operators and services (monitoring, load balancers) send HTTP   
>> 
>> 
>> requests to '/api/v1' endpoint on master or agent. See   
>> 
>> 
>> `docs/operator-http-api.md` for details. 
>> 
>> 
>>  
>> 
>> 
>>   * [MESOS-4828] - **Experimental** support for a new `disk/xfs' isolator
>> 
>> 
>> has been added to isolate disk resources more efficiently. Please refer 
>> to   
>> 
>> docs/mesos-containerizer.md for more details.
>>
>> 
>>  
>> 
>> 
>>   * [MESOS-4355] - **Experimental** support for Docker volume plugin. We 
>> added a 
>> 
>> new isolator 'docker/volume' which allows users to use external volumes 
>> in   
>> 
>> Mesos containerizer. Currently, the isolator interacts with the Docker   
>> 
>> 
>> volume plugins using a tool called 'dvdcli'. By speaking the Docker 
>> volume   
>> 
>> plugin API, most of the Docker volume plugins are supported. 
>> 
>> 
>>  
>> 
>> 
>>   * [MESOS-4641] - **Experimental** A new network isolator, the  
>> 
>> 
>> `network/cni` isolator, has been introduced in the `MesosContainerizer`. 
>> The 
>> 
>> `network/cni` isolator implements the Container Network Interface (CNI)  
>> 
>> 
>> specification proposed by CoreOS.  With CNI the `network/cni` isolator 
>> is
>> 
>> able to allocate a network namespace to Mesos containers and attach the  
>> 
>> 
>> container to different types of IP networks by invoking network drivers  
>> 
>> 
>> called CNI plugins.  
>>
>> 
>>  
>> 
>> 
>>   * [MESOS-2948, MESOS-5403] - The authorizer interface has been refactored 
>> in   
>> 
>> order to decouple the ACLs definition language from the interface.   
>> 
>> 
>> It additionally includes the option of retrieving `ObjectApprover`. An   
>> 
>> 
>> `ObjectApprover` can be used to synchronously check authorizations for a 
>> 
>> 
>> given object and is hence useful when authorizing a large number of 
>> objects  
>> 
>> and/or large objects (which need to be copied using request based
>> 
>> 
>> authorization). NOTE: This is a **breaking change** for authorizer 
>> modules.  
>> 
>>  
>> 
>> 
>>   * [MESOS-5405] - The `subject` and `object` fields in 
>> authorization::Request   
>> 
>> have been changed from required to optional. If either of these fields 
>> 

[RESULT][VOTE] Release Apache Mesos 1.0.0 (rc4)

[Vinod Kone]

Hi all,

The vote for Mesos 1.0.0 (rc4) has passed with the following votes.


+1 (Binding)

--

Kapil Arya

Jie Yu

Benjamin Mahler


+1 (Non-binding)

--

Haosdent

Greg Mann

Zhitao Li


+0

-

Yan Xu


There were no  -1 votes.


*NOTE: There were a couple known issues [MESOS-5911
, MESOS-5913
] that couldn't be fixed
in time for the 1.0. We plan to do a patch release to fix these ASAP.*


Please find the release at:

https://dist.apache.org/repos/dist/release/mesos/1.0.0


It is recommended to use a mirror to download the release:

http://www.apache.org/dyn/closer.cgi


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.0.0


The mesos-1.0.0.jar has been released to:

https://repository.apache.org


The website (http://mesos.apache.org) will be updated shortly to reflect
this release.


Thanks,

On Fri, Jul 22, 2016 at 10:40 PM, Vinod Kone  wrote:

> Hi all,
>
>
> Please vote on releasing the following candidate as Apache Mesos 1.0.0.
>
> *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a
> majority of at least 3 +1 PMC votes are cast.*
>
> 1.0.0 includes the following:
>
>
> 
>
>   * Scheduler and Executor v1 HTTP APIs are now considered stable.
>
>
>
>
>
>   * [MESOS-4791] - **Experimental** support for v1 Master and Agent APIs.
> These
>
> APIs let operators and services (monitoring, load balancers) send
> HTTP
>
> requests to '/api/v1' endpoint on master or agent. See
>
>
> `docs/operator-http-api.md` for details.
>
>
>
>
>
>   * [MESOS-4828] - **Experimental** support for a new `disk/xfs' isolator
>
>
> has been added to isolate disk resources more efficiently. Please
> refer to
>
> docs/mesos-containerizer.md for more details.
>
>
>
>
>
>   * [MESOS-4355] - **Experimental** support for Docker volume plugin. We
> added a
>
> new isolator 'docker/volume' which allows users to use external
> volumes in
>
> Mesos containerizer. Currently, the isolator interacts with the
> Docker
>
> volume plugins using a tool called 'dvdcli'. By speaking the Docker
> volume
>
> plugin API, most of the Docker volume plugins are supported.
>
>
>
>
>
>   * [MESOS-4641] - **Experimental** A new network isolator, the
>
>
> `network/cni` isolator, has been introduced in the
> `MesosContainerizer`. The
>
> `network/cni` isolator implements the Container Network Interface
> (CNI)
>
> specification proposed by CoreOS.  With CNI the `network/cni` isolator
> is
>
> able to allocate a network namespace to Mesos containers and attach
> the
>
> container to different types of IP networks by invoking network
> drivers
>
> called CNI plugins.
>
>
>
>
>
>   * [MESOS-2948, MESOS-5403] - The authorizer interface has been
> refactored in
>
> order to decouple the ACLs definition language from the interface.
>
>
> It additionally includes the option of retrieving `ObjectApprover`.
> An
>
> `ObjectApprover` can be used to synchronously check authorizations for
> a
>
> given object and is hence useful when authorizing a large number of
> objects
>
> and/or large objects (which need to be copied using request based
>
>
> authorization). NOTE: This is a **breaking change** for authorizer
> modules.
>
>
>
>
>   * [MESOS-5405] - The `subject` and `object` fields in
> authorization::Request
>
> have been changed from required to optional. If either of these fields
> is
>
> not set, the request should only be authorized if any subject/object
> should
>
> be allowed.
>
>
> NOTE: This is a semantic change for authorizer modules.
>
>
>
>
>
>   * [MESOS-4931, MESOS-5709, MESOS-5704] - Authorization based HTTP
> endpoint
>
> filtering enables operators to restrict what part of the cluster state
> a
>
> user is authorized to see.
>
>
> Consider for example the `/state` master endpoint: an operator can
> now
>
> authorize users to only see a subset of the running frameworks, tasks,
> or
>
> Consider for example the `/state` master endpoint: an operator can
> now
>
> authorize users to only see a subset of the running frameworks, tasks,
> or
>
> executors. The following endpoints support HTTP endpoint filtering:
>
>
> '/state', '/state-summary', '/tasks', '/frameworks','/weights',
>
>
> and '/roles'. Additonally the following v1 API calls support
> filtering:
>
> 'GET_ROLES','GET_WEIGHTS','GET_FRAMEWORKS', 'GET_STATE', and
> 'GET_TASKS'.
>
>
>
>
>   * [MESOS-4909] - Tasks can now specify a kill policy. They are
> best-effort,
>
> because machine failures or forcible terminations may occur.
> Currently, the
>
> only available kill policy is how long to