[OASIS Issue Tracker] Created: (TOSCA-95) Use Case: Managing DNS and Public IPs

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Use Case: Managing DNS and Public IPs
-------------------------------------

                 Key: TOSCA-95
                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-95
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Task
          Components: Interop
         Environment: Use case for development against TOSCA-v1.0-cs01.
            Reporter: Matthew Rutkowski 
            Assignee: Derek Palma


Public IPs usually need to be resolvable via DNS. This is typically done by one of:
1) Binding an IP address already known by DNS to the VM exposing the EndPoint. 
2) Updating the DNS service with the dynamic IP address of the VM exposing the EndPoint

Examples:
TBD - There is a SugarCRM picture in the PowerPoint,  can we develop this as a basis?

Notes:
Matt: pre-deploy and post-deploy considerations? There seems to be overlap in conveying access/credentials from one tier (endpoint) to another as described in previous use cases, are there dependencies on these use cases (a priority for resolution)?

References:
https://www.oasis-open.org/apps/org/workgroup/tosca-interop/download.php/48513/TOSCASugarCRMUseCase-CompleteConnectivity.pptx
https://www.oasis-open.org/apps/org/workgroup/tosca-interop/download.php/48514/ConsiderationsFor2TierWebApplications.docx

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira