Difference between revisions of "Resource Management"

From Gcube Wiki
Jump to: navigation, search
(Resource List)
(Resource List)
Line 53: Line 53:
  
 
# Retrieve Profile      : shows the selected resource(s) profile(s) in the [[Profiles]] panel;
 
# Retrieve Profile      : shows the selected resource(s) profile(s) in the [[Profiles]] panel;
 +
 
# Find Related Resources : shows the selected resource(s) related information in the [[Related Resource]] panel;
 
# Find Related Resources : shows the selected resource(s) related information in the [[Related Resource]] panel;
 +
 
# Add To Scope          : shows the form which lets users to add selected resource(s) to an accessible scope;
 
# Add To Scope          : shows the form which lets users to add selected resource(s) to an accessible scope;
 
#: The form shows the selected resources and a list of available destination scope(s)(if any).  
 
#: The form shows the selected resources and a list of available destination scope(s)(if any).  
Line 61: Line 63:
 
# Remove From Scope      : removes the selected resource(s) from the current scope;  
 
# Remove From Scope      : removes the selected resource(s) from the current scope;  
 
#: This operation removes the selected resource(s) from the selected scope(s) by modifying his profile. If a resource isn't published in any other scope, this operations causes the complete deletion of that resource from the Information System. Please note that it's not possible to remove a resource from an Infrastructure level scope.
 
#: This operation removes the selected resource(s) from the selected scope(s) by modifying his profile. If a resource isn't published in any other scope, this operations causes the complete deletion of that resource from the Information System. Please note that it's not possible to remove a resource from an Infrastructure level scope.
 +
 
# Edit                  : shows the form which lets users to edit details of a specified resource;
 
# Edit                  : shows the form which lets users to edit details of a specified resource;
 
#: The shown form depends on the selected resource's category. A check is performed during the insertion of specified fields to prevent an incorrect editing. In the example below the field "body" of a Generic Resource doesn't contain a correct XML text, so the form higlights it specifing that the constrain is not satisfied.
 
#: The shown form depends on the selected resource's category. A check is performed during the insertion of specified fields to prevent an incorrect editing. In the example below the field "body" of a Generic Resource doesn't contain a correct XML text, so the form higlights it specifing that the constrain is not satisfied.
Line 69: Line 72:
 
#: [[Image:ResourceManagement_CreateResourcePopup.png]]
 
#: [[Image:ResourceManagement_CreateResourcePopup.png]]
  
*Delete                : deletes the selected resource(s) from the Information System;
+
# Delete                : deletes the selected resource(s) from the Information System;
*Ban                    : shows the form which lets users to create custom filters to ban resources;
+
#: This operation causes the deletion of the selected resource(s) from the current scope and recursively from all of it's underlying scopes. If the resource(s) are published in other scopes of an upper or same level of the current scope this operation is implemented as a set of calls to Remove From Scope operation to prevent the cancellation from those scopes.
*Shut Down              : shows the form which lets users to shut down the specified gCube Hosting Node(s);
+
*Deploy                : shows the form which lets users to deploy specified Software(s) to one or more gCube Hosting Nodes;
+
  
A clarification about "Remove From Scope" and "Delete" operations' behaviour is needed:
+
# Ban                    : shows the form which lets users to create custom filters to ban resources;
 +
#: The form is divided in 3 main sections:
 +
#: The "Select filter level" part shows the selected resource's profile structure to let people specify which tag(s) must be evaluated by the filter.
 +
#: The center part lets users define the kind of condition to be evaluated by the filter. A newer condition is defined by pressing the "Add filter" button. The "Remove filter" button allows user to delete the selected filter from "Filter summary" grid.
 +
#: The "Filter summary" part shows the condition(s) already defined by the user, which will form the ban filter.
 +
#: The filter is actually submitted to the system in the current scope after pressing the "Submit Filter" button.
 +
#: [[Image:ResourceManagement_BanFilter_Popup.png]]
  
*Remove From Scope
+
*Shut Down              : shows the form which lets users to shut down the specified gCube Hosting Node(s);
+
*Deploy                : shows the form which lets users to deploy specified Software(s) to one or more gCube Hosting Nodes;
 
+
*Delete
+
This operation causes the deletion of the selected resource(s) from the current scope and recursively from all of it's underlying scopes. If the resource(s) are published in other scopes of an upper or same level of the current scope this operation is implemented as a set of calls to Remove From Scope operation to prevent the cancellation from those scopes.
+
  
 
== Profiles ==
 
== Profiles ==

Revision as of 18:24, 19 January 2010

This application lets administrator users to manage resources providing the basic functionalities to access and modify their data information. The interface has 5 main sections:

Dimensions of the former 4 panels are customizable by drag-and-dropping their borders. It's also possible to collapse them by clicking their upper right button;

ResourceManagement General.png

Resource Navigation

This section allows browsing of resources, accessing main resources categories and sub categories. Sub categories are retrieved dynamically using these resource properties:

Resources

|----Collection
|     |----User / System
|
|----gCube Hosting Node
|     |----Site
|
|----Generic Resource
|     |----Secondary Type
| 
|----Metadata Collection
|     |----Schema Name
|
|----Software
|     |----Service Class
|
|----Running Instance
      |----Service Class

WSResources

|----Service Class
      |----Service Name

A click on a resource category forces the portlet to show the list of available resources of that category for the current scope in the Resource List panel.


Resource List

This section provides a list of all accessible resources of the selected category/subcategory (see Resource Navigation) in the current scope. Displayed columns are different for every category. It is also possible to hide/show columns by enabling/disabling them from the menu available in the column headers. Ordering options are available for every column in the same menu. ResourceManagement ColumnMenu.png

Right-clicking on selected resource(s) users can access to a contextual menu which provides different operations depending on the selected category. Available operations are :

  1. Retrieve Profile  : shows the selected resource(s) profile(s) in the Profiles panel;
  1. Find Related Resources : shows the selected resource(s) related information in the Related Resource panel;
  1. Add To Scope  : shows the form which lets users to add selected resource(s) to an accessible scope;
    The form shows the selected resources and a list of available destination scope(s)(if any).
    The operation is performed by pressing the "Add to selected scope" button.
    ResourceManagement AddToScopePopup.png
  1. Remove From Scope  : removes the selected resource(s) from the current scope;
    This operation removes the selected resource(s) from the selected scope(s) by modifying his profile. If a resource isn't published in any other scope, this operations causes the complete deletion of that resource from the Information System. Please note that it's not possible to remove a resource from an Infrastructure level scope.
  1. Edit  : shows the form which lets users to edit details of a specified resource;
    The shown form depends on the selected resource's category. A check is performed during the insertion of specified fields to prevent an incorrect editing. In the example below the field "body" of a Generic Resource doesn't contain a correct XML text, so the form higlights it specifing that the constrain is not satisfied.
    ResourceManagement EditResource Popup.png
  1. New  : shows the form which lets users to create a new resource of the selected category;
    The shown form depends on the selected resource's category. A check is performed during the insertion of specified fields to prevent an incorrect editing. In the example below is shown the form to register a new Software and empty mandatory fields are highlightened.The software archive of Software to be registered can be specified either by inserting a local path in the user's computer or by inserting its url.
    ResourceManagement CreateResourcePopup.png
  1. Delete  : deletes the selected resource(s) from the Information System;
    This operation causes the deletion of the selected resource(s) from the current scope and recursively from all of it's underlying scopes. If the resource(s) are published in other scopes of an upper or same level of the current scope this operation is implemented as a set of calls to Remove From Scope operation to prevent the cancellation from those scopes.
  1. Ban  : shows the form which lets users to create custom filters to ban resources;
    The form is divided in 3 main sections:
    The "Select filter level" part shows the selected resource's profile structure to let people specify which tag(s) must be evaluated by the filter.
    The center part lets users define the kind of condition to be evaluated by the filter. A newer condition is defined by pressing the "Add filter" button. The "Remove filter" button allows user to delete the selected filter from "Filter summary" grid.
    The "Filter summary" part shows the condition(s) already defined by the user, which will form the ban filter.
    The filter is actually submitted to the system in the current scope after pressing the "Submit Filter" button.
    ResourceManagement BanFilter Popup.png
  • Shut Down  : shows the form which lets users to shut down the specified gCube Hosting Node(s);
  • Deploy  : shows the form which lets users to deploy specified Software(s) to one or more gCube Hosting Nodes;

Profiles

This Panel shows a set of profiles as requested by the user. Profiles are displayed in a tree, and it's possible to view them as xml formatted text by clicking the "View XML" button.


Related Resources

This panel shows related information about one or more specified resources. Depending on the category of the resource, the kind of information displayed is different :

  • Collection  : list of information about related Metadata Collections;
  • gCube Hosting Node  : list of information about all Running Instances running in the specified node;
  • Generic Resource  : not available;
  • Metadata Collection  : list of information about related indexes;
  • Software  : list of information about deployed instances of the specified Software;
  • Running Instance  : information about the selected Running Instance's gCube Hosting Node and Software;
  • WSResource  : same information of Running Instance, based upon the one which published the selected WSResource;

Main Menu

Main Menu provides a set of menus to perform these operations:

  • Find  : shows a profile by providing its resource's unique ID;
  • Refresh  : forces refresh of a part/ all the portlet interface information;
  • Create  : shows a form to create a specific kind of resource;


Configuration

The portlet is intended to operate in 2 different modes:

  • In portal mode

In this state the portlet offers the entire set of possible operations on resources but it allow access to only the scope related to user's portal session.

  • Stand alone mode

In this state the portlet offers the possibility to access all available scopes, but it's not possible to make any changes to resources.


The configuration is done by editing the config file config/config.properties and setting the values "true|false" to the mode labels. Please note that this file is loaded by the application at start-up time, so you need to restart it after editing the file, to let the modifications affect the portlet's behaviour.

Scopes

To let the portlet manage new INFRASTRUCTURES and VO scopes , you should edit the xml/scopedata.xml file by putting new scopes description as described in the [[Monitoring_System#Configuring_Infrastructure_Viewer | Configuring Infrastructure Viewer] section of the Monitor System documentation.