Thursday, December 6, 2012

Google Enterprise Fragmentation

I am writing this in Google Docs, something that I generally stay away from as it certainly does not have the features necessary for a complex document, but will suffice for a blog entry.

However, this is an example for the dilemma that Google presents to its user set.  The tools seems to be there, but there are significant limitation or exceptions when you stray only a little-bit outside of their larger application set or environment.

In this entry, the focus is on the differences between the Google-based environments that I use, or try to use everyday.  Google apparently wants these environments to look the same, but any Enterprise user finds out quickly that they are not.

My company uses Google Apps primarily for email and some level of document exchange.  I personally have a Windows-based PC as well as an Android-based Tablet.  These two Google environments that center around the Chrome browser can lead to moment of “what was Google thinking” exasperation.

Up until recently (I don’t know exactly when), Google Apps, such as Document and Spreadsheet appeared quite differently in Chrome on the PC and the Tablet.  I just checked this morning, and now there seems to be some convergence of the look-and-feel.  Part of this was the release of Chrome for Android, which has now become my default browser on both platforms.

But, right now, Chrome is a tease.  On my PC, viewing a PDF is done quite differently than on the Android tablet.  Chrome works directly with nearly all PDFs and displays as a native format within a browser window.  On the tablet, loading a PDF causes a traditional download event that then requires the launch of a separate program to view the document.  Maybe this is a bit of nitpicking, but if Google wants the Enterprise space, then differences like this must be resolved.

Another more immediate tease occurred this week.  Chrome Remote Desktop, out of beta, appeared as a capability sent from heaven.  I was about to travel and did not want to take my desktop-replacement laptop on the journey.  I was able to quickly fire-up Remote Desktop on my laptop and another laptop and voila a remote desktop that worked remarkably well.  I then got my tablet and quickly determined that there was no Android Chrome client available, thwarting my mobile remote desktop access plans.  It is not even clear if Google is working on such a capability.

This got me thinking about the same-but-different environments that Google provides.  There are Google Chrome applications that you get from the Web-store and there are Android applications.  With the common denominator being Chrome, you would think that this would be the services convergence environment, at least for Enterprise services.  Alas, but no, at least not yet.  Because of this, I am not sure that I would consider a Chrome OS Laptop as I fear this introduces yet another environment with limitations and differences that are not necessarily foreseen until encountered.

Microsoft is certainly attempting their convergence approach for Tablets, Phones, PCs, and even the Xbox.  The eventual cleaner, easier to use, more uniform, and (of course) secure environment will likely dominate the emerging mobile Enterprise.

Monday, October 29, 2012

Software Defined Network (SDN) Considerations for Commercial Network Service Providers


More than four years ago I wrote that carrier service providers must realize that they are in reality “application enablers” see (Going Horizontal on the Vertical) and that Service Providers needed to Virtualize the WAN.    These posts indicated two important areas that relevant to the discussion of Software Defined Networks (SDN) in the context of commercial services (A good summary of describing the SDN approach as compared to the prevalent distributed control model can be found at SDN A Backward Step Forward).

The two areas I described were that:
  1. Network service providers have to provide an Application Programming Interface (API) for service requests and service status
  2. Virtualization of the Core network enables customers to define what they want out of their network ensemble. 
It appears to me that the evolution of SDN technology needs to follow a similar path as virtual machine technologies.  That is the maturation of technology at the enterprise-level and then the transition to a commercial services provider’s infrastructure.  The first instantiation of virtual machine technology enabled the consolidation and increase in efficiency of an organization’s infrastructure.  The next steps were the development of multi-tenancy environments and transition into commercial “Cloud” services.

The successful public service provider SDN controller must be able to provide a user with the control needed by their application set, while at the same time enabling the service provider to optimize their network.  There are significant options about what the SDN concept means for a service provider and what it looks like to a customer:
  1. Is the goal to provide “raw” virtualized standard router-type services? That is, does the customer select a router type and instantiate a set of virtual core routers to meet their requirements?
  2. Is there a network equivalent of an x86_64 (i.e., Generic PC processor) virtual machine?  Do you provide a blank sheet and development environment for customers to create their own virtual network devices?
  3. Is the goal to make it appear that the network is a single large “router” regardless of the number and physical locations of the actual network?  Wow, I get my own world-wide network that looks like a single router!  Can you also provide a “primary” and “backup” virtual router?
  4. Do you provide a Plain Old IP VPN service for customers that just want the same-old-same-old basic service?
  5. Do you provide multiple network personalities at the same time to a customer?  That is a network connection and control that enables both IP transport that appears as standard WAN VPN services (with traditional standard QoS – 99.9% packet delivery) as well as services that are more tailored data center operations such as moving Virtual Machines (with near Time Domain Multiplexed QoS – 100% packet delivery). 
As the “simplicity” increases from the customer perspective, the complexity for the service provider increases to manage the increasingly dynamic nature of the services offered and customer demands.

Finally, can we expect novel SDN-based capabilities to be provided by traditional network service providers, or do we need companies that “think outside the box” to move into this area?  If the introduction of large-scale Cloud services define the pattern, then companies like Google and Amazon may lead the network charge.