SAN FRANCISCO, USA–Technology vendors such as VMware are rolling out tools touted to facilitate closer collaboration between an organisation’s IT operations and developer teams, but not everyone believes this is always a good thing. Developers should be singular about building applications and not feel they have to think about managing infrastructures within their organisation.
During a panel discussion at VMworld 2019 here Thursday, VMware’s vice president of product management Paul Dul pointed to the tech vendor’s goal to offer tools that would bridge the traditional divide between the IT development and operations teams and asked panellists if the interaction between their teams had improved.
“I hope not,” quipped Stephan Massalt, vice president of cloud labs at Swisscom Cloud Labs. “I’m convinced we shouldn’t let developers–specifically enterprises developers–talk about infrastructure…they should be focusing on their job. Sometimes, they act like rock stars and think they know everything, and they should not,” he said.
Massalt acknowledged that the traditional gulf between ops and developers indeed was narrowing and this was a good step forward, but with recent developments such as the emergence of Kubernetes, developers were being asked to assume too many roles and having to think about infrastructure issues.
He underscored the need to create a conducive environment on which to write good codes, giving developers some constraints within which to deploy applications so that critical business policies would be complied with. “You need to put guardrails in place,” he said. This, he added, would ensure applications were developed to be robust, consistent, reliable, and able to communicate with legacy software.
The role of the ops team then was to put in place the tools that would let developers achieve that, he said, adding that one of the main benefits of containers was that applications could be built without worrying about the underlying infrastructure.
Fellow panellist John Paice, platform engineering anchor for Dick’s Sporting Goods, though, welcomed closer collaboration between the various IT teams, including security, developers, and infrastructure. These had functioned in silos and the organisation was working to bring down the walls, Paice said.
Sharat Nellutla, Verizon’s associate director, Verizon, added that better communication between both operations and developers would allow for more efficient planning and use of resources.
At VMworld this year, the virtualisation vendor had outlined plans to tap Kubernetes and bridge the divide between the developer and IT operations teams. Project Pacific, for instance, was touted as an ongoing development effort to eventually bring the capabilities of Kubernetes natively into the vSphere platform.
VMware said it would enable application-level control for applying policies and role-based access to developers and provide a consolidated view of VMware vCenter Server for Kubernetes clusters, containers, and virtual machines.
In addition, IT administrators would be able to use vSphere tools to push Kubernetes clusters to developers, who then would be able to use Kubernetes APIs (application programming interfaces) to access software-defined data centre infrastructures. In a nutshell, Project Pacific would give the development and IT operations teams a consistent view via Kubenetes constructs in vSphere.
And this would be core to all future developments at VMware, said its COO of customer operations Sanjay Poonen, who said containers and cloud native models would be native to its infrastructure moving forward, as opposed to being bolted on.
Speaking to Asian media on the sidelines of the conference, Poonen added that all future releases would be “container-ready”, enabling customers to run containerised applications on top, with Kubernetes as the orchestrator.
Asked about competition with the likes of Red Hat and HPE in the DevOps space, he told ZDNet that any company that contributed to the open source community and Kubernetes was “a good thing”. That said, he touted VMware’s packaged offering for container platforms as currently the best strategy in the market.
He further noted that seven years after it was launched, Red Hat’s OpenShift had just 1,000 customers and a revenue of between $100 million and $150 million. In comparison, the collective revenue of Pivotal and VMware’s Open Stack was $750 million.
Poonen said: “So we think we’ll be differentiated from OpenShift and have more potential to take Kubernetes into our core platform vSphere than OpenShift can take that into Linux, because there’s more container desire in virtual machines than an Linux operations manager. So I feel good about our competitive differentiation to Red Hat.
“That said, yes, Tanzu will absolutely compete straight on with OpenShift, but we also will support customers who pick OpenSihft [and any other competing brand].”
Based in Singapore, Eileen Yu reported for ZDNet from VMworld 2019 in San Francisco on the invitation of VMware.
With containers poised to replace virtual machines, VMware’s plans to go big on Kubernetes are significant to its future growth, but its speed in executing on this strategy will be critical to fend off potential competitors.
Following the announcement to acquire Pivotal, VMware believes Tanzu will position it to deliver the most comprehensive enterprise-grade Kubernetes-based portfolio for modern applications.
A lesson on the past, present, and future of cloud from the VMware playbook.
HPE and Red Hat are tying Red Hat OpenShift Container Platform with HPE Synergy to speed up container application delivery for the enterprise.
The tech giant has announced a new way to build cloud infrastructure, a partnership with Google Cloud, VMware PKS support for its cloud platforms, and the rollout of its Data Center-as-a-service offering to US customers.