Batch chunks from ingest.py
This commit is contained in:
184
out/946344868/chunks.json
Normal file
184
out/946344868/chunks.json
Normal file
@@ -0,0 +1,184 @@
|
||||
[
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 0,
|
||||
"timestamp": "2:45",
|
||||
"timestamp_sec": 165,
|
||||
"title": "Red Hat 8 to 9 Migration Strategy",
|
||||
"summary": "For enterprise cluster migration with Oracle database: cannot simply add new RHEL9 servers to existing cluster. New servers will have different IDs, breaking DR synchronization. Database connections will increase from 2-4 nodes, potentially overwhelming Oracle sizing. No protective isolation prevents new servers from processing immediately.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 1,
|
||||
"timestamp": "6:41",
|
||||
"timestamp_sec": 401,
|
||||
"title": "Recommended Migration Approaches",
|
||||
"summary": "Three viable migration paths: (1) Build new DR system, disconnect current DR, replicate to temp database, repoint new environment to old database when ready; (2) Use existing DR as temporary migration environment, then rebuild fresh DR; (3) Fresh build against new Oracle database with import/export (loses audit logs, tracking tables, server locks). Fresh build is cleanest if audit trail loss is acceptable.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 2,
|
||||
"timestamp": "10:38",
|
||||
"timestamp_sec": 638,
|
||||
"title": "Edge Server Migration",
|
||||
"summary": "Do not attempt to migrate edge servers \u2014 build new edges from scratch and recreate configuration. Standard cluster allows mixed machine types, but edge clusters require identical machines. Export locks from database before rebuild. Reinstalling edges is preferred if reconfiguration takes more than 15 minutes.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 3,
|
||||
"timestamp": "12:22",
|
||||
"timestamp_sec": 742,
|
||||
"title": "Certificate Handling and Infrastructure Validation",
|
||||
"summary": "Certificates move with import/export; cluster certificate CN is typically the load balancer name, not individual servers. Key validation items: ensure all storage mount points match new servers, verify DNS configuration, confirm LDAP/SSO whitelists new server IPs, whitelist new IPs with mail notification systems and antivirus.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 4,
|
||||
"timestamp": "16:45",
|
||||
"timestamp_sec": 1005,
|
||||
"title": "Zero Downtime Upgrade vs OS Migration Differences",
|
||||
"summary": "ZGU replicates database schema within same database, dynamically switching between schemas. OS upgrade uses classical DR model with separate databases. ZGU maintains same ST version; OS upgrade causes service disruption. ZGU not yet suitable for OS upgrades.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 5,
|
||||
"timestamp": "19:09",
|
||||
"timestamp_sec": 1149,
|
||||
"title": "Database and OS Upgrade Constraints",
|
||||
"summary": "Database OS, version, and hardware upgrades all require complete disconnection from ST \u2014 no ZGU capability exists for these. DR systems allow brief switching but lose tracking table, audit log, and password change history during disconnection window. Always coordinate with database, DNS, and networking teams.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 6,
|
||||
"timestamp": "24:36",
|
||||
"timestamp_sec": 1476,
|
||||
"title": "SMB Connector Protocol and Use Cases",
|
||||
"summary": "SMB connector is a transfer site protocol like SSH/FTP; ST acts as client connecting to Samba server. Connection port is user-specified per transfer site configuration. Designed as folder monitor replacement for cloud/remote access scenarios.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 7,
|
||||
"timestamp": "26:14",
|
||||
"timestamp_sec": 1574,
|
||||
"title": "SMB Performance Limitations",
|
||||
"summary": "SMB creates new connection per file with mount/dismount cycle on each operation \u2014 not recommended for high-volume transfers. Suitable for small datasets (1-10 files per day). For high-frequency transfers, use CFT (Axway's lightweight hop server) for guaranteed delivery with better performance.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 8,
|
||||
"timestamp": "31:42",
|
||||
"timestamp_sec": 1902,
|
||||
"title": "SFTP Authentication Timeout Troubleshooting",
|
||||
"summary": "Five-minute authentication timeout suggests firewall/load balancer closing idle connections. Authentication should complete in under 30 seconds; excessive time indicates server overload or noncompliant SSH implementation. ST connection timeout and idle timeout settings available per transfer site. Test directly from edge using SSH client to isolate issue.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 9,
|
||||
"timestamp": "36:55",
|
||||
"timestamp_sec": 2215,
|
||||
"title": "SSH Server Compliance and Maverick Libraries",
|
||||
"summary": "ST uses Maverick SSH libraries (not OpenSSH), strictly RFC-compliant. Some noncompliant servers behave differently with Maverick vs OpenSSH. If public key signing with RSA-SHA2-512 is slow, try lower cipher/signature algorithms. Maverick stricter than OpenSSH on RFC adherence.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 10,
|
||||
"timestamp": "41:36",
|
||||
"timestamp_sec": 2496,
|
||||
"title": "UNC Path Troubleshooting on Windows Shares",
|
||||
"summary": "ST is a Linux application accessing Windows shares \u2014 not Windows-to-Windows. When desktop can access UNC path but ST cannot: verify path access from ST server directly. Check for typos, trailing spaces, case sensitivity. Try FQDN (server.organization.org) instead of short hostname. Use IP address as last resort.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 11,
|
||||
"timestamp": "46:58",
|
||||
"timestamp_sec": 2818,
|
||||
"title": "Account Maintenance Application Limitations",
|
||||
"summary": "Only one Account Maintenance application can be scheduled system-wide. Cannot run multiple apps with different thresholds. To disable for specific accounts, set threshold to unreachable high number (e.g., 9999 days).",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
},
|
||||
{
|
||||
"video_id": "946344868",
|
||||
"video_url": "https://vimeo.com/946344868",
|
||||
"chapter_index": 12,
|
||||
"timestamp": "51:18",
|
||||
"timestamp_sec": 3078,
|
||||
"title": "Multiple Notification Thresholds Workaround",
|
||||
"summary": "Single Account Maintenance application supports multiple day values in threshold field (e.g., 60, 30, 3). Notifications sent on all specified days. Use 6+ values for redundancy in case server is offline on any single scheduled day. Field accepts multiple comma-separated values.",
|
||||
"transcript": "",
|
||||
"is_demo": false,
|
||||
"frame_description": null,
|
||||
"source": "ask-annie",
|
||||
"series": "ST Best Practices Q&A"
|
||||
}
|
||||
]
|
||||
Reference in New Issue
Block a user