qc4vmware
Virtuoso
Virtuoso

Thank you for the information on overriding the resource naming template.  My opinion is that VMware introduced a bug in the way this was implemented.  I'm a decent vRA / vRO user and it is not a problem to implement this as an extendibility step but I find it confusing to operations staff and often to VMware support folk when we override this kind of out of the box feature.  It was one less thing I had to use extensibility for... until now.  We did something similar to this in vRA 6/7 lines of products and hit some bugs with race conditions related to some steps having run with the automatically generated name and the desired final name not getting applied until a bit later down the line.  Hopefully we will not run into any similar issues in vRA 8.  I don't think so judging by how things have been flowing thus far but it just seems unnecessary  to support this naming convention... especially since it has worked just fine until now.

Reply
0 Kudos