Difference between revisions of "Fedcloud-tf:WorkGroups:Scenario5"

From EGIWiki
Jump to: navigation, search
(References)
(Redirected page to Federated Cloud Monitoring)
 
(5 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}}
+
#REDIRECT[[Federated_Cloud_Monitoring]]
 
 
== Scenario 5: Reliability/Availability of Resource Providers  ==
 
 
 
<font color="red">Leader: Emir Imamagic, SRCE</font>
 
 
 
== Scenario collaborators  ==
 
 
 
{| border="1"
 
|-
 
! Role
 
! Institution
 
! Name
 
|-
 
| Scenario leader
 
| SRCE
 
| Emir Imamagic
 
|-
 
| Collaborator
 
| INFN
 
| Daniele Cesini
 
|-
 
| Collaborator
 
| CESGA
 
| Ivan Diaz
 
|-
 
| Collaborator
 
| CESGA
 
| Alvaro Simon
 
|}
 
 
 
<br>
 
 
 
== What Monitoring means in this context  ==
 
 
 
Monitoring in this context is the monitoring of the availability and reliability of the cloud resources provided by the resource providers. What will be tested is the possibility for an hypothetical user to instantiate at least one predefined virtual machine within a given period of time. It consists of an "external" monitoring, no data will be collected from inside the VMs or underlying virtualization systems. Monitoring the capabilities of the cloud resource providers in terms of how many resources are available is beyond the scope of this Scenario, at least in its initial phase. Possible evolution of the FedCloud monitoring will be evaluated when the basic monitoring will be in place.
 
 
 
The outcome of Scenario5 will be a system that is able to run at least one probe on each Resource Provider paticipating to the FedCloud.
 
 
 
Given the experience accumulated with the [http://www.nagios.org NAGIOS] system within the EMI and EGI projects the monitoring framework will be based on NAGIOS. This has also the advantage to ease the integration of the FedCloud monitoring framework in the [https://wiki.egi.eu/wiki/SAM SAM] monitoring sytem used by the EGI project to monitor the production infrastructure.
 
 
 
== Integration with EGI operational tools  ==
 
 
 
=== GOCDB  ===
 
 
 
The following '''service types''' can be added to GOCDB:
 
 
 
*eu.egi.cloud.accounting (required)
 
*eu.egi.cloud.information.bdii (required)
 
*eu.egi.cloud.storage-management.cdmi&nbsp;
 
*eu.egi.cloud.vm-management.occi (required)
 
*eu.egi.cloud.vm-metadata.marketplace
 
 
 
All RPs must enter cloud service endpoints to GOCDB in order to enable integration with other operational tools.
 
 
 
First step is defining site to which the endpoints will belong. There are two possible options:
 
 
 
'''1.''' Register resources on an existing EGI site
 
 
 
*pre-reqs:
 
**RP is associated with the existing site and the team handling existing grid services is the same/very close with the cloud team
 
**site's Certification Status is "Certified"
 
 
 
'''2.''' Register resources on a new site
 
 
 
*new site should have the following settings:
 
**Infrastructure: 'Production'
 
**Certification Status: 'Candidate'
 
*check the example of NGI_GRNET site: https://goc.egi.eu/portal/index.php?Page_Type=View_Object&amp;object_id=119660&amp;grid_id=0
 
 
 
In both cases service endpoints should have the following flags set:
 
 
 
*Production: 'N' (If the site is ready to certify the service please contact the fedcloud list first)
 
*Beta: 'N'
 
*Monitored: 'Y'
 
 
 
Special rules apply for the following service types:
 
 
 
*eu.egi.cloud.storage-management.cdmi: '''Endpoint URL''' field must contain the following info:
 
 
 
http[s]://hostname:port
 
 
 
*eu.egi.cloud.vm-management.occi: '''Endpoint URL''' field must contain the following info:
 
 
 
https://hostname:port/?image=&lt;image_name&gt;&amp;resource=&lt;resource_name&gt;
 
 
 
Both &lt;image_name&gt; and &lt;resource_name&gt; cannot contain spaces. These attributes map to os_tpl and resource_tpl respectively.
 
 
 
Further information about GOCDB can be find on the following page: [[GOCDB/Input System User Documentation]].
 
 
 
=== SAM ===
 
 
 
Central SAM instance is deployed for monitoring cloud resources. Once the set of probes is fully defined probes will be included to official SAM release. Once included to official release central instance will be switched off.
 
 
 
SAM instance is on the following address: https://cloudmon.egi.eu/nagios.
 
 
 
Detailed description of tests can be found [[Cloud_SAM_tests|here]].
 
 
 
== Technology ==
 
 
 
 
 
=== Nagios probes  ===
 
 
 
'''Who has the responsibility to develop probes?''' Following the EGI model probes are developed by the Technology Providers and are integrated into the monitoring framework by the EGI-JRA1 staff that can also provide support during the initial phase of probes development in order to give guidelines and templates.
 
 
 
'''Information''' on how to develop NAGIOS probes can be retrieved in the [https://tomtools.cern.ch/confluence/display/SAMDOC/Probes+Development SAM Development Guide]
 
 
 
'''List of available probes '''within EGI is reported in the [https://tomtools.cern.ch/confluence/display/SAMDOC/Released+Probes SAM Administrrator Guide]
 
 
 
=== The EGI SAM&nbsp;System  ===
 
 
 
The SAM system is basically a framework consisting of: <br>- Nagios monitoring system (https://[http://www.nagios.org/ www.nagios.org]), <br>- custom databases for topology, probes description and storing results of tests <br>- web interface MyWLCG/MyEGI ([https://tomtools.cern.ch/confluence/display/SAM/MyWLCG https://tomtools.cern.ch/confluence/display/SAM/MyWLCG]) <br>Probes used to perform check of services are provided by service developers. In case of EMI services probes are provided by EMI product teams. In case of Globus Toolkit, probes are provided by IGE project, etc. SAM team only maintains probes which test internal SAM functions (e.g. communication with messaging system, database synchronization, etc).
 
 
 
More information on SAM can be found [[SAM|here]].
 
 
 
== Activities ==
 
 
 
{| class="wikitable"
 
!Probe
 
!Description
 
!Responsible
 
!Deadline
 
!Status
 
|-
 
|OCCI - extensions
 
|Decided on F2F to deploy contextualization tests, which are already implemented. Tasks:
 
* check if this can be applied to all OCCI endpoints
 
* probe configuration
 
* define test name.
 
|Boris Parak, Emir Imamagic
 
|February 2015.
 
|IN PROGRESS
 
|-
 
|CDMI
 
|Decided on F2F to implement a lightweight probe that will be similar to existing SRM probe.
 
|Emir Imamagic
 
|February 2015.
 
|IN PROGRESS
 
|-
 
|APEL
 
|Decided on F2F to rewrite APEL tests to be consistent with grid sites (APEL-Pub only).  Tasks:
 
* implement publishing mechanism on APEL side
 
* define topic name & configure cloudmon consumer to listen to it
 
* define test name.
 
|Stuart Pullinger, Emir Imamagic
 
|?? 2015.
 
|IN PROGRESS
 
|}
 
 
 
== References  ==
 
 
 
[[SAM|The SAM system EGi wiki pages]]
 
 
 
[[Image:Flessr nagios probes.pdf|FleSSR Nagios Cloud Probes Document]] (Thanks to David Wallom)
 

Latest revision as of 13:09, 8 June 2015