Re: [Architecture] Maintaining carbon-store GitHub repo
On Wed, Jan 21, 2015 at 8:56 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi Prabath et. al, These database scripts[2] and some of the files in [3] are bound to both org.wso2.es.feature and org.wso2.store.feature. Basically, both these features serve the same purpose, i.e. expose ES apps [4]. org.wso2.es.feature exports ES apps with a prefix(ex: es-store, es-publisher) while org.wso2.store.feature exports apps as it is(ex:store, publisher). The reason to export apps with a prefix in the app name is to prevent conflicts with apps shipped with api-mgt features, in the products which used both *es *and *apimgt* features(ex:product-greg). But in the future *apimgt* will be also using ES apps hence there will not be apps shipped with apimgt-feature with the same names as in es-feature. Then no longer there will be two features org.wso2.es.feature and org.wso2.store.feature. At that point we can move dbscripts and other resources into the carbon-store feature org.wso2.store.feature. Until then, as per the offline discussions with Ruchira, Sagara and KasunG, we have decided to keep dbscrips[2] and feature related stuff from [3] into a top level directory in *carbon-store* repo. ( *carbon-store/resources*) Got it. Thanks for the detailed explanation. Cheers, Prabath [2] https://github.com/wso2/product-es/tree/master/modules/distribution/src/dbscripts/storage [3] https://github.com/wso2/product-es/tree/master/modules/distribution/src/repository [4] https://github.com/wso2/product-es/tree/master/modules/apps Thanks! - Ayesha On Wed, Jan 21, 2015 at 5:39 PM, Prabath Abeysekera praba...@wso2.com wrote: Hi Ayesha, On Tue, Jan 20, 2015 at 8:28 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi all, I have completed basic repo separation discussed above along with commit history of the code base.(https://github.com/ayshsandu/carbon-store). I still need to include some necessary resource directories to this repo for it to be fully functional. There are 3 folders listed under product-es/disribution/src [1] - *product-es/disribution/src/dbscripts/storage* [2] - contains ES storage related dbscripts and exported from org.wso2.es.feature and org.wso2.store.feature. - In our repo separation we should move this to *carbon-store* repo. - I suggest this can be located in below directory structure in *carbon-store* repo, and update export paths in org.wso2.es.feature and org.wso2.store.feature. - *carbon-store/features/resources/dbscripts* - Otherwise where should this be located? If these database scripts are bound to some specific feature, why don't we bundle them up with that particular feature instead of having them copied into a location common to all features (i.e. *carbon-store/features/resources/dbscripts*)? Cheers, Prabath - *product-es/distribution/src/repository *[3] - This folder is also exported from org.wso2.es.feature and org.wso2.store.feature. - There are several folders in this location and as I see most of them are ES prodouct specific. - I suggest that we keep product specific stuff in *product-es/disribution/src/repository* as it is and move other necessary files to *carbon-store/features/resources/repository *location and update export paths in org.wso2.es.feature and org.wso2.store.feature. - But I am having hard-time on exactly identifying files in *product-es/disribution/src/repository *location what are ES-product related and what should be exported from features. Please, advice on this separation. - *product-es/distribution/src/assembly* - This contains ES product specific files and will be kept in product-es as it is. Please suggest your concerns on above points. [1] https://github.com/wso2/product-es/tree/master/modules/distribution/src [2] https://github.com/wso2/product-es/tree/master/modules/distribution/src/dbscripts/storage [3] https://github.com/wso2/product-es/tree/master/modules/distribution/src/repository Thanks! - Ayesha On Mon, Jan 19, 2015 at 8:10 PM, Sagara Gunathunga sag...@wso2.com wrote: +1 Thanks ! On Mon, Jan 19, 2015 at 7:33 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi, Please refer the repo structure mentioned above as below. Sorry about missing it fist-place. Thanks! -Ayesha On Mon, Jan 19, 2015 at 7:24 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi all, I have started creating carbon-store GitHub repo as suggested in the mail thread Creating carbon-store GitHub repo. Along with *components* and *features* we will be moving *apps* and *jaggery-modules *into this repo. Finally the main repo structure would be like below. - *apps**[1] *will contain jaggeryapps we ship with ES pack and reused by other products. - *jaggery-modules* [2] are reusable and required by *apps*
Re: [Architecture] Maintaining carbon-store GitHub repo
Hi Ayesha, On Tue, Jan 20, 2015 at 8:28 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi all, I have completed basic repo separation discussed above along with commit history of the code base.(https://github.com/ayshsandu/carbon-store). I still need to include some necessary resource directories to this repo for it to be fully functional. There are 3 folders listed under product-es/disribution/src [1] - *product-es/disribution/src/dbscripts/storage* [2] - contains ES storage related dbscripts and exported from org.wso2.es.feature and org.wso2.store.feature. - In our repo separation we should move this to *carbon-store* repo. - I suggest this can be located in below directory structure in *carbon-store* repo, and update export paths in org.wso2.es.feature and org.wso2.store.feature. - *carbon-store/features/resources/dbscripts* - Otherwise where should this be located? If these database scripts are bound to some specific feature, why don't we bundle them up with that particular feature instead of having them copied into a location common to all features (i.e. *carbon-store/features/resources/dbscripts*)? Cheers, Prabath - *product-es/distribution/src/repository *[3] - This folder is also exported from org.wso2.es.feature and org.wso2.store.feature. - There are several folders in this location and as I see most of them are ES prodouct specific. - I suggest that we keep product specific stuff in *product-es/disribution/src/repository* as it is and move other necessary files to *carbon-store/features/resources/repository *location and update export paths in org.wso2.es.feature and org.wso2.store.feature. - But I am having hard-time on exactly identifying files in *product-es/disribution/src/repository *location what are ES-product related and what should be exported from features. Please, advice on this separation. - *product-es/distribution/src/assembly* - This contains ES product specific files and will be kept in product-es as it is. Please suggest your concerns on above points. [1] https://github.com/wso2/product-es/tree/master/modules/distribution/src [2] https://github.com/wso2/product-es/tree/master/modules/distribution/src/dbscripts/storage [3] https://github.com/wso2/product-es/tree/master/modules/distribution/src/repository Thanks! - Ayesha On Mon, Jan 19, 2015 at 8:10 PM, Sagara Gunathunga sag...@wso2.com wrote: +1 Thanks ! On Mon, Jan 19, 2015 at 7:33 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi, Please refer the repo structure mentioned above as below. Sorry about missing it fist-place. Thanks! -Ayesha On Mon, Jan 19, 2015 at 7:24 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi all, I have started creating carbon-store GitHub repo as suggested in the mail thread Creating carbon-store GitHub repo. Along with *components* and *features* we will be moving *apps* and *jaggery-modules *into this repo. Finally the main repo structure would be like below. - *apps**[1] *will contain jaggeryapps we ship with ES pack and reused by other products. - *jaggery-modules* [2] are reusable and required by *apps* After completing this repo separation, other products which are using ES stuffs will be able to integrate all the ES related components via this *carbon-store *repo and will not be depend on *product-es*. What are the other inputs on this? How have APIM has exposed jaggery related components in this case? [1] https://github.com/wso2/product-es/tree/master/modules/apps [2] https://github.com/wso2/product-es/tree/master/modules/jaggery-modules/ Thanks! - Ayesha -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- 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 -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- Prabath Abeysekara Associate Technical Lead, Data TG. WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471 ___ Architecture mailing list Architecture@wso2.org
Re: [Architecture] Maintaining carbon-store GitHub repo
Hi Prabath et. al, These database scripts[2] and some of the files in [3] are bound to both org.wso2.es.feature and org.wso2.store.feature. Basically, both these features serve the same purpose, i.e. expose ES apps [4]. org.wso2.es.feature exports ES apps with a prefix(ex: es-store, es-publisher) while org.wso2.store.feature exports apps as it is(ex:store, publisher). The reason to export apps with a prefix in the app name is to prevent conflicts with apps shipped with api-mgt features, in the products which used both *es *and *apimgt* features(ex:product-greg). But in the future *apimgt* will be also using ES apps hence there will not be apps shipped with apimgt-feature with the same names as in es-feature. Then no longer there will be two features org.wso2.es.feature and org.wso2.store.feature. At that point we can move dbscripts and other resources into the carbon-store feature org.wso2.store.feature. Until then, as per the offline discussions with Ruchira, Sagara and KasunG, we have decided to keep dbscrips[2] and feature related stuff from [3] into a top level directory in *carbon-store* repo. (*carbon-store/resources*) [2] https://github.com/wso2/product-es/tree/master/modules/distribution/src/dbscripts/storage [3] https://github.com/wso2/product-es/tree/master/modules/distribution/src/repository [4] https://github.com/wso2/product-es/tree/master/modules/apps Thanks! - Ayesha On Wed, Jan 21, 2015 at 5:39 PM, Prabath Abeysekera praba...@wso2.com wrote: Hi Ayesha, On Tue, Jan 20, 2015 at 8:28 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi all, I have completed basic repo separation discussed above along with commit history of the code base.(https://github.com/ayshsandu/carbon-store). I still need to include some necessary resource directories to this repo for it to be fully functional. There are 3 folders listed under product-es/disribution/src [1] - *product-es/disribution/src/dbscripts/storage* [2] - contains ES storage related dbscripts and exported from org.wso2.es.feature and org.wso2.store.feature. - In our repo separation we should move this to *carbon-store* repo. - I suggest this can be located in below directory structure in *carbon-store* repo, and update export paths in org.wso2.es.feature and org.wso2.store.feature. - *carbon-store/features/resources/dbscripts* - Otherwise where should this be located? If these database scripts are bound to some specific feature, why don't we bundle them up with that particular feature instead of having them copied into a location common to all features (i.e. *carbon-store/features/resources/dbscripts*)? Cheers, Prabath - *product-es/distribution/src/repository *[3] - This folder is also exported from org.wso2.es.feature and org.wso2.store.feature. - There are several folders in this location and as I see most of them are ES prodouct specific. - I suggest that we keep product specific stuff in *product-es/disribution/src/repository* as it is and move other necessary files to *carbon-store/features/resources/repository *location and update export paths in org.wso2.es.feature and org.wso2.store.feature. - But I am having hard-time on exactly identifying files in *product-es/disribution/src/repository *location what are ES-product related and what should be exported from features. Please, advice on this separation. - *product-es/distribution/src/assembly* - This contains ES product specific files and will be kept in product-es as it is. Please suggest your concerns on above points. [1] https://github.com/wso2/product-es/tree/master/modules/distribution/src [2] https://github.com/wso2/product-es/tree/master/modules/distribution/src/dbscripts/storage [3] https://github.com/wso2/product-es/tree/master/modules/distribution/src/repository Thanks! - Ayesha On Mon, Jan 19, 2015 at 8:10 PM, Sagara Gunathunga sag...@wso2.com wrote: +1 Thanks ! On Mon, Jan 19, 2015 at 7:33 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi, Please refer the repo structure mentioned above as below. Sorry about missing it fist-place. Thanks! -Ayesha On Mon, Jan 19, 2015 at 7:24 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi all, I have started creating carbon-store GitHub repo as suggested in the mail thread Creating carbon-store GitHub repo. Along with *components* and *features* we will be moving *apps* and *jaggery-modules *into this repo. Finally the main repo structure would be like below. - *apps**[1] *will contain jaggeryapps we ship with ES pack and reused by other products. - *jaggery-modules* [2] are reusable and required by *apps* After completing this repo separation, other products which are using ES stuffs will be able to integrate all the ES related components via this *carbon-store *repo
Re: [Architecture] Maintaining carbon-store GitHub repo
Hi all, I have completed basic repo separation discussed above along with commit history of the code base.(https://github.com/ayshsandu/carbon-store). I still need to include some necessary resource directories to this repo for it to be fully functional. There are 3 folders listed under product-es/disribution/src [1] - *product-es/disribution/src/dbscripts/storage* [2] - contains ES storage related dbscripts and exported from org.wso2.es.feature and org.wso2.store.feature. - In our repo separation we should move this to *carbon-store* repo. - I suggest this can be located in below directory structure in *carbon-store* repo, and update export paths in org.wso2.es.feature and org.wso2.store.feature. - *carbon-store/features/resources/dbscripts* - Otherwise where should this be located? - *product-es/distribution/src/repository *[3] - This folder is also exported from org.wso2.es.feature and org.wso2.store.feature. - There are several folders in this location and as I see most of them are ES prodouct specific. - I suggest that we keep product specific stuff in *product-es/disribution/src/repository* as it is and move other necessary files to *carbon-store/features/resources/repository *location and update export paths in org.wso2.es.feature and org.wso2.store.feature. - But I am having hard-time on exactly identifying files in *product-es/disribution/src/repository *location what are ES-product related and what should be exported from features. Please, advice on this separation. - *product-es/distribution/src/assembly* - This contains ES product specific files and will be kept in product-es as it is. Please suggest your concerns on above points. [1] https://github.com/wso2/product-es/tree/master/modules/distribution/src [2] https://github.com/wso2/product-es/tree/master/modules/distribution/src/dbscripts/storage [3] https://github.com/wso2/product-es/tree/master/modules/distribution/src/repository Thanks! - Ayesha On Mon, Jan 19, 2015 at 8:10 PM, Sagara Gunathunga sag...@wso2.com wrote: +1 Thanks ! On Mon, Jan 19, 2015 at 7:33 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi, Please refer the repo structure mentioned above as below. Sorry about missing it fist-place. Thanks! -Ayesha On Mon, Jan 19, 2015 at 7:24 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi all, I have started creating carbon-store GitHub repo as suggested in the mail thread Creating carbon-store GitHub repo. Along with *components* and *features* we will be moving *apps* and *jaggery-modules *into this repo. Finally the main repo structure would be like below. - *apps**[1] *will contain jaggeryapps we ship with ES pack and reused by other products. - *jaggery-modules* [2] are reusable and required by *apps* After completing this repo separation, other products which are using ES stuffs will be able to integrate all the ES related components via this *carbon-store *repo and will not be depend on *product-es*. What are the other inputs on this? How have APIM has exposed jaggery related components in this case? [1] https://github.com/wso2/product-es/tree/master/modules/apps [2] https://github.com/wso2/product-es/tree/master/modules/jaggery-modules/ Thanks! - Ayesha -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- 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 -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Maintaining carbon-store GitHub repo
Hi all, I have started creating carbon-store GitHub repo as suggested in the mail thread Creating carbon-store GitHub repo. Along with *components* and *features* we will be moving *apps* and *jaggery-modules *into this repo. Finally the main repo structure would be like below. - *apps**[1] *will contain jaggeryapps we ship with ES pack and reused by other products. - *jaggery-modules* [2] are reusable and required by *apps* After completing this repo separation, other products which are using ES stuffs will be able to integrate all the ES related components via this *carbon-store *repo and will not be depend on *product-es*. What are the other inputs on this? How have APIM has exposed jaggery related components in this case? [1] https://github.com/wso2/product-es/tree/master/modules/apps [2] https://github.com/wso2/product-es/tree/master/modules/jaggery-modules/ Thanks! - Ayesha -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Maintaining carbon-store GitHub repo
+1 Thanks ! On Mon, Jan 19, 2015 at 7:33 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi, Please refer the repo structure mentioned above as below. Sorry about missing it fist-place. Thanks! -Ayesha On Mon, Jan 19, 2015 at 7:24 PM, Ayesha Dissanayaka aye...@wso2.com wrote: Hi all, I have started creating carbon-store GitHub repo as suggested in the mail thread Creating carbon-store GitHub repo. Along with *components* and *features* we will be moving *apps* and *jaggery-modules *into this repo. Finally the main repo structure would be like below. - *apps**[1] *will contain jaggeryapps we ship with ES pack and reused by other products. - *jaggery-modules* [2] are reusable and required by *apps* After completing this repo separation, other products which are using ES stuffs will be able to integrate all the ES related components via this *carbon-store *repo and will not be depend on *product-es*. What are the other inputs on this? How have APIM has exposed jaggery related components in this case? [1] https://github.com/wso2/product-es/tree/master/modules/apps [2] https://github.com/wso2/product-es/tree/master/modules/jaggery-modules/ Thanks! - Ayesha -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com ayshsa...@gmail.com -- 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
