1 / 10

AWIPS RFC Shortfalls Team Update

AWIPS RFC Shortfalls Team Update. Jon Roe OHD/HL/HSEB Semi-Annual RFC HIC Meeting 31 July 2008. Topics. Team genesis 2007 - 2008 activities Current status RFC Configuration Project. Team Genesis. Semi-annual RFC HIC Meeting in Silver Spring on 24 July 2007

eytan
Download Presentation

AWIPS RFC Shortfalls Team Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AWIPS RFC Shortfalls Team Update Jon Roe OHD/HL/HSEB Semi-Annual RFC HIC Meeting 31 July 2008

  2. Topics • Team genesis • 2007 - 2008 activities • Current status • RFC Configuration Project AWIPS RFC Shortfalls Team Update

  3. Team Genesis • Semi-annual RFC HIC Meeting in Silver Spring on 24 July 2007 • RFC HICs noted shortfalls expected in AWIPS’ ability to support RFC mission in AWIPS II era given “black box” migration • Based on long term, not addressed, shortfalls experienced during AWIPS I era AWIPS RFC Shortfalls Team Update

  4. Team Genesis • Jason Tuell, AWIPS II Migration project manager (then), took serious note of concerns • “RFC Shortfalls” team convened soon after composed of Jason, Ronla Henry, Jeff Zimmerman, and Jon Roe supported by the HICs AWIPS RFC Shortfalls Team Update

  5. 2007 – 2008 Activities • Harold Opitz drafted a summary citing the following key areas: • Communication bandwidth • Data storage • Database performance • Service back-up • Computational speed • Initial thought was some improvements could be considered for AWIPS I but these concerns have now been focused on AWIPS II AWIPS RFC Shortfalls Team Update

  6. 2007 – 2008 Activities • Meetings • The OHD & OS&T directors: 14 Aug 07 • The team: 7 Sep 07, 19 Oct 07, 15 Jan 08, 15 May 08, and 19 Jun 08 • RFC local applications (loosely connected to team activities): 7 Jan 08 • Intent was to work action items based on the 5 key areas AWIPS RFC Shortfalls Team Update

  7. 2007 – 2008 Activities • Attention paid mostly to database performance and computational speed • Harold, John Halquist, and Billy Olsen defined and drafted some performance metrics • To measure AWIPS II migration success • To use as targets for improvements • These metrics (and more) will be needed to help define a proper RFC configuration AWIPS RFC Shortfalls Team Update

  8. Current Status • RFC Shortfall concerns have been translated to various AWIPS/OSIP projects • OSIP 07-017, CHPS Infrastructure • OSIP 07-054, Re-evaluate RAX Requirements • OSIP 07-056, RFC Back-up Initiative • OSIP 07-059, RFC Configuration • AWIPS II Extended collection of projects • Team has disbanded as of 20 Jun 08 in favor of pursuing the various AWIPS/OSIP projects • Complicated intertwining of projects • CHPS Project most concerned with providing infrastructure and aiding definition of RFC Configuration but cannot ignore RFC Back-up nor RAX re-evaluation AWIPS RFC Shortfalls Team Update

  9. OSIP 07-059: RFC Configuration Project • Initiated out of RFC Shortfalls team by HSD (Jeff Z.) and OS&T (Edwin W.) • Kick-off meeting held 2 Jul 08 • Current AWIPS architecture based on WFO mission • Project to define proper configuration for RFC mission • Introduction of the River Ensemble Processors (RPs) helps but overall configuration, using other processors in the mix, must be established • Example: RFCs make greater demands on the relational database management system • Two open trouble tickets on shefdecode performance that can’t be fixed with simple AWIPS software fixes • CHPS migration using separate prototype hardware should assist the definition of the RFC configuration • Need to establish performance gap (if any) following hardware refreshes for RPs, DXs, PXs, RAX and the configuration analysis AWIPS RFC Shortfalls Team Update

  10. Discussion? AWIPS RFC Shortfalls Team Update

More Related