-
Notifications
You must be signed in to change notification settings - Fork 150
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
Preflight Check #667
Comments
I'm not sure as to what exactly you mean by "configuration verification", can you please elaborate on that? Do you mean that nodes should run a sort of "acceptance test" where you check that some conditions hold true in an automated and repeatable/scriptable way? (e.g., can submit a test job to the batch-queuing system) |
I would like to verify that the config is free of errors and the deployment start, where the cloud provider is verified passes the test... i.e. keys, etc.Then I would be sure that the content of the config is free of errors. If the deployment then fails, it is a different issue.
What do you think?
Kind regards,Alex
|
If you mean ElastiCluster's config file, that is already done (at config load time). |
I am currently automating the deployment via elasticluster. Is it possible to include the option for configuration verification in the elasticluster. I would suggest to use the beginning part of the deployment where the config will be verified and the provider will be checked. The deployment should then stop and return a code (success or fail).
What is the oppinion?
The text was updated successfully, but these errors were encountered: