Overview of Funded Virtual Team projects
This page is under construction as of 15 March 2013. It is intended to be a repository for information on EGI's funded mini-projects that are being progressed under the established Virtual Team framework. Owner of this page is Michel Drescher - Michel.Drescher@egi.eu.
- For background information on Virtual Teams please read the introduction to the Virtual Team framework.
- For the list of NGI International Liaisons please go to http://www.egi.eu/about/ngis/NILs.html.
In June 2012, the EGI Council endorsed the EGI strategy ‘Seeking new horizons: EGI’s role in 2020’ (see http://go.egi.eu/EGI2020) as a framework for the future developments of the EGI Community. As a result of this report, the EGI-InSPIRE PMB sought suggestions from within the EGI-InSPIRE consortium for activities that could be undertaken during PY4 of the EGI-InSPIRE project to accelerate the objectives identified in the EGI strategy of:
- Undertaking Coordination and Community Building across the EGI Community and its stakeholders.
- Maintaining and expanding the Operational Infrastructure and its management tools to support other Research Infrastructures and Cloud Technologies.
- Enabling the deployment of domain specific and centrally provisioned Virtual Research Environments.
As a result, over 30 suggestions were received and following an assessment undertaken by the EGI-InSPIRE PMB and the AMB, 11 activities were prioritised for implementation. These will accelerate EGI’s strategic goals by investing in tools to build and educate communities, to integrate and effectively use federated clouds, and to provide enhanced operational tools for virtual organisations, a new approach to computing availability and reliability, enhancements to EGI’s service registry to support other projects and infrastructures, and tools for automating resource allocation. Together, these activities will reduce the barriers for researchers to access the resources that they need wherever they may be located. The activities translate into the mini-projects tabled beneath. Summaries of the activities and the motivations behind each of them can be found in the associated wiki pages (managed by the respective project leaders).
Reporting & management
All active EGI mini projects are aggregated under the newly formed EGI-InSPIRE Work Package 8 (SA4); each mini project has a Task number assigned within this work package as indicated in the following section.
An overview, and "roster" of mini project members are maintained at http://go.egi.eu/Funded-VTs. From this spreadsheet, individuals are added and removed to PPT, EGI SSO groups etc.
WP8 will report weekly to the EGI-InSPIRE Activity Management Board, which is meeting weekly every Wednesday morning. Therefore, WP8 management seeks to collect weekly reports from every mini projects every Tuesday afternoon until CoB (close of business). Note that this does not mean that you have to change your planning to weekly cycles, if you chose to plan, e.g. in 2-week sprints.
When reporting, please indicate:
- Which Task, including Task name, e.g. "TSA4.8 CloudCaps"
- Reporting period (start date and end date), e.g. "Mon 1 Apr - Tue Tue 23 Apr".
- Progress on things you work on
- Problems you encounter, but can solve
- Problems and issues you need our help with.
If your plans differ from the examples, or do not align with the weekly AMB schedule, that is okay, but please, be consistent: Whether you report on calendar weeks (using week numbers, actual dates, span more than one week) is okay for as long as you choose one schematic and stick to it. If you choose to report bi-weekly (i.e. twice a month), that is also okay, but I will mark this accordingly in the aggregated AMB report.
Please send your reports to the ML email@example.com.
To report your efforts for financial administration, the EGI-InSPIRE project uses PPT. Please record your individual funded mini project effort at the end of every month and have your supervisor approve your PPT timesheets.
- Use PPT to report your funded effort (unfunded effort need not be recorded) - https://pptevm.cern.ch/egi/ui/main.do
- EGI SSO is used to manage access to tools such as PPT, Wiki, DocDB, etc. - https://www.egi.eu/sso
- Meeting planner
- EGI provides an Indico instance for planning meetings and recording agendas and minutes. A mini project section has bee set up - Indico section for mini projects
- The EGI Wiki provides an area for mini projects to document their charter and other material - Funded Virtual Teams Wiki
- Document database
- EGI provides a document database. Mini project teams should store their deliverables etc in DocDB, using the "WP8" tag - WP8 documents in DocDB
- Mailing lists
- There are two mailing lists used for the mini projects: (a) the Leaders & Shepherds list, firstname.lastname@example.org, and (b) the mini projects member list, email@example.com..
Active EGI mini-projects
All started in April 2013. The respective Tasks and Task Leaders are responsible for maintaining the subsequent mini project pages.
|Project title||Project leader||EGI.eu technical shepherd||Project website|
|Template Team page||VT Template Wiki page All Projects are asked to use this where possible.|
|TSA4.2: Massive Open Online Course Development||Jan Bot <firstname.lastname@example.org>||Gergely Sipos||VT MOOC|
|TSA4.3: Evaluation of Liferay modules||Gergely Sipos <email@example.com>||Gergely Sipos||VT Liferay|
|TSA4.4: Providing OCCI support for arbitrary Cloud Management Frameworks||Boris Parak <firstname.lastname@example.org>||Michel Drescher||VT OCCI for CMF|
|TSA4.5: CDMI Support in Cloud Management Frameworks||Ilja Livenson <email@example.com>||Michel Drescher||VT CDMI in CMF|
|TSA4.6: Dynamic Deployments for OCCI Compliant Clouds||Marc-Elian Bégin <firstname.lastname@example.org>||Michel Drescher||VT OCCI CompCloud|
|TSA4.7: Automatic Deployment and Execution of Applications using Cloud Services.||Enol Fernández <email@example.com>||Michel Drescher||VT AppDeployment|
|TSA4.8: Transforming Scientific Research Platforms to Exploit Cloud Capacity||Björn Hagemeier <firstname.lastname@example.org>||Michel Drescher||VT CloudCaps|
|TSA4.9: VO Administration and operations PORtal (VAPOR)||Franck Michel <email@example.com>||Diego Scardaci||VT VAPOR|
|TSA4.10: A new approach to Computing Availability and Reliability Reports||Christos Kanellopoulos <firstname.lastname@example.org>||Tiziana Ferrari||VT Comp Reports|
|TSA4.11: GOCDB Scoping Extensions and Management Interface||David Meredith <email@example.com>||Diego Scardaci||VT GOCDBExt|
|TSA4.12: Tools for automating applying for and allocating federated resources||Tomasz Szepieniec <firstname.lastname@example.org>||Tiziana Ferrari||VT Resource Allocation Tools|