When you update the Oracle PCA Controller Software to Release 2.3.x, the Oracle VM Manager on the management nodes is upgraded to version 3.4.x. In the next phase, you upgrade the compute nodes to the corresponding Oracle VM Server version 3.4.x as well. However, it is possible and supported to keep certain compute nodes – for example a server pool or tenant group – running at version 3.2.10 or 3.2.11, which results in a mixed environment.
In such a mixed environment, the existing configuration and the deployed virtual machines from before the Controller Software update, continue to function as before. The compute nodes that have not been upgraded, can no longer be reconfigured within Oracle VM Manager or using the Oracle PCA CLI. The following is an overview of the functional restrictions on non-upgraded compute nodes:
Unsupported Oracle PCA functionality with Oracle VM Server 3.2.x
adding a compute node to a tenant group or removing it from a tenant group
adding a compute node to a new network or removing it from a network
adding a network to a tenant group containing a non-upgraded compute node
removing a network from a tenant group containing a non-upgraded compute node
migrating a running virtual machine from an upgraded compute node to a non-upgraded compute node
Oracle VM Manager Operations supported with Oracle VM Server 3.2.x
presenting a storage repository to a compute node
presenting a storage repository to a tenant group containing a compute node
creating a new virtual machine and starting a virtual machine on a compute node
migrating a running or stopped virtual machine between non-upgraded compute nodes
migrating a running or stopped virtual machine from a non-upgraded compute node to an upgraded compute node
migrating a stopped virtual machine from an upgraded compute node to a non-upgraded compute node