Meego Wiki
Views

Build Infrastructure/Community Builder/Server Layout

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→signer)
Line 48: Line 48:
==== signer ====
==== signer ====
-
We need to understand how to sign packages.
+
Separate VM, needs additional security hardening.
 +
Setup signer documented [http://en.opensuse.org/openSUSE:Build_Service_Signer here].
=== worker VMs ===
=== worker VMs ===

Revision as of 10:50, 11 August 2010

Contents

cbuild host

Has direct access from internet to VMs only

Volume Groups:

  • OBS_backend
  • VM

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.

Volume Groups:

  • OBS_backend

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

Separate VM, needs additional security hardening.

Setup signer documented here.

worker VMs

cworker host

No direct access from internet.

Volume Groups:

  • OBS

worker VMs

All connectivity to crepo VMs


References:

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