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

cusomiztion spec #92

Open
rj-reilly opened this issue Sep 29, 2016 · 3 comments
Open

cusomiztion spec #92

rj-reilly opened this issue Sep 29, 2016 · 3 comments

Comments

@rj-reilly
Copy link
Contributor

rj-reilly commented Sep 29, 2016

how do you call the customization spec ? I see the options but the actual name of the spec in vsphere ? my windows machines seem to find one automatically ? but not my linux servers.
rob

@mwrock
Copy link
Contributor

mwrock commented Sep 30, 2016

Looks like the readme could use some help there. I actually never used this feature but based on the code you would provide a string value to customization_spec instead of a hash.

@rj-reilly
Copy link
Contributor Author

I will update the docs and submit a PR. thanks

@rj-reilly rj-reilly reopened this Oct 3, 2016
@rj-reilly
Copy link
Contributor Author

rj-reilly commented Oct 3, 2016

The reason i am re-opening is this driver had previously applied a customization spec when providing the hash and using the name provided in vsphere_name: hostname, but at some point this stopped working and it just comes up with the template name. This is an issue for us as we need to start multiple hosts and take action based on their name. I just tried this by giving it the name of the custom spec but it still comes up with template name, although it does reboot like it is applying cspec. I will do some testing and see i can find at which version this stopped.

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

No branches or pull requests

2 participants