Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

validate reservation.yaml #174

Closed
ivotron opened this issue Aug 4, 2017 · 2 comments · Fixed by #342
Closed

validate reservation.yaml #174

ivotron opened this issue Aug 4, 2017 · 2 comments · Fixed by #342
Assignees

Comments

@ivotron
Copy link

ivotron commented Aug 4, 2017

Would be useful to have a --validate flag that validates the YAML for a given subcommand. For example: enos up --validate would check whether the YAML file contains all the necessary info for executing the up operation.

@rcherrueau
Copy link
Member

Like the idea. Implementing the --validate for the up should be an easy task thanks to the default_config method in a provider. But, for the enos os that should validate the inventory file, or for enos bench that should verify the workload, the validation gets tough.

Instead of a --validate, I propose something like enos new my-exp --provider=chameleon that makes a my-exp directory with a reservation file dedicated to chameleon, plus a default inventory and workload. It should limit the risk of wrong configurations.

@ivotron, @BeyondTheClouds/enos what do you think?

In a second time we could implement a better cli, à la npm init for instance. It will ask you to fill required fields and avoid the manual edition of the reservation file.

@msimonin
Copy link
Contributor

Let's start hacking this ;)

@rcherrueau rcherrueau mentioned this issue Apr 27, 2021
rcherrueau added a commit to rcherrueau/enos that referenced this issue Apr 27, 2021
'enos new' takes a new argument called '--provider' with the name of one of
enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm,
chameleonbaremetal, openstack, vmong5k, static).  It then generates a
reservation.yaml specific to that provider.

This and the json schema validation from enoslib implement BeyondTheClouds#174.
rcherrueau added a commit to rcherrueau/enos that referenced this issue Apr 27, 2021
'enos new' takes a new argument called '--provider' with the name of one of
enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm,
chameleonbaremetal, openstack, vmong5k, static).  It then generates a
reservation.yaml specific to that provider.

This and the json schema validation from enoslib implement BeyondTheClouds#174.
rcherrueau added a commit to rcherrueau/enos that referenced this issue Apr 27, 2021
'enos new' takes a new argument called '--provider' with the name of one of
enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm,
chameleonbaremetal, openstack, vmong5k, static).  It then generates a
reservation.yaml specific to that provider.

This and the json schema validation from enoslib implement BeyondTheClouds#174.
rcherrueau added a commit to rcherrueau/enos that referenced this issue Apr 27, 2021
'enos new' takes a new argument called '--provider' with the name of one of
enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm,
chameleonbaremetal, openstack, vmong5k, static).  It then generates a
reservation.yaml specific to that provider.

This and the json schema validation from enoslib implement BeyondTheClouds#174.
rcherrueau added a commit to rcherrueau/enos that referenced this issue Apr 27, 2021
'enos new' takes a new argument called '--provider' with the name of one of
enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm,
chameleonbaremetal, openstack, vmong5k, static).  It then generates a
reservation.yaml specific to that provider.

This and the json schema validation from enoslib implement BeyondTheClouds#174.
rcherrueau added a commit to rcherrueau/enos that referenced this issue Apr 27, 2021
'enos new' takes a new argument called '--provider' with the name of one of
enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm,
chameleonbaremetal, openstack, vmong5k, static).  It then generates a
reservation.yaml specific to that provider.

This and the json schema validation from enoslib implement BeyondTheClouds#174,BeyondTheClouds#315
rcherrueau added a commit to rcherrueau/enos that referenced this issue Apr 27, 2021
'enos new' takes a new argument called '--provider' with the name of one of
enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm,
chameleonbaremetal, openstack, vmong5k, static).  It then generates a
reservation.yaml specific to that provider.

This and the json schema validation from enoslib implement BeyondTheClouds#174 and
implement BeyondTheClouds#315
rcherrueau added a commit to rcherrueau/enos that referenced this issue Apr 27, 2021
'enos new' takes a new argument called '--provider' with the name of one of
enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm,
chameleonbaremetal, openstack, vmong5k, static).  It then generates a
reservation.yaml specific to that provider.

This and the json schema validation from enoslib implement BeyondTheClouds#174 and
implement BeyondTheClouds#315
rcherrueau added a commit to rcherrueau/enos that referenced this issue Apr 28, 2021
'enos new' takes a new argument called '--provider' with the name of one of
enos providers (i.e., g5k, vagrant:virtualbox, vagrant:libvirt, chameleonkvm,
chameleonbaremetal, openstack, vmong5k, static).  It then generates a
reservation.yaml specific to that provider.

This and the json schema validation from enoslib implement BeyondTheClouds#174 and
implement BeyondTheClouds#315
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants