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-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=59848#comment-59848 ] 

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

As a follow up to yesterday meeting.
my needs on monitoring are of 2 types:
1) monitoring resources for "operation sake"
2) monitoring business events for "billing/analysis sake"

I think that we now need to concentrate on the first point.
In this case the monitoring system as stated is external and usually the timing of monitoring is decided in the central server (in my case Zabbix, but could be Nagios etc)
What I need is a way in tosca to express the fact that a specific node is monitored and maybe to state some "monitoring tool" specific information (so using properties here) that allows the orchestrator to do the magic.
To go into detail I'm planning on defining a node type for zabbix agent since this component needs to be installed together with the topology and I will use a reletion between the agent and the node to express what I will monitor.
Than I will need an "abstract" node (that is one that will not be managed by the orchestrator, but that the orchestrator has to be able to find to manage the zabbix server in this way with a relation between the zabbix's agent node and the abstract zabbix server node I plan to manage to express the needed configurations.
The problem is on how to express this in a way that is interoperable that is without creating a "zabbix" set of nodes (otherwise my tosca file will run only on orchestrators that implement that node type definition)
A possible solution could be to create a generic agent node and adding a set of info that can be generic enough to represent the comunication port between the agent and the server.

Is this something in line with what you were defining?

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


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