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 our 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 SAS drives (most of it currently cold), accessible via Ceph (radosgw or Kubernets PersistentVolumes).
Tenants
Most services have been migrated from our old machines into Kubernetes. Exceptions are listed below.
You are also free to host your own personal stuff there within reason. See below for access.
Boston Evacuation Aktion
Here's a list of services that currently live on Boston Packets, but we'd like to migrate to hscloud. Ask on #infra on how to contribute.
- https://wiki.hackerspace.pl - dokuwiki, as of 2024-12, on krnlexception's todo list. Betatesting available at https://hswaw-wiki.cloud.of-a.cat.
- https://webchat.hackerspace.pl - just a redirect?
- mailman (https://lists.hackerspace.pl) - the web service is already on k8s, but also proxied via boston. Mailman-core and the database (used by both web and core, postgres) are still on boston.
- ldap/kerberos - (hard)
- email services (exim, dovecot) - (hard)
Planned upgrades
See crashcloud.
Monitoring
Documentation, Getting Access and Usage
Self-documenting in hackdoc (hscloud documentation stored within hscloud): https://hackdoc.hackerspace.pl/doc/codelabs/index.md