Difference between revisions of "Technology"

From EGIWiki
Jump to: navigation, search
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Tech menubar}} {{TOC_right}}
+
{{Tech menubar}}  
  
The EGI Technology wiki space aims at providing a platform for documenting all types of documentation related to technology, system architecture and innovation.
+
Welcome to '''EGI Technology'''. 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.
+
*'''[[EGI Software Provisioning|Software Provisioning]]''' - activity governs and executes processes through which EGI ensures that deployed software
 +
*'''[[Middleware|Middleware]]''' - information concerning Middleware supported in EGI, (Product teams, support, decommissioning and operations calendars, UMD release schedule, requirements gathering)
 +
*'''[[EGI Technology Glossary|Technology Glossary]]''' - terms that are used in describing the processes of provisioning and supporting software for EGIs production infrastructure.
  
== Governance & Coordination ==
+
If you want to contact EGI for comments, questions or any kind of feedback related to the following pages, please send an e-mail to '''operations at mailman.egi.eu''' or submit a ticket to the "Operations" Support Unit in the [http://helpdesk.egi.eu/ EGI Helpdesk].
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 ==
+
== Management boards ==
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.
 
  
Innovation labs can be experiments, proofs of concepts, task forces, informal collaborations. However, the key characteristics of any such lab are:
+
*'''Technology Coordination Board (TCB)''' <br>The TCB governs the overall process of technology evolution through negotiating formal agreements with Technology Providers who are responsible for the constant delivery of software according to the requirements developed and specified by the EGI Community (End users ans Operations). Members of the TCB are members of the executive management of EGI.eu, representing the EGI User Community, the EGI Operations Community, and EGI Software Provisioning activity. Furthermore, key representatives of affiliated Technology Providers partake meetings of the TCB providing input, guidance and feedback from software engineering experts within their teams.
* Short-lived, focused activity examining a well-scoped problem and potential solution
+
*'''Quality Assurance Task Force (QATF)''' <br>The Quality Assurance Task Force provides a forum for specialists in Quality Assurance from EGI and affiliated Technology Providers as a regular forum for continuous review and improvements of the Quality Criteria defined within EGI.
* Documented outcome summarising the findings and outcomes, advocating pro or contra further examination under closer scrutiny and improved professional engineering.
+
*'''Automation Task Force (ATF)''' <br>The Automation Task Force coordinates the technical processes and integration points for Technology Providers and EGI's technical implementation of the Software Provisioning process. Experts in process automation, repository maintenance and software provisioning from EGI and its affiliated Technology Providers define the processes and artifacts required to sustain continuous software provisioning on EGIs production infrastructure.
  
== Roadmap ==
+
[[Image:Provisioning workflow.png]]
The roadmap informs about the goals of the technology innovation. The roadmap provides a high-level overview on the various activities with links to further information and detail. Typically, activities mentioned in the roadmap are innovative in nature and thus backed by projects receiving public funding of some sort. For what concerns EGI, the ultimate goal and decision and the end of the (technology related) project is whether to insert the technology into the EGI production infrastructure or not.
 
  
== Architecture ==
+
[[Category:Technology]]
The high-level architecture of the EGI production infrastructure is documented in this area. The level of detail will remain at (sub-)systems and interfaces and drill into details where absolutely necessary. Documentation on architecture and design of the individual systems will be added or linked subsequently.
 
 
 
== Deployed platforms ==
 
This section will provide over time an overview and high-level description of the Community Platforms deployed in the EGI production infrastructure.
 

Latest revision as of 16:29, 23 March 2016

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


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

  • Software Provisioning - activity governs and executes processes through which EGI ensures that deployed software
  • Middleware - information concerning Middleware supported in EGI, (Product teams, support, decommissioning and operations calendars, UMD release schedule, requirements gathering)
  • Technology Glossary - terms that are used in describing the processes of provisioning and supporting software for EGIs production infrastructure.

If you want to contact EGI for comments, questions or any kind of feedback related to the following pages, please send an e-mail to operations at mailman.egi.eu or submit a ticket to the "Operations" Support Unit in the EGI Helpdesk.

Management boards

  • Technology Coordination Board (TCB)
    The TCB governs the overall process of technology evolution through negotiating formal agreements with Technology Providers who are responsible for the constant delivery of software according to the requirements developed and specified by the EGI Community (End users ans Operations). Members of the TCB are members of the executive management of EGI.eu, representing the EGI User Community, the EGI Operations Community, and EGI Software Provisioning activity. Furthermore, key representatives of affiliated Technology Providers partake meetings of the TCB providing input, guidance and feedback from software engineering experts within their teams.
  • Quality Assurance Task Force (QATF)
    The Quality Assurance Task Force provides a forum for specialists in Quality Assurance from EGI and affiliated Technology Providers as a regular forum for continuous review and improvements of the Quality Criteria defined within EGI.
  • Automation Task Force (ATF)
    The Automation Task Force coordinates the technical processes and integration points for Technology Providers and EGI's technical implementation of the Software Provisioning process. Experts in process automation, repository maintenance and software provisioning from EGI and its affiliated Technology Providers define the processes and artifacts required to sustain continuous software provisioning on EGIs production infrastructure.

Provisioning workflow.png