civilinfrastructureplatform:ciptestingboardatdeskdingledevdeployment
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
civilinfrastructureplatform:ciptestingboardatdeskdingledevdeployment [2017/10/16 10:13] rajmarshall make the gpg verify output correct and update the git clone output |
civilinfrastructureplatform:ciptestingboardatdeskdingledevdeployment [2018/04/04 10:13] rajmarshall enhance private network note |
||
|---|---|---|---|
| Line 130: | Line 130: | ||
| 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 140: | Line 140: | ||
| '' 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'... | ||
| Line 161: | Line 160: | ||
| '' user@host:board-at-desk-single-dev$ '' | '' user@host:board-at-desk-single-dev$ '' | ||
| - | 5. If you wish to use the 1.0 release version rather than the git master then do: | ||
| - | ''git checkout v1.0'' | + | 5. Launch the Virtual Machine using Vagrant |
| - | + | ||
| - | 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. | 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. | ||
| Line 185: | Line 201: | ||
| - | 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
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
