What this category's data looks like
For the deployment, operations, and application handover of kindergarten home-school co-education communication, the material source is the deployment environment and the administrator version upgrade page, and the update cadence changes with the image version and migration task records. Category materials include committed items and response times, descriptions of children's performance, classification of parents' demands, and notification delivery records. When these materials enter the deployment and upgrade function, their roles differ: committed items and response times are used to check the response closed loop in the handover form, descriptions of children's performance are used to compare whether observation records and statements are consistent, classification of parents' demands is used to confirm whether feedback is categorized, and notification delivery is used to verify delivery status. In terms of field characteristics, the deployment side focuses on image version identifiers and migration task records, while the business side focuses on item-by-item records in the handover form. Deployment status and operation records serve as handover-ready materials and are completed by operations handover and business use. When materials enter this function, first check that the version, connection, and task records are consistent, then check item by item according to the handover form.
Configuration and implementation checks
This step is executed by the deployment environment and the administrator version upgrade page (server-side operation), and outputs the image version, migration task records, and data row index status. The handover-ready deployment status and operation records are then completed by operations handover and business use.
| Object | Check | Verification action |
|---|---|---|
| Main service and commercial edition image versions | Both images are the same target version; check the version identifiers against the version notes | On the version upgrade page, view the version identifiers of both images and check the connection status of MONGODB_URI, PG_URL, and REDIS_URL |
| Historical chunk training task migration | Trigger only after the old instance has been fully stopped and the old task lease has expired; view the task execution record | On the administrator's version upgrade page, view the execution record of this task and confirm the task status and trigger time |
| Knowledge base rebuild status migration | Trigger only after the previous migration is complete; compare the time and status of the two records | Compare the time and status of the two migration records and confirm the dependency order |
| Data row index status | After migration, it is a new index status system; sample one data row and check the status field | Sample one data row and check the index status field to confirm it is not an old marker |
Three common errors
- Symptom: committed items and response times are missing from the handover form, and parents' demands are not categorized. Cause: deployment status records were not synchronized to the business handover, resulting in commitments not being responded to and feedback not being categorized.
- Symptom: descriptions of children's performance do not match observation records, and notification delivery records are inconsistent with the handover form. Cause: when business materials entered the deployment function, they were not compared item by item according to the category's verification dimensions.
- Symptom: the service can start, but the data row status is still an old marker, or the script execution reports an error. Cause: the two image versions are inconsistent, or the migration script trigger order and dependency relationships were not checked.
How to verify the setup
Acceptance for this function: check the version identifiers of the two images, then check the execution records of the two migration scripts in order, and confirm the DB_MAX_LINK connection and data row index status.
Business test: check once item by item according to the handover form and see which record is missing.
- On the version upgrade page, view the version identifiers of the two images and check the migration task records and data row index status.
- Check item by item according to the handover form: committed items and response times, descriptions of children's performance, classification of parents' demands, and notification delivery records.