Skip to content

Registry workshop 2024‐09‐24

Jump to bottom
thomas loubrieu edited this page Sep 24, 2024 · 6 revisions

Agenda

  1. beta-test status from Engineering node, lesson learned so far.
  2. Other feedback from the beta testers
  3. Q&A

Beta-test status from Engineering node, lesson learned so far.

Per node status

  • IMG: change password date expired, account re-created last week
  • PSA: account work, not feedback for a few weeks now
  • SBN: setting up Dev environment for tests
  • GEO: harvest works successfully as well as status queries with registry-client. Experimenting now with parallel jobs.

Overall lessons learned:

Issue with the change password link in an interim manual

Fixed

Confusion between former registry login and new ones

Need to add details/warning in the user's manual.

Expiration of the temporary password, 7 days

Adapt the validity period ? Add something in the manual, in the email ?

Ideas:

  • synchronize information sending with Node activity.
  • increase the expiration period to adapt the schedule of the nodes

Security of the information communication

To be discussed with JPL SA's.

Ideas:

  • don't send the username together with the password
  • rotate passwords and communicate when it is going to expire

Order of sections in the manual

Need to revise the organization of the manual.

Issue with web application firewall blocking access

Fixed for short term, all beta-tester node can access in production.

For mid-term, the AWS configuration will be streamlined to simplify the configuration, especially, have a single place to configure the IPs.

Registry-client on-boarding

Required prior knowledge on the OpenSearch API.

Examples with registry-client:

  • use file for query, especially in windows:
  • filters,
  • pagination
  • property names (to be done)
  • distinct values

Short term solution: 101 support for now

Mid-term:

Have a better documentation with query templates.

See PR https://github.com/NASA-PDS/registry-client/pull/17

Access to dashboards

https://github.com/NASA-PDS/registry/issues/323

Protocol in harvest config file

image

Prod vs Test

The software has been thoroughly tested by Engineering node, and is deployed in production, ready for beta test.

However, we understand that you might want to test in a different environment, 2 options:

  • short term: if you have access to JPL VPN, Dev environment
  • mid-term: deployment of a Test instance.

Node names

A bug in harvest makes the node name in property inconsistent.

1 bug: https://github.com/NASA-PDS/harvest/issues/186 1 new requirement: https://github.com/NASA-PDS/harvest/issues/187

We will have a new release of harvest shortly and already loaded product will be fixed by Engineering Node.

Other feedback

GEO harvest logs

Pulling LDD when 404 dialogue with GEO

Q&A

Irma Trejo (ATM node) volunteers to use the registry. Thomas will send her the information package to start using the registry and a new username and password.

Steps before opening to more users

  • wait for the next harvest release to open the registry for more users.
  • improve the documentation wherever needed (see above).
Clone this wiki locally