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-215) Ability to Manage node(s) by a Manager node


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

Chris Lauwers commented on TOSCA-215:
-------------------------------------

Could this requirement be addressed using a combination of composition (e.g. as provided by the current nested templates proposal) and delegation (a proposed feature where the orchestrator could delegate lifecycle operations for some components to an external entity)?

> Ability to Manage node(s) by a Manager node
> -------------------------------------------
>
>                 Key: TOSCA-215
>                 URL: https://issues.oasis-open.org/browse/TOSCA-215
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Spec - Simple Profile
>            Reporter: Sahdev Zala 
>
> Provide an ability to create a ‘Manager’ node which can manage one or more ‘Manage’ node. The Manager node can configure Mange node(s) and do other things like passing certain properties between nodes. Manage node should able to provide notification for Manger to take needed actions. 
> This is very important in order to embed an agent or orchestrator as part of TOSCA deployment. 
> This is a high level description and I am opening it up for further discussion. 



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


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