[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-229) Requirements / target filters and subsituable / selectable are too confusing.
Luc Boutier created TOSCA-229: --------------------------------- Summary: Requirements / target filters and subsituable / selectable are too confusing. Key: TOSCA-229 URL: https://issues.oasis-open.org/browse/TOSCA-229 Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC Issue Type: Improvement Components: Profile-YAML, Spec - Simple Profile Reporter: Luc Boutier There is too many notions in the requirements management in the current simple profile document. This makes things very hard to follow while there is actually in my opinion not that many notions to be defined. Target filter makes no sense in my opinion in their current placement (on the node template requirements) as they are duplicated with the selectable directive. I think it would be more consistent to use the 'selectable' directive in every situations rather than relying on target_filter. I also think that selectable pattern is also exactly the same as substitutable from a user perspective as this answer a single need: - I want to link some components to a node that is abstract and I rely on the orchestrator tool to provide a node that match my requirement. The fact that the orchestrator provides a selectable or automatic (substitutable) matching (or both with a best-match) is a tool feature and has no place in the specification in my opinion. The matching and quality of matching feature and presentation of the feature is implementor specific. -- This message was sent by Atlassian JIRA (v6.2.2#6258)