Hi All,
Milestone 1 goals for tenant isolation in git achieved successfully. But
not fully integrated with the application creation process. Now, when a
user belongs to a tenant creates and repository, it is created in the
tenant space. Filtering applications for a user is done by the
existing plugin ,so there is no need to change it.


cheers!!



On Fri, Jul 19, 2013 at 2:12 PM, Asanka Dissanayake <[email protected]>wrote:

> Hi All,
> I tried the $subject with gitblit 1.3.0 . It works fine.
>
> *What have been done so far?*
> There is a service called *TenantRepoCreation* service.which is a super
> tenant service. It creates the tenant space it gitblit for the tenant.
> Thereafter every repository created for the tenant will be created in the
> tenant space allocated for the tenant in gitblit .
>
> As Ajanthan mentioned , we can map tenant to ProjectModel in the gitblit
> api.
>
> *What next?*
> 1. Modify the appfactory plugin to support projectmodels.
> 2. Filter out and view repositories for the user inside the tenant .
> 3. Permission module.
>
>
> On Mon, Jul 15, 2013 at 5:07 PM, Asanka Dissanayake <[email protected]>wrote:
>
>> Thanks Ajanthan, that will be quite useful will look into this.
>>
>>
>> On Mon, Jul 15, 2013 at 4:52 PM, Ajanthan Balachandran <[email protected]
>> > wrote:
>>
>>> There is another option also.You can use gitblit ProjectModel[0].This is
>>> the perfect map for tenants.
>>>
>>>
>>> On Mon, Jul 15, 2013 at 4:39 PM, Asanka Dissanayake <[email protected]>wrote:
>>>
>>>> Yes, that can be done using a permission plugin. Will list out the
>>>> security concerns soon.
>>>>
>>>>
>>>> On Mon, Jul 15, 2013 at 4:10 PM, Paul Fremantle <[email protected]> wrote:
>>>>
>>>>> Can we apply security based on this scheme easily? I don't know how
>>>>> Git security works...
>>>>>
>>>>> Paul
>>>>>
>>>>>
>>>>> On 15 July 2013 11:32, Asanka Dissanayake <[email protected]> wrote:
>>>>>
>>>>>> Hi All,
>>>>>> I am working on the $subject and here is the my point of view of
>>>>>> achieving the $subject.
>>>>>>
>>>>>> Simply we can group repositories in the Git using repo creation url
>>>>>> as host/tenantName/repo.git
>>>>>> So it will create a subfolder with name tenantName and create
>>>>>> repo.git inside it.
>>>>>>
>>>>>> So that folder will act as a tenant space.All git repositories of the
>>>>>> tenant can be found in that folder.
>>>>>>
>>>>>> (I tested this in local setup)
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> *Asanka Dissanayake
>>>>>> Software Engineer*
>>>>>> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
>>>>>> *
>>>>>> email: [email protected] <[email protected]>,   blog:
>>>>>> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94
>>>>>> 71 8373821*
>>>>>>
>>>>>> _______________________________________________
>>>>>> Architecture mailing list
>>>>>> [email protected]
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Paul Fremantle
>>>>> CTO and Co-Founder, WSO2
>>>>> OASIS WS-RX TC Co-chair, Apache Member
>>>>>
>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Asanka Dissanayake
>>>> Software Engineer*
>>>> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
>>>> *
>>>> email: [email protected] <[email protected]>,   blog:
>>>> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94
>>>> 71 8373821*
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> [email protected]
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>> [0]
>>> https://github.com/gitblit/gitblit/blob/master/src/main/java/com/gitblit/models/ProjectModel.java
>>> --
>>> ajanthan
>>> --
>>> Ajanthan Balachandiran
>>> Senior Software Engineer;
>>> Solutions Technologies Team ;WSO2, Inc.;  http://wso2.com/
>>>
>>> email: ajanthan <http://goog_595075977>@wso2.com; cell: +94775581497
>>> blog: http://bkayts.blogspot.com/
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *Asanka Dissanayake
>> Software Engineer*
>> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
>> *
>> email: [email protected] <[email protected]>,   blog:
>> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94
>> 71 8373821*
>>
>
>
>
> --
>
> *Asanka Dissanayake
> Software Engineer*
> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
> *
> email: [email protected] <[email protected]>,   blog:
> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
> 8373821*
>



-- 

*Asanka Dissanayake
Software Engineer*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
*
email: [email protected] <[email protected]>,   blog:
cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
8373821*
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to