stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Imesh Gunaratne (JIRA)" <>
Subject [jira] [Updated] (STRATOS-123) Implement Support for Multi-Tenancy
Date Wed, 27 Nov 2013 04:35:36 GMT


Imesh Gunaratne updated STRATOS-123:

    Affects Version/s:     (was: 4.0.0 M2)

> Implement Support for Multi-Tenancy
> -----------------------------------
>                 Key: STRATOS-123
>                 URL:
>             Project: Stratos
>          Issue Type: Sub-task
>            Reporter: Imesh Gunaratne
>            Assignee: Imesh Gunaratne
>             Fix For: 4.0.0 M4
> To provide support for multi-tenant applications, the load balancer needs to identify
the host name (or mapped domain name if available) and the tenant id from the incoming request
and delegate that request to the next available member in the relevant cluster.
> Tenant Definition:
> - A tenant could be partitioned into clusters by defining tenant ranges for each cluster.
>   Example: (Cluster 1 - Tenant Range: 1-100, Cluster 2 - Tenant Range: 101-200, Cluster
3: Tenant Range: 201-*)
> - Each tenant needs to define an id and a domain name.
> Properties found in the Request URL:
> - Host name
> - Tenant id or tenant domain name
> Required Functionality:
> 1. If tenant id is found in the request URL identify the cluster and delegate the request
to the next available member.
> 2. If tenant domain is found in the request, find the tenant id using the available tenant
information and execute 1.
> Tenant Information:
> Stratos Manager (SM) needs to publish tenant information to a message broker topic so
that coupling between the load balancer and SM is less. As a result the load balancer could
operate in isolation just by communicating with the message broker.

This message was sent by Atlassian JIRA

View raw message