Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI-Engage:Software and services"

From EGIWiki
Jump to navigation Jump to search
Line 33: Line 33:
== Procedure for quality assessment <br>  ==
== Procedure for quality assessment <br>  ==


This procedure is part of [[EGI-Engage:Quality Plan#Review_process_for_deliverables_and_milestones|Review process for deliverables and milestones]] It describe how quality check is done for SW deliverables.
This procedure is part of [[PROC01_Deliverables_and_milestones_review|Review process for deliverables and milestones]] It describe how quality check is done for SW deliverables and can be found under [https://wiki.egi.eu/wiki/PROC05_Software_deliverable_testing https://wiki.egi.eu/wiki/PROC05_Software_deliverable_testing]
 
'''Requirement:'''
 
*Production tools should have a production and a testing/devel instance (at least 2 instances in total)
 
'''Testing Options:'''
 
*Each product team should choose between two possible ways to verify the quality of its release:
*#Manual test
*#(Semi-)Automatic internal procedure to test the release
 
In both cases, tests and short document must be finished by the deliverable deadline in the DoA. Similar procedures can be applied to internal EGI-Engage releases (between to SW deliverables) or to releases related to the core service activities. In these cases the short document is not strictly needed although storing a test report would be useful.
 
<br> '''1. Manual Test:'''
 
#as for the classical deliverables (the documents), 3 reviewers (1 moderator + 2 reviewers) will be assigned to each software deliverable. The WP manager has the responsibility to identify the reviewers.  
#The reviewers will perform the validation tests on the candidate release
#In the case of deliverables containing more than 1 software releases, we will have 3 reviewers for deliverable plus supporting testers
#The candidate release should be installed on the testing/devel instance
#Tests will be executed within a week. During this period the testing/devel instance should not be updated. Reviewers and developers should agree on the week to perform the tests
#Outcome of the testing process will be part of the short document describing the software release
 
'''2. (Semi-)Automatic Internal Testing procedure:'''
 
#the PT should propose to its work package leader a (semi-)automatic procedure to verify the quality of its releases. An example of this procedure is a continuous integration system with a set of automatic/manual tests executed against each built.  
#this procedure should be properly documented.  
#the document at point 2) should:
##describe the process adopted by the PT to create a new release
##describe the quality tests performed against each release
##contain instructions to rollback to the previous release in case of issues in production and describe how the risk of data loss (e.g. for A/R and accounting) is managed
#the WP manager, in collaboration with the project management, should validate and approve the procedure verifying it can guarantee a good level of quality assessment. 5) Outcome of this (Semi-)Automatic Internal Testing procedure should be reported in the short document describing the software release (including a reference to the document at point 2))
 
<br>


= Licenses  =
= Licenses  =

Revision as of 14:50, 31 May 2016

EGI-Engage project: Main page WP1(NA1) WP3(JRA1) WP5(SA1) PMB Deliverables and Milestones Quality Plan Risk Plan Data Plan
Roles and
responsibilities
WP2(NA2) WP4(JRA2) WP6(SA2) AMB Software and services Metrics Project Office Procedures



Help and support: quality@egi.eu


This page provides all rules and guides regarding software and services created under the EGI-Engage project.


Quality

Services

Quality of services produced within EGI-Engage project will be ensured by the adoption of the EGI Services management standard FitSM, a international standard developed by the FedSM project.

Instruction for Tools teams can be found under Instructions Tools teams


Software

The software produced within the project will follow the well established Software provisioning process that has been adopted since 2010, based on the definition of quality criteria, quality verification and software validation in a controlled production environment of the federated EGI infrastructure.

The development activities within the project will augment capabilities of existing open source software. The resulting software code, tools and interfaces developed as part of EGI-Engage will be released as open source code and the full access will be provided via publicly available source code repositories such as GitHub, SourceForge, Subversion (SVN), Concurrent Version System (CVS) etc. Software developers will be able to choose their preferred source code repository to better integrate with existing practices, nevertheless they will need to

  • ensure that the contribution is openly accessible,
  • add the metadata information needed to enable reuse,
  • communicate the URL to the consortium.


Procedure for quality assessment

This procedure is part of Review process for deliverables and milestones It describe how quality check is done for SW deliverables and can be found under https://wiki.egi.eu/wiki/PROC05_Software_deliverable_testing

Licenses

  • New developed software: An OSI-approved license (http://opensource.org/licenses), for any new software developed within the Project;
  • Further develop software: In order to comply with the open access policy and maximise possibility for reuse of results, EGI-Engage partners, together, agree not to further develop software released with a non-open license and which cannot be re-released using an OSI-approved license.
  • Existing software: If no existing OSI license is being used for existing software, the adoption of the Apache 2.0 license is possible.

Source Code

In order to comply with the open access policy and maximise possibility for reuse of results, EGI-Engage software code, tools and interfaces that fall under the joint ownership will be published under an OSI-approved license . If no existing OSI license is being used, we propose the adoption of the Apache 2.0 license. Free and unrestricted access to research result is a measurable barrier to uptake by SME’s and can slow down innovation in measurable terms , and the consortium will make it a priority to comply with the Horizon 2020 Mandate in full support of Europe 2020 Initiative’s Economic Growth Agenda.


The work represented by this source file was partially or entirely funded by the EGI-Engage project co-funded by the European Union (EU) Horizon 2020 program under Grant number 654142.

Copyright [yyyy] [name of copyright owner]

Licensed under the [license name] (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at [link to license]

Unless required by applicable law or agreed to in writing, software 
distributed under the License is distributed on an "AS IS" BASIS, 
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
See the License for the specific language governing permissions and 
limitations under the License.

Acknowledgement for websites

Acknowledgement should be visible at the portals and source code public repositories.
Please contact quality @ egi.eu for customized version of banner

To acknowledge EGI-Engage (Service co-funded by EGI-Engage)

Template: Tool acknowledgment4.png

To acknowledge EGI.eu EGI-Engage (Service co-funded by EGI.eu and EGI-Engage)

Template: Tool acknowledgment3.png


Software and Service table

Work package
Tool name

Deliverable 

Milestone

Tool url
Tool wiki
Description
Customer of the tool
User documentation
Technical documentation
Product team
License
Source code
WP6
Assisted pattern recognition tools integrated with EGI for citizen science
D6.1 Current version: http://lxbifi21.bifi.unizar.es:5000/ Final instance will be deployed for production under a different URL.
https://wiki.egi.eu/wiki/EGI-Engage:WP6_Caffe A demonstrator service built on the Caffe deep learning framework to classify flowers based on uploaded images. LifeWatch About the Caffe deep learning framework: http://caffe.berkeleyvision.org
About the Caffe deep learning framework: http://caffe.berkeleyvision.org

BIFI

Eduardo Lostal - eduardol@bifi.es,

Fran Sanz -frasanz@bifi.es

BSD 2-Clause License

https://github.com/BVLC/caffe ,(source code)

https://github.com/EGI-Lifewatch-CC,(training samples)

WP6
gLibrary, the INFN Digital Repository System
D6.2 Project homepage: https://glibrary.ct.infn.it API endpoint (for developers): https://glibrary.ct.infn.it:3500  (Access to be required to INFN)
https://csgf.readthedocs.org/en/latest/glibrary/docs/index.html
A service to create and manage repositories of digital assets on grid, cloud and local storage
DARIAH CC

https://csgf.readthedocs.org/en/latest/glibrary/docs/index.html http://csgf.readthedocs.org/en/latest/glibrary/docs/glibrary2.html (APIs documentation)
INFN
Apache License 2.0
https://github.com/csgf/glibrary
WP6
The Parallel Semantic Search Engine
D6.2 http://csgf.egi.eu/dariah-sse-parallel
https://csgf.readthedocs.org/en/latest/parallel-semantic-search-portlet/docs/index.html
A service conceived to demonstrate the potential of Open Access Data infrastructures coupled with semantic web technologies to address the issues of data discovery and correlation
DARIAH CC https://csgf.readthedocs.org/en/latest/parallel-semantic-search-portlet/docs/index.html (PSSE) http://csgf.readthedocs.org/en/latest/semantic-search-portlet/docs/index.html (SSE) http://csgf.readthedocs.org/en/latest/semantic-search-api/docs/index.html (API SSE)
https://csgf.readthedocs.org/en/latest/parallel-semantic-search-portlet/docs/index.html
INFN
Apache License 2.0 https://github.com/csgf/parallel-semantic-search-portlet (PSSE) https://github.com/csgf/semantic-search-portlet (SSE) https://github.com/csgf/semantic-search-api (API)
WP3
APEL
D3.3 http://apel.github.io/
https://wiki.egi.eu/wiki/Accounting_Repository
EGI Core Service – The Accounting Repository collects and stores user accounting records from various services offered by EGI.
EGI
https://twiki.cern.ch/twiki/bin/view/EMI/EMI3APELClient
https://twiki.cern.ch/twiki/bin/view/EMI/EMI3APELClient
STFC
Apache License 2.0 https://github.com/apel/apel
WP3
Operations Portal
D3.4 http://operations-portal.egi.eu
https://wiki.egi.eu/wiki/Operations_Portal
The Operations Portal provides VO management functions and other capabilities, which support the EGI daily operations. It is a central portal for the operations community that offers a bundle of different capabilities, such as the broadcast tool, VO management facilities, a security dashboard and an operations dashboard that is used to display information about failing monitoring probes and to open tickets to the affected Resource Centres. The dashboard also supports the central grid oversight activities. It is fully interfaced with the EGI Helpdesk and the monitoring system through messaging. It is a critical component as it is used by all EGI Operations Centres to provide support to the respective Resource Centres. The Operations Portal provides tools supporting the daily running of operations of the entire infrastructure: grid oversight, security operations, VO management, broadcast, VO metrics. VAPOR: the Vo Administration and operations PORtal, is a generic tool to assist community managers and support teams in performing their daily activities. The application provides resources status indicators, statistical reports, data management tools.
EGI
OPERATIONS PORTAL: https://forge.in2p3.fr/projects/opsportaluser/wiki/Main_Features_of_the_dashboard VAPOR : http://operations-portal.egi.eu/vapor_dev/globalHelp
https://forge.in2p3.fr/projects/opsportaluser/wiki/Main_Features_of_the_dashboard
IN2P3/CNRS
Apache License 2.0 https://gitlab.in2p3.fr/groups/opsportal
WP3
ARGO
D3.4 http://argo.egi.eu
https://wiki.egi.eu/wiki/ARGO
ARGO is a flexible and scalable framework for monitoring status, availability and reliability
EGI http://argoeu.github.io ; http://argo.egi.eu
http://argoeu.github.io
GRNET, SRCE, CNRS
Apache License 2.0 https://github.com/ARGOeu/
WP3
GOCDB
D3.4
https://goc.egi.eu
https://wiki.egi.eu/wiki/GOCDB
GOCDB is a central registry to record information about the topology of an e-Infrastructure. This includes entities such as resource centres (sites), services, service-endpoints and their downtimes, contact information and roles of users responsible for operations at different levels. The service enforces a number of business rules and defines different grouping mechanisms and object-tagging for the purposes of fine-grained resource filtering.
EGI
https://wiki.egi.eu/wiki/GOCDB/Documentation_Index
https://wiki.egi.eu/wiki/GOCDB/Documentation_Index
STFC
Apache License 2.0 https://github.com/GOCDB/gocdb
WP3
Secant
D3.4


Secant is a framework to detect security vulnerabilities in images of virtual machines. It tries to detect the most common security issues that often lead to incidents and prevent them from appearing in the context of EGI cloud facilities.
EGI
https://github.com/CESNET/secant
https://github.com/CESNET/secant
CESNET
Apache
https://github.com/CESNET/secant
WP4
Federated Hosting Node Manager
D4.5


The service enables D4Science infrastructure and VRE managers to respond to variations in the need for computational resources by joining/disposing additional resources from external infrastructures (i.e. FedCloud).   
Providers of the D4Science infrastructure
https://wiki.gcube-system.org/gcube/GCube_Documentation
https://wiki.gcube-system.org/gcube/GCube_Documentation
Engineering Ingegneria Informatica (ENG), Consiglio Nazionale delle Ricerche (CNR)
European Union Public Licence (EUPL version 1.1)
http://svn.research-infrastructures.eu/d4science/gcube/trunk
WP6 MoBrain Web Portal D6.4 https://mobrain.egi.eu
Portlet-based Web portal by the MoBrain Competence Centre. The portal is the entry point, it will aggregate information from the various web portals of the WeNMR, INSTRUCT and N4U research communities.
Researchers    Public


Gnúbila
https://www.liferay.com/downloads/liferay-portal/license-ce
https://www.liferay.com/downloads/liferay-portal/available-releases
WP6
Tsunami simulation portal (iCOMCOT portal)
D6.9
https://icomcot.twgrid.org

iCOMCOT provides web portal services to simulate the entire lifespan of a tsunami, from its generation, propagation and runup/rundown on coastal regions, by the Cornell Multi-grid Coupled Tsunami Model (COMCOT).
Researchers https://documents.egi.eu/document/2784
https://documents.egi.eu/document/2784
ASGC/AS
Apache License, Version 2.0
https://github.com/hdyen/comcot
WP6
Weather simulation portal (WRF portal)
D6.9
https://gwrf.twgrid.org

gWRF provides web portal services for numerical weather predication by the Weather Research and Forecasting (WRF) model developed by NCAR.
Researchers https://documents.egi.eu/document/2784 https://documents.egi.eu/document/2784 ASGC/AS Apache License, Version 2.0 https://github.com/yyr/wrf
WP3
Accounting portal
D3.5
https://accounting-devel-next.egi.cesga.es/
https://wiki.egi.eu/wiki/Accounting_Portal
The Accounting Portal provides data accounting views for users, VO Managers, NGI operations and the general public.
EGI, WLCG, Site and VO Admins, Infrastructure Users, others
https://documents.egi.eu/document/2789
https://documents.egi.eu/document/2545
CESGA / CSIC
Apache License, Version 2.0 https://github.com/cesga-egi/accounting