Archive:Build Service Appliance

This article about the Open Build Service is obsolete! You can find up to date information on https://openbuildservice.org/download/

The preferred method of deploying an Open Build Service instance are the OBS software appliances. In these appliances the OBS components are combined with the openSUSE Distribution to run optimally on a server or in a virtual machine.

Preparation

It's best to prepare the hosts you deploy the OBS appliances to with a LVM volume group of the name "OBS". This volume group should be as big as possible because it get's used by the OBS server components for data storage and the OBS workers for root/swap/cache file systems.

pvcreate /dev/sdX1
vgcreate "OBS" /dev/sdX1

Server Installation

The OBS server images contain a recent openSUSE distribution with a pre-installed and pre-configured OBS backend, API, web frontend and worker.

The system adapts to the hardware on first boot and defaults to automatic IP and DNS configuration via DHCP. The image scans for a LVM volume group called "OBS" and will use that to set up logical volumes for the workers root/swap/cache file systems. Additionally if this volume group contains a logical volume named "server" it will be used as the data partition for the server.

Installation Images

There are installation images. When you boot, they run a basic installer that lets you choose the block device to deploy the image to.

http://download.opensuse.org/repositories/OBS:/Server:/2.6/images/iso/obs-server.x86_64.install.iso

You put this image on a USB stick and boot from it.

xzcat obs-server-install.x86_64.raw.xz > /dev/sdX

Warning: /dev/sdX is the main device of your USB stick. Do NOT put it into a partition like /dev/sda1

Warning: If you use the wrong device, you will destroy all data on it!

VirtualBox/VMWARE

For VirtualBox and VMware there are a configuration file (.vmx) and a disk image (.vmdk). You can load the configuration into VMware workstation/player or VirtualBox.

http://download.opensuse.org/repositories/OBS:/Server:/2.6/images/obs-server.x86_64.vmx

http://download.opensuse.org/repositories/OBS:/Server:/2.6/images/obs-server.x86_64.vmdk

KVM/QEMU

For QEMU/KVM there is a disk image in the qcow format which you can start.

http://download.opensuse.org/repositories/OBS:/Server:/2.6/images/obs-server.x86_64.qcow2

Raw Disk Image

If you want to deploy directly to a block device there is an file system image (.raw)

http://download.opensuse.org/repositories/OBS:/Server:/2.6/images/obs-server.x86_64.raw.xz

xzcat obs-server.x86_64.raw.xz > /dev/sdX

Warning: /dev/sdX is the main device of your block device. Do NOT put it into a partition like /dev/sda1

Warning: If you use the wrong device, you will destroy all data on it!

Worker Installation

There is also an image which includes a recent openSUSE distribtion and only the OBS worker component. The system on this image adapts to the hardware on first boot, defaults to automatic IP and DNS configuration via DHCP and OBS server discovery via SLP. This image is also looking for a LVM volume group with the name "OBS" during boot to create logical volumes for the workers root/swap/cache filesystems.

Raw Disk Image

You can use this file system image to deploy it directly to a block device or boot it with KVM/QEMU.

http://download.opensuse.org/repositories/OBS:/Server:/2.6/images/obs-worker.x86_64.raw.xz

Updating

All images come pre-configured with the right set of repositories and can updated via the system tools YaST or zypper at any time. Another way is to replace the entire image. If you update the image keep in mind that you need to have have your data directory (/srv/obs) on a separate storage (LVM volume, partition etc.) otherwise it will get deleted.