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
 
(267 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.
 
<br>
 
 
 
<br>
 
== UMD3 and UMD4 (main middleware distribution)  ==


This page provides 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).
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.  


= UMD Roadmap =
'''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>
The Unified Middleware Distribution (UMD) is the integrated set of software components that EGI makes available from technology providers within the EGI Community. These components are distributed to provide an integrated offering for deployment on the EGI production infrastructure.


'''Latest UMD Roadmap''': [https://documents.egi.eu/document/272 D5.2]
UMD3 will still receive security or critical updates for SL6. UMD3/SL5 and UMD3/Debian are not supported anymore.  


= Technology Providers=
=== Support for yaim  ===
==EMI==
===Roadmap and Support Plan===
* 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]
* EMI Software Maintenance and Support Plan ([https://twiki.cern.ch/twiki/pub/EMI/DeliverableDSA11/EMI-DSA1.1-1277556-Software_Maintenance_Support_Plan-v1.0.pdf pdf])
* EMI [https://twiki.cern.ch/twiki/bin/view/EMI/EmiDeliverables Deliverables]
**[https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDNA131 Technical Development Plan]


===Release schedules and documentation===
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.  
* 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 ===
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.  
* [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 ===
=== Why is SL6 both in UMD3 and UMD4?  ===
* '''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'''
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.  
** [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-OS and CMD-ONE (cloud middleware)  ==


*'''Download'''
The Cloud Middleware Distribution (CMD) distributes OpenStack and OpenNebula integration components developed by Cloud Technology Providers to Resource Centres (i.e. cloud sites).  
** 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]
** 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]'''


== IGE ==
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 .  
* '''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]


= YAIM =
== UMD and CMD  ==
* [https://twiki.cern.ch/twiki/bin/view/LCG/Site-info_configuration_variables YAIM configuration variables]
* [https://twiki.cern.ch/twiki/bin/view/LCG/YaimGuide400 YAIM 4 Guide for System Administrators]
* [https://twiki.cern.ch/twiki/bin/view/LCG/YaimGuide400#Known_issues YAIM 4 known issues]


=Software release and deployment process =
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).  
This section describes the EGI process to deploy new versions of deployed software and operational tools into the EGI production infrastructure.
==Release workflow==
<!--* [[Middleware:Release_Process]]-->
* [[NSRW_New_Software_Release_Workflow|New Software Release Workflow]] (NSRW)
<!--* [https://documents.egi.eu/document/53 Deploying Software into the EGI production infrastructure, Milestone MS402]-->


==Deployment workflow (Staged Rollout)==
At the moment UMD4 is supported, accepting CentOS7 and SL6 packages. '''Ubuntu is not yet enabled'''.  
* Staged Rollout [[Staged-rollout-procedures|workflow]]
* [https://www.egi.eu/earlyAdopters/table Early Adopters]
* [https://www.egi.eu/earlyAdopters/teams distribution] of Early Adopters per component
<!--* 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:
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.  
* [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)


= Requirements=
CMD for OpenNebula has been created to decouple from OpenStack, having a very different release cycle.  
== Existing requirements ==
The following table provides access to ''all'' open EGI requirements (UMD requirements and tool requirements), submitted by the User Community and the Operations Community.


{|border="1"
{| width="800" cellspacing="1" cellpadding="1" border="1"
|- style="background-color:darkgray;"
|+ '''Supported middleware distributions summary'''  
|'''Areas'''
|'''Tickets'''
|- style="background:lightgray;"
|rowspan="2" |'''User Communities'''
|[https://wiki.egi.eu/wiki/RTReports#Requirements_from_user_communities UMD Requirements]
|-
|-
| [https://wiki.egi.eu/wiki/RTReports#Requirements_for_user_tools_and_services Tools and Services Requirements]
|  
|- style="background:lightgray;"
| '''Description'''
|rowspan="2" |'''Operations'''
| '''Operating Systems supported'''
|[https://wiki.egi.eu/wiki/RTReports#Requirements_for_UMD UMD Requirements]. These requirements can be also accessed directly on RT from the [https://rt.egi.eu/rt/Dashboards/1749/SA1%20Middleware%20requirements SA1 middleware requirements dashboard]
|-
|-
|[https://wiki.egi.eu/wiki/RTReports#Requirements_for_Operational_Tools Operational Tools]
| '''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
|}
|}


== Collecting requirements ==
== Wiki description  ==
* [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
* [https://wiki.egi.eu/wiki/Nagios-requirements.html Nagios test requirements]
* [https://wiki.egi.eu/wiki/mw-requirements.html Middleware requirements]
* [https://wiki.egi.eu/wiki/tool-requirements.html Tool requirements - coming soon]
* [[EGI Operations Surveys]]
* NEW! [[Jobs wordir and tempdir]]


=Standards=
{|
* Distributed Resource Management Application API Specification 1.0, DRMAA Working Group, [http://www.ogf.org/documents/GFD.133.pdf GWD-R.133]
|-
* GLUE Schema Specification [http://forge.gridforum.org/sf/docman/do/downloadDocument/projects.glue-wg/docman.root.background.specifications/doc14185 version 1.3], 2007
| [[Software Calendars|Software Calendars]]
* GLUE Specification [http://www.ogf.org/documents/GFD.147.pdf version 2.0], 2009 | [http://glue20.web.cern.ch/glue20/ HTML rendering]
| Support Calendar, Decommissioning Calendar, Operations Calendar
* [https://twiki.cern.ch/twiki/pub/LCG/WLCGCommonComputingReadinessChallenges/WLCG_GlueSchemaUsage-1.8.pdf Usage of Glue Schema v1.3 for WLCG Installed Capacity information]
|-
| [[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)
|}
 
= External resources  =
 
*[https://twiki.cern.ch/twiki/bin/view/LCG/WLCGBaselineVersions Baseline versions of services and client tools for WLCG]
 
[[Category:Middleware]]

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