diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20120131/006396.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20120131/006396.html | 108 |
1 files changed, 108 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20120131/006396.html b/zarb-ml/mageia-discuss/20120131/006396.html new file mode 100644 index 000000000..58e4ee5fe --- /dev/null +++ b/zarb-ml/mageia-discuss/20120131/006396.html @@ -0,0 +1,108 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] [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-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20%5BMageia-dev%5D%20Servers%20downtime%20scheduled%20from%0A%09Feb.%201%20to%202%20for%20maintenance&In-Reply-To=%3CCAONrEtahnKtk1XoFrHwo3n3gVj-2YqrVqPKur5HvTAYRbvWt%3Dw%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006394.html"> + <LINK REL="Next" HREF="006397.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] [Mageia-dev] Servers downtime scheduled from Feb. 1 to 2 for maintenance</H1> + <B>Thierry Vignaud</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20%5BMageia-dev%5D%20Servers%20downtime%20scheduled%20from%0A%09Feb.%201%20to%202%20for%20maintenance&In-Reply-To=%3CCAONrEtahnKtk1XoFrHwo3n3gVj-2YqrVqPKur5HvTAYRbvWt%3Dw%40mail.gmail.com%3E" + TITLE="[Mageia-discuss] [Mageia-dev] Servers downtime scheduled from Feb. 1 to 2 for maintenance">thierry.vignaud at gmail.com + </A><BR> + <I>Tue Jan 31 17:02:25 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="006394.html">[Mageia-discuss] [Mageia-dev] Servers downtime scheduled from Feb. 1 to 2 for maintenance +</A></li> + <LI>Next message: <A HREF="006397.html">[Mageia-discuss] Long Term Support Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6396">[ date ]</a> + <a href="thread.html#6396">[ thread ]</a> + <a href="subject.html#6396">[ subject ]</a> + <a href="author.html#6396">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 31 January 2012 15:09, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">misc at zarb.org</A>> wrote: +>><i> some Mageia servers will be down from Wednesday Feb. 1st to Thursday +</I>>><i> Feb. 2nd for maintenance. Particularly, the following services will be +</I>>><i> unavailable: +</I>>><i> - our LDAP/user identity db, +</I>>><i> - build system, +</I>>><i> - Bugzilla, +</I>>><i> - all mailing-lists hosted on ml.mageia.org, +</I>>><i> - Wiki, +</I>>><i> - forums. +</I>><i> - transifex +</I>><i> - epoll +</I>><i> - svn, git +</I>><i> - youri web interface +</I>><i> - maint db +</I>><i> +</I>><i> in short, almost all web applications ( ie, hosted on alamut ), and the +</I>><i> build system. See <A HREF="http://svnweb.mageia.org/adm/puppet/manifests/nodes/">http://svnweb.mageia.org/adm/puppet/manifests/nodes/</A> +</I>><i> +</I>><i> And to complete : +</I>><i> - ldap will still work ( we do have a redundant setup, even if I have +</I>><i> not finished making sure everything use the 2nd ldap in case of failure +</I>><i> ), but readonly +</I>><i> +</I>><i> - mails will still be queued, so nothing should be lost +</I>><i> +</I>><i> We will announce on irc the exact moment when we plan to shutdown +</I>><i> servers. +</I> +Announce it by mail too please. + +BTW, we should try to make more stuff redundancy. Withough going up to +using DRBD +for VM images, we could: +- for SVN, it's easy to have at least a RO secondary server: +<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> +if we stop write access on the master, we could wait for the slave to +keep up with the latest commits, then make it RW +when we need to stop the master. +- for bugzilla, have two VM who perform master-master replication; we +can this way + I'm not sure bugzilla support writing on both ends, but without +performing load balancing, + when needed, we could stop access to the active one, wait for +replication to finish, open + access on the second one +- having more hypervisors and live migrating our VMs off the +hypervisor we update so that + rebooting it doesn't impact service; +- ... + +See you +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006394.html">[Mageia-discuss] [Mageia-dev] Servers downtime scheduled from Feb. 1 to 2 for maintenance +</A></li> + <LI>Next message: <A HREF="006397.html">[Mageia-discuss] Long Term Support Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6396">[ date ]</a> + <a href="thread.html#6396">[ thread ]</a> + <a href="subject.html#6396">[ subject ]</a> + <a href="author.html#6396">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss +mailing list</a><br> +</body></html> |