Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <0ACBC9BD-8050-43BC-BCC2-6D093C53870C@hortonworks.com>
References: <CAD++eC=_3u=MxNCEZnomgAQ0-oYQr4gPbft=25ovUOgO0NkOdg@mail.gmail.com>
 <249334B5-B854-493D-A264-D22AD13E7BF6@hortonworks.com> <CAGCyb56_N=LvENsyou-vak=dcCPgKZoB8TOWt67imQy5p_8Dnw@mail.gmail.com>
 <0ACBC9BD-8050-43BC-BCC2-6D093C53870C@hortonworks.com>
From: larry mccay <lmccay@apache.org>
Date: Wed, 6 Sep 2017 21:41:19 -0400
Message-ID: <CACRbFyhT0saNqWW3fnyfH2=n+h7Nn1Ouj-=EoprLw24A4wBE9Q@mail.gmail.com>
Subject: Re: [DISCUSS] Looking to Apache Hadoop 3.1 release
To: Wangda Tan <wheeleast@gmail.com>
Cc: Arun Suresh <arun.suresh@gmail.com>, Steve Loughran <stevel@hortonworks.com>,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>,
	"mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>,
	"hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
	"common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>, Anu Engineer <aengineer@hortonworks.com>
Content-Type: multipart/alternative; boundary="f403043cb094a9396905588f8e8d"
archived-at: Thu, 07 Sep 2017 01:41:27 -0000

--f403043cb094a9396905588f8e8d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Wangda -

Thank you for starting this conversation!

+1000 for a faster release cadence.
Quicker releases make turning around security fixes so much easier.

When we consider alpha features, let=E2=80=99s please ensure that they are =
not
delivered in a state that has known security issues and also make sure that
they are disabled by default. IMO - it is not a feature - alpha or
otherwise - unless it has some reasonable assurance of being secure. Please
don't see this as calling out any particular feature. I just think we need
to be very explicit about security expectations. Maybe this is already well
understood.

Thank you for this proposed plan and for volunteering!

=E2=80=94larry

On Wed, Sep 6, 2017 at 7:22 PM, Anu Engineer <aengineer@hortonworks.com>
wrote:

> Hi Wangda,
>
> We are planning to start the Ozone merge discussion by the end of this
> month. I am hopeful that it will be merged pretty soon after that.
> Please add Ozone to the list of features that are being tracked for Apach=
e
> Hadoop 3.1.
>
> We would love to release Ozone as an alpha feature in Hadoop 3.1.
>
> Thanks
> Anu
>
>
> On 9/6/17, 2:26 PM, "Arun Suresh" <arun.suresh@gmail.com> wrote:
>
> >Thanks for starting this Wangda.
> >
> >I would also like to add:
> >- YARN-5972: Support Pausing/Freezing of opportunistic containers
> >
> >Cheers
> >-Arun
> >
> >On Wed, Sep 6, 2017 at 1:49 PM, Steve Loughran <stevel@hortonworks.com>
> >wrote:
> >
> >>
> >> > On 6 Sep 2017, at 19:13, Wangda Tan <wheeleast@gmail.com> wrote:
> >> >
> >> > Hi all,
> >> >
> >> > As we discussed on [1], there were proposals from Steve / Vinod etc =
to
> >> have
> >> > a faster cadence of releases and to start thinking of a Hadoop 3.1
> >> release
> >> > earlier than March 2018 as is currently proposed.
> >> >
> >> > I think this is a good idea. I'd like to start the process sooner, a=
nd
> >> > establish timeline etc so that we can be ready when 3.0.0 GA is out.
> With
> >> > this we can also establish faster cadence for future Hadoop 3.x
> releases.
> >> >
> >> > To this end, I propose to target Hadoop 3.1.0 for a release by mid J=
an
> >> > 2018. (About 4.5 months from now and 2.5 months after 3.0-GA, instea=
d
> of
> >> > 6.5 months from now).
> >> >
> >> > I'd also want to take this opportunity to come up with a more
> elaborate
> >> > release plan to avoid some of the confusion we had with 3.0 beta.
> General
> >> > proposal for the timeline (per this other proposal [2])
> >> > - Feature freeze date - all features should be merged by Dec 15, 201=
7.
> >> > - Code freeze date - blockers/critical only, no more improvements an=
d
> non
> >> > blocker/critical bug-fixes: Jan 1, 2018.
> >> > - Release date: Jan 15, 2018
> >> >
> >> > Following is a list of features on my radar which could be candidate=
s
> >> for a
> >> > 3.1 release:
> >> > - YARN-5734, Dynamic scheduler queue configuration. (Owner: Jonathan
> >> Hung)
> >> > - YARN-5881, Add absolute resource configuration to CapacitySchedule=
r.
> >> > (Owner: Sunil)
> >> > - YARN-5673, Container-executor rewrite for better security,
> >> extensibility
> >> > and portability. (Owner Varun Vasudev)
> >> > - YARN-6223, GPU isolation. (Owner: Wangda)
> >> >
> >> > And from email [3] mentioned by Andrew, there=E2=80=99re several oth=
er HDFS
> >> > features want to be released with 3.1 as well, assuming they fit the
> >> > timelines:
> >> > - Storage Policy Satisfier
> >> > - HDFS tiered storage
> >> >
> >> > Please let me know if I missed any features targeted to 3.1 per this
> >> > timeline.
> >>
> >>
> >> HADOOP-13786 : S3Guard committer, which also adds resilience to failur=
es
> >> talking to S3 (we barely have any today),
> >>
> >> >
> >> > And I want to volunteer myself as release manager of 3.1.0 release.
> >> Please
> >> > let me know if you have any suggestions/concerns.
> >>
> >> well volunteered :)
> >>
> >> >
> >> > Thanks,
> >> > Wangda Tan
> >> >
> >> > [1] http://markmail.org/message/hwar5f5ap654ck5o?q=3D
> >> > Branch+merges+and+3%2E0%2E0-beta1+scope
> >> > [2] http://markmail.org/message/hwar5f5ap654ck5o?q=3DBranch+
> >> > merges+and+3%2E0%2E0-beta1+scope#query:Branch%20merges%
> >> > 20and%203.0.0-beta1%20scope+page:1+mid:2hqqkhl2dymcikf5+state:result=
s
> >> > [3] http://markmail.org/message/h35obzqrh3ag6dgn?q=3DBranch+merge
> >> > s+and+3%2E0%2E0-beta1+scope
>

--f403043cb094a9396905588f8e8d--