Re: [RESULT] [VOTE] Accept TubeMQ into the Apache Incubator
Thanks Justin. I have requested the dev and private mailing list for TubeMQ already, will start from there. Thanks, Junping Justin Mclean 于2019年12月15日周日 上午8:21写道： > Hi, > > I’ve gone ahead and done this for you. Given this podling hasn’t > bootstrapped yet where is the conversation taking place about it? I would > suggest you create the mailing list and move the conversation there as soon > as you can. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [RESULT] [VOTE] Accept TubeMQ into the Apache Incubator
Hi, I’ve gone ahead and done this for you. Given this podling hasn’t bootstrapped yet where is the conversation taking place about it? I would suggest you create the mailing list and move the conversation there as soon as you can. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Accept TubeMQ into the Apache Incubator
Hi, > Can you point me where are the instructions to set up podling.xml? It in the mentor section [1] > I didn’t find any details here: > http://incubator.apache.org/cookbook/#podling_infrastructure_setup. Cookbook is a fairly need page and doesn’t;t include everything. Thanks, Justin 1. http://incubator.apache.org/guides/mentor.html#add_to_incubation_summary_file - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Accept TubeMQ into the Apache Incubator
Thanks Justin for reminding on this. Can you point me where are the instructions to set up podling.xml? I didn't find any details here: http://incubator.apache.org/cookbook/#podling_infrastructure_setup. Do I miss something? Thanks, Junping Justin Mclean 于2019年12月12日周四 上午7:01写道： > Hi, > > > Looks like infra/resource hasn't been setup for TubeMQ. I just open > > https://jira.apache.org/jira/browse/INFRA-19549 > > The podling needs to exist in the podling.xml file first, before the LDAP > and DNS can be created. > > Thanks, > Justin
Re: [RESULT] [VOTE] Accept TubeMQ into the Apache Incubator
Hi, > Looks like infra/resource hasn't been setup for TubeMQ. I just open > https://jira.apache.org/jira/browse/INFRA-19549 The podling needs to exist in the podling.xml file first, before the LDAP and DNS can be created. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Accept TubeMQ into the Apache Incubator
Looks like infra/resource hasn't been setup for TubeMQ. I just open https://jira.apache.org/jira/browse/INFRA-19549 Thanks, Junping David Nalley 于2019年11月3日周日 上午8:01写道： > Hi folks, > > I am happy to report that this vote is now closed and has passed > unanimously. > > 25 +1 (14 of which were binding) votes were cast. > > I am excited to welcome the TubeMQ community into the Apache Incubator. > > --David > > On Tue, Oct 29, 2019 at 9:48 PM David Nalley wrote: > > > > Hi folks, > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > Apache Incubator. > > > > Please cast your vote: > > > > [ ] +1, bring TubeMQ into the Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > The vote will open at least for 72 hours and only votes from the > > Incubator PMC are binding, but votes from everyone are welcome. > > > > =Abstract= > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > Tencent Big Data since 2013. It focuses on high-performance storage > > and transmission of massive data in big data scenarios.After nearly > > seven years of massive data precipitation, TubeMQ has certain > > advantages in production practice (stability + performance) and low > > cost compared to many open source MQ projects. > > > > =Proposal= > > > > TubeMQ is suitable for high concurrency, massive data and tolerates a > > small amount of data loss scenarios under abnormal conditions, such as > > massive log collection, indicator statistics and monitoring, etc. > > TubeMQ does not support highly reliable data transmission services > > yet. It could be on a future project roadmap, as many other MQs. but > > not today. > > > > =Rationale= > > > > Just like other message queue systems, TubeMQ is built on the > > publish-subscribe pattern, aka pub-sub. > > In this pattern, producers publish messages to topics while consumers > > subscribe to those topics. After incoming messages get proceeded, > > consumers send an acknowledgement back to producer. Once a > > subscription has been created, all messages will be tracked and > > retained by TubeMQ, even if the consumer go offline for some reasons. > > Retained messages will be discarded only when a consumer acknowledges > > that they've been successfully processed. > > > > Portal is responsible for interact with user and admin system which > > include two parts: API and web portal. > > > > Master is controller of the cluster, which include one or multiple > > master node(s) which is responsible for managing state of cluster, > > resource scheduling, authentication check and maintaining of metadata. > > As a reliable system, TubeMQ provides HA solution for master node. > > > > Broker is responsible for data store which include a cluster of broker > > nodes. Every broker node is managing a set of topics, include: append, > > delete, update, query of topic information. In TubeMQ, these brokers > > can be horizontal scaled and can be very large size for massive data > > case. > > > > Client is responsible for producing and consuming messages. When a > > pub-sub topic get setup, we can support two ways (push and pull) for > > delivering message from producers to consumers. > > > > Zookeeper is for storing offset of messages which is used to recover > > topic during some components get failed. > > > > > > =Initial Goals= > > > > The initial goal will be to move the current codebase in github’s > > repository under Tencent account to Apache and integrate with the > > Apache development process and infrastructure. > > A primary goal of incubation will be to grow and diversify the TubeMQ > > community. We are well aware that the project community is largely > > comprised of individuals from a single company. We aim to change that > > during incubation. > > > > =Current Status= > > > > As previously mentioned, TubeMQ is under active development at > > Tencent, and is being used in processing large volumes of data for > > most services and products. > > > > =Meritocracy= > > > > We value meritocracy and we understand that it is the basis for an > > open community that encourages multiple companies and individuals to > > contribute and be invested in the project’s future. We will encourage > > and monitor participation and make sure to extend privileges and > > responsibilities to all contributors. > > > > =Community= > > > > TubeMQ is currently being used by developers at Tencent and a growing > > number of users are actively using it in production environments. > > TubeMQ has received contributions from developers working outside of > > Tencent since it was open sourced on github in September 2019 By > > bringing TubeMQ to Apache we aim to assure current and future > > contributors that the TubeMQ community is neutral, meritocratic, and > > open, in order to broaden and diversity the user and developer > > community. > > > > =Core
Re: [RESULT] [VOTE] Accept TubeMQ into the Apache Incubator
Thank David for driving this progress and everyone to make it possible. Welcome the TubeMQ community into the Apache Incubator :-) Best, tison. David Nalley 于2019年11月3日周日 上午8:01写道： > Hi folks, > > I am happy to report that this vote is now closed and has passed > unanimously. > > 25 +1 (14 of which were binding) votes were cast. > > I am excited to welcome the TubeMQ community into the Apache Incubator. > > --David > > On Tue, Oct 29, 2019 at 9:48 PM David Nalley wrote: > > > > Hi folks, > > > > The [DISCUSS] thread on TubeMQ has died down. > > > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > > Apache Incubator. > > > > Please cast your vote: > > > > [ ] +1, bring TubeMQ into the Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring TubeMQ into the Incubator, because... > > > > The vote will open at least for 72 hours and only votes from the > > Incubator PMC are binding, but votes from everyone are welcome. > > > > =Abstract= > > > > TubeMQ is a distributed messaging queue (MQ) system developed by > > Tencent Big Data since 2013. It focuses on high-performance storage > > and transmission of massive data in big data scenarios.After nearly > > seven years of massive data precipitation, TubeMQ has certain > > advantages in production practice (stability + performance) and low > > cost compared to many open source MQ projects. > > > > =Proposal= > > > > TubeMQ is suitable for high concurrency, massive data and tolerates a > > small amount of data loss scenarios under abnormal conditions, such as > > massive log collection, indicator statistics and monitoring, etc. > > TubeMQ does not support highly reliable data transmission services > > yet. It could be on a future project roadmap, as many other MQs. but > > not today. > > > > =Rationale= > > > > Just like other message queue systems, TubeMQ is built on the > > publish-subscribe pattern, aka pub-sub. > > In this pattern, producers publish messages to topics while consumers > > subscribe to those topics. After incoming messages get proceeded, > > consumers send an acknowledgement back to producer. Once a > > subscription has been created, all messages will be tracked and > > retained by TubeMQ, even if the consumer go offline for some reasons. > > Retained messages will be discarded only when a consumer acknowledges > > that they've been successfully processed. > > > > Portal is responsible for interact with user and admin system which > > include two parts: API and web portal. > > > > Master is controller of the cluster, which include one or multiple > > master node(s) which is responsible for managing state of cluster, > > resource scheduling, authentication check and maintaining of metadata. > > As a reliable system, TubeMQ provides HA solution for master node. > > > > Broker is responsible for data store which include a cluster of broker > > nodes. Every broker node is managing a set of topics, include: append, > > delete, update, query of topic information. In TubeMQ, these brokers > > can be horizontal scaled and can be very large size for massive data > > case. > > > > Client is responsible for producing and consuming messages. When a > > pub-sub topic get setup, we can support two ways (push and pull) for > > delivering message from producers to consumers. > > > > Zookeeper is for storing offset of messages which is used to recover > > topic during some components get failed. > > > > > > =Initial Goals= > > > > The initial goal will be to move the current codebase in github’s > > repository under Tencent account to Apache and integrate with the > > Apache development process and infrastructure. > > A primary goal of incubation will be to grow and diversify the TubeMQ > > community. We are well aware that the project community is largely > > comprised of individuals from a single company. We aim to change that > > during incubation. > > > > =Current Status= > > > > As previously mentioned, TubeMQ is under active development at > > Tencent, and is being used in processing large volumes of data for > > most services and products. > > > > =Meritocracy= > > > > We value meritocracy and we understand that it is the basis for an > > open community that encourages multiple companies and individuals to > > contribute and be invested in the project’s future. We will encourage > > and monitor participation and make sure to extend privileges and > > responsibilities to all contributors. > > > > =Community= > > > > TubeMQ is currently being used by developers at Tencent and a growing > > number of users are actively using it in production environments. > > TubeMQ has received contributions from developers working outside of > > Tencent since it was open sourced on github in September 2019 By > > bringing TubeMQ to Apache we aim to assure current and future > > contributors that the TubeMQ community is neutral, meritocratic, and > > open, in order to broaden and diversity the user and developer > > community. >
[RESULT] [VOTE] Accept TubeMQ into the Apache Incubator
Hi folks, I am happy to report that this vote is now closed and has passed unanimously. 25 +1 (14 of which were binding) votes were cast. I am excited to welcome the TubeMQ community into the Apache Incubator. --David On Tue, Oct 29, 2019 at 9:48 PM David Nalley wrote: > > Hi folks, > > The [DISCUSS] thread on TubeMQ has died down. > > Accordingly, I would like to call a VOTE to accept TubeMQ into the > Apache Incubator. > > Please cast your vote: > > [ ] +1, bring TubeMQ into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring TubeMQ into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > =Abstract= > > TubeMQ is a distributed messaging queue (MQ) system developed by > Tencent Big Data since 2013. It focuses on high-performance storage > and transmission of massive data in big data scenarios.After nearly > seven years of massive data precipitation, TubeMQ has certain > advantages in production practice (stability + performance) and low > cost compared to many open source MQ projects. > > =Proposal= > > TubeMQ is suitable for high concurrency, massive data and tolerates a > small amount of data loss scenarios under abnormal conditions, such as > massive log collection, indicator statistics and monitoring, etc. > TubeMQ does not support highly reliable data transmission services > yet. It could be on a future project roadmap, as many other MQs. but > not today. > > =Rationale= > > Just like other message queue systems, TubeMQ is built on the > publish-subscribe pattern, aka pub-sub. > In this pattern, producers publish messages to topics while consumers > subscribe to those topics. After incoming messages get proceeded, > consumers send an acknowledgement back to producer. Once a > subscription has been created, all messages will be tracked and > retained by TubeMQ, even if the consumer go offline for some reasons. > Retained messages will be discarded only when a consumer acknowledges > that they've been successfully processed. > > Portal is responsible for interact with user and admin system which > include two parts: API and web portal. > > Master is controller of the cluster, which include one or multiple > master node(s) which is responsible for managing state of cluster, > resource scheduling, authentication check and maintaining of metadata. > As a reliable system, TubeMQ provides HA solution for master node. > > Broker is responsible for data store which include a cluster of broker > nodes. Every broker node is managing a set of topics, include: append, > delete, update, query of topic information. In TubeMQ, these brokers > can be horizontal scaled and can be very large size for massive data > case. > > Client is responsible for producing and consuming messages. When a > pub-sub topic get setup, we can support two ways (push and pull) for > delivering message from producers to consumers. > > Zookeeper is for storing offset of messages which is used to recover > topic during some components get failed. > > > =Initial Goals= > > The initial goal will be to move the current codebase in github’s > repository under Tencent account to Apache and integrate with the > Apache development process and infrastructure. > A primary goal of incubation will be to grow and diversify the TubeMQ > community. We are well aware that the project community is largely > comprised of individuals from a single company. We aim to change that > during incubation. > > =Current Status= > > As previously mentioned, TubeMQ is under active development at > Tencent, and is being used in processing large volumes of data for > most services and products. > > =Meritocracy= > > We value meritocracy and we understand that it is the basis for an > open community that encourages multiple companies and individuals to > contribute and be invested in the project’s future. We will encourage > and monitor participation and make sure to extend privileges and > responsibilities to all contributors. > > =Community= > > TubeMQ is currently being used by developers at Tencent and a growing > number of users are actively using it in production environments. > TubeMQ has received contributions from developers working outside of > Tencent since it was open sourced on github in September 2019 By > bringing TubeMQ to Apache we aim to assure current and future > contributors that the TubeMQ community is neutral, meritocratic, and > open, in order to broaden and diversity the user and developer > community. > > =Core Developers= > > TubeMQ was initially developed at Tencent and is under active > development. We believe Tencent will be of interest to a broad range > of users and developers and that incubating the project at the ASF > will help us build a diverse, sustainable community. > > =Alignment= > > TubeMQ utilizes other Apache projects such as Hadoop, HBase and > Zookeeper. We anticipate integration with ad
