[ https://issues.apache.org/jira/browse/STRATOS-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lahiru Sandaruwan resolved STRATOS-1081. ---------------------------------------- Resolution: Fixed > Fix Domain Mappings Functionality with Application SignUp Process > ----------------------------------------------------------------- > > Key: STRATOS-1081 > URL: https://issues.apache.org/jira/browse/STRATOS-1081 > Project: Stratos > Issue Type: Improvement > Components: Stratos Manager > Affects Versions: 4.1.0 Alpha > Reporter: Imesh Gunaratne > Assignee: Imesh Gunaratne > Fix For: 4.1.0 Alpha > > > Domain mappings functionality was introduced in 4.0.0 release to allow users > to map domain names for their service subscriptions. The result was that > users were able to use domain names for accessing service clusters without > having to use the generated cluster host names. > In 4.0.0 release these domain names were managed against the service > subscriptions made by the tenants. Now in 4.1.0 release we do not have a > concept of subscriptions, rather application signups are used for managing > artifact repository information. > IMO to fix domain mappings functionality in 4.1.0 release we may need to > store domain names against application signups. > Single-Tenant Applications: > - An application signup is auto generated for each single-tenant application > by extracting the artifact repository information provided. > - Since there could only be one application signup for a single-tenant > application, users could add domain names for each service cluster by > specifying the application id and the cartridge alias. > Multi-Tenant Applications: > - Each tenant could signup for a a multi-tenant application after super > tenant deploys the application. > - Application signup could be stored against application id and tenant id. -- This message was sent by Atlassian JIRA (v6.3.4#6332)