# OpenStack

OpenStack is meant for custom workloads that do not fit into any other service offered by TU Wien. It gives you access
to CPU and GPU resources in the form of simply deployed virtual machines that can then be configured to serve most
purposes.

!!! warning

    The OpenStack service is not location-redundant. Hosting mission-critical workloads is not recommended. If you are
    looking for a virtual machine solution for mission-critical workloads, please check out
    [TUhost](https://www.it.tuwien.ac.at/services/netzwerk-und-server/tuhost-virtual-server-hosting).

## When should you use OpenStack?

The short answer is probably not. We provide access to our compute resources in many other ways that can be used more
efficiently. OpenStack is an underlying tool for many of our other services rather than something we recommend for
direct consumption. That said, there are a few cases where it makes sense:

- **Custom workloads**: You have a workload that needs custom-compiled code, direct access, or can somehow not run on a
  [TUhost](https://www.it.tuwien.ac.at/en/services/network-and-servers/tuhost-virtual-server-hosting) machine.
- **Testing environment**: You need a simple, low-power machine to run tests that cannot run in a container or on
  [TUhost](https://www.it.tuwien.ac.at/en/services/network-and-servers/).
- **GPU workloads**: You need a GPU, and our [SLURM](https://datalab.tuwien.ac.at/science/slurm/) or
  [Jupyter](https://datalab.tuwien.ac.at/science/jaas/) environments don't fit your use case.

!!! note
    CPU resources are available on demand. All of our GPUs are currently allocated, so GPU flavors are not generally
    available. If you need persistent GPU capacity, contact us about hosting your own GPUs.

!!! tip

    Kind request: if you intend to create more than 1-2 VMs, please create a [private network](https://datalab.tuwien.ac.at/infrastructure/openstack/networking/) and use
    only as many public IP addresses as you absolutely need.

## Resources

The resources you can request via OpenStack fall into a few categories:

| Resource            | Description                                                                                       |
|---------------------|---------------------------------------------------------------------------------------------------|
| Compute             | CPU flavors, from small 1-vCPU machines to large high-memory or HPC flavors. See [flavors](https://datalab.tuwien.ac.at/infrastructure/openstack/flavors/). |
| GPU                 | NVIDIA GPUs through dedicated GPU flavors, currently not generally available. See [flavors](https://datalab.tuwien.ac.at/infrastructure/openstack/flavors/). |
| Storage             | Volumes (Cinder) and shared file systems (Manila/CephFS, e.g. NFS). See [storage](https://datalab.tuwien.ac.at/infrastructure/openstack/storage/).    |
| Networking          | Private networks, routers, floating IPs, load balancers and security groups. See [networking](https://datalab.tuwien.ac.at/infrastructure/openstack/networking/). |

## Getting started

1. [Log in](https://datalab.tuwien.ac.at/infrastructure/openstack/login/) to OpenStack.
2. [Create a project](https://datalab.tuwien.ac.at/infrastructure/openstack/creating-a-project/) or request access to an existing one.
3. [Create a virtual machine](https://datalab.tuwien.ac.at/infrastructure/openstack/creating-a-vm/).