17 KiB
description | layout | page_title | sidebar_current |
---|---|---|---|
The openstack Packer builder is able to create new images for use with OpenStack. The builder takes a source image, runs any provisioning necessary on the image after launching it, then creates a new reusable image. This reusable image can then be used as the foundation of new servers that are launched within OpenStack. | docs | OpenStack - Builders | docs-builders-openstack |
OpenStack Builder
Type: openstack
The openstack
Packer builder is able to create new images for use with
OpenStack. The builder takes a source image, runs
any provisioning necessary on the image after launching it, then creates a new
reusable image. This reusable image can then be used as the foundation of new
servers that are launched within OpenStack. The builder will create temporary
keypairs that provide temporary access to the server while the image is being
created. This simplifies configuration quite a bit.
The builder does not manage images. Once it creates an image, it is up to you to use it or delete it.
~> Note: To use OpenStack builder with the OpenStack Newton (Oct 2016) or earlier, we recommend you use Packer v1.1.2 or earlier version.
~> OpenStack Liberty or later requires OpenSSL! To use the OpenStack
builder with OpenStack Liberty (Oct 2015) or later you need to have OpenSSL
installed if you are using temporary key pairs, i.e. don't use
ssh_keypair_name
nor
ssh_password
. All major
OS'es have OpenSSL installed by default except Windows. This have been resolved
in OpenStack Ocata(Feb 2017).
~> Note: OpenStack Block Storage volume support is available only for V3 Block Storage API. It's available in OpenStack since Mitaka release (Apr 2016).
Configuration Reference
There are many configuration options available for the builder. They are segmented below into two categories: required and optional parameters. Within each category, the available configuration keys are alphabetized.
In addition to the options listed here, a communicator can be configured for this builder.
Required:
-
flavor
(string) - The ID, name, or full URL for the desired flavor for the server to be created. -
image_name
(string) - The name of the resulting image. -
identity_endpoint
(string) - The URL to the OpenStack Identity service. If not specified, Packer will use the environment variablesOS_AUTH_URL
, if set. This is not required if usingcloud.yaml
. -
source_image
(string) - The ID or full URL to the base image to use. This is the image that will be used to launch a new server and provision it. Unless you specify completely custom SSH settings, the source image must havecloud-init
installed so that the keypair gets assigned properly. -
source_image_name
(string) - The name of the base image to use. This is an alternative way of providingsource_image
and only either of them can be specified. -
source_image_filter
(map) - The search filters for determining the base image to use. This is an alternative way of providingsource_image
and only one of these methods can be used.source_image
will override the filters. -
username
oruser_id
(string) - The username or id used to connect to the OpenStack service. If not specified, Packer will use the environment variableOS_USERNAME
orOS_USERID
, if set. This is not required if using access token instead of password or if usingcloud.yaml
. -
password
(string) - The password used to connect to the OpenStack service. If not specified, Packer will use the environment variablesOS_PASSWORD
, if set. This is not required if using access token instead of password or if usingcloud.yaml
.
Optional:
-
availability_zone
(string) - The availability zone to launch the server in. If this isn't specified, the default enforced by your OpenStack cluster will be used. This may be required for some OpenStack clusters. -
cacert
(string) - Custom CA certificate file path. If omitted theOS_CACERT
environment variable can be used. -
cert
(string) - Client certificate file path for SSL client authentication. If omitted theOS_CERT
environment variable can be used. -
cloud
(string) - An entry in aclouds.yaml
file. See the OpenStack os-client-config documentation for more information aboutclouds.yaml
files. If omitted, theOS_CLOUD
environment variable is used. -
config_drive
(boolean) - Whether or not nova should use ConfigDrive for cloud-init metadata. -
domain_name
ordomain_id
(string) - The Domain name or ID you are authenticating with. OpenStack installations require this if identity v3 is used. Packer will use the environment variableOS_DOMAIN_NAME
orOS_DOMAIN_ID
, if set. -
endpoint_type
(string) - The endpoint type to use. Can be any of "internal", "internalURL", "admin", "adminURL", "public", and "publicURL". By default this is "public". -
floating_ip
(string) - A specific floating IP to assign to this instance. -
floating_ip_network
(string) - The ID or name of an external network that can be used for creation of a new floating IP. -
floating_ip_pool
(string) - Deprecated usefloating_ip_network
instead. -
image_members
(array of strings) - List of members to add to the image after creation. An image member is usually a project (also called the "tenant") with whom the image is shared. -
image_visibility
(string) - One of "public", "private", "shared", or "community". -
insecure
(boolean) - Whether or not the connection to OpenStack can be done over an insecure connection. By default this is false. -
key
(string) - Client private key file path for SSL client authentication. If omitted theOS_KEY
environment variable can be used. -
metadata
(object of key/value strings) - Glance metadata that will be applied to the image. -
instance_name
(string) - Name that is applied to the server instance created by Packer. If this isn't specified, the default is same asimage_name
. -
instance_metadata
(object of key/value strings) - Metadata that is applied to the server instance created by Packer. Also called server properties in some documentation. The strings have a max size of 255 bytes each. -
networks
(array of strings) - A list of networks by UUID to attach to this instance. -
ports
(array of strings) - A list of ports by UUID to attach to this instance. -
rackconnect_wait
(boolean) - For rackspace, whether or not to wait for Rackconnect to assign the machine an IP address before connecting via SSH. Defaults to false. -
region
(string) - The name of the region, such as "DFW", in which to launch the server to create the image. If not specified, Packer will use the environment variableOS_REGION_NAME
, if set. -
reuse_ips
(boolean) - Whether or not to attempt to reuse existing unassigned floating ips in the project before allocating a new one. Note that it is not possible to safely do this concurrently, so if you are running multiple openstack builds concurrently, or if other processes are assigning and using floating IPs in the same openstack project while packer is running, you should not set this to true. Defaults to false. -
security_groups
(array of strings) - A list of security groups by name to add to this instance. -
source_image_filter
(object) - Filters used to populate filter options. Example:{ "source_image_filter": { "filters": { "name": "ubuntu-16.04", "visibility": "protected", "owner": "d1a588cf4b0743344508dc145649372d1", "tags": ["prod", "ready"] }, "most_recent": true } }
This selects the most recent production Ubuntu 16.04 shared to you by the given owner. NOTE: This will fail unless exactly one image is returned, or
most_recent
is set to true. In the example of multiple returned images,most_recent
will cause this to succeed by selecting the newest image of the returned images.-
filters
(map of strings) - filters used to select asource_image
. NOTE: This will fail unless exactly one image is returned, ormost_recent
is set to true. Of the filters described in ImageService, the following are valid:-
name (string)
-
owner (string)
-
tags (array of strings)
-
visibility (string)
-
-
most_recent
(boolean) - Selects the newest created image when true. This is most useful for selecting a daily distro build.
You may set use this in place of
source_image
Ifsource_image_filter
is provided alongsidesource_image
, thesource_image
will override the filter. The filter will not be used in this case. -
-
ssh_interface
(string) - The type of interface to connect via SSH. Values useful for Rackspace are "public" or "private", and the default behavior is to connect via whichever is returned first from the OpenStack API. -
ssh_ip_version
(string) - The IP version to use for SSH connections, valid values are4
and6
. Useful on dual stacked instances where the default behavior is to connect via whichever IP address is returned first from the OpenStack API. -
ssh_keypair_name
(string) - If specified, this is the key that will be used for SSH with the machine. By default, this is blank, and Packer will generate a temporary keypair.ssh_password
is used.ssh_private_key_file
orssh_agent_auth
must be specified whenssh_keypair_name
is utilized. -
ssh_agent_auth
(boolean) - If true, the local SSH agent will be used to authenticate connections to the source instance. No temporary keypair will be created, and the values ofssh_password
andssh_private_key_file
will be ignored. To use this option with a key pair already configured in the source image, leave thessh_keypair_name
blank. To associate an existing key pair with the source instance, set thessh_keypair_name
field to the name of the key pair. -
temporary_key_pair_name
(string) - The name of the temporary key pair to generate. By default, Packer generates a name that looks likepacker_<UUID>
, where <UUID> is a 36 character unique identifier. -
tenant_id
ortenant_name
(string) - The tenant ID or name to boot the instance into. Some OpenStack installations require this. If not specified, Packer will use the environment variableOS_TENANT_NAME
orOS_TENANT_ID
, if set. Tenant is also called Project in later versions of OpenStack. -
token
(string) - the token (id) to use with token based authorization. Packer will use the environment variableOS_TOKEN
, if set. -
use_floating_ip
(boolean) - Deprecated usefloating_ip
orfloating_ip_pool
instead. -
user_data
(string) - User data to apply when launching the instance. Note that you need to be careful about escaping characters due to the templates being JSON. It is often more convenient to useuser_data_file
, instead. Packer will not automatically wait for a user script to finish before shutting down the instance this must be handled in a provisioner. -
user_data_file
(string) - Path to a file that will be used for the user data when launching the instance. -
use_blockstorage_volume
(boolean) - Use Block Storage service volume for the instance root volume instead of Compute service local volume (default). -
volume_name
(string) - Name of the Block Storage service volume. If this isn't specified, random string will be used. -
volume_type
(string) - Type of the Block Storage service volume. If this isn't specified, the default enforced by your OpenStack cluster will be used. -
volume_size
(int) - Size of the Block Storage service volume in GB. If this isn't specified, it is set to source image min disk value (if set) or calculated from the source image bytes size. Note that in some cases this needs to be specified, ifuse_blockstorage_volume
is true. -
volume_availability_zone
(string) - Availability zone of the Block Storage service volume. If omitted, Compute instance availability zone will be used. If both of Compute instance and Block Storage volume availability zones aren't specified, the default enforced by your OpenStack cluster will be used. -
image_disk_format
(string) - Disk format of the resulting image. This option works ifuse_blockstorage_volume
is true.
Basic Example: DevStack
Here is a basic example. This is a example to build on DevStack running in a VM.
{
"type": "openstack",
"identity_endpoint": "http://<destack-ip>:5000/v3",
"tenant_name": "admin",
"domain_name": "Default",
"username": "admin",
"password": "<your admin password>",
"region": "RegionOne",
"ssh_username": "root",
"image_name": "Test image",
"source_image": "<image id>",
"flavor": "m1.tiny",
"insecure": "true"
}
Basic Example: Rackspace public cloud
Here is a basic example. This is a working example to build a Ubuntu 12.04 LTS (Precise Pangolin) on Rackspace OpenStack cloud offering.
{
"type": "openstack",
"username": "foo",
"password": "foo",
"region": "DFW",
"ssh_username": "root",
"image_name": "Test image",
"source_image": "23b564c9-c3e6-49f9-bc68-86c7a9ab5018",
"flavor": "2"
}
Basic Example: Private OpenStack cloud
This example builds an Ubuntu 14.04 image on a private OpenStack cloud, powered by Metacloud.
{
"type": "openstack",
"ssh_username": "root",
"image_name": "ubuntu1404_packer_test_1",
"source_image": "91d9c168-d1e5-49ca-a775-3bfdbb6c97f1",
"flavor": "2"
}
In this case, the connection information for connecting to OpenStack doesn't appear in the template. That is because I source a standard OpenStack script with environment variables set before I run this. This script is setting environment variables like:
OS_AUTH_URL
OS_TENANT_ID
OS_USERNAME
OS_PASSWORD
This is slightly different when identity v3 is used:
OS_AUTH_URL
OS_USERNAME
OS_PASSWORD
OS_DOMAIN_NAME
OS_TENANT_NAME
This will authenticate the user on the domain and scope you to the project. A
tenant is the same as a project. It's optional to use names or IDs in v3. This
means you can use OS_USERNAME
or OS_USERID
, OS_TENANT_ID
or
OS_TENANT_NAME
and OS_DOMAIN_ID
or OS_DOMAIN_NAME
.
The above example would be equivalent to an RC file looking like this :
export OS_AUTH_URL="https://identity.myprovider/v3"
export OS_USERNAME="myuser"
export OS_PASSWORD="password"
export OS_USER_DOMAIN_NAME="mydomain"
export OS_PROJECT_DOMAIN_NAME="mydomain"
Basic Example: Instance with Block Storage root volume
A basic example of Instance with a remote root Block Storage service volume. This is a working example to build an image on private OpenStack cloud powered by Selectel VPC.
{
"type": "openstack",
"identity_endpoint": "https://api.selvpc.com/identity/v3",
"tenant_id": "2e90c5c04c7b4c509be78723e2b55b77",
"username": "foo",
"password": "foo",
"region": "ru-3",
"ssh_username": "root",
"image_name": "Test image",
"source_image": "5f58ea7e-6264-4939-9d0f-0c23072b1132",
"networks": "9aab504e-bedf-48af-9256-682a7fa3dabb",
"flavor": "1001",
"availability_zone": "ru-3a",
"use_blockstorage_volume": true,
"volume_type": "fast.ru-3a"
}
Notes on OpenStack Authorization
The simplest way to get all settings for authorization against OpenStack is to
go into the OpenStack Dashboard (Horizon) select your Project and navigate
Project, Access & Security, select API Access and Download OpenStack RC
File v3. Source the file, and select your wanted region by setting environment
variable OS_REGION_NAME
or OS_REGION_ID
and
export OS_TENANT_NAME=$OS_PROJECT_NAME
or
export OS_TENANT_ID=$OS_PROJECT_ID
.
~> OS_TENANT_NAME
or OS_TENANT_ID
must be used even with Identity v3,
OS_PROJECT_NAME
and OS_PROJECT_ID
has no effect in Packer.
To troubleshoot authorization issues test you environment variables with the OpenStack cli. It can be installed with
$ pip install --user python-openstackclient
Authorize Using Tokens
To authorize with a access token only identity_endpoint
and token
is
needed, and possibly tenant_name
or tenant_id
depending on your token type.
Or use the following environment variables:
OS_AUTH_URL
OS_TOKEN
- One of
OS_TENANT_NAME
orOS_TENANT_ID