From forsberg at efod.se  Sun Oct 29 19:41:25 2006
From: forsberg at efod.se (Erik Forsberg)
Date: Sun, 29 Oct 2006 19:41:25 +0100
Subject: [Tracker-discuss] Getting Started
Message-ID: <87odrv6k2y.fsf@uterus.efod.se>

-----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..).

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? 

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

* 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.)

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

Backup
- ------

* What backup facilities are included in the hosting offer? 

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

Access
- ------

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

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

Monitoring
- ----------

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

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.

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

Cheers,
\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFFRPXUrJurFAusidkRAhrXAKCHt8LBaI3rbs7G+cov+7DOnEkcBwCfXPDD
cnawo0QapBpaHMVsNiXz4l4=
=naYd
-----END PGP SIGNATURE-----

From brett at python.org  Sun Oct 29 20:16:32 2006
From: brett at python.org (Brett Cannon)
Date: Sun, 29 Oct 2006 11:16:32 -0800
Subject: [Tracker-discuss] Getting Started
In-Reply-To: <87odrv6k2y.fsf@uterus.efod.se>
References: <87odrv6k2y.fsf@uterus.efod.se>
Message-ID: <bbaeab100610291116q10f42993mb7cc5ab7b1d2e740@mail.gmail.com>

On 10/29/06, Erik Forsberg <forsberg at efod.se> 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!


Yes, everyone has accepted.  I will probably be sending out the announcement
email today.

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..).
>
> 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?
>
> * Will the python-dev tracker be the only software running on this
>   machine? (I assume so, since Brett wrote something about root
>   access)
>
> * 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.)
>
> * Does the machine have RAID for its disks? Is there support for
>   monitoring the disks, and who will be responsible for that?
>
> Backup
> - ------
>
> * What backup facilities are included in the hosting offer?
>
> * Are there any alternative ways to make backups, such as usage of
>   rsync, rdiff-backup or similar to some python-community-controlled
>   machine?


We can work this out with the pydotorg folks.  But yes, we can get the
access needed through SSH 2 keys.

Access
> - ------
>
> * Which protocols will be available for access to the machine? I
>   prefer using only SSH (with sftp for file transfers).
>
> On the security side, perhaps we should lock down the root account and
> use sudo to gain root credentials from individual accounts?


pydotorg only allows SSSH 2 key access for accounts and actually removes
password access.  It's worked out rather well I think.  Don't know how they
handle root, though.

Monitoring
> - ----------
>
> * Is there a nagios (or similar) installation somewhere that we can
>   use to monitor the tracker, its backup etc?
>
> 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.


We can make a project in the Python svn repository for this without issue.

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


I guess you don't want to keep this on the server itself since keeping the
tracker you are reporting bugs for on the tracker that has the bugs is kind
of bad.  =)

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061029/eee43f48/attachment.htm 

From pfdubois at gmail.com  Sun Oct 29 20:18:21 2006
From: pfdubois at gmail.com (Paul Dubois)
Date: Sun, 29 Oct 2006 11:18:21 -0800
Subject: [Tracker-discuss] Getting Started
In-Reply-To: <87odrv6k2y.fsf@uterus.efod.se>
References: <87odrv6k2y.fsf@uterus.efod.se>
Message-ID: <f74a6c2f0610291118h7ed78ae1v9926f48dc9c8572f@mail.gmail.com>

I have a somewhat more basic question. Who did the prototype, where are the
results of it, and what if anything needs to be done differently. What
backend, etc.

I am not experienced with subversion but I hate cvs; in particular I hate
the poor cvs branching model / behavior. For my own roundup trackers I use a
two-branch scheme:

main = distribution as received from Richard

Branch this to "ours"; when new distribution received, check it in on main
and integrate changes into "ours".

I use Perforce; Perforce will grant a free license to us as an open-source
project, I believe. However, I'm ok with Subversion as long as the branching
stuff works. This area, however, is one place where open source stuff has
not been as good as the commercial.

We have used a 'fake' user as the owner of roundup with a sudo from
individual maintainer accounts. This works fine. One has no need at all to
be root the way I do it. You build your own dedicated Python and install
into it, so that you aren't related to the root's Python on the machine.




On 10/29/06, Erik Forsberg <forsberg at efod.se> 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..).
>
> 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?
>
> * Will the python-dev tracker be the only software running on this
>   machine? (I assume so, since Brett wrote something about root
>   access)
>
> * 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.)
>
> * Does the machine have RAID for its disks? Is there support for
>   monitoring the disks, and who will be responsible for that?
>
> Backup
> - ------
>
> * What backup facilities are included in the hosting offer?
>
> * Are there any alternative ways to make backups, such as usage of
>   rsync, rdiff-backup or similar to some python-community-controlled
>   machine?
>
> Access
> - ------
>
> * Which protocols will be available for access to the machine? I
>   prefer using only SSH (with sftp for file transfers).
>
> On the security side, perhaps we should lock down the root account and
> use sudo to gain root credentials from individual accounts?
>
> Monitoring
> - ----------
>
> * Is there a nagios (or similar) installation somewhere that we can
>   use to monitor the tracker, its backup etc?
>
> 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.
>
> * Where should we keep our tracker bugs? I'm happy to keep the
>   http://efod.se/ptt/ (python-tracker-tracker) online if you like.
>
> Cheers,
> \EF
> - --
> Erik Forsberg                 http://efod.se
> GPG/PGP Key: 1024D/0BAC89D9
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>
>
> iD8DBQFFRPXUrJurFAusidkRAhrXAKCHt8LBaI3rbs7G+cov+7DOnEkcBwCfXPDD
> cnawo0QapBpaHMVsNiXz4l4=
> =naYd
> -----END PGP SIGNATURE-----
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061029/c46c2482/attachment.html 

From pfdubois at gmail.com  Sun Oct 29 20:21:40 2006
From: pfdubois at gmail.com (Paul Dubois)
Date: Sun, 29 Oct 2006 11:21:40 -0800
Subject: [Tracker-discuss] Getting Started
In-Reply-To: <bbaeab100610291116q10f42993mb7cc5ab7b1d2e740@mail.gmail.com>
References: <87odrv6k2y.fsf@uterus.efod.se>
	<bbaeab100610291116q10f42993mb7cc5ab7b1d2e740@mail.gmail.com>
Message-ID: <f74a6c2f0610291121i6aae6740o7ff8bd6a8a75a8b4@mail.gmail.com>

I don't really see a problem with the tracker bugs; if you want a separate
tracker, the same server can handle it. No reason this couldn't just be a
default tracker, not fancy at all.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061029/9d316faa/attachment.htm 

From seefeld at sympatico.ca  Sun Oct 29 21:26:38 2006
From: seefeld at sympatico.ca (Stefan Seefeld)
Date: Sun, 29 Oct 2006 15:26:38 -0500
Subject: [Tracker-discuss] Getting Started
In-Reply-To: <87odrv6k2y.fsf@uterus.efod.se>
References: <87odrv6k2y.fsf@uterus.efod.se>
Message-ID: <45450E7E.8020504@sympatico.ca>

Erik Forsberg wrote:

> 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.

I agree.

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

Fine, though I think it might be more appropriate to start by moving
this meta-tracker over to the new host and then start from there.

(Or set up a new one; it's just a vanilla demo tracker anyway, right ?)

Regards,
		Stefan


-- 

      ...ich hab' noch einen Koffer in Berlin...

From forsberg at efod.se  Sun Oct 29 20:35:59 2006
From: forsberg at efod.se (Erik Forsberg)
Date: Sun, 29 Oct 2006 20:35:59 +0100
Subject: [Tracker-discuss] Getting Started
In-Reply-To: <f74a6c2f0610291118h7ed78ae1v9926f48dc9c8572f@mail.gmail.com>
	(Paul Dubois's message of "Sun, 29 Oct 2006 11:18:21 -0800")
References: <87odrv6k2y.fsf@uterus.efod.se>
	<f74a6c2f0610291118h7ed78ae1v9926f48dc9c8572f@mail.gmail.com>
Message-ID: <87k62i7w4g.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Paul Dubois" <pfdubois at gmail.com> writes:

> I have a somewhat more basic question. Who did the prototype, 

Some people on the roundup-devel list, with me and Stefan Seefeldt as
the main contributors, created the prototype. I'm hosting it on
http://efod.se/python-tracker/. 

> where are the
> results of it, and what if anything needs to be done differently. What
> backend, etc.

The results are in two forms:

1) The tracker is available as a CVS module in the roundup CVS, which
   is located at
   sourceforge.
   http://roundup.cvs.sourceforge.net/roundup/python-tracker/ for a
   ViewCVS view. Anonymous CVS checkout instructions at
   http://sourceforge.net/cvs/?group_id=31577 

2) We have a bug tracker for feature requests etc. available at
   http://efod.se/ptt/ 

It's also possible that the python infrastructure team has some notes
from their evaluation of the trackers? 

Regarding the backend question, I think the people on roundup-devel
agreed that PostgreSQL is probably the way to go. 

> I am not experienced with subversion but I hate cvs; in particular I hate
> the poor cvs branching model / behavior. For my own roundup trackers
> I use a two-branch scheme:
>
> main = distribution as received from Richard
>
> Branch this to "ours"; when new distribution received, check it in on main
> and integrate changes into "ours".

Sounds like what CVS calls Vendor Branches. That is indeed a good way
to handle source code in this kind of project. 

> We have used a 'fake' user as the owner of roundup with a sudo from
> individual maintainer accounts. This works fine. One has no need at all to
> be root the way I do it. You build your own dedicated Python and install
> into it, so that you aren't related to the root's Python on the
> machine.

Perhaps not. It's still convenient to have root access for mail
configuration etc. But it's fully possible that we can cope without
root access. It will depend a bit on how we setup the instance -
fastcgi or mod_python, etc? That will have to be discussed.

Cheers,
\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFFRQKerJurFAusidkRAr/aAJ4lAo+TW05S+Lx/hk9Tcz/9NsXTUwCZAQkv
Y5E6mFhYP1GeEzPwN8m1x28=
=iVzX
-----END PGP SIGNATURE-----

From forsberg at efod.se  Sun Oct 29 20:37:22 2006
From: forsberg at efod.se (Erik Forsberg)
Date: Sun, 29 Oct 2006 20:37:22 +0100
Subject: [Tracker-discuss] Getting Started
In-Reply-To: <45450E7E.8020504@sympatico.ca> (Stefan Seefeld's message of
	"Sun, 29 Oct 2006 15:26:38 -0500")
References: <87odrv6k2y.fsf@uterus.efod.se> <45450E7E.8020504@sympatico.ca>
Message-ID: <87fyd67w25.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan Seefeld <seefeld at sympatico.ca> writes:

>> * Where should we keep our tracker bugs? I'm happy to keep the
>>   http://efod.se/ptt/ (python-tracker-tracker) online if you like. 
>
> Fine, though I think it might be more appropriate to start by moving
> this meta-tracker over to the new host and then start from there.

Brett has a point in the fact that it's hard to report bugs on a
tracker that is down :-). 
>
> (Or set up a new one; it's just a vanilla demo tracker anyway, right ?)

Yes. 

Cheers,
\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFFRQLxrJurFAusidkRAilIAJ9m6vOUCXTlaznVzjfkAVQjK7OcfACaA0lc
sSZLhmLptGpbElk2pj3aTk4=
=0xL+
-----END PGP SIGNATURE-----

From brett at python.org  Sun Oct 29 20:55:19 2006
From: brett at python.org (Brett Cannon)
Date: Sun, 29 Oct 2006 11:55:19 -0800
Subject: [Tracker-discuss] Getting Started
In-Reply-To: <f74a6c2f0610291118h7ed78ae1v9926f48dc9c8572f@mail.gmail.com>
References: <87odrv6k2y.fsf@uterus.efod.se>
	<f74a6c2f0610291118h7ed78ae1v9926f48dc9c8572f@mail.gmail.com>
Message-ID: <bbaeab100610291155s5dfed6b6p618afc4f098c9714@mail.gmail.com>

On 10/29/06, Paul Dubois <pfdubois at gmail.com> wrote:
>
> I have a somewhat more basic question. Who did the prototype, where are
> the results of it, and what if anything needs to be done differently. What
> backend, etc.
>
> I am not experienced with subversion but I hate cvs; in particular I hate
> the poor cvs branching model / behavior. For my own roundup trackers I use a
> two-branch scheme:
>
> main = distribution as received from Richard
>
> Branch this to "ours"; when new distribution received, check it in on main
> and integrate changes into "ours".
>
> I use Perforce; Perforce will grant a free license to us as an open-source
> project, I believe. However, I'm ok with Subversion as long as the branching
> stuff works. This area, however, is one place where open source stuff has
> not been as good as the commercial.


Branching is very simple in Subversion.  If you want to see how to do it see
the python-dev FAQ entries on branching (
http://www.python.org/dev/faq/#how-do-i-create-a-branch).

I think keeping it in Python's svn repository has the nice effect of not
causing a proliferation of support infrastructure for Python overall from
ballooning.  We already keep an eye on svn, but if we tacked on Perforce
(even if it was just for use by you guys) that is just one more process and
software install to keep track of.

I understand your pain with CVS, Paul, but svn does a good job of dealing
with CVS's major shortcomings.

-Brett


We have used a 'fake' user as the owner of roundup with a sudo from
> individual maintainer accounts. This works fine. One has no need at all to
> be root the way I do it. You build your own dedicated Python and install
> into it, so that you aren't related to the root's Python on the machine.
>
>
>
>
> On 10/29/06, Erik Forsberg <forsberg at efod.se> 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..).
> >
> > 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?
> >
> > * Will the python-dev tracker be the only software running on this
> >   machine? (I assume so, since Brett wrote something about root
> >   access)
> >
> > * 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.)
> >
> > * Does the machine have RAID for its disks? Is there support for
> >   monitoring the disks, and who will be responsible for that?
> >
> > Backup
> > - ------
> >
> > * What backup facilities are included in the hosting offer?
> >
> > * Are there any alternative ways to make backups, such as usage of
> >   rsync, rdiff-backup or similar to some python-community-controlled
> >   machine?
> >
> > Access
> > - ------
> >
> > * Which protocols will be available for access to the machine? I
> >   prefer using only SSH (with sftp for file transfers).
> >
> > On the security side, perhaps we should lock down the root account and
> > use sudo to gain root credentials from individual accounts?
> >
> > Monitoring
> > - ----------
> >
> > * Is there a nagios (or similar) installation somewhere that we can
> >   use to monitor the tracker, its backup etc?
> >
> > 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.
> >
> > * Where should we keep our tracker bugs? I'm happy to keep the
> >    http://efod.se/ptt/ (python-tracker-tracker) online if you like.
> >
> > Cheers,
> > \EF
> > - --
> > Erik Forsberg                 http://efod.se
> > GPG/PGP Key: 1024D/0BAC89D9
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.2.2 (GNU/Linux)
> > Comment: Processed by Mailcrypt 3.5.8+ <
> > http://mailcrypt.sourceforge.net/>
> >
> > iD8DBQFFRPXUrJurFAusidkRAhrXAKCHt8LBaI3rbs7G+cov+7DOnEkcBwCfXPDD
> > cnawo0QapBpaHMVsNiXz4l4=
> > =naYd
> > -----END PGP SIGNATURE-----
> > _______________________________________________
> > Tracker-discuss mailing list
> > Tracker-discuss at python.org
> > http://mail.python.org/mailman/listinfo/tracker-discuss
> >
>
>
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061029/c7bc4761/attachment.html 

From brett at python.org  Sun Oct 29 21:58:05 2006
From: brett at python.org (Brett Cannon)
Date: Sun, 29 Oct 2006 12:58:05 -0800
Subject: [Tracker-discuss] Status of new issue tracker
Message-ID: <bbaeab100610291258i43e47510rab00c0f40107e292@mail.gmail.com>

The initial admins for the Roundup installation have been chosen: Paul
DuBois, Michael Twomey, Stefan Seefeld, and Erik Forsberg.  The offer from
Upfront Systems (http://www.upfrontsystems.co.za/) has been accepted for
professional Roundup hosting.

Discussion of how to handle the new tracker (including the design of it,
handling the transition, etc.) will take place on the tracker-discuss
mailing list (http://mail.python.org/mailman/listinfo/tracker-discuss).  If
you want to provide input on what you want the new tracker to do, please
join the list.  Input from members of python-dev will take precedence so
please participate if you have any interest.


I don't have a timeline on when all of this will happen (talks amongst the
four admins has already started on the mailing list and Upfront has started
the process of getting us our account).  The first step is to get the admins
situated with their new server.  Then we start worrying about what info we
want the tracker to store and how to transition off of SF.

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061029/460f52c4/attachment.htm 

From roche at upfrontsystems.co.za  Sun Oct 29 23:49:02 2006
From: roche at upfrontsystems.co.za (=?ISO-8859-1?Q?Roch=E9?= Compaan)
Date: Mon, 30 Oct 2006 00:49:02 +0200
Subject: [Tracker-discuss] Getting Started
In-Reply-To: <87odrv6k2y.fsf@uterus.efod.se>
References: <87odrv6k2y.fsf@uterus.efod.se>
Message-ID: <1162162142.8245.12.camel@kwaaitjie>

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


From anthony at interlink.com.au  Mon Oct 30 00:25:43 2006
From: anthony at interlink.com.au (Anthony Baxter)
Date: Mon, 30 Oct 2006 10:25:43 +1100
Subject: [Tracker-discuss] Getting Started
In-Reply-To: <1162162142.8245.12.camel@kwaaitjie>
References: <87odrv6k2y.fsf@uterus.efod.se>
	<1162162142.8245.12.camel@kwaaitjie>
Message-ID: <200610301025.46223.anthony@interlink.com.au>

On Monday 30 October 2006 09:49, Roch? Compaan wrote:
> > * 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?


Why not just use the same tracker?

Note that there's already a 'trac' installation for python.org bugs. I don't 
see any reason why we couldn't use the same tracker for all of this, with 
appropriately defined pools.


From seefeld at sympatico.ca  Mon Oct 30 01:33:24 2006
From: seefeld at sympatico.ca (Stefan Seefeld)
Date: Sun, 29 Oct 2006 19:33:24 -0500
Subject: [Tracker-discuss] Getting Started
In-Reply-To: <200610301025.46223.anthony@interlink.com.au>
References: <87odrv6k2y.fsf@uterus.efod.se>	<1162162142.8245.12.camel@kwaaitjie>
	<200610301025.46223.anthony@interlink.com.au>
Message-ID: <45454854.2080402@sympatico.ca>

Anthony Baxter wrote:
> On Monday 30 October 2006 09:49, Roch? Compaan wrote:
>>> * 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?
> 
> 
> Why not just use the same tracker?

At least initially that would be hard. We are still in the phase where
we discuss schema changes, and so it is better to not have to do these
changes on a live tracker. (Also, as mentioned before, where do you
report a bug about the tracker being unreachable ?)

For the meta-tracker we don't need anything but the most basic (default)
setup, i.e. this thing can go live instantly.

Regards,
		Stefan

-- 

      ...ich hab' noch einen Koffer in Berlin...