[DISCUSS] jbatch impl @Apache?

[Romain Manni-Bucau]

Hi

As you probably know JavaEE 7 proposes a new spec called JBatch (aka JSR
352).

I'd love to see an implementation @Apache.

There is ATM only one implementation (spring-batch doesn't pass the full
TCKs): the RI (done by IBM).

AFAIK they doesn't aim to create a community about this spec but their
implementation is under the license Apache v2 and starting to implement it
from scratch i started to get something very close to them (i just started
but seeing my classes so close i decided to stop my impl from scratch and
see if forking wouldn't be a better/easier solution).

Personally my plan would be to fork their code and clean/update it and
create a community around it.

About it i have some questions:
1) does it sound good?
2) any interested people?
3) how to process exactly?

*Romain Manni-Bucau*
*Twitter: @rmannibucau *
*Blog: **http://rmannibucau.wordpress.com/*
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*

Re: [DISCUSS] jbatch impl @Apache?

[Alan Cabrera]

Is there enough interest to generate an active community for this?  Would it 
make more sense to do this work under Geronimo or TomEE?


Regards,
Alan


On Aug 26, 2013, at 7:01 AM, Romain Manni-Bucau  wrote:

> Hi
> 
> As you probably know JavaEE 7 proposes a new spec called JBatch (aka JSR
> 352).
> 
> I'd love to see an implementation @Apache.
> 
> There is ATM only one implementation (spring-batch doesn't pass the full
> TCKs): the RI (done by IBM).
> 
> AFAIK they doesn't aim to create a community about this spec but their
> implementation is under the license Apache v2 and starting to implement it
> from scratch i started to get something very close to them (i just started
> but seeing my classes so close i decided to stop my impl from scratch and
> see if forking wouldn't be a better/easier solution).
> 
> Personally my plan would be to fork their code and clean/update it and
> create a community around it.
> 
> About it i have some questions:
> 1) does it sound good?
> 2) any interested people?
> 3) how to process exactly?
> 
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau *
> *Blog: **http://rmannibucau.wordpress.com/*
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] jbatch impl @Apache?

[Romain Manni-Bucau]

A bunch of users will be standalone users so a separated project sounds
fine to me
Le 26 août 2013 17:15, "Alan Cabrera"  a écrit :

> Is there enough interest to generate an active community for this?  Would
> it make more sense to do this work under Geronimo or TomEE?
>
>
> Regards,
> Alan
>
>
> On Aug 26, 2013, at 7:01 AM, Romain Manni-Bucau 
> wrote:
>
> > Hi
> >
> > As you probably know JavaEE 7 proposes a new spec called JBatch (aka JSR
> > 352).
> >
> > I'd love to see an implementation @Apache.
> >
> > There is ATM only one implementation (spring-batch doesn't pass the full
> > TCKs): the RI (done by IBM).
> >
> > AFAIK they doesn't aim to create a community about this spec but their
> > implementation is under the license Apache v2 and starting to implement
> it
> > from scratch i started to get something very close to them (i just
> started
> > but seeing my classes so close i decided to stop my impl from scratch and
> > see if forking wouldn't be a better/easier solution).
> >
> > Personally my plan would be to fork their code and clean/update it and
> > create a community around it.
> >
> > About it i have some questions:
> > 1) does it sound good?
> > 2) any interested people?
> > 3) how to process exactly?
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau *
> > *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache jclouds-1.6.2-incubating RC2

[Roman Shaposhnik]

On Thu, Aug 22, 2013 at 6:06 AM, Andrew Phillips  wrote:
> Hi all
>
> This is the third release candidate for Apache jclouds
> 1.6.2-incubating, the second jclouds release at Apache.
>
> This is the IPMC vote. The PPMC vote [1] passed, with one +1 from
> mentors (Olivier Lamy). Please use the separate [DISCUSS] thread for
> anything but votes.
>
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324574&styleName=Html&projectId=12314430
>
> *** Please download, test and vote by Tuesday, August 27th, 06:00 PDT /
> 09:00 EDT / 15:00 CET.
>
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/jclouds/1.6.2-incubating-rc2/
>
> Maven staging repos:
> https://repository.apache.org/content/repositories/orgapachejclouds-102/
>
> The tags to be voted upon:
> - jclouds -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=1a74b20b5d3b632a0a27195722dc39a2f4014275
>
> - jclouds-labs -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=7d5baa5edb66ff2f221ecccffeaffb56e6188ccd
>
> - jclouds-labs-openstack -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs-openstack.git;a=tag;h=c18518ff4b16388e472d635fcd1e377af70c23db
>
> - jclouds-chef -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=d28af2d458ecc1f783b096bff097d78016155dc4
>
> - jclouds-karaf -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=b5779131dbfd8baebf28d84372510adac42c0743
>
> - jclouds-cli -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=5f9bdaf5c16450187a43e7591795e9ffb7674127
>
> jclouds KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/incubator/jclouds/KEYS
>
> [ ] +1
> [ ] 0
> [ ] -1 (explain why)
>
> Thanks to all involved for their time!

+1 (binding)

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache jclouds-1.6.2-incubating RC2

[Suresh Marru]

+ 1 (binding) 

JClouds PPMC,

The release verification script is handy, should consider sharing it with 
general list, it could be could possibly be improved and tuned to project 
specific verifications. 

Suresh

On Aug 22, 2013, at 9:06 AM, Andrew Phillips  wrote:

> Hi all
> 
> This is the third release candidate for Apache jclouds
> 1.6.2-incubating, the second jclouds release at Apache.
> 
> This is the IPMC vote. The PPMC vote [1] passed, with one +1 from
> mentors (Olivier Lamy). Please use the separate [DISCUSS] thread for
> anything but votes.
> 
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324574&styleName=Html&projectId=12314430
> 
> *** Please download, test and vote by Tuesday, August 27th, 06:00 PDT /
> 09:00 EDT / 15:00 CET.
> 
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
> 
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/jclouds/1.6.2-incubating-rc2/
> 
> Maven staging repos:
> https://repository.apache.org/content/repositories/orgapachejclouds-102/
> 
> The tags to be voted upon:
> - jclouds -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=1a74b20b5d3b632a0a27195722dc39a2f4014275
> 
> - jclouds-labs -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=7d5baa5edb66ff2f221ecccffeaffb56e6188ccd
> 
> - jclouds-labs-openstack -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs-openstack.git;a=tag;h=c18518ff4b16388e472d635fcd1e377af70c23db
> 
> - jclouds-chef -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=d28af2d458ecc1f783b096bff097d78016155dc4
> 
> - jclouds-karaf -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=b5779131dbfd8baebf28d84372510adac42c0743
> 
> - jclouds-cli -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=5f9bdaf5c16450187a43e7591795e9ffb7674127
> 
> jclouds KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/incubator/jclouds/KEYS
> 
> [ ] +1
> [ ] 0
> [ ] -1 (explain why)
> 
> Thanks to all involved for their time!
> 
> ap
> 
> [1] http://markmail.org/message/2r66vkuhgg4quw5r


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[PROPOSAL] Aurora for Incubation

[Dave Lester]

Hi All,

We're pleased to share a draft ASF incubation proposal for Aurora, a
service scheduler used to schedule jobs onto Apache Mesos that we've
developed at Twitter. Aurora provides all of the primitives necessary to
quickly deploy and scale stateless and fault tolerant services in a
datacenter. The complete proposal can be found:
https://wiki.apache.org/incubator/AuroraProposal, and also pasted below.

In particular, we'd love to add additional mentors to the project. Your
feedback is appreciated.

Dave

= Abstract =

Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

= Proposal =

Aurora is a scheduler that provides all of the primitives necessary to
quickly deploy and scale stateless and fault tolerant services in a
datacenter.

Aurora builds on top of Apache Mesos and provides common features that
allow any site to run large scale production applications. While the
project is currently used in production at Twitter, we wish to develop a
community to increase contributions and see it thrive in the future.

= Background =

The initial development of Aurora was done at Twitter, and is planned to be
open sourced. This proposal is for Aurora to join the Apache Incubator.

= Rationale =

While the Apache Mesos core focuses on distributing individual tasks across
nodes in a cluster, typical services consist of dozens or hundreds of
replicas of tasks. As a service scheduler, Aurora provides the abstraction
of a "job" to bundle and manage these tasks. Aurora provides many key
functionalities centered around a job, including: definition, the concept
of an instance and the serverset, deployment and scheduling, health
checking, and introspection. It also allows cross-cutting concerns to be
handled like observability and log collection.

= Current Status =

== Meritocracy ==

By submitting this incubator proposal, we’re expressing our intent to build
a diverse developer community around Aurora that will conduct itself
according to The Apache Way and use meritocratic means of accepting
contributions. Several members of the Aurora team overlap with Apache
Mesos, which successfully graduated from the Incubator and has embraced a
meritocratic model of governance; we plan to follow a similar path forward
with Aurora and believe that a synergy between both projects will make this
even easier.

== Community ==

Aurora is currently being used internally at Twitter. By open sourcing the
project, we hope to extend our contributor base significantly and create a
vibrant community around the project.

== Core Developers ==

Aurora is currently being developed by a team of seven engineers at Twitter.

== Alignment ==

The ASF is a natural choice to host the Aurora project, given the goal of
open sourcing the project and fostering a community to grow and support the
software. Additionally, Aurora integrates with Apache Mesos, and Apache
ZooKeeper for service discovery.

We believe that inclusion within Apache will build stronger ties between
these projects, and create further alignment between their goals and
communities.

= Known Risks =

== Orphaned Products ==

The core developers plan to continue working full time on the project, and
there is very little risk of Aurora being abandoned since it is running
hundreds of services as part of Twitter’s infrastructure. Additionally,
members of the Mesos community beyond Twitter have expressed interest in an
advanced scheduler like Aurora (see “Interested Parties” section); we
believe that need will drive some of the community involvement necessary
for the project to incubate successfully.

== Inexperience with Open Source ==

Initial Aurora committers have varying levels of experience using and
contributing to Open Source projects, however by working with our mentors
and the Apache community we believe we will be able to conduct ourselves in
accordance with Apache Incubator guidelines. The close relationship between
the Aurora team and Apache Mesos means there is an awareness of the
incubation process and a willingness to embrace The Apache Way.

== Homogenous Developers ==

The initial set of committers are from a single organization, however we
expect that once approved for incubation the project will attract
contributors from more organizations. We have already had conversations
with other companies who have expressed an interest in Aurora.

== Reliance on Salaried Developers ==

Initial Aurora committers are salaried developers at Twitter, however
shortly after open sourcing the code we plan to diversify the project’s
core committers and contributors.

== Relationships with Other Apache Products ==

Initially, Aurora has been developed as a scheduler for Apache Mesos.
Additionally, it relies on ZooKeeper for service discovery, allowing
servers to register at a location and clients to subsequently discover the
servers.

== An Excessive Fascination with the Apache Brand ==

While we respect the reputation of the Apache brand and have no doubts that
it will 

Re: [PROPOSAL] Aurora for Incubation

[Jake Farrell]

I would like to volunteer to be a mentor for this project.

I am the Apache Thrift project chair and I am involved in the Apache
infrastructure group. I have handled releases for Apache Thrift since its
incubation and am very familiar with new project bootstrapping and
coordination. I think that my experiences with back end systems and scaling
architectures would be a perfect fit for this project along with my desire
to help new comers learn the Apache way.

Thank you for your consideration
-Jake




On Mon, Aug 26, 2013 at 6:27 PM, Dave Lester wrote:

> Hi All,
>
> We're pleased to share a draft ASF incubation proposal for Aurora, a
> service scheduler used to schedule jobs onto Apache Mesos that we've
> developed at Twitter. Aurora provides all of the primitives necessary to
> quickly deploy and scale stateless and fault tolerant services in a
> datacenter. The complete proposal can be found:
> https://wiki.apache.org/incubator/AuroraProposal, and also pasted below.
>
> In particular, we'd love to add additional mentors to the project. Your
> feedback is appreciated.
>
> Dave
>
> = Abstract =
>
> Aurora is a service scheduler used to schedule jobs onto Apache Mesos.
>
> = Proposal =
>
> Aurora is a scheduler that provides all of the primitives necessary to
> quickly deploy and scale stateless and fault tolerant services in a
> datacenter.
>
> Aurora builds on top of Apache Mesos and provides common features that
> allow any site to run large scale production applications. While the
> project is currently used in production at Twitter, we wish to develop a
> community to increase contributions and see it thrive in the future.
>
> = Background =
>
> The initial development of Aurora was done at Twitter, and is planned to be
> open sourced. This proposal is for Aurora to join the Apache Incubator.
>
> = Rationale =
>
> While the Apache Mesos core focuses on distributing individual tasks across
> nodes in a cluster, typical services consist of dozens or hundreds of
> replicas of tasks. As a service scheduler, Aurora provides the abstraction
> of a "job" to bundle and manage these tasks. Aurora provides many key
> functionalities centered around a job, including: definition, the concept
> of an instance and the serverset, deployment and scheduling, health
> checking, and introspection. It also allows cross-cutting concerns to be
> handled like observability and log collection.
>
> = Current Status =
>
> == Meritocracy ==
>
> By submitting this incubator proposal, we’re expressing our intent to build
> a diverse developer community around Aurora that will conduct itself
> according to The Apache Way and use meritocratic means of accepting
> contributions. Several members of the Aurora team overlap with Apache
> Mesos, which successfully graduated from the Incubator and has embraced a
> meritocratic model of governance; we plan to follow a similar path forward
> with Aurora and believe that a synergy between both projects will make this
> even easier.
>
> == Community ==
>
> Aurora is currently being used internally at Twitter. By open sourcing the
> project, we hope to extend our contributor base significantly and create a
> vibrant community around the project.
>
> == Core Developers ==
>
> Aurora is currently being developed by a team of seven engineers at
> Twitter.
>
> == Alignment ==
>
> The ASF is a natural choice to host the Aurora project, given the goal of
> open sourcing the project and fostering a community to grow and support the
> software. Additionally, Aurora integrates with Apache Mesos, and Apache
> ZooKeeper for service discovery.
>
> We believe that inclusion within Apache will build stronger ties between
> these projects, and create further alignment between their goals and
> communities.
>
> = Known Risks =
>
> == Orphaned Products ==
>
> The core developers plan to continue working full time on the project, and
> there is very little risk of Aurora being abandoned since it is running
> hundreds of services as part of Twitter’s infrastructure. Additionally,
> members of the Mesos community beyond Twitter have expressed interest in an
> advanced scheduler like Aurora (see “Interested Parties” section); we
> believe that need will drive some of the community involvement necessary
> for the project to incubate successfully.
>
> == Inexperience with Open Source ==
>
> Initial Aurora committers have varying levels of experience using and
> contributing to Open Source projects, however by working with our mentors
> and the Apache community we believe we will be able to conduct ourselves in
> accordance with Apache Incubator guidelines. The close relationship between
> the Aurora team and Apache Mesos means there is an awareness of the
> incubation process and a willingness to embrace The Apache Way.
>
> == Homogenous Developers ==
>
> The initial set of committers are from a single organization, however we
> expect that once approved for incubation the project will attract
> contributors from mo

Re: [PROPOSAL] Aurora for Incubation

[Henry Saputra]

Hi Dave,

This looks like interesting project and good contributions from Twitter
engineering.

But given that close relationship with Apache Mesos, wouldn't it be more
effective to be delivered as extension or feature contribution to Apache
Mesos?


- Henry


On Mon, Aug 26, 2013 at 3:27 PM, Dave Lester wrote:

> Hi All,
>
> We're pleased to share a draft ASF incubation proposal for Aurora, a
> service scheduler used to schedule jobs onto Apache Mesos that we've
> developed at Twitter. Aurora provides all of the primitives necessary to
> quickly deploy and scale stateless and fault tolerant services in a
> datacenter. The complete proposal can be found:
> https://wiki.apache.org/incubator/AuroraProposal, and also pasted below.
>
> In particular, we'd love to add additional mentors to the project. Your
> feedback is appreciated.
>
> Dave
>
> = Abstract =
>
> Aurora is a service scheduler used to schedule jobs onto Apache Mesos.
>
> = Proposal =
>
> Aurora is a scheduler that provides all of the primitives necessary to
> quickly deploy and scale stateless and fault tolerant services in a
> datacenter.
>
> Aurora builds on top of Apache Mesos and provides common features that
> allow any site to run large scale production applications. While the
> project is currently used in production at Twitter, we wish to develop a
> community to increase contributions and see it thrive in the future.
>
> = Background =
>
> The initial development of Aurora was done at Twitter, and is planned to be
> open sourced. This proposal is for Aurora to join the Apache Incubator.
>
> = Rationale =
>
> While the Apache Mesos core focuses on distributing individual tasks across
> nodes in a cluster, typical services consist of dozens or hundreds of
> replicas of tasks. As a service scheduler, Aurora provides the abstraction
> of a "job" to bundle and manage these tasks. Aurora provides many key
> functionalities centered around a job, including: definition, the concept
> of an instance and the serverset, deployment and scheduling, health
> checking, and introspection. It also allows cross-cutting concerns to be
> handled like observability and log collection.
>
> = Current Status =
>
> == Meritocracy ==
>
> By submitting this incubator proposal, we’re expressing our intent to build
> a diverse developer community around Aurora that will conduct itself
> according to The Apache Way and use meritocratic means of accepting
> contributions. Several members of the Aurora team overlap with Apache
> Mesos, which successfully graduated from the Incubator and has embraced a
> meritocratic model of governance; we plan to follow a similar path forward
> with Aurora and believe that a synergy between both projects will make this
> even easier.
>
> == Community ==
>
> Aurora is currently being used internally at Twitter. By open sourcing the
> project, we hope to extend our contributor base significantly and create a
> vibrant community around the project.
>
> == Core Developers ==
>
> Aurora is currently being developed by a team of seven engineers at
> Twitter.
>
> == Alignment ==
>
> The ASF is a natural choice to host the Aurora project, given the goal of
> open sourcing the project and fostering a community to grow and support the
> software. Additionally, Aurora integrates with Apache Mesos, and Apache
> ZooKeeper for service discovery.
>
> We believe that inclusion within Apache will build stronger ties between
> these projects, and create further alignment between their goals and
> communities.
>
> = Known Risks =
>
> == Orphaned Products ==
>
> The core developers plan to continue working full time on the project, and
> there is very little risk of Aurora being abandoned since it is running
> hundreds of services as part of Twitter’s infrastructure. Additionally,
> members of the Mesos community beyond Twitter have expressed interest in an
> advanced scheduler like Aurora (see “Interested Parties” section); we
> believe that need will drive some of the community involvement necessary
> for the project to incubate successfully.
>
> == Inexperience with Open Source ==
>
> Initial Aurora committers have varying levels of experience using and
> contributing to Open Source projects, however by working with our mentors
> and the Apache community we believe we will be able to conduct ourselves in
> accordance with Apache Incubator guidelines. The close relationship between
> the Aurora team and Apache Mesos means there is an awareness of the
> incubation process and a willingness to embrace The Apache Way.
>
> == Homogenous Developers ==
>
> The initial set of committers are from a single organization, however we
> expect that once approved for incubation the project will attract
> contributors from more organizations. We have already had conversations
> with other companies who have expressed an interest in Aurora.
>
> == Reliance on Salaried Developers ==
>
> Initial Aurora committers are salaried developers at Twitter, however
> shortly af

Re: [PROPOSAL] Aurora for Incubation

[Dave Lester]

Excellent, thank you Jake! I will add your name to the proposal.

Dave

On Mon, Aug 26, 2013 at 3:47 PM, Jake Farrell  wrote:

> I would like to volunteer to be a mentor for this project.
>
> I am the Apache Thrift project chair and I am involved in the Apache
> infrastructure group. I have handled releases for Apache Thrift since its
> incubation and am very familiar with new project bootstrapping and
> coordination. I think that my experiences with back end systems and scaling
> architectures would be a perfect fit for this project along with my desire
> to help new comers learn the Apache way.
>
> Thank you for your consideration
> -Jake
>
>
>
>
> On Mon, Aug 26, 2013 at 6:27 PM, Dave Lester  >wrote:
>
> > Hi All,
> >
> > We're pleased to share a draft ASF incubation proposal for Aurora, a
> > service scheduler used to schedule jobs onto Apache Mesos that we've
> > developed at Twitter. Aurora provides all of the primitives necessary to
> > quickly deploy and scale stateless and fault tolerant services in a
> > datacenter. The complete proposal can be found:
> > https://wiki.apache.org/incubator/AuroraProposal, and also pasted below.
> >
> > In particular, we'd love to add additional mentors to the project. Your
> > feedback is appreciated.
> >
> > Dave
> >
> > = Abstract =
> >
> > Aurora is a service scheduler used to schedule jobs onto Apache Mesos.
> >
> > = Proposal =
> >
> > Aurora is a scheduler that provides all of the primitives necessary to
> > quickly deploy and scale stateless and fault tolerant services in a
> > datacenter.
> >
> > Aurora builds on top of Apache Mesos and provides common features that
> > allow any site to run large scale production applications. While the
> > project is currently used in production at Twitter, we wish to develop a
> > community to increase contributions and see it thrive in the future.
> >
> > = Background =
> >
> > The initial development of Aurora was done at Twitter, and is planned to
> be
> > open sourced. This proposal is for Aurora to join the Apache Incubator.
> >
> > = Rationale =
> >
> > While the Apache Mesos core focuses on distributing individual tasks
> across
> > nodes in a cluster, typical services consist of dozens or hundreds of
> > replicas of tasks. As a service scheduler, Aurora provides the
> abstraction
> > of a "job" to bundle and manage these tasks. Aurora provides many key
> > functionalities centered around a job, including: definition, the concept
> > of an instance and the serverset, deployment and scheduling, health
> > checking, and introspection. It also allows cross-cutting concerns to be
> > handled like observability and log collection.
> >
> > = Current Status =
> >
> > == Meritocracy ==
> >
> > By submitting this incubator proposal, we’re expressing our intent to
> build
> > a diverse developer community around Aurora that will conduct itself
> > according to The Apache Way and use meritocratic means of accepting
> > contributions. Several members of the Aurora team overlap with Apache
> > Mesos, which successfully graduated from the Incubator and has embraced a
> > meritocratic model of governance; we plan to follow a similar path
> forward
> > with Aurora and believe that a synergy between both projects will make
> this
> > even easier.
> >
> > == Community ==
> >
> > Aurora is currently being used internally at Twitter. By open sourcing
> the
> > project, we hope to extend our contributor base significantly and create
> a
> > vibrant community around the project.
> >
> > == Core Developers ==
> >
> > Aurora is currently being developed by a team of seven engineers at
> > Twitter.
> >
> > == Alignment ==
> >
> > The ASF is a natural choice to host the Aurora project, given the goal of
> > open sourcing the project and fostering a community to grow and support
> the
> > software. Additionally, Aurora integrates with Apache Mesos, and Apache
> > ZooKeeper for service discovery.
> >
> > We believe that inclusion within Apache will build stronger ties between
> > these projects, and create further alignment between their goals and
> > communities.
> >
> > = Known Risks =
> >
> > == Orphaned Products ==
> >
> > The core developers plan to continue working full time on the project,
> and
> > there is very little risk of Aurora being abandoned since it is running
> > hundreds of services as part of Twitter’s infrastructure. Additionally,
> > members of the Mesos community beyond Twitter have expressed interest in
> an
> > advanced scheduler like Aurora (see “Interested Parties” section); we
> > believe that need will drive some of the community involvement necessary
> > for the project to incubate successfully.
> >
> > == Inexperience with Open Source ==
> >
> > Initial Aurora committers have varying levels of experience using and
> > contributing to Open Source projects, however by working with our mentors
> > and the Apache community we believe we will be able to conduct ourselves
> in
> > accordance with Apache Incubator gu

Re: [PROPOSAL] Aurora for Incubation

[Dave Lester]

Hi Henry,

Great question. Multiple schedulers are actively being developed for Mesos,
including Aurora by Twitter, Chronos by Airbnb (
http://nerds.airbnb.com/introducing-chronos/), one called Marathon that I
understand will be open sourced in the future, and I've spoken with several
different folks at meetups who are developing their own. There is some
overlap between these schedulers, but they also meet different use-cases so
I still think it makes sense to create Aurora as a separate Apache project
from the Mesos core.

It's also worth noting (and perhaps this is something to highlight in the
proposal itself) that a scheduler like Aurora could potentially be used
with other systems should the community wish to pursue that development in
the future.

Dave


On Mon, Aug 26, 2013 at 3:55 PM, Henry Saputra wrote:

> Hi Dave,
>
> This looks like interesting project and good contributions from Twitter
> engineering.
>
> But given that close relationship with Apache Mesos, wouldn't it be more
> effective to be delivered as extension or feature contribution to Apache
> Mesos?
>
>
> - Henry
>
>
> On Mon, Aug 26, 2013 at 3:27 PM, Dave Lester wrote:
>
>> Hi All,
>>
>> We're pleased to share a draft ASF incubation proposal for Aurora, a
>> service scheduler used to schedule jobs onto Apache Mesos that we've
>> developed at Twitter. Aurora provides all of the primitives necessary to
>> quickly deploy and scale stateless and fault tolerant services in a
>> datacenter. The complete proposal can be found:
>> https://wiki.apache.org/incubator/AuroraProposal, and also pasted below.
>>
>> In particular, we'd love to add additional mentors to the project. Your
>> feedback is appreciated.
>>
>> Dave
>>
>> = Abstract =
>>
>> Aurora is a service scheduler used to schedule jobs onto Apache Mesos.
>>
>> = Proposal =
>>
>> Aurora is a scheduler that provides all of the primitives necessary to
>> quickly deploy and scale stateless and fault tolerant services in a
>> datacenter.
>>
>> Aurora builds on top of Apache Mesos and provides common features that
>> allow any site to run large scale production applications. While the
>> project is currently used in production at Twitter, we wish to develop a
>> community to increase contributions and see it thrive in the future.
>>
>> = Background =
>>
>> The initial development of Aurora was done at Twitter, and is planned to
>> be
>> open sourced. This proposal is for Aurora to join the Apache Incubator.
>>
>> = Rationale =
>>
>> While the Apache Mesos core focuses on distributing individual tasks
>> across
>> nodes in a cluster, typical services consist of dozens or hundreds of
>> replicas of tasks. As a service scheduler, Aurora provides the abstraction
>> of a "job" to bundle and manage these tasks. Aurora provides many key
>> functionalities centered around a job, including: definition, the concept
>> of an instance and the serverset, deployment and scheduling, health
>> checking, and introspection. It also allows cross-cutting concerns to be
>> handled like observability and log collection.
>>
>> = Current Status =
>>
>> == Meritocracy ==
>>
>> By submitting this incubator proposal, we’re expressing our intent to
>> build
>> a diverse developer community around Aurora that will conduct itself
>> according to The Apache Way and use meritocratic means of accepting
>> contributions. Several members of the Aurora team overlap with Apache
>> Mesos, which successfully graduated from the Incubator and has embraced a
>> meritocratic model of governance; we plan to follow a similar path forward
>> with Aurora and believe that a synergy between both projects will make
>> this
>> even easier.
>>
>> == Community ==
>>
>> Aurora is currently being used internally at Twitter. By open sourcing the
>> project, we hope to extend our contributor base significantly and create a
>> vibrant community around the project.
>>
>> == Core Developers ==
>>
>> Aurora is currently being developed by a team of seven engineers at
>> Twitter.
>>
>> == Alignment ==
>>
>> The ASF is a natural choice to host the Aurora project, given the goal of
>> open sourcing the project and fostering a community to grow and support
>> the
>> software. Additionally, Aurora integrates with Apache Mesos, and Apache
>> ZooKeeper for service discovery.
>>
>> We believe that inclusion within Apache will build stronger ties between
>> these projects, and create further alignment between their goals and
>> communities.
>>
>> = Known Risks =
>>
>> == Orphaned Products ==
>>
>> The core developers plan to continue working full time on the project, and
>> there is very little risk of Aurora being abandoned since it is running
>> hundreds of services as part of Twitter’s infrastructure. Additionally,
>> members of the Mesos community beyond Twitter have expressed interest in
>> an
>> advanced scheduler like Aurora (see “Interested Parties” section); we
>> believe that need will drive some of the community involvement necessary
>> for the pr

Re: [PROPOSAL] Aurora for Incubation

[Henry Saputra]

HI Dave, thanks for your reply.

Yeah I think it would be super useful to highlight ability to use Aurora
with other systems.

Another question: looks like from the proposal, it does not rely on Mesos
library as external dependencies at all?

Like other incubator projects, would you consider not having aurora-user
and aurora-issues lists at the beginning of incubation?
I think we would like to have dev list as the main list to have development
discussion in the early phase of incubation (other IPMCs probably
would recommend the same)


Thanks again,

- Henry


On Mon, Aug 26, 2013 at 4:13 PM, Dave Lester wrote:

> Hi Henry,
>
> Great question. Multiple schedulers are actively being developed for
> Mesos, including Aurora by Twitter, Chronos by Airbnb (
> http://nerds.airbnb.com/introducing-chronos/), one called Marathon that I
> understand will be open sourced in the future, and I've spoken with several
> different folks at meetups who are developing their own. There is some
> overlap between these schedulers, but they also meet different use-cases so
> I still think it makes sense to create Aurora as a separate Apache project
> from the Mesos core.
>
> It's also worth noting (and perhaps this is something to highlight in the
> proposal itself) that a scheduler like Aurora could potentially be used
> with other systems should the community wish to pursue that development in
> the future.
>
> Dave
>
>
> On Mon, Aug 26, 2013 at 3:55 PM, Henry Saputra wrote:
>
>> Hi Dave,
>>
>> This looks like interesting project and good contributions from Twitter
>> engineering.
>>
>> But given that close relationship with Apache Mesos, wouldn't it be more
>> effective to be delivered as extension or feature contribution to Apache
>> Mesos?
>>
>>
>> - Henry
>>
>>
>> On Mon, Aug 26, 2013 at 3:27 PM, Dave Lester 
>> wrote:
>>
>>> Hi All,
>>>
>>> We're pleased to share a draft ASF incubation proposal for Aurora, a
>>> service scheduler used to schedule jobs onto Apache Mesos that we've
>>> developed at Twitter. Aurora provides all of the primitives necessary to
>>> quickly deploy and scale stateless and fault tolerant services in a
>>> datacenter. The complete proposal can be found:
>>> https://wiki.apache.org/incubator/AuroraProposal, and also pasted below.
>>>
>>> In particular, we'd love to add additional mentors to the project. Your
>>> feedback is appreciated.
>>>
>>> Dave
>>>
>>> = Abstract =
>>>
>>> Aurora is a service scheduler used to schedule jobs onto Apache Mesos.
>>>
>>> = Proposal =
>>>
>>> Aurora is a scheduler that provides all of the primitives necessary to
>>> quickly deploy and scale stateless and fault tolerant services in a
>>> datacenter.
>>>
>>> Aurora builds on top of Apache Mesos and provides common features that
>>> allow any site to run large scale production applications. While the
>>> project is currently used in production at Twitter, we wish to develop a
>>> community to increase contributions and see it thrive in the future.
>>>
>>> = Background =
>>>
>>> The initial development of Aurora was done at Twitter, and is planned to
>>> be
>>> open sourced. This proposal is for Aurora to join the Apache Incubator.
>>>
>>> = Rationale =
>>>
>>> While the Apache Mesos core focuses on distributing individual tasks
>>> across
>>> nodes in a cluster, typical services consist of dozens or hundreds of
>>> replicas of tasks. As a service scheduler, Aurora provides the
>>> abstraction
>>> of a "job" to bundle and manage these tasks. Aurora provides many key
>>> functionalities centered around a job, including: definition, the concept
>>> of an instance and the serverset, deployment and scheduling, health
>>> checking, and introspection. It also allows cross-cutting concerns to be
>>> handled like observability and log collection.
>>>
>>> = Current Status =
>>>
>>> == Meritocracy ==
>>>
>>> By submitting this incubator proposal, we’re expressing our intent to
>>> build
>>> a diverse developer community around Aurora that will conduct itself
>>> according to The Apache Way and use meritocratic means of accepting
>>> contributions. Several members of the Aurora team overlap with Apache
>>> Mesos, which successfully graduated from the Incubator and has embraced a
>>> meritocratic model of governance; we plan to follow a similar path
>>> forward
>>> with Aurora and believe that a synergy between both projects will make
>>> this
>>> even easier.
>>>
>>> == Community ==
>>>
>>> Aurora is currently being used internally at Twitter. By open sourcing
>>> the
>>> project, we hope to extend our contributor base significantly and create
>>> a
>>> vibrant community around the project.
>>>
>>> == Core Developers ==
>>>
>>> Aurora is currently being developed by a team of seven engineers at
>>> Twitter.
>>>
>>> == Alignment ==
>>>
>>> The ASF is a natural choice to host the Aurora project, given the goal of
>>> open sourcing the project and fostering a community to grow and support
>>> the
>>> software. Additionally, Aurora i

Re: [PROPOSAL] Aurora for Incubation

[Jean-Baptiste Onofré]

Hi guys,

the proposal is interesting.
Quick question: do you plan to focus only on Mesos, or create a kind of 
more global and standalone job scheduler ?


Regards
JB

On 08/27/2013 12:27 AM, Dave Lester wrote:

Hi All,

We're pleased to share a draft ASF incubation proposal for Aurora, a
service scheduler used to schedule jobs onto Apache Mesos that we've
developed at Twitter. Aurora provides all of the primitives necessary to
quickly deploy and scale stateless and fault tolerant services in a
datacenter. The complete proposal can be found:
https://wiki.apache.org/incubator/AuroraProposal, and also pasted below.

In particular, we'd love to add additional mentors to the project. Your
feedback is appreciated.

Dave

= Abstract =

Aurora is a service scheduler used to schedule jobs onto Apache Mesos.

= Proposal =

Aurora is a scheduler that provides all of the primitives necessary to
quickly deploy and scale stateless and fault tolerant services in a
datacenter.

Aurora builds on top of Apache Mesos and provides common features that
allow any site to run large scale production applications. While the
project is currently used in production at Twitter, we wish to develop a
community to increase contributions and see it thrive in the future.

= Background =

The initial development of Aurora was done at Twitter, and is planned to be
open sourced. This proposal is for Aurora to join the Apache Incubator.

= Rationale =

While the Apache Mesos core focuses on distributing individual tasks across
nodes in a cluster, typical services consist of dozens or hundreds of
replicas of tasks. As a service scheduler, Aurora provides the abstraction
of a "job" to bundle and manage these tasks. Aurora provides many key
functionalities centered around a job, including: definition, the concept
of an instance and the serverset, deployment and scheduling, health
checking, and introspection. It also allows cross-cutting concerns to be
handled like observability and log collection.

= Current Status =

== Meritocracy ==

By submitting this incubator proposal, we’re expressing our intent to build
a diverse developer community around Aurora that will conduct itself
according to The Apache Way and use meritocratic means of accepting
contributions. Several members of the Aurora team overlap with Apache
Mesos, which successfully graduated from the Incubator and has embraced a
meritocratic model of governance; we plan to follow a similar path forward
with Aurora and believe that a synergy between both projects will make this
even easier.

== Community ==

Aurora is currently being used internally at Twitter. By open sourcing the
project, we hope to extend our contributor base significantly and create a
vibrant community around the project.

== Core Developers ==

Aurora is currently being developed by a team of seven engineers at Twitter.

== Alignment ==

The ASF is a natural choice to host the Aurora project, given the goal of
open sourcing the project and fostering a community to grow and support the
software. Additionally, Aurora integrates with Apache Mesos, and Apache
ZooKeeper for service discovery.

We believe that inclusion within Apache will build stronger ties between
these projects, and create further alignment between their goals and
communities.

= Known Risks =

== Orphaned Products ==

The core developers plan to continue working full time on the project, and
there is very little risk of Aurora being abandoned since it is running
hundreds of services as part of Twitter’s infrastructure. Additionally,
members of the Mesos community beyond Twitter have expressed interest in an
advanced scheduler like Aurora (see “Interested Parties” section); we
believe that need will drive some of the community involvement necessary
for the project to incubate successfully.

== Inexperience with Open Source ==

Initial Aurora committers have varying levels of experience using and
contributing to Open Source projects, however by working with our mentors
and the Apache community we believe we will be able to conduct ourselves in
accordance with Apache Incubator guidelines. The close relationship between
the Aurora team and Apache Mesos means there is an awareness of the
incubation process and a willingness to embrace The Apache Way.

== Homogenous Developers ==

The initial set of committers are from a single organization, however we
expect that once approved for incubation the project will attract
contributors from more organizations. We have already had conversations
with other companies who have expressed an interest in Aurora.

== Reliance on Salaried Developers ==

Initial Aurora committers are salaried developers at Twitter, however
shortly after open sourcing the code we plan to diversify the project’s
core committers and contributors.

== Relationships with Other Apache Products ==

Initially, Aurora has been developed as a scheduler for Apache Mesos.
Additionally, it relies on ZooKeeper for service discovery, allowing
servers t