Hyper-converged infrastructure “HCI”

Software-defined, virtualizes all elements of systems. Hypervisor
Software defined storage
Software defined networking
COTS commercial off –the-shelf servers

The primary difference between converged infrastructure and hyperconverged infrastructure is that in HCI both the storage area network and the underlying storage abstractions[clarification needed] are implemented virtually in software (at or via the hypervisor) rather than physically in hardware

Because software-defined elements are implemented in the context of the hypervisor, management of all resources can be federated (shared) across all instances of a hyper-converged infrastructure.

Converged Infrastructure
IT organizations use converged infrastructure to centralize the management of IT resources, to consolidate systems, to increase resource-utilization rates, and to lower costs. Converged infrastructures foster these objectives by implementing pools of computers, storage and networking resources that can be shared by multiple applications and managed in a collective manner using policy-driven processes.

IT vendors and IT industry analysts use various terms to describe the concept of a converged infrastructure. These include "converged system", "unified computing", "fabric-based computing", and "dynamic infrastructure".

A converged infrastructure addresses the problem of siloed architectures and IT sprawl by pooling and sharing IT resources. Rather than dedicating a set of resources to a particular computing technology, application or line of business, converged infrastructure creates a pool of virtualized servers, storage and networking capacity that is shared by multiple applications and lines of business.
Proxmox
is an open-source virtualization platform, allowing deployment and managment of vm’s and containers
The kernel-mode component of KVM is a part of the Linux kernel, itself licensed under GNU General Public License, version 2.
Based on Ubuntu LTS kernel

Two types
Container-based with LXC
Full virtualization with KVM


KVM
(Kernel-based VM) Is a virtualization module in the Linux kernel allowing the kernel to function as a hypervisor.

It requires a CPU with hardware virtualization extensions (intel vt, amd-v)

It exposes the /dev/kvm interface, which a user mode host can then use to:
Set up the guest VM's address space. The host must also supply a firmware image (usually a custom BIOS when emulating PCs) that the guest can use to bootstrap into its main OS.

Feed the guest simulated I/O.

Map the guest's video display back onto the system host.
There are numerous Virtual Machine Monitors (VMMs) which can utilise the KVM interface including kvmtool, crosvm and Firecracker and numerous specialised VMMs built with frameworks such as rust-vmm.

Internally, KVM uses SeaBIOS as an open source implementation of a 16-bit x86 BIOS.

KVM itself emulates very little hardware, instead deferring to a higher level client application such as QEMU, crosvm, or Firecracker for device emulation.

KVM provides the following (2) emulated devices:
--Virtual CPU and memory
--VirtIO

wikipedia.org/wiki/Hyper-converged_infrastructure
wikipedia.org/wiki/Proxmox_Virtual_Environment

Accessibility
 --overview

API
 --REST best practices
 --REST demo
 --REST vs RPC
 --Wikipedia API

Blockchain
 --overview

Blog
 --The 'Brute Force' Mistake
 --The Bezosian Protocol: Eliminating Learned Helplessness
 --The Humility Protocol: Reality Over Reputation
 --The Jobsian Protocol: Systems Analysis as a War on Entropy
 --The Jordan Framework: Engineering a Competitive Edge
 --Time Management as an Operational System: The Tracy Framework
 --Tracy on Goals: Vector Alignment & Execution

Cloud
 --AWS overview

CSS/HTML
 --Admissions Portal Simulation Lab
 --Bootstrap carousel
 --Grid demo
 --markdown demo

DevOps
 --Agile Principles
 --DevOps overview
 --Drupal, containerized
 --Prometheus & Grafana
 --RKE2: Deploying the Rancher Kubernetes Engine

Encoding
 --Overview

Ergonomics
 --Desk configuration
 --Device fleet
 --Input device array
 --keystroke mechanics
 --Phones & RSI

ERP
 --Anthology overview
 --Ellucian Banner
 --Higher Ed ERP Simulation Lab
 --PeopleSoft Campus Solutions
 --PESC standards
 --Slate data model

Git
 --Authoring & Deploying the Post-Receive Hook
 --Pipeline Optimization, Web-Root Migration, & Dependency Remediation
 --syntax overview
 --troubleshooting libcrypto

Hardware
 --Device fleet
 --Electricity fundamentals
 --Homelab diagram

Identity & Access
 --Automating Enterprise IAM Lifecycles
 --Deploying Entra Connect
 --Foundations
 --OIDC Integration
 --Provisioning Okta Dev Tenant

Java
 --Fundamentals

Javascript
 --Advanced Interaction: jQuery & UI Frameworks
 --input prompt demo
 --misc demo
 --Time and Date functions
 --Vue demo

Linux
 --Auditing the live interface state using ethtool
 --grep demo
 --HCI and Proxmox
 --Persistent Infrastructure Telemetry: TMUX
 --Proxmox install
 --xammp ftp server

Mail flow
 --DKIM, SPF, DMARC
 --MAPI

Microsoft
 --AZ-800: Administering Windows Server Hybrid Core Infrastructure
 --BAT scripting
 --Group Policy
 --IIS
 --robocopy
 --Server 2022 setup - Virtualbox

Misc
 --Applications
 --Computer Science Foundations
 --Field Notes: RainPoint Bluetooth Hose Timer
 --Protocols, TLS & Distributed Scale
 --regex
 --Resources
 --Runtimes, ASTs & Data Structures
 --Sustainable Computing
 --Terminology
 --Tribute to Computer Scientists

Networks
 --BGP Peering & Security Hardening Lab
 --CCNA Lammle Study Guide
 --Cisco 1921/K9 router
 --NGFW vs. Legacy
 --routing protocols
 --throughput calculations

PHP/SQL
 --Cookies
 --database interaction
 --demo, OSI Layers quiz
 --Foreign key constraint demo
 --fundamentals
 --MySQL and PHPmyAdmin setup
 --pagination
 --security
 --session variables
 --SQL fundamentals
 --structures
 --Tables display

Python
 --fundamentals

Security
 --Kerberos: Protocol Architecture
 --NTP Overview
 --Overview- GRC (Governance, Risk, and Compliance)
 --Security Blog
 --SSH fundamentals

Serialization
 --JSON demo
 --YAML demo