4 installfailed = """Once the node meets these requirements, please reinitiate the install
7 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
9 Update the BootState to 'Reinstall', then reboot the node.
11 If you have already performed this step and are still receiving this
12 message, please reply so that we may investigate the problem.
15 # Load default message templates
17 {'message_id': 'Verify account',
18 'subject': "Verify account registration",
20 Please verify that you registered for a %(PLC_NAME)s account with the
21 username %(email)s by visiting:
23 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/persons/register.php?id=%(person_id)d&key=%(verification_key)s
25 You must wait for this account to be approved before you can begin using it, please be patient.
27 If you did not register for a %(PLC_NAME)s account, please ignore this
28 message, or contact %(PLC_NAME)s Support <%(PLC_MAIL_SUPPORT_ADDRESS)s>.
32 {'message_id': 'New PI account',
33 'subject': "New PI account registration from %(first_name)s %(last_name)s <%(email)s> at %(site_name)s",
35 %(first_name)s %(last_name)s <%(email)s> has signed up for a new
36 %(PLC_NAME)s account at %(site_name)s and has requested a PI role. PIs
37 are responsible for enabling user accounts, creating slices, and
38 ensuring that all users abide by the %(PLC_NAME)s Acceptable Use
41 Only %(PLC_NAME)s administrators may enable new PI accounts. If you
42 are a PI at %(site_name)s, please respond and indicate whether this
43 registration is acceptable.
45 To view the request, visit:
47 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/persons/index.php?id=%(person_id)d
51 {'message_id': 'New account',
52 'subject': "New account registration from %(first_name)s %(last_name)s <%(email)s> at %(site_name)s",
54 %(first_name)s %(last_name)s <%(email)s> has signed up for a new
55 %(PLC_NAME)s account at %(site_name)s and has requested the following
58 To deny the request or enable the account, visit:
60 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/persons/index.php?id=%(person_id)d
64 {'message_id': 'Password reset requested',
65 'subject': "Password reset requested",
67 Someone has requested that the password of your %(PLC_NAME)s account
68 %(email)s be reset. If this person was you, you may continue with the
71 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/persons/reset_password.php?id=%(person_id)d&key=%(verification_key)s
73 If you did not request that your password be reset, please contact
74 %(PLC_NAME)s Support <%(PLC_MAIL_SUPPORT_ADDRESS)s>. Do not quote or
75 otherwise include any of this text in any correspondence.
79 {'message_id': 'Password reset',
80 'subject': "Password reset",
82 The password of your %(PLC_NAME)s account %(email)s has been
87 Please change it at as soon as possible by visiting:
89 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/persons/index.php?id=%(person_id)d
91 If you did not request that your password be reset, please contact
92 %(PLC_NAME)s Support <%(PLC_MAIL_SUPPORT_ADDRESS)s>. Do not quote or
93 otherwise include any of this text in any correspondence.
97 # Boot Manager messages
98 {'message_id': "installfinished",
99 'subject': "%(hostname)s completed installation",
101 %(hostname)s just completed installation.
103 The node should be usable in a couple of minutes if installation was
108 {'message_id': "insufficientdisk",
109 'subject': "%(hostname)s does not have sufficient disk space",
111 %(hostname)s failed to boot because it does not have sufficent disk
112 space, or because its disk controller was not recognized.
114 Please replace the current disk or disk controller or install
115 additional disks to meet the current hardware requirements.
119 {'message_id': "insufficientmemory",
120 'subject': "%(hostname)s does not have sufficient memory",
122 %(hostname)s failed to boot because it does not have sufficent
125 Please install additional memory to meet the current hardware
130 {'message_id': "authfail",
131 'subject': "%(hostname)s failed to authenticate",
134 %(hostname)s failed to authenticate for the following reason:
138 The most common reason for authentication failure is that the
139 authentication key stored in the node configuration file, does not
140 match the key on record.
142 There are two possible steps to resolve the problem.
144 1. If you have used an All-in-one BootCD that includes the plnode.txt file,
145 then please check your machine for any old boot media, either in the
146 floppy drive, or on a USB stick. It is likely that an old configuration
147 is being used instead of the new configuration stored on the BootCD.
149 2. If you are using Generic BootCD image, then regenerate the node
150 configuration file by visiting:
152 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
154 Under 'Download', follow the 'Download plnode.txt file for %(hostname)s'
155 option, and save the downloaded file as plnode.txt on either a floppy
156 disk or a USB flash drive. Be sure the 'Boot State' is set to 'Boot',
157 and, then reboot the node.
159 If you have already performed this step and are still receiving this
160 message, please reply so that we can help investigate the problem.
164 {'message_id': "notinstalled",
165 'subject': "%(hostname)s is not installed",
168 %(hostname)s failed to boot because it has either never been
169 installed, or the installation is corrupt.
171 Please check if the hard drive has failed, and replace it if so. After
174 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
176 Change the 'Boot State' to 'Reinstall', and then reboot the node.
178 If you have already performed this step and are still receiving this
179 message, please reply so that we may investigate the problem.
183 {'message_id': "missingkernel",
184 'subject': "%(hostname)s is missing its production kernel",
187 %(hostname)s failed to boot because the filesystem is missing its production
190 No action is needed from you at this time; this message is merely
193 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
195 We will investigate the problem shortly.
199 {'message_id': "filesystemcorrupted",
200 'subject': "%(hostname)s may have corrupt filesystem",
203 %(hostname)s failed to boot because the filesystem appears to be corrupted.
205 No action is needed from you at this time; this message is merely
208 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
210 We will investigate the problem shortly.
214 {'message_id': "mountfailed",
215 'subject': "%(hostname)s could not mount filesystem",
218 %(hostname)s failed to boot because the boot scripts could not mount the
221 This could be for a number of reasons. No action is needed from you at this
222 time; this message is merely informational.
224 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
226 We will investigate the problem shortly.
230 {'message_id': "hostnamenotresolve",
231 'subject': "%(hostname)s does not resolve",
234 %(hostname)s failed to boot because its hostname does not resolve, or
235 does resolve but does not match its configured IP address.
237 Please check the network settings for the node, especially its
238 hostname, IP address, and DNS servers, by visiting:
240 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
242 Correct any errors, and change the 'Boot State' to 'Reinstall', and then
245 If you have already performed this step and are still receiving this
246 message, please reply so that we may investigate the problem.
250 # XXX N.B. I don't think these are necessary, since there's no
251 # way that the Boot Manager would even be able to contact the
252 # API to send these messages.
254 {'message_id': "noconfig",
255 'subject': "%(hostname)s does not have a configuration file",
257 %(hostname)s failed to boot because it could not find a PlanetLab
258 configuration file. To create this file, visit:
260 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
262 Click the Configuration File link, and save the downloaded file as
263 plnode.txt on either a floppy disk or a USB flash drive. Change the
264 'Boot State' to 'Reinstall', and then reboot the node.
266 If you have already performed this step and are still receiving this
267 message, please reply so that we may investigate the problem.
271 {'message_id': "nodetectednetwork",
272 'subject': "%(hostname)s has unsupported network hardware",
276 %(hostname)s failed to boot because it has network hardware that is
277 unsupported by the current production kernel. If it has booted
278 successfully in the past, please try re-installing it by visiting:
280 https://%(PLC_WWW_HOST)s:%(PLC_WWW_SSL_PORT)d/db/nodes/?id=%(node_id)d
282 Change the 'Boot State' to 'Reinstall', and then reboot the node.
284 If you have already performed this step and are still receiving this
285 message, please reply so that we may investigate the problem.
290 for message in message_templates: