[RESULT][VOTE] Accept Helix into Apache Incubator
Hello, Since 72 hours passed, I am closing the vote. Helix has been accepted for Apache Incubator with the following vote tally: +1 : 11 (8 binding) -1 : 0 Thanks, Kishore G Details: 1. Ted Dunning (binding) 2. Jakob Homan (binding) 3. Chris Douglas (binding) 4. Jukka Zitting (binding) 5. Roman Shaposhnik (non binding) 6. Patrick Hunt (binding) 7. Ahmed Radwan (non-binding) 8. Mahadev Konar (binding) 9. Suresh Maru (binding) 10. Bruno Mahe (non binding) 11. Olivier Lamy (binding)
Re: [VOTE] Accept Helix into Apache Incubator
Thanks Olivier for your interest. I am happy to have you as mentor. I am still having issues in editing the wiki, but will add you as mentor once I resolve it. thanks, Kishore G On Sat, Oct 13, 2012 at 7:38 AM, Olivier Lamy wrote: > +1 (binding). > Looks very interesting. Let me know if you need an other mentor for > the incubation. > > 2012/10/10 kishore g : >> Hi, >> >> I would like to call a vote for accepting Helix for incubation in the >> Apache Incubator. I have pasted the full proposal below. >> >> Please cast your vote: >> >> [ ] +1, bring Helix into Incubator >> [ ] +0, I don't care either way, >> [ ] -1, do not bring Helix into Incubator, because ... >> >> This vote will be open for 72 hours and only votes from the Incubator >> PMC are binding. >> >> Thanks, >> Kishore G >> >> >> == Abstract == >> Helix is a cluster management system for managing partitioned and >> replicated resources in distributed data systems. >> >> == Proposal == >> Helix provides an abstraction that separates coordination and >> management tasks from functional tasks of a distributed system. The >> developer defines the system behavior via a state machine, the >> transitions between those states, and constraints on states and >> transitions that govern the system’s valid settings. Helix ensures the >> distributed system satisfies the state machine, controlling state >> changes as appropriate during common operational activities such as >> upgrades, component failures, bootstrapping, running maintenance >> tasks, and adding capacity. >> >> == Background == >> Helix was developed at LinkedIn to manage large clusters for several >> diverse applications, including a distributed, partitioned, >> replicated, highly available document store with a master-slave model, >> a search service with multiple replicas that are updated atomically >> and in near real-time, and a change data capture service for reliably >> transporting database changes to caches, other dependent databases and >> indexes. >> >> These services use Helix to reliably manage dozens of clusters in >> multiple data centers. These services meet stringent SLAs at large >> scale for mission-critical production applications such as search, >> social gestures, and profiles. >> Helix has proven to be flexible for a wide variety of system >> configurations and operational patterns, is easy to integrate, with >> pluggable interfaces enabling custom behavior. It depends on Apache >> Zookeeper for coordination and tracking of system state across the >> cluster, as well as providing fault tolerance. >> Helix is written in Java. It was developed internally at LinkedIn to >> meet our particular use cases, but will be useful to many >> organizations facing a similar need to manage large clusters. >> Therefore, we would like to share it the ASF and begin developing a >> community of developers and users within Apache. >> >> == Rationale == >> Many organizations can benefit from a generalized cluster management >> system such as Helix. While our distributed data systems use-cases for >> a very large website like LinkedIn has driven the design of Helix, its >> uses are varied and we expect many new use cases to emerge. >> >> == Current Status == >> === Meritocracy === >> Our intent with this incubator proposal is to start building a diverse >> developer community around Helix following the Apache meritocracy >> model. Since Helix was initially developed in late 2011, we have had >> fast adoption and contributions by multiple teams at LinkedIn. >> We plan to continue support for new contributors and work with those >> who contribute significantly to the project to make them committers. >> >> === Community === >> Helix is currently being used internally at LinkedIn and is in >> production in that company for customer-facing features. Recent public >> presentations of Helix and its goals garnered much interest from >> potential contributors. We hope to extend our contributor base >> significantly and invite all those who are interested in building >> large-scale distributed systems to participate. >> To further this goal, we use GitHub issue tracking and branching facilities. >> >> === Core Developers === >> Helix is currently being developed by three engineers at LinkedIn: >> Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, >> an engineer at Trifacta. Kishore, the lead developer and architect, >> has experience within Apache as an S4 committer. Shi developed the >> partition to node mapping and rebalancing algorithm, cluster admin >> APIs, and the health check framework. Jason developed the cluster >> controller and most of the test framework. Adam developed the rich >> alerting framework that enables cluster-wide, “intelligent“ alerts. >> >> === Alignment === >> The ASF is the natural choice to host the Helix project as its goal of >> encouraging community-driven open-source projects fits with our vision >> for Helix. Many projects that can benefit from He
Re: [VOTE] Accept Helix into Apache Incubator
+1 (binding). Looks very interesting. Let me know if you need an other mentor for the incubation. 2012/10/10 kishore g : > Hi, > > I would like to call a vote for accepting Helix for incubation in the > Apache Incubator. I have pasted the full proposal below. > > Please cast your vote: > > [ ] +1, bring Helix into Incubator > [ ] +0, I don't care either way, > [ ] -1, do not bring Helix into Incubator, because ... > > This vote will be open for 72 hours and only votes from the Incubator > PMC are binding. > > Thanks, > Kishore G > > > == Abstract == > Helix is a cluster management system for managing partitioned and > replicated resources in distributed data systems. > > == Proposal == > Helix provides an abstraction that separates coordination and > management tasks from functional tasks of a distributed system. The > developer defines the system behavior via a state machine, the > transitions between those states, and constraints on states and > transitions that govern the system’s valid settings. Helix ensures the > distributed system satisfies the state machine, controlling state > changes as appropriate during common operational activities such as > upgrades, component failures, bootstrapping, running maintenance > tasks, and adding capacity. > > == Background == > Helix was developed at LinkedIn to manage large clusters for several > diverse applications, including a distributed, partitioned, > replicated, highly available document store with a master-slave model, > a search service with multiple replicas that are updated atomically > and in near real-time, and a change data capture service for reliably > transporting database changes to caches, other dependent databases and > indexes. > > These services use Helix to reliably manage dozens of clusters in > multiple data centers. These services meet stringent SLAs at large > scale for mission-critical production applications such as search, > social gestures, and profiles. > Helix has proven to be flexible for a wide variety of system > configurations and operational patterns, is easy to integrate, with > pluggable interfaces enabling custom behavior. It depends on Apache > Zookeeper for coordination and tracking of system state across the > cluster, as well as providing fault tolerance. > Helix is written in Java. It was developed internally at LinkedIn to > meet our particular use cases, but will be useful to many > organizations facing a similar need to manage large clusters. > Therefore, we would like to share it the ASF and begin developing a > community of developers and users within Apache. > > == Rationale == > Many organizations can benefit from a generalized cluster management > system such as Helix. While our distributed data systems use-cases for > a very large website like LinkedIn has driven the design of Helix, its > uses are varied and we expect many new use cases to emerge. > > == Current Status == > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Helix following the Apache meritocracy > model. Since Helix was initially developed in late 2011, we have had > fast adoption and contributions by multiple teams at LinkedIn. > We plan to continue support for new contributors and work with those > who contribute significantly to the project to make them committers. > > === Community === > Helix is currently being used internally at LinkedIn and is in > production in that company for customer-facing features. Recent public > presentations of Helix and its goals garnered much interest from > potential contributors. We hope to extend our contributor base > significantly and invite all those who are interested in building > large-scale distributed systems to participate. > To further this goal, we use GitHub issue tracking and branching facilities. > > === Core Developers === > Helix is currently being developed by three engineers at LinkedIn: > Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, > an engineer at Trifacta. Kishore, the lead developer and architect, > has experience within Apache as an S4 committer. Shi developed the > partition to node mapping and rebalancing algorithm, cluster admin > APIs, and the health check framework. Jason developed the cluster > controller and most of the test framework. Adam developed the rich > alerting framework that enables cluster-wide, “intelligent“ alerts. > > === Alignment === > The ASF is the natural choice to host the Helix project as its goal of > encouraging community-driven open-source projects fits with our vision > for Helix. Many projects that can benefit from Helix will rely on > Apache ZooKeeper for cluster state management, and can far more easily > achieve their operational goals by using Helix. > > == Known Risks == > === Orphaned Products === > The core developers plan to work full time on the project. There is > very little risk of Helix being abandoned as it is a critical part of > Link
Re: [VOTE] Accept Helix into Apache Incubator
On 10/10/2012 09:37 AM, kishore g wrote: Hi, I would like to call a vote for accepting Helix for incubation in the Apache Incubator. I have pasted the full proposal below. +1 (non binding) Thanks, Bruno - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Helix into Apache Incubator
+ 1 (binding), Good luck folks! Suresh On Oct 10, 2012, at 12:37 PM, kishore g wrote: > Hi, > > I would like to call a vote for accepting Helix for incubation in the > Apache Incubator. I have pasted the full proposal below. > > Please cast your vote: > > [ ] +1, bring Helix into Incubator > [ ] +0, I don't care either way, > [ ] -1, do not bring Helix into Incubator, because ... > > This vote will be open for 72 hours and only votes from the Incubator > PMC are binding. > > Thanks, > Kishore G > > > == Abstract == > Helix is a cluster management system for managing partitioned and > replicated resources in distributed data systems. > > == Proposal == > Helix provides an abstraction that separates coordination and > management tasks from functional tasks of a distributed system. The > developer defines the system behavior via a state machine, the > transitions between those states, and constraints on states and > transitions that govern the system’s valid settings. Helix ensures the > distributed system satisfies the state machine, controlling state > changes as appropriate during common operational activities such as > upgrades, component failures, bootstrapping, running maintenance > tasks, and adding capacity. > > == Background == > Helix was developed at LinkedIn to manage large clusters for several > diverse applications, including a distributed, partitioned, > replicated, highly available document store with a master-slave model, > a search service with multiple replicas that are updated atomically > and in near real-time, and a change data capture service for reliably > transporting database changes to caches, other dependent databases and > indexes. > > These services use Helix to reliably manage dozens of clusters in > multiple data centers. These services meet stringent SLAs at large > scale for mission-critical production applications such as search, > social gestures, and profiles. > Helix has proven to be flexible for a wide variety of system > configurations and operational patterns, is easy to integrate, with > pluggable interfaces enabling custom behavior. It depends on Apache > Zookeeper for coordination and tracking of system state across the > cluster, as well as providing fault tolerance. > Helix is written in Java. It was developed internally at LinkedIn to > meet our particular use cases, but will be useful to many > organizations facing a similar need to manage large clusters. > Therefore, we would like to share it the ASF and begin developing a > community of developers and users within Apache. > > == Rationale == > Many organizations can benefit from a generalized cluster management > system such as Helix. While our distributed data systems use-cases for > a very large website like LinkedIn has driven the design of Helix, its > uses are varied and we expect many new use cases to emerge. > > == Current Status == > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Helix following the Apache meritocracy > model. Since Helix was initially developed in late 2011, we have had > fast adoption and contributions by multiple teams at LinkedIn. > We plan to continue support for new contributors and work with those > who contribute significantly to the project to make them committers. > > === Community === > Helix is currently being used internally at LinkedIn and is in > production in that company for customer-facing features. Recent public > presentations of Helix and its goals garnered much interest from > potential contributors. We hope to extend our contributor base > significantly and invite all those who are interested in building > large-scale distributed systems to participate. > To further this goal, we use GitHub issue tracking and branching facilities. > > === Core Developers === > Helix is currently being developed by three engineers at LinkedIn: > Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, > an engineer at Trifacta. Kishore, the lead developer and architect, > has experience within Apache as an S4 committer. Shi developed the > partition to node mapping and rebalancing algorithm, cluster admin > APIs, and the health check framework. Jason developed the cluster > controller and most of the test framework. Adam developed the rich > alerting framework that enables cluster-wide, “intelligent“ alerts. > > === Alignment === > The ASF is the natural choice to host the Helix project as its goal of > encouraging community-driven open-source projects fits with our vision > for Helix. Many projects that can benefit from Helix will rely on > Apache ZooKeeper for cluster state management, and can far more easily > achieve their operational goals by using Helix. > > == Known Risks == > === Orphaned Products === > The core developers plan to work full time on the project. There is > very little risk of Helix being abandoned as it is a critical part of > LinkedIn's internal
Re: [VOTE] Accept Helix into Apache Incubator
+1 binding. On Wed, Oct 10, 2012 at 1:32 PM, Ted Dunning wrote: > +1 (binding) > > On Wed, Oct 10, 2012 at 9:37 AM, kishore g wrote: > >> Hi, >> >> I would like to call a vote for accepting Helix for incubation in the >> Apache Incubator. I have pasted the full proposal below. >> >> Please cast your vote: >> >> [ ] +1, bring Helix into Incubator >> [ ] +0, I don't care either way, >> [ ] -1, do not bring Helix into Incubator, because ... >> >> This vote will be open for 72 hours and only votes from the Incubator >> PMC are binding. >> >> Thanks, >> Kishore G >> >> >> == Abstract == >> Helix is a cluster management system for managing partitioned and >> replicated resources in distributed data systems. >> >> == Proposal == >> Helix provides an abstraction that separates coordination and >> management tasks from functional tasks of a distributed system. The >> developer defines the system behavior via a state machine, the >> transitions between those states, and constraints on states and >> transitions that govern the system’s valid settings. Helix ensures the >> distributed system satisfies the state machine, controlling state >> changes as appropriate during common operational activities such as >> upgrades, component failures, bootstrapping, running maintenance >> tasks, and adding capacity. >> >> == Background == >> Helix was developed at LinkedIn to manage large clusters for several >> diverse applications, including a distributed, partitioned, >> replicated, highly available document store with a master-slave model, >> a search service with multiple replicas that are updated atomically >> and in near real-time, and a change data capture service for reliably >> transporting database changes to caches, other dependent databases and >> indexes. >> >> These services use Helix to reliably manage dozens of clusters in >> multiple data centers. These services meet stringent SLAs at large >> scale for mission-critical production applications such as search, >> social gestures, and profiles. >> Helix has proven to be flexible for a wide variety of system >> configurations and operational patterns, is easy to integrate, with >> pluggable interfaces enabling custom behavior. It depends on Apache >> Zookeeper for coordination and tracking of system state across the >> cluster, as well as providing fault tolerance. >> Helix is written in Java. It was developed internally at LinkedIn to >> meet our particular use cases, but will be useful to many >> organizations facing a similar need to manage large clusters. >> Therefore, we would like to share it the ASF and begin developing a >> community of developers and users within Apache. >> >> == Rationale == >> Many organizations can benefit from a generalized cluster management >> system such as Helix. While our distributed data systems use-cases for >> a very large website like LinkedIn has driven the design of Helix, its >> uses are varied and we expect many new use cases to emerge. >> >> == Current Status == >> === Meritocracy === >> Our intent with this incubator proposal is to start building a diverse >> developer community around Helix following the Apache meritocracy >> model. Since Helix was initially developed in late 2011, we have had >> fast adoption and contributions by multiple teams at LinkedIn. >> We plan to continue support for new contributors and work with those >> who contribute significantly to the project to make them committers. >> >> === Community === >> Helix is currently being used internally at LinkedIn and is in >> production in that company for customer-facing features. Recent public >> presentations of Helix and its goals garnered much interest from >> potential contributors. We hope to extend our contributor base >> significantly and invite all those who are interested in building >> large-scale distributed systems to participate. >> To further this goal, we use GitHub issue tracking and branching >> facilities. >> >> === Core Developers === >> Helix is currently being developed by three engineers at LinkedIn: >> Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, >> an engineer at Trifacta. Kishore, the lead developer and architect, >> has experience within Apache as an S4 committer. Shi developed the >> partition to node mapping and rebalancing algorithm, cluster admin >> APIs, and the health check framework. Jason developed the cluster >> controller and most of the test framework. Adam developed the rich >> alerting framework that enables cluster-wide, “intelligent“ alerts. >> >> === Alignment === >> The ASF is the natural choice to host the Helix project as its goal of >> encouraging community-driven open-source projects fits with our vision >> for Helix. Many projects that can benefit from Helix will rely on >> Apache ZooKeeper for cluster state management, and can far more easily >> achieve their operational goals by using Helix. >> >> == Known Risks == >> === Orphaned Products === >> The core developers plan t
Re: [VOTE] Accept Helix into Apache Incubator
[ ] +1, bring Helix into Incubator (non-binding) On Wed, Oct 10, 2012 at 9:37 AM, kishore g wrote: > Hi, > > I would like to call a vote for accepting Helix for incubation in the > Apache Incubator. I have pasted the full proposal below. > > Please cast your vote: > > [ ] +1, bring Helix into Incubator > [ ] +0, I don't care either way, > [ ] -1, do not bring Helix into Incubator, because ... > > This vote will be open for 72 hours and only votes from the Incubator > PMC are binding. > > Thanks, > Kishore G > > > == Abstract == > Helix is a cluster management system for managing partitioned and > replicated resources in distributed data systems. > > == Proposal == > Helix provides an abstraction that separates coordination and > management tasks from functional tasks of a distributed system. The > developer defines the system behavior via a state machine, the > transitions between those states, and constraints on states and > transitions that govern the system’s valid settings. Helix ensures the > distributed system satisfies the state machine, controlling state > changes as appropriate during common operational activities such as > upgrades, component failures, bootstrapping, running maintenance > tasks, and adding capacity. > > == Background == > Helix was developed at LinkedIn to manage large clusters for several > diverse applications, including a distributed, partitioned, > replicated, highly available document store with a master-slave model, > a search service with multiple replicas that are updated atomically > and in near real-time, and a change data capture service for reliably > transporting database changes to caches, other dependent databases and > indexes. > > These services use Helix to reliably manage dozens of clusters in > multiple data centers. These services meet stringent SLAs at large > scale for mission-critical production applications such as search, > social gestures, and profiles. > Helix has proven to be flexible for a wide variety of system > configurations and operational patterns, is easy to integrate, with > pluggable interfaces enabling custom behavior. It depends on Apache > Zookeeper for coordination and tracking of system state across the > cluster, as well as providing fault tolerance. > Helix is written in Java. It was developed internally at LinkedIn to > meet our particular use cases, but will be useful to many > organizations facing a similar need to manage large clusters. > Therefore, we would like to share it the ASF and begin developing a > community of developers and users within Apache. > > == Rationale == > Many organizations can benefit from a generalized cluster management > system such as Helix. While our distributed data systems use-cases for > a very large website like LinkedIn has driven the design of Helix, its > uses are varied and we expect many new use cases to emerge. > > == Current Status == > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Helix following the Apache meritocracy > model. Since Helix was initially developed in late 2011, we have had > fast adoption and contributions by multiple teams at LinkedIn. > We plan to continue support for new contributors and work with those > who contribute significantly to the project to make them committers. > > === Community === > Helix is currently being used internally at LinkedIn and is in > production in that company for customer-facing features. Recent public > presentations of Helix and its goals garnered much interest from > potential contributors. We hope to extend our contributor base > significantly and invite all those who are interested in building > large-scale distributed systems to participate. > To further this goal, we use GitHub issue tracking and branching facilities. > > === Core Developers === > Helix is currently being developed by three engineers at LinkedIn: > Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, > an engineer at Trifacta. Kishore, the lead developer and architect, > has experience within Apache as an S4 committer. Shi developed the > partition to node mapping and rebalancing algorithm, cluster admin > APIs, and the health check framework. Jason developed the cluster > controller and most of the test framework. Adam developed the rich > alerting framework that enables cluster-wide, “intelligent“ alerts. > > === Alignment === > The ASF is the natural choice to host the Helix project as its goal of > encouraging community-driven open-source projects fits with our vision > for Helix. Many projects that can benefit from Helix will rely on > Apache ZooKeeper for cluster state management, and can far more easily > achieve their operational goals by using Helix. > > == Known Risks == > === Orphaned Products === > The core developers plan to work full time on the project. There is > very little risk of Helix being abandoned as it is a critical part of > LinkedIn's internal infra
Re: [VOTE] Accept Helix into Apache Incubator
+1, bring Helix into Incubator (binding) Patrick On Wed, Oct 10, 2012 at 9:37 AM, kishore g wrote: > Hi, > > I would like to call a vote for accepting Helix for incubation in the > Apache Incubator. I have pasted the full proposal below. > > Please cast your vote: > > [ ] +1, bring Helix into Incubator > [ ] +0, I don't care either way, > [ ] -1, do not bring Helix into Incubator, because ... > > This vote will be open for 72 hours and only votes from the Incubator > PMC are binding. > > Thanks, > Kishore G > > > == Abstract == > Helix is a cluster management system for managing partitioned and > replicated resources in distributed data systems. > > == Proposal == > Helix provides an abstraction that separates coordination and > management tasks from functional tasks of a distributed system. The > developer defines the system behavior via a state machine, the > transitions between those states, and constraints on states and > transitions that govern the system’s valid settings. Helix ensures the > distributed system satisfies the state machine, controlling state > changes as appropriate during common operational activities such as > upgrades, component failures, bootstrapping, running maintenance > tasks, and adding capacity. > > == Background == > Helix was developed at LinkedIn to manage large clusters for several > diverse applications, including a distributed, partitioned, > replicated, highly available document store with a master-slave model, > a search service with multiple replicas that are updated atomically > and in near real-time, and a change data capture service for reliably > transporting database changes to caches, other dependent databases and > indexes. > > These services use Helix to reliably manage dozens of clusters in > multiple data centers. These services meet stringent SLAs at large > scale for mission-critical production applications such as search, > social gestures, and profiles. > Helix has proven to be flexible for a wide variety of system > configurations and operational patterns, is easy to integrate, with > pluggable interfaces enabling custom behavior. It depends on Apache > Zookeeper for coordination and tracking of system state across the > cluster, as well as providing fault tolerance. > Helix is written in Java. It was developed internally at LinkedIn to > meet our particular use cases, but will be useful to many > organizations facing a similar need to manage large clusters. > Therefore, we would like to share it the ASF and begin developing a > community of developers and users within Apache. > > == Rationale == > Many organizations can benefit from a generalized cluster management > system such as Helix. While our distributed data systems use-cases for > a very large website like LinkedIn has driven the design of Helix, its > uses are varied and we expect many new use cases to emerge. > > == Current Status == > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Helix following the Apache meritocracy > model. Since Helix was initially developed in late 2011, we have had > fast adoption and contributions by multiple teams at LinkedIn. > We plan to continue support for new contributors and work with those > who contribute significantly to the project to make them committers. > > === Community === > Helix is currently being used internally at LinkedIn and is in > production in that company for customer-facing features. Recent public > presentations of Helix and its goals garnered much interest from > potential contributors. We hope to extend our contributor base > significantly and invite all those who are interested in building > large-scale distributed systems to participate. > To further this goal, we use GitHub issue tracking and branching facilities. > > === Core Developers === > Helix is currently being developed by three engineers at LinkedIn: > Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, > an engineer at Trifacta. Kishore, the lead developer and architect, > has experience within Apache as an S4 committer. Shi developed the > partition to node mapping and rebalancing algorithm, cluster admin > APIs, and the health check framework. Jason developed the cluster > controller and most of the test framework. Adam developed the rich > alerting framework that enables cluster-wide, “intelligent“ alerts. > > === Alignment === > The ASF is the natural choice to host the Helix project as its goal of > encouraging community-driven open-source projects fits with our vision > for Helix. Many projects that can benefit from Helix will rely on > Apache ZooKeeper for cluster state management, and can far more easily > achieve their operational goals by using Helix. > > == Known Risks == > === Orphaned Products === > The core developers plan to work full time on the project. There is > very little risk of Helix being abandoned as it is a critical part of > LinkedIn's internal infr
Re: [VOTE] Accept Helix into Apache Incubator
On Wed, Oct 10, 2012 at 7:37 PM, kishore g wrote: > I would like to call a vote for accepting Helix for incubation in the > Apache Incubator. I have pasted the full proposal below. +1 (not binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Helix into Apache Incubator
Hi, On Wed, Oct 10, 2012 at 7:37 PM, kishore g wrote: > I would like to call a vote for accepting Helix for incubation in the > Apache Incubator. I have pasted the full proposal below. [x] +1, bring Helix into Incubator BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Helix into Apache Incubator
+1 (binding) -C On Wed, Oct 10, 2012 at 9:37 AM, kishore g wrote: > Hi, > > I would like to call a vote for accepting Helix for incubation in the > Apache Incubator. I have pasted the full proposal below. > > Please cast your vote: > > [ ] +1, bring Helix into Incubator > [ ] +0, I don't care either way, > [ ] -1, do not bring Helix into Incubator, because ... > > This vote will be open for 72 hours and only votes from the Incubator > PMC are binding. > > Thanks, > Kishore G > > > == Abstract == > Helix is a cluster management system for managing partitioned and > replicated resources in distributed data systems. > > == Proposal == > Helix provides an abstraction that separates coordination and > management tasks from functional tasks of a distributed system. The > developer defines the system behavior via a state machine, the > transitions between those states, and constraints on states and > transitions that govern the system’s valid settings. Helix ensures the > distributed system satisfies the state machine, controlling state > changes as appropriate during common operational activities such as > upgrades, component failures, bootstrapping, running maintenance > tasks, and adding capacity. > > == Background == > Helix was developed at LinkedIn to manage large clusters for several > diverse applications, including a distributed, partitioned, > replicated, highly available document store with a master-slave model, > a search service with multiple replicas that are updated atomically > and in near real-time, and a change data capture service for reliably > transporting database changes to caches, other dependent databases and > indexes. > > These services use Helix to reliably manage dozens of clusters in > multiple data centers. These services meet stringent SLAs at large > scale for mission-critical production applications such as search, > social gestures, and profiles. > Helix has proven to be flexible for a wide variety of system > configurations and operational patterns, is easy to integrate, with > pluggable interfaces enabling custom behavior. It depends on Apache > Zookeeper for coordination and tracking of system state across the > cluster, as well as providing fault tolerance. > Helix is written in Java. It was developed internally at LinkedIn to > meet our particular use cases, but will be useful to many > organizations facing a similar need to manage large clusters. > Therefore, we would like to share it the ASF and begin developing a > community of developers and users within Apache. > > == Rationale == > Many organizations can benefit from a generalized cluster management > system such as Helix. While our distributed data systems use-cases for > a very large website like LinkedIn has driven the design of Helix, its > uses are varied and we expect many new use cases to emerge. > > == Current Status == > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Helix following the Apache meritocracy > model. Since Helix was initially developed in late 2011, we have had > fast adoption and contributions by multiple teams at LinkedIn. > We plan to continue support for new contributors and work with those > who contribute significantly to the project to make them committers. > > === Community === > Helix is currently being used internally at LinkedIn and is in > production in that company for customer-facing features. Recent public > presentations of Helix and its goals garnered much interest from > potential contributors. We hope to extend our contributor base > significantly and invite all those who are interested in building > large-scale distributed systems to participate. > To further this goal, we use GitHub issue tracking and branching facilities. > > === Core Developers === > Helix is currently being developed by three engineers at LinkedIn: > Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, > an engineer at Trifacta. Kishore, the lead developer and architect, > has experience within Apache as an S4 committer. Shi developed the > partition to node mapping and rebalancing algorithm, cluster admin > APIs, and the health check framework. Jason developed the cluster > controller and most of the test framework. Adam developed the rich > alerting framework that enables cluster-wide, “intelligent“ alerts. > > === Alignment === > The ASF is the natural choice to host the Helix project as its goal of > encouraging community-driven open-source projects fits with our vision > for Helix. Many projects that can benefit from Helix will rely on > Apache ZooKeeper for cluster state management, and can far more easily > achieve their operational goals by using Helix. > > == Known Risks == > === Orphaned Products === > The core developers plan to work full time on the project. There is > very little risk of Helix being abandoned as it is a critical part of > LinkedIn's internal infrastructure and is in production us
Re: [VOTE] Accept Helix into Apache Incubator
Binding +1. On Wed, Oct 10, 2012 at 1:32 PM, Ted Dunning wrote: > +1 (binding) > > On Wed, Oct 10, 2012 at 9:37 AM, kishore g wrote: > >> Hi, >> >> I would like to call a vote for accepting Helix for incubation in the >> Apache Incubator. I have pasted the full proposal below. >> >> Please cast your vote: >> >> [ ] +1, bring Helix into Incubator >> [ ] +0, I don't care either way, >> [ ] -1, do not bring Helix into Incubator, because ... >> >> This vote will be open for 72 hours and only votes from the Incubator >> PMC are binding. >> >> Thanks, >> Kishore G >> >> >> == Abstract == >> Helix is a cluster management system for managing partitioned and >> replicated resources in distributed data systems. >> >> == Proposal == >> Helix provides an abstraction that separates coordination and >> management tasks from functional tasks of a distributed system. The >> developer defines the system behavior via a state machine, the >> transitions between those states, and constraints on states and >> transitions that govern the system’s valid settings. Helix ensures the >> distributed system satisfies the state machine, controlling state >> changes as appropriate during common operational activities such as >> upgrades, component failures, bootstrapping, running maintenance >> tasks, and adding capacity. >> >> == Background == >> Helix was developed at LinkedIn to manage large clusters for several >> diverse applications, including a distributed, partitioned, >> replicated, highly available document store with a master-slave model, >> a search service with multiple replicas that are updated atomically >> and in near real-time, and a change data capture service for reliably >> transporting database changes to caches, other dependent databases and >> indexes. >> >> These services use Helix to reliably manage dozens of clusters in >> multiple data centers. These services meet stringent SLAs at large >> scale for mission-critical production applications such as search, >> social gestures, and profiles. >> Helix has proven to be flexible for a wide variety of system >> configurations and operational patterns, is easy to integrate, with >> pluggable interfaces enabling custom behavior. It depends on Apache >> Zookeeper for coordination and tracking of system state across the >> cluster, as well as providing fault tolerance. >> Helix is written in Java. It was developed internally at LinkedIn to >> meet our particular use cases, but will be useful to many >> organizations facing a similar need to manage large clusters. >> Therefore, we would like to share it the ASF and begin developing a >> community of developers and users within Apache. >> >> == Rationale == >> Many organizations can benefit from a generalized cluster management >> system such as Helix. While our distributed data systems use-cases for >> a very large website like LinkedIn has driven the design of Helix, its >> uses are varied and we expect many new use cases to emerge. >> >> == Current Status == >> === Meritocracy === >> Our intent with this incubator proposal is to start building a diverse >> developer community around Helix following the Apache meritocracy >> model. Since Helix was initially developed in late 2011, we have had >> fast adoption and contributions by multiple teams at LinkedIn. >> We plan to continue support for new contributors and work with those >> who contribute significantly to the project to make them committers. >> >> === Community === >> Helix is currently being used internally at LinkedIn and is in >> production in that company for customer-facing features. Recent public >> presentations of Helix and its goals garnered much interest from >> potential contributors. We hope to extend our contributor base >> significantly and invite all those who are interested in building >> large-scale distributed systems to participate. >> To further this goal, we use GitHub issue tracking and branching >> facilities. >> >> === Core Developers === >> Helix is currently being developed by three engineers at LinkedIn: >> Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, >> an engineer at Trifacta. Kishore, the lead developer and architect, >> has experience within Apache as an S4 committer. Shi developed the >> partition to node mapping and rebalancing algorithm, cluster admin >> APIs, and the health check framework. Jason developed the cluster >> controller and most of the test framework. Adam developed the rich >> alerting framework that enables cluster-wide, “intelligent“ alerts. >> >> === Alignment === >> The ASF is the natural choice to host the Helix project as its goal of >> encouraging community-driven open-source projects fits with our vision >> for Helix. Many projects that can benefit from Helix will rely on >> Apache ZooKeeper for cluster state management, and can far more easily >> achieve their operational goals by using Helix. >> >> == Known Risks == >> === Orphaned Products === >> The core developers plan t
Re: [VOTE] Accept Helix into Apache Incubator
+1 (binding) On Wed, Oct 10, 2012 at 9:37 AM, kishore g wrote: > Hi, > > I would like to call a vote for accepting Helix for incubation in the > Apache Incubator. I have pasted the full proposal below. > > Please cast your vote: > > [ ] +1, bring Helix into Incubator > [ ] +0, I don't care either way, > [ ] -1, do not bring Helix into Incubator, because ... > > This vote will be open for 72 hours and only votes from the Incubator > PMC are binding. > > Thanks, > Kishore G > > > == Abstract == > Helix is a cluster management system for managing partitioned and > replicated resources in distributed data systems. > > == Proposal == > Helix provides an abstraction that separates coordination and > management tasks from functional tasks of a distributed system. The > developer defines the system behavior via a state machine, the > transitions between those states, and constraints on states and > transitions that govern the system’s valid settings. Helix ensures the > distributed system satisfies the state machine, controlling state > changes as appropriate during common operational activities such as > upgrades, component failures, bootstrapping, running maintenance > tasks, and adding capacity. > > == Background == > Helix was developed at LinkedIn to manage large clusters for several > diverse applications, including a distributed, partitioned, > replicated, highly available document store with a master-slave model, > a search service with multiple replicas that are updated atomically > and in near real-time, and a change data capture service for reliably > transporting database changes to caches, other dependent databases and > indexes. > > These services use Helix to reliably manage dozens of clusters in > multiple data centers. These services meet stringent SLAs at large > scale for mission-critical production applications such as search, > social gestures, and profiles. > Helix has proven to be flexible for a wide variety of system > configurations and operational patterns, is easy to integrate, with > pluggable interfaces enabling custom behavior. It depends on Apache > Zookeeper for coordination and tracking of system state across the > cluster, as well as providing fault tolerance. > Helix is written in Java. It was developed internally at LinkedIn to > meet our particular use cases, but will be useful to many > organizations facing a similar need to manage large clusters. > Therefore, we would like to share it the ASF and begin developing a > community of developers and users within Apache. > > == Rationale == > Many organizations can benefit from a generalized cluster management > system such as Helix. While our distributed data systems use-cases for > a very large website like LinkedIn has driven the design of Helix, its > uses are varied and we expect many new use cases to emerge. > > == Current Status == > === Meritocracy === > Our intent with this incubator proposal is to start building a diverse > developer community around Helix following the Apache meritocracy > model. Since Helix was initially developed in late 2011, we have had > fast adoption and contributions by multiple teams at LinkedIn. > We plan to continue support for new contributors and work with those > who contribute significantly to the project to make them committers. > > === Community === > Helix is currently being used internally at LinkedIn and is in > production in that company for customer-facing features. Recent public > presentations of Helix and its goals garnered much interest from > potential contributors. We hope to extend our contributor base > significantly and invite all those who are interested in building > large-scale distributed systems to participate. > To further this goal, we use GitHub issue tracking and branching > facilities. > > === Core Developers === > Helix is currently being developed by three engineers at LinkedIn: > Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, > an engineer at Trifacta. Kishore, the lead developer and architect, > has experience within Apache as an S4 committer. Shi developed the > partition to node mapping and rebalancing algorithm, cluster admin > APIs, and the health check framework. Jason developed the cluster > controller and most of the test framework. Adam developed the rich > alerting framework that enables cluster-wide, “intelligent“ alerts. > > === Alignment === > The ASF is the natural choice to host the Helix project as its goal of > encouraging community-driven open-source projects fits with our vision > for Helix. Many projects that can benefit from Helix will rely on > Apache ZooKeeper for cluster state management, and can far more easily > achieve their operational goals by using Helix. > > == Known Risks == > === Orphaned Products === > The core developers plan to work full time on the project. There is > very little risk of Helix being abandoned as it is a critical part of > LinkedIn's internal infrastructure and is in production us
[VOTE] Accept Helix into Apache Incubator
Hi, I would like to call a vote for accepting Helix for incubation in the Apache Incubator. I have pasted the full proposal below. Please cast your vote: [ ] +1, bring Helix into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Helix into Incubator, because ... This vote will be open for 72 hours and only votes from the Incubator PMC are binding. Thanks, Kishore G == Abstract == Helix is a cluster management system for managing partitioned and replicated resources in distributed data systems. == Proposal == Helix provides an abstraction that separates coordination and management tasks from functional tasks of a distributed system. The developer defines the system behavior via a state machine, the transitions between those states, and constraints on states and transitions that govern the system’s valid settings. Helix ensures the distributed system satisfies the state machine, controlling state changes as appropriate during common operational activities such as upgrades, component failures, bootstrapping, running maintenance tasks, and adding capacity. == Background == Helix was developed at LinkedIn to manage large clusters for several diverse applications, including a distributed, partitioned, replicated, highly available document store with a master-slave model, a search service with multiple replicas that are updated atomically and in near real-time, and a change data capture service for reliably transporting database changes to caches, other dependent databases and indexes. These services use Helix to reliably manage dozens of clusters in multiple data centers. These services meet stringent SLAs at large scale for mission-critical production applications such as search, social gestures, and profiles. Helix has proven to be flexible for a wide variety of system configurations and operational patterns, is easy to integrate, with pluggable interfaces enabling custom behavior. It depends on Apache Zookeeper for coordination and tracking of system state across the cluster, as well as providing fault tolerance. Helix is written in Java. It was developed internally at LinkedIn to meet our particular use cases, but will be useful to many organizations facing a similar need to manage large clusters. Therefore, we would like to share it the ASF and begin developing a community of developers and users within Apache. == Rationale == Many organizations can benefit from a generalized cluster management system such as Helix. While our distributed data systems use-cases for a very large website like LinkedIn has driven the design of Helix, its uses are varied and we expect many new use cases to emerge. == Current Status == === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around Helix following the Apache meritocracy model. Since Helix was initially developed in late 2011, we have had fast adoption and contributions by multiple teams at LinkedIn. We plan to continue support for new contributors and work with those who contribute significantly to the project to make them committers. === Community === Helix is currently being used internally at LinkedIn and is in production in that company for customer-facing features. Recent public presentations of Helix and its goals garnered much interest from potential contributors. We hope to extend our contributor base significantly and invite all those who are interested in building large-scale distributed systems to participate. To further this goal, we use GitHub issue tracking and branching facilities. === Core Developers === Helix is currently being developed by three engineers at LinkedIn: Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, an engineer at Trifacta. Kishore, the lead developer and architect, has experience within Apache as an S4 committer. Shi developed the partition to node mapping and rebalancing algorithm, cluster admin APIs, and the health check framework. Jason developed the cluster controller and most of the test framework. Adam developed the rich alerting framework that enables cluster-wide, “intelligent“ alerts. === Alignment === The ASF is the natural choice to host the Helix project as its goal of encouraging community-driven open-source projects fits with our vision for Helix. Many projects that can benefit from Helix will rely on Apache ZooKeeper for cluster state management, and can far more easily achieve their operational goals by using Helix. == Known Risks == === Orphaned Products === The core developers plan to work full time on the project. There is very little risk of Helix being abandoned as it is a critical part of LinkedIn's internal infrastructure and is in production use. === Inexperience with Open Source === Only one of the core developers has experience with open source development. Kishore has been actively involved with the ASF as a committer and lead developer of S4. === Homogeneous Developers === The current core d
