1 #################### body for messages
3 installfailed = """Once the node meets these requirements, please reinitiate the install
6 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
8 Update the BootState to 'Reinstall', then reboot the node.
10 If you have already performed this step and are still receiving this
11 message, please reply so that we may investigate the problem.
14 # Load default message templates
16 {'message_id': 'Verify account',
17 'subject': "Verify account registration",
19 Please verify that you registered for a %(PLC_NAME)s account with the
20 username %(email)s by visiting:
22 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/persons/register.php?id=%(person_id)d&key=%(verification_key)s
24 You must wait for this account to be approved before you can begin using it, please be patient.
26 If you did not register for a %(PLC_NAME)s account, please ignore this
27 message, or contact %(PLC_NAME)s Support <%(PLC_MAIL_SUPPORT_ADDRESS)s>.
31 {'message_id': 'New PI account',
32 'subject': "New PI account registration from %(first_name)s %(last_name)s <%(email)s> at %(site_name)s",
34 %(first_name)s %(last_name)s <%(email)s> has signed up for a new
35 %(PLC_NAME)s account at %(site_name)s and has requested a PI role. PIs
36 are responsible for enabling user accounts, creating slices, and
37 ensuring that all users abide by the %(PLC_NAME)s Acceptable Use
40 Only %(PLC_NAME)s administrators may enable new PI accounts. If you
41 are a PI at %(site_name)s, please respond and indicate whether this
42 registration is acceptable.
44 To view the request, visit:
46 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/persons/index.php?id=%(person_id)d
50 {'message_id': 'New account',
51 'subject': "New account registration from %(first_name)s %(last_name)s <%(email)s> at %(site_name)s",
53 %(first_name)s %(last_name)s <%(email)s> has signed up for a new
54 %(PLC_NAME)s account at %(site_name)s and has requested the following
57 To deny the request or enable the account, visit:
59 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/persons/index.php?id=%(person_id)d
63 {'message_id': 'Password reset requested',
64 'subject': "Password reset requested",
66 Someone has requested that the password of your %(PLC_NAME)s account
67 %(email)s be reset. If this person was you, you may continue with the
70 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/persons/reset_password.php?id=%(person_id)d&key=%(verification_key)s
72 If you did not request that your password be reset, please contact
73 %(PLC_NAME)s Support <%(PLC_MAIL_SUPPORT_ADDRESS)s>. Do not quote or
74 otherwise include any of this text in any correspondence.
78 {'message_id': 'Password reset',
79 'subject': "Password reset",
81 The password of your %(PLC_NAME)s account %(email)s has been
86 Please change it at as soon as possible by visiting:
88 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/persons/index.php?id=%(person_id)d
90 If you did not request that your password be reset, please contact
91 %(PLC_NAME)s Support <%(PLC_MAIL_SUPPORT_ADDRESS)s>. Do not quote or
92 otherwise include any of this text in any correspondence.
96 # Boot Manager messages
97 {'message_id': "installfinished",
98 'subject': "%(hostname)s completed installation",
100 %(hostname)s just completed installation.
102 The node should be usable in a couple of minutes if installation was
107 {'message_id': "insufficientdisk",
108 'subject': "%(hostname)s does not have sufficient disk space",
110 %(hostname)s failed to boot because it does not have sufficent disk
111 space, or because its disk controller was not recognized.
113 Please replace the current disk or disk controller or install
114 additional disks to meet the current hardware requirements.
118 {'message_id': "insufficientmemory",
119 'subject': "%(hostname)s does not have sufficient memory",
121 %(hostname)s failed to boot because it does not have sufficent
124 Please install additional memory to meet the current hardware
129 {'message_id': "authfail",
130 'subject': "%(hostname)s failed to authenticate",
133 %(hostname)s failed to authenticate for the following reason:
137 The most common reason for authentication failure is that the
138 authentication key stored in the node configuration file, does not
139 match the key on record.
141 There are two possible steps to resolve the problem.
143 1. If you have used an All-in-one BootCD that includes the plnode.txt file,
144 then please check your machine for any old boot media, either in the
145 floppy drive, or on a USB stick. It is likely that an old configuration
146 is being used instead of the new configuration stored on the BootCD.
148 2. If you are using Generic BootCD image, then regenerate the node
149 configuration file by visiting:
151 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
153 Under 'Download', follow the 'Download plnode.txt file for %(hostname)s'
154 option, and save the downloaded file as plnode.txt on either a floppy
155 disk or a USB flash drive. Be sure the 'Boot State' is set to 'Boot',
156 and, then reboot the node.
158 If you have already performed this step and are still receiving this
159 message, please reply so that we can help investigate the problem.
163 {'message_id': "notinstalled",
164 'subject': "%(hostname)s is not installed",
167 %(hostname)s failed to boot because it has either never been
168 installed, or the installation is corrupt.
170 Please check if the hard drive has failed, and replace it if so. After
173 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
175 Change the 'Boot State' to 'Reinstall', and then reboot the node.
177 If you have already performed this step and are still receiving this
178 message, please reply so that we may investigate the problem.
182 {'message_id': "missingkernel",
183 'subject': "%(hostname)s is missing its production kernel",
186 %(hostname)s failed to boot because the filesystem is missing its production
189 No action is needed from you at this time; this message is merely
192 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
194 We will investigate the problem shortly.
198 {'message_id': "filesystemcorrupted",
199 'subject': "%(hostname)s may have corrupt filesystem",
202 %(hostname)s failed to boot because the filesystem appears to be corrupted.
204 No action is needed from you at this time; this message is merely
207 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
209 We will investigate the problem shortly.
213 {'message_id': "mountfailed",
214 'subject': "%(hostname)s could not mount filesystem",
217 %(hostname)s failed to boot because the boot scripts could not mount the
220 This could be for a number of reasons. No action is needed from you at this
221 time; this message is merely informational.
223 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
225 We will investigate the problem shortly.
229 {'message_id': "hostnamenotresolve",
230 'subject': "%(hostname)s does not resolve",
233 %(hostname)s failed to boot because its hostname does not resolve, or
234 does resolve but does not match its configured IP address.
236 Please check the network settings for the node, especially its
237 hostname, IP address, and DNS servers, by visiting:
239 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
241 Correct any errors, and change the 'Boot State' to 'Reinstall', and then
244 If you have already performed this step and are still receiving this
245 message, please reply so that we may investigate the problem.
249 # XXX N.B. I don't think these are necessary, since there's no
250 # way that the Boot Manager would even be able to contact the
251 # API to send these messages.
253 {'message_id': "noconfig",
254 'subject': "%(hostname)s does not have a configuration file",
256 %(hostname)s failed to boot because it could not find a PlanetLab
257 configuration file. To create this file, visit:
259 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
261 Click the Configuration File link, and save the downloaded file as
262 plnode.txt on either a floppy disk or a USB flash drive. Change the
263 'Boot State' to 'Reinstall', and then reboot the node.
265 If you have already performed this step and are still receiving this
266 message, please reply so that we may investigate the problem.
270 {'message_id': "nodetectednetwork",
271 'subject': "%(hostname)s has unsupported network hardware",
275 %(hostname)s failed to boot because it has network hardware that is
276 unsupported by the current production kernel. If it has booted
277 successfully in the past, please try re-installing it by visiting:
279 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
281 Change the 'Boot State' to 'Reinstall', and then reboot the node.
283 If you have already performed this step and are still receiving this
284 message, please reply so that we may investigate the problem.
289 for message in message_templates: