Ciena Migration Workbench

Drop in Ciena configs

Two upload lanes, deliberately separated. The SAOS 6 source is the migration INPUT (what's on the device today); the SAOS 10 target reference / lab baseline is the migration TARGET context. Generated candidates are output of the generator and live in their own section below — they're never fed back through these upload lanes, and they never appear in the source / baseline pickers.

Candidate-only. Uploads land in the project / reference store but are NEVER applied to a device by ChangeGuard.

Configure target

Shared across every section below. Pick the project, the SAOS 6 source, the baseline reference, and the target model + version once; every action on this page reuses them.

1. Migration Review

Runs POST /api/reviews/ciena-migration and produces a review_id + report. Use the same review_id below to render XML or download the export package.

2. Render Deployable SAOS 10 CLI

Calls POST /api/reviews/{id}/saos10-deployable-config. This is the strict copy/paste SAOS 10 CLI path. It is separate from upgrade ciena-cfg.xml and the NETCONF XML candidate.

2b. Conversion Workflow

Runs the strict deployable check, blocker worklist, and NIM proposal pass together. Output remains candidate-only until evidence or lab validation clears every blocker.

3. Agent Worklist

Calls POST /api/reviews/{id}/saos10-agent-worklist. Returns blocker metadata, candidate lab commands, local evidence citations, and Ansible hints without raw restricted source text.

3b. NIM Candidate Proposals

Calls POST /api/reviews/{id}/saos10-nim-proposals. Uses NVIDIA NIM to propose candidate CLI from the same blocker worklist, evidence hints, and Ansible hints. Proposals do not clear the deployable gate until backed by accepted evidence.

3c. Accuracy Evaluation

Summarizes persisted agent proposal runs and operator/lab feedback for this review. Proposals are not evidence; accepted lab transcripts remain the evidence source.

4. Render SAOS 10 NETCONF Candidate

Calls GET /api/reviews/{id}/saos10-xml. Returns JSON metadata (sections rendered + UNMAPPABLE source verbs the operator must hand-translate) plus the candidate XML inline. The XML is candidate-only — not production approved and not a deployable copy/paste or ciena-cfg.xml restore configuration.

5. Render Upgrade ciena-cfg.xml (direct)

Calls GET /api/reviews/{id}/upgrade-xml. Renders the baseline-overlay ciena-cfg.xml directly — same renderer as the export package but skips the ZIP. Use this when you only need the XML file.

6. Download Export Package

Calls GET /api/reviews/{id}/export-package. Returns a ZIP with review-report.json, template-pack-status.json, ciena-cfg.xml, provenance.json, README.md, and validation-checklist.json.

Reminder: open the bundled README.md before any apply step; check provenance.json for the completion summary.

7. Template Pack / Proposals

Read-only snapshot of the Ciena Template Pack v0.1 for the configured target. Proposal authoring is intentionally not exposed in the UI; the API at /api/vendor-packs/ciena/templates remains available for that workflow.

Suggest from Evidence (advisory)

Draft a template PROPOSAL using the curated KB profile (evidence/ciena/kb_profiles/<target_model>_saos6_to_saos10_v2/). The result lands at status=proposed and must be approved through the existing review workflow before any generator uses it. Evidence is advisory — never production-ready.

Human approval required before generation. The suggester does not approve, and never claims production-readiness.

KB Profile Tools

The KB profile builder writes curated Markdown evidence under evidence/ciena/kb_profiles/<id>/. The Knowledge Base indexes the Markdown directly. This view renders the same files into sanitized HTML for human reading — script / style / iframe / inline event handlers are stripped, the candidate-only banner is preserved, and per-file provenance (source path, repo, commit, source_reference_ids, snippet_ids, redaction status) is surfaced. The rendered HTML is served with X-Robots-Tag: noindex so it never enters search or KB scope.

Note: the HTML view is operator-facing only. The underlying Markdown files stay the KB source of truth and are NOT modified by this view. Build the profile via POST /api/vendor-packs/ciena/evidence/kb-profiles/<id>/build before opening if the profile prefix is empty.

8. References

Counts by source_type. Snippet bodies are restricted and never shown here. Use the dedicated References page to upload, archive, or tombstone references.