Datasets:

expedient-ai
/

vmware-vcf9-knowledge

@@ -1,116 +1,116 @@
----
-license: cc-by-4.0
-task_categories:
-- question-answering
-language:
-- en
-size_categories:
-- n<1K
-pretty_name: VMware VCF 9 and Broadcom-Era Product Knowledge (Q&A)
-tags:
-- vmware
-- vsphere
-- vsan
-- nsx
-- broadcom
-- cloud-foundation
-- licensing
-- technical-support
-- knowledge-base
-configs:
-- config_name: default
-  data_files: data/train.jsonl
----
-# VMware VCF 9 & Broadcom-Era Product Knowledge (Q&A)
-A curated question-and-answer dataset covering **VMware Cloud Foundation 9**, the
-Broadcom-era VMware product line, **subscription licensing**, and **opening and managing
-support tickets with Broadcom**. 500 entries, each grounded in an official Broadcom/VMware
-source URL.
-## Motivation
-Operations teams and AI assistants working with VMware environments need accurate,
-source-attributed answers about the post-acquisition VMware landscape — new product names
-(Aria → VCF Operations, etc.), the VCF 9 architecture, the subscription licensing model,
-and the Broadcom support portal workflows. Public training corpora predate most of this.
-## Dataset structure
-One JSON object per line in `data/train.jsonl`:
-| Field | Type | Description |
-| --- | --- | --- |
-| `id` | string | Stable id (`vmw-0001` … `vmw-0500`) |
-| `question` | string | The question |
-| `answer` | string | Grounded answer (plain text, 40–130 words typical) |
-| `product` | string | Product/area tag (VCF 9.0, NSX 9, vSAN 9, VCF Operations, Broadcom Support, …) |
-| `category` | string | `architecture` / `product-catalog` / `licensing` / `support-ticketing` / `operations` |
-| `difficulty` | string | `basic` / `intermediate` / `advanced` |
-| `source` | string | Official URL the answer was grounded in |
-### Category distribution
-| Category | Entries |
-| --- | ---: |
-| operations | 138 |
-| product-catalog | 112 |
-| architecture | 100 |
-| licensing | 75 |
-| support-ticketing | 75 |
-Difficulty mix: 145 basic / 224 intermediate / 131 advanced.
-## Coverage highlights
-- **VCF 9 architecture** — release (17 June 2025, build 24755599), full bill of materials
-  (component versions/builds), VCF Installer, SDDC Manager (UI deprecation), management vs
-  workload domains, NSX 9 (VPCs, vDefend), vSAN 9 (ESA/OSA), vSphere Supervisor + VKS,
-  VCF Operations family renames, FIPS defaults.
-- **Product catalog** — VCF vs vSphere Foundation (VVF), add-on model (vSAN TiB, Private AI
-  Foundation with NVIDIA), HCX, Live Site Recovery / Live Recovery / Live Recovery Cloud,
-  Tanzu/Kubernetes components, hyperscaler documentation status.
-- **Licensing** — subscription license files replacing 25-char keys, vCenter-anchored
-  assignment, 16-cores-per-CPU minimum (8 for VCF Edge), vSAN TiB capacity, VCF Business
-  Services console (vcf.broadcom.com), connected/disconnected registration, 180-day usage
-  reporting, 90-day post-expiry behavior, pooling/split licenses, version-down rights.
-- **Support & ticketing** — support.broadcom.com workflows, severity definitions and
-  response objectives (Sev 1: 30 min; Sev 2–4: 2/4/8 business hours per the Broadcom
-  Maintenance Policy Handbook), case content requirements, diagnostic bundles (SDDC Manager
-  SoS with `--collect-all-logs`, vCenter support-bundle export, NSX support bundles),
-  Site IDs (KB 142873), entitlement requirements.
-- **Operations** — upgrade paths (VCF 5.x → 9.0.x, staged online depot, VCF Download Tool),
-  vLCM baseline→image transition, certificate management in VCF Operations, password
-  Update/Remediate/Rotate, fleet backup/restore (SFTP targets, schedules, encryption
-  passphrase), host commissioning/network pools, vSAN stretch clusters, vCenter import.
-## Method and sourcing
-Every entry was authored against official Broadcom sources — `techdocs.broadcom.com`
-(VCF 9.0 documentation, release notes, BOM), `support.broadcom.com`, the Broadcom
-Maintenance Policy Handbook (`docs.broadcom.com`), and Broadcom KB articles — with each
-entry citing the page it was grounded in. Facts that current public pages do not establish
-(e.g., the exact perpetual-sales cutoff date, True Forward commercial terms, VMware-specific
-phone numbers, VVF commercial tier names) are answered with explicit uncertainty rather
-than guessed.
-## Caveats
-- **Time-sensitive values** (release builds, response-time policy, pricing-adjacent terms)
-  reflect official pages as reviewed on **2026-10-30**. Re-verify before contractual use.
-- Broadcom's Maintenance Policy Handbook is general Broadcom policy; VMware-specific
-  support applicability depends on customer contract terms — entries flag this where
-  relevant.
-- Answers are concise operational knowledge, not a substitute for the full official
-  documentation; follow the `source` URL for authoritative detail.
-## Intended use
-- Fine-tuning / SFT for infrastructure-support assistants (fits `messages`-style chat
-  formatting straightforwardly).
-- Retrieval-augmented generation (RAG) knowledge base for VMware/Broadcom operations.
-- Evaluation of LLM knowledge on the Broadcom-era VMware product line.
-Not intended for: contractual licensing decisions, SLA commitments, or as a replacement
-for official Broadcom documentation.

+---
+license: cc-by-4.0
+task_categories:
+- question-answering
+language:
+- en
+size_categories:
+- n<1K
+pretty_name: VMware VCF 9 and Broadcom-Era Product Knowledge (Q&A)
+tags:
+- vmware
+- vsphere
+- vsan
+- nsx
+- broadcom
+- cloud-foundation
+- licensing
+- technical-support
+- knowledge-base
+configs:
+- config_name: default
+  data_files: data/train.jsonl
+---
+# VMware VCF 9 & Broadcom-Era Product Knowledge (Q&A)
+A curated question-and-answer dataset covering **VMware Cloud Foundation 9**, the
+Broadcom-era VMware product line, **subscription licensing**, and **opening and managing
+support tickets with Broadcom**. 504 entries, each grounded in an official Broadcom/VMware
+source URL.
+## Motivation
+Operations teams and AI assistants working with VMware environments need accurate,
+source-attributed answers about the post-acquisition VMware landscape — new product names
+(Aria → VCF Operations, etc.), the VCF 9 architecture, the subscription licensing model,
+and the Broadcom support portal workflows. Public training corpora predate most of this.
+## Dataset structure
+One JSON object per line in `data/train.jsonl`:
+| Field | Type | Description |
+| --- | --- | --- |
+| `id` | string | Stable id (`vmw-0001` … `vmw-0504`) |
+| `question` | string | The question |
+| `answer` | string | Grounded answer (plain text, 40–130 words typical) |
+| `product` | string | Product/area tag (VCF 9.0, NSX 9, vSAN 9, VCF Operations, Broadcom Support, …) |
+| `category` | string | `architecture` / `product-catalog` / `licensing` / `support-ticketing` / `operations` |
+| `difficulty` | string | `basic` / `intermediate` / `advanced` |
+| `source` | string | Official URL the answer was grounded in |
+### Category distribution
+| Category | Entries |
+| --- | ---: |
+| operations | 139 |
+| product-catalog | 113 |
+| architecture | 100 |
+| licensing | 78 |
+| support-ticketing | 74 |
+Difficulty mix: 145 basic / 224 intermediate / 131 advanced.
+## Coverage highlights
+- **VCF 9 architecture** — release (17 June 2025, build 24755599), full bill of materials
+  (component versions/builds), VCF Installer, SDDC Manager (UI deprecation), management vs
+  workload domains, NSX 9 (VPCs, vDefend), vSAN 9 (ESA/OSA), vSphere Supervisor + VKS,
+  VCF Operations family renames, FIPS defaults.
+- **Product catalog** — VCF vs vSphere Foundation (VVF), add-on model (vSAN TiB, Private AI
+  Foundation with NVIDIA), HCX, Live Site Recovery / Live Recovery / Live Recovery Cloud,
+  Tanzu/Kubernetes components, hyperscaler documentation status.
+- **Licensing** — subscription license files replacing 25-char keys, vCenter-anchored
+  assignment, 16-cores-per-CPU minimum (8 for VCF Edge), vSAN TiB capacity, VCF Business
+  Services console (vcf.broadcom.com), connected/disconnected registration, 180-day usage
+  reporting, 90-day post-expiry behavior, pooling/split licenses, version-down rights.
+- **Support & ticketing** — support.broadcom.com workflows, severity definitions and
+  response objectives (Sev 1: 30 min; Sev 2–4: 2/4/8 business hours per the Broadcom
+  Maintenance Policy Handbook), case content requirements, diagnostic bundles (SDDC Manager
+  SoS with `--collect-all-logs`, vCenter support-bundle export, NSX support bundles),
+  Site IDs (KB 142873), entitlement requirements.
+- **Operations** — upgrade paths (VCF 5.x → 9.0.x, staged online depot, VCF Download Tool),
+  vLCM baseline→image transition, certificate management in VCF Operations, password
+  Update/Remediate/Rotate, fleet backup/restore (SFTP targets, schedules, encryption
+  passphrase), host commissioning/network pools, vSAN stretch clusters, vCenter import.
+## Method and sourcing
+Every entry was authored against official Broadcom sources — `techdocs.broadcom.com`
+(VCF 9.0 documentation, release notes, BOM), `support.broadcom.com`, the Broadcom
+Maintenance Policy Handbook (`docs.broadcom.com`), and Broadcom KB articles — with each
+entry citing the page it was grounded in. Facts that current public pages do not establish
+(e.g., the exact perpetual-sales cutoff date, True Forward commercial terms, VMware-specific
+phone numbers, VVF commercial tier names) are answered with explicit uncertainty rather
+than guessed.
+## Caveats
+- **Time-sensitive values** (release builds, response-time policy, pricing-adjacent terms)
+  reflect official pages as reviewed on **2026-10-30**. Re-verify before contractual use.
+- Broadcom's Maintenance Policy Handbook is general Broadcom policy; VMware-specific
+  support applicability depends on customer contract terms — entries flag this where
+  relevant.
+- Answers are concise operational knowledge, not a substitute for the full official
+  documentation; follow the `source` URL for authoritative detail.
+## Intended use
+- Fine-tuning / SFT for infrastructure-support assistants (fits `messages`-style chat
+  formatting straightforwardly).
+- Retrieval-augmented generation (RAG) knowledge base for VMware/Broadcom operations.
+- Evaluation of LLM knowledge on the Broadcom-era VMware product line.
+Not intended for: contractual licensing decisions, SLA commitments, or as a replacement
+for official Broadcom documentation.