You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ariatosca.apache.org by "Ran Ziv (JIRA)" <ji...@apache.org> on 2017/08/16 08:53:00 UTC
[jira] [Assigned] (ARIA-350) Substitution Mapping
[ https://issues.apache.org/jira/browse/ARIA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ran Ziv reassigned ARIA-350:
----------------------------
Assignee: Ran Ziv (was: Avia Efrat)
> Substitution Mapping
> --------------------
>
> Key: ARIA-350
> URL: https://issues.apache.org/jira/browse/ARIA-350
> Project: AriaTosca
> Issue Type: Epic
> Reporter: Ran Ziv
> Assignee: 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)