2014
Software
Unknown
Distributed user interfaces framework: multi-device and multi-user environments with dynamically migrating engines
Frosini L.
Framework for distributed user interfaces able: - To provide developers with an API that can be exploited in both Web and Android applications in order to obtain application user interfaces (UIs) that can be more easily dynamically distributed and/or migrated in multi-device and multi-user environments. - To dynamically create sessions of groups of users/devices with a distributed UI. The elements of the UI can be distributed according to specific device(s), group(s) of devices, specific user(s), groups of users classified by roles. - To avoid the need for a fixed server to manage the distribution, which can be useful when connectivity is limited.
Frosini L.
Framework for distributed user interfaces able: - To provide developers with an API that can be exploited in both Web and Android applications in order to obtain application user interfaces (UIs) that can be more easily dynamically distributed and/or migrated in multi-device and multi-user environments. - To dynamically create sessions of groups of users/devices with a distributed UI. The elements of the UI can be distributed according to specific device(s), group(s) of devices, specific user(s), groups of users classified by roles. - To avoid the need for a fixed server to manage the distribution, which can be useful when connectivity is limited.
See at: hiis.isti.cnr.it | CNR ExploRA
2015
Report
Open Access
Software Release Procedure and Tools
Giammatteo G., Frosini L., Laskaris N.
Deliverable D4.1 - "Software Release Procedures and Tools" aims to provide a detailed description of the procedures applied and tools used to manage releases of the gCube System within Work Package 4. gCube System is the software at the basis of all VREs applications, data management services and portals. Given the large size of the gCube system, its high degree of modularity and the number of developers involved in the implementation, a set of procedures that formalize and simplify the integration, test, documentation and distribution of the software have been defined within Work Package 4 (in particular within task T4.4 - "Software Integration and Release"). These procedures allow to coordinate the actions and the timing of the different actors to successfully release new versions of the gCube System respecting time and quality constraints. This deliverable type is "Other" and it consists of a set of wiki pages hosted by the gCube System Wiki [1]. The full version of the deliverable is available at the following URL: https://wiki.gcube-system.org/gcube/Software_Integration_and_Distribution:_Overview The deliverable is structured in the following sections: · The section "Release Roles" presents the six roles that have been identified within task T4.4 to manage the software release process: i) Release Manager, ii) Subsystem Manager, iii) Developer, iv) Tester, v) Documentation Editor and vi) Documentation Author. The deliverable describes for each role the responsibilities and contact persons; · The section "Release Tools" presents the tools used to automate different phases of the release process. The main tools described are: i) Subversion [2] used to host the source code, ii) ETICS [3] and BTRT [4] used to automate the build and test of components, iii) the gCube Distribution Site [5] used to distribute the software and host the documentation and iv) Redmine [6] used to coordinate the release cycle through tickets; · The section "Release Procedure" describes the steps and the actors of the procedures defined and executed to roll out a new version of gCube System: Continuous Integration, Release Cycle, Maintenance Release Cycle, Changelog Generation and Distribution procedure; · The section "Test Plan" presents the type of tests (i.e. static code analysis, unit testing, functional testing and deployment testing) and the procedure to execute them for every gCube release; · The section "Naming Convention" contains the naming conventions for gCube components to be applied in the different tools; · The section "Release Log" summarizes all the gCube releases and contains some useful indicators for each release (e.g. number of updated components, number of integration days); The intended readers of this deliverable are mainly technical people working on the development of the gCube System such as developers, release managers and testers. They can find in the deliverable a reference to the steps they need to follow and the tools they need to use during the release process.Source: Project report, BlueBRIDGE, Deliverable D4.1, 2015
Giammatteo G., Frosini L., Laskaris N.
Deliverable D4.1 - "Software Release Procedures and Tools" aims to provide a detailed description of the procedures applied and tools used to manage releases of the gCube System within Work Package 4. gCube System is the software at the basis of all VREs applications, data management services and portals. Given the large size of the gCube system, its high degree of modularity and the number of developers involved in the implementation, a set of procedures that formalize and simplify the integration, test, documentation and distribution of the software have been defined within Work Package 4 (in particular within task T4.4 - "Software Integration and Release"). These procedures allow to coordinate the actions and the timing of the different actors to successfully release new versions of the gCube System respecting time and quality constraints. This deliverable type is "Other" and it consists of a set of wiki pages hosted by the gCube System Wiki [1]. The full version of the deliverable is available at the following URL: https://wiki.gcube-system.org/gcube/Software_Integration_and_Distribution:_Overview The deliverable is structured in the following sections: · The section "Release Roles" presents the six roles that have been identified within task T4.4 to manage the software release process: i) Release Manager, ii) Subsystem Manager, iii) Developer, iv) Tester, v) Documentation Editor and vi) Documentation Author. The deliverable describes for each role the responsibilities and contact persons; · The section "Release Tools" presents the tools used to automate different phases of the release process. The main tools described are: i) Subversion [2] used to host the source code, ii) ETICS [3] and BTRT [4] used to automate the build and test of components, iii) the gCube Distribution Site [5] used to distribute the software and host the documentation and iv) Redmine [6] used to coordinate the release cycle through tickets; · The section "Release Procedure" describes the steps and the actors of the procedures defined and executed to roll out a new version of gCube System: Continuous Integration, Release Cycle, Maintenance Release Cycle, Changelog Generation and Distribution procedure; · The section "Test Plan" presents the type of tests (i.e. static code analysis, unit testing, functional testing and deployment testing) and the procedure to execute them for every gCube release; · The section "Naming Convention" contains the naming conventions for gCube components to be applied in the different tools; · The section "Release Log" summarizes all the gCube releases and contains some useful indicators for each release (e.g. number of updated components, number of integration days); The intended readers of this deliverable are mainly technical people working on the development of the gCube System such as developers, release managers and testers. They can find in the deliverable a reference to the steps they need to follow and the tools they need to use during the release process.Source: Project report, BlueBRIDGE, Deliverable D4.1, 2015
See at:
goo.gl 
| ISTI Repository | CNR ExploRA
2015
Software
Unknown
gCube smart executor [Release 1.2 , 04 December 2015]
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.
See at: CNR ExploRA | www.gcube-system.org
2015
Software
Unknown
gCube document store framework [Release 1.0 , 18 December 2015]
Frosini L.
Document Store Framework is a set of libraries allowing to store information in NoSQL document store. The data models are discovered at runtime and each document is validated before persisting it. The framework persist the data in NoSQL document store through connectors discovered at runtime. The currently provided connector are for CouchDB, CouchBase and MongoDB. The framework is fault-tolerant as it provides bufferization and fallbacks persistence over filesystem in the case the entitled persistence in not available at any moment. When the persistence is back, the data is retrieved from the filesystem and finally stored where expected. It is explicitly designed for cloud computing though it can also be used for local needs by providing an adequate persistence connector.
Frosini L.
Document Store Framework is a set of libraries allowing to store information in NoSQL document store. The data models are discovered at runtime and each document is validated before persisting it. The framework persist the data in NoSQL document store through connectors discovered at runtime. The currently provided connector are for CouchDB, CouchBase and MongoDB. The framework is fault-tolerant as it provides bufferization and fallbacks persistence over filesystem in the case the entitled persistence in not available at any moment. When the persistence is back, the data is retrieved from the filesystem and finally stored where expected. It is explicitly designed for cloud computing though it can also be used for local needs by providing an adequate persistence connector.
See at: CNR ExploRA | www.gcube-system.org
2015
Software
Unknown
gCube accounting framework. Release 1.1
Frosini L.
This framework provide facilities to persist and query accounting data in a distributed infrastructure (grid/cloud). The framework discover dynamically the connector of the NoSQL DB to use to persist accounting data. Moreover it discovers the connection parameters and the credential to use either from local configuration files or from the infrastructure registry. The framework is capable to recognize the different operational context and add this information to accounted data.
Frosini L.
This framework provide facilities to persist and query accounting data in a distributed infrastructure (grid/cloud). The framework discover dynamically the connector of the NoSQL DB to use to persist accounting data. Moreover it discovers the connection parameters and the credential to use either from local configuration files or from the infrastructure registry. The framework is capable to recognize the different operational context and add this information to accounted data.
See at: CNR ExploRA | www.gcube-system.org
2016
Software
Unknown
gCube accounting framework. Release 2.0
Frosini L.
This framework provide facilities to persist and query accounting data in a distributed infrastructure (grid/cloud). The framework discover dynamically the connector of the NoSQL DB to use to persist accounting data. Moreover it discovers the connection parameters and the credential to use either from local configuration files or from the infrastructure registry. The framework is capable to recognize the different operational context and add this information to accounted data.
Frosini L.
This framework provide facilities to persist and query accounting data in a distributed infrastructure (grid/cloud). The framework discover dynamically the connector of the NoSQL DB to use to persist accounting data. Moreover it discovers the connection parameters and the credential to use either from local configuration files or from the infrastructure registry. The framework is capable to recognize the different operational context and add this information to accounted data.
See at: CNR ExploRA
2016
Software
Unknown
gCube accounting framework. Release 2.1
Frosini L.
This framework provide facilities to persist and query accounting data in a distributed infrastructure (grid/cloud). The framework discover dynamically the connector of the NoSQL DB to use to persist accounting data. Moreover it discovers the connection parameters and the credential to use either from local configuration files or from the infrastructure registry. The framework is capable to recognize the different operational context and add this information to accounted data
Frosini L.
This framework provide facilities to persist and query accounting data in a distributed infrastructure (grid/cloud). The framework discover dynamically the connector of the NoSQL DB to use to persist accounting data. Moreover it discovers the connection parameters and the credential to use either from local configuration files or from the infrastructure registry. The framework is capable to recognize the different operational context and add this information to accounted data
See at: CNR ExploRA | www.gcube-system.org
2016
Software
Unknown
gCube accounting framework. Release 2.2
Frosini L.
This framework provide facilities to persist and query accounting data in a distributed infrastructure (grid/cloud). The framework discover dynamically the connector of the NoSQL DB to use to persist accounting data. Moreover it discovers the connection parameters and the credential to use either from local configuration files or from the infrastructure registry. The framework is capable to recognize the different operational context and add this information to accounted data.
Frosini L.
This framework provide facilities to persist and query accounting data in a distributed infrastructure (grid/cloud). The framework discover dynamically the connector of the NoSQL DB to use to persist accounting data. Moreover it discovers the connection parameters and the credential to use either from local configuration files or from the infrastructure registry. The framework is capable to recognize the different operational context and add this information to accounted data.
See at: CNR ExploRA | www.gcube-system.org
2016
Software
Unknown
gCube document store framework [Release 1.1 , 18 May 2016]
Frosini L.
Document Store Framework is a set of libraries allowing to store information in NoSQL document store. The data models are discovered at runtime and each document is validated before persisting it. The framework persist the data in NoSQL document store through connectors discovered at runtime. The currently provided connector are for CouchDB, CouchBase and MongoDB. The framework is fault-tolerant as it provides bufferization and fallbacks persistence over filesystem in the case the entitled persistence in not available at any moment. When the persistence is back, the data is retrieved from the filesystem and finally stored where expected. It is explicitly designed for cloud computing though it can also be used for local needs by providing an adequate persistence connector.
Frosini L.
Document Store Framework is a set of libraries allowing to store information in NoSQL document store. The data models are discovered at runtime and each document is validated before persisting it. The framework persist the data in NoSQL document store through connectors discovered at runtime. The currently provided connector are for CouchDB, CouchBase and MongoDB. The framework is fault-tolerant as it provides bufferization and fallbacks persistence over filesystem in the case the entitled persistence in not available at any moment. When the persistence is back, the data is retrieved from the filesystem and finally stored where expected. It is explicitly designed for cloud computing though it can also be used for local needs by providing an adequate persistence connector.
See at: CNR ExploRA | www.gcube-system.org
2016
Software
Unknown
gCube smart executor [Release 1.3 , 08 February 2016]
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.
See at: CNR ExploRA | www.gcube-system.org
2016
Software
Unknown
gCube Information System
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
See at: CNR ExploRA | www.gcube-system.org
2016
Software
Unknown
gCube Information System. [Release 1.1]
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
See at: CNR ExploRA | www.gcube-system.org
2016
Software
Unknown
gCube Smart Executor. [Release 1.4]
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.Project(s): BlueBRIDGE
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.Project(s): BlueBRIDGE
See at: CNR ExploRA | www.gcube-system.org
2017
Software
Unknown
gCube Information System. [Release 1.3]
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
See at: CNR ExploRA | www.gcube-system.org
2017
Software
Unknown
gCube Smart Executor. [Release 1.6]
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.
See at: CNR ExploRA | www.gcube-system.org
2017
Software
Unknown
gCube Smart Executor. [Release 1.7]
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.
See at: CNR ExploRA | www.gcube-system.org
2017
Software
Unknown
gCube Information System. [Release 1.4]
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
See at: CNR ExploRA | www.gcube-system.org
2017
Software
Unknown
gCube Information System. [Release 1.5]
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
See at: CNR ExploRA | www.gcube-system.org
2017
Software
Unknown
gCube Smart Executor. [Release 1.5]
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.
Frosini L.
Smart Executor is a service which allows to schedule, start, stop, and monitor the execution of tasks. It runs tasks provided as plugins (dynamically discovered). The Smart Executor has been designed to be deployed in a typical cloud-based infrastructure and it offers a SOAP/REST interface and a Java client library.
See at: CNR ExploRA | www.gcube-system.org
2017
Software
Unknown
gCube Information System. [Release 1.6]
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
Frosini L.
The gCube Information System (shortly, IS) delivers functionalities for publishing, discovering, and monitoring the set of resources forming the infrastructure. Moreover it allows to federate different infrastructures. It acts as the registry of the infrastructure, i.e. all the resources are registered in the IS and every service partaking in the infrastructure must refer to it to dynamically discover the other infrastructure constituents. Moreover, the approach provided by the IS is of great support for the dynamic deployment capabilities of gCube.Project(s): BlueBRIDGE
See at: CNR ExploRA | www.gcube-system.org