microLXC Public Test

Neoon

@Neoon said:
Maintenance Announcement
I have to carry out some changes on the backend, this will make the backend unavailable for roughly 1 hour or less.
Running machines are not affected, however no tasks or deployments can be done.
Will be done this week, Saturday, 11th of May, at around 20:00 GMT.

Done.

ehab

hey @Neoon

time we donate to you

give us a paypal email?

yes,,, now .... use money to buy new pants

Shot²

hey @Neoon - there's a Tokyo Equinix 'microJP' instance that can't be terminated.

(trying to delete the 128MB and recreate it with 256MB, or else Debian craps its bed with some operations)

Neoon

@ehab said:
hey @Neoon

time we donate to you

give us a paypal email?

yes,,, now .... use money to buy new pants

If you want to donate, I added [email protected] to Paypal, so you can do so.
Tanks, probably gonna buy me a pack of new pants though, for real.

@Shot² said:
hey @Neoon - there's a Tokyo Equinix 'microJP' instance that can't be terminated.

(trying to delete the 128MB and recreate it with 256MB, or else Debian craps its bed with some operations)

I rebooted it, fixed for now.
As long we are using LXD, the error probably will come up from time to time.

Have to migrate all nodes to Incus, however I don't wanna rush it.
Probably though gonna do a test migration and then start migrating a bunch.

Neoon

Maintenance Announcement

microLXC still got 3 nodes running on an older version of Ubuntu.
I will upgrade these 3 nodes next week, the Kernel version will be bumped to 5.15 afterwards.

Affected Locations
- Sandefjord
- Melbourne
- Tokyo

The System will be only rebooted once, so downtime should be minimal however expect 30-60 minutes.
Will be done next week, Saturday, 18th of May, at around 20:00 GMT.

dgc1980

e41b-a63b-50e6-f44f

edit: wow what a easy process, decided to jump on and play around and it was easy as to get a system deployed

Neoon

Maintenance Announcement

I mentioned a while ago once Incus becomes LTS, that microLXC will slowly migrate away from LXD.
Incus is basically a fork from LXD, which has been created a few months after Canonical took over LXD and changed the licenses.

Technically LXD still has support until 2029, so does Incus, however due to the consistent issues, with LXD and snap, I did choose to migrate to Incus.
So far my testing has gone without any issues, hence I want to start migrating the first nodes.

The first batch of Nodes that will be migrated this Weekend are Johannesburg and Valdivia.
This will be done Sunday, 19th of May, at around 20:00 GMT.

Downtime should be minimal, expected to be 10 minutes or less, since no reboot is needed.

Neoon

@Neoon said:
Maintenance Announcement

microLXC still got 3 nodes running on an older version of Ubuntu.
I will upgrade these 3 nodes next week, the Kernel version will be bumped to 5.15 afterwards.

Affected Locations
- Sandefjord
- Melbourne
- Tokyo

The System will be only rebooted once, so downtime should be minimal however expect 30-60 minutes.
Will be done next week, Saturday, 18th of May, at around 20:00 GMT.

Done.

Brueggus

@Neoon said:

@Neoon said:
Maintenance Announcement

microLXC still got 3 nodes running on an older version of Ubuntu.
I will upgrade these 3 nodes next week, the Kernel version will be bumped to 5.15 afterwards.

Affected Locations
- Sandefjord
- Melbourne
- Tokyo

The System will be only rebooted once, so downtime should be minimal however expect 30-60 minutes.
Will be done next week, Saturday, 18th of May, at around 20:00 GMT.

Done.

Could you check if the IPv6 setup in Melbourne got messed up somehow? Outgoing IPv6 works fine but incoming connections don't get through:

19. 2406:d501:f:99::                                                                                                                      0.0%    17  387.4 337.5 319.3 402.8  25.1
20. 2406:d501:f:106::3                                                                                                                    0.0%    17  358.7 335.1 319.5 375.8  18.8
21. 2402:7340:3::1                                                                                                                        5.9%    17  377.5 332.8 319.1 389.6  22.8
22. (no route to host)

Neoon

@Brueggus said:

@Neoon said:

@Neoon said:
Maintenance Announcement

microLXC still got 3 nodes running on an older version of Ubuntu.
I will upgrade these 3 nodes next week, the Kernel version will be bumped to 5.15 afterwards.

Affected Locations
- Sandefjord
- Melbourne
- Tokyo

The System will be only rebooted once, so downtime should be minimal however expect 30-60 minutes.
Will be done next week, Saturday, 18th of May, at around 20:00 GMT.

Done.

Could you check if the IPv6 setup in Melbourne got messed up somehow? Outgoing IPv6 works fine but incoming connections don't get through:

19. 2406:d501:f:99::                                                                                                                      0.0%    17  387.4 337.5 319.3 402.8  25.1
20. 2406:d501:f:106::3                                                                                                                    0.0%    17  358.7 335.1 319.5 375.8  18.8
21. 2402:7340:3::1                                                                                                                        5.9%    17  377.5 332.8 319.1 389.6  22.8
22. (no route to host)

IPv6 forwarding got disabled for some reason.
Does it work now?

Brueggus

@Neoon said: Does it work now?

Yes, it does. And maybe it has all the time. My container's IPv6 changed which I didn't notice.

Neoon

@Brueggus said:

@Neoon said: Does it work now?

Yes, it does. And maybe it has all the time. My container's IPv6 changed which I didn't notice.

You have a /64, you can set any IPv6 address within that /64 static if you want.
By default you get one allocated via DHCP6, which is based on your mac address.

However I didn't know that upgrading Ubuntu would flip the mac addresses, interesting.

Ouji

@Neoon, hi!

Thank you for the amazing work.

Do the LXC support VPN (tun devices)?

Neoon

@Ouji said:
@Neoon, hi!

Thank you for the amazing work.

Do the LXC support VPN (tun devices)?

I never used OpenVPN on LXC, so no idea.

Ouji

@Neoon said: I never used OpenVPN on LXC, so no idea.

I will try and report back, but on Proxmox you need to passthrough the TUN device for it to work (or have the container privileged).

Thanks!

sh97

@Ouji said:

@Neoon said: I never used OpenVPN on LXC, so no idea.

I will try and report back, but on Proxmox you need to passthrough the TUN device for it to work (or have the container privileged).

Thanks!

It works, I have wireguard setup on it.

Neoon

@Neoon said:
Maintenance Announcement

I mentioned a while ago once Incus becomes LTS, that microLXC will slowly migrate away from LXD.
Incus is basically a fork from LXD, which has been created a few months after Canonical took over LXD and changed the licenses.

Technically LXD still has support until 2029, so does Incus, however due to the consistent issues, with LXD and snap, I did choose to migrate to Incus.
So far my testing has gone without any issues, hence I want to start migrating the first nodes.

The first batch of Nodes that will be migrated this Weekend are Johannesburg and Valdivia.
This will be done Sunday, 19th of May, at around 20:00 GMT.

Downtime should be minimal, expected to be 10 minutes or less, since no reboot is needed.

Its done, please lemme know if you face any issues.

Neoon

@sh97 said:

@Ouji said:

@Neoon said: I never used OpenVPN on LXC, so no idea.

I will try and report back, but on Proxmox you need to passthrough the TUN device for it to work (or have the container privileged).

Thanks!

It works, I have wireguard setup on it.

Yes, wireguard works because the kernel is new enough to have the kernel module build in.

Neoon

Good news everyone, the prefix for Islamabad has been announced.
However, still no ETA on JP.

Thanks to @host_c and Virtury

host_c

@Neoon said:
Good news everyone, the prefix for Islamabad has been announced.
However, still no ETA on JP.

Thanks to @host_c and Virtury

Yeeeee!!!

carlin0

Thanks @host_c

Otus9051

offtopic, is this still a "public test"?

Neoon

@Otus9051 said:
offtopic, is this still a "public test"?

Yes, maybe at some point when everything runs on Incus and the backend is rewritten no more.

Neoon

Maintenance Announcement
Next batch for migrating to Incus.

Affected Nodes
Tokyo, Auckland, Melbourne and Groningen

Expected downtime roughly 5-10 minutes, per Node.
Will be carried out at Friday, 31th of May, at around 20:00 GMT.

Ganonk

Thank you

Neoon

@Neoon said:
Maintenance Announcement
Next batch for migrating to Incus.

Affected Nodes
Tokyo, Auckland, Melbourne and Groningen

Expected downtime roughly 5-10 minutes, per Node.
Will be carried out at Friday, 31th of May, at around 20:00 GMT.

Auckland went fine, however there have been complications with Tokyo and Melbourne, the majority of the Containers are back up running however I could not bring back up 4 containers.

Still have to figure out why, will update once I know more.

Fritz

Mine is up @Neoon

Neoon

All contains are up and running.

Neoon

Maintenance Announcement For Oradea

On June 10, 2024, we will perform node security updates and patches. These updates require a reboot of the node/physical server to be applied. The expected downtime is approximately 15 to 25 minutes per node.

During this time, your VPS will be powered down.

Operations will begin at 17:00 CET (Central European Time).

beanman109

is this where i post token still
if so
39ab-31d4-28d7-735c

Neoon

Maintenance Announcement For Oradea
Forgot to post this Yesterday.

We will conduct routing Infrastructure Upgrade and optimisations on 20-June-2024 starting at 08:00 AM untill 10:00 AM Romania, Bucharest time.

During this time, internet conectivity will be interupted ocassionally to your services.

We estimate a downtime of 10 to 30 minutes for IPV4 and 1 to 2 ours for IPV6.

Also Regarding Chile.
There has been a Network outage for roughly 6 hours, this has been resolved however the cause seems to be still unknown.

Neoon

The Deployment issue in Oradea has been fixed.
For some reason a TLS Certificate wasn't renewed by the cron.

host_c

That moment when CRON does not run

Neoon

Currently some KVM templates are broken, will look into this when I got time.
Meanwhile you can still mount netboot.xyz and install Manually if you need that specific OS.

jqr

I've been meaning to play with this. Things are slow at work, so, why not? Thanks Neoon!

c803-f6a4-1ce1-9e31

Neoon

@Neoon said:
Currently some KVM templates are broken, will look into this when I got time.
Meanwhile you can still mount netboot.xyz and install Manually if you need that specific OS.

Fixed, please lemme know if you have any issues regarding KVM deployments.

Neoon

Vilnius and Milan are now available.
Thanks to https://www.hosteroid.uk/ and https://synthohosting.net/

Neoon

@Neoon said:
Vilnius and Milan are now available.
Thanks to https://www.hosteroid.uk/ and https://synthohosting.net/

However, there seems to be an issue with the quotas.
Looks like I have to change the storage driver.

Please backup your data if you have any, I am gonna wipe the data disk tomorrow and switch the storage driver.

The Locations will be available shortly afterwards.

Neoon

Everyone that has a Container on either Milan or Vilnius has been notified.
As soon the last container has been removed, I will change the storage driver and the location will be available again shortly.

Neoon

@Neoon said:
Vilnius and Milan are now available.
Thanks to https://www.hosteroid.uk/ and https://synthohosting.net/

Available again, took a bit longer since I waited for the last confirmation.

Neoon

Restocked Vilnius.

Neoon

IPv6 connectivity issue in Milan has been fixed.

Neoon

No info about Chile though, the prefixes disappeared from the routing table entirely.
Will post here when I know more.

Brueggus

@Neoon said:
No info about Chile though, the prefixes disappeared from the routing table entirely.
Will post here when I know more.

Here's the email Zappie sent yesterday:

At about 5:50am 29th June NZST (About 3 hours prior from this notification being sent) we have noticed that there has been network distributions in our Chile facility. 

We are in communication with a datacenter tech (our upstreams) who are investigating the fault. So far we have been told that there has been power related failures in the facility

We are hoping and expect things to come back online within the next hour or so, and will continue to get updates from the upstream datacenter

Neoon

@Brueggus said:

@Neoon said:
No info about Chile though, the prefixes disappeared from the routing table entirely.
Will post here when I know more.

Here's the email Zappie sent yesterday:

At about 5:50am 29th June NZST (About 3 hours prior from this notification being sent) we have noticed that there has been network distributions in our Chile facility. 

We are in communication with a datacenter tech (our upstreams) who are investigating the fault. So far we have been told that there has been power related failures in the facility

We are hoping and expect things to come back online within the next hour or so, and will continue to get updates from the upstream datacenter

Yea he send out an email correct, I didn't noticed it because my monitoring was going off and the email went under.
Thanks for posting though.

Neoon

Restocked Milan.

Xenic

35e7-cea6-f41d-600b

nike1999

I really want a New Zealand VPS test, but unfortunately my account does not meet the requirements. Thank you anyway

Neoon

Bratislava is now available thanks to @Hosteroid
Groningen is not longer available and will be discontinued in a few weeks, replacement Node in Meppel should be up by end of the week.

Hosteroid

@Neoon said:
Bratislava is now available thanks to @Hosteroid
Groningen is not longer available and will be discontinued in a few weeks, replacement Node in Meppel should be up by end of the week.

Good luck with it!