Page MenuHomeSoftware Heritage

production-worker05: Increase memory and scratch disk space
ClosedPublic

Authored by ardumont on Oct 13 2022, 3:43 PM.

Details

Summary

Related to T4618

Test Plan
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.rancher-node-production-worker05.proxmox_vm_qemu.node will be updated in-place
  ~ resource "proxmox_vm_qemu" "node" {
      ~ balloon                   = 16384 -> 32768
        id                        = "uffizi/qemu/112"
      ~ memory                    = 32768 -> 65536
        name                      = "rancher-node-production-worker05"
        # (37 unchanged attributes hidden)

      ~ disk {
          ~ size         = "30G" -> "50G"
            # (17 unchanged attributes hidden)
        }

        # (2 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Diff Detail

Repository
rSPRE sysadm-provisioning
Branch
master
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 32280
Build 50562: arc lint + arc unit

Event Timeline

olasd added a subscriber: olasd.

does ballooning interact correctly with kubernetes' memory accounting? I assume that'd do a better job if the node only had a static amount of memory.

This revision is now accepted and ready to land.Oct 13 2022, 3:50 PM

Drop ballooning, it seems unneeded as the node is already at its top memory