Comprehensive, version sensitive, guest OS listing/validation
Open
Nobody has claimed this yet.
enhancement
help wanted
wishlist
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
Based on input from here we suspect that the GuestOS list needs to change based on which version of the API we're talking to. There should be a clean and clever way to manage this list.
- The list ostensibly changes based on vSphere API version (growing with each subsequent release)
- The list currently resides in vim.vm.GuestOsDescriptor.GuestOsIdentifier
- From this library we are concerned with it chiefly as a data validation measure since the server will error on an invalid value.
Questions:
- Should we handle this list retroactively?
- Should we merely accept the latest version of the list?
- Can we completely ignore the list at all?
- Can we trap errors for invalid GuestOS identifiers as sent by the server and expose them sensibly instead?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing vim.vm.GuestOsDescriptor.GuestOsIdentifier in the pyvmomi documentation and the linked nova/virt/vmwareapi/constants.py reference. Determine how GuestOS identifiers vary by vSphere API version and which validation or server-error behavior the issue should cover; done requires a settled approach and defined handling for invalid identifiers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100