OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TCIcon indicating the project type

OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC

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-24 Plan Portability API
  3. TOSCA-49

"Real-Time" Topology Updates for Boundary Systems

    Details

    • Type: Sub-task
    • Status: Deferred
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Spec
    • Labels:
      None
    • Environment:

      All

      Description

      Increasingly, monitoring solutions are concerned with assuring the availability of Services. To achieve this goal they must have an accurate and current internal representation of the Service Topology. For monitoring solutions, and other boundary systems, that are not the authoritative source of Service Topology, TOSCA should provide a means for discovery and "real-time" updates of Service Topology.

      Use Case: A service assurance product wishes to reason about Service Topology for the purpose of performing its function. To do so, it ought to be able to discover Service's Topology as well as remain informed of any changes related to the topology.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          lippa02 Paul Lipton (Inactive) added a comment -

          Part of this (discovery of the service topology) may be covered by the proposed TOSCA-24.

          Show
          lippa02 Paul Lipton (Inactive) added a comment - Part of this (discovery of the service topology) may be covered by the proposed TOSCA-24 .
          Hide
          Permalink
          lippa02 Paul Lipton (Inactive) added a comment -

          Robert, since this is related to TOSCA-24, would you care to have this considered by the same ad hoc group that is discussing TOSCA-24 or do you wish to discuss/propose this with the TC?

          Show
          lippa02 Paul Lipton (Inactive) added a comment - Robert, since this is related to TOSCA-24 , would you care to have this considered by the same ad hoc group that is discussing TOSCA-24 or do you wish to discuss/propose this with the TC?
          Hide
          Permalink
          revans Robert Evans (Inactive) added a comment -

          Paul,

          I wouldn't mind merging this issue into TOSCA-24 or even closing this issue if it is covered in its entirety by that jira issue. I would, however, like the option to participate in any ad hoc group that is working the issue.

          Show
          revans Robert Evans (Inactive) added a comment - Paul, I wouldn't mind merging this issue into TOSCA-24 or even closing this issue if it is covered in its entirety by that jira issue. I would, however, like the option to participate in any ad hoc group that is working the issue.
          Hide
          Permalink
          lippa02 Paul Lipton (Inactive) added a comment -

          Robert, thank you for your flexibility and helpfulness. I have added TOSCA-24 to this week's agenda so that we hear the status of the ad hoc group and/or find consensus in the TC, if possible. This issue will be discussed before this issue so that you will be able to consider if the decision on TOSCA-24 satisfies you and the TC afterwards in relation to this issue.

          Show
          lippa02 Paul Lipton (Inactive) added a comment - Robert, thank you for your flexibility and helpfulness. I have added TOSCA-24 to this week's agenda so that we hear the status of the ad hoc group and/or find consensus in the TC, if possible. This issue will be discussed before this issue so that you will be able to consider if the decision on TOSCA-24 satisfies you and the TC afterwards in relation to this issue.
          Hide
          Permalink
          lippa02 Paul Lipton (Inactive) added a comment -

          Robert, the TC asks if you wish to table this issue to v.net, since you say it is/maybe related to TOSCA-24, Plan Portability API, which is tabled for v.next. If this is not what you want, could you please attend the 9/20 meeting in order to propose/explain the issue to the TC?

          Show
          lippa02 Paul Lipton (Inactive) added a comment - Robert, the TC asks if you wish to table this issue to v.net, since you say it is/maybe related to TOSCA-24 , Plan Portability API, which is tabled for v.next. If this is not what you want, could you please attend the 9/20 meeting in order to propose/explain the issue to the TC?
          Hide
          Permalink
          lippa02 Paul Lipton (Inactive) added a comment -

          Based on discussion with Rob on September 19 and 20, as per his direction, am deferring this to v.next. It should be considered placed it under consideration of the ad hoc group looking at the Plan Portability API work and is appropriately subtasked to TOSCA-24.

          Show
          lippa02 Paul Lipton (Inactive) added a comment - Based on discussion with Rob on September 19 and 20, as per his direction, am deferring this to v.next. It should be considered placed it under consideration of the ad hoc group looking at the Plan Portability API work and is appropriately subtasked to TOSCA-24 .

            People

            • Assignee:
              Unassigned
              Reporter:
              revans Robert Evans (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: