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
- ...order-right:1px solid #aaa;" | [[Fedcloud-tf:WorkGroups:Scenario1|Scenario 1<br>VM Management]] | style="border-right:1px solid #aaa;" | [[Fedcloud-tf:WorkGroups:Scenario2|Scenario 2<br>Data Management]]1 KB (154 words) - 12:15, 17 April 2015
- = [Closed] Scenario 6: VM/Resource state change notification = The scenario enables:4 KB (528 words) - 10:26, 20 April 2015
- ...ps://documents.egi.eu/public/ShowDocument?docid=1677 DCH-RP Deliverable D3.1]; '''Scenario 1.3:'''4 KB (545 words) - 09:29, 14 August 2013
- ...“Assign to ROC/NGI” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the Hel ...g the “Notify SITE” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the Hel6 KB (999 words) - 16:36, 25 March 2019
- {| cellspacing="0" cellpadding="5" border="1" | 1 end-point8 KB (1,175 words) - 13:47, 13 September 2019
- Image:b2share-b2safe.png|B2SHARE and B2SAFE scenario Image:nds2-b2safe.png|NDS2 GUI client and B2SAFE scenario4 KB (597 words) - 15:36, 4 March 2014
- The UNICORE TSI service [R 1] was found to be vulnerable to a command injection attack by an This is most serious in the deployment scenario where UNICORE/X and TSI are on same host as it4 KB (566 words) - 17:37, 31 March 2015
- ...Scenarios 1 and 2 (coming from DCH-RP Deliverable D3.1) as follows in PoC 1: For Scenario 1, we should like to do the following: check the integrity/audit the data tha9 KB (1,412 words) - 13:55, 24 September 2013
- In the worst case scenario this may allow a user or someone with a stolen certificate to submit See [R 1]2 KB (245 words) - 11:51, 13 October 2015
- ...n tool, workflow, service, etc. was assessed as part of a Proof of Concept scenario. These scenarios are managed and tested using the workpackage's [http://go ...ill report on a specific component (tool, service, etc.) that is used in a scenario, and the aspects for which it was assessed. The assessed component will be3 KB (503 words) - 22:50, 9 August 2013
- ...rect link] [https://www.egi.eu/indico/getFile.py/access?resId=0&materialId=1&confId=488 EVO details] [https://www.egi.eu/indico/conferenceDisplay.py?con === 1. Middleware releases and staged rollout ===5 KB (697 words) - 12:36, 15 October 2012
- ...and one or more collaborators are chosen among the Task Force members. The scenario evaluation performed by each work group is recorded in [[Fedcloud-tf:WorkGr ...that an EGI cloud infrastructure should have in order to support the given scenario;12 KB (1,632 words) - 17:32, 24 October 2016
- See [R 1] [R 2] and [R 3] ...ember of our team looked at the patch and the vulnerability and the attack scenario would be:3 KB (377 words) - 12:04, 5 June 2015
- | 1 | 1 or more working days9 KB (1,376 words) - 18:30, 3 January 2022
- This is described in OpenStack Security Notice 0074 [R 1] in [R 1]3 KB (519 words) - 16:08, 11 January 2017
- ! style="text-align: left;" | 1. Evaluate SCAPE preservation tools ! style="text-align: left;" | 4. Re-run experiment for Scenario 1.1 & 1.42 KB (271 words) - 14:37, 31 March 2014
- ===Use case #1=== ('''Note:''' Sorry, I didn't understood if the following scenario is completly absorbed in the GOCDB Regionalisation Plans. Therefore, I stat3 KB (485 words) - 14:21, 28 April 2015
- | 1 | 1 or more working days7 KB (954 words) - 10:39, 10 November 2020
- 1. Service Maintenance/Availability: * Development of a recommended Argus server deployment scenario in the NGIs, RCs2 KB (339 words) - 13:54, 11 June 2013
- === User Step 1: User Login/Register into Portal === 1. The entry page of Portal:3 KB (457 words) - 15:03, 2 February 2015