You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by Billie Rinaldi <bi...@gmail.com> on 2017/09/01 18:58:53 UTC
Re: [VOTE] Merge yarn-native-services branch into trunk
+1 (non-binding)
On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate and
> orchestrate existing services to YARN either docker or non-docker based.
> - YARN-4793[2]. A Rest API server for user to deploy a service via a
> simple JSON spec
> - YARN-4757[3]. Extending today's service registry with a simple DNS
> service to enable users to discover services deployed on YARN
> - YARN-6419[4]. UI support for native-services on the new YARN UI
> All these new services are optional and are sitting outside of the
> existing system, and have no impact on existing system if disabled.
>
> Special thanks to a team of folks who worked hard towards this: Billie
> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith Sharma
> K S, Sunil G, Akhil PB. This effort could not be possible without their
> ideas and hard work.
>
> Thanks,
> Jian
>
> [1] https://issues.apache.org/jira/browse/YARN-5079
> [2] https://issues.apache.org/jira/browse/YARN-4793
> [3] https://issues.apache.org/jira/browse/YARN-4757
> [4] https://issues.apache.org/jira/browse/YARN-6419
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Arun Suresh <as...@apache.org>.
+1 (binding).
Cheers
-Arun
On Fri, Sep 1, 2017 at 5:24 PM, Wangda Tan <wh...@gmail.com> 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 the great job!
>
> Best,
> Wangda
>
>
> On Fri, Sep 1, 2017 at 3:33 PM, Gour Saha <gs...@hortonworks.com> wrote:
>
> > +1 (non-binding)
> >
> > On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
> >
> > >+1 (non-binding)
> > >
> > >On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
> > >>and
> > >> orchestrate existing services to YARN either docker or non-docker
> based.
> > >> - YARN-4793[2]. A Rest API server for user to deploy a service via a
> > >> simple JSON spec
> > >> - YARN-4757[3]. Extending today's service registry with a simple DNS
> > >> service to enable users to discover services deployed on YARN
> > >> - YARN-6419[4]. UI support for native-services on the new YARN UI
> > >> All these new services are optional and are sitting outside of the
> > >> existing system, and have no impact on existing system if disabled.
> > >>
> > >> Special thanks to a team of folks who worked hard towards this: Billie
> > >> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
> > >>Sharma
> > >> K S, Sunil G, Akhil PB. This effort could not be possible without
> their
> > >> ideas and hard work.
> > >>
> > >> Thanks,
> > >> Jian
> > >>
> > >> [1] https://issues.apache.org/jira/browse/YARN-5079
> > >> [2] https://issues.apache.org/jira/browse/YARN-4793
> > >> [3] https://issues.apache.org/jira/browse/YARN-4757
> > >> [4] https://issues.apache.org/jira/browse/YARN-6419
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> > >>
> > >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >
> >
>
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Arun Suresh <as...@apache.org>.
+1 (binding).
Cheers
-Arun
On Fri, Sep 1, 2017 at 5:24 PM, Wangda Tan <wh...@gmail.com> 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 the great job!
>
> Best,
> Wangda
>
>
> On Fri, Sep 1, 2017 at 3:33 PM, Gour Saha <gs...@hortonworks.com> wrote:
>
> > +1 (non-binding)
> >
> > On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
> >
> > >+1 (non-binding)
> > >
> > >On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
> > >>and
> > >> orchestrate existing services to YARN either docker or non-docker
> based.
> > >> - YARN-4793[2]. A Rest API server for user to deploy a service via a
> > >> simple JSON spec
> > >> - YARN-4757[3]. Extending today's service registry with a simple DNS
> > >> service to enable users to discover services deployed on YARN
> > >> - YARN-6419[4]. UI support for native-services on the new YARN UI
> > >> All these new services are optional and are sitting outside of the
> > >> existing system, and have no impact on existing system if disabled.
> > >>
> > >> Special thanks to a team of folks who worked hard towards this: Billie
> > >> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
> > >>Sharma
> > >> K S, Sunil G, Akhil PB. This effort could not be possible without
> their
> > >> ideas and hard work.
> > >>
> > >> Thanks,
> > >> Jian
> > >>
> > >> [1] https://issues.apache.org/jira/browse/YARN-5079
> > >> [2] https://issues.apache.org/jira/browse/YARN-4793
> > >> [3] https://issues.apache.org/jira/browse/YARN-4757
> > >> [4] https://issues.apache.org/jira/browse/YARN-6419
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> > >>
> > >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >
> >
>
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Arun Suresh <as...@apache.org>.
+1 (binding).
Cheers
-Arun
On Fri, Sep 1, 2017 at 5:24 PM, Wangda Tan <wh...@gmail.com> 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 the great job!
>
> Best,
> Wangda
>
>
> On Fri, Sep 1, 2017 at 3:33 PM, Gour Saha <gs...@hortonworks.com> wrote:
>
> > +1 (non-binding)
> >
> > On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
> >
> > >+1 (non-binding)
> > >
> > >On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
> > >>and
> > >> orchestrate existing services to YARN either docker or non-docker
> based.
> > >> - YARN-4793[2]. A Rest API server for user to deploy a service via a
> > >> simple JSON spec
> > >> - YARN-4757[3]. Extending today's service registry with a simple DNS
> > >> service to enable users to discover services deployed on YARN
> > >> - YARN-6419[4]. UI support for native-services on the new YARN UI
> > >> All these new services are optional and are sitting outside of the
> > >> existing system, and have no impact on existing system if disabled.
> > >>
> > >> Special thanks to a team of folks who worked hard towards this: Billie
> > >> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
> > >>Sharma
> > >> K S, Sunil G, Akhil PB. This effort could not be possible without
> their
> > >> ideas and hard work.
> > >>
> > >> Thanks,
> > >> Jian
> > >>
> > >> [1] https://issues.apache.org/jira/browse/YARN-5079
> > >> [2] https://issues.apache.org/jira/browse/YARN-4793
> > >> [3] https://issues.apache.org/jira/browse/YARN-4757
> > >> [4] https://issues.apache.org/jira/browse/YARN-6419
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> > >>
> > >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >
> >
>
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Arun Suresh <as...@apache.org>.
+1 (binding).
Cheers
-Arun
On Fri, Sep 1, 2017 at 5:24 PM, Wangda Tan <wh...@gmail.com> 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 the great job!
>
> Best,
> Wangda
>
>
> On Fri, Sep 1, 2017 at 3:33 PM, Gour Saha <gs...@hortonworks.com> wrote:
>
> > +1 (non-binding)
> >
> > On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
> >
> > >+1 (non-binding)
> > >
> > >On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
> > >>and
> > >> orchestrate existing services to YARN either docker or non-docker
> based.
> > >> - YARN-4793[2]. A Rest API server for user to deploy a service via a
> > >> simple JSON spec
> > >> - YARN-4757[3]. Extending today's service registry with a simple DNS
> > >> service to enable users to discover services deployed on YARN
> > >> - YARN-6419[4]. UI support for native-services on the new YARN UI
> > >> All these new services are optional and are sitting outside of the
> > >> existing system, and have no impact on existing system if disabled.
> > >>
> > >> Special thanks to a team of folks who worked hard towards this: Billie
> > >> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
> > >>Sharma
> > >> K S, Sunil G, Akhil PB. This effort could not be possible without
> their
> > >> ideas and hard work.
> > >>
> > >> Thanks,
> > >> Jian
> > >>
> > >> [1] https://issues.apache.org/jira/browse/YARN-5079
> > >> [2] https://issues.apache.org/jira/browse/YARN-4793
> > >> [3] https://issues.apache.org/jira/browse/YARN-4757
> > >> [4] https://issues.apache.org/jira/browse/YARN-6419
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > >> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> > >>
> > >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >
> >
>
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Wangda Tan <wh...@gmail.com>.
+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 <gs...@hortonworks.com> wrote:
> +1 (non-binding)
>
> On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
>
> >+1 (non-binding)
> >
> >On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
> >>and
> >> orchestrate existing services to YARN either docker or non-docker based.
> >> - YARN-4793[2]. A Rest API server for user to deploy a service via a
> >> simple JSON spec
> >> - YARN-4757[3]. Extending today's service registry with a simple DNS
> >> service to enable users to discover services deployed on YARN
> >> - YARN-6419[4]. UI support for native-services on the new YARN UI
> >> All these new services are optional and are sitting outside of the
> >> existing system, and have no impact on existing system if disabled.
> >>
> >> Special thanks to a team of folks who worked hard towards this: Billie
> >> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
> >>Sharma
> >> K S, Sunil G, Akhil PB. This effort could not be possible without their
> >> ideas and hard work.
> >>
> >> Thanks,
> >> Jian
> >>
> >> [1] https://issues.apache.org/jira/browse/YARN-5079
> >> [2] https://issues.apache.org/jira/browse/YARN-4793
> >> [3] https://issues.apache.org/jira/browse/YARN-4757
> >> [4] https://issues.apache.org/jira/browse/YARN-6419
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Wangda Tan <wh...@gmail.com>.
+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 <gs...@hortonworks.com> wrote:
> +1 (non-binding)
>
> On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
>
> >+1 (non-binding)
> >
> >On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
> >>and
> >> orchestrate existing services to YARN either docker or non-docker based.
> >> - YARN-4793[2]. A Rest API server for user to deploy a service via a
> >> simple JSON spec
> >> - YARN-4757[3]. Extending today's service registry with a simple DNS
> >> service to enable users to discover services deployed on YARN
> >> - YARN-6419[4]. UI support for native-services on the new YARN UI
> >> All these new services are optional and are sitting outside of the
> >> existing system, and have no impact on existing system if disabled.
> >>
> >> Special thanks to a team of folks who worked hard towards this: Billie
> >> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
> >>Sharma
> >> K S, Sunil G, Akhil PB. This effort could not be possible without their
> >> ideas and hard work.
> >>
> >> Thanks,
> >> Jian
> >>
> >> [1] https://issues.apache.org/jira/browse/YARN-5079
> >> [2] https://issues.apache.org/jira/browse/YARN-4793
> >> [3] https://issues.apache.org/jira/browse/YARN-4757
> >> [4] https://issues.apache.org/jira/browse/YARN-6419
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Wangda Tan <wh...@gmail.com>.
+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 <gs...@hortonworks.com> wrote:
> +1 (non-binding)
>
> On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
>
> >+1 (non-binding)
> >
> >On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
> >>and
> >> orchestrate existing services to YARN either docker or non-docker based.
> >> - YARN-4793[2]. A Rest API server for user to deploy a service via a
> >> simple JSON spec
> >> - YARN-4757[3]. Extending today's service registry with a simple DNS
> >> service to enable users to discover services deployed on YARN
> >> - YARN-6419[4]. UI support for native-services on the new YARN UI
> >> All these new services are optional and are sitting outside of the
> >> existing system, and have no impact on existing system if disabled.
> >>
> >> Special thanks to a team of folks who worked hard towards this: Billie
> >> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
> >>Sharma
> >> K S, Sunil G, Akhil PB. This effort could not be possible without their
> >> ideas and hard work.
> >>
> >> Thanks,
> >> Jian
> >>
> >> [1] https://issues.apache.org/jira/browse/YARN-5079
> >> [2] https://issues.apache.org/jira/browse/YARN-4793
> >> [3] https://issues.apache.org/jira/browse/YARN-4757
> >> [4] https://issues.apache.org/jira/browse/YARN-6419
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Wangda Tan <wh...@gmail.com>.
+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 <gs...@hortonworks.com> wrote:
> +1 (non-binding)
>
> On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
>
> >+1 (non-binding)
> >
> >On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
> >>and
> >> orchestrate existing services to YARN either docker or non-docker based.
> >> - YARN-4793[2]. A Rest API server for user to deploy a service via a
> >> simple JSON spec
> >> - YARN-4757[3]. Extending today's service registry with a simple DNS
> >> service to enable users to discover services deployed on YARN
> >> - YARN-6419[4]. UI support for native-services on the new YARN UI
> >> All these new services are optional and are sitting outside of the
> >> existing system, and have no impact on existing system if disabled.
> >>
> >> Special thanks to a team of folks who worked hard towards this: Billie
> >> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
> >>Sharma
> >> K S, Sunil G, Akhil PB. This effort could not be possible without their
> >> ideas and hard work.
> >>
> >> Thanks,
> >> Jian
> >>
> >> [1] https://issues.apache.org/jira/browse/YARN-5079
> >> [2] https://issues.apache.org/jira/browse/YARN-4793
> >> [3] https://issues.apache.org/jira/browse/YARN-4757
> >> [4] https://issues.apache.org/jira/browse/YARN-6419
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> >> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>
>
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Gour Saha <gs...@hortonworks.com>.
+1 (non-binding)
On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
>+1 (non-binding)
>
>On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
>>and
>> orchestrate existing services to YARN either docker or non-docker based.
>> - YARN-4793[2]. A Rest API server for user to deploy a service via a
>> simple JSON spec
>> - YARN-4757[3]. Extending today's service registry with a simple DNS
>> service to enable users to discover services deployed on YARN
>> - YARN-6419[4]. UI support for native-services on the new YARN UI
>> All these new services are optional and are sitting outside of the
>> existing system, and have no impact on existing system if disabled.
>>
>> Special thanks to a team of folks who worked hard towards this: Billie
>> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
>>Sharma
>> K S, Sunil G, Akhil PB. This effort could not be possible without their
>> ideas and hard work.
>>
>> Thanks,
>> Jian
>>
>> [1] https://issues.apache.org/jira/browse/YARN-5079
>> [2] https://issues.apache.org/jira/browse/YARN-4793
>> [3] https://issues.apache.org/jira/browse/YARN-4757
>> [4] https://issues.apache.org/jira/browse/YARN-6419
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Gour Saha <gs...@hortonworks.com>.
+1 (non-binding)
On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
>+1 (non-binding)
>
>On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
>>and
>> orchestrate existing services to YARN either docker or non-docker based.
>> - YARN-4793[2]. A Rest API server for user to deploy a service via a
>> simple JSON spec
>> - YARN-4757[3]. Extending today's service registry with a simple DNS
>> service to enable users to discover services deployed on YARN
>> - YARN-6419[4]. UI support for native-services on the new YARN UI
>> All these new services are optional and are sitting outside of the
>> existing system, and have no impact on existing system if disabled.
>>
>> Special thanks to a team of folks who worked hard towards this: Billie
>> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
>>Sharma
>> K S, Sunil G, Akhil PB. This effort could not be possible without their
>> ideas and hard work.
>>
>> Thanks,
>> Jian
>>
>> [1] https://issues.apache.org/jira/browse/YARN-5079
>> [2] https://issues.apache.org/jira/browse/YARN-4793
>> [3] https://issues.apache.org/jira/browse/YARN-4757
>> [4] https://issues.apache.org/jira/browse/YARN-6419
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Gour Saha <gs...@hortonworks.com>.
+1 (non-binding)
On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
>+1 (non-binding)
>
>On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
>>and
>> orchestrate existing services to YARN either docker or non-docker based.
>> - YARN-4793[2]. A Rest API server for user to deploy a service via a
>> simple JSON spec
>> - YARN-4757[3]. Extending today's service registry with a simple DNS
>> service to enable users to discover services deployed on YARN
>> - YARN-6419[4]. UI support for native-services on the new YARN UI
>> All these new services are optional and are sitting outside of the
>> existing system, and have no impact on existing system if disabled.
>>
>> Special thanks to a team of folks who worked hard towards this: Billie
>> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
>>Sharma
>> K S, Sunil G, Akhil PB. This effort could not be possible without their
>> ideas and hard work.
>>
>> Thanks,
>> Jian
>>
>> [1] https://issues.apache.org/jira/browse/YARN-5079
>> [2] https://issues.apache.org/jira/browse/YARN-4793
>> [3] https://issues.apache.org/jira/browse/YARN-4757
>> [4] https://issues.apache.org/jira/browse/YARN-6419
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: [VOTE] Merge yarn-native-services branch into trunk
Posted by Gour Saha <gs...@hortonworks.com>.
+1 (non-binding)
On 9/1/17, 11:58 AM, "Billie Rinaldi" <bi...@gmail.com> wrote:
>+1 (non-binding)
>
>On Thu, Aug 31, 2017 at 8:33 PM, Jian He <jh...@hortonworks.com> 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 framework (ApplicationMaster) to migrate
>>and
>> orchestrate existing services to YARN either docker or non-docker based.
>> - YARN-4793[2]. A Rest API server for user to deploy a service via a
>> simple JSON spec
>> - YARN-4757[3]. Extending today's service registry with a simple DNS
>> service to enable users to discover services deployed on YARN
>> - YARN-6419[4]. UI support for native-services on the new YARN UI
>> All these new services are optional and are sitting outside of the
>> existing system, and have no impact on existing system if disabled.
>>
>> Special thanks to a team of folks who worked hard towards this: Billie
>> Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith
>>Sharma
>> K S, Sunil G, Akhil PB. This effort could not be possible without their
>> ideas and hard work.
>>
>> Thanks,
>> Jian
>>
>> [1] https://issues.apache.org/jira/browse/YARN-5079
>> [2] https://issues.apache.org/jira/browse/YARN-4793
>> [3] https://issues.apache.org/jira/browse/YARN-4757
>> [4] https://issues.apache.org/jira/browse/YARN-6419
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
>> For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org