@hashicorp
The vSphere plugin is able to create vSphere virtual machines for use with any VMware product.
- Official
Updated last month
- GitHub(opens in new tab)
vSphere Supervisor
Type: vsphere-supervisor
Artifact BuilderId: vsphere.supervisor
This builder deploys and publishes new VMs to a vSphere Supervisor cluster using VM Service. If you are new to VM Service, please refer to Deploying and Managing Virtual Machines in vSphere with Tanzu for more information.
- It uses a kubeconfig file to connect to the vSphere Supervisor cluster.
- It uses the VM-Operator API to deploy and configure the source VM.
- It uses the Packer provisioners to customize the VM after establishing a successful connection.
- It publishes the customized VM as a new VM image to the designated content library in vSphere.
- The builder supports versions following the VMware Product Lifecycle Matrix from General Availability to End of General Support. Builds on versions that are end of support may work, but configuration options may throw errors if they do not exist in the vSphere API for those versions.
Examples
Example Packer template:
HCL2
JSON
Refer to the examples/supervisor directory within the GitHub repository for more complete examples.
Configuration Reference
There are various configuration options available for each step in this builder. The required items are listed below as well as the optional configs further down the page.
Required
image_name
(string) - Name of the source virtual machine (VM) image.class_name
(string) - Name of the VM class that describes virtual hardware settings.storage_class
(string) - Name of the storage class that configures storage-related attributes.
Optional
Supervisor Connection
kubeconfig_path
(string) - The path to kubeconfig file for accessing to the vSphere Supervisor cluster. Defaults to the value ofKUBECONFIG
envvar or$HOME/.kube/config
if the envvar is not set.supervisor_namespace
(string) - The Supervisor namespace to deploy the source VM. Defaults to the current context's namespace in kubeconfig.
Source VM Creation
source_name
(string) - Name of the source VM. Defaults topacker-vsphere-supervisor-<random-suffix>
.network_type
(string) - Name of the network type to attach to the source VM's network interface. Defaults to empty.network_name
(string) - Name of the network to attach to the source VM's network interface. Defaults to empty.keep_input_artifact
(bool) - Preserve all the created objects in Supervisor cluster after the build finishes. Defaults tofalse
.bootstrap_provider
(string) - Name of the bootstrap provider to use for configuring the source VM. Supported values areCloudInit
,Sysprep
, andvAppConfig
. Defaults toCloudInit
.bootstrap_data_file
(string) - Path to a file with bootstrap configuration data. Required ifbootstrap_provider
is not set toCloudInit
. Defaults to a basic cloud config that sets up the user account from the SSH communicator config.
Source VM Watching
watch_source_timeout_sec
(int) - The timeout in seconds to wait for the source VM to be ready. Defaults to1800
.
Source VM Publishing
publish_image_name
(string) - The name of the published VM image. If not specified, the vm-operator API will set a default name.watch_publish_timeout_sec
(int) - The timeout in seconds to wait for the VM to be published. Defaults to600
.
Communicator Configuration
ssh_host
(string) - The address to SSH to. This usually is automatically configured by the builder.ssh_port
(int) - The port to connect to SSH. This defaults to22
.ssh_username
(string) - The username to connect to SSH with. Required if using SSH.ssh_password
(string) - A plaintext password to use to authenticate with SSH.ssh_ciphers
([]string) - This overrides the value of ciphers supported by default by Golang. The default value is [ "aes128-gcm@openssh.com", "chacha20-poly1305@openssh.com", "aes128-ctr", "aes192-ctr", "aes256-ctr", ]Valid options for ciphers include: "aes128-ctr", "aes192-ctr", "aes256-ctr", "aes128-gcm@openssh.com", "chacha20-poly1305@openssh.com", "arcfour256", "arcfour128", "arcfour", "aes128-cbc", "3des-cbc",
ssh_clear_authorized_keys
(bool) - If true, Packer will attempt to remove its temporary key from~/.ssh/authorized_keys
and/root/.ssh/authorized_keys
. This is a mostly cosmetic option, since Packer will delete the temporary private key from the host system regardless of whether this is set to true (unless the user has set the-debug
flag). Defaults to "false"; currently only works on guests withsed
installed.ssh_key_exchange_algorithms
([]string) - If set, Packer will override the value of key exchange (kex) algorithms supported by default by Golang. Acceptable values include: "curve25519-sha256@libssh.org", "ecdh-sha2-nistp256", "ecdh-sha2-nistp384", "ecdh-sha2-nistp521", "diffie-hellman-group14-sha1", and "diffie-hellman-group1-sha1".ssh_certificate_file
(string) - Path to user certificate used to authenticate with SSH. The~
can be used in path and will be expanded to the home directory of current user.ssh_pty
(bool) - Iftrue
, a PTY will be requested for the SSH connection. This defaults tofalse
.ssh_timeout
(duration string | ex: "1h5m2s") - The time to wait for SSH to become available. Packer uses this to determine when the machine has booted so this is usually quite long. Example value:10m
. This defaults to5m
, unlessssh_handshake_attempts
is set.ssh_disable_agent_forwarding
(bool) - If true, SSH agent forwarding will be disabled. Defaults tofalse
.ssh_handshake_attempts
(int) - The number of handshakes to attempt with SSH once it can connect. This defaults to10
, unless assh_timeout
is set.ssh_bastion_host
(string) - A bastion host to use for the actual SSH connection.ssh_bastion_port
(int) - The port of the bastion host. Defaults to22
.ssh_bastion_agent_auth
(bool) - Iftrue
, the local SSH agent will be used to authenticate with the bastion host. Defaults tofalse
.ssh_bastion_username
(string) - The username to connect to the bastion host.ssh_bastion_password
(string) - The password to use to authenticate with the bastion host.ssh_bastion_interactive
(bool) - Iftrue
, the keyboard-interactive used to authenticate with bastion host.ssh_bastion_private_key_file
(string) - Path to a PEM encoded private key file to use to authenticate with the bastion host. The~
can be used in path and will be expanded to the home directory of current user.ssh_bastion_certificate_file
(string) - Path to user certificate used to authenticate with bastion host. The~
can be used in path and will be expanded to the home directory of current user.ssh_file_transfer_method
(string) -scp
orsftp
- How to transfer files, Secure copy (default) or SSH File Transfer Protocol.NOTE: Guests using Windows with Win32-OpenSSH v9.1.0.0p1-Beta, scp (the default protocol for copying data) returns a a non-zero error code since the MOTW cannot be set, which cause any file transfer to fail. As a workaround you can override the transfer protocol with SFTP instead
ssh_file_transfer_protocol = "sftp"
.ssh_proxy_host
(string) - A SOCKS proxy host to use for SSH connectionssh_proxy_port
(int) - A port of the SOCKS proxy. Defaults to1080
.ssh_proxy_username
(string) - The optional username to authenticate with the proxy server.ssh_proxy_password
(string) - The optional password to use to authenticate with the proxy server.ssh_keep_alive_interval
(duration string | ex: "1h5m2s") - How often to send "keep alive" messages to the server. Set to a negative value (-1s
) to disable. Example value:10s
. Defaults to5s
.ssh_read_write_timeout
(duration string | ex: "1h5m2s") - The amount of time to wait for a remote command to end. This might be useful if, for example, packer hangs on a connection after a reboot. Example:5m
. Disabled by default.ssh_remote_tunnels
([]string) -ssh_local_tunnels
([]string) -
temporary_key_pair_type
(string) -dsa
|ecdsa
|ed25519
|rsa
( the default )Specifies the type of key to create. The possible values are 'dsa', 'ecdsa', 'ed25519', or 'rsa'.
NOTE: DSA is deprecated and no longer recognized as secure, please consider other alternatives like RSA or ED25519.
temporary_key_pair_bits
(int) - Specifies the number of bits in the key to create. For RSA keys, the minimum size is 1024 bits and the default is 4096 bits. Generally, 3072 bits is considered sufficient. DSA keys must be exactly 1024 bits as specified by FIPS 186-2. For ECDSA keys, bits determines the key length by selecting from one of three elliptic curve sizes: 256, 384 or 521 bits. Attempting to use bit lengths other than these three values for ECDSA keys will fail. Ed25519 keys have a fixed length and bits will be ignored.NOTE: DSA is deprecated and no longer recognized as secure as specified by FIPS 186-5, please consider other alternatives like RSA or ED25519.
winrm_username
(string) - The username to use to connect to WinRM.winrm_password
(string) - The password to use to connect to WinRM.winrm_host
(string) - The address for WinRM to connect to.NOTE: If using an Amazon EBS builder, you can specify the interface WinRM connects to via
ssh_interface
winrm_no_proxy
(bool) - Setting this totrue
adds the remotehost:port
to theNO_PROXY
environment variable. This has the effect of bypassing any configured proxies when connecting to the remote host. Default tofalse
.winrm_port
(int) - The WinRM port to connect to. This defaults to5985
for plain unencrypted connection and5986
for SSL whenwinrm_use_ssl
is set to true.winrm_timeout
(duration string | ex: "1h5m2s") - The amount of time to wait for WinRM to become available. This defaults to30m
since setting up a Windows machine generally takes a long time.winrm_use_ssl
(bool) - Iftrue
, use HTTPS for WinRM.winrm_insecure
(bool) - Iftrue
, do not check server certificate chain and host name.winrm_use_ntlm
(bool) - Iftrue
, NTLMv2 authentication (with session security) will be used for WinRM, rather than default (basic authentication), removing the requirement for basic authentication to be enabled within the target guest. Further reading for remote connection authentication can be found here.
Deprovisioning Tasks
If you would like to clean up the VM after the build is complete, you could use the Ansible provisioner to run the following tasks to delete machine-specific files and data.
HCL2
JSON
Content of cleanup-playbook.yml
: