Create a new hypervisor with bhyve as host for our FreeBSD VMs.
Requirements for order fulfillment:
- RAM. If we look at hyper-001 RAM, 72 Gb of the 128 Gb (48+24) are assigned to the Docker engines, all the remaining RAM are for FreeBSD production VMs. In the current pricing situation, that makes a 64 Gb server clearly acceptable.
- Network / provider. The public IP address for the mail server works well; it's an OVH IPFO, that means we need a OVH server. Take a product compatible with vRack. If we can't meet this criteria, the mail server can stay on hyper-001 too.
Requirements for provisionning:
- evaluate how to create router-004 / router-005 VMs, in blue/green deployment mode or CARP
- establish a IP migration plan
- scenario I. Assign a new IP block for all FreeBSD VM: 172.27.27.96/27 (delete on NetBox 172.27.27.96/28 and 172.27.27.112/28, to merge into /27)
- scenario II. Assign a new IP block for Dwellers / docker-002, keep VMs on hyper-002 on 172.27.27.0/27
- link routers on hyper-001 and hyper-002, ideally through the vRack, at worst by GRE tunnel
- evaluate how to work with ZFS in an optimal way: we NEED zfs AND on host AND on guests (heavy use of snapshots)
Ref T1938 for migration ESXi -> bhyve