Skip to content

Commit 9e4ca75

Browse files
author
Manuel Perez Belmonte
committed
Added model definition and cost model example
1 parent bf5aa73 commit 9e4ca75

File tree

1 file changed

+12
-2
lines changed

1 file changed

+12
-2
lines changed

docs/index.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,17 @@ For now, the 0.0.2 version is using Mock up values to simmulate the interaction
6161
![ElasTest Cost Engine Mock up architecture](imgs/MockECE.png)
6262

6363
The Cost Models are defined in a generic way so can be adapted to several cases from VM orchestrations, Service
64-
instantiations and Services that contain VM orchestration as part of them. The used format is the following:
64+
instantiations and Services that contain VM orchestration as part of them. The data model used is the following:
65+
66+
- `name` : Name of the Cost Model.
67+
- `type` : Cost Model type.
68+
- `fix_cost` : Map containing the keys and values of the fields that need to be accounted in a fix bases.
69+
- `var_rate` : Map containing the keys and values of the fields that need to be accounted under a pay as you go premises.
70+
- `components` : Map containing the links to another Cost Models.
71+
- `description` : Description of the Cost Model.
72+
73+
74+
An example of a Cost Model definition could be as the following:
6575

6676
```
6777
{
@@ -77,7 +87,7 @@ instantiations and Services that contain VM orchestration as part of them. The u
7787
"gb_hhd" : 0.0775
7888
},
7989
"components":{
80-
"id" : "CostModelYId"
90+
"Services" : ["CostModelYId"]
8191
},
8292
"description" : "On demand provisioning of a VM. Includes as a component a package X accounted by the Cost Model Y"
8393
}

0 commit comments

Comments
 (0)