Showing posts with label canonical. Show all posts
Showing posts with label canonical. Show all posts

Friday, 19 December 2014

Why there’s no open-source standard-bearer for the network

Why there’s no open-source standard-bearer for the network

Open-source creeps into the network from below, but no Red Hat analogues in sight

Open-source software plays an increasingly prominent role in many areas of modern business IT – it’s in servers, databases and even the cloud. Vendors like Red Hat, Canonical and others have managed to graft open-source principles onto a profitable business model. The former company became the first open-source-centered business with $1 billion in annual revenue in 2012.

So what about the network? Why isn’t there an open-source alternative there?

Plenty of reasons, according to experts, including the difficulty of challenging established incumbents, the dangers of getting eaten alive by a large customer and the sheer scale and complexity of managing a heterodox network in an orthodox way.

THE HEAVYWEIGHTS
Obviously, the incumbents in most fields of enterprise technology are formidable enough, but networking hopefuls have to contend with a bona-fide giant of the realm in the form of Cisco – which sells between 65% and 70% of the world’s enterprise switches, 80% of the enterprise routers, and 18% of the security appliances – still good for tops in its category, according to IDC.

More than that, however, they’re actually pleasing their customers, according to 451 Research analyst Peter Christy.

“If you talk to Cisco customers, rather than viewing them as a predatory, monopolistic company they would like to get away from, they view them as the best tech vendor they deal with in terms of helping the customer succeed,” he said.

Companies have to compete with Cisco to do a better job providing a working network, which isn’t easy to do. (Not that it’s stopped some companies from trying – Brocade bought open-source networking software maker Vyatta in 2012 with that end in mind.) And that’s not to say that companies that, like Cisco, depend on branded hardware are going to have it all their own way in perpetuity.

"[Network management] is a freaking hard problem. It’s just a lot of things to try to cover, and the market moves."

John Michelsen, CTO for CA Technologies
Neela Jacques is the executive director of the Open Daylight project, which is a collaborative group that works to create open-source networking software. He argues that some pricey proprietary hardware isn’t worth it.

“In some areas, there’s been tremendous innovation and differentiation, where you’re paying $100,000 for a box and it really is solving a problem you couldn’t solve otherwise,” he said. “But especially at the lower end of the market, there’s been very, very high margins for a long time, and the boxes haven’t really changed as much.”

All too often, Jacques said, networking hardware is made by a no-name ODM in China, programmed with a specific vendor’s network operating system, and marked up by a factor of five to 10.

“People have been looking at that and saying ‘wait a second – if we could just create an open-source version of that network operating system, then someone could get the exact same SKU that they’re putting into their environment,’” he added.

Christy noted that three of the four biggest clouds out there – Amazon, Facebook, and Google, with Microsoft the odd company out – build their own networking boxes. Even hardware makers like Riverbed say that commodity hardware is the wave of the future.

“Why should they buy the same thing from Cisco if they can build what they want, somewhat tweaked, by themselves, with the same outside manufacturers?” he asked.

A FREAKING HARD PROBLEM
Even so, CA Technologies CTO John Michelsen said, attempts to create a broad-based performance management framework in an open-source manner, like OpenNMS, haven’t been terribly successful because the issues faced are simply very difficult.

“It’s a freaking hard problem. It’s just a lot of things to try to cover, and the market moves," he said.

The well-known aphorism of UNIX philosophy says to “write programs that do one thing and do it well” – a problematic stance for broad-based network management and performance optimization systems, which are, almost by definition, heavily multi-functional.

Michelsen said that his company’s application performance management product is designed to monitor eight separate aspects of the network.

“It’s very hard to bring an integrated set of very deep-science things in several different areas. Each of these different types of monitoring are their own science project,” he said.

SWALLOWED UP
Despite the philosophical and logistical problems, open-source technology is still a major part of the network – it’s just in there at a very low level, according to 451’s Christy.

Big companies that buy a service from smaller ones impose tough contractual terms around code escrow – meaning that the vendor will have to provide a copy of their offering’s source code for legal safe-keeping, so that the bigger firm will be able to continue to function if the smaller one goes out of business.

Open source obviates a lot of those headaches, in principle. It also offers companies in the same industry a way to collaborate on development without fear of being accused of collusion.

But it also means that open source tends to get swallowed up by big companies in the network space, one way or another. Key early adopters of open-source networking technology have had so much in-house technological expertise that it becomes difficult to offer them a paid service offering – they can simply do that themselves.

“The biggest users always self-support – it’s not a commercial opportunity,” said Christy.

That same open-source code, freely viewed and tinkered with by companies full of top programming talent, helps fuel the aforementioned shift in the direction of commodity hardware.

BIG KIDS ONLY
But, obviously, not every company has Facebook or Google’s battalions of elite developers. It’s because of this that the hands-off, managed service option remains popular.

“In the case of networking, for most customers, there’s a greater motivation to let the vendor sit in the middle and integrate patches and be responsible for the operation of the network as a whole, than it is for, say, the typical use of Linux,” Christy said.

Jacques argues that open-source’s low-level presence on the network is strong, and could eventually diversify to the point at which smaller customers are more attracted to it.

“Open-source is a key underpinning of network management technology, but absent a “core platform,” there’s little chance of open-source making it to the app layer.

“[L]ook at what happened with Linux, for example. It took Linux being credible for running servers … for people to look and turn it into something to run cars and phones and home security systems and all that,” he said. “I think you’ll see the exact same thing in networking, because you can’t have an open-source app that sits on a proprietary platform.”




 
Best Microsoft MCTS Training – Microsoft MCITP Training at Certkingdom.com

Wednesday, 15 January 2014

Ubuntu 13.10 takes aim at Microsoft, Apple, Google

Although not reviewed here, we tried Canonical's optional Landscape service, which can be hosted internally or by Canonical. It reports conditions of covered Ubuntu instances. It can inform an administrator if instances need updates, has failed in a number of ways, when administrative approval is needed, when certain types of jobs are completed, and when upgrades are available and applied.

It's a bit primitive compared to other third-party packages, and those that are largely OS-specific, like Microsoft System Center. It's possible to watch administrative jobs like cloud populating, as well as dreary desktop instance monitoring.

Cross Platform
“The Desktop, The Server, and The Smartphone” sounds like the title to a bad poem, but it's possible to do with Ubuntu 13.10, although the number of smartphones supported today appears to be just two. We had a leftover Nexus 4 from another experiment, and went through the provisioning steps to upgrade it to Ubuntu, via Ubuntu's developer site.

Currently, the smartphone/phablet program is available only to developers and OEMs. We therefore put on our developer hats and gave it a try. The Galaxy Nexus and Nexus 4 are the only phones supported, and only a shell and core apps are available. We used a T-Mobile SIM to make a call. The call worked. The steps in between using an Android 4.2+ phone and running Ubuntu are many.

The phone has to be reflashed, via a USB cable connection. Then, our Nexus had to be unlocked, via the factory OEM unlocking method, all described on the Ubuntu website. Once back into Android Jelly Bean 4.1, we downloaded the image needed, which is a one-way step. This is the step that requires the most patience, as it takes much longer than we expected. We were ready to restart the process when magically, the phone restarted and came up. We made a call, and yes, went to Facebook. It's well-documented, and heavily full of caveats.

Ubuntu warns frequently and dramatically that the process can brick a phone, and we believe this. It's for developers today, but it looks, feels, and behaves like Ubuntu's Unity interface. It's possible if you don't brick the phone on the way to Ubuntu, that you can back-grade to Android, which we did, although it had its own harrowing moments.

The good news is that like other components of this release, Canonical tips its hand where it's going, the undertaking they're going through to bring a cross-platform user interface into (hopefully) the next LTS release.

Overall
This is a spaghetti-against-the-wall release. IT organizations with an Ubuntu focus will want to pay attention to the release, as it's a harbinger of things to come. It has enough in the form of early-release apps that some portions, the attractive ones, aren't ready for release -- just as Microsoft trial-balloons features before they're entirely ready for production. But one quality of this release is that it's a hell of a tease, and more so when the competitors have enormous amounts of capitalization and history behind them. The ideas and momentum seem to be crystalizing, and Canonical has a lot of work ahead of it to take these into reliable production.

How We Tested
We deployed Ubuntu 13.10 on native and virtual machines in our lab and at Expedient/Indy, which hosts our network operations center. We used a limited number of notebooks, principally Lenovo Thinkpads and VMs under Oracle VirtualBox and Microsoft Hyper-V V3. Server bare metal took place on an older Dell server, as well as into VMs on VMware 5.5 running on a Lenovo ThinkServer and Hyper-V V3 on a HP DL-380G8. Although OpenStack constructs are available for these hypervisors and others, we didn't test Hadoop clusters in our examinations.

Best Microsoft MCTS Certification, Microsoft MCITP Training at certkingdom.com