Ok, well... I don't have the reason to use precisely Cinder. What I need is the ability to create, delete and attach data volumes to instances. As far as I know I can't do it without Cinder. If you can show me a path how to do it, and use local storages only - that would be really great
Regards, IT engineer Farheap, Russia Ivan Derbenev From: Bob Ball [mailto:bob.b...@citrix.com] Sent: Tuesday, July 14, 2015 4:58 PM To: Ivan Derbenev; openstack@lists.openstack.org Subject: RE: xenserver and cinder As I understand it Cinder provides volumes that must be accessible to VMs on any of the hosts - i.e. must be accessed over the network. Therefore if you want to use Cinder to provide data volumes (or BFV) then you need a VM/physical machine/storage array providing the actual storage which is accessible over the network. I'm not aware of a way to use Cinder create volumes that are only accessible to VMs on a single host - which is what you would need to use storage that is entirely local to the hypervisor. Just to understand, why are you trying to use Cinder backed by local storage only? What's the use case here? Bob From: Ivan Derbenev [mailto:ivan.derbe...@tech-corps.com] Sent: 14 July 2015 14:50 To: Bob Ball; openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: RE: xenserver and cinder So, do I understand it right - I can't get rid of additional layer for cinder volumes, if I want to use local storage? Regards, IT engineer Farheap, Russia Ivan Derbenev From: Bob Ball [mailto:bob.b...@citrix.com] Sent: Tuesday, July 14, 2015 12:34 PM To: Ivan Derbenev; openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: RE: xenserver and cinder Hi Ivan, XenAPINFSDriver was primarily useful for pooled scenarios (which in turn relied on Nova aggregates) - however it's not the easiest way to consume Cinder volumes. The XenServer Nova integration supports BFV and volume attach for Cinder volumes presented over iSCSI, so however those are managed by Cinder is independent of how XenServer can consume them. Even when using the deprecated XenAPINFSDriver, the storage had to be remote storage (i.e. provided to the host through an NFS server) so that does not let you use the hypervisor-local storage as block storage provisionable by Cinder and you would have needed a separate VM if you actually need your Cinder volumes to be provisioned from local storage. Bob From: Ivan Derbenev [mailto:ivan.derbe...@tech-corps.com] Sent: 13 July 2015 18:53 To: openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: [Openstack] xenserver and cinder Hello, guys! We are currently making an installation of XS6.5+OS Juno (maybe we'll switch to kilo) We have 2 servers, controller has glance, nova and keystone, and compute vms have only nova-compute installed. We use local storage on each server, not shared one (this is important) We want to implement cinder service to manage volumes easily, but i can't understand how can we do it.XenAPINFSDriver is deprecated and isn't supported any more. The only solution i found so far is to create storage VM, give it some space and use this space for cinder volumes, and then mount it in VMs as ISCSI targets. And in the same time nova uses xenAPI to create and manage volumes when it creates instances. And what i want to make is to make cinder use Xenserver volumes both when nova creates VM and when i create volume with cinder. Without second level of abstraction. Can you tell me what are the best practices to use cinder for Xenservers with local storage? Regards, Ivan Derbenev
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack