OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [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=61219#comment-61219 ] 

Chris Lauwers commented on TOSCA-233:

Hi Luca, I completely agree with your observation. In fact, we had exactly this discussion in the YAML meeting a couple of weeks ago. We currently model Docker containers as "Container" nodes instead of "Software Component" nodes. From a modeling point-of-view, what really matters is the software component and its associated interfaces, capabilities, requirements, properties, and attributes. Whether the software component is packaged as a Docker container, a VM, or is installed using a bunch of scripts isn't really important from a modeling point of view. Of course those things are important from a deployment point-of-view, so it's important to know which deployment artifacts are associated with the software component (docker image vs. VM vs. install scripts). This means that the same software components could come packaged with different deployment artifacts.

So, if we adopted your approach where everything is modeled as a software component and docker images and VMs are just deployment artifacts associated with those software component, then we could think about adding operations not just for deploying software components from those artifacts, but also for creating new artifacts for deployed software components. For example, it should be possible to deploy a software component from a set of install scripts and then create a docker image deployment artifact from that software component. We can't do that if docker containers are modeled as "containers" instead of software components.

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]