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

[Maât]

Le 13/01/2011 13:29, Michael Scherer a écrit :

----8<----
> In any case, postgresql to mysql conversion doesn't look doable.
>
It could be done using things like TOS

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

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

> 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 ).
ok for that

> 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 ).
Nope... the we don't need to have cascading git repos... each integration/testing/production can be cloned from reference

>>> 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".
>
That's the way phpBB people deals with "mods" : authors (not phpBB Team) publish them on the mods dedicated forum, and you are free to use (or not) them without warranty at all some are widely used and well known to be stable...

That's why integration and testing stages are so important

>>> 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.
>
Nope... master/slave replication will not fit my needs : i need 2 separate bases. The production i won't play with it.

For testing : once i updated the code to the new version there can be SQL modifications : new tables, alter tables, insert or update for rows...

This will be triggered from admin board of phpBB... with a master/slave this would be forbidden or would brake replication

But we could perfectly use the last (nightly ,) production backup to populate the test base when i need to go back to "clean production state"


>> 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.
ok for me

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