Develop plan and next steps for transitioning EDSC to NGAP 1.1
Discussion Items
The following is high level overview of what needs to happen to transition EDSC to NGAP 1.1
Send NCIS an overview of application. (Node/Rails/NLP/DB)
Docker file
Ensure NCIS team has access to build and deploy plans in Bamboo
NCIS team does testing in NGAP SIT
Create apps in NGAP Prod for App Sit/UAT/Prod
Distribute keys as needed
NCIS team - GO!
EDSC will need to move through the following environments to demonstrate a high level of confidence that the transition to NGAP Prod will be successful and smooth.
ECS SIT - Internal only for testing
ECS UAT - Internal
ECS Prod - Public
Tim has been added to the EDSC Slack channel and we are all committed to helping each other, communicating, raising issue early, documenting everything, and driving the effort of transitioning to NGAP 1.1 to completion. This will spill over into Sprint 3 of PI7.
Action items
Timothy Goff to confirm if EDSC and CMR can use the same DB or need to migrate/transfer
Timothy Goff to provide guidance on clusters for EDSC
Timothy Goff to determine current EDSC scaling (and other) config and how it maps to new config
Timothy Goff confirm downtime associated with transitioning. We need a deployment/roll-out plan and what should be expected by app owners, dev teams, and end users.
Timothy Goff / user-396c2 to break down transition ticket (
NGAP-1996
-
Getting issue details...STATUS
) into smaller tickets. We need detailed traceability!
NGAP-2145
-
Getting issue details...STATUSNGAP-2146
-
Getting issue details...STATUS
user-396c2 to confirm plan for sprint 3 completion (EDSC SIT to NGAP 1.1 Prod)