[STRATOS-659] Improve Domain Mappings Functionality to Re-Write URLs in Load Balancer

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.1.0 RC3
• Component/s: Load Balancer
• Assignee: Imesh Gunaratne
• Reporter: Imesh Gunaratne
• Created: 29/May/14 17:47
• Updated: 31/May/15 07:21
• Resolved: 01/Jun/14 05:17

Description

In current Domain Mappings implementation Stratos allows to add domain mappings to service subscriptions with following parameters: cartridgeType, subscriptionAlias, list of <domainName, appContext>.

Stratos Manager sends this information to load balancers via the message broker. Load balancer keeps domainName in a hash map against its cluster, once a request is received, the cluster is fetched and request is delegated to the next available member in that cluster without touching the request path. In the member a Tomcat virtual host could be created with the appContext to map the incoming request path to actual application path.

However this design might not work with different types of services which may not be able to use Tomcat virtual hosts. More importantly URL mapping functionality needed to be implemented in each and every service.

Therefore we could overcome this problem by introducing a new functionality in load balancer to map URLs and directly delegate the incoming requests to the member application context path.

Incoming request:
https://foo.org/some/file/path?someQueryParam=value

Application Context:
/tenant/foo.org/app-name/version

LB re-writes it to:
https://member-ip:port/tenant/tenant-identifier/app-name/version/some/file/path/?someQueryParam=value