VRE Definition And Creation

1,045 views

Published on

Slides presented at the D4Science VRE Management Training Event which took place on 30/04/2009 in Rome, Italy.

More information: http://www.d4science.eu/node/213

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,045
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

VRE Definition And Creation

  1. 1. D4Science VRE Management Training Event 30th April 2009 Rome (Italy) D4Science VRE Definition and Creation www.d4science.eu
  2. 2. Outline 2 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  3. 3. Infrastructure Resources 1 A gCube-based infrastructure manages: 3 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  4. 4. Infrastructure Resources: gHN 1 The gCube Hosting Node : Is the runtime container of gCube services Provides access to local hardware resources, Storage systems, instruments, CPU cycles Grants lifetime management Mediates service2service interactions route requests to target service enforce security and scope policies Detailed information on how to install a gHN is available on the wiki site accessible here. 4 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  5. 5. Infrastructure Resources: gCube Service 1 A gCube Service is a software packaged as Service Archive (SA). These SAs: Follow a predefined structure Group inter-connected packages Declare dependencies to other packages Detailed information on the Service Archive Specification is available on the wiki site accessible here. All SAs are stored in a common repository, the gCube Software Repository. The storage of any gCube SA in this repository is subject to a certification process. A gCube infrastructure only runs certified service. 5 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  6. 6. Infrastructure Resources: gCube VO Services 1 • gCube VO Services run in a VO scope and are exploited by all VREs of that VO Can they be Can we have Can they be shared multiple restarted across instances in the without manual VOs? same VO? staging? Content Management Storage Management, NO NO YES Collection Management Metadata Broker YES YES YES Metadata Manager NO YES YES XML Indexer NO YES YES Indexes (ForwardIndexes, FullTextIndexes, NO YES NO (1.1.7) GeoIndexes) YES (1.2.0) Personalisation (ProfileAdministration, YES YES YES UserProfileAccess): 6 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  7. 7. Infrastructure Resources: gCube VRE Services 1 • gCube VRE Services run in a VRE scope and are exploited by that VRE only (1.1.7). • gCube VRE Services (1.3.0) will remove this limitation as reported in the following table Can we share a Can they be RI across restarted VREs? without manual staging? Search Master NO YES Search Operators YES YES Google Service YES YES DIR YES YES Annotation YES YES Thumbnailer YES YES 7 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  8. 8. Virtual Organization (VO) 2 A Virtual Organization (VO) models sets of users and resources belonging to a e-Infrastructure. VO It defines : What is shared Who is allowed to share The conditions under which sharing occurs VOs may have a limited lifetime may span multiple actual organizations 8 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  9. 9. Virtual Research Environment (VRE) 2 A Virtual Research Environment (VRE) provides a framework of applications, services and data sources dynamically identified to support the processes of research/collaboration/cooperation. VRE 1 The purpose of a VRE is to help selected VO members to carry out cooperative activities like data analysis and processing, and to produce new knowledge using specialized tools. VRE 2 VO 9 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  10. 10. VRE Definition 3 The VRE Definition is the operation performed by a VRE Designer to request the creation of a new VRE • It does not allocate any resource to the new VRE • It does not compromise the other VREs • It does not produce any tangible effect until approval 10 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  11. 11. VRE Definition Steps 3 1. VRE Information Definition (Name, Description, Lifetime) 2. VRE Content Definition a. Selection of the collections b. Selection of the descriptive metadata formats 3. VRE Functionality Definition a. Selection of access functions: textual search, geographic search, quick search, google search, search by query expression b. Selection of content functions: annotation, report template definition, report definition, course management (1.2.0), thumbnail, metadata editing (1.2.0) 4. VRE Verification 11 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  12. 12. VRE Definition Steps (1) 3 1. VRE Information Definition (Name, Description, Lifetime) 12 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  13. 13. VRE Definition Steps (2a) 3 2. VRE Content Definition a. Selection of the collections 13 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  14. 14. VRE Definition Steps (2b) 3 2. VRE Content Definition b. Selection of the descriptive metadata formats 14 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  15. 15. VRE Definition Steps (3a) 3 3. VRE Functionality Definition a. Selection of access functions 15 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  16. 16. VRE Definition Steps (3b) 3 3. VRE Functionality Definition b. Selection of content functions 16 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  17. 17. VRE Design Steps (4) 3 4. VRE Verification 17 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  18. 18. VRE Approval 4 The VRE Approval is the operation performed by a VRE Manager to create a new VRE • It must allocate at least 2 gHNs to the new VRE • It can temporarily compromise the other VREs • It produces the environment • It is not the last step 18 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  19. 19. VRE Approval Steps 4 1. VRE Validation 2. gHNs Selection 2 gHNs at least VRE Manager service will be deployed on Either on the same site where the VRE Manager of the VO is running Or on the first selected node VRE services (identified through the selected functionality) will be deployed on the remaining selected gHNs 3. VRE Creation 19 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  20. 20. VRE Approval Steps (1) 4 1. VRE Validation 20 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  21. 21. VRE Approval Steps (2) 4 2. gHNs Selection 21 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  22. 22. VRE Approval Steps 4 3. VRE Creation 22 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  23. 23. VRE Deployment 5 The VRE Deployment is the operation activated by the VRE Manager and operated by the system to deploy the VRE Manager and VRE services on the selected gHNs. A Deployment Report is generated to report the result of the deployment. Detailed information on how to analyze and interpret the information reported in the Deployment Report is available on the wiki site accessible here. 23 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  24. 24. VRE Management 6 The VRE Management is the last mandatory activity. It allows to define the: 1. VRE layout 2. VRE Information Space 24 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  25. 25. VRE Management (1) 6 1. VRE layout The VRE layout defines how the portlets are displayed by the portal. Each portlet gives access to a functionality selected by the VRE Designer. The VRE layout is persisted as generic resource in the Information System and can be edited using the ‘Layout Editor’ portlet Available only for users either with ‘VRE-Manager’ or ‘VO-Admin’ role 25 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  26. 26. Layout Editor Portlet 6 26 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  27. 27. VRE Management (2) 6 2. VRE Information Space Describe the available collections, their hierarchy, and their descriptive information (description, references, etc.) It is used by the portal to group collections and retrieve extra information for each available collection The Information Space Editor portlet is available for editing this resource It is available only to users either with ‘VRE-Manager’ or ‘VO- Admin’ role 27 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  28. 28. Information Space Editor Portlet 6 28 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  29. 29. Information Space Editor Portlet 6 The first column shows all the available collections for this VRE The collections that are highlighted with blue color are the ones that already exist on this VRE The second column shows the hierarchical structure of the collections. New collections can be added to groups Existing collections can be removed Existing collections can be moved to different groups (drag and drop to move collections to other groups) The third column shows details for the selected collection These information are editable 29 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  30. 30. VRE Personalization 7 The VRE personalization can be done manipulating the VRE Generic Resources: MetadataSchemaInfo Generic Resource Presentation XSLTs Generic Resources Metadata XSLTs Generic Resources Used for functional and presentation reasons these generic resources are inherited by the VO Generic resources can be registered and updated using the ‘GenericResource’ portlet that is available only to users either with ‘VRE-Manager’ or ‘VO-Admin’ role Detailed information on the VRE Generic Resources is available on the wiki site accessible here. 30 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  31. 31. MetadataSchemaInfo Generic Resource 7 MetadataSchemaInfo is the generic resource that defines for each available metadata schema: the searchable fields that portal users can search in, the fields that can be used to sort the result obtained executing a query The fields declared as “searchable” should be part of the corresponding metadata XML schema Detailed information on the MetadataSchemaInfo is available on the wiki site accessible here. 31 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  32. 32. Format of MetadataSchemaInfo 7 Format <schemaName> <option> <option-name>displayed name in search fields at portal</option-name> <option-value>actual xml-element name in metadata</option-value> <option-type>fielded</option-type> <option-sort>XPath expression to be used for sort</option-sort> </option> ... </schemaName> If a searchable field is not needed to be used for sorting the <option-sort> element must not have a value 32 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  33. 33. Presentation XSLTs Generic Resources 7 The portal uses XSLTs which are applied per different schema when either a combined, simple, or browse search is performed In order for the portal to work properly, a ‘default’ xslt for each available metadata schema is required Except the ‘default’ xslts, other xslts can be added to personalize the environment Users can select which xslt they want to use per schema by using the UserProfile portlet 33 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  34. 34. Presentation XSLTs Generic Resources 7 Each presentation xslt should follow a name pattern so that it will be correctly parsed by the portal Name pattern: PresentationXSLT_SchemaName_XSLTName Where SchemaName is the name of the metadata schema for which this xslt will be applied and XSLTName is a name of your choice except the ‘default’ that cannot be used The body of these resources should be the desired XSLT These XSLTs are applied to the result of a search producing the HTML representation of the results. Detailed information on the PresentationXSLT is available on the wiki site accessible here. 34 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  35. 35. Presentation XSLT - HOW to create it 7 A presentation XSLT transforms result metadata objects to their corresponding HTML representations, which are then rendered by the results portlet. Normally, such a XSLT produces a HTML table with two columns. The first column contains the names of the fields which must be included in the rendered results The second column contains the values of these fields The XSLT should check if each field is present in the results before adding a row to the output table. 35 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  36. 36. Presentation XSLT - Example 7 <xsl:stylesheet version=quot;1.0quot;> <xsl:output encoding=quot;UTF-8quot; method=quot;htmlquot; omit-xml-declaration=quot;yesquot;/> <xsl:template match=quot;/”> <table> <xsl:if test=quot;//*[local-name()='title']”> <tr> Check if the “title” <td align=quot;rightquot; class=quot;window-title-inactivequot; width=quot;120quot;> field is present and <b>Title:</b> add a row in the </td> output table. Put <td> the field name in <xsl:value-of select=quot;//*[local-name()='title']quot;/> the first cell and </td> the field value in </tr> the second cell. </xsl:if> ….. Do the same for ….. every other field, ….. adding more rows </table> </xsl:template> </xsl:stylesheet> 36 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  37. 37. Metadata XSLTs Generic Resources 7 For presenting the metadata of a result object the portal uses XSLTs which are applied per different schema. In order for the portal to work properly, a ‘default’ xslt for each available metadata schema is required Except the ‘default’ xslts, other xslts can be added to personalize the environment Users can select which xslt they want to use per schema by using the UserProfile portlet 37 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  38. 38. Metadata XSLTs Generic Resources 7 Each presentation xslt follows a name pattern so that it will be correctly parsed by the portal Name pattern: MetadataXSLT_SchemaName_XSLTName Where SchemaName is the name of the metadata schema for which this xslt will be applied and XSLTName is a name of your choice except the ‘default’ that should always be used The body of these resources contains the desired XSLT These XSLTs are applied to the metadata of a result object producing the HTML representation of the metadata Detailed information on the MetadataXSLT is available on the wiki site accessible here. 38 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  39. 39. Metadata XSLT - HOW to create it 7 A metadataXSLT transforms the metadata of a result object to their corresponding HTML representations, which are then rendered by the metadata portlet. Normally, such a XSLT produces a HTML table which have as a header the name of each metadata field and as rows the values of the corresponding field The XSLT should check if each field is present in the results before adding a row to the output table 39 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  40. 40. Metadata XSLT - Example 7 <xsl:stylesheet version=quot;2.0quot;> <xsl:output encoding=quot;UTF-8quot; indent=quot;yesquot; method=quot;htmlquot; version=quot;1.0quot;/> <xsl:template match=quot;/”> <table border=quot;1quot; style=quot;border-collapse: collapse;quot; width=quot;60%quot;> <xsl:if test=quot;//*[local-name()='publisher']quot;> <th align=quot;leftquot; class=quot;diligent-headerquot;>Publisher</th> Check if the <xsl:for-each select=quot;//*[local-name()='publisher']”> “publisher” field is <tr> present and add a <td> header in the <xsl:value-of select=quot;self::node()quot;/> output table. For </td> all “publisher” </tr> values add them </xsl:for-each> as rows </xsl:if> ….. Do the same for ….. every other field, </table> adding more rows </xsl:template> </xsl:stylesheet> 40 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009
  41. 41. Support for personalization 7 A new portlet will be available soon (1.2.0). This new portlet will provide an easy and graphical way for creating all required generic resources. Using this portlet it won’t be needed to learn the syntax of XSLT 41 D4Science VRE Management Training www.d4science.eu Roma (Italy), 30th April 2009

×