VMware docs for migrating existing docker compose projects to k3s #1209
Conversation
Co-authored-by: Ashley <[email protected]>
…er compose to a k3s setup
|
|
||
| We will want to copy the data from the recently shut-down VM above to a new vmdk disk file that we will mount onto our k3s control-plane server. Copying the disk will ensure we have a backup plan if anything goes wrong during our migration process. This will keep the original project data intact. | ||
|
|
||
| govc device.info -vm /<datacenter_name>/vm/<sub_dir> |
There was a problem hiding this comment.
@Hareet I'd suggest changing this to govc device.info -vm /<datacenter_name>/vm/vm_name. sub_dir suggests a dir within a VM is being targeted by the command.
|
|
||
| govc device.info -vm /<datacenter_name>/vm/<sub_dir> | ||
|
|
||
| Example of above output: |
There was a problem hiding this comment.
@Hareet I propose changing this to Example *subset* of the above output highlighting the SAN disk to clarify that the output from this command is a lot more.
|
|
||
| Take note of the .vmdk file name from the above output, as well as the datastore name. | ||
|
|
||
| govc datastore.ls -ds=<datastore_name> <sub-dir> . |
There was a problem hiding this comment.
@Hareet I had to specify the data centre to run this command successfully. Either export GOVC_DATACENTER=x or govc datastore.ls -dc=<datacenter_name> -ds=<datastore_name> <sub-dir> .
|
@Hareet Can you have a look at Reagan's suggestions? |
|
@Hareet what is the plan with this PR? Can we merge it? Does it need extra work? cc @mrjones-plip |
|
Thanks @andrablaj ! I've moved the docs to the correct locations, merged main, and merged troubleshooting section to be a sub section. I thiiiink this is good to go then with possibly one non-subjective comment from Reagan, but I really defer to @Hareet on if what I did was OK and how much work this needs. |
|
@mrjones-plip, considering the work you've been leading on archiving migration pages, is this PR still needed? We should merge it if still necessary - or close it if outdated. |
|
This still seems relevant, as I believe it's very close to what MoH KE is doing right now. @Hareet - I'll merge this tomorrow unless I hear a "wait - needs fixes before merging!" from you (feel free to then take ~week to add the fixes) Thanks both! |
Hmm... tough balance. I think it's pretty stale. MoH-KE probably went through the GUI / I really don't know what they did. I'd wager it's better to close this as old, and let them or ask them to open a more relevant, newer one. This was pretty specific to eCHIS-KE at that time (VMware versions and permissions), so I'm not sure how many other partners would really use it. It won't do much harm being there, so either way is fine. |
|
thanks! Less is more, I'll close and won't merge. This PR is here for the never forgetting if push comes to shove. |
No description provided.