Decoupling kiso up from experiment.yml file

[philrhc]

Hello, I am building a tool on top of kiso which allows the user to generate experiment.yml files through a cartesian product of independent variables. One of those is the number of machines with the given label. I also have four different experiment types that I am using.

The result is a huge number of slices when all that I really want is to provision four of five slices of 50 nodes and then run many experiment.ymls against the slice.

[mayani]

The experiments field is an array of experiments. What prevents it from being suitable for your use case?

sites:
  # Slice 1 configuration

experiments:
  - # Experiment 1 - Variable A1, B1, ..
  - # Experiment 1 - Variable A2, B1, ..
  - # Experiment 1 - Variable A1, B2, ..
  - # Experiment 1 - Variable A2, B2, ..

  - # Setup / Cleanup for Experiment 2

  - # Experiment 2 - Variable A1, B1, ..

Another workaround/hack is to have multiple experiment files, but to run kiso commands with the same output dir.

kiso up --output out experiment-1.yml
kiso run --output out experiment-1.yml
kiso run --output out --force experiment-2.yml

With the above, both experiment-1 and experiment-2 will run on the same resource provisioned during the kiso up stage.

[philrhc]

okay thank you, both great suggestions