| I disagree about the F1000's having a highly competent CTO office team. Much less unlimited HC and budget. Earlier in my career I worked my way up from Linux sysadmin to Enterprise architect and designed a private vSphere/vCAC private cloud (100K+ ESXi hosts, 12PB SAN, US east/west, Canada, EU) for a F15 company and the level of incompetence I saw in tech leadership from the CTO office down was staggering. Most CTO leadership in the F1000 has determined long ago that kingdom building and protecting headcount is their top priority, so they don't want things to be too efficient. They have to protect their 300 Windows admin HC and 100 Linux admin HC at all costs, so if you give their customers (the line of business unit managers and developers) an API that lets them provision a virtual server in minutes and might automate away the job of 80% of those Windows admins who were doing manual builds, they will slow it down to the point that it is just as slow as the old 6 month long manual provisioning process. I watched this play out first hand. On my small team we designed a private cloud that could give you a Linux/Windows server in ~20 minutes with as much storage as you wanted, and it was so effective at stealing internal customers that the VPs who managed the server build/run teams made sure to break it apart into their separate storage, compute, and database silos so that the provisioning process got slow again. It still takes them 6 months and a project manager to provision a single server now. These dinosaurs don't want change. They want to kingdom build and make sure they have hundreds of dead weight server admins so that when they get forced to cut due to budget reductions they won't get cut too deep. They could care less about the bottom line, and the CEO and executive leadership don't know they're being gaslit by their CTO office on down about the "dangers of public cloud." |