SoyuzInfrastructureOverview

Differences between revisions 6 and 7
⇤ ← Revision 6 as of 2008-09-01 19:01:04 →
Size: 1039
Editor: bd231c99
Comment:
← Revision 7 as of 2009-09-04 19:08:22 → ⇥
Size: 1353
Editor: bd23baa8
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
The entire system can be divided in smaller ''sub-domains'': General Soyuz-related content classes and tests can be found at ''lp.soyuz''
Line 15: Line 15:
 * Upload processing,
 * Source building and
 * Archive publishing.		 However the the entire system depends on other components:

|| Component || Module ||
|| Upload server || canonical.poppy ||
|| Source Building || canonical.buildd ||
|| Upload processing || lp.archiveuploader ||
|| Build dispatching || lp.builddmaster ||
|| Archive publishing || lp.archivepublisher ||

=== Upload server ===


=== Source building ===
Line 27: Line 38:

=== Source building ===		 === Build dispatching ===

Contents

  1. Introduction
  2. Overview
  3. Sub-Domains
    1. Upload server
    2. Source building
    3. Uploading processing
    4. Build dispatching
    5. Archive publishing

Introduction

This document is a brief overview of the Soyuz infrastructure.

Overview

alt Soyuz Backend

Sub-Domains

General Soyuz-related content classes and tests can be found at lp.soyuz

However the the entire system depends on other components:

Component

Module

Upload server

canonical.poppy

Source Building

canonical.buildd

Upload processing

lp.archiveuploader

|| Build dispatching || lp.builddmaster ||

Archive publishing

lp.archivepublisher

Upload server

Source building

Uploading processing

The upload processor job runs every 5 minutes processing all ftp uploads.

Among other tasks, this job check the upload content/metadata consistency (usual dak-inherited checks) and archive version coherency.

The result is a upload queue records, containing a source or binary package release, that will be announced via email according it's status: REJECTED | NEW | UNAPPROVED | ACCEPTED.

Build dispatching

Published sources are dispatched to launchpad-buildds instantly and collected as binary uploads (.changes + N .deb).

Archive publishing

Virtually any Source or Binary release can be published in a given Archive.

CelsoProvidelo/SoyuzInfrastructureOverview (last edited 2009-09-04 19:29:21 by bd23baa8)