<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><b>Chile EQ Web post-mortem update on action items:</b><br>
<br><font size="3"><b>1) Processes were high on webservers.</b></font>
<br>
<br><font size="3">The number of processes was high (upper-400's to 500+)
for all the webservers, espcecially ehp3 which was causing everything to
slow down and rsyncs to fail (on ehp3 many times, and on ehp1 one time).
This was due to the high amount of web traffic, the ongoing latency
issue with ehp3, and the missing 4th server, ehp4.</font>
<br>
<br><font size="3"><b>ACTION ITEMS:</b></font>
<br>
<br><font size="3">a) test using Blowfish cipher and null cipher, which have
less (or no) encryption but less overhead also - Chris, Eric</font> - <b>COMPLETE</b><br><font size="3">b) test Eric's pushit script that includes error handling
- Chris, Eric</font> - <b>COMPLETE</b>, but needs to be modified by Chris<br><font size="3">c) move ehp3 to Menlo - Stan & Chris</font> - <b>no progress</b><br>
<br><font size="3">---</font>
<br><font size="3"><b>2) RSS feed appears to be getting corrupted.</b></font>
<br>
<br><font size="3">Clients that use the EQ RSS feed are encountering problems
that appear to be related to corrupted feeds. Wan entered a ticket
for this in Trac (#926) which has been assigned to Jeremy.</font>
<br>
<br><font size="3"><b>ACTION ITEMS:</b></font>
<br>
<br><font size="3">a) look into RSS feed problems - Jeremy</font> - user error - <b>COMPLETE</b><br>
<br><font size="3">---</font>
<br><font size="3"><b>3) PAGER failures with PDL.</b></font>
<br>
<br><font size="3">Sometime between 9:03 am and 1:54 pm on Saturday, February
27, the prototype PDL client running on losspager1 stopped transmitting
content to ehpmaster. That client is configured to send PAGER content
to ehpmaster and ehpbackup. Interestingly (but not usefully), it
continued to transmit data to ehpbackup. We saw this same behavior
during the Haiti response, leading me to believe that this behavior has
something to do with excessive network "load" on the PDL client.<br>
<br>
We experience similar behavior on ehpmaster, which has a PDL client configured
to receive PAGER content from losspager1. This client is configured
to call two scripts when it receives content:<br>
1) A logging script<br>
2) The PAGER indexer script.<br>
<br>
At (at least) three different times on Feb 27, the PDL client failed to
call the indexing script when receiving PAGER content. In each case,
the client called the script when a later bundle of PAGER content was received.</font>
<br>
<br><font size="3"><b>ACTION ITEMS:</b></font>
<br>
<br><font size="3">a) test the current production version of PDL in the PAGER
development environment; the PDL client must be reliable - Mike, Jeremy</font> - <b>unknown</b><br><font size="3">b) implement a stop/restart every 24 hours and try this
when things get hung - Mike</font> - <b>unknown</b><br>
<br><font size="3">---</font>
<br><font size="3"><b>3) Tsunami add-ons did not work as expected.</b></font>
<br>
<br><font size="3">The tsunami warning centers didn't send any updates after
the first add-on, or they did but were not associated with the event since
they were using their own eventID rather than the authoritative eventID.
Manual add-ons for tsunami alerts were not possible, and general
information links were placed in the wrong section on the Tsunami tab.</font>
<br>
<br><font size="3"><b>ACTION ITEMS:</b></font>
<br>
<br><font size="3">a) create an add-on type for general info tsunami links
- Jeremy</font> - <b>COMPLETE</b><br><font size="3">b) look into using warning center alerts to trigger add-on
links - Jeremy</font> - will not do - <span class="Apple-style-span" style="font-weight: bold; ">COMPLETE</span><br><font size="3">c) add recenteqs check for superceded events to that add-ons
with non-authoritative eventIDs can be still added to the event page -
Jeremy</font> - <b>unknown</b><br><font size="3">d) modifications to allow access to the non-authoritative
eventID add-ons through the EQintheNews Admin - Jeremy</font> - <b>unknown</b><br><font size="3">e) find out web stats of pageviews for tsunami alerts
- Lisa</font> - <b>meeting with Paul 3/18</b><br><font size="3">f) talk to Paul about which links he thinks we should
be using - Lisa </font> - <b>meeting with Paul 3/18</b><br><font size="3">g) look at Tsunami Warning Center websites for links we
think we should be using - Madeleine</font> - <b>unknown</b><br>
<br><font size="3"><b>4) Aftershock Map procedure needs to be determined.</b></font>
<br>
<br><font size="3">The aftershock map was requested again, and this time
we got the list in a different format than the first or second time. Eric
had to write another parser for the input to create the XML file. Gavin
will continue to give us an updated list every morning until no longer
needed so we can update the map each morning.</font>
<br>
<br><div><font size="3"><b>ACTION ITEMS:</b></font> </div><div><br><font size="3">a) We need to determine a definitive source for the aftershock
list and a standard procedure for the product as it is now; have a meeting.
- Lisa </font> <b>meeting with Paul 3/18</b><br>
<br><font size="3"><b>5) The Executive Summary failed and there was a 20-30
min delay getting it out.</b></font>
<br>
<br><font size="3">The form did not contain validation, so an incorrect user
entry caused it to fail.</font>
<br>
<br></div><div><font size="3"><b>ACTION ITEMS:</b></font> </div><div><br><font size="3">a) Validation will be added to the app. - Matthew</font> - <b>COMPLETE, I think</b><br><font size="3">b) We will recreate the Exec Summary from the ground up
during FY10 using a project plan.</font>
<br>
<br>
<br><font size="3"><b>Additional action items not related to Chile EQ:</b></font>
<br>
<br><font size="3">a) The 2004 Sumatra event and 2006 Gulf of Mexico event
have the same eventID, and their information keeps getting mixed up on
their event pages. Since then, the year has been added to the eventID,
so this will not happen again, but we need to manually change these eventIDs
to include the year as a prefix, and put redirects in place for the old
links. - Jeremy </font> - <b>COMPLETE</b><br>
<br><font size="3">b) Organize a workshop for the DB group, Edge, Hydra,
two new student hires, Scott, and Volkan to share information about the
web architecture and future plans, and the website infrastructure such
as the Admin area, Trac ticketing, documentation, and versioning system.
Scott and Volkan would travel to Golden for the workshop. - Lisa</font> - <b>will do now that Bill Horton has started</b><br>
<br><font size="3">c) Give Gavin PAGER admin privileges in the Admin area.
- Lisa <b>- COMPLETE</b></font><br>
<br></div></body></html>