Transitioning From VMware
Overview
- KorGrid runs on top of a unified hyperconverged platform combining compute, storage, and network.
- Unlike VMware's modular ecosystem, our hypervisor operates as a single OS with built-in redundancy.
- This guide maps VMware concepts to our platform's equivalents to ease your migration.
If you’re a VMware user considering a shift to KorGrid, this guide will help you understand the differences in architecture, terminology, and workflows. VMware’s vSphere and ESXi provide a robust virtualization platform, often paired with vSAN, NSX, or vCenter for storage, networking, and management. KorGrid, however, integrates these capabilities into a single, software-defined data center operating system. This document outlines the key distinctions and offers practical steps to migrate your VMware workloads.
Prerequisites
- Familiarity with VMware vSphere, ESXi, and optionally vSAN or NSX.
- A backup of your VMware VMs and configurations before migration.
Key Differences
Architecture
Aspect | VMware (vSphere/ESXi) | KorGrid |
|---|---|---|
Core Design | Separate hypervisor (ESXi) with optional vCenter for management. Add-ons like vSAN and NSX extend functionality. | Single OS integrating virtualization, storage (vSAN), and networking. No separate management layer required. |
Deployment | Install ESXi on bare metal, then configure vCenter, vSAN, etc., separately. | OS on nodes, creating a unified system from the start. |
Scalability | Scale compute and storage independently with additional licenses (e.g., vSAN). | Scale-out with nodes (compute, storage, or both) within a single vSAN instance. |
Multi-Tenancy | Limited native multi-tenancy; requires vCloud Director or manual segmentation. | Built-in nested multi-tenancy with isolated tenants and sub-tenants. |
Takeaway: Our platform eliminates the need for separate components like vCenter or NSX by embedding everything into one system, simplifying deployment and management.
Terminology
VMware Term | KorGrid Term | Notes |
|---|---|---|
ESXi Host | Node | A physical server or VDC. |
vCenter | KorGrid UI | The web-based UI runs on controller nodes (Node 1 & 2) for system-wide management. |
Cluster | Cluster | Groups of nodes with similar hardware. |
vSAN | vSAN | vSAN is integral, pooling storage across all nodes automatically. |
Datastore | vSAN Storage Tiers | KorGrid organizes storage into tiers within the vSAN. |
Virtual Switch | Fabric Physical Network | KorGrid presents the physical network uplinks across multiple nodes into a logical switch that is referred to as a "Physical Network". |
VM | VM | Virtual Machines are a similar concept. |
dvPortGroup | Fabric External Network | Virtual Networks that can represent a Layer 2 Network (e.g. a VLAN) that a VM can have its vNIC on. Can also do Layer 3 services (routing, DNS, DHCP, BGP/OSPF, VPN) |
Resource Pool | Tenant | Tenants are isolated virtual data centers with their own resources and management. |
Takeaway: While some terms overlap (e.g., VM, vSAN), concepts like “Tenants” and “Internal Networks” offer more integrated and flexible options than VMware equivalents.
Networking
Feature | VMware | KorGrid |
|---|---|---|
Networking | vSphere Distributed Switch or Standard Switch; NSX for advanced features. | Built-in layer 2/3 networking with Core Fabric and External Networks. |
VLANs | Configured via virtual switches. | Configured on Physical Networks or Internal Networks. |
Redundancy | NIC teaming or LACP on switches. | Core Fabric Networks (dedicated L2) and bonded External Networks. |
Key Difference: KorGrid runs jumbo frames (MTU 9192) on Core Fabric Networks for vSAN and node communication, unlike VMware’s optional jumbo frame support.
Storage
- VMware: vSAN is an optional add-on requiring specific licensing and configuration. Datastores are managed separately.
- KorGrid: vSAN is the default storage system, pooling all node drives into tiers. No separate datastore creation is needed, storage is automatically available to VMs and tenants.
Migration Tip: Export VMware VMs as OVF/OVA files.
Management
- VMware: vCenter provides a centralized UI, with command-line options via PowerCLI.
- KorGrid: A web UI runs on Controller Nodes, with API access for automation.
Takeaway: KorGrid's UI is more lightweight and always available, avoiding the need for a separate vCenter VM or appliance.