Go to file
Joshua Boniface c8404ecea7 Add daemon configuration reference 2019-07-28 20:27:15 -04:00
client-api Remove junk whitespace 2019-07-26 15:13:21 -04:00
client-cli Implement Ceph volume resize and rename 2019-07-26 15:13:21 -04:00
client-common Fix the same bug in a different place 2019-07-26 23:28:57 -04:00
debian Remove obsolete init attempt 2019-07-06 19:03:55 -04:00
docs Add daemon configuration reference 2019-07-28 20:27:15 -04:00
node-daemon Move intervals config one level up 2019-07-28 19:33:23 -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 Massive rejigger into single daemon 2018-10-14 02:40:54 -04:00
LICENSE Remove licence blurb for python_dhcp_server 2018-10-14 16:29:39 -04:00
README.md Fix bad replace 2019-07-07 15:36:45 -04:00
build-and-deploy.sh Add little deploy script for testing purposes 2019-06-27 14:37:42 -04:00
build-deb.sh Massive rejigger into single daemon 2018-10-14 02:40:54 -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

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