docs: VMO refactor

docs/docs-content/vm-management/architecture.md

@@ -14,6 +14,9 @@ on top of an existing data center or edge cluster.
 
 ![Diagram that explains the architecture behind Palette VMO.](/vm-management_architecture_vmo-architecture.webp)
 
+For more detailed information about the technical architecture of VMO, refer to
+[Palette VMO Reference Architecture](https://www.spectrocloud.com/resources/whitepaper/vmo-architecture-pdf).
+
 ## Palette VMO Components
 
 By default, Palette VMO includes the following components:

docs/docs-content/vm-management/create-manage-vm/deploy-vm-from-template.md

@@ -15,7 +15,7 @@ organization's administrator provides.
 - An active cluster with the Virtual Machine Orchestrator (VMO) pack. Review
   [Create a VMO Profile](../create-vmo-profile.md) to configure the dashboard.
 
-  - If this is an Edge cluster with VMs as Edge hosts, such as a VM in VMWare vCenter, the VM Edge host must support
+  - If this is an Edge cluster with VMs as Edge hosts, such as a VM in VMware vCenter, the VM Edge host must support
     hardware-assisted virtualization to the guest Operating System (OS).
 
 - Outbound internet connectivity for port 443 is allowed so that you and your applications can connect with the Spectro

docs/docs-content/vm-management/create-manage-vm/update-vm-configuration.md

@@ -12,7 +12,7 @@ You can add storage and additional network interfaces to your virtual machines (
 
 ## Add Disk Storage
 
-KubeVirt allows hot plugging additional storage into a running VM. Both block and file system volume types are
+KubeVirt allows hot plugging additional storage into an active VM. Both block and file system volume types are
 supported. Disks are "hot plugged" into your VMs, meaning that you do not need to power off the VM in order to add
 disks.
 

docs/docs-content/vm-management/environment-setup.md

@@ -12,25 +12,44 @@ resources.
 
 ## Hardware Resources
 
+The following sections list the hardware requirements for worker nodes and control plane nodes in a VMO cluster.
+
+### Worker Nodes
+
 Refer to the following table for the minimum and recommended hardware specifications for the worker nodes of the
 cluster.
 
-| Component            | Minimum                                            | Recommended                                        | Comments                                                                         |
-| -------------------- | -------------------------------------------------- | -------------------------------------------------- | -------------------------------------------------------------------------------- |
-| **Server**           | 2U Rackmount Chassis                               | 2U Rackmount Chassis                               | Needs to fit FC adapters and have sufficient NICs.                               |
-| **CPU**              | Intel or AMD x64 CPU with 8 cores                  | Intel or AMD x64 CPU with 8 cores                  |                                                                                  |
-| **RAM**              | 24 GB                                              | 256 GB or more                                     | Assumes the deployment of 20 VMs per node multiplied by the median RAM per VM.   |
-| **Network Adapters** | 2 x 10 Gbps <br /> (data + management)             | 2 x 10 Gbps (data) <br /> 2 x 10 Gbps (management) | Pod overlay operates on the management network.                                  |
-| **Storage Adapters** | 2 x 16 Gbps FC                                     | 2 x 16 Gbps FC                                     |                                                                                  |
-| **Disks**            | Local disk for the OS boot (SAN boot is supported) | Local disk for the OS boot                         | Boot from SAN requires special consideration due to the multipath configuration. |
+| Component            | Minimum                                                                                            | Recommended                                        | Comments                                                                                             |
+| -------------------- | -------------------------------------------------------------------------------------------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
+| **Form Factor**      | The server must fit Fiber Channel (FC) adapters and have sufficient Network Interface Cards (NIC). | 2U Rackmount Chassis                               |                                                                                                      |
+| **CPU**              | Intel or AMD x64 CPU with 8 cores                                                                  | Intel or AMD x64 CPU with 8 cores                  |                                                                                                      |
+| **RAM**              | 24 GB                                                                                              | 256 GB or more                                     | Assumes the deployment of 20 VMs per node multiplied by the median RAM per VM.                       |
+| **Network Adapters** | 2 x 10 Gbps <br /> (data + management)                                                             | 2 x 10 Gbps (data) <br /> 2 x 10 Gbps (management) | Pod overlay operates on the management network.                                                      |
+| **Storage Adapters** | 2 x 16 Gbps FC                                                                                     | 2 x 16 Gbps FC                                     | Storage adapters must support the FC protocol, a high-speed network protocol used for data transfer. |
+| **Disks**            | Local disk for the OS boot (SAN boot is supported)                                                 | Local disk for the OS boot                         | Boot from SAN requires special consideration due to the multi-path configuration.                    |
+
+### Control Plane Nodes
 
 Typically, the cluster control plane nodes do not operate any VMO workloads. As a result, they can have lighter hardware
-specifications. For example, a server with 4 cores and 8 GB RAM is sufficient for a minimum-specification control plane
-node.
+specifications in terms of CPU and RAM. For example, a server with 4 cores and 8 GB RAM is sufficient for a
+minimum-specification control plane node. The rest of the hardware requirements for control plane nodes remain the same
+as worker nodes.
+
+| Component            | Minimum                                                                                            | Recommended                                        | Comments                                                                                             |
+| -------------------- | -------------------------------------------------------------------------------------------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
+| **Form Factor**      | The server must fit Fiber Channel (FC) adapters and have sufficient Network Interface Cards (NIC). | 2U Rackmount Chassis                               |                                                                                                      |
+| **Network Adapters** | 2 x 10 Gbps <br /> (data + management)                                                             | 2 x 10 Gbps (data) <br /> 2 x 10 Gbps (management) | Pod overlay operates on the management network.                                                      |
+| **Storage Adapters** | 2 x 16 Gbps FC                                                                                     | 2 x 16 Gbps FC                                     | Storage adapters must support the FC protocol, a high-speed network protocol used for data transfer. |
+| **Disks**            | Local disk for the OS boot (SAN boot is supported)                                                 | Local disk for the OS boot                         | Boot from SAN requires special consideration due to the multi-path configuration.                    |
 
-You can increase the hardware specifications based on the total number of control plane and worker nodes you want in the
-cluster. Refer to the following table for guidance on control plane node sizing. Note that these recommendations assume
-that each cluster has at least three control plane nodes.
+The CPU and RAM requirements for control plane nodes increase with the number of worker nodes and namespaces in the
+cluster. Refer to the following table for guidance on control plane node sizing.
+
+::: warning
+
+These recommendations assume that each cluster has at least three control plane nodes.
+
+:::
 
 | Worker Nodes | Namespaces | CPU Cores | Memory (GB) |
 | ------------ | ---------- | --------- | ----------- |
@@ -111,14 +130,14 @@ also use this option. In this case, you need to adjust the configuration for **b
 tagged VLAN, we recommend using a native or untagged VLAN for PXE.
 
 The **bond_data.20** subinterface provides outbound connectivity, as it has the default gateway. This is the primary way
-to publish services from container workloads to the end users. If there are any specific data-center networks that you
+to publish services from container workloads to the end users. If there are any specific data center networks that you
 want to reach over the **bond_management.10** subinterface instead, you can configure them through static routes on the
 `172.16.0.0/22` subnet in Canonical MAAS. Those routes will be automatically applied by MAAS upon server installation.
 
 For publishing workloads from VMs, you have the following ways:
 
-- Running the VM on the pod network like containers and publishing the individual VM ports as Kubernetes services on the
-  **bond_data.20** network. In this case, you can use MetalLB to assign IP addresses.
+- Operating the VM on the pod network like containers and publishing the individual VM ports as Kubernetes services on
+  the **bond_data.20** network. In this case, you can use MetalLB to assign IP addresses.
 
 - Placing the entire VM on a VLAN and using Multus to assign the VM to a VLAN on top of the **br0** interface. In this
   case, it's the responsibility of the VM (for static IPs) or the network (for DHCP) to assign IP addresses.

docs/docs-content/vm-management/rbac/add-roles-and-role-bindings.md

@@ -14,8 +14,8 @@ You must configure permissions for actions that users can perform on Virtual Mac
 Virtual Machine Orchestrator (VMO), such as cloning, updating, and migrating VMs. You can do this by creating roles and
 cluster role bindings to determine access permissions. Refer to
 [VM User Roles and Permissions](./vm-roles-permissions.md) for a list of Cluster Roles and equivalent Palette Roles. To
-learn more about Cluster RBAC in Palette, review the
-[RBAC and NS Support](../../clusters/cluster-management/cluster-rbac.md) guide.
+learn more about role-based Access Control (RBAC) in Palette, review the
+[RBAC and Namespace Support](../../clusters/cluster-management/cluster-rbac.md) guide.
 
 ## Prerequisites
 

docs/docs-content/vm-management/rbac/rbac.md

@@ -11,6 +11,10 @@ tags: ["vmo"]
 Access to the Virtual Machines (VM) is governed by Role-Based Access Control (RBAC). You must create roles and role
 bindings and role bindings and assign them to users before they are allowed to create or manage VMs.
 
+To get started, review [VM Roles and Permissions](./vm-roles-permissions.md) and learn about the default roles and the
+available permissions. Then, refer to [Add Roles and Role Bindings](./add-roles-and-role-bindings.md) to learn how to
+assign roles and role bindings to users.
+
 ## Resources
 
 - [Add Roles and Role Bindings](./add-roles-and-role-bindings.md)

docs/docs-content/vm-management/vm-management.md

@@ -22,7 +22,7 @@ Palette VMO simplifies infrastructure management, improves resource utilization,
 
 You will benefit from Palette VMO in the following cases:
 
-- You are planning to shift from VMs to containers gradually and want to continue running both during the transition.
+- You are planning to gradually shift from VMs to containers and want to continue using both during the transition.
 
 - Your established infrastructure combines containers and VMs, and you want to manage them more effectively.
 
@@ -36,12 +36,12 @@ To get started with Palette VMO, review the [Architecture](./architecture.md) pa
 involved in enabling VMO for your infrastructure. Then, review the [Create a VMO Profile](./create-vmo-profile.md) guide
 to prepare everything you need to deploy your first VMO cluster.
 
-Once your VMO cluster is up and running, refer to the [Create and Manage VMs](./create-manage-vm/create-manage-vm.md)
+Once your VMO cluster is up and healthy, refer to the [Create and Manage VMs](./create-manage-vm/create-manage-vm.md)
 section for information on deploying VMs from existing Palette templates and performing standard VM operations.
 Alternatively, review the [Advanced Topics](./create-manage-vm/advanced-topics/advanced-topics.md) section to understand
 how you can create VM and disk templates, manage the VM resources, and perform other advanced operations.
 
-Finally, refer to the [Role-based access control (RBAC)](./rbac/rbac.md) section for information on configuring roles
+Finally, refer to the [Role-based Access Control (RBAC)](./rbac/rbac.md) section for information on configuring roles
 and permissions for your VMs.
 
 ## Resources