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
- 42 bytes (5 words) - 13:10, 8 June 2015
- 19 bytes (2 words) - 11:25, 5 June 2015
- Different technologies or approaches allow translating someone's federated identity to an X.509 credential. *[[Fedcloud-tf:WorkGroups:Federated AAI:per-user sub-proxy|Per-user sub-proxy]] is a mechanism where a robot certif395 bytes (55 words) - 11:36, 11 February 2015
- 6 KB (966 words) - 20:57, 28 February 2015
Page text matches
- | style="border-right:1px solid #aaa;" | [[Fedcloud-tf:WorkGroups:OpenIssues|'''Open issues<br>''']] | style="border-right:1px solid #aaa;" | [[Fedcloud-tf:WorkGroups:Scenario1|Scenario 1<br>VM Management]]1 KB (154 words) - 12:15, 17 April 2015
- For the technical implementations of this scenario, please go to [[Federated AAI Implementation]]. ...ers, as well as the specific settings for FCTF can be found at [[Federated AAI Integration Status]].2 KB (320 words) - 17:51, 5 May 2015
- This page deals with the implementation of the AAI scenario in the various services. For one, we need to look into each of the == [[Fedcloud-tf:WorkGroups:Scenario1|VM Management]] ==3 KB (480 words) - 12:13, 13 February 2013
- {{Fedcloud-tf:Menu}} {{Fedcloud-tf:WorkGroups:Menu}} {{TOC_right}} ...ollect and process (and certain conditions to that). This also affects the Federated Clouds Task Force since personal data (to some extent) is expected to be co1 KB (138 words) - 13:15, 6 February 2012
- Different technologies or approaches allow translating someone's federated identity to an X.509 credential. *[[Fedcloud-tf:WorkGroups:Federated AAI:per-user sub-proxy|Per-user sub-proxy]] is a mechanism where a robot certif395 bytes (55 words) - 11:36, 11 February 2015
- ...This will include integrating existing cloud infrastructures with the EGI Federated Cloud platform (e.g. the Canadian CANFAR infrastructure) and accelerated co #Expand the EGI federated Cloud platform with new IaaS capabilities;17 KB (2,439 words) - 14:24, 2 February 2017
- *identify and work with [[Federated Cloud user support|user communities]] willing to be early adopters of the t ...phases. During each phase, the Task Force evaluates a set of [[Fedcloud-tf:WorkGroups|scenarios]] that an EGI federation of clouds should support. The scenarios10 KB (1,518 words) - 12:22, 17 March 2016
- Before taking any decision about the requirements for a federated AAI, one needs to be sure what type of federation is desired. There are roughly The federated cloud systems are all the same for the user. He only interacts with a singl8 KB (1,229 words) - 13:17, 26 April 2013
- * Federated Cloud TF * participated in WLCG AAI on Storage meeting5 KB (714 words) - 18:20, 6 January 2015