|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ABSTRACT
This paper describes our experiences implementing and operating a globally distributed application composed of services available on a Cloud Computing infrastructure. Intel needed a service that could give us an idea of end users' experiences with Intel Corporation's website from different regions of the globe. We built our monitoring system on top of the PlanetLab distributed systems testbed. Our first implementation relied on static configurations and needed manual intervention to respond to network and node outages. PlanetLab has Cloud Computing and Service Oriented Architecture features that enabled us to increase our application's robustness by using web services for Virtual Machine (VM) allocation, VM provisioning, resource availability, and geographic information. We found that we had to treat service provided resource information like network equipment treats network information. Despite the lack of service level guarantees for PlanetLab VMs and Internet connectivity, we constructed a robust global monitoring service that is used by Intel network personnel today. REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
INDEX TERMS
Primary Classification:
General Terms:
Keywords:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||