You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Gilbert Song <gi...@apache.org> on 2017/12/01 23:58:26 UTC

Mesos 1.5.0 Release

Folks,

It is time for Mesos 1.5.0 release. I am the release manager.

We plan to cut the rc1 in next couple weeks. Please start to wrap up
patches if you are contributing or shepherding any issue. If you expect any
particular JIRA for this new release, please set *Target Version* as "
*1.5.0"* and mark it as "*Blocker*" priority.

The dashboard for Mesos 1.5.0 will be posted in this thread soon.

Cheers,
Gilbert

Re: Persistent volume with ceph

Posted by Guang Ya Liu <gy...@gmail.com>.
My bad, I did not notice it is requesting for a Mesos solution.

Can you help check following docs to see if they can help?

1.
https://github.com/apache/mesos/blob/master/docs/isolators/docker-volume.md
2. https://github.com/codedellemc/dvdcli
3. https://github.com/thecodeteam/rexray#storage-provider-support

On Thu, Dec 28, 2017 at 11:45 AM, Guang Ya Liu <gy...@gmail.com> wrote:

> For your reference
>
> 1. https://github.com/kubernetes-incubator/external-
> storage/tree/master/ceph/rbd
> 2. https://crondev.com/kubernetes-persistent-storage-ceph/
>
> Hope this helps.
>
> On Sat, Dec 23, 2017 at 8:22 PM, Marc Roos <M....@f1-outsourcing.eu>
> wrote:
>
>>
>> Is there a recommended procedure, or has anyone experience with using
>> ceph storage as persistent volumes with a database?
>>
>> Eg. A mysql/mariadb/influxdb writing to a rbd image from a rbd ceph
>> pool?
>>
>>
>>
>>
>>
>

Re: Persistent volume with ceph

Posted by Guang Ya Liu <gy...@gmail.com>.
For your reference

1.
https://github.com/kubernetes-incubator/external-storage/tree/master/ceph/rbd
2. https://crondev.com/kubernetes-persistent-storage-ceph/

Hope this helps.

On Sat, Dec 23, 2017 at 8:22 PM, Marc Roos <M....@f1-outsourcing.eu> wrote:

>
> Is there a recommended procedure, or has anyone experience with using
> ceph storage as persistent volumes with a database?
>
> Eg. A mysql/mariadb/influxdb writing to a rbd image from a rbd ceph
> pool?
>
>
>
>
>

Local volume not getting any data

Posted by Marc Roos <M....@f1-outsourcing.eu>.
 
I am not getting what I am doing wrong here. 

Influx is writing the data at the correct location
[marc@m02 mesos]# ls -lart 
/var/lib/mesos/provisioner/containers/d481a7ad-e404-4d6e-baea-9c06a6f9f2
28/backends/copy/rootfses/fef9b89e-4be6-45df-be8f-fa367ea55648/influxdbd
ata/
total 0
drwxr-xr-x 22 root root 289 Dec 23 14:44 ..
drwxr-xr-x  4 root root  30 Dec 23 14:44 .
drwxr-xr-x  2 root root  21 Dec 23 14:44 meta
drwxr-xr-x  3 root root  23 Dec 23 14:44 data

But is should end up here not?
[marc@m02 mesos]# ls -lart 
/var/lib/mesos/volumes/roles/foo/influxdb#influxdbdata#5435256f-e7e7-11e
7-88f3-0a58c0a80001/
total 0
drwxr-xr-x 3 root root 72 Dec 23 14:43 ..
drwxr-xr-x 2 root root  6 Dec 23 14:43 .




{
  "id": "influxdb",
  "cmd": null,
  "cpus": 0.5,
  "mem": 128,
  "instances": 1,
  "acceptedResourceRoles": ["*"],
  "container": {
    "type": "MESOS",
    "docker": {
      "image": "influxdb",
      "credential": null,
      "forcePullImage": false
    },
    "volumes": [
      {
        "containerPath": "influxdbdata",
        "persistent": {
          "type": "root",
          "size": 100
          },
        "mode": "RW" 
      }
    ]
  },
  "env": {
    "INFLUXDB_META_DIR": "/influxdbdata/meta",
    "INFLUXDB_DATA_DIR": "/influxdbdata/data",
    "INFLUXDB_REPORTING_DISABLED": "true",
    "INFLUXDB_HTTP_AUTH_ENABLED": "true",
    "INFLUXDB_ADMIN_ENABLED": "true",
    "INFLUXDB_ADMIN_USER": "admin",
    "INFLUXDB_ADMIN_PASSWORD": "xxxxx" 
  },

    "healthChecks": [
    {
      "gracePeriodSeconds": 240,
      "intervalSeconds": 10,
      "timeoutSeconds": 10,
      "maxConsecutiveFailures": 10,
      "port": 8086,
      "path": "/ping",
      "protocol": "HTTP",
      "ignoreHttp1xx": false
    }
  ]
}





Persistent volume with ceph

Posted by Marc Roos <M....@f1-outsourcing.eu>.
 
Is there a recommended procedure, or has anyone experience with using 
ceph storage as persistent volumes with a database?

Eg. A mysql/mariadb/influxdb writing to a rbd image from a rbd ceph 
pool?





RE: Cannot enable the isolator volume/host_path

Posted by Marc Roos <M....@f1-outsourcing.eu>.
 

mesos-1.4.1-2.0.1.x86_64
marathon-1.4.9-1.0.668.el7.x86_64


-----Original Message-----
From: Jie Yu [mailto:yujie.jay@gmail.com] 
Sent: zaterdag 23 december 2017 1:12
To: user
Subject: Re: Cannot enable the isolator volume/host_path

What's your Mesos version?

On Fri, Dec 22, 2017 at 4:09 PM, Marc Roos <M....@f1-outsourcing.eu> 
wrote:




	Dec 23 01:04:33 m01 mesos-slave[10344]: E1223 01:04:33.213044 10344
	main.cpp:489] EXIT with status 1: Failed to create a containerizer:
	Could not create MesosContainerizer: Failed to create isolator
	'volume/host_path': Unknown or unsupported isolator
	
	/etc/mesos-slave/isolation
	filesystem/linux,docker/runtime,volume/image
	
	http://mesos.apache.org/documentation/latest/container-volume/ 
<http://mesos.apache.org/documentation/latest/container-volume/> 
	




Re: Cannot enable the isolator volume/host_path

Posted by Jie Yu <yu...@gmail.com>.
What's your Mesos version?

On Fri, Dec 22, 2017 at 4:09 PM, Marc Roos <M....@f1-outsourcing.eu> wrote:

>
>
> Dec 23 01:04:33 m01 mesos-slave[10344]: E1223 01:04:33.213044 10344
> main.cpp:489] EXIT with status 1: Failed to create a containerizer:
> Could not create MesosContainerizer: Failed to create isolator
> 'volume/host_path': Unknown or unsupported isolator
>
> /etc/mesos-slave/isolation
> filesystem/linux,docker/runtime,volume/image
>
> http://mesos.apache.org/documentation/latest/container-volume/
>

Cannot enable the isolator volume/host_path

Posted by Marc Roos <M....@f1-outsourcing.eu>.
 

Dec 23 01:04:33 m01 mesos-slave[10344]: E1223 01:04:33.213044 10344 
main.cpp:489] EXIT with status 1: Failed to create a containerizer: 
Could not create MesosContainerizer: Failed to create isolator 
'volume/host_path': Unknown or unsupported isolator

/etc/mesos-slave/isolation
filesystem/linux,docker/runtime,volume/image

http://mesos.apache.org/documentation/latest/container-volume/

Re: Mesos 1.5.0 Release

Posted by Jie Yu <yu...@gmail.com>.
Branched!

https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=shortlog;h=refs/heads/1.5.x

- JIe

On Fri, Dec 22, 2017 at 3:12 PM, Jie Yu <yu...@gmail.com> wrote:

> Hey folks,
>
> I did a cleanup on tickets that target for 1.5.0. Here are the remaining
> tickets:
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20MESOS%20AND%20status%20in%20(Open%2C%20%22In%
> 20Progress%22%2C%20Reviewable%2C%20Accepted)%20AND%20%
> 22Target%20Version%2Fs%22%20%3D%201.5.0
>
> Please let take the action to either re-target, or let me know that it has
> to go into 1.5.0.
>
> Given the current situation, I'll do the *branch off *today (1.5.x) and
> tag rc1 probably next week.
>
> *For Committers*: if you have patch that you want to land in 1.5.0,
> please also commit into the 1.5.x branch!
>
> Thanks,
> - Jie
>
> On Fri, Dec 22, 2017 at 3:14 AM, Alex Rukletsov <al...@mesosphere.com>
> wrote:
>
>> https://issues.apache.org/jira/browse/MESOS-8297 has just landed. Let's
>> include it in 1.5.0 as well.
>>
>> On Fri, Dec 22, 2017 at 4:35 AM, Jie Yu <yu...@gmail.com> wrote:
>>
>>> Yeah, I am doing a grooming right now.
>>>
>>> Sent from my iPhone
>>>
>>> > On Dec 21, 2017, at 7:25 PM, Benjamin Mahler <bm...@apache.org>
>>> wrote:
>>> >
>>> > Meng is working on https://issues.apache.org/jira/browse/MESOS-8352
>>> and we
>>> > should land it tonight if not tomorrow. I can cherry pick if it's after
>>> > your cut, and worst case it can go in 1.5.1.
>>> >
>>> > Have you guys gone over the unresolved items targeted for 1.5.0? I see
>>> a
>>> > lot of stuff, might be good to start adjusting / removing their target
>>> > versions to give folks a chance to respond on the ticket?
>>> >
>>> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20M
>>> ESOS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%
>>> 2C%20Reviewable%2C%20Accepted)%20AND%20%22Target%20Version%
>>> 2Fs%22%20%3D%201.5.0
>>> >
>>> > For example, https://issues.apache.org/jira/browse/MESOS-8337 looks
>>> pretty
>>> > bad to me (master crash).
>>> >
>>> >> On Thu, Dec 21, 2017 at 7:00 PM, Jie Yu <yu...@gmail.com> wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that
>>> needs to
>>> >> go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
>>> >> Thanks!
>>> >>
>>> >> - Jie
>>> >>
>>> >>> On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org>
>>> wrote:
>>> >>>
>>> >>> Folks,
>>> >>>
>>> >>> It is time for Mesos 1.5.0 release. I am the release manager.
>>> >>>
>>> >>> We plan to cut the rc1 in next couple weeks. Please start to wrap up
>>> >>> patches if you are contributing or shepherding any issue. If you
>>> expect
>>> >>> any
>>> >>> particular JIRA for this new release, please set *Target Version* as
>>> "
>>> >>> *1.5.0"* and mark it as "*Blocker*" priority.
>>> >>>
>>> >>> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
>>> >>>
>>> >>> Cheers,
>>> >>> Gilbert
>>> >>>
>>> >>
>>> >>
>>>
>>
>>
>

Re: Mesos 1.5.0 Release

Posted by Jie Yu <yu...@gmail.com>.
Branched!

https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=shortlog;h=refs/heads/1.5.x

- JIe

On Fri, Dec 22, 2017 at 3:12 PM, Jie Yu <yu...@gmail.com> wrote:

> Hey folks,
>
> I did a cleanup on tickets that target for 1.5.0. Here are the remaining
> tickets:
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20MESOS%20AND%20status%20in%20(Open%2C%20%22In%
> 20Progress%22%2C%20Reviewable%2C%20Accepted)%20AND%20%
> 22Target%20Version%2Fs%22%20%3D%201.5.0
>
> Please let take the action to either re-target, or let me know that it has
> to go into 1.5.0.
>
> Given the current situation, I'll do the *branch off *today (1.5.x) and
> tag rc1 probably next week.
>
> *For Committers*: if you have patch that you want to land in 1.5.0,
> please also commit into the 1.5.x branch!
>
> Thanks,
> - Jie
>
> On Fri, Dec 22, 2017 at 3:14 AM, Alex Rukletsov <al...@mesosphere.com>
> wrote:
>
>> https://issues.apache.org/jira/browse/MESOS-8297 has just landed. Let's
>> include it in 1.5.0 as well.
>>
>> On Fri, Dec 22, 2017 at 4:35 AM, Jie Yu <yu...@gmail.com> wrote:
>>
>>> Yeah, I am doing a grooming right now.
>>>
>>> Sent from my iPhone
>>>
>>> > On Dec 21, 2017, at 7:25 PM, Benjamin Mahler <bm...@apache.org>
>>> wrote:
>>> >
>>> > Meng is working on https://issues.apache.org/jira/browse/MESOS-8352
>>> and we
>>> > should land it tonight if not tomorrow. I can cherry pick if it's after
>>> > your cut, and worst case it can go in 1.5.1.
>>> >
>>> > Have you guys gone over the unresolved items targeted for 1.5.0? I see
>>> a
>>> > lot of stuff, might be good to start adjusting / removing their target
>>> > versions to give folks a chance to respond on the ticket?
>>> >
>>> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20M
>>> ESOS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%
>>> 2C%20Reviewable%2C%20Accepted)%20AND%20%22Target%20Version%
>>> 2Fs%22%20%3D%201.5.0
>>> >
>>> > For example, https://issues.apache.org/jira/browse/MESOS-8337 looks
>>> pretty
>>> > bad to me (master crash).
>>> >
>>> >> On Thu, Dec 21, 2017 at 7:00 PM, Jie Yu <yu...@gmail.com> wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that
>>> needs to
>>> >> go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
>>> >> Thanks!
>>> >>
>>> >> - Jie
>>> >>
>>> >>> On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org>
>>> wrote:
>>> >>>
>>> >>> Folks,
>>> >>>
>>> >>> It is time for Mesos 1.5.0 release. I am the release manager.
>>> >>>
>>> >>> We plan to cut the rc1 in next couple weeks. Please start to wrap up
>>> >>> patches if you are contributing or shepherding any issue. If you
>>> expect
>>> >>> any
>>> >>> particular JIRA for this new release, please set *Target Version* as
>>> "
>>> >>> *1.5.0"* and mark it as "*Blocker*" priority.
>>> >>>
>>> >>> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
>>> >>>
>>> >>> Cheers,
>>> >>> Gilbert
>>> >>>
>>> >>
>>> >>
>>>
>>
>>
>

Re: Mesos 1.5.0 Release

Posted by Jie Yu <yu...@gmail.com>.
Hey folks,

I did a cleanup on tickets that target for 1.5.0. Here are the remaining
tickets:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MESOS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reviewable%2C%20Accepted)%20AND%20%22Target%20Version%2Fs%22%20%3D%201.5.0

Please let take the action to either re-target, or let me know that it has
to go into 1.5.0.

Given the current situation, I'll do the *branch off *today (1.5.x) and tag
rc1 probably next week.

*For Committers*: if you have patch that you want to land in 1.5.0, please
also commit into the 1.5.x branch!

Thanks,
- Jie

On Fri, Dec 22, 2017 at 3:14 AM, Alex Rukletsov <al...@mesosphere.com> wrote:

> https://issues.apache.org/jira/browse/MESOS-8297 has just landed. Let's
> include it in 1.5.0 as well.
>
> On Fri, Dec 22, 2017 at 4:35 AM, Jie Yu <yu...@gmail.com> wrote:
>
>> Yeah, I am doing a grooming right now.
>>
>> Sent from my iPhone
>>
>> > On Dec 21, 2017, at 7:25 PM, Benjamin Mahler <bm...@apache.org>
>> wrote:
>> >
>> > Meng is working on https://issues.apache.org/jira/browse/MESOS-8352
>> and we
>> > should land it tonight if not tomorrow. I can cherry pick if it's after
>> > your cut, and worst case it can go in 1.5.1.
>> >
>> > Have you guys gone over the unresolved items targeted for 1.5.0? I see a
>> > lot of stuff, might be good to start adjusting / removing their target
>> > versions to give folks a chance to respond on the ticket?
>> >
>> > https://issues.apache.org/jira/issues/?jql=project%20%3D%
>> 20MESOS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%
>> 22%2C%20Reviewable%2C%20Accepted)%20AND%20%22Target%
>> 20Version%2Fs%22%20%3D%201.5.0
>> >
>> > For example, https://issues.apache.org/jira/browse/MESOS-8337 looks
>> pretty
>> > bad to me (master crash).
>> >
>> >> On Thu, Dec 21, 2017 at 7:00 PM, Jie Yu <yu...@gmail.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that
>> needs to
>> >> go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
>> >> Thanks!
>> >>
>> >> - Jie
>> >>
>> >>> On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org>
>> wrote:
>> >>>
>> >>> Folks,
>> >>>
>> >>> It is time for Mesos 1.5.0 release. I am the release manager.
>> >>>
>> >>> We plan to cut the rc1 in next couple weeks. Please start to wrap up
>> >>> patches if you are contributing or shepherding any issue. If you
>> expect
>> >>> any
>> >>> particular JIRA for this new release, please set *Target Version* as "
>> >>> *1.5.0"* and mark it as "*Blocker*" priority.
>> >>>
>> >>> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
>> >>>
>> >>> Cheers,
>> >>> Gilbert
>> >>>
>> >>
>> >>
>>
>
>

Re: Mesos 1.5.0 Release

Posted by Jie Yu <yu...@gmail.com>.
Hey folks,

I did a cleanup on tickets that target for 1.5.0. Here are the remaining
tickets:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MESOS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reviewable%2C%20Accepted)%20AND%20%22Target%20Version%2Fs%22%20%3D%201.5.0

Please let take the action to either re-target, or let me know that it has
to go into 1.5.0.

Given the current situation, I'll do the *branch off *today (1.5.x) and tag
rc1 probably next week.

*For Committers*: if you have patch that you want to land in 1.5.0, please
also commit into the 1.5.x branch!

Thanks,
- Jie

On Fri, Dec 22, 2017 at 3:14 AM, Alex Rukletsov <al...@mesosphere.com> wrote:

> https://issues.apache.org/jira/browse/MESOS-8297 has just landed. Let's
> include it in 1.5.0 as well.
>
> On Fri, Dec 22, 2017 at 4:35 AM, Jie Yu <yu...@gmail.com> wrote:
>
>> Yeah, I am doing a grooming right now.
>>
>> Sent from my iPhone
>>
>> > On Dec 21, 2017, at 7:25 PM, Benjamin Mahler <bm...@apache.org>
>> wrote:
>> >
>> > Meng is working on https://issues.apache.org/jira/browse/MESOS-8352
>> and we
>> > should land it tonight if not tomorrow. I can cherry pick if it's after
>> > your cut, and worst case it can go in 1.5.1.
>> >
>> > Have you guys gone over the unresolved items targeted for 1.5.0? I see a
>> > lot of stuff, might be good to start adjusting / removing their target
>> > versions to give folks a chance to respond on the ticket?
>> >
>> > https://issues.apache.org/jira/issues/?jql=project%20%3D%
>> 20MESOS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%
>> 22%2C%20Reviewable%2C%20Accepted)%20AND%20%22Target%
>> 20Version%2Fs%22%20%3D%201.5.0
>> >
>> > For example, https://issues.apache.org/jira/browse/MESOS-8337 looks
>> pretty
>> > bad to me (master crash).
>> >
>> >> On Thu, Dec 21, 2017 at 7:00 PM, Jie Yu <yu...@gmail.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that
>> needs to
>> >> go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
>> >> Thanks!
>> >>
>> >> - Jie
>> >>
>> >>> On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org>
>> wrote:
>> >>>
>> >>> Folks,
>> >>>
>> >>> It is time for Mesos 1.5.0 release. I am the release manager.
>> >>>
>> >>> We plan to cut the rc1 in next couple weeks. Please start to wrap up
>> >>> patches if you are contributing or shepherding any issue. If you
>> expect
>> >>> any
>> >>> particular JIRA for this new release, please set *Target Version* as "
>> >>> *1.5.0"* and mark it as "*Blocker*" priority.
>> >>>
>> >>> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
>> >>>
>> >>> Cheers,
>> >>> Gilbert
>> >>>
>> >>
>> >>
>>
>
>

Re: Mesos 1.5.0 Release

Posted by Alex Rukletsov <al...@mesosphere.com>.
https://issues.apache.org/jira/browse/MESOS-8297 has just landed. Let's
include it in 1.5.0 as well.

On Fri, Dec 22, 2017 at 4:35 AM, Jie Yu <yu...@gmail.com> wrote:

> Yeah, I am doing a grooming right now.
>
> Sent from my iPhone
>
> > On Dec 21, 2017, at 7:25 PM, Benjamin Mahler <bm...@apache.org> wrote:
> >
> > Meng is working on https://issues.apache.org/jira/browse/MESOS-8352 and
> we
> > should land it tonight if not tomorrow. I can cherry pick if it's after
> > your cut, and worst case it can go in 1.5.1.
> >
> > Have you guys gone over the unresolved items targeted for 1.5.0? I see a
> > lot of stuff, might be good to start adjusting / removing their target
> > versions to give folks a chance to respond on the ticket?
> >
> > https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20MESOS%20AND%20status%20in%20(Open%2C%20%22In%
> 20Progress%22%2C%20Reviewable%2C%20Accepted)%20AND%20%
> 22Target%20Version%2Fs%22%20%3D%201.5.0
> >
> > For example, https://issues.apache.org/jira/browse/MESOS-8337 looks
> pretty
> > bad to me (master crash).
> >
> >> On Thu, Dec 21, 2017 at 7:00 PM, Jie Yu <yu...@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that needs
> to
> >> go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
> >> Thanks!
> >>
> >> - Jie
> >>
> >>> On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org>
> wrote:
> >>>
> >>> Folks,
> >>>
> >>> It is time for Mesos 1.5.0 release. I am the release manager.
> >>>
> >>> We plan to cut the rc1 in next couple weeks. Please start to wrap up
> >>> patches if you are contributing or shepherding any issue. If you expect
> >>> any
> >>> particular JIRA for this new release, please set *Target Version* as "
> >>> *1.5.0"* and mark it as "*Blocker*" priority.
> >>>
> >>> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
> >>>
> >>> Cheers,
> >>> Gilbert
> >>>
> >>
> >>
>

Re: Mesos 1.5.0 Release

Posted by Alex Rukletsov <al...@mesosphere.com>.
https://issues.apache.org/jira/browse/MESOS-8297 has just landed. Let's
include it in 1.5.0 as well.

On Fri, Dec 22, 2017 at 4:35 AM, Jie Yu <yu...@gmail.com> wrote:

> Yeah, I am doing a grooming right now.
>
> Sent from my iPhone
>
> > On Dec 21, 2017, at 7:25 PM, Benjamin Mahler <bm...@apache.org> wrote:
> >
> > Meng is working on https://issues.apache.org/jira/browse/MESOS-8352 and
> we
> > should land it tonight if not tomorrow. I can cherry pick if it's after
> > your cut, and worst case it can go in 1.5.1.
> >
> > Have you guys gone over the unresolved items targeted for 1.5.0? I see a
> > lot of stuff, might be good to start adjusting / removing their target
> > versions to give folks a chance to respond on the ticket?
> >
> > https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20MESOS%20AND%20status%20in%20(Open%2C%20%22In%
> 20Progress%22%2C%20Reviewable%2C%20Accepted)%20AND%20%
> 22Target%20Version%2Fs%22%20%3D%201.5.0
> >
> > For example, https://issues.apache.org/jira/browse/MESOS-8337 looks
> pretty
> > bad to me (master crash).
> >
> >> On Thu, Dec 21, 2017 at 7:00 PM, Jie Yu <yu...@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that needs
> to
> >> go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
> >> Thanks!
> >>
> >> - Jie
> >>
> >>> On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org>
> wrote:
> >>>
> >>> Folks,
> >>>
> >>> It is time for Mesos 1.5.0 release. I am the release manager.
> >>>
> >>> We plan to cut the rc1 in next couple weeks. Please start to wrap up
> >>> patches if you are contributing or shepherding any issue. If you expect
> >>> any
> >>> particular JIRA for this new release, please set *Target Version* as "
> >>> *1.5.0"* and mark it as "*Blocker*" priority.
> >>>
> >>> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
> >>>
> >>> Cheers,
> >>> Gilbert
> >>>
> >>
> >>
>

Re: Mesos 1.5.0 Release

Posted by Jie Yu <yu...@gmail.com>.
Yeah, I am doing a grooming right now.

Sent from my iPhone

> On Dec 21, 2017, at 7:25 PM, Benjamin Mahler <bm...@apache.org> wrote:
> 
> Meng is working on https://issues.apache.org/jira/browse/MESOS-8352 and we
> should land it tonight if not tomorrow. I can cherry pick if it's after
> your cut, and worst case it can go in 1.5.1.
> 
> Have you guys gone over the unresolved items targeted for 1.5.0? I see a
> lot of stuff, might be good to start adjusting / removing their target
> versions to give folks a chance to respond on the ticket?
> 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MESOS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reviewable%2C%20Accepted)%20AND%20%22Target%20Version%2Fs%22%20%3D%201.5.0
> 
> For example, https://issues.apache.org/jira/browse/MESOS-8337 looks pretty
> bad to me (master crash).
> 
>> On Thu, Dec 21, 2017 at 7:00 PM, Jie Yu <yu...@gmail.com> wrote:
>> 
>> Hi,
>> 
>> We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that needs to
>> go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
>> Thanks!
>> 
>> - Jie
>> 
>>> On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org> wrote:
>>> 
>>> Folks,
>>> 
>>> It is time for Mesos 1.5.0 release. I am the release manager.
>>> 
>>> We plan to cut the rc1 in next couple weeks. Please start to wrap up
>>> patches if you are contributing or shepherding any issue. If you expect
>>> any
>>> particular JIRA for this new release, please set *Target Version* as "
>>> *1.5.0"* and mark it as "*Blocker*" priority.
>>> 
>>> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
>>> 
>>> Cheers,
>>> Gilbert
>>> 
>> 
>> 

Re: Mesos 1.5.0 Release

Posted by Jie Yu <yu...@gmail.com>.
Yeah, I am doing a grooming right now.

Sent from my iPhone

> On Dec 21, 2017, at 7:25 PM, Benjamin Mahler <bm...@apache.org> wrote:
> 
> Meng is working on https://issues.apache.org/jira/browse/MESOS-8352 and we
> should land it tonight if not tomorrow. I can cherry pick if it's after
> your cut, and worst case it can go in 1.5.1.
> 
> Have you guys gone over the unresolved items targeted for 1.5.0? I see a
> lot of stuff, might be good to start adjusting / removing their target
> versions to give folks a chance to respond on the ticket?
> 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MESOS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reviewable%2C%20Accepted)%20AND%20%22Target%20Version%2Fs%22%20%3D%201.5.0
> 
> For example, https://issues.apache.org/jira/browse/MESOS-8337 looks pretty
> bad to me (master crash).
> 
>> On Thu, Dec 21, 2017 at 7:00 PM, Jie Yu <yu...@gmail.com> wrote:
>> 
>> Hi,
>> 
>> We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that needs to
>> go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
>> Thanks!
>> 
>> - Jie
>> 
>>> On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org> wrote:
>>> 
>>> Folks,
>>> 
>>> It is time for Mesos 1.5.0 release. I am the release manager.
>>> 
>>> We plan to cut the rc1 in next couple weeks. Please start to wrap up
>>> patches if you are contributing or shepherding any issue. If you expect
>>> any
>>> particular JIRA for this new release, please set *Target Version* as "
>>> *1.5.0"* and mark it as "*Blocker*" priority.
>>> 
>>> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
>>> 
>>> Cheers,
>>> Gilbert
>>> 
>> 
>> 

Re: Mesos 1.5.0 Release

Posted by Benjamin Mahler <bm...@apache.org>.
Meng is working on https://issues.apache.org/jira/browse/MESOS-8352 and we
should land it tonight if not tomorrow. I can cherry pick if it's after
your cut, and worst case it can go in 1.5.1.

Have you guys gone over the unresolved items targeted for 1.5.0? I see a
lot of stuff, might be good to start adjusting / removing their target
versions to give folks a chance to respond on the ticket?

https://issues.apache.org/jira/issues/?jql=project%20%3D%20MESOS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reviewable%2C%20Accepted)%20AND%20%22Target%20Version%2Fs%22%20%3D%201.5.0

For example, https://issues.apache.org/jira/browse/MESOS-8337 looks pretty
bad to me (master crash).

On Thu, Dec 21, 2017 at 7:00 PM, Jie Yu <yu...@gmail.com> wrote:

> Hi,
>
> We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that needs to
> go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
> Thanks!
>
> - Jie
>
> On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org> wrote:
>
>> Folks,
>>
>> It is time for Mesos 1.5.0 release. I am the release manager.
>>
>> We plan to cut the rc1 in next couple weeks. Please start to wrap up
>> patches if you are contributing or shepherding any issue. If you expect
>> any
>> particular JIRA for this new release, please set *Target Version* as "
>> *1.5.0"* and mark it as "*Blocker*" priority.
>>
>> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
>>
>> Cheers,
>> Gilbert
>>
>
>

Re: Mesos 1.5.0 Release

Posted by Benjamin Mahler <bm...@apache.org>.
Meng is working on https://issues.apache.org/jira/browse/MESOS-8352 and we
should land it tonight if not tomorrow. I can cherry pick if it's after
your cut, and worst case it can go in 1.5.1.

Have you guys gone over the unresolved items targeted for 1.5.0? I see a
lot of stuff, might be good to start adjusting / removing their target
versions to give folks a chance to respond on the ticket?

https://issues.apache.org/jira/issues/?jql=project%20%3D%20MESOS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reviewable%2C%20Accepted)%20AND%20%22Target%20Version%2Fs%22%20%3D%201.5.0

For example, https://issues.apache.org/jira/browse/MESOS-8337 looks pretty
bad to me (master crash).

On Thu, Dec 21, 2017 at 7:00 PM, Jie Yu <yu...@gmail.com> wrote:

> Hi,
>
> We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that needs to
> go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
> Thanks!
>
> - Jie
>
> On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org> wrote:
>
>> Folks,
>>
>> It is time for Mesos 1.5.0 release. I am the release manager.
>>
>> We plan to cut the rc1 in next couple weeks. Please start to wrap up
>> patches if you are contributing or shepherding any issue. If you expect
>> any
>> particular JIRA for this new release, please set *Target Version* as "
>> *1.5.0"* and mark it as "*Blocker*" priority.
>>
>> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
>>
>> Cheers,
>> Gilbert
>>
>
>

Re: Mesos 1.5.0 Release

Posted by Jie Yu <yu...@gmail.com>.
Hi,

We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that needs to
go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
Thanks!

- Jie

On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org> wrote:

> Folks,
>
> It is time for Mesos 1.5.0 release. I am the release manager.
>
> We plan to cut the rc1 in next couple weeks. Please start to wrap up
> patches if you are contributing or shepherding any issue. If you expect any
> particular JIRA for this new release, please set *Target Version* as "
> *1.5.0"* and mark it as "*Blocker*" priority.
>
> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
>
> Cheers,
> Gilbert
>

Re: Mesos 1.5.0 Release

Posted by Jie Yu <yu...@gmail.com>.
Hi,

We're about to cut 1.5.0-rc1 tomorrow. If you have any thing that needs to
go into 1.5.0 that hasn't landed, please let me or Gilbert know asap.
Thanks!

- Jie

On Fri, Dec 1, 2017 at 3:58 PM, Gilbert Song <gi...@apache.org> wrote:

> Folks,
>
> It is time for Mesos 1.5.0 release. I am the release manager.
>
> We plan to cut the rc1 in next couple weeks. Please start to wrap up
> patches if you are contributing or shepherding any issue. If you expect any
> particular JIRA for this new release, please set *Target Version* as "
> *1.5.0"* and mark it as "*Blocker*" priority.
>
> The dashboard for Mesos 1.5.0 will be posted in this thread soon.
>
> Cheers,
> Gilbert
>