Kubernetes comes to OpenStack this time thanks to Mirantis

For businesses wanting to run the Kubernetes cluster management framework for containers on OpenStack clouds, Google and Mirantis have teamed up to make that happen more easily.

The OpenStack Murano application catalog technology promises to ease deployment of Kubernetes clusters on OpenStack and then deploy Docker containers on those clusters.

Murano provides what Mirantis CEO Adrian Ionel (pictured above) described as a “seamless point-and-click experience” not only for deploying workloads to OpenStack, but also making sure they get there with associated automation, provisioning and security intact. “In this case we use it to automate the provisioning and life cycle management of containers,” he said.

Murano, he added, makes it easier for people to build application environments that can be container-only, or mix containers with bare metal and virtual machines in one big happy package. (I’m paraphrasing here.)

This is not the industry’s first attempt to bring Kubernetes technology, open sourced by Google last year, over to OpenStack. In August, [company] Hewlett-Packard[/company] announced its own Kubernetes setup utility for HP’s OpenStack-based Helion cloud, but I haven’t heard much about it since.

There is no exclusivity in this latest news. The work Mirantis and [company]Google[/company] have done here will, in theory, help customers deploy Kubernetes on any OpenStack distribution. Mirantis and Google will demonstrate the technology Thursday in San Francisco.

And in the grand scheme of things, nearly every cloud or wanna-be cloud vendor worth its salt (including SaltStack) Microsoft, IBM, Red Hat and others, have pledged or contributed actual support for Kubernetes.

This latest news is another indication that Google is indeed serious about providing cloud capabilities to business customers, many of whom still view public clouds like Google Cloud Platform with suspicion. OpenStack is the cloud framework usually mentioned when a company decides to deploy a private cloud that they deem more suited for mission-critical workloads.

“From a Google perspective, containerization is important and running container clusters is a great way to enable developers to be productive,” said Kit Merker, the Google product manager focusing on Google Container Engine and Kubernetes.

“We know that enterprises will take time to transition to cloud. Kubernetes is a way to optimize infrastructure so it can run workloads in private or public cloud or bare metal.”

kubernetes openstackSo this is about workload portability but not really hybrid cloud per se. “This means you can build an application that uses containers and then move it to a different environment. That is what Kubernetes is all about,” he said. That is not the same thing as seamlessly integrating public and private clouds into a hybrid scenario.

[company]Amazon[/company] Web Services still leads the world in public cloud but Google and [company]Microsoft[/company] are giving it a run for its money. Microsoft Azure, because of its business roots, is seen as an attractive public cloud for that company’s myriad business customers so both Google and AWS have to show that they “get” CIO concerns about cloud deployment and provide enterprise class features and functions.

This step by Google, along with other moves announced in the fall and more recent news that it’s bringing four Google services to VMware’s  vCloud Air, are meant to reassure the C-suite set that Google means business.

Note: This story was updated at 11:11 a.m. PST with a more complete list of Kubernetes contributors.

 

Was 2014 the end of enterprise computing?

It’s been just over a year since I left Netflix and joined Battery Ventures. So it seemed appropriate (if a couple of weeks late) to take a look back at some technology and cloud themes that bubbled up in 2014 and offer a few predictions for the coming year.

In 2015 I expect more hubbub over everything from the Docker/containerization craze to Netflix’s open-source cloud platform to — dare I say it? — the end of enterprise computing. Here are some thoughts about the recently ended year in tech, in no particular order:

The Netflix open source cloud platform got traction

The Netflix team continues to release projects (about ten new repos on GitHub during 2014) and get more traction.

Notable external use cases for the [company]Netflix[/company] platform include growth in interest in the Reactive programming model using Hystrix; the Spring Microservices architecture including [company]Netflix[/company]; IBM’s Watson services, built using NetflixOSS; and Nike’s online services using NetflixOSS described at the AWS Re:Invent conference. Some aspects of the NetflixOSS architecture have been more widely influential, as seen in the growth of interest in microservices and the immutable service model encouraged by

Docker

Docker wasn’t on anyone’s 2014 roadmap, but is on everyone’s 2015 roadmap. (There was even a New York Times story about it earlier this year.) The Docker open-source project—which automates the deployment of new applications inside software “containers” — is an excellent example of how to drive viral adoption of a developer product, and it combines four useful things in one. It’s portable, speeds up development, defines the configuration and is shared via Docker hub. It’s become a key ecosystem and will undoubtedly continue to grow in 2015.

The concept of anti-fragility took off

The ideas behind the Netflix Chaos Monkey, a Netflix service that helps test the automation that helps systems recover from problems, are that you have to prove you are resilient and exercise failure-recovery mechanisms by creating your own failures. This is now so prevalent that it’s being mentioned in unexpected places, such as a business discussion with Workday, and a talk by the CIO of the Department of Homeland Security Citizenship and Immigration Services at the DevOps Enterprise Summit. As enterprises re-architect their systems using principles from DevOps, micro-services and cloud native architectures, the trend is to bake in and automate recovery and resilience.

Cloud roundup: AWS moves on to a new phase

[company]Amazon[/company] Web Services continues to dominate cloud computing, and the service doubled its IP address range again this year, to about 10 million. The IP address range sets an approximate upper limit on the number of instances that AWS could run at the same time, since by default most instances get assigned one address. It is one of the few available metrics that shows the growth rate.

An interesting reversal occurred during 2014: Previously, clouds were seen as having missing features compared to data centers, but now there are many startups that are building products for data centers to provide features that already exist for AWS. It appears that the most sophisticated operations architectures are now on AWS, not on premise.

[company]Microsoft[/company] Azure is getting a lot of enterprise-cloud signups but still doesn’t represent a significant proportion of the overall cloud market. There were several large and embarrassing Azure outages in 2014, and relatively few non-Microsoft services were impacted enough for the public to notice.

AWS had a few zone-level, partial outages or network partitions, but nothing significant enough to cause widespread impacts. Notably, it’s now two years since the last big AWS outage. (Remember all the press those used to get?). While AWS has matured and made its services and operating practices more resilient, Azure has some work to do.

[company]Google[/company] spent 2014 getting enterprise features in place and hiring lots of ex-AWS people. But it still has a lot to prove as a cloud vendor. Google is an interesting alternative to AWS for startups, but the company is going to have trouble getting the enterprise market adoption that Microsoft and AWS have already figured out. Startup cloud vendor Digital Ocean, meanwhile, is growing fast and has carved out a space for itself as the simple, developer oriented, cloud solution. AWS has added so many features that it’s a full-time job just trying to keep up with them, so I think there is a place in the market for something easy to understand and use.

Enterprise computing vendors

Bottom line: The big, traditional enterprise-computing vendors are failing to grow their customer bases. You can watch their revenue from new-product sales fade.

Services and support revenue will increase to compensate in the short term, but even that will eventually collapse as customers move on to low-cost, open-source solutions or outsource to cloud-based services. This is one of those times in which replacement technology revenue is an order of magnitude cheaper than the incumbent revenue.

For example, we could see market segments that currently generate $10 billion of revenue for traditional enterprise-computing vendors be entirely replaced by $1 billion of revenue for cloud vendors and open-source based startups. My friends Peter Magnusson and Marten Mickos joined Oracle Cloud and HP Cloud in 2014. I wish them well, but I’m not optimistic that they will be able to generate enough revenue to offset the losses elsewhere.

Adrian Cockcroft is technology fellow at Battery Ventures. Prior to that he was cloud architect at Netflix, but also spent time as distinguished engineer at eBay and Sun Microsystems.

Amazon Web Services gets with the Golang program

Amazon Web Services already offers software development kits (SDKs) for Java, C#, Ruby, Python, JavaScript, PHP and Objective C programming languages. Now it says it will add Go (aka Golang) to that list. More accurately, it says it’s taken over aws-go, an SDK developed by Stripe. The SDK is in a sort of beta stage, with work continuing.

While Go doesn’t have nearly as many users as Java or C — an IEEE Spectrum survey ranked it as the nineteenth most popular language between Scala and Arduino — it’s gained traction among developers. That’s especially true for those building cloud or web services infrastructure. Docker, which has taken the development world like a gale force wind, is written in Go, for example. This slideshow explains why.

Just ask Derek Collison, Founder and CEO of Apcera who called Golang’s rise to fame more than two years ago.

Asked if he still holds that opinion, he was unequivocal. “[Go] got quite a bit right with the language for the Get Sh*t Done crowd, it appeals to them and anyone doing distributed systems or cloud platforms … should at least consider it,” he said via email.  Apcera, was built on Go and 95 percent of its code-base is Go, he said, adding: “We made this decision over Node.js which has had its struggles as of late on the community side.”

Sendgrid is moving over to Golang from Perl, and here’s a succinct rationale by Sendgrid co-founder Tim Jenkins, who said Go, which incubated at [company]Google[/company], facilitates concurrent programming so that calculations can execute at the same or overlapping times rather than one at a time.

While what we do isn’t rocket science, doing it at a scale of over 500 million messages per day is extremely challenging … One of the most compelling reasons for using Go at SendGrid is having the concept of concurrent asynchronous programming as part of the language. The argument always came up that you can do asynchronous programming in Java, but it isn’t pretty. My argument was always that ‘We can keep doing it in Perl,’ which usually helped people to understand that just because you can do something with a technology doesn’t mean its the best way to do it.

[company]Amazon[/company], which wants to be the default tool provider to developers everywhere, is filling in an important checkbox here.

This story was updated at 8:10 a.m. with Derek Collison’s comments.

Docker adds new leadership to open-source project

Docker is rejiggering the operational structure of the Docker open-source container project and is adding a couple of people to help oversee the project alongside with Docker, Inc. co-founder and CTO Solomon Hykes.

The new leadership roles are the chief architect, chief maintainer and chief operator, and they were created to help Docker accommodate its rapid growth. Docker claims that it now has roughly 740 project contributors and that the open-source project has generated 85,000 Docker-specific applications and more than 20,000 projects like management frameworks and monitoring tools.

Hykes will take on the role of chief architect, in which he’ll be responsible for outlining future endeavors of the Docker project like its recently-released orchestration services. Michael Crosby, who has been a Docker open-source contributor since 2013, will become chief maintainer and will be responsible for ensuring that community member code and contributions adhere to Docker’s standards.

Steve Francia, formerly chief developer advocate for MongoDB, was brought onboard as Docker’s chief operator, and his role will be to ensure that community members are actively communicating with each other, making sure that releases go out on time and welcoming new contributors into the Docker fold. In some open source communities, it might be intimidating for new users to participate out of fear of getting called out for perceived mistakes or the like.

“One thing we do is that we don’t say no,” said Francia. “We say here is what you need to do to be a yes.”

If certain bad apples appear in the Docker community and start causing trouble, Francia will take action but he stresses that his job is “about making people feel welcome, not reprimanding people.”

While Docker doesn’t have a formalized code of conduct akin to something that Chef or the Python Software Foundation have, Francia said Docker has “some guidelines” for monitoring bad behavior. The Docker project has only been around for 18 months and project members “will be working to communicating those guidelines better” as time goes on.

Be sure to listen to Docker CEO Ben Golub on the Structure Show podcast where he discussed Docker in 2015, its new services and where it sees CoreOS.

[soundcloud url=”https://api.soundcloud.com/tracks/182147043″ params=”color=ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false” width=”100%” height=”166″ iframe=”true” /]

What’s big in venture capital: Security, security, security

Steve Herrod has seen a lot in the enterprise IT space, having spent 12 years at VMware — the last several years as CTO and vice president of R&D — before leaving in 2013 to join venture capital firm General Catalyst Partners. And right now, after seemingly dozens of high-profile cyberattacks in as many months, Herrod has security on his mind. He came on the Structure Show podcast this week to tell how he’s thinking about that space.

Here are a few choice quotes from the interview (including about Docker and the pace of tech innovation), but it’s definitely worth hearing the whole thing. Herrod offers up a lot more thoughts on the cybersecurity. as well as cloud computing, containers and the public appetite for tech IPOs.

[soundcloud url=”https://api.soundcloud.com/tracks/184974081?secret_token=s-DR28d” params=”color=ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false” width=”100%” height=”166″ iframe=”true” /]

Download This Episode

Subscribe in iTunes

The Structure Show RSS Feed

Security as corporate strategy

“For me, it’s the first time that sort of infrastructure issues are coming up at board-of-director meeting for completely non-technology companies,” Herrod said. “Nobody wants to be in the news whatsoever, and the cost of these break-ins is obviously ridiculously high.”

There is no enterprise force field

“I think you should just assume bad things are going to happen, so let’s think about how to mitigate or restrict how bad they can be,” Herrod explained.

“Forget perimeter,” he added. “Let’s think about how do we wrap data, how do we write applications, how do we use identity as the very core, regardless of where we’re accessing things?”

Mobilize 2011: Stacey Higginbotham – Senior Writer, GigaOM; Stephen Herrod – CTO, VMware

Steve Herrod at Structure 2011.

It’s time to give the cloud it’s due on security

“If you meet the ops teams and the groups that are there building these clouds, I think they’re far more secure than what’s going on in the private data centers because they have much more-intensive staffs,” Herrod said. “These guys have gone through every audit — they’re the superset of every audit that their customers have to go through, and they see the most-sophisticated attacks and thus have to do a lot of work behind it.”

2014 was the year of the container; 2015 will be a year of awakening

“Last year was the year of Docker awareness. I think it was the most-publicized open source thing since OpenStack,” Herrod said. “… But I think this is the year you see the hype die down and kind of the realities of what it means to use these containers [and] the fighting that will go on between a bunch of different vendors offering the best approach to containers.”

Keeping up with new tools is a full-time job

“I actually see all the time the developer back channels on what is the most-productive toolset or what is the coolest way to build this new type of startup company,” Herrod said. “That travels super-quickly through conferences, through articles, through social networks, and thus I think you get this herd mentality moving to the next new thing very quickly.”

Amazon Web Services adds to its enterprise war chest

This week Amazon Web Services continued its enterprise-focused feature push with new resource groups and a tag editor for EC2 instances, which means that IT people at big companies (or even smaller organizations) will have an easier time isolating the resources they use.

The new [company]Amazon[/company] Tag Editor makes it easier for admins to group resources on a logical basis whereas before they had to tag them “service-by-service, region-by-region” according to the AWS blog post.

Admins can also then allocate a group of resources that share one tag or more and the group can span regions and services. This, said AWS, creates a “custom console that organizes and consolidates the information you need on a per-project basis.” There’s more here from IDG news.

Over the past six months or so, AWS has launched features to appeal to Windows admins, their counterparts in the VMware  world; directory services, and a service catalog for its cloud products that some think will soon encompass third-party services in the cloud and on premises as well.

New Google SDK for data heads

Also this week in cloud,  Google said it is open-sourcing the software development kit (SDK) for Cloud Dataflow, which itself was announced (in alpha form) at Google I/O in June. Dataflow’s goal is to make it easier for analysts, data scientists and developers to access large data sets for their work.

Per the [company]Google[/company] Cloud Platform blog post, the SDK

… introduces a unified model for batch and stream data processing. Our approach to temporal based aggregations provides a rich set of windowing primitives allowing the same computations to be used with batch or stream based data sources. We will continue to innovate on new programming primitives and welcome the community to participate in this process.

This SDK sort of compares to the AWS Kinesis Java client while Cloud Dataflow overall will contend with Amazon’s Kinesis service, which, as one developer pointed out “is available now, fully supported and not in alpha or beta.”

Google Cloud Platform logo

Docker boss responds to CoreOS fracas

Who knew that containers could stir so much passion? This week on the Structure Show, [company]Docker[/company] CEO Ben Golub talks about the dustup CoreOS started with its Rocket container news and touches on other hot topics as well. So check out Derrick Harris’ and Jonathan Vanian’s chat with Golub about halfway through, but if you want to hear about our take on how [company]Hortonworks[/company] and [company]New Relic[/company] were faring in their first week as publicly held companies, start at the beginning.

Ben Golub, CEO of Docker

Ben Golub, CEO of Docker

[soundcloud url=”https://api.soundcloud.com/tracks/182147043″ params=”color=ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false” width=”100%” height=”166″ iframe=”true” /]

 

Download This Episode

Subscribe in iTunes

The Structure Show RSS Feed

Where is enterprise infrastructure headed in 2015?

The enterprise industry is another year older … and hopefully somewhat wiser. Here’s what enterprise watchers should expect to see in 2015.

More cyber attacks

Sadly, this is an easy one. As bad as 2014 has been, and it has been bad, we’re just seeing the tip of the iceberg. Given the steady increase in value going through our systems (credit cards numbers, personal information, IP), organized crime and nation-sponsored attacks will continue to rise in quantity and sophistication. The current approaches to security clearly aren’t cutting it, which is why the security space is one of my biggest personal focus areas. (Full disclosure I’m an investor in Illumio, Menlo Security and ThreatStream, all companies in this space.)

AWS pushes further into the enterprise

Almost every startup that we fund today is using [company]Amazon[/company] Web Services, but it’s interesting to see AWS creep further into the medium and larger companies that dominate IT spending. At this year’s AWS Re:Invent, there were lots of compelling enterprise anecdotes, plenty of “all-in” stories, and, most importantly, the arrival of an ecosystem. There were startups and large companies alike announcing integrations with AWS with particular focus on the “-ities” — predictability, manageability, security, and availability. These are good signs of increased adoption in mainstream businesses where it’s now not “if” but “when” a company adopts cloud.

AWS: Reinvent

The rise of IaaS competitors

AWS continues with its strong lead, but 2014 also showed that there’s going to be a bigger fight than ever. In particular, [company]Google[/company] Compute Engine and [company]Microsoft[/company] Azure are rapidly improving their services and have the pocketbooks to fight this for the long term. Throw in Rackspace, IBM, vCloud Air, HP and the many other regional or vertically oriented offerings, and it’s going to be a major battle — with customers as the likely winners.

Containers get down to work

The rise of Docker has been one of the true success stories of 2014. However, it has also created a deluge of competitors (CoreOSRed HatUbuntu) and interesting co-opters (AmazonGoogle and VMware). Quite a year for a previously unheralded technology. The rise is real, but I believe that some of the hype will subside in 2015 as the some of the real work of making containers usable by enterprises begins in earnest.

Docker and the money container

Converged/hyper-converged infrastructure grabs the limelight

2014 saw continued excitement over “converged infrastructure,” pre-configured hardware/software bundles that are powerful and easy to adopt. Nutanix, VCE and Cisco UCS get most of the attention, but there’s lots of interesting competition on the way, especially as the latter two vendors update their relationship status to “It’s complicated.” Latest offerings include VMware’s EVO designs to new products from the big system vendors (Dell and HP are particularly aggressive). And I can personally attest to a slew of startups heading into this converged world with a variety of technologies and approaches.

APIs on the mind

I wrote about “mobile-first infrastructure” earlier this year and continue to think it will drive several longer-term infrastructure changes. In 2015, I think it will manifest itself most as the rise of APIs in enterprise development, as companies both produce and consume APIs like never before. Look for increased conversations, companies and challenges arising over this shift. (Full disclosure: I’m a backer of RunScope, which makes developer tools for this “API economy.”)

Network virtualization gets its legs

There has been much discussion of the arrival of software-defined networking (SDN). However, the term itself has been polluted to a point where it means different things to almost anyone you ask. I prefer the term network virtualization to speak more holistically about the advancement in separating out the logical network from the physical network. Cisco ACI and VMware NSX appear to have the lead, and 2014 saw significant movement from proof-of-concepts toward significant paid usage. Anecdotally, most of the adoption is in service providers, financial services and tech-heavy IT companies. 2015 should see further progress in the adoption, including by a broader set of consumers.

Big deals for big data

In 2014 there was nonstop talk about big data, analytics, and the opportunities and challenges of each. 2014 funding for companies has been unprecedented, ranging from Intel’s huge bet on Cloudera to substantial private investments in DataStax (driver of Cassandra)Databricks (driver of Spark)PlatforaAltiScaleDataGravity and numerous others. (My company, General Catalyst, invested in AltiScale and DataGravity.) Next year these companies will all focus on revenue — and we’ll see how the public markets respond to at least one Hadoop vendor, as Hortonworks is now a public company.

That’s one person’s cut at developments in enterprise infrastructure for 2015, and I’m sure I’ve omitted others that will be even bigger. That’s what is so fun about this space these days: We’re in a modern-day renaissance driven by the convergence of new technologies, new expectations and new challenges, all of which point toward more and bigger changes happening each year than may have taken place in prior decades. Here’s to the fun ride ahead.

Dr. Steve Herrod is a managing director at General Catalyst Partners and was CTO and senior vice president of R&D at VMware.

Note: This story was updated at 5:24 p.m. PST to correct the reference to Cisco ACI (application-centric infrastructure) not ACE.

CoreOS CEO: We’re not out to replace Docker, just its containers

There was a major shakeup in the world of container-based computing this week when operating system provider CoreOS decided to get into the container space with a new open source project called Rocket. It’s a container runtime environment as well as a set of specifications for how App Containers — what CoreOS calls its container images — are built and function. But the bigger news industry-wide was the suggestion from CoreOS that it built Rocket because developer darling Docker isn’t living up to expectations.

CoreOS Co-founder and CEO Alex Polvi came on the Structure Show podcast this week to clarify that message and to explain the rationale behind Rocket and everything CoreOS does. If you’re interested in the future of containers, distributed systems and even cloud computing, both business-wise and technologically, it’s a must-listen interview. Here are some highlights, but there’s a lot more good stuff.

[soundcloud url=”https://api.soundcloud.com/tracks/179884272?secret_token=s-mb5PC” params=”color=ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false” width=”100%” height=”166″ iframe=”true” /]

Download This Episode

Subscribe in iTunes

The Structure Show RSS Feed

We’re fine with Docker, really!

If there’s one point that Polvi really wants to get across, it’s that CoreOS didn’t build Rocket because it doesn’t like Docker — either the technology or the company. He called that notion — expressed by the media, as well as, in numerous fora, Docker founder and CTO Solomon Hykes — “fundamentally flawed.”

The rationale behind Rocket is simple, Polvi explained. Docker is turning into more of a platform, adding in features around cluster management, networking and booting cloud servers, and CoreOS wanted to make sure that the original, simple container component didn’t get lost to the world as that happens. In fact, he says he’s fine with the idea of a Docker platform:

[blockquote person=”” attribution=””]”That’s a fine product, the private cloud is an open territory right now still. So the Docker platform is a product that needs to exist. We just want the simple composable building block to also exist for people that have their own platforms or they’re trying to build their own platform to use as a reusable component.”[/blockquote]

Although, below the surface, it might not be the mutual respect society the companies would like everyone to think it is. Later, while comparing Docker’s move away from containers to VMware’s move away from virtual machines, Polvi noted, “There is a debate as to whether the technology warrants another company like VMware to emerge.”

CoreOS CEO Alex Polvi

CoreOS CEO Alex Polvi

We build what we have to

When you consider the CoreOS business strategy, the reasons for Rocket begin to look a little more clear. Polvi calls the CoreOS lineup of technologies, which also includes a database, registry service, cluster management and other pieces, “a platform for platform builders.” It’s building the “primitives” that people need to build next-generation distributed systems and platforms, as opposed to actually building the platforms (think Heroku or CoreOS partner Deis) where people ultimately deploy applications.

“We are never trying to just take somebody else’s solution and build it,” Polvi said. “We’re trying to fill in the white space and build something that’s technically sound in an area we think is an open problem.”

He contrasts this with Docker, which he says is now becoming more akin to cluster (and container) management plays such as Mesosphere and the Kubernetes project, or VMware. Those technologies might use containers and let users move them around and manage them, but they’re far more about the management aspect than about the containers, or any other pieces of infrastructure, themselves.

Kubernetes works levels above the container, which isn't mentioned on this diagram from Microsoft.

Kubernetes works levels above the container, which isn’t mentioned on this diagram from Microsoft.

In fact, despite the fact that CoreOS has its own cluster-management tool, called Fleet, Polvi said the company actually contributes quite a bit to the Google-led Kubernetes project because it really likes the technology and the trajectory the project is on.

“Docker was a similar thing early on,” he added. “We used it for a year, we collaborated heavily with that community, but then it became clear they were on a trajectory that was no longer what we needed — and what a lot of people needed, not just us.”

Still, Polvi noted, technically, there’s no reason why Docker containers and Rocket can’t coexist provided Docker is willing to work within CoreOS’s container specifications or collaborate with CoreOS to develop a standard container format.

Structure 2010: Sebastian Stadil – CEO, Scalr; William “Skip” Bacon – VP of Products and CTO, Virtual Instruments; Michael A.Jackson – Co-Founder, President, and COO, Adaptive Computing; Jagan Jagannathan – Founder and CTO, Xangati; Alex Polvi – CEO and Co-Founder, Cloudkick; Javier Soltero – CTO for Management Products, SpringSource

A younger Polvi (far left) talking cloud a Structure 2010.

A quick thought on the cloud

We also asked Polvi about the world of cloud computing, where he used to work after Rackspace acquired his last startup, CloudKick, and where many CoreOS workloads will likely run. Maybe old allegiances just die hard, but Polvi thinks Rackspace is actually in a pretty good position as bigger cloud providers such as Amazon Web Services, Google and Microsoft continue to drive down prices.

“Now, because of the competitive pressure of the cloud providers, compute on infrastructure will go asymptotically to free over time, as well,” he said. “If you think about it, what’s left after the hard parts of software are free and the compute itself is relatively free, or free enough? … I think it’s service, that’s how you do it. You help people use all this stuff.”

Amazon’s Jeff Bezos talks succession plan (sorta)

The week in cloud

Last week, Amazon CEO Jeff Bezos talked a bit on stage about what Amazon would be without him. At a Business Insider event, Bezos was asked the zillion-dollar succession question. After the slow-mo Microsoft CEO search we endured last year, that topic resonates.

And the answer was: Yes, [company]Amazon[/company] does have a CEO successor lined up should something happen to Bezos, as it does with all senior managers, presumably including the Amazon Web Services brain trust of Andy Jassy and Werner Vogels.

So who is that successor? Bezos put down the hammer: “It’s a secret.”

Also interesting is Bezos’ take on how Seattle-based Amazon differs from stereotypical Silicon Valley tech companies. There are no free gourmet-lunches and no suburban Montessori-school-like headquarters. Amazon’s culture revolves around its urban HQ and a definitive butt-in-chair work ethic.

And, in Bezos’ opinion, taking a job with the company that offers the best free massages may not be the optimal career choice for a young engineer. More here from Gigaom’s Jeff Roberts on the event..

The full segment is here.

Container-on-container violence

If you were on a tech media news blackout last week, you missed the dustup touched off when CoreOS launched its own Rocket container, in a move seen as a direct shot at Docker.

CoreOS’s contention is that while Docker adds orchestration and other trimmings to its container it’s sort of neglecting the container itself and that its process model is “fundamentally flawed.”

Docker cried foul. If a company wants to just use just the Docker container, it can do so although Docker’s “batteries included but removeable” slogan isn’t helping its cause.

It makes total sense for CoreOS to glom onto what it sees as a great thing to get a piece of the action, which is how many people see what’s transpiring. “Every time some piece of technology gains traction you see all these prospectors staking claims,” said one long time observer who thinks CoreOS hasn’t done itself any favors the way it went about this, blasting out a blog post on the eve of Dockercon.

This gold rush happened with Rails, it happened with Node.js, it happened with Linux, and now it’s happening with Docker, he said.

But it also looks like there’s fear that the Docker “platform” will encroach on stuff offered by third parties, which Docker CTO and Founder Solomon Hykes addressed in comments to this blog post by CloudCredo CEO Colin Humphreys. Hykes wrote:

“The fact that Docker is building a platform does not at all mean that ‘docker’, the command-line tool, will become bloated and monolithic. Quite the contrary! The major theme of Docker is in fact the exact opposite: to make it more modular, and make it easier to use one part without the other. In fact, the very features mentioned by the CoreOS blog post (machine management, clustering) will not, in fact, be incorporated into the Docker binary.”

Below check out a couple of relevant Structure Show podcasts. First, last week’s show with CoreOS CEO Alex Polvi in which he says there’s nothing wrong with Docker going the platform route, but people need just plain containers. Then one from July in which Hykes discusses (presciently) how tricky Docker governance was going to be going forward.

[soundcloud url=”https://api.soundcloud.com/tracks/179884272?secret_token=s-mb5PC” params=”color=ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false” width=”100%” height=”166″ iframe=”true” /]

CoreOS CEO Alex Polvi

CoreOS CEO Alex Polvi

 

[soundcloud url=”https://api.soundcloud.com/tracks/158076928″ params=”color=ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false” width=”100%” height=”166″ iframe=”true” /]

 

Docker Founder and CTO Solomon Hykes at DockerCon 2014

Docker Founder and CTO Solomon Hykes at DockerCon 2014

 

 

 

SHOW NOTES

Hosts: Barbara Darrow and Derrick Harris

Download This Episode

Subscribe in iTunes

The Structure Show RSS Feed

PREVIOUS EPISODES:

More from Facebook on its new networking architecture 

Do you find OSS hard to deploy? Say hey to ZerotoDocker

All about AWS Re:Invent and oh some Hortonworks and Microsoft news too

Ok, we admit it. Google may be serious about cloud after all

EMC cloud really isn’t all about EMC hardware, says EMC product chief