Console is now available on microLXC. https://i.imgur.com/pb5xXYH.png
This will spawn a shell inside your container or virtual machine (if you still have lxd-agent installed)
Different options without spawning a shell will follow.
I wanted actually to do more, however, it has been delayed already but the patch has been tested sooooo here we go
Patchnotes
Switching from slot based to resource based Instead of 1 Slot, you get 1GB of available memory you can use as you want.
Currently there are no rules or limits, besides your allocation and if the location has stock.
I will see how things will develop, adding rules or limits based on that.
Due to switching to resource based pools, the 50GB Plan in Norway has been limited to 10 slots, which is about half of the SSDâs storage, the Package just exists because terrahost decided to throw in a TB SSD.
Enabled the 128MB Package again, probably will do more Packages, already at roughly 20 right now, counting disabled and enabled ones.
May do Regional 128MB Packages with more Storage.
The current 128MB Package is Global.
Had no time yet, to test the templates on 64MB, so not enabled yet, 128MB Package already does not support all operating systems.
Increased minimum Uplink to 100Mbit on all Packages, no matter what size, same goes for IPv6 you get a /64 on everything, routed, except Tokyo.
Also increased the CPU caps to a minimum of 50%, Norway has been unleashed to 200%, since its a Dedi
Very cool, looking forward to working with it. I was born in Groningen, but I already have a machine in NL, and right now located in TH, so chose SGâŚ! ff82-a1e6-93b3-92e4
Got no response at all, so trying again: 9550-93ec-bdf5-e10d
(I donât want to be impatient, but I got the impression that the whole process is automated, and the script is supposed to check my post with the code and whether I match the requirementsâŚ)
EDIT: Maybe it is a manual check, in which case please disregard one of my attempts to apply.
The thing is, you have to complete the setup.
According to the logs, you actually passed verification however you never completed it aka you just closed your browser window.
Itâs been going now for half an hour. Is it perhaps struggling with the length of the threadâŚ?
EDIT: It must have fully timed out (perhaps 30 mins?), itâs back to the launch page, it never went past Token Verification.
Last try: 45f2-f8c3-ea10-ee36
EDIT: After around 33 mins. it went from âVerifying accountâ to âDeployâ. I tried refreshing in-between this time to see if that would do anything, but it just stayed on the Verifying account page. Perhaps this is the natural end to the Public TestâŚ?
@pepa65 If it takes longer than 5 minutes, something is likely broken.
In this case it was, I fixed it.
The system when verifying what you post, does not follow redirects neither does it read the same comment twice. The domain was changed back and forth and I didnât update all parts, ideally its just one but I didnât refactor it yet.
Helsinki is now available, No IPv6 however, plan was running a wg tunnel back to Norway, however routing was not feasible.
Right now its without IPv6 and probably will stay this way, local brokers are available though.
This Location will be KVM only for now, since this is our first machine with Debian, I donât have a live kernel patching solution yet so no LXC, expect a reboot though every now and then, will be announced here.
Because we donât have smoler packages available, the is currently a 50% discount off the memory usage, so if you get the 512MB package it will be calculated as 256MB and so on until the Node is about half full.
/48 IPv6 for PK is on the way, should be available in the next few days.
Took a bit longer than expected.
No ETA for Tokyo though.
The containers on Tokyo have been restarted today accidentally, I needed to replace a certificate however I did a restart instead of a reload, hence the reboot.