Difference between revisions of "Common-accounting-model ABANDONED"
(→Service) |
(→Execution) |
||
Line 19: | Line 19: | ||
=== Execution === | === Execution === | ||
− | + | This specification will be used to take into account information about services running jobs on the infrastructure (Workflow Engine, Execution Engine, Statistical Manager, Aquamaps). | |
− | + | For this resource type, there are two sub-types: | |
− | + | ||
− | + | ||
− | + | ||
− | + | ==== Job ==== | |
− | + | Contains the information about the overall job, that will be partitioned in N Tasks. | |
− | + | ||
+ | Specific Job properties: | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
* jobId : an unique identifier for the job | * jobId : an unique identifier for the job | ||
+ | * jobQualifier : qualifies the job in terms of algorithm type or job type (e.g. search, data-transformation, etc) | ||
* jobName : name of the job | * jobName : name of the job | ||
* jobStart : the instant the job start running | * jobStart : the instant the job start running | ||
* jobEnd : the instant the job ends its execution | * jobEnd : the instant the job ends its execution | ||
* jobStatus: completed/failed | * jobStatus: completed/failed | ||
+ | * vmsUsed : number of the VMs (gHNs) used by the job. | ||
* wallDuration : duration between the instant the job start running and the instant the job ends its execution. | * wallDuration : duration between the instant the job start running and the instant the job ends its execution. | ||
− | |||
− | |||
− | |||
− | Specific | + | ==== Task ==== |
+ | Contains the information about one slice of the overall Job. | ||
+ | |||
+ | Specific Task properties: | ||
− | * refHost : hostname of the | + | * jobId : reference to the Job that generated this Task |
− | * refVM : | + | * refHost : hostname of the virtual machine (gHN) |
− | * usageStart : the earlier usage time of the | + | * refVM : virtual machine id (gHN) |
− | * usageEnd: the latest usage time of the | + | * usageStart : the earlier usage time of the Task |
+ | * usageEnd: the latest usage time of the Task | ||
* usagePhase: completed/failed | * usagePhase: completed/failed | ||
− | * inputFilesNumber : number of input files to the | + | * inputFilesNumber : number of input files to the Task |
− | * inputFilesSize : dimension of input files to the | + | * inputFilesSize : dimension of input files to the Task |
− | * outputFilesNumber : number of output files from the | + | * outputFilesNumber : number of output files from the Task |
− | * outputFilesSize : dimension of output files from the | + | * outputFilesSize : dimension of output files from the Task |
− | * overallNetworkIn : overhead of the input traffic over the network to the | + | * overallNetworkIn : overhead of the input traffic over the network to the Task |
− | * overallNetworkOut : overhead of the output traffic over the network from the | + | * overallNetworkOut : overhead of the output traffic over the network from the Task |
+ | * cores : number of cores per Task. | ||
+ | * processors : number of processors per Task. | ||
=== Service === | === Service === |
Revision as of 13:32, 24 May 2013
Contents
Scope
This library contains the definition of the resource accounting record.
Data-model
The structure of a generic accounting record (Usage Record, UR) will be composed of a set of common fields for all resource types, in particular:
- id : an unique identifier for the UR
- consumerId : the user actually consuming the resource (optional, for future purposes)
- createTime : when the UR was created
- startTime, endTime : the time window the UR refers to
- resourceType : the type of resource the UR tracks
- scope : the scope of the resource
- resourceOwner : who owns the resource and/or who creates the UR
Furthermore, for each UR there will be a section to be filled with the specific properties per resource type (key-value pairs).
Resource Types
The resource types we've identified are: Execution, Service, Data-access and Storage.
Execution
This specification will be used to take into account information about services running jobs on the infrastructure (Workflow Engine, Execution Engine, Statistical Manager, Aquamaps).
For this resource type, there are two sub-types:
Job
Contains the information about the overall job, that will be partitioned in N Tasks.
Specific Job properties:
- jobId : an unique identifier for the job
- jobQualifier : qualifies the job in terms of algorithm type or job type (e.g. search, data-transformation, etc)
- jobName : name of the job
- jobStart : the instant the job start running
- jobEnd : the instant the job ends its execution
- jobStatus: completed/failed
- vmsUsed : number of the VMs (gHNs) used by the job.
- wallDuration : duration between the instant the job start running and the instant the job ends its execution.
Task
Contains the information about one slice of the overall Job.
Specific Task properties:
- jobId : reference to the Job that generated this Task
- refHost : hostname of the virtual machine (gHN)
- refVM : virtual machine id (gHN)
- usageStart : the earlier usage time of the Task
- usageEnd: the latest usage time of the Task
- usagePhase: completed/failed
- inputFilesNumber : number of input files to the Task
- inputFilesSize : dimension of input files to the Task
- outputFilesNumber : number of output files from the Task
- outputFilesSize : dimension of output files from the Task
- overallNetworkIn : overhead of the input traffic over the network to the Task
- overallNetworkOut : overhead of the output traffic over the network from the Task
- cores : number of cores per Task.
- processors : number of processors per Task.
Service
This specification will be used to take into account information about the services invocations.
Specific service attributes
- callerIP : IP address that originated the service call
- invocationCount : number of invocations (aggregated information)
- averageInvocationTime : average invocation time (aggregated information)
- serviceClass : name of the service class
- serviceName : name of the service
Data-access
Specific Data-access properties:
- sourceId: the identifier of the Tree Manager source which is the target of a read/write operation
- operation : the name of the read/write operation performed via the Tree Manager over a given source
- treeId : the identfier of a tree within the data source which is the target of a given read/write operation performed via the Tree Manager
- treeCount : the number of trees within the data source which are accessed/written as the result of a given read/write operation performed via the Tree Manager
Storage
This model specification will be used to take into account storage resources and timeseries/services using DBs backend.
Specific storage attributes:
- operationType : GET, PUT, UPDATE, DELETE
- targetResource : URI representing the storage resource
- fileDimension : dimension of the storage resource
- hostname: hostname of the host where the storage library is invoked