Thanks Thomas,
What I'm trying to achieve is the following :
To be able to create a VM on a host (that's a compute and volume host at
the same time) then call cinder and let it find the host and create and
attach volumes there.
I guess the biggest problem is to be able to identify the host, as you
said the host_id is of little use here. Unless I try to query the nova
api as admin and get a list of hypervisors and their vms. But then I'll
have to match the nova host name with the cinder host name.
Any thoughts on this ? Is there any blueprint for attaching local
volumes in cinder ?
Thanks,
Abbass,
On 07/16/2014 05:44 PM, [email protected] wrote:
So I see a couple of issues here:
1) reliability - need to decide what the scheduler does if the nova
api isn't responding - hanging and ignoring future scheduling requests
is not a good option... a timeout and putting the volume into error
might be fine.
2) Nova doesn't expose hostname as identifiers unless I'm mistaken, it
exposes some abstract host_id. Need to figure out the mapping between
those and cinder backends.
With those to caveats in mind, I don't see why not, nor indeed any
other way of solving the problem unless / until the
grand-unified-sheduler-of-everything happens.
Starting a cinder spec on the subject might be the best place to
collect people's thoughts?
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
