Table of Contents
hscloud
VMs are coming any day now ~q3k, A.D. 2018
Our new internal highly-available Infrastructure/Platform-as-a-Service.
This runs in out datacenter (dcr01 on netbox). This is different from our ISP services or internal machines.
Components
Currently hscloud is made up of a Kubernetes cluster named k0.hswaw.net. It runs on the following machines: bc01n01, bc01n02, bc01n03, dcr01s22, dcr01s24. In total we have 328GB of RAM and 144 x86 cores. We also have a half PB of storage on old SATA drives (most of it currently cold), accessible via Ceph (radosgw or Kubernets PersistentVolumes).
Tenants
We are moving services from our old machines into Kubernetes. Amongst other, currently running on the cluster is:
With more to come.
You are also free to host your own personal stuff there within reason. See below for access.
Getting Access
Clone the hscloud monorepo and follow the README. For now you will have to be added to a special group to have access via prodvider/prodaccess, ask any BOFH. For an introduction on how to use this, ping q3k or informatic.
By default a personal namespace will be created for you (personal-$user) that you can start anything in. A fairly draconian PodSecurityPolicy is present that might prevent you from using most traditional containers (eg. apt on ubuntu). If you don't know what this means, ask q3k.
