Manage ONAP via TOSCA
- jh245g@att.com
Create ONAP deployment
Log into the manager. Select Local Blueprints. You will find the onap buleprint. Click the Deploy button to create a deployment.
Click the Deploy button to create a deployment.
Input | description | default value |
|---|---|---|
Deployment name | The unique name for this deployment | N/A |
tiller-server-ip | The IP address of K8s master | N/A |
tiller-server-port | The NodePort of tiller deployment | N/A |
chart-repo-url | The URL of helm repo | |
chart-version | The helm chart version | 2.0.0 |
namespace | The K8s namespace to deploy onap | onap |
stable-repo-url | The URL for stable repository |
One deployment represent one ONAP instance. The manager is able to manage multiple ONAP instances.
ONAP life-cycle management
Once deployment created. You can find the onap deployment.
In the deployment, there are several workflows. We will use install, upgrade, rollback and Uninstall to manage the life-cycle of ONAP.
Here is one record demo.
Install
Execute the install workflow, it will deploy all the ONAP helm charts into target K8s cluster.
User can check deployment status in "Deployment Executions"
Here it shows the install workflow complete.
Results:
Upgrade
The upgrade workflow is for individual components. So we should provide node_instance_id to identify the component. User can get node_instance_id from "Nodes" section.
Input | description | default value |
|---|---|---|
node_instance_id | The unique id of onap component | N/A |
chartRepo | The URL of helm repo | N/A |
chartVersion | The helm chart version | N/A |
config_json | The JSON format config overwrite. This method is suitable for small amount config change. Leave it empty, if use config_url. | N/A |
config_url | The URL of the overwrite config file. This method is suitable for large amount config change. Leave it empty, if use config_json. | N/A |
config_format | if use config_url, please provide the type of file. json or yaml | json |
Rollback
The Rollback workflow can rolls back an ONAP component to a previous revision.
Input | description | default value |
|---|---|---|
node_instance_id | The unique id of onap component | N/A |
revision | revision (version) number of onap component. User can find it in "helm-history" | N/A |
Uninstall
The Uninstall workflow will delete all the helm deployment form K8s cluster.