I think we should consider adding GitBlit service to Storage Server? Paul
On 21 February 2013 05:00, Lakmal Warusawithana <[email protected]> wrote: > As per below mail thread +1 for omit git repository bundled with S2. For > doing that we need to fulfil below requirements. > > 1. Get users external or private git repository credentials. > 2. expose a service (REST) to get git push notification > > We already have 2 (for github scenario) but need to be generalize. For > support 1 below is new implementation design we are going to follow. > > 1. Capturing repoUser and repoPassword from user input. (whether GUI > or CLI) Data transmission happens via SSL > 2. Will store repoPassword in UserStore by encrypt using a key. > 3. Will keep above key in secure wallet. > 4. When cartridge trigger artifact update and it will call a ADC > service (through SSL) and get repo credentials and do git pull > > So above scenario we only kept user credential securely in only one > location. > > For AF scenario we can have gitblit but its will be out of S2 core > services. > > In future we need to extends this service to support SVN as well. > > Please share your thoughts > > thanks > On Thu, Feb 14, 2013 at 10:40 PM, Nirmal Fernando <[email protected]> wrote: > >> Paul, >> >> On Thu, Feb 14, 2013 at 9:41 PM, Paul Fremantle <[email protected]> wrote: >> >>> The Git repo should NOT have these directories by *default*. The >>> directory structure is completely dependent on which cartridge(s) you are >>> developing against. >> >> >> This is what exactly we're doing now. You can define how your repository >> should look like, by using the Cartridge definition, >> >>> >>> Paul >>> >>> PS we still need to address whether we are willing to support GitBlit as >>> a new service. >>> >>> >>> On 14 February 2013 14:44, Lahiru Sandaruwan <[email protected]> wrote: >>> >>>> Hi all, >>>> >>>> I think we could have use the Git repository created by App factory, >>>> when AF and S2 integration. >>>> But we have to have the folder structure relevant to WSO2 application >>>> server as Sajith also mentioned. >>>> i.e Git repository should include "axis2modules axis2services >>>> jaggeryapps jaxwebapps modulemetafiles servicemetafiles webapps" >>>> folders inside that. >>>> >>>> AF team, >>>> >>>> Is above possible? >>>> >>>> Thanks. >>>> >>>> >>>> On Thu, Feb 14, 2013 at 10:54 AM, Sajith Kariyawasam >>>> <[email protected]>wrote: >>>> >>>>> Hi Paul, >>>>> >>>>> We support both the options, a Git repository hosted in somewhere else >>>>> can be used. If no repository is given at the time of subscription, an >>>>> internal repo is created >>>>> and that will be used. >>>>> >>>>> When using an external repo, that has to have the proper folder >>>>> structure depending on the cartridge type, which can be mentioned in the >>>>> user guide (Folder structure per cartridge type is defined in cartridge >>>>> specific config file). >>>>> >>>>> >>>>> On Tue, Feb 12, 2013 at 5:28 PM, Paul Fremantle <[email protected]> wrote: >>>>> >>>>>> Folks >>>>>> >>>>>> I like Gitblit. It seems like a good approach and its under the right >>>>>> license >>>>>> >>>>>> BUT!!!!! >>>>>> >>>>>> I don't think we've thought this through properly. Is Stratos 2.0 >>>>>> going to embed a Git server? If so that is a BIG architecture change for >>>>>> Stratos 2.0. >>>>>> >>>>>> I see this as a potential option for App Factory, but I think Stratos >>>>>> 2.0 should be assuming you have a Git or SVN somewhere else by default. >>>>>> If >>>>>> we are going to start offering Git serving as part of the product that >>>>>> has >>>>>> big implications: >>>>>> >>>>>> 1) scalability >>>>>> 2) disk requirements >>>>>> 3) support >>>>>> etc >>>>>> >>>>>> Paul >>>>>> >>>>>> On 11 February 2013 19:03, Ramith Jayasinghe <[email protected]> wrote: >>>>>> >>>>>>> This would help: >>>>>>> >>>>>>> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/appfac/org.wso2.carbon.appfactory.repository/src/main/java/org/wso2/carbon/appfactory/git/repository/provider/ >>>>>>> >>>>>>> >>>>>>> On Mon, Feb 11, 2013 at 10:57 AM, Sajith Kariyawasam < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> On Mon, Feb 11, 2013 at 11:13 PM, Ramith Jayasinghe < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Appfactory already integrates with GIT. >>>>>>>>> It might be useful to check code there. >>>>>>>>> >>>>>>>>> >>>>>>>> Great.! Will have a look into it, >>>>>>>> >>>>>>>> Appfactory team, are you guys having a Git repository management >>>>>>>> component that can be reused in S2 ? >>>>>>>> >>>>>>>> What is the library being used? >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Feb 11, 2013 at 9:31 AM, Sajith Kariyawasam < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Feb 11, 2013 at 5:57 PM, Lahiru Sandaruwan < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> +1 for this improvement as it is critical to handle the >>>>>>>>>>> concurrency in subscriptions. >>>>>>>>>>> Sajith please create an improvement Jira to track this. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> Its already in JIRA https://wso2.org/jira/browse/SPI-101 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Thanks. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Mon, Feb 11, 2013 at 5:43 PM, Isuru Haththotuwa < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Feb 11, 2013 at 3:57 PM, Isuru Haththotuwa < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Feb 11, 2013 at 3:22 PM, Sajith Kariyawasam < >>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi all, >>>>>>>>>>>>>> >>>>>>>>>>>>>> This is to keep track of the improvements to be done in Git >>>>>>>>>>>>>> repo management functionality in Stratos 2.0, since we faced >>>>>>>>>>>>>> some issues >>>>>>>>>>>>>> when creating Git repositories concurrently, in our current >>>>>>>>>>>>>> implementation >>>>>>>>>>>>>> which uses set of shell scripts to do that. >>>>>>>>>>>>>> >>>>>>>>>>>>>> So we are looking for a way to replace those shell scripts >>>>>>>>>>>>>> with a Java Client, >>>>>>>>>>>>>> >>>>>>>>>>>>>> found [1] provides a nice way to manage git repositories, and >>>>>>>>>>>>>> is equipped with a Java API [2] as well, so that in Stratos 2 >>>>>>>>>>>>>> code, I >>>>>>>>>>>>>> think we can use this API instead of our bash scripts.. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I did some basic tests and were able to create users and git >>>>>>>>>>>>>> repositories using a Java program.. >>>>>>>>>>>>>> >>>>>>>>>>>>>> So I think we can use Gitblit WAR [3] as the repository >>>>>>>>>>>>>> server, and use [2] to create / manage repos and, use Jgit [4] >>>>>>>>>>>>>> to do Git >>>>>>>>>>>>>> pull/push >>>>>>>>>>>>>> >>>>>>>>>>>>>> Will update the thread as work progresses. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Appreciate feedback on this >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> +1. I have used jgit [4], and it supports all git operations >>>>>>>>>>>>> through java code. Will look in to see if it supports the >>>>>>>>>>>>> management aspect >>>>>>>>>>>>> as well, if so we can use a single library for this. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> It seems that jgit only provides Git software capabilities, and >>>>>>>>>>>> does not support Git-hosting. Therefore we can't use it for the >>>>>>>>>>>> git server >>>>>>>>>>>> and repository management requirements. I had a look at gitlib as >>>>>>>>>>>> well, and >>>>>>>>>>>> it seems to fit in to the picture nicely. +1 for using it. >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> [1] http://gitblit.com/ >>>>>>>>>>>>>> [2] >>>>>>>>>>>>>> http://code.google.com/p/gitblit/downloads/detail?name=gbapi-1.2.1.zip >>>>>>>>>>>>>> [3] >>>>>>>>>>>>>> http://code.google.com/p/gitblit/downloads/detail?name=gitblit-1.2.1.war >>>>>>>>>>>>>> [4] http://www.eclipse.org/jgit/ >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>> * >>>>>>>>>>>>>> * >>>>>>>>>>>>>> *Sajith Kariyawasam* >>>>>>>>>>>>>> *Senior Software Engineer; WSO2, Inc.; http://wso2.com* >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Dev mailing list >>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Thanks and Regards, >>>>>>>>>>>>> >>>>>>>>>>>>> Isuru H. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Thanks and Regards, >>>>>>>>>>>> >>>>>>>>>>>> Isuru H. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Dev mailing list >>>>>>>>>>>> [email protected] >>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> -- >>>>>>>>>>> Lahiru Sandaruwan >>>>>>>>>>> Software Engineer, >>>>>>>>>>> Cloud Team, >>>>>>>>>>> WSO2 Inc., http://wso2.com >>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>> >>>>>>>>>>> email: [email protected] cell: (+94) 773 325 954 >>>>>>>>>>> blog: http://lahiruwrites.blogspot.com/ >>>>>>>>>>> twitter: http://twitter.com/lahirus >>>>>>>>>>> linked-in: >>>>>>>>>>> http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>>>>>>>>>> <http://wso2con.com/> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Regards, >>>>>>>>>> * >>>>>>>>>> * >>>>>>>>>> *Sajith Kariyawasam* >>>>>>>>>> *Senior Software Engineer; WSO2, Inc.; http://wso2.com* >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Dev mailing list >>>>>>>>>> [email protected] >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Ramith Jayasinghe >>>>>>>>> Technical Lead >>>>>>>>> >>>>>>>>> WSO2 Inc., http://wso2.com >>>>>>>>> lean.enterprise.middleware >>>>>>>>> >>>>>>>>> E: [email protected] >>>>>>>>> P: +1 (469) 583-2035 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Regards, >>>>>>>> * >>>>>>>> * >>>>>>>> *Sajith Kariyawasam* >>>>>>>> *Senior Software Engineer; WSO2, Inc.; http://wso2.com* >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Ramith Jayasinghe >>>>>>> Technical Lead >>>>>>> WSO2 Inc., http://wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> E: [email protected] >>>>>>> P: +1 (469) 583-2035 >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> [email protected] >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Paul Fremantle >>>>>> CTO and Co-Founder, WSO2 >>>>>> OASIS WS-RX TC Co-chair, VP, Apache Synapse >>>>>> >>>>>> >>>>>> >>>>>> UK: +44 207 096 0336 >>>>>> US: +1 646 595 7614 >>>>>> >>>>>> blog: http://pzf.fremantle.org >>>>>> twitter.com/pzfreo >>>>>> [email protected] >>>>>> >>>>>> wso2.com Lean Enterprise Middleware >>>>>> >>>>>> Disclaimer: This communication may contain privileged or other >>>>>> confidential information and is intended exclusively for the addressee/s. >>>>>> If you are not the intended recipient/s, or believe that you may have >>>>>> received this communication in error, please reply to the sender >>>>>> indicating >>>>>> that fact and delete the copy you received and in addition, you should >>>>>> not >>>>>> print, copy, retransmit, disseminate, or otherwise use the information >>>>>> contained in this communication. Internet communications cannot be >>>>>> guaranteed to be timely, secure, error or virus-free. The sender does not >>>>>> accept liability for any errors or omissions. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> * >>>>> * >>>>> *Sajith Kariyawasam* >>>>> *Senior Software Engineer; WSO2, Inc.; http://wso2.com* >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> -- >>>> Lahiru Sandaruwan >>>> Software Engineer, >>>> Cloud Team, >>>> WSO2 Inc., http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> email: [email protected] cell: (+94) 773 325 954 >>>> blog: http://lahiruwrites.blogspot.com/ >>>> twitter: http://twitter.com/lahirus >>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>>> <http://wso2con.com/> >>>> >>> >>> >>> >>> -- >>> Paul Fremantle >>> CTO and Co-Founder, WSO2 >>> OASIS WS-RX TC Co-chair, VP, Apache Synapse >>> >>> >>> >>> UK: +44 207 096 0336 >>> US: +1 646 595 7614 >>> >>> blog: http://pzf.fremantle.org >>> twitter.com/pzfreo >>> [email protected] >>> >>> wso2.com Lean Enterprise Middleware >>> >>> Disclaimer: This communication may contain privileged or other >>> confidential information and is intended exclusively for the addressee/s. >>> If you are not the intended recipient/s, or believe that you may have >>> received this communication in error, please reply to the sender indicating >>> that fact and delete the copy you received and in addition, you should not >>> print, copy, retransmit, disseminate, or otherwise use the information >>> contained in this communication. Internet communications cannot be >>> guaranteed to be timely, secure, error or virus-free. The sender does not >>> accept liability for any errors or omissions. >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> Thanks & regards, >> Nirmal >> >> Software Engineer- Platform Technologies Team, WSO2 Inc. >> Mobile: +94715779733 >> Blog: http://nirmalfdo.blogspot.com/ >> >> <http://nirmalfdo.blogspot.com/> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Lakmal Warusawithana > Software Architect; WSO2 Inc. > Mobile : +94714289692 > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
