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 [2018/03/14 10:55]
rajmarshall fixing pre-formatted output
civilinfrastructureplatform:ciptestingboardatdeskdingledevdeployment [2018/11/28 14:56] (current)
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_v1_0/​box/​cip_board_at_desk_v1.0.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_v1_0/​box/​cip_board_at_desk_v1.0.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** ''​
Line 79: 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** ''​
Line 94: Line 96:
    ​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 100: 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_v1.0.box cip-bad-sd1_0** ''​ ''​ user@host:​board-at-desk-single-dev$ **./​importbox.sh ../​cip_board_at_desk_v1.0.box cip-bad-sd1_0** ''​
Line 118: 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 143: Line 145:
 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'​...
Line 169: Line 171:
 // 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 6. The provisioning now requires a network restart during that process, at this point the output is
civilinfrastructureplatform/ciptestingboardatdeskdingledevdeployment.1521024954.txt.gz ยท Last modified: 2018/03/14 10:55 by rajmarshall