1. Go to the script/ folder:
2. Run initialize.py to clone all dependent repositories of a Seattle component.
3. Run build.py to create a runnable environment for the monitoring scripts
4. Go to the RUNNABLE folder to run advertise_monitor.r2py or updater_monitor.py

• Infrastructure Components:
  • Clearinghouse
  • Custom Installer Builder
  • Software Updater Site
• Services:
  • Advertising Service: central, central_v2, udpcentral
  • Zenodotus
  • Time
• Components:
  • VM/Vessels
  • Node Mananger
  • Experiment Mananger
• Targets already monitored:
  • disk space (monitor_disk.py)
  • resource violation (nanny.py)
  • vessel info (checked in the installer)

To consider:

• metrics: availability, performance, usage, etc.
• location: local machine, node manager, Seattle server, Clearinghouse server, etc.
• users: server operator, contributor, Seattle users, general public
• notification

• central
  • check status of advertiseserver.poly.edu (port 10102) by first validating the hostname and then trying to open a connection to the hostname
    • alive
    • dead -> why? NetworkAddressError, ConnectionRefusedError, TimeoutError, InternetConnectivityError
  • announce and lookup a test <key, value> pair
• central_v2
  • check status of advertiseserver_v2.poly.edu (port 10102): same as with central
  • announce and lookup a test <key, value> pair
• udpcentral
  • check if domain name of UDP server exists
  • announce and lookup test to see if the server is listening

• Check the status of the server (as with the advertise server) URL: https://seattle.poly.edu/updatesite/. Servername: seattle.poly.edu
• Check if the updater site delivers the correct updates by checking the signatures in a downloaded metainfo

Same implementation as in zenodotus_alive.py in integrationtests

• Check status of Zenodotus server. Servername: zenodotus.poly.edu - IP address: 128.238.63.50
• Use advertise service to check that multiples nodes' IP addresses are registered to a single hostname

Same implementation as in test_time_tcp.py and test_time_servers_running.py in integrationtests

• Find time server(s) by doing an advertise lookup
• Make an NTP query and compare the returned time with the local time on the machine

• Use wget to download the website
  • https://seattleclearinghouse.poly.edu/
  • https://sensibilityclearinghouse.poly.edu/custominstallerbuilder/
• Record the time, number of files, download speed KB/s
• Analyze the raw data:
  • min, max, average, median
  • compare with the production Clearinghouse's

• integrationtestslib.py tracks errors. notifications.py tracks all statuses.
• Modes of notifications: report all statuses, report only errors, report frequency, report only prioritized services (determined by the users)
• Use send_gmail.py module to send notification emails
• Modularity between monitoring scripts and notification modules.