1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
|
<!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=%3CCANa9xwtnUoLrY2pdgHVgSoX1jKAFn20NgL3cKT9O63s0-DxRqw%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="004355.html">
<LINK REL="Next" HREF="004357.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] questions about our infrastructure setup & costs</H1>
<B>Romain d'Alverny</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=%3CCANa9xwtnUoLrY2pdgHVgSoX1jKAFn20NgL3cKT9O63s0-DxRqw%40mail.gmail.com%3E"
TITLE="[Mageia-sysadm] questions about our infrastructure setup & costs">rdalverny at gmail.com
</A><BR>
<I>Mon Apr 2 15:23:25 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="004355.html">[Mageia-sysadm] Fwd: [Mageia-discuss] (no subject)
</A></li>
<LI>Next message: <A HREF="004357.html">[Mageia-sysadm] questions about our infrastructure setup & costs
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4356">[ date ]</a>
<a href="thread.html#4356">[ thread ]</a>
<a href="subject.html#4356">[ subject ]</a>
<a href="author.html#4356">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hi,
following past week-end incident, and I know that there are already
some reflexions and discussions about that, I'm posting the following
questions/needs, with my treasurer/board hat; some of these may
already have answers, so please just link me to them.
It comes down to:
- board needs to have an up-to-date view of how much our
infrastructure costs, and would cost in different setups; and this,
split in separate, functional chunks;
- how can we change our setup to: 1) reduce the impact of having one
chunk (here a faulty RJ45 in Marseille) shut down so much of the
project for such a long time and 2) have a quick report, automatic
about this (not only for sysadmin, but for all users of our
infrastructure).
So here is how I would put it:
A. could you, as sysadmin, draw (graphically) the dependencies
between services, at a certain functional scale + their current
location/host;
* goal: have an overview of Mageia infrastructure, from the outside
of sysadmin team (and yes, again, that is needed);
* can we get it produced from the puppet conf? => the goal being
for now to have such a visual overview first, not to have it
automated.
* the function blocks I can think of would be (but add/split/fix
accordingly):
+ core for communication & doc:
- user accounts (LDAP, identity.m.o)
- communications (mailing-lists, mail server)
- documentation (Wiki, Bugzilla)
- a specific code repository (not related to the build system)
for adm and/or one dedicated to organization (paperwork, reports,
constitution, etc.)
+ Web hosts (www, blog, planet, forums, security notifs, etc.)
+ core for building the distribution
- code repo
- buildsystem
- translation tools
- other?
+ core for distribution software
- primary mirror
+ other?
B. based on these functional chunks, for each, could you:
* document what is needed for them: storage, bandwidth, what it
represent in full hardware today, what it should grow to. Goals are:
- to have a clear idea of how much it represents/costs: today, or
if we would move to other hosting solutions (paid or not, hardware or
virtual);
- to know how much we need to budget in security for these services;
- to know what our options (and needs) are for migrating some
services to an architecture or a paid solution that would improve
their availability (and accessibility in case of failure).
C. various questions:
* could both above documentation (A and B) be maintained through changes;
* would it be possible to have the systems hosting our services to
have a prefix in their fqdn with the city/country they are located in?
Goal: being more explicit about where a service is located at this
time, so that a $ host www.mageia.org can answer me something like
champagne.paris.fr.mageia.org - for instance. I don't mean to change
all that, but I'm wondering about the opportunity.
* what do you think about maintaining a separate blog (for
opening/closing tickets + a global summary of what xymon provides
already) under status.mageia.org (or maybe a different domain, for
that matter)? (something similar to status.twitter.com)
Thanks!
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="004355.html">[Mageia-sysadm] Fwd: [Mageia-discuss] (no subject)
</A></li>
<LI>Next message: <A HREF="004357.html">[Mageia-sysadm] questions about our infrastructure setup & costs
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4356">[ date ]</a>
<a href="thread.html#4356">[ thread ]</a>
<a href="subject.html#4356">[ subject ]</a>
<a href="author.html#4356">[ 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>
|
