Mike Fratto

Network Computing Editor

Upcoming Events

Where the Cloud Touches Down: Simplifying Data Center Infrastructure Management

Thursday, July 25, 2013
10:00 AM PT/1:00 PM ET

In most data centers, DCIM rests on a shaky foundation of manual record keeping and scattered documentation. OpManager replaces data center documentation with a single repository for data, QRCodes for asset tracking, accurate 3D mapping of asset locations, and a configuration management database (CMDB). In this webcast, sponsored by ManageEngine, you will see how a real-world datacenter mapping stored in racktables gets imported into OpManager, which then provides a 3D visualization of where assets actually are. You'll also see how the QR Code generator helps you make the link between real assets and the monitoring world, and how the layered CMDB provides a single point of view for all your configuration data.

Register Now!

A Network Computing Webinar:
SDN First Steps

Thursday, August 8, 2013
11:00 AM PT / 2:00 PM ET

This webinar will help attendees understand the overall concept of SDN and its benefits, describe the different conceptual approaches to SDN, and examine the various technologies, both proprietary and open source, that are emerging. It will also help users decide whether SDN makes sense in their environment, and outline the first steps IT can take for testing SDN technologies.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

See more from this blogger

Standardizing Cloud APIs Is Useless

In a session on open source in the cloud at the Cloud Connect show in Santa Clara, Calif., Randy Bias of Cloudscaling dropped a bombshell of a statement: "API's don't matter." What Bias was really asking was, "What role do standards play in cloud computing?" With a wry smirk, Bias went on to explain that mimicking Amazon's APIs, for example, is useless if providers don't have the ability to deliver all of the features and functions of Amazon's service, including the things you don't see like reliability and scaling. Of course APIs matter, but having a functional standardized cloud service management API doesn't and, I'd argue, never will.

An API boils down to a contract between those who created the API and those who use the API. It doesn't matter if the API is for a development library or a service. The API developer promises that if you make a method call properly, the API will consume the request or data and then do something with it. Just because Russell Crowe can play mathematician John Nash in the movie "A Beautiful Mind," it doesn't mean that Russell Crowe is a mathematician. What matters when trying to solve a problem involving game theory is that you find someone like Nash who can work the problem, rather than someone like Russell Crowe who can only pretend to do so.

What's important about an API is that there is an easy way to use it. In the cloud world, RESTful APIs, SOAP, Web services, and so on allow providers to expose their systems in ways that others can use. The cry for cloud service management standards--standards that define a common API for service interaction--doesn't yet make sense. The discipline is too young to know what needs to be standardized and what core set of cloud service features should be standardized. It's easy to say, "Standardize the method call to instantiate a new VM," but what are the required features to do that? Selecting an OS or VM image? Setting the number of NICs, CPU or RAM? Requiring special hardware like a GPU or crypto processor? Geographic location? What about OS language?

Some or all of these might be important for you but not for others, so should all of these be standardized? Wait, some group can create a standardized schema supporting a common namespace, as well as custom namespaces similar to RADIUS attribute dictionaries or SNMP MIBs (both of which are a whole 'nother world of hurt). Then you need a way to discover the available capabilities that a service offers and address any missing requirements you may need, which has to happen whether there are standards or not.

What is important with cloud standards is that providers have well-defined, robust APIs using foundational, standards-based protocols and data formats such as HTTP transport and XML-formatted files, and not developing industrywide, high-level, functional schemas and methods. The goal of IT standards is for products and technologies to foster interoperation. If standards can't result in interoperation, then the standard is useless. Developers and integrators need a way to work with the existing features and functions of a service. Everything else is distraction.

Mike Fratto is editor of Network Computing. You can email him, follow him on Twitter, or join the Network Computing group on LinkedIN. He's not as grumpy as he seems.

Related Reading

More Insights

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | Please read our commenting policy.
Vendor Comparisons
Network Computing’s Vendor Comparisons provide extensive details on products and services, including downloadable feature matrices. Our categories include:

Research and Reports

Network Computing: April 2013

TechWeb Careers