Brontekst bekijken van YoloCloud

[https://vm.hackalot.nl YoloCloud] is the premier provider of hackerspace hosting, located right at the hub of creativity known as Hackalot.
Free VYSes (Virtual Yolo Servers) are provided to all members of Hackalot.

= Rules =

# You are provided with a so-called "project" that has a fixed amount of Disk and RAM available to you. If you need more, ask rewby or Xesxen.
# The above limits are an upper limit, please don't make VMs that are unnecessarily big.
# The hypervisor is a shared resource, please treat it as such.
# Our uptime is "it's sometimes up". Make sure your VMs can handle reboots.
# Our data retention SLA is "some data will be retained". BYOB (bring your own backups)
# Be excellent to each other.
# Please don't do anything that can get hackalot in trouble.

= Getting started =

The hypervisor can be accessed at https://vm.hackalot.nl/ (LAN-only or remotely via [[VPN]]).
Sign in by clicking the "Login with SSO" button, this will send you to the Hackalot SSO for sign-in.

The first time you log in, you won't be able to see anything and most buttons will be grayed out.
This is expected, it may take up to 2 minutes for the automation to come by and finish setting up your user.
Once this has happened, please refresh the page.

You can then select a project (in the top-left) with the name <code>m-<your username></code>.
You have to select your project again every time you log in. (Admin users will see the default project, please remember to switch to your own project.)

== Creating your first VM ==

# A recommended one-time step is to navigate to "Profiles", then "default", then "configuration" and click on "Add SSH key". This adds your SSH key to the default profile and it will be deployed automatically to all future VMs you make.
# Navigate to the "Instances" page.
# Click "Create instance".
# Input a name for the vm (this follows dns rules)
# Select an image. Note: The debian images don't seem to include an SSH server by default.
# Select an instance type. See the FAQ on type selection.
# Move to the "Disk" section on the left and check that you are okay with the amount of disk space. Click the pencil icon to change the size of your root disk.
# Move to the "Resource Limits" section on the left. "Exposed CPU limit" and "Memory limit" are the amount of cpu cores and memory allocated to your instance, make sure to set them as needed.
# Click "Create and start".

Once the VM boots, it will be available under <code><name>.<username>.vm.hackalot.nl</code>.

== Using the control panel ==
From the "Instances" panel you can access all your instances.
If you click on the hostname you will enter the VM specific page.
From there you can use the "Configuration" tab to edit the VM setup.
You can also use "Console" to access the VM console.
You can use "Terminal" to access the root account of the VM. The terminal doubles as a backdoor way of getting in if you lock yourself out.

= External Access =

The IPv6 addresses are unfiltered on all ports.
All addresses on a VM are unfiltered from the space network as well as the [[VPN]]. (The control panel is also accessible from the [[VPN]].)

== HTTP/HTTPS Ingress ==

If you wish to make a web application accessible on the public internet, we provide a "transparent" proxy.
This proxy does both HTTP and HTTPS; for HTTPS we proxy based on SNI and do *not* terminate the TLS.
Thus you should set up your VM to listen on both port 80 and port 443 (HTTPS).
Letsencrypt's HTTP challenge (default for software like caddy) works fine.

As an additional service, <code><username>.member.hackalot.nl</code> is already configured correctly and all members are allowed to use their subdomain to host services/websites. (You can also nest services; e.g. <code>nextcloud.hacker.member.hackalot.nl</code>)

Here's how you use it:
# Add a <code>CNAME</code> record in your domain of choice and point it at <code>vm-ingress.hackalot.nl</code>. (Already done if you're using <code><username>.member.hackalot.nl</code>)
# Open the control panel at https://vm.hackalot.nl/
# Go to the instance that has to receive the domain.
# Go to the configuration tab.
# Click on the "YAML Configuration" toggle.
# Under the <code>config:</code> key, add: <code>user.ingress.domains: <your domain></code> (this can be a comma-separated list of multiple domains) (you can also set <code>user.ingress.proxy: "true"</code> to get PROXY headers added)
# Click save.
# Wait 1-2 minutes.
# Any plain HTTP requests or HTTPS requests with the header/SNI set to your domain will now be forwarded to this VM/Container.

= FAQ =

== What instance type should I use? ==
"Container" means LXC containers and "VM" is a full KVM vm.

If you're running "normal" services, "Container" will work fine.
If you're running podman or docker, use "VM".

== My instance type button is grayed out ==

You probably selected a "cached" image. (Recognized by the green select button.)
A cached image is one that you've used previously.
Unfortunately LXD has a UI-papercut where if you use a cached image, you can only use the instance type you used it for.
To solve this, go find the non-cached image in the list and use that instead.

== Should I be worried about the resources on YoloCloud? ==

The Hackalot region is supplied with two E5-2670v2 CPUs, 192GB of ram, and 2.5TB of usable storage.
While we ask that you don't assign needlessly large amounts of resources, there should not be any issue running heavier applications.

For example, don't assign 16G ram and 20 cores just to run nginx serving a static site.
But if you want to run some elasticsearch thing that needs 8G ram to perform at all reasonably, go ahead.

== My custom flavour of Linux won't start? ==

Either when deploying, or later once you've created your VM, change the following setting:

* Under <code>Security policies</code> set <code>Enable secureboot (VMs only)</code> to <code>false</code>