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

Capability to determine make image behavior due to sysprep. #6

Open
binod33 opened this issue Aug 5, 2015 · 3 comments
Open

Capability to determine make image behavior due to sysprep. #6

binod33 opened this issue Aug 5, 2015 · 3 comments

Comments

@binod33
Copy link

binod33 commented Aug 5, 2015

Some clouds like azure does not run sysprep on VMs automatically and requests the users to verify if the sysprep has been run or not before making an image from that particular VM. If dasein can tell users which clouds does not run sysprep automatically or provides the verification option via capability, it might easier for the user to be aware of these cases before imaging a vm.

@drewlyall
Copy link
Contributor

I don't believe there are any clouds that automatically run sysprep when imaging the VM. Obviously Azure does not but neither does AWS or GCE or vSphere.
I'm not exactly sure what capability we would be putting in place here?

@binod33
Copy link
Author

binod33 commented Sep 30, 2015

AWS generates new windows vm passwords as a default behavior even when launching from a non sysprepped image. But in case of Azure, sysprepped images is necessary in order for the user provided credentials to be set in the vm during launch. So maybe a capability to describe such behavior in cloud like
settingBoopstrapUserRequiresSyspreppedImage

@drewlyall
Copy link
Contributor

That's getting into awfully hypervisor level stuff, not really cloud level.
Dasein shouldn't really know nor care whether you're sysprepping an image.
And AWS specifically recommends that you do...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants