diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2012-April/004376.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2012-April/004376.html | 125 |
1 files changed, 125 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2012-April/004376.html b/zarb-ml/mageia-sysadm/2012-April/004376.html new file mode 100644 index 000000000..6661b9a3f --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-April/004376.html @@ -0,0 +1,125 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] questions about our infrastructure setup & costs + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20questions%20about%20our%20infrastructure%20setup%20%26%20costs&In-Reply-To=%3C1333433178.8337.15.camel%40liliana.cdg.redhat.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="004369.html"> + <LINK REL="Next" HREF="004358.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] questions about our infrastructure setup & costs</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20questions%20about%20our%20infrastructure%20setup%20%26%20costs&In-Reply-To=%3C1333433178.8337.15.camel%40liliana.cdg.redhat.com%3E" + TITLE="[Mageia-sysadm] questions about our infrastructure setup & costs">misc at zarb.org + </A><BR> + <I>Tue Apr 3 08:06:18 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="004369.html">[Mageia-sysadm] questions about our infrastructure setup & costs +</A></li> + <LI>Next message: <A HREF="004358.html">[Mageia-sysadm] questions about our infrastructure setup & costs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#4376">[ date ]</a> + <a href="thread.html#4376">[ thread ]</a> + <a href="subject.html#4376">[ subject ]</a> + <a href="author.html#4376">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le lundi 02 avril 2012 à 22:12 +0200, Buchan Milne a écrit : +><i> On Monday, 2 April 2012 16:59:59 Michael Scherer wrote: +</I>><i> > Le lundi 02 avril 2012 à 15:23 +0200, Romain d'Alverny a écrit : +</I> +><i> > > 2) have a quick report, automatic +</I>><i> > > +</I>><i> > > about this (not only for sysadmin, but for all users of our +</I>><i> > > infrastructure). +</I>><i> > +</I>><i> > I do think for me that the current report of xymon are sufficient. +</I>><i> +</I>><i> There is some room for enhancements, but that requires a bit more knowledge +</I>><i> regarding real (physical) dependencies than I have at present. +</I>><i> +</I>><i> I can maybe add some examples which don't require that knowledge, so others +</I>><i> can add some more. +</I> +Yes, do not hesitate. + + +><i> > And of course, most of them have metered network connections that would +</I>><i> > maybe not be suitable for something like valstar, who act as a primary +</I>><i> > mirror. For reference, since we have started the server : +</I>><i> > +</I>><i> > RX bytes:453228974131 (422.1 GiB) +</I>><i> > TX bytes:9311461347504 (8.4 TiB) +</I>><i> > +</I>><i> > Uptime is 60 days. +</I>><i> > That's around 4 T per month of transfert. +</I>><i> +</I>><i> How much of this is internal to the hosting provider? +</I> +I have no idea. That's hard to say because on one hand, valstar serve as +mirror for builder, so there is lots of traffic. on the other hand, we +act as main mirror ( so traffic is duplicated 3/4 ), so every new rpms +and iso would be sent too. +As well as every tarball upload and download, from builder and from +packagers. + +Since RX would be "isos from rabbit + rpms build from jonund/ecosse + +tarball sent from packager", and TX is "isos sent to mirrors + rpms to +mirrors + chroot installation", I cannot give any realistic estimation. + +><i> [...] +</I>><i> A)That we should be able to know when our network connection is down? +</I>><i> +</I>><i> IMHO, the hosting provider should be monitoring this (our data center business +</I>><i> does this for all managed hosting customers). If the hosting provider is not +</I>><i> able to do that, then our options are: +</I>><i> 1)Monitor servers in one location from servers in another, and ensure that +</I>><i> they can inform us without requiring the servers in the first location to be +</I>><i> available +</I>><i> 2)Monitor the network interfaces etc. from inside the network, but have a non- +</I>><i> network notification system, such as SMS modem, or old cell-phone (Nokia 5110 +</I>><i> was the usual choice a few years ago). Alternatively, a 3G dongle for IP-based +</I>><i> access could be considered. +</I>><i> +</I>><i> (note that so far, there is minimal cost involved) +</I> +Monitoring is nice, but that's not a end. That doesn't serve much if we +cannot act on it :/ + +Usually, people see quite fast that everything is down. +-- +Michael Scherer + +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="004369.html">[Mageia-sysadm] questions about our infrastructure setup & costs +</A></li> + <LI>Next message: <A HREF="004358.html">[Mageia-sysadm] questions about our infrastructure setup & costs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#4376">[ date ]</a> + <a href="thread.html#4376">[ thread ]</a> + <a href="subject.html#4376">[ subject ]</a> + <a href="author.html#4376">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |