Your SlideShare is downloading. ×
Distributed System Lab. 1 Grid Virtualization Engine: Design ...
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Distributed System Lab. 1 Grid Virtualization Engine: Design ...

345
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
345
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Grid Virtualization Engine: Design, Implementation, and Evaluation Lizhe Wang, Senior Member, IEEE, Gregor von Laszewski, Member, IEEE, Jie Tao, and Marcel Kunze 報告人:倪丞頤
  • 2. Outline
    • Introduction
    • Purpose
    • Detail about GVE
    • Implementation
    • Experiments
    • Conclusion
  • 3. Introduction
    • Virtual machines offer various advantages which can help Grid communities to solve research issues.
    • The work proposed in this paper focuses on building a Web service based virtual machine provider for Grid infrastructures.
  • 4. Difficulties of Grid Computing
    • Qualities of service (QoS) of resource provision and performance isolation.
    • Configurations of customized runtime environment for Grid applications need administration privileges
  • 5. Virtualization’s Benefit for Grid Systems
    • On demand creation and customization
      • Users can create a customized VM
    • Performance isolation
      • VM’s Users can expect dedicated computing environments
    • Legacy software support
      • Customized VM are compatible
    • Easy management
      • VM can offer users with the “root” access
  • 6. Challenges for VM-based Grid Systems
    • Site Autonomy
      • The host resources are commonly owned and controlled by different institutes or organizations.
    • Hierarchy
      • A virtual machine-based Grid system is hierarchical in nature.
    • Heterogeneity
      • A VM based Grid system includes various virtual machine.
    • Large scale distribution
      • Computing and data centers frequently build Grid across distributed sites.
  • 7. Grid Virtualization Engine (GVE)
    • The GVE is light weight distributed middleware, which enables users to operate virtual machines and provides virtual distributed environments across distributed computing centers.
  • 8. Aims & Unique Contribution
    • To work in a large scale distributed Grid infrastructure.
    • Defines a hierarchical virtual machine based Grid system model.
    • Builds a scalable and efficient GVE service that can provide virtual machine resources to Grid system based on popular VMMs.
    • Makes a performance evaluation on GVE and virtual machines with a nontrival application.
    • Provides our experience of employing virtual machine resources for Grid infrastructures.
  • 9. VM-Based Grid System Model
  • 10. VM-Based Grid System Model
    • Access Service
      • Allows remote users to access resources of the computer center.
      • The GVE service is developed and integrated in this level.
    • Virtual Machines
      • GVE service operates on virtual machines in this level.
    • Host Resources
      • Which are installed with virtual machine hypervisors.
      • The GVE Agent Service is implemented in this level with aids of VMM APIs and SDKs.
  • 11. Architecture of GVE
  • 12. GVE
    • GVE Site Service
      • Which resides on the access point of a Computer Site
      • Communicates with GVE Agents
    • GVE Agents
      • Which are responsible for accepting requirements from GVE Site service.
      • Organizing the requirements and passing the requirements to proper underlying VMMs with corresponding APIs, commands, and messages.
    • Virtual Machine Disk Database
  • 13. GVE Site Service
    • It manages host resources inside the center by communicating with the GVE Agent Services
    • GVE Web Service
      • It decides the Agent Service to which virtual machine requests should be sent and defines the policies of resource allocation.
    • User Information Service
      • Make an inventory of the data that the GVE Site Service needs to store and create an interface that provides methods to store and manage data.
    • User Information Database
      • Records the management policies and accounting information of virtual machine usage.
      • The place where the user information and the virtual machine information is stored.
  • 14. GVE Agent Service
    • Run on the host resources and is virtualization technology dependent.
    • All GVE Agent Services implement the same Web Service interface.
    • The Registry Service provides the following functions to access the Registry Database, which stores the state of virtual machines, the GVE Site information, the state of the virtual machine request and management.
    • The Virtual Machine Disk Database may not be directly implemented by the GVE developer.
  • 15. Use Case of GVE
  • 16. Implementation of GVE
    • To define the services provided by describing them using Web Service Description Language (WSDL).
    • Java interfaces and Web Service artifacts are generated using JAXB.
    • To create a database and a Java interface to access and manage the database.
    • For the GVE Site Service, the User Information Database is created.
    • The Java interfaces and classes are implemented according to their functions and roles with VMM APIs.
  • 17. GVE Site Service Implementation
    • The User Information Service is a Web service used by the GVE Site Service to access and to manage the data stored in the User Information Database.
    • The User Information Database is defined with the data entities of Agent services, virtual machines and user information.
    • The GVE Site Service defines various Web Service portTypes in the WSDL file.
    • Job, RequestVirtualMachine or GetRequestVirtualMachineResult, means a virtual machine request or a virtual machine management operation.
    • The JobState is the object returned to GVE clients
  • 18. Implementation of the GVE Agent Service
    • The Agent Web service implements a lot of operations about VM with underlying Virtual Machine Monitor APIs.
    • Implementation of Registry Service and Disk Database Access
      • The data structures are defined firstly.
      • The interface of the Registry Service is then defined in the WSDL file, which contains the portTypes.
      • The implementation of the interface termed as DataProvider.
      • The Registry Database tables are generated at runtime.
    • VMware Infrastructure SDK does not provide APIs
      • Solved by InstallService, deploying an extraWeb Service component in VM
  • 19. GVE instance start overhead The max overhead of starting time is around 17%
  • 20. GVE network performance The throughputs between virtual machines can reach around 90% of those between real machines.
  • 21. CMS Performance Evaluation OSCAR test results ORCA-digi test results ORCA-dst test results Pythia test results
  • 22. CMS Performance Evaluation OSCAR test results ROOT test results In General, VM can attain 70%-95% performance of real machines.
  • 23. Service composition of workflow system
  • 24. Execution process of the workflow services
  • 25. Conclusion
    • GVE is a software layer which resides between users and various Virtual Machine implementations.
    • The GVE is designed and implemented in modularity.
    • The GVE is designed and implemented in the hierarchical flavor.
  • 26. Future Work
    • Development of industrial security control mechanism.
    • Accommodation of more virtual machine technologies.
    • Moving the GVE work into the Cloud computing context.