CMF![](/images/icons/linkext7.gif)
RDK Releases![](/images/icons/linkext7.gif)
Documentation![](/images/icons/linkext7.gif)
CMF Videos![](/images/icons/linkext7.gif)
Support
Support for CMF is provided by the RDK Support group.
To contact RDK Support:
Enter a ticket: https://jira.rdkcentral.com/
or
E-mail: support@rdkcentral.com
...
Template Tickets (these are cloned for each task)
Task | Template Ticket | ||||||||
---|---|---|---|---|---|---|---|---|---|
TDK Intake |
| ||||||||
RDK-B Iteration/Release |
| ||||||||
RDK-V Iteration/Release |
| ||||||||
RDK-B CODEMGMT Iteration |
| ||||||||
RDK-B CODEMGMT Quarterly Release |
| ||||||||
RDK-V CODEMGMT Iteration |
| ||||||||
RDK-V CODEMGMT Quarterly Release |
| ||||||||
RDK-C CODEMGMT Quarterly Release |
|
CMF Sanity Test Monitoring Test Descriptions
Emulator and RPI Reference Platform Documentation
draw.io Diagram | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Sanity Test Flows
DUT | Jenkins Sanity Test Flow Job | Comments |
---|---|---|
EMU-B | https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-rdkb-emulator-wifi-flow/ |
|
RPI-B | https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-rdkb-raspberrypi-wifi-flow/ | |
EMU-V | https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-hv04-emulators/ |
|
RPI-V | https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-rdkv-raspberrypi-flow/ |
|
RPI RefApp | https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-raspberrypi-refapp-flow/ |
|
RPI |
Thunder | https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test- |
raspberrypi- |
thunder-flow/ |
xg1v3
| |
RPI Westeros | https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-oss- |
raspberrypi- |
flow/ |
|
|
|
TDK Documentation and Releases
Emulator and RPI Reference Platform Documentation
CMF Test Framework Design
...
CMF TDK Testing is done using 3 frameworks (2 in active use):
DUT | TDK Framework | Jenkins Flow | TDK Manager URL | LabSlave | Comments |
---|---|---|---|---|---|
EMU-B | ATF | https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-atf-start-flow-emub/ | http://192.168.32.63/rdk-test-tool/?targetUri=%2Fexecution%2Fcreate | griffen | |
RPI-B | ATF | https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-atf-start-flow-rpib/ | http://192.168.32.69/rdk-test-tool/?targetUri=%2Fexecution%2Fcreate |
griffen |
RPI-V | ATF | https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-atf-start-flow-rpiv/ | http://192.168.32.70/rdk-test-tool/?targetUri=%2Fexecution%2Fcreate |
griffen |
EMU-V | RDKV-EMU | https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-emu-start-flow/ | see section "Access EMU-V TDK |
manager on web browser" in Useful Information | heron |
| |||||
|
| corvus |
|
All of which are kicked off with a set of input parameters to their various Jenkins jobs. Currently supporting 4 'RUNTYPE' options – 'release', 'nightly', 'nightly-full', and 'master' .(no longer used).
There is also a dry-rinBelow is each framework's instruction to run a flow job for the various RUNTYPE options and the differences those options make in regards to each phase of each flowrun option which we often to use the debug issues or for testing changes to the frameworks.
...
Test Metrics | Link |
---|---|
Nightly | CMF Nightly Test Metrics |
Iteration | CMF Iteration Test Metrics |
Quarterly | CMF Release Test Metrics |
...
Code Block |
---|
# clone the test repo git clone "https://code.rdkcentral.com/r/cmf/test" # gittiles link browse code in browser via gitiles (must be logged into gerrit) https://code.rdkcentral.com/r/plugins/gitiles/cmf/test # TDK test results repo (soon to be deprecated, used to store TDK reference results) git clone "https://code.rdkcentral.com/r/tata/test-results" # clone the jenkins dsl test repo where all our test jenkins jobs are maintained git clone "https://code.rdkcentral.com/r/cmf/jenkins-dsl/jobs/test" # setup the commit hook if you want push changes for review in CMF Gerrit cd <repo> gitdir=$(git rev-parse --git-dir); curl -o ${gitdir}/hooks/commit-msg https://code.rdkcentral.com/r/tools/hooks/commit-msg ; chmod +x ${gitdir}/hooks/commit-msg # useful git commands/workflow sequence if/when working on branches rather than pushing changes directly on master git checkout master git pull —rebase git checkout -b <branch name> … make changes git add <files> git commit -m "CMFLAB-XXX <commit msg>" git push origin <branch name> if single commit: git checkout master git cherry-pick <commit ID> git push origin HEAD:refs/for/master if multiple commits: git rebase -i HEAD~<# of commits from HEAD> … pick top commit; squash all others git log (**check to see that squashed commit has Change-ID) if no Change-ID in commit: git commit —amend; exit editor (Change-ID should now be there) git push origin HEAD:refs/for/master |
S3 Bucket | Purpose |
---|---|
s3://rdkcmf-test-results/ |
|
s3://rdkcmf-test-logs/ |
|
s3://rdkcmf-artifacts/jobs/ |
|
s3://rdkcmf-artifacts/jobs/test-manual-artifacts/ |
|
s3://rdkcmf-community-artifacts/jobs/ |
|
The test team maintain their own build scripts which we use to build and test debug images for defect investigations. These scripts are run on personal build slaves and can be used to build on any branch we support in CMF.
...
Code Block | ||
---|---|---|
| ||
cd ~/jenkinsroot/workspace/builds ./build_emub<platform>.sh <branch> <prepare|build> # Note follow the prompts to select what image(s) you want to build and whether you want to automatically smoke test the image # typical branches used are `rdk-next`, `rdk-dev-yymm`, `nightly/yyymmdd-rdk-dev`, `nightly/yyymmdd-rdk-next` |
...
on griffen:
Code Block | ||
---|---|---|
| ||
get_vpc_key -i 192.168.32.74 -u <username> griffen sudo su jenkins # general info commands vboxmanage list vms vboxmanage list runningvms vboxmanage showvminfo "rdkb-emu-tdk" vboxmanage list usbhost # restart vm (needed during runs where VM has crashed, i.e. ping not working) vboxmanage startvm "rdkb-emu-tdk" --type headless # if above restartstart doesn't work power it off first vboxmanage controlvm rdkb-emu-tdk poweroff vboxmanage startvm "rdkb-emu-tdk" --type headless # destroy VM - mechanism 1 vboxmanage controlvm rdkb-emu-tdk poweroff vboxmanage unregistervm "rdkb-emu-tdk" --delete # destroy VM - mechanism 2 vboxmanage startvm rdkb-emu-tdk --type emergencystop vboxmanage unregistervm --delete rdkb-emu-tdk # rdp session for RDK-B Emulator, run following ssh command then on RDP client connect to localhost:3388 ssh -o "PasswordAuthentication=no" -L 3388:192.168.32.74:3388 -i ~/.griffen-<username>.rsa <username>@192.168.32.74 |
...
Code Block | ||
---|---|---|
| ||
# do get vps on heron first get_vpc_key -i 192.168.32.76 -u <username> heron # ssh and tunnel through local port for the TDK Manager your interested in ssh -L 8085:192.168.21.31:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76 ssh -L 8086:192.168.21.32:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76 ssh -L 8087:192.168.21.33:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76 ssh -L 8088:192.168.21.34:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76 ssh -L 8089:192.168.21.35:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76 ssh -L 8090:192.168.21.36:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76 ssh -L 8091:192.168.21.38:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76 ssh -L 8092:192.168.21.39:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76 # now you can access any of the 8 TDK EMU-V TDK Managers in your browser via http://localhost:<port>/rdk-test-tool/execution/create # e.g. ssh -L 8085:192.168.21.31:8080 -i ~/.heron-jamescol.rsa jamescol@192.168.32.76 http://localhost:8086/rdk-test-tool/execution/create |
To connect to TDK Manager VM's used in ATF testing: EMU-B TDK Manager VM, RPI-B TDK VM, RPI-V TDK VM you can use one of two methods either via vagrant ssh or ssh directly using it’s IP
...
Sometimes it's useful to access the platform/DUT directly for defect investigation etc for emulators we can ssh to the device, for RPI's we can connect to the devices either by serial (via telnet on iolan) or by ssh'ing directly to the device.
For RPI Rack Setup and IP addresses, see
Code Block | ||
---|---|---|
| ||
# firstrdkb-emu connectTDK to griffenVM get_vpc_key -i 192.168.32.74 -u <username> griffen sudo su jenkins #ssh get list of VM's running and their status vagrant global-status # output will look like vagrant global-status id name provider state directory --------------------------o "StrictHostKeyChecking=no" root@10.5.25.100 # RPI via telnet # telnet <iolan ip> <port> # note the port number will follow the slot the RPI is in, e.g. 10001 is R03S01, 10008 is R03S08 telnet 10.5.25.5 10002 # use CTRL-] to quit # tip if you accidently hit CTRL-C while in a telnet session it will stop responding, quit and do following to recover # echo 03 | xxd -r -p | nc <iolan ip> <port> echo 03 | xxd -r -p | nc 10.5.25.5 10015 # RPI via ssh # ssh -o "StrictHostKeyChecking=no" root@<IP> # e.g. 2 RPI-B TDK ssh -o "StrictHostKeyChecking=no" root@10.5.25.102 ssh -o "StrictHostKeyChecking=no" root@10.5.25.108 # RDKV-EMU TDK Hybrids and Clients # these device IP's are not static so you either get it's IP from the console output of the # https://jenkins.cmf.code.rdkcentral.com/view/TEST/job/test-emu-prepare-dut/ job are use vagrant to connect on heron get_vpc_key -i 192.168.32.76 -u <username> heron sudo su jenkins vagrant global-status id name provider state directory ----------------------------------------------------------------------------------- f6380e9 nfs-server-rdkb ------------------------------------------------------------- 7a9a0d5 default virtualbox running /home/jenkins/jenkins2root/cmflab-vagrantsworkspace/nfs-server/rdkb 0885fe0 tdk-emulator-rdkb test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-hyb1 c8902cd default virtualbox running /home/jenkins/cmflab-vagrants/rdkb/emulator/tdk 5e18def tdk-emulator-rdkb-rpi /jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-mc1 11caf80 default virtualbox running /home/jenkins/cmflab-vagrants/rdkb/rpi/tdk f3fdd9a tdk-emulator-raven-atf-rpi-rdkv/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-hyb2 a0e30e0 default virtualbox running /home/jenkins/cmflab-vagrants/rdkv/rpi/tdk 81a242c tdk-emulator-rdkb-rpi-e2e/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-mc2 bee0188 default virtualbox running /home/jenkins/cmflab-vagrants/rdkb/rpi/tdk-e2e 1b99642 rdkb-webserver /jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-hyb3 e1fc8c3 default virtualbox running /home/jenkins/cmflab-vagrantsjenkins2root/rdkb/webserver # run command `vagrant ssh <id>` vagrant ssh 0885fe0 # some other vagrant commands vagrant status <id> vagrant halt <id> vagrant up <id> |
( ii ) via ssh
Code Block | ||
---|---|---|
| ||
# first connect to griffen or some other lab server machine (e.g. heron/corvus/raven)
get_vpc_key -i 192.168.32.74 -u <username> griffen
sudo su jenkins
# ssh to TDK VM using it's IP
# TDK Manager Emulator
ssh -o "StrictHostKeyChecking=no" vagrant@10.5.25.40
ssh -o "StrictHostKeyChecking=no" vagrant@192.168.32.63
http://192.168.32.63/rdk-test-tool/execution/create
# TDK Manager RPI-B
ssh -o "StrictHostKeyChecking=no" vagrant@10.5.25.41
ssh -o "StrictHostKeyChecking=no" vagrant@192.168.32.69
http://192.168.32.69/rdk-test-tool/execution/create
# TDK Manager RPI-V
ssh -o "StrictHostKeyChecking=no" vagrant@10.5.25.43
ssh -o "StrictHostKeyChecking=no" vagrant@192.168.32.70
http://192.168.32.70/rdk-test-tool/execution/create |
To connect to EMU-V VM's
workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-mc3
318efaa default virtualbox running /home/jenkins/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-hyb4
c0ef362 default virtualbox running /home/jenkins/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-mc4
1e66545 default virtualbox running /home/jenkins/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-hyb5
2f90e49 default virtualbox running /home/jenkins/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-mc5
d51c759 default virtualbox running /home/jenkins/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-hyb6
3bb2290 default virtualbox running /home/jenkins/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-mc6
186b64d default virtualbox running /home/jenkins/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-hyb7
1ad3bc7 default virtualbox running /home/jenkins/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-mc7
972eb8b default virtualbox running /home/jenkins/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-hyb8
b96a896 default virtualbox running /home/jenkins/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-mc8
# vagrant ssh <id>
vagrant ssh 7a9a0d5
# or also cd into relevant dir and ssh directly
cd /home/jenkins/jenkins2root/workspace/test-emu-prepare-dut/cmf_testbed/emulator/functional/em-tdk-hyb1
vagrant status
vagrant ssh
|
To connect to any of the TDK Manager VM's used in ATF testing: EMU-B TDK Manager VM, RPI-B TDK VM, RPI-V TDK VM you can use one of two methods either via vagrant ssh or ssh directly using it’s IP
( i ) via vagrant
Code Block | ||
---|---|---|
| ||
# first connect to griffen
get_vpc_key -i 192.168.32.74 -u <username> griffen
sudo su jenkins
# get list of VM's running and their status
vagrant global-status
# output will look like
vagrant global-status
id name provider state directory
| ||
Code Block | ||
| ||
# first connect to heron get_vpc_key -i 192.168.32.76 -u <uname> heron sudo su jenkins # get list of VM's running and their status vagrant global-status # output will list all emu-v VM's and the following TDK VM's vagrant global-status id name provider state directory ------------------------------------------------------------------------------------------------------------------------------------------------- eeacce1f6380e9 tdknfs-emulator-1server-rdkb virtualbox running /home/jenkins/manager-vagrant c4c70a1cmflab-vagrants/nfs-server/rdkb 0885fe0 tdk-emulator-2rdkb virtualbox running /home/jenkins/manager-vagrant 148b8d3cmflab-vagrants/rdkb/emulator/tdk 5e18def tdk-emulator-3-rdkb-rpi virtualbox running /home/jenkins/manager-vagrant 09ef373cmflab-vagrants/rdkb/rpi/tdk f3fdd9a tdk-emulator-4raven-atf-rpi-rdkv virtualbox running /home/jenkins/manager-vagrant e778206cmflab-vagrants/rdkv/rpi/tdk 81a242c tdk-emulator-5 virtualbox running /home/jenkins/manager-vagrant 9633df6 tdk-emulator-6-rdkb-rpi-e2e virtualbox running /home/jenkins/manager-vagrant 9e17573 tdk-emulator-7 virtualbox running /home/jenkins/manager-vagrant ae67a6f tdk-emulator-8/cmflab-vagrants/rdkb/rpi/tdk-e2e 1b99642 rdkb-webserver virtualbox running /home/jenkins/manager-vagrantcmflab-vagrants/rdkb/webserver # run command `vagrant ssh <id>` vagrant ssh eeacce10885fe0 # some other vagrant commands vagrant status <id> vagrant halt <id> vagrant up <id> |
( ii ) via ssh
Code Block | ||
---|---|---|
| ||
# iffirst vagrant-globalconnect statusto doesgriffen notor worksome (canother belab buggy)server machine (e.g. heron/corvus/raven) get_vpc_key -i 192.168.32.74 -u <username> griffen sudo su jenkins # ssh to TDK VM using it's IP # TDK Manager Emulator ssh -o "StrictHostKeyChecking=no" vagrant@10.5.25.40 ssh -o "StrictHostKeyChecking=no" vagrant@192.168.32.63 http://192.168.32.63/rdk-test-tool/execution/create # TDK Manager RPI-B ssh -o "StrictHostKeyChecking=no" vagrant@10.5.25.41 ssh -o "StrictHostKeyChecking=no" vagrant@192.168.32.69 http://192.168.32.69/rdk-test-tool/execution/create # TDK Manager RPI-V ssh -o "StrictHostKeyChecking=no" vagrant@10.5.25.43 ssh -o "StrictHostKeyChecking=no" vagrant@192.168.32.70 http://192.168.32.70/rdk-test-tool/execution/create |
To connect to any of the 8 EMU-V TDK VM's
Code Block | ||
---|---|---|
| ||
# first connect to heron get_vpc_key -i 192.168.32.76 -u <uname> heron sudo su jenkins # get list of VM's running and their status vagrant global-status # output will list all emu-v VM's and the following TDK VM's vagrant global-status idthen cd into dir where vagrants are run vagrant status cd /home/jenkins/manager-vagrant vagrant status Current machine states: tdk-emulator-1 running (virtualbox) tdk-emulator-2 running (virtualbox) tdk-emulator-3 running (virtualbox) tdk-emulator-4 running (virtualbox) tdk-emulator-5 running (virtualbox) tdk-emulator-6 running (virtualbox) tdk-emulator-7 name running (virtualbox) tdk-emulator-8 provider state running (virtualbox) vagrant ssh tdk-emulator-1 # to ssh using IP , cat the VagrantFile to get the IP for the manager you want cat /home/jenkins/manager-vagrant/Vagrantfile tdk_managers = [ {:hostname => 'tdk-emulator-1', :ip => '192.168.21.31', :box => 'ubuntu/trusty64'}, {:hostname => 'tdk-emulator-2', :ip => '192.168.21.32', :box => 'ubuntu/trusty64'}, {:hostname => 'tdk-emulator-3', :ip => '192.168.21.33', :box => 'ubuntu/trusty64'}, {:hostname => 'tdk-emulator-4', :ip => '192.168.21.34', :box => 'ubuntu/trusty64'}, {:hostname => 'tdk-emulator-5', :ip => '192.168.21.35', :box => 'ubuntu/trusty64'}, {:hostname => 'tdk-emulator-6', :ip => '192.168.21.36', :box => 'ubuntu/trusty64'}, {:hostname => 'tdk-emulator-7', :ip => '192.168.21.38', :box => 'ubuntu/trusty64'}, {:hostname => 'tdk-emulator-8', :ip => '192.168.21.39', :box => 'ubuntu/trusty64'} ] ssh -o "StrictHostKeyChecking=no" vagrant@192.168.21.31 <-- this is currently looking for password, need to check with ALAN |
Some General TDK Manager VM Commands
Code Block | ||
---|---|---|
| ||
# check if tftp server is running on the TDK Manager VM
vagrant@tdk-emulator-rdkb:~$ ps -ef | grep tftp
vagrant 12660 12630 0 12:17 pts/0 00:00:00 grep --color=auto tftp
root 13444 13389 0 Sep18 ? 00:00:00 sudo python /var/lib/tomcat6/webapps/rdk-test-tool/fileStore/tftp_server.py 69 /var/lib/tomcat6/webapps/rdk-test-tool/logs/logs/
root 13446 13444 0 Sep18 ? 00:00:05 python /var/lib/tomcat6/webapps/rdk-test-tool/fileStore/tftp_server.py 69 /var/lib/tomcat6/webapps/rdk-test-tool/logs/logs/
# Manually start TDK TFTP Server on a TDK VM (tftp server is used on manager to transfer agent logs from DUT)
sudo python /var/lib/tomcat6/webapps/rdk-test-tool/fileStore/tftp_server.py 69 /var/lib/tomcat6/webapps/rdk-test-tool/logs/logs/ &
# kill tftp serrver
sudo pkill -f tftp
# to manually set the route on TDK Manager VM (this is needed if you can't connect to the webui of VM via your browser), e.g. can happen when VM was restarted abnormally
route del default
sudo route del default; sudo route add default gw 192.168.32.1 dev eth1
# to change interface or mechanism for agent log transfer (can be set to tftp/REST) edit tm.config file and restart tomcat
vi /var/lib/tomcat6/webapps/rdk-test-tool/fileStore/tm.config
sudo pkill -f tftp
sudo service tomcat6 stop
sudo service tomcat6 start
|
Sometimes it's useful to access the platform/DUT directly for defect investigation etc for emulators we can ssh to the device, for RPI's we can connect to the devices either by serial (via telnet on iolan) or by ssh'ing directly to the device.
For RPI Rack Setup and IP addresses, see
...
language | bash |
---|
...
directory
-------------------------------------------------------------------------------------------------------------------------------------------------
eeacce1 tdk-emulator-1 virtualbox running /home/jenkins/manager-vagrant
c4c70a1 tdk-emulator-2 virtualbox running /home/jenkins/manager-vagrant
148b8d3 tdk-emulator-3 virtualbox running /home/jenkins/manager-vagrant
09ef373 tdk-emulator-4 virtualbox running /home/jenkins/manager-vagrant
e778206 tdk-emulator-5 virtualbox running /home/jenkins/manager-vagrant
9633df6 tdk-emulator-6 virtualbox running /home/jenkins/manager-vagrant
9e17573 tdk-emulator-7 virtualbox running /home/jenkins/manager-vagrant
ae67a6f tdk-emulator-8 virtualbox running /home/jenkins/manager-vagrant
# run command `vagrant ssh <id>`
vagrant ssh eeacce1
# some other vagrant commands
vagrant status <id>
vagrant halt <id>
vagrant up <id>
# if vagrant-global status does not work (can be buggy) then cd into dir where vagrants are run from and run command vagrant status
cd /home/jenkins/manager-vagrant
vagrant status
Current machine states:
tdk-emulator-1 running (virtualbox)
tdk-emulator-2 running (virtualbox)
tdk-emulator-3 running (virtualbox)
tdk-emulator-4 running (virtualbox)
tdk-emulator-5 running (virtualbox)
tdk-emulator-6 running (virtualbox)
tdk-emulator-7 running (virtualbox)
tdk-emulator-8 running (virtualbox)
vagrant ssh tdk-emulator-1
# to ssh using IP , cat the VagrantFile to get the IP for the manager you want
cat /home/jenkins/manager-vagrant/Vagrantfile
tdk_managers = [
{:hostname => 'tdk-emulator-1', :ip => '192.168.21.31', :box => 'ubuntu/trusty64'},
{:hostname => 'tdk-emulator-2', :ip => '192.168.21.32', :box => 'ubuntu/trusty64'},
{:hostname => 'tdk-emulator-3', :ip => '192.168.21.33', :box => 'ubuntu/trusty64'},
{:hostname => 'tdk-emulator-4', :ip => '192.168.21.34', :box => 'ubuntu/trusty64'},
{:hostname => 'tdk-emulator-5', :ip => '192.168.21.35', :box => 'ubuntu/trusty64'},
{:hostname => 'tdk-emulator-6', :ip => '192.168.21.36', :box => 'ubuntu/trusty64'},
{:hostname => 'tdk-emulator-7', :ip => '192.168.21.38', :box => 'ubuntu/trusty64'},
{:hostname => 'tdk-emulator-8', :ip => '192.168.21.39', :box => 'ubuntu/trusty64'}
]
ssh -o "StrictHostKeyChecking=no" vagrant@192.168.21.31 <-- this is currently looking for password, need to check with ALAN
|
Some General TDK Manager VM Commands
Code Block | ||
---|---|---|
| ||
# check if tftp server is running on the TDK Manager VM
vagrant@tdk-emulator-rdkb:~$ ps -ef | grep tftp
vagrant 12660 12630 0 12:17 pts/0 00:00:00 grep --color=auto tftp
root 13444 13389 0 Sep18 ? 00:00:00 sudo python /var/lib/tomcat6/webapps/rdk-test-tool/fileStore/tftp_server.py 69 /var/lib/tomcat6/webapps/rdk-test-tool/logs/logs/
root 13446 13444 0 Sep18 ? 00:00:05 python /var/lib/tomcat6/webapps/rdk-test-tool/fileStore/tftp_server.py 69 /var/lib/tomcat6/webapps/rdk-test-tool/logs/logs/
# Manually start TDK TFTP Server on a TDK VM (tftp server is used on manager to transfer agent logs from DUT)
sudo python /var/lib/tomcat6/webapps/rdk-test-tool/fileStore/tftp_server.py 69 /var/lib/tomcat6/webapps/rdk-test-tool/logs/logs/ &
# kill tftp serrver
sudo pkill -f tftp
# to manually set the route on TDK Manager VM (this is needed if you can't connect to the webui of VM via your browser), e.g. can happen when VM was restarted abnormally
route del default
sudo route del default; sudo route add default gw 192.168.32.1 dev eth1
# to change interface or mechanism for agent log transfer (can be set to tftp/REST) edit tm.config file and restart tomcat
vi /var/lib/tomcat6/webapps/rdk-test-tool/fileStore/tm.config
sudo pkill -f tftp
sudo service tomcat6 stop
sudo service tomcat6 start
|
The CMF procedure for flashing RPI's using UBOOT for automated testing is documented in RPI flashing procedure documentation
To format SD card using SD Formatter
To flash RDK SD cards with a prebuilt sd image:
Best results on linux seen with GNOME Partition Editor (gparted)
Install from universal repositories, requires super user permissions to run the program.
Partitioning Info:
16GB SSD Layout:
Partition | Label | Designation | File System | Size (MiB) |
---|---|---|---|---|
1 | BOOT | Primary | Fat32 | 488 |
2 | RDK | Primary | EXT4 | 2048 |
3 | UBU | Primary | EXT4 | 10240 |
4 | DATA | Primary | EXT4 | (Remaining Space) |
32GB SSD Layout:
Partition | Label | Designation | File System | Size (MiB) |
---|---|---|---|---|
1 | BOOT | Primary | Fat32 | 488 |
2 | RDK | Primary | EXT4 | 10240 |
3 | UBU | Primary | EXT4 | 10240 |
4 | DATA | Primary | EXT4 | (Remaining Space) |
Important: the boot partition must be populated at a bare minimum before the ssd is put into a DUT for the CMF Automation to succeed.
The partitions created in the previous section should be mounted to your filesystem, in recent ubuntu, these should mount to
...
# Acquire an RDK Build archive:
$ aws s3 ls s3://rdkcmf-artifacts/jobs/community-build-rdkv-raspberrypi/
# Choose latest build number, e.g. 1472, check files therein, then copy the build to your local workspace:
$ aws s3 cp s3://rdkcmf-artifacts/jobs/community-build-rdkv-raspberrypi/1472/test-archive-rdk-hybrid-raspberrypi-community-nightly-<build-id>.tar.gz .
# Extract the archive into a local directory:
$ mkdir rdk-hybrid && tar xvzf test-archive-rdk-hybrid-raspberrypi-community-nightly-<build-id>.tar.gz -C rdk-hybrid
# Configure u-boot as explicit kernel image for first time sd provisioning:
# Edit the file rdk-hybrid/boot/config.txt, find the line `#kernel=""` and change it to `kernel=u-boot.bin`, save and close the file.
# Copy the boot contents to BOOT partition
$ cp -r rdk-hybrid/boot /media/($USER)/BOOT
# Extract the root filesystem to RDK partition
$ tar xvjf rdk-hybrid/rootfs/rdk-generic-hybrid-wpe-image-raspberrypi-rdk-hybrid.tar.bz2 -C /media/($USER)/RDK
# Provisioning RDK-CMF-UBUNTU (WiFi Client):
# Acquire RDK-CMF-Ubuntu:
$ aws s3 ls s3://rdkcmf-artifacts/test-artifacts/test-ubuntu-artifacts
# Choose latest build number, e.g. 3, check files therein, then copy the build root file system (rootfs) to your local workspace (No need for boot filesystem):
$ aws s3 cp s3://rdkcmf-artifacts/test-artifacts/test-ubuntu-artifacts/3/ubuntu_rootfs_<build-sha>.tar.bz2 .
# Extract the archive into the SSD UBU Partition:
$ tar xvjf ubuntu_rootfs_<build-sha>.tar.bz2 -C /media/($USER)/UBU
# Ensure all Read/Write cases complete
$ sudo sync
Unmount/Eject the sd card and transfer to the DUT