ariatosca-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arthur Berezin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARIA-350) Substitution Mapping
Date Tue, 17 Oct 2017 12:46:00 GMT

     [ https://issues.apache.org/jira/browse/ARIA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arthur Berezin updated ARIA-350:
--------------------------------
    Description: 
Though we parse substitution mappings and create the appropriate models, the orchestrator
does nothing with them.

The idea is for the instantiation module (in the future!) let the reqs-and-caps engine appropriately
connect other existing service templates that could fulfill the requirement. If a match is
made, one big service would be created out of node templates from both service templates.




  was:
Though we parse substitution mappings and create the appropriate models, the orchestrator
does nothing with them.

The idea is for the instantiation module (in the future!) let the reqs-and-caps engine appropriately
connect other existing service templates that could fulfill the requirement. If a match is
made, one big service would be created out of node templates from both service templates.


> Substitution Mapping
> --------------------
>
>                 Key: ARIA-350
>                 URL: https://issues.apache.org/jira/browse/ARIA-350
>             Project: AriaTosca
>          Issue Type: Epic
>            Reporter: Ran Ziv
>
> Though we parse substitution mappings and create the appropriate models, the orchestrator
does nothing with them.
> The idea is for the instantiation module (in the future!) let the reqs-and-caps engine
appropriately connect other existing service templates that could fulfill the requirement.
If a match is made, one big service would be created out of node templates from both service
templates.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message