https://github.com/ow2-proactive/connector-cloud

https://github.com/ow2-proactive/connector-cloud

Last synced: over 1 year ago
JSON representation

• Host: GitHub
• URL: https://github.com/ow2-proactive/connector-cloud
• Owner: ow2-proactive
• Created: 2015-05-16T13:38:52.000Z (about 11 years ago)
• Default Branch: master
• Last Pushed: 2016-04-08T11:52:57.000Z (about 10 years ago)
• Last Synced: 2025-01-25T17:15:48.103Z (over 1 year ago)
• Language: Java
• Size: 23.4 MB
• Stars: 0
• Watchers: 22
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README-monitoring.txt

Awesome Lists containing this project

README

          
### README MONITORING ###

Monitoring mechanisms can be activated to retrieve information from the IaaS infrastructure. 

Monitoring configuration parameters are passed as any other Infrastructure parameter while creating the 

Node Source. One example of monitoring parameter is as follows: 

 

   $ ./bin/unix/rm-client -c config/authentication/rm.cred -cn NSNAME --infrastructure org.ow2.proactive.iaas.nova.NovaInfrastructure rmi://localhost:1234/ 0 http://openstack.cloud.univcloud.fr:5000/v2.0 'monitoringEnabled,showVMProcessesOnHost,useApi,cred=config/authentication/rm.cred,hostsfile=../monitoringHosts,useRMNodeOnHost,useRMNodeOnVM' admin activeeon Admin cfd45429-9535-40ca-921d-a1f8fa792d9b 1 "config/authentication/rm.cred" 

### MONITORING PARAMETERS

The format is as follows: 

   '[,OPTION1][,OPTION2=VALUE][,OPTION3]...'

## Mandatory parameters

   

      Tells if monitoring features will be enabled or not. If disabled no other parameter will be 

      taken into account.

## Optional parameters

# API parameters

   useApi

      Use the IaaS API to get monitoring information.

# Sigar monitoring parameters

   useRMNodeOnHost

      If present, the monitoring system will assume an RMNode is running on every Host.

   useRMNodeOnVM

      If present, the monitoring system will assume an RMNode is running on every VM, and also that it joined 

      the RM.

   cred=

      If provided, the monitoring system will retrieve monitoring information from hosts/hypervisors 

      through Sigar. The Sigar MBean will be exposed by the standard RMNode. The RMNode Sigar MBean 

      will be contacted using the provided credential. Hosts/hypervisors monitored this way need to 

      run an RMNode connected to the RM, but withouth being added as a node (it means having the 

      parameter addNodeAttempts set to 0, as follows:  

      '/bin/unix/rm-start-node ... --addNodeAttempts 0 ...').

   hostsfile=

      Use this file to list the set of hosts that will have to be monitored through Sigar. 

      The file format is a standard java Properties file. It contains entries with format name=jmxrourl. 

   showVMProcessesOnHost  

      If present, when providing information about a Host, the system will show VM processes information (like kvm

      processes) running on the host. Requires flag useRMNodeOnHost.

# Cache parameters

Every VM or Host set of properties can be cached. There are 2 caches. A VM properties cache (a map vmid:mapofprops) 

and a Hosts properties cache (a map hostid:mapofprops).

   maximumCacheEntries=

      Maximum amount of cache entries for each cache.

   autoUpdateCache

      If present, each cache will be updated regularly even if no miss occurs. 

   refreshPeriodSeconds=

      Determines the period for refresh of each cache.

   expirationTimeSeconds=

      Determines the time it takes for a simple entry (of any cache) to be considered as stale (time measured from 

      the last time a write for the entry took place).