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-113

Explore Software Environment Centricity vs. Application Driven

    XMLWordPrintable

    Details

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

      Description

      Explore if TOSCA specs should be built from an application driven point and only allow definition of connections between components or it should allow definition of lower level hardware requirements as well.

      Hardware requirements may include networking details, VM requirements etc.

      Use Case: Network connection between application components

      Scenario: An application has 2 components Java and MySQL which need to communicate with each other.

      Option 1: Application just specifies the 2 components and that there must be a connection between the two. Possibly specifying the protocol and port number on the MySQL side.
      Option 2: Application specified additional details including # of cores, memory, Firewall configuration etc. of MySQL component in addition to what is specified in Option 1.

      Will supporting these hardware requirements be mandatory? How do we allow TOSCA to be generic enough to accomodate PaaS platforms that abstract away the hardware details from the application?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              kraman Krishna Raman (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: