RE: [tosca] [OASIS Issue Tracker] (TOSCA-233) How to handle VM image in terms of software component

[Chris Lauwers <lauwers@ubicity.com>]

It seems to me that this is an implementation issue. What's important is that the ISO "artifact" is uniquely identified by its URL. Tosca support for artifacts let you do this. The orchestrator could decide to download the ISO file every time, or it could decide to "cache" it locally. 

Chris

-----Original Message-----
From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of OASIS Issues Tracker
Sent: Monday, September 21, 2015 7:09 AM
To: tosca@lists.oasis-open.org
Subject: [tosca] [OASIS Issue Tracker] (TOSCA-233) How to handle VM image in terms of software component


    [ https://issues.oasis-open.org/browse/TOSCA-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60746#comment-60746 ] 

Luca Gioppo commented on TOSCA-233:
-----------------------------------

My problem is that just stating that there is an image is not enough for mapping all cases.
For an ISO image for example:
- I could declare it as an ISO as the "template" to use in CloudStack to generate the new VM but the ISO could be there or I could need to upload it to the environment.
How do we want the orchestrator behave in this case? If I specify the URL of the image for example is not clear if I want it to place in the cloud, just check if the ISO is already there, force an update of the ISO in the cloud env.

> How to handle VM image in terms of software component
> -----------------------------------------------------
>
>                 Key: TOSCA-233
>                 URL: https://issues.oasis-open.org/browse/TOSCA-233
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Profile-YAML
>    Affects Versions: CSD03
>            Reporter: shitao li
>
> The different types of artifact (such as ovf image, docker image ) expose different capabilities. Right now, there is no common software component can handle arbitrary artifact. 
> Once the artifact has put into a node, how do we expose its capability, we need a general mechanism. 
> This issue is related to docker and NFV VDU use cases.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php