blog/tags/sitesummary/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen: Entries Tagged sitesummary</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="sitesummary.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21     <h3>Entries tagged "sitesummary".</h3>
  22
  23     <div class="entry">
  24       <div class="title">
  25         <a href="http://people.skolelinux.org/pere/blog/Automatic_Munin_and_Nagios_configuration.html">Automatic Munin and Nagios configuration</a>
  26       </div>
  27       <div class="date">
  28         27th January 2010
  29       </div>
  30       <div class="body">
  31         <p>One of the new features in the next Debian/Lenny based release of
  32 Debian Edu/Skolelinux, which is scheduled for release in the next few
  33 days, is automatic configuration of the service monitoring system
  34 Nagios.  The previous release had automatic configuration of trend
  35 analysis using Munin, and this Lenny based release take that a step
  36 further.</p>
  37
  38 <p>When installing a Debian Edu Main-server, it is automatically
  39 configured as a Munin and Nagios server.  In addition, it is
  40 configured to be a server for the
  41 <a href="http://wiki.debian.org/DebianEdu/HowTo/SiteSummary">SiteSummary
  42 system</a> I have written for use in Debian Edu.  The SiteSummary
  43 system is inspired by a system used by the University of Oslo where I
  44 work.  In short, the system provide a centralised collector of
  45 information about the computers on the network, and a client on each
  46 computer submitting information to this collector.  This allow for
  47 automatic information on which packages are installed on each machine,
  48 which kernel the machines are using, what kind of configuration the
  49 packages got etc.  This also allow us to automatically generate Munin
  50 and Nagios configuration.</p>
  51
  52 <p>All computers reporting to the sitesummary collector with the
  53 munin-node package installed is automatically enabled as a Munin
  54 client and graphs from the statistics collected from that machine show
  55 up automatically on http://www/munin/ on the Main-server.</p>
  56
  57 <p>All non-laptop computers reporting to the sitesummary collector are
  58 automatically monitored for network presence (ping and any network
  59 services detected).  In addition, all computers (also laptops) with
  60 the nagios-nrpe-server package installed and configured the way
  61 sitesummary would configure it, are monitored for full disks, software
  62 raid status, swap free and other checks that need to run locally on
  63 the machine.</p>
  64
  65 <p>The result is that the administrator on a school using Debian Edu
  66 based on Lenny will be able to check the health of his installation
  67 with one look at the Nagios settings, without having to spend any time
  68 keeping the Nagios configuration up-to-date.</p>
  69
  70 <p>The only configuration one need to do to get Nagios up and running
  71 is to set the password used to get access via HTTP.  The system
  72 administrator need to run "<tt>htpasswd /etc/nagios3/htpasswd.users
  73 nagiosadmin</tt>" to create a nagiosadmin user and set a password for
  74 it to be able to log into the Nagios web pages.  After that,
  75 everything is taken care of.</p>
  76
  77       </div>
  78       <div class="tags">
  79
  80
  81         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary</a>.
  82
  83
  84       </div>
  85     </div>
  86     <div class="padding"></div>
  87
  88     <div class="entry">
  89       <div class="title">
  90         <a href="http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html">Sitesummary tip: Listing MAC address of all clients</a>
  91       </div>
  92       <div class="date">
  93         14th May 2010
  94       </div>
  95       <div class="body">
  96         <p>In the recent Debian Edu versions, the
  97 <a href="http://wiki.debian.org/DebianEdu/HowTo/SiteSummary">sitesummary
  98 system</a> is used to keep track of the machines in the school
  99 network.  Each machine will automatically report its status to the
 100 central server after boot and once per night.  The network setup is
 101 also reported, and using this information it is possible to get the
 102 MAC address of all network interfaces in the machines.  This is useful
 103 to update the DHCP configuration.</p>
 104
 105 <p>To give some idea how to use sitesummary, here is a one-liner to
 106 ist all MAC addresses of all machines reporting to sitesummary.  Run
 107 this on the collector host:</p>
 108
 109 <blockquote><pre>
 110 perl -MSiteSummary -e 'for_all_hosts(sub { print join(" ", get_macaddresses(shift)), "\n"; });'
 111 </pre></blockquote>
 112
 113 <p>This will list all MAC addresses assosiated with all machine, one
 114 line per machine and with space between the MAC addresses.</p>
 115
 116 <p>To allow system administrators easier job at adding static DHCP
 117 addresses for hosts, it would be possible to extend this to fetch
 118 machine information from sitesummary and update the DHCP and DNS
 119 tables in LDAP using this information.  Such tool is unfortunately not
 120 written yet.</p>
 121
 122       </div>
 123       <div class="tags">
 124
 125
 126         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary</a>.
 127
 128
 129       </div>
 130     </div>
 131     <div class="padding"></div>
 132
 133     <div class="entry">
 134       <div class="title">
 135         <a href="http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html">Sitesummary tip: Listing computer hardware models used at site</a>
 136       </div>
 137       <div class="date">
 138          3rd June 2010
 139       </div>
 140       <div class="body">
 141         <p>When using sitesummary at a site to track machines, it is possible
 142 to get a list of the machine types in use thanks to the DMI
 143 information extracted from each machine.  The script to do so is
 144 included in the sitesummary package, and here is example output from
 145 the Skolelinux build servers:</p>
 146
 147 <blockquote><pre>
 148 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
 149   vendor                    count
 150   Dell Computer Corporation     1
 151     PowerEdge 1750              1
 152   IBM                           1
 153     eserver xSeries 345 -[8670M1X]-     1
 154   Intel                         2
 155   [no-dmi-info]                 3
 156 maintainer:~#
 157 </pre></blockquote>
 158
 159 <p>The quality of the report depend on the quality of the DMI tables
 160 provided in each machine.  Here there are Intel machines without model
 161 information listed with Intel as vendor and no model, and virtual Xen
 162 machines listed as [no-dmi-info].  One can add -l as a command line
 163 option to list the individual machines.</p>
 164
 165 <p>A larger list is
 166 <a href="http://narvikskolen.no/sitesummary/">available from the the
 167 city of Narvik</a>, which uses Skolelinux on all their shools and also
 168 provide the basic sitesummary report publicly.  In their report there
 169 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
 170 their machines, and as sitesummary is available in both distributions,
 171 it is trivial to get all of them to report to the same central
 172 collector.</p>
 173
 174       </div>
 175       <div class="tags">
 176
 177
 178         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary</a>.
 179
 180
 181       </div>
 182     </div>
 183     <div class="padding"></div>
 184
 185     <div class="entry">
 186       <div class="title">
 187         <a href="http://people.skolelinux.org/pere/blog/Setting_up_a_new_school_with_Debian_Edu_Squeeze.html">Setting up a new school with Debian Edu/Squeeze</a>
 188       </div>
 189       <div class="date">
 190         25th January 2012
 191       </div>
 192       <div class="body">
 193         <p>The next version of <a href="http://www.skolelinux.org/">Debian Edu
 194 / Skolelinux</a> will include a new tool
 195 <tt>sitesummary2ldapdhcp</tt>, which can be used to quickly set up all
 196 the computers in a school without much manual labour.  Here is a short
 197 summary on how to use it to set up a new school.</p>
 198
 199 <p>First, install a combined Main Server and Thin Client Server as the
 200 central server in the network.  Next, PXE boot all the client machines
 201 as thin clients and wait 5 minutes after the last client booted to
 202 allow the clients to report their existence to the central server.  When
 203 this is done, log on to the central server and run
 204 <tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
 205 collected information to generate system objects in LDAP.  The output
 206 will look similar to this:</p>
 207
 208 <p><blockquote><pre>
 209 % sitesummary2ldapdhcp -a
 210 info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
 211 info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
 212
 213 Enter password if you want to activate these changes, and ^c to abort.
 214
 215 Connecting to LDAP as cn=admin,ou=ldap-access,dc=skole,dc=skolelinux,dc=no
 216 enter password: *******
 217 %
 218 </pre></blockquote></p>
 219
 220 <p>After providing the LDAP administrative password (the same as the
 221 root password set during installation), the LDAP database will be
 222 populated with system objects for each PXE booted machine with
 223 automatically generated names.  The final step to set up the school is
 224 then to log into <a href="https://oss.gonicus.de/labs/gosa/">GOsa</a>,
 225 the web based user, group and system administration system to change
 226 system names, add systems to the correct host groups and finally
 227 enable DHCP and DNS for the systems.  All clients that should be used
 228 as diskless workstations should be added to the workstation-hosts
 229 group.  After this is done, all computers can be booted again via PXE
 230 and get their assigned names and group based configuration
 231 automatically.</p>
 232
 233 <p>We plan to release beta3 with the updated version of this feature
 234 enabled this weekend.  You might want to give it a try.</p>
 235
 236 <p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
 237 hosts, one need to add the option -a.  I forgot to mention this in my
 238 original text, and have added it to the text now.</p>
 239
 240       </div>
 241       <div class="tags">
 242
 243
 244         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary</a>.
 245
 246
 247       </div>
 248     </div>
 249     <div class="padding"></div>
 250
 251     <p style="text-align: right;"><a href="sitesummary.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
 252     <div id="sidebar">
 253
 254
 255
 256 <h2>Archive</h2>
 257 <ul>
 258
 259 <li>2012
 260 <ul>
 261
 262 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 263
 264 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 265
 266 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 267
 268 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 269
 270 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 271
 272 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (17)</a></li>
 273
 274 </ul></li>
 275
 276 <li>2011
 277 <ul>
 278
 279 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 280
 281 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 282
 283 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 284
 285 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 286
 287 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 288
 289 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 290
 291 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 292
 293 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 294
 295 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 296
 297 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 298
 299 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 300
 301 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 302
 303 </ul></li>
 304
 305 <li>2010
 306 <ul>
 307
 308 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 309
 310 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 311
 312 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 313
 314 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 315
 316 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 317
 318 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 319
 320 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 321
 322 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 323
 324 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 325
 326 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 327
 328 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 329
 330 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 331
 332 </ul></li>
 333
 334 <li>2009
 335 <ul>
 336
 337 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 338
 339 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 340
 341 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 342
 343 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 344
 345 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 346
 347 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 348
 349 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 350
 351 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 352
 353 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 354
 355 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 356
 357 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 358
 359 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 360
 361 </ul></li>
 362
 363 <li>2008
 364 <ul>
 365
 366 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 367
 368 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
 369
 370 </ul></li>
 371
 372 </ul>
 373
 374
 375
 376 <h2>Tags</h2>
 377 <ul>
 378
 379  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
 380
 381  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
 382
 383  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
 384
 385  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (2)</a></li>
 386
 387  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (12)</a></li>
 388
 389  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
 390
 391  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (55)</a></li>
 392
 393  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (105)</a></li>
 394
 395  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (9)</a></li>
 396
 397  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (3)</a></li>
 398
 399  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (137)</a></li>
 400
 401  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (16)</a></li>
 402
 403  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
 404
 405  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (28)</a></li>
 406
 407  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (16)</a></li>
 408
 409  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
 410
 411  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (4)</a></li>
 412
 413  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
 414
 415  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (20)</a></li>
 416
 417  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (177)</a></li>
 418
 419  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (132)</a></li>
 420
 421  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (3)</a></li>
 422
 423  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
 424
 425  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (29)</a></li>
 426
 427  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (48)</a></li>
 428
 429  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
 430
 431  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
 432
 433  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
 434
 435  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (4)</a></li>
 436
 437  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
 438
 439  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
 440
 441  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (1)</a></li>
 442
 443  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (23)</a></li>
 444
 445  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
 446
 447  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (32)</a></li>
 448
 449  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
 450
 451  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (4)</a></li>
 452
 453  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (10)</a></li>
 454
 455  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (6)</a></li>
 456
 457  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (28)</a></li>
 458
 459  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (1)</a></li>
 460
 461  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (23)</a></li>
 462
 463 </ul>
 464
 465
 466     </div>
 467     <p style="text-align: right">
 468  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.4</a>
 469 </p>
 470
 471   </body>
 472 </html>