[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-202) Cardinalities for capabilities and requirements
Luc Boutier created TOSCA-202: --------------------------------- Summary: Cardinalities for capabilities and requirements Key: TOSCA-202 URL: https://issues.oasis-open.org/browse/TOSCA-202 Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC Issue Type: Bug Components: Profile-YAML Reporter: Luc Boutier We should add optional cardinalities parameters to the capabilities (upper_bound) and requirements (lower_bound and upper_bound) on a node. Capabilities bounds being 0 to upper_bound defaults to unbounded (we could have containers that supports only a single application for example and it's important that we can model it). Requirements bounds being lower_bound (defaults to 1) to upper_bound (defaults to 1). -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]