[OASIS Issue Tracker] Commented: (TOSCA-99) Use Case: Patching a deployed service template (e.g. an OS node)

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Frank Leymann  commented on TOSCA-99:
-------------------------------------

I single lifecycle operation may often not be enough. I consider this a typical use case for plans.

> Use Case: Patching a deployed service template (e.g. an OS node)
> ----------------------------------------------------------------
>
>                 Key: TOSCA-99
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-99
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Interop
>         Environment: Use case for development against TOSCA-v1.0-cs01.
>            Reporter: Matthew Rutkowski 
>            Assignee: Derek Palma
>
> How is it known if the patch should/can be applied? For OS level patches. (framework, middleware, and app patches too) 
> Example:
> TBD
> Notes:
> Matt: Note: this is a lifecycle operation that is post-deploy.  What do we need during deployment on nodes to enable this at a later time? Versions constrainst?  Notifications?
> Reference:
> https://www.oasis-open.org/apps/org/workgroup/tosca-interop/download.php/48514/ConsiderationsFor2TierWebApplications.docx

-- 
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