Hi,
Is there a way in vRA 8.0 to use vRO XaaS components on the blueprint design canvas?
It appears you can only publish XaaS as catalogue items. 😕
Have VMware killed this off in favour of event subscriptions?
It was the response I was given by VMware when I asked about the missing feature.
As there is no official roadmap the "feature" could come, or not come, at any time.
It's not there at launch, but it IS supposed to be coming.
Though I wouldn't hold my breath until at least 8.2.
Thanks for the reply Steve.
Do you know if this info is publicly available or is it "insider info"?
Cheers,
It was the response I was given by VMware when I asked about the missing feature.
As there is no official roadmap the "feature" could come, or not come, at any time.
Thanks again Steve. I've pushed the query over to our TAM now, so VMware can provide a response.
It would be interesting to know the thoughts from yourself, and the community in general, about the impact of not having this feature.
From my perspective we've only being using vRA for 6 months. We've just started with infrastructure automation, and became knee deep in v7.6 very quickly.
When using event subscriptions to run vRO workflows I've found you can't handle the return codes back in vRA so you lose control of the script execution. If a script fails, a vRA deployment continues uninterrupted. If on the other hand, the vRO workflow is published as an XaaS component and dragged on to the vRA blueprint design canvas, sequencing and script execution is handled by vRA and any errors correctly interrupt the deployment. Maybe I'm missing something, but if the ability to use XaaS components on the bp design canvas was removed, a huge amount of functionality would go with it.
Failing an EBS subscription can force the entire deployment to fail. It just depends on which lifecycle you are running in; if you are not using the default failure lifecycles (pre-building, pre-machineprovisioned) then you need to configure a custom property to send failures to the failure queue. EBS is definitely the right choice when you need to run logic per machine and force it for all deployments. The trouble with XaaS is if you require it for every build, how do you make sure people have put it on their blueprint.
In saying that, XaaS definitely has its use cases and similar functionality needs to be provided.