Add additional info about OVA deployment
This commit is contained in:
@ -32,7 +32,7 @@ Within each node, the PVC daemon is a single Python 3 program which handles all
|
||||
|
||||
The daemon uses an object-oriented approach, with most cluster objects being represented by class objects of a specific type. Each node has a full view of all cluster objects and can interact with them based on events from the cluster as needed.
|
||||
|
||||
Further information about the node daemon architecture can be found at the [daemon architecture page](/architecture/daemon).
|
||||
Further information about the node daemon manual can be found at the [daemon manual page](/manuals/daemon).
|
||||
|
||||
## Client Architecture
|
||||
|
||||
@ -58,9 +58,7 @@ The CLI client is self-documenting using the `-h`/`--help` arguments, though a s
|
||||
|
||||
The overall management, deployment, bootstrapping, and configuring of nodes is accomplished via a set of Ansible roles, found in the [`pvc-ansible` repository](https://github.com/parallelvirtualcluster/pvc-ansible), and nodes are installed via a custom installer ISO generated by the [`pvc-installer` repository](https://github.com/parallelvirtualcluster/pvc-installer). Once the cluster is set up, nodes can be added, replaced, or updated using this Ansible framework.
|
||||
|
||||
Further information about the Ansible deployment architecture can be found at the [Ansible architecture page](/architecture/ansible).
|
||||
|
||||
The Ansible configuration manual can be found at the [Ansible manual page](/manuals/ansible).
|
||||
The Ansible configuration and architecture manual can be found at the [Ansible manual page](/manuals/ansible).
|
||||
|
||||
## About the author
|
||||
|
||||
|
Reference in New Issue
Block a user