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/000160.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/000160.html')
| -rw-r--r-- | zarb-ml/mageia-webteam/2011-January/000160.html | 116 |
1 files changed, 116 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/2011-January/000160.html b/zarb-ml/mageia-webteam/2011-January/000160.html new file mode 100644 index 000000000..3090887db --- /dev/null +++ b/zarb-ml/mageia-webteam/2011-January/000160.html @@ -0,0 +1,116 @@ +<!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=%3C1295268131.24697.7.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="000158.html"> + <LINK REL="Next" HREF="000150.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=%3C1295268131.24697.7.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-webteam] [Mageia-sysadm] Forum VM needs">misc at zarb.org + </A><BR> + <I>Mon Jan 17 13:42:10 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000158.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI>Next message: <A HREF="000150.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#160">[ date ]</a> + <a href="thread.html#160">[ thread ]</a> + <a href="subject.html#160">[ subject ]</a> + <a href="author.html#160">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le samedi 15 janvier 2011 à 16:46 +0100, Maât a écrit : +><i> Le 15/01/2011 16:11, Michael scherer a écrit : +</I>><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>><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>><i> +</I>><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>><i> ok for pull but human-triggered ! +</I>><i> +</I>><i> in case of a commit pushed by error i don't want production forum follow the move by itself ! +</I> +We could had a post receive hook that check that any commit comes from +testing first. Ie, no way to commit to production without pushing to +testing first. + +I would even check that the commit was in testing for at least X days or +X hours. But this may cause trouble for security fix. On the other hand, +you don't want to rush a security fix... + +><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>><i> doing backups would be a good idea imho +</I> +Yeah, obviously yes. But we either do them on the same server ( and +that's kinda useless I fear ), or we do this cross servers ( and that's +kinda complex ). + +We could for a start dump pgsql on valstar, and sync svn on alamut. + +Or use rabbit, there is 2 To, we could spare some for backups ? + +-- +Michael Scherer + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000158.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI>Next message: <A HREF="000150.html">[Mageia-webteam] [Mageia-sysadm] Forum VM needs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#160">[ date ]</a> + <a href="thread.html#160">[ thread ]</a> + <a href="subject.html#160">[ subject ]</a> + <a href="author.html#160">[ 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> |