- newdown_one=("""PlanetLab node(s) down: %(loginbase)s""",
-"""
-Hello,
-
-As part of PlanetLab node monitoring, we noticed the following nodes were down at your site:
-
-%(hostname_list)s
-We're writing because we need your help returning them to their regular operation.
-
-To help, please confirm that a verison 3.0 or greater BootCD is installed in the machine. Then, after checking that the node is properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we are seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network. It may take several minutes before Comon registers your node. Until that time, visiting the link below will return the message 'could not find requested table - probably empty'.
-
- http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
-
-If the machine has booted successfully, you may check it more quickly by logging in with your site_admin account, and running:
-
- sudo /usr/sbin/vps ax
-
-If you have a BootCD older than 3.0, you will need to create a new BootImage on CD or USB. You can find instructions for this at the Technical Contact's Guide:
-
- https://www.planet-lab.org/doc/guides/bootcdsetup
-
-If after following these directions, and either logging in with your site_admin account or seeing the CoMon report of your machine, there is no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
-
-Finally, you can track the current status of your machines using this Google Gadget:
-
- http://fusion.google.com/add?source=atgs&moduleurl=http://monitor.planet-lab.org/monitor/sitemonitor.xml
-
-Thank you for your help,
- -- PlanetLab Central (support@planet-lab.org)
-""")
-
-#If no one responds, then after a week, we will disable your site's ability to create new slices. Because this action will directly affect your site's registered PI, we will also CC the PI for help at that time.
-
- newdown_two=("""PlanetLab node(s) down: %(loginbase)s""",
-"""
-Hello,
-
-As part of PlanetLab node monitoring, we noticed the following nodes were down at your site:
-
-%(hostname_list)s
-We're writing again because our previous correspondence, sent only to the registered Technical Contact, has gone unacknowledged for at least a week, and we need your help returning these machines to their regular operation. We understand that machine maintenance can take time. So, while we wait for the machines to return to their regular operation slice creation has been suspended at your site. No new slices may be created, but the existing slices and services running within them will be unaffected.
-
-To help, please confirm that a verison 3.0 or greater BootCD is installed in the machine. Then, after checking that the node is properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we are seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network. It may take several minutes before Comon registers your node. Until that time, visiting the link below will return the message 'could not find requested table - probably empty'.
-
- http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
-
-If the machine has booted successfully, you may check it more quickly by logging in with your site_admin account, and running:
-
- sudo /usr/sbin/vps ax
-
-If you have a BootCD older than 3.0, you will need to create a new Boot CD and configuration file. You can find instructions for this at the Technical Contact's Guide:
-
- https://www.planet-lab.org/doc/guides/bootcdsetup
-
-If after following these directions, and either logging in with your site_admin account or seeing the CoMon report of your machine, there is no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
-
-Finally, you can track the current status of your machines using this Google Gadget:
-
- http://fusion.google.com/add?source=atgs&moduleurl=http://monitor.planet-lab.org/monitor/sitemonitor.xml
-
-After another week, we will disable all slices currently running on PlanetLab. Because this action will directly affect all users of these slices, these users will also be notified at that time.
-
-Thank you for your help,
- -- PlanetLab Central (support@planet-lab.org)
-""")
-
- newdown_three=("""PlanetLab node(s) down: %(loginbase)s""",
-"""
-Hello,
-
-As part of PlanetLab node monitoring, we noticed the following nodes were down at your site:
-
-%(hostname_list)s
-We understand that machine maintenance can take time. We're writing again because our previous correspondences, sent first to the registered Technical Contact then the the Site PI, have gone unacknowledged for at least two weeks, and we need your help returning these machines to their regular operation. This is the third time attempting to contact someone in regard to these machines at your site. So, while we wait for the machines to return to their regular operation all current slice activity will be suspended. Current experiments will be stopped and will not be be able to start again until there is evidence that you have begun to help with the maintenance of these machines.
-
-To help, please confirm that a verison 3.0 or greater BootCD is installed in the machine. Then, after checking that the node is properly networked, power cycle the machine. Note that rebooting the machine may not fully resolve the problems we are seeing. Once the machine has come back up, please visit the Comon status page to verify that your node is accessible from the network. It may take several minutes before Comon registers your node. Until that time, visiting the link below will return the message 'could not find requested table - probably empty'.
-
- http://summer.cs.princeton.edu/status/tabulator.cgi?table=nodes/table_%(hostname)s&limit=50
-
-If the machine has booted successfully, you may check it more quickly by logging in with your site_admin account, and running:
-
- sudo /usr/sbin/vps ax
-
-If you have a BootCD older than 3.0, you will need to create a new Boot CD and configuration file. You can find instructions for this at the Technical Contact's Guide:
-
- https://www.planet-lab.org/doc/guides/bootcdsetup
-
-Finally, you can track the current status of your machines using this Google Gadget:
-
- http://fusion.google.com/add?source=atgs&moduleurl=http://monitor.planet-lab.org/monitor/sitemonitor.xml
-
-If after following these directions, and either logging in with your site_admin account or seeing the CoMon report of your machine, there is no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
-
-Thank you for your help,
- -- PlanetLab Central (support@planet-lab.org)
-""")
-
- newbootcd_one=(""" Planetlab nodes need a new BootCD: %(loginbase)s""", # : %(hostname)s""",
-"""As part of PlanetLab node monitoring, we noticed the following nodes have an out-dated BootCD:
-
-%(hostname_list)s
-This usually implies that you need to update the BootCD and node configuration file stored on the read-only media (either the all-in-one ISO CD, floppy disk, or write-protected USB stick).
-
-To check the status of these and any other machines that you manage please visit:
-
- http://comon.cs.princeton.edu/status
-
-Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
-
- https://www.planet-lab.org/doc/guides/bootcdsetup
-
-If your node returns to normal operation after following these directions, then there's no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
-
-Thank you for your help,
- -- PlanetLab Central (support@planet-lab.org)
-""")
-#After a week, we will disable your site's ability to create new slices. Because this action will directly affect your site's registered PI, we will also CC the PI for help at that time.
-
- newbootcd_two=(""" Planetlab nodes need a new BootCD: %(loginbase)s""", # : %(hostname)s""",
-"""As part of PlanetLab node monitoring, we noticed the following nodes have an out-dated BootCD:
-
-%(hostname_list)s
-This usually implies that you need to update the BootCD and node configuration file stored on the read-only media (Either the all-in-one ISO CD, floppy disk, or write-protected USB stick).
-
-We're writing again because our previous correspondence, sent only to the registered Technical Contact, has gone unacknowledged for at least a week, and we need your help returning these machines to their regular operation. We understand that machine maintenance can take time. So, while we wait for the machines to return to their regular operation, slice creation has been suspended at your site. No new slices may be created, but the existing slices and services running within them will be unaffected.
-
-To check the status of these and any other machines that you manage please visit:
-
- http://comon.cs.princeton.edu/status
-
-Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
-
- https://www.planet-lab.org/doc/guides/bootcdsetup
-
-If your node returns to normal operation after following these directions, then there's no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
-
-After another week, we will disable all slices currently running on PlanetLab. Because this action will directly affect all users of these slices, these users will also be notified at that time.
-
-Thank you for your help,
- -- PlanetLab Central (support@planet-lab.org)
-""")
- newbootcd_three=(""" Planetlab nodes need a new BootCD: %(loginbase)s""", # : %(hostname)s""",
-"""As part of PlanetLab node monitoring, we noticed the following nodes have an out-dated BootCD:
-
-%(hostname_list)s
-This usually implies that you need to update the BootCD and node configuration file stored on the read-only media (Either the all-in-one ISO CD, floppy disk, or write-protected USB stick).
-
-We understand that machine maintenance can take time. We're writing again because our previous correspondences, sent first to the registered Technical Contact then the the Site PI, have gone unacknowledged for at least two weeks, and we need your help returning these machines to their regular operation. This is the third time attempting to contact someone in regard to these machines at your site. So, while we wait for the machines to return to their regular operation all current slice activity will be suspended. Current experiments will be stopped and will not be be able to start again until there is evidence that you have begun to help with the maintenance of these machines.
-
-To check the status of these and any other machines that you manage please visit:
-
- http://comon.cs.princeton.edu/status
-
-Instructions to perform the steps necessary for a BootCD upgrade are available in the Technical Contact's Guide.
-
- https://www.planet-lab.org/doc/guides/bootcdsetup
-
-If your node returns to normal operation after following these directions, then there's no need to respond to this message. However, if there are any console messages relating to the node's failure, please report them to PlanetLab support (support@planet-lab.org) so we can help resolve the issue. Including this message in your reply will help us coordinate our records with the actions you've taken.
-
-Thank you for your help,
- -- PlanetLab Central (support@planet-lab.org)
-""")
- pcuthankyou_one=("""Thank you for correcting your PlanetLab node PCU - %(loginbase)s""",
- """
-While monitoring your site, we noticed that the following PCU *improved* their states:
-
-%(hostname_list)s
-Often, system administration is a thankless job, but not today. :-)
-
-Thank you!
- -- PlanetLab Central (support@planet-lab.org)
- """)
-