Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagebash
themeMidnight
titleinstall
helm install $DIR/../helm/"${PARENT_CHART}" -f $OVERRIDEYAML --namespace "${NONRTRIC_NAMESPACE:-nonrtric}" --name "${RELEASE_PREFIX}"

The deploy-nonrtric script is called only the first time and every other redeployment should call install script as long as you don't do any change in helm charts. This saves time and resource as we reuse the existing charts packaged and served by helm repo.

To deploy the nonrtric components in kuberentes you need to call the below command from bin directory within nonrtric,

Code Block
languagebash
themeMidnight
titlerun install command
root@vm1:~/dep/nonrtric/bin#./install -f ../RECIPE_EXAMPLE/example_recipe.yaml

Once the deployment starts you see the below log in console,

Code Block
languagetext
themeMidnight
titleInstall log
Chart name- nonrtric
namespace/nonrtric created
configmap/nonrtric-recipe created
Deploying NONRTRIC components [controlpanel a1controller a1simulator policymanagementservice nonrtric]
Updating the Parent Chart [nonrtric]
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "local" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 5 charts
Downloading a1controller from repo http://127.0.0.1:8879/charts
Downloading a1simulator from repo http://127.0.0.1:8879/charts
Downloading controlpanel from repo http://127.0.0.1:8879/charts
Downloading policymanagementservice from repo http://127.0.0.1:8879/charts
Downloading nonrtric-common from repo http://127.0.0.1:8879/charts
Deleting outdated charts
NAME:   r2-dev-nonrtric
LAST DEPLOYED: Tue Apr 21 10:43:46 2020
NAMESPACE: nonrtric
STATUS: DEPLOYED

RESOURCES:
==> v1/ConfigMap
NAME                               DATA  AGE
controlpanel-configmap             1     1s
policymanagementservice-configmap  1     1s

==> v1/Service
NAME                     TYPE       CLUSTER-IP    EXTERNAL-IP  PORT(S)         AGE
a1controller             ClusterIP  10.43.34.119  <none>       8282/TCP        1s
dbhost                   ClusterIP  10.43.30.35   <none>       3306/TCP        1s
sdnctldb01               ClusterIP  10.43.89.176  <none>       3306/TCP        1s
a1-sim                   ClusterIP  None          <none>       8085/TCP        1s
controlpanel             NodePort   10.43.8.241   <none>       8080:30090/TCP  1s
policymanagementservice  NodePort   10.43.79.184  <none>       8081:30092/TCP  1s

==> v1/Deployment
NAME                     DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
a1controller             1        1        1           0          1s
db                       1        1        1           0          1s
controlpanel             1        1        1           0          1s
policymanagementservice  1        1        1           0          1s

==> v1/StatefulSet
NAME        DESIRED  CURRENT  AGE
a1-sim-osc  2        1        1s
a1-sim-std  2        1        1s

==> v1/Pod(related)
NAME                                      READY  STATUS             RESTARTS  AGE
a1controller-5c9f5b586c-wktgg             0/1    ContainerCreating  0         1s
db-549ff9b4d5-9skl5                       0/1    ContainerCreating  0         1s
controlpanel-5f4ccc78cb-lc97c             0/1    ContainerCreating  0         1s
policymanagementservice-79d5cdb475-lkhcn  0/1    ContainerCreating  0         1s
a1-sim-osc-0                              0/1    ContainerCreating  0         1s
a1-sim-std-0                              0/1    ContainerCreating  0         0s

...