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] Commented: (TOSCA-28) Selection of DeploymentArtifacts for a NodeTemplate


    [ http://tools.oasis-open.org/issues/browse/TOSCA-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30958#action_30958 ] 

Paul Lipton  commented on TOSCA-28:
-----------------------------------

Discussed on 8/16. From chat (Derek and others please elaborate in comments below), an overview:

[12:51] Derek Palma (Vnomic): TOSCA-28: The changes we are considering are to leverage the thinking for matching requirement and capabilities where we use constraint expressions for matching. However, instead of using requirement and capability types, the deployment artifact would explicitly specify the node type it is able to materialize to allow type based selection of candidates.
[12:52] Derek Palma (Vnomic): Selection would be by type, to find the candidates, and then using the constraints to select final single deployment artifact.

This will be discussed again on 8/30, will probably vote on it on 8/30, too. 


> Selection of DeploymentArtifacts for a NodeTemplate
> ---------------------------------------------------
>
>                 Key: TOSCA-28
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-28
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Derek Palma
>            Assignee: Derek Palma
>
> In the SugarCRM use case we have situations where the selection of DeploymentArtifacts is a function of the deployment context. For example:
> 1) When a specific cloud is deployed to, the appropriate image be provided or selected.
> 2) When a specific OS is only available or desirable the appropriate packages for that OS must be installed. E.g. for Redhat RPMs as well as correct binaries etc.
> 3) Selection of a specific hosting component (or subsystem) based on the environment or other contextual dependencies. For example, the version or features of the Apache web server.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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