Difference between revisions of "24.05.2013 Accounting model and portlet requirements"

From D4Science Wiki
Jump to: navigation, search
(Created page with "==== Details ==== *Description: Meeting notes on Resource Accounting *Date: 24-May-2013 from 10:00 to 12:15 *Topics: Resource accounting model *Participants: Andrea Manzi (CER...")
 
Line 5: Line 5:
 
*Topics: Resource accounting model  
 
*Topics: Resource accounting model  
 
*Participants: Andrea Manzi (CERN), Ermanno Travaglino (ENG), Pasquale Pagano (CNR), Luigi Fortunati (CNR).
 
*Participants: Andrea Manzi (CERN), Ermanno Travaglino (ENG), Pasquale Pagano (CNR), Luigi Fortunati (CNR).
 +
 +
== Resource Accounting Model ==
 +
 +
 +
* objective of the model : make possible the accounting for the single user and having the possibility to understand trends
 +
 +
=== Job Execution  ===
 +
 +
we should include the requirements of other services running job on the infrastructure Aquamaps/Statistical Manager and in case adapt the model
 +
 +
instead of plan/ExecutionEngine we should put Job/task
 +
 +
we have to remove any reference to specific Service
 +
 +
to add jobId in the Execution Engine.( task)
 +
 +
move the n core, n cpu at Task level
 +
 +
we need to have a new record to be publihsed by the portal in order to map the user with the job it
 +
 +
 +
=== Service ===
 +
 +
the model is fine as it is now.
 +
 +
=== Data Access ===
 +
 +
 +
we should include also SPD ( not only Tree Manager), but we should think about also the Geonetwork access
 +
 +
we should calculate the quantity of data accessed in terms of kb.
 +
 +
we should include the type of data accessed ( geo/biodiversity)
 +
 +
we don't need a record for data transfer (it's a combination of data access and Storage records)
 +
 +
 +
== Storage ==
 +
 +
we should use the same model also for the timeseries/services using DBs backend
 +
 +
we have to include also the UPDATE operation
 +
 +
there is also the need to have a summary of the storage used for each user/service, to be filled service side periodically. a new type should be used for this ( summary)
 +
 +
it should be generalized ( serviceclass/servicename => consumerId)

Revision as of 11:18, 24 May 2013

Details

  • Description: Meeting notes on Resource Accounting
  • Date: 24-May-2013 from 10:00 to 12:15
  • Topics: Resource accounting model
  • Participants: Andrea Manzi (CERN), Ermanno Travaglino (ENG), Pasquale Pagano (CNR), Luigi Fortunati (CNR).

Resource Accounting Model

  • objective of the model : make possible the accounting for the single user and having the possibility to understand trends

Job Execution

we should include the requirements of other services running job on the infrastructure Aquamaps/Statistical Manager and in case adapt the model

instead of plan/ExecutionEngine we should put Job/task

we have to remove any reference to specific Service

to add jobId in the Execution Engine.( task)

move the n core, n cpu at Task level

we need to have a new record to be publihsed by the portal in order to map the user with the job it


Service

the model is fine as it is now.

Data Access

we should include also SPD ( not only Tree Manager), but we should think about also the Geonetwork access

we should calculate the quantity of data accessed in terms of kb.

we should include the type of data accessed ( geo/biodiversity)

we don't need a record for data transfer (it's a combination of data access and Storage records)


Storage

we should use the same model also for the timeseries/services using DBs backend

we have to include also the UPDATE operation

there is also the need to have a summary of the storage used for each user/service, to be filled service side periodically. a new type should be used for this ( summary)

it should be generalized ( serviceclass/servicename => consumerId)

Retrieved from "https://wiki.d4science.org/index.php?title=24.05.2013_Accounting_model_and_portlet_requirements&oldid=12573"