Expand hypervisor_type meta data with Virtuozzo hypervisor

Virtuozzo hypervisor reports itself as 'vz' hypervisor, and it
was supported as libvirt virt type since Kilo. Let's expand
image metadata so that it will possible to filter out compute nodes,
which don't support images requiring hypervisor_type=vz

Lite-Spec-Id: I6ba0fcf670aecddde95cfdc6850cdb751dec2058

Change-Id: I51afacf83655107a6c4e4c226623fa360bdafca2
This commit is contained in:
Maxim Nestratov 2016-07-11 22:38:51 +03:00
parent 04b3339fac
commit cac2fc67ec
2 changed files with 11 additions and 1 deletions

View File

@ -12,7 +12,7 @@
"properties": {
"hypervisor_type": {
"title": "Hypervisor Type",
"description": "Hypervisor type required by the image. Used with the ImagePropertiesFilter. \n\n KVM - Kernel-based Virtual Machine. LXC - Linux Containers (through libvirt). QEMU - Quick EMUlator. UML - User Mode Linux. hyperv - Microsoft® hyperv. vmware - VMware® vsphere. Baremetal - physical provisioning. For more information, see: http://docs.openstack.org/trunk/config-reference/content/section_compute-hypervisors.html",
"description": "Hypervisor type required by the image. Used with the ImagePropertiesFilter. \n\n KVM - Kernel-based Virtual Machine. LXC - Linux Containers (through libvirt). QEMU - Quick EMUlator. UML - User Mode Linux. hyperv - Microsoft® hyperv. vmware - VMware® vsphere. Baremetal - physical provisioning. VZ - Virtuozzo OS Containers and Virtual Machines (through libvirt). For more information, see: http://docs.openstack.org/trunk/config-reference/content/section_compute-hypervisors.html",
"type": "string",
"enum": [
"baremetal",
@ -22,6 +22,7 @@
"qemu",
"uml",
"vmware",
"vz",
"xen"
]
},

View File

@ -0,0 +1,9 @@
---
upgrade:
- |
The metadata definition for ``hypervisor_type`` in the
``OS::Compute::Hypervisor`` namespace has been extended to include
the Virtuozzo hypervisor, designated as ``vz``. You may upgrade
the definition using:
``glance-manage db load_metadefs [--path <path>] [--merge] [--prefer_new]``