Posts

Hello! I am CK notes, an IT systems engineer documenting real-world datacenter experience, infrastructure engineering, and everyday life. This first post introduces why I started this blog, the meaning behind ‘CK notes’, and the topics I plan to cover. 💡 Why the name ‘CK notes’? When looking at the blog address or title, you might have initially thought of the fashion brand (Calvin Klein). 😄 However, CK notes carries a sincere engineering purpose: ...

When delivering an HPE SimpliVity with VME (VM Essentials) 2-node cluster to an enterprise customer, you will almost invariably hear the client’s IT team request: “Please just host the Arbiter VM directly on the newly delivered SimpliVity nodes.” To an experienced systems engineer, this request highlights two critical architectural and commercial dilemmas. 1. The Field Dilemmas: Chicken-and-Egg & The Licensing Trap Dilemma 1: The Arbiter Must Exist Before SimpliVity Storage is Created A 2-node SimpliVity cluster requires active network communication with an Arbiter IP before the cluster creation wizard can even begin. If the SimpliVity nodes haven’t been initialized and no storage pool exists, where can you run the Arbiter VM? It is a classic chicken-and-egg paradox. ...

1. Overview HPE SimpliVity is a solution that provides integrated computing, storage, and network based on hyperconverged infrastructure (HCI). The storage architecture is based on RAID + RAIN structure andNFS protocol, and VMware-based SimpliVity and VME have similarities and differences. 2. Storage architecture core composition 1) RAID + RAIN structure RAID (Local): Configure RAID inside each node to prepare for disk failure RAIN (Cluster): Data replication to other nodes in the cluster → Data integrity is guaranteed even when node failures Double protection structure ensures high level of high availability (HA) 2) NFS protocol based data store Use NFS datastore in a VMware ESXi or VME environment OmniStack (based on VMware) or VME software virtualizes local storage to provide a logical pool of storage Virtual machines (VMs) operate reliably through this NFS datastore. 3) Data efficiency Reduce storage space through **Deduplication **+Compression technology Provides built-in backup and recovery functions → Self-DR (disaster recovery) possible without external storage 3. VMware-based SimpliVity vs HPE SimpliVity VME comparison table item SimpliVity on VMware HPE SimpliVity VME Storage Protocol NFS-based NFS-based How data is protected RAID + RAIN + OmniStack Acceleration Card RAID + RAIN (Software Defined) Hardware Dependencies OmniStack Accelerator Card required No additional hardware required, based on standard x86 servers Management Platform VMware vCenter integration VME Manager + Morpheus (can be managed simultaneously with VMware) Scalability Expandable by adding nodes Equally node-based scalability Backup/Restore Built-in features provided Provides the same built-in features Cost Structure VMware License + OmniStack Card Cost Socket-based licensing (up to 70% savings compared to VMware) 4. Additional advantages of VME architecture Hardware simplification: Reduce points of failure and ease maintenance by eliminating OmniStack cards Software-defined approach: Utilizes the latest OS (based on Ubuntu) and open source technology to improve flexibility and update speed IPv6 and modern network support: Optimized for next-generation network environments Management efficiency: Morpheus integration provides a hybrid operating environment that can manage VMware and VME simultaneously Cloud-friendliness: Enhanced on-premises + cloud scalability through HPE GreenLake integration 5. Key takeaways Common features: RAID + RAIN structure, NFS protocol-based datastore, built-in backup/recovery function Difference: VMware-based requires OmniStack card, VME is software-defined for greater simplicity and cost-effectiveness 6. Reference sources HPE SimpliVity official product page HPE VME Release Notes Documentation HPE InfoSight Solutions Guide

1. Solution Overview HPE SimpliVity VME (Virtual Machine Essentials) is an enterprise virtualization platform based on hyperconverged infrastructure (HCI) that integrates compute, storage, and networking into a unified architecture to reduce operational complexity while delivering high availability and data efficiency. By eliminating the overhead of traditional 3-tier architectures (discrete servers, SAN switches, and external storage arrays), it combines a lightweight KVM-based virtualization layer with the HPE OmniStack Virtual Controller (OVC) to streamline on-premises infrastructure. ...

1. Overview VMware has long led the market with its enterprise-class virtualization platform, and HPE VME (HPE Virtual Machine Essentials) is a hyperconverged solution that emphasizes cost-effectiveness and simplicity. The two platforms have differentiated strengths in purpose and functionality. 2. Key Differences 1) Architecture and underlying technology VMware vSphere: Based on ESXi hypervisor, provides advanced VM management features HPE VME: KVM-based, HPE ProLiant servers + Ubuntu OS, Morpheus platform allows simultaneous management with VMware 2) Management and integration VMware: vCenter-centric management, strong integration with VMware ecosystem (NSX, vSAN) HPE VME: Single management console (VME Manager), HPE GreenLake and Morpheus integration, multi-hypervisor support 3) Cost structure VMware: Core-based licensing → increased costs, policy changes after Broadcom acquisition HPE VME: Socket-based licensing → Simple and predictable, resulting in up to 70% cost savings 4) Functional differences VMware: Provides advanced features such as vMotion, DRS, SR-IOV, etc. HPE VME: Built-in backup/recovery, data deduplication/compression, emphasis on simplicity (NSX-level network automation not supported) 5) Scalability and flexibility VMware: Rich hardware compatibility, enhanced cloud native and container integration HPE VME: Cloud expansion based on HPE GreenLake, enabling rapid deployment 3. Comparison table item VMware vSphere HPE VME (VM Essentials) Hypervisor ESXi KVM-based Management Platform vCenter VME Manager + Morpheus Integrity VMware ecosystem (NSX, vSAN) HPE GreenLake can simultaneously manage VMware License Core-based (increased cost) Socket-based (predictable, cost-saving) Advanced Features vMotion, DRS, SR-IOV, etc. Backup/recovery, deduplication/compression (emphasis on simplicity) Scalability Diverse hardware, cloud native Based on HPE ProLiant, GreenLake scalable Cost Effectiveness relatively high Up to 70% savings possible 4. Key takeaways VMware: Strengths in enterprise-class features and ecosystem integration, but burdened by cost and complexity HPE VME: Simplicity, cost-effectiveness, strength in hybrid management, and coexistence with VMware environments 5. Reference sources HPE Official Site – Introduction to VME VMware vSphere product page HPE VME vs VMware comparison review