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/000157.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/000157.html')
| -rw-r--r-- | zarb-ml/mageia-webteam/2011-January/000157.html | 144 |
1 files changed, 144 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/2011-January/000157.html b/zarb-ml/mageia-webteam/2011-January/000157.html new file mode 100644 index 000000000..717ce154c --- /dev/null +++ b/zarb-ml/mageia-webteam/2011-January/000157.html @@ -0,0 +1,144 @@ +<!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%20%20%20Forum%20VM%20needs&In-Reply-To=%3C20110115151159.GB23639%40sisay.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000155.html"> + <LINK REL="Next" HREF="000158.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%20%20%20Forum%20VM%20needs&In-Reply-To=%3C20110115151159.GB23639%40sisay.ephaone.org%3E" + TITLE="[Mageia-webteam] [Mageia-sysadm] Forum VM needs">misc at zarb.org + </A><BR> + <I>Sat Jan 15 16:11:59 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000155.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI>Next message: <A HREF="000158.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#157">[ date ]</a> + <a href="thread.html#157">[ thread ]</a> + <a href="subject.html#157">[ subject ]</a> + <a href="author.html#157">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, Jan 15, 2011 at 11:46:38AM +0100, Maât wrote: +><i> Le 13/01/2011 13:29, Michael Scherer a écrit : +</I>><i> +</I>><i> ----8<---- +</I>><i> > In any case, postgresql to mysql conversion doesn't look doable. +</I>><i> > +</I>><i> It could be done using things like TOS +</I> +Url ? + +><i> > But we are not ready, see my answer about gitorious. So here is a +</I>><i> > proposal in 4 steps : +</I>><i> > +</I>><i> > Now : +</I>><i> > - we do a git checkout every 5 minutes ( just need the url, and +</I>><i> > testing ) +</I>><i> Ouch +</I> +Why ouch ? + +5 minutes is too often, not often enough ? +( this is configurable, as this is based on cron ) + +I would prefer a pull based approach rather than push, because +1) this is already written +2) this is more secure + +But it may not be good for deployment. + +><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 +</I>><i> >> and i and perhaps other php devs +</I>><i> > /me close eyes when reading "(more of less) official patches". +</I>><i> > +</I>><i> That's the way phpBB people deals with "mods" : authors (not phpBB Team) publish them on the mods +</I>><i> dedicated forum, and you are free to use (or not) them without warranty at all some are widely +</I>><i> used and well known to be stable... +</I>><i> +</I>><i> That's why integration and testing stages are so important +</I> +Because software distribution is crappy ? +That's indeed a good reason ( now, do not be asthonished if we joke on php... ) + +><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>><i> > Could we do it with a master/slave replication without much trouble ? +</I>><i> > ( and possibly, one that would automatically recreate the db once it is +</I>><i> > dropped ) +</I>><i> > +</I>><i> > Or we can do snapshot using lvm, but I think this can be quite fragile. +</I>><i> > +</I>><i> Nope... master/slave replication will not fit my needs : i need 2 separate bases. The production i won't play +</I>><i> with it. +</I>><i> +</I>><i> For testing : once i updated the code to the new version there can be SQL modifications : new tables, alter tables, +</I>><i> insert or update for rows... +</I>><i> +</I>><i> This will be triggered from admin board of phpBB... with a master/slave this would be forbidden or would brake +</I>><i> replication +</I> +That's the idea, stop the replication for testing purposes. Hence my note about recreating it once we +drop the slave. + +We start with a clean db, we replicate. +Once we want to test the upgrade, we stop replication, we test. +We drop the db, we resync if needed + +Once we finished the test, we drop the tables, and we restart the synchronisation. + +><i> But we could perfectly use the last (nightly ,) production backup to populate the test base when i need to go +</I>><i> back to "clean production state" +</I> +This requires use to do backup, and so have at least a backup process +But we can also do it. I just think that replication would be less heavy +on IO than dump/reload when needed ( and would be easier to automate ). + +I wonder if we could distribute sql dump of the forum on mirror ( like we could for bugs ). I see +no obvious use for that at the moment, but liberating data can lead to unexpected usages, and would +be a interesting move ( or a at least, a interesting thought experiment, since there is private messages +involved, so this would requires cleaning ) + +-- +Michael Scherer +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000155.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI>Next message: <A HREF="000158.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#157">[ date ]</a> + <a href="thread.html#157">[ thread ]</a> + <a href="subject.html#157">[ subject ]</a> + <a href="author.html#157">[ 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> |