| ... | ... | @@ -17,7 +17,7 @@ This section outlines what you will need in order to deploy Openair-CN on your O |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**Ho to create Ubuntu images with os-*config**
|
|
|
|
** 1. Create Ubuntu images with os-*config**
|
|
|
|
|
|
|
|
To create os-*config ready Ubuntu images just use the following commands:
|
|
|
|
|
| ... | ... | @@ -31,3 +31,14 @@ export PATH="${PWD}/dib-utils/bin:$PATH" |
|
|
|
export ELEMENTS_PATH=tripleo-image-elements/elements:heat-templates/hot/software-config/elements
|
|
|
|
diskimage-builder/bin/disk-image-create vm ubuntu os-collect-config os-refresh-config os-apply-config heat-config heat-config-script -o ubuntu-$DIB_RELEASE-os-config.qcow2
|
|
|
|
|
|
|
|
** 2. Upload your created image to glance**
|
|
|
|
|
|
|
|
Use the horizon GUI or the glance command-line client to upload the image you just created to your OpenStack cloud.
|
|
|
|
|
|
|
|
** 3. Create an SSH keypair for logging in to instances **
|
|
|
|
|
|
|
|
You will need an SSH key to login to instances created by Heat. Therefore an SSH keypair needs to be defined for your tenant. There are several possibilities to achieive this:
|
|
|
|
|
|
|
|
* You have already a keypair defined for your tenant. That is fine, you can use that one for your OAI deployment.
|
|
|
|
* You can create a new SSH keypair directly in OpenStack. Keep in mind to keep the key file at secret place.
|
|
|
|
* You can import the public part of an existing SSH key to OpenStack |
