Go to file
Joshua Boniface 01c8986381 Update help messages in meta command 2019-10-12 02:08:52 -04:00
client-api Use build-in selector and respect limits in client 2019-10-12 01:45:44 -04:00
client-cli Update help messages in meta command 2019-10-12 02:08:52 -04:00
client-common Fix minor bugs 2019-10-12 02:03:23 -04:00
debian Bump version to 0.5 2019-08-08 20:56:27 -04:00
docs Implement VM metadata and use it 2019-10-12 01:17:39 -04:00
node-daemon Use node instead of hypervisor consistently 2019-10-12 01:59:08 -04:00
.file-header Add file header template 2018-09-10 01:19:08 -04:00
.gitignore Ignore swap files 2018-06-18 21:26:36 -04:00
.gitlab-ci.yml Correct artifact location 2019-08-20 09:40:18 -04:00
LICENSE Remove licence blurb for python_dhcp_server 2018-10-14 16:29:39 -04:00
README.md Update README badges 2019-08-08 20:48:28 -04:00
build-and-deploy.sh Build with sudo too, if needed 2019-09-07 12:32:21 -04:00
build-deb.sh Bump version to 0.5 2019-08-08 20:56:27 -04:00
mkdocs.yml Revert "Add material theme to docs" 2019-07-10 15:23:26 -04:00
pvc_logo.svg A few more tweaks 2018-06-06 02:43:34 -04:00

README.md

PVC - The Parallel Virtual Cluster suite

Logo banner

License Release Pipeline Status Documentation Status

PVC is a suite of Python 3 tools to manage virtualized clusters. It provides a fully-functional private cloud based on four key principles:

  1. Be Free Software Forever (or Bust)
  2. Be Opinionated and Efficient and Pick The Best Software
  3. Be Scalable and Redundant but Not Hyperscale
  4. 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.

See the documentation here