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-99) Use Case: Patching a deployed service template (e.g. an OS node)


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

Derek Palma commented on TOSCA-99:
----------------------------------

Patching is specific case of update where a deployment exists and it is desired to change some aspect of it such as: a) replacing one or more components; b) changing the configuration of one ore more components (e.g. update a property); c) changing one or more parts of the topology. These are not only very general operations but very common activities which occur after initial deployment.

The TOSCA TC could decide to support these kinds of updates or just state they are out of scope.

Each of these kinds of updates could be supported by editing the current Service Template and passing it to the TOSCA container so it can orchestrate the necessary changes to reflect the new Service Template.




> 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

        


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