News, requests and patches for loang.net
 help / color / mirror / code / Atom feed
From: <mcsinyx@disroot.org>
To: <chung@loa.loang.net>
Subject: Fwd: [vpsFree.cz] Option to move VPS to node5.brq
Date: Mon, 14 Oct 2024 13:32:00 +0900	[thread overview]
Message-ID: <D4V8XATQSBSL.3C4GIO4VMMRGP@disroot.org> (raw)
In-Reply-To: <D4V8WHLUFG9L.33C3O2C6J1VSK@disroot.org>

Hello, frens,

Our provider offers to move our VPS to another node (5.brq)
which hasn't been suffering from outage like the one we are on (6.brq):

Forwarded message from vpsFree.cz on 2024-10-12 at 14:57+02:00:
> we'd like to apologize for outages of node6.brq that are plaguing us this month.
> We're working on a solution, but it may still take some time to figure it out.
>
> We can move your VPS to node5.brq if you'd like. Note that node5.brq uses cgroups v2.
> You can read more about cgroups in our knowledge base:
>
>   https://kb.vpsfree.org/manuals/vps/cgroups
>
> All distributions released in the last few years support cgroups v2. Problems
> can arise should you have some older Docker version (<20.10) that does not support
> cgroups v2 or if you're explicitly configuring cgroups v1 parameters somewhere.
> If you've never needed to know what cgroups are, then you're most likely good to go.
>
> You have the following VPS on node6.brq:
>
>   21857 brno (cgroups v2 is supported by NixOS unstable)
>
> The move can be planned on a specific day and time or during maintenance window
> configured in VPS details. Due to the cgroups change, we recommend that you check
> that everything is working as expected afterwards.
>
> Please let us know if you'd like to have your VPS moved.

I would like to proceed with this migration and let vpsFree.cz choose
whatever timeslot convenient for them.  If anyone needs any service
provided under loang.net at any specific time, please let us know
so we can tell them to avoid that window.

Your frenly pubnix admin,

~cnx

       reply	other threads:[~2024-10-14  4:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D4V8WHLUFG9L.33C3O2C6J1VSK@disroot.org>
2024-10-14  4:32 ` mcsinyx [this message]
2024-10-16  6:46   ` cnx

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D4V8XATQSBSL.3C4GIO4VMMRGP@disroot.org \
    --to=mcsinyx@disroot.org \
    --cc=chung@loa.loang.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://trong.loang.net/nixos-conf
	https://trong.loang.net/phylactery
	https://trong.loang.net/site

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).