-
Couldn't load subscription status.
- Fork 59
🌱 Disable FastDeploy+Direct / NVRAM file support #1081
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
akutz
wants to merge
1
commit into
vmware-tanzu:main
from
akutz:feature/fast-deploy-disable-direct-mode
Closed
🌱 Disable FastDeploy+Direct / NVRAM file support #1081
akutz
wants to merge
1
commit into
vmware-tanzu:main
from
akutz:feature/fast-deploy-disable-direct-mode
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
afdc984 to
a8091dd
Compare
This patch temporarily disables FastDeploy+Direct mode as well as support for FastDeploy with NVRAM files. They may both be re-enabled by setting a single flag to true. This patch is required to mitigate a bug in vpxd on main related to vSAN datastores. Currently they do not support creating VMs using an explicit path.
a8091dd to
e56e778
Compare
|
Replaced by #1084. |
Minimum allowed line rate is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do, and why is it needed?
This patch temporarily disables FastDeploy+Direct mode as well as support for FastDeploy with NVRAM files. They may both be re-enabled by setting a single flag to true.
This patch is required to mitigate a bug in vpxd on main related to vSAN datastores. Currently they do not support creating VMs using an explicit path.
Which issue(s) is/are addressed by this PR? (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes
NAAre there any special notes for your reviewer:
This patch has been validated on two testbeds:
Non-vSAN
vSAN
ls -p -w1 /vmfs/volumes/vsanDatastore >/tmp/before-vm-1.txtThe following VM was deployed:
The VM specifies direct mode which should fallback gracefully to deploy OVF, which we can see in the following VM Op logs:
The VM does power on and get an IP, so it works:
On the ESXi host let's list the contents of the
/vmfs/volumes/vsanDatastorefolder:ls -p -w1 /vmfs/volumes/vsanDatastore >/tmp/after-vm-1.txtAnd let's verify that the only additional folders in the vsanDatastore are the friendly name symlink and the real folder for the newly created VM:
The only new files are:
f1cb9268-0608-e425-a857-0200631fbd42-- the VM's actual directorymy-vm-1-direct-- the symlink vSAN creates pointing to the VM's actual directoryThe following VM was deployed:
The VM specifies direct mode which should fallback gracefully to deploy OVF, which we can see in the following VM Op logs:
The VM does power on and get an IP, so it works:
On the ESXi host let's list the contents of the
/vmfs/volumes/vsanDatastorefolder:ls -p -w1 /vmfs/volumes/vsanDatastore >/tmp/after-vm-2.txtAnd let's verify that the only additional folders in the vsanDatastore are the friendly name symlink and the real folder for the newly created VM:
The only new files are:
ddcd9268-cff8-bf07-e393-0200637b65a8-- the VM's actual directorymy-vm-2-linked-- the symlink vSAN creates pointing to the VM's actual directoryPlease add a release note if necessary: