Actions
User story #14142
closed
Add a possibility to separate the vms provisionning in rtf from vagrant
Effort required:
Name check:
Fix check:
Regression:
Description
Since vagrant can only provision one machine at a time, externalize this part can save a lot of time in vms deployments.
Still, the vboxguest addtions update, the cleanbox script and network/hostname setup will still be done in the vagrant provisioning.
Provisioning will be add as a parameter in the platforms json files. Adding a "provision" key will prevent vagrant from running the standard rudder setup.
Adding a "provision" key with the value "python" will boot the vmS with vagrant before using python to install the rudder-setup on it.
I hope that this way we will be able to massively reduce the execution time needed to setup the rudder platforms tests.
Updated by Félix DALLIDET almost 6 years ago
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
Updated by Félix DALLIDET almost 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-tests/pull/146
Updated by Félix DALLIDET almost 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-tests|6b152a1e61a378d0b933a7815a90ec818b8dff33.
Updated by Benoît PECCATTE over 5 years ago
- Status changed from Pending release to Released
Actions