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
- ...iki page provides a collated, tabular overview of issues and their planned release as communicated by the relevant technology provider. ! Component1 KB (174 words) - 19:25, 9 January 2015
- #REDIRECT [[EGI-InSPIRE:Component Issues Release Schedule]]59 bytes (6 words) - 19:24, 9 January 2015
Page text matches
- #REDIRECT [[EGI-InSPIRE:Component Issues Release Schedule]]59 bytes (6 words) - 19:24, 9 January 2015
- ...is '''not reassigned''' to another support unit. On the other hand, tough issues when DMSU expertise runs out should be still reassigned. ...and 3rd support action is needed, the ticket is cloned (one new ticket per component), and the clones are linked appropriately with the original.5 KB (809 words) - 16:19, 12 December 2014
- === 1.1 EMI-1 release status (Cristina) === **MyProxy (proxyrenewal) update: first release in UMD1.06 KB (816 words) - 18:09, 29 November 2012
- The release schedule of UMD containing the candidate products for each release can be found here [[UMD_Release_Schedule]] ...es from '''InVerification''' to '''StageRollOut''', this means that the SW component as passed the verification process, i.e. was '''ACCEPTED''' in the verifica9 KB (1,499 words) - 17:57, 10 December 2014
- ...ave a particular interest in, with the proviso that they may need to debug issues with a particular update and in any case should report their findings. Such The release schedule of UMD containing the candidate products for each release can be found here [[UMD_Release_Schedule]]12 KB (1,986 words) - 15:17, 23 March 2016
- *through the gLite WMS component ...Workload Management System (WMS), the ICE (Interface to CREAM Environment) component of the WMS is used. To select the CREAM instances to which the job can be s7 KB (1,099 words) - 10:55, 14 May 2013
- ** schedule meeting with DRIHM: prospective use case * Schedule meeting on how EGI can monitor BioVeL services7 KB (953 words) - 23:01, 24 December 2014
- Michael Grønager: however, I have a few issues ...sed and to ensure a better GGUS representation in terms of spport units pr component4 KB (785 words) - 16:22, 12 December 2014
- ...MB, the aim is to implement this new SW provisioning process for the EMI 2 release by the end of April 2012. ...the UMD production repositories, a “base” repository with the initial UMD release and an “updates” repositories for the subsequent updates.17 KB (2,640 words) - 16:05, 16 October 2012
- === 1.1 EMI-1 release status (Cristina) === .../indico/materialDisplay.py?contribId=0&materialId=0&confId=495 EMI release schedule (PDF)]<br>12 KB (1,755 words) - 12:32, 15 October 2012
- * Payment schedule for PQ11 and PY3 agreed with PO and paid ...11/19/nederlandse-supertelescoop-lofar-vindt-eerste-pulsars-2/ LOFAR Press release] (in Dutch)12 KB (1,709 words) - 23:04, 24 December 2014
- * Payment schedule for PQ11 and PY3 closing costs prepared * MOOC progresses with assembling the course material, but has some issues with temporary grid certificates.12 KB (1,734 words) - 23:05, 24 December 2014