Configuring Microsoft HyperV cloud connection

In order for Managed services to access the Microsoft HyperV Cloud environment, you must provide value for the following parameters:

  • Microsoft HyperV username - The user to connect to Microsoft HyperV, which is a mandatory field.
  • Microsoft HyperV password - The password to connect to Microsoft HyperV, which is a mandatory field.
  • Microsoft HyperV Host - Microsoft HyperV hostname or IP address, which is a mandatory field.
  • Port - The port on which winrm runs on Microsoft HyperV system (port that is used by the Microsoft HyperV APIs to communicate with the system). The default value is 5985, and it is a mandatory field.
  • Https enabled - Boolean value field that indicates whether communication to winrm on the Microsoft HyperV system (used by the Microsoft HyperV API) is over http or https, the latter being the default value.
  • TLS disabled - Boolean value field that indicates whether TLS Verification is used for the Microsoft HyperV API calls. The default value is TLS verification disabled.
  • NTLM enabled - Boolean value field that indicates whether winrm on Microsoft HyperV system (used by the Microsoft HyperV API) uses NTLM authentication. The default value is NTLM authentication enabled.
  • Connection timeout - The timeout to wait for the connection to become available for Microsoft HyperV API calls. The default value is 30s. It's a mandatory field.
  • CA certificate path - The path to the CA certificate to use for Microsoft HyperV API calls, which is an optional field.
  • Certificate path - The path to the certificate to use for authentication for Microsoft HyperV API calls, which is an optional field.
  • Certificate private key path - The path to the certificate private key to use for authentication for Microsoft HyperV API calls, which is an optional field.
  • TLS server name - The TLS server name for the host used for Microsoft HyperV API calls.

Uploading certificates

You must upload the certificates to the provider terraform pod using the Create a Terraform file API with type=file. The API uploads the certificates to /home/terraform/.terraform.d/cam. The value for certificate path variables must be /home/terraform/.terraform.d/cam/your_certificate_name.

Microsoft HyperV provider plugin binary

Microsoft HyperV provider is classified by Hashicorp as a community provider. The provider binary is not included with Managed services since it is neither official nor a verified provider.

If your Managed services installation has access to the internet, then the provider will be downloaded when you run the Microsoft HyperV Terrafrom template.

If your Managed services installation is in an air tight environment, then you need to download the provider binary from Microsoft HyperV Terrafrom Github repository.

If you installed Managed services on IBM Power, then you need to download the source from Microsoft HyperV Terrafrom GitHub repository and build the binary for IBM Power.