This post is more than 5 years old
10 Posts
0
2207
ViPR Controller - Block volume ingest question
Hi All,
I have a question regarding the block volume ingestion service on ViPR Controller.
If a Volume is created in ViPR, but the masking and zoning is done manually outside of ViPR (using native element managers)(ViPR-c therefore has no knowledge of the volume masking), will this volume appear in the list of volumes that we can ingest after we run the "Discover Unmanaged Volumes" service in the Service catalogue?
I think that ViPR-C will not find volume as an unmanaged volume. However don't have a test ViPR-C environment to test this out.
Thanks in advance,
Luke
sathyaprakash.mohandass
41 Posts
0
May 5th, 2017 08:00
Hi All,
To my understanding. In this scenario, the virtual volume would be a known or managed volume for ViPR. But the storage-view is a unmanaged storage-view. So, the corresponding exportgroup would have not been created in ViPR. Once you do a discover unmanaged volumes, ViPR is going to discover the storage-views which does not have "no_vipr" in it and create corresponding exportgroup in ViPR. You should be able to Ingest the volume after that. This is my understanding and even I don't have a test environment. Let us know if works the same way.
Thanks,
Sathya
Velik1
36 Posts
1
May 4th, 2017 07:00
If your question is about "how can I ingest a volume in that predicament", the recommendation is to delete the volume from inventory using Service Catalog - Block Storage Services - Remove Volume and Associated Exports (ensure you pick deletion from Inventory option), and then run Discovery Unmanaged Volumes, followed up Ingest Exported UnManaged Volumes
kernelzilla
17 Posts
1
May 4th, 2017 07:00
Hi Luke!
In the scenario you described, the volume would appear in the list of volumes for ingestion in the 'Ingest Exported Unmanaged Volumes' service catalog option after performing a fresh Unmanaged Volume discovery. The volume would appear in this list until all unmanaged export masks have been ingested.
Also, keep in mind that ViPR does not ingest zones when ingesting the volumes. If the volume is unexported and deleted via ViPR GUI after ingestion, the zones would still remain on the fabric and would need to be manually cleared.
Hope this helps!
Patrick
llittlefield
10 Posts
0
May 4th, 2017 16:00
Hi All,
Thanks for the reply. It seems there are two different views here, so I am not too sure what is going to work.
Patrick - from your answer it seems that ViPR-C is able to ingest an export mask for a volume that it already knows about because it was created in ViPR-C. Is that correct?
Thank you,
Luke
Velik1
36 Posts
0
May 5th, 2017 07:00
different perspectives. similar views.
llittlefield
10 Posts
0
May 7th, 2017 17:00
Hi All,
Thanks for the replies. Sounds like we will be able to ingest the volume in this scenario. If I get a chance to test it I will let you know (but I'm not sure that I will).
Thanks!
Luke