Unsolved
This post is more than 5 years old
13 Posts
0
1302
December 20th, 2016 08:00
Orchestrating Storage with ViPR (SOFO)
Hi All,
Just wanted to clear up a few things about storage orchestration with ViPR.
What I've done up till now.
1. Setting up ViPR and configuring Keystone as the Authentication provider and syncing OpenStack tenants.
2. Added the Computes as hosts in ViPR.
The storage I commission through ViPR successfully shoes up in the compute but only after I reboot the compute which is a big problem for obvious reasons, in what way can this be avoided. Secondly how to attach this volume with the instances. Do I have to create an LV and mount it on the /var/lib/instances/myinstance/ directory in the compute, Normally this is managed by cinder and frankly mounting a storage every time I spin up an instance is kind of tedious.
Am I missing something here, please let me know what can be done, any suggestion is greatly appreciated.
Best Regards
Mustafa.
Ayrton_Senna1
1 Rookie
•
62 Posts
0
December 22nd, 2016 10:00
Your question is pretty vague.
Whats the host operating system you are provisioning storage to? Is it a new build or existing host ? Whats the backend storage system ? Rescaning for a volume depends on the type of host OS. Also, HBA vendors have their own scripts to perform rescans without reboot.
I have seen in some cases with Linux hosts requiring a reboot if we present LUN with ID 0. But thats only for single LUN,remaining LUN's doesn't require reboot.
MustafaM
13 Posts
0
December 24th, 2016 03:00
1. Ubuntu 1404
2. Existing
3. EMC VPLEX
My main question is not actually about LUN discovery, rather it's about SOFO in ViPR. Normally attaching storage with computes is handled by cinder. In Storage orchestration we have to do it manually. why is it so? How are we suppose to attach a volume with an instance launched on a compute, when we have deployed ViPR in SOFO configuration?