This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Testing ILMT environment and running on ProxMox 9.1.4, API let you "investigate" and get a report of a specific node;
first you have to manage the API authentication on ProxMox then, connecting to the principal node and pointing on the "requested node" specs, and you can have all detail about the node.
https://<IP_OF_THE:FIRST_NODE>:8006/api2/json/nodes/<NAME_OF_THE_INTERESTED_NODE>/report
After the query you can read a lot of stuff but the interesting part is, in my personal home environment:
[CUT] lscpu\nArchitecture: x86_64\nCPU op-mode(s): 32-bit, 64-bit\nAddress sizes: 43 bits physical, 48 bits virtual\nByte Order: Little Endian\nCPU(s): 48\nOn-line CPU(s) list: 0-47\nVendor ID: AuthenticAMD\nModel name: AMD Ryzen Threadripper 2970WX 24-Core Processor\nCPU family: 23\nModel: 8\nThread(s) per core: 2\nCore(s) per socket: 24\nSocket(s): 1\nStepping: 2\nFrequency boost: enabled\nCPU(s) scaling MHz: 105%\nCPU max MHz: 3000.0000\nCPU min MHz: 2200.0000\nBogoMIPS: 5987.99\nFlags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid amd_dcm aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate ssbd ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 clzero xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca sev sev_es [CUT]
...that is more than enough of what ILMT need to know, it seams.
So, as far as I can understand, and because of the spreading of ProxMox on customers infrastructure that is getting significant, it doesn't seems so difficult to implement such integration. IMHO...
Am I so wrong?
our company is using IBM Informix more than 25 years, we are moving our VM workloads from VMWARE to Proxmox, it will be supported by ILMT? Proxmox is an emergent solution from enterprises.
Same problem, I would like can move IBM worloads to Proxmox controlled by ILMT metric tool.
Same problem here, we are moving vm's to proxmox but are unable to monitor the vm's in ILMT
This Virtualization is not prioritized by IBM for Eligible Virtualization Technology for Virtualization Capacity by the IBM WorldWide Pricing and Strategy oorganization. If the posiiton will change, then ILMT will provide support.