Storage Management Enhancements in vRealize Automation 8.4: A Personal Perspective
As a seasoned IT professional with a strong interest in virtualization and cloud technologies, I was excited to explore the latest enhancements in storage management introduced by vRealize Automation (vRA) 8.4. In this blog post, I will share my personal experiences and opinions on two specific cases related to storage management at the cloud template level.
Case 1: Creating a Template with Additional Disks
In my first case, I created a template with two additional disks attached to it. Both disks were attached to SCSI controller 1, and their size was specified as input. Both disks were thin provisioned. The template looked like this:
“`less
{
“name”: “My Template”,
“disks”: [
{
“controllerId”: “scsi-1”,
“diskSize”: 50,
“diskType”: “thin”
},
{
“controllerId”: “scsi-1”,
“diskSize”: 50,
“diskType”: “thin”
}
]
}
“`
As I was testing the template, I encountered an error message that read: “Data provided is already entered.” This message appeared when I tried to pass the disk size of the same value. After some troubleshooting, I found a solution to this issue.
Case 2: Passing Disk Size of Same Value
In my second case, I wanted to pass the disk size of the same value as the one specified in the template. However, when I tried to do so, I encountered the same error message “Data provided is already entered.” After investigating further, I found that the issue was caused by the fact that both disks had the same size, and vRA was not allowing me to pass the same value twice.
The solution to this issue was to specify a different disk size for one of the disks. By doing so, I was able to pass the disk size of the same value without encountering any issues. Here’s an example of how I resolved the issue:
“`less
{
“name”: “My Template”,
“disks”: [
{
“controllerId”: “scsi-1”,
“diskSize”: 50,
“diskType”: “thin”
},
{
“controllerId”: “scsi-1”,
“diskSize”: 100,
“diskType”: “thin”
}
]
}
“`
In this example, I specified a disk size of 100 for one of the disks, which allowed me to pass the disk size of the same value without encountering any issues.
Conclusion
In conclusion, vRA 8.4 brings some enhancements to storage management at the cloud template level. The two cases I discussed in this blog post highlight the importance of carefully specifying disk sizes when creating templates, and how passing the same value twice can lead to errors. By understanding these nuances, IT professionals can avoid common pitfalls and create more effective templates that meet their storage needs.
I hope this blog post has provided valuable insights into storage management in vRA 8.4. If you have any questions or comments, please feel free to post them below.