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 "Technology insertion plans"

From EGIWiki
Jump to navigation Jump to search
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Tech menubar}} {{Tech Roadmap submenu}}  
{{SWProv menubar}}  
 
{{SWProv Roadmap submenu}}  
{{TOC_right}}
{{TOC_right}}  
 
The following describes the EGI Capabilities and the expected implementations from available EGI Technology Provider.
The following new technologies are currently in the planning to be inserted into the EGI production infrastructure.
The following new technologies are currently in the planning to be inserted into the EGI production infrastructure.


== SAGA ==
== New Middleware Components ==
 
In various discussions with the SAGA Project members during the EGU User Forum in Vilnius, TCB meetings and other occasions, the following was agreed:
* The SAGA adapters (for the various existing Grid middleware stacks such as UNICORE, gLite etc.) will not be provisioned through the SAGA project. Instead, the larger projects responsible for these stacks will take the respective adapters through their certification processes and publish the plugins through their repositories to EGI.
* The maintenance of the SAGA adapters will be provided by either IGE, EMI, or SAGA (transparently behind either EMI or IGE).
 
== QosCosGrid ==
 
The QosCosGrid (QCG) middleware is used in the Mapper Project. The Mapper project and EGI Operations are interested in having the QosCosGrid middleware components provisioned through EGI's Software Provisioning process into the UMD.
 
The following outlines a plan and rough target dates for when QCG components may appear in UMD releases, once it is agreed to go down that road.
 
Process owner is the EGI Technology Manager.
 
{| cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;" width=90%
|- style="background-color:darkgray;"
! style="border-bottom:1px solid black; text-align:left;" | Step
! style="border-bottom:1px solid black; text-align:left;" | Name
! style="border-bottom:1px solid black; text-align:left;" | Description
! style="border-bottom:1px solid black; text-align:left;" | EGI liaison/contact
! style="border-bottom:1px solid black; text-align:left;" | Documentation
! style="border-bottom:1px solid black; text-align:left;" width=100em | Target date
|-
| 1
| Initial security assessment
| An initial security assessment needs to demonstrate whether the software is considered reasonably safe enough to be deployed in the EGI production infrastructure. An external security assessment is also considered satisfactory input to reach a decision.
| SCG chair, COO
| [[QosCosGrid Initial Security assessment | QCG assessment]]
| May 2012
|-
| 2
| Pioneer Resource Centres for production deployment
| A minimum number of Resource Centres are needed that are willing to deploy QCG off the UMD repository for production use to support their local user communities.
 
Training for site admins may have to be provided by the CQG Technology Provider, and must be recorded here as requested, and provided.
| COO, Operations Officer, CCO
|
| June 2012
|-
| 3
| Resource Centres acting as Early Adopters
| At least one, better two or more Resource Centre are necessary for Staged Rollout. Once found they will coordinate with the Staged Rollout Manager.
 
Training for site admins may have to be provided by the CQG Technology Provider, and must be recorded here as requested, and provided.
| COO/Operations Officer, Staged Rollout Manager
|
| June 2012
|-
| 4
| Verification recruiting
| Before QCG gets accepted for production deployment, it must be verified against Quality Criteria. There must be at least one verification engineer available for each QCG component that is intended to be deployed in production. Two ways forward are possible here:
* Existing verification engineers take on the job to verify QCG
* New verification engineers must be recruited, on voluntary (unfunded, best effort) basis.
 
Training for verification engineers (whether existing or new) may have to be provided by the CQG Technology Provider, and must be recorded here as requested, and provided.
| QC Verification group leader
|
| June 2012
|-
| 5
| Compile set of Quality Criteria
| A set of Quality Criteria need to be compiled for CQG. This can be sourced from existing quality criteria, newly developed Quality Criteria, or both.
| QC Definition group leader
|
| July 2012
|-
| 6
| First provisioning of QCG for UMD
| A first bundle of QCG components are taken through the EGI Software Provisioning process.
| QC Verificaiton group leader, Staged Rollout Manager
|
| September 2012
|}


=== FTS3 ===
* HomePage: http://fts3-service.web.cern.ch/
* Planned version: [http://fts3-service.web.cern.ch/documentation/releases 3.2.27]
* Planned release date: '''Dec. 2014'''
* Softwre Provisioning Status: [https://rt.egi.eu/rt/Ticket/Display.html?id=7466 RT #7466]


=== Frontier Squid ===
* HomePage: http://frontier.cern.ch/
* Planned version: [http://frontier.cern.ch/dist/rpms-debug/frontier-squidRELEASE_NOTES 2.7STABLE9-19.1]
* Planned release date: '''Oct. 2014'''
* Softwre Provisioning Status: [https://rt.egi.eu/rt/Ticket/Display.html?id=7464 RT #7464], [https://rt.egi.eu/rt/Ticket/Display.html?id=7465 RT #7465]


== Genesis II ==
=== CVMFS ===
* HomePage: http://cernvm.cern.ch/portal/filesystem
* Planned version: [http://cernvm.cern.ch/portal/filesystem/cvmfs-2.1.19 2.1.19]
* Planned release date: '''Oct. 2014'''
* Softwre Provisioning Status: [https://rt.egi.eu/rt/Ticket/Display.html?id=7519 RT #7519], [https://rt.egi.eu/rt/Ticket/Display.html?id=7496 RT #7496]

Latest revision as of 21:24, 23 October 2014

Software Provisioning menu: Software Provisioning Process UMD Release Process Quality Assurance UMD Staged Rollout



Roadmap and Technology | Technology insertion plans | UMD Release Schedule Overview | Glossary




The following describes the EGI Capabilities and the expected implementations from available EGI Technology Provider. The following new technologies are currently in the planning to be inserted into the EGI production infrastructure.

New Middleware Components

FTS3

Frontier Squid

CVMFS

Retrieved from "https://wiki.egi.eu/w/index.php?title=Technology_insertion_plans&oldid=70930"