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"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
{{Tech menubar}}  
{{Tech menubar}}  
[[Category:Technology]]


{| width="100%" style="background: none repeat scroll 0% 0% rgb(249, 249, 249); margin: 1.2em 0px 6px; border: 1px solid rgb(221, 221, 221);"
{| width="100%" style="background: none repeat scroll 0% 0% rgb(249, 249, 249); margin: 1.2em 0px 6px; border: 1px solid rgb(221, 221, 221);"
Line 18: Line 17:


|}
|}
The EGI Technology wiki space aims at providing a platform for documenting all types of documentation related to technology, system architecture and innovation.


This type of cross-cutting documentation is a very young concept in EGI and will be expanded over time.
The EGI Technology wiki space aims at providing a platform for documenting all types of documentation related to technology, system architecture and innovation.<br>


== Governance & Coordination ==
== Governance &amp; Coordination ==
All policies and processes that have anything to do with technology, and involve people dealing with technology require clear documentation and overview. This includes:
* Technology Coordination Board
* UMD Release Team (URT)
* Technology Provider support network


== Innovation Laboratory  ==
Work related to Technology run on EGI&nbsp;Infrastructure is coordinated by following teams:


Any technology deprecates over time, and is eventually replaced by alternative software and technology. In the very early stages in the technology lifecycle, anything new requires testing and some minimal proof of further exploring its suitability for the technology stack deployed in EGI.
*Technology Coordination Board
*UMD Release Team (URT)
*Technology Provider support network


Innovation labs can be experiments, proofs of concepts, task forces, informal collaborations. However, the key characteristics of any such lab are:


*Short-lived, focused activity examining a well-scoped problem and potential solution
*Documented outcome summarising the findings and outcomes, advocating pro or contra further examination under closer scrutiny and improved professional engineering.


See more: '''[https://wiki.egi.eu/wiki/Innovation_Laboratory Innovation Laboratory]'''
== Deployed platforms  ==


This section is supposed to provide overview and high-level description of the Community Platforms deployed in the EGI production infrastructure.


== Deployed platforms ==
This section will provide over time an overview and high-level description of the Community Platforms deployed in the EGI production infrastructure.
[[Category:Technology]]
[[Category:Technology]]

Revision as of 19:29, 9 December 2014

Technology Software Component Delivery Software Provisioning UMD Middleware Cloud Middleware Distribution Containers Distribution Technology Glossary


Welcome to EGI Technology

Contact information

e-mail: send an e-mail to operations at mailman.egi.eu

Ticket: submit a ticket to the "Operations" Support Unit in the EGI Helpdesk

The EGI Technology wiki space aims at providing a platform for documenting all types of documentation related to technology, system architecture and innovation.

Governance & Coordination

Work related to Technology run on EGI Infrastructure is coordinated by following teams:

  • Technology Coordination Board
  • UMD Release Team (URT)
  • Technology Provider support network


Deployed platforms

This section is supposed to provide overview and high-level description of the Community Platforms deployed in the EGI production infrastructure.