Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

terraform provider for libvirt

License

NotificationsYou must be signed in to change notification settings

MalloZup/terraform-provider-libvirt

 
 

Repository files navigation

alphaBuild Status


This is a terraform provider that lets you provisionservers on alibvirt host viaTerraform.

Table of Content

Website Docs

Introduction & Goals

This project exists:

  • To allow teams to get the benefitsSoftware Defined Infrastructure Terraform provides, on top of classical and cheap virtualization infrastructure provided by Linux andKVMThis helps in very dynamicDevOps, Development and Testing activities.
  • To allow for mixing KVM resources with other infrastructure Terraform is able to manage

What isNOT in scope:

  • To support every advanced featurelibvirt supports

    This would make the mapping from terraform complicated and not maintanable. See theHow to contribute section to understand how to approach new features.

Downloading

Builds for openSUSE, CentOS, Ubuntu, Fedora are created with openSUSE'sOBS. The build definitions are available for both thestable andmaster branches.

Using published binaries/builds

Using packages

Follow the instructions for your distribution:

Building from source

Requirements

  • Terraform
  • Go (to build the provider plugin)
  • libvirt 1.2.14 or newer development headers
  • cgo is required by thelibvirt-go package.export CGO_ENABLED="1"

This project usesgo modules to vendor all itsdependencies.

You do not have to interact withmodules since the vendored packages arealready included in the repo.

Ensure you have the latest version of Go installed on your system, terraform usuallytakes advantage of features available only inside of the latest stable release.

You need also need libvirt-dev(el) package installed.

Building The Provider

Clone repository to:$GOPATH/src/github.com/dmacvicar/terraform-provider-libvirt

mkdir -p $GOPATH/src/github.com/dmacvicar; cd $GOPATH/src/github.com/dmacvicargit clone https://github.com/dmacvicar/terraform-provider-libvirt.git

Enter the provider directory and build the provider

cd $GOPATH/src/github.com/dmacvicar/terraform-provider-libvirtmake install

If you are using Go >= 1.11, you don't need to build inside GOPATH:

export GO111MODULE=onexport GOFLAGS=-mod=vendormake install

You will now find the binary at$GOPATH/bin/terraform-provider-libvirt.

Installing

  • Check that libvirt daemon 1.2.14 or newer is running on the hypervisor (virsh version --daemon)
  • mkisofs is required to use theCloudInit

Copied from the Terraform documentation:

At present Terraform can automatically install only the providers distributed by HashiCorp. Third-party providers can be manually installed by placing their plugin executables in one of the following locations depending on the host operating system:

On Linux and unix systems, in the sub-path.terraform.d/plugins in your user's home directory.

On Windows, in the sub-pathterraform.d/plugins beneath your user's "Application Data" directory.

terraform init will search this directory for additional plugins during plugin initialization.

Using the provider

Here is an example that will setup the following:

  • A virtual server resource

(create this as libvirt.tf and run terraform commands from this directory):

provider"libvirt" {uri="qemu:///system"}

You can also set the URI in the LIBVIRT_DEFAULT_URI environment variable.

Now, define a libvirt domain:

resource"libvirt_domain""terraform_test" {name="terraform_test"}

Now you can see the plan, apply it, and then destroy the infrastructure:

$terraform init$terraform plan$terraform apply$terraform destroy

Look at more advanced exampleshere

Using multiple hypervisors / provider instances

You can target different libvirt hosts instantiating theprovider multiple times.Example.

Using qemu-agent

From its documentation,qemu-agent:

It is a daemon program running inside the domain which is supposed to help management applications with executing functions which need assistance of the guest OS.

Until terraform-provider-libvirt 0.4.2, qemu-agent was used by default to get network configuration. However, if qemu-agent is not running, this creates a delay until connecting to it times-out.

In current versions, we default to not to attempt connecting to it, and attempting to retrieve network interface information from the agent needs to be enabled explicitly withqemu_agent = true, further detailshere. Note that you still need to make sure the agent is running in the OS, and that is unrelated to this option.

Note: when using bridge network configurations you need to enable theqemu_agent = true. otherwise you will not retrieve the ip adresses of domains.

Be aware that this variables may be subject to change again in future versions.

Upstream projects using terraform-libvirt:

Authors

See also the list ofcontributors who participated in this project.

The structure and boilerplate is inspired from theSoftlayer andGoogle Terraform provider sources.

License

  • Apache 2.0, See LICENSE file

About

terraform provider for libvirt

Resources

License

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Go98.3%
  • Other1.7%

[8]ページ先頭

©2009-2025 Movatter.jp