VRA 8.6 and vSphere 6.7 U3 SDRS

 

We completed our homework related to SDRS testing with vRA8.Testing was performed on vRA8 DEV env and in our DEV vCenter, we have dedicated storage cluster with 2x5TB LUNs with SDRS set up to full auto. Both advance properties VraInitPlacement and VraExpandDisk are set to 1. Same storage cluster is used for vRA7 deployments where everything works as expected.

 

There are 3 scenarios as we discussed, here are the results:

1)      Standard SDRS placement

More scenarios was tested.

a)       There was only 400GB per LUN free space remaining. Single machine requested with 70GB OS disk and 2x 350GB data.

b)      300GB free space on one LUN, 500GB free space on another. Single machine requested with 70GB OS disk and 2x 350GB data. Some files were moved for LUN with 300GB free space to be able store 350GB drive.

Placement from vCenter(no vRA) directly

Placement from vRA8

Result: Passed. Both worked as expected.

 

2)      Multi deployment

More deployments in single request to verify if the same recommendation is used for both. 2 machines with 70GB OS drive and 350GB data drive. 500GB of free space on both LUNs.

One machine was deployed successfully, second one failed with error: Provisioning operation failed. Error from vCenter: Insufficient disk space on datastore 'LID021_001'.

Result: Failed. Seems that same recommendation was passed to both deployments. Deployments are from single request, but separate in vRA and they were approved almost in the same time.

 

3)      Existing drive extension

Extension of data drive with not enough space for extension on LUN. On both LUNs was 200GB free space. Existing 350GB drive was requested to be extended about 300GB. Expectation was that some files from LUN where data drive is located will be moved to second one.

Result: Failed. No files were moved to have enough space for extension on affected LUN. Action failed with there is not enough space on LUN.

 

Seems vRA8 doesn’t use by default property(VirtualMachine.Admin.Datastore.Cluster.ResourceLeaseDurationSec 3600) necessary to utilize properties set up on vCenter. Is it possible to define it somewhere in blueprint (as on 7) or inject in request?