https://worldofeuc.com logo
Join Slack
Powered by
cross posting in case anyone else has run into thi...
# nutanix-euc
r
cross posting in case anyone else has run into this, or more importantly if anyone knows if there's any official guidance around naming PC clusters vs. host clusters - so far I haven't found anything, nor have I really found anything in particular about what repercussions renaming a PC cluster itself may have on downstream tools - has anyone seen anything along those lines, other than the aesthetic (or is it rizz? i can't keep up)? Well, and obviously api scripts that try to return network information breaking.. :)
j
I'll take a look at their deployment scripts and see what they are using, PC has its own cluster type that should be used for filtering - name isn't a great identifier :-)
r
it's doing a name filter search based on what's in the ini file against /api/clustermgmt/v4.0/config/clusters? - i've only half looked into it today in between some other things, but it seems like the objectType is the same for both (clustermgmt.v4.config.Cluster)
specifically it's the validateNutanixClusterDetails block in the uagdeployntnx.ps1 file (thought about posting the code but who knows might get upset about that since technically you'd need entitlement to access the scripts..)
j
yah, their return is filtering on name only -> they should filter on name + 
config.clusterFunction
(this can be 
AOS
, or 
PRISM_CENTRAL
, or a few other values) - so you would be getting an array back and bup bow
Will pass this back to the Omnissa PMs, can you drop me an email - first.last@nutanix.com so they know it's come from from folks in the field 🙂
r
yeah will send something along shortly - i actually had posted about it on their community earlier, mind if i update that with your note (with credit of course)? https://community.omnissa.com/forums/topic/71994-uag-deploy-failure-on-nutanix/
if pressure from both sides gets them to fix it, maybe we can also convince them to publish an OVF that actually works on Nutanix too instead of having to manually extract the vmdk from the same package used for vmware 😄
j
no worries, I don't need credit, it's all good - go for it 🙂
👍 1
r
not that i want to encourage anyone using the same name for multiple pieces of their infrastructure mind you, but at least it's an easy fix 🙂
j
small wins in life, we gotta take them
Open in Slack
PreviousNext
Powered by