OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Event Interface Proposal


Hello Calin, Chris,

 

This is regarding the event interface proposal  that was uploaded in OASIS portal recently:  https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/63289/EventInterface2018_06_20.docx   

 I believe this has not yet been discussed in TOSCA Simple Profile meetings, but  is in plan for TOSCA YAML v1.3.

I  have a few comments and suggestions on this:

 

1.       We could embed implementation artifacts in the  event_interfaces which could be responsible for triggering these events external to the Orchestrator. This is in addition to how information in such notification will be stored on node instances/topology instance attributes after it has been received.

 

2.       Just an alignment with common approaches like REST (when you can POST or wait for callback notification), we could rename “event_interface” as “notification”

 

3.       Introduce a  new keyword “TOPOLOGY” on similar lines as “SELF”. This provides possibility to fill topology attributes as a result of an operation or event and provide possibility to read topology attribute values from node instances inside topology.

 

 

  notifications:  #event_interfaces in the original proposal

        key_reports:

          availability_report:

            outputs:

              name: availability

              value: [ TOPOLOGY, monitor, ubuntu_availability ]

            implementation:    #new                

              primary: alarm_processing         #  new

       

            event_types:

              - failure_monitoring

         fault_report:

            outputs:

              name: fault

              value: [ SELF, monitor, failure ]

            implementation:                     #

              primary: alarm_processing         #  new

              dependencies:                     #

                - prober                        #

            event_types:

              - failure_processing             

 

 

 

Kindly share your thoughts on this.

 

Regards,

 

 

 

Priya TG
Netcracker Technology


+91 (080) 4935 2500 |office
+91 (988) 0533 580 | mobile

 

We are Netcracker, and we are focused forward

 

 


The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]