- % curl -v http://localhost:32080/appmgr/ric/v1/health/ready
-
-The output should look as follows.
-
-.. code::
-
- * Trying 10.0.2.100...
- * TCP_NODELAY set
- * Connected to 10.0.2.100 (10.0.2.100) port 32080 (#0)
- > GET /appmgr/ric/v1/health/ready HTTP/1.1
- > Host: 10.0.2.100:32080
- > User-Agent: curl/7.58.0
- > Accept: */*
- >
- < HTTP/1.1 200 OK
- < Content-Type: application/json
- < Content-Length: 0
- < Connection: keep-alive
- < Date: Wed, 22 Jan 2020 20:55:39 GMT
- < X-Kong-Upstream-Latency: 0
- < X-Kong-Proxy-Latency: 2
- < Via: kong/1.3.1
- <
- * Connection #0 to host 10.0.2.100 left intact
-
-
-Undeploying the Infrastructure and Platform Groups
---------------------------------------------------
-
-To undeploy all the containers, perform the following steps in a root shell
-within the it-dep repository.
-
-.. code:: bash
-
- # cd bin
- # ./undeploy-ric-platform
-
-Results similar to below indicate a complete and successful cleanup.
-
-.. code::
-
- # ./undeploy-ric-platform
- Undeploying RIC platform components [appmgr rtmgr dbaas1 e2mgr e2term a1mediator submgr vespamgr rsm jaegeradapter infrastructure]
- release "r3-appmgr" deleted
- release "r3-rtmgr" deleted
- release "r3-dbaas1" deleted
- release "r3-e2mgr" deleted
- release "r3-e2term" deleted
- release "r3-a1mediator" deleted
- release "r3-submgr" deleted
- release "r3-vespamgr" deleted
- release "r3-rsm" deleted
- release "r3-jaegeradapter" deleted
- release "r3-infrastructure" deleted
- configmap "ricplt-recipe" deleted
- namespace "ricxapp" deleted
- namespace "ricinfra" deleted
- namespace "ricplt" deleted
-
-
-Restarting the VM
------------------
-
-After a reboot of the VM, and a suitable delay for initialization,
-all the containers should be running again as shown above.