Re: [PROPOSAL] Zipkin for Apache Incubator
+1. It's great that Zipkin can be a part of Apache Incubator project. After going through the discussion here[1], I can see Zipkin leverage Github infrastructure a lot, we may need to figure out if we need to setup the user mailing list for this project. I agree with what John has said, you may consider twice for migration user discussion from github to apache mailing list. I think Skywalking may face the same issue, few people register the mailing list because lots of discussion happen in the github issues. I'd be happy to be the mentor of this project if you are interested.I guess there is still a room for additional mentor. As some part of my daily work[2] is based on the work of zipkin, I can devote more time on this project. [1] https://github.com/openzipkin/openzipkin.github.io/issues/51 [2] https://github.com/apache/incubator-servicecomb-saga Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Aug 17, 2018 at 5:29 PM, Adrian Cole wrote: > I would like to propose Zipkin as an Apache Incubator project. > > The text of the proposal can be found below as well as on the Incubator > wiki: > > https://wiki.apache.org/incubator/ZipkinProposal > > I believe we should have 3 mentors.. currently we have 2 (plus Wu > Sheng and I who are familiar but not mentor-grade :P). If another > person can volunteer to mentor us, would be sweet. > > -Adrian > > = Abstract = > Zipkin is a distributed tracing system. It helps gather timing data > needed to troubleshoot latency problems in microservice architectures. > It manages both the collection and lookup of this data. Zipkin’s > design is based on the Google Dapper paper. > > = Proposal = > Zipkin provides a defined data model and payload type for distributed > trace data collection. It also provides an UI and http api for > querying the data. Its server implements this api and includes > abstractions for storage and transport of trace payloads. The > combination of these parts avoid lock-in to a specific tracing > backend. For example, Zipkin includes integration with different open > source storage mechanisms like Apache Cassandra and Elasticsearch. It > also includes bridges to convert collected data and forward it to > service offerings such as Amazon X-Ray and Google Stackdriver. > Ecosystem offering extend this portability further. > > While primarily focused on the system, Zipkin also includes tracing > libraries which applications use to report timing information. > Zipkin's core organization includes tracer libraries written in Java, > Javascript, Go, PHP and Ruby. These libraries use the formats > mentioned above to report data, as well "B3" which is a header format > needed to send trace identifiers along with production requests. Many > Zipkin libraries can also send data directly to other services such as > Amazon X-Ray and Google Stackdriver, skipping any Zipkin > infrastructure. There are also more Zipkin tracing libraries outside > the core organization than inside it. This is due to the "OpenZipkin" > culture of promoting ecosystem work. > > = Background = > Zipkin began in 2012 at Twitter during a time they were investigating > performance problems underlying the "fail whale" seen by users. The > name Zipkin is from the Turkish word for harpoon: the harpoon that > will kill the failures! Incidentally, Zipkin was not the first tracing > system, it had roots in a former system at Twitter named > BigBrotherBird. It is due to BigBrotherBird that the de-facto tracing > headers we still use today include the prefix "X-B3". > > In 2015, a community of users noticed the project was not healthy in > so far as it hadn't progressed and often didn't accept pull requests, > and the Cassandra backend was stuck on an unmaintained library. For > example, the Apache Incubator H-Trace project started in some ways as > a reaction to the inability to customize the code. The root cause of > this was Twitter moving to internal storage (Manhattan) and also the > project not being managed as a product. By mid 2015, the community > regrouped as OpenZipkin and the codebase moved from Twitter to an org > also named OpenZipkin. This led to fast progress on concerns including > initially a server rewrite and Docker based deployment. > > In 2018, the second version of the data model completed, and along the > way, many new libraries became standard, including javascript, golang > and PHP. The community is dramatically larger than 2015, and Zipkin > remains the most popular tracing system despite heavy competition. > > = Rationale = > Zipkin is a de-facto distributed tracing system, which is more > important as architectures become more fine grained due to popularity > of microservice or even serverless architectures. Applications > transition to use more complex communication including asynchronous > code and service mesh, increasing the need for tools that visualize > the behavior of requests as they map across an architecture. > > Zipkin's server is focused only
Re: [PROPOSAL] Zipkin for Apache Incubator
+1 and exited since it sounds like the promise of a lot of communities interactions (skywalking, cxf, geronimo opentracing, ). Le sam. 18 août 2018 14:27, kristof.adriaenss...@gmail.com < kristof.adriaenss...@gmail.com> a écrit : > +1 Looks like a good move for the community based on the initial goals and > motivations as also mentioned here: > https://github.com/openzipkin/zipkin/issues/2152 > > On 2018/08/17 09:29:47, Adrian Cole wrote: > > I would like to propose Zipkin as an Apache Incubator project. > > > > The text of the proposal can be found below as well as on the Incubator > wiki: > > > > https://wiki.apache.org/incubator/ZipkinProposal > > > > I believe we should have 3 mentors.. currently we have 2 (plus Wu > > Sheng and I who are familiar but not mentor-grade :P). If another > > person can volunteer to mentor us, would be sweet. > > > > -Adrian > > > > = Abstract = > > Zipkin is a distributed tracing system. It helps gather timing data > > needed to troubleshoot latency problems in microservice architectures. > > It manages both the collection and lookup of this data. Zipkin’s > > design is based on the Google Dapper paper. > > > > = Proposal = > > Zipkin provides a defined data model and payload type for distributed > > trace data collection. It also provides an UI and http api for > > querying the data. Its server implements this api and includes > > abstractions for storage and transport of trace payloads. The > > combination of these parts avoid lock-in to a specific tracing > > backend. For example, Zipkin includes integration with different open > > source storage mechanisms like Apache Cassandra and Elasticsearch. It > > also includes bridges to convert collected data and forward it to > > service offerings such as Amazon X-Ray and Google Stackdriver. > > Ecosystem offering extend this portability further. > > > > While primarily focused on the system, Zipkin also includes tracing > > libraries which applications use to report timing information. > > Zipkin's core organization includes tracer libraries written in Java, > > Javascript, Go, PHP and Ruby. These libraries use the formats > > mentioned above to report data, as well "B3" which is a header format > > needed to send trace identifiers along with production requests. Many > > Zipkin libraries can also send data directly to other services such as > > Amazon X-Ray and Google Stackdriver, skipping any Zipkin > > infrastructure. There are also more Zipkin tracing libraries outside > > the core organization than inside it. This is due to the "OpenZipkin" > > culture of promoting ecosystem work. > > > > = Background = > > Zipkin began in 2012 at Twitter during a time they were investigating > > performance problems underlying the "fail whale" seen by users. The > > name Zipkin is from the Turkish word for harpoon: the harpoon that > > will kill the failures! Incidentally, Zipkin was not the first tracing > > system, it had roots in a former system at Twitter named > > BigBrotherBird. It is due to BigBrotherBird that the de-facto tracing > > headers we still use today include the prefix "X-B3". > > > > In 2015, a community of users noticed the project was not healthy in > > so far as it hadn't progressed and often didn't accept pull requests, > > and the Cassandra backend was stuck on an unmaintained library. For > > example, the Apache Incubator H-Trace project started in some ways as > > a reaction to the inability to customize the code. The root cause of > > this was Twitter moving to internal storage (Manhattan) and also the > > project not being managed as a product. By mid 2015, the community > > regrouped as OpenZipkin and the codebase moved from Twitter to an org > > also named OpenZipkin. This led to fast progress on concerns including > > initially a server rewrite and Docker based deployment. > > > > In 2018, the second version of the data model completed, and along the > > way, many new libraries became standard, including javascript, golang > > and PHP. The community is dramatically larger than 2015, and Zipkin > > remains the most popular tracing system despite heavy competition. > > > > = Rationale = > > Zipkin is a de-facto distributed tracing system, which is more > > important as architectures become more fine grained due to popularity > > of microservice or even serverless architectures. Applications > > transition to use more complex communication including asynchronous > > code and service mesh, increasing the need for tools that visualize > > the behavior of requests as they map across an architecture. > > > > Zipkin's server is focused only on distributed tracing. It is meant to > > be used alongside existing logging and metrics systems. Generally, the > > community optimizes brown field concerns such as interop over breaking > > changes such as experimental features. The combination of code and > > community make Zipkin a safe and easier choice for various sites to > > introduce or grow their
Re: [PROPOSAL] Zipkin for Apache Incubator
+1 Looks like a good move for the community based on the initial goals and motivations as also mentioned here: https://github.com/openzipkin/zipkin/issues/2152 On 2018/08/17 09:29:47, Adrian Cole wrote: > I would like to propose Zipkin as an Apache Incubator project. > > The text of the proposal can be found below as well as on the Incubator wiki: > > https://wiki.apache.org/incubator/ZipkinProposal > > I believe we should have 3 mentors.. currently we have 2 (plus Wu > Sheng and I who are familiar but not mentor-grade :P). If another > person can volunteer to mentor us, would be sweet. > > -Adrian > > = Abstract = > Zipkin is a distributed tracing system. It helps gather timing data > needed to troubleshoot latency problems in microservice architectures. > It manages both the collection and lookup of this data. Zipkin’s > design is based on the Google Dapper paper. > > = Proposal = > Zipkin provides a defined data model and payload type for distributed > trace data collection. It also provides an UI and http api for > querying the data. Its server implements this api and includes > abstractions for storage and transport of trace payloads. The > combination of these parts avoid lock-in to a specific tracing > backend. For example, Zipkin includes integration with different open > source storage mechanisms like Apache Cassandra and Elasticsearch. It > also includes bridges to convert collected data and forward it to > service offerings such as Amazon X-Ray and Google Stackdriver. > Ecosystem offering extend this portability further. > > While primarily focused on the system, Zipkin also includes tracing > libraries which applications use to report timing information. > Zipkin's core organization includes tracer libraries written in Java, > Javascript, Go, PHP and Ruby. These libraries use the formats > mentioned above to report data, as well "B3" which is a header format > needed to send trace identifiers along with production requests. Many > Zipkin libraries can also send data directly to other services such as > Amazon X-Ray and Google Stackdriver, skipping any Zipkin > infrastructure. There are also more Zipkin tracing libraries outside > the core organization than inside it. This is due to the "OpenZipkin" > culture of promoting ecosystem work. > > = Background = > Zipkin began in 2012 at Twitter during a time they were investigating > performance problems underlying the "fail whale" seen by users. The > name Zipkin is from the Turkish word for harpoon: the harpoon that > will kill the failures! Incidentally, Zipkin was not the first tracing > system, it had roots in a former system at Twitter named > BigBrotherBird. It is due to BigBrotherBird that the de-facto tracing > headers we still use today include the prefix "X-B3". > > In 2015, a community of users noticed the project was not healthy in > so far as it hadn't progressed and often didn't accept pull requests, > and the Cassandra backend was stuck on an unmaintained library. For > example, the Apache Incubator H-Trace project started in some ways as > a reaction to the inability to customize the code. The root cause of > this was Twitter moving to internal storage (Manhattan) and also the > project not being managed as a product. By mid 2015, the community > regrouped as OpenZipkin and the codebase moved from Twitter to an org > also named OpenZipkin. This led to fast progress on concerns including > initially a server rewrite and Docker based deployment. > > In 2018, the second version of the data model completed, and along the > way, many new libraries became standard, including javascript, golang > and PHP. The community is dramatically larger than 2015, and Zipkin > remains the most popular tracing system despite heavy competition. > > = Rationale = > Zipkin is a de-facto distributed tracing system, which is more > important as architectures become more fine grained due to popularity > of microservice or even serverless architectures. Applications > transition to use more complex communication including asynchronous > code and service mesh, increasing the need for tools that visualize > the behavior of requests as they map across an architecture. > > Zipkin's server is focused only on distributed tracing. It is meant to > be used alongside existing logging and metrics systems. Generally, the > community optimizes brown field concerns such as interop over breaking > changes such as experimental features. The combination of code and > community make Zipkin a safe and easier choice for various sites to > introduce or grow their observability practice. > > = Initial Goals = > The initial goals are to mature OpenZipkin's community process. For > example, while OpenZipkin has a good collaborative process, it lacks > formality around project management functions defined in the Apache > Software Foundation (ASF). We also seek out help with brand abuse > which is becoming common practice in the competitive landscape, yet >
Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.3 [RC3]
I checked the source.zip file data, it is same with the data with the tag, but the pom version was not same with the git repo as Mark already point out. I guess you did use the maven release plugin to do the latest release, as we cannot see the release plugin commit log there. After going through PPMC voting thread, there are several rounds of vote there, so I guess there may have some uncommitted change when doing the release. As we are doing the source release, it quit import that we ship the exactly source which is tagged to let the other user can do the same release without changing the code. @Jun Liu, could you double check that? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sat, Aug 18, 2018 at 5:56 AM, Mark Thomas wrote: > On 12/08/18 08:12, Jun Liu wrote: > > > > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [X] -1 disapprove with the reason (binding) > > The sha512 hashes are missing the '*' marker that indicates they are > hashes for binary files rather than text files. Trivial issue. Can be > addressed in the next release. > > I'd expect the files to be named "apache-dubbo..." not "dubbo...". Nice > to have (not all Apache projects use this naming convention). Something > to consider for the next release. > > Consider including mvnw and mvnw.cmd in the source release so it is > simpler to get started with the build from a source release. > > The 2.6.3 tag does not agree with the source release. This is a > significant issue and enough for me to vote against the release. A diff > shows most (all?) of the pom.xml have a version of "2.6.4-SNAPSHOT" in > the tag but "2.6.3" in the source release. > > I dug into this a little. At first I thought the tag / commit in the > vote was wrong. It is. But is isn't just that. If I go back to > > a8be0eaaddab198ed03b0150d4db03e2b22f023f > > things are better but: > a) there are still differences > b) the tag includes multiple commits after this point > > > Mark > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [PROPOSAL] Zipkin for Apache Incubator
As expressed many times through different channels, I am strong +1 to this. I think this new age at zipkin will be so beneficial for the community. On 2018/08/17 09:29:47, Adrian Cole wrote: > I would like to propose Zipkin as an Apache Incubator project.> > > The text of the proposal can be found below as well as on the Incubator wiki:> > > https://wiki.apache.org/incubator/ZipkinProposal> > > I believe we should have 3 mentors.. currently we have 2 (plus Wu> > Sheng and I who are familiar but not mentor-grade :P). If another> > person can volunteer to mentor us, would be sweet.> > > -Adrian> > > -- *José Carlos*
