# SWSI Development Meeting Notes

Meeting Date: March 26, 2002

Time: 9:30 AM

Place: GSFC, Building 12, rm. E200

**[Attendees:]{.underline}** Cathy Chang, Sue Edwards, Gerry Klitsch,
Sergey Nikhinson, Jerry Rauser, Scott Robinson, Harshna Sampat, and Joe
Stevens

**[Action Items Responses:]{.underline}**

1.  Action Item #37 response -- (Investigate reliability/performance of
    RAID disks for use as a backend server database storage) -- Joe
    noted that RAID disks came in on March 25. Joe asked Scott (and for
    Alan) to begin set-up (this is of high priority). **This Action Item
    has been Closed** (as per Joe), **and another Action Item has been
    opened (AI# 88)** to integrate the RAID Arrays into the backend
    server configuration. Scott noted that the server configuration may
    require a significant amount of down time from testing, and he is to
    use the second backup host for the RAID Arrays. Scott is to start
    this work on the week on April 1 through 5.

2.  Action Item #77 response -- (Setup two new servers for DAS interface
    testing) -- Scott reported that he is still working on the backend
    server working with IP Filters, and is to install new patches to all
    4 machines **(this Action Item has been Closed)**.

3.  [New Action Item]{.underline} -- Joe (and Tom) are to check into the
    status of the two new servers **(see Action Item \# 89)**.

4.  Action Item #79 -- (Check on CCB's status of the SWSI SRD) -- Jerry
    noted that he will give Reginald Brooks a call and check out the
    status of the Requirements Document. Joe stated that we have
    responded to everything to date.

5.  Action Item #81 response -- (Begin work on High Availability (HA)
    and find out what is required for HA software) -- Scott reported
    that he has completed work on the open side, and is progressing with
    work with Solaris 8.

6.  Action Item #86 response -- (Check into the SSH protocol and install
    on the operational servers) -- Scott noted that he is still working
    this item. Scott mentioned an underline problem and is waiting for a
    patch for ZLIB (Sun Patch). Scott is to get IP Filter working and
    get the patch when it is in.

7.  [New Action Item]{.underline} -- Joe questioned whether or not the
    I&T Host have Development Software. Joe actioned himself and Scott
    to look into [not]{.underline} having Development Suites on the I&T
    Hosts **(see Action Item \# 90)**.

8.  Action Item #87 response -- (Find a new area to house the SWSI
    development hardware prior to SWSI going operational) -- It was
    noted that June 1, 2002 looks like the drop-dead date to have SWSI
    out of the Lab. Harshna has talked to John Russell, and Scott has
    talked to Joe Snyder in NCC about this issue. It was also noted that
    it would be ideal to move all the same addresses from Building 12 to
    Building 13. Scott is to check about having IP addresses moved from
    Building 12 to Building 13 **(see Action Item #91)**.

**[Testing Status:]{.underline}**

> **Bugs**

-   NSIA team continuing testing of SWSI Build 3/Patch 6.

> **DAS**

-   Joe reported that Sergey and himself have been working on Bug items
    from DAS testing, and that DAS personnel are coming up to speed
    (learning the system).

-   Sergey is working on alert problems.

> **GP-B**

-   Testing started on March 11.

-   Favorable results from tests.

-   Testing is to continue through April 14.

**[Open Discussion:]{.underline}**

-   Build 3/Patch 7 -- Harshna requested a freeze for March 29 to
    deliver Build 3/Patch 7 by April 1, and that all major Bugs be
    worked/completed before the freeze. Scott is to tag Build 3 into CVS
    and create a Build 4 CVS structure **(see Action item \# 92**).

-   Build 4 activities to begin after the delivery of Build 3 (April 1
    scheduled date).

-   Joe suggested a possible enhancement to the SWSI Main Panel, to
    extend the Panel to depict the availability of DAS/NCC/ANCC
    services, i.e., buttons to display -- (green) for connected, (red)
    for disconnected, etc...

The Connection Panel will show:

> [For DAS:]{.underline} connected (green)/disconnected (red).

[For NCCDS:]{.underline} A top-level connection would indicate
red/yellow/green status. The red color means all the connections for the
user SICs are down. The yellow color means one or more, but not all,
connections for user SICs is down. The green

> Color means all the connections for the user SICs are up. The user
> will be able to click on the top level connection \"button\" to get
> the detailed connection status for all the user SICs. Each SIC
> connection would show the aggregated connection status for that SIC
> (red/yellow/green), i.e. it won\'t have the breakdown of Schedule
> Request connection, Real-Time connection, UPD connection etc... What
> is not defined is how SNIF and SDIF will pass this information to
> Isolator. The options are: (1) define new message between Isolator and
> SNIF/SDIF, (2) modify database schema to store connection status (to
> be stored SNIF/SDIF) and Isolator read it on a periodic basis to send
> it to Client.