Difference between revisions of "Software Repository"

From Gcube Wiki
Jump to: navigation, search
(→‎Functionality)
Line 19: Line 19:
  
 
The signatures of the actual implemented methods are presented below. These operations allow uploading, deleting, listing, and getting package. As well as other advanced operations that operate over packages dependencies.  
 
The signatures of the actual implemented methods are presented below. These operations allow uploading, deleting, listing, and getting package. As well as other advanced operations that operate over packages dependencies.  
−
 
  
 
:1. '''store'''
 
:1. '''store'''
Line 28: Line 27:
 
This operation stores a software archive into the Software Repository in pending state. Pending status means that software archive is valid, and receive an unique ID that it was not previously used.
 
This operation stores a software archive into the Software Repository in pending state. Pending status means that software archive is valid, and receive an unique ID that it was not previously used.
 
The main issue of this method is the validation. You can find more informations about the controls performed on [[ Software_Archive_Specification | Software Archives Specification]]
 
The main issue of this method is the validation. You can find more informations about the controls performed on [[ Software_Archive_Specification | Software Archives Specification]]
−
 
  
 
''StoreMessage'' type contains Service Class, Service Name and Version of the service, the URL from where the software archive can be downloaded, and the service description. Further contains a String[] with scopes where the Service should be published.
 
''StoreMessage'' type contains Service Class, Service Name and Version of the service, the URL from where the software archive can be downloaded, and the service description. Further contains a String[] with scopes where the Service should be published.
  
 
''Return'' String with the result description NEW (if is the service is not already stored), UPDATE if the service is already present on Software Repsoitory and will be updated.
 
''Return'' String with the result description NEW (if is the service is not already stored), UPDATE if the service is already present on Software Repsoitory and will be updated.
−
 
  
 
:2. '''approve'''
 
:2. '''approve'''
Line 45: Line 42:
  
 
''Return'' It returns OK if operation success, an error message otherwise.
 
''Return'' It returns OK if operation success, an error message otherwise.
−
 
  
 
:3. '''delete'''
 
:3. '''delete'''
Line 67: Line 63:
  
 
''Return'' The method returns the URI from where the requested package can be downloaded.
 
''Return'' The method returns the URI from where the requested package can be downloaded.
−
 
  
 
:5. '''listPending'''
 
:5. '''listPending'''
Line 85: Line 80:
 
</Services>
 
</Services>
 
</pre>
 
</pre>
−
 
−
 
  
 
:6. '''isDeployable'''
 
:6. '''isDeployable'''
Line 111: Line 104:
 
</Dependency>
 
</Dependency>
 
</pre>
 
</pre>
−
 
  
 
:7. '''listScopedPackages'''
 
:7. '''listScopedPackages'''
Line 136: Line 128:
 
</Dependency>
 
</Dependency>
 
</pre>
 
</pre>
−
 
  
 
=== Dependencies ===
 
=== Dependencies ===

Revision as of 11:26, 5 June 2008

Software Repository

Introduction

The Software Repository validates, stores, and manages packages. It checks packages dependencies and giving both access to packages relations and access to the stored packages supports the dynamic packages deployment.

This repository accepts registration requests coming from the Sofware Archive Registration Portlet that is part of the VRE Management

Implentation Overview

This component is responsible for the validation, storage, and maintenance of the Software Archives, each software archive contains all files declared on the Service Profile . It checks packages dependencies and by ensuring access to them, it supports the dynamic packages deployment.

The Software Repository is a WSRF service, implemented as specified by the Singleton Pattern.

The service includes a Validation phase that checks software archives based on service profiles declarations. It control also that service profiles are valid against the service profile schema. Controls performed includes checking that all declared files are in the right place into the service archive structure. After validation phase (if successfull) it store in a pending state all packages declared in service profile. When the Software Archive is approved the Software Repository finally store all packages in the repository for dynamic deployment


Functionality

The signatures of the actual implemented methods are presented below. These operations allow uploading, deleting, listing, and getting package. As well as other advanced operations that operate over packages dependencies.

1. store
store(StoreMessage) -> String

This operation stores a software archive into the Software Repository in pending state. Pending status means that software archive is valid, and receive an unique ID that it was not previously used. The main issue of this method is the validation. You can find more informations about the controls performed on Software Archives Specification

StoreMessage type contains Service Class, Service Name and Version of the service, the URL from where the software archive can be downloaded, and the service description. Further contains a String[] with scopes where the Service should be published.

Return String with the result description NEW (if is the service is not already stored), UPDATE if the service is already present on Software Repsoitory and will be updated.

2. approve
approve (String) -> String

Approve an already stored service archive with the service ID passed as argument if exists.

String Service ID

Return It returns OK if operation success, an error message otherwise.

3. delete
delete (String) -> String

This operation deletes a stored pending software archive from the Software Repository with the service ID passed as argument if exists.

String Service ID

Return It returns OK if operation success, an error message otherwise.

4. get
get(GetMessage) -> String


GetMessage type contains Service Class, Service Name, Service Version, Package Name and Package Version of the requested package

Return The method returns the URI from where the requested package can be downloaded.

5. listPending
listPending( ) -> String

Return This operation returns an XML containing all stored service archives with status pending. The XML structure is as follow: 

<Services>
 <Service>
  <Id>7d829530-20cc-11dd-9bb6-f65af7f707cc</Id>
  <Class>Class</Class>
  <Name>Name</Name>
  <Version>1.0</Version>
 </Service>
</Services>
6. isDeployable
isDeployable(String) -> StringArray

With this functionality it is possible to know if a service is deployable. This means all dependences are deployable too.

String Service ID

Return StringArray containing on each element a piece of xml that describes the dependency 

<Dependency>
	<Service>
		<Class>Class</Class>
		<Name>Name</Name>
		<Version>1.0</Version>
	</Service>
	<Package>MainPackage</Package>
	<Version>1.1</Version>
	<Scope level="GHN"/>
</Dependency>
7. listScopedPackages
listScopedPackages(ListScopedPackagesMessage) -> StringArray

This operation lists all dependencies with a certain scope level given as argument.

ListScopedPackagesMessage type contains serviceID and scope(GHN, VRE, VO)

Return StringArray containing on each element a piece of xml that describes the dependency 

<Dependency>
	<Service>
		<Class>Class</Class>
		<Name>Name</Name>
		<Version>1.0</Version>
	</Service>
	<Package>MainPackage</Package>
	<Version>1.1</Version>
	<Scope level="GHN"/>
</Dependency>

Dependencies

The dependencies of the Package Repository Service are:

  • GHN: to host service.
  • Commons-compress from Jakarta: to File compress functionality.
  • hsqldb: to use the DB
  • MavenCustom: to use maven repository functionality


Know Bugs and Limitations

Retrieved from "https://wiki.gcube-system.org/index.php?title=Software_Repository&oldid=3512"