1
0
-1

How to login to Robot pod (in ONAP OOM installation) and execute the demo.sh init script? to onboard the distributed service into VID? Is this step even mandatory?


I was able to login to the ROBOT POD and find the demo.s script. When ran ./demo.sh init, no output. Logs are below.


root@onap:~# kubectl exec -it --namespace onap rsys-robot-robot-ffb4b9f4d-mqdn4 bash
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/# ls
bin boot dev etc home lib lib64 media mnt opt proc root run sbin share srv sys tmp usr var
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/# cd /opt/
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/opt# ls
google
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/opt#
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/opt# cd google/
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/opt/google# ls
chrome
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/opt/google#
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/opt/google# cd chrome/
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/opt/google/chrome# ls
MEIPreload cron libwidevinecdm.so natives_blob.bin product_logo_256.png resources.pak
chrome default-app-block locales product_logo_128.png product_logo_32.png swiftshader
chrome-sandbox default_apps nacl_helper product_logo_16.png product_logo_32.xpm v8_context_snapshot.bin
chrome_100_percent.pak google-chrome nacl_helper_bootstrap product_logo_22.png product_logo_48.png xdg-mime
chrome_200_percent.pak icudtl.dat nacl_irt_x86_64.nexe product_logo_24.png product_logo_64.png xdg-settings
root@rsys-robot-robot-ffb4b9f4d-mqdn4:~# cd /root/
root@rsys-robot-robot-ffb4b9f4d-mqdn4:~# ls
root@rsys-robot-robot-ffb4b9f4d-mqdn4:~# cd ..
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/# ls
bin boot dev etc home lib lib64 media mnt opt proc root run sbin share srv sys tmp usr var
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/# find . -name demo.sh
./var/opt/OpenECOMP_ETE/demo/boot/robot/demo.sh
find: './proc/1/map_files': Permission denied
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/# cd /var/opt/OpenECOMP_ETE/demo/boot/robot/
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/var/opt/OpenECOMP_ETE/demo/boot/robot# ls
demo.sh ete.sh integration_preload_parameters.py integration_robot_properties.py vm_config2robot.sh
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/var/opt/OpenECOMP_ETE/demo/boot/robot#
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/var/opt/OpenECOMP_ETE/demo/boot/robot# ./demo.sh init
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/var/opt/OpenECOMP_ETE/demo/boot/robot#
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/var/opt/OpenECOMP_ETE/demo/boot/robot# ./demo.sh
Usage: demo.sh <command> [<parameters>]

demo.sh init
- Execute both init_customer + distribute

demo.sh init_customer
- Create demo customer (Demonstration) and services, etc.

demo.sh distribute [<prefix>]
- Distribute demo models (demoVFW and demoVLB)

demo.sh preload <vnf_name> <module_name>
- Preload data for VNF for the <module_name>

demo.sh appc <module_name>
- provide APPC with vFW module mount point for closed loop

demo.sh init_robot [ <etc_hosts_prefix> ]
- Initialize robot after all ONAP VMs have started

demo.sh cds
- Instantiate vFW service with Controller Design Studio feature for the a demo customer (DemoCust<uuid>)

demo.sh instantiateVFW | instantiateVFWCL
- Instantiate vFW or vFWCL module for the a demo customer (DemoCust<uuid>)

demo.sh deleteVNF <module_name from instantiateVFW>
- Delete the module created by instantiateVFW

demo.sh heatbridge <stack_name> <service_instance_id> <service> [<ipv4-oam-address>]
- Run heatbridge against the stack for the given service instance and service
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/var/opt/OpenECOMP_ETE/demo/boot/robot# ./demo.sh init_robot
WEB Site Password for user 'test': root@rsys-robot-robot-ffb4b9f4d-mqdn4:/var/opt/OpenECOMP_ETE/demo/boot/robot#
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/var/opt/OpenECOMP_ETE/demo/boot/robot# ./demo.sh init
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/var/opt/OpenECOMP_ETE/demo/boot/robot#
root@rsys-robot-robot-ffb4b9f4d-mqdn4:/var/opt/OpenECOMP_ETE/demo/boot/robot# exit
exit
command terminated with exit code 127

    CommentAdd your comment...

    1 answer

    1.  
      2
      1
      0

      Balaji Shankaran to run /demo.sh you don't have to login to robot container bash. Just go to robot directory in git clone oom. You can find demo.sh there 

      root@oom1:~/oom/kubernetes/robot# ls
      Chart.yaml demo-k8s.sh ete-k8s.sh requirements.yaml resources templates values.yaml
      root@oom1:~/oom/kubernetes/robot#

      Running ./demo.sh init is required in order to initialize AAI but on boarding and distribution isn't mandatory. However, robot init will take care all these based on the inputs you provide. You can onboard and distribute your VNF manually.  

      1. Balaji Shankaran

        kranthi guttikonda 

        Thanks for the response. On the same note,

        is there any steps captured to add our itnernally developed component to eb part of ROBOT demo-k8s.sh/ete-k8s.sh scripts?

        Thanks

        Balaji Shankaran


      2. Sathish Kumar Muniappan

        my setup was k8s.

        ./oom/kubernetes/robot/ete-k8s.sh onap health

        am targeting with aai test case run. am not to  make ti pass.


        how to debug ?

      CommentAdd your comment...