Skip to content
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

VCH Management APIs: Ensure VCH creation log read/write does not assume relationship between image store path and VM path #6729

Closed
zjs opened this issue Nov 8, 2017 · 0 comments
Assignees
Labels
area/api The Vritual Container Host management API component/install kind/debt Problems that increase the cost of other work priority/p2 team/lifecycle

Comments

@zjs
Copy link
Member

zjs commented Nov 8, 2017

See #6665 (comment):

There is a vch.FolderName method that you could call that tells you the directory name of the VM.
It looks like that has been recently changed to only provide the Base name - I am unsure why and @caglar10ur has just left. However this is the call used in lib/install/management/appliance.go:523.

The ImageStores path MAY be the same, but should not be in the case of vSAN - a VM in vSAN MUST have a dedicated namespace and I believe we place the image VMDKS into their own namespace.

@zjs zjs added area/api The Vritual Container Host management API component/install kind/debt Problems that increase the cost of other work team/lifecycle labels Nov 8, 2017
@zjs zjs added this to the Sprint 21 Lifecycle milestone Nov 8, 2017
@zjs zjs self-assigned this Nov 20, 2017
@zjs zjs closed this as completed in #6800 Nov 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api The Vritual Container Host management API component/install kind/debt Problems that increase the cost of other work priority/p2 team/lifecycle
Projects
None yet
Development

No branches or pull requests

1 participant