Start a Conversation



5 Posts


May 10th, 2021 14:00


In my environment we have always used non unique identifiers for LUNS, we name them according to what host they are used for, this was primarily due to them being passed through VPLEX however now that we have migrated out from behind VPLEX we have kept this naming convention.    I have been testing rest api as i want to automate LUN creation to be spawned from ServiceNow  -> Ansible Tower.  What im finding is once you put in the identifier ie vol_name if its not unique there is a chance it could either grow another existing LUN with the same name etc rather than creating a new one.  Has anyone found a way around this.  My initial thoughts are to just not use REST API, but id rather use if i can.   Has anyone done this and just added a bogus name for the initial LUN creation than rerun with new_name?

11 Posts

June 1st, 2021 07:00


Don't understand how a create new LUN operation could end up expanding an already existing LUN if they share the same volume identifier. Is that really the case?

5 Posts

June 3rd, 2021 07:00

From my testing yes, that is what i am seeing

No Events found!