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: RE: [tosca] [OASIS Issue Tracker] (TOSCA-216) General Issues for Monitoring Ad Hoc Group


In my opinion, the monitoring system needs to be an integral part of the orchestrator. We can't talk about things like "scaling policies" unless "scaling" is defined as an operation that's performed by an orchestrator. Policies regulate operations, and we can't have policies without first defining the operations they regulate.

Furthermore, if scaling (and scaling policies) is something the orchestrator does, then the mechanism for obtaining the inputs into those policies needs to be part of the orchestrator as well.  Since those inputs can only come from a monitoring system, the monitoring system needs to be an integral part of the orchestrator.

If a monitoring system is part of the orchestration system, then all we need in the template is some indication of which attributes are being monitored and feed into the policies.

Chris


-----Original Message-----
From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of OASIS Issues Tracker
Sent: Monday, September 21, 2015 6:56 AM
To: tosca@lists.oasis-open.org
Subject: [tosca] [OASIS Issue Tracker] (TOSCA-216) General Issues for Monitoring Ad Hoc Group


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

Luca Gioppo commented on TOSCA-216:
-----------------------------------

We need to express the need to attach to the service template the knowledge of HOW to link to the monitoring system.

We need to agree if the monitoring system is something external to the "service" if yes we need to define how (in a descriptive way and not imperative) state that a generic node needs to be linked to the monitoring.

Depending on the node the operations connected to this "description" will be either adding an agent to a host and opening firewall etc.


> General Issues for Monitoring Ad Hoc Group
> -------------------------------------------
>
>                 Key: TOSCA-216
>                 URL: https://issues.oasis-open.org/browse/TOSCA-216
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Monitoring
>            Reporter: Paul Lipton
>            Assignee: Chip Holden
>
> Please feel free to add questions or comments concerning monitoring in TOSCA to this ticket. We will review them in the TOSCA Monitoring ad hoc (https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=38956). Please contact Ifat Afek or Chip Holden for invite information.
> An initial proposal is being worked in TOSCA-189.



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

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 



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