Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S sysadm-environment
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 167
    • Issues 167
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Platform
  • Infrastructure
  • sysadm-environment
  • Issues
  • #4410
Closed
Open
Issue created Jul 27, 2022 by Antoine R. Dumont@ardumontOwner

Upgrade vm templates

When provisioning new rancher cluster or new nodes, vm templates are old enough that it takes at least one hour [1] to provision one node. It's too long.

Updating template should cut down that time by some unknown order of magnitude.

To reproduce, just clone out of the proxmox ui our template 10008 (bullseye-zfs) and start it. The boot takes forever as cloud-init is upgrading the zfs part (kernel module compilation and whatnot). That must be the pain point which should disappear altogether if we upgrate that template.

  • [1] swh-sysadmin-provisioning!83 (closed)

Migrated from T4410 (view on Phabricator)

Edited Oct 18, 2022 by Antoine R. Dumont
Assignee
Assign to
Time tracking