Go to file

Joshua Boniface 080ca3201c Correct actual problem with this_node		2019-06-18 13:43:54 -04:00
client-api	Add new endpoints	2019-05-10 23:26:59 -04:00
client-cli	Ensure myhostname is short	2019-05-23 22:27:34 -04:00
client-common	Show vCPU count on CLI output	2019-06-02 22:30:26 -04:00
debian	Remove disable of pvc-flush	2019-05-23 23:47:57 -04:00
docs	Remove backup file	2019-05-30 21:59:56 -04:00
node-daemon	Correct actual problem with this_node	2019-06-18 13:43:54 -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	Minor tweaks to README appearance	2019-03-14 20:37:47 -04:00
build-deb.sh	Massive rejigger into single daemon	2018-10-14 02:40:54 -04:00
mkdocs.yml	Add documentation to project	2019-03-14 20:23:39 -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

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 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