XenSource and Citrix Get Hitched: An *Interesting* Marriage
So XenSource and Citrix got hitched today. A marriage made in heaven?
Well, from one perspective, absolutely. Citrix has a big presence in a certain type of desktop virtualization -- display presentation. And, of course, Citrix and Microsoft have a close, even symbiotic relationship. Finally, XenSource and Microsoft have cooperated closely on Microsoft's upcoming Windows Server 2008 virtualization technology (aka Viridian). So, lots of points for synergy, reinforcing existing commercial relationships, and, of course, Citrix needed a way to respond to VMware's desktop initiatives, as Doug Dineley noted in this InfoWorld blog posting. From this perspective, the acquisition is a tight coupling of complementary technologies and companies.
From anther perspective, though, the marriage, as they say, "has issues," primarily revolving around XenSource's existing business model.
XenSource is the commercial sponsor of the open source Xen virtualization project, using Xen as a foundation for its own XenServer products. Xen the technology has many contributors beyond XenSource itself: Intel, AMD, IBM, Red Hat, and others. Most of the other contributors to Xen view the technology as key to the battles of their various markets: Red Hat against Windows, Intel and AMD against each other (coalitions make for strange partnership arrangements), IBM against HP, and so on. Most of these participants are most interested in Xen in its Linux form, unlike XenSource, which, as noted above, has been frank about its Microsoft focus.
What made (and makes) this coalition possible is the fact that it is based on open source, which seems to be able to convince competitors to collaborate in a common effort.
XenSource itself took the role of (if I may mix a metaphor) of Switzerland, neutrally shepherding Xen. Of course, it differs from Switzerland in one very important respect: it does not hold a strictly neutral role. It actively markets its own Xen-based product called XenServer, which undoubtedly formed a large part of the reason Citrix was interested in the acquisition.
As you might expect, a coalition in which a vital member both shepherds a key component and competes with a number of the coalition members carries some tension, as in any coalition in which members' interests are aligned but not identical. The Citrix acquisition is likely to, if not increase the tension, at least add confusion to the tension, as additional interests and initiatives get put into the mix.
Certainly a critical element in keeping the Xen coalition moving forward will be a deft hand in managing open source relationships, particularly given the complex situation described in the previous paragraph.
An important question is how Citrix will handle XenSource's open source activities. It's one thing to assert a commitment to participating in an open source community; the reality of actually working in the fluid, jumbled world of open source community can be quite challenging. I worked with one company that had the software it wrote for its own products rewritten by the person in charge of the project! Believe me, that kind of thing can take some getting used to, particularly if you're coming from a world in which you control the entire product offering. So I expect a learning curve and a period of adjustment, as there is in any new marriage. This will be especially true in terms of keeping XenSource's (and Xen's) Linux focus going, given that Citrix is primarily Microsoft Windows-oriented.
Overall, I believe this is a plus for Xen virtualization. With the resources of a
Print
Well, from one perspective, absolutely. Citrix has a big presence in a certain type of desktop virtualization -- display presentation. And, of course, Citrix and Microsoft have a close, even symbiotic relationship. Finally, XenSource and Microsoft have cooperated closely on Microsoft's upcoming Windows Server 2008 virtualization technology (aka Viridian). So, lots of points for synergy, reinforcing existing commercial relationships, and, of course, Citrix needed a way to respond to VMware's desktop initiatives, as Doug Dineley noted in this InfoWorld blog posting. From this perspective, the acquisition is a tight coupling of complementary technologies and companies.
From anther perspective, though, the marriage, as they say, "has issues," primarily revolving around XenSource's existing business model.
XenSource is the commercial sponsor of the open source Xen virtualization project, using Xen as a foundation for its own XenServer products. Xen the technology has many contributors beyond XenSource itself: Intel, AMD, IBM, Red Hat, and others. Most of the other contributors to Xen view the technology as key to the battles of their various markets: Red Hat against Windows, Intel and AMD against each other (coalitions make for strange partnership arrangements), IBM against HP, and so on. Most of these participants are most interested in Xen in its Linux form, unlike XenSource, which, as noted above, has been frank about its Microsoft focus.
What made (and makes) this coalition possible is the fact that it is based on open source, which seems to be able to convince competitors to collaborate in a common effort.
XenSource itself took the role of (if I may mix a metaphor) of Switzerland, neutrally shepherding Xen. Of course, it differs from Switzerland in one very important respect: it does not hold a strictly neutral role. It actively markets its own Xen-based product called XenServer, which undoubtedly formed a large part of the reason Citrix was interested in the acquisition.
As you might expect, a coalition in which a vital member both shepherds a key component and competes with a number of the coalition members carries some tension, as in any coalition in which members' interests are aligned but not identical. The Citrix acquisition is likely to, if not increase the tension, at least add confusion to the tension, as additional interests and initiatives get put into the mix.
Certainly a critical element in keeping the Xen coalition moving forward will be a deft hand in managing open source relationships, particularly given the complex situation described in the previous paragraph.
An important question is how Citrix will handle XenSource's open source activities. It's one thing to assert a commitment to participating in an open source community; the reality of actually working in the fluid, jumbled world of open source community can be quite challenging. I worked with one company that had the software it wrote for its own products rewritten by the person in charge of the project! Believe me, that kind of thing can take some getting used to, particularly if you're coming from a world in which you control the entire product offering. So I expect a learning curve and a period of adjustment, as there is in any new marriage. This will be especially true in terms of keeping XenSource's (and Xen's) Linux focus going, given that Citrix is primarily Microsoft Windows-oriented.
Overall, I believe this is a plus for Xen virtualization. With the resources of a
Previous Post: Linus Torvalds: Virtualization SucksNext Post: Sun's interesting virtualization initiative
Most Discussed Posts
Cloud computing has emerged as one of the most significant game changers to hit the technology landscape in the past 20 years. With this massive expansion of the cloud, the perception of the IT organization is shifting from a utility player to a change agent. This eBook breaks down five ways progressive organizations are using cloud-based IT Management solutions to help drive innovation and become more strategic, including: adding visibility and analytics, speeding up time-to-value, lowering costs, improving prioritization, and providing a blueprint for future cloud deployments.
Read the white paper to see how IBM helped Citigroup deliver new services and enhancements to their 200 million customers faster.
There are 3 ways to modernize legacy applications: rewrite completely, acquire packaged solutions or migrate existing code. This paper explains why it's best to migrate and how IBM® Rational® software can help.
Accommodating specific lines of business can result in a hybrid ecosystem of applications and servers. The resulting complexity of this architecture makes for an environment that is costly to maintain and difficult to change when addressing new challenges.
This whitepaper will help you to define a mobile device passcode policy. Security managers must attempt to reconcile two opposing goals. They must: 1) create a passcode policy that is strong enough to protect the device if it is lost or stolen, while: 2) not annoying users with needless length or complexity.
This whitepaper, authored by The Radicati Group, looks at the key reasons organizations should consider moving to a cloud-based archiving solution. Email archiving solutions enable organizations to store, monitor, and collect electronic data exchanged by their users to comply with internal policies and regulations.
ATERNITY will showcase a 30-minute demo on how Fortune 500 companies are leveraging its award-winning FPI Platform to deliver a user-centric approach to Proactive IT Management.
For businesses to move forward and tap into the ever-expanding universe of Internet users and network-enabled devices, it's critical to learn how to make the transition to IPv6. Learn the critical steps your organization must take to make a seamless transition-and keep your business world connected.
Learn how IT teams can protect against spear phishing tactics. Harry Sverdlove, chief technology officer of Bit9 offers a frank discussion about spear phishing - the most common technique used in today's advanced attacks.
Learn how to build a solid business case for your migration to Red Hat Enterprise Linux so you can run leaner, innovate faster, be more flexible and own the New Now.
Social media isn't about you; it's about everything around you. As you consider how your customers want to communicate with you, social media is something that can't be ignored. But what should your strategy be? Is social media "just another channel?" What kind of a plan makes sense for your contact center and for your customers? Join our experts as they share their insight and research results.
Hardware tokens were a popular method of strong authentication in past years but the cumbersome provisioning and distribution tasks, high support requirements and replacement costs have limited their growth. The additional log-in steps that hardware tokens require and the resulting user frustrations have limited adoption and make them impractical for larger scale partner and customer applications.
Sponsored Links
