![]() It would take a performance hit, but for some the trade-off might be worth it. Or "sync" a container to a virtualized OS version of the app, where you can deploy the full panoply of debugging tools to inspect what is happening on the container in ways that would be terribly inconvenient or not even possible on the container, like using log file analysis tools that wouldn't be on the container. infrastructure).then does it in reverse as well. I was looking forward to something like a VMWare Fusion/Workstation-powered session that starts off with a virtualized OS, auto-generates a container configuration file by watching everything you install and detecting what the installed app uses while you run it through its paces, creates and deploys a containerized app, perhaps onto your laptop and perhaps injecting directly into a cloud instance you point to (bonus points for integrated account support and API hooks for customizing the cloud deployment flow or injecting into your Chef/Puppet/etc. The container virtualization market is moving fast, so quick, effective integration is required. Even a brand-new domestic team would have zero chance. There is zero chance the offshore team has the built-up institutional knowledge the original HostedUI team painstakingly accreted over decades to quickly integrate seamless container virtualization into the desktop-hosted Workstation and Fusion products. ![]() Perhaps native desktop OS support for virtualization is shaping up much faster and more robustly than we realize, VMWare execs see the writing on the wall and decided to exit the space on a high note instead of fighting future ever-declining revenues in that space, and they will count upon lower-margin solutions based upon native desktop OS virtualization features to address the desktop-to-server scaling issue. I lack insight into why VMWare effectively gave up on holding down the desktop end of the spectrum, which essentially tells customers that the capability to scale from desktops to servers is no longer as important to its mission or business model. Just as server- and desktop-hosted virtualization should co-exist on another axis of the ecosystem. > Supporting container workloads doesn't need to come at the expense of "traditional" virtualization.Ībsolutely agree with you, I think machine and container virtualization should co-exist in a sophisticated ecosystem and it isn't an either-or. ![]() It will be interesting to see what VMWare's competitors come up with. By jettisoning certain product lines that complemented and completed a market message to your customers, you open up high-margin products to much more effective competitive attacks. It looks great to boost relative margins, though. I can assure you there are many more who did not go on record.Īpplying a single financial metric across all your products loses focus upon what really matters to your customers. After IBM ditched their "low-profit" servers, for example, you can find a CIO going on record here and there saying they abandoned their all-IBM-servers policy in their shops. Not a few enterprise customers value these "low profitability" product lines, because they promise to lower the complexity of dealing with a wide-area problem space. Probably because that category didn't meet an arbitrary profitability criteria, instead of a customer-focused analysis of what value propositions the product line brought to the table when looked at as a part of an entire picture of all other products offered.Īnother possibility is VMWare might be defocusing their traditional virtualization and this is the first of an all-in shift to containers because that's a growth market at the moment. This seems a strategic exit by VMWare to cede all desktop-hosted virtualization markets to competitors. Great description of what a tight-knit, motivated team can accomplish.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |