Skip to content

Registry Workshop 2024‐04‐23

Jump to bottom
thomas loubrieu edited this page Apr 23, 2024 · 4 revisions

Agenda

  • Information on the Registry multi-tenant impact on Discipline Nodes
  • Q&A

Registry multitenant impact on discipline nodes

Reminder: We want to use a single Opensearch domain. AWS provides a managed service called serverless which is cost-effective but requires upgrade of the clients (loader tools, api, sweeper)

Status:

  • migration tested
  • initial harvest/registry-mgr developed
  • api proof of concept
  • sweeper upgrade started

Plan:

  • migration in production will start early in May
  • that will include downtime:
    • no more data loaded on current service until new harvest is released by EN and deployed by DN
    • API to access the registry might have downtime as well and be gradually migrated (e.g. first simple search, then membership...)

Action for DN:

  • install the new harvest release
  • upgrade the configuration to connect to the new registry's OpenSearch
  • upgrade the configuration to locate the products/bundles... to be loaded, EN will provide examples and support to upgrade.
  • direct access to the OpenSearch API will be provided. EN will provide a python script for direct access to Opensearch
  • user account could be migrated from the legacy system and or new account can be created.

Need to remove the DN specific API end-point from the API documentation.

Next status by end of April.

EN will email everyone 1 week before DN should stop loading data. Current date is May 6th. Then 3 days ahead of time and when it actually happens.

Downtime should be a couple of weeks.

Q&A

Facets: will the nodes need to tell harvest which fields need to be facetted ? Short answer is no. EN need to provide guidance on how to get facets from the OpenSearch API directly.

Clone this wiki locally