© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
At this point, we need to have a meeting. We have a number of hurdles that commenting on this ticket will not resolve. My email is in my profile, please have your management reach out, and include Dorian.
For Mantic, it's already post-Freeze. Due to our lack of testing environment, making the change before 23.10 goes out would be problematic.
###
please see the previous comments -- I still do not have any real guidance on
I'm still awaiting the ISV Documentation. Without it, we're shooting in the dark, and tossing images over the wall for testing.
1. VSphere support and OVF information: [0]
b. backwards compatibility -- if i use HW version 15, is it happily supported in ESXi 8? What are the tradoffs? will older HW Versions not boot on newer VSphere at all? What is the minimum to make it work "everywhere?"
c. Features -- what do we need to do here? the docs list tons of features, when they're added, levels of support, etc. Is there something we need to be doing?
2. what are "defaults" vs. "environment" setups. How do we ensure our OVF will boot in many environments, but is fully configurable as needed?
3. best practices for producing a "base" OVA, knowing that every environment is different (so what values need set in which stanzas to be able to ensure users can override as needed).
> Is Canonical using open-vmdk code to create ovf and vmdk files or some other approach like qemu?
first, all our code here is open source, so please feel free to read everything. I've linked this all previous:
1. https:/
a. function that is always used.
b. utilizes https:/
2. vmdk base generation: https:/
a. gist: takes our rootfs ext4 and creates the vmdk
3. OVA: https:/
a. gist: utilizes an OVF template, and shoves in pieces, and packages with the vmdk
4. the template: https:/
As this is all open source, you can also issue MPs directly! Launchpad follows a forking workflow. You can also attach diffs directly to tickets
as for `open-vmdk` specifically, I don't see it packaged for Ubuntu. I do not see it in Debian either. Would you be open to having this packaged for distros to use? Otherwise, we cannot use it for building images. All tools must either be
a. a part of the distro or;
b. developed internally by Canonical
> For automation of testing, please check out the open-source project
The issue here is licenses and testing. I'll reach out to Dorian again, but this trail went cold a few years ago. We're still going to have issues keeping up with changes in VSphere.
[0] https:/