User Tools

Site Tools


civilinfrastructureplatform:ciptestingboardatdeskdingledevdeployment

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
civilinfrastructureplatform:ciptestingboardatdeskdingledevdeployment [2017/08/16 14:41]
rajmarshall [Warnings and Errors during Vagrant Up Process] test image
civilinfrastructureplatform:ciptestingboardatdeskdingledevdeployment [2018/11/28 14:56]
rajmarshall improve snapshot info
Line 17: Line 17:
 ''​ user@host:​cip$ ''​ ''​ user@host:​cip$ ''​
  
-3. Download the latest ​version of the pre-provisioned box using the command line as shown or by simply clicking the given link below. ​+3. Download the 1.0 version of the pre-provisioned box using the command line as shown or by simply clicking the given link below. ​
  
-''​ user@host:​cip$ **wget https://​s3-us-west-2.amazonaws.com/​download.cip-project.org/​ciptesting/​b%40d/​b%40d_v0_9_1/box/cip_board_at_desk_v0.9.1.box** ''​+''​ user@host:​cip$ **wget https://​s3-us-west-2.amazonaws.com/​download.cip-project.org/​ciptesting/​b%40d/​b%40d_v1_0/box/cip_board_at_desk_v1.0.box** ''​
  
  
-4. Download the latest ​version of the VM's sha256sum so we can confirm that what we received was not modified.+4. Download the 1.0 version of the VM's sha256sum so we can confirm that what we received was not modified.
  
-''​ user@host:​cip$ **wget https://​s3-us-west-2.amazonaws.com/​download.cip-project.org/​ciptesting/​b%40d/​b%40d_v0_9_1/box/cip_board_at_desk_v0.9.1.sha256sum** ''​+''​ user@host:​cip$ **wget https://​s3-us-west-2.amazonaws.com/​download.cip-project.org/​ciptesting/​b%40d/​b%40d_v1_0/box/cip_board_at_desk_v1.0.sha256sum** ''​
  
 // Note: You may need to install the sha256sum program using your distro'​s package manager. // // Note: You may need to install the sha256sum program using your distro'​s package manager. //
Line 30: Line 30:
 5. Download the VM's signature so we can verify the VM signature matches. 5. Download the VM's signature so we can verify the VM signature matches.
  
-''​ user@host:​cip$ **wget https://​s3-us-west-2.amazonaws.com/​download.cip-project.org/​ciptesting/​b%40d/​b%40d_v0_9_1/box/cip_board_at_desk_v0.9.1.box.sig** ''​+''​ user@host:​cip$ **wget https://​s3-us-west-2.amazonaws.com/​download.cip-project.org/​ciptesting/​b%40d/​b%40d_v1_0/box/cip_board_at_desk_v1.0.box.sig** ''​
  
 6. Download the CIP VM signer'​s public key 6. Download the CIP VM signer'​s public key
  
-''​ user@host:​cip$ **wget https://​s3-us-west-2.amazonaws.com/​download.cip-project.org/​ciptesting/​b%40d/​b%40d_v0_9_1/​sources/​pubkey.txt** ''​+''​ user@host:​cip$ **wget https://​s3-us-west-2.amazonaws.com/​download.cip-project.org/​ciptesting/​b%40d/​b%40d_v1_0/​sources/​pubkey.txt** ''​
  
 ==== Using SHA256sum and GPG to check integrity and signature of pre-provisioned box ==== ==== Using SHA256sum and GPG to check integrity and signature of pre-provisioned box ====
Line 42: Line 42:
 ''​ user@host:​cip$ **<​nowiki>​gpg --import pubkey.txt</​nowiki>​** ''​ ''​ user@host:​cip$ **<​nowiki>​gpg --import pubkey.txt</​nowiki>​** ''​
  
-   gpg: key 73715D37: "​Robert Marshall (Codething) <​robert.marshall@codethink.co.uk>" ​added +  ​gpg: key 33D89A0573715D37public key "​Robert Marshall (Codething) <​robert.marshall@codethink.co.uk>" ​imported 
-   ​gpg: Total number processed: 1+  gpg: Total number processed: 1 
 +  gpg:               ​imported:​ 1 
 + 
  
 8. Calculate the SHA256 sum of the Virtual Machine box file 8. Calculate the SHA256 sum of the Virtual Machine box file
  
-''​ user@host:​cip$ **<​nowiki>​sha256sum --check ​cip_board_at_desk_v0.9.1.sha256sum</​nowiki>​** ''​+''​ user@host:​cip$ **<​nowiki>​sha256sum --check ​cip_board_at_desk_v1.0.sha256sum</​nowiki>​** ''​
  
-'' ​cip_board_at_desk_v0.9.1.box: OK ''​+'' ​cip_board_at_desk_v1.0.box: OK ''​
  
 We are looking for the line that says **OK**. This tells us that the sha256sum'​s are the same. We are looking for the line that says **OK**. This tells us that the sha256sum'​s are the same.
Line 55: Line 57:
 9. Verify the signature of the CIP VM 9. Verify the signature of the CIP VM
  
-''​ user@host:​cip$ **<​nowiki>​gpg --verify ​cip_board_at_desk_v0.9.1.box.sig ​cip_board_at_desk_v0.9.1.box</​nowiki>​** ''​+''​ user@host:​cip$ **<​nowiki>​gpg --verify ​cip_board_at_desk_v1.0.box.sig ​cip_board_at_desk_v1.0.box</​nowiki>​** ''​
  
-   gpg: Signature made Thu 25 May 2017 09:27:45 BST using RSA key ID 73715D37+   gpg --verify cip_board_at_desk_v1.0.box.sig cip_board_at_desk_v1.0.box 
 +   gpg: Signature made Fri 13 Oct 2017 11:36:06 BST using RSA key ID 0647F909
    gpg: Good signature from "​Robert Marshall (Codething) <​robert.marshall@codethink.co.uk>"​    gpg: Good signature from "​Robert Marshall (Codething) <​robert.marshall@codethink.co.uk>"​
    gpg: WARNING: This key is not certified with a trusted signature!    gpg: WARNING: This key is not certified with a trusted signature!
-   gpg: There is no indication that the signature belongs to the owner. +   ​gpg: ​         There is no indication that the signature belongs to the owner. 
-   ​Primary key fingerprint: ​8B2E 53ED 058B 79F3 E162  A001 33D8 9A05 7371 5D37+   ​Primary key fingerprint: ​83B2 E0FD 9B33 61ED 2C0E  381C 318B 48B3 0647 F909
  
-We are looking for the 2nd line stating that this is a **Good signature...**+We are looking for the 2nd output ​line stating that this is a **Good signature...**
  
 // Note: The Warnings shown above are normal, as they depend on your setup and configuration. Here are explanations for the warnings you might encounter://​ // Note: The Warnings shown above are normal, as they depend on your setup and configuration. Here are explanations for the warnings you might encounter://​
Line 76: Line 79:
 // This refers to your level of trust in your belief that you possess our real public key. This is a personal decision. Ideally, a CIP developer would hand you the key in person, but more commonly, you downloaded it. Was the download tampered with? Probably not, but this decision is up to you. Setting up a web of trust is one method for trusting them. See the GPG documentation for more information on how to work with public keys: [[http://​www.gnupg.org/​gph/​en/​manual/​x334.html]] // // This refers to your level of trust in your belief that you possess our real public key. This is a personal decision. Ideally, a CIP developer would hand you the key in person, but more commonly, you downloaded it. Was the download tampered with? Probably not, but this decision is up to you. Setting up a web of trust is one method for trusting them. See the GPG documentation for more information on how to work with public keys: [[http://​www.gnupg.org/​gph/​en/​manual/​x334.html]] //
  
 +
 +10. If you wish to use the snapshot release go to the [[cipdownload#​snapshot-b-d-box|Download]] page and use the links for the snapshot from there, continue from step 6 above.
  
 ==== Import the box into Vagrant and launch the Virtual Machine ==== ==== Import the box into Vagrant and launch the Virtual Machine ====
  
-10. Clone the board-at-desk-single-dev GitLab Project+11. Clone the board-at-desk-single-dev GitLab Project
  
 ''​ user@host:​cip$ **git clone https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev** ''​ ''​ user@host:​cip$ **git clone https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev** ''​
  
    ​Cloning into '​board-at-desk-single-dev'​...    ​Cloning into '​board-at-desk-single-dev'​...
-   ​remote:​ Counting objects: ​465, done. +   ​remote:​ Counting objects: ​588, done. 
-   ​remote:​ Compressing objects: 100% (171/171), done. +   ​remote:​ Compressing objects: 100% (248/248), done. 
-   ​remote:​ Total 465 (delta ​291), reused ​463 (delta ​290+   ​remote:​ Total 588 (delta ​369), reused ​548 (delta ​338
-   ​Receiving objects: 100% (465/465), 15.06 MiB | 16.92 MiB/s, done. +   ​Receiving objects: 100% (588/588), 15.09 MiB | 8.92 MiB/s, done. 
-   ​Resolving deltas: 100% (291/291), done. +   ​Resolving deltas: 100% (369/369), done. 
-   ​Checking connectivity... done.+   ​Checking connectivity... done. 
  
-11. Change to the newly created board-at-desk-single-dev directory.+12. Change to the newly created board-at-desk-single-dev directory.
  
 ''​ user@host:​cip$ **cd board-at-desk-single-dev** ''​ ''​ user@host:​cip$ **cd board-at-desk-single-dev** ''​
Line 97: Line 102:
 ''​ user@host:​board-at-desk-single-dev$ ''​ ''​ user@host:​board-at-desk-single-dev$ ''​
  
-12. Import the Virtual Machine into Vagrant and launch the VM+13. Import the Virtual Machine into Vagrant and launch the VM
  
-''​ user@host:​board-at-desk-single-dev$ **./​importbox.sh ../cip_board_at_desk_v0.9.1.box cip-bad-sd0_91** ''​+''​ user@host:​board-at-desk-single-dev$ **./​importbox.sh ../cip_board_at_desk_v1.0.box cip-bad-sd1_0** ''​
  
    ​==>​ box: Box file was not detected as metadata. Adding it directly...    ​==>​ box: Box file was not detected as metadata. Adding it directly...
-   ​==>​ box: Adding box '​cip-bad-sd0_91' (v0) for provider:  +   ​==>​ box: Adding box '​cip-bad-sd1_0' (v0) for provider:  
-       box: Unpacking necessary files from: file:///​home/​user/​cip/​cip_board_at_desk_v0.9.1.box +       box: Unpacking necessary files from: file:///​home/​user/​cip/​cip_board_at_desk_v1.0.box 
-   ​==>​ box: Successfully added box '​cip-bad-sd0_91' (v0) for '​virtualbox'​! ​+   ​==>​ box: Successfully added box '​cip-bad-sd1_0' (v0) for '​virtualbox'​! ​
    ...    ...
    the VM will begin to boot    the VM will begin to boot
Line 115: Line 120:
 // Note: If you see an error message stating: The SSH command responded with a non-zero exit status. You can safely ignore this error, we will be connecting to the VM using SSH in the next step. // // Note: If you see an error message stating: The SSH command responded with a non-zero exit status. You can safely ignore this error, we will be connecting to the VM using SSH in the next step. //
  
-13. Next, you will move on to the [[ciptestingboardatdesksingledevsetup|B@D Setup and Configuration wiki page]]+14. Next, you will move on to the [[ciptestingboardatdesksingledevsetup|B@D Setup and Configuration wiki page]]
  
 ---- ----
Line 127: Line 132:
 This tutorial needs the same list of **prerequisites** as those listed [[ciptestingboardatdesksingledevfeaturepage#​prerequisites|on the features page]]. This tutorial needs the same list of **prerequisites** as those listed [[ciptestingboardatdesksingledevfeaturepage#​prerequisites|on the features page]].
  
-==== Clone the CIP B@D Repo, Build the Virtual Machine ​and Run Example Tests ====+==== Clone the CIP Vagrant ​Repo and launch ​the Virtual Machine ====
  
 1. Create a clean directory to hold the Vagrant files needed to build the Virtual Machine (VM) from scratch. We will use the ''/​home/​user/​v_cip''​ directory in these instructions,​ but you can replace it with whatever makes the most sense for you. 1. Create a clean directory to hold the Vagrant files needed to build the Virtual Machine (VM) from scratch. We will use the ''/​home/​user/​v_cip''​ directory in these instructions,​ but you can replace it with whatever makes the most sense for you.
Line 137: Line 142:
 ''​ user@host:​v_cip$ ''​ ''​ user@host:​v_cip$ ''​
  
-==== Clone the CIP Vagrant Repo and launch the Virtual Machine ==== 
  
 3. Clone the board-at-desk-single-dev GitLab Project 3. Clone the board-at-desk-single-dev GitLab Project
  
-''​ user@host:cip$ **git clone https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev** ''​+''​ user@host:v_cip$ **git clone https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev** ''​
  
    ​Cloning into '​board-at-desk-single-dev'​...    ​Cloning into '​board-at-desk-single-dev'​...
-   ​remote:​ Counting objects: ​465, done. +   ​remote:​ Counting objects: ​588, done. 
-   ​remote:​ Compressing objects: 100% (171/171), done. +   ​remote:​ Compressing objects: 100% (248/248), done. 
-   ​remote:​ Total 465 (delta ​291), reused ​463 (delta ​290+   ​remote:​ Total 588 (delta ​369), reused ​548 (delta ​338
-   ​Receiving objects: 100% (465/465), 15.06 MiB | 16.92 MiB/s, done. +   ​Receiving objects: 100% (588/588), 15.09 MiB | 8.92 MiB/s, done. 
-   ​Resolving deltas: 100% (291/291), done. +   ​Resolving deltas: 100% (369/369), done. 
-   ​Checking connectivity... done.+   ​Checking connectivity... done.  
 +   
  
 4. Change to the newly created board-at-desk-single-dev directory. 4. Change to the newly created board-at-desk-single-dev directory.
Line 157: Line 162:
 ''​ user@host:​board-at-desk-single-dev$ ''​ ''​ user@host:​board-at-desk-single-dev$ ''​
  
-5. If you wish to use the 0.9.1 release version rather than the git master then do: 
  
-''​git checkout v0.9.1''​ +5. Launch the Virtual Machine using Vagrant
-// Note that the 0.9.1 release will not work for the Windows 10 version of Board at Desk, you need the git master. // +
- +
-6. Launch the Virtual Machine using Vagrant+
  
 ''​ user@host:​board-at-desk-single-dev$ **vagrant up**''​ ''​ user@host:​board-at-desk-single-dev$ **vagrant up**''​
  
-Example output from the launch is available in the [[https://​gitlab.com/​cip-project/​cip-testing/​CIP-kernel-test-logs/​blob/​b589e0b68f891a9c0fe044502abcc9541203b1c1/​vagrant-up.output|CIP-kernel-test-logs ]] repos.+Example output from the launch is available in the [[https://​gitlab.com/​cip-project/​cip-testing/​CIP-kernel-test-logs/​blob/​master/​vagrant-up.output|CIP-kernel-test-logs ]] repos.
  
 // Note: One Ethernet port on the VM is Bridged, so it will ask you which one of the Ethernet Adapters on the host machine you wish to bridge. You can automate this by adding your desired Ethernet port in the Vagrantfile. ​ // Note: One Ethernet port on the VM is Bridged, so it will ask you which one of the Ethernet Adapters on the host machine you wish to bridge. You can automate this by adding your desired Ethernet port in the Vagrantfile. ​
 e.g. change the config.vm.network line  to\\ <​nowiki>​config.vm.network "​public_network",​ use_dhcp_assigned_default_route:​ true,  :bridge => '​eth0'</​nowiki>//​ e.g. change the config.vm.network line  to\\ <​nowiki>​config.vm.network "​public_network",​ use_dhcp_assigned_default_route:​ true,  :bridge => '​eth0'</​nowiki>//​
 +
 +// Note: The Vagrant instance uses a private network to communicate with an attached board connected via a host USB, this network uses the IP address 192.168.22.0 if this will clash with your network settings then you will need to edit the Vagrant file and also alter integration-scripts/​configure_lava.sh before running `vagrant up`. //
 +
 +6. The provisioning now requires a network restart during that process, at this point the output is
 +
 +
 +   ​==>​ default: Setting up net-tools (1.60+git20161116.90da8a0-1) ...
 +   ​==>​ default: now run vagrant halt; vagrant up; vagrant provision; ​
 +   ​==>​ default: to complete b@d provisioning
 +   The SSH command responded with a non-zero exit status. Vagrant
 +   ​assumes that this means the command failed. The output for this command
 +   ​should be in the log above. Please read the output to determine what
 +   went wrong.
 +
 +So as instructed:
 +
 +''​ user@host:​board-at-desk-single-dev$ **vagrant halt**''​ \\ 
 +''​ user@host:​board-at-desk-single-dev$ **vagrant up**''​ \\
 +''​ user@host:​board-at-desk-single-dev$ **vagrant provision**''​
 +
 +
 +7. Restart the Virtual Machine using Vagrant (this step is necessary in order for the LAVA configuration to take effect). See [[https://​wiki.linuxfoundation.org/​civilinfrastructureplatform/​ciptestingknownissues#​b-d-virtual-machine-troubleshooting-guide|Troubleshooting Guide]] for a fuller description of the issue.
 +
 +''​ user@host:​board-at-desk-single-dev$ **vagrant halt**''​ \\ 
 +''​ user@host:​board-at-desk-single-dev$ **vagrant up**''​
 +
  
 ==== Warnings and Errors during Vagrant Up Process ==== ==== Warnings and Errors during Vagrant Up Process ====
Line 175: Line 202:
 Please see the [[https://​wiki.linuxfoundation.org/​civilinfrastructureplatform/​ciptestingknownissues|B@D Known Issues, Workarounds and Troubleshooting Guide]] page for any errors or warnings you may encounter. Please see the [[https://​wiki.linuxfoundation.org/​civilinfrastructureplatform/​ciptestingknownissues|B@D Known Issues, Workarounds and Troubleshooting Guide]] page for any errors or warnings you may encounter.
  
-(Please ignore this: 
- ​{{:​civilinfrastructureplatform:​b_d-4.jpg?​200|}} - only there for testing) 
  
-6. Next, you will move on to the [[ciptestingboardatdesksingledevsetup|B@D Setup and Configuration wiki page]]+8. Next, you will move on to the [[ciptestingboardatdesksingledevsetup|B@D Setup and Configuration wiki page]]
    
civilinfrastructureplatform/ciptestingboardatdeskdingledevdeployment.txt · Last modified: 2018/11/28 14:56 by rajmarshall