diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2012-April/004358.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2012-April/004358.html | 166 |
1 files changed, 166 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2012-April/004358.html b/zarb-ml/mageia-sysadm/2012-April/004358.html new file mode 100644 index 000000000..aa01bc0b0 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-April/004358.html @@ -0,0 +1,166 @@ +<!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%09costs&In-Reply-To=%3C20120402154903.GX21938%40mars-attacks.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="004376.html"> + <LINK REL="Next" HREF="004362.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] questions about our infrastructure setup & costs</H1> + <B>nicolas vigier</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20questions%20about%20our%20infrastructure%20setup%20%26%09costs&In-Reply-To=%3C20120402154903.GX21938%40mars-attacks.org%3E" + TITLE="[Mageia-sysadm] questions about our infrastructure setup & costs">boklm at mars-attacks.org + </A><BR> + <I>Mon Apr 2 17:49:03 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="004376.html">[Mageia-sysadm] questions about our infrastructure setup & costs +</A></li> + <LI>Next message: <A HREF="004362.html">[Mageia-sysadm] questions about our infrastructure setup & costs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#4358">[ date ]</a> + <a href="thread.html#4358">[ thread ]</a> + <a href="subject.html#4358">[ subject ]</a> + <a href="author.html#4358">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Mon, 02 Apr 2012, Romain d'Alverny wrote: + +><i> Hi, +</I>><i> +</I>><i> following past week-end incident, and I know that there are already +</I>><i> some reflexions and discussions about that, I'm posting the following +</I>><i> questions/needs, with my treasurer/board hat; some of these may +</I>><i> already have answers, so please just link me to them. +</I>><i> +</I>><i> It comes down to: +</I>><i> - board needs to have an up-to-date view of how much our +</I>><i> infrastructure costs, and would cost in different setups; and this, +</I>><i> split in separate, functional chunks; +</I>><i> - how can we change our setup to: 1) reduce the impact of having one +</I>><i> chunk (here a faulty RJ45 in Marseille) shut down so much of the +</I>><i> project for such a long time and 2) have a quick report, automatic +</I>><i> about this (not only for sysadmin, but for all users of our +</I>><i> infrastructure). +</I>><i> +</I>><i> So here is how I would put it: +</I>><i> +</I>><i> A. could you, as sysadmin, draw (graphically) the dependencies +</I>><i> between services, at a certain functional scale + their current +</I>><i> location/host; +</I>><i> * goal: have an overview of Mageia infrastructure, from the outside +</I>><i> of sysadmin team (and yes, again, that is needed); +</I>><i> * can we get it produced from the puppet conf? => the goal being +</I>><i> for now to have such a visual overview first, not to have it +</I>><i> automated. +</I>><i> * the function blocks I can think of would be (but add/split/fix +</I>><i> accordingly): +</I>><i> + core for communication & doc: +</I>><i> - user accounts (LDAP, identity.m.o) +</I>><i> - communications (mailing-lists, mail server) +</I>><i> - documentation (Wiki, Bugzilla) +</I>><i> - a specific code repository (not related to the build system) +</I>><i> for adm and/or one dedicated to organization (paperwork, reports, +</I>><i> constitution, etc.) +</I>><i> + Web hosts (www, blog, planet, forums, security notifs, etc.) +</I>><i> + core for building the distribution +</I>><i> - code repo +</I>><i> - buildsystem +</I>><i> - translation tools +</I>><i> - other? +</I>><i> + core for distribution software +</I>><i> - primary mirror +</I>><i> + other? +</I>><i> +</I>><i> B. based on these functional chunks, for each, could you: +</I>><i> * document what is needed for them: storage, bandwidth, what it +</I>><i> represent in full hardware today, what it should grow to. Goals are: +</I>><i> - to have a clear idea of how much it represents/costs: today, or +</I>><i> if we would move to other hosting solutions (paid or not, hardware or +</I>><i> virtual); +</I>><i> - to know how much we need to budget in security for these services; +</I>><i> - to know what our options (and needs) are for migrating some +</I>><i> services to an architecture or a paid solution that would improve +</I>><i> their availability (and accessibility in case of failure). +</I> +Using paid hosting will not remove problems like bad RJ45 or switch +that stop working. If we want good availability, we need more servers +in different places. + +I think it could help to have a few other servers in a different +datacenter, and duplicate services when it is easy to do (like ldap, +mirrors list, etc ...). In other cases like build system scheduler / +main mirror however, it's difficult to duplicate without conflicts +between the different servers, and cannot be done in a few minutes (or +hours), so I think we should migrate only in case of very long outage +(when we know that it will take more than a few days). Having a few +more servers available would help if we need to migrate some things in +case of big problem on one of the server. + +><i> C. various questions: +</I>><i> * could both above documentation (A and B) be maintained through changes; +</I>><i> * would it be possible to have the systems hosting our services to +</I>><i> have a prefix in their fqdn with the city/country they are located in? +</I>><i> Goal: being more explicit about where a service is located at this +</I>><i> time, so that a $ host www.mageia.org can answer me something like +</I>><i> champagne.paris.fr.mageia.org - for instance. I don't mean to change +</I>><i> all that, but I'm wondering about the opportunity. +</I> +I don't think having location of servers in the hostname is very useful. +It's not very difficult for someone interested to know the location of a +server. + +><i> * what do you think about maintaining a separate blog (for +</I>><i> opening/closing tickets + a global summary of what xymon provides +</I>><i> already) under status.mageia.org (or maybe a different domain, for +</I>><i> that matter)? (something similar to status.twitter.com) +</I> +We are already adding posts on official blog, and mails on mailling +list in case of problem, so what would be the use of an other separate +blog for this ? + +</PRE> + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="004376.html">[Mageia-sysadm] questions about our infrastructure setup & costs +</A></li> + <LI>Next message: <A HREF="004362.html">[Mageia-sysadm] questions about our infrastructure setup & costs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#4358">[ date ]</a> + <a href="thread.html#4358">[ thread ]</a> + <a href="subject.html#4358">[ subject ]</a> + <a href="author.html#4358">[ 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> |