matthew/packer-plugin-xenserver
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
fb4d888419
packer-plugin-xenserver/examples
History
daniel fb4d888419 updated examples/README.md to refekt current state
2021-04-15 18:02:41 +02:00
..
centos added centos8-netinstall 2021-04-15 18:02:41 +02:00
http added centos8-netinstall 2021-04-15 18:02:41 +02:00
centos8.json Update docs on and remove it from the examples in favor of the default behavior 2021-03-30 22:46:14 -07:00
README.md updated examples/README.md to refekt current state 2021-04-15 18:02:41 +02:00
ubuntu-2004.json Update docs on and remove it from the examples in favor of the default behavior 2021-03-30 22:46:14 -07:00

README.md

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. This doc will focus on the details relevant to the particular distro.

Running the examples

In order to run this example 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.

  1. 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 to configure the VM template. Please see the autoinstall docs 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 and meta-data for autoinstall must be present.

Centos

The Centos examples use kickstart files to configure the VM template. Please see the kickstart documentation 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 file must be present.