.. | ||
diskimage-create.sh | ||
image-tests.sh | ||
README.rst | ||
requirements.txt | ||
test-requirements.txt | ||
tox.ini | ||
version.txt |
Diskimage-builder script for creating Octavia Amphora images
Octavia is an operator-grade reference implementation for Load Balancing as a Service (LBaaS) for OpenStack. The component of Octavia that does the load balancing is known as amphora. Amphora may be a virtual machine, may be a container, or may run on bare metal. Creating images for bare metal amphora installs is outside the scope of this version but may be added in a future release.
Prerequisites
This script assumes a typical Linux environment and was developed on Ubuntu 12.04.5 LTS.
Python pip should be installed as well as the python modules found in the requirements.txt file.
Your cache directory should have at least 1GB available, the working directory will need ~1.5GB, and your image destination will need ~500MB
The script will use the version of diskimage-builder installed on your system, or it can be overridden by setting the following environment variables:
DIB_REPO_PATH = /<some directory>/diskimage-builder
DIB_ELEMENTS = /<some directory>/diskimage-builder/elements
The following packages are required on each platform: Ubuntu and Fedora: qemu kpartx git CentOS and RedHat Enterprise Linux: qemu-kvm qemu-img kpartx git CentOS requires the EPEL repo and python-argparse:
$ sudo rpm -Uvh --force http://mirrors.kernel.org/fedora-epel/6/i386/epel-release-6-8.noarch.rpm
$ yum install python-argparse
Test Prerequisites
The tox image tests require libguestfs-tools 1.24 or newer. Libguestfs allows testing the Amphora image without requiring root privileges. On Ubuntu systems you also need to give read access to the kernels for the user running the tests:
$ sudo chmod 0644 /boot/vmlinuz*
Tests were run on Ubuntu 14.04.1 LTS during development.
Usage
This script and associated elements will build Amphora images. Current support is with an Ubuntu base OS and HAProxy. The script can use Fedora or CentOS as a base OS but these will not initially be tested or supported. As the project progresses and/or the diskimage-builder project adds support for additional base OS options they may become available for Amphora images. This does not mean that they are necessarily supported or tested.
The script will use environment variables to customize the build beyond the Octavia project defaults, such as adding elements.
The supported and tested image is created by using the diskimage-create.sh defaults (no command line parameters or environment variables set). As the project progresses we may add additional supported configurations.
Command syntax:
[-a i386 | amd64 | armhf ]
[-b haproxy ]
[-c ~/.cache/image-create | <cache directory> ]
[-h]
[-i ubuntu | fedora | centos | rhel ]
[-o amphora-x64-haproxy | <filename> ]
[-r <root password> ]
[-s 2 | <size in GB> ]
[-t qcow2 | tar ]
[-v]
[-w <working directory> ]
'-a' is the architecture type for the image (default: amd64)
'-b' is the backend type (default: haproxy)
'-c' is the path to the cache directory (default: ~/.cache/image-create)
'-h' display help message
'-i' is the base OS (default: ubuntu)
'-o' is the output image file name
'-r' enable the root account in the generated image (default: disabled)
'-s' is the image size to produce in gigabytes (default: 2)
'-t' is the image type (default: qcow2)
'-v' display the script version
'-w' working directory for image building (default: .)
Environment Variables
These are optional environment variables that can be set to override the script defaults.
- CLOUD_INIT_DATASOURCES
-
- Comma separated list of cloud-int datasources
- Default: ConfigDrive
- Options: NoCloud, ConfigDrive, OVF, MAAS, Ec2, <others>
- Reference: https://launchpad.net/cloud-init
- BASE_OS_MIRROR
-
- URL to a mirror for the base OS selected
- Default: None
- DIB_ELEMENTS
-
- Override the elements used to build the image
- Default: None
- DIB_LOCAL_ELEMENTS
-
- Elements to add to the build (requires DIB_LOCAL_ELEMENTS_PATH be specified)
- Default: None
- DIB_LOCAL_ELEMENTS_PATH
-
- Path to the local elements directory
- Default: None
- DIB_REPO_PATH
-
- Directory containing diskimage-builder
- Default: <directory above OCTAVIA_HOME>/diskimage-builder
- Reference: https://github.com/openstack/diskimage-builder
- OCTAVIA_REPO_PATH
-
- Directory containing octavia
- Default: <directory above the script location>
- Reference: https://github.com/openstack/octavia
RHEL specific variables
- Building a RHEL-based image requires:
-
- a RHEL 7 base cloud image, manually download from the Red Hat Customer Portal. Set the DIB_LOCAL_IMAGE variable to point to the file. More details at: <DIB_REPO_PATH>/elements/rhel7
- a Red Hat subscription for the matching Red Hat OpenStack Platform repository. Set the needed registration parameters depending on your configuration. More details at: <DIB_REPO_PATH>/elements/rhel-common
Here is an example with Customer Portal registration and OSP 8 repository: .. code:: bash
$ export DIB_LOCAL_IMAGE='/tmp/rhel-guest-image-7.2-20160302.0.x86_64.qcow2'
$ export REG_METHOD='portal' REG_REPOS='rhel-7-server-openstack-8-rpms'
$ export REG_USER='<user>' REG_PASSWORD='<password>' REG_AUTO_ATTACH=true
This example uses registration via a Satellite (the activation key must enable an OSP repository): .. code:: bash
$ export DIB_LOCAL_IMAGE='/tmp/rhel-guest-image-7.2-20160302.0.x86_64.qcow2'
$ export REG_METHOD='satellite' REG_ACTIVATION_KEY="<activation key>"
$ export REG_SAT_URL="<satellite url>" REG_ORG="<satellite org>"
Container Support
The Docker command line required to import a tar file created with this script is:
$ docker import - image:amphora-x64-haproxy < amphora-x64-haproxy.tar
References
This documentation and script(s) leverage prior work by the OpenStack TripleO and Sahara teams. Thank you to everyone that worked on them for providing a great foundation for creating Octavia Amphora images.
Copyright
Copyright 2014 Hewlett-Packard Development Company, L.P.
All Rights Reserved.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.