1 / 17

GSAF: A Grid-based Services Transfer F ramework

The GSAF framework aims to dynamically allocate services in grid systems, breaking tight coupling between services and computers. It optimizes resource utilization, provides resource management, and enhances system flexibility.

vicki
Télécharger la présentation

GSAF: A Grid-based Services Transfer F ramework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GSAF: A Grid-based Services Transfer Framework Chunyan Miao, Wang Wei, Zhiqi Shen, Tan Tin Wee

  2. Motivation • Grid provides an integrated computing environment, facilitating maintenance and control of information and other kinds of resources e.g. services. • However, • Existing services are still tied with definite containers. • When new services are deployed,they come to function only after container is restarted.

  3. Objective • Execute services dynamicallyto break the tight coupling between services and computers

  4. Grid Resource Allocation • Grid resource allocation has attracted a lot of attention in recent years: • Globus focuses on providing uniform and scalable mechanisms for namingand locating computational and communication resources on remote systems. • GRASP [1] supports some features for user-friendly resource allocationsuch as resource brokering, scheduling, monitoring, and so forth. • Nassif et al. [2] presented a Multi-Agent System that chooses the best place to run a grid job by making use of negotiation.

  5. GSAF • Existing work mainly focuses on how to find, locate, select and schedule existing static services. • GSAF (A Grid-based ServicesAllocation Framework) is proposed to: • dynamically extend and adjust computing ability ofnodes in grid systems. • balance the total weight by fully utilizing free oridle computing resources. • and provide a form of resource management to improve the flexibility of Systems

  6. GSAF—Resource View • Service components viewed as explicitly manageable resources • GSAF partitions resources into: • Service Components Repository (SCR): logical pool gathering all the available service components • Computing Nodes Repository (CNR): hardware pool gathering available computers • Data Sources Repository (DSR): logical pool gathering all the data related to service components.

  7. GSAF—R-language • R-language: a resource-oriented workflow description language • Three logical elements • Action: a definite resource processing behavior • Scenario: a finite series of actions • Task: scenario which has definite and meaningful purpose according to userrequest.A task is basically a running script

  8. GSAF Architecture • Computers are categorized into two different kinds of nodes: • central nodes: responsible for central management and scheduling such as resource managing and task scheduling • and computing nodes: contribute computingability to run services, i.e. the resources in CNR • Each node is controlled by an agent. The whole system is thus a multi-agent system (MAS).

  9. GSAF Architecture (cont’d) • Architecture of Central Node Agent

  10. GSAF Architecture (cont’d) • Architecture of Computing Node Agent

  11. GSAF Architecture (cont’d)

  12. GSAF Strategies • Use service cacheto deal with the service components swapping: a distinct feature of GSAF. • LRU (Least Recently Used): The least recently used service component in buffer is recorded. If replacement is needed, swat it out. • NRU (Not Recently Used): The service component which hasn't been used in a certain period is recorded. If replacement is needed, swat it out. • FIFO (First-In First-Out): The service components are organized in a queue according to the order of arrival. If replacement is needed, swat out the service at the head of queue.

  13. GSAF—Strategies (cont’d) • Although the best solution is to select the most powerful computer, it may not be practical in real use because of the changings on-the-fly, for example the CPUusage. • A heuristic selection strategy is used in GSAF, namely, weighted ranking.

  14. Prototype • An application of GSAFis implemented in the field of bio data mining system. • Use Globus Toolkit 3.2to provide grid environment. • The modules of central node andcomputing node are implemented as grid services in Java supported byGlobus grid service container.

  15. Conclusion • GSAF is proposed to dynamically allocate services • Swap and execute services dynamicallyto break the tight coupling between services and computers. • All the resources are categorized and managed in corresponding repository. • Dynamic binding among different kinds of resourcesprovides a flexible pattern to execute services • On going and Future work: • Applications ofGSAF to Bio Applications. • Mobile Service Flow on WWW • Trusted Service Grid

  16. Thank You!

  17. References • [1] OGSA(Open Grid Services Architecture) Documents:http://www.globus.org/ogsa • [2] Globus: Research in Resource Management, http://www.globus.org/research/ • [3] L. Nassif, J. M. Nogueira, M. Ahmed, R. Impey, A. Karmouch. Agent-based Negotiation for Resource Allocation in Grid. Workshop on Computational Grids andApplications, 2005 • [4] R. Parra-Hernandez, D. Vanderster and N. J. Dimopoulos. Resource Managementand Knapsack Formulations on the Grid. IEEE/ACM International Workshop onGrid Computing (GRID'04), 2004

More Related