-
Notifications
You must be signed in to change notification settings - Fork 22
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
VM IP static configuration #241
Comments
Hi @joppino, you are right - this feature is currently missing in the |
Hi! After merge your feature, i would like to create PR for other params (and pr for terraform provider). What do you think ? Also i think, that all of func NewInitialization(customScript, hostname string) BuildableInitialization {..} And all other parameters should be configured via builder: initialization := NewInitialization("custom-script", "hostname").WithSomeParam("some-param"); |
Hello, I've opened a similar issue in the terraform ovirt provider which is using this client.
It seems no more possibile to configure the VM main NIC using the initialization parameter nic_configuration as before with the terraform provider.
It seems that this is due to the fact that in the current ovirt-client version (v2.1.0) the Initialization contains a Cloud-init custom script and/or the initialization hostname, and nothing more:
So the question is how to replicate the previous behavior. The Ansible module still lets the user specify the initial nic_configuration, but I cannot find a way to replicate this in the current version.
Thanks
The text was updated successfully, but these errors were encountered: