# wiki

name: WikiStart
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Atelier de Gestion et de Supervision des Réseaux (NM-F) =

  '''Dates:''' 25-29 mai (Lundi-Vendredi), 2015
  [[BR]]
  '''Lieu:'''  Tunis (TUNISIE)
  [[BR]]
  '''Langue:''' Français. 
  [[BR]]
  '''Langues des instructeurs:''' Français


  == Objectifs de l'atelier ==

  Cet atelier de 5 jours introduit les concepts de bases et les composantes nécessaires à la gestion et supervision efficace des réseaux IP, en apprenant l'utilisation d'outils avancés, et de pratiques établies (Best Practices).

  Faisant partie de la conférence/rencontres AIS 2015, le public visé sont les ingénieurs et administrateurs systèmes et réseau des FAI et autres moyens et grands réseaux, y compris les réseaux académiques, qui sont amenés à devoir gérer et superviser leurs réseaux et systèmes, y compris la correction des problèmes. Voir l'Agenda pour la liste des sujets abordés.


  == Prérequis ==

    * Un ordinateur portable avec Wifi
    * Connaissance préalable des concepts de base et de l'administration des réseaux IP
    * Connaissance préalable de l'utilisation des systèmes UNIX/Linux et de la ligne de command (CLI)

  == Éléments de l'atelier ==

   * [wiki:Agenda Emploi du temps]
   * [raw-attachment:NMF_participants.pdf Liste des participants]

   * Merci au NSRC qui a fournit le kit et tous les supports (formation, wiki)

   [http://nsrc.org/ NSRC] [[Image(nsrc-logo.png)]]

   * Merci à l'AFNIC qui a financé la traduction des supports de cours 

   [http://www.afnic.fr/ AFNIC] [[Image(https://nsrc.org/workshops/2011/dakar-gestion-supervision-reseau/chrome/site/Afnic.gif)]]

  == Outils ==

  * [raw-attachment:putty.exe PuTTY]

  == Network Operations Center (NOC) ==

   * [raw-attachment:diagram.png Topologie Reseau]
   * Espace [wiki:NOC]
   * Références [wiki:References]
   *[https://noc.ws.nsrc.org/configs/ Fichiers de Configuration]
   * [https://noc.ws.nsrc.org/downloads/ Logiciles]
    
   * [http://noc.ws.nsrc.org/cacti Cacti]
    * Utilisateur: guest Mot de passe: guest
    * Utilisateur: admin password: celui de la classe
   * MRTG
   * [http://noc.ws.nsrc.org/nagios3 Nagios]
    * Connectez vous avec l'utilisateur guest et le mot de passe guest
    * [wiki:NagiosDiag Nagios Network Diagram]
   * [http://noc.ws.nsrc.org/nfsen/nfsen.php NfSen]
   * Request Tracker
    * Connectez vous avec l'utilisateur sysadm et le mot de passe est celui de la classe
   * [http://noc.ws.nsrc.org/cgi-bin/14all.cgi/ RRDTool]
    * Traffic sur les interfaces des routeurs de la classe
   * [http://noc.ws.nsrc.org/cgi-bin/smokeping.cgi Smokeping]
   * WebSVN (RANCID router configs)


  == Autres Supports ==

   * TracGuide --  Documentation
   * TitleIndex -- Liste Complete des autres pages Wiki en local
   * [raw-attachment:joe-editor.pdf Editeur Joe]
   * [raw-attachment:vi-editor.pdf Editeur Vi]

  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||08:30 - 10:30 ||
  ||Pause     ||10:30 - 11:00 ||
  ||Session 2 ||11:00 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [https://afnog.org/ AfNOG]  || Togo/France ||
  ||'''FB'''||Fanta Bouba  ||    [http://nsrc.org/ NSRC]  || Tchad/Sénégal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.htm HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||                 ||Cacti                                        || DA ||  ||    ||[http://www.cacti.net/ Cacti]||   
  ||Session II   ||Contrôle de Versions et configuration: RANCID || FB ||  ||      ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||Smokeping                                     || DA ||                       ||   ||[http://oss.oetiker.ch/smokeping/ SmokePing]|| 
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session II      ||Nagios                                      || FB ||       ||   ||[http://www.nagios.org/ Nagios]||
  ||Session III     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||Session IV      ||Gestion des journaux (Log)                || JH ||  ||   ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Ticketing Systems (Request Tracker)            || FB ||   ||     ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session II    || Observium - Demo  || DA  ||    ||   ||
  ||Session III     ||!NetFlow et NFSen                            || JH ||  ||         ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||Session IV    ||!NetFlow et NFSen (suite)                    ||JH ||   ||       ||          || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||08:30 - 10:30 ||
  ||Pause     ||10:30 - 11:00 ||
  ||Session 2 ||11:00 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [https://afnog.org/ AfNOG]  || Togo/France ||
  ||'''FB'''||Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/Sénégal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.htm HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||                 ||Cacti                                        || DA ||  ||    ||[http://www.cacti.net/ Cacti]||   
  ||Session II   ||Contrôle de Versions et configuration: RANCID || FB ||  ||      ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||Smokeping                                     || DA ||                       ||   ||[http://oss.oetiker.ch/smokeping/ SmokePing]|| 
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session II      ||Nagios                                      || FB ||       ||   ||[http://www.nagios.org/ Nagios]||
  ||Session III     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||Session IV      ||Gestion des journaux (Log)                || JH ||  ||   ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Ticketing Systems (Request Tracker)            || FB ||   ||     ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session II    || Observium - Demo  || DA  ||    ||   ||
  ||Session III     ||!NetFlow et NFSen                            || JH ||  ||         ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||Session IV    ||!NetFlow et NFSen (suite)                    ||JH ||   ||       ||          || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||08:30 - 10:30 ||
  ||Pause     ||10:30 - 11:00 ||
  ||Session 2 ||11:00 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [https://afnog.org/ AfNOG]  || Togo/France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.htm HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||                 ||Cacti                                        || DA ||  ||    ||[http://www.cacti.net/ Cacti]||   
  ||Session II   ||Contrôle de Versions et configuration: RANCID || FB ||  ||      ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||Smokeping                                     || DA ||                       ||   ||[http://oss.oetiker.ch/smokeping/ SmokePing]|| 
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session II      ||Nagios                                      || FB ||       ||   ||[http://www.nagios.org/ Nagios]||
  ||Session III     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||Session IV      ||Gestion des journaux (Log)                || JH ||  ||   ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Ticketing Systems (Request Tracker)            || FB ||   ||     ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session II    || Observium - Demo  || DA  ||    ||   ||
  ||Session III     ||!NetFlow et NFSen                            || JH ||  ||         ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||Session IV    ||!NetFlow et NFSen (suite)                    ||JH ||   ||       ||          || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||08:30 - 10:30 ||
  ||Pause     ||10:30 - 11:00 ||
  ||Session 2 ||11:00 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.htm HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||                 ||Cacti                                        || DA ||  ||    ||[http://www.cacti.net/ Cacti]||   
  ||Session II   ||Contrôle de Versions et configuration: RANCID || FB ||  ||      ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||Smokeping                                     || DA ||                       ||   ||[http://oss.oetiker.ch/smokeping/ SmokePing]|| 
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session II      ||Nagios                                      || FB ||       ||   ||[http://www.nagios.org/ Nagios]||
  ||Session III     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||Session IV      ||Gestion des journaux (Log)                || JH ||  ||   ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Ticketing Systems (Request Tracker)            || FB ||   ||     ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session II    || Observium - Demo  || DA  ||    ||   ||
  ||Session III     ||!NetFlow et NFSen                            || JH ||  ||         ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||Session IV    ||!NetFlow et NFSen (suite)                    ||JH ||   ||       ||          || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.htm HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||                 ||Cacti                                        || DA ||  ||    ||[http://www.cacti.net/ Cacti]||   
  ||Session II   ||Contrôle de Versions et configuration: RANCID || FB ||  ||      ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||Smokeping                                     || DA ||                       ||   ||[http://oss.oetiker.ch/smokeping/ SmokePing]|| 
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session II      ||Nagios                                      || FB ||       ||   ||[http://www.nagios.org/ Nagios]||
  ||Session III     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||Session IV      ||Gestion des journaux (Log)                || JH ||  ||   ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Ticketing Systems (Request Tracker)            || FB ||   ||     ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session II    || Observium - Demo  || DA  ||    ||   ||
  ||Session III     ||!NetFlow et NFSen                            || JH ||  ||         ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||Session IV    ||!NetFlow et NFSen (suite)                    ||JH ||   ||       ||          || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.htm HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II   ||Cacti                                        || DA ||  ||    ||[http://www.cacti.net/ Cacti]||   
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||Smokeping                                     || DA ||                       ||   ||[http://oss.oetiker.ch/smokeping/ SmokePing]|| 
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session II      ||Nagios                                      || FB ||       ||   ||[http://www.nagios.org/ Nagios]||
  ||Session III     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||Session IV      ||Gestion des journaux (Log)                || JH ||  ||   ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Ticketing Systems (Request Tracker)            || FB ||   ||     ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session II    || Observium - Demo  || DA  ||    ||   ||
  ||Session III     ||!NetFlow et NFSen                            || JH ||  ||         ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||Session IV    ||!NetFlow et NFSen (suite)                    ||JH ||   ||       ||          || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.htm HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session II      ||Nagios                                      || FB ||       ||   ||[http://www.nagios.org/ Nagios]||
  ||Session III     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||Session IV      ||Gestion des journaux (Log)                || JH ||  ||   ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Ticketing Systems (Request Tracker)            || FB ||   ||     ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session II    || Observium - Demo  || DA  ||    ||   ||
  ||Session III     ||!NetFlow et NFSen                            || JH ||  ||         ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||Session IV    ||!NetFlow et NFSen (suite)                    ||JH ||   ||       ||          || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session II      ||Nagios                                      || FB ||       ||   ||[http://www.nagios.org/ Nagios]||
  ||Session III     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||Session IV      ||Gestion des journaux (Log)                || JH ||  ||   ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Ticketing Systems (Request Tracker)            || FB ||   ||     ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session II    || Observium - Demo  || DA  ||    ||   ||
  ||Session III     ||!NetFlow et NFSen                            || JH ||  ||         ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||Session IV    ||!NetFlow et NFSen (suite)                    ||JH ||   ||       ||          || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||                ||                                            ||  ||                      ||                ||                               ||
  |||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session II      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session III     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||Session IV      ||Gestion des journaux (Log)                || JH || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Ticketing Systems (Request Tracker)            || FB ||   ||     ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session II    || Observium - Demo  || DA  ||    ||   ||
  ||Session III     ||!NetFlow et NFSen                            || JH ||  ||         ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||Session IV    ||!NetFlow et NFSen (suite)                    ||JH ||   ||       ||          || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  |||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Gestion des journaux (Log)                || JH || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II    ||Ticketing Systems (Request Tracker)            || FB ||   ||     ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session III    || Observium - Demo  || DA  ||    ||   ||
  ||Session IV     ||!NetFlow et NFSen                            || JH ||  ||         ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  |||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Gestion des journaux (Log)                || JH ||         ||               ||                               ||
  ||Session II    ||Ticketing Systems (Request Tracker)            || FB ||   ||     ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session III    || Observium - Demo  || DA  ||    ||   ||
  ||Session IV     ||!NetFlow et NFSen                            || JH ||  ||         ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  |||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Gestion des journaux (Log)               || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2] 
  ||Session II    ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt.en.pdf PDF-2]   ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session III    || Observium - Demo  || DA  ||  [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||Session IV     ||!NetFlow et NFSen                            || JH || [raw-attachment:netflow.pdf NetFlow]  || [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]              ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  |||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Gestion des journaux (Log)               || JH || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II    ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt.en.pdf PDF-2]   ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session III    || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||Session IV     ||!NetFlow et NFSen|| JH || [raw-attachment:netflow.pdf NetFlow]  || [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]              ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  |||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Gestion des journaux (Log)               || JH || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II    ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2]   ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session III    || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||Session IV     ||!NetFlow et NFSen|| JH || [raw-attachment:netflow.pdf NetFlow]  || [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]              ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  |||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Gestion des journaux (Log)               || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II    ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2]   ||[http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session III    || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||Session IV     ||!NetFlow et NFSen|| DA || [raw-attachment:netflow.pdf NetFlow]  || [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]              ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  |||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Gestion des journaux (Log)               || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II    ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session III    || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||Session IV     ||!NetFlow et NFSen|| DA || [raw-attachment:netflow.pdf NetFlow]  || [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]              ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  |||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Gestion des journaux (Log)               || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II    ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session III    || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||Session IV     ||!NetFlow et NFSen|| DA || [raw-attachment:netflow.pdf NetFlow]  || [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]  |  [raw-attachment:exercise2-install-nfdump-nfsen-vFR.htm HTML-1] | [raw-attachment:exercise3-nfsen-top-talkers-vFR.htm HTML-2] | [raw-attachment:exercise4-using-NfSen-vFR.pdf PDF-3]             ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||DA ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évaluation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  |||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Gestion des journaux (Log)               || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II & III ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session IV || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||

  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I & II  ||!NetFlow et NFSen|| DA || [raw-attachment:netflow.pdf NetFlow]  || [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]  |  [raw-attachment:exercise2-install-nfdump-nfsen-vFR.htm HTML-2] | [raw-attachment:exercise3-nfsen-top-talkers-vFR.htm HTML-3] | [raw-attachment:exercise4-using-NfSen-vFR.pdf PDF-4]             ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évaluation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''     ||                                             ||  ||                      ||                ||                               ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Gestion des journaux (Log)               || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II & III ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session IV || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||

  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I & II  ||!NetFlow et NFSen|| DA || [raw-attachment:netflow.pdf NetFlow]  || [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]  |  [raw-attachment:exercise2-install-nfdump-nfsen-vFR.htm HTML-2] | [raw-attachment:exercise3-nfsen-top-talkers-vFR.htm HTML-3] | [raw-attachment:exercise4-using-NfSen-vFR.pdf PDF-4]             ||[http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]||
  ||Session III    ||Network Documentation (Netdot)                 || DA || ||   ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évaluation en ligne, Examen                               || || || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  ||||    ||  || 
  ||               ||Définitions et terminologie                  ||  ||  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I    ||Gestion des journaux (Log)       || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II & III ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session IV || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||

  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || [raw-attachment:network-documentation-and-netdot-vFR.pdf NetDot]  ||  [raw-attachment:exercises-netdot-vFR.pdf PDF-1]  ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || [https://nsrc.org/limesurvey/index.php/84193/lang-fr Evaluation] | [Examen] || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  || [raw-attachment:local-network-analysis-vFR.pdf PDF] || [raw-attachment:exercises-network-metrics-and-analysis-vFR.pdf PDF]   ||  || 
  ||               ||Définitions et terminologie                  ||  || [raw-attachment:network-performance-definitions-vFR.pdf PDF]  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I    ||Gestion des journaux (Log)       || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II & III ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session IV || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen (suite)    ||JH ||  ||       ||          || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || [raw-attachment:network-documentation-and-netdot-vFR.pdf NetDot]  ||  [raw-attachment:exercises-netdot-vFR.pdf PDF-1]  ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || [https://nsrc.org/limesurvey/index.php/84193/lang-fr Evaluation] | [Examen] || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  || [raw-attachment:local-network-analysis-vFR.pdf PDF] || [raw-attachment:exercises-network-metrics-and-analysis-vFR.pdf PDF]   ||  || 
  ||               ||Définitions et terminologie                  ||  || [raw-attachment:network-performance-definitions-vFR.pdf PDF]  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I    ||Gestion des journaux (Log)       || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II & III ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session IV || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I+II    ||!NetFlow et NFSen ||JH ||  [raw-attachment:netflow.pdf NetFlow] ||    [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]      ||    [http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow] [http://nfsen.sourceforge.net/ NfSen]      || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || [raw-attachment:network-documentation-and-netdot-vFR.pdf NetDot]  ||  [raw-attachment:exercises-netdot-vFR.pdf PDF-1]  ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || [https://nsrc.org/limesurvey/index.php/84193/lang-fr Evaluation] | [Examen] || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  || [raw-attachment:local-network-analysis-vFR.pdf PDF] || [raw-attachment:exercises-network-metrics-and-analysis-vFR.pdf PDF]   ||  || 
  ||               ||Définitions et terminologie                  ||  || [raw-attachment:network-performance-definitions-vFR.pdf PDF]  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I    ||Gestion des journaux (Log)       || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II & III ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session IV || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||!NetFlow ||JH ||  [raw-attachment:netflow.pdf PDF] ||    [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]      ||    [http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow]    || 
  ||Session II    ||!NFSEN ||JH ||  [raw-attachment:netflow.pdf PDF] ||    [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]      ||   [http://nfsen.sourceforge.net/ NfSen]      || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || [raw-attachment:network-documentation-and-netdot-vFR.pdf NetDot]  ||  [raw-attachment:exercises-netdot-vFR.pdf PDF-1]  ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || [https://nsrc.org/limesurvey/index.php/84193/lang-fr Evaluation] | [Examen] || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  || [raw-attachment:local-network-analysis-vFR.pdf PDF] || [raw-attachment:exercises-network-metrics-and-analysis-vFR.pdf PDF]   ||  || 
  ||               ||Définitions et terminologie                  ||  || [raw-attachment:network-performance-definitions-vFR.pdf PDF]  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I    ||Gestion des journaux (Log)       || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II & III ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session IV || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||!NetFlow ||JH ||  [raw-attachment:netflow.pdf PDF] ||    [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]      ||    [http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow]    || 
  ||Session II    ||!NFSEN ||JH || [raw-attachment:nfsen.pdf NfSen] ||   [raw-attachment:exercise2-install-nfdump-nfsen-vFR.htm HTML-1] | [raw-attachment:exercise3-nfsen-top-talkers-vFR.htm HTML-2] | [raw-attachment:exercise4-using-NfSen-vFR.pdf PDF-3]     ||   [http://nfsen.sourceforge.net/ NfSen]      || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || [raw-attachment:network-documentation-and-netdot-vFR.pdf NetDot]  ||  [raw-attachment:exercises-netdot-vFR.pdf PDF-1]  ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || [https://nsrc.org/limesurvey/index.php/84193/lang-fr Evaluation] | [Examen] || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  || [raw-attachment:local-network-analysis-vFR.pdf PDF] || [raw-attachment:exercises-network-metrics-and-analysis-vFR.pdf PDF]   ||  || 
  ||               ||Définitions et terminologie                  ||  || [raw-attachment:network-performance-definitions-vFR.pdf PDF]  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I    ||Gestion des journaux (Log)       || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II & III ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session IV || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||!NetFlow ||JH ||  [raw-attachment:netflow.pdf PDF] ||    [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]      ||    [http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow]    || 
  ||Session II    ||!NFSEN ||JH || [raw-attachment:nfsen.pdf NfSen] ||   [raw-attachment:exercise2-install-nfdump-nfsen-vFR.htm HTML-1] | [raw-attachment:exercise3-nfsen-top-talkers-vFR.htm HTML-2] | [raw-attachment:exercise4-using-NfSen-vFR.pdf PDF-3]     ||   [http://nfsen.sourceforge.net/ NfSen]      || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || [raw-attachment:network-documentation-and-netdot-vFR.pdf NetDot]  ||  [raw-attachment:exercises-netdot-vFR.pdf PDF-1]  ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || [ https://nsrc.org/limesurvey/index.php/491527/lang-fr Evaluation] || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  || [raw-attachment:local-network-analysis-vFR.pdf PDF] || [raw-attachment:exercises-network-metrics-and-analysis-vFR.pdf PDF]   ||  || 
  ||               ||Définitions et terminologie                  ||  || [raw-attachment:network-performance-definitions-vFR.pdf PDF]  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I    ||Gestion des journaux (Log)       || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II & III ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session IV || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||!NetFlow ||JH ||  [raw-attachment:netflow.pdf PDF] ||    [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]      ||    [http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow]    || 
  ||Session II    ||!NFSEN ||JH || [raw-attachment:nfsen.pdf NfSen] ||   [raw-attachment:exercise2-install-nfdump-nfsen-vFR.htm HTML-1] | [raw-attachment:exercise3-nfsen-top-talkers-vFR.htm HTML-2] | [raw-attachment:exercise4-using-NfSen-vFR.pdf PDF-3]     ||   [http://nfsen.sourceforge.net/ NfSen]      || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || [raw-attachment:network-documentation-and-netdot-vFR.pdf NetDot]  ||  [raw-attachment:exercises-netdot-vFR.pdf PDF-1]  ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évalutation en ligne, Examen                               || || [ https://nsrc.org/limesurvey/index.php/491527/lang-fr/ Evaluation] || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  || [raw-attachment:local-network-analysis-vFR.pdf PDF] || [raw-attachment:exercises-network-metrics-and-analysis-vFR.pdf PDF]   ||  || 
  ||               ||Définitions et terminologie                  ||  || [raw-attachment:network-performance-definitions-vFR.pdf PDF]  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: Agenda
author: fbouba
ipnr: 2607:8400:2880:4::80df:9d13
text:
  = Emploi du temps de l'atelier =

  '''Emploi du temps'''

  ||          ||              ||
  ||Session 1 ||09:00 - 11:00 ||
  ||Pause     ||11:00 - 11:30 ||
  ||Session 2 ||11:30 - 13:00 ||
  ||Déjeuner  ||13:00 - 14:00 ||
  ||Session 3 ||14:00 - 15:30 ||
  ||Pause     ||15:30 - 16:00 ||
  ||Session 4 ||16:00 - 17:30||
  ||          ||              ||

  '''Instructeurs'''
  [[br]]

  ||        ||                      ||                        ||          ||
  ||'''JH'''||Jean-Robert Hountomey  || [http://www.africacert.org/ Africa CERT]    || Togo/USA ||
  ||'''DA'''|| Danny Afahounko || [http://www.afnog.org/ AfNOG]  || Togo/ France  ||
  ||'''FB'''|| Fanta Bouba  || [http://nsrc.org/ NSRC]  || Tchad/ Senegal ||
  ||        ||                      ||                        ||          ||
   
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Lundi'''    ||'''Thème'''                                  ||'''Qui'''  ||'''Présentations'''   ||'''Exercices''' ||'''Logiciel mis en oeuvre'''      ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I      ||Bienvenue                                    || FB  || [raw-attachment:welcome-vFR.pdf PDF]                     ||  [raw-attachment:Quizz_de_Niveau-NM-F.pdf Questionnaire niveau]   ||                               ||
  ||               ||Rappels Linux                                || FB ||[raw-attachment:linux-minimal-vFR.pdf PDF]                  ||                ||                                ||
  ||               ||Usage SSH                                    ||  FB ||                                                                                       ||  [raw-attachment:ssh-usage-vFR.pdf PDF]   || ||
  ||Session II     ||Introduction à la supervision des réseaux    || FB ||[raw-attachment:network-management-vFR.pdf PDF]                     ||                ||                               ||
  ||Session III   ||Configuration des éqpt. Cisco                || DA ||[raw-attachment:cisco-config-elements-vFR.pdf PDF] ||  [raw-attachment:exercises-cisco-config-vFR.pdf PDF]          ||      ||
  ||Session IV     ||SNMP                                         || DA || [raw-attachment:snmp-vFR.pdf PDF]                     ||    [raw-attachment:exercises-snmp-v1-v2c-vFR.txt HTML]    ||[http://www.net-snmp.org/ net-snmp]||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Mardi'''    ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||Suite SNMP                               || DA ||      ||                     ||                  ||
  ||Session II ||Cacti  || DA || [raw-attachment:cacti-from-packages-vFR.pdf PDF]  ||  [raw-attachment:exercises-cacti-part-I-vFR.pdf PDF]     ||[http://www.cacti.net/ Cacti]||
  ||Session III  ||Contrôle de Versions et configuration: RANCID || FB || [raw-attachment:config-management-rancid-vFR.pdf PDF] ||  [raw-attachment:rancid-exercise-vFR.pdf PDF]    ||[http://www.shrubbery.net/rancid/ RANCID] [http://websvn.tigris.org/ WebSVN]||
  ||Session IV       ||RANCID (Suite) || FB ||  ||   || ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||'''Mercredi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I      ||Smokeping || DA || [raw-attachment:smokeping-vFR.pdf PDF]  ||  [raw-attachment:exercises-smokeping-vFR-part1.pdf PDF-1] |  [raw-attachment:exercises-smokeping-vFR-part2.pdf PDF-2]          ||[http://oss.oetiker.ch/smokeping/ SmokePing]||
  ||Session II       ||Smokeping (suite)            || DA || ||         ||   || 
  ||Session III      ||Nagios                                      || FB || [raw-attachment:nagios-vFR.pdf PDF]      ||  [raw-attachment:exercises-nagios-part-I-basic-vFR.pdf PDF-1-3] | [raw-attachment:exercises-nagios-part-IV-V-medium-vFR.pdf PDF-4-5] | [raw-attachment:exercises-nagios-part-VI-VIII-medium-vFR.pdf PDF-6-8] | [raw-attachment:exercises-nagios-part-IX-optional-vFR.pdf PDF-9] ||[http://www.nagios.org/ Nagios]||
  ||Session IV     ||Nagios (suite)                              || FB ||   ||            ||  ||
  ||                ||                                             ||  ||                      ||                ||                               ||
  ||'''Jeudi'''  ||                                            ||  ||                      ||                ||                               ||
  ||                ||                                            ||  ||                      ||                ||                               ||
  ||Session I    ||Gestion des journaux (Log)       || FB || [raw-attachment:log-management-vFR-tenshi.pdf PDF]         || [raw-attachment:exercises-log-management-syslog-ng-vFR.htm HTML-1] | [raw-attachment:exercises-log-management-tenshi-vFR.htm HTML-2]               ||                               ||
  ||Session II & III ||Ticketing Systems (Request Tracker)            || FB || [raw-attachment:ticketing-rt-vFR.pdf PDF]   ||  [raw-attachment:exercises-rt-lab1-vFR.htm HTML-1] | [raw-attachment:exercises-nagios-rt-vFR.pdf PDF-2] || [http://bestpractical.com/rt/ Request Tracker (RT)]||
  ||Session IV || Observium - Demo  || DA  || [raw-attachment:observium.pdf PDF]   || [raw-attachment:observium-install-vFR.htm HTML-1] | [raw-attachment:observium-lab-1-vFR.htm HTML-2]  ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Vendredi''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||Session I    ||!NetFlow ||JH ||  [raw-attachment:netflow.pdf PDF] ||    [raw-attachment:exercise1-flow-export-vFR.htm HTML-1]      ||    [http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html NetFlow]    || 
  ||Session II    ||!NFSEN ||JH || [raw-attachment:nfsen.pdf NfSen] ||   [raw-attachment:exercise2-install-nfdump-nfsen-vFR.htm HTML-1] | [raw-attachment:exercise3-nfsen-top-talkers-vFR.htm HTML-2] | [raw-attachment:exercise4-using-NfSen-vFR.pdf PDF-3]     ||   [http://nfsen.sourceforge.net/ NfSen]      || 
  ||Session III    ||Network Documentation (Netdot)                 || DA || [raw-attachment:network-documentation-and-netdot-vFR.pdf NetDot]  ||  [raw-attachment:exercises-netdot-vFR.pdf PDF-1]  ||[http://netdot.uoregon.edu Netdot] ||                  
  ||Session IV    ||Fiches d'évaluation                               || || [https://nsrc.org/limesurvey/index.php/491527/lang-fr Evaluation] || || || 
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||'''Sessions +''' ||                                           ||  ||                      ||                ||                               ||
  ||               ||                                             ||  ||                      ||                ||                               ||
  ||               ||Analyse du réseau local                      ||  || [raw-attachment:local-network-analysis-vFR.pdf PDF] || [raw-attachment:exercises-network-metrics-and-analysis-vFR.pdf PDF]   ||  || 
  ||               ||Définitions et terminologie                  ||  || [raw-attachment:network-performance-definitions-vFR.pdf PDF]  ||  ||  ||
  ||               ||                                                          ||  ||                                        ||             ||    ||


  {{{
  #!html
  <div align="center">
  Suivez le NSRC sur <a href="http://www.facebook.com/nsrc.org">Facebook</a>, <a href="http://google.com/+NSRCorg">G+</a> et <a href="http://twitter.com/nsrcworld">Twitter</a>.
  </div>
  }}}


name: TracBatchModify
author: trac
ipnr: 127.0.0.1
text:
  = Trac Ticket Batch Modification =
  [[TracGuideToc]]

  From [wiki:TracQuery custom query] results Trac provides support for modifying a batch of tickets in one request.

  To perform a batch modification select the tickets you wish to modify and set the new field values using the section underneath the query results. 

  == List fields

  The `Keywords` and `Cc` fields are treated as lists, where list items can be added and/or removed in addition of replacing the entire list value. All list field controls accept multiple items (i.e. multiple keywords or cc addresses).


name: WikiMacros
author: trac
ipnr: 127.0.0.1
text:
  = Trac Macros =

  [[PageOutline]]

  Trac macros are plugins to extend the Trac engine with custom 'functions' written in Python. A macro inserts dynamic HTML data in any context supporting WikiFormatting. Its syntax is `[[macro-name(optional-arguments)]]`.

  The WikiProcessors are another kind of macros. They typically deal with alternate markup formats and transformation of larger "blocks" of information (like source code highlighting). They are used for processing the multiline `{{{#!wiki-processor-name ... }}}` blocks.

  == Using Macros ==

  Macro calls are enclosed in two ''square brackets''. Like Python functions, macros can also have arguments, a comma separated list within parentheses.

  === Getting Detailed Help ===
  The list of available macros and the full help can be obtained using the !MacroList macro, as seen [#AvailableMacros below].

  A brief list can be obtained via `[[MacroList(*)]]` or `[[?]]`.

  Detailed help on a specific macro can be obtained by passing it as an argument to !MacroList, e.g. `[[MacroList(MacroList)]]`, or, more conveniently, by appending a question mark (`?`) to the macro's name, like in `[[MacroList?]]`.



  === Example ===

  A list of 3 most recently changed wiki pages starting with 'Trac':

  ||= Wiki Markup =||= Display =||
  {{{#!td
    {{{
    [[RecentChanges(Trac,3)]]
    }}}
  }}}
  {{{#!td style="padding-left: 2em;"
  [[RecentChanges(Trac,3)]]
  }}}
  |-----------------------------------
  {{{#!td
    {{{
    [[RecentChanges?(Trac,3)]]
    }}}
  }}}
  {{{#!td style="padding-left: 2em;"
  [[RecentChanges?(Trac,3)]]
  }}}
  |-----------------------------------
  {{{#!td
    {{{
    [[?]]
    }}}
  }}}
  {{{#!td style="padding-left: 2em"
  {{{#!html 
  <div style="font-size: 80%" class="trac-macrolist">
  <h3><code>[[Image]]</code></h3>Embed an image in wiki-formatted text.

  The first argument is the file …
  <h3><code>[[InterTrac]]</code></h3>Provide a list of known <a class="wiki" href="/wiki/InterTrac">InterTrac</a> prefixes.
  <h3><code>[[InterWiki]]</code></h3>Provide a description list for the known <a class="wiki" href="/wiki/InterWiki">InterWiki</a> prefixes.
  <h3><code>[[KnownMimeTypes]]</code></h3>List all known mime-types which can be used as <a class="wiki" href="/wiki/WikiProcessors">WikiProcessors</a>.
  Can be …</div>
  }}}
  etc.
  }}}

  == Available Macros ==

  ''Note that the following list will only contain the macro documentation if you've not enabled `-OO` optimizations, or not set the `PythonOptimize` option for [wiki:TracModPython mod_python].''

  [[MacroList]]

  == Macros from around the world ==

  The [http://trac-hacks.org/ Trac Hacks] site provides a wide collection of macros and other Trac [TracPlugins plugins] contributed by the Trac community. If you're looking for new macros, or have written one that you'd like to share with the world, please don't hesitate to visit that site.

  == Developing Custom Macros ==
  Macros, like Trac itself, are written in the [http://python.org/ Python programming language] and are developed as part of TracPlugins.

  For more information about developing macros, see the [trac:TracDev development resources] on the main project site.


  Here are 2 simple examples showing how to create a Macro with Trac 0.11. 

  Also, have a look at [trac:source:tags/trac-0.11/sample-plugins/Timestamp.py Timestamp.py] for an example that shows the difference between old style and new style macros and at the [trac:source:tags/trac-0.11/wiki-macros/README macros/README] which provides a little more insight about the transition.

  === Macro without arguments ===
  To test the following code, you should saved it in a `timestamp_sample.py` file located in the TracEnvironment's `plugins/` directory.
  {{{
  #!python
  from datetime import datetime
  # Note: since Trac 0.11, datetime objects are used internally

  from genshi.builder import tag

  from trac.util.datefmt import format_datetime, utc
  from trac.wiki.macros import WikiMacroBase

  class TimeStampMacro(WikiMacroBase):
      """Inserts the current time (in seconds) into the wiki page."""

      revision = "$Rev$"
      url = "$URL$"

      def expand_macro(self, formatter, name, text):
          t = datetime.now(utc)
          return tag.b(format_datetime(t, '%c'))
  }}}

  === Macro with arguments ===
  To test the following code, you should saved it in a `helloworld_sample.py` file located in the TracEnvironment's `plugins/` directory.
  {{{
  #!python
  from genshi.core import Markup

  from trac.wiki.macros import WikiMacroBase

  class HelloWorldMacro(WikiMacroBase):
      """Simple HelloWorld macro.

      Note that the name of the class is meaningful:
       - it must end with "Macro"
       - what comes before "Macro" ends up being the macro name

      The documentation of the class (i.e. what you're reading)
      will become the documentation of the macro, as shown by
      the !MacroList macro (usually used in the WikiMacros page).
      """

      revision = "$Rev$"
      url = "$URL$"

      def expand_macro(self, formatter, name, text, args):
          """Return some output that will be displayed in the Wiki content.

          `name` is the actual name of the macro (no surprise, here it'll be
          `'HelloWorld'`),
          `text` is the text enclosed in parenthesis at the call of the macro.
            Note that if there are ''no'' parenthesis (like in, e.g.
            [[HelloWorld]]), then `text` is `None`.
          `args` are the arguments passed when HelloWorld is called using a
          `#!HelloWorld` code block.
          """
          return 'Hello World, text = %s, args = %s' % \
              (Markup.escape(text), Markup.escape(repr(args)))

  }}}

  Note that `expand_macro` optionally takes a 4^th^ parameter ''`args`''. When the macro is called as a [WikiProcessors WikiProcessor], it's also possible to pass `key=value` [WikiProcessors#UsingProcessors processor parameters]. If given, those are stored in a dictionary and passed in this extra `args` parameter. On the contrary, when called as a macro, `args` is  `None`. (''since 0.12'').

  For example, when writing:
  {{{
  {{{#!HelloWorld style="polite" -silent verbose
  <Hello World!>
  }}}

  {{{#!HelloWorld
  <Hello World!>
  }}}

  [[HelloWorld(<Hello World!>)]]
  }}}
  One should get:
  {{{
  Hello World, text = <Hello World!> , args = {'style': u'polite', 'silent': False, 'verbose': True}
  Hello World, text = <Hello World!> , args = {}
  Hello World, text = <Hello World!> , args = None
  }}}

  Note that the return value of `expand_macro` is '''not''' HTML escaped. Depending on the expected result, you should escape it by yourself (using `return Markup.escape(result)`) or, if this is indeed HTML, wrap it in a Markup object (`return Markup(result)`) with `Markup` coming from Genshi, (`from genshi.core import Markup`).  

  You can also recursively use a wiki Formatter (`from trac.wiki import Formatter`) to process the `text` as wiki markup, for example by doing:

  {{{
  #!python
  from genshi.core import Markup
  from trac.wiki.macros import WikiMacroBase
  from trac.wiki import Formatter
  import StringIO

  class HelloWorldMacro(WikiMacroBase):
  	def expand_macro(self, formatter, name, text, args):
  		text = "whatever '''wiki''' markup you want, even containing other macros"
  		# Convert Wiki markup to HTML, new style
  		out = StringIO.StringIO()
  		Formatter(self.env, formatter.context).format(text, out)
  		return Markup(out.getvalue())
  }}}


name: TracInstall
author: trac
ipnr: 127.0.0.1
text:
  = Trac Installation Guide for 1.0 = 
  [[TracGuideToc]]

  Trac is written in the Python programming language and needs a database, [http://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL], or [http://mysql.com/ MySQL]. For HTML rendering, Trac uses the [http://genshi.edgewall.org Genshi] templating system.

  Since version 0.12, Trac can also be localized, and there's probably a translation available for your language. If you want to be able to use the Trac interface in other languages, then make sure you have installed the optional package [#OtherPythonPackages Babel]. Pay attention to the extra steps for localization support in the [#InstallingTrac Installing Trac] section below. Lacking Babel, you will only get the default english version, as usual.

  If you're interested in contributing new translations for other languages or enhance the existing translations, then please have a look at [[trac:TracL10N]].

  What follows are generic instructions for installing and setting up Trac and its requirements. While you may find instructions for installing Trac on specific systems at [trac:TracInstallPlatforms TracInstallPlatforms] on the main Trac site, please be sure to '''first read through these general instructions''' to get a good understanding of the tasks involved.

  [[PageOutline(2-3,Installation Steps,inline)]]

  == Dependencies ==
  === Mandatory Dependencies
  To install Trac, the following software packages must be installed:

   * [http://www.python.org/ Python], version >= 2.5 and < 3.0
     (note that we dropped the support for Python 2.4 in this release)
   * [http://peak.telecommunity.com/DevCenter/setuptools setuptools], version >= 0.6, or better yet, [http://pypi.python.org/pypi/distribute distribute]
   * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6 (unreleased version 0.7dev should work as well)

  You also need a database system and the corresponding python bindings.
  The database can be either SQLite, PostgreSQL or MySQL.

  ==== For the SQLite database #ForSQLite

  As you must be using Python 2.5, 2.6 or 2.7, you already have the SQLite database bindings bundled with the standard distribution of Python (the `sqlite3` module).

  However, if you'd like, you can download the latest and greatest version of [[trac:Pysqlite]] from 
  [http://code.google.com/p/pysqlite/downloads/list google code], where you'll find the Windows
  installers or the `tar.gz` archive for building from source: 
  {{{
  $ tar xvfz <version>.tar.gz 
  $ cd <version> 
  $ python setup.py build_static install 
  }}}
   
  This will download the latest SQLite code and build the bindings. 

  SQLite 2.x is no longer supported.

  A known bug PySqlite versions 2.5.2-4 prohibits upgrade of trac databases
  from 0.11.x to 0.12. Please use versions 2.5.5 and newer or 2.5.1 and
  older. See #9434 for more detail.

  See additional information in [trac:PySqlite PySqlite].

  ==== For the PostgreSQL database #ForPostgreSQL

  You need to install the database and its Python bindings:
   * [http://www.postgresql.org/ PostgreSQL], version 8.0 or later
   * [http://pypi.python.org/pypi/psycopg2 psycopg2]

  See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details.


  ==== For the MySQL database #ForMySQL

  Trac can now work quite well with MySQL, provided you follow the guidelines.

   * [http://mysql.com/ MySQL], version 5.0 or later
   * [http://sf.net/projects/mysql-python MySQLdb], version 1.2.2 or later

  It is '''very''' important to read carefully the  [trac:MySqlDb] page before creating the database.

  === Optional Dependencies

  ==== Version Control System ====

  ===== Subversion =====
   * [http://subversion.apache.org/ Subversion], 1.5.x or 1.6.x and the '''''corresponding''''' Python bindings. Older versions starting from 1.0, like 1.2.4, 1.3.2 or 1.4.2, etc. should still work. For troubleshooting information, check the [trac:TracSubversion#Troubleshooting TracSubversion] page.

  There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. (Good luck finding precompiled SWIG bindings for any Windows package at that listing. TracSubversion points you to [http://alagazam.net Algazam], which works for me under Python 2.6.)

  Note that Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], neither does it work yet with the newer `ctype`-style bindings. 


  '''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported].


  ===== Others =====

  Support for other version control systems is provided via third-parties. See [trac:PluginList] and [trac:VersionControlSystem].

  ==== Web Server ====
  A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server ] section below.

  Alternatively you configure Trac to run in any of the following environments.
   * [http://httpd.apache.org/ Apache] with 
     - [http://code.google.com/p/modwsgi/ mod_wsgi], see [wiki:TracModWSGI] and 
       http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac
     - [http://modpython.org/ mod_python 3.3.1], deprecated: see TracModPython)
   * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi)
   * an [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web
     server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp])
   * a CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script 
     is highly discouraged''', better use one of the previous options. 
     

  ==== Other Python Packages ====

   * [http://babel.edgewall.org Babel], version >= 0.9.5, 
     needed for localization support (unreleased version 1.0dev should work as well)
   * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9 
     for WikiRestructuredText.
   * [http://pygments.pocoo.org Pygments] for 
     [wiki:TracSyntaxColoring syntax highlighting].
     [http://silvercity.sourceforge.net/ SilverCity] and/or 
     [http://gnu.org/software/enscript/enscript.html Enscript] may still be used
     but are deprecated and you really should be using Pygments.
   * [http://pytz.sf.net pytz] to get a complete list of time zones,
     otherwise Trac will fall back on a shorter list from 
     an internal time zone implementation.

  '''Attention''': The various available versions of these dependencies are not necessarily interchangable, so please pay attention to the version numbers above. If you are having trouble getting Trac to work please double-check all the dependencies before asking for help on the [trac:MailingList] or [trac:IrcChannel].

  Please refer to the documentation of these packages to find out how they are best installed. In addition, most of the [trac:TracInstallPlatforms platform-specific instructions] also describe the installation of the dependencies. Keep in mind however that the information there ''probably concern older versions of Trac than the one you're installing'' (there are even some pages that are still talking about Trac 0.8!).


  == Installing Trac ==
  === Using `easy_install`
  One way to install Trac is using [http://pypi.python.org/pypi/setuptools setuptools].
  With setuptools you can install Trac from the subversion repository; 

  A few examples:

   - install Trac 1.0:
     {{{
     easy_install Trac==1.0
     }}}
     (NOT YET ENABLED)
   - install latest development version 1.0dev:
     {{{
     easy_install Trac==dev
     }}}
     Note that in this case you won't have the possibility to run a localized version of Trac;
     either use a released version or install from source 

  === Using `pip`
  'pip' is an easy_install replacement that is very useful to quickly install python packages.
  To get a trac installation up and running in less than 5 minutes:

  Assuming you want to have your entire pip installation in `/opt/user/trac`

   - 
  {{{
  pip -E /opt/user/trac install trac psycopg2 
  }}}
  or
   - 
  {{{
  pip -E /opt/user/trac install trac mysql-python 
  }}}

  Make sure your OS specific headers are available for pip to automatically build PostgreSQL (libpq-dev) or MySQL (libmysqlclient-dev) bindings.

  pip will automatically resolve all dependencies (like Genshi, pygments, etc.) and download the latest packages on pypi.python.org and create a self contained installation in `/opt/user/trac`.

  All commands (`tracd`, `trac-admin`) are available in `/opt/user/trac/bin`. This can also be leveraged for `mod_python` (using `PythonHandler` directive) and `mod_wsgi` (using `WSGIDaemonProcess` directive)

  Additionally, you can install several trac plugins (listed [http://pypi.python.org/pypi?:action=search&term=trac&submit=search here]) through pip.



  === From source
  Of course, using the python-typical setup at the top of the source directory also works.

  You can obtain the source for a .tar.gz or .zip file corresponding to a release (e.g. Trac-1.0.tar.gz), or you can get the source directly from the repository (see Trac:SubversionRepository for details).

  {{{
  $ python ./setup.py install
  }}}

  ''You'll need root permissions or equivalent for this step.''

  This will byte-compile the python source code and install it as an .egg file or folder in the `site-packages` directory
  of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as htdocs and templates.

  The script will also install the [wiki:TracAdmin trac-admin] command-line tool, used to create and maintain [wiki:TracEnvironment project environments], as well as the [wiki:TracStandalone tracd] standalone server.

  If you install from source and want to make Trac available in other languages, make sure  Babel is installed. Only then, perform the `install` (or simply redo the `install` once again afterwards if you realize Babel was not yet installed):
  {{{
  $ python ./setup.py install
  }}}
  Alternatively, you can do a `bdist_egg` and copy the .egg from dist/ to the place of your choice, or you can create a Windows installer (`bdist_wininst`).

  === Advanced Options ===

  To install Trac to a custom location, or find out about other advanced installation options, run:
  {{{
  easy_install --help
  }}}

  Also see [http://docs.python.org/inst/inst.html Installing Python Modules] for detailed information.

  Specifically, you might be interested in:
  {{{
  easy_install --prefix=/path/to/installdir
  }}}
  or, if installing Trac to a Mac OS X system:
  {{{
  easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages
  }}}
  Note: If installing on Mac OS X 10.6 running {{{ easy_install http://svn.edgewall.org/repos/trac/trunk }}} will install into {{{ /usr/local }}} and {{{ /Library/Python/2.6/site-packages }}} by default

  The above will place your `tracd` and `trac-admin` commands into `/usr/local/bin` and will install the Trac libraries and dependencies into `/Library/Python/2.5/site-packages`, which is Apple's preferred location for third-party Python application installations.


  == Creating a Project Environment ==

  A [TracEnvironment Trac environment] is the backend storage where Trac stores information like wiki pages, tickets, reports, settings, etc. An environment is basically a directory that contains a human-readable [TracIni configuration file], and various other files and directories.

  A new environment is created using [wiki:TracAdmin trac-admin]:
  {{{
  $ trac-admin /path/to/myproject initenv
  }}}

  [TracAdmin trac-admin] will prompt you for the information it needs to create the environment, such as the name of the project and the [TracEnvironment#DatabaseConnectionStrings database connection string]. If you're not sure what to specify for one of these options, just press `<Enter>` to use the default value. 

  Using the default database connection string in particular will always work as long as you have SQLite installed.
  For the other [DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point.

  Since 0.12, Trac doesn't ask for a [TracEnvironment#SourceCodeRepository source code repository] anymore when creating an environment. Repositories can be [TracRepositoryAdmin added] afterward, or the version control support can be disabled completely if you don't need it.

  Also note that the values you specify here can be changed later by directly editing the [TracIni conf/trac.ini] configuration file.

  Finally, make sure the user account under which the web front-end runs will have '''write permissions''' to the environment directory and all the files inside. This will be the case if you run `trac-admin ... initenv` as this user. If not, you should set the correct user afterwards. For example on Linux, with the web server running as user `apache` and group `apache`, enter:
  {{{
  # chown -R apache.apache /path/to/myproject
  }}}

  {{{#!div class=important
  '''Warning:''' Please only use ASCII-characters for account name and project path, unicode characters are not supported there.
  }}}


  == Deploying Trac

  === Running the Standalone Server ===

  After having created a Trac environment, you can easily try the web interface by running the standalone server [wiki:TracStandalone tracd]:
  {{{
  $ tracd --port 8000 /path/to/myproject
  }}}

  Then, fire up a browser and visit `http://localhost:8000/`. You should get a simple listing of all environments that `tracd` knows about. Follow the link to the environment you just created, and you should see Trac in action. If you only plan on managing a single project with Trac you can have the standalone server skip the environment list by starting it like this:
  {{{
  $ tracd -s --port 8000 /path/to/myproject
  }}}

  === Running Trac on a Web Server ===

  Trac provides various options for connecting to a "real" web server: 
   - [wiki:TracFastCgi FastCGI]
   - [wiki:TracModWSGI mod_wsgi] 
   - //[wiki:TracModPython mod_python] (no longer recommended, as mod_python is not actively maintained anymore)//
   - //[wiki:TracCgi CGI] (should not be used, as the performance is far from optimal)//

  Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. Other deployment scenarios are possible: [trac:TracNginxRecipe nginx], [http://projects.unbit.it/uwsgi/wiki/Example#Traconapacheinasub-uri uwsgi], [trac:TracOnWindowsIisIsapi Isapi-wsgi] etc.

  ==== Generating the Trac cgi-bin directory ==== #cgi-bin

  In order for Trac to function properly with FastCGI you need to have a `trac.fcgi` file and for mod_wsgi a `trac.wsgi` file. These are Python scripts which load the appropriate Python code. They can be generated using the `deploy` option of [wiki:TracAdmin trac-admin].

  There is, however, a bit of a chicken-and-egg problem. The [wiki:TracAdmin trac-admin] command requires an existing environment to function, but complains if the deploy directory already exists. This is a problem, because environments are often stored in a subdirectory of the deploy. The solution is to do something like this:
  {{{
  mkdir -p /usr/share/trac/projects/my-project
  trac-admin /usr/share/trac/projects/my-project initenv
  trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy
  mv /tmp/deploy/* /usr/share/trac
  }}}


  ==== Mapping Static Resources ====

  Out of the box, Trac will pass static resources such as style sheets or images through itself. For anything but a tracd only based deployment, this is far from optimal as the web server could be set up to directly serve those static resources (for CGI setup, this is '''highly undesirable''' and will cause abysmal performance).

  Web servers such as [http://httpd.apache.org/ Apache] allow you to create “Aliases” to resources, giving them a virtual URL that doesn't necessarily reflect the layout of the servers file system. We also can map requests for static resources directly to the directory on the file system, avoiding processing these requests by Trac itself.

  There are two primary URL paths for static resources - `/chrome/common` and `/chrome/site`. Plugins can add their own resources, usually accessible by `/chrome/<plugin>` path, so its important to override only known paths and not try to make universal `/chrome` alias for everything.

  Note that in order to get those static resources on the filesystem, you need first to extract the relevant resources from Trac using the [TracAdmin trac-admin]` <environment> deploy` command:
  [[TracAdminHelp(deploy)]]

  The target `<directory>` will then contain an `htdocs` directory with:
   - `site/` - a copy of the environment's directory `htdocs/` 
   - `common/` - the static resources of Trac itself
   - `<plugins>/` - one directory for each resource directory managed by the plugins enabled for this environment

  ===== Example: Apache and `ScriptAlias` ===== #ScriptAlias-example

  Assuming the deployment has been done this way:
  {{{
  $ trac-admin /var/trac/env deploy /path/to/trac/htdocs/common
  }}}

  Add the following snippet to Apache configuration ''before'' the `ScriptAlias` or `WSGIScriptAlias` (which map all the other requests to the Trac application), changing paths to match your deployment:
  {{{
  Alias /trac/chrome/common /path/to/trac/htdocs/common
  Alias /trac/chrome/site /path/to/trac/htdocs/site

  <Directory "/path/to/www/trac/htdocs">
    Order allow,deny
    Allow from all
  </Directory>
  }}}

  If using mod_python, you might want to add this too (otherwise, the alias will be ignored):
  {{{
  <Location "/trac/chrome/common/">
    SetHandler None
  </Location>
  }}}

  Note that we mapped `/trac` part of the URL to the `trac.*cgi` script, and the path `/trac/chrome/common` is the path you have to append to that location to intercept requests to the static resources. 

  Similarly, if you have static resources in a project's `htdocs` directory (which is referenced by `/trac/chrome/site` URL in themes), you can configure Apache to serve those resources (again, put this ''before'' the `ScriptAlias` or `WSGIScriptAlias` for the .*cgi scripts, and adjust names and locations to match your installation):
  {{{
  Alias /trac/chrome/site /path/to/projectenv/htdocs

  <Directory "/path/to/projectenv/htdocs">
    Order allow,deny
    Allow from all
  </Directory>
  }}}

  Alternatively to aliasing `/trac/chrome/common`, you can tell Trac to generate direct links for those static resources (and only those), using the [[wiki:TracIni#trac-section| [trac] htdocs_location]] configuration setting:
  {{{
  [trac]
  htdocs_location = http://static.example.org/trac-common/
  }}}
  Note that this makes it easy to have a dedicated domain serve those static resources (preferentially [http://code.google.com/speed/page-speed/docs/request.html#ServeFromCookielessDomain cookie-less]).

  Of course, you still need to make the Trac `htdocs/common` directory available through the web server at the specified URL, for example by copying (or linking) the directory into the document root of the web server:
  {{{
  $ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common
  }}}


  ==== Setting up the Plugin Cache ====

  Some Python plugins need to be extracted to a cache directory. By default the cache resides in the home directory of the current user. When running Trac on a Web Server as a dedicated user (which is highly recommended) who has no home directory, this might prevent the plugins from starting. To override the cache location you can set the PYTHON_EGG_CACHE environment variable. Refer to your server documentation for detailed instructions on how to set environment variables.

  == Configuring Authentication ==

  Trac uses HTTP authentication. You'll need to configure your webserver to request authentication when the `.../login` URL is hit (the virtual path of the "login" button). Trac will automatically pick the REMOTE_USER variable up after you provide your credentials. Therefore, all user management goes through your web server configuration. Please consult the documentation of your web server for more info.

  The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. 

  Please refer to one of the following sections:
   * TracStandalone#UsingAuthentication if you use the standalone server, `tracd`.
   * [wiki:TracModWSGI#ConfiguringAuthentication TracModWSGI#ConfiguringAuthentication] if you use the Apache web server, with any of its front end: `mod_wsgi` of course, but the same instructions applies also for `mod_python`, `mod_fcgi` or `mod_fastcgi`.
   * TracFastCgi if you're using another web server with FCGI support (Cherokee, Lighttpd, !LiteSpeed, nginx)

  == Granting admin rights to the admin user
  Grant admin rights to user admin:
  {{{
  $ trac-admin /path/to/myproject permission add admin TRAC_ADMIN
  }}}
  This user will have an "Admin" entry menu that will allow you to admin your trac project.

  == Finishing the install

  === Automatic reference to the SVN changesets in Trac tickets ===

  You can configure SVN to automatically add a reference to the changeset into the ticket comments, whenever changes are committed to the repository. The description of the commit needs to contain one of the following formulas:
   * '''`Refs #123`''' - to reference this changeset in `#123` ticket
   * '''`Fixes #123`''' - to reference this changeset and close `#123` ticket with the default status ''fixed''

  This functionality requires a post-commit hook to be installed as described in [wiki:TracRepositoryAdmin#ExplicitSync TracRepositoryAdmin], and enabling the optional commit updater components by adding the following line to the `[components]` section of your [wiki:TracIni#components-section trac.ini], or enabling the components in the "Plugins" admin panel.
  {{{
  tracopt.ticket.commit_updater.* = enabled
  }}}
  For more information, see the documentation of the `CommitTicketUpdater` component in the "Plugins" admin panel.

  === Using Trac ===

  Once you have your Trac site up and running, you should be able to create tickets, view the timeline, browse your version control repository if configured, etc.

  Keep in mind that //anonymous// (not logged in) users can by default access only a few of the features, in particular they will have a read-only access to the resources. You will need to configure authentication and grant additional [wiki:TracPermissions permissions] to authenticated users to see the full set of features.

  '' Enjoy! ''

  [trac:TracTeam The Trac Team]

  ----
  See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracUpgrade, TracPermissions


name: TracReports
author: trac
ipnr: 127.0.0.1
text:
  = Trac Reports =
  [[TracGuideToc]]

  The Trac reports module provides a simple, yet powerful reporting facility
  to present information about tickets in the Trac database.

  Rather than have its own report definition format, TracReports relies on standard SQL
  `SELECT` statements for custom report definition. 

    '''Note:''' ''The report module is being phased out in its current form because it seriously limits the ability of the Trac team to make adjustments to the underlying database schema. We believe that the [wiki:TracQuery query module] is a good replacement that provides more flexibility and better usability. While there are certain reports that cannot yet be handled by the query module, we intend to further enhance it so that at some point the reports module can be completely removed. This also means that there will be no major enhancements to the report module anymore.''

    ''You can already completely replace the reports module by the query module simply by disabling the former in [wiki:TracIni trac.ini]:''
    {{{
    [components]
    trac.ticket.report.* = disabled
    }}}
    ''This will make the query module the default handler for the “View Tickets” navigation item. We encourage you to try this configuration and report back what kind of features of reports you are missing, if any.''

  A report consists of these basic parts:
   * '''ID''' — Unique (sequential) identifier 
   * '''Title''' — Descriptive title
   * '''Description''' — A brief description of the report, in WikiFormatting text.
   * '''Report Body''' — List of results from report query, formatted according to the methods described below.
   * '''Footer''' — Links to alternative download formats for this report.

  == Changing Sort Order ==
  Simple reports - ungrouped reports to be specific - can be changed to be sorted by any column simply by clicking the column header. 

  If a column header is a hyperlink (red), click the column you would like to sort by. Clicking the same header again reverses the order.

  == Changing Report Numbering ==
  There may be instances where you need to change the ID of the report, perhaps to organize the reports better. At present this requires changes to the trac database. The ''report'' table has the following schema ''(since 0.10)'':
   * id integer PRIMARY KEY
   * author text
   * title text
   * query text
   * description text
  Changing the ID changes the shown order and number in the ''Available Reports'' list and the report's perma-link. This is done by running something like:
  {{{
  update report set id=5 where id=3;
  }}}
  Keep in mind that the integrity has to be maintained (i.e., ID has to be unique, and you don't want to exceed the max, since that's managed by SQLite someplace).

  You may also need to update or remove the report number stored in the report or query.

  == Navigating Tickets ==
  Clicking on one of the report results will take you to that ticket. You can navigate through the results by clicking the ''Next Ticket'' or ''Previous Ticket'' links just below the main menu bar, or click the ''Back to Report'' link to return to the report page.

  You can safely edit any of the tickets and continue to navigate through the results using the ''!Next/Previous/Back to Report'' links after saving your results, but when you return to the report, there will be no hint about what has changed, as would happen if you were navigating a list of tickets obtained from a query (see TracQuery#NavigatingTickets). ''(since 0.11)''

  == Alternative Download Formats ==
  Aside from the default HTML view, reports can also be exported in a number of alternative formats.
  At the bottom of the report page, you will find a list of available data formats. Click the desired link to 
  download the alternative report format.

  === Comma-delimited - CSV (Comma Separated Values) ===
  Export the report as plain text, each row on its own line, columns separated by a single comma (',').
  '''Note:''' The output is fully escaped so carriage returns, line feeds, and commas will be preserved in the output.

  === Tab-delimited ===
  Like above, but uses tabs (\t) instead of comma.

  === RSS - XML Content Syndication ===
  All reports support syndication using XML/RSS 2.0. To subscribe to an RSS feed, click the orange 'XML' icon at the bottom of the page. See TracRss for general information on RSS support in Trac.

  ----

  == Creating Custom Reports ==

  ''Creating a custom report requires a comfortable knowledge of SQL.''

  '''Note that you need to set up [TracPermissions#Reports permissions] in order to see the buttons for adding or editing reports.'''

  A report is basically a single named SQL query, executed and presented by
  Trac.  Reports can be viewed and created from a custom SQL expression directly
  in the web interface.

  Typically, a report consists of a SELECT-expression from the 'ticket' table,
  using the available columns and sorting the way you want it.

  == Ticket columns ==
  The ''ticket'' table has the following columns:
   * id
   * type
   * time
   * changetime
   * component
   * severity  
   * priority 
   * owner
   * reporter
   * cc
   * version
   * milestone
   * status
   * resolution
   * summary
   * description
   * keywords

  See TracTickets for a detailed description of the column fields.

  Example: '''All active tickets, sorted by priority and time'''
  {{{
  SELECT id AS ticket, status, severity, priority, owner, 
         time AS created, summary FROM ticket 
    WHERE status IN ('new', 'assigned', 'reopened')
    ORDER BY priority, time
  }}}


  == Advanced Reports: Dynamic Variables ==
  For more flexible reports, Trac supports the use of ''dynamic variables'' in report SQL statements. 
  In short, dynamic variables are ''special'' strings that are replaced by custom data before query execution.

  === Using Variables in a Query ===
  The syntax for dynamic variables is simple, any upper case word beginning with '$' is considered a variable.

  Example:
  {{{
  SELECT id AS ticket,summary FROM ticket WHERE priority=$PRIORITY
  }}}

  To assign a value to $PRIORITY when viewing the report, you must define it as an argument in the report URL, leaving out the leading '$'.

  Example:
  {{{
   http://trac.edgewall.org/reports/14?PRIORITY=high
  }}}

  To use multiple variables, separate them with an '&'.

  Example:
  {{{
   http://trac.edgewall.org/reports/14?PRIORITY=high&SEVERITY=critical
  }}}

  Dynamic variables can also be used in the report title and description (since 1.1.1).

  === !Special/Constant Variables ===
  There is one dynamic variable whose value is set automatically (the URL does not have to be changed) to allow practical reports. 

   * $USER — Username of logged in user.

  Example (''List all tickets assigned to me''):
  {{{
  SELECT id AS ticket,summary FROM ticket WHERE owner=$USER
  }}}



  == Advanced Reports: Custom Formatting ==
  Trac is also capable of more advanced reports, including custom layouts,
  result grouping and user-defined CSS styles. To create such reports, we'll use
  specialized SQL statements to control the output of the Trac report engine.

  === Special Columns ===
  To format reports, TracReports looks for 'magic' column names in the query
  result. These 'magic' names are processed and affect the layout and style of the 
  final report.

  === Automatically formatted columns ===
   * '''ticket''' — Ticket ID number. Becomes a hyperlink to that ticket. 
   * '''id''' — same as '''ticket''' above when '''realm''' is not set
   * '''realm''' — together with '''id''', can be used to create links to other resources than tickets (e.g. a realm of ''wiki'' and an ''id'' to a page name will create a link to that wiki page)
   * '''created, modified, date, time''' — Format cell as a date and/or time.
   * '''description''' — Ticket description field, parsed through the wiki engine.

  '''Example:'''
  {{{
  SELECT id AS ticket, created, status, summary FROM ticket 
  }}}

  Those columns can also be defined but marked as hidden, see [#column-syntax below].

  See trac:wiki/CookBook/Configuration/Reports for some example of creating reports for realms other than ''ticket''.

  === Custom formatting columns ===
  Columns whose names begin and end with 2 underscores (Example: '''`__color__`''') are
  assumed to be ''formatting hints'', affecting the appearance of the row.
   
   * '''`__group__`''' — Group results based on values in this column. Each group will have its own header and table.
   * '''`__grouplink__`''' — Make the header of each group a link to the specified URL. The URL is taken from the first row of each group.
   * '''`__color__`''' — Should be a numeric value ranging from 1 to 5 to select a pre-defined row color. Typically used to color rows by issue priority.
  {{{
  #!html
  <div style="margin-left:7.5em">Defaults: 
  <span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #fdc; border-color: #e88; color: #a22">Color 1</span>
  <span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #ffb; border-color: #eea; color: #880">Color 2</span>
  <span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #fbfbfb; border-color: #ddd; color: #444">Color 3</span>
  <span style="border: none; color: #333; background: transparent; font-size: 85%; background: #e7ffff; border-color: #cee; color: #099">Color 4</span>
  <span style="border: none; color: #333; background: transparent;  font-size: 85%; background: #e7eeff; border-color: #cde; color: #469">Color 5</span>
  </div>
  }}}
   * '''`__style__`''' — A custom CSS style expression to use on the `<tr>` element of the current row.
   * '''`__class__`''' — Zero or more space-separated CSS class names to be set on the `<tr>` element of the current row. These classes are added to the class name derived from `__color__` and the odd / even indicator.

  '''Example:''' ''List active tickets, grouped by milestone, group header linked to milestone page, colored by priority''
  {{{
  SELECT p.value AS __color__,
       t.milestone AS __group__,
       '../milestone/' || t.milestone AS __grouplink__,
       (CASE owner WHEN 'daniel' THEN 'font-weight: bold; background: red;' ELSE '' END) AS __style__,
         t.id AS ticket, summary
    FROM ticket t,enum p
    WHERE t.status IN ('new', 'assigned', 'reopened') 
      AND p.name=t.priority AND p.type='priority'
    ORDER BY t.milestone, p.value, t.severity, t.time
  }}}

  '''Note:''' A table join is used to match ''ticket'' priorities with their
  numeric representation from the ''enum'' table.

  === Changing layout of report rows === #column-syntax
  By default, all columns on each row are display on a single row in the HTML
  report, possibly formatted according to the descriptions above. However, it's
  also possible to create multi-line report entries.

   * '''`column_`''' — ''Break row after this''. By appending an underscore ('_') to the column name, the remaining columns will be continued on a second line.

   * '''`_column_`''' — ''Full row''. By adding an underscore ('_') both at the beginning and the end of a column name, the data will be shown on a separate row.

   * '''`_column`''' — ''Hide data''. Prepending an underscore ('_') to a column name instructs Trac to hide the contents from the HTML output. This is useful for information to be visible only if downloaded in other formats (like CSV or RSS/XML).
     This can be used to hide any kind of column, even important ones required for identifying the resource, e.g. `id as _id` will hide the '''Id''' column but the link to the ticket will be present.

  '''Example:''' ''List active tickets, grouped by milestone, colored by priority, with  description and multi-line layout''

  {{{
  SELECT p.value AS __color__,
         t.milestone AS __group__,
         (CASE owner 
            WHEN 'daniel' THEN 'font-weight: bold; background: red;' 
            ELSE '' END) AS __style__,
         t.id AS ticket, summary AS summary_,             -- ## Break line here
         component,version, severity, milestone, status, owner,
         time AS created, changetime AS modified,         -- ## Dates are formatted
         description AS _description_,                    -- ## Uses a full row
         changetime AS _changetime, reporter AS _reporter -- ## Hidden from HTML output
    FROM ticket t,enum p
    WHERE t.status IN ('new', 'assigned', 'reopened') 
      AND p.name=t.priority AND p.type='priority'
    ORDER BY t.milestone, p.value, t.severity, t.time
  }}}

  === Reporting on custom fields ===

  If you have added custom fields to your tickets (a feature since v0.8, see TracTicketsCustomFields), you can write a SQL query to cover them. You'll need to make a join on the ticket_custom table, but this isn't especially easy.

  If you have tickets in the database ''before'' you declare the extra fields in trac.ini, there will be no associated data in the ticket_custom table. To get around this, use SQL's "LEFT OUTER JOIN" clauses. See [trac:TracIniReportCustomFieldSample TracIniReportCustomFieldSample] for some examples.

  === A note about SQL rewriting #rewriting

  Beyond the relatively trivial replacement of dynamic variables, the SQL query is also altered in order to support two features of the reports:
   1. [#sort-order changing the sort order]
   2. pagination support (limitation of the number of result rows displayed on each page)
  In order to support the first feature, the sort column is inserted in the `ORDER BY` clause in the first position or in the second position if a `__group__` column is specified (an `ORDER BY` clause is created if needed). In order to support pagination, a `LIMIT ... OFFSET ...` clause is appended.
  The query might be too complex for the automatic rewrite to work correctly, resulting in an erroneous query. In this case you still have the possibility to control exactly how the rewrite is done by manually inserting the following tokens:
   - `@SORT_COLUMN@`, the place where the name of the selected sort column will be inserted,
   - `@LIMIT_OFFSET@`, the place where the pagination support clause will be added
  Note that if you write them after an SQL comment, `--`, you'll effectively disable rewriting if this is what you want!

  Let's take an example, consider the following SQL query:
  {{{
  -- ## 4: Assigned, Active Tickets by Owner ## --

  -- 
  -- List assigned tickets, group by ticket owner, sorted by priority.
  -- 

  SELECT p.value AS __color__,
     owner AS __group__,
     id AS ticket, summary, component, milestone, t.type AS type, severity, time AS created,
     changetime AS _changetime, description AS _description,
     reporter AS _reporter
    FROM ticket t,enum p
    WHERE status = 'assigned'
  AND p.name=t.priority AND p.type='priority'
    ORDER BY __group__, p.value, severity, time
  }}}

  The automatic rewrite will be the following (4 rows per page, page 2, sorted by `component`):
  {{{
  SELECT p.value AS __color__,
     owner AS __group__,
     id AS ticket, summary, component, milestone, t.type AS type, severity, time AS created,
     changetime AS _changetime, description AS _description,
     reporter AS _reporter
    FROM ticket t,enum p
    WHERE status = 'assigned'
  AND p.name=t.priority AND p.type='priority'
    ORDER BY __group__ ASC, `component` ASC,  __group__, p.value, severity, time
   LIMIT 4 OFFSET 4
  }}}

  The equivalent SQL query with the rewrite tokens would have been:
  {{{
  SELECT p.value AS __color__,
     owner AS __group__,
     id AS ticket, summary, component, milestone, t.type AS type, severity, time AS created,
     changetime AS _changetime, description AS _description,
     reporter AS _reporter
    FROM ticket t,enum p
    WHERE status = 'assigned'
  AND p.name=t.priority AND p.type='priority'
    ORDER BY __group__, @SORT_COLUMN@, p.value, severity, time
  @LIMIT_OFFSET@
  }}}

  If you want to always sort first by priority and only then by the user selected sort column, simply use the following `ORDER BY` clause:
  {{{
    ORDER BY __group__, p.value, @SORT_COLUMN@, severity, time
  }}}

  ----
  See also: TracTickets, TracQuery, TracGuide, [http://www.sqlite.org/lang_expr.html Query Language Understood by SQLite]


name: TracRss
author: trac
ipnr: 127.0.0.1
text:
  = Using RSS with Trac =
  [[TracGuideToc]]

  Several of the Trac modules support content syndication using the RSS (Really Simple Syndication) XML format.
  Using the RSS subscription feature in Trac, you can easily monitor progress of the project, a set of issues or even changes to a single file.

  Trac supports RSS feeds in:

   * TracTimeline —  Use the RSS feed to '''subscribe to project events'''.[[br]]Monitor overall project progress in your favorite RSS reader.
   * TracTickets, TracReports, and TracQuery — Allows syndication of report and ticket query results.[[br]]Be notified about important and relevant issue tickets.
   * TracBrowser and TracRevisionLog — Syndication of file changes.[[br]]Stay up to date with changes to a specific file or directory.

  == How to access RSS data ==
  Anywhere in Trac where RSS is available, you should find a small orange '''XML''' icon, typically placed at the bottom of the page. Clicking the icon will access the RSS feed for that specific resource.

  '''Note:''' Different modules provide different data in their RSS feeds. Usually, the syndicated information corresponds to the current view. For example, if you click the RSS link on a report page, the feed will be based on that report. It might be explained by thinking of the RSS feeds as an ''alternate view of the data currently displayed''.

  == Links ==
   * ''Specifications:''
     * http://blogs.law.harvard.edu/tech/rss — RSS 2.0 Specification

   * ''Multi-platform RSS readers:''
     * http://www.rssowl.org/ — Open source, Eclipse-based, RSS reader for Linux, Mac and Windows systems that supports https and authenticated feeds.

   * ''Linux/BSD/*n*x systems:''
     * http://liferea.sourceforge.net/ — Open source GTK2 RSS Reader for Linux
     * [http://akregator.sourceforge.net/ Akregator] — Open source KDE RSS Reader (part of KDE-PIM)

   * ''Mac OS X systems:''
     * http://ranchero.com/netnewswire/ — An excellent RSS reader for Mac OS X (has both free and pay versions)
     * http://www.utsire.com/shrook/ — An RSS reader for Max OS X that supports https (even with self signed certificates) and authenticated feeds.
     * http://vienna-rss.sourceforge.net/ — Open source Feed Reader for Mac OS X with smart folders support
     * http://www.mesadynamics.com/Tickershock.html — Non-intrusive "news ticker" style RSS reader for Mac OS X

   * ''Windows systems:''
     * http://www.rssreader.com/ — Free and powerful RSS Reader for Windows
     * http://www.sharpreader.net/ — A free RSS Reader written in .NET for Windows

   * ''Firefox:''
     * http://www.mozilla.org/products/firefox/ — Mozilla Firefox features plenty [https://addons.mozilla.org/en-US/firefox/search/?q=rss&appver=&platform= add-ons] for supporting RSS

  ----
  See also: TracGuide, TracTimeline, TracReports, TracBrowser


name: TracRepositoryAdmin
author: trac
ipnr: 127.0.0.1
text:
  = Repository Administration =
  [[PageOutline(2-3)]]

  == Quick start == #QuickStart

   * Manage repositories in the "Repository" admin panel, with `trac-admin` or in the `[repositories]` section of [wiki:TracIni#repositories-section trac.ini].
   * Set up a call to `trac-admin $ENV changeset added $REPO $REV` in the post-commit hook of each repository. Additionally, add a call to `trac-admin $ENV changeset modified $REPO $REV` in the post-revprop-change hook of repositories allowing revision property changes.
   * Set the `[trac] repository_sync_per_request` option to an empty value to disable per-request syncing.
   * Make sure the user under which your Subversion hooks are run has write access to the Trac environment, or use a tool like `sudo` to temporarily elevate privileges.

  == Specifying repositories == #Repositories
  Starting with 0.12, Trac can handle more than one repository per environment. The pre-0.12 way of specifying the repository with the `repository_dir` and `repository_type` options in the `[trac]` section of [wiki:TracIni trac.ini] is still supported, but two new mechanisms allow including additional repositories into an environment.

  It is also possible to define aliases of repositories, that act as "pointers" to real repositories. This can be useful when renaming a repository, to avoid breaking all the links to the old name.

  A number of attributes can be associated with each repository, which define the repository's location, type, name and how it is displayed in the source browser. The following attributes are supported:

  ||='''Attribute''' =||='''Description''' =||
  ||`alias` ||\
  ||A repository having an `alias` attribute is an alias to a real repository. All TracLinks referencing the alias resolve to the aliased repository. Note that multiple indirection is not supported, so an alias must always point to a real repository. The `alias` and `dir` attributes are mutually exclusive. ||
  ||`description` ||\
  ||The text specified in the `description` attribute is displayed below the top-level entry for the repository in the source browser. It supports WikiFormatting. ||
  ||`dir` ||\
  ||The `dir` attribute specifies the location of the repository in the filesystem. It corresponds to the value previously specified in the option `[trac] repository_dir`. The `alias` and `dir` attributes are mutually exclusive. ||
  ||`hidden` ||When set to `true`, the repository is hidden from the repository index page in the source browser. Browsing the repository is still possible, and links referencing the repository remain valid. ||
  ||`type` ||The `type` attribute sets the type of version control system used by the repository. Trac supports Subversion and Git out-of-the-box, and plugins add support for many other systems. If `type` is not specified, it defaults to the value of the `[trac] repository_type` option. ||
  ||`url` ||The `url` attribute specifies the root URL to be used for checking out from the repository. When specified, a "Repository URL" link is added to the context navigation links in the source browser, that can be copied into the tool used for creating the working copy. ||

  A repository `name` and one of `alias` or `dir` attributes are mandatory. All others are optional.

  After adding a repository, the cache for that repository must be re-synchronized once with the `trac-admin $ENV repository resync` command.

   `repository resync <repos>`::
     Re-synchronize Trac with a repository.


  === In `trac.ini` === #ReposTracIni
  Repositories and repository attributes can be specified in the `[repositories]` section of [wiki:TracIni#repositories-section trac.ini]. Every attribute consists of a key structured as `{name}.{attribute}` and the corresponding value separated with an equal sign (`=`). The name of the default repository is empty.

  The main advantage of specifying repositories in `trac.ini` is that they can be inherited from a global configuration (see the [wiki:TracIni#GlobalConfiguration global configuration] section of TracIni). One drawback is that, due to limitations in the `ConfigParser` class used to parse `trac.ini`, the repository name is always all-lowercase.

  The following example defines two Subversion repositories named `project` and `lib`, and an alias to `project` as the default repository. This is a typical use case where a Trac environment previously had a single repository (the `project` repository), and was converted to multiple repositories. The alias ensures that links predating the change continue to resolve to the `project` repository.
  {{{
  #!ini
  [repositories]
  project.dir = /var/repos/project
  project.description = This is the ''main'' project repository.
  project.type = svn
  project.url = http://example.com/svn/project
  project.hidden = true

  lib.dir = /var/repos/lib
  lib.description = This is the secondary library code.
  lib.type = svn
  lib.url = http://example.com/svn/lib

  .alias = project
  }}}
  Note that `name.alias = target` makes `name` an alias for the `target` repo, not the other way around.

  === In the database === #ReposDatabase
  Repositories can also be specified in the database, using either the "Repositories" admin panel under "Version Control", or the `trac-admin $ENV repository` commands.

  The admin panel shows the list of all repositories defined in the Trac environment. It allows adding repositories and aliases, editing repository attributes and removing repositories. Note that repositories defined in `trac.ini` are displayed but cannot be edited.

  The following [wiki:TracAdmin trac-admin] commands can be used to perform repository operations from the command line.

   `repository add <repos> <dir> [type]`::
     Add a repository `<repos>` located at `<dir>`, and optionally specify its type.

   `repository alias <name> <target>`::
     Create an alias `<name>` for the repository `<target>`.

   `repository remove <repos>`::
     Remove the repository `<repos>`.

   `repository set <repos> <key> <value>`::
     Set the attribute `<key>` to `<value>` for the repository `<repos>`. 

  Note that the default repository has an empty name, so it will likely need to be quoted when running `trac-admin` from a shell. Alternatively, the name "`(default)`" can be used instead, for example when running `trac-admin` in interactive mode.


  == Repository synchronization == #Synchronization
  Prior to 0.12, Trac synchronized its cache with the repository on every HTTP request. This approach is not very efficient and not practical anymore with multiple repositories. For this reason, explicit synchronization through post-commit hooks was added. 

  There is also new functionality in the form of a repository listener extension point ''(IRepositoryChangeListener)'' that is triggered by the post-commit hook when a changeset is added or modified, and can be used by plugins to perform actions on commit.

  === Mercurial Repositories ===
  Please note that at the time of writing, no initial resynchronization or any hooks are necessary for Mercurial repositories - see [trac:#9485] for more information. 

  === Explicit synchronization === #ExplicitSync
  This is the preferred method of repository synchronization. It requires setting the `[trac]  repository_sync_per_request` option in [wiki:TracIni#trac-section trac.ini] to an empty value, and adding a call to `trac-admin` in the post-commit hook of each repository. Additionally, if a repository allows changing revision metadata, a call to `trac-admin` must be added to the post-revprop-change hook as well.

   `changeset added <repos> <rev> [...]`::
     Notify Trac that one or more changesets have been added to a repository.

   `changeset modified <repos> <rev> [...]`::
     Notify Trac that metadata on one or more changesets in a repository has been modified.

  The `<repos>` argument can be either a repository name (use "`(default)`" for the default repository) or the path to the repository.

  Note that you may have to set the environment variable PYTHON_EGG_CACHE to the same value as was used for the web server configuration before calling trac-admin, if you changed it from its default location. See [wiki:TracPlugins Trac Plugins] for more information.

  The following examples are complete post-commit and post-revprop-change scripts for Subversion. They should be edited for the specific environment, marked executable (where applicable) and placed in the `hooks` directory of each repository. On Unix (`post-commit`):
  {{{#!sh
  #!/bin/sh
  export PYTHON_EGG_CACHE="/path/to/dir"
  /usr/bin/trac-admin /path/to/env changeset added "$1" "$2"
  }}}
  Note: Ubuntu doesn't seem to like /usr/bin/trac-admin, so just use:
  {{{#!sh
  #!/bin/sh
  export PYTHON_EGG_CACHE="/path/to/dir"
  trac-admin /path/to/env/ changeset added "$1" "$2"
  }}}
  On Windows (`post-commit.cmd`):
  {{{#!application/x-dos-batch
  @C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset added "%1" "%2"
  }}}

  The post-revprop-change hook for Subversion is very similar. On Unix (`post-revprop-change`):
  {{{#!sh
  #!/bin/sh
  export PYTHON_EGG_CACHE="/path/to/dir"
  /usr/bin/trac-admin /path/to/env changeset modified "$1" "$2"
  }}}
  On Windows (`post-revprop-change.cmd`):
  {{{#!application/x-dos-batch
  @C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset modified "%1" "%2"
  }}}

  The Unix variants above assume that the user running the Subversion commit has write access to the Trac environment, which is the case in the standard configuration where both the repository and Trac are served by the web server. If you access the repository through another means, for example `svn+ssh://`, you may have to run `trac-admin` with different privileges, for example by using `sudo`.

  Note that calling `trac-admin` in your Subversion hooks can slow down the commit and log editing operations on the client side. You might want to use the [trac:source:trunk/contrib/trac-svn-hook contrib/trac-svn-hook] script which starts `trac-admin` in an asynchronous way. The script also comes with a number of safety checks and usage advices which should make it easier to set up and test your hooks. There's no equivalent `trac-svn-hook.bat` for Windows yet, but the script can be run by Cygwin's bash.

  See the [http://svnbook.red-bean.com/en/1.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks section about hooks] in the Subversion book for more information. Other repository types will require different hook setups.

  Git hooks can be used in the same way for explicit syncing of git repositories. Add the following to `.git/hooks/post-commit`:
  {{{#!sh
  REV=$(git rev-parse HEAD)
  trac-admin /path/to/env changeset added <my-repository> $REV
  }}}

  For Mercurial, add the following entries to the `.hgrc` file of each repository accessed by Trac (if [trac:TracMercurial] is installed in a Trac `plugins` directory, download [trac:source:mercurial-plugin/tracext/hg/hooks.py hooks.py] and place it somewhere accessible):
  {{{#!ini
  [hooks]
  ; If mercurial-plugin is installed globally
  commit = python:tracext.hg.hooks.add_changesets
  changegroup = python:tracext.hg.hooks.add_changesets

  ; If mercurial-plugin is installed in a Trac plugins directory
  commit = python:/path/to/hooks.py:add_changesets
  changegroup = python:/path/to/hooks.py:add_changesets

  [trac]
  env = /path/to/env
  trac-admin = /path/to/trac-admin
  }}}

  === Per-request synchronization === #PerRequestSync
  If the post-commit hooks are not available, the environment can be set up for per-request synchronization. In that case, the `[trac] repository_sync_per_request` option in [wiki:TracIni#trac-section trac.ini] must be set to a comma-separated list of repository names to be synchronized.

  Note that in this case, the changeset listener extension point is not called, and therefore plugins using it will not work correctly.


  == Migration from a single-repository setup (Subversion) == #Migration
  The following procedure illustrates a typical migration from a Subversion single-repository setup to multiple repositories.

   1. Remove the default repository specification from the `[trac] repository_dir` option.
   1. Add the main repository as a named repository.
   1. Re-synchronize the main repository.
   1. Set up post-commit and post-revprop-change hooks on the "main" repository, and set `[trac] repository_sync_per_request` to an empty value.
   1. Add an alias to the main repository as the default repository (by leaving out the the `name`, e.g. `.alias = main`). This ensures that all links predating the migration still resolve to the main repository.
   1. Repeat steps 2, 3 and 4 to add other "named" repositories as needed.

  == Migration from a single-repository setup (Mercurial) == #MigrationMercurial
  The following procedure illustrates a typical migration from a Mercurial single-repository setup to multiple repositories. Please note that at the time of writing, no initial resynchronization or any hooks are necessary for Mercurial repositories - see [trac:ticket:9485 #9485] for more information.

   1. Upgrade to the latest version of the TracMercurial plugin.
   1. Remove the default repository specification from the `[trac] repository_dir` option.
   1. Add the main repository as a named repository.
   1. Add an alias to the main repository as the default repository (by leaving out the the `name`, e.g. `.alias = main`). This ensures that all links predating the migration still resolve to the main repository.
   1. Repeat step 3 to add other "named" repositories as needed.

  == Troubleshooting ==

  === My trac-post-commit-hook doesn't work anymore === #trac-post-commit-hook

  You must now use the optional components from `tracopt.ticket.commit_updater.*`, which you can activate through the Plugins panel in the Administrative part of the web interface, or by directly modifying the [TracIni#components-section "[components]"] section in the trac.ini. Be sure to use [#ExplicitSync explicit synchronization] as explained above.


name: TracFineGrainedPermissions
author: trac
ipnr: 127.0.0.1
text:
  [[PageOutline(2-5, Contents, floated)]]
  = Fine grained permissions =

  Before Trac 0.11, it was only possible to define fine-grained permissions checks on the repository browser sub-system.

  Since 0.11, there's a general mechanism in place that allows custom **permission policy plugins** to grant or deny any action on any kind of Trac resources, even at the level of specific versions of such resources.

  Note that for Trac 0.12, `authz_policy` has been integrated as an optional module (in `tracopt.perm.authz_policy.*`), so it's installed by default and can simply be activated via the //Plugins// panel in the Trac administration module.


  == Permission Policies ==

  A great diversity of permission policies can be implemented, and Trac comes with a few examples. 

  Which policies are currently active is determined by a configuration setting in TracIni:
  e.g.
  {{{
  [trac]
  permission_policies = AuthzSourcePolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
  }}}
  This lists the [#AuthzSourcePolicy] described below as the first policy, followed by the !DefaultPermissionPolicy which checks for the traditional coarse grained style permissions described in TracPermissions, and the !LegacyAttachmentPolicy which knows how to use the coarse grained permissions for checking the permissions available on attachments.

  Among the possible optional choices, there is [#AuthzPolicy], a very generic permission policy, based on an Authz-style system. See
  [trac:source:branches/0.12-stable/tracopt/perm/authz_policy.py authz_policy.py] for details. 

  Another popular permission policy [#AuthzSourcePolicy], re-implements the pre-0.12 support for checking fine-grained permissions limited to Subversion repositories in terms of the new system.

  See also [trac:source:branches/0.12-stable/sample-plugins/permissions sample-plugins/permissions] for more examples.


  === !AuthzPolicy === 
  ==== Configuration ====
  * Install [http://www.voidspace.org.uk/python/configobj.html ConfigObj] (still needed for 0.12).
  * Copy authz_policy.py into your plugins directory (only for Trac 0.11).
  * Put a [http://swapoff.org/files/authzpolicy.conf authzpolicy.conf] file somewhere, preferably on a secured location on the server, not readable for others than the webuser. If the  file contains non-ASCII characters, the UTF-8 encoding should be used.
  * Update your `trac.ini`:
    1. modify the [TracIni#trac-section permission_policies] entry in the `[trac]` section
  {{{
  [trac]
  ...
  permission_policies = AuthzPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
  }}}
    1. add a new `[authz_policy]` section
  {{{
  [authz_policy]
  authz_file = /some/trac/env/conf/authzpolicy.conf
  }}}
    1. enable the plugin through [/admin/general/plugin WebAdmin] or by editing the `[components]` section
  {{{
  [components]
  ...
  # Trac 0.12
  tracopt.perm.authz_policy.* = enabled
  # for Trac 0.11 use this
  #authz_policy.* = enabled 
  }}}


  ==== Usage Notes ====
  Note that the order in which permission policies are specified is quite critical, 
  as policies will be examined in the sequence provided.

  A policy will return either `True`, `False` or `None` for a given permission check. `True` is returned if the policy explicitly grants the permission. `False` is returned if the policy explicitly denies the permission. `None` is returned if the policy is unable to either grant or deny the permission.

  NOTE: Only if the return value is `None` will the ''next'' permission policy be consulted.
  If none of the policies explicitly grants the permission, the final result will be `False` 
  (i.e. permission denied).

  The `authzpolicy.conf` file is a `.ini` style configuration file:
  {{{
  [wiki:PrivatePage@*]
  john = WIKI_VIEW, !WIKI_MODIFY
  jack = WIKI_VIEW
  * =
  }}}
  * Each section of the config is a glob pattern used to match against a Trac resource
    descriptor. These descriptors are in the form:
  {{{
  <realm>:<id>@<version>[/<realm>:<id>@<version> ...]
  }}}
    Resources are ordered left to right, from parent to child. If any
    component is inapplicable, `*` is substituted. If the version pattern is
    not specified explicitely, all versions (`@*`) is added implicitly

    Example: Match the WikiStart page
  {{{
  [wiki:*]
  [wiki:WikiStart*]
  [wiki:WikiStart@*]
  [wiki:WikiStart]
  }}}

    Example: Match the attachment `wiki:WikiStart@117/attachment/FOO.JPG@*`
    on WikiStart
  {{{
  [wiki:*]
  [wiki:WikiStart*]
  [wiki:WikiStart@*]
  [wiki:WikiStart@*/attachment/*]
  [wiki:WikiStart@117/attachment/FOO.JPG]
  }}}

  * Sections are checked against the current Trac resource descriptor '''IN ORDER''' of
    appearance in the configuration file. '''ORDER IS CRITICAL'''.

  * Once a section matches, the current username is matched against the keys 
    (usernames) of the section, '''IN ORDER'''. 
    * If a key (username) is prefixed with a `@`, it is treated as a group. 
    * If a value (permission) is prefixed with a `!`, the permission is
      denied rather than granted.

    The username will match any of 'anonymous', 'authenticated', <username> or '*', using normal Trac permission rules. || '''Note:''' Other groups which are created by user (e.g. by 'adding subjects to groups' on web interface page //Admin / Permissions//) cannot be used. See [trac:ticket:5648 #5648] for details about this missing feature ||

  For example, if the `authz_file` contains:
  {{{
  [wiki:WikiStart@*]
  * = WIKI_VIEW

  [wiki:PrivatePage@*]
  john = WIKI_VIEW
  * = !WIKI_VIEW
  }}}
  and the default permissions are set like this:
  {{{
  john           WIKI_VIEW
  jack           WIKI_VIEW
  # anonymous has no WIKI_VIEW
  }}}

  Then: 
    * All versions of WikiStart will be viewable by everybody (including anonymous)
    * !PrivatePage will be viewable only by john
    * other pages will be viewable only by john and jack

  Groups:
  {{{
  [groups]
  admins = john, jack
  devs = alice, bob

  [wiki:Dev@*]
  @admins = TRAC_ADMIN
  @devs = WIKI_VIEW
  * =

  [*]
  @admins = TRAC_ADMIN
  * =
  }}}

  Then:
  - everything is blocked (whitelist approach), but
  - admins get all TRAC_ADMIN everywhere and
  - devs can view wiki pages.

  Some repository examples (Browse Source specific):
  {{{
  # A single repository:
  [repository:test_repo@*]
  john = BROWSER_VIEW, FILE_VIEW
  # John has BROWSER_VIEW and FILE_VIEW for the entire test_repo

  # All repositories:
  [repository:*@*]
  jack = BROWSER_VIEW, FILE_VIEW
  # John has BROWSER_VIEW and FILE_VIEW for all repositories
  }}}

  Very fine grain repository access:
  {{{
  # John has BROWSER_VIEW and FILE_VIEW access to trunk/src/some/location/ only
  [repository:test_repo@*/source:trunk/src/some/location/*@*]
  john = BROWSER_VIEW, FILE_VIEW


  # John has BROWSER_VIEW and FILE_VIEW access to only revision 1 of all files at trunk/src/some/location only
  [repository:test_repo@*/source:trunk/src/some/location/*@1]
  john = BROWSER_VIEW, FILE_VIEW


  # John has BROWSER_VIEW and FILE_VIEW access to all revisions of 'somefile' at trunk/src/some/location only 
  [repository:test_repo@*/source:trunk/src/some/location/somefile@*]
  john = BROWSER_VIEW, FILE_VIEW


  # John has BROWSER_VIEW and FILE_VIEW access to only revision 1 of 'somefile' at trunk/src/some/location only
  [repository:test_repo@*/source:trunk/src/some/location/somefile@1]
  john = BROWSER_VIEW, FILE_VIEW
  }}}

  Note: In order for Timeline to work/visible for John, we must add CHANGESET_VIEW to the above permission list.


  ==== Missing Features ====
  Although possible with the !DefaultPermissionPolicy handling (see Admin panel), fine-grained permissions still miss those grouping features (see [trac:ticket:9573 #9573], [trac:ticket:5648 #5648]). Patches are partially available, see forgotten authz_policy.2.patch  part of [trac:ticket:6680 #6680]).

  You cannot do the following:
  {{{
  [groups]
  team1 = a, b, c
  team2 = d, e, f
  team3 = g, h, i
  departmentA = team1, team2
  }}}

  Permission groups are not supported either. You cannot do the following:
  {{{
  [groups]
  permission_level_1 = WIKI_VIEW, TICKET_VIEW
  permission_level_2  = permission_level_1, WIKI_MODIFY, TICKET_MODIFY
  [*]
  @team1 = permission_level_1
  @team2 = permission_level_2
  @team3 = permission_level_2, TICKET_CREATE
  }}}

  === !AuthzSourcePolicy  (mod_authz_svn-like permission policy) === #AuthzSourcePolicy

  At the time of this writing, the old fine grained permissions system from Trac 0.11 and before used for restricting access to the repository has  been converted to a permission policy component, but from the user point of view, this makes little if no difference.

  That kind of fine-grained permission control needs a definition file, which is the one used by Subversion's mod_authz_svn. 
  More information about this file format and about its usage in Subversion is available in the  [http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbasedauthz.html Path-Based Authorization] section in the Server Configuration chapter of the svn book.

  Example:
  {{{
  [/]
  * = r

  [/branches/calc/bug-142]
  harry = rw
  sally = r

  [/branches/calc/bug-142/secret]
  harry =
  }}}

   * '''/''' = ''Everyone has read access by default''
   * '''/branches/calc/bug-142''' = ''harry has read/write access, sally read only''
   * '''/branches/calc/bug-142/secret''' = ''harry has no access, sally has read access (inherited as a sub folder permission)''

  ==== Trac Configuration ====

  To activate fine grained permissions you __must__ specify the {{{authz_file}}} option in the {{{[trac]}}} section of trac.ini. If this option is set to null or not specified the permissions will not be used.

  {{{
  [trac]
  authz_file = /path/to/svnaccessfile
  }}}

  If you want to support the use of the `[`''modulename''`:/`''some''`/`''path''`]` syntax within the `authz_file`, add 

  {{{
  authz_module_name = modulename
  }}}

  where ''modulename'' refers to the same repository indicated by the `repository_dir` entry in the `[trac]` section. As an example, if the `repository_dir` entry in the `[trac]` section is {{{/srv/active/svn/blahblah}}}, that would yield the following:

  {{{ 
  [trac]
  authz_file = /path/to/svnaccessfile
  authz_module_name = blahblah
  ...
  repository_dir = /srv/active/svn/blahblah 
  }}}

  where the svn access file, {{{/path/to/svnaccessfile}}}, contains entries such as {{{[blahblah:/some/path]}}}.

  '''Note:''' Usernames inside the Authz file __must__ be the same as those used inside trac. 

  As of version 0.12, make sure you have ''!AuthzSourcePolicy'' included in the permission_policies list in trac.ini, otherwise the authz permissions file will be ignored.

  {{{ 
  [trac]
  permission_policies = AuthzSourcePolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
  }}}

  ==== Subversion Configuration ====

  The same access file is typically applied to the corresponding Subversion repository using an Apache directive like this:
  {{{
  <Location /repos>
    DAV svn
    SVNParentPath /usr/local/svn

    # our access control policy
    AuthzSVNAccessFile /path/to/svnaccessfile
  </Location>
  }}}

  For information about how to restrict access to entire projects in a multiple project environment see [trac:wiki:TracMultipleProjectsSVNAccess]

  == Debugging permissions
  In trac.ini set:
  {{{
  [logging]
  log_file = trac.log
  log_level = DEBUG
  log_type = file
  }}}

  And watch:
  {{{
  tail -n 0 -f log/trac.log | egrep '\[perm\]|\[authz_policy\]'
  }}}

  to understand what checks are being performed. See the sourced documentation of the plugin for more info.


  ----
  See also: TracPermissions,
  [http://trac-hacks.org/wiki/FineGrainedPageAuthzEditorPlugin TracHacks:FineGrainedPageAuthzEditorPlugin] for a simple editor plugin.


name: WikiRestructuredTextLinks
author: trac
ipnr: 127.0.0.1
text:
  = TracLinks in reStructuredText =

  This document illustrates how to use the `:trac:` role in reStructuredText. The page is written like:

  {{{
  {{{
  #!rst 
  Examples:

   * Tickets: :trac:`#1` or :trac:`ticket:1`
   * Ticket comments: :trac:`comment:ticket:1:2`
   * Reports: :trac:`{1}` or :trac:`report:1`
   * Changesets: :trac:`r1`, :trac:`[1]` or :trac:`changeset:1`
   * Revision log: :trac:`r1:3`, :trac:`[1:3]` or :trac:`log:@1:3`, :trac:`log:trunk@1:3`
   * Diffs (since version 0.10): :trac:`diff:@20:30`, :trac:`diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default` or :trac:`diff:trunk/trac@3538//sandbox/vc-refactoring/trac@3539`
   * Wiki pages: :trac:`CamelCase` or :trac:`wiki:CamelCase`
   * Milestones: :trac:`milestone:1.0`
   * Attachment: :trac:`attachment:ticket:944:attachment.1073.diff`
   * Files: :trac:`source:trunk/COPYING`
   * A specific file revision: :trac:`source:/trunk/COPYING@200`
   * A particular line of a specific file revision: :trac:`source:/trunk/COPYING@200#L25`

  An explicit label can be specified, separated from the link by a space:

   * See :trac:`#1 ticket 1` and the :trac:`source:trunk/COPYING license`.
  }}}
  }}}

  Provided you have docutils installed, the above block will render as:
  ----
  {{{
  #!rst 
  Examples:

   * Tickets: :trac:`#1` or :trac:`ticket:1`
   * Ticket comments: :trac:`comment:ticket:1:2`
   * Reports: :trac:`{1}` or :trac:`report:1`
   * Changesets: :trac:`r1`, :trac:`[1]` or :trac:`changeset:1`
   * Revision log: :trac:`r1:3`, :trac:`[1:3]` or :trac:`log:@1:3`, :trac:`log:trunk@1:3`
   * Diffs (since version 0.10): :trac:`diff:@20:30`, :trac:`diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default` or :trac:`diff:trunk/trac@3538//sandbox/vc-refactoring/trac@3539`
   * Wiki pages: :trac:`CamelCase` or :trac:`wiki:CamelCase`
   * Milestones: :trac:`milestone:1.0`
   * Attachment: :trac:`attachment:ticket:944:attachment.1073.diff`
   * Files: :trac:`source:trunk/COPYING`
   * A specific file revision: :trac:`source:/trunk/COPYING@200`
   * A particular line of a specific file revision: :trac:`source:/trunk/COPYING@200#L25`

  An explicit label can be specified, separated from the link by a space:

   * See :trac:`#1 ticket 1` and the :trac:`source:trunk/COPYING license`.
  }}}
  ----

  Note also that any of the above could have been written using substitution references and the `trac::` directive:
  {{{
  {{{
  #!rst
  See |ticket123|.

   .. |ticket123| trac:: ticket:123 this ticket
  }}}
  }}}

  This renders as:
  ----

  {{{
  #!rst
  See |ticket123|.

   .. |ticket123| trac:: ticket:123 this ticket
  }}}

  ----
  See also: WikiRestructuredText, TracLinks


name: SandBox
author: trac
ipnr: 127.0.0.1
text:
  = The Sandbox =

  This is just a page to practice and learn WikiFormatting. 

  Go ahead, edit it freely.


name: TracQuery
author: trac
ipnr: 127.0.0.1
text:
  = Trac Ticket Queries =
  [[TracGuideToc]]

  In addition to [wiki:TracReports reports], Trac provides support for ''custom ticket queries'', used to display lists of tickets meeting a specified set of criteria. 

  To configure and execute a custom query, switch to the ''View Tickets'' module from the navigation bar, and select the ''Custom Query'' link.

  == Filters ==

  When you first go to the query page the default filter will display tickets relevant to you:
   * If logged in then all open tickets it will display open tickets assigned to you.
   * If not logged in but you have specified a name or email address in the preferences then it will display all open tickets where your email (or name if email not defined) is in the CC list.
   * If not logged and no name/email defined in the preferences then all open issues are displayed.

  Current filters can be removed by clicking the button to the left with the minus sign on the label.  New filters are added from the pulldown lists at the bottom corners of the filters box ('And' conditions on the left, 'Or' conditions on the right).  Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''or'' of the criteria.

  You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.

  Once you've edited your filters click the ''Update'' button to refresh your results.

  == Navigating Tickets ==
  Clicking on one of the query results will take you to that ticket.  You can navigate through the results by clicking the ''Next Ticket'' or ''Previous Ticket'' links just below the main menu bar, or click the ''Back to Query'' link to return to the query page.  

  You can safely edit any of the tickets and continue to navigate through the results using the ''!Next/Previous/Back to Query'' links after saving your results.  When you return to the query ''any tickets which were edited'' will be displayed with italicized text.  If one of the tickets was edited such that [[html(<span style="color: grey">it no longer matches the query criteria </span>)]] the text will also be greyed. Lastly, if '''a new ticket matching the query criteria has been created''', it will be shown in bold. 

  The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again.

  == Saving Queries ==

  Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have ''Updated'' the view and then click the ''Save query'' button displayed beneath the results.
  You can also save references to queries in Wiki content, as described below.

  ''Note:'' one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click ''Save query''. This will build the query string for you. All you need to do is remove the extra line breaks.

  ''Note:'' you must have the '''REPORT_CREATE''' permission in order to save queries to the list of default reports. The ''Save query'' button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.


  === Using TracLinks ===

  You may want to save some queries so that you can come back to them later.  You can do this by making a link to the query from any Wiki page.
  {{{
  [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
  }}}

  Which is displayed as:
    [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]

  This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]).

  Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
  {{{
  [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
  }}}

  Which is displayed as:
    [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

  === Using the `[[TicketQuery]]` Macro ===

  The [trac:TicketQuery TicketQuery] macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.

  Example:
  {{{
  [[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
  }}}

  This is displayed as:
    [[TicketQuery(version=0.6|0.7&resolution=duplicate)]]

  Just like the [wiki:TracQuery#UsingTracLinks query: wiki links], the parameter of this macro expects a query string formatted according to the rules of the simple [wiki:TracQuery#QueryLanguage ticket query language]. This also allows displaying the link and description of a single ticket:
  {{{
  [[TicketQuery(id=123)]]
  }}}

  This is displayed as:
    [[TicketQuery(id=123)]]

  A more compact representation without the ticket summaries is also available:
  {{{
  [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
  }}}

  This is displayed as:
    [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

  Finally, if you wish to receive only the number of defects that match the query, use the ``count`` parameter.

  {{{
  [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
  }}}

  This is displayed as:
    [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]

  === Customizing the ''table'' format ===
  You can also customize the columns displayed in the table format (''format=table'') by using ''col=<field>'' - you can specify multiple fields and what order they are displayed by placing pipes (`|`) between the columns like below:

  {{{
  [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
  }}}

  This is displayed as:
  [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

  ==== Full rows ====
  In ''table'' format you can also have full rows by using ''rows=<field>'' like below:

  {{{
  [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]
  }}}

  This is displayed as:
  [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]


  === Query Language ===

  `query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (`&`). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (`|`), meaning that the filter matches any of the values. To include a literal `&` or `|` in a value, escape the character with a backslash (`\`).

  The available operators are:
  || '''`=`''' || the field content exactly matches one of the values ||
  || '''`~=`''' || the field content contains one or more of the values ||
  || '''`^=`''' || the field content starts with one of the values ||
  || '''`$=`''' || the field content ends with one of the values ||

  All of these operators can also be negated:
  || '''`!=`''' || the field content matches none of the values ||
  || '''`!~=`''' || the field content does not contain any of the values ||
  || '''`!^=`''' || the field content does not start with any of the values ||
  || '''`!$=`''' || the field content does not end with any of the values ||

  The date fields `created` and `modified` can be constrained by using the `=` operator and specifying a value containing two dates separated by two dots (`..`). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be left out to avoid having to quote the query string. 
  || '''`created=2007-01-01..2008-01-01`''' || query tickets created in 2007 ||
  || '''`created=lastmonth..thismonth`''' || query tickets created during the previous month ||
  || '''`modified=1weekago..`''' || query tickets that have been modified in the last week ||
  || '''`modified=..30daysago`''' || query tickets that have been inactive for the last 30 days ||

  ----
  See also: TracTickets, TracReports, TracGuide


name: TracLinks
author: trac
ipnr: 127.0.0.1
text:
  = Trac Links =
  [[TracGuideToc]]

  TracLinks are a fundamental feature of Trac, because they allow easy hyperlinking between the various entities in the system—such as tickets, reports, changesets, Wiki pages, milestones, and source files—from anywhere WikiFormatting is used.

  TracLinks are generally of the form '''type:id''' (where ''id'' represents the
  number, name or path of the item) though some frequently used kinds of items
  also have short-hand notations.

  == Where to use TracLinks ==
  You can use TracLinks in:

   * Source code (Subversion) commit messages
   * Wiki pages
   * Full descriptions for tickets, reports and milestones

  and any other text fields explicitly marked as supporting WikiFormatting.

  == Overview ==

  ||= Wiki Markup =||= Display =||
  {{{#!td
   Wiki pages :: `CamelCase` or `wiki:CamelCase`
   Parent page :: `[..]`
   Tickets :: `#1` or `ticket:1`
   Ticket comments :: `comment:1:ticket:2`
   Reports :: `{1}` or `report:1`
   Milestones :: `milestone:1.0`
   Attachment :: `attachment:example.tgz` (for current page attachment), `attachment:attachment.1073.diff:ticket:944` (absolute path)
   Changesets :: `r1`, `[1]`, `changeset:1` or (restricted) `[1/trunk]`, `changeset:1/trunk`
   Revision log :: `r1:3`, `[1:3]` or `log:@1:3`, `log:trunk@1:3`, `[2:5/trunk]`
   Diffs :: `diff:@1:3`, `diff:plugins/0.12/mercurial-plugin@9128:9953`,
            `diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default` 
            or `diff:trunk/trac@3538//sandbox/vc-refactoring@3539`
   Files :: `source:trunk/COPYING`, `source:/trunk/COPYING@200` (at version 200), `source:/trunk/COPYING@200#L25` (at version 200, line 25)
  }}}
  {{{#!td
   Wiki pages :: CamelCase or wiki:CamelCase
   Parent page :: [..]
   Tickets :: #1 or ticket:1
   Ticket comments :: comment:1:ticket:2 
   Reports :: {1} or report:1
   Milestones :: milestone:1.0
   Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path)
   Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk
   Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
   Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953,
            diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default 
            or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
   Files :: source:trunk/COPYING, source:/trunk/COPYING@200 (at version 200), source:/trunk/COPYING@200#L25 (at version 200, line 25)
  }}}

  '''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
  pages whose names do not follow WikiPageNames rules, i.e., single words,
  non-alphabetic characters, etc. See WikiPageNames for more about features specific
  to links to Wiki page names.


  {{{#!table class=""
  |||| Trac links using the full (non-shorthand) notation can also be given a custom link title like this: ||
  {{{#!td
  {{{
  [ticket:1 This is a link to ticket number one] or
  [[ticket:1|This is another link to ticket number one]].
  }}}
  }}}
  {{{#!td
  [ticket:1 This is a link to ticket number one] or
  [[ticket:1|This is another link to ticket number one]].
  }}}
  |--------------------------------------------------------------------------------------
  |||| If the title is omitted, only the id (the part after the colon) is displayed:  ||
  {{{#!td
  {{{
  [ticket:1] or [[ticket:2]]
  }}}
  }}}
  {{{#!td
  [ticket:1] or [[ticket:2]]
  }}}
  |--------------------------------------------------------------------------------------
  |||| `wiki` is the default if the namespace part of a full link is omitted:  || 
  {{{#!td
  {{{
  [SandBox the sandbox] or
  [[SandBox|the sandbox]]
  }}}
  }}}
  {{{#!td
  [SandBox the sandbox] or
  [[SandBox|the sandbox]]
  }}}
  |--------------------------------------------------------------------------------------
  |||| The short form ''realm:target'' can also be wrapped within a <...> pair, [[br]] which allow for arbitrary characters (i.e. anything but >)  ||
  {{{#!td
  {{{
  <wiki:Strange(page@!)>
  }}}
  }}}
  {{{#!td
  <wiki:Strange(page@!)>
  }}}
  }}}

  TracLinks are a very simple idea, but actually allow quite a complex network of information. In practice, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's happening in a project or why a particular change was made.


  == Advanced use of TracLinks ==

  === Relative links ===

  To create a link to a [trac:SubWiki SubWiki]-page just use a '/':
  {{{
   WikiPage/SubWikiPage or ./SubWikiPage
  }}}

  To link from a [trac:SubWiki SubWiki] page to a parent, simply use a '..':
  {{{
    [..] or [[..]]
  }}}
    [..] or [[..]]

  To link from a [trac:SubWiki SubWiki] page to a [=#sibling sibling] page, use a '../':
  {{{
    [../Sibling see next sibling] or [[../Sibling|see next sibling]]
  }}}
    [../Sibling see next sibling] or [[../Sibling|see next sibling]]

  But in practice you often won't need to add the `../` prefix to link to a sibling page.
  For resolving the location of a wiki link, it's the target page closest in the hierarchy
  to the page where the link is written which will be selected. So for example, within 
  a sub-hierarchy, a sibling page will be targeted in preference to a toplevel page.
  This makes it easy to copy or move pages to a sub-hierarchy by [[WikiNewPage#renaming|renaming]] without having to adapt the links.

  In order to link explicitly to a [=#toplevel toplevel] Wiki page,
  use the `wiki:/` prefix.
  Be careful **not** to use the `/` prefix alone, as this corresponds to the
  [#Server-relativelinks] syntax and with such a link you will lack the `/wiki/` 
  part in the resulting URL.

  ''(Changed in 0.11)'' Note that in Trac 0.10, using e.g. `[../newticket]`  may have worked for linking to the `/newticket` top-level URL, but since 0.11, such a link will stay in the wiki namespace and therefore link to a sibling page. 
  See [#Server-relativelinks] for the new syntax.

  === Link anchors ===

  To create a link to a specific anchor in a page, use '#':
  {{{
   [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]
  }}}
    [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]

  Hint: when you move your mouse over the title of a section, a '¶' character will be displayed. This is a link to that specific section and you can use this to copy the `#...` part inside a relative link to an anchor.

  To create a link to the first or last occurrence of a term on a page, use a ''pseudo anchor'' starting with '#/' or '#?':
  {{{
   [#/Milestone first occurrence of Milestone] or
   [#?Milestone last occurrence of Milestone]
  }}}
   [#/Milestone first occurrence of Milestone] or
   [#?Milestone last occurrence of Milestone]
  This will also highlight all other matches on the linked page. By default only case sensitive matches are considered. To include case insensitive matches append '/i':
  {{{
   [#/Milestone/i first occurrence of Milestone or milestone] or
   [#?Milestone/i last occurrence of Milestone or milestone]
  }}}
   [#/Milestone/i first occurrence of Milestone or milestone] or
   [#?Milestone/i last occurrence of Milestone or milestone]

  ''(since Trac 1.0)''

  Such anchors can be very useful for linking to specific lines in a file in the source browser:
  {{{
   [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or
   [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47]
  }}}
   [trac:source:tags/trac-0.12/trac/wiki/api.py#L127 Line 127] or
   [trac:source:tags/trac-0.12/trac/ticket/roadmap.py#L47 Line 47]
  (Hint: The line numbers displayed in the source browser are links to anchors on the respective lines.)

  Since such links become outdated when the file changes, it can be useful to link using a '#/' pseudo anchor instead:
  {{{
   [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or
   [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]
  }}}
   [trac:source:trunk/trac/wiki/api.py#/IWikiSyntaxProvider IWikiSyntaxProvider] or
   [trac:source:trunk/trac/env.py#/ISystemInfoProvider ISystemInfoProvider]

  === InterWiki links ===

  Other prefixes can be defined freely and made to point to resources in other Web applications. The definition of those prefixes as well as the URLs of the corresponding Web applications is defined in a special Wiki page, the InterMapTxt page. Note that while this could be used to create links to other Trac environments, there's a more specialized way to register other Trac environments which offers greater flexibility.

  === InterTrac links ===

  This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.

  Any type of Trac link can be written in one Trac environment and actually refer to resources in another Trac environment. All that is required is to prefix the Trac link with the name of the other Trac environment followed by a colon. The other Trac environment must be registered on the InterTrac page. 

  A distinctive advantage of InterTrac links over InterWiki links is that the shorthand form of Trac links (e.g. `{}`, `r`, `#`) can also be used. For example if T was set as an alias for Trac, links to Trac tickets can be written #T234, links to Trac changesets can be written [trac 1508].
  See InterTrac for the complete details. 

  === Server-relative links ===

  It is often useful to be able to link to objects in your project that
  have no built-in Trac linking mechanism, such as static resources, `newticket`,
  a shared `/register` page on the server, etc.

  To link to resources inside the project, use either an absolute path from the project root, 
  or a relative link from the URL of the current page (''Changed in 0.11''):

  {{{
  [/newticket Create a new ticket] or [[//newticket|Create a new ticket]]
  [/ home] or [[/|home]]
  }}}

  Display: [/newticket Create a new ticket] or [[//newticket|Create a new ticket]]
  [/ home] or [[/|home]]

  To link to another location on the server (possibly outside the project but on the same host), use the `//` prefix (''Changed in 0.11''):

  {{{
  [//register Register Here] or [[//register|Register Here]]
  }}}

  Display: [//register Register Here] or [[//register|Register Here]]

  === Quoting space in TracLinks ===

  Immediately after a TracLinks prefix, targets containing space characters should
  be enclosed in a pair of quotes or double quotes.
  Examples:
   * !wiki:"The whitespace convention"
   * !attachment:'the file.txt' or
   * !attachment:"the file.txt" 
   * !attachment:"the file.txt:ticket:123" 

  Note that by using [trac:WikiCreole] style links, it's quite natural to write links containing spaces:
   * ![[The whitespace convention]]
   * ![[attachment:the file.txt]]

  === Escaping Links ===

  To prevent parsing of a !TracLink, you can escape it by preceding it with a '!' (exclamation mark).
  {{{
   !NoLinkHere.
   ![42] is not a link either.
  }}}

  Display:
   !NoLinkHere.
   ![42] is not a link either.


  === Parameterized Trac links ===

  Many Trac resources have more than one way to be rendered, depending on some extra parameters. For example, a Wiki page can accept a `version` or a `format` parameter, a report can make use of dynamic variables, etc.

  Trac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples:
   - `wiki:WikiStart?format=txt`
   - `ticket:1?version=1`
   - `[/newticket?component=module1 create a ticket for module1]`
   - `[/newticket?summary=Add+short+description+here create a ticket with URL with spaces]`


  == TracLinks Reference ==
  The following sections describe the individual link types in detail, as well as notes on advanced usage of links.

  === attachment: links ===

  The link syntax for attachments is as follows:
   * !attachment:the_file.txt creates a link to the attachment the_file.txt of the current object
   * !attachment:the_file.txt:wiki:MyPage creates a link to the attachment the_file.txt of the !MyPage wiki page
   * !attachment:the_file.txt:ticket:753 creates a link to the attachment the_file.txt of the ticket 753

  Note that the older way, putting the filename at the end, is still supported: !attachment:ticket:753:the_file.txt.

  If you'd like to create a direct link to the content of the attached file instead of a link to the attachment page, simply use `raw-attachment:` instead of `attachment:`.

  This can be useful for pointing directly to an HTML document, for example. Note that for this use case, you'd have to allow the web browser to render the content by setting `[attachment] render_unsafe_content = yes` (see TracIni#attachment-section). Caveat: only do that in environments for which you're 100% confident you can trust the people who are able to attach files, as otherwise this would open up your site to [wikipedia:Cross-site_scripting cross-site scripting] attacks.

  See also [#export:links].

  === comment: links ===

  When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment.
  It is possible to link to a comment of a specific ticket from anywhere using one of the following syntax:
   - `comment:3:ticket:123` 
   - `ticket:123#comment:3` (note that you can't write `#123#!comment:3`!)
  It is also possible to link to the ticket's description using one of the following syntax:
   - `comment:description` (within the ticket)
   - `comment:description:ticket:123`
   - `ticket:123#comment:description`

  === htdocs: links ===

  Use `htdocs:path/to/file` to reference files in the `htdocs` directory of the Trac environment, the [TracEnvironment#DirectoryStructure web resource directory].

  === query: links ===

  See TracQuery#UsingTracLinks and [#ticket:links].

  === search: links ===

  See TracSearch#SearchLinks 

  === ticket: links ===
   ''alias:'' `bug:`

  Besides the obvious `ticket:id` form, it is also possible to specify a list of tickets or even a range of tickets instead of the `id`. This generates a link to a custom query view containing this fixed set of tickets.

  Example: 
   - `ticket:5000-6000`
   - `ticket:1,150`

  ''(since Trac 0.11)''

  === timeline: links ===

  Links to the timeline can be created by specifying a date in the ISO:8601 format. The date can be optionally followed by a time specification. The time is interpreted as being UTC time, but alternatively you can specify your local time, followed by your timezone if you don't want to compute the UTC time.

  Examples:
   - `timeline:2008-01-29`
   - `timeline:2008-01-29T15:48`
   - `timeline:2008-01-29T15:48Z`
   - `timeline:2008-01-29T16:48+01`

  ''(since Trac 0.11)''

  === wiki: links ===

  See WikiPageNames and [#QuotingspaceinTracLinks quoting space in TracLinks] above. It is possible to create a link to a specific page revision using the syntax WikiStart@1.

  === Version Control related links ===

  It should be noted that multiple repository support works by creating a kind of virtual namespace for versioned files in which the toplevel folders correspond to the repository names. Therefore, in presence of multiple repositories, a ''/path'' specification in the syntax of links detailed below should start with the name of the repository. If omitted, the default repository is used. In case a toplevel folder of the default repository has the same name as a repository, the latter "wins". One can always access such folder by fully qualifying it (the default repository can be an alias of a named repository, or conversely, it is always possible to create an alias for the default repository, ask your Trac administrator).

  For example, `source:/trunk/COPYING` targets the path `/trunk/COPYING` in the default repository, whereas `source:/projectA/trunk/COPYING` targets the path `/trunk/COPYING` in the repository named `projectA`. This can be the same file if `'projectA'` is an alias to the default repository or if `''` (the default repository) is an alias to `'projectA'`.

  ==== source: links ====
   ''aliases:'' `browser:`, `repos:`

  The default behavior for a source:/some/path link is to open the browser in that directory directory 
  if the path points to a directory or to show the latest content of the file.

  It's also possible to link directly to a specific revision of a file like this:
   - `source:/some/file@123` - link to the file's revision 123
   - `source:/some/file@head` - link explicitly to the latest revision of the file

  If the revision is specified, one can even link to a specific line number:
   - `source:/some/file@123#L10`
   - `source:/tag/0.10@head#L10`

  Finally, one can also highlight an arbitrary set of lines:
   - `source:/some/file@123:10-20,100,103#L99` - highlight lines 10 to 20, and lines 100 and 103.
     ''(since 0.11)''

  Note that in presence of multiple repositories, the name of the repository is simply integrated in the path you specify for `source:` (e.g. `source:reponame/trunk/README`). ''(since 0.12)''

  ==== export: links ====

  To force the download of a file in the repository, as opposed to displaying it in the browser, use the `export` link.  Several forms are available:
   * `export:/some/file` - get the HEAD revision of the specified file
   * `export:123:/some/file` - get revision 123 of the specified file
   * `export:/some/file@123` - get revision 123 of the specified file

  This can be very useful for displaying XML or HTML documentation with correct stylesheets and images, in case that has been checked in into the repository. Note that for this use case, you'd have to allow the web browser to render the content by setting `[browser] render_unsafe_content = yes` (see TracIni#browser-section), otherwise Trac will force the files to be downloaded as attachments for security concerns. 

  If the path is to a directory in the repository instead of a specific file, the source browser will be used to display the directory (identical to the result of `source:/some/dir`).

  ==== log: links ====

  The `log:` links are used to display revision ranges. In its simplest form, it can link to the latest revisions of the specified path, but it can also support displaying an arbitrary set of revisions.
   - `log:/` - the latest revisions starting at the root of the repository
   - `log:/trunk/tools` - the latest revisions in `trunk/tools`
   - `log:/trunk/tools@10000` - the revisions in `trunk/tools` starting from  revision 10000
   - `log:@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 
   - `log:/trunk/tools@20788,20791:20795` - list revision 20788 and the revisions from 20791 to 20795 which affect the given path

  There are short forms for revision ranges as well:
   - `[20788,20791:20795]`
   - `[20788,20791:20795/trunk/tools]`
   - `r20791:20795` (but not `r20788,20791:20795` nor `r20791:20795/trunk`)

  Finally, note that in all of the above, a revision range can be written either as `x:y` or `x-y`.

  In the presence of multiple repositories, the name of the repository should be specified as the first part of the path, e.g. `log:repos/branches` or `[20-40/repos]`.

  ----
  See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki
   


name: TracPermissions
author: trac
ipnr: 127.0.0.1
text:
  = Trac Permissions =
  [[TracGuideToc]]

  Trac uses a simple, case sensitive, permission system to control what users can and can't access.

  Permission privileges are managed using the [TracAdmin trac-admin] tool or (new in version 0.11) the ''General / Permissions'' panel in the ''Admin'' tab of the web interface.

  In addition to the default permission policy described in this page, it is possible to activate additional permission policies by enabling plugins and listing them in the `[trac] permission_policies` configuration entry in the TracIni. See TracFineGrainedPermissions for more details.

  Non-authenticated users accessing the system are assigned the name "anonymous". Assign permissions to the "anonymous" user to set privileges for anonymous/guest users. The parts of Trac that a user does not have the privileges for will not be displayed in the navigation.
  In addition to these privileges, users can be granted additional individual rights in effect when authenticated and logged into the system. All logged in users belong to the virtual group "authenticated", which inherits permissions from "anonymous".

  == Graphical Admin Tab ==
  ''This feature is new in version 0.11.''

  To access this tab, a user must have one of the following permissions: `TRAC_ADMIN`, `PERMISSION_ADMIN`, `PERMISSION_ADD`, `PERMISSION_REMOVE`. The permissions can granted using the `trac-admin` command (more on `trac-admin` below):
  {{{
    $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN
  }}}

  Then, the user `bob` will be able to see the Admin tab, and can then access the permissions menu. This menu will allow you to perform all the following actions, but from the browser without requiring root access to the server (just the correct permissions for your user account). '''Use at least one lowercase character in user names, as all-uppercase names are reserved for permissions.'''

   1. [[Image(htdocs:../common/guide/admin.png)]]
   1. [[Image(htdocs:../common/guide/admin-permissions.png)]]
   1. [[Image(htdocs:../common/guide/admin-permissions-TICKET_ADMIN.png)]]

  An easy way to quickly secure a new Trac install is to run the above command on the anonymous user, install the [http://trac-hacks.org/wiki/AccountManagerPlugin AccountManagerPlugin], create a new admin account graphically and then remove the TRAC_ADMIN permission from the anonymous user.

  == Available Privileges ==

  To enable all privileges for a user, use the `TRAC_ADMIN` permission. Having `TRAC_ADMIN` is like being `root` on a *NIX system: it will allow you to perform any operation.

  Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac ('''note that the privilege names are case-sensitive'''):

  === Repository Browser ===

  || `BROWSER_VIEW` || View directory listings in the [wiki:TracBrowser repository browser] ||
  || `LOG_VIEW` || View revision logs of files and directories in the [wiki:TracBrowser repository browser] ||
  || `FILE_VIEW` || View files in the [wiki:TracBrowser repository browser] ||
  || `CHANGESET_VIEW` || View [wiki:TracChangeset repository check-ins] ||

  === Ticket System ===

  || `TICKET_VIEW` || View existing [wiki:TracTickets tickets] and perform [wiki:TracQuery ticket queries] ||
  || `TICKET_CREATE` || Create new [wiki:TracTickets tickets] ||
  || `TICKET_APPEND` || Add comments or attachments to [wiki:TracTickets tickets] ||
  || `TICKET_CHGPROP` || Modify [wiki:TracTickets ticket] properties (priority, assignment, keywords, etc.) with the following exceptions: edit description field, add/remove other users from cc field when logged in, and set email to pref ||
  || `TICKET_MODIFY` || Includes both `TICKET_APPEND` and `TICKET_CHGPROP`, and in addition allows resolving [wiki:TracTickets tickets]. Tickets can be assigned to users through a [TracTickets#Assign-toasDrop-DownList drop-down list] when the list of possible owners has been restricted. ||
  || `TICKET_EDIT_CC` || Full modify cc field ||
  || `TICKET_EDIT_DESCRIPTION` || Modify description field ||
  || `TICKET_EDIT_COMMENT` || Modify comments ||
  || `TICKET_BATCH_MODIFY` || [wiki:TracBatchModify Batch modify] tickets ||
  || `TICKET_ADMIN` || All `TICKET_*` permissions, plus the deletion of ticket attachments and modification of the reporter and description fields. It also allows managing ticket properties in the WebAdmin panel. ||

  Attention: the "view tickets" button appears with the `REPORT_VIEW` permission.

  === Roadmap ===

  || `MILESTONE_VIEW` || View milestones and assign tickets to milestones. ||
  || `MILESTONE_CREATE` || Create a new milestone ||
  || `MILESTONE_MODIFY` || Modify existing milestones ||
  || `MILESTONE_DELETE` || Delete milestones ||
  || `MILESTONE_ADMIN` || All `MILESTONE_*` permissions ||
  || `ROADMAP_VIEW` || View the [wiki:TracRoadmap roadmap] page, is not (yet) the same as MILESTONE_VIEW, see [trac:#4292 #4292] ||
  || `ROADMAP_ADMIN` || to be removed with [trac:#3022 #3022], replaced by MILESTONE_ADMIN ||

  === Reports ===

  || `REPORT_VIEW` || View [wiki:TracReports reports], i.e. the "view tickets" link. ||
  || `REPORT_SQL_VIEW` || View the underlying SQL query of a [wiki:TracReports report] ||
  || `REPORT_CREATE` || Create new [wiki:TracReports reports] ||
  || `REPORT_MODIFY` || Modify existing [wiki:TracReports reports] ||
  || `REPORT_DELETE` || Delete [wiki:TracReports reports] ||
  || `REPORT_ADMIN` || All `REPORT_*` permissions ||

  === Wiki System ===

  || `WIKI_VIEW` || View existing [wiki:TracWiki wiki] pages ||
  || `WIKI_CREATE` || Create new [wiki:TracWiki wiki] pages ||
  || `WIKI_MODIFY` || Change [wiki:TracWiki wiki] pages ||
  || `WIKI_RENAME` || Rename [wiki:TracWiki wiki] pages ||
  || `WIKI_DELETE` || Delete [wiki:TracWiki wiki] pages and attachments ||
  || `WIKI_ADMIN` || All `WIKI_*` permissions, plus the management of ''readonly'' pages. ||

  === Permissions ===

  || `PERMISSION_GRANT` || add/grant a permission ||
  || `PERMISSION_REVOKE` || remove/revoke a permission ||
  || `PERMISSION_ADMIN` || All `PERMISSION_*` permissions ||

  === Others ===

  || `TIMELINE_VIEW` || View the [wiki:TracTimeline timeline] page ||
  || `SEARCH_VIEW` || View and execute [wiki:TracSearch search] queries ||
  || `CONFIG_VIEW` || Enables additional pages on ''About Trac'' that show the current configuration or the list of installed plugins ||
  || `EMAIL_VIEW` || Shows email addresses even if [wiki:TracIni#trac-section trac show_email_addresses] configuration option is false ||

  == Creating New Privileges ==

  To create custom permissions, for example to be used in a custom workflow, enable the optional [trac:ExtraPermissionsProvider tracopt.perm.config_perm_provider.ExtraPermissionsProvider] component in the "Plugins" admin panel, and add the desired permissions to the `[extra-permissions]` section in your [wiki:TracIni#extra-permissions-section trac.ini]. For more information, please refer to the documentation of the component in the admin panel.

  == Granting Privileges ==

  You grant privileges to users using [wiki:TracAdmin trac-admin]. The current set of privileges can be listed with the following command:
  {{{
    $ trac-admin /path/to/projenv permission list
  }}}

  This command will allow the user ''bob'' to delete reports:
  {{{
    $ trac-admin /path/to/projenv permission add bob REPORT_DELETE
  }}}

  The `permission add` command also accepts multiple privilege names:
  {{{
    $ trac-admin /path/to/projenv permission add bob REPORT_DELETE WIKI_CREATE
  }}}

  Or add all privileges:
  {{{
    $ trac-admin /path/to/projenv permission add bob TRAC_ADMIN
  }}}

  == Permission Groups ==

  There are two built-in groups, "authenticated" and "anonymous".
  Any user who has not logged in is automatically in the "anonymous" group.
  Any user who has logged in is also in the "authenticated" group.
  The "authenticated" group inherits permissions from the "anonymous" group.
  For example, if the "anonymous" group has permission WIKI_MODIFY, 
  it is not necessary to add the WIKI_MODIFY permission to the "authenticated" group as well.

  Custom groups may be defined that inherit permissions from the two built-in groups.

  Permissions can be grouped together to form roles such as ''developer'', ''admin'', etc.
  {{{
    $ trac-admin /path/to/projenv permission add developer WIKI_ADMIN
    $ trac-admin /path/to/projenv permission add developer REPORT_ADMIN
    $ trac-admin /path/to/projenv permission add developer TICKET_MODIFY
    $ trac-admin /path/to/projenv permission add bob developer
    $ trac-admin /path/to/projenv permission add john developer
  }}}

  Group membership can be checked by doing a {{{permission list}}} with no further arguments; the resulting output will include group memberships. '''Use at least one lowercase character in group names, as all-uppercase names are reserved for permissions'''.

  == Adding a New Group and Permissions ==
  Permission groups can be created by assigning a user to a group you wish to create, then assign permissions to that group.

  The following will add ''bob'' to the new group called ''beta_testers'' and then will assign WIKI_ADMIN permissions to that group. (Thus, ''bob'' will inherit the WIKI_ADMIN permission)
  {{{ 
     $ trac-admin /path/to/projenv permission add bob beta_testers
     $ trac-admin /path/to/projenv permission add beta_testers WIKI_ADMIN

  }}}

  == Removing Permissions ==

  Permissions can be removed using the 'remove' command. For example:

  This command will prevent the user ''bob'' from deleting reports:
  {{{
    $ trac-admin /path/to/projenv permission remove bob REPORT_DELETE
  }}}

  Just like `permission add`, this command accepts multiple privilege names.

  You can also remove all privileges for a specific user:
  {{{
    $ trac-admin /path/to/projenv permission remove bob '*'
  }}}

  Or one privilege for all users:
  {{{
    $ trac-admin /path/to/projenv permission remove '*' REPORT_ADMIN
  }}}

  == Default Permissions ==

  By default on a new Trac installation, the `anonymous` user will have ''view'' access to everything in Trac, but will not be able to create or modify anything.
  On the other hand, the `authenticated` users will have the permissions to ''create and modify tickets and wiki pages''.

  '''anonymous'''
  {{{
   BROWSER_VIEW 
   CHANGESET_VIEW 
   FILE_VIEW 
   LOG_VIEW 
   MILESTONE_VIEW 
   REPORT_SQL_VIEW 
   REPORT_VIEW 
   ROADMAP_VIEW 
   SEARCH_VIEW 
   TICKET_VIEW 
   TIMELINE_VIEW
   WIKI_VIEW
  }}}

  '''authenticated'''
  {{{
   TICKET_CREATE 
   TICKET_MODIFY 
   WIKI_CREATE 
   WIKI_MODIFY  
  }}}
  ----
  See also: TracAdmin, TracGuide and TracFineGrainedPermissions


name: TracWorkflow
author: trac
ipnr: 127.0.0.1
text:
  = The Trac Ticket Workflow System =
  [[TracGuideToc]]

  The Trac issue database provides a configurable workflow.

  == The Default Ticket Workflow ==
  === Environments upgraded from 0.10 ===
  When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section.
  The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10.

  Graphically, that looks like this:

  {{{#!Workflow width=500 height=240
  leave = * -> *
  leave.operations = leave_status
  leave.default = 1
  accept = new -> assigned
  accept.permissions = TICKET_MODIFY
  accept.operations = set_owner_to_self
  resolve = new,assigned,reopened -> closed
  resolve.permissions = TICKET_MODIFY
  resolve.operations = set_resolution
  reassign = new,assigned,reopened -> new
  reassign.permissions = TICKET_MODIFY
  reassign.operations = set_owner
  reopen = closed -> reopened
  reopen.permissions = TICKET_CREATE
  reopen.operations = del_resolution
  }}}

  There are some significant "warts" in this; such as accepting a ticket sets it to 'assigned' state, and assigning a ticket sets it to 'new' state.  Perfectly obvious, right?
  So you will probably want to migrate to "basic" workflow; [trac:source:trunk/contrib/workflow/migrate_original_to_basic.py contrib/workflow/migrate_original_to_basic.py] may be helpful.

  === Environments created with 0.11 ===
  When a new environment is created, a default workflow is configured in your trac.ini.  This workflow is the basic workflow (described in `basic-workflow.ini`), which is somewhat different from the workflow of the 0.10 releases.

  Graphically, it looks like this:

  {{{#!Workflow width=700 height=300
  leave = * -> *
  leave.operations = leave_status
  leave.default = 1
  accept = new,assigned,accepted,reopened -> accepted
  accept.permissions = TICKET_MODIFY
  accept.operations = set_owner_to_self
  resolve = new,assigned,accepted,reopened -> closed
  resolve.permissions = TICKET_MODIFY
  resolve.operations = set_resolution
  reassign = new,assigned,accepted,reopened -> assigned
  reassign.permissions = TICKET_MODIFY
  reassign.operations = set_owner
  reopen = closed -> reopened
  reopen.permissions = TICKET_CREATE
  reopen.operations = del_resolution
  }}}

  == Additional Ticket Workflows ==

  There are several example workflows provided in the Trac source tree; look in [trac:source:trunk/contrib/workflow contrib/workflow] for `.ini` config sections.  One of those may be a good match for what you want. They can be pasted into the `[ticket-workflow]` section of your `trac.ini` file. However if you have existing tickets then there may be issues if those tickets have states that are not in the new workflow. 

  Here are some [http://trac.edgewall.org/wiki/WorkFlow/Examples diagrams] of the above examples.

  == Basic Ticket Workflow Customization ==

  Note: Ticket "statuses" or "states" are not separately defined. The states a ticket can be in are automatically generated by the transitions defined in a workflow. Therefore, creating a new ticket state simply requires defining a state transition in the workflow that starts or ends with that state.

  Create a `[ticket-workflow]` section in `trac.ini`.
  Within this section, each entry is an action that may be taken on a ticket. 
  For example, consider the `accept` action from `simple-workflow.ini`:
  {{{
  accept = new,accepted -> accepted
  accept.permissions = TICKET_MODIFY
  accept.operations = set_owner_to_self
  }}}
  The first line in this example defines the `accept` action, along with the states the action is valid in (`new` and `accepted`), and the new state of the ticket when the action is taken (`accepted`).
  The `accept.permissions` line specifies what permissions the user must have to use this action.
  The `accept.operations` line specifies changes that will be made to the ticket in addition to the status change when this action is taken.  In this case, when a user clicks on `accept`, the ticket owner field is updated to the logged in user.  Multiple operations may be specified in a comma separated list.

  The available operations are:
   - del_owner -- Clear the owner field.
   - set_owner -- Sets the owner to the selected or entered owner.
     - ''actionname''`.set_owner` may optionally be set to a comma delimited list or a single value.
   - set_owner_to_self -- Sets the owner to the logged in user.
   - del_resolution -- Clears the resolution field
   - set_resolution -- Sets the resolution to the selected value.
     - ''actionname''`.set_resolution` may optionally be set to a comma delimited list or a single value. Example:
       {{{
  resolve_new = new -> closed
  resolve_new.name = resolve
  resolve_new.operations = set_resolution
  resolve_new.permissions = TICKET_MODIFY
  resolve_new.set_resolution = invalid,wontfix
       }}}
   - leave_status -- Displays "leave as <current status>" and makes no change to the ticket.
  '''Note:''' Specifying conflicting operations (such as `set_owner` and `del_owner`) has unspecified results.

  {{{
  resolve_accepted = accepted -> closed
  resolve_accepted.name = resolve
  resolve_accepted.permissions = TICKET_MODIFY
  resolve_accepted.operations = set_resolution
  }}}

  In this example, we see the `.name` attribute used.  The action here is `resolve_accepted`, but it will be presented to the user as `resolve`.

  For actions that should be available in all states, `*` may be used in place of the state.  The obvious example is the `leave` action:
  {{{
  leave = * -> *
  leave.operations = leave_status
  leave.default = 1
  }}}
  This also shows the use of the `.default` attribute.  This value is expected to be an integer, and the order in which the actions are displayed is determined by this value.  The action with the highest `.default` value is listed first, and is selected by default.  The rest of the actions are listed in order of decreasing `.default` values.
  If not specified for an action, `.default` is 0.  The value may be negative.

  There are a couple of hard-coded constraints to the workflow.  In particular, tickets are created with status `new`, and tickets are expected to have a `closed` state.  Further, the default reports/queries treat any state other than `closed` as an open state.

  While creating or modifying a ticket workflow, `contrib/workflow/workflow_parser.py` may be useful.  It can create `.dot` files that [http://www.graphviz.org GraphViz] understands to provide a visual description of the workflow.

  This can be done as follows (your install path may be different).
  {{{
  cd /var/local/trac_devel/contrib/workflow/
  sudo ./showworkflow /srv/trac/PlannerSuite/conf/trac.ini
  }}}
  And then open up the resulting `trac.pdf` file created by the script (it will be in the same directory as the `trac.ini` file).

  An online copy of the workflow parser is available at http://foss.wush.net/cgi-bin/visual-workflow.pl

  After you have changed a workflow, you need to restart apache for the changes to take effect. This is important, because the changes will still show up when you run your script, but all the old workflow steps will still be there until the server is restarted.

  == Example: Adding optional Testing with Workflow ==

  By adding the following to your [ticket-workflow] section of trac.ini you get optional testing.  When the ticket is in new, accepted or needs_work status you can choose to submit it for testing.  When it's in the testing status the user gets the option to reject it and send it back to needs_work, or pass the testing and send it along to closed.  If they accept it then it gets automatically marked as closed and the resolution is set to fixed.  Since all the old work flow remains, a ticket can skip this entire section.

  {{{
  testing = new,accepted,needs_work,assigned,reopened -> testing
  testing.name = Submit to reporter for testing
  testing.permissions = TICKET_MODIFY

  reject = testing -> needs_work
  reject.name = Failed testing, return to developer

  pass = testing -> closed
  pass.name = Passes Testing
  pass.operations = set_resolution
  pass.set_resolution = fixed
  }}}

  === How to combine the `tracopt.ticket.commit_updater` with the testing workflow ===

  The [[trac:source:trunk/tracopt/ticket/commit_updater.py|tracopt.ticket.commit_updater]] is the optional component that [[TracRepositoryAdmin#trac-post-commit-hook|replaces the old trac-post-commit-hook]], in Trac 0.12.

  By default it reacts on some keywords found in changeset message logs like ''close'', ''fix'' etc. and performs the corresponding workflow action.

  If you have a more complex workflow, like the testing stage described above and you want the ''closes'' keyword to move the ticket to the ''testing'' status instead of the ''closed'' status, you need to adapt the code a bit. 

  Have a look at the [[trac:wiki:0.11/TracWorkflow#How-ToCombineSVNtrac-post-commit-hookWithTestWorkflow|Trac 0.11 recipe]] for the `trac-post-commit-hook`, this will give you some ideas about how to modify the component.

  == Example: Add simple optional generic review state ==

  Sometimes Trac is used in situations where "testing" can mean different things to different people so you may want to create an optional workflow state that is between the default workflow's `assigned` and `closed` states, but does not impose implementation-specific details. The only new state you need to add for this is a `reviewing` state. A ticket may then be "submitted for review" from any state that it can be reassigned. If a review passes, you can re-use the `resolve` action to close the ticket, and if it fails you can re-use the `reassign` action to push it back into the normal workflow.

  The new `reviewing` state along with its associated `review` action looks like this:

  {{{
  review = new,assigned,reopened -> reviewing
  review.operations = set_owner
  review.permissions = TICKET_MODIFY
  }}}

  Then, to integrate this with the default Trac 0.11 workflow, you also need to add the `reviewing` state to the `accept` and `resolve` actions, like so:

  {{{
  accept = new,reviewing -> assigned
  […]
  resolve = new,assigned,reopened,reviewing -> closed
  }}}

  Optionally, you can also add a new action that allows you to change the ticket's owner without moving the ticket out of the `reviewing` state. This enables you to reassign review work without pushing the ticket back to the `new` status.

  {{{
  reassign_reviewing = reviewing -> *
  reassign_reviewing.name = reassign review
  reassign_reviewing.operations = set_owner
  reassign_reviewing.permissions = TICKET_MODIFY
  }}}

  The full `[ticket-workflow]` configuration will thus look like this:

  {{{
  [ticket-workflow]
  accept = new,reviewing -> assigned
  accept.operations = set_owner_to_self
  accept.permissions = TICKET_MODIFY
  leave = * -> *
  leave.default = 1
  leave.operations = leave_status
  reassign = new,assigned,accepted,reopened -> assigned
  reassign.operations = set_owner
  reassign.permissions = TICKET_MODIFY
  reopen = closed -> reopened
  reopen.operations = del_resolution
  reopen.permissions = TICKET_CREATE
  resolve = new,assigned,reopened,reviewing -> closed
  resolve.operations = set_resolution
  resolve.permissions = TICKET_MODIFY
  review = new,assigned,reopened -> reviewing
  review.operations = set_owner
  review.permissions = TICKET_MODIFY
  reassign_reviewing = reviewing -> *
  reassign_reviewing.operations = set_owner
  reassign_reviewing.name = reassign review
  reassign_reviewing.permissions = TICKET_MODIFY
  }}}

  == Example: Limit the resolution options for a new ticket ==

  The above resolve_new operation allows you to set the possible resolutions for a new ticket.  By modifying the existing resolve action and removing the new status from before the `->` we then get two resolve actions.  One with limited resolutions for new tickets, and then the regular one once a ticket is accepted.

  {{{
  resolve_new = new -> closed
  resolve_new.name = resolve
  resolve_new.operations = set_resolution
  resolve_new.permissions = TICKET_MODIFY
  resolve_new.set_resolution = invalid,wontfix,duplicate

  resolve = assigned,accepted,reopened -> closed
  resolve.operations = set_resolution
  resolve.permissions = TICKET_MODIFY
  }}}

  == Advanced Ticket Workflow Customization ==

  If the customization above is not extensive enough for your needs, you can extend the workflow using plugins.  These plugins can provide additional operations for the workflow (like code_review), or implement side-effects for an action (such as triggering a build) that may not be merely simple state changes.  Look at [trac:source:trunk/sample-plugins/workflow sample-plugins/workflow] for a few simple examples to get started.

  But if even that is not enough, you can disable the !ConfigurableTicketWorkflow component and create a plugin that completely replaces it.

  == Adding Workflow States to Milestone Progress Bars ==

  If you add additional states to your workflow, you may want to customize your milestone progress bars as well.  See [TracIni#milestone-groups-section TracIni].

  == some ideas for next steps ==

  New enhancement ideas for the workflow system should be filed as enhancement tickets against the `ticket system` component.  If desired, add a single-line link to that ticket here.  Also look at the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin] as it provides experimental operations.

  If you have a response to the comments below, create an enhancement ticket, and replace the description below with a link to the ticket.

   * the "operation" could be on the nodes, possible operations are:
     * '''preops''': automatic, before entering the state/activity
     * '''postops''': automatic, when leaving the state/activity
     * '''actions''': can be chosen by the owner in the list at the bottom, and/or drop-down/pop-up together with the default actions of leaving the node on one of the arrows.
  ''This appears to add complexity without adding functionality; please provide a detailed example where these additions allow something currently impossible to implement.''

   * operations could be anything: sum up the time used for the activity, or just write some statistical fields like 
  ''A workflow plugin can add an arbitrary workflow operation, so this is already possible.''

   * set_actor should be an operation allowing to set the owner, e.g. as a "preop":
     * either to a role, a person
     * entered fix at define time, or at run time, e.g. out of a field, or select.
  ''This is either duplicating the existing `set_owner` operation, or needs to be clarified.''

   * Actions should be selectable based on the ticket type (different Workflows for different tickets)
  ''Look into the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin]'s `triage` operation.''

   * I'd wish to have an option to perform automatic status changes. In my case, I do not want to start with "new", but with "assigned". So tickets in state "new" should automatically go into state "assigned". Or is there already a way to do this and I just missed it?
  ''Have a look at [http://trac-hacks.org/wiki/TicketCreationStatusPlugin TicketCreationStatusPlugin] and [http://trac-hacks.org/wiki/TicketConditionalCreationStatusPlugin TicketConditionalCreationStatusPlugin]''

   * I added a 'testing' state. A tester can close the ticket or reject it. I'd like the transition from testing to rejected to set the owner to the person that put the ticket in 'testing'. The [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin] is close with set_owner_to_field, but we need something like set_field_to_owner.

   * I'd like to track the time a ticket is in each state, adding up 'disjoints' intervals in the same state.


name: TracAccessibility
author: trac
ipnr: 127.0.0.1
text:
  = Accessibility Support in Trac =

  Not every user has a graphic environment with a mouse or other pointing device. Some users rely on keyboard, alternative keyboard or voice input to navigate links, activate form controls, etc. In Trac, we work to assure users may interact with devices other than a pointing device.

  The keyboard shortcuts must be enabled for a session through the [/prefs/keybindings Keyboard Shortcuts] preferences panel.

  Trac supports accessibility keys for the most common operations.
   - on Linux platforms, press any of the keys listed below in combination with the `<Alt>` key 
   - on a Mac, use the `<ctrl>` key instead
   - on Windows, you need to hit `<Shift> + <Alt> + <Key>`. This works for most browsers (Firefox, Chrome, Safari and Internet Explorer)

  == Global Access Keys ==

   * `1` - WikiStart
   * `2` - [wiki:TracTimeline Timeline]
   * `3` - [wiki:TracRoadmap Roadmap]
   * `4` - [wiki:TracSearch Search]
   * `6` - [wiki:TracGuide Trac Guide / Documentation]
   * `7` - [wiki:TracTickets New Ticket]
   * `9` - [/about About Trac]
   * `0` - This page
   * `e` - Edit this page
   * `f` - Search


  ----
  See also: TracGuide


name: TracPlugins
author: trac
ipnr: 127.0.0.1
text:
  = Trac plugins =
  [[TracGuideToc]]

  From version 0.9 onwards, Trac is extensible with [trac:PluginList plugins]. Plugin functionality is based on the [trac:TracDev/ComponentArchitecture component architecture], with peculiarities described in the [TracDev/PluginDevelopment plugin development] page.

  == Plugin discovery ==

  From the user's point of view, a plugin is either a standalone .py file or an .egg package. Trac looks for plugins in the global shared plugins directory (see [TracIni#GlobalConfiguration Global Configuration]) and in the `plugins` directory of the local TracEnvironment. Components defined in globally-installed plugins should be explicitly enabled in the [[TracIni#components-section| [components] ]] section of the trac.ini file.

  == Requirements for Trac eggs ==

  To use egg-based plugins in Trac, you need to have [http://peak.telecommunity.com/DevCenter/setuptools setuptools] (version 0.6) installed.

  To install `setuptools`, download the bootstrap module [http://peak.telecommunity.com/dist/ez_setup.py ez_setup.py] and execute it as follows:

  {{{
  $ python ez_setup.py
  }}}

  If the `ez_setup.py` script fails to install the setuptools release, you can download it from [http://www.python.org/pypi/setuptools PyPI] and install it manually.

  Plugins can also consist of a single `.py` file dropped directly into either the project's or the shared `plugins` directory.

  == Installing a Trac plugin ==

  === For a single project ===

  Plugins are typically packaged as [http://peak.telecommunity.com/DevCenter/PythonEggs Python eggs]. That means they are .zip archives with the file extension `.egg`.

  If you have downloaded a source distribution of a plugin, and want to build the `.egg` file:

   * Unpack the source. It should provide `setup.py`.
   * Run:

  {{{
  $ python setup.py bdist_egg
  }}}

  You should have a *.egg file. Examine the output of running python to find where this was created.

  Once you have the plugin archive, copy it into the `plugins` directory of the [wiki:TracEnvironment project environment]. Also, make sure that the web server has sufficient permissions to read the plugin egg. Then restart the web server. If you are running as a [wiki:TracStandalone "tracd" standalone server], restart tracd (kill and run again).

  To uninstall a plugin installed this way, remove the egg from the `plugins` directory and restart the web server.

  Note: the Python version that the egg is built with ''must'' match the Python version with which Trac is run. For example, if you're running Trac under Python 2.5, but have upgraded your standalone Python to 2.6, the eggs won't be recognized.

  Note also: in a multi-project setup, a pool of Python interpreter instances will be dynamically allocated to projects based on need; since plugins occupy a place in Python's module system, the first version of any given plugin to be loaded will be used for all projects. In other words, you cannot use different versions of a single plugin in two projects of a multi-project setup. It may be safer to install plugins for all projects (see below), and then enable them selectively on a project-by-project basis.

  === For all projects ===

  ==== With an .egg file ====

  Some plugins (such as [trac:SpamFilter SpamFilter]) are downloadable as an `.egg` file that can be installed with the `easy_install` program:
  {{{
  easy_install TracSpamFilter
  }}}

  If `easy_install` is not on your system, see the Requirements section above to install it. Windows users will need to add the `Scripts` directory of their Python installation (for example, `C:\Python24\Scripts`) to their `PATH` environment variable (see [http://peak.telecommunity.com/DevCenter/EasyInstall#windows-notes easy_install Windows notes] for more information).

  If Trac reports permission errors after installing a zipped egg, and you would rather not bother providing a egg cache directory writable by the web server, you can get around it by simply unzipping the egg. Just pass `--always-unzip` to `easy_install`:
  {{{
  easy_install --always-unzip TracSpamFilter-0.4.1_r10106-py2.6.egg
  }}}
  You should end up with a directory having the same name as the zipped egg (complete with `.egg` extension) and containing its uncompressed contents.

  Trac also searches for plugins installed in the shared plugins directory ''(since 0.10)''; see TracIni#GlobalConfiguration. This is a convenient way to share the installation of plugins across several, but not all, environments.

  ==== From source ====

  `easy_install` makes installing from source a snap. Just give it the URL to either a Subversion repository or a tarball/zip of the source:
  {{{
  easy_install http://svn.edgewall.com/repos/trac/plugins/0.12/spam-filter-captcha
  }}}

  ==== Enabling the plugin ====

  Unlike plugins installed per-environment, you'll have to explicitly enable globally installed plugins via [wiki:TracIni trac.ini]. This also applies to plugins installed in the shared plugins directory, i.e. the path specified in the `[inherit] plugins_dir` configuration option. 

  This is done in the `[components]` section of the configuration file. For example:
  {{{
  [components]
  tracspamfilter.* = enabled
  }}}

  The name of the option is the Python package of the plugin. This should be specified in the documentation of the plugin, but can also be easily discovered by looking at the source (look for a top-level directory that contains a file named `__init__.py`).

  Note: After installing the plugin, you must restart your web server.

  ==== Uninstalling ====

  `easy_install` or `python setup.py` does not have an uninstall feature. Hower, it is usually quite trivial to remove a globally-installed egg and reference:

   1. Do `easy_install -m [plugin name]` to remove references from `$PYTHONLIB/site-packages/easy-install.pth` when the plugin installed by setuptools.
   1. Delete executables from `/usr/bin`, `/usr/local/bin`, or `C:\\Python*\Scripts`. To find what executables are involved, refer to the `[console-script]` section of `setup.py`.
   1. Delete the .egg file or folder from where it's installed (usually inside `$PYTHONLIB/site-packages/`).
   1. Restart the web server.

  If you are uncertain about the location of the egg, here's a small tip to help locate an egg (or any package). Just replace `myplugin` with whatever namespace the plugin uses (as used when enabling the plugin):
  {{{
  >>> import myplugin
  >>> print myplugin.__file__
  /opt/local/python24/lib/site-packages/myplugin-0.4.2-py2.4.egg/myplugin/__init__.pyc
  }}}

  == Setting up the plugin cache ==

  Some plugins will need to be extracted by the Python eggs runtime (`pkg_resources`), so that their contents are actual files on the file system. The directory in which they are extracted defaults to `.python-eggs` in the home directory of the current user, which may or may not be a problem. You can, however, override the default location using the `PYTHON_EGG_CACHE` environment variable.

  To do this from the Apache configuration, use the `SetEnv` directive:
  {{{
  SetEnv PYTHON_EGG_CACHE /path/to/dir
  }}}

  This works whether you're using the [wiki:TracCgi CGI] or the [wiki:TracModPython mod_python] front-end. Put this directive next to where you set the path to the [wiki:TracEnvironment Trac environment], i.e. in the same `<Location>` block.

  For example (for CGI):
  {{{
   <Location /trac>
     SetEnv TRAC_ENV /path/to/projenv
     SetEnv PYTHON_EGG_CACHE /path/to/dir
   </Location>
  }}}

  Or (for mod_python):
  {{{
   <Location /trac>
     SetHandler mod_python
     ...
     SetEnv PYTHON_EGG_CACHE /path/to/dir
   </Location>
  }}}

   ''Note: !SetEnv requires the `mod_env` module which needs to be activated for Apache. In this case the !SetEnv directive can also be used in the `mod_python` Location block.''

  For [wiki:TracFastCgi FastCGI], you'll need to `-initial-env` option, or whatever is provided by your web server for setting environment variables. 

   ''Note: that if you already use -initial-env to set the project directory for either a single project or parent you will need to add an additional -initial-env directive to the !FastCgiConfig directive. I.e.

  {{{
  FastCgiConfig -initial-env TRAC_ENV=/var/lib/trac -initial-env PYTHON_EGG_CACHE=/var/lib/trac/plugin-cache
  }}}

  === About hook scripts ===

  If you've set up some subversion hook scripts that call the Trac engine, such as the post-commit hook script provided in the `/contrib` directory, make sure you define the `PYTHON_EGG_CACHE` environment variable within these scripts as well.

  == Troubleshooting ==

  === Is setuptools properly installed? ===

  Try this from the command line:
  {{{
  $ python -c "import pkg_resources"
  }}}

  If you get '''no output''', setuptools '''is''' installed. Otherwise, you'll need to install it before plugins will work in Trac.

  === Did you get the correct version of the Python egg? ===

  Python eggs have the Python version encoded in their filename. For example, `MyPlugin-1.0-py2.5.egg` is an egg for Python 2.5, and will '''not''' be loaded if you're running a different Python version (such as 2.4 or 2.6).

  Also, verify that the egg file you downloaded is indeed a .zip archive. If you downloaded it from a Trac site, chances are you downloaded the HTML preview page instead.

  === Is the plugin enabled? ===

  If you install a plugin globally (i.e., ''not'' inside the `plugins` directory of the Trac project environment), you must explicitly enable it in [TracIni trac.ini]. Make sure that:

   * ...you actually added the necessary line(s) to the `[components]` section.
   * ...the package/module names are correct.
   * ...the value is "enabled", not "enable" or "Enable".

  === Check the permissions on the .egg file ===

  Trac must be able to read the .egg file. 

  === Check the log files ===

  Enable [wiki:TracLogging logging] and set the log level to `DEBUG`, then watch the log file for messages about loading plugins.

  === Verify you have proper permissions ===

  Some plugins require you have special permissions in order to use them. [trac:WebAdmin WebAdmin], for example, requires the user to have TRAC_ADMIN permissions for it to show up on the navigation bar.

  === Is the wrong version of the plugin loading? ===

  If you put your plugins inside plugins directories, and certainly if you have more than one project, you need to make sure that the correct version of the plugin is loading. Here are some basic rules:

   * Only one version of the plugin can be loaded for each running Trac server (i.e., each Python process). The Python namespaces and module list will be shared, and it cannot handle duplicates. Whether a plugin is `enabled` or `disabled` makes no difference.
   * A globally-installed plugin (typically `setup.py install`) will override any version in the global or project plugins directories. A plugin from the global plugins directory will be located ''before'' any project plugins directory.
   * If your Trac server hosts more than one project (as with `TRAC_ENV_PARENT_DIR` setups), having two versions of a plugin in two different projects will give uncertain results. Only one of them will load, and the one loaded will be shared by both projects. Trac will load the first plugin found, usually from the project that receives the first request.
   * Having more than one version listed inside Python site-packages is fine (i.e., installed with `setup.py install`) -- setuptools will make sure you get the version installed most recently. However, don't store more than one version inside a global or project plugins directory -- neither version number nor installed date will matter at all. There is no way to determine which one will be located first when Trac searches the directory for plugins.

  === If all of the above failed ===

  Okay, so the logs don't mention plugins, the egg is readable, the Python version is correct, ''and'' the egg has been installed globally (and is enabled in trac.ini)... and it ''still'' doesn't work or give any error messages or any other indication as to why. Hop on the [trac:IrcChannel IrcChannel] and ask away!

  == Web-based plugin administration ==

  The WebAdmin plugin (part of the core since 0.11) offers limited support for plugin configuration through the web to users with `TRAC_ADMIN` permission:

  * en/disabling installed plugins
  * installing plugins by uploading them as eggs

  You probably want to disable the second function for security reasons: in `trac.ini`, in the `[components]` section, add the line
  {{{
  trac.admin.web_ui.PluginAdminPanel = disabled
  }}}
  This disables the whole panel, so the first function will no longer be available either.

  ----
  See also TracGuide, [trac:PluginList plugin list], [trac:TracDev/ComponentArchitecture component architecture].


name: PageTemplates
author: trac
ipnr: 127.0.0.1
text:
  = Wiki Page Templates = 

    ''(since [http://trac.edgewall.org/milestone/0.11 0.11])''

  The default content for a new wiki page can be chosen from a list of page templates. 

  That list is generated from all the wiki pages having a name starting with ''PageTemplates/''.
  The initial content of a new page will simply be the content of the chosen template page, or a blank page if the special ''(blank page)'' entry is selected. When there are no wiki pages with the ''PageTemplates/'' prefix, the initial content will always be the blank page and the list selector will not be shown (i.e. this matches the behavior we had up to now).

  To create a new template, simply create a new page having a name starting with ''PageTemplates/''.

  (Hint: one could even create a ''!PageTemplates/Template'' for facilitating the creation of new templates!)

  After the first template has been created, a drop-down selection box will automatically appear on any new wiki pages that are created.  By default it is located on the right side of the 'Create this page' button. The default selection will be ''blank page'', or ''!DefaultPage'' if ''!PageTemplates/DefaultPage'' exists.

  Available templates: 
  [[TitleIndex(PageTemplates/)]]
  ----
  See also: TracWiki


name: TracSupport
author: trac
ipnr: 127.0.0.1
text:
  = Trac Support =

  Like in most [http://www.opensource.org/ open source projects], "free" Trac support is available primarily through the community itself, mainly through the [trac:MailingList mailing list] and the [trac: project wiki]. The latter is the authoritative source for the TracGuide (administrator and user guides for Trac).

  There is also an [trac:IrcChannel IRC channel], where people might be able to help out. Much of the 'live' development discussions also happen there.

  Before you start a new support query, make sure you've done the appropriate searching:
   * in the project's [trac:TracFaq FAQ]
   * in past messages to the [http://groups.google.com/group/trac-users Trac Users Mailing List]
   * in the Trac ticket system, using either a [trac:search:?q=&ticket=on&wiki=on full search] or a [trac:query: ticket query].

  Please '''don't''' create a ticket in trac.egdewall.org for asking a support question about Trac. Only use it when you face a ''real'' and ''new'' bug in Trac, and do so only after having read the [trac:NewTicketGuidelines NewTicketGuidelines]. The more a bug report or enhancement request complies with those guidelines, the higher the chances are that it will be fixed or implemented promptly!

  ----
  See also: [trac:MailingList], [trac:TracTroubleshooting], [trac:CommercialServices]


name: TracTicketsCustomFields
author: trac
ipnr: 127.0.0.1
text:
  = Custom Ticket Fields =
  Trac supports adding custom, user-defined fields to the ticket module. Using custom fields, you can add typed, site-specific properties to tickets.

  == Configuration ==
  Configuring custom ticket fields is done in the [wiki:TracIni trac.ini] file. All field definitions should be under a section named `[ticket-custom]`.

  The syntax of each field definition is:
  {{{
   FIELD_NAME = TYPE
   (FIELD_NAME.OPTION = VALUE)
   ...
  }}}
  The example below should help to explain the syntax.

  === Available Field Types and Options ===
   * '''text''': A simple (one line) text field.
     * label: Descriptive label.
     * value: Default value.
     * order: Sort order placement. (Determines relative placement in forms with respect to other custom fields.)
     * format: One of: 
       * `plain` for plain text 
       * `wiki` to interpret the content as WikiFormatting (''since 0.11.3'') 
       * `reference` to treat the content as a queryable value (''since 1.0'') 
       * `list` to interpret the content as a list of queryable values, separated by whitespace (''since 1.0'')
   * '''checkbox''': A boolean value check box.
     * label: Descriptive label.
     * value: Default value (0 or 1).
     * order: Sort order placement.
   * '''select''': Drop-down select box. Uses a list of values.
     * label: Descriptive label.
     * options: List of values, separated by '''|''' (vertical pipe).
     * value: Default value (one of the values from options).
     * order: Sort order placement.
   * '''radio''': Radio buttons. Essentially the same as '''select'''.
     * label: Descriptive label.
     * options: List of values, separated by '''|''' (vertical pipe).
     * value: Default value (one of the values from options).
     * order: Sort order placement.
   * '''textarea''': Multi-line text area.
     * label: Descriptive label.
     * value: Default text.
     * cols: Width in columns.
     * rows: Height in lines.
     * order: Sort order placement.
     * format: Either `plain` for plain text or `wiki` to interpret the content as WikiFormatting. (''since 0.11.3'')

  === Sample Config ===
  {{{
  [ticket-custom]

  test_one = text
  test_one.label = Just a text box

  test_two = text
  test_two.label = Another text-box
  test_two.value = Default [mailto:joe@nospam.com owner]
  test_two.format = wiki

  test_three = checkbox
  test_three.label = Some checkbox
  test_three.value = 1

  test_four = select
  test_four.label = My selectbox
  test_four.options = one|two|third option|four
  test_four.value = two

  test_five = radio
  test_five.label = Radio buttons are fun
  test_five.options = uno|dos|tres|cuatro|cinco
  test_five.value = dos

  test_six = textarea
  test_six.label = This is a large textarea
  test_six.value = Default text
  test_six.cols = 60
  test_six.rows = 30
  }}}

  ''Note: To make entering an option for a `select` type field optional, specify a leading `|` in the `fieldname.options` option.''

  === Reports Involving Custom Fields ===

  Custom ticket fields are stored in the `ticket_custom` table, not in the `ticket` table. So to display the values from custom fields in a report, you will need a join on the 2 tables. Let's use an example with a custom ticket field called `progress`.

  {{{
  #!sql
  SELECT p.value AS __color__,
     id AS ticket, summary, owner, c.value AS progress
    FROM ticket t, enum p, ticket_custom c
    WHERE status IN ('assigned') AND t.id = c.ticket AND c.name = 'progress'
  AND p.name = t.priority AND p.type = 'priority'
    ORDER BY p.value
  }}}
  '''Note''' that this will only show tickets that have progress set in them, which is '''not the same as showing all tickets'''. If you created this custom ticket field ''after'' you have already created some tickets, they will not have that field defined, and thus they will never show up on this ticket query. If you go back and modify those tickets, the field will be defined, and they will appear in the query. If that's all you want, you're set.

  However, if you want to show all ticket entries (with progress defined and without), you need to use a `JOIN` for every custom field that is in the query.
  {{{
  #!sql
  SELECT p.value AS __color__,
     id AS ticket, summary, component, version, milestone, severity,
     (CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner,
     time AS created,
     changetime AS _changetime, description AS _description,
     reporter AS _reporter,
    (CASE WHEN c.value = '0' THEN 'None' ELSE c.value END) AS progress
    FROM ticket t
       LEFT OUTER JOIN ticket_custom c ON (t.id = c.ticket AND c.name = 'progress')
       JOIN enum p ON p.name = t.priority AND p.type='priority'
    WHERE status IN ('new', 'assigned', 'reopened')
    ORDER BY p.value, milestone, severity, time
  }}}

  Note in particular the `LEFT OUTER JOIN` statement here.

  === Updating the database ===

  As noted above, any tickets created before a custom field has been defined will not have a value for that field. Here's a bit of SQL (tested with SQLite) that you can run directly on the Trac database to set an initial value for custom ticket fields. Inserts the default value of 'None' into a custom field called 'request_source' for all tickets that have no existing value:

  {{{
  #!sql
  INSERT INTO ticket_custom
     (ticket, name, value)
     SELECT 
        id AS ticket,
        'request_source' AS name,
        'None' AS value
     FROM ticket 
     WHERE id NOT IN (
        SELECT ticket FROM ticket_custom
     );
  }}}

  If you added multiple custom fields at different points in time, you should be more specific in the subquery on table {{{ticket}}} by adding the exact custom field name to the query:

  {{{
  #!sql
  INSERT INTO ticket_custom
     (ticket, name, value)
     SELECT 
        id AS ticket,
        'request_source' AS name,
        'None' AS value
     FROM ticket 
     WHERE id NOT IN (
        SELECT ticket FROM ticket_custom WHERE name = 'request_source'
     );
  }}}

  ----
  See also: TracTickets, TracIni


name: TracNavigation
author: trac
ipnr: 127.0.0.1
text:
  = Trac Navigation =

  Starting with Trac 0.11, it is now possible to customize the main and meta navigation entries in some basic ways.

  The new `[mainnav]` and `[metanav]` configuration sections can now be used to customize the text and link used for the navigation items, or even to disable them.  The `mainnav` and `metanav` options in the `[trac]` configuration section can also be used to change the order.

  === `[mainnav]` #mainnav-bar
  `[mainnav]` corresponds to the '''main navigation bar''', the one containing entries such as ''Wiki'', ''Timeline'', ''Roadmap'', ''Browse Source'' and so on. This navigation bar is meant to access the default page of the main modules enabled in Trac that are accessible for the current user.


  ** [=#Example Example] ** 

  In the following example, we rename the link to the Wiki start "Home", and make the "View Tickets" entry link to a specific report.  The second example (below) also hides the "!Help/Guide" link.

  Relevant excerpt from the TracIni:
  {{{
  [mainnav]
  wiki.label = Home
  tickets.href = /report/24
  }}}

  === `[metanav]` #metanav-bar
  `[metanav]` corresponds to the '''meta navigation bar''', by default positioned above the main navigation bar and below the ''Search'' box. It contains the ''Log in'', ''Logout'', ''!Help/Guide'' etc. entries. This navigation bar is meant to access some global information about the Trac project and the current user.

  There is one special entry in the  `[metanav]` section: `logout.redirect` is the page the user sees after hitting the logout button. 
  [[comment(see also #Trac3808)]]

  ** Example ** 

  {{{
  [metanav]
  help = disabled
  logout.redirect = wiki/Logout
  }}}


  === Notes
  Possible URL formats (for `.href` or `.redirect`):
  || '''config''' || '''redirect to''' ||
  || `wiki/Logout` || `/projects/env/wiki/Logout` ||
  || `http://hostname/` || `http://hostname/` ||
  || `/projects` || `/projects` ||


  === `[trac]` #nav-order
  The `mainnav` and `metanav` options in the `[trac]` configuration section control the order in which the navigation items are displayed (left to right).  This can be useful with plugins that add navigation items.

  ** Example ** 

  In the following example, we change the order to prioritise the ticket related items further left.

  Relevant excerpt from the TracIni:
  {{{
  [trac]
  mainnav = wiki,tickets,newticket,timeline,roadmap,browser,search,admin
  }}}

  The default order and item names can be viewed in the [TracIni#trac-section trac section of TracIni].

  === Context Navigation #ctxtnav-bar

  Note that it is still not possible to customize the '''contextual navigation bar''', i.e. the one usually placed below the main navigation bar.


  ----
  See also: TracInterfaceCustomization, and the [http://trac-hacks.org/wiki/NavAddPlugin TracHacks:NavAddPlugin] or [http://trac-hacks.org/wiki/MenusPlugin TracHacks:MenusPlugin] (still needed for adding entries)


name: WikiDeletePage
author: trac
ipnr: 127.0.0.1
text:
  = Deleting a Wiki Page =

  Existing wiki pages can be completely deleted using the ''Delete Page'' or the ''Delete this Version'' buttons at the bottom of the wiki page. These buttons are only visible for users with `WIKI_DELETE` permissions.

  '''Note:''' Deleting a wiki page is an irreversible operation.

  If you want to delete a page because you actually re-created a new page with the same content but a different name, it is recommended to keep the page and use it as a redirection page instead of completely deleting it, as to not frustrate the visitor with broken links when coming to the site from a search engine. 

  In this situation, chances are that you actually wanted to [[WikiNewPage#renaming|rename]] the page instead of doing a copy + delete. 
  The ''Rename'' operation also offers you the possibility to create a redirection page.
  A redirection page is a short page that  contains a link such as  “See !SomeOtherPage”. 

  However, deleting specific versions or even complete pages can make sense to remove spam or other abusive submissions.

  ----
  See also: TracWiki, TracPermissions


name: TracTimeline
author: trac
ipnr: 127.0.0.1
text:
  = The Trac Timeline =
  [[TracGuideToc]]

  The timeline provides a historic view of the project in a single report.

  It lists all Trac events that have occurred in chronological order, a
  brief description of each event and if applicable, the person responsible for
  the change.

  The timeline lists these kinds of events:
   * '''Wiki page events''' — Creation and changes
   * '''Ticket events''' — Creation and resolution/closing (and optionally other changes)
   * '''Source code changes ''' — Repository check-ins
   * '''Milestone ''' — Milestone completed

  Each event entry provides a hyperlink to the specific event in question, who authored the change as well as
  a brief excerpt of the actual comment or text, if available.

  It is possible to filter the displayed events with the various filters in the option panel:
   * ''View changes from'' — the date from which to start displaying events (current date if empty). Events that occurred after this date will not be shown, only those that occurred before that date.
   * ''and X days back'' — how many days backwards in time to get events.
   * ''done by'' — the author of an event. It accepts a space-separated list of authors for which events should be included. Alternatively, if the author names are prefixed by a "-" character, then the events having those authors will be excluded, and all the others included. Single or double quotes can be used for specifying author names containing space characters. ''(since 0.12)''
   * ''Changesets in all repositories'' — if you have more than one repository connected to your Trac project, then you can filter the output so events from specific repositories are not shown. ''(since 0.12)''
   * ''Milestones reached'' — display or hide milestones reached.
   * ''Opened and closed tickets'' — display or hide ticket open or close events.
   * ''Wiki changes'' — display or hide Wiki change events.

  See !TracIni's [wiki:TracIni#timeline-section "[timeline] section"] for timeline configuration options.

  == RSS Support ==

  The Timeline module supports subscription using RSS 2.0 syndication. To subscribe to project events, click the orange '''XML''' icon at the bottom of the page. See TracRss for more information on RSS support in Trac.

  ----
  See also: TracGuide, TracIni, TracWiki, WikiFormatting, TracRss, TracNotification


name: TracNotification
author: trac
ipnr: 127.0.0.1
text:
  = Email Notification of Ticket Changes =
  [[TracGuideToc]]

  Trac supports notification of ticket changes via email. 

  Email notification is useful to keep users up-to-date on tickets/issues of interest, and also provides a convenient way to post all ticket changes to a dedicated mailing list. For example, this is how the [http://lists.edgewall.com/archive/trac-tickets/ Trac-tickets] mailing list is set up.

  Disabled by default, notification can be activated and configured in [wiki:TracIni trac.ini].

  == Receiving Notification Mails ==
  When reporting a new ticket or adding a comment, enter a valid email address or your username in the ''reporter'', ''assigned to/owner'' or ''cc'' field. Trac will automatically send you an email when changes are made to the ticket (depending on how notification is configured).

  This is useful to keep up-to-date on an issue or enhancement request that interests you.

  === How to use your username to receive notification mails ===

  To receive notification mails, you can either enter a full email address or your username. To get notified with a simple username or login, you need to specify a valid email address in the ''Preferences'' page. 

  Alternatively, a default domain name ('''`smtp_default_domain`''') can be set in the TracIni file (see [#ConfigurationOptions Configuration Options] below). In this case, the default domain will be appended to the username, which can be useful for an "Intranet" kind of installation.

  When using apache and mod_kerb for authentication against Kerberos / Active Directory, usernames take the form ('''`username@EXAMPLE.LOCAL`'''). To avoid this being interpreted as an email address, add the Kerberos domain to  ('''`ignore_domains`''').

  == Configuring SMTP Notification ==

  '''Important:''' For TracNotification to work correctly, the `[trac] base_url` option must be set in [wiki:TracIni trac.ini]. 

  === Configuration Options ===
  These are the available options for the `[notification]` section in trac.ini.

   * '''`smtp_enabled`''': Enable email notification.
   * '''`smtp_from`''': Email address to use for ''Sender''-headers in notification emails.
   * '''`smtp_from_name`''': Sender name to use for ''Sender''-headers in notification emails.
   * '''`smtp_from_author`''': (''since 1.0'') Use the author of a change (the reporter of a new ticket, or the author of a comment) as the `From:` header value in notification e-mails (default: false). If the author hasn't set an e-mail address, `smtp_from` and `smtp_from_name` are used instead.
   * '''`smtp_replyto`''': Email address to use for ''Reply-To''-headers in notification emails.
   * '''`smtp_default_domain`''': (''since 0.10'') Append the specified domain to addresses that do not contain one. Fully qualified addresses are not modified. The default domain is appended to all username/login for which an email address cannot be found from the user settings.
   * '''`smtp_always_cc`''': List of email addresses to always send notifications to. ''Typically used to post ticket changes to a dedicated mailing list.''
   * '''`smtp_always_bcc`''': (''since 0.10'') List of email addresses to always send notifications to, but keeps addresses not visible from other recipients of the notification email 
   * '''`smtp_subject_prefix`''': (''since 0.10.1'') Text that is inserted before the subject of the email. Set to "!__default!__" by default.
   * '''`always_notify_reporter`''':  Always send notifications to any address in the reporter field (default: false).
   * '''`always_notify_owner`''': (''since 0.9'') Always send notifications to the address in the owner field (default: false).
   * '''`always_notify_updater`''': (''since 0.10'') Always send a notification to the updater of a ticket (default: true).
   * '''`use_public_cc`''': (''since 0.10'') Addresses in To: (owner, reporter) and Cc: lists are visible by all recipients (default is ''Bcc:'' - hidden copy).
   * '''`use_short_addr`''': (''since 0.10'') Enable delivery of notifications to addresses that do not contain a domain (i.e. do not end with ''@<domain.com>'').This option is useful for intranets, where the SMTP server can handle local addresses and map the username/login to a local mailbox. See also `smtp_default_domain`. Do not use this option with a public SMTP server. 
   * '''`ignore_domains`''': Comma-separated list of domains that should not be considered part of email addresses (for usernames with Kerberos domains).
   * '''`mime_encoding`''': (''since 0.10'') This option allows selecting the MIME encoding scheme. Supported values:
     * `none`: default value, uses 7bit encoding if the text is plain ASCII, or 8bit otherwise. 
     * `base64`: works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines.
     * `qp` or `quoted-printable`: best for european languages (more compact than base64) if 8bit encoding cannot be used.
   * '''`ticket_subject_template`''': (''since 0.11'') A [http://genshi.edgewall.org/wiki/Documentation/text-templates.html Genshi text template] snippet used to get the notification subject.
   * '''`email_sender`''': (''since 0.12'') Name of the component implementing `IEmailSender`. This component is used by the notification system to send emails. Trac currently provides the following components:
     * `SmtpEmailSender`: connects to an SMTP server (default).
     * `SendmailEmailSender`: runs a `sendmail`-compatible executable.

  Either '''`smtp_from`''' or '''`smtp_replyto`''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails.

  The following options are specific to email delivery through SMTP.
   * '''`smtp_server`''': SMTP server used for notification messages.
   * '''`smtp_port`''': (''since 0.9'') Port used to contact the SMTP server.
   * '''`smtp_user`''': (''since 0.9'') User name for authentication SMTP account.
   * '''`smtp_password`''': (''since 0.9'') Password for authentication SMTP account.
   * '''`use_tls`''': (''since 0.10'') Toggle to send notifications via a SMTP server using [http://en.wikipedia.org/wiki/Transport_Layer_Security TLS], such as GMail.

  The following option is specific to email delivery through a `sendmail`-compatible executable.
   * '''`sendmail_path`''': (''since 0.12'') Path to the sendmail executable. The sendmail program must accept the `-i` and `-f` options.

  === Example Configuration (SMTP) ===
  {{{
  [notification]
  smtp_enabled = true
  smtp_server = mail.example.com
  smtp_from = notifier@example.com
  smtp_replyto = myproj@projects.example.com
  smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com
  }}}

  === Example Configuration (`sendmail`) ===
  {{{
  [notification]
  smtp_enabled = true
  email_sender = SendmailEmailSender
  sendmail_path = /usr/sbin/sendmail
  smtp_from = notifier@example.com
  smtp_replyto = myproj@projects.example.com
  smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com
  }}}

  === Customizing the e-mail subject ===
  The e-mail subject can be customized with the `ticket_subject_template` option, which contains a [http://genshi.edgewall.org/wiki/Documentation/text-templates.html Genshi text template] snippet. The default value is:
  {{{
  $prefix #$ticket.id: $summary
  }}}
  The following variables are available in the template:

   * `env`: The project environment (see [trac:source:/trunk/trac/env.py env.py]).
   * `prefix`: The prefix defined in `smtp_subject_prefix`.
   * `summary`: The ticket summary, with the old value if the summary was edited.
   * `ticket`: The ticket model object (see [trac:source:/trunk/trac/ticket/model.py model.py]). Individual ticket fields can be addressed by appending the field name separated by a dot, e.g. `$ticket.milestone`.

  === Customizing the e-mail content ===

  The notification e-mail content is generated based on `ticket_notify_email.txt` in `trac/templates`.  You can add your own version of this template by adding a `ticket_notify_email.txt` to the templates directory of your environment. The default looks like this:

  {{{
  $ticket_body_hdr
  $ticket_props
  {% choose ticket.new %}\
  {%   when True %}\
  $ticket.description
  {%   end %}\
  {%   otherwise %}\
  {%     if changes_body %}\
  ${_('Changes (by %(author)s):', author=change.author)}

  $changes_body
  {%     end %}\
  {%     if changes_descr %}\
  {%       if not changes_body and not change.comment and change.author %}\
  ${_('Description changed by %(author)s:', author=change.author)}
  {%       end %}\
  $changes_descr
  --
  {%     end %}\
  {%     if change.comment %}\

  ${changes_body and _('Comment:') or _('Comment (by %(author)s):', author=change.author)}

  $change.comment
  {%     end %}\
  {%   end %}\
  {% end %}\

  -- 
  ${_('Ticket URL: <%(link)s>', link=ticket.link)}
  $project.name <${project.url or abs_href()}>
  $project.descr
  }}}
  == Sample Email ==
  {{{
  #42: testing
  ---------------------------+------------------------------------------------
         Id:  42             |      Status:  assigned                
  Component:  report system  |    Modified:  Fri Apr  9 00:04:31 2004
   Severity:  major          |   Milestone:  0.9                     
   Priority:  lowest         |     Version:  0.6                     
      Owner:  anonymous      |    Reporter:  jonas@example.com               
  ---------------------------+------------------------------------------------
  Changes:
    * component:  changset view => search system
    * priority:  low => highest
    * owner:  jonas => anonymous
    * cc:  daniel@example.com =>
           daniel@example.com, jonas@example.com
    * status:  new => assigned

  Comment:
  I'm interested too!

  --
  Ticket URL: <http://example.com/trac/ticket/42>
  My Project <http://myproj.example.com/>
  }}}


  == Customizing e-mail content for MS Outlook ==

  Out-of-the-box, MS Outlook normally presents plain text e-mails with a variable-width font; the ticket properties table will most certainly look like a mess in MS Outlook. This can be fixed with some customization of the [#Customizingthee-mailcontent e-mail template].

  Replace the following second row in the template:
  {{{
  $ticket_props
  }}}

  with this instead (''requires Python 2.6 or later''):
  {{{
  --------------------------------------------------------------------------
  {% with
     pv = [(a[0].strip(), a[1].strip()) for a in [b.split(':') for b in
           [c.strip() for c in 
            ticket_props.replace('|', '\n').splitlines()[1:-1]] if ':' in b]];
     sel = ['Reporter', 'Owner', 'Type', 'Status', 'Priority', 'Milestone', 
            'Component', 'Severity', 'Resolution', 'Keywords'] %}\
  ${'\n'.join('%s\t%s' % (format(p[0]+':', ' <12'), p[1]) for p in pv if p[0] in sel)}
  {% end %}\
  --------------------------------------------------------------------------
  }}}

  The table of ticket properties is replaced with a list of a selection of the properties. A tab character separates the name and value in such a way that most people should find this more pleasing than the default table, when using MS Outlook.
  {{{#!div style="margin: 1em 1.75em; border:1px dotted"
  {{{#!html
  #42: testing<br />
  --------------------------------------------------------------------------<br />
  <table cellpadding=0>
  <tr><td>Reporter:</td><td>jonas@example.com</td></tr>
  <tr><td>Owner:</td><td>anonymous</td></tr>
  <tr><td>Type:</td><td>defect</td></tr>
  <tr><td>Status:</td><td>assigned</td></tr>
  <tr><td>Priority:</td><td>lowest</td></tr>
  <tr><td>Milestone:</td><td>0.9</td></tr>
  <tr><td>Component:</td><td>report system</td></tr>
  <tr><td>Severity:</td><td>major</td></tr>
  <tr><td>Resolution:</td><td> </td></tr>
  <tr><td>Keywords:</td><td> </td></tr>
  </table>
  --------------------------------------------------------------------------<br />
  Changes:<br />
  <br />
  &nbsp;&nbsp;* component: &nbsp;changset view =&gt; search system<br />
  &nbsp;&nbsp;* priority: &nbsp;low =&gt; highest<br />
  &nbsp;&nbsp;* owner: &nbsp;jonas =&gt; anonymous<br />
  &nbsp;&nbsp;* cc: &nbsp;daniel@example.com =&gt;<br />
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;daniel@example.com, jonas@example.com<br />
  &nbsp;&nbsp;* status: &nbsp;new =&gt; assigned<br />
  <br />
  Comment:<br />
  I'm interested too!<br />
  <br />
  --<br />
  Ticket URL: &lt;http://example.com/trac/ticket/42&gt;<br />
  My Project &lt;http://myproj.example.com/&gt;<br />
  }}}
  }}}

  **Important**: Only those ticket fields that are listed in `sel` are part of the HTML mail. If you have defined custom ticket fields which shall be part of the mail they have to be added to `sel`, example:
  {{{
     sel = ['Reporter', ..., 'Keywords', 'Custom1', 'Custom2']
  }}}

  However, it's not as perfect as an automatically HTML-formatted e-mail would be, but presented ticket properties are at least readable by default in MS Outlook...


  == Using GMail as the SMTP relay host ==

  Use the following configuration snippet
  {{{
  [notification]
  smtp_enabled = true
  use_tls = true
  mime_encoding = base64
  smtp_server = smtp.gmail.com
  smtp_port = 587
  smtp_user = user
  smtp_password = password
  }}}

  where ''user'' and ''password'' match an existing GMail account, ''i.e.'' the ones you use to log in on [http://gmail.com]

  Alternatively, you can use `smtp_port = 25`.[[br]]
  You should not use `smtp_port = 465`. It will not work and your ticket submission may deadlock. Port 465 is reserved for the SMTPS protocol, which is not supported by Trac. See [comment:ticket:7107:2 #7107] for details.
   
  == Filtering notifications for one's own changes ==
  In Gmail, use the filter:

  {{{
  from:(<smtp_from>) (("Reporter: <username>" -Changes) OR "Changes (by <username>)")
  }}}

  For Trac .10, use the filter:
  {{{
  from:(<smtp_from>) (("Reporter: <username>" -Changes -Comment) OR "Changes (by <username>)" OR "Comment (by <username>)")
  }}}

  to delete these notifications.

  In Thunderbird, there is no such solution if you use IMAP
  (see http://kb.mozillazine.org/Filters_(Thunderbird)#Filtering_the_message_body).

  The best you can do is to set "always_notify_updater" in conf/trac.ini to false.
  You will however still get an email if you comment a ticket that you own or have reported.

  You can also add this plugin:
  http://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin

  == Troubleshooting ==

  If you cannot get the notification working, first make sure the log is activated and have a look at the log to find if an error message has been logged. See TracLogging for help about the log feature.

  Notification errors are not reported through the web interface, so the user who submit a change or a new ticket never gets notified about a notification failure. The Trac administrator needs to look at the log to find the error trace.

  === ''Permission denied'' error ===

  Typical error message:
  {{{
    ...
    File ".../smtplib.py", line 303, in connect
      raise socket.error, msg
    error: (13, 'Permission denied')
  }}}

  This error usually comes from a security settings on the server: many Linux distributions do not let the web server (Apache, ...) to post email message to the local SMTP server.

  Many users get confused when their manual attempts to contact the SMTP server succeed:
  {{{
  telnet localhost 25
  }}}
  The trouble is that a regular user may connect to the SMTP server, but the web server cannot:
  {{{
  sudo -u www-data telnet localhost 25
  }}}

  In such a case, you need to configure your server so that the web server is authorized to post to the SMTP server. The actual settings depend on your Linux distribution and current security policy. You may find help browsing the Trac [trac:MailingList MailingList] archive.

  Relevant ML threads:
   * SELinux: http://article.gmane.org/gmane.comp.version-control.subversion.trac.general/7518

  For SELinux in Fedora 10:
  {{{
  $ setsebool -P httpd_can_sendmail 1
  }}}
  === ''Suspected spam'' error ===

  Some SMTP servers may reject the notification email sent by Trac.

  The default Trac configuration uses Base64 encoding to send emails to the recipients. The whole body of the email is encoded, which sometimes trigger ''false positive'' SPAM detection on sensitive email servers. In such an event, it is recommended to change the default encoding to "quoted-printable" using the `mime_encoding` option.

  Quoted printable encoding works better with languages that use one of the Latin charsets. For Asian charsets, it is recommended to stick with the Base64 encoding.

  === ''501, 5.5.4 Invalid Address'' error ===

  On IIS 6.0 you could get a 
  {{{
  Failure sending notification on change to ticket #1: SMTPHeloError: (501, '5.5.4 Invalid Address')
  }}}
  in the trac log. Have a look [http://support.microsoft.com/kb/291828 here] for instructions on resolving it.


  ----
  See also: TracTickets, TracIni, TracGuide


name: TracImport
author: trac
ipnr: 127.0.0.1
text:
  = Importing ticket data =
  [[PageOutline]]

  By means of migrating from other issue-tracking systems, perform some external actions over tickets or simply synchronize different data bases, there are some available tools, plug-ins or scripts which lets you import or up-date tickets into Trac.

  Below, follows a collection of some of those.

  == !TicketImportPlugin ==

   [http://trac-hacks.org/wiki/TicketImportPlugin TicketImportPlugin] :: mainly, but not only, this plug-in lets you import or up-date into Trac a series of tickets from a '''CSV file''' or (if the [http://pypi.python.org/pypi/xlrd xlrd library] is installed) from an '''Excel file'''. 

  == !ExportImportXlsPlugin ==

   [http://trac-hacks.org/wiki/ExportImportXlsPlugin ExportImportXlsPlugin] :: this plug-in add an admin panel for export and import tickets via '''XLS file'''.
    * It depends on the python packages xlwt/rxld.

  == Bugzilla ==

   [http://trac-hacks.org/wiki/BugzillaIssueTrackingPlugin BugzillaIssueTrackingPlugin] :: integrates Bugzilla into Trac keeping TracLinks

  Ticket data can be imported from Bugzilla using the [http://trac.edgewall.org/browser/trunk/contrib/bugzilla2trac.py bugzilla2trac.py] script, available in the contrib/ directory of the Trac distribution.

  {{{
  $ bugzilla2trac.py
  bugzilla2trac - Imports a bug database from Bugzilla into Trac.

  Usage: bugzilla2trac.py [options]

  Available Options:
    --db <MySQL dbname>              - Bugzilla's database
    --tracenv /path/to/trac/env      - full path to Trac db environment
    -h | --host <MySQL hostname>     - Bugzilla's DNS host name
    -u | --user <MySQL username>     - effective Bugzilla's database user
    -p | --passwd <MySQL password>   - Bugzilla's user password
    -c | --clean                     - remove current Trac tickets before importing
    --help | help                    - this help info

  Additional configuration options can be defined directly in the script.
  }}}

  Currently, the following data is imported from Bugzilla:

    * bugs
    * bug activity (field changes)
    * bug attachments
    * user names and passwords (put into a htpasswd file)

  The script provides a number of features to ease the conversion, such as:

    * PRODUCT_KEYWORDS:  Trac doesn't have the concept of products, so the script provides the ability to attach a ticket keyword instead.

    * IGNORE_COMMENTS:  Don't import Bugzilla comments that match a certain regexp.

    * STATUS_KEYWORDS:  Attach ticket keywords for the Bugzilla statuses not available in Trac.  By default, the 'VERIFIED' and 'RELEASED' Bugzilla statuses are translated into Trac keywords.

  For more details on the available options, see the configuration section at the top of the script.

  == Jira ==

   [http://trac-hacks.org/wiki/JiraToTracIntegration JiraToTracIntegration] :: provides tools to import Atlassian Jira backup files into Trac. The plug-in consists of a Python 3.1 commandline tool that:
     - Parses the Jira backup XML file
     - Sends the imported Jira data and attachments to Trac using the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]
     - Generates a htpasswd file containing the imported Jira users and their SHA-512 base64 encoded passwords

  == Mantis ==

   [http://trac-hacks.org/wiki/MantisImportScript MantisImportScript] :: script to import from Mantis into Trac the following data:
    * bugs
    * bug comments
    * bug activity (field changes)
    * attachments (as long as the files live in the mantis db, not on the filesystem) .

  == !PlanetForge ==

   [http://trac-hacks.org/wiki/PlanetForgeImportExportPlugin PlanetForgeImportExportPlugin] :: this plugin exports Trac data (wiki, tickets, compoments, permissions, repositories, etc.) using the open format designed by the COCLICO project. It extends the webadmin panel and the 'trac admin ...' command. Still has no 'import' feature. 

  == Scarab ==

   [http://trac-hacks.org/wiki/ScarabToTracScript ScarabToTracScript] :: script that migrates Scarab issues to Trac tickets
      * Requires [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin]

  == Sourceforge ==

   [http://trac-hacks.org/wiki/SfnToTracScript SfnToTracScript] :: importer of !SourceForge's new backup file (originated from #Trac3521)

  Also, ticket data can be imported from Sourceforge using the [http://trac.edgewall.org/browser/trunk/contrib/sourceforge2trac.py sourceforge2trac.py] script, available in the contrib/ directory of the Trac distribution.

  == Other ==

  Since trac uses a SQL database to store the data, you can import from other systems by examining the database tables. Just go into [http://www.sqlite.org/sqlite.html sqlite] command line to look at the tables and import into them from your application.

  === Comma delimited file - CSV ===
  See [http://trac.edgewall.org/attachment/wiki/TracSynchronize/csv2trac.2.py csv2trac.2.py] for details.  This approach is particularly useful if one needs to enter a large number of tickets by hand. (note that the ticket type type field, (task etc...) is also needed for this script to work with more recent Trac releases)
  Comments on script: The script has an error on line 168, ('Ticket' needs to be 'ticket').  Also, the listed values for severity and priority are swapped. 

  ----
  See also: 
   * to import/export wiki pages: TracAdmin, 
   * to export tickets: TracTickets, TracQuery


