Resources and Properties. This Service creates and manage a WS-Resource for each gCube resource that has to be considered part of the e-Infrastructure the IS-Registry is responsible for. Such WS- Resources (ProfileResource) implement the Resource Model described in the Resource Domain (cf. Section 2.1), in fact each of them consists of four parts: • A unique identifier identifying the resource univocally;
Resources and Properties. This Service creates and manages a WS-Resource for each gLite resource that has to be considered part of the e-Infrastructure the IS-Registry is responsible for. Such WS- Resources implement the Resource Model described in the Resource Domain (cf. Section 2.1), in particular they instantiate the gLiteResource part. The following three types of WS-Resources are created and managed: • gLiteService – to represent a gLite Service. It contains a unique ID, a status label and status information; • gLiteCE – to represent a gLite Computing Element (CE). It contains a unique ID and information about the operational status of the resource including the number of running jobs, the number of waiting jobs, the number of total jobs, the estimated response time, the worst response time, the free jobs slot, the xxx xxxx clock time, the max CPU time, the max total jobs, the max running jobs, the assigned job slots and the priority; • gLiteSE – to represent a gLite Storage Element (SE). It contains a unique ID and information about the operational status of the resource including the used storage space, the available storage space and the current IO load;
Resources and Properties. For each Aggregator Source the IS-IC is requested to aggregate an ISICResource is created and managed (for each Aggregator Source registration a new ServiceGroupEntry is created). Such a WS-Resource extends the AggregatorServiceGroupResource and each time the state of the ServiceGroupEntry changes the underlying Aggregator Framework invokes the relative delivery method.
Resources and Properties. The service adopts the xxxxxxxxx pattern. The managed resource represents the operational status of the service by exposing a set of properties, e.g. number of topics currently published, the number of subscriptions managed, the number of pending subscriptions.
Resources and Properties. To be defined in the next version of this design document.
Resources and Properties. The VO-Management Authorization adopts a Factory Pattern to support VOs hierarchies and manages a Resource for each VOs Each VOResource publishes as WS- ResourceProperty the VOName of the corresponding VO. The VOResource instantiation implies, consequently, its initialization, i.e. the creation of basic Roles, Operations, Resources, Resource Types, Sharing Rules and Permissions.
Resources and Properties. The Delegation service is a xxxxxxxxx stateful Web Service bound to a DelegationResource resource. The DelegationResource manages delegated credentials and credential listeners subscribed by co-hosted services. For security reasons, the information managed by the DelegationResource is not persistent and it is never stored on local file system.
Resources and Properties. The Credentials Renewal service adopts a Factory Pattern and manages CredentialsRenewalResource resource. The CredentialsRenewalResource manages credentials renewal tasks.
Resources and Properties. The VRE Modeler Model adopts a Factory Pattern and manages a Resource for each of the VREs it is currently handling a model. Such resource is characterised by the VRE Identifier and the specification criteria that have been specified organised in terms of Descriptive Information, Content Information, Functionality Information, User Information and Architecture Information.
Resources and Properties. THE VRE Manager adopts the Factory pattern. In particular, it creates and manages two types of resources: the VREManagerVREScope and the VREManagerVOScope. The former, i.e. the VREManagerVREScope, is created whenever a new VRE is created and used to keep track of the status of the VRE including the set of resources belonging to it, e.g. the list of the gHNs, the list of the Running Instances, the list of Collections. For such a resource the service exposes the VRE name and its ID. The latter, i.e. the VREManagerVOScope, is created to manage each VO and used to manage it with respect to the purpose of this service, i.e. keep track of the set of VO mandatory services deployed. For such a resource the service exposes the VO name and the relative map, i.e. the IDs of the backbone services (non VRE specific) governing the operation of the VO and the relative VRE, e.g. the Software Repository, the IS-Registry.
