Difference between revisions of "EGI-Engage:Software and services"
Line 114: | Line 114: | ||
! scope="col" | Work package<br> | ! scope="col" | Work package<br> | ||
! scope="col" | Tool name<br> | ! scope="col" | Tool name<br> | ||
! scope="col" | | |||
Deliverable | |||
Milestone | |||
! scope="col" | Tool url<br> | ! scope="col" | Tool url<br> | ||
! scope="col" | Tool wiki<br> | ! scope="col" | Tool wiki<br> | ||
Line 126: | Line 131: | ||
| WP6<br> | | WP6<br> | ||
| Assisted pattern recognition tools integrated with EGI for citizen science<br> | | Assisted pattern recognition tools integrated with EGI for citizen science<br> | ||
| D6.1 | |||
| Current version: http://lxbifi21.bifi.unizar.es:5000/ Final instance will be deployed for production under a different URL. <br> | | Current version: http://lxbifi21.bifi.unizar.es:5000/ Final instance will be deployed for production under a different URL. <br> | ||
| https://wiki.egi.eu/wiki/EGI-Engage:WP6_Caffe | | https://wiki.egi.eu/wiki/EGI-Engage:WP6_Caffe | ||
Line 148: | Line 154: | ||
| WP6<br> | | WP6<br> | ||
| gLibrary, the INFN Digital Repository System<br> | | gLibrary, the INFN Digital Repository System<br> | ||
| 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) <br> | | Project homepage: https://glibrary.ct.infn.it API endpoint (for developers): https://glibrary.ct.infn.it:3500 (Access to be required to INFN) <br> | ||
| https://csgf.readthedocs.org/en/latest/glibrary/docs/index.html<br> | | https://csgf.readthedocs.org/en/latest/glibrary/docs/index.html<br> | ||
Line 160: | Line 167: | ||
| WP6<br> | | WP6<br> | ||
| The Parallel Semantic Search Engine<br> | | The Parallel Semantic Search Engine<br> | ||
| D6.2 | |||
| http://csgf.egi.eu/dariah-sse-parallel <br> | | http://csgf.egi.eu/dariah-sse-parallel <br> | ||
| https://csgf.readthedocs.org/en/latest/parallel-semantic-search-portlet/docs/index.html<br> | | https://csgf.readthedocs.org/en/latest/parallel-semantic-search-portlet/docs/index.html<br> | ||
Line 170: | Line 178: | ||
| 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)<br> | | 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)<br> | ||
|- | |- | ||
| <br> | | WP3<br> | ||
| <br> | | APEL<br> | ||
| <br> | | D3.3 | ||
| <br> | | http://apel.github.io/<br> | ||
| <br> | | https://wiki.egi.eu/wiki/Accounting_Repository<br> | ||
| <br> | | EGI Core Service – The Accounting Repository collects and stores user accounting records from various services offered by EGI.<br> | ||
| <br> | | EGI<br> | ||
| <br> | | https://twiki.cern.ch/twiki/bin/view/EMI/EMI3APELClient<br> | ||
| <br> | | https://twiki.cern.ch/twiki/bin/view/EMI/EMI3APELClient<br> | ||
| | | STFC<br> | ||
| <br> | | Apache License 2.0 | ||
| https://github.com/apel/apel<br> | |||
|- | |- | ||
| <br> | | WP3<br> | ||
| <br> | | Operations Portal<br> | ||
| <br> | | D3.4 | ||
| <br> | | http://operations-portal.egi.eu <br> | ||
| <br> | | https://wiki.egi.eu/wiki/Operations_Portal <br> | ||
| 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.<br> | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 196: | Line 206: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 208: | Line 219: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 220: | Line 232: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 232: | Line 245: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 244: | Line 258: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 256: | Line 271: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 268: | Line 284: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 280: | Line 297: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 292: | Line 310: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 304: | Line 323: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 316: | Line 336: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 328: | Line 349: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 340: | Line 362: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 352: | Line 375: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 364: | Line 388: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 376: | Line 401: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 388: | Line 414: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 400: | Line 427: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 412: | Line 440: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 424: | Line 453: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 436: | Line 466: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 448: | Line 479: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 460: | Line 492: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> | ||
Line 472: | Line 505: | ||
| <br> | | <br> | ||
| <br> | | <br> | ||
| | |||
| <br> | | <br> | ||
| <br> | | <br> |
Revision as of 15:52, 31 March 2016
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.
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.
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))
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)
To acknowledge EGI.eu EGI-Engage (Service co-funded by EGI.eu and EGI-Engage)
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) |
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. |
||||||