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 "Middleware"

From EGIWiki
Jump to navigation Jump to search
 
(296 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Template:Op menubar}}
{{Template:Tech menubar}} {{Template:Middleware_menubar}}  
{{TOC_right}}


[[Category:Middleware]]
This wiki collects all the information concerning Middleware supported in EGI.
This page provdes information on supported software, the related release roadmaps and documentation, together with information about processes to validate and deploy new releases and to phase out unsupported software releases. The Technology Providers that currently signed a Service Level Agreement are the [http://www.eu-emi.eu/ European Middleware Initiative] (EMI) and the [http://www.ige-project.eu/ Initiative for Globus in Europe] (IGE).
 
<br>
 
 
 
<br>
 
== UMD3 and UMD4 (main middleware distribution)  ==
 
Unified Middleware Distribution (UMD) is the integrated set of software components contributed by Technology Providers and packaged for deployment as production quality services in EGI.
 
'''UMD4 is the current supported UMD distribution.''' It supports CentOS7, SL6. Also Ubuntu 16 (Xenial) will be supported in the future, if Technology Providers require that.<br>
 
UMD3 will still receive security or critical updates for SL6. UMD3/SL5 and UMD3/Debian are not supported anymore.
 
=== Support for yaim  ===
 
With UMD4/CentOS7 yaim is not supported anymore as a tool to configure the distributed middleware. Instead, every product will follow its documented procedure to install, configure, test the product.
 
So for each product, UMD users will point to the product-specific documentation, which will provide puppet recipes, or ansible recipes, or custom scripts or even step-by-step guides (this last is true especially with very simply configurated products). Even yaim can be used as a configuration tool, and indeed you will find it distributed in the upcoming UMD4.4, but this will mean that some team (in this case the VOBOX) is using yaim to configure their products.  
 
=== Why is SL6 both in UMD3 and UMD4?  ===
 
The UMD3/SL6 and UMD4/SL6: the latter is a mirror of the former excluding products that are reaching or already reached end of life. If you want to install a UI, you can use both, but we advice to use UMD4/SL6.Of course dedicated documentation will be provided with the release in CentOS7.  
 
== CMD-OS and CMD-ONE (cloud middleware)  ==
 
The Cloud Middleware Distribution (CMD) distributes OpenStack and OpenNebula integration components developed by Cloud Technology Providers to Resource Centres (i.e. cloud sites).
 
Two different distribution are available, CMD-OS for OpenStack and CMD-ONE for OpenNebula. For further details, please have a look at the Cloud Middleware Distribution wiki https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution .  


= Technology Providers=
== UMD and CMD ==
==EMI==
===Roadmap===
* DJRA1.1.1 – [https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDJRA111 Compute Area Work Plan and Status Report]
* DJRA1.2.1 – [https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDJRA121 Data Area Work Plan and Status Report]
* DJRA1.3.1 – [https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDJRA131 Security Area Work Plan and Status Report]
* DJRA1.4.1 - [https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDJRA141 Infrastructure Area Work Plan and Status Report]  
===Release schedules and documentation===
* NEW! '''[https://savannah.cern.ch/task/?group=emi-releases Release schedule]''': the EMI tracker will contain items about individual component releases as well as EMI releases
* NEW! EMI services [https://twiki.cern.ch/twiki/bin/view/EMI/EMIServicesDocs documentation]


=== ARC ===
Regular grid components and in general all non cloud-specific components will keep going to UMD. Also clients for the user to interact with the EGI infrastructure are distributed with UMD (storage clients, cloud-related clients).  
* [http://www.nordugrid.org/arc/ Overview]
*'''Releases'''
** [http://www.nordugrid.org/arc/releases/0_8_3/ Latest release]
** [http://wiki.nordugrid.org/index.php/Roadmap Development roadmap]
** [http://wiki.nordugrid.org/index.php/Release_management Release management]
*'''[http://www.nordugrid.org/papers.html Documentation]'''
<!-- * [http://download.nordugrid.org/ Download page]-->


===gLite ===
At the moment UMD4 is supported, accepting CentOS7 and SL6 packages. '''Ubuntu is not yet enabled'''.  
* '''Supported middleware'''
** gLite [http://glite.cern.ch/support_calendar/ support calendar]
** gLite 3.1 [http://glite.cern.ch/R3.1/ end-of-support schedule], OMB approved, 26 Nov 2010
** [https://twiki.cern.ch/twiki/bin/view/LCG/WLCGBaselineVersions WLCG baseline clients and services]
* '''Releases'''
** [http://glite.cern.ch/ Latest releases] and future [http://bit.ly/22we3i Release Schedule]
<!-- * [http://glite.web.cern.ch/glite/packages/latestRelease.asp Latest updates] -->


* '''Documentation'''
Products in UMD major releases should have a release cycle that is compatible with the UMD one: major releases are supported with updates for at least 1 year, security for 2 years. As this doesn't happen with OpenStack related components, we created CMD for OpenStack.  
** [http://glite.cern.ch/admin_documentation Installation and configuration documentation]
<!--* [http://glite.web.cern.ch/glite/documentation/default.asp User guide and general docuementation]
** gLite [http://glite.web.cern.ch/glite/packages/R3.2/ 3.2]: User guide and general docuementation
** gLite [http://glite.web.cern.ch/glite/packages/R3.1/ 3.1]: User guide and general docuementation-->
** [http://glite.web.cern.ch/glite/documentation/userGuide.asp gLite User Guide]


=== UNICORE ===
CMD for OpenNebula has been created to decouple from OpenStack, having a very different release cycle.


*'''Download'''
{| width="800" cellspacing="1" cellpadding="1" border="1"
** Download server & central services: [https://sourceforge.net/projects/unicore/files/1%20UNICORE%206%20Servers%20and%20Services/1.1%20Core%20Server/ Core Server] | [https://sourceforge.net/projects/unicore/files/1%20UNICORE%206%20Servers%20and%20Services/1.2%20Workflow%20System/ Workflow System] | [https://sourceforge.net/projects/unicore/files/1%20UNICORE%206%20Servers%20and%20Services/1.3%20Common%20Information%20Service/ Common Information Service]
|+ '''Supported middleware distributions summary'''  
** Download clients: [https://sourceforge.net/projects/unicore/files/2%20UNICORE%206%20Clients,%20Applications,%20and%20APIs/2.1%20UNICORE%20Rich%20Client%20(URC)/ Rich Client] | [https://sourceforge.net/projects/unicore/files/2%20UNICORE%206%20Clients,%20Applications,%20and%20APIs/2.3%20Commandline%20Client%20(UCC)/ Command Line Client] | [https://sourceforge.net/projects/unicore/files/2%20UNICORE%206%20Clients,%20Applications,%20and%20APIs/2.4%20HiLA%20Programming%20API/ HiLA API]
|-
* '''[http://unicore.eu/documentation/ Documentation]'''
|
| '''Description'''
| '''Operating Systems supported'''
|-
| '''UMD4'''
| Regular grid components and in general all non cloud-specific components will keep going to UMD. Also clients for the user to interact with the EGI infrastructure are distributed with UMD (storage clients, cloud-related clients).  
| CentOS7, SL6
|-
| '''CMD-OS'''
| OpenStack integration components developed by Cloud Technology Providers to Resource Centres
| CentOS7, Xenial
|-
| '''CMD-ONE'''  
| OpenNebula integration components developed by Cloud Technology Providers to Resource Centres
| CentOS7
|}


== IGE ==
== Wiki description  ==
* '''Releases'''
** IGE [https://docs.google.com/document/d/1zjUEcBjyR3hDLGRqAkE5OudSN94ZHa7PHVNyhQIOV0c/edit?hl=en&authkey=CMzLvcEH&pli=1# Release Schedule]
* '''Documentation'''
** GT [http://www.globus.org/toolkit/docs/latest-stable/user/#gtuser User Guide]
** GT [http://www.globus.org/toolkit/docs/latest-stable/ Release Manuals]


= Collecting Requirements=
{|
* [https://www.egi.eu/indico/getFile.py/access?contribId=1&resId=0&materialId=0&confId=152 EGI Operations requirements gathering process], OMB, 21 Dec 2010
|-
* NEW! [https://wiki.egi.eu/wiki/Nagios-requirements.html Nagios test requirements]
| [[Software Calendars|Software Calendars]]  
* NEW! [https://wiki.egi.eu/wiki/mw-requirements.html Middleware requirements]
| Support Calendar, Decommissioning Calendar, Operations Calendar
* [https://wiki.egi.eu/wiki/tool-requirements.html Tool requirements - coming soon]
|-
* NEW! [[EGI Operations Surveys]]
| [[Technology Providers|Technology Providers list]]
| Information about Technology Providers supporting EGI
|-
| [[UMD Release Schedule|Unified Middleware Distribution (UMD) release schedule]]  
| the planned release schedule for UMD major and minor releases
|-
| [[Software release and deployment process|Release and deployment process]]
| describes the EGI process to deploy new versions of deployed software and operational tools into the EGI production infrastructure
|-
| [[Middleware Requirements|Middleware and Tool Requirements]]  
| existing requirements, how to submit requirements
|-
| [[EGI Cloud Middleware Distribution|Cloud Middleware Distribution]]  
| details on the CMD release cycle(still proposal)
|}


=Software deployment processes =
= External resources  =
This section describes the EGI process to deploy new versions of deployed software and operational tools into the EGI production infrastructure.
* [[Middleware:Release_Process]]
* [https://documents.egi.eu/document/53 Deploying Software into the EGI production infrastructure, Milestone MS402]
* Staged Rollout: list of [https://wiki.egi.eu/wiki/Staged-Rollout Early Adopters and software components]
* [https://wiki.egi.eu/wiki/EGI_IGTF_Release_Process EGI IGTF Release Process]


Other:
*[https://twiki.cern.ch/twiki/bin/view/LCG/WLCGBaselineVersions Baseline versions of services and client tools for WLCG]
* [https://edms.cern.ch/document/985325/1 Procedure for retiring middleware services] (to be updated)
* [https://edms.cern.ch/document/1057955/1 Processes for Maintaining and Enforcing a List of Supported gLite Middleware Service] (to be updated)


=Standards=
[[Category:Middleware]]
* GLUE Schema Specification [http://forge.gridforum.org/sf/docman/do/downloadDocument/projects.glue-wg/docman.root.background.specifications/doc14185 version 1.3], 2007
* GLUE Specification [http://www.ogf.org/documents/GFD.147.pdf version 2.0], 2009 | [http://glue20.web.cern.ch/glue20/ HTML rendering]
* [https://twiki.cern.ch/twiki/pub/LCG/WLCGCommonComputingReadinessChallenges/WLCG_GlueSchemaUsage-1.8.pdf Usage of Glue Schema v1.3 for WLCG Installed Capacity information]

Latest revision as of 17:01, 22 August 2017

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


Middleware menu: Home Software Calendars Technology Providers UMD Release Schedule UMD Products Overview UMD Products ID Cards Release and deployment process Middleware Requirements Next middleware release


This wiki collects all the information concerning Middleware supported in EGI.




UMD3 and UMD4 (main middleware distribution)

Unified Middleware Distribution (UMD) is the integrated set of software components contributed by Technology Providers and packaged for deployment as production quality services in EGI.

UMD4 is the current supported UMD distribution. It supports CentOS7, SL6. Also Ubuntu 16 (Xenial) will be supported in the future, if Technology Providers require that.

UMD3 will still receive security or critical updates for SL6. UMD3/SL5 and UMD3/Debian are not supported anymore.

Support for yaim

With UMD4/CentOS7 yaim is not supported anymore as a tool to configure the distributed middleware. Instead, every product will follow its documented procedure to install, configure, test the product.

So for each product, UMD users will point to the product-specific documentation, which will provide puppet recipes, or ansible recipes, or custom scripts or even step-by-step guides (this last is true especially with very simply configurated products). Even yaim can be used as a configuration tool, and indeed you will find it distributed in the upcoming UMD4.4, but this will mean that some team (in this case the VOBOX) is using yaim to configure their products.

Why is SL6 both in UMD3 and UMD4?

The UMD3/SL6 and UMD4/SL6: the latter is a mirror of the former excluding products that are reaching or already reached end of life. If you want to install a UI, you can use both, but we advice to use UMD4/SL6.Of course dedicated documentation will be provided with the release in CentOS7.

CMD-OS and CMD-ONE (cloud middleware)

The Cloud Middleware Distribution (CMD) distributes OpenStack and OpenNebula integration components developed by Cloud Technology Providers to Resource Centres (i.e. cloud sites).

Two different distribution are available, CMD-OS for OpenStack and CMD-ONE for OpenNebula. For further details, please have a look at the Cloud Middleware Distribution wiki https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution .

UMD and CMD

Regular grid components and in general all non cloud-specific components will keep going to UMD. Also clients for the user to interact with the EGI infrastructure are distributed with UMD (storage clients, cloud-related clients).

At the moment UMD4 is supported, accepting CentOS7 and SL6 packages. Ubuntu is not yet enabled.

Products in UMD major releases should have a release cycle that is compatible with the UMD one: major releases are supported with updates for at least 1 year, security for 2 years. As this doesn't happen with OpenStack related components, we created CMD for OpenStack.

CMD for OpenNebula has been created to decouple from OpenStack, having a very different release cycle.

Supported middleware distributions summary
Description Operating Systems supported
UMD4 Regular grid components and in general all non cloud-specific components will keep going to UMD. Also clients for the user to interact with the EGI infrastructure are distributed with UMD (storage clients, cloud-related clients). CentOS7, SL6
CMD-OS OpenStack integration components developed by Cloud Technology Providers to Resource Centres CentOS7, Xenial
CMD-ONE OpenNebula integration components developed by Cloud Technology Providers to Resource Centres CentOS7

Wiki description

Software Calendars Support Calendar, Decommissioning Calendar, Operations Calendar
Technology Providers list Information about Technology Providers supporting EGI
Unified Middleware Distribution (UMD) release schedule the planned release schedule for UMD major and minor releases
Release and deployment process describes the EGI process to deploy new versions of deployed software and operational tools into the EGI production infrastructure
Middleware and Tool Requirements existing requirements, how to submit requirements
Cloud Middleware Distribution details on the CMD release cycle(still proposal)

External resources