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: [OASIS Issue Tracker] (TOSCA-224) Need a way for resolving order for requirement processing

Thomas Spatzier  created TOSCA-224:

             Summary: Need a way for resolving order for requirement processing
                 Key: TOSCA-224
                 URL: https://issues.oasis-open.org/browse/TOSCA-224
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Bug
          Components: Profile-YAML, Spec - Simple Profile
            Reporter: Thomas Spatzier 

In the simple profile in YAML specification, requirement definitions are currently defined as a list. The reason was that we wanted to be able to preserve ordering, allowing a node type author to prescribe the order in which requirements in a template get processed.

This allows for example, to make sure that operations (e.g. implemented as scripts) attached to the relationships that bind the requirements at runtime get run in the right order.

However, we currently do not have a means for describing how requirements defined in a node type sort into the order of requirements inherited from parent node types. We cannot just assume that newly defined requirements get added to the end of the list of inherited requirements. This would mean, the generic "dependency" requirement defined by the Root node type (thus inherited by any other node type) would always be processed first, which is not desirable.

This message was sent by Atlassian JIRA

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