AutoBuilder Cluster Setup - Revision history

Yoann Congal: /* As root */ Fix QuickStart doc URL

2024-03-18T21:29:01Z

As root: Fix QuickStart doc URL

← Older revision		Revision as of 21:29, 18 March 2024
Line 3:		Line 3:
	==As root==		==As root==
	* Install base OS with minimal target		* Install base OS with minimal target
	* Install the requirements from ~~http~~://~~www~~.yoctoproject.org/~~docs/current/yocto~~-~~project-qs~~/~~yocto~~-~~project~~-~~qs.html~~		* Install the requirements from https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html#build-host-packages
	** (Note: if you plan to build the poky-eclipse-neon plugin, openjdk-headless 1.8 is required.)		** (Note: if you plan to build the poky-eclipse-neon plugin, openjdk-headless 1.8 is required.)
	* If you plan to run the sanity tests (which is typical for an AB), the following additional packages need to be installed:		* If you plan to run the sanity tests (which is typical for an AB), the following additional packages need to be installed:
Line 32:		Line 32:
	** * hard memlock 16384		** * hard memlock 16384
	** * soft memlock 16384		** * soft memlock 16384


	==As pokybuild==		==As pokybuild==

MichaelHalstead at 17:48, 11 October 2021

2021-10-11T17:48:27Z

← Older revision		Revision as of 17:48, 11 October 2021
Line 25:		Line 25:
	* Install nfs-utils or nfs-common, add Domain to /etc/idmapd.conf, fstab entry, mount NAS under /srv/autobuilder.		* Install nfs-utils or nfs-common, add Domain to /etc/idmapd.conf, fstab entry, mount NAS under /srv/autobuilder.
	* We use more watches then the defaults generally allow so, echo "fs.inotify.max_user_watches=65536" >> /etc/sysctl.conf		* We use more watches then the defaults generally allow so, echo "fs.inotify.max_user_watches=65536" >> /etc/sysctl.conf
			* We open more files than most distros allow so adjust ulimits. Add to /etc/security/limits.conf
			** * hard nproc 515294
			** * soft nproc 514543
			** * soft nofile 131072
			** * hard nofile 131072
			** * hard memlock 16384
			** * soft memlock 16384


	==As pokybuild==		==As pokybuild==

MichaelHalstead at 15:31, 3 August 2021

2021-08-03T15:31:58Z

← Older revision		Revision as of 15:31, 3 August 2021
Line 7:		Line 7:
	* If you plan to run the sanity tests (which is typical for an AB), the following additional packages need to be installed:		* If you plan to run the sanity tests (which is typical for an AB), the following additional packages need to be installed:
	** GitPython for Python2 and Python3		** GitPython for Python2 and Python3
			** zstd & lz4 (or liblz4-tool)
	** xsltproc		** xsltproc
	** gnupg		** gnupg

MichaelHalstead: Adding newly needed global git config.

2017-09-20T22:08:05Z

Adding newly needed global git config.

← Older revision		Revision as of 22:08, 20 September 2017
Line 33:		Line 33:
	** edit one of the several examples included in repo e.g. cp -r buildset-config.controller buildset-config		** edit one of the several examples included in repo e.g. cp -r buildset-config.controller buildset-config

			* configure git
			** git config --global gc.auto 0
			** git config --global user.name pokybuild
			** git config --global user.email pokybuild@$(hostname -f)
	* update config/autobuilder.conf and yocto-worker/buildbot.tac		* update config/autobuilder.conf and yocto-worker/buildbot.tac
	* Start the worker		* Start the worker

MichaelHalstead: add vnc port info.

2017-08-04T22:11:41Z

add vnc port info.

← Older revision		Revision as of 22:11, 4 August 2017
Line 20:		Line 20:
	** /bin/su - pokybuild -c "/usr/bin/vncserver"		** /bin/su - pokybuild -c "/usr/bin/vncserver"
	**Note that the location of the buildtools might actually be different than the example shown here, depending on the default path, etc. If you run into a tunctl error when generating the tapdevs, it's likely a path problem.		**Note that the location of the buildtools might actually be different than the example shown here, depending on the default path, etc. If you run into a tunctl error when generating the tapdevs, it's likely a path problem.
	** You will need to run vncserver once as the pokybuild user, and set the password. The password of "builder" is generally used.		** You will need to run vncserver once as the pokybuild user, and set the password. The password of "builder" is generally used. Sanity tests require vncserver to listen on port 5901, the default.
	* 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 under /srv/autobuilder.		* Install nfs-utils or nfs-common, add Domain to /etc/idmapd.conf, fstab entry, mount NAS under /srv/autobuilder.

MichaelHalstead at 20:30, 20 July 2017

2017-07-20T20:30:04Z

← Older revision		Revision as of 20:30, 20 July 2017
Line 15:		Line 15:
	* If a "kvm" group does not exist, add it to /etc/group and ensure /dev/kvm gid is set to "kvm" and is mode 660. Add pokybuild user to the "kvm" group.		* If a "kvm" group does not exist, add it to /etc/group and ensure /dev/kvm gid is set to "kvm" and is mode 660. Add pokybuild user to the "kvm" group.
	* git clone --single-branch https://git.yoctoproject.org/git/poky /root/poky (in /root for historical reasons, should change in the future)		* git clone --single-branch https://git.yoctoproject.org/git/poky /root/poky (in /root for historical reasons, should change in the future)
	* Install https://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.		* ''If adding tap devs for sanity testing.'' Install https://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, /etc/init.d/boot.local, or as systemd unit files, which should perform the following:		* Add startup scripts to create tap devs and start vncserver, in /etc/rc.local, /etc/init.d/boot.local, or as systemd unit files, which should perform the following:
	** cd /root/poky/scripts/; ./runqemu-gen-tapdevs 6000 100 32 /opt/poky/sysroots/x86_64-pokysdk-linux/		** cd /root/poky/scripts/; ./runqemu-gen-tapdevs 6000 100 32 /opt/poky/sysroots/x86_64-pokysdk-linux/

Tracy Graydon: /* As root */

2017-02-16T22:14:13Z

As root

← Older revision		Revision as of 22:14, 16 February 2017
Line 17:		Line 17:
	* Install https://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.		* Install https://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, /etc/init.d/boot.local, or as systemd unit files, which should perform the following:		* Add startup scripts to create tap devs and start vncserver, in /etc/rc.local, /etc/init.d/boot.local, or as systemd unit files, which should perform the following:
	** cd /root/poky/scripts/; ./runqemu-gen-tapdevs 6000 100 32 /opt/poky/sysroots/x86_64-pokysdk-linux/ Note that the location of the buildtools might actually be different than the example shown here, depending on the default path, etc. If you run into a tunctl error when generating the tapdevs, it's likely a path problem.		** cd /root/poky/scripts/; ./runqemu-gen-tapdevs 6000 100 32 /opt/poky/sysroots/x86_64-pokysdk-linux/
	** /bin/su - pokybuild -c "/usr/bin/vncserver"		** /bin/su - pokybuild -c "/usr/bin/vncserver"
			**Note that the location of the buildtools might actually be different than the example shown here, depending on the default path, etc. If you run into a tunctl error when generating the tapdevs, it's likely a path problem.
	** You will need to run vncserver once as the pokybuild user, and set the password. The password of "builder" is generally used.		** You will need to run vncserver once as the pokybuild user, and set the password. The password of "builder" is generally used.
	* 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.

Tracy Graydon: /* As root */

2017-02-16T22:06:17Z

As root

← Older revision		Revision as of 22:06, 16 February 2017
Line 17:		Line 17:
	* Install https://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.		* Install https://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, /etc/init.d/boot.local, or as systemd unit files, which should perform the following:		* Add startup scripts to create tap devs and start vncserver, in /etc/rc.local, /etc/init.d/boot.local, or as systemd unit files, which should perform the following:
	** cd /root/poky/scripts/; ./runqemu-gen-tapdevs 6000 100 32 /opt/poky/sysroots/x86_64-pokysdk-linux/ Note that the location of the buildtools might actually be different than the example shown here. If you run into a tunctl error when generating the tapdevs, it's likely a path problem.		** cd /root/poky/scripts/; ./runqemu-gen-tapdevs 6000 100 32 /opt/poky/sysroots/x86_64-pokysdk-linux/ Note that the location of the buildtools might actually be different than the example shown here, depending on the default path, etc. If you run into a tunctl error when generating the tapdevs, it's likely a path problem.
	** /bin/su - pokybuild -c "/usr/bin/vncserver"		** /bin/su - pokybuild -c "/usr/bin/vncserver"
	** You will need to run vncserver once as the pokybuild user, and set the password. The password of "builder" is generally used.		** You will need to run vncserver once as the pokybuild user, and set the password. The password of "builder" is generally used.

Tracy Graydon: /* As root */

2017-02-16T21:47:22Z

As root

← Older revision		Revision as of 21:47, 16 February 2017
Line 17:		Line 17:
	* Install https://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.		* Install https://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, /etc/init.d/boot.local, or as systemd unit files, which should perform the following:		* Add startup scripts to create tap devs and start vncserver, in /etc/rc.local, /etc/init.d/boot.local, or as systemd unit files, which should perform the following:
	** cd /root/poky/scripts/; ./runqemu-gen-tapdevs 6000 100 32 /opt/poky/sysroots/x86_64-pokysdk-linux/		** cd /root/poky/scripts/; ./runqemu-gen-tapdevs 6000 100 32 /opt/poky/sysroots/x86_64-pokysdk-linux/ Note that the location of the buildtools might actually be different than the example shown here. If you run into a tunctl error when generating the tapdevs, it's likely a path problem.
	** /bin/su - pokybuild -c "/usr/bin/vncserver"		** /bin/su - pokybuild -c "/usr/bin/vncserver"
			** You will need to run vncserver once as the pokybuild user, and set the password. The password of "builder" is generally used.
	* 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 under /srv/autobuilder.		* Install nfs-utils or nfs-common, add Domain to /etc/idmapd.conf, fstab entry, mount NAS under /srv/autobuilder.
	* We use more watches then the defaults generally allow so, echo "fs.inotify.max_user_watches=65536" >> /etc/sysctl.conf		* We use more watches then the defaults generally allow so, echo "fs.inotify.max_user_watches=65536" >> /etc/sysctl.conf


	==As pokybuild==		==As pokybuild==

MichaelHalstead: inotify document

2016-12-15T21:57:06Z

inotify document

← Older revision		Revision as of 21:57, 15 December 2016
Line 21:		Line 21:
	* 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 under /srv/autobuilder.		* Install nfs-utils or nfs-common, add Domain to /etc/idmapd.conf, fstab entry, mount NAS under /srv/autobuilder.
			* We use more watches then the defaults generally allow so, echo "fs.inotify.max_user_watches=65536" >> /etc/sysctl.conf


	==As pokybuild==		==As pokybuild==