Difference between revisions of "Resource Management Installation"
Manuele.simi (Talk | contribs) (→Installation) |
Lucio.lelii (Talk | contribs) (→Requirements) |
||
Line 293: | Line 293: | ||
==== Requirements ==== | ==== Requirements ==== | ||
− | The VREDefinitionPortlet ( | + | The VREDefinitionPortlet (the VREModeler's GUI) allows (in one of its steps) the VRECreator to select a set of functionalities. A functionality is a set of services and portlets that allow the VREUser to perform specifics operations. These set of functionalities should be defined in a Generic Resource published on the IS. |
The Generic Resource must be defined as follow: | The Generic Resource must be defined as follow: | ||
Revision as of 10:38, 2 October 2009
gHNManager
Installation
The gHNManager is a Local Service shipped and installed within the gHN distribution.
gHN Configuration
No specific configuration is needed, but the usual gHN's one
Instance Configuration
The service instance does not require any specific configuration. As Local Service, it automatically joins all the gHN scopes.
Verify the Installation
Once the gHN is started, the $GLOBUS_LOCATION/nohup.out file has to report (among the others) the following portType:
gHN started at: http://host:port/wsrf/services/ with the following services: GCUBE SERVICES: ... [3]: http://host:port/wsrf/services/gcube/common/vremanagement/GHNManager ...
Looking at the $GLOBUS_LOCATION/logs/container.fullog, the following messages related to the gHNManager initialisation have to be observed:
2009-07-06 16:08:04,329 INFO contexts.ServiceContext [GHNManager-Initialiser,info:78] [0.0s] GHNManager: Added scope(s) [/testing] 2009-07-06 16:08:04,329 INFO contexts.ServiceContext [GHNManager-Initialiser,info:78] [0.0010s] GHNManager: INITIALISING RUNNING INSTANCE 2009-07-06 16:08:04,479 TRACE contexts.ServiceContext [GHNManager-Initialiser,trace:82] [0.151s] GHNManager: loading RI profile 2009-07-06 16:08:04,490 INFO contexts.ServiceContext [GHNManager-Initialiser,info:78] [0.162s] GHNManager: Added scope(s) [/testing, /testing/vo1] 2009-07-06 16:08:04,495 INFO contexts.ServiceContext [GHNManager-Initialiser,info:78] [0.167s] GHNManager: managing security with a GCUBESimpleServiceSecurityManager 2009-07-06 16:08:04,497 INFO contexts.ServiceContext [GHNManager-Initialiser,info:78] [0.169s] GHNManager: managing remote persistence with a GCUBERINoPersistenceManager 2009-07-06 16:08:04,500 INFO contexts.GHNContext [GHNManager-Initialiser,info:78] [0.997s] GHNContext: REGISTERED RI OF (VREMANAGEMENT,GHNMANAGER) 2009-07-06 16:08:04,538 INFO contexts.ServiceContext [GHNManager-Initialiser,info:78] [0.21s] GHNManager: moved to status INITIALISED 2009-07-06 16:08:04,542 DEBUG contexts.ServiceContext [GHNConsumer$<anon>,debug:66] [0.0s] GHNManager: UPDATE event received 2009-07-06 16:08:04,744 INFO contexts.ServiceContext [GHNManager-Subscriber,info:78] [0.0s] GHNManager: registering for GHN shutdown events 2009-07-06 16:08:04,745 INFO contexts.ServiceContext [GHNManager-Subscriber,info:78] [0.0010s] GHNManager: registering for GHN scope events as a local service 2009-07-06 16:08:04,790 TRACE impl.GHNManager [PortTypeConsumer,trace:82] [0.0s] GHNManager: INITIALISING PORTTYPE GHNMANAGER
Afterward, per each gHN scope, the following messages related to the gHN profile publication have to be reported in the same log file:
2009-07-06 16:08:04,542 DEBUG contexts.ServiceContext [GHNConsumer$<anon>,debug:66] [0.0s] GHNManager: UPDATE event received 2009-07-06 16:08:04,544 DEBUG contexts.ServiceContext [GHNConsumer$<anon>,debug:66] [0.0020s] GHNManager: Publishing GHN profile in scope /testing 2009-07-06 16:08:04,551 TRACE impl.GCUBEProfileManager [GHNConsumer$<anon>,trace:82] GCUBEProfileManager: Trying to update resource with ID=0722bbe0-50f5-11de-aea3-d209846ff30b in scope /testing 2009-07-06 16:08:04,586 TRACE scope.GCUBEScopeManagerImpl [GHNConsumer$<anon>,trace:82] GCUBEScopeManagerImpl: Setting scope /testing in Thread[GHNConsumer$<anon>,5,main] 2009-07-06 16:08:04,586 INFO tasks.ISRegistryServiceUpdaterHandler [GHNConsumer$<anon>,info:78] ISRegistryServiceUpdaterHandler: looking for instances of ISRegistry ServiceHandler 2009-07-06 16:08:04,587 TRACE tasks.ISRegistryServiceUpdaterHandler [GHNConsumer$<anon>,trace:82] ISRegistryServiceUpdaterHandler: Refreshing Registry instances 2009-07-06 16:08:04,588 TRACE tasks.ISRegistryLookup [GHNConsumer$<anon>,trace:82] ISRegistryLookup: Querying the IS for Registry instances 2009-07-06 16:08:05,102 TRACE tasks.ISRegistryServiceUpdaterHandler [GHNConsumer$<anon>,trace:82] ISRegistryServiceUpdaterHandler: Connecting to the IS-Registry instance located at http://grid10.4dsoft.hu:8080/wsrf/services/gcube/informationsystem/registry/RegistryFactory... 2009-07-06 16:08:05,244 INFO contexts.GCUBERemotePortTypeContext$1 [GHNConsumer$<anon>,info:78] : Preparing call to service InformationSystem,IS-Registry in scope /testing 2009-07-06 16:08:05,592 TRACE impl.GCUBEProfileManager [GHNConsumer$<anon>,trace:82] GCUBEProfileManager: Resource with ID=0722bbe0-50f5-11de-aea3-d209846ff30b successfully updated
Deployer
Installation
The Deployer is a Local Service shipped and installed within the gHN distribution.
gHN Configuration
No specific configuration is needed, but the usual gHN's one.
Instance Configuration
The service instance does not require any specific configuration. As Local Service, it automatically joins all the gHN scopes.
Verify the Installation
Once the gHN is started, the $GLOBUS_LOCATION/nohup.out file has to report (among the others) the following portType:
gHN started at: http://host:port/wsrf/services/ with the following services: GCUBE SERVICES: ... [3]: http://host:port/wsrf/services/gcube/common/vremanagement/Deployer ...
Looking at the $GLOBUS_LOCATION/logs/container.fullog, the following messages related to the Deployer initialisation have to be observed:
2009-07-06 16:08:05,538 INFO contexts.ServiceContext [Deployer-Initialiser,info:78] [0.0s] Deployer: Added scope(s) [/testing] 2009-07-06 16:08:05,538 INFO contexts.ServiceContext [Deployer-Initialiser,info:78] [0.0s] Deployer: INITIALISING RUNNING INSTANCE 2009-07-06 16:08:05,539 TRACE contexts.ServiceContext [Deployer-Initialiser,trace:82] [0.0010s] Deployer: loading RI profile 2009-07-06 16:08:05,542 INFO contexts.ServiceContext [Deployer-Initialiser,info:78] [0.0040s] Deployer: Added scope(s) [/testing, /testing/vo1] 2009-07-06 16:08:05,543 INFO contexts.ServiceContext [Deployer-Initialiser,info:78] [0.0050s] Deployer: managing security with a GCUBESimpleServiceSecurityManager 2009-07-06 16:08:05,543 INFO contexts.ServiceContext [Deployer-Initialiser,info:78] [0.0050s] Deployer: managing remote persistence with a GCUBERINoPersistenceManager 2009-07-06 16:08:05,544 INFO contexts.GHNContext [Deployer-Initialiser,info:78] [0.0s] GHNContext: REGISTERED RI OF (VREMANAGEMENT,DEPLOYER) 2009-07-06 16:08:05,544 INFO impl.ServiceContext [VREModeler-Subscriber,info:78] [0.0s] VREModeler: registering for GHN shutdown events 2009-07-06 16:08:05,545 INFO impl.ServiceContext [VREModeler-Subscriber,info:78] [0.0s] VREModeler: registering for GHN scope removal events 2009-07-06 16:08:05,545 INFO contexts.ServiceContext [Deployer-Initialiser,info:78] [0.0070s] Deployer: moved to status INITIALISED 2009-07-06 16:08:05,550 INFO contexts.ServiceContext [Deployer-Subscriber,info:78] [0.0s] Deployer: registering for GHN shutdown events 2009-07-06 16:08:05,550 INFO contexts.ServiceContext [Deployer-Subscriber,info:78] [0.0010s] Deployer: registering for GHN scope events as a local service 2009-07-06 16:08:05,551 TRACE impl.Deployer [PortTypeConsumer,trace:82] [0.0s] Deployer: INITIALISING PORTTYPE DEPLOYER
VREManager
Installation
The VREManager is typically installed in two ways:
- statically, for infrastructure and VO scopes
- here the service is deployed on a gHN as any other gCube Service by typing:
gcore-deploy-service <path>/org.gcube.vremanagement.vremanager.gar
- The command above assumes that the $GLOBUS_LOCATION/bin folder is in your PATH
- dynamically, for VRE scopes
- in this case, it is the VREModeler service that takes care of the installation and its settings. Typically, the VREManager is installed as first step of the VRE creation process.
gHN Configuration
No specific configuration is needed, but the usual gHN's one.
Instance Configuration
The VREManager is a scope-specific service, meaning that it must join one and only one scope. Therefore, it must be configured properly to behave in the assigned scope. In the case of a dynamically deployed instance, the appropriate configuration is automatically done by the Deployer service.
In the case of a statically deployed instance, its JNDI file ($GLOBUS_LOCATION/etc/org.gcube.vremanagement.vremanager/jndi-config.xml) must be configured to join only one scope. In the following example, the instance (startScopes environment variable) is configured to join the scope named /testing/vo1:
<jndiConfig xmlns="http://wsrf.globus.org/jndi/config"> <service name="gcube/vremanagement/VREManager/service"> <environment name="configDir" value="etc/org.gcube.vremanagement.vremanager" type="java.lang.String" override="false" /> <environment name="securityManagerClass" value="org.gcube.common.core.security.GCUBESimpleServiceSecurityManager" type="java.lang.String" override="false" /> <environment name="startScopes" value="/testing/vo1" type="java.lang.String" override="false" /> </service> <service name="gcube/vremanagement/VREManager"> <environment name="name" value="VREManager" type="java.lang.String" override="false" /> <environment name="RPDName" value="VREManagerResourceProperties" type="java.lang.String" override="false"/> <resource name="home" type="org.gcube.vremanagement.vremanager.impl.state.VREManagerHome"> <resourceParams> <parameter> <name>factory</name> <value>org.globus.wsrf.jndi.BeanFactory</value> </parameter> <parameter> <name>resourceClass</name> <value>org.gcube.vremanagement.vremanager.impl.state.VREResource</value> </parameter> </resourceParams> </resource> </service> </jndiConfig>
[TBC]
Verify the Installation
Once the gHN is started, the $GLOBUS_LOCATION/nohup.out file has to report (among the others) the following portType:
gHN started at: http://host:port/wsrf/services/ with the following services: GCUBE SERVICES: ... [5]: http://host:port/wsrf/services/gcube/vremanagement/VREManager ...
Looking at the $GLOBUS_LOCATION/logs/container.fullog, the following messages related to the VREManager initialisation have to be observed:
2009-07-14 22:17:19,986 INFO resultsetservice.ServiceContext [ResultSetService-Initialiser,info:78] [1.141s] ResultSetService: moved to status INITIALISED 2009-07-14 22:17:20,421 INFO contexts.ServiceContext [VREManager-Initialiser,info:78] [0.0s] VREManager: Added scope(s) [/d4science.research-infrastructures.eu] 2009-07-14 22:17:20,422 INFO contexts.ServiceContext [VREManager-Initialiser,info:78] [0.0010s] VREManager: INITIALISING RUNNING INSTANCE 2009-07-14 22:17:20,424 INFO contexts.ServiceContext [VREManager-Initialiser,info:78] [0.0030s] VREManager: starting in scopes [/d4science.research-infrastructures.eu] 2009-07-14 22:17:20,424 INFO contexts.ServiceContext [VREManager-Initialiser,info:78] [0.0030s] VREManager: Added scope(s) [/d4science.research-infrastructures.eu] 2009-07-14 22:17:20,425 INFO contexts.ServiceContext [VREManager-Initialiser,info:78] [0.0040s] VREManager: managing security with a GCUBESimpleServiceSecurityManager 2009-07-14 22:17:20,425 INFO contexts.ServiceContext [VREManager-Initialiser,info:78] [0.0040s] VREManager: managing remote persistence with a GCUBERINoPersistenceManager 2009-07-14 22:17:20,426 INFO contexts.GHNContext [VREManager-Initialiser,info:78] [0.0s] GHNContext: REGISTERED RI OF (VREMANAGEMENT,VREMANAGER) 2009-07-14 22:17:21,309 TRACE impl.VREManager [PortTypeConsumer,trace:82] [0.0s] VREManager: INITIALISING PORTTYPE VREMANAGER 2009-07-14 22:17:21,322 TRACE state.VREManagerHome [HomeConsumer,trace:82] [0.0s] VREManager: INITIALISING VREMANAGERHOME 2009-07-14 22:17:21,322 TRACE persistence.GCUBENoPersistenceDelegate [HomeConsumer,trace:82] GCUBENoPersistenceDelegate: initialising GCUBENoPersistenceDelegate 2009-07-14 22:17:21,323 INFO state.VREManagerHome [HomeConsumer,info:78] [0.0010s] VREManager: managing resources in TRANSIENT mode 2009-07-14 22:17:21,326 INFO state.VREManagerHome [HomeConsumer,info:78] [0.0040s] VREManager: activated sweeper to run every 60 seconds
Software Repository
Installation
The Software Repository can be deployed on a gHN as any other gCube Service by typing:
gcore-deploy-service <path>/org.gcube.vremanagement.softwarerepository.gar
The command above assumes that the $GLOBUS_LOCATION/bin folder is in your PATH.
In addition, it requires that the following software are available in the $GLOBUS_LOCATION/lib folder:
- hsqldb 1.8.0 (or higher)
- commons-compress 1.00
- mavencustom 1.00.01
- jetty 7.0 (or higher)
- maven-2.0.8 (or higher)
All of them can be downloaded from Software Distribution Site, while the installation instructions are available in their websites.
gHN Configuration
[TBP]
Instance Configuration
[TBP]
Verify the Installation
...
2009-07-14 22:17:22,457 INFO impl.ServiceContext [SoftwareRepository-Initialiser,info:78] [0.0s] SoftwareRepository: Added scope(s) [/d4science.research-infrastructures.eu] 2009-07-14 22:17:22,458 INFO impl.ServiceContext [SoftwareRepository-Initialiser,info:78] [0.0010s] SoftwareRepository: INITIALISING RUNNING INSTANCE 2009-07-14 22:17:22,460 INFO impl.ServiceContext [SoftwareRepository-Initialiser,info:78] [0.0030s] SoftwareRepository: starting in scopes [/d4science.research-infrastructures.eu] 2009-07-14 22:17:22,460 INFO impl.ServiceContext [SoftwareRepository-Initialiser,info:78] [0.0030s] SoftwareRepository: Added scope(s) [/d4science.research-infrastructures.eu] 2009-07-14 22:17:22,461 INFO impl.ServiceContext [SoftwareRepository-Initialiser,info:78] [0.0040s] SoftwareRepository: managing security with a GCUBEServiceSecurityManagerImpl 2009-07-14 22:17:22,461 INFO impl.ServiceContext [SoftwareRepository-Initialiser,info:78] [0.0040s] SoftwareRepository: managing remote persistence with a GCUBERINoPersistenceManager 2009-07-14 22:17:22,462 INFO contexts.GHNContext [SoftwareRepository-Initialiser,info:78] [0.0s] GHNContext: REGISTERED RI OF (VREMANAGEMENT,SOFTWAREREPOSITORY) 2009-07-14 22:17:22,539 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.082s] SoftwareRepository: banned version: 0.00.00 2009-07-14 22:17:22,540 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.083s] SoftwareRepository: regular expression for dependency version is: \s*(((\(|\[)\s*\d{1,2}.\d{1,2}.\d{1,2}\s*,\s*\d{1,2}.\d{1,2}.\d{1,2}\s*(\)|\]))|(\d{1,2}.\d{1,2}.\d{1,2}))\s* 2009-07-14 22:17:22,637 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.18s] SoftwareRepository: DB filename = /home/gcube1/gCore/etc/org.gcube.vremanagement.softwarerepository/db 2009-07-14 22:17:22,639 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.182s] SoftwareRepository: Queries file = /home/gcube1/gCore/etc/org.gcube.vremanagement.softwarerepository/dbQuery.xml 2009-07-14 22:17:22,639 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.182s] SoftwareRepository: Tmp directory = /home/gcube1/gCore/etc/org.gcube.vremanagement.softwarerepository/tmp 2009-07-14 22:17:22,640 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.183s] SoftwareRepository: Pending directory = /home/gcube1/gCore/etc/org.gcube.vremanagement.softwarerepository/pending 2009-07-14 22:17:22,640 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.183s] SoftwareRepository: Maven directory = /home/gcube1/gCore/etc/org.gcube.vremanagement.softwarerepository/maven 2009-07-14 22:17:22,640 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.183s] SoftwareRepository: Maven settings file path = settings.xml 2009-07-14 22:17:22,641 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.184s] SoftwareRepository: HTTP Server Base path = /home/gcube1/gCore/etc/org.gcube.vremanagement.softwarerepository/jetty/webapps 2009-07-14 22:17:22,642 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.185s] SoftwareRepository: HTTP Server port = 6900 2009-07-14 22:17:22,642 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.185s] SoftwareRepository: HTTP relative Maven directory = maven 2009-07-14 22:17:22,642 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.185s] SoftwareRepository: HTTP relative Report directory = report 2009-07-14 22:17:22,643 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.186s] SoftwareRepository: XSLT directory = /home/gcube1/gCore/etc/org.gcube.vremanagement.softwarerepository/xslt 2009-07-14 22:17:22,646 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.189s] SoftwareRepository: Documentation will be controlled in doc/api on each package 2009-07-14 22:17:22,646 DEBUG impl.ServiceContext [SoftwareRepository-Initialiser,debug:66] [0.189s] SoftwareRepository: On each package the file containing link with the source code should be svnpath.txt ...
[TBP]
VREModeler
Installation
The VREModeler is typically installed as any other gCube Service by typing:
gcore-deploy-service <path>/org.gcube.vremanagement.vremodeler.gar
The command above assumes that the $GLOBUS_LOCATION/bin folder is in your PATH
In addition, the service requires that the following software are available in the $GLOBUS_LOCATION/lib folder:
- hsqldb 1.8.0 (or higher)
gHN Configuration
[TBP]
Instance Configuration
[TBP]
Verify the Installation
[TBP]
Requirements
The VREDefinitionPortlet (the VREModeler's GUI) allows (in one of its steps) the VRECreator to select a set of functionalities. A functionality is a set of services and portlets that allow the VREUser to perform specifics operations. These set of functionalities should be defined in a Generic Resource published on the IS. The Generic Resource must be defined as follow:
<Resource> <ID>df899630-82ae-11de-a6cc-f15c9cf886be</ID> <Type>GenericResource</Type> <Scopes> </Scopes> <Profile> <SecondaryType>VREModelerResource</SecondaryType> <Name>FuctionalitiesResource</Name> <Description> A Generic resource containing the functionalities requested to a VRE at design time </Description> <Body> <MainFunctionalities> <MainFunctionality> <Name>Access Functions</Name> <Description> This class of functions characterises the facilities that can be activated in the Virtual Research Environment to support users in requesting, locating, and accessing the Virtual Research Environment content. </Description> <Functionalities> <Functionality> <Name>Search (Browse, Simple, and Combined)</Name> <Description> By selecting this function VRE users will be provided with facilities supporting the discovery of Information Objects by issuing keyword based queries. This is the simplest modality for discovering Information Objects constituting the VRE Information Space. In addition to the specification of the keywords characterising the Information Objects the user is interested in, this function permits to restrict the Information Space in which to search by specifying the set of Collections against which the query will be evaluated. </Description> <Services> <Service> <ServiceName>FilterXPathOperator</ServiceName> <ServiceClass>Search</ServiceClass> </Service> ... more services </Services> <Portlets> <Portlet>userprofileeditingportlet#UserProfileEditingPortlet</Portlet> <Portlet>layoutcreator#LayoutcreatorPortlet</Portlet> ... more portlets </Portlets> </Functionality> ... more functionalities </Functionalities> </MainFunctionality> ... more main functionalities </MainFunctionalities> </Body> </Profile> </Resource>