Joshua Boniface
b17b7bf22b
This particular arping interval/count, along with forcing it to run in the foreground, seems to minimize the packet loss when the primary coordinator transitions. Through extensive testing, this value results in the, consistently, least amount of loss: 1-2 pings, at an 0.025s ping interval, return "TTL exceeded", with no other loss, and only when the node the test VM is on is the one switching to secondary state. No other combination of values here, nor tweaks to other parts of the code, seem able to reduce this further, therefore this is likely the best configuration possible. |
||
---|---|---|
client-api | ||
client-cli | ||
client-common | ||
debian | ||
docs | ||
node-daemon | ||
.file-header | ||
.gitignore | ||
.gitlab-ci.yml | ||
LICENSE | ||
README.md | ||
build-and-deploy.sh | ||
build-deb.sh | ||
mkdocs.yml | ||
pvc_logo.svg |
README.md
PVC - The Parallel Virtual Cluster suite
PVC is a suite of Python 3 tools to manage virtualized clusters. It provides a fully-functional private cloud based on four key principles:
- Be Free Software Forever (or Bust)
- Be Opinionated and Efficient and Pick The Best Software
- Be Scalable and Redundant but Not Hyperscale
- Be Simple To Use, Configure, and Maintain
It is designed to be an administrator-friendly but extremely powerful and rich modern private cloud system, but without the feature bloat and complexity of tools like OpenStack. With PVC, an administrator can provision, manage, and update a cluster of dozens or more hypervisors running thousands of VMs using a simple CLI tool, HTTP API, or [eventually] web interface. PVC is based entirely on Debian GNU/Linux and Free-and-Open-Source tools, providing the glue to bootstrap, provision and manage the cluster, then getting out of the administrators' way.
Your cloud, the best way; just add physical servers.