Bug #31874
Updated by Evgeni Golov almost 4 years ago
Ohai, when hitting <code>/api/compute_resources/:id/available_clusters/:cluster_id/available_networks</code> for different Compute Resources, <code>cluster_id</code> has different meanings, which makes writing a client harder than it should be. On oVirt/RHV, it's the <code>id</code> from <code>/api/compute_resources/:id/available_clusters</code>, which seems logical. On VMware, it's the <code>name</code> <code>name<code> (or maybe <code>full_path</code>, on all cluster I have access to, those are identical), which is pretty off for my understanding of "ID" :) On Google, the cluster id is completely ignored. I only tested this on 2.1, but expect it to be present in other releases too.