summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-webteam/2011-January/000160.html
blob: 3090887db4fd7b94d01037774e5eb14c11ef8d21 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
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 &#224; 16:46 +0100, Ma&#226;t a &#233;crit :
&gt;<i> Le 15/01/2011 16:11, Michael scherer a &#233;crit :
</I>&gt;<i> &gt; On Sat, Jan 15, 2011 at 11:46:38AM +0100, Ma&#226;t wrote:
</I>&gt;<i> &gt;&gt; Le 13/01/2011 13:29, Michael Scherer a &#233;crit :
</I>&gt;<i> &gt;&gt;
</I>&gt;<i> &gt;&gt; ----8&lt;----
</I>&gt;<i> &gt;&gt;&gt; In any case, postgresql to mysql conversion doesn't look doable.
</I>&gt;<i> &gt;&gt;&gt;
</I>&gt;<i> &gt;&gt; It could be done using things like TOS
</I>&gt;<i> &gt; Url ? 
</I>&gt;<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>&gt;<i> 
</I>&gt;<i> &gt;&gt;&gt; But we are not ready, see my answer about gitorious. So here is a
</I>&gt;<i> &gt;&gt;&gt; proposal in 4 steps :
</I>&gt;<i> &gt;&gt;&gt;
</I>&gt;<i> &gt;&gt;&gt; Now :
</I>&gt;<i> &gt;&gt;&gt; - we do a git checkout every 5 minutes ( just need the url, and
</I>&gt;<i> &gt;&gt;&gt; testing )
</I>&gt;<i> &gt;&gt; Ouch
</I>&gt;<i> &gt; Why ouch ?
</I>&gt;<i> &gt;
</I>&gt;<i> &gt; 5 minutes is too often, not often enough ?
</I>&gt;<i> &gt; ( this is configurable, as this is based on cron )
</I>&gt;<i> &gt;
</I>&gt;<i> &gt; I would prefer a pull based approach rather than push, because 
</I>&gt;<i> &gt; 1) this is already written
</I>&gt;<i> &gt; 2) this is more secure
</I>&gt;<i> &gt;  
</I>&gt;<i> &gt; But it may not be good for deployment.
</I>&gt;<i> &gt;
</I>&gt;<i> ok for pull but human-triggered !
</I>&gt;<i> 
</I>&gt;<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...

&gt;<i> &gt;&gt; But we could perfectly use the last (nightly ,) production backup to populate the test base when i need to go 
</I>&gt;<i> &gt;&gt; back to &quot;clean production state&quot;
</I>&gt;<i> &gt; This requires use to do backup, and so have at least a backup process
</I>&gt;<i> &gt; But we can also do it. I just think that replication would be less heavy 
</I>&gt;<i> &gt; on IO than dump/reload when needed ( and would be easier to automate ).
</I>&gt;<i> &gt;
</I>&gt;<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>