Support custom default libvirt schemas in provisioner #93
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Support tuning performance of VMs, based on information from https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_tuning_and_optimization_guide. Ideally, allow this to be configurable via either modifications to the
system_templatefacility, of asystem_templatesubclass, perhaps atuning_template.changed milestone to %3
Some obvious first tweaks:
Support configurable block device emulation, ideally in the storage template. Perhaps per-disk.
Would allow specifying emulated IDE or SCSI versus VirtIO which is the current default. For OVAs, read this from the OVF file.
Support multiple VirtIO disk queues (
<driver queues='N'/>in thecontrollersection), default to 1, configurable to another number.Support multiple VirtIO network queues (same as above).
Support Paravirtualized Page Faults.
Moving from 0.8 to future. At this time I think the utility of these changes is minimal as all modern systems suppor VirtIO, and making the adjustments manually during or after the provisioning state is more reasonable.
changed milestone to %4
Ties into #101 as well, since implementation 2 of that solution would allow these to be specified as configuration parameters for each VM.
Since I did not use implementation 2 for #101, this remains a manual process. And I think that's OK. The defaults are sane for the vast majority of modern operating systems in a basic configuration, and any tweaks can be made by using the
--no-startoption to the provisioner and then manually tweaking the configuration.That said, I think it would be useful to allow the overriding of the default libvirt schema in the provisioner. This is a slightly different feature, but would allow this sort of flexibility before deploying VMs. A "default schema" field could then be added to the system template and used when deploying a VM.
changed title from {-Tune performance of provisioned VMs-} to {+Support custom default libvirt schemas in provisioner+}
The implementation of the
create()aspect of VM provisioner scripts in #158 effectively completes this: since the configuration of new VMs in the provisioner is handled by administrator-configurable code, arbitrary changes can be made at will, with the currentlibvirt_schemalibraries serving as standardized known-good examples.