Uploaded image for project: 'OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC'
  1. OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
  2. TOSCA-95

Use Case: Managing DNS and Public IPs

    XMLWordPrintable

    Details

    • Type: Task
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Interop
    • Labels:
      None
    • Environment:

      Use case for development against TOSCA-v1.0-cs01.

    • Proposal:
      Hide

      Diagram(s): TBD
      Proposal(s): TBD

      Show
      Diagram(s): TBD Proposal(s): TBD

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              dpalma Derek Palma (Inactive)
              Reporter:
              mrutkows Matthew Rutkowski (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: