Once a kubernetes environment is available and the deployment artifacts have been customized for your location, ONAP is ready to be installed.
In-order to be able to support multiple ONAP instances within a single kubernetes environment a configuration set is required. The createConfig.sh
script is used to do this.
> ./createConfig.sh -n onapTrial |
The bash script createAll.bash
is used to create an ONAP deployment with kubernetes. It has two primary functions:
> ./createAll.bash -n onapTrial |
Namespaces provide isolation between ONAP components as ONAP release 1.0 contains duplicate application (e.g. mariadb) and port usage. As such createAll.bash
requires the user to enter a namespace prefix string that can be used to separate multiple deployments of onap. The result will be set of 10 namespaces (e.g. onapTrial-sdc, onapTrial-aai, onapTrial-mso, onapTrial-message-router, onapTrial-robot, onapTrial-vid, onapTrial-sdnc, onapTrial-portal, onapTrial-policy, onapTrial-appc
) being created within the kubernetes environment. A prerequisite pod config-init (pod-config-init.yaml
) may need editing to match your environment and deployment into the default namespace before running createAll.bash
.
If you'd like to see the installation of ONAP by OOM take a look at this short video demonstration by Mike Elliott: OOM Demo Video
OOM uses the Kubernetes container management system to orchestrate the life cycle of the ONAP infrastructure components. If you'd like to learn more about how this works or develop the deployment specifications for a project not already managed by OOM look here: OOM User Guide.