[Tracker-discuss] Getting Started

Roché Compaan roche at upfrontsystems.co.za
Sun Oct 29 23:49:02 CET 2006


On Sun, 2006-10-29 at 19:41 +0100, Erik Forsberg wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi!
> 
> I don't know if all of the "initial admins" have indicated their
> willingness yet, but you are at least all subscribed to this list - so
> let's get started working!
> 
> A bunch of infrastructure- and development-related questions popped up
> in my head, so I wrote them down below. Hopefully, there's someone
> here that can answer them :-) (I did notice at least one
> upfrontsystems.co.za person in the list roster..).

Hi Erik, that's me :-)

> 
> Infrastructure
> ==============
> 
> Machine
> - -------
> 
> * What kind of machine are Upfront Systems's going to host for the
>   python-dev tracker? How much CPU, memory and disk is available? 

AMD Athlon 64 with 512 MB RAM and 40GB available for your virtual
server.

> 
> * Will the python-dev tracker be the only software running on this
>   machine? (I assume so, since Brett wrote something about root
>   access)

Your virtual server (http://linux-vserver) will run alongside other
vservers.

> 
> * Which Linux distribution will it run, and who will be responsible
>   to keep the system up to date with security patches etc? We, or
>   Upfront? (I prefer the latter.)

Debian, and we will maintain the system.

> * Does the machine have RAID for its disks? Is there support for
>   monitoring the disks, and who will be responsible for that? 

It has a RAID controller.

> 
> Backup
> - ------
> 
> * What backup facilities are included in the hosting offer? 

Hourly backup of the data to a backup server in the data centre.

> 
> * Are there any alternative ways to make backups, such as usage of
>   rsync, rdiff-backup or similar to some python-community-controlled
>   machine? 

We use both rsync and rdiff-backup so this shouldn't be a problem.

> 
> Access
> - ------
> 
> * Which protocols will be available for access to the machine? I
>   prefer using only SSH (with sftp for file transfers). 

SSH (with sftp) is available.

> 
> On the security side, perhaps we should lock down the root account and
> use sudo to gain root credentials from individual accounts? 

This is standard practice for us.

> 
> Monitoring
> - ----------
> 
> * Is there a nagios (or similar) installation somewhere that we can
>   use to monitor the tracker, its backup etc?

We use monit to monitor services on the box and nagios to monitor the
box remotely.

> 
> Development
> ===========
> 
> * Is there a subversion repository we could use for the development of
>   the tracker? So far we've used a module in the CVS repository for
>   roundup (on Sourceforge), but as I prefer subversion and don't enjoy
>   the "stability" of sourceforge, I'd enjoy a stable subversion
>   repository for this development.

Why not host this on the same box?

> * Where should we keep our tracker bugs? I'm happy to keep the
>   http://efod.se/ptt/ (python-tracker-tracker) online if you like. 


Why not just use another roundup instance on the same box for this?

-- 
Roché Compaan
Upfront Systems                   http://www.upfrontsystems.co.za



More information about the Tracker-discuss mailing list