summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/2012-April/004378.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-sysadm/2012-April/004378.html')
-rw-r--r--zarb-ml/mageia-sysadm/2012-April/004378.html136
1 files changed, 136 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2012-April/004378.html b/zarb-ml/mageia-sysadm/2012-April/004378.html
new file mode 100644
index 000000000..fdee84191
--- /dev/null
+++ b/zarb-ml/mageia-sysadm/2012-April/004378.html
@@ -0,0 +1,136 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-sysadm] questions about our infrastructure setup &amp; 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=%3C1333456728.8337.38.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="004377.html">
+ <LINK REL="Next" HREF="004392.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-sysadm] questions about our infrastructure setup &amp; 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=%3C1333456728.8337.38.camel%40liliana.cdg.redhat.com%3E"
+ TITLE="[Mageia-sysadm] questions about our infrastructure setup &amp; costs">misc at zarb.org
+ </A><BR>
+ <I>Tue Apr 3 14:38:48 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="004377.html">[Mageia-sysadm] questions about our infrastructure setup &amp; costs
+</A></li>
+ <LI>Next message: <A HREF="004392.html">[Mageia-sysadm] questions about our infrastructure setup &amp; costs
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4378">[ date ]</a>
+ <a href="thread.html#4378">[ thread ]</a>
+ <a href="subject.html#4378">[ subject ]</a>
+ <a href="author.html#4378">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le mardi 03 avril 2012 &#224; 10:34 +0200, Romain d'Alverny a &#233;crit :
+&gt;<i> On Mon, Apr 2, 2012 at 21:00, Michael scherer &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at zarb.org</A>&gt; wrote:
+</I>&gt;<i> &gt; Well, you have the hardware we paid, no ?
+</I>&gt;<i> &gt; The accounting is on the bank account, and despites requiring searching, it
+</I>&gt;<i> &gt; was published.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; If iyou need information on the hardware we got at the beggining, I can send
+</I>&gt;<i> &gt; on this list a partial history of where
+</I>&gt;<i> &gt; does every piece of hardware come from, if that what you need, but I prefer to
+</I>&gt;<i> &gt; be sure that's really what you need before spending a afternoon on this.
+</I>&gt;<i>
+</I>&gt;<i> It's more important, looking ahead, to know what is needed, because
+</I>&gt;<i> the costs of the infrastructure before and today (offered/acquired
+</I>&gt;<i> hardware, hosting, etc.) are not the same for hardware/services
+</I>&gt;<i> available today or tomorrow. For a given service, the needs are known
+</I>&gt;<i> and stable (or can be planned). The cost (and options) of that
+</I>&gt;<i> infrastructure, on the other hand, may change more rapidly with time
+</I>&gt;<i> (up or down).
+</I>&gt;<i>
+</I>&gt;<i> &gt; Basically : [...]
+</I>&gt;<i>
+</I>&gt;<i> &gt; I do not say that's not a good idea to document ( I started to write
+</I>&gt;<i> &gt; various SOP on the wiki ), just that I fear that no one will
+</I>&gt;<i> &gt; be motivated to do it and to keep it up to date, especially for such a huge
+</I>&gt;<i> &gt; document.
+</I>&gt;<i>
+</I>&gt;<i> Thanks for the tips anyway, I'll see what I can prepare with that,
+</I>&gt;<i> although I'm afraid it's useless, given some echoes to this thread
+</I>&gt;<i> (here and elsewhere). I won't be able to plan for your (sysadmin)
+</I>&gt;<i> capacities and needs (that means, looking 2/3 years ahead), if you
+</I>&gt;<i> don't tell me in a documented, maintained and clear way.
+</I>
+To tell the truth, I think we have more than what we need in term of
+hardware. While we can always be ok with faster builders and so on, as I
+say, we upgrade, stuff are seen as fast, and after 1 week, that's
+becoming the reference speed and so people do not see it anymore.
+
+So I propose to rather take in account than in X years, we will have
+lost Y servers, Z harddrive, etc, and plan this.
+
+( of course, we do not have X Y Z, but at least, that's the way i would
+pursue for planning )
+
+&gt;<i> Doesn't need to be a huge doc, especially for a start. But it needs to
+</I>&gt;<i> revolve around something logical for deployment and understandable for
+</I>&gt;<i> most, non technical people, so service-centered didn't seem absurd to
+</I>&gt;<i> me, and a graphic-based format neither, so that a sense of priority
+</I>&gt;<i> can be shared.
+</I>
+Service centered is not absurd, just it doesn't map easily to physical
+hardware for now.
+
+I would be in favor of moving from &quot;one big server&quot; to &quot;several system&quot;
+for alamut ( and also for valstar maybe ). This would permit several
+improvements :
+- delayed upgrade ( ie, we will upgrade one service at a time )
+
+- easier duplication for testing ( clone vm, upgrade vm, if it doesn't
+work, we fix and try again )
+
+- remote upgrade ( ie, done by the confort of my chair in Paris, not in
+a noisy server room )
+
+- better service isolation, and the path toward less centralized
+management ( ie, we could let someone play with tx without touching to
+the rest, etc ).
+
+- better resilience, by moving vm accross server in case of upgrade, etc
+
+an,d from a network point of view, a better layout ( ie, server are not
+directly exposed to the internet, we can put a reverse proxy with
+various goodies like a page to say &quot;we are upgrading&quot; when the virtual
+server is down for maintainance, etc )
+
+Until then, that's hard to say &quot;this service requires that amount of
+ressources&quot;.
+
+--
+Michael Scherer
+
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="004377.html">[Mageia-sysadm] questions about our infrastructure setup &amp; costs
+</A></li>
+ <LI>Next message: <A HREF="004392.html">[Mageia-sysadm] questions about our infrastructure setup &amp; costs
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#4378">[ date ]</a>
+ <a href="thread.html#4378">[ thread ]</a>
+ <a href="subject.html#4378">[ subject ]</a>
+ <a href="author.html#4378">[ 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>