-...@hadoop.apache.org
Subject: Re: [VOTE] Merge yarn-native-services branch into trunk
Congratulations to all the contributors involved, this is a great step forward!
+Vinod
> On Nov 6, 2017, at 2:40 PM, Jian He wrote:
>
> Okay, I just merged the branch to trunk (108 commits in total !)
> A
Congratulations to all the contributors involved, this is a great step forward!
+Vinod
> On Nov 6, 2017, at 2:40 PM, Jian He wrote:
>
> Okay, I just merged the branch to trunk (108 commits in total !)
> Again, thanks for all who contributed to this feature!
>
> Jian
>
> On Nov 6, 2017, at 1:2
Okay, I just merged the branch to trunk (108 commits in total !)
Again, thanks for all who contributed to this feature!
Jian
On Nov 6, 2017, at 1:26 PM, Jian He
mailto:j...@hortonworks.com>> wrote:
Here’s +1 from myself.
The vote passes with 7 (+1) bindings and 2 (+1) non-bindings.
Thanks for
Here’s +1 from myself.
The vote passes with 7 (+1) bindings and 2 (+1) non-bindings.
Thanks for all who voted. I’ll merge to trunk by the end of today.
Jian
On Nov 6, 2017, at 8:38 AM, Billie Rinaldi
mailto:billie.rina...@gmail.com>> wrote:
+1 (binding)
On Mon, Oct 30, 2017 at 1:06 PM, Jian H
+1 (binding)
On Mon, Oct 30, 2017 at 1:06 PM, Jian He wrote:
> Hi All,
>
> I would like to restart the vote for merging yarn-native-services to trunk.
> Since last vote, we have been working on several issues in documentation,
> DNS, CLI modifications etc. We believe now the feature is in a much
+1 (non-binding)
-Gour
On 10/30/17, 1:49 PM, "Jian He" wrote:
>Few more things:
>
>This is the document for trying a non-docker service on YARN.
>https://github.com/apache/hadoop/blob/yarn-native-services/hadoop-yarn-pro
>ject/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/QuickSt
+1 (binding) thanks Jian for all the great work!
Built from branch and deployed, able to bring up services along with atsv2
enabled and new YARN UI integration.
Tried flexing, start, stop operations using REST api's.
- Rohith Sharma K S
On 31 October 2017 at 01:36, Jian He wrote:
> Hi All,
>
>
+1 (binding)
Tested the branch code and brought up services like sleep and httpd. Also
verified UI as well.
- Sunil
On Tue, Oct 31, 2017 at 1:36 AM Jian He wrote:
> Hi All,
>
> I would like to restart the vote for merging yarn-native-services to trunk.
> Since last vote, we have been working
wrote:
>
> > +1
> > Thanks,
> > Chandni
> >
> > From: Jian He
> > Sent: Monday, October 30, 2017 1:49 PM
> > To: yarn-...@hadoop.apache.org; Hdfs-dev; Hadoop Common;
> > mapreduce
wrote:
>
> > +1
> > Thanks,
> > Chandni
> >
> > From: Jian He
> > Sent: Monday, October 30, 2017 1:49 PM
> > To: yarn-...@hadoop.apache.org; Hdfs-dev; Hadoop Common;
> > mapreduce-...@hadoop.apache.org
> &
t; mapreduce-...@hadoop.apache.org
> Subject: Re: [VOTE] Merge yarn-native-services branch into trunk
>
> Few more things:
>
> This is the document for trying a non-docker service on YARN.
> https://github.com/apache/hadoop/blob/yarn-native-
> services/hadoop-yarn-project/hadoop-
+1
Thanks,
Chandni
From: Jian He
Sent: Monday, October 30, 2017 1:49 PM
To: yarn-...@hadoop.apache.org; Hdfs-dev; Hadoop Common;
mapreduce-...@hadoop.apache.org
Subject: Re: [VOTE] Merge yarn-native-services branch into trunk
Few more things:
This is
Few more things:
This is the document for trying a non-docker service on YARN.
https://github.com/apache/hadoop/blob/yarn-native-services/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/yarn-service/QuickStart.md
And the document for a docker based service
https://github.com/ap
Hi All,
I would like to restart the vote for merging yarn-native-services to trunk.
Since last vote, we have been working on several issues in documentation, DNS,
CLI modifications etc. We believe now the feature is in a much better shape.
Some back ground:
At a high level, the following are the
Hi Allen,
Thanks for sharing the feedback. I opened YARN-7191 for addressing the feedback.
We can move the discussions there.
Thanks,
Jian
> On Sep 13, 2017, at 10:10 AM, Allen Wittenauer
> wrote:
>
>
>> On Sep 8, 2017, at 9:25 AM, Jian He wrote:
>>
>> Hi Allen,
>> The documentations are
> On Sep 8, 2017, at 9:25 AM, Jian He wrote:
>
> Hi Allen,
> The documentations are committed. Please check QuickStart.md and others in
> the same folder.
> YarnCommands.md doc is updated to include new commands.
> DNS default port is also documented.
> Would you like to give a look and see if
Thanks for your consideration Jian, let's track this for GA then.
Best,
Andrew
On Fri, Sep 8, 2017 at 3:02 PM, Jian He wrote:
> Hi Andrew,
>
> At this point, there are no more release blockers including documentations
> from our side - all work done.
> But I agree it is too close to the release
Hi Andrew,
At this point, there are no more release blockers including documentations from
our side - all work done.
But I agree it is too close to the release, after talking with other team
members, we are fine to drop this from beta,
And we want to target this for GA.
I’m withdrawing this vo
Hi Allen,
The documentations are committed. Please check QuickStart.md and others in the
same folder.
YarnCommands.md doc is updated to include new commands.
DNS default port is also documented.
Would you like to give a look and see if it address your concerns ?
Jian
> On Sep 6, 2017, at 10:19
Hi folks,
This vote closes today. I see a -1 from Allen on inclusion in beta1. I see
there's active fixing going on, but given that we're one week out from RC0,
I think we should drop this from beta1.
Allen, Jian, others, is this reasonable? What release should we retarget
this for? I don't have
> Please correct me if I’m wrong, but the current summary of the branch,
> post these changes, looks like:
Sorry for confusion, I was actively writing the formal documentation for how to
use/how it works etc. and will post soon in a few hours.
> On Sep 6, 2017, at 10:15 AM, Allen Wittenau
> On Sep 5, 2017, at 6:23 PM, Jian He wrote:
>
>> If it doesn’t have all the bells and whistles, then it shouldn’t be on
>> port 53 by default.
> Sure, I’ll change the default port to not use 53 and document it.
>> *how* is it getting launched on a privileged port? It sounds like the
> If it doesn’t have all the bells and whistles, then it shouldn’t be on
> port 53 by default.
Sure, I’ll change the default port to not use 53 and document it.
> *how* is it getting launched on a privileged port? It sounds like the
> expectation is to run “command” as root. *ALL* o
Thanks Allen. You are right, the github renderer does have trouble
rendering the headers. I was only looking at the html generated by mvn
site, which did not have trouble rendering them. Anyway I added a space
after all the hashes and it looks ok through github now.
-Gour
On 9/5/17, 3:20 PM, "Al
> On Sep 5, 2017, at 3:12 PM, Gour Saha wrote:
>
> 2) Lots of markdown problems in the NativeServicesDiscovery.md document.
> This includes things like Œyarnsite.xml¹ (missing a dash.)
>
> The md patch uploaded to YARN-5244 had some special chars. I fixed those
> in YARN-7161.
It’s a
2) Lots of markdown problems in the NativeServicesDiscovery.md document.
This includes things like Œyarnsite.xml¹ (missing a dash.)
The md patch uploaded to YARN-5244 had some special chars. I fixed those
in YARN-7161.
>
-
To
> On Sep 5, 2017, at 2:53 PM, Jian He wrote:
>
>> Based on the documentation, this doesn’t appear to be a fully function DNS
>> server as an admin would expect (e.g., BIND, Knot, whatever). Where’s
>> forwarding? How do I setup notify? Are secondaries even supported? etc, etc.
>
> It seems l
> 1) Did I miss it or is there no actual end-user documentation on how to use
> this?
Yes, we are in the process of finishing up the the doc and posting it. We
considered this a release blocker for 3.0.0-beta1 and so working on it in
parallel while the branch merge happens.
> 2) Lots of
> On Aug 31, 2017, at 8:33 PM, Jian He wrote:
> I would like to call a vote for merging yarn-native-services to trunk.
1) Did I miss it or is there no actual end-user documentation on how to
use this? I see
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/native-serv
+1 (binding).
Cheers
-Arun
On Fri, Sep 1, 2017 at 5:24 PM, Wangda Tan wrote:
> +1 (Binding), I tried to use YARN service assembly before to run different
> kinds of jobs (for example, distributed Tensorflow), it is really easy for
> end user to run jobs on YARN.
>
> Thanks to the whole team for
+1 (Binding), I tried to use YARN service assembly before to run different
kinds of jobs (for example, distributed Tensorflow), it is really easy for
end user to run jobs on YARN.
Thanks to the whole team for the great job!
Best,
Wangda
On Fri, Sep 1, 2017 at 3:33 PM, Gour Saha wrote:
> +1 (n
+1 (non-binding)
On 9/1/17, 11:58 AM, "Billie Rinaldi" wrote:
>+1 (non-binding)
>
>On Thu, Aug 31, 2017 at 8:33 PM, Jian He wrote:
>
>> Hi All,
>>
>> I would like to call a vote for merging yarn-native-services to trunk.
>>The
>> vote will run for 7 days as usual.
>>
>> At a high level, the fol
+1 (non-binding)
On Thu, Aug 31, 2017 at 8:33 PM, Jian He wrote:
> Hi All,
>
> I would like to call a vote for merging yarn-native-services to trunk. The
> vote will run for 7 days as usual.
>
> At a high level, the following are the key feautres implemented.
> - YARN-5079[1]. A native YARN fram
Hi All,
I would like to call a vote for merging yarn-native-services to trunk. The vote
will run for 7 days as usual.
At a high level, the following are the key feautres implemented.
- YARN-5079[1]. A native YARN framework (ApplicationMaster) to migrate and
orchestrate existing services to YAR
34 matches
Mail list logo