Repository navigation
docs: add Coming from VMware, Requirements, and Automation for Talos Director - #860
sterlingkoch wants to merge 1 commit into
Conversation
sterlingkoch
added
documentation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
📋 Automated documentation review
|
| @@ -0,0 +1,22 @@ | |||
| --- | |||
| title: Automation | |||
There was a problem hiding this comment.
i am not sure i can deduce what this page is about from the title automation, and this is especially important, when i am looking for a page through the navbar, or through search or maybe even using claude
| @@ -0,0 +1,22 @@ | |||
| --- | |||
| title: Automation | |||
There was a problem hiding this comment.
i feel like this page, could be folded into another page, but its definitely up for discussion. i also dont want us to crowd the overview section too much. but then again up for discussion as well
| @@ -0,0 +1,53 @@ | |||
| --- | |||
| title: Coming from VMware | |||
There was a problem hiding this comment.
i dont know if this page's title is so different from the Migrate from vmware title. Maybe a more descriptive title
Also we mention VMWare so much already, probably the third page dedicated to VMware, i worry its starting to lean markety
|
|
||
| **VMware software stays VMware's.** Warm migrations use VMware's Virtual Disk Development Kit (VDDK) when it is available. Talos Director does not bundle it, so you upload it from your own VMware entitlement. See [What Happens During a Migration](/director/compute/what-happens-during-a-migration). | ||
|
|
||
| ## Moving your VMs |
There was a problem hiding this comment.
i think the migrate from vmware page should also link to this page, what do you think?
| | VMware Tools | QEMU guest agent and VirtIO drivers | Installed in the guest. The migration engine removes VMware Tools during conversion. | | ||
| | vSphere Kubernetes Service | Kubernetes clusters | Talos Linux clusters on VMs, created from the same console and managed through Omni. See [Kubernetes Clusters](/director/kubernetes/kubernetes-clusters). | | ||
|
|
||
| ## What is different |
There was a problem hiding this comment.
also i think a more descriptive title here
This branch was successfully deployed
2 participants
What
Three new pages under Overview: Coming from VMware, Requirements and Supported Platforms, and Automation. Also adds them, How Talos Director Works, and What Happens During a Migration to the "where to go next" list on What Is Talos Director?
Why
Most Director evaluators are moving off vSphere. They want to know what our names are for the things they already use, what hardware and storage are validated, and what they can automate. None of that has a page today.
Change
coming-from-vmware.mdx: a table of about 20 vSphere terms mapped to Talos Director (vCenter, ESXi, DRS, HA, vMotion, EVC, datastores, port groups, NSX DFW, content libraries, VKS, and so on), what works differently, and where to start a migration.requirements.mdx: servers, storage, networking, guests, Kubernetes, and migration sources, each marked Validated, Supported, or Roadmap, plus host and migration requirements.automation.mdx: the REST API and its OpenAPI specification, the Equivalent CLI / API panel, Terraform after GA, andkubectlaccess. SDKs and other tools get added once it's confirmed which ones customers can use.director.yaml, the regenerateddocs.json, and five links on What Is Talos Director?Testing
make style-check-changed-localandnpx mint dev.npx mint broken-linkspasses once docs: add What Happens During a Migration for Talos Director #858 and docs: add How Talos Director Works #859 are in.