Build Infrastructure/Community Builder/Server Layout

Contents 1 cbuild host 1.1 cdownloads VM 1.2 api and webui VM 1.3 Assorted VMs 2 crepo host 2.1 cbe VM 2.1.1 src-server 2.1.2 repo-server 2.1.3 signer 2.2 worker VMs 3 cworker host 3.1 worker VMs

cbuild host

cdownloads VM

Primary focus is to publish projects (ie locally built rpms) Running lighttpd - this is where public downloads will be served from.

• 2-4 CPU
• Storage: Enough for published packages... no MeeGo or Fremantle binaries

api and webui VM

Minimal local disk, handle ldap, monitor backend 4 CPUs each to start

Assorted VMs

Systems such as:

• BOSS for autobuilder logic
• Web tools
• Assorted particpants

No significant resources atm

crepo host

No direct access from internet.

cbe VM

Eventually ~4-6 CPUs (1/scheduler +1-2)

This VM hosts the backend schedulers, dispatchers and servers.

src-server

Storage here for user project source.

• Local project source

repo-server

Storage for target *and* published binaries although the binaries will be published via rsync to cdownloads before being made public.

• Locally built binaries
• MeeGo binaries for building
• Fremantle binaries for building
• Other distro binaries

signer

We need to understand how to sign packages.

worker VMs

cworker host

No direct access from internet.

worker VMs

All connectivity to crepo VMs

---

References:

• http://en.opensuse.org/openSUSE:Build_Service_Backend_Key_Components