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.
Search results
Jump to navigation
Jump to search
Page title matches
- * Service name: UMD Software provisioning infrastructure ...re provisioning infrastructure provides the technical tools to support the UMD release process from pulling packages from the developers repositories to t4 KB (642 words) - 15:47, 6 June 2016
- #REDIRECT [[EGI Core activities:2015-bidding UMD infrastructure]]65 bytes (7 words) - 15:47, 6 June 2016
Page text matches
- #REDIRECT [[EGI Core activities:2015-bidding UMD infrastructure]]65 bytes (7 words) - 15:47, 6 June 2016
- EGI’s commitment through EGI.eu is to coordinate a federated compute and data infrastructure to support diverse research communities across Europe and their internation *[[2016-bidding/UMD CMD quality assurance|UMD and CMD quality assurance]]7 KB (868 words) - 09:54, 24 June 2021
- The EGI SVG and CSIRT have looked at the advisory and think for the EGI infrastructure On behalf of the EGI SVG, CSIRT and the UMD release team,1 KB (163 words) - 10:33, 1 April 2015
- ...h GRID Storage Elements is necessary to access them, so the requirement of UMD on VM (see below). A setup centralized installations of CORSIKA and OFFLINE * additional packages: UMD packages, CVMFS|1 KB (151 words) - 16:23, 25 May 2015
- ...able to the community before UMD verification/integration ('''no QA, just “UMD” community repository''') == UMD release ==3 KB (419 words) - 16:36, 11 January 2016
- ...onents within it. Minor releases within a major series (i.e. UMD 1.0.x and UMD 1.1.y) may introduce new functionality but existing interfaces and behaviou ...then that given Product is in danger of not being included in the planned UMD release and will be shipped later.24 KB (3,040 words) - 14:48, 7 June 2021
- ...page reports the main information about the products currently released in UMD: *UMD-2 : 3.3.029 KB (4,324 words) - 14:11, 10 April 2017
- StoRM 1.11.1 was released in UMD-3. StoRM 1.8.3 security support ends on July 15 2013. ...mplete and successful process of staged rollout for a version of StoRM for UMD-3.15 KB (2,164 words) - 19:57, 7 May 2015
- == 1.2 UMD release == ....0 released on 09.12.2014''' : http://repository.egi.eu/2014/12/09/release-umd-3-10-0/10 KB (1,544 words) - 15:22, 12 January 2015
- === Task JRA1.1 Authentication and Authorisation Infrastructure === * Ongoing integration in UMD of rOCCI and Keystone-VOMS8 KB (1,115 words) - 15:53, 1 September 2015
- == UMD/CMD == ** in parallel, UMD team will test upgrading the umd-release package from UMD3/SL6 to UMD4/SL6 to make usre everything works pro17 KB (2,469 words) - 15:04, 12 February 2018
- Technology Providers (TP) that release products for UMD provide, for each product: ...ducts]] to compare the presence of the different products in the different UMD releases. <br> ''28 KB (4,038 words) - 10:12, 8 October 2021
- **Exploring potential use case with Bioinformatics Infrastructure for Life Sciences === Task JRA1.1 Authentication and Authorisation Infrastructure ===8 KB (1,171 words) - 11:24, 29 July 2015
- ** Research Infrastructure session: call with RICH project, agreement about agenda, discussion about s === Task JRA1.1 Authentication and Authorisation Infrastructure ===12 KB (1,607 words) - 15:32, 26 October 2015
- ...dures for the operational services that are integrated into the production infrastructure. ...s function includes administrative and reporting functions of the helpdesk infrastructure (e.g. collecting ticket statistics, internal and external reporting of stat45 KB (6,684 words) - 16:17, 6 January 2015
- *the eef-members list which is hosted for the European E-infrastructure Forum ...g from resolution of problems with the intranet services, through managing UMD software releases, upto tracking progress of project tasks and formal deliv21 KB (3,243 words) - 16:04, 6 February 2020