| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
Merge the user data specified by explicit terraform directives into
the raw data provided by the user. The raw data has priority over the
values specified using older directives.
Signed-off-by: Flavio Castelli <fcastelli@suse.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We've added the facility to define a disk bus type of scsi to the
specification of a disk in the domain definition. If the disk is
a scsi disk, a random wwn is generated unless a wwn is provided for
that disk.
The disk stanza now looks as follows:
disk {
volume_id = "${libvirt_volume.mydisk.id}"
scsi = "yes"
wwn = "05abcd123456789a"
}
Having "scsi" present with any value will specify a scsi bus for
the disk. If "wwn" is present for a scsci disk then the value of
"wwn" is used for the disk wwn, otherwise a random value is generated.
|
| |
|
|
|
|
|
| |
Since the `graphics` and `video` devices cause problems on s390x and
ppc64, they are ignored when creating a domain.
Signed-off-by: Thomas Hipp <thipp@suse.de>
|
| | |
|
| |\
| |
| | |
Add DNS forwarder blocks to network resource definition
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There can be one or more of these optional blocks. Each block
looks as follows:
dns_forwarder {
address = "my address"
domain = "my domain"
}
One or both of "address" and "domain" can be specified in each block.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A few changes here:
1. CoreOS Ignition support: A CoreOS Ignition file can be
specified for a domain using the "coreos_ignition"
parameter. This requires the emission of additional
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 description in
https://libvirt.org/formatdomain.html#elementsConsole
|
| | |
|
| |
|
|
|
|
|
| |
This changes the disk block in the domain resource to be defined as a map,
instead of an object. There is no difference in the standard use case,
but it allows to generate disk maps via interpolations and variables
which is useful in modules.
|
| |
|
|
|
| |
Two slashes instead of three lead to an obscure CA related error message:
http://wiki.libvirt.org/page/Failed_to_connect_to_the_hypervisor#Cannot_read_CA_certificate
|
| |
|
|
| |
Minor fixes
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a network card is attached to a LAN the `domain.ListAllInterfaceAddresses`
API cannot be used to get the IP address associated with the interfaces.
The only solution to this problem is to use the [Qemu guest agent](http://wiki.libvirt.org/page/Qemu_guest_agent)
to fetch this information.
This PR will take advantage of the qemu guest ageint (when installed
inside of the domain) to workaround the limitations of the
`domain.ListAllInterfaceAddresses`.
In theory this PR could also allow to relax the required version of
libvirt.
Signed-off-by: Flavio Castelli <fcastelli@suse.com>
|
| |
|
|
|
| |
Methods for adding/removing hosts to a network
Style, formatting improvements and fixes
|
| |
|
|
| |
Signed-off-by: Flavio Castelli <fcastelli@suse.com>
|
| |
|
|
| |
Signed-off-by: Flavio Castelli <fcastelli@suse.com>
|
| |
|
|
|
|
| |
I like it more ;)
Signed-off-by: Flavio Castelli <fcastelli@suse.com>
|
| |
|
|
|
|
|
|
|
|
| |
Allow to set custom metadata of a domain. This feature can be used to quickly
integrate terraform with other tools.
For example, this can be used to ship custom grains to salt-ssh via a
custom salt roster module.
Signed-off-by: Flavio Castelli <fcastelli@suse.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
It's now possible to specify a base volume by using the
`base_volume_name`. This is an approach done also by other Terraform
providers: either use an "internal" ID or a human-friendly name.
This makes easier to share the same base volume between different
terraform projects.
Signed-off-by: Flavio Castelli <fcastelli@suse.com>
|
| |\
| |
| |
| |
| |
| | |
Closes #18.
Merge branch 'connect_ip_address'
|
| | |
| |
| |
| | |
waiting for an address.
|
| |/
|
|
|
|
| |
Updated the examples to make them work as expected.
Signed-off-by: Flavio Castelli <fcastelli@suse.com>
|
| | |
|
| | |
|
| |
|
|
| |
https://github.com/hashicorp/terraform/issues/3287 is open
|
| | |
|
| | |
|
| | |
|
| |
|