; ASD
Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out
Your Federal Quarterly Tax Payments are due April 15th Get Help Now >>

ASD

VIEWS: 2 PAGES: 7

  • pg 1
									                         Connect. Communicate. Collaborate




ASD – Questions
  Stephan Kraft
  June 2007, Cambridge
ASD                                                    Connect. Communicate. Collaborate




• What information is needed by Erlangen from the deployers? This
  information will be collected by the ASD for Erlangen. Erlangen to
  specify.
    – possibility of antenna installation, time, cost
    – what time signal can be used, existing time sources (GPS, PZF, PPS, ntp)
    – will box be used as ntp server?
    – IP adresses for eth0, eth1, remote management card (IPv4 only): IPv4,
      IPv6, submask, gateways etc., IPv6 not mandatory
    – contact person, address, phone, email etc.
    – shipping address
    – firewall information for using local dns servers
ASD                                                                 Connect. Communicate. Collaborate



• What information is needed by the ASD from Erlangen
   – Antenna installation training and procedure
   – Tools documentation (installation procedure, utilisation guide).
       • Deliverable S3.7.4 of SA3 for BWCTL MP/ Hades (step by step
         instruction), updated regularly
   – Known Errors
       • ticket system /bugzilla, to be decided, now FAQ pages in perfSONAR
         wiki
   – Tool/web-service installation URL
       • currently in the win-labor wiki – must be moved to GN2 wiki
   – How to monitor the tool/web-services
       • gandalf.rrze.uni-erlangen.de/nagios/ win-labor.dfn.de/nagios/ -> account for ASD
   – All information of boxes in excell sheet, new information from Erlangen to ASD, ASD
     to update. -> parallel information on GN2 wiki, later on database
ASD                                               Connect. Communicate. Collaborate



• What information is needed by Erlangen from the
  ASD
  – Monthly reports (on received incidents, questions and
    RFEs)
     • nagios, emails, other sources raises trouble ticket
     • first step: single point of contact ASD
     • second step: if accepted -> automated ticket raising, history,
       FAQ and solution „knowledge base“
  – Information for the configuration changes
     • information from deployer
     • information from incidents
ASD                                                                         Connect. Communicate. Collaborate


•   What procedures are needed (one document, word -> docbook):
     – equipment shipment/moving procedure (ASD)
          •   document must be refined, procedure review on feedback
          •   shipment to EU – not EU countries: minimize process
          •   shipment of defective machines
          •   shipment from NREN to NREN
     – equipment ordering procedure (ASD)
          • via Erlangen
     – incident escalation procedure (ASD + Erlangen) seee before
          • nagios, emails, other sources raises trouble ticket
          • first step: single point of contact ASD
          • second step: if accepted -> automated ticket raising, history, FAQ and solution „knowledge
            base“
     – procedure for bringing a new equipment into operation (ASD + Erlangen)
          • documentation to be send from Erlangen to ASD
     – procedure for changing the configuration of the tools (Erlangen)
          •   must be translated (Erlangen) and will be put int S3.7.4 (mid July, parts of it earlier on wiki)
ASD                                              Connect. Communicate. Collaborate




• Question: are there some actions that the service desk will
  be able to do in the long run for the maintenance -
  configuration changes
   – hardware maintenance: case dependent (cost, on site capabilities,
     kind of failure), normally done by Erlangen
   – admin account for ASD (like SA3) for changing confs.
   – change management in Erlangen (Jochen)


• The work done with Erlangen would be used as the basis
  for defining the collaboration between the ASD and the
  developers.
ASD                                      Connect. Communicate. Collaborate



• What the service desk will offer support for
  – the Hades tool: user utilisation, GPS antenna
    installation, operation (?), monitoring
  – Hades MA: user utilisation, monitoring.
  – BWCTL MP: user utilisation, installation, configuration,
    monitoring.
  – perfsonarUI BWCTL: user utilisation, configuration (?),
    monitoring.
  – incident escalation (problem not solved by ASD directly)
    to Erlangen

								
To top