- Community Home
- >
- Software
- >
- HPE OneView
- >
- pre 3.1 Volume Templates - any way to change the P...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2017 10:43 AM
тАО08-21-2017 10:43 AM
I have dozens of pre 3.1 Volume templates, which at that time did not suppport Thin DD.
Now with 3.1, Thin DD is supported. Is there a way to change the provisioning type of a pre 3.1 Vol template from Thin to ThinDD.
A pre 3.1 Vol template, Edit does not give an option to change the "provisioning" to "Thin DD"
I dont want to delete and recreate these templates in 3.1 just to change the provisioning type.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2017 03:05 PM
тАО08-23-2017 03:05 PM
SolutionThis is a defect in OneView 3.1. A fix for this is planned for the upcoming 3.10.08 patch.
OneView 3.0 volume templates upgraded to 3.1 are not getting the "Thin Deduplication" option added to them, so don't show up when editing/using the upgraded volume template. Volume templates created in OneView 3.1 are fine.
A simple fix is to delete and recreate your affected volume templates in OneView 3.1. This is what you said you didn't want to do, but i wanted to document it as an option.
You can repair your upgraded volume templates by performing the following REST operations. This assumes you are familiar with using the OneView REST api. If so, continue. If not, then you can wait for the patch or use the recreate option above.
To repair an existing OneView 3.1 volume template, perform the following using the REST client of your choice:
- Perform a GET on the URI of the volume template to repair. The URI can be seen in the OneView UI when viewing the volume template (ex. GET <host>/rest/storage-volume-templates/108a1864-4812-40f9-a875-a7d9004a4ede )
- In the reply, find the property definition below and add "Thin Deduplication" to the "enum" list as shown underlined below:
{
...
"properties": {
"provisioningType": {
"enum":[ "Thin", "Full", "Thin Deduplication"]
...
}
3. Perform a PUT of the modified reply above back to the volume template (ex. PUT <host>/rest/storage-volume-templates/108a1864-4812-40f9-a875-a7d9004a4ede )
After repair, you should be able to edit the volume template in the OneView UI, selecting among the three provisioning type values (Full, Thin, Thin Deduplication), and create volumes using the volume template.
Gary
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2017 05:07 PM
тАО08-23-2017 05:07 PM
Re: pre 3.1 Volume Templates - any way to change the Prov type ?
Gary
the REST API method is good enough until a formal fix comes via the GUI. Thanks for the solution