[blag-whereto] BLAG Trac #15: BLAG Buildsystem Server Spec
BLAG
admin at trac.slated.org
Fri Apr 3 16:52:32 BST 2009
#15: BLAG Buildsystem Server Spec
------------------------------------+---------------------------------------
Reporter: Homer | Owner: lxo
Type: Request For Assistance | Status: new
Priority: major | Milestone: BLAG 90002
Component: BLAG Infrastructure | Version:
Keywords: |
------------------------------------+---------------------------------------
= __Punkit Buildsystem Specs__ =
----
This has been requested by the FSF for review.
----
'''Primary purpose: Software buildsystem using
[http://fedoraproject.org/wiki/Koji/ServerHowTo Koji] and
[http://fedoraproject.org/wiki/Projects/Plague Plague]'''
'''Secondary purpose: Software publishing system using
[https://fedorahosted.org/bodhi/ Bodhi]'''
If this is a virtual host, then there shouldn't be much details required,
other than the disk allocation, otherwise we need to determine other
factors such as the CPU and memory (and possibly RAID). So depending on
the type of system on offer, some of the following may not apply:
----
* CPU: "AMD Phenom II X4 925" 2.8GHz (Part: HDX925WFK4DGI)
* Disk allocation: 5x100GB HDD in software RAID6 (300GB cap)
* RAM: 8GB DDR3 ECC (Registered)
* Network: Wired Gigabit networking with Internet access (Ports 80, 81,
22, and possibly others). A root level server certificate for Apache (for
HTTPS).
----
Or nearest offer :)
Also:
----
* A regular backup service (or facility for us to perform manually). This
is essential, since we cannot afford to lose this data.
* Monthly data transfer allocation: indeterminate at this point, but
likely to be at least 100GB for the first month, and several GB per month
thereafter (estimate).
* CPU utilisation allocation (slices): Punkit will likely hog all
available CPU time. This is the nature of computational systems like
buildsystems. However, this will only occur during periods of active
building. It is as yet undetermined how "busy" Punkit will be initially.
Ultimately, it may end up working 24/7, assuming BLAG builds some
momentum.
----
Note: Factors such as RAID parity and RAM ECC secure the integrity of the
system, at a slight cost to performance, but are overall desirous for a
server.
It should also be noted that Plague offsets the server workload, by
allowing others to build packages on their local machines, with the
results being pushed back to the buildsystem. This reduces CPU overhead at
the cost of some network bandwidth.
Please indicate your approval, disapproval, or alternative suggestions
below.
+1 submit for review.
{{{
-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.4.9 (GNU/Linux)
owGbwMvMwCR49Dpv1H7nvJOMa5STmJNyEj2v6ctyaRsqFJcm5WaWKKTlFykkFhQU
5Zcl5uhxcXW4sTAIMjGwsTKB1DFwcQrA9O/dzrCg31y5lWGKb0ut/Ilu81O7eJRC
k88xLGiaseeqXuzfVypfznNtfWq28vWUrJ0A
=6+qc
-----END PGP MESSAGE-----
}}}
--
Ticket URL: <http://trac.slated.org/ticket/15>
BLAG <http://www.blagblagblag.org/>
BLAG Linux and GNU
More information about the blag-whereto
mailing list