Vega SillyTavern cutover: validation, Pangolin repoint, and rollback closure #4

New issue

Closed

opened 2026-07-01 12:30:33 +01:00 by nimmo · 0 comments

nimmo commented

2026-07-01 12:30:33 +01:00

Owner

Goal

Validate the native SillyTavern service on vega, repoint Pangolin to it, and preserve a safe rollback window.

This issue is intended to be self-contained and executable without referring to a local project note.

Acceptance Checklist

Validate newt.service and sillytavern.service status locally on vega.
Confirm the native SillyTavern endpoint responds locally on http://127.0.0.1:8384.
Check recent logs for both services.
Verify /var/lib/SillyTavern/config.yaml is a symlink and /var/lib/SillyTavern/config-source.yaml is readable.
Verify there are no unexpected ownership mismatches under /var/lib/SillyTavern.
Repoint the Pangolin SillyTavern resource to the native Newt instance.
Keep /srv/stacks/sillytavern in place during the rollback window.
If validation fails, execute the rollback steps below.
Only retire the legacy stack after the native service has run cleanly for a while.

Validation Procedure

Validate locally before changing Pangolin:

systemctl status newt.service
systemctl status sillytavern.service
curl -I http://127.0.0.1:8384
journalctl -u newt.service -n 100 --no-pager
journalctl -u sillytavern.service -n 100 --no-pager
sudo test -L /var/lib/SillyTavern/config.yaml
sudo test -r /var/lib/SillyTavern/config-source.yaml
sudo find /var/lib/SillyTavern -xdev ! -user sillytavern -print

If all checks look good, repoint the Pangolin SillyTavern resource to the new native Newt instance.

Rollback Procedure

If validation fails:

sudo systemctl stop sillytavern.service
sudo systemctl stop newt.service
cd /srv/stacks/sillytavern
docker compose up -d

Then repoint Pangolin back to the old Docker/Newt path.

Rollback Notes

If rollback occurs before the temporary mask is removed, run sudo systemctl unmask sillytavern.service so the mask does not survive the migration attempt.
Writes made after native SillyTavern starts exist only in /var/lib/SillyTavern.
Before a later rollback, stop the native service and preserve that directory.
Do not blindly reverse-sync native writes into the legacy tree, because application-version changes may have altered the data format.
Do not delete /srv/stacks/sillytavern until the native service has run cleanly for a while and the rollback window has closed.

Close-Out

This issue is complete only when Pangolin has been repointed successfully, the native service has stayed healthy through the chosen observation window, and the legacy stack is no longer needed as rollback state.

## Goal Validate the native SillyTavern service on `vega`, repoint Pangolin to it, and preserve a safe rollback window. This issue is intended to be self-contained and executable without referring to a local project note. ## Acceptance Checklist - Validate `newt.service` and `sillytavern.service` status locally on `vega`. - Confirm the native SillyTavern endpoint responds locally on `http://127.0.0.1:8384`. - Check recent logs for both services. - Verify `/var/lib/SillyTavern/config.yaml` is a symlink and `/var/lib/SillyTavern/config-source.yaml` is readable. - Verify there are no unexpected ownership mismatches under `/var/lib/SillyTavern`. - Repoint the Pangolin `SillyTavern` resource to the native Newt instance. - Keep `/srv/stacks/sillytavern` in place during the rollback window. - If validation fails, execute the rollback steps below. - Only retire the legacy stack after the native service has run cleanly for a while. ## Validation Procedure Validate locally before changing Pangolin: ```bash systemctl status newt.service systemctl status sillytavern.service curl -I http://127.0.0.1:8384 journalctl -u newt.service -n 100 --no-pager journalctl -u sillytavern.service -n 100 --no-pager sudo test -L /var/lib/SillyTavern/config.yaml sudo test -r /var/lib/SillyTavern/config-source.yaml sudo find /var/lib/SillyTavern -xdev ! -user sillytavern -print ``` If all checks look good, repoint the Pangolin `SillyTavern` resource to the new native Newt instance. ## Rollback Procedure If validation fails: ```bash sudo systemctl stop sillytavern.service sudo systemctl stop newt.service cd /srv/stacks/sillytavern docker compose up -d ``` Then repoint Pangolin back to the old Docker/Newt path. ## Rollback Notes - If rollback occurs before the temporary mask is removed, run `sudo systemctl unmask sillytavern.service` so the mask does not survive the migration attempt. - Writes made after native SillyTavern starts exist only in `/var/lib/SillyTavern`. - Before a later rollback, stop the native service and preserve that directory. - Do not blindly reverse-sync native writes into the legacy tree, because application-version changes may have altered the data format. - Do not delete `/srv/stacks/sillytavern` until the native service has run cleanly for a while and the rollback window has closed. ## Close-Out This issue is complete only when Pangolin has been repointed successfully, the native service has stayed healthy through the chosen observation window, and the legacy stack is no longer needed as rollback state.

nimmo added this to the (deleted) project

2026-07-01 15:51:54 +01:00

nimmo added this to the Vega SillyTavern Cutover milestone

2026-07-01 16:04:06 +01:00

nimmo added the

host:vega

service:sillytavern

phase:validation

project:vega-sillytavern-cutover

labels

2026-07-01 16:05:06 +01:00

nimmo closed this issue