[Mageia-webteam] [Mageia-sysadm] Forum VM needs

[Michael Scherer]

Le mercredi 12 janvier 2011 à 23:05 +0100, Maât a écrit :
> Le 12/01/2011 22:37, nicolas vigier a écrit :
> > On Wed, 12 Jan 2011, Maât wrote:

> >> So phpBB needs a LAMP Stack : Apache + PHP5 + MysSQL5 (it prefers to have MySQLi extention)
> > Do you know if it would be possible to use Postgresql instead of MySQL ?
> > We already have a Postgresql server running on alamut that we could use.
> phpBB3 is supposed to work with PostgreSQL 7.3+ though it's not as widely used as MySQL as a phpBB backend.

Great, so more testing to do /o\

> The problem (for me) is that i just know the basic of PostgreSQL... so we'll need someone else skilled 
> enough to tune it (and i'd be truly happy to learn from him/her)

Nanar will be able to do it, even if hosting a small database like this
may not be very appealing to him. There is just 5g, when compared to
sophie, I let him give the numbers.

But I would prefer to have it hosted on mysql if we later migrate to
another vm. The lag Marseille <-> Toulouse will not be good if it can be
avoided. We could also setup a different postgresql server on the forum
vm in this case.

In any case, postgresql to mysql conversion doesn't look doable.

> There will be a central node repos (somewhere... perhaps github or gitorious) cloned from upstream 
> phpbb... from there we'll clone dev repos to add our changes... templates, mods integrations, specific patches etc.

I would prefer to have it hosted on our servers, for various and obvious
reasons ( like : "handling the auth and permission ourself" "proper
bugtracker integration", etc ).

But we are not ready, see my answer about gitorious. So here is a
proposal in 4 steps :

Now :
- we do a git checkout every 5 minutes ( just need the url, and
testing )

Later ( like short term ):
- sysadmins do work to have a git repository, who will be the exact
state of production, and be the reference. That where changes are
pushed, and where the server take his checkout. So this way, the project
handle who can push to it using ldap (unification of auth, delegatation
etc ).

Later again ( like mid term ) :
- you express your needs in term of hosting ( like what type of hook,
requirement in term of web interface, "need to do review" "need to show
dancing hamster" , etc ) when we do a call for that ( you can do before,
but this will potentially be lost ).

Once we have installed this :
- you switch to our infrastructure.

> We'll clone also integration repos (used for first test level) from which test 
> repos will be cloned and then production will be at the end
> 
> Of these 3 i'd like at least to have test on the server (and production obviously)

Since we do have puppet and can clone machine, I would then prefer to
have a separate vm for test than for production, unless there is problem
with the intended usage (like you really need to have the exact same
hardware, for load testing purpose ).

> > Do you need modifications in phpBB sources ?
> >
> yes... some coming from (more or less) official patches (called "mods") some coming from ash and i and perhaps other php devs

/me close eyes when reading "(more of less) official patches".

> > If that's only for configuration files, we can host them on puppet svn
> > and deploy them with puppet.
> >
> if you want to play with puppet for production and having us not touching it with our dirty hands (^^) i'm perfectly ok with 
> that... but i neeed a integration and testing forum with cascaded by git cloning 
> (and i need to sync database of test from production to simulate version migration then cancel and replay as much a i need) 

Could we do it with a master/slave replication without much trouble ?
( and possibly, one that would automatically recreate the db once it is
dropped )

Or we can do snapshot using lvm, but I think this can be quite fragile.


> so that we test our changes (and the migration process) on a perfectly identic env before putting them in production.

As said, I would strongly favor a automated deployment using git, at
least on production server.

> (And git will be the spine of all that process)
>  
> > Can we have access to the sources, list of changes (if changes are
> > needed), and configuration files somewhere ?
> >
> > If a source management is needed, I would use Mageia svn for now, and
> > later an other source management software when it is setup on Mageia
> > servers.
> Svn does not offer enough flexibility for playing with our repository while 
> keeping a true link with upstream to merge their change with ours without pain :-/
> 
> (Sorry but here SVN is not an option we should consider viable imho)

As I said, if people want us to host git, there is a few questions to
answer first ( I guess that 2 weeks to gather requirement should
suffice, given proper flamewar handling )

-- 
Michael Scherer