terraform plan
```
terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
module.deposit.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/120]
module.worker2.proxmox_vm_qemu.node: Refreshing state... [id=branly/qemu/112]
module.scheduler0.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/116]
module.db0.proxmox_vm_qemu.node: Refreshing state... [id=orsay/qemu/115]
module.journal0.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/122]
module.vault.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/121]
module.worker0.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/117]
module.storage0.proxmox_vm_qemu.node: Refreshing state... [id=orsay/qemu/114]
module.webapp.proxmox_vm_qemu.node: Refreshing state... [id=branly/qemu/119]
module.worker1.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/118]
------------------------------------------------------------------------
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# module.rp0.proxmox_vm_qemu.node will be created
+ resource "proxmox_vm_qemu" "node" {
+ agent = 0
+ balloon = 1024
+ bios = "seabios"
+ boot = "c"
+ ciuser = "root"
+ clone = "debian-buster-2020-10-16"
+ clone_wait = 15
+ cores = 2
+ cpu = "host"
+ desc = "Node to host the reverse proxy"
+ force_create = false
+ full_clone = false
+ hotplug = "network,disk,usb"
+ id = (known after apply)
+ ipconfig0 = "ip=192.168.130.20/24,gw=192.168.130.1"
+ kvm = true
+ memory = 2048
+ name = "rp0"
+ nameserver = "192.168.100.29"
+ numa = false
+ onboot = true
+ os_type = "cloud-init"
+ preprovision = true
+ searchdomain = "internal.staging.swh.network"
+ sockets = 1
+ ssh_host = (known after apply)
+ ssh_port = (known after apply)
+ ssh_user = "root"
+ sshkeys = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDVKCfpeIMg7GS3Pk03ZAcBWAeDZ+AvWk2k/pPY0z8MJ3YAbqZkRtSK7yaDgJV6Gro7nn/TxdJLo2jEzzWvlC8d8AEzhZPy5Z/qfVVjqBTBM4H5+e+TItAHFfaY5+0WvIahxcfsfaq70MWfpJhszAah3ThJ4mqzYaw+dkr42+a7Gx3Ygpb/m2dpnFnxvXdcuAJYStmHKU5AWGWWM+Fm50/fdMqUfNd8MbKhkJt5ihXQmZWMOt7ls4N8i5NZWnS9YSWow8X/ENOEqCRN9TyRkc+pPS0w9DNi0BCsWvSRJOkyvQ6caEnKWlNoywCmM1AlIQD3k4RUgRWe0vqg/UKPpH3Z root@terraform"
+ target_node = "branly"
+ vcpus = 0
+ vlan = -1
+ vmid = 0
+ disk {
+ backup = false
+ cache = "none"
+ format = "raw"
+ id = 0
+ iothread = false
+ mbps = 0
+ mbps_rd = 0
+ mbps_rd_max = 0
+ mbps_wr = 0
+ mbps_wr_max = 0
+ replicate = false
+ size = "32G"
+ storage = "proxmox"
+ storage_type = "cephfs"
+ type = "virtio"
}
+ network {
+ bridge = "vmbr443"
+ firewall = false
+ id = 0
+ link_down = false
+ macaddr = (known after apply)
+ model = "virtio"
+ queues = -1
+ rate = -1
+ tag = -1
}
}
Plan: 1 to add, 0 to change, 0 to destroy.
Changes to Outputs:
+ rp0_summary = (known after apply)
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
```