41 lines
1.7 KiB
Markdown
41 lines
1.7 KiB
Markdown
- DONE question Mahendran Chandrasekaran - node limit per cluster for HVM
|
|
completed:: [[06-10-2025]]
|
|
- pigned julian and vish 08:50 [[06-10-2025]]
|
|
- tested = 10, limited by testing HW avail
|
|
- no plan to increase
|
|
- DONE How can the program also cater for intake of ISV requests for HVM as well?
|
|
completed:: [[06-11-2025]]
|
|
- Morpheus Partner Program #call
|
|
- solution provider program over X sales
|
|
- seems focused on seller partners vs vendors
|
|
- PBM - Partner Business Manager #defintion
|
|
- {:height 124, :width 302}
|
|
-
|
|
- Veeam #call
|
|
- Feedback from phase 1
|
|
- VME download and installed nested on another hypervisor
|
|
- Did explorations of architecture and api interfaces etc
|
|
- Creates a dev template for create/destroy of a testing install for the development team (e.g. for automated functional/unit tests)
|
|
- In process of ordering HW for testing on baremetal (e.g. for performance testing )
|
|
- Open comments
|
|
- Proxmox = Qemu + Proxmox for CBT tracking
|
|
- Q: Can we do qcow2 only for the CBT to get moving faster?
|
|
- Yes, but there are many outlier API interfaces to gather metadata about the VM
|
|
- MVP plan:
|
|
- Morpheus API for all metadata
|
|
- Qemu directly for CBT
|
|
- Veeam outlined challenges with relying on opensource community for the CBT interface
|
|
- Q: Can we use MBD for QEMU block access
|
|
- yes, but proxy on host is faster
|
|
- i.e. proxy VM on host - this provides much more control over load via caching, ordering, etc
|
|
- snapshot of block device, and that then gets attached to the proxy for backup
|
|
- Cody Ault to send over info on ovirt docs
|
|
-
|
|
-
|
|
-
|
|
-
|
|
-
|
|
-
|
|
-
|
|
-
|
|
- |