(→OTS server installation) |
(→OTS server installation) |
||
| (25 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | = OTS | + | = OTS 0.8.x installation Ubuntu = |
| + | |||
| + | If using 0.1.x version, see [[Quality/QA-tools/OTS/UserDocumentation/Migration_0.1_0.8| migration from 0.1.x to 0.8.x]] document. | ||
== Used hardware == | == Used hardware == | ||
| Line 16: | Line 18: | ||
Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change. | Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change. | ||
| - | All OTS machines need to be able to access other OTS machines based on their hostname. | + | '''Note''' All OTS machines need to be able to access other OTS machines based on their hostname. |
| + | |||
| + | How to check that DNS names are correct: | ||
| + | |||
| + | 1. Check OTS server's hostname | ||
| + | hostname | ||
| + | 2. Ping the OTS server's hostname from the OTS worker | ||
| + | ping <hostname> | ||
| + | |||
| + | If ping fails, add manually OTS server's hostname to OTS workers '''/etc/hosts''' file | ||
| + | <IP> <hostname> | ||
== Preparation == | == Preparation == | ||
| Line 22: | Line 34: | ||
There are two ways of getting OTS binary packages: from '''the source code''' | There are two ways of getting OTS binary packages: from '''the source code''' | ||
or from the '''MeeGo Tools:Testing repository'''. From the repository you can get | or from the '''MeeGo Tools:Testing repository'''. From the repository you can get | ||
| - | the stable version and from the source code the development version. | + | the stable version and from the source code the development version. If you wish to install OTS from source follow instructions howto [[Quality/QA-tools/OTS/UserDocumentation/Installation#Building_packages_from_source|build packages from the source]]. |
| - | + | === Set up Tools:Testing repository === | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | By setting up the repository it allows you to install OTS and other MeeGo QA tools via apt-get command. Follow the [[Quality/QA-tools/How_to_set_up_repositories|instructions]]. | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
== OTS server installation == | == OTS server installation == | ||
| - | |||
| - | |||
| - | |||
* Install OTS server components | * Install OTS server components | ||
sudo apt-get install python-ots-common python-ots-results python-ots-server | sudo apt-get install python-ots-common python-ots-results python-ots-server | ||
| - | |||
| - | |||
* Configure OTS server settings | * Configure OTS server settings | ||
| - | sudo nano /etc/ | + | sudo nano /etc/ots/server.conf |
Recommended to change following: | Recommended to change following: | ||
| Line 68: | Line 53: | ||
* Install OTS server plug-ins | * Install OTS server plug-ins | ||
| - | [ | + | [[Quality/QA-tools/OTS/Plugins/HTTP_logger|Logger plug-in]] (recommended) |
| - | [ | + | [[Quality/QA-tools/OTS/Plugins/Email|Email plug-in]] (recommended) |
| - | See more plug-ins from [ | + | See more plug-ins from [[Quality/QA-tools/OTS/Plugins|OTS Plug-ins]] |
* If logger plug-in is installed | * If logger plug-in is installed | ||
| Line 83: | Line 68: | ||
sudo chown <user>:<group> /var/log/ots | sudo chown <user>:<group> /var/log/ots | ||
| + | * Now you can start OTS server | ||
ots_server | ots_server | ||
| Line 94: | Line 80: | ||
* Configure OTS worker settings | * Configure OTS worker settings | ||
| - | sudo nano /etc/ots. | + | sudo nano /etc/ots/worker.conf |
Change 'devicegroup', example meego_n900 | Change 'devicegroup', example meego_n900 | ||
Change 'host' to server's address | Change 'host' to server's address | ||
| - | |||
| - | |||
| - | |||
* Start OTS worker | * Start OTS worker | ||
| - | ots_worker | + | sudo ots_worker |
== OTS tools == | == OTS tools == | ||
| Line 115: | Line 98: | ||
* Trigger a test run | * Trigger a test run | ||
ots_trigger -s localhost/xmlrpc -b test_build -i http://url_to_image -p example_sw_product -e test@man.com | ots_trigger -s localhost/xmlrpc -b test_build -i http://url_to_image -p example_sw_product -e test@man.com | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
== How to install N900 automation tools to OTS worker == | == How to install N900 automation tools to OTS worker == | ||
| + | |||
| + | * Remove network-manager, because it breaks the USB connection. See more information from autotest-guide. | ||
* Install dependencies | * Install dependencies | ||
| - | sudo apt-get install meego-ai- | + | sudo apt-get install meego-ai-flasher eat-host-ubuntu |
| - | + | ||
* Get N900 flasher from the Nokia's tablets-dev portal | * Get N900 flasher from the Nokia's tablets-dev portal | ||
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2_i386.deb | http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2_i386.deb | ||
sudo dpkg -i maemo_flasher-3.5_2.5.2.2_i386.deb | sudo dpkg -i maemo_flasher-3.5_2.5.2.2_i386.deb | ||
| - | * | + | * Start HAT driver |
| - | sudo | + | sudo hat_drv & |
| - | * | + | * Test manually that everything is OK, this is executed in the worker |
| - | + | sudo conductor -u <image url> | |
| - | sudo | + | |
| - | + | ||
| - | * | + | * Start OTS worker |
| - | sudo | + | sudo ots_worker |
| - | + | == Building packages from source == | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | If you which to build your own packages and install OTS from them here are the instructions. But it is recommended to install OTS using the repository. | |
| - | + | ||
| + | * Install git core | ||
| + | sudo apt-get install git-core | ||
| + | |||
| + | * Get sources | ||
| + | git clone git://gitorious.org/meego-quality-assurance/ots.git | ||
| + | |||
| + | * Get building tools | ||
| + | sudo apt-get install dpkg-dev debhelper python-setuptools | ||
| + | |||
| + | * Build packages | ||
| + | cd ots | ||
| + | dpkg-buildpackage -rfakeroot | ||
| + | |||
| + | * Install dependencies | ||
| + | sudo apt-get install python-django python-amqplib python-configobj rabbitmq-server test-definition | ||
| + | |||
| + | * Now you can install the packages | ||
| + | sudo dpkg -i <package> | ||
Contents |
If using 0.1.x version, see migration from 0.1.x to 0.8.x document.
Using static IP addresses on all OTS machines is strongly recommended. It is possible to setup the system also with dynamic IP addresses but it might cause problems every now and then because IP's and hostnames change.
Note All OTS machines need to be able to access other OTS machines based on their hostname.
How to check that DNS names are correct:
1. Check OTS server's hostname
hostname
2. Ping the OTS server's hostname from the OTS worker
ping <hostname>
If ping fails, add manually OTS server's hostname to OTS workers /etc/hosts file
<IP> <hostname>
There are two ways of getting OTS binary packages: from the source code or from the MeeGo Tools:Testing repository. From the repository you can get the stable version and from the source code the development version. If you wish to install OTS from source follow instructions howto build packages from the source.
By setting up the repository it allows you to install OTS and other MeeGo QA tools via apt-get command. Follow the instructions.
sudo apt-get install python-ots-common python-ots-results python-ots-server
sudo nano /etc/ots/server.conf
Recommended to change following:
'example_sw_product', example to 'meego_product' 'devicegroup', example to 'meego_n900'
Logger plug-in (recommended) Email plug-in (recommended)
See more plug-ins from OTS Plug-ins
Change permissions to logging directory sudo chown www-data:www-data /var/log/ots
Now the OTS server can be used via apache (django_xmlrpc).
Change user permissions to logging directory sudo chown <user>:<group> /var/log/ots
ots_server
sudo apt-get install python-amqplib testrunner-lite
sudo apt-get install python-ots-common python-ots-worker
sudo nano /etc/ots/worker.conf
Change 'devicegroup', example meego_n900
Change 'host' to server's address
sudo ots_worker
Tools are used for triggering test runs from the command line.
sudo apt-get install python-ots-tools
ots_trigger -s localhost/xmlrpc -b test_build -i http://url_to_image -p example_sw_product -e test@man.com
sudo apt-get install meego-ai-flasher eat-host-ubuntu
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php?f=maemo_flasher-3.5_2.5.2.2_i386.deb sudo dpkg -i maemo_flasher-3.5_2.5.2.2_i386.deb
sudo hat_drv &
sudo conductor -u <image url>
sudo ots_worker
If you which to build your own packages and install OTS from them here are the instructions. But it is recommended to install OTS using the repository.
sudo apt-get install git-core
git clone git://gitorious.org/meego-quality-assurance/ots.git
sudo apt-get install dpkg-dev debhelper python-setuptools
cd ots dpkg-buildpackage -rfakeroot
sudo apt-get install python-django python-amqplib python-configobj rabbitmq-server test-definition
sudo dpkg -i <package>