Information Technology Reference
In-Depth Information
4.2.2 Cascading DCI Bridges
Several DCI Bridge objects may coexist within the same gUSE environment. These
DCI Bridges can be connected together in a treelike way (Fig. 4.2 ). Notice that this
cascading of DCI Bridge services is possible because they all use the JSDL job
submission description which contains information on the resource and target
storages required for input and output
file staging. This feature of the DCI Bridge is
exploited in creating a solution for the direct connection of gUSE with clouds
(Sect. 4.5 ). The
first connected DCI Bridge (object) is distinguished, and we call it
the Master DCI Bridge (this is the root of the DCI Bridge tree). It can be con
gured
via the Information portlet (Resource tab) within the WS-PGRADE portal. All other
eventual DCI Bridges must be con
gured by using their explicit URLs. All visible
resources should be presented by their names within the Master DCI Bridge. This
rather restrictive condition has a very simple cause: the front end of the
WS-PGRADE/gUSE system is not able (for the time being) to walk over the
internal chains of the connected DCI Bridge objects, i.e., it
only the Master
DCI Bridge. However, the real access properties of the mentioned resources may be
described in different DCI Bridges.
The use of several DCI Bridges can provide seamless load-balancing between
multiple DCIs. The load-balancing is implemented through the Master DCI Bridge,
sees
Fig. 4.2 Treelike connection of DCI Bridges to provide load-balancing between DCIs
Search WWH ::




Custom Search