Hello everyone,
Just a quick update on the release status. We still need the following
JIRAs to be resolved.
* MYRIAD-43 Replace com.ebay namespace with org.apache
* MYRIAD-98 Move from 4 spaces to 2 spaces for indentation
- Jim is working on both of them
* MYRIAD-114 Automatic dashboard building
- Not sure if anyone is working on this one.
The last comment on JIRA indicates Jim and Ken are collaborating to
resolve this.
* MYRIAD-150 Update NOTICE file
- I think this is done. The JIRA has to be just marked as Resolved.
* MYRIAD-159 Change default mesos version to 0.24
- A minor one line change, but someone still needs to do it.
* MYRIAD-145 Document Myriad Release Process
- Created a draft on the wiki. Will update it as we tag the RC and
publish it for voting.
* MYRIAD-44 Prepare for 0.1.0 release
- Just an Umbrella JIRA keeping track of the individual items.
In addition, Yuliya submitted a PR for MYRIAD-160.
Thanks,
Santosh
On Fri, Oct 23, 2015 at 11:32 AM, Santosh Marella <smare...@maprtech.com>
wrote:
> > let Myriad pick a random port outside of Mesos
>
> Agree with Darin. Picking a port outside of Mesos is prohibitive.
>
> I felt the simplest solution would be to pick a random port from the list
> of ports offered to Myriad.
>
> The right solution, as Darin mentioned in the JIRA, would be to remove NM
> from RM's memory.
> I haven't looked at YARN's code deep enough to see if that's possible. But
> that's something worth exploring.
>
> Thanks,
> Santosh
>
> On Fri, Oct 23, 2015 at 9:57 AM, Darin Johnson <dbjohnson1...@gmail.com>
> wrote:
>
>> On MYRIAD-160, it's a really bad idea to let Myriad pick a random port
>> outside of Mesos as other frameworks might select that port the
>> probability
>> of that happening is 1-(number of ports requested by other
>> frameworks)/(number of ports in use). This could get near 50% and cause
>> frameworks that are being good citizens to crash.
>>
>> I'm also not convinced randomizing the port is in fact the correct fix for
>> this in the long term, as there is still a non-zero chance you'll get that
>> port again.
>>
>> Darin
>>
>>
>>
>> On Fri, Oct 23, 2015 at 12:56 AM, yuliya Feldman <
>> yufeld...@yahoo.com.invalid> wrote:
>>
>> > Great list.
>> > I would include MYRIAD-160 to the list - I am working on that one. Of
>> > course as a workaround we could not use Mesos ports and let NM ports
>> > randomization kick in.I also almost done with MYRIAD-148 - it was really
>> > tricky. Should submit PR tonight.
>> > Thanks,Yuliya
>> > From: Darin Johnson <dbjohnson1...@gmail.com>
>> > To: Dev <dev@myriad.incubator.apache.org>
>> > Sent: Thursday, October 22, 2015 8:29 PM
>> > Subject: Re: JIRA work for 0.1.0
>> >
>> > I think this sounds good about right. A few Jim marked were new
>> features,
>> > gotta leave something for the 0.2.0 release :).
>> >
>> >
>> >
>> >
>> > On Thu, Oct 22, 2015 at 8:08 AM, Santosh Marella <smare...@maprtech.com
>> >
>> > wrote:
>> >
>> > > I looked at the JIRAs currently marked with fix version
>> "myriad-0.1.0".
>> > > There were 19 of them. I moved a few out. We are currently at 14.
>> > >
>> > > However, IMO the show stoppers are really the following:
>> > >
>> > > MYRIAD-43 Replace com.ebay namespace with org.apache
>> > > MYRIAD-44 Prepare for 0.1.0 release
>> > > MYRIAD-98 Move from 4 spaces to 2 spaces for indentation
>> > > MYRIAD-114 Automatic dashboard building
>> > > MYRIAD-145 Document Myriad Release Process
>> > > MYRIAD-150 Update NOTICE file
>> > > MYRIAD-159 Change default mesos version to 0.24
>> > >
>> > > Unless anyone thinks there are other JIRAs that are show stoppers, I
>> > think
>> > > we should stick to the above list
>> > > and cut a RC as soon as we address the above.
>> > >
>> > > **I'm positive the above can be fixed by early next week (10/27) and
>> we
>> > can
>> > > have a RC out for voting mid next week (10/28).**
>> > >
>> > > If we can't fix the above JIRAs in time or if new ones come up as
>> "show
>> > > stoppers", we will have a revised date.
>> > > And, of course, more fixes are welcome, as long as they can be merged
>> > > before 10/27.
>> > >
>> > > Just to let everyone know about the Apache release process (@Adam,
>> feel
>> > > free to chime in):
>> > > - Apache requires that a RC be put out for voting on
>> > dev@myriad.incubator
>> > > for 72 hrs or until 3 binding +1s and no binding -1s,
>> > > - followed by a similar voting round on general@incubator.
>> > >
>> > > Now to run the last mile..!
>> > >
>> > > Cheers,
>> > > Santosh
>> > >
>> > > On Wed, Oct 21, 2015 at 2:48 PM, Adam Bordelon <a...@mesosphere.io>
>> > wrote:
>> > >
>> > > > Keep in mind that Santosh (as Release Manager) has final authority
>> over
>> > > > pushing things out of 0.1.0.
>> > > >
>> > > > I created a (hopefully public) filter for Unresolved 0.1.0 Myriad
>> > JIRAs:
>> > > > https://issues.apache.org/jira/browse/MYRIAD-44?filter=12333786
>> > > >
>> > > > Maybe we should create a dashboard too, like
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12327111
>> > > >
>> > > > On Wed, Oct 21, 2015 at 1:38 PM, Jim Klucar <klu...@gmail.com>
>> wrote:
>> > > >
>> > > > > I went through JIRA and assigned a bunch of the tickets to the
>> Myriad
>> > > > 0.1.0
>> > > > > release. Some of them are really low hanging fruit, so I think we
>> can
>> > > > knock
>> > > > > most of these out. As Adam said in the meeting, we'd rather have
>> too
>> > > many
>> > > > > flagged for the release and pair down rather than miss some. To
>> that
>> > > end,
>> > > > > please go through the tickets that are still unmarked and set the
>> Fix
>> > > > > Version/s: to Myriad 0.1.0 if you think they should be fixed or by
>> > the
>> > > > > release.
>> > > > >
>> > > > > Jim
>> > > > >
>> > > >
>> > >
>> >
>> >
>> >
>> >
>>
>
>
