summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/2010-October/000045.html
blob: 6916362936b76a0a5357236e1f6d75feddaf7b67 (plain)
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
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-sysadm] planning for sysadmin task
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20planning%20for%20sysadmin%20task&In-Reply-To=%3C1288004735.31779.27.camel%40akroma.ephaone.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="000044.html">
   <LINK REL="Next"  HREF="000056.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-sysadm] planning for sysadmin task</H1>
    <B>Michael Scherer</B> 
    <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20planning%20for%20sysadmin%20task&In-Reply-To=%3C1288004735.31779.27.camel%40akroma.ephaone.org%3E"
       TITLE="[Mageia-sysadm] planning for sysadmin task">misc at zarb.org
       </A><BR>
    <I>Mon Oct 25 13:05:35 CEST 2010</I>
    <P><UL>
        <LI>Previous message: <A HREF="000044.html">[Mageia-sysadm] planning for sysadmin task
</A></li>
        <LI>Next message: <A HREF="000056.html">[Mageia-sysadm] planning for sysadmin task
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#45">[ date ]</a>
              <a href="thread.html#45">[ thread ]</a>
              <a href="subject.html#45">[ subject ]</a>
              <a href="author.html#45">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Le lundi 25 octobre 2010 &#224; 10:24 +0100, Buchan Milne a &#233;crit :
&gt;<i> On Sunday, 24 October 2010 11:58:26 Olivier Thauvin wrote:
</I>&gt;<i> &gt; * Michael Scherer (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at zarb.org</A>) wrote:
</I>&gt;<i> &gt; &gt; Hi,
</I>&gt;<i> &gt; &gt; 
</I>&gt;<i> &gt; &gt; so now the server are in place, we have to install them. Here is a
</I>&gt;<i> &gt; &gt; proposal of the needed services :
</I>&gt;<i> &gt; &gt; 
</I>&gt;<i> &gt; &gt; Then we need to deploy the basic infrastructure for us. Again, I assume
</I>&gt;<i> &gt; &gt; that no one is against apache :
</I>&gt;<i> &gt; &gt; - ldap ( valstar or alamut ? )
</I>&gt;<i> 
</I>&gt;<i> At this stage, I am thinking that we may want 3 servers running LDAP:
</I>&gt;<i> -Master LDAP server, which is primarily not used by read-only clients. I 
</I>&gt;<i> haven't tested referrals yet in my app, so for now CatDap will probably need 
</I>&gt;<i> to use it. Could possibly be used as fall-back for either of the slaves
</I>&gt;<i> -1 slave used primarily for infrastructure support, but not exposed to much 
</I>&gt;<i> external traffic. Mostly nss_ldap/pam_ldap on build hosts, and any other 
</I>&gt;<i> infrastructure stuff which we decide to put in LDAP. If the total userbase is 
</I>&gt;<i> too large we could consider a partial replica (e.g. only posixAccount 
</I>&gt;<i> entries), though we may need to test this a bit ...
</I>&gt;<i> -1 slave used primarily for external traffic, e.g. forum, wiki etc. This could 
</I>&gt;<i> be the web server running some of these applications.
</I>&gt;<i> 
</I>&gt;<i> If this is excessive, we could consider combining master and internal read 
</I>&gt;<i> access on one server (but I would prefer to have at least one fall-back
</I>
For the moment, we have 5 servers, so for the beggining, it may indeed
be too much. So basically, ldap master on valstar ( ie, svn hdlist,
etc ) and external on alamut ?

And later, a ldap slave on the server used for forum ?

&gt;<i> &gt; May I suggest to setup all our web on same server, especially since a
</I>&gt;<i> &gt; lot use perl-Catalyst (buchan's one, epoll and the one I did to manage
</I>&gt;<i> &gt; mirror).
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; May I also suggest all our web be installed using RPM ?
</I>&gt;<i> &gt; Notice I got some issue using catalyst in fcgi mod, but it works fine in
</I>&gt;<i> &gt; server mode + apache as proxy.
</I>&gt;<i> 
</I>&gt;<i> I will try and create a package today. I think all the dependencies should be 
</I>&gt;<i> available for Mdv2010.0 and up. However, if we want to have any contributions 
</I>&gt;<i> (skinning work from web team, localisations) with quick testing, it may be 
</I>&gt;<i> useful to run one instance from an svn checkout.
</I>
Ie, have a production instance and a devel instance ?

Nothing prevent us from doing rpm from svn snapshot at regular interval
too.

&gt;<i> BTW., do we want to run these apps on separate virtual hosts? Should I ship 
</I>&gt;<i> vhost definition in apache config (e.g. for identity.mageia.org)?
</I>
I would say &quot;yes&quot;

&gt;<i> &gt; &gt; - create account for us.
</I>&gt;<i> 
</I>&gt;<i> Set up host authentication to LDAP first? We will need SSL certificates for 
</I>&gt;<i> LDAP hosts as well. Self-signed certs or certs from self-signed CA are fine.
</I>
Ok.

&gt;<i> &gt; Yup, especially if we have to work on them :)
</I>&gt;<i> 
</I>&gt;<i> I have created some accounts in LDAP, and I am happy to create any we need to 
</I>&gt;<i> proceed to the point where the account registration portion of CatDap is 
</I>&gt;<i> running. However, I think we may want to get internal use of it (for 
</I>&gt;<i> registration) before opening the gates ...
</I>&gt;<i> 
</I>&gt;<i> Also, I probably need to start work on the admin features, for now I am 
</I>&gt;<i> planning:
</I>&gt;<i> -user modification (e.g. add posixAccount to existing user account, modify any 
</I>&gt;<i> attributes necessary manually, 
</I>&gt;<i> -group management (add groups, modify group membership etc.)
</I>&gt;<i> 
</I>&gt;<i> Please let me know what other features are important sooner than later.
</I>
ssh keys support ( as I think we will use it for us ) ? After a second
tought, we can do it by hand, 

I also think notification of subscription could be interesting, but
again, we may not need it now.

&gt;<i> &gt; &gt; then the rest is less prioritary :
</I>&gt;<i> &gt; &gt; - postfix ( alamut )
</I>&gt;<i> &gt; &gt; - migrate to sympa ( alamut )
</I>&gt;<i> &gt; &gt; - enter everybody in the ldap
</I>&gt;<i> &gt; &gt; - nagios/munin ( or similar ) ( alamut )
</I>&gt;<i> 
</I>&gt;<i> xymon?
</I>
yup, why, as long it is packaged, i am ok.


-- 
Michael Scherer

</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="000044.html">[Mageia-sysadm] planning for sysadmin task
</A></li>
	<LI>Next message: <A HREF="000056.html">[Mageia-sysadm] planning for sysadmin task
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#45">[ date ]</a>
              <a href="thread.html#45">[ thread ]</a>
              <a href="subject.html#45">[ subject ]</a>
              <a href="author.html#45">[ 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>