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

VM OU Customization #2275

Open
PierreNa opened this issue Dec 19, 2024 · 4 comments · May be fixed by #2276
Open

VM OU Customization #2275

PierreNa opened this issue Dec 19, 2024 · 4 comments · May be fixed by #2276

Comments

@PierreNa
Copy link

PierreNa commented Dec 19, 2024

SUMMARY

Since vSphere 8u2 a new feature is available on Policies and Profiles > VM Customization Specifications interface.
Right now we can specify Active Directory OU directly on customization.

image

ISSUE TYPE

We've tested this new feature, and apparently the customisation call works fine, but it doesn't apply the specified OR path.

image

From what I've been able to see in the function code, it doesn't take this parameter.
vmware_guest_customization_info.py

COMPONENT NAME

vmware_guest_customization_spec

ADDITIONAL INFORMATION

This is a really useful feature in complicated environments where the operator does not have access to the AD. It makes it possible to be more autonomous and more relevant when executing workflows.

ihumster pushed a commit to ihumster/community.vmware that referenced this issue Dec 20, 2024
@ihumster ihumster linked a pull request Dec 20, 2024 that will close this issue
@ihumster
Copy link
Collaborator

@PierreNa Hello. You were looking at the wrong module. Customization is done in the vmware_guest module. I added a new parameter to the customization section, as PR #2276 will merge into the main branch - you can use this parameter to set domainOU when deploying a VM.

@PierreNa
Copy link
Author

Ok thank you so much, if I'm not wrong this feature are not implemented today ?

@ihumster
Copy link
Collaborator

@PierreNa Yes, this functionality appeared only in vSphere 8.0U2 and since then no one has raised the question of its relevance. But it looks like it wouldn’t be very difficult to implement, which is what I did. The burden of testing will be on you because... I’m afraid I simply won’t be able to implement tests for this function, and I currently have nowhere to test it on my own stand.

@PierreNa
Copy link
Author

@ihumster, OK, so it may take a long time before this is implemented in branch main.

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

Successfully merging a pull request may close this issue.

2 participants