| ... | ... | @@ -42,6 +42,7 @@ 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
|
|
|
|
```
|
|
|
|
As a remark (12-12-2016), you can see above that we use trusty (14.04) version of Ubuntu ($DIB_RELEASE). In principle the heat template works with Ubuntu xenial (16.04), however we have problems connecting UEs to the core when using xenial. So please test with trusty (14.04) version of Ubuntu first.
|
|
|
|
|
|
|
|
**2. Upload your created image to OpenStack**
|
|
|
|
|
| ... | ... | @@ -53,7 +54,7 @@ glance image-create --disk-format qcow2 --file ubuntu-$DIB_RELEASE-os-config.qco |
|
|
|
|
|
|
|
**3. Create or upload an SSH keypair for logging into 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 achieve this:
|
|
|
|
You will need an SSH key to be able to login to instances created by Heat. Therefore an SSH keypair needs to be defined for your tenant. There are several possibilities to achieve 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 a secret place.
|
| ... | ... | @@ -74,11 +75,13 @@ You are almost done with your cloud setup, once again check the following on you |
|
|
|
* Go to horizons 'Orchestration' tab and click on 'Launch Stack'.
|
|
|
|
* As template provide the file you downloaded before and click on next. No environment file is needed.
|
|
|
|
* Now adjust the values your for your needs, and press on next.
|
|
|
|
|
|
|
|
Here you have a little video how it should look like:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Depending on your clouds performance and the flavors selected it can take more than the normal timeout (60 minutes). with build flavor of 4 cores you should be fine in 30 minutes.
|
|
|
|
* When the stack was created successfully nodes need to be rebooted for using updated or custom (SPGW) kernels.
|
|
|
|
* After reboot the three programs oai_hss, mme and spgw on the respective instances need to be started and the core is up.
|
|
|
|
Here is the corresponding video for that:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
