YaST control center
YaST is a single tool for the user as well as for the sysadmin. In YaST you can configure services, the network, partitions and more. YaST is available as a graphical tool as well as in a text based version (ncurses
openSUSE VPS
openSUSE VPS, YaST and zypper on EPYC.
We run openSUSE Leap 15.5 stable as well as Tumbleweed on our nodes with AMD EPYC Genoa processors and use NVMe storage in RAID10.
We use this very sysadmin-centric Linux for our work. So we also make very good use of YaST as our control center, of snapper for rollbacks of changes, of zypper for packages and of btrfs for the filesystem. btrfs already supports bootable filesystem snapshots out of the box.
openSUSE is not currently available on BuyVPS. We plan to bring it back in a future release. In the meantime you can upload a custom openSUSE ISO from the panel.
Why openSUSE for sysadmin-centric work.
openSUSE is the community Linux behind SUSE Enterprise. Four reasons it stays in the panel:
Available right now.
Both flavors are in the panel. Pick by release model.
Workloads that fit openSUSE.
YaST-friendly sysadmin tasks, SUSE Enterprise Server ready work, rolling environments with rollback capabilities.
NVMe RAID10 and EPYC, in numbers.
These numbers come from the median of the 5 runs of the Geekbench single core and multi core tests on the Dedicated CPU D-4 plan in Amsterdam (2 vCPU pinned cores on EPYC Genoa processors, 4 GB DDR5 ECC memory, 60 GB NVMe RAID10 storage). You can find the full methodology for the benchmarks as well as the public Geekbench profiles for the single and multi core runs on the corresponding page.
Everything you need to operate it.
The control panel and REST API allow to perform every action of the VPS lifecycle without needing to contact support. All actions can be scripted from end to end. The API is also compatible with Terraform and Ansible.
- Reboot, shutdown, force-reset
- Reboot/shutdown/force-reset (ACPI shutdown if VPS is up).
- Reinstall any supported OS
- Destroy any existing installation and provision new installation of supported OS in less than a minute. Your SSH key will still be attached due to use of Cloud-Init.
- Rescue mode
- Boot from a recovery environment with the disk(s) mounted. From this environment you can then for example fix file system issues, change root password, fix problems with the initramfs etc.
- Custom ISO upload
- Upload any ISO (like a Linux distribution) and attach it as a CDROM to a server inside the HTML5 console and then install from there.
- HTML5 console
- HTML5 console, no VNC required to connect to a server where ssh has been misconfigured.
- Reverse DNS (PTR)
- Set IPv4 and IPv6 PTR records from the control panel. This is required for any mail server that wants to send out email.
- SSH key management
- Existing ssh keys can be attached to newly provisioned servers. The ssh keys are then injected by Cloud-Init on the first boot of the server.
- REST API
- Deploy, resize, power-cycle and snapshot servers through a full REST API that also covers volumes, backups, ISO uploads, firewall rules, SSH keys and recipes. Generate API credentials and drive everything from Terraform, Ansible or your own CI/CD pipeline.
Pricing
Same Linux, both regions.
Same Linux, both regions.
Same price.
Prices Linux same region same. Pricing provided for same Linux, same region (Amsterdam and New York), with prices for 2 year term. We are comparing the Standard, Dedicated CPU and High Memory servers with Linux.
Compare every plan
Standard
$18.40/mo
Shared 1:4 vCPU, S-4 to S-64
Dedicated CPU
$29.60/mo
Pinned 1:1 cores, D-4 to D-64
High Memory
$199.20/mo
1:8 RAM ratio, H-64 to H-192
Deploy an openSUSE VPS
in under a minute.
Our VPS's have the exact same hardware in both Amsterdam and New York. The managed VPS hosting from our panel has the exact same features in both locations. Also the support in both locations is identical. To login to your VPS within a minute or so add your SSH key to the VPS and then in the Cloud-Init section add the key as well. After the first boot it will be injected to the VPS so you can login with root as normal.
Common questions
FAQ about running openSUSE on BuyVPS.
Fast answers to common questions for openSUSE VPS Hosting such as plan selection, VPS deployment, support and administration of an openSUSE VPS on KVM.
FAQ
Common questions
Which openSUSE flavors do you support?
openSUSE Leap 15.5 (stable) and openSUSE Tumbleweed (rolling release). Both get you up and running within a minute using Cloud-Init.
What is the difference between Leap and Tumbleweed?
openSUSE Leap 15.5 is a stable release based on the SUSE Enterprise codebase (like SUSE Linux Enterprise Server), while openSUSE Tumbleweed is a rolling-release distribution that is always up to date and contains the latest versions of software. Tumbleweed uses snapper for rollback of changes to previous versions of the system.
Can I switch from Leap to Tumbleweed?
Yes, with the zypper distribution upgrade procedure. Snapshot first so you can roll back if anything goes wrong during the upgrade.
Is btrfs the default filesystem?
Yes. Previous changes on the system can be rolled back by snapper. The GRUB bootloader can even boot from previous snapshots.
Does openSUSE include SELinux or AppArmor?
The default mandatory access control layer in openSUSE is AppArmor. SELinux is available for openSUSE but not enabled by default.
Can I use YaST in headless mode?
Yes, YaST can run in a text-based interface over SSH. Use yast (text UI) or yast --ncurses.
How fresh is Tumbleweed?
openSUSE Tumbleweed is a daily rolling release. It generally follows upstream within a couple of days, after changes have gone through the openSUSE infrastructure testing processes.
Can I run containers on openSUSE?
openSUSE contains packages for Podman, Buildah and Docker in its official repositories. The newest container runtimes are released first in Tumbleweed.
Ready to deploy
Deploy openSUSE on a measured VPS
From $18.40/mo on a 2-year term, fixed for life. Paste this cloud-init to boot hardened in one step:
#cloud-config
package_update: true
packages: [ufw, fail2ban]
runcmd:
- ufw allow OpenSSH
- ufw --force enable
- systemctl enable --now fail2ban