[Dev] Moving CassandraLogProvider from carbon-utils to a different repo
Hi all, As a result of Simplifying Carbon Platform Logging Story Supporting Extending [1] the ability to plug any log provider to carbon server has been implemented [2]. This can be done by implementing the LogProvider interface and using logging-config.xml file to provide configurations needed to initialize the log provider implementation. Carbon log viewer will use this interface to get the LogEvents and show it on Log View UI. There has been some implementations already done and these log providers reside in carbon-utils repo [3]. One such log provider is CassandraLogProvider which can be used to provide logs from a cassandra instance. However since having this implementation in carbon-utils repo introduces dependencies on cassandra-thrift and hector-core we cannot keep this implementation in the carbon-utils. So where is the best place to keep this implementation since it is useful for many products? [1] https://wso2.org/jira/browse/COMMONS-110 [2] https://wso2.org/jira/browse/COMMONS-111 [3] https://github.com/shamrath/carbon-utils/tree/CircularBuffer_fix/components/logging/org.wso2.carbon.logging.service/src/main/java/org/wso2/carbon/logging/service/provider Thanks. /Gayashan -- *Gayashan Amarasinghe* Software Engineer | Platform TG WSO2, Inc. | http://wso2.com lean. enterprise. middleware Mobile : +94718314517 Blog : gayashan-a.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Moving CassandraLogProvider from carbon-utils to a different repo
Can it be moved to carbon-commons? On Tue, Sep 2, 2014 at 12:25 PM, Gayashan Amarasinghe gayas...@wso2.com wrote: Hi all, As a result of Simplifying Carbon Platform Logging Story Supporting Extending [1] the ability to plug any log provider to carbon server has been implemented [2]. This can be done by implementing the LogProvider interface and using logging-config.xml file to provide configurations needed to initialize the log provider implementation. Carbon log viewer will use this interface to get the LogEvents and show it on Log View UI. There has been some implementations already done and these log providers reside in carbon-utils repo [3]. One such log provider is CassandraLogProvider which can be used to provide logs from a cassandra instance. However since having this implementation in carbon-utils repo introduces dependencies on cassandra-thrift and hector-core we cannot keep this implementation in the carbon-utils. So where is the best place to keep this implementation since it is useful for many products? [1] https://wso2.org/jira/browse/COMMONS-110 [2] https://wso2.org/jira/browse/COMMONS-111 [3] https://github.com/shamrath/carbon-utils/tree/CircularBuffer_fix/components/logging/org.wso2.carbon.logging.service/src/main/java/org/wso2/carbon/logging/service/provider Thanks. /Gayashan -- *Gayashan Amarasinghe* Software Engineer | Platform TG WSO2, Inc. | http://wso2.com lean. enterprise. middleware Mobile : +94718314517 Blog : gayashan-a.blogspot.com -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez* http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Moving CassandraLogProvider from carbon-utils to a different repo
On Tue, Sep 2, 2014 at 1:20 PM, Afkham Azeez az...@wso2.com wrote: Can it be moved to carbon-commons? This means carbon-commons will depend on cassandra-thrift and hector-core, I don't think that as a good approach. AFAIK this is required for few products such as BAM, CEP, MB etc. so can't we move to a project common for those projects only ? Thanks ! On Tue, Sep 2, 2014 at 12:25 PM, Gayashan Amarasinghe gayas...@wso2.com wrote: Hi all, As a result of Simplifying Carbon Platform Logging Story Supporting Extending [1] the ability to plug any log provider to carbon server has been implemented [2]. This can be done by implementing the LogProvider interface and using logging-config.xml file to provide configurations needed to initialize the log provider implementation. Carbon log viewer will use this interface to get the LogEvents and show it on Log View UI. There has been some implementations already done and these log providers reside in carbon-utils repo [3]. One such log provider is CassandraLogProvider which can be used to provide logs from a cassandra instance. However since having this implementation in carbon-utils repo introduces dependencies on cassandra-thrift and hector-core we cannot keep this implementation in the carbon-utils. So where is the best place to keep this implementation since it is useful for many products? [1] https://wso2.org/jira/browse/COMMONS-110 [2] https://wso2.org/jira/browse/COMMONS-111 [3] https://github.com/shamrath/carbon-utils/tree/CircularBuffer_fix/components/logging/org.wso2.carbon.logging.service/src/main/java/org/wso2/carbon/logging/service/provider Thanks. /Gayashan -- *Gayashan Amarasinghe* Software Engineer | Platform TG WSO2, Inc. | http://wso2.com lean. enterprise. middleware Mobile : +94718314517 Blog : gayashan-a.blogspot.com -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919 blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez* http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Moving CassandraLogProvider from carbon-utils to a different repo
Shall we move it to carbon-storage-management repo since it contains all the cassandra related artifacts? On Tue, Sep 2, 2014 at 1:45 PM, Sagara Gunathunga sag...@wso2.com wrote: On Tue, Sep 2, 2014 at 1:20 PM, Afkham Azeez az...@wso2.com wrote: Can it be moved to carbon-commons? This means carbon-commons will depend on cassandra-thrift and hector-core, I don't think that as a good approach. AFAIK this is required for few products such as BAM, CEP, MB etc. so can't we move to a project common for those projects only ? Thanks ! On Tue, Sep 2, 2014 at 12:25 PM, Gayashan Amarasinghe gayas...@wso2.com wrote: Hi all, As a result of Simplifying Carbon Platform Logging Story Supporting Extending [1] the ability to plug any log provider to carbon server has been implemented [2]. This can be done by implementing the LogProvider interface and using logging-config.xml file to provide configurations needed to initialize the log provider implementation. Carbon log viewer will use this interface to get the LogEvents and show it on Log View UI. There has been some implementations already done and these log providers reside in carbon-utils repo [3]. One such log provider is CassandraLogProvider which can be used to provide logs from a cassandra instance. However since having this implementation in carbon-utils repo introduces dependencies on cassandra-thrift and hector-core we cannot keep this implementation in the carbon-utils. So where is the best place to keep this implementation since it is useful for many products? [1] https://wso2.org/jira/browse/COMMONS-110 [2] https://wso2.org/jira/browse/COMMONS-111 [3] https://github.com/shamrath/carbon-utils/tree/CircularBuffer_fix/components/logging/org.wso2.carbon.logging.service/src/main/java/org/wso2/carbon/logging/service/provider Thanks. /Gayashan -- *Gayashan Amarasinghe* Software Engineer | Platform TG WSO2, Inc. | http://wso2.com lean. enterprise. middleware Mobile : +94718314517 Blog : gayashan-a.blogspot.com -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919 blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez* http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Inosh Goonewardena Associate Technical Lead- WSO2 Inc. Mobile: +94779966317 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Moving CassandraLogProvider from carbon-utils to a different repo
Well, I don't think it's really the right move to have this added to carbon-storage-management repository. IMO, it has no meaning within the context of storage provisioning which is what carbon-storage-management primarily focuses on. CassandraLogProvider is some utility that's used across the platform right? If that's the case, it has to be added to some common repository, I believe. In addition to that, what CassandraLogProvider depends on (cassandra-thrift, hector-core, etc) is anyway not being maintained as part of carbon-storage-management repository. All considered, I believe, we should probably add this to some other appropriate location which is common for all components in the platform. Cheers, Prabath On Tue, Sep 2, 2014 at 2:29 PM, Inosh Goonewardena in...@wso2.com wrote: Shall we move it to carbon-storage-management repo since it contains all the cassandra related artifacts? On Tue, Sep 2, 2014 at 1:45 PM, Sagara Gunathunga sag...@wso2.com wrote: On Tue, Sep 2, 2014 at 1:20 PM, Afkham Azeez az...@wso2.com wrote: Can it be moved to carbon-commons? This means carbon-commons will depend on cassandra-thrift and hector-core, I don't think that as a good approach. AFAIK this is required for few products such as BAM, CEP, MB etc. so can't we move to a project common for those projects only ? Thanks ! On Tue, Sep 2, 2014 at 12:25 PM, Gayashan Amarasinghe gayas...@wso2.com wrote: Hi all, As a result of Simplifying Carbon Platform Logging Story Supporting Extending [1] the ability to plug any log provider to carbon server has been implemented [2]. This can be done by implementing the LogProvider interface and using logging-config.xml file to provide configurations needed to initialize the log provider implementation. Carbon log viewer will use this interface to get the LogEvents and show it on Log View UI. There has been some implementations already done and these log providers reside in carbon-utils repo [3]. One such log provider is CassandraLogProvider which can be used to provide logs from a cassandra instance. However since having this implementation in carbon-utils repo introduces dependencies on cassandra-thrift and hector-core we cannot keep this implementation in the carbon-utils. So where is the best place to keep this implementation since it is useful for many products? [1] https://wso2.org/jira/browse/COMMONS-110 [2] https://wso2.org/jira/browse/COMMONS-111 [3] https://github.com/shamrath/carbon-utils/tree/CircularBuffer_fix/components/logging/org.wso2.carbon.logging.service/src/main/java/org/wso2/carbon/logging/service/provider Thanks. /Gayashan -- *Gayashan Amarasinghe* Software Engineer | Platform TG WSO2, Inc. | http://wso2.com lean. enterprise. middleware Mobile : +94718314517 Blog : gayashan-a.blogspot.com -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919 blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez* http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Inosh Goonewardena Associate Technical Lead- WSO2 Inc. Mobile: +94779966317 -- Prabath Abeysekara Associate Technical Lead, Data TG. WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Moving CassandraLogProvider from carbon-utils to a different repo
Another fact is, this is not used only by BAM, CEP or MB. Any product which wishes to publish logs to Cassandra will use this. Correct me if I am wrong. So, this is a util to me. On Tue, Sep 2, 2014 at 7:15 PM, Prabath Abeysekera praba...@wso2.com wrote: Well, I don't think it's really the right move to have this added to carbon-storage-management repository. IMO, it has no meaning within the context of storage provisioning which is what carbon-storage-management primarily focuses on. CassandraLogProvider is some utility that's used across the platform right? If that's the case, it has to be added to some common repository, I believe. In addition to that, what CassandraLogProvider depends on (cassandra-thrift, hector-core, etc) is anyway not being maintained as part of carbon-storage-management repository. All considered, I believe, we should probably add this to some other appropriate location which is common for all components in the platform. Cheers, Prabath On Tue, Sep 2, 2014 at 2:29 PM, Inosh Goonewardena in...@wso2.com wrote: Shall we move it to carbon-storage-management repo since it contains all the cassandra related artifacts? On Tue, Sep 2, 2014 at 1:45 PM, Sagara Gunathunga sag...@wso2.com wrote: On Tue, Sep 2, 2014 at 1:20 PM, Afkham Azeez az...@wso2.com wrote: Can it be moved to carbon-commons? This means carbon-commons will depend on cassandra-thrift and hector-core, I don't think that as a good approach. AFAIK this is required for few products such as BAM, CEP, MB etc. so can't we move to a project common for those projects only ? Thanks ! On Tue, Sep 2, 2014 at 12:25 PM, Gayashan Amarasinghe gayas...@wso2.com wrote: Hi all, As a result of Simplifying Carbon Platform Logging Story Supporting Extending [1] the ability to plug any log provider to carbon server has been implemented [2]. This can be done by implementing the LogProvider interface and using logging-config.xml file to provide configurations needed to initialize the log provider implementation. Carbon log viewer will use this interface to get the LogEvents and show it on Log View UI. There has been some implementations already done and these log providers reside in carbon-utils repo [3]. One such log provider is CassandraLogProvider which can be used to provide logs from a cassandra instance. However since having this implementation in carbon-utils repo introduces dependencies on cassandra-thrift and hector-core we cannot keep this implementation in the carbon-utils. So where is the best place to keep this implementation since it is useful for many products? [1] https://wso2.org/jira/browse/COMMONS-110 [2] https://wso2.org/jira/browse/COMMONS-111 [3] https://github.com/shamrath/carbon-utils/tree/CircularBuffer_fix/components/logging/org.wso2.carbon.logging.service/src/main/java/org/wso2/carbon/logging/service/provider Thanks. /Gayashan -- *Gayashan Amarasinghe* Software Engineer | Platform TG WSO2, Inc. | http://wso2.com lean. enterprise. middleware Mobile : +94718314517 Blog : gayashan-a.blogspot.com -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919 blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez* http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Inosh Goonewardena Associate Technical Lead- WSO2 Inc. Mobile: +94779966317 -- Prabath Abeysekara Associate Technical Lead, Data TG. WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Moving CassandraLogProvider from carbon-utils to a different repo
On Tue, Sep 2, 2014 at 7:24 PM, Amila Maha Arachchi ami...@wso2.com wrote: Another fact is, this is not used only by BAM, CEP or MB. Any product which wishes to publish logs to Cassandra will use this. Correct me if I am wrong. So, this is a util to me. Right now not all products use this feature and my concern is with this change carbon-util is depends on cassandra-thrift and hector-core. BTW if majority of products need this feature we can have it under carbon-util or carbon-common then one team has to take ownership and mange cassandra-thrift/hector-core versions in carbon-common project. Thanks ! On Tue, Sep 2, 2014 at 7:15 PM, Prabath Abeysekera praba...@wso2.com wrote: Well, I don't think it's really the right move to have this added to carbon-storage-management repository. IMO, it has no meaning within the context of storage provisioning which is what carbon-storage-management primarily focuses on. CassandraLogProvider is some utility that's used across the platform right? If that's the case, it has to be added to some common repository, I believe. In addition to that, what CassandraLogProvider depends on (cassandra-thrift, hector-core, etc) is anyway not being maintained as part of carbon-storage-management repository. All considered, I believe, we should probably add this to some other appropriate location which is common for all components in the platform. Cheers, Prabath On Tue, Sep 2, 2014 at 2:29 PM, Inosh Goonewardena in...@wso2.com wrote: Shall we move it to carbon-storage-management repo since it contains all the cassandra related artifacts? On Tue, Sep 2, 2014 at 1:45 PM, Sagara Gunathunga sag...@wso2.com wrote: On Tue, Sep 2, 2014 at 1:20 PM, Afkham Azeez az...@wso2.com wrote: Can it be moved to carbon-commons? This means carbon-commons will depend on cassandra-thrift and hector-core, I don't think that as a good approach. AFAIK this is required for few products such as BAM, CEP, MB etc. so can't we move to a project common for those projects only ? Thanks ! On Tue, Sep 2, 2014 at 12:25 PM, Gayashan Amarasinghe gayas...@wso2.com wrote: Hi all, As a result of Simplifying Carbon Platform Logging Story Supporting Extending [1] the ability to plug any log provider to carbon server has been implemented [2]. This can be done by implementing the LogProvider interface and using logging-config.xml file to provide configurations needed to initialize the log provider implementation. Carbon log viewer will use this interface to get the LogEvents and show it on Log View UI. There has been some implementations already done and these log providers reside in carbon-utils repo [3]. One such log provider is CassandraLogProvider which can be used to provide logs from a cassandra instance. However since having this implementation in carbon-utils repo introduces dependencies on cassandra-thrift and hector-core we cannot keep this implementation in the carbon-utils. So where is the best place to keep this implementation since it is useful for many products? [1] https://wso2.org/jira/browse/COMMONS-110 [2] https://wso2.org/jira/browse/COMMONS-111 [3] https://github.com/shamrath/carbon-utils/tree/CircularBuffer_fix/components/logging/org.wso2.carbon.logging.service/src/main/java/org/wso2/carbon/logging/service/provider Thanks. /Gayashan -- *Gayashan Amarasinghe* Software Engineer | Platform TG WSO2, Inc. | http://wso2.com lean. enterprise. middleware Mobile : +94718314517 Blog : gayashan-a.blogspot.com -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919 blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez* http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Inosh Goonewardena Associate Technical Lead- WSO2 Inc. Mobile: +94779966317 -- Prabath Abeysekara Associate Technical Lead, Data TG. WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list
