Virtual servers (sometimes also referred to as "cloud servers") are our bread and butter. Since they run on different physical hosts than the storage they use, we often refer to their function as "compute".
Currently, our servers come in two different types of compute flavors:
- Flex - CPU cores are shared between virtual servers; these flavors provide room for short-term load peaks and are ideal for most applications.
- Plus - The physically available computing power is not overcommitted; these flavors provide consistent CPU performance and are ideal for demanding workloads.
See https://www.cloudscale.ch/en/pricing for more details.
Servers can be launched in two different ways:
- Through the Cloud Control Panel (https://control.cloudscale.ch).
- Through the REST API (https://api.cloudscale.ch).
The API can be used in various ways:
- Using an HTTP client (Curl, Python Requests library etc.).
- Using our official CLI.
- Using our Ansible cloud collection.
- Using our Terraform provider.
- API Documentation
- Blog Post: Plus Flavors
- Blog Post: Our API
- Blog Post: Our CLI
- Blog Post: Ansible (1/2)
- Blog Post: Ansible (2/2)
- Blog Post: Terraform (1/2)
- Blog Post: Terraform (2/2)
- Blog Post: Cloud-Init (1/2)
- Blog Post: Cloud-Init (2/2)
Using the following tools, launch and delete a server (once per each tool):
- Your library of choice (Curl, Python Requests library etc.).
- An Ansible playbook.
- A Terraform config.
- The official CLI.
Make sure to connect to each server before deleting it to ensure that it actually booted correctly.
Using your favorite tool, create a flex-4-1 instance, then turn it into a plus-4-2 instance.
Virtual servers launched on IaaS platforms usually need some kind of initial provisioning (interface configuration, hostname, SSH authorized keys). The de-facto industry standard is using cloud-config for cloud-init. Learn more about it and try launching a server using cloud-init to install nginx right after boot, without any additional intervention.