AutoBuilder Cluster Setup: Difference between revisions
From Yocto Project
Jump to navigationJump to search
(Clarify a bit) |
No edit summary |
||
| Line 1: | Line 1: | ||
==As root== | |||
* Install base OS with minimal target | * Install base OS with minimal target | ||
* Add pokybuild user (uid=6000) | * Add pokybuild user (uid=6000, or for older clusters 1006) | ||
* Install the requirements from http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html | * Install the requirements from http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html | ||
* git clone --single-branch http://git.yoctoproject.org/git/poky /root/poky (in /root for historical reasons, should change in the future) | * git clone --single-branch http://git.yoctoproject.org/git/poky /root/poky (in /root for historical reasons, should change in the future) | ||
| Line 14: | Line 10: | ||
* Disable or edit firewall rules to allow all connections to the tap devices. This allows sanity tests to connect to booted images. | * Disable or edit firewall rules to allow all connections to the tap devices. This allows sanity tests to connect to booted images. | ||
* Install nfs-utils or nfs-common, add Domain to /etc/idmapd.conf, fstab entry, mount NAS | * Install nfs-utils or nfs-common, add Domain to /etc/idmapd.conf, fstab entry, mount NAS | ||
==As pokybuild== | |||
* Set up buildset-config, either: | |||
** edit one of the several examples included in repo e.g. cp -r buildset-config.controller buildset-config | |||
** Add ssh key to clone production yocto-autobuilder | |||
*** git clone http://git.yoctoproject.org/git/yocto-autobuilder && cd yocto-autobuilder && git remote add prod git@git.yoctoproject.org:yocto-autobuilder-production && git checkout -b yoctoio prod/yoctoio | |||
* update config/autobuilder.conf and yocto-worker/buildbot.tac | |||
* Start the worker | |||
** touch ~/yocto-autobuilder/.setupdone | ** touch ~/yocto-autobuilder/.setupdone | ||
** . yocto-autobuilder-setup | ** . yocto-autobuilder-setup | ||
** ./yocto-start-autobuilder worker | ** ./yocto-start-autobuilder worker | ||
Revision as of 19:06, 19 July 2016
As root
- Install base OS with minimal target
- Add pokybuild user (uid=6000, or for older clusters 1006)
- Install the requirements from http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html
- git clone --single-branch http://git.yoctoproject.org/git/poky /root/poky (in /root for historical reasons, should change in the future)
- Install http://downloads.yoctoproject.org/releases/yocto/yocto-{latest release}/toolchain/x86_64/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-{relver}.sh to /opt/poky
- Add startup scripts to create tap devs and start vncserver, in /etc/rc.local or as systemd unit files, should perform the following
- cd /root/poky/scripts/; ./runqemu-gen-tapdevs 6000 100 32 /opt/poky/sysroots/x86_64-pokysdk-linux/
- /bin/su - pokybuild -c "/usr/bin/vncserver"
- Disable or edit firewall rules to allow all connections to the tap devices. This allows sanity tests to connect to booted images.
- Install nfs-utils or nfs-common, add Domain to /etc/idmapd.conf, fstab entry, mount NAS
As pokybuild
- Set up buildset-config, either:
- edit one of the several examples included in repo e.g. cp -r buildset-config.controller buildset-config
- Add ssh key to clone production yocto-autobuilder
- git clone http://git.yoctoproject.org/git/yocto-autobuilder && cd yocto-autobuilder && git remote add prod git@git.yoctoproject.org:yocto-autobuilder-production && git checkout -b yoctoio prod/yoctoio
- update config/autobuilder.conf and yocto-worker/buildbot.tac
- Start the worker
- touch ~/yocto-autobuilder/.setupdone
- . yocto-autobuilder-setup
- ./yocto-start-autobuilder worker
