ScienceCloud Hardware¶

Overview¶

ScienceCloud currently provides the compute instances and storage with the following grand totals:

Computing¶

nodes	virtual CPUs	total RAM
🔧 Coming Soon

GPU-Computing¶

nodes	GPUs	virtual CPUs	total RAM
🔧 Coming Soon

For more information about GPUs on ScienceCloud, please see the GPU section.

Storage¶

Block storage served by Cinder and object storage served by Swift:

type	raw capacity	usable capacity
Block storage	🔧 Coming Soon
Object storage	🔧 Coming Soon

Network¶

Every compute node has a non-blocking, redundant, 10gbps link to the internal network. This network is used to access the underlying storage infrastructure and provide network connectivity to the virtual machines.

The uplink to the University network is a redundant 20gbps link.

Flavors¶

Instances started on ScienceCloud land on different generations of CPUs depending on flavor. For available flavors, see the ScienceCloud flavor availability report.

Hypervisors¶

No. nodes	CPU type @ base clock	Base clock	Architecture	CPU/vCPU	RAM per node	Accelerators
🔧 Coming Soon

Both the instance root disk's data and any additionally attached volumes' data are stored on our CEPH cluster and are thus accessed via a redundant 20 or 50 gigabit network link.

To reduce fragmentation flavors are statically mapped to a specific hypervisor type. More specifically:

Flavor type	Hypervisor CPU
🔧 Coming Soon

There are a few cases in which it is desirable to have instances backed by the same generation of hardware (i.e. custom compiled software optimized with specific flags).

This can be accomplished on request by enabling specific flavors that are bound to a specific CPU generation. You should keep in mind that the binding solution will be more prone to issues during hardware maintenance as the instances cannot be moved easily from one host to another.

Flavor availability report¶

Direct link: https://herd.science-it.uzh.ch/avail-flavors/avail-public-flavors.html