applied models changes
This commit is contained in:
@@ -21,6 +21,10 @@ For each instance of a computing component we can specify :
|
||||
- **arguments**, which will be passed to the entrypoint
|
||||
- **Environment variables**
|
||||
|
||||
The fields **input** and **output** list the different links coming in and out of the computing components.
|
||||
> [!] This is redundant with the Links object that we create when parsing the XML in oc-scheduler, might be better to remove them if proved redundant
|
||||
|
||||
|
||||
## Datacenter
|
||||
|
||||
A datacenter is identified by its **DC acronym** which is a very short form of its name.
|
||||
|
||||
5
docs/identified_problems.md
Normal file
5
docs/identified_problems.md
Normal file
@@ -0,0 +1,5 @@
|
||||
# Code
|
||||
|
||||
- [ ] In most of the components from 'models/' we have a method to add input and output to the model, however this linking of components is already done in oc-schedule when parsing the MxGraph. We need to determine if adding relations between components inside the objects themself is necessary.
|
||||
- When running in debug mode with a breakpoint inside the first line of computing.addLink it is only called once
|
||||
- [ ]
|
||||
Reference in New Issue
Block a user