[–] 2 points 2 years ago (1 child)

I would start by moving the services running on the host to a VM, less downtime for those when switching to proxmox.

Also, if possible, address the data issue before migrating. If you can add more disks, you could setup a new zfs pool, ready to be used by proxmox.

And don't forget to backup (to external storage), you never know what could go wrong.

  • source
  • [–] 10 points 2 years ago (1 child)

    Great post, thanks for sharing 👍

    I would suggest to give Ansible a try, it would make it really easy to deploy a new service with all required users and config.

  • source
  • [–] 7 points 2 years ago (1 child)

    It looks like you are trying to reinvent parts of kubernetes.

    I would recommend to give it a try, it's easy to spin up with k3s, even on a single node!

    Set imagePullPolicy to Always in your deployments (this is more or less k8s version of compose) and latest tag, then every time you restart a deployment, you get the latest version, with auto rollback. Set the tag to a static version and it doesn't update as long as you don't change it.

    For gitops, add fluxcd.io and you're set, it doesn't even require a CI workflow.

    For the data copy, k8s provides Volume Snapshots https://kubernetes.io/docs/concepts/storage/volume-snapshots/

  • source
  • [–] 1 point 3 years ago*

    The documentation clearly states that idle vms on free tier could be reclaimed: https://docs.oracle.com/en-us/iaas/Content/FreeTier/freetier_topic-Always_Free_Resources.htm#freetier_topic_Always_Free_Resources_Infrastructure

    Idle Always Free compute instances may be reclaimed by Oracle. Oracle will deem virtual machine and bare metal compute instances as idle if, during a 7-day period, the following are true: CPU utilization for the 95th percentile is less than 15% Network utilization is less than 15% Memory utilization is less than 15% (applies to A1 shapes only)

    So don't create a 4 core 32gb ram vm to run a vpn, and you should be fine :)

  • source