[debian-edu-commits] [Debian Wiki] Update of "DebianEdu/Documentation/en/ITIL/Delivery" by PetterReinholdtsen

[Debian Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.

The "DebianEdu/Documentation/en/ITIL/Delivery" page has been changed by PetterReinholdtsen:
https://wiki.debian.org/DebianEdu/Documentation/en/ITIL/Delivery?action=diff&rev1=10&rev2=11

  
  Here is a list of commonly encountered bottlenecks and what to do to get rid of them:
  
+ ||'''Bottlenecks'''||'''Actions'''||
+ ||Missing sound, USB stick support and DVD on thin clients.||Install diskless workstations (> 800 MHz processor, > 256 MB RAM)||
+ ||Has 60 thin clients connected to the server and want more PCs.||Go for diskless clients, or install another a thin client server||
+ ||Thin clients runs slowly after we expanded with 20 pieces without acquiring a new server machine||Install 2GB more memory on the server machine||
+ ||Thin clients with 32MB memory does not start after upgrading to Skolelinux 2.0||Turn on cache (swap) of the thin clients, or downgrade to LTSP 4.2 which is set up with swap.||
- <table>
- <tbody>
- <tr class="odd">
- <td align="left">'''Bottlenecks'''
- </td>
- <td align="left">'''Actions'''
- </td>
- </tr>
- <tr class="even">
- <td align="left">Missing sound, USB stick support and DVD on thin clients.
- </td>
- <td align="left">Install diskless workstations (> 800 MHz processor, > 256 MB RAM)
- </td>
- </tr>
- <tr class="odd">
- <td align="left">Has 60 thin clients connected to the server and want more PCs.
- </td>
- <td align="left">Go for diskless clients, or install another a thin client server
- </td>
- </tr>
- <tr class="even">
- <td align="left">Thin clients runs slowly after we expanded with 20 pieces without acquiring a new server machine
- </td>
- <td align="left">Install 2GB more memory on the server machine
- </td>
- </tr>
- <tr class="odd">
- <td align="left">Thin clients with 32MB memory does not start after upgrading to Skolelinux 2.0
- </td>
- <td align="left">Turn on cache (swap) of the thin clients, or downgrade to LTSP 4.2 which is set up with swap.
- </td>
- </tr>
- <tr class="even">
- <td align="left">Flash animations make the thin clients slow when 50 students are logged into the same server machine
+ ||Flash animations make the thin clients slow when 50 students are logged into the same server machine||Install diskless clients||
- </td>
- <td align="left">Install diskless clients
- </td>
- </tr>
- </tbody>
- </table>
  
  === Implementation ===
  
@@ -284, +250 @@

  
  Availability can be measured using several methods. Here are some examples:
  
+ ||'''Value'''||'''Meaning'''||
- <table>
- <tbody>
- <tr class="odd">
- <td align="left">'''Value'''
- </td>
- <td align="left">'''Meaning'''
- </td>
- </tr>
- <tr class="even">
- <td align="left">% available
- </td>
- <td align="left">The value can be availability between hours 08:00 and 18:00. If the system is down 1 hours during one day, than the system is available in 90% of the agreed upon time. If availability is measured over a month with 20 work days, then the system is available 95% of the time.
+ ||% available||The value can be availability between hours 08:00 and 18:00. If the system is down 1 hours during one day, than the system is available in 90% of the agreed upon time. If availability is measured over a month with 20 work days, then the system is available 95% of the time.||
- </td>
- </tr>
- <tr class="odd">
- <td align="left">% unavailable
- </td>
- <td align="left">Is the system down one hour during an agreed uptime, for example 10 hours a day, the system is unavailable in 10% of the time. Measured over 20 days, we may assume the system has been unavailable for 5% of the time.
+ ||% unavailable||Is the system down one hour during an agreed uptime, for example 10 hours a day, the system is unavailable in 10% of the time. Measured over 20 days, we may assume the system has been unavailable for 5% of the time.||
- </td>
- </tr>
- <tr class="even">
- <td align="left">Hours unavailable
- </td>
- <td align="left">One can agree to the number of times one accepts the system is unavailable during, for example within one month (20 days). It can be a maximum of one hour halt in the period, and between 08:00 until 18:00.
+ ||Hours unavailable||One can agree to the number of times one accepts the system is unavailable during, for example within one month (20 days). It can be a maximum of one hour halt in the period, and between 08:00 until 18:00.||
- </td>
- </tr>
- <tr class="odd">
- <td align="left">Error frequency
- </td>
- <td align="left">Even error rate can be measured per day or every month. 3 errors in the month and that the system is down between 08:00 until 18:00, is an example.
+ ||Error frequency||Even error rate can be measured per day or every month. 3 errors in the month and that the system is down between 08:00 until 18:00, is an example.||
- </td>
- </tr>
- <tr class="even">
- <td align="left">Consequences of errors
- </td>
- <td align="left">Measured values are a common starting point for judging whether an error to have consequences beyond ordinary error correction. The customer or the school for example, may ask to pay less for the operating agreement for the current month.
+ ||Consequences of errors||Measured values are a common starting point for judging whether an error to have consequences beyond ordinary error correction. The customer or the school for example, may ask to pay less for the operating agreement for the current month.||
- </td>
- </tr>
- </tbody>
- </table>
  
  The most important is that your measure describes the user experience in the best possible way. Therefore, one should measure what is important for the user.