Virtual Machines

Dalet Flex is fully compatible traditional virtual machines hosting.

When on-premises, running Flex on virtual machines is probably the easiest way to leverage an existing virtualization infrastructure in place.

Dalet Flex as no particular vendor-stickiness and is fully compatible with:

  • VMware
  • Nutanix
  • Proxmox
  • QEMU/KVM
  • Xen

and probably many other technological stacks.

When on metal, there's no added-value 'as-a-service' thing one can use. Every service will come bundled within Flex application.

Requirements

A typical deployment consist of multiple virtual machines spread against as many hypervisors as possible.

The operator is solely responsible for designing and maintaining a production-grade virtualization cluster. While Dalet can make design recommendation, it is up to the customer to ensure that the setup has been done as to ensure full resilience and high-availability of the system, including network and storage resources, as to ensure hot-migration of workloads, survivability of hypervisor host in case of failure or maintenance, capacity to absorb the load and traffic, resilience of datastores in case of disk loss or deficiency.

Support Responsibility

The virtualization underlying hardware hypervisors are to be managed by the operator. Dalet will not be responsible for any hardware computing/networking/storage changes or issues which may prevent the Flex system from working.

High-Availability

Dalet Flex makes use of Virtual IPs (VIP) to manage software high-availability. Not all virtualization platforms support such a behavior by default.

Example: By default, VMware’s dvSwitch network configuration only allows VMware issued MAC addresses to be routed and consequently, the VRPP promiscuous feature must be enabled as well as authorizing non-VMware based MAC addresses.