Differential D1762 Diff 5994 proxmox/terraform/storage.tf

Changeset View

Standalone View

proxmox/terraform/storage.tf

This file was added.

				# Keyword use:
				# - provider: Define the provider(s)
				# - data: Retrieve data information to be used within the file
				# - resource: Define resource and create/update

				provider "proxmox" {
				pm_tls_insecure = true
				pm_api_url = "https://orsay.internal.softwareheritage.org:8006/api2/json"
				# in a shell (see README): source ./setup.sh
				}

				# `pass search terraform-proxmox` in credential store
				variable "ssh_key_data" {
				ardumontAuthorUnsubmitted Done Inline Actions Right now, the name is different (should be uffizi) because: we need it to define the hostname (for puppet) and that's the only way i saw for now [1] but i also saw a "getVmRefByName" in the plugin's code and i'm unsure about the collision policy yet. I'd prefer we use "vm id" but as far as i could tell, we cannot for now. So to be on the safe side, i'll continue with different names for now. [1] ftigeot spoke about dhcp but i'm unsure of the delay implied by this solution (which i think would possibly the right one in the long run) ardumont: Right now, the name is different (should be uffizi) because: - we need it to define the…
				ardumontAuthorUnsubmitted Done Inline Actions (I submitted anyway because i wanted to keep my reasoning somewhere) My fear seems unfounded as per [1] From what i gather, the composition of the {vm-name, target-node} are used to refuse to create 2 similar named vm (aside the case of using `forceCreate` flag which we won't use, so i say ;) (target-node being the hypervisor) Still, i prefer to stay on the safe side for now. [1] https://github.com/Telmate/terraform-provider-proxmox/blob/9c1f2f41941f94ebd88b1175bd587511d09ae23c/proxmox/resource_vm_qemu.go#L400-L406 ardumont: (I submitted anyway because i wanted to keep my reasoning somewhere) My fear seems unfounded…
				type = "string"
				default = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDVKCfpeIMg7GS3Pk03ZAcBWAeDZ+AvWk2k/pPY0z8MJ3YAbqZkRtSK7yaDgJV6Gro7nn/TxdJLo2jEzzWvlC8d8AEzhZPy5Z/qfVVjqBTBM4H5+e+TItAHFfaY5+0WvIahxcfsfaq70MWfpJhszAah3ThJ4mqzYaw+dkr42+a7Gx3Ygpb/m2dpnFnxvXdcuAJYStmHKU5AWGWWM+Fm50/fdMqUfNd8MbKhkJt5ihXQmZWMOt7ls4N8i5NZWnS9YSWow8X/ENOEqCRN9TyRkc+pPS0w9DNi0BCsWvSRJOkyvQ6caEnKWlNoywCmM1AlIQD3k4RUgRWe0vqg/UKPpH3Z root@terraform"
				}

				variable "user_admin" {
				type = "string"
				default = "root"
				}

				variable "domain" {
				type = "string"
				default = "internal.staging.swh.network"
				}

				variable "environment" {
				type = "string"
				default = "new_staging"
				}

				ardumontAuthorUnsubmitted Done Inline Actions That will go away at some point (prior to landing). ardumont: That will go away at some point (prior to landing).
				variable "puppet_master" {
				type = "string"
				default = "pergamon.internal.softwareheritage.org"
				}

				variable "dns" {
				type = "string"
				default = "192.168.100.29"
				}

				variable "gateway" {
				type = "string"
				default = "192.168.100.1"
				}

				resource "proxmox_vm_qemu" "storage0" {
				name = "storage0"
				desc = "swh storage node"
				# hypervisor onto which make the vm
				target_node = "orsay"
				# See init-template.md to see the template vm bootstrap
				clone = "template-debian-9"
				# linux kernel 2.6
				qemu_os = "l26"
				# generic setup
				sockets = 1
				cores = 2
				memory = 8192
				# boot machine when hypervirsor starts
				onboot = true
				#### cloud-init setup
				# to actually set some information per os_type (values: ubuntu, centos,
				# cloud-init). Keep this as cloud-init
				os_type = "cloud-init"
				# ciuser - User name to change ssh keys and password for instead of the
				# image’s configured default user.
				ciuser = "${var.user_admin}"
				# searchdomain - Sets DNS search domains for a container.
				searchdomain = "${var.domain}"
				# nameserver - Sets DNS server IP address for a container.
				nameserver = "${var.dns}"
				# sshkeys - public ssh keys, one per line
				sshkeys = "${var.ssh_key_data}"
				# FIXME: When T1872 lands, this will need to be updated
				# ipconfig0 - [gw =] [,ip=<IPv4Format/CIDR>]
				ipconfig0 = "ip=192.168.100.125/24,gw=${var.gateway}"
				ssh_user = "${var.user_admin}"
				disk {
				id = 0
				type = "virtio"
				storage = "orsay-ssd-2018"
				storage_type = "ssd"
				size = "32G"
				}
				network {
				id = 0
				model = "virtio"
				bridge = "vmbr0"
				macaddr = "3E:70:84:BF:9B:F5"
				}

				# Delegate to puppet at the end of the provisioning the software setup
				provisioner "remote-exec" {
				inline = [
				"puppet agent --server ${var.puppet_master} --environment=${var.environment} --waitforcert 60 --certname storage0.${var.domain} --test --noop",
				ardumontAuthorUnsubmitted Done Inline Actions `--noop` should go away as we want to actually apply. That means that we must know already what that node will be used for (but hey, we are calling puppet so that should be obvious ;). `--certname` might be best to not use it (but i don't know why yet ;) ardumont: `--noop` should go away as we want to actually apply. That means that we must know already what…
				]
				}
				}