====== Meta-scheduling Infrastructures with GridWay ====== ===== Enterprise Grid Infrastructures ===== Enterprise grids enable diverse resource sharing to improve internal collaboration and achieve a better return from information technology investment. Available resources within a company are better exploited and the administrative overhead is minimized by using Grid technology. The resources are part of the same administrative domain. Theses infrastructures require a centralized approach for scheduling and accounting. The administrator must be able to apply centralized usage policies and access to global reporting and accounting. Enterprise grid infrastructures require meta-schedulers to provide support for multiple users in a single scheduling instance. **Figure 2. Enterprise Grid deployment with GridWay.** {{ documentation:administrator:gw_enterprise.png |Enterprise Grid deployment with GridWay. }}\\ ===== Partner Grid Infrastructures ===== Partner grid infrastructures of several scales are being deployed within the context of different research projects, whose final goal is to provide large-scale, secure and reliable sharing of resources among partner organizations and supply-chain participants. Such partner grids allow access to a higher computing performance to satisfy peak demands and also provide support to face collaborative projects. The multiple administration domains existing in a partner grid infrastructure prevent the deployment of centralized meta-schedulers, with total control over client requests and resource status. Organization-level meta-schedulers provide support for multiple intra-organization users in each scheduling instance. This means that there is one scheduling instance for each organization, and all scheduling instances compete with each other for the available resources. **Figure 3. Partner Grid deployment with GridWay.** {{ documentation:administrator:gw_partner.png |Partner Grid deployment with GridWay.}}\\ ===== Federation of Grid Infrastructures ===== Please visit the web page about [[ecosystem:gridgateway| GridGateWay]] to find out how to deploy federated grid infrastructures using Globus and GridWay. A WS-GRAM service hosting a GridWay meta-scheduler provides the standard functionality required to implement a gateway to a federated grid. That is to virtualize a whole grid, providing a powerful abstraction of the underlying grid resource management services. **Figure 4. Grid Federation with GridWay and GridGateWays.** {{ documentation:administrator:gw_federation.png |Grid Federation with GridWay and GridGateWays.}}\\