Meego Wiki
Views

Build Infrastructure/Community Builder/Server Layout

From MeeGo wiki
< Build Infrastructure | Community Builder
Revision as of 12:00, 26 April 2011 by Amigadave (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Based on : http://en.opensuse.org/openSUSE:Build_Service_Deployment

Contents

cbuild host

Has direct access from internet to VMs only

Volume Groups:

  • OBS_backend
  • VM

download VM : cdownload

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

frontend VM : cfe

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

This has mysql which http://en.opensuse.org/openSUSE:Build_Service_Deployment says should be on 'storage'. Not sure...

Assorted VMs

Systems such as:

  • BOSS for autobuilder logic
  • Web tools
  • Assorted particpants

No significant resources atm

crepo host

No direct access from internet.

Volume Groups:

  • OBS_Storage
  • VM

backend VM : cbe

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

This VM hosts the backend schedulers, dispatchers and servers.

storage VM : cstore

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

Separate VM, needs additional security hardening.

Setup signer documented here.

worker VMs

cworker host

No direct access from internet.

Volume Groups:

  • OBS

worker VMs

Only need connectivity to crepo VMs


References:

Retrieved from "http://wiki.meego.com/Build_Infrastructure/Community_Builder/Server_Layout"
Personal tools