[
https://issues.apache.org/jira/browse/ARIA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Berezin updated ARIA-350:
--------------------------------
Comment: was deleted
(was: The design doc:
https://drive.google.com/open?id=19nPjSj6mJyXWd4KLxPqRNp_TPqLpvXjzj98NXrAmcjc
Additional v1.2 issues (a non-exhaustive list):
https://docs.google.com/document/d/18yZC8qIWMbWBeULOzmLTT_oVrZXQ3z4030U6JIXdJ84/edit
)
> 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.
> The design doc:
> https://drive.google.com/open?id=19nPjSj6mJyXWd4KLxPqRNp_TPqLpvXjzj98NXrAmcjc
> Additional v1.2 issues (a non-exhaustive list):
> https://docs.google.com/document/d/18yZC8qIWMbWBeULOzmLTT_oVrZXQ3z4030U6JIXdJ84/edit
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
