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

Use Case: Handling errors on Operations during (and post) deployment (i.e. an Error Model)

    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: TBD
      Proposal: TBD

      Show
      Diagram: TBD Proposal: TBD

      Description

      Is there an error model? What information is available regarding the execution results of a plan? What is the final representation of the complete deployment?

      Example:
      TBD

      Notes:
      Matt: Many thoughts here to break out...
      Derek: need std. set of errors (semantics) if operation fails (imp or decl). Perhaps a best practice. If scripting how can you write a generic script for any TOSCA engine.

      Reference:
      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: