Jay,
Thanks for that info. It appears that the cinder-volume service can speak to the SolidFire over the network but for some reason it can't actually access it over iSCSI. I think it might be something to do with how we are tagging / untagging VLANs.
Thank you for your help, I think I am heading in the right direction now!
Kind Regards,
Grant
Grant,
Doing the boot from volume is actually quite different than attaching a volume to an instance.
In the case that you are doing the boot from volume (assuming that your glance storage is not in the Solidfire) the volume is created and attached to where the cinder-volume service is running. Then the image is written into the volume.
Have you verified that the host and container that is running cinder-volume is able to access the Solidfire backend?
Jay
On 1/11/2019 4:45 AM, Grant Morley wrote:
Hi Jay,
Thanks for the tip there. I am still having some trouble with it which is really annoying. The strange thing is, I can launch a volume and attach it to an instance absolutely fine. The only issue I am having is literally creating this bootable volume.
I assume creating a volume and attaching it to an instance is exactly the same as creating a bootable volume minus the Nova part?
I would just expect nothing to work if nothing could speak to the SolidFire.
Would it make a difference if the current image that is being copied over to the bootable volume is in a ceph cluster? I know glance should deal with it but I am wondering if the copy of the image is the actual issue?
Thanks again,
On 11/01/2019 00:10, Jay S. Bryant wrote:
Grant,
So, the copy is failing because it can't find the volume to copy the image into.
I would check the host and container for any iSCSI errors as well as the backend. It appears that something is going wrong when attempting to temporarily attach the volume to write the image into it.
Jay
On 1/10/2019 7:16 AM, Grant Morley wrote:
Hi all,
We are in the process of trying to add a SolidFire storage solution to our existing OpenStack setup and seem to have hit a snag with cinder / iscsi.
We are trying to create a bootable volume to allow us to launch an instance from it, but we are getting some errors in our cinder-volumes containers that seem to suggest they can't connect to iscsi although the volume seems to create fine on the SolidFire node.
The command we are running is:
openstack volume create --image $image-id --size 20 --bootable --type solidfire sf-volume-v12
The volume seems to create on SolidFire but I then see these errors in the "cinder-volume.log"
The volume containers can talk to the iscsi VIP on the SolidFire so I am a bit stuck and wondered if anyone had come across any issues before?
Kind Regards,
--
Grant MorleyCloud LeadAbsolute DevOps Ltd
Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP--
Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP