Google hooks up with Scale for cloud collab?! What does it all mean?
And what will it become?
At long last, Google's cloud has an on-premises extension. That extension is... Scale Computing? The cloud giant and hyperconverged infrastructure (HCI) vendor have have said they will build a service with some interesting potential.
The collaboration started a couple of years ago when Scale was approached by the Chocolate Factory to work with them on a new project. Google came to Scale on a purely nerd-to-nerd basis as some staff had been impressed by the upstream code contributions that Scale had been making. The result is nested virtualisation support within Google Cloud Project (GCP).
This allows Scale to virtualise an instance of their hyperconvergence software. Combined with some software-defined networking wizardry and an on-premises virtual machine, this GCP/Scale instance can be used by a customer's existing on-premises cluster for backups and disaster recovery just as they could use the traditional physical appliance to do cluster-to-cluster backups.
Because the GCP instance is just a hypervisor and any potential virtual machines running inside a Google Cloud VM, that VM can be resized as needed. This means that while serving as nothing more than a backup point, the instance could be set to consume minimal CPU and RAM with a large hard drive. If required to assume a disaster recovery role, the amount of RAM and CPU could be increased until it could run all the required VMs.
From Scale's standpoint, this announcement is a significant achievement. And to be fair, the work they put into creating a push-button simple layer 2 networking bridge between an on-premises Scale cluster and a GCP instance is worthy of a little praise. It's not an easy thing. The Google Cloud instance appears to the customer as though it were part of the same subnet they use internally. Compared to that, virtualising an instance of their own software is child's play.
For Google, it is a nice first step towards a fully functional hybrid cloud.
But – and it's a big but – Scale Computing and GCP have a very long way to go before they are even in the same league as full-featured offerings like Azure Stack.
Of greater interest to me are the wider implications for what having qualified this technology for general availability means. Doing a first rollout with Google is reasonably straightforward, because Google uses KVM and nested virtualisation with KVM can be accomplished with almost zero overhead compared to running on bare metal. It is one of the things KVM is very, very good at.
In theory, any service provider willing to stand up a KVM-based environment with the right configuration could also support a Scale hybrid infrastructure. While Amazon uses Xen and Microsoft uses Hyper-V, in theory each of these hypervisors could be set for nested virtualisation.
I have no real idea of what the efficiency of such a solution would be, and it would be quite interesting to see whether the finely tuned versions of these hypervisors run by the cloud giants could run Scale's nested hypervisors anywhere near as close to the speed of bare metal as Google's KVM-based cloud.
Smaller service providers may of course run whichever hypervisor they wish. There are service providers around the world with significant investments in KVM-based clouds. Most clouds running OpenStack, for example, run KVM. Down the road, this could lead to smaller regional service providers with an existing business of being managed service providers for small businesses standing up Scale-based hybrid clouds.
I find this Scale/GCP tie-up interesting not so much because of Google's involvement, but because of the non-Google things that can be done.
Hybrid infrastructure for the rest of us
Scale is best known as an HCI service that targets the small business market. Instead of taking an enterprise-focused solution, crippling it, and offering it at a still-unaffordable price, Scale built their product for small businesses and decided they would add enterprise-class features as and when they had customers asking for them.
Unofficially, Scale's target market is the business with one or two sysadmins who had only ever really administered Windows, were afraid of the command line, and just didn't want to have to bother with infrastructure. This has resulted in a robust and largely automated solution with very few nerd knobs to twiddle. It does the job, and generalist admins who don't have the time to become specialists can't get themselves into too much trouble using it.
As I see it, this makes Scale an attractive option for managed service providers. Channel players of all sizes are looking for a business model that allows them to survive in a world increasingly dominated by public cloud providers in general, and Amazon's AWS in particular. The "feed your customers to public cloud provider" approach isn't viable in the long run, so a lot of channel partners are standing up their own clouds.
Scale's hybrid infrastructure offers service providers a couple of different models. A service provider can opt to serve as a backup and disaster recovery point for their existing customer base. Alternately, the service provider could run the majority of the customer's workloads on their cloud and extrude a physical Scale Computing appliance onto the customer's premises to handle only those workloads that absolutely must remain on site.
The push-button layer 2 networking voodoo that Scale has created to make the GCP Scale instance appear on the same subnet as a customer's on-premises network can also work for service providers.
I won't exactly leap for joy at the idea that I can magically back up my workloads to Google's cloud. I don't trust the government to which Google is beholden. Also Google rolls over for them. Regional service providers working hand-in-glove with SMBs to create hybrid infrastructures, however, is a concept of which I am a strong proponent.
It's not really a hybrid cloud
You'll note that I don't call Scale's offering a hybrid cloud. They really want me to, and they themselves are pitching it as a hybrid cloud, but I can't call it that. As far as I am concerned, clouds have things that Scale does not. A self-service portal is one such missing feature. A robust and well-documented RESTful API is another.
Scale also lacks any of the tools required to build composable workloads. Clouds are all about building composable workloads, and then automating them with scripting. This is not a hybrid cloud.
While lacking some "cloud-like" niceties, Scale's hybrid infrastructure still does place it in some pretty rare company. Very few vendors are able to offer a service provider the ability to create a hybrid infrastructure. Fewer still offer transparent layer 2 bridging.
VMware can do this. You can order up service-provider provisioned VMware infrastructure in various flavours right now, including a hybrid infrastructure product. Of course, this being VMware and anything related to the word "cloud", such a thing is spectacularly difficult. Not to mention outrageously expensive.
When talking about the possibility of service provider clouds, however, it isn't Scale versus any of the big brand names that comes to mind. Microsoft, VMware and so forth pay little more than lip service to enabling service providers to offer hybrid infrastructure, let alone full-blown hybrid clouds. Ultimately, these behemoths want to own the customer relationship and as much of the associated revenue as possible, something that the service providers would ideally like to avoid.
As such, I see Scale competing more directly with smaller players such as Hypergrid, Yottabyte, or any of the OpenStack-in-a-can vendors like Stratoscale.
From a technical standpoint, it doesn't really matter how the service provider might choose to stand up the Scale virtual node VMs. Although, considering that Scale has not yet decided when, if or how they'll license their virtual nodes to service providers, their commercial decisions in that regard could close doors.
If Scale don't take the Apple route of insisting that virtual Scale nodes only be run on Scale appliances (which, for service providers, I sincerely doubt they'd make a requirement) then they can offer service providers a means to test the waters with minimal risk. Service providers could start by running their first few virtual Scale instances inside VMs on whatever infrastructure they already have (most likely VMware) until they proved that there was demand. Once demand is proven they could start investing in a KVM infrastructure to dedicated to standing up Scale virtual nodes.
One is an engineered, purpose-built hybrid infrastructure. The other is a clever hack that uses virtualization to make a previously existing solution do something it was never originally designed to do. It's hard not see the dichotomy between the two as some sort of metaphor for the entire IT industry.
Getting users on board
Because each customer's virtual Scale node lives inside a virtual machine, it's a little bit easier for the service provider to explain to customers how their data and workloads are isolated from other customers who also use the same shared physical infrastructure.
On the other hand, if the customer wishes to create sub-virtual data centres using the Scale model, they would have to instantiate a virtual Scale node as a VM running on top of their already-virtual Scale node. This is something that, at present, Scale has no plans of supporting. You don't get too many layers deep before this gets really complicated and overhead starts to become an issue.
The smallest businesses are unlikely to want to carve up their hybrid infrastructure into virtual data centres. For the next few years, at least, they are most likely to be interested in self-service as a means for systems administrators to instantiate infrastructure and services that will then be managed by those systems administrators.
Today's medium-sized companies, however, are eager to have individual departments managing their own IT, and are already struggling with shadow IT problems when departments turn to the public cloud to do exactly that without IT's permission. Administrators from these organisations would most likely benefit from being able to carve up infrastructure into virtual data centres, and to allow department heads to carve up their allocations by project, service, customer or other billable identifier.
All of this still applies if you take the service providers out of the equation. Google's GCP is really just a great big service provider, and Scale's current announcement is giving them a means by which to reach out to small businesses.
At some point, however, the Google/Scale offering will compete against Microsoft's Azure Stack, an engineered, purpose-built hybrid cloud connected to a competing public cloud provider. With the small difference that Microsoft's marketing and sales departments are a few orders of magnitude larger than anything a regional service provider partnership could bring to bear.
The Google-Scale announcement is interesting, both for what it is and what it could one day become. Scale will face some stiff competition. ®