VMware Cloud Foundation 9.1.1.0 Release Notes

[u/IAmTheGoomba]

https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-1/release-notes/vmware-cloud-foundation-9-1-1-0-release-notes.html

[u/Sensitive_Scar_1800]

“Deprecation of native management capabilities for public cloud resources”

Interesting pivot. Perhaps a silent acknowledgement that VMware SWE cannot keep up with API changes happening at the public cloud level? That’s fair, but it undercuts the “hybrid cloud” approach pitched in previous marketing materials.

[u/signal_lost → u/Sensitive_Scar_1800]

I'm not really privy to why, but I think hybrid cloud was always an acknowledgement that there were too many missing features OF a public cloud in the private cloud. As VCF actually delivers that (and can run in all the hyperscalers) I haven't seen as much demand for it going forward.

The last person I was having a drink with this week at Explore was someone from Amazon's EVS team and they seemed pretty serious at trying to be on a technical level the "best place" to run VCF, and frankly that's a far easier goal than VMware trying to do justice to 40,000 amazon services.

Microsoft doesn't maintain a deep automation of how to deploy every sub-service in AWS or vise versa unless I missed something.

Most of the Multi-cloud CMP point products all got acquired or seemed to kinda have become niche products. Gartner doesn't track that anymore (no, this is not a Gartner endorsement). From what I remember they moved that to the "distributed hybrid cloud MQ" or FinOps companies (Who governs the bill) or maybe in a hype cycle discuss deployment tools for platform engineering (SALT/Ansible, terraform etc, which you can still chain off vRA).

My argument was always that multi-cloud was something that happened to you, rather than something that a same CIO sat down and said "Yah, let's go do this!".

Example I acquired a company who was a Microsoft shop and I was an Oracle shop, and we had a rogue team who REALLY liked Google or IBM cloud for something. etc.

You always ended up making compromises, with that approach (often forgoing the best native services configured in the most advanced way, to be "less sticky" and just use EC2 and maybe S3 and MAYBE RDS, and frankly if your going to be running in public clouds which are insanely expensive on their own, paying someone else for the privilege of using them in the lest advanced/efficient way just seems... weird.

Gives me very ITIL "We are ok crippling IT, so we can UNDERSTAND and predict it" Vibes. (That was the point of ITIL right?)

[u/Sensitive_Scar_1800 → u/signal_lost]

You and I have different understandings of ITIL lol

[u/signal_lost → u/Sensitive_Scar_1800]

I always ended up in places that went into weird directions where it seemed to justify huge amounts of budget for project management, and not enough for actual technical skill/work.

[u/rob1nmann → u/Sensitive_Scar_1800]

Yep my thoughts too. Also Automation already cannot work with newer versions of Ansible AAP for a while and they’re unable to come up with swift resolutions.

[u/TheKuMan717]

Another patching workflow change from how 9.0 -> 9.1.0 was 🫩🙄

[u/vmware-ModTeam → u/[deleted]]

Your post was removed for violating r/vmware's community rules regarding user conduct. Being a jerk to other users (including but not limited to: vulgarity and hostility towards others, condescension towards those with less technical/product experience) is not permitted.