VMware Cloud Community
Windspirit
Hot Shot
Hot Shot

Adding a new vSphere.Disk using vRO

vRA 8.9

the existing vRA Action "Add Disk" will create an Cloud.vSphere.Disk, however I need to do it via vRO. (I know I could call the API to trigger the Action etc...sure...but not what I'm after). The Libary has a Workflows called Ïnfrastructure/Disks/Create Disk" and "Infrastructure/Machines/Disks/Attach Machine Disk" and they work. They will create in the deployment a new Disk and attach it.

HOWEVER:
there are certain problems I have using the workflows:

  • Disk get created in own folder (not with the VM)
  • Attach Workflow sais that :
    • The Unit Number to be assigned (Deprecated).
    • The SCSI controller to be assigned (Deprecated).
  • Disk created is of type Cloud.Volume
  • When deploying the disk is usable and good in vSphere, HOWEVER when deleting the Deployment I get an error "Only disk with status AVAILABLE can be deleted, as it is not attached to any VM" and it deletes everything BUT the disk in the deployment. In vSphere the vmdk gets destroyed all fine.

I attached the REST return for the disks to show the difference. Any idea what REST API function the UI call triggers?

Reply
0 Kudos
1 Reply
Windspirit
Hot Shot
Hot Shot

OK..so one part I could now figure out.

The Error about the disk comes from the Attach that I run DRIECTLY after the AddDisk. But it seams that even as the Request is finished the disk is not really done and the attach does something funny. A 60sec WAIT will work wonders.

Still not clear HOW I can get a Cloud.vSphere.Disk instead of a Cloud.Volume? 

@VMware the attach wants the UnitNumber as Sting...should be a Number.

Tags (1)
Reply
0 Kudos