Skip to main content

Defining Deployment Objective

Before entering the prerequisites checklist and starting the installation of PVM Plaivid, you must make a specific decision: What will this host host?

PVM Plaivid is the virtualization Core layer and is always installed first; however, products such as Inad and Fylad are deployed on this same Plaivid. Some infrastructure settings — specifically network architecture and storage space partitioning — must be determined right now, before starting to install Plaivid, based on the final product.

Warning

Why is this decision important right now? Changing the network architecture or partitioning structure after installing Plaivid is not simple or risk-free. For example, if you do not separate /var from / and later find that you need it, there is no possibility of "carving" space from / while it is in use without risking data loss. For this reason, the deployment objective must be determined before starting partitioning and network configuration, not during or after installation.

Base Physical InfrastructurePhysical Server / ESXiBase Physical InfrastructureVirtualization Core Layer (Core)PVM PlaividVirtualization Core Layer (Core)Deployed on PlaividInadDeployed on PlaividDeployed on PlaividRakaardDeployed on PlaividDeployed on PlaividFyladDeployed on PlaividDeployed on PlaividPVM DesktopDeployed on PlaividDeployed on PlaividDurkadDeployed on Plaivid

What does this decision affect?

AreaImpact of Decision
Network ArchitectureThe number and role of required physical ports differs depending on which product will run on this host (for example, Inad requires a dedicated port for Internet access which Fylad does not need).
Storage PartitioningWhether to separate the /var partition from /, and its exact capacity, depends on the final product.

Select Your Option

This host will serve as only PVM Plaivid, without installing Inad, Fylad, or any other product on it.

In this scenario:

  • There is no need to study the network architecture document of a specific product; the general network checklist in the "Prerequisites" section is sufficient.
  • In the "Standard Partition Structure" section, select the "Only Plaivid" scenario; meaning there is no need to separate /var from / and the entire remaining space is allocated to /.

You can proceed directly to the next step, namely "Pre-installation Checklist".

This host will host Inad.

Before proceeding, completely read and prepare these two documents:

  • Inad Network Architecture — Including dedicated Internet port requirement and other Inad-specific network settings
  • Inad Storage Requirements — Including suggested /var capacity for this product

:::info Reminder for the Partitioning Step When you reach the "Standard Partition Structure" section in the Storage configuration document, you must select the "Separation" scenario (i.e., create / and /var separately). :::

After preparing these two documents, return to this page and continue with the "Pre-installation Checklist" path.

This host will host Fylad.

Before proceeding, completely read and prepare these two documents:

  • Fylad Network Architecture — Network settings specific to this product
  • Fylad Storage Requirements — Including suggested /var capacity for this product
Reminder for the Partitioning Step

When you reach the "Standard Partition Structure" section in the Storage configuration document, you must select the "Separation" scenario (i.e., create / and /var separately).

After preparing these two documents, return to this page and continue with the "Pre-installation Checklist" path.

If you are still not sure what product will be installed on this host

Important Recommendation

If there is a possibility that you will add Inad or Fylad on this host in the near future, choose the "Separation" scenario right now. As explained in the basic concepts section, LVM allows you to easily add more space to /var in the future (growing forward is simple), but if you have not separated /var from the beginning, separating it from an / that is in use is practically impossible without service downtime or risk of data loss.

If in doubt, coordinate with the CloudAvid team so that the deployment objective for this host is definitively specified; guessing at this stage is not recommended.

Next Step

After selecting the appropriate path and reading the related documents (if applicable), continue to: Pre-installation Checklist.