Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add documentation on cloud-init and qemu-guest-agent #283

Closed
wants to merge 2 commits into from
Closed

Add documentation on cloud-init and qemu-guest-agent #283

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e2356ce
Added docs on cloud-init and qemu-guest-agent
Jul 31, 2021
3489ca4
Added docs on cloud-init and qemu-guest-agent
Jul 31, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions docs/resources/vm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,3 +214,26 @@ VMs can be imported using the `id`, e.g.
```
$ terraform import ovirt_vm.vm 90593465-e777-4d8d-8e98-51a6d799f6e6
```

## Template / Existing Disk Requirements

If you are leveraging a template or an existing disk when creating a VM resource. There are a few requirements that must be configured beforehand.

Mainly, on the template or existing disk, a few packages must be installed for `cloud-init` (IE - the `initialization` section) to work, as well as oVirt data propagation (for network information, etc).

The following packages and services are generally required:
* `qemu-guest-agent`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please replace tabs with spaces

* Both installing the package, and enabling the service.
* This allows propagation from subsequent data sources, such as network information.
* `cloud-init`
* Both installing the package, and enabling the service.
* This allows the VM resource to leverage the `cloud-init` features for the `initialization` section.

Here is a quick example for `RHEL / CentOS 8`:

```bash
dnf -y install cloud-init cloud-utils-growpart qemu-guest-agent
systemctl enable qemu-guest-agent cloud-init
```

There are various other considerations to take into account, especially if you are using other operating systems. But this initial information should give you a baseline to find the specific configuration steps required for your environment.