Change Details

New options are available in the proxmox provider plugin so: - add vmid as defined in proxmox today - had to inline the module call for the storage node (which has more than 1 disk). It's now inlined like the gateway (which has more than 1 network declaration) - do not fallback to default values. So hypervisor, bridge must be declared for each node. - separate staging from production to avoid touching the production node (for now) Note that i had to tweak a bit the terraform.tfstate json file. Pondering whether we can't just commit this into the repository (as a poor man configuration shared management as a first step). Note: Oh yeah, also, i dropped the local "zookeeper.tf" and "kelvingrove.tf" file because the `terraform plan resource=staging.tf` would not work). As a result, we saw those zookeeper and kelvingrove nodes to be spawned in the plan below.

New options are available in the proxmox provider plugin so: - Add vmid as defined in proxmox today (so it won't try and generate one for some reason) - Had to inline the "module node" call for the storage0 node (which has more than 1 disk). It's now inlined like the gateway (which has more than 1 network declaration). So it's a bit repetitive but it's declared appropriately. - Separate staging from production to avoid touching the production node (for now) - As a poor man configuration shared management, i added the staging terraform.tfstate within the repository... (no sensible information in there) - Do not fallback to default values. So some properties are not set for everyone (e.g. hypervisor, bridge, etc...). They must be declared for each node. Now the terraform plan for staging sounds reasonable. I modified some production nodes according to their current configuration but stopped as it's a subject for another time. (Shout out if i need to remove those but this sounds like lost time to do so, might as well keep it since it's done)

New options are available in the proxmox provider plugin so: - add- Add vmid as defined in proxmox today - had to inline the module call for the storage node (which has more than 1 disk). It's now inlined like the gateway (which has more than 1 network declaration) - do not fallback to default values. So hypervisor, bridge must be declared for each node. - separate staging from production to avoid touching the production node (for now (so it won't try and generate one for some reason) Note that i had to tweak a bit the terraform.tfstate json file. Pondering whether we can't just commit this into the repository (as a poor man configuration shared management as a first step)- Had to inline the "module node" call for the storage0 node (which has more than 1 disk). It's now inlined like the gateway (which has more than 1 network declaration). So it's a bit repetitive but it's declared appropriately. Note: Oh yeah- Separate staging from production to avoid touching the production node (for now) - As a poor man configuration shared management, i added the staging terraform.tfstate within the repository... (no sensible information in there) - Do not fallback to default values. So some properties are not set for everyone (e.g. hypervisor, bridge, also,etc...). i dropped the local "zookeeper.tf" and "kelvingrove.tf" file because the `terraform plan resource=staging.tf` would not work)They must be declared for each node. Now the terraform plan for staging sounds reasonable. I modified some production nodes according to their current configuration but stopped as it's a subject for another time. As a result(Shout out if i need to remove those but this sounds like lost time to do so, we saw those zookeeper and kelvingrove nodes to be spawned in the plan below.might as well keep it since it's done)