diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-webteam/2011-January/000149.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-webteam/2011-January/000149.html')
| -rw-r--r-- | zarb-ml/mageia-webteam/2011-January/000149.html | 168 |
1 files changed, 168 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/2011-January/000149.html b/zarb-ml/mageia-webteam/2011-January/000149.html new file mode 100644 index 000000000..47731a910 --- /dev/null +++ b/zarb-ml/mageia-webteam/2011-January/000149.html @@ -0,0 +1,168 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-webteam] [Mageia-sysadm] Forum VM needs + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20%5BMageia-sysadm%5D%20Forum%20VM%20needs&In-Reply-To=%3C1294921772.6060.1.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000145.html"> + <LINK REL="Next" HREF="000152.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-webteam] [Mageia-sysadm] Forum VM needs</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20%5BMageia-sysadm%5D%20Forum%20VM%20needs&In-Reply-To=%3C1294921772.6060.1.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-webteam] [Mageia-sysadm] Forum VM needs">misc at zarb.org + </A><BR> + <I>Thu Jan 13 13:29:32 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000145.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI>Next message: <A HREF="000152.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#149">[ date ]</a> + <a href="thread.html#149">[ thread ]</a> + <a href="subject.html#149">[ subject ]</a> + <a href="author.html#149">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mercredi 12 janvier 2011 à 23:05 +0100, Maât a écrit : +><i> Le 12/01/2011 22:37, nicolas vigier a écrit : +</I>><i> > On Wed, 12 Jan 2011, Maât wrote: +</I> +><i> >> So phpBB needs a LAMP Stack : Apache + PHP5 + MysSQL5 (it prefers to have MySQLi extention) +</I>><i> > Do you know if it would be possible to use Postgresql instead of MySQL ? +</I>><i> > We already have a Postgresql server running on alamut that we could use. +</I>><i> phpBB3 is supposed to work with PostgreSQL 7.3+ though it's not as widely used as MySQL as a phpBB backend. +</I> +Great, so more testing to do /o\ + +><i> The problem (for me) is that i just know the basic of PostgreSQL... so we'll need someone else skilled +</I>><i> enough to tune it (and i'd be truly happy to learn from him/her) +</I> +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. + +><i> There will be a central node repos (somewhere... perhaps github or gitorious) cloned from upstream +</I>><i> phpbb... from there we'll clone dev repos to add our changes... templates, mods integrations, specific patches etc. +</I> +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. + +><i> We'll clone also integration repos (used for first test level) from which test +</I>><i> repos will be cloned and then production will be at the end +</I>><i> +</I>><i> Of these 3 i'd like at least to have test on the server (and production obviously) +</I> +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 ). + +><i> > Do you need modifications in phpBB sources ? +</I>><i> > +</I>><i> yes... some coming from (more or less) official patches (called "mods") some coming from ash and i and perhaps other php devs +</I> +/me close eyes when reading "(more of less) official patches". + +><i> > If that's only for configuration files, we can host them on puppet svn +</I>><i> > and deploy them with puppet. +</I>><i> > +</I>><i> if you want to play with puppet for production and having us not touching it with our dirty hands (^^) i'm perfectly ok with +</I>><i> that... but i neeed a integration and testing forum with cascaded by git cloning +</I>><i> (and i need to sync database of test from production to simulate version migration then cancel and replay as much a i need) +</I> +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. + + +><i> so that we test our changes (and the migration process) on a perfectly identic env before putting them in production. +</I> +As said, I would strongly favor a automated deployment using git, at +least on production server. + +><i> (And git will be the spine of all that process) +</I>><i> +</I>><i> > Can we have access to the sources, list of changes (if changes are +</I>><i> > needed), and configuration files somewhere ? +</I>><i> > +</I>><i> > If a source management is needed, I would use Mageia svn for now, and +</I>><i> > later an other source management software when it is setup on Mageia +</I>><i> > servers. +</I>><i> Svn does not offer enough flexibility for playing with our repository while +</I>><i> keeping a true link with upstream to merge their change with ours without pain :-/ +</I>><i> +</I>><i> (Sorry but here SVN is not an option we should consider viable imho) +</I> +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 + + +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000145.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI>Next message: <A HREF="000152.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#149">[ date ]</a> + <a href="thread.html#149">[ thread ]</a> + <a href="subject.html#149">[ subject ]</a> + <a href="author.html#149">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-webteam">More information about the Mageia-webteam +mailing list</a><br> +</body></html> |