Skip to content

Commit e32cc09

Browse files
Update index.md
1 parent 62a5f0b commit e32cc09

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

docs/index.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ When the ECE is started correctly, a basic UI will be exposed at http://localhos
3131
The 0.0.2 version of ECE initializes the databases and includes two different Cost Models as initial values. The T-Jobs are mocked up until the DSL is correctly defined.
3232

3333
The ECE UI offers the functionality to estimate the price of running a specified T-Job running under a Cost Model.
34-
![ElasTest Cost Engine Demo Interface v0.0.2](imgs/CostEngine002Demo.png)
34+
![ElasTest Cost Engine Demo Interface v0.0.2](imgs/CostEngine002Demo.png =480x640)
3535

3636
The ECE UI also ofers a simple way to manage all the Cost Models, creating, deleting and requesting for the json structure.
3737

@@ -52,9 +52,12 @@ ECE will be in contact with the following ElasTest services:
5252
- [The TORM](https://github.com/elastest/elastest-torm) will provide the T-Job details.
5353
- [The EMS](https://github.com/elastest/elastest-monitoring-service) will provide information about the running T-Jobs.
5454

55+
5556
![ElasTest Cost Engine final architecture](imgs/ECEArch.png)
5657

5758
For now, the 0.0.2 version is using Mock up values to simmulate the interaction with the rest of the ElasTest Components.
59+
60+
5861
![ElasTest Cost Engine Mock up architecture](imgs/MockECE.png)
5962

6063
The Cost Models are defined in a generic way so can be adapted to several cases from VM orchestrations, Service

0 commit comments

Comments
 (0)