Dvorak,  F.

Filipovic,  J.

Kouril,  D.

Matyska,  L.

Poul,  M.

Sitera,  J.

Sustr, Z.

Vocu,  M.

English

ZENODO

Monitoring Virtual Machine Statuswith L&BSˇustr, Z., Sitera, J., Filipovicˇ, J., Dvoˇra´k, F.,Voc˚u, M., Kouˇril, D., Poul, M., Matyska, L.CESNET, Czech RepublicL&B IntroductionThe Logging and Bookkeeping service• Long-standing part of the gLite middleware (EDG, EGEE, EMI)– Monitoring production compute jobs, mostly WMS– Back-end to the well known glite-wms-job-statuscommand• Collects event messages from grid elements• Processes the information• Publishes status information in several ways:– query/response interface – L&B querying API/HTML– subscribe/publish interface – L&B notificationsI OpenWire/STOMP, RSS, L&B legacy• Supports multiple types of grid processes– Compute jobs, collections, file transfers– Newest addition: Virtual MachinesPrague, 19 September 2012 2L&B: a Message Processing UnitFig. 1: L&B receiving and producing messages over different channelsPrague, 19 September 2012 3Virtual Machine Status InfoVirtual Machine (VM) Life Cycle• Obvious similarities with a compute job life cycle– Well-defined life span– State transitions triggered by event messages– Shared infrastructure• Even more similarity with pilot jobs– Start up with no specific payload defined– Attract attention when ready, get assigned payload• Added benefits of using grid monitoring tools– Already in place– The same tool (L&B) can be used to monitor both layers– Easy to keep track of VM-Payload relationship• VM seen as “just another job type”Prague, 19 September 2012 4Status Diagram• Inspired by Open Nebula 3.0specification• Driven by events collected frommultiple sources:– Open Nebula or another VM manager– Hypervisor such as Xen– Actual VM instance• Event logging instrumented through– a client library (C, C++, Java)– command line tools• VM-specific states mapped to genericgLite states for universal queriesFig. 2: VM state diagramPrague, 19 September 2012 5Event SourcesComponent Events AttributesCloudManager Register, Create, Running,Host detail, Shutdown,DoneHostname, Physical hostname, Owner, Require-ments. . .VM Image Really Running, Shutdown Runtime information, usertagsHypervisor Running, Shutdown• Some types of events received from multiple components– Provide for redundancy and fine-grained monitoring– Fill in details known only at certain levelPrague, 19 September 2012 6Job Relationships• Extension of known L&B concept• Previously: specific case implementations– subjobs ↔ collection/DAG parents– compute jobs ↔ sandbox transfers• New: generic bilateral relationship– Registered/updated by events– Relationship status record maintainedI Distinguishes active from past relationships– One of intended uses: linking compute jobs to VMsI Typically registered by batch system, known to both jobsFig. 3: Jobs related to a VM – a screenshotPrague, 19 September 2012 7Benefits brought in by L&B• Per-job ACL-based authorization• Robust state interpretation– Resistant to events delivered out of order or not delivered at all• Highly configurable output– Applies to synchronous queries as well as generated messagestreams– Complex sets of conditions supportedI Messages sent over certain channels only if conditions are metPrague, 19 September 2012 8Summary• Existing grid component has been extended to follow VMs as“another type of job”• Keeping track of relationships with payload – regular computejobs of different kinds• Multiple chnannels available for receiving output, either byquery or broadcast• Potential for supporting event input over many channelsPrague, 19 September 2012 9ThanksThank YouPrague, 19 September 2012 10

Monitoring Virtual Machine Status with L&B

https://zenodo.org/record/6579/files/lb-vm.pdf

Monitoring Virtual Machine Status with L&B

Abstract

Similar works

Full text

Available Versions

ZENODO