I have a multi-hypervisor OpenStack cloud, with kvm and lxd as the hypervisors.
I've tried to follow the comments from bug #1524297 to set this up and it's possible I've done something wrong, but juju is ignoring the virt-type constraint I specify when deploying. I can specify any value and it doesn't throw an error, and if I specify kvm as the virt type it still puts my instances on lxd hypervisors.
Here is my images/images/streams/v1/com.ubuntu.cloud-released-imagemetadata.json:
http://paste.ubuntu.com/18839128/
I used generate-metadata with the --virt-type parameter to generate the contents for one of the images, the manually added the second (due to bug #1600054 I can't use generate-image to append a second image).
It validates fine:
http://paste.ubuntu.com/18839433/
When I deploy like this I expect an error due to using an invalid constraint value:
juju deploy cs:postgresql --constraints virt-type=blah
But the unit deploys fine, to an lxd hypervisor.
When I deploy like this I expect the unit to go to kvm, but the unit still goes to lxd:
juju deploy cs:postgresql --constraints virt-type=kvm
I think my images are setup properly in glance, when I launch them they start on the right hypervisor - I used hypervisor-type=qemu for kvm and hypervisor-type=lxd for the lxd image.
I've attached machine-0.log from the controller too.
This is with 2.0 beta 11.
I can see virt coming from cli but by the time we come to add a machine, the constraint is lost...
I am working on resolution.