<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Servers downtime scheduled from Feb. 1 to 2 for maintenance
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Servers%20downtime%20scheduled%20from%20Feb.%201%20to%202%20for%0A%20maintenance&In-Reply-To=%3C4F281BC8.1020107%40gmail.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="011677.html">
   <LINK REL="Next"  HREF="011680.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Servers downtime scheduled from Feb. 1 to 2 for maintenance</H1>
    <B>Guillaume Rousse</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Servers%20downtime%20scheduled%20from%20Feb.%201%20to%202%20for%0A%20maintenance&In-Reply-To=%3C4F281BC8.1020107%40gmail.com%3E"
       TITLE="[Mageia-dev] Servers downtime scheduled from Feb. 1 to 2 for maintenance">guillomovitch at gmail.com
       </A><BR>
    <I>Tue Jan 31 17:50:16 CET 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="011677.html">[Mageia-dev] Servers downtime scheduled from Feb. 1 to 2 for	maintenance
</A></li>
        <LI>Next message: <A HREF="011680.html">[Mageia-dev] [Mageia-discuss] Servers downtime scheduled from	Feb. 1 to 2 for maintenance
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#11678">[ date ]</a>
              <a href="thread.html#11678">[ thread ]</a>
              <a href="subject.html#11678">[ subject ]</a>
              <a href="author.html#11678">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Le 31/01/2012 17:02, Thierry Vignaud a &#233;crit :
&gt;<i> On 31 January 2012 15:09, Michael Scherer&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>&gt;  wrote:
</I>&gt;&gt;&gt;<i> some Mageia servers will be down from Wednesday Feb. 1st to Thursday
</I>&gt;&gt;&gt;<i> Feb. 2nd for maintenance. Particularly, the following services will be
</I>&gt;&gt;&gt;<i> unavailable:
</I>&gt;&gt;&gt;<i> - our LDAP/user identity db,
</I>&gt;&gt;&gt;<i> - build system,
</I>&gt;&gt;&gt;<i> - Bugzilla,
</I>&gt;&gt;&gt;<i> - all mailing-lists hosted on ml.mageia.org,
</I>&gt;&gt;&gt;<i> - Wiki,
</I>&gt;&gt;&gt;<i> - forums.
</I>&gt;&gt;<i> - transifex
</I>&gt;&gt;<i> - epoll
</I>&gt;&gt;<i> - svn, git
</I>&gt;&gt;<i> - youri web interface
</I>&gt;&gt;<i> - maint db
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> in short, almost all web applications ( ie, hosted on alamut ), and the
</I>&gt;&gt;<i> build system. See <A HREF="http://svnweb.mageia.org/adm/puppet/manifests/nodes/">http://svnweb.mageia.org/adm/puppet/manifests/nodes/</A>
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> And to complete :
</I>&gt;&gt;<i> - ldap will still work ( we do have a redundant setup, even if I have
</I>&gt;&gt;<i> not finished making sure everything use the 2nd ldap in case of failure
</I>&gt;&gt;<i> ), but readonly
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> - mails will still be queued, so nothing should be lost
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> We will announce on irc the exact moment when we plan to shutdown
</I>&gt;&gt;<i> servers.
</I>&gt;<i>
</I>&gt;<i> Announce it by mail too please.
</I>&gt;<i>
</I>&gt;<i> BTW, we should try to make more stuff redundancy. Withough going up to
</I>&gt;<i> using DRBD
</I>&gt;<i> for VM images, we could:
</I>&gt;<i> - for SVN, it's easy to have at least a RO secondary server:
</I>&gt;<i> <A HREF="http://svnbook.red-bean.com/en/1.7/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.writethruproxy">http://svnbook.red-bean.com/en/1.7/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.writethruproxy</A>
</I>&gt;<i> if we stop write access on the master, we could wait for the slave to
</I>&gt;<i> keep up with the latest commits, then make it RW
</I>&gt;<i> when we need to stop the master.
</I>&gt;<i> - for bugzilla, have two VM who perform master-master replication; we
</I>&gt;<i> can this way
</I>&gt;<i>   I'm not sure bugzilla support writing on both ends, but without
</I>&gt;<i> performing load balancing,
</I>&gt;<i>   when needed, we could stop access to the active one, wait for
</I>&gt;<i> replication to finish, open
</I>&gt;<i>   access on the second one
</I>Given the few downtime sofar, is this really justified ? Complexity is 
rarely a synonym of high availability...

&gt;<i> - having more hypervisors and live migrating our VMs off the
</I>&gt;<i> hypervisor we update so that
</I>&gt;<i>    rebooting it doesn't impact service;
</I>&gt;<i> - ...
</I>This one seems perfectly reasonable, tough, as natively supported by 
hypervisors.

-- 
BOFH excuse #101:

Collapsed Backbone
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="011677.html">[Mageia-dev] Servers downtime scheduled from Feb. 1 to 2 for	maintenance
</A></li>
	<LI>Next message: <A HREF="011680.html">[Mageia-dev] [Mageia-discuss] Servers downtime scheduled from	Feb. 1 to 2 for maintenance
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#11678">[ date ]</a>
              <a href="thread.html#11678">[ thread ]</a>
              <a href="subject.html#11678">[ subject ]</a>
              <a href="author.html#11678">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>