Alert.png 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.

Difference between revisions of "VT EGI Pay-for-Use PoC Workplan"

From EGIWiki
Jump to navigation Jump to search
Line 16: Line 16:
*Technical  
*Technical  
**Review [https://wiki.egi.eu/wiki/EGI_Pay-for-Use_PoC_Technical_Details technical detail table] and complete with relevant information  
**Review [https://wiki.egi.eu/wiki/EGI_Pay-for-Use_PoC_Technical_Details technical detail table] and complete with relevant information  
**Associate prices within GOCDB  
**Associate prices within GOCDB according to instructions provided [https://wiki.egi.eu/wiki/EGI_Pay-for-Use_PoC_Technical_Details#Price_in_Accounting here]
**Accounting Portal to make required extraction from GOCDB and accounting for usage  
**Accounting Portal to make required extraction from GOCDB and accounting for usage
***Pull the site data and create a table for use in displaying charging. This table should be directly viewable, at least for the pilot.
***Create test cpu view like the cloud one.  Best to base it on the Custom_View so that we can select particular VOs relevant to the pilot.
**Investigate and implement a billing function (initially a virtual bill)  
**Investigate and implement a billing function (initially a virtual bill)  
**Perform a gap analysis of supporting services (either new or extensions to the current tools) that would enable the increased automation of the process once it has been manually established and subsequent development required for missing functionality.  
**Perform a gap analysis of supporting services (either new or extensions to the current tools) that would enable the increased automation of the process once it has been manually established and subsequent development required for missing functionality.  
Line 40: Line 42:
*TBD based on activities carried out. Dedicated F2F to be discussed either following EC review or other date TBD (e.g. Sept 2014).
*TBD based on activities carried out. Dedicated F2F to be discussed either following EC review or other date TBD (e.g. Sept 2014).


'''December 2014: Circulation/Publication of Final Proof of Concept Report'''
'''December 2014: Circulation/Publication of Final Proof of Concept Report'''  


*To be included in final EGI-InSPIRE Periodic Report (Lead: EGI.eu with requested contributions from PoC members)
*To be included in final EGI-InSPIRE Periodic Report (Lead: EGI.eu with requested contributions from PoC members)

Revision as of 10:25, 22 January 2014

Pay-For-Use menu: Home Processes/Instructions Service/Price Overview Service Management Legal/Policy Actions Meetings


List of overall workplan and activities agreed.

(To be developed)


January 2014: Kick-off of the activity

  • Hold first call - 23 Feb 2014 @ 12:00 CET (TBC)
  • Establish fixed day and time for semi-monthly calls

April 2014: First phase implementation of all technical specifications, list of required agreements and refinements to policy issues documented in the EGI Sustainability Plan (M48)

  • Technical
    • Review technical detail table and complete with relevant information
    • Associate prices within GOCDB according to instructions provided here
    • Accounting Portal to make required extraction from GOCDB and accounting for usage
      • Pull the site data and create a table for use in displaying charging. This table should be directly viewable, at least for the pilot.
      • Create test cpu view like the cloud one. Best to base it on the Custom_View so that we can select particular VOs relevant to the pilot.
    • Investigate and implement a billing function (initially a virtual bill)
    • Perform a gap analysis of supporting services (either new or extensions to the current tools) that would enable the increased automation of the process once it has been manually established and subsequent development required for missing functionality.
    • Report back on identified issues and overall progress (Lead: TBD)
  • Policy/Legal
    • Identify and evaluate legal, policy, and organisational issues around the full implementation of the pay-for-use model (review initial information from first survey)
    • Articulate appropriate business and responsibility models (review initial broker models developed)
    • Request potential consultation from FedSM regarding service management processes and agreements.
    • Collate information to be presented within Sustainability Plan that is easily digestible (Lead: EGI.eu)

May 2014: Pay-for-Use aspects included in Federated Cloud release (even in Beta/pre-production)

  • Identify members involved in the EGI Federated Cloud to serve as pay-for-use representatives
  • Gather requirements from the EGI FedCloud for its inclusion

June 2014: First presentation of activities and feedback from EGI-InSPIRE EC Review

  • PoC to decide what information to be presented and ultimate goal

October 2014: Conclusion of phase 2 activities: updates from feedback and overall refinements

  • TBD based on activities carried out. Dedicated F2F to be discussed either following EC review or other date TBD (e.g. Sept 2014).

December 2014: Circulation/Publication of Final Proof of Concept Report

  • To be included in final EGI-InSPIRE Periodic Report (Lead: EGI.eu with requested contributions from PoC members)