-
Notifications
You must be signed in to change notification settings - Fork 457
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
A few changes here: 1. CoreOS Ignition support: A CoreOS Ignition file can be specified for a domain using the "coreos_ignition" parameter. Alternatively the "coreos_ignition" parameter can be set equal to a Terraform ignition object. If the latter, the ignition object is written to a file in /tmp whose name is a hash of the object itself. This file-name is stored in libvirt domain metadata, and is removed when the domain is destroyed. This feature requires the emission of qemu:commandline XML XML and also the setting of the XML name-space to "http://libvirt.org/schemas/domain/qemu/1.0" 2. "graphics" block: A "graphics" block can be specified in a domain definition. We've added this because we've found that for some builds of qemu the default "spice" emulator doesn't work and results in failure to boot the VMs. 3. "console" block: One or more "console" blocks can be specified in a domain definition. Note the description in domain.html.markdown, and the information in https://libvirt.org/formatdomain.html#elementsConsole Added a test for coreos_ignition in resource_libvirt_domain_test.go
- Loading branch information
1 parent
ea96b66
commit 252e13d
Showing
6 changed files
with
165 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters