Difference between revisions of "VT EGI Pay-for-Use Actions"
Jump to navigation Jump to search
|Line 3:||Line 3:|
*/01 - DM: Add GOCDB extensions to separate Grid and Cloud storage and suggesting a name, so that each provider and insert the prices to each.
*13/- RR: Submit BDII/FedCloud Requirement from P4U.
*13/- DS/DM/RR: Agree that most info will end up in e-Grant, discuss offline and circulate a proposal for where information will be hosted and how.
*13/- SH: Update wikipage with processes (using presentation diagram) so we can start to describe the current process and identify gaps.
*13/- RPs: Enter e-GRANT at least once prior to next meeting.
*13/- RR: Circulate mail when e-GRANT is ready for RP testing.
*13/- RP: Test e-GRANT once prompted by RR – Ref. 13/06.
*13/- SH: Send Engineering EGI RP response to technical requirements.
*13/- SH: Turn technical requirements spreadsheet into a general information sheet using Engineering and Helix Nebula as a starting point for comments.
*13/- RPs: Fill-in and/or comment on general technical requirements spreadsheet – Ref. 13/09.
*13/- SH: Circulate Google Doc with instructions for collecting NA5.2 contributions.
*13/- SH: Circulate a Doodle for 17 or 18 Nov.
Revision as of 17:04, 12 November 2014
|Pay-For-Use menu:||Home •||Processes/Instructions •||Service/Price Overview •||Service Management •||Legal/Policy •||Actions •||Meetings •|
- 13/01 - DM: Add GOCDB extensions to separate Grid and Cloud storage and suggesting a name, so that each provider and insert the prices to each.
- 13/02 - RR: Submit BDII/FedCloud Requirement from P4U.
- 13/03 - DS/DM/RR: Agree that most info will end up in e-Grant, discuss offline and circulate a proposal for where information will be hosted and how.
- 13/04 - SH: Update wikipage with processes (using presentation diagram) so we can start to describe the current process and identify gaps.
- 13/05 - RPs: Enter e-GRANT at least once prior to next meeting.
- 13/06 - RR: Circulate mail when e-GRANT is ready for RP testing.
- 13/07 - RP: Test e-GRANT once prompted by RR – Ref. 13/06.
- 13/08 - SH: Send Engineering EGI RP response to technical requirements.
- 13/09 - SH: Turn technical requirements spreadsheet into a general information sheet using Engineering and Helix Nebula as a starting point for comments.
- 13/10 - RPs: Fill-in and/or comment on general technical requirements spreadsheet – Ref. 13/09.
- 13/11 - SH: Circulate Google Doc with instructions for collecting NA5.2 contributions.
- 13/12 - SH: Circulate a Doodle for 17 or 18 Nov.
- 11/08 - PO: Check to see if a sample contract could be provided for EGI to tailor.
- JI/LA: To follow up on
- 11/09 - SH: Check with FedSM for underpinning contract template.
- SH: I sent a request, following a series of project activities, templates are back up the priority list, but may not be available by end of PoC.
- 10/03 - RCs: Publish storage pricing information in GOCDB.
- Ref. 13/01
- 10/06 - TS/PoC: Review pricing schemes and comment on feasibility and initial pricing schemes to start with.
- 10/07 - DS: Review Master Service Agreement when available for applicability for EGI Marketplace.
- 10/08 - RCs: Hold internal discussions and provide updates as part of a roundtable during PoC calls.
- SH: Input to be provided as part of EGI-InSPIRE Periodic Report and/or PoC Final Report – to be collected now.
- 11/01 - SH: Circulate first draft of overview and business model/pricing presentation.
- 11/02 - SH: Circulate outline of technical points to cover.
- 11/03 - DS: Coordinate slides with technical reps and circulate slides for comments.
- 11/04 - VS: Contact David Foster regarding procurement for presentation input.
- 11/05 - JJ: Prepare draft slide deck for RC feedback.
- 11/06 - RCs: Provide individual input to legal and policy slides circulated by JJ.
- 11/07 - DS: Write the FedCloud or recuperate from emails the different cloud “flavors” and circulate.
- 11/10 - SH: Forward Charity Engine Broker agreement to PoC list.
- 11/11 - SA: Provide a summary of agreements required for HNX.
- 11/12 - SH: Set up WebEx for 19 Sept at 10:00 CEST call TBC.
- 10/01 - SH: Circulate link to the Pay-for-Use Proof of Concept - Report of Phase 1.
- 10/04 - Tool Dev: Review the HNX SCR and tailor it according to EGI pay-for-use requirements.
- 10/05 - DB/SH: Prepare a draft SLA and circulate for comments *10/02 - SP/JG: Extract list of sites publishing storage pricing information and circulate to the list.
- 10/10 - PoC: Confirm physical presence at EGI Sept Workshop.
- 10/11 - NA5.2: Provide a summary of activities carried out for May, June and July by 31 July 2014.
- 10/09 - SH: Structure presentations in Indico and confirm speakers.
- 10/12 - SH: Complete the Doodle poll for post proposal call deadline.
- 07/01 - VS: Review Cloud for Europe PCP tender info and provide initial feedback.
- 07/02 - JG/SP: Add GOCDB storage extension based on proposed unit/time.
- 07/03 - DS: Review business processes and label UP (User Portal) and TDR (Tool Development Roadmap).
- 07/04 - All: Provide ideas/input for the 30’ discussion part of the pay-for-use session at the EGI CF’14.
- 07/05 - SH: Complete the Doodle poll for post EGI CF’14.
- 06/01 - SH: Follow-up for technical presentation speaker for EGI CF’14 pay-for-use session.
- 06/02 - SH: Circulate details of the FitSM training at EGICF’14.
- 06/03 - RCs: Review ESA documents for procurement participation and tender requirements.
- 06/04 - All: Complete the Doodle poll.
- 05/01 - MS: Follow-up to see why PL-Grid site(s) not publishing pricing information.
- 05/02 - MS/DS: Kick-start discussions around pay-for-use within eGRANT.
- 05/03 - SH: Ask MK or PS what VOMS server could be used to create a VO for each contract that is created within the pay-for-use context.
- 05/04 - SH: Refine business scenario based on discussions and allocate sections for feedback.
- 05/05 - All: Complete allocated sections prior to next call.
- 05/06 - SH: Send EGI CF’14 pay-for-use session structure for comments/feedback
- 05/07 - SH: Add PoC wikipage link to the main page.
- 05/08 - SH: Circulate WebEx call-in details for 24 April @ 10:00.
- 04/01 - JG: Circulate details on storage info to be provided (e.g. units).
- 04/02 - SH: Finalize table prioritizing user stories for feedback offline.
- 04/03 - SH: Create Google Doc for collating information around agreed topics for allocation.
- 04/04 - SH: Circulate WebEx call-in details for 28 March @ 10:00.
- 03/01 - JG: Circulate an updated list of remaining sites to provide info in GOCDB (ref. extensions).
- 03/02 - RCs: Remaining sites to provide info in GOCDB (ref. extensions).
- 03/03 - RCs: DPM or dCache sites to provide pricing info for storage as initial work.
- 03/04 - JG: Add separate VAT column in GOCDB.
- 03/05 - SH: Add separate VAT column in wiki.
- 03/06 - SH: Add service and supporting activity definitions in the SM page on the wiki.
- 03/07 - SH: Circulate a WebEx call-in details for 14 March @ 10:00.
- 02/01 - ALL: Review Open Data Pilot info and provide feedback both positive and negative.
- 02/02 - JG/AS: Add storage pricing fields in GOCDB and AP.
- 02/03 - JG: Look at the GOCDB extensions required and circulate details for comments.
- 02/04 - SH: Add cloud pricing and storage columns to wikipage.
- 02/05 - ALL: Each member of the PoC to provide 3-4 questions (either by mail or directly on the wiki) they would like to have answered to develop activities around.
- 02/06 - SH: Get wikipage editing rights for group members.
- 02/07 - DS: Confirm alternate contact for tool development.
- 02/08 - ALL: Confirm alternate email addresses for Google docs.
- 02/09 - ALL: Confirm topics of interest for participation by mail or directly on the wiki.
- 02/10 - SH: Send mail to collect institution contacts for EGI-InSPIRE PPT (TNA5.2).
- 02/11 - ID: Check “custom” for by VO view.
- 02/12 - SH: Prepare a message to NGIs for providing pricing (To be discussed during next call as this needs to be sent post-development).
- 02/13 - SH: Circulate a Doodle poll for next call on Feb 26 or 28.
- 01/01 - RCs: All Resource Centres to follow instructions for adding prices into accounting system.
- 01/02 - RCs: Provide information for completing the Technical Details Table.
- 01/03 - SH: Add HEPSPEC06 reference to price column in technical detail table.
- 01/04 - AS: Investigate the option of adding price/cost per user.
- 01/05 - SH: Revise objectives to expand references to the various tools that may be required.
- 01/06 - SH: Add responsibility table to wiki.
- 01/07 - SH: Revise output to clarify running proof of concept in pre-production.
- 01/08 - ALL: Provide contact details of anyone to be added to mailing list.
- 01/09 - SH/ALL: Confirm preference of 11:00 or 12:00 Thursdays and double check other meetings.