[
http://jira.amdatu.org/jira/browse/AMDATUOPENSOCIAL-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11415#comment-11415
]
Ivo Ladage - van Doorn edited comment on AMDATUOPENSOCIAL-42 at 9/13/11 4:04 PM:
---------------------------------------------------------------------------------
I thinks there are two options to fix multi tenancy in Shindig:
- Simple & quick fix: We could implement a custom ContainerConfig, which binds
itself to the ContainerConfig class in the registered Social API module. In the
getProperty implementation of this containerConfig, it could check if the
expression %tenant_host% is used. If so, it reads the hostname associated with
the current tenant (already available in Shindig) and replaces the expression
with this hostname. The container js configuration (container.js) should use
this expression for hostnames to be replaced with the tenant hostname at
runtime. This would be a simple and fast fix. However, this means that Shindig
runs only 1 container. The fix just ensures that the proper hostnames are used.
- Full fix: Implement a multi container Shindig, where containers are
spawned/removed automatically when tenants are added/removed. If a new Tenant
comes available, a new container_[tenant].js should be added to the work
directory. Also a custom ContainerConfig, which binds itself to the
ContainerConfig class in the registered Social API module should be
implemented. This ContainerConfig is tenant aware and will reload container
properties when tenants come and go. The generated container_[tenant].js files
would need to contain hard coded hostnames, the ones associated with that
tenant. Furthermore, custom gadget contexts should be instantiated. Currently,
Shindig assumes the default container, appending 'container=default' to the
URLs. For that we will need to modify the shindig-container.js which now uses
hard coded container 'default'. In this scenario we would have a full multi
tenant solution, where shindig containers can be configured with different
themes, skins, OAu!
th settings, OpenSocial features and security tokens per tenant.
was (Author: ivol):
I thinks there are two options to fix multi tenancy in Shindig:
- Simple & quick fix: We could implement a custom ContainerConfig, which binds
itself to the ContainerConfig class in the registered Social API module. In the
getProperty implementation of this containerConfig, it could check if the
expression %tenant_host% is used. If so, it reads the hostname associated with
the current tenant (already available in Shindig) and replaces the expression
with this hostname. The container js configuration (container.js) should use
this expression for hostnames to be replaced with the tenant hostname at
runtime. This would be a simple and fast fix. However, this means that Shindig
runs only 1 container. The fix just ensures that the proper hostnames are used.
- Full fix: Implement a multi container Shindig, where containers are
spawned/removed automatically when tenants are added/removed. If a new Tenant
comes available, a new container_[tenant].js should be added to the work
directory. Also a custom ContainerConfig, which binds itself to the
ContainerConfig class in the registered Social API module should be
implemented. This ContainerConfig is tenant aware and will reload container
properties when tenants come and go. The generated container_[tenant].js files
would need to contain hard coded hostnames, the ones associated with that
tenant. Furthermore, custom gadget contexts should be instantiated. Currently,
Shindig assumes the default container, appending 'container=default' to the
URLs.
> Support multi tenancy in OpenSocial/Shindig
> -------------------------------------------
>
> Key: AMDATUOPENSOCIAL-42
> URL: http://jira.amdatu.org/jira/browse/AMDATUOPENSOCIAL-42
> Project: Amdatu OpenSocial
> Issue Type: Task
> Reporter: Dion Meijer
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.2.0
>
>
> On an production enviroment the property "shindig.host" has to be configured
> in "deploy\org.amdatu.opensocial.shindig.cfg":
> shindig.host=wpg.blueconic.com
> Since this property can only be configured once, this might lead to problems
> in a multitenant enviroment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
