packer-plugin-xenserver/examples/README.md

37 lines
2.0 KiB
Markdown

## Examples
In order for new users to get up and running with the packer builder, a few examples of building a machine image with popular distros have been created.
In order to see an exhaustive list of configuration options for the packer builder please see the [following documentation](../docs/builders/xenserver-iso.html.markdown). This doc will focus on the details relevant to the particular distro.
### Running the examples
In order to run the examples you will need to perform the following steps:
1. Export those vars:
```
PKR_VAR_remote_host
PKR_VAR_remote_password
PKR_VAR_remote_username
PKR_VAR_sr_name
PKR_VAR_sr_iso_name
```
`PKR_VAR_remote_host` must be the resource pool primary, aka the master.
2. Run `packer init path/to/defenition.pkr.hcl` to download the xenserver plugin
2. Run `packer build path/to/defenition.pkr.hcl`
so for example:
`packer build examples/centos/centos8-netinstall.pkr.hcl`
### Ubuntu
The Ubuntu example uses the [autoinstall tool](https://ubuntu.com/server/docs/install/autoinstallhttps://ubuntu.com/server/docs/install/autoinstall) to configure the VM template. Please see the [autoinstall docs](https://ubuntu.com/server/docs/install/autoinstall-reference) for an exhaustive list of what is supported.
Packer will create a http server to serve the files as specified from the `http_directory` specified in the builder configuration. This is where the [user-data](http/ubuntu-2004/user-data) and [meta-data](http/ubuntu-2004/meta-data) for autoinstall must be present.
### Centos
The Centos examples use kickstart files to configure the VM template. Please see the [kickstart documentation](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/sect-kickstart-syntax) for the options that are supported.
Packer will create a http server to serve the files as specified from the `http_directory` specified in the builder configuration. This is where the [kickstart config](http/centos8/ks-centos8.cfg) file must be present.