search

NASA-PDS / registry

PDS Registry provides service and software application necessary for tracking, searching, auditing, locating, and maintaining artifacts within the system. These artifacts can range from data files and label files, schemas, dictionary definitions for objects and elements, services, etc.
https://nasa-pds.github.io/registry
Apache License 2.0
2 stars 2 forks source link

Implement Registry Multi-tenancy with Cognito in the loop #185

Closed jordanpadams closed 2 days ago

jordanpadams commented 1 year ago

💡 Description

Initial design and Serverless, schema setup:

OpenSearch Serverless Authentication

Tools adaptations

Loader Tools
API
Sweeper
Other

Additional Testing

Deployment and Data Migration

Cutover planning

jordanpadams commented 1 year ago

📆 April Status: Completion date expected to be delayed 1 week due to technology comparison needed. No impact on other tasks or deliveries

jordanpadams commented 1 year ago

📆 May status: Delayed 1 sprint due to increase in scope and complexity. Solution has been identified and is underway. Slack built into schedule should alleviate delays. No impact on delivery expected.

jordanpadams commented 1 year ago

📆 June status: Delayed an additional sprint due to increasing scope and learning-on-the-fly with OpenSearch authorization. No impact on build anticipated.

jordanpadams commented 1 year ago

📆 July status: Long delay due to Registry / API issues causing block in https://github.com/NASA-PDS/registry/issues/179. Full deployment with authorization layer to be delayed, but partial deployment expected by delivery date. This delivery will actually cause less impact on users, so the partial deployment will have no effect on success of delivery.

jordanpadams commented 1 year ago

📆 August status: Working this architecture and deployment with MCP SAs. Expected completion by end of month.

jordanpadams commented 12 months ago

📆 September status: tightly coupled with https://github.com/NASA-PDS/cloud-tasks/issues/35, this is in work. Continuing to work issues with serverless approach and AWS team.

jordanpadams commented 10 months ago

📆 October Status: tightly coupled with https://github.com/NASA-PDS/planetary-data-cloud/issues/35, this is in work, but blocked by AWS technical team response times and issues being encountered with the service

jordanpadams commented 9 months ago

📆 November status: Finally unblocked by https://github.com/NASA-PDS/planetary-data-cloud/issues/35, and migration is underway. Working on user management right now. On schedule.

jordanpadams commented 8 months ago

📆 December status: In work. On schedule.

jordanpadams commented 7 months ago

📆 01/2024 status: In work. Delayed 2 sprints. Will impact deferral of https://github.com/NASA-PDS/registry-api/issues/285

jordanpadams commented 6 months ago

📆 02/2024 status: In work. Should be completed be end of sprint (3/7)

jordanpadams commented 5 months ago

📆 03/2024 status: Delayed 2 additional sprints as this is a blocker for the build delivery. I&T will begin on time, but the team will test this last.

jordanpadams commented 4 months ago

📆 04/2024 status: Delayed an additional 2 sprints. Will require separate mini-I&T to complete this delivery and release.

jordanpadams commented 3 months ago

📆 05/2024 status: Delayed 1 additional sprint. Will require separate mini-I&T to complete this delivery and release. Outside of scope of B14.1 delivery.

jordanpadams commented 2 months ago

📆 06/2024 status: Delayed an additional sprint due to additional unforeseen blocking issues. Significant impacts on rest of tasks in Build. All impacts will be review with SWG.

jordanpadams commented 1 month ago

📆 07/2024 status: Progress ongoing, but delayed an additional 2 sprints due to additional unforeseen blocking issues with networking. Significant impacts on rest of tasks in Build. All impacts will be reviewed with SWG.

jordanpadams commented 3 weeks ago

📆 08/2024 status: Progress ongoing, but delayed an additional sprint. To be done by end of this sprint

jordanpadams commented 2 days ago

This is done. Moving remaining sub-tasks to next build since they are some wrap-up activities that are not required for delivery to production.