Re: Looking for Contributitors: Apache Flink meets Apache Mesos and DC/OS

[Sundeep.Kumar3]

Please count me in .

Envoyé de mon iPhone

Le 22 juin 2017 à 06:27, Jörg Schad 
> a écrit :

The only required skill is interest in that package :).

There are many different tasks including development, testing, building docker 
images, documentation 

We will discuss details in during the meeting.

Joerg

On Wed, Jun 21, 2017 at 7:33 PM, 
> wrote:
Hi,
Greetings …

What are the skill sets required for contributing towards the Flink Framework.

Regards,
Sundeep Kumar

From: Jörg Schad [mailto:jo...@mesosphere.io]
Sent: Wednesday, June 21, 2017 4:26 PM
To: OSS Team >
Cc: dev >; user 
>; users 
>; Till Rohrmann 
>
Subject: Looking for Contributitors: Apache Flink meets Apache Mesos and DC/OS

Hi,
we are actively looking for contributors (and anyone interested) for the
Flink DC/OS package, as well as the Mesos Flink framework.

We will have a first meeting to explain the current package and outline/develop 
a potential roadmap in the next virtual DC/OS office hours: 
https://www.http://meetup.com/DC-OS-Online-Meetup/events/240919616/.

If you cannot make it to this virtual event, feel free to reach out via the 
#flink channel in the  DC/OS community slack 
(chat.dcos.io).

Looking forwards to many cool features around Flink and Mesos/ DC/OS,
Jörg and Till
This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information. 
If you are not the intended recipient(s), please reply to the sender and 
destroy all copies of the original message. Any unauthorized review, use, 
disclosure, dissemination, forwarding, printing or copying of this email, 
and/or any action taken in reliance on the contents of this e-mail is strictly 
prohibited and may be unlawful. Where permitted by applicable law, this e-mail 
and other e-mail communications sent to and from Cognizant e-mail addresses may 
be monitored.

--
You received this message because you are subscribed to the Google Groups "OSS 
Team" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
oss-team+unsubscr...@mesosphere.io.
To post to this group, send email to 
oss-t...@mesosphere.io.
To view this discussion on the web visit 
https://groups.google.com/a/mesosphere.io/d/msgid/oss-team/175267E2B470D14D85BF4C2FBAC4022738AB5088%40CTSINCHNSXMBV.http://cts.com.

This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information. 
If you are not the intended recipient(s), please reply to the sender and 
destroy all copies of the original message. Any unauthorized review, use, 
disclosure, dissemination, forwarding, printing or copying of this email, 
and/or any action taken in reliance on the contents of this e-mail is strictly 
prohibited and may be unlawful. Where permitted by applicable law, this e-mail 
and other e-mail communications sent to and from Cognizant e-mail addresses may 
be monitored.

Re: Work group on Community

[Vinod Kone]

Can we use http://doodle.com/ to arrive at consensus regarding time slot?

@vinodkone

> On Jun 22, 2017, at 8:07 AM, Judith Malnick  wrote:
> 
> Hi everyone, 
> 
> Thanks for the interest! I know many of you are in Asia for MesosCon, so I'm 
> just going to propose a few times (Pacific time) and see if anything works. 
> Monday, June 26th at 5 pm
> Wednesday, June 28th at 10 am
> Thursday, July 6th at 8 am
> Wednesday, July 19th at 10 am
> Tell me what you think about these, and if none of them work we can try some 
> others. 
> 
> All the best! 
> Judith 
> 
> 
>> On Wed, Jun 21, 2017 at 2:47 AM, Jörg Schad  wrote:
>> Very excited and happy to join!
>> 
>>> On Sat, Jun 17, 2017 at 1:38 AM, James Peach  wrote:
>>> 
>>> > On Jun 15, 2017, at 10:57 AM, Vinod Kone  wrote:
>>> >
>>> > Hi folks,
>>> >
>>> > Seeing that our first official containerizer WG is off to a good start, we
>>> > want to use that momentum to start new WGs.
>>> >
>>> > I'm proposing that we start a new work group on community. The mission of
>>> > this work group would be to figure out ways to grow the size of our
>>> > community and improve the experience of community members (users, devs,
>>> > contributors, committers etc).
>>> >
>>> > In the first meeting, we can nail down what the charter of this work group
>>> > should be etc. My initial ideas for the topics/components this work group
>>> > could cover
>>> >
>>> > --> Releases
>>> > --> Roadmap
>>> > --> Reviews
>>> > --> JIRA
>>> > --> CI
>>> >
>>> > Over time, I'm hoping that new specific work groups will sprung up that 
>>> > can
>>> > own some of these topics.
>>> >
>>> > If you are interested in joining this work group, please reply to this
>>> > thread and I'll add you to the invite.
>>> 
>>> I'm interested, but unlikely to have much bandwidth to contribute anything 
>>> substantial. One suggestion I have is that a Mesos Weekly news would be 
>>> pretty great. There is a lot of activity on reviewboard, slack and in 
>>> design documents and collecting that in a regular newsletter would give 
>>> that activity a lot more visibility.
>>> 
>>> J
>> 
> 
> 
> 
> -- 
> Judith Malnick
> DC/OS Community Manager
> 310-709-1517

Re: Looking for Contributitors: Apache Flink meets Apache Mesos and DC/OS

[Jörg Schad]

The only required skill is interest in that package :).

There are many different tasks including development, testing, building
docker images, documentation 

We will discuss details in during the meeting.

Joerg

On Wed, Jun 21, 2017 at 7:33 PM,  wrote:

> Hi,
>
> Greetings …
>
>
>
> What are the skill sets required for contributing towards the Flink
> Framework.
>
>
>
> Regards,
>
> Sundeep Kumar
>
>
>
> *From:* Jörg Schad [mailto:jo...@mesosphere.io]
> *Sent:* Wednesday, June 21, 2017 4:26 PM
> *To:* OSS Team 
> *Cc:* dev ; user ; users <
> us...@dcos.io>; Till Rohrmann 
> *Subject:* Looking for Contributitors: Apache Flink meets Apache Mesos
> and DC/OS
>
>
>
> Hi,
>
> we are actively looking for contributors (and anyone interested) for the
>
> Flink DC/OS package, as well as the Mesos Flink framework.
>
>
>
> We will have a first meeting to explain the current package and
> outline/develop a potential roadmap in the next virtual DC/OS office hours:
> https://www.meetup.com/DC-OS-Online-Meetup/events/240919616/.
>
>
>
> If you cannot make it to this virtual event, feel free to reach out via
> the #flink channel in the  DC/OS community slack (chat.dcos.io).
>
>
>
> Looking forwards to many cool features around Flink and Mesos/ DC/OS,
>
> Jörg and Till
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information. If you are not the intended recipient(s), please reply to the
> sender and destroy all copies of the original message. Any unauthorized
> review, use, disclosure, dissemination, forwarding, printing or copying of
> this email, and/or any action taken in reliance on the contents of this
> e-mail is strictly prohibited and may be unlawful. Where permitted by
> applicable law, this e-mail and other e-mail communications sent to and
> from Cognizant e-mail addresses may be monitored.
>
> --
> You received this message because you are subscribed to the Google Groups
> "OSS Team" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to oss-team+unsubscr...@mesosphere.io.
> To post to this group, send email to oss-t...@mesosphere.io.
> To view this discussion on the web visit https://groups.google.com/a/
> mesosphere.io/d/msgid/oss-team/175267E2B470D14D85BF4C2FBAC402
> 2738AB5088%40CTSINCHNSXMBV.cts.com
> 
> .
>

Re: Work group on Community

[Judith Malnick]

Hi everyone,

Thanks for the interest! I know many of you are in Asia for MesosCon, so
I'm just going to propose a few times (Pacific time) and see if anything
works.

   - Monday, June 26th at 5 pm
   - Wednesday, June 28th at 10 am
   - Thursday, July 6th at 8 am
   - Wednesday, July 19th at 10 am

Tell me what you think about these, and if none of them work we can try
some others.

All the best!
Judith


On Wed, Jun 21, 2017 at 2:47 AM, Jörg Schad  wrote:

> Very excited and happy to join!
>
> On Sat, Jun 17, 2017 at 1:38 AM, James Peach  wrote:
>
>>
>> > On Jun 15, 2017, at 10:57 AM, Vinod Kone  wrote:
>> >
>> > Hi folks,
>> >
>> > Seeing that our first official containerizer WG is off to a good start,
>> we
>> > want to use that momentum to start new WGs.
>> >
>> > I'm proposing that we start a new work group on community. The mission
>> of
>> > this work group would be to figure out ways to grow the size of our
>> > community and improve the experience of community members (users, devs,
>> > contributors, committers etc).
>> >
>> > In the first meeting, we can nail down what the charter of this work
>> group
>> > should be etc. My initial ideas for the topics/components this work
>> group
>> > could cover
>> >
>> > --> Releases
>> > --> Roadmap
>> > --> Reviews
>> > --> JIRA
>> > --> CI
>> >
>> > Over time, I'm hoping that new specific work groups will sprung up that
>> can
>> > own some of these topics.
>> >
>> > If you are interested in joining this work group, please reply to this
>> > thread and I'll add you to the invite.
>>
>> I'm interested, but unlikely to have much bandwidth to contribute
>> anything substantial. One suggestion I have is that a Mesos Weekly news
>> would be pretty great. There is a lot of activity on reviewboard, slack and
>> in design documents and collecting that in a regular newsletter would give
>> that activity a lot more visibility.
>>
>> J
>
>
>


-- 
Judith Malnick
DC/OS Community Manager
310-709-1517 <(310)%20709-1517>

Re: RFC: Partition Awareness

[Megha Sharma]

Thank you all for the feedback.
To summarize, not killing tasks for non-Partition Aware frameworks will make 
the schedulers see a higher volume of non terminal updates for tasks for which 
they have already received a TASK_LOST but nothing new that they are not seeing 
today. So, this shouldn’t be a breaking change for frameworks and this will 
make the partition awareness logic simpler. I will update MESOS-7215 
 with the details once the 
design is ready.

Thanks
Megha Sharma

On Jun 1, 2017, at 2:56 PM, Vinod Kone  wrote:

On Thu, Jun 1, 2017 at 2:22 PM, Benjamin Mahler  wrote:

If I understood correctly, the proposal is to not kill the tasks for
non-partition aware frameworks? That seems like a pretty big change for
frameworks that are not partition aware and expect the old killing
semantics.


Adding to what Neil said, I think most (if not all) non-PA frameworks
would've already rescheduled the task after seeing a TASK_LOST. The
difference is that previously such tasks can come back to TASK_RUNNING iff
master fails over and non-strict registry (default) is used. Now, we are
saying tasks can come back to TASK_RUNNING irrespective of master fail
over. The assumption/hope is that this shouldn't break existing frameworks
in a catastrophic way.

> On Jun 1, 2017, at 2:30 PM, Neil Conway  wrote:
> 
> Hi Ben,
> 
> The argument for changing the semantics is that correct frameworks
> should _always_ have accounted for the possibility that TASK_LOST
> tasks would go back to running (due to the non-strict registry
> semantics). The proposed change would just increase the probability of
> this behavior occurring. From a certain POV, this change would
> actually make it easier to write correct frameworks because the
> TASK_LOST scenario will be less of a corner case :)
> 
> Implementing the task-killing behavior is a bit tricky, because the
> task might continue to run on the agent for a considerable period of
> time. During that time, we can either:
> 
> (a) omit the being-killed task from the master's memory (current
> behavior). That means that any resources used by the task appear to be
> unused, so there might be a concurrent task launch that attempts to
> use them and fails.
> 
> (b) track the being-killed task in the master's memory. This ensures
> the task's resources are not re-offered until the task is actually
> terminated. The concern here is that this "being-killed" task is in a
> weird state -- what task status should it have? When it finally dies,
> we don't want to report a terminal status update back to frameworks
> (for backward compatibility).
> 
> Neither of those approaches seemed ideal, hence we are wondering
> whether we really need to implement this backward compatibility
> behavior in the first place.
> 
> Neil
> 
> On Thu, Jun 1, 2017 at 2:22 PM, Benjamin Mahler  wrote:
>> If I understood correctly, the proposal is to not kill the tasks for
>> non-partition aware frameworks? That seems like a pretty big change for
>> frameworks that are not partition aware and expect the old killing
>> semantics.
>> 
>> It seems like we should just directly fix the issue, do you have a sense of
>> what the difficulty is there? Is it the re-use of the existing framework
>> shutdown message to kill the tasks that makes this problematic?
>> 
>> On Fri, May 26, 2017 at 3:19 PM, Megha Sharma  wrote:
>>> 
>>> Hi All,
>>> 
>>> We are working on fixing a potential issue MESOS-7215 with partition
>>> awareness which happens when an unreachable agent, with tasks for
>>> non-Partition Aware frameworks, attempts to re-register with the master.
>>> Before the support for partition-aware frameworks, which was introduced in
>>> Mesos 1.1.0 MESOS-5344,  if an agent partitioned from the master attempted
>>> to re-register, then it will be shut down and all the tasks on the agent
>>> would be terminated. With this feature, the partitioned agents were no
>>> longer shut down by the master when they re-registered but to keep the old
>>> behavior the tasks on these agents were still shutdown if the corresponding
>>> framework didn’t opt-in to partition awareness.
>>> 
>>> One of the possible solutions to address the issue mentioned in MESOS-7215
>>> is to change master’s behavior to not kill the tasks for non-Partition aware
>>> frameworks when an unreachable agent re-registers with the master. When an
>>> agent goes unreachable i.e. fails the masters health check ping for
>>> max_agent_ping_timeouts then the master sends TASK_LOST status updates for
>>> all the tasks on this agent which have been launched by non-Partition Aware
>>> frameworks. So, if such tasks are no longer killed by the master then upon
>>> agent re-registration the frameworks will see a non-terminal status updates
>>> for tasks for which they already received a TASK_LOST.
>>> This change will 

Re: Looking for Contributitors: Apache Flink meets Apache Mesos and DC/OS

[Stavros Kontopoulos]

Will be there as I have already started working on that.

best,
Stavros

On Wed, Jun 21, 2017 at 2:33 PM,  wrote:

> Hi,
>
> Greetings …
>
>
>
> What are the skill sets required for contributing towards the Flink
> Framework.
>
>
>
> Regards,
>
> Sundeep Kumar
>
>
>
> *From:* Jörg Schad [mailto:jo...@mesosphere.io]
> *Sent:* Wednesday, June 21, 2017 4:26 PM
> *To:* OSS Team 
> *Cc:* dev ; user ; users <
> us...@dcos.io>; Till Rohrmann 
> *Subject:* Looking for Contributitors: Apache Flink meets Apache Mesos
> and DC/OS
>
>
>
> Hi,
>
> we are actively looking for contributors (and anyone interested) for the
>
> Flink DC/OS package, as well as the Mesos Flink framework.
>
>
>
> We will have a first meeting to explain the current package and
> outline/develop a potential roadmap in the next virtual DC/OS office hours:
> https://www.meetup.com/DC-OS-Online-Meetup/events/240919616/.
>
>
>
> If you cannot make it to this virtual event, feel free to reach out via
> the #flink channel in the  DC/OS community slack (chat.dcos.io).
>
>
>
> Looking forwards to many cool features around Flink and Mesos/ DC/OS,
>
> Jörg and Till
> This e-mail and any files transmitted with it are for the sole use of the
> intended recipient(s) and may contain confidential and privileged
> information. If you are not the intended recipient(s), please reply to the
> sender and destroy all copies of the original message. Any unauthorized
> review, use, disclosure, dissemination, forwarding, printing or copying of
> this email, and/or any action taken in reliance on the contents of this
> e-mail is strictly prohibited and may be unlawful. Where permitted by
> applicable law, this e-mail and other e-mail communications sent to and
> from Cognizant e-mail addresses may be monitored.
>

RE: Looking for Contributitors: Apache Flink meets Apache Mesos and DC/OS

[Sundeep.Kumar3]

Hi,
Greetings …

What are the skill sets required for contributing towards the Flink Framework.

Regards,
Sundeep Kumar

From: Jörg Schad [mailto:jo...@mesosphere.io]
Sent: Wednesday, June 21, 2017 4:26 PM
To: OSS Team 
Cc: dev ; user ; users 
; Till Rohrmann 
Subject: Looking for Contributitors: Apache Flink meets Apache Mesos and DC/OS

Hi,
we are actively looking for contributors (and anyone interested) for the
Flink DC/OS package, as well as the Mesos Flink framework.

We will have a first meeting to explain the current package and outline/develop 
a potential roadmap in the next virtual DC/OS office hours: 
https://www.meetup.com/DC-OS-Online-Meetup/events/240919616/.

If you cannot make it to this virtual event, feel free to reach out via the 
#flink channel in the  DC/OS community slack (chat.dcos.io).

Looking forwards to many cool features around Flink and Mesos/ DC/OS,
Jörg and Till
This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information. 
If you are not the intended recipient(s), please reply to the sender and 
destroy all copies of the original message. Any unauthorized review, use, 
disclosure, dissemination, forwarding, printing or copying of this email, 
and/or any action taken in reliance on the contents of this e-mail is strictly 
prohibited and may be unlawful. Where permitted by applicable law, this e-mail 
and other e-mail communications sent to and from Cognizant e-mail addresses may 
be monitored.

Looking for Contributitors: Apache Flink meets Apache Mesos and DC/OS

[Jörg Schad]

Hi,
we are actively looking for contributors (and anyone interested) for the
Flink DC/OS package, as well as the Mesos Flink framework.

We will have a first meeting to explain the current package and
outline/develop a potential roadmap in the next virtual DC/OS office hours:
https://www.meetup.com/DC-OS-Online-Meetup/events/240919616/.

If you cannot make it to this virtual event, feel free to reach out via the
#flink channel in the  DC/OS community slack (chat.dcos.io).

Looking forwards to many cool features around Flink and Mesos/ DC/OS,
Jörg and Till

Re: Work group on Community

[Jörg Schad]

Very excited and happy to join!

On Sat, Jun 17, 2017 at 1:38 AM, James Peach  wrote:

>
> > On Jun 15, 2017, at 10:57 AM, Vinod Kone  wrote:
> >
> > Hi folks,
> >
> > Seeing that our first official containerizer WG is off to a good start,
> we
> > want to use that momentum to start new WGs.
> >
> > I'm proposing that we start a new work group on community. The mission of
> > this work group would be to figure out ways to grow the size of our
> > community and improve the experience of community members (users, devs,
> > contributors, committers etc).
> >
> > In the first meeting, we can nail down what the charter of this work
> group
> > should be etc. My initial ideas for the topics/components this work group
> > could cover
> >
> > --> Releases
> > --> Roadmap
> > --> Reviews
> > --> JIRA
> > --> CI
> >
> > Over time, I'm hoping that new specific work groups will sprung up that
> can
> > own some of these topics.
> >
> > If you are interested in joining this work group, please reply to this
> > thread and I'll add you to the invite.
>
> I'm interested, but unlikely to have much bandwidth to contribute anything
> substantial. One suggestion I have is that a Mesos Weekly news would be
> pretty great. There is a lot of activity on reviewboard, slack and in
> design documents and collecting that in a regular newsletter would give
> that activity a lot more visibility.
>
> J

Compiling my own framework

[Thodoris Zois]

Hello list,

I have created my own framework in Java and i don’t know how to compile it. Any 
help with some instructions would be really appreciated. Right now i am just 
replacing the code in TestFramework.java so i can run my code after compiling 
it with ‘make tests’. But compile takes time, so i wonder how i can make this 
procedure fast!

Thank you,
Thodoris