nasa / opera-sds-int

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

OPERA-SDS-VnV-10: Verify the interface for control of the operational system

LucaCinquini opened this issue · comments

Verification Activity:

Verify that the interface may allow for control of the operational system, including:

  • current processing load / activity
  • identification of problems / issues in the system
  • ability to halt or stop a given process
  • monitor the health of the SDS
  • ability to monitor on a per-product basis
  • ability to initiate on-demand jobs
  • (possibly more)

Suggested approach for L3_DSWx_HLS:

o Navigate to the SDS "on-demand" UI (URL? Name?) and submit L3_DSWx_HLS jobs for a pre-selected time period and geographic extent. Verify that the jobs start.

o While the jobs are running, navigate to the SDS UI (URL? Name?) to monitor the system load and activity

o While the jobs are running, navigate to the SDS UI (URL? Name?) to sub-select a single job and monitor its progress throughout its lifecycle (download inputs, execute PGE, send CNM message, output archive) to a successful completion. Look for system jobs related to the same product, but with different names.

o While the jobs are running, navigate to the SDS UI (URL? Name?) to sub-select a single job, wait until the job is entering the PGE phase, stop the job, then restart it (Question: is this even possible with HySDS?)

o While the jobs are running, use the AWS console to manually stop one of the worker nodes where the jobs are running. Verify that at least one job fails and that its log shows that the problem can be traced to a failing worker node.

o While the jobs are running, navigate to the SDS UI to monitor the health of the system (URL? Name? Is it Kibana) and check a few key metrics (which ones?)

Work with PCM developers to specify all details.

Ok to transfer to TestRail.