Joshua Boniface
a6f8500309
1. Move fence monitoring to its own thread rather than doing the listing and triggering within the main keepalive thread. 2. Add a global lock key at /config/fence_lock and use this lock key to prevent multiple nodes from trying to run fences simultaneously. 3. Run the fencing monitor for each node sequentially within the context of the main fence monitoring thread, to ensure that fences of multiple nodes happen sequentially rather than in parallel. All of these should help to prevent any anomalies where one node can try to fence multiple nodes at once without recourse. |
||
|---|---|---|
| .github | ||
| .hooks | ||
| api-daemon | ||
| client-cli | ||
| daemon-common | ||
| debian | ||
| health-daemon | ||
| images | ||
| monitoring | ||
| node-daemon | ||
| worker-daemon | ||
| .bbuilder-tasks.yaml | ||
| .file-header | ||
| .flake8 | ||
| .gitignore | ||
| .version | ||
| CHANGELOG.md | ||
| LICENSE | ||
| README.md | ||
| build-and-deploy.sh | ||
| build-stable-deb.sh | ||
| build-unstable-deb.sh | ||
| bump-version | ||
| format | ||
| gen-api-doc | ||
| gen-api-migrations | ||
| gen-zk-migrations | ||
| lint | ||
| pvc.sample.conf | ||
| test-cluster.sh | ||
README.md
What is PVC?
PVC is a Linux KVM-based hyperconverged infrastructure (HCI) virtualization cluster solution that is fully Free Software, scalable, redundant, self-healing, self-managing, and designed for administrator simplicity. It is an alternative to other HCI solutions such as Ganeti, Harvester, Nutanix, and VMWare, as well as to other common virtualization stacks such as ProxMox and OpenStack.
PVC is a complete HCI solution, built from well-known and well-trusted Free Software tools, to assist an administrator in creating and managing a cluster of servers to run virtual machines, as well as self-managing several important aspects including storage failover, node failure and recovery, virtual machine failure and recovery, and network plumbing. It is designed to act consistently, reliably, and unobtrusively, letting the administrator concentrate on more important things.
PVC is highly scalable. From a minimum (production) node count of 3, up to 12 or more, and supporting many dozens of VMs, PVC scales along with your workload and requirements. Deploy a cluster once and grow it as your needs expand.
As a consequence of its features, PVC makes administrating very high-uptime VMs extremely easy, featuring VM live migration, built-in always-enabled shared storage with transparent multi-node replication, and consistent network plumbing throughout the cluster. Nodes can also be seamlessly removed from or added to service, with zero VM downtime, to facilitate maintenance, upgrades, or other work.
PVC also features an optional, fully customizable VM provisioning framework, designed to automate and simplify VM deployments using custom provisioning profiles, scripts, and CloudInit userdata API support.
Installation of PVC is accomplished by two main components: a Node installer ISO which creates on-demand installer ISOs, and an Ansible role framework to configure, bootstrap, and administrate the nodes. Installation can also be fully automated with a companion cluster bootstrapping system. Once up, the cluster is managed via an HTTP REST API, accessible via a Python Click CLI client or WebUI (eventually).
Just give it physical servers, and it will run your VMs without you having to think about it, all in just an hour or two of setup time.
Getting Started
To get started with PVC, please see the About page for general information about the project, and the Getting Started page for details on configuring your first cluster.
Changelog
View the changelog in CHANGELOG.md. Please note that any breaking changes are announced here; ensure you read the changelog before upgrading!
Screenshots
These screenshots show some of the available functionality of the PVC system and CLI as of PVC v0.9.85.
The CLI features an integrated, fully-featured help system to show details about every possible command.
A single CLI instance can manage multiple clusters, including a quick detail view, and will default to a "local" connection if an "/etc/pvc/pvc.conf" file is found; sensitive API keys are hidden by default.
PVC can show the key details of your cluster at a glance, including health, persistent fault events, and key resources; the CLI can output both in pretty human format and JSON for easier machine parsing in scripts.
PVC can show details about the nodes in the cluster, including their live health and resource utilization.
PVC can show details about the VMs in the cluster, including their state, resource allocations, current hosting node, and metadata.
In addition to the above basic details, PVC can also show extensive information about a running VM's devices and other resource utilization.
PVC has two major client network types, and ensures a consistent configuration of client networks across the entire cluster; managed networks can feature DHCP, DNS, firewall, and other functionality including DHCP reservations.
PVC provides a convenient abstracted view of the underlying Ceph system and can manage all core aspects of it.
PVC can display logs from VM serial consoles (if properly configured) and nodes in-client to facilitate quick troubleshooting.
PVC provides full VM lifecycle management, as well as long-running worker-based commands (in this example, clearing a VM's storage locks).
PVC features an extensively customizable and configurable VM provisioner system, including EC2-compatible CloudInit support, allowing you to define flexible VM profiles and provision new VMs with a single command.
PVC features several monitoring integration examples under "node-daemon/monitoring", including CheckMK, Munin, and, most recently, Prometheus, including an example Grafana dashboard for cluster monitoring and alerting.