vNIC backend deployment control

Todays networking standard on IBM PowerVM is moving towards the use of vNIC but today we lack the support to control how the SR-IOV and vNIC infrastructure is deployed using PowerVC.
Today we have deployed 2 pair of VIO (4 vios) server where each pair is maintaining network and storage traffic for Production or Non-Production systems. This works well with SEA and NPIV as
we have deployed it one different ethernet switches internaly and on the SAN side we use NPIV and connectivity groups where we control the use of the SAN adapter and VIO servers.
PMR:TS003807969

This level of control is not possible today if vNICs are used, and what we get is vNIC backing devices are deployed at random between the 4 VIO servers. This is not optimal for network switch reduandency and
network traffice isolation. So we need to be able to control the deployment of the backing devices for vNIC to specific VIO server pairs and on top of this we also need to be able to control this on a pr adapter
port level and addtionaly we need to be able to define avalibility groups so we can control our network switch redancency.

Below is an example of the setup where we have 4 vio server and 4 adapter ports. Each lpar has one production vnic with 2 backing devices. In the real world we have 3 aditional network (production, backup and application network).


------------
| T-LPAR |
------------
/ \
/ \
---------- ----------
| TVIO1 | | TVIO2 |
---------- ----------
/ \
-------------- ---------------
| ADAPT 1 P0 | | ADAPT 2 P0 |
-------------- ---------------

------------
| P-LPAR |
------------
/ \
/ \
---------- ----------
| PVIO1 | | PVIO2 |
---------- ----------
/ \
-------------- ---------------
| ADAPT 3 P0 | | ADAPT 4 P0 |
-------------- ---------------