Page MenuHomePhabricator

Upgrade to Debian bullseye
Open, HighPublic

Description

Current:

bots1 - 4 vCPUs, 4G RAM, 30G disk - laxhv0/node4 - IPv4 & 6
tools1  - 6 vCPUs, 4G RAM, 200G disk - lonhv0/node1 - IPv4 
db1  - 6 vCPUs, 4G RAM, 200G disk - lonhv0/node1 - IPv4
Total - 16 vCPUs, 12G Ram, 430G disk

Proposed:

bots2002 - 4 vCPUs, 4G RAM, 75G disk - UK - v6
tools2002  - 4 vCPUs, 4G RAM, 50G disk - UK - v6
db2002  - 4 vCPUs, 4G RAM, 50G disk - UK - v6
Total - 12 vCPUs, 12G Ram, 175G disk

I've looked at disk/cpu/mem usage

Update order:

  • db1 -> db2002
  • tools1 -> tools2002
  • bots1 -> bots2002

Details

Security
None

Event Timeline

RhinosF1 updated the task description. (Show Details)
RhinosF1 renamed this task from Plan for bullseye to Upgrade to Debian bullseye.May 8 2021, 1:07 PM
RhinosF1 updated the task description. (Show Details)

Will file subtasks for each as soon as it's out.

Are we planning to use AArch64 VMs for this?

In T239#4610, @RhinosF1 wrote:

Yes

In that case we need to update the proposed specs, since if you have more space you have more ram and VCPUs as well. Not to mention that the largest storage option is 72GB, while we are currently proposing larger then that for bots1.

In T239#4610, @RhinosF1 wrote:

Yes

In that case we need to update the proposed specs, since if you have more space you have more ram and VCPUs as well.

I spoke to Hampton and he said they'll be able to add custom ones.

A request for support has been created and assigned #220833.

So eth says FH doesn't offer custom specs for aarch64 vms. Honestly the v1.medium option would probably work for us for all three servers.