Skip to end of banner
Go to start of banner

PTF Environment Checklist

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

EC2

  • 8 EC2 Instances
  • EC2 Instance Type: m6i.2xlarge
  • Cloudwatch dashboard setup

ECS

  • 77 Services
  • 3 Okapi tasks
  • All services have 2 tasks except for: mod-data-import, mod-data-export, mod-quick-marc, mod-data-export-spring, 
  • Run ECS Comparison Tool to check memory and CPU allocations differences against past release's deployment.
  • All services do NOT have R/W split enabled
  • UI built on all 3 tenants (or at least fs09000000)

RDS

  • 2 Database nodes, one read and one write node
  • EC2 instance type: db.r6g.xlarge
  • Performance Insight is enabled on both database nodes
  • Compare database schema against the schema of a DB cluster that was created from scratch to identify if there were any database objects missing. If there are any differences, make them to be like the other environment's schema.
  • Run Vacuum and ANALYZE table on inventory-storage.instance | item | holdings-record tables

Kafka

  • ECS cluster points to ptf-kafka-3
  • The Data Import topics all have 2 partitions each
  • The inventory and search topics all have 2 or 4 partition
  • There are 4 DNS entries in Route 53, each points to a different Kafka cluster broker

OpenSearch

  • ECS cluster points to fse-ptf OpenSearch cluster
  • Inventory records (instances, authority, holdings) are indexed on Elastic Search

Functional

  • Verify DB's CPU and memory utilization are typical (using RDS' monitoring graphs)
  • Verify modules' CPU and memory utilization are typical (using Cloudwatch Dashboard)
  • Go to Inventory app, select Items tab and look at the counts of the facets on the left to see if the counts are typical (in the millions for Available and other facets)
  • Perform a quick CICO test from the interface to see if there are no issues
  • Perform a quick DI test to make sure that everything is working
  • Run Karate smoke tests if possible.



  • No labels