diff options
Diffstat (limited to 'zarb-ml/mageia-webteam/2011-January/000158.html')
-rw-r--r-- | zarb-ml/mageia-webteam/2011-January/000158.html | 161 |
1 files changed, 161 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/2011-January/000158.html b/zarb-ml/mageia-webteam/2011-January/000158.html new file mode 100644 index 000000000..9169e9d40 --- /dev/null +++ b/zarb-ml/mageia-webteam/2011-January/000158.html @@ -0,0 +1,161 @@ +<!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=%3C4D31C15F.70104%40vilarem.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000157.html"> + <LINK REL="Next" HREF="000160.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-webteam] [Mageia-sysadm] Forum VM needs</H1> + <B>Maât</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=%3C4D31C15F.70104%40vilarem.net%3E" + TITLE="[Mageia-webteam] [Mageia-sysadm] Forum VM needs">maat-ml at vilarem.net + </A><BR> + <I>Sat Jan 15 16:46:39 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000157.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI>Next message: <A HREF="000160.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#158">[ date ]</a> + <a href="thread.html#158">[ thread ]</a> + <a href="subject.html#158">[ subject ]</a> + <a href="author.html#158">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 15/01/2011 16:11, Michael scherer a écrit : +><i> On Sat, Jan 15, 2011 at 11:46:38AM +0100, Maât wrote: +</I>>><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>><i> Url ? +</I><A HREF="http://fr.talend.com/products-data-integration/talend-open-studio.php">http://fr.talend.com/products-data-integration/talend-open-studio.php</A> + +>>><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>><i> Why ouch ? +</I>><i> +</I>><i> 5 minutes is too often, not often enough ? +</I>><i> ( this is configurable, as this is based on cron ) +</I>><i> +</I>><i> I would prefer a pull based approach rather than push, because +</I>><i> 1) this is already written +</I>><i> 2) this is more secure +</I>><i> +</I>><i> But it may not be good for deployment. +</I>><i> +</I>ok for pull but human-triggered ! + +in case of a commit pushed by error i don't want production forum follow the move by itself ! + +>>>>><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>><i> Because software distribution is crappy ? +</I>><i> That's indeed a good reason ( now, do not be asthonished if we joke on php... ) +</I>cleanlyness of projet is not linked with the language or technology used... it's much more linked to the way people are organized inside the communities :) +>>>>><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>><i> That's the idea, stop the replication for testing purposes. Hence my note about recreating it once we +</I>><i> drop the slave. +</I>><i> +</I>><i> We start with a clean db, we replicate. +</I>><i> Once we want to test the upgrade, we stop replication, we test. +</I>><i> We drop the db, we resync if needed +</I>><i> +</I>><i> Once we finished the test, we drop the tables, and we restart the synchronisation. +</I>><i> +</I>Haaaaaa ! + +that's brilliant ! + +(i'm ashamed to admit that i did not imagine to use db synchronization this way) + +Of course if this is doable i'm ok more twice than one :) + +>><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>><i> This requires use to do backup, and so have at least a backup process +</I>><i> But we can also do it. I just think that replication would be less heavy +</I>><i> on IO than dump/reload when needed ( and would be easier to automate ). +</I>><i> +</I>doing backups would be a good idea imho + +><i> I wonder if we could distribute sql dump of the forum on mirror ( like we could for bugs ). I see +</I>><i> no obvious use for that at the moment, but liberating data can lead to unexpected usages, and would +</I>><i> be a interesting move ( or a at least, a interesting thought experiment, since there is private messages +</I>><i> involved, so this would requires cleaning ) +</I>><i> +</I>that would need cleaning indeed as french law (and imho ethics too wether legally enforced or not) protects personal data + +cheers + +Maât + + + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000157.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI>Next message: <A HREF="000160.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#158">[ date ]</a> + <a href="thread.html#158">[ thread ]</a> + <a href="subject.html#158">[ subject ]</a> + <a href="author.html#158">[ 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> |