[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-188) Requirements section should be turned to a map instead of list
[ https://issues.oasis-open.org/browse/TOSCA-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] noa koffman updated TOSCA-188: ------------------------------ Description: Requirements section is currently a list, however since the get_attribute function allows to refer to a requirement by name, it forces the requirements names to be unique. This limitation implicitly forces the section to behave as a map, and I think this should be expressed explicitly by turning the section in to a map, like the current capabilities section. current situation: software: type: tosca.nodes.SoftwareComponent properties:... attributes: ip_address: {get_attribute: [ SELF, host, ip_address] } #which host??? requirements: # the get attribute expression is referring to host, however there can be multiple "host" # requirements, and each can have different attribute values. - host: server_be relationship: tosca.relationships.HostedOn - host: server_fe relationship: tosca.relationships.HostedOn server_be: type: tosca.nodes.Compute ... server_fe: type: tosca.nodes.Compute ... proposed fix: software: type: tosca.nodes.SoftwareComponent properties:... attributes: ip_address: {get_attribute: [ SELF, host_be, ip_address] } requirements: # in this case the reference will be mapped uniquely to the one matching requirement name. host_be: # names are forced to be unique target: server_be relationship: tosca.relationships.HostedOn host_fe: # names are forced to be unique target: server_fe relationship: tosca.relationships.HostedOn server_be: type: tosca.nodes.Compute ... server_fe: type: tosca.nodes.Compute ... was:Requirements section is currently a list, however since the get_attribute function allows to refer to a requirement by name, it forces the requirements names to be unique. This limitation implicitly forces the section to behave as a map, and I think this should be expressed explicitly by turning the section in to a map, like the current capabilities section. > Requirements section should be turned to a map instead of list > -------------------------------------------------------------- > > Key: TOSCA-188 > URL: https://issues.oasis-open.org/browse/TOSCA-188 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: Bug > Components: Spec - Simple Profile > Reporter: noa koffman > > Requirements section is currently a list, however since the get_attribute function allows to refer to a requirement by name, it forces the requirements names to be unique. This limitation implicitly forces the section to behave as a map, and I think this should be expressed explicitly by turning the section in to a map, like the current capabilities section. > current situation: > software: > type: tosca.nodes.SoftwareComponent > properties:... > attributes: > ip_address: {get_attribute: [ SELF, host, ip_address] } #which host??? > requirements: > # the get attribute expression is referring to host, however there can be multiple "host" > # requirements, and each can have different attribute values. > - host: server_be > relationship: tosca.relationships.HostedOn > - host: server_fe > relationship: tosca.relationships.HostedOn > server_be: > type: tosca.nodes.Compute > ... > > server_fe: > type: tosca.nodes.Compute > ... > proposed fix: > software: > type: tosca.nodes.SoftwareComponent > properties:... > attributes: > ip_address: {get_attribute: [ SELF, host_be, ip_address] } > requirements: > # in this case the reference will be mapped uniquely to the one matching requirement name. > host_be: # names are forced to be unique > target: server_be > relationship: tosca.relationships.HostedOn > host_fe: # names are forced to be unique > target: server_fe > relationship: tosca.relationships.HostedOn > server_be: > type: tosca.nodes.Compute > ... > > server_fe: > type: tosca.nodes.Compute > ... -- 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]