User Tools

Site Tools


civilinfrastructureplatform:ciptestingboardatdesksingledevfeaturepage

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:ciptestingboardatdesksingledevfeaturepage [2017/10/18 09:50]
rajmarshall [Other tools] correct python licence link
civilinfrastructureplatform:ciptestingboardatdesksingledevfeaturepage [2018/11/28 14:35] (current)
rajmarshall [Snapshot Release] sublink the snapshot on downloads
Line 36: Line 36:
 ==== initramfs is now built locally ==== ==== initramfs is now built locally ====
  
-Previously, Board At Desk was using the initiramfs ​provided by Linaro in their infrastructure. This created in B@D a dependency on the network connection latency that, under certain circumstances led to errors due to timeouts and that Linaro built version ran more slowly with an internal timeout. Now initramfs is [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​41|built locally]] which improves the speed of the tests, also removing that need to access the internet.+Previously, Board At Desk was using the initramfs ​provided by Linaro in their infrastructure. This created in B@D a dependency on the network connection latency that, under certain circumstances led to errors due to timeouts and that Linaro built version ran more slowly with an internal timeout. Now initramfs is [[https://​gitlab.com/​cip-project/​cip-testing/​board-at-desk-single-dev/​merge_requests/​41|built locally]] which improves the speed of the tests, also removing that need to access the internet.
  
 ==== Bug Fixes ==== ==== Bug Fixes ====
Line 45: Line 45:
 ===== What is Board At Desk v1.0? ===== ===== What is Board At Desk v1.0? =====
  
-At a high level, Board At Desk is a testing environment based on two basic components, LAVA and kernelci designed to allow any developer to test locally on any board a Linux kernel or a simple Linux based system, evaluate the results and share them, together with the logs, with their colleagues. What makes B@D different is that in order to do so, there is need for a managed centralised service. It is designed to run locally. ​+At a high level, Board At Desk is a testing environment based on two basic components, LAVA and kernelci designed to allow any developer to test locally on any board a Linux kernel or a simple Linux based system, evaluate the results and share them, together with the logs, with their colleagues. What makes B@D different is that in order to do so, there is no need for a managed centralised service. It is designed to run locally. ​
  
 Board At Desk - Single Developer, ​ creates and publishes a VM that contains all the kernelci tools. Testing of any kernel is enabled by the installation of LAVA and the supply of, currently, a small number of health checks and reference tests. The test results can then be shared with other developers by using LAVA notifications either directly or via the [[https://​lists.cip-project.org/​mailman/​listinfo/​cip-testing-results|cip-testing-results]] email list. Board At Desk - Single Developer, ​ creates and publishes a VM that contains all the kernelci tools. Testing of any kernel is enabled by the installation of LAVA and the supply of, currently, a small number of health checks and reference tests. The test results can then be shared with other developers by using LAVA notifications either directly or via the [[https://​lists.cip-project.org/​mailman/​listinfo/​cip-testing-results|cip-testing-results]] email list.
Line 51: Line 51:
 If we take a deeper look, there are several technologies and configurations involved. This block diagram tries to give a little more detail.  ​ If we take a deeper look, there are several technologies and configurations involved. This block diagram tries to give a little more detail.  ​
  
-Board At Desk - Single Dev. block diagram- this lays out the structure of the testing environment. The host running GNU/Linux or Windows 10 runs B@D within a Vagrant environment,​ this environment is provisioned during initial boot with the kernelci and LAVA packages which pull in other necessary tools using ansible, apt-get and git so that the box is ready for kernel builds and testing. {{ :​civilinfrastructureplatform:​b_d_v1_0_block_diagram.jpg |}}+Board At Desk - Single Dev. block diagram- this lays out the structure of the testing environment. The host running GNU/Linux or Windows 10 runs B@D within a Vagrant environment,​ this environment is provisioned during initial boot with the kernelci and LAVA packages which pull in other necessary tools using ansible, apt-get and git so that the box is ready for kernel builds and testing. {{ :​civilinfrastructureplatform:​b_d_git_block_diagram.jpg?600 |}}
  
 These are the main software components and the versions shipped in the previous version compared to the current one. These are the main software components and the versions shipped in the previous version compared to the current one.
Line 57: Line 57:
 ==== Virtualization ==== ==== Virtualization ====
  
-^  Tool  ^  Version in v0.9.1 release ​ ^   ​Version in v1.0 release ^  License ^ +^  Tool  ^  Version in v0.9.1 release ​ ^   ​Version in v1.0 release ^ Version in git ^ License ^ 
-|  Vagrant ​          ​| ​ v1.8.1 ​ |  v1.9.1 ​ |  MIT  | +|  Vagrant ​          ​| ​ v1.8.1 ​ |  v1.9.1 ​ ​| ​ v2.0.4 ​ ​| ​ MIT  | 
-|  VirtualBox ​       |  v4.3  |  v4.3  |  GPLv2  |+|  VirtualBox ​       |  v4.3  |  v4.3  |  ​v5.2.10 ​ | GPLv2  |
  
 ==== KernelCI ==== ==== KernelCI ====
Line 65: Line 65:
 KernelCI components included in this release vs the previous one: KernelCI components included in this release vs the previous one:
  
-^  Tool  ^  Version in v0.9.1 release ​ ^   ​Version in v1.0 release ​ ^   ​License ​ ^ +^  Tool  ^  Version in v0.9.1 release ​ ^   ​Version in v1.0 release ​ ^  ​Version in git ^ License ​ ^ 
-|  board-at-desk-single-dev ​ |  v0.9.1 ​ |  v1.0  |  AGPLv3 ​ | +|  board-at-desk-single-dev ​ |  v0.9.1 ​ |  v1.0  ​|  AGPLv3 ​ | 
-|  kernelci-backend ​ |  v2017.3.2 ​ |  v2017.7.2 ​ |  AGPLv3 ​ | +|  kernelci-backend ​ |  v2017.3.2 ​ |  v2017.7.2  |  v2018.2  |  AGPLv3 ​ | 
-|  kernelci-backend-config ​ |  v0.9.1 ​ |  v2017.7.2 ​ |  AGPLv3 ​ | +|  kernelci-backend-config ​ |  v0.9.1 ​ |  v2017.7.2  |  v2018.2  |  AGPLv3 ​ | 
-|  kernelci-frontend ​ |  v2017.5 ​ |  v2017.7.1 ​ |  AGPLv3 ​ | +|  kernelci-frontend ​ |  v2017.5 ​ |  v2017.7.1 ​ ​| ​ v2018.2 ​ ​| ​ AGPLv3 ​ | 
-|  kernelci-frontend-config ​ |   ​| ​ v2017.7.1 ​ |  AGPLv3 ​ | +|  kernelci-frontend-config ​ |   ​| ​ v2017.7.1 ​ ​| ​ v2018.2 ​ ​| ​ AGPLv3 ​ | 
-|  kernelci-build ​    ​| ​ v0.9.1 ​ |  v1.0   ​| ​ LGPLv2.1 ​ | +|  kernelci-build ​    ​| ​ v0.9.1 ​ |  v1.0   |  LGPLv2.1 ​ | 
-|  Ansible ​ |  v2.3.0.0 ​ |  v2.4.0.0 ​ |  [[https://​github.com/​ansible/​ansible/​blob/​devel/​COPYING|GPLv3.0]] ​ | +|  Ansible ​ |  v2.3.0.0 ​ |  v2.4.0.0 ​ ​| ​ v2.5.2 ​ ​| ​ [[https://​github.com/​ansible/​ansible/​blob/​devel/​COPYING|GPLv3.0]] ​ | 
-|  Flask framework ​ |  v0.10.1 ​ |  v.0.10.1 ​ |  BSD 3-clause ​ | +|  Flask framework ​ |  v0.10.1 ​ |  v.0.10.1  |  v0.10.1  |  BSD 3-clause ​ | 
-|  Nginx Web Server ​ |  1.10.3-1 ​ |  1.10.3-1 ​ |  BSD 3-clause ​ | +|  Nginx Web Server ​ ​| ​ 1.10.3-1 ​ ​| ​ 1.10.3-1 ​ |  1.10.3-1 ​ |  BSD 3-clause ​ | 
-|  MongoDB Database ​ |   ​3.2.13 ​ |  3.2.11-2 ​ |  [[https://​github.com/​mongodb/​mongo/​blob/​master/​GNU-AGPL-3.0.txt|AGPLv3]] and language drivers under [[https://​github.com/​mongodb/​mongo/​blob/​master/​APACHE-2.0.txt|Apache v2.0]] ​ | +|  MongoDB Database ​ |   ​3.2.13 ​ ​| ​ 3.2.11-2 ​ ​| ​ 3.2.11-2 ​ |  [[https://​github.com/​mongodb/​mongo/​blob/​master/​GNU-AGPL-3.0.txt|AGPLv3]] and language drivers ​\\ under [[https://​github.com/​mongodb/​mongo/​blob/​master/​APACHE-2.0.txt|Apache v2.0]] ​ | 
-|  ARM Cross-Compiler ​ |  6.3.0-16 ​ |  6.3.0-18 ​ |  --  | +|  ARM Cross-Compiler ​ |  6.3.0-16 ​ ​| ​ 6.3.0-18 ​ ​| ​ 6.3.0-18 ​ |  --  | 
-|  ARMhf Cross Compiler |  6.3.0-16 ​ |  6.3.0-18 ​ |  --  |+|  ARMhf Cross Compiler |  6.3.0-16 ​ ​| ​ 6.3.0-18 ​ ​| ​ 6.3.0-18 ​ |  --  |
  
 ==== LAVAv2 ==== ==== LAVAv2 ====
Line 83: Line 83:
 LAVAv2 components included in this Board at Desk v1.0 are: LAVAv2 components included in this Board at Desk v1.0 are:
  
-^  Tool  ^  Version in v0.9.1 release ​ ^   ​Version in v1.0 release ^  License ​ ^ +^  Tool  ^  Version in v0.9.1 release ​ ^   ​Version in v1.0 release ^   Version in git ^ License ​ ^ 
-|  LAVAv2 ​ |  2016.12-1 ​ |  2017-7-1 ​ |  [[https://​github.com/​Linaro/​lava-server/​blob/​release/​COPYING.AGPL-3|AGPLv3]] ​ | +|  LAVAv2 ​ |  2016.12-1 ​ |  2017-7-1 ​ |  ​2018-4-1 ​ | [[https://​github.com/​Linaro/​lava-server/​blob/​release/​COPYING.AGPL-3|AGPLv3]] ​ | 
-|  Apache Web Server ​ |  v2.4.25-3 ​ |  v2.4.25-3 ​ |  Apache v2  | +|  Apache Web Server ​ |  v2.4.25-3 ​ |  v2.4.25-3 ​ |  ​v2.4.25-3 ​ | Apache v2  | 
-|  Django CMS  |  v1.8.16 ​ |   ​1:​1.11.5-2 |  [[https://​github.com/​django/​django/​blob/​master/​LICENSE|BSD]] ​ | +|  Django CMS  |  v1.8.16 ​ |   ​1:​1.11.5-2 ​ |  ​1.11.10-1 ​ | [[https://​github.com/​django/​django/​blob/​master/​LICENSE|BSD]] ​ | 
-|  PostgreSQL DDBB  |  9.6+181 ​ |  9.6+181 ​ |  [[https://​www.postgresql.org/​about/​licence/​|PostgreSQL license]] ​ |+|  PostgreSQL DDBB  ​| ​ 9.6+181 ​ ​| ​ 9.6+181 ​ |  9.6+181 ​ |  [[https://​www.postgresql.org/​about/​licence/​|PostgreSQL license]] ​ |
  
  
Line 94: Line 94:
 Other tools used in Board at desk v1.0  Other tools used in Board at desk v1.0 
  
-^  Tool  ^  Version in v0.9.1 release ​ ^   ​Version in v1.0 release ^  License ​ ^ +^  Tool  ^  Version in v0.9.1 release ​ ^   ​Version in v1.0 release ​^  Version in git ^  License ​ ^ 
-|  Python ​ |  2.7.13 ​ |  2.7.13 ​ |  [[https://​docs.python.org/​2/​license.html#​psf-license-agreement-for-python-release|PSF License]] ​ |+|  Python ​ |  2.7.13 ​ |  2.7.13 ​ |  ​2.7.13 / 3.5.3    | [[https://​docs.python.org/​2/​license.html#​psf-license-agreement-for-python-release|PSF License]] ​ |
  
 The overall CIP license policy can be read [[https://​www.cip-project.org/​wp-content/​uploads/​sites/​17/​2017/​04/​cip_agreement_charter_121916.pdf | here ]]. The overall CIP license policy can be read [[https://​www.cip-project.org/​wp-content/​uploads/​sites/​17/​2017/​04/​cip_agreement_charter_121916.pdf | here ]].
 +
 +===== Snapshot Release =====
 +
 +A snapshot release was created in October 2018 to support the Renesas iwg20m board and include the latest bug fixes. See the [[cipdownload#​snapshot-b-d-box|Download page]] page for links.
  
 ===== Prerequisites ===== ===== Prerequisites =====
Line 103: Line 107:
 This tutorial assumes that you have the following installed on the host machine: This tutorial assumes that you have the following installed on the host machine:
 ==== For Linux ==== ==== For Linux ====
-   * git v2.7.or better+   * git v2.11.or better
    * Vagrant v1.9.1 or better    * Vagrant v1.9.1 or better
    * VirtualBox v4.3 or better    * VirtualBox v4.3 or better
Line 115: Line 119:
    * Vagrant v1.9.1 or better    * Vagrant v1.9.1 or better
    * VirtualBox v4.3 or better    * VirtualBox v4.3 or better
 +   * For kernelci web interface you will need a Firefox or Chrome installation as the Windows browsers do not work with the KernelCI webserver.
    * core.autocrlf=input is needed in the git settings for the scripts to run under Debian of the virtual machine    * core.autocrlf=input is needed in the git settings for the scripts to run under Debian of the virtual machine
    * Vagrant needs the guest additions ''​vagrant plugin install vagrant-vbguest''​    * Vagrant needs the guest additions ''​vagrant plugin install vagrant-vbguest''​
Line 127: Line 132:
   - Deploy B@D through [[ciptestingboardatdeskdingledevdeployment#​b-d-deployment-method-2-building-vm-from-scratch-using-vagrant-15|Vagrant]] or by downloading the [[ciptestingboardatdeskdingledevdeployment#​b-d-standalone-virtual-machine-box|B@D standalone VM box]] directly.   - Deploy B@D through [[ciptestingboardatdeskdingledevdeployment#​b-d-deployment-method-2-building-vm-from-scratch-using-vagrant-15|Vagrant]] or by downloading the [[ciptestingboardatdeskdingledevdeployment#​b-d-standalone-virtual-machine-box|B@D standalone VM box]] directly.
   - Once deployed, [[[[ciptestingboardatdesksingledevsetup|configure B@D]].   - Once deployed, [[[[ciptestingboardatdesksingledevsetup|configure B@D]].
-  - Connect ​the board ([[beagleboneblackboard|Beaglebone Black]] in this caseto the host machine, where B@D is deployed.+  - Depending upon the board you are using, connect ​the board [[beagleboneblackboard|Beaglebone Black]] ​or [[renesasboard|IWG20M]] - in the Renesas ​case you must provision the box yourself rather than downloading the pre-provisioned box -  ​to the host machine, where B@D is deployed.
   - [[cipsystembuildhowto|Build the kernel (system)]] to be tested and the required artifacts.   - [[cipsystembuildhowto|Build the kernel (system)]] to be tested and the required artifacts.
   - Check the [[civilinfrastructureplatform/​ciptestingreferencetestcases|reference test cases]] and try them as examples.   - Check the [[civilinfrastructureplatform/​ciptestingreferencetestcases|reference test cases]] and try them as examples.
Line 155: Line 160:
    * Renesas iWave-M (iwg20m)    * Renesas iWave-M (iwg20m)
       * [[http://​www.iwavesystems.com/​rz-g1m-qseven-development-kit.html|Board specs]] description.       * [[http://​www.iwavesystems.com/​rz-g1m-qseven-development-kit.html|Board specs]] description.
-      ​* Information about [[https://​www.elinux.org/​R-Car/​Upstream-Kernel-Release-Highlights|new features]] being incorporated to the Linux Kernel that could be incorporated to the CIP kernel, so they can be tested in B@D. +   * Information about [[https://​www.elinux.org/​R-Car/​Upstream-Kernel-Release-Highlights|new features]] being incorporated to the Linux Kernel that could be incorporated to the CIP kernel, so they can be tested in B@D. 
-      * [[https://​elinux.org/​RZ-G/​Boards/​SK-RZG1M|Set up instructions]] to bring a different board, but the same SoC, up. +   ​* [[https://​elinux.org/​RZ-G/​Boards/​SK-RZG1M|Set up instructions]] to bring a different board, but the same SoC, up. 
    * Cyclone V (not supported yet)    * Cyclone V (not supported yet)
    * Kernel CI https://​kernelci.org/​    * Kernel CI https://​kernelci.org/​
 [[ciptesting|Back to the parent page]] [[ciptesting|Back to the parent page]]
civilinfrastructureplatform/ciptestingboardatdesksingledevfeaturepage.1508320241.txt.gz · Last modified: 2017/10/18 09:50 by rajmarshall