As today is Father’s Day, I got to thinking about the stuff my father taught me that sunk in enough to have influenced my career or the guidance I’ve given others. On one hand, he introduced me to my first computer – an Apple II that he brought home to do spreadsheet/accounting work. We didn’t have any in school at the time, and I don’t recall the neighbors having one yet. He was just curious about how it worked. On the other hand, computers were really not a big part of my life growing up, so this may turn out to be more about learning skills and dealing with changes.
Many of my friends followed a path that was similar to their parents, and in the case of many of my male friends, it was influenced by their fathers. Doctors follow doctors. Lawyers follow lawyers. Engineers follow engineers. Teachers follow teachers. Coaches follow coaches. And so on. But my father grew up a farmer. No computers. No electronics. Just land to plow and animals to raise.
He told me many times how much he disliked the farm life, but he spent an equal amount of time telling me about the work ethic that comes with farming. Up early, work late, deal with bad weather and uncertainties. Sick days don’t exist. There were no shortcuts. You measure yourself on the effort (day-to-day), but ultimately on the collective results. And you find the balance between the things you love and the things you need to do – just because. Continued »
While it is only expected to have 2000 attendees, next week’s DockerCon 2015 is already shaping up to be one of the most highly anticipated events of the trade-show calendar. As noted VC (and Cloud expert) Adrian Cockcroft likes to say, “Docker wasn’t on anyone’s roadmap in 2014. It’s on everyone’s roadmap in 2015.”
Here’s what I’m looking forward to at the event:
- Who is Docker in 2015? Per their mission statement, “Docker is an open platform that enables developers and system administrators to create distributed applications.” They have taken $150M in VC funding. They have a rapidly growing community (both in downloads/contributions) and new Docker-centric startups, but are also acquiring companies (eg. Socketplane, Kitematic) to fill in holes in their “stack”. Do they solidify themselves as a “platform”, competing with structured or unstructured PaaS offerings“, or do they avoid that classification and just stay focused on being an enabling technology? Do they target developers, operators, or both?
- Who is the Docker ecosystem in 2015? Last year, they limited attendance to 200-250 people. This year it’s 2000 (by comparison, Cloud Foundry Summit was ~1500). In about 18 months, Docker has been downloaded over 300M times. Many start-ups will come out of stealth next week, and many enterprise vendors will be jumping on the Docker bandwagon. But the biggest question I have is how does the Docker philosophy of “batteries included, but removable” resonate with the ecosystem? Is Docker building a flexible, pluggable stack, or are they building a more monolithic “suite” that is less ecosystem friendly?
- How do the new Docker v1.7 plugins work? Just released, it will be interesting to watch how this segment of the marketplace grows. Will the plugins be vendor-specific (and proprietary) or will significant contributions by vendors be made back into the primary, open projects?
- Is Storage + Docker hot? One of the topics that I’ve been hearing over and over again in the context of container is, “How do we manage persistent data, or storage?” I’ve heard it in the content of Mesos and Kubernetes, in the context of Cloud Foundry and now we’re seeing early announcements from projects like Flocker and RexRay, as well as new “volume” concepts and functionality in v1.7 of Docker. While container-based applications tend to be associated with stateless applications, the reality is that data must be dealt with somehow, and many people are looking at ways to bring the benefits of containers to the management of data.
- Security? VMware tried to tell the world that containers alone are not enough (or “insecure”) and are best run in a VM. Some early surveys confirm that many container deploys are still running in VMs. But Docker has tried to counter these claims with Security Best Practices and tools to avoid getting their momentum stalled, especially in Enterprise accounts.
- Users? Customers? Paying Customers? Use-Cases? There is no doubt that Docker is white-hot these days, but who are the users, what industries do they represent and are they creating revenue streams for Docker, Inc? The speaker lineup and agenda looks promising, with many geographic regions and industries represented, so it’ll be good to ask some deeper questions about how Docker is being used in their environments.
Overall, it should be a great benchmark to understand where this fast moving company and community is moving. Docker has the potential to disrupt so many segments of the Cloud-Native application industry, so it’ll be interesting to see how big of a piece of the pie they are going after and how the marketplace responds.
Before I get into my thoughts on VelocityConf (Santa Clara, 2015), I thought that I’d share a quick story. I’ve been attending open source events and meetups for several years (OpenStack Summit, LinuxCon/CloudOpen, DevOps Days, Cloud Foundry Summit, etc.) and have become comfortable with the vibe and communities at the events. They are very different from vendor events, in good ways and bad ways.
A few months ago, during my day job, we decided that we’d like to host a DevOps Days style event before EMC World. I reached out to some friends to see what the proper steps were to host an event, since DevOps Days has a planning organization. I was introduced to Bridget Kromhout (@bridgetkromhout) and we spoke for an hour about our idea for an event. As expected, she was very friendly and informative, but a little bit cautious about a “big vendor” doing this, since other “big vendors” had violated some of their guidelines about over-marketing in the past. Fair enough, we’d do our best stay within all of their guidelines as we hoped to show this community that we wanted to contribute valuable things (beyond free food & drink). Although she didn’t need to (we weren’t an official event), Bridget continued to provide us guidance and encouragement, as well as occasionally correcting us when we made some tactical errors. I tell this story because Bridget is like so many others that are involved in DevOps Days and VelocityConf – they are passionate about this domain and excited to help others that wish to learn and share. But she’s also very focused on it being done the “right way”, as we’ve seen too many other industry trends get swept up in marketing hype.
What does this have to do with IT organizations and VelocityConf? Actually, quite a bit…
Some common misperceptions about open source events (or DevOps or Web Scale, etc.)
- If it’s all open source, nobody spends or makes any money. – Tell that to Target, MLB, Google, Microsoft, Etsy, Orbitz, and many others names that presented sessions. Or tell that to the many VCs walking around the halls looking for the next big idea to fund.
- It’s just a bunch of neck-beard hippies. – Keep thinking that. They run some of the most influential and powerful companies in the world, and are getting presidents elected. Beards optional.
- They don’t understand the Enterprise. – Tell that to the Enterprise group that stuck around after a Security + DevOps session to talk about how they used DevOps, Public Cloud and Agile Development while dealing with SOX, HIPAA, and a bunch of other heavy regulatory guidelines.
- It’s just a Silicon Valley thing. – Except that they hold the events worldwide, and you’d find as many influential people from NYC or Minneapolis as you would Portland or SF/Bay.
Here’s what I loved about VelocityConf:
One of the most frequently discussed topics on the podcast, sometimes on the air and sometimes off, is the financial future of all these cool new technology companies that have open source software at the core of their business. Companies like Docker, CoreOS, Hashicorp, Mesosphere, Puppet Labs, Chef, Mirantis, Ansible and many others. We watch as they continue to get increasing large VC funding rounds, and like the dot-com bubble of the last 1990s, we wonder how they will match their revenue models with their valuation models. [Note: Puppet Labs had a strong Q1 revenue announcement]. Are these companies that are built only for acquisition (short-term), or do they have the sustaining power to last 5, 6 or 7 years before they move to IPO stage.
Keep in mind that these companies, with open source at their core, are different from other start-ups that are enduring longer periods of existence/growth (5, 6, 7yrs) without building an open source community – eg. Nutanix, SolidFire, Virtustream, Box.net, etc.
As I think about all the funding, I remember back to some of the most important (and pragmatic) guidance I’ve gotten from entrepreneurs like Rodrigo Flores and Rodney Rogers – “no matter how cool you think your technology is, it can only create a sustainable business if you can actually collect a Purchase Order (P.O.)”. And it’s important to remember that there is a big difference between building a community around a technology and building a business around your technology. It’s the difference between creating value and capturing value. The former requires technologists and vision. The latter requires that you understand not only who will fall in love with the technology, but who will approve and fund the acquisition of the technology (directly or as-a-Service). It means contacts, licenses, terms of payments and all those are things that aren’t embedded in a GitHub update. Continued »
For just a two day event, the 2015 Cloud Foundry summit produced quite a few interesting elements for a community that is starting to mature and hit it’s stride. I’ve written about it a couple times (here, and indirectly from discussions here) immediately following the show. But now that I’ve had a few days to reflect on it, some other thoughts came to mind:
The Foundries are Forming
When we spoke with Sam Ramji, he spoke about the development and contribution model for Cloud Foundry projects. While “outside” contributions are considered, to become a core contributor one must work within the “Foundry” model of pair programming. And in 2015, several new “Dojos” have been stood up. Dojos are the physical locations where the Cloud Foundry model of pair programming is preached and practiced. While a dojo existed at the Pivotal offices in San Francisco, new dojos have now been added in EMC’s Boston/Cambridge, and new dojos were announced for RTP, NC (by IBM) and another independent dojo in San Francisco (by Cloud Foundry Foundation). In speaking with leaders in the Cloud Foundry Foundation, it’s expected that more dojos will open in 2015 and 2016, including locations outside of the United States.
New Business Models are Forming
IBM offers Cloud Foundry as a public cloud service, under the BlueMix brand. Pivotal offers it under the Pivotal Web Services Brand. CenturyLinkCloud now offers Cloud Foundry via their 13 Data Centers. Huiwei will offer Cloud Foundry to their global customer base. And many others are offering Cloud Foundry both on-prem and off-prem, delivering interoperability across multiple clouds and in multiple geographic regions. Interoperability and competitive markets create great value and opportunities for customers. It creates the potential for new business models to emerge.
Public Cloud is the Starting Point, But Private Clouds still Exist
The premier customers that were highlighted throughout the week were well-known Enterprise names, across multiple industries. For many of them, their starting point in using Cloud Foundry was a public cloud offering or instance. It not only allows the developers to get new applications up and running quickly, but it also begins the organizational transformation that’s needed to make PaaS a successful IT model. It’s the model called out in books like “Switch“, where small but noticeable change is more important than boiling the ocean. And then for many of these companies, they would deploy an on-prem instance and continue to build cloud native apps and transform their culture or business. This is a reversal of the model we frequently heard about IaaS models, where it started as an on-prem IT Transformation, with the promise of extending it to a public cloud for added capacity – “cloudbursting”. Continued »
In my case, I recently found myself in Kitty Hawk, North Carolina, ascending the sandy Kill Devil Hills. It was on a school field trip with my older daughter to learn about the history of the state. On this site, back in 1903, Orville and Wilbur Wright manned the first motorized flight. Soaring amongst the birds, high above the sandy ground, finding balance between wind and gravity.
In parallel, I’ve been preparing a talk about “Why Business Should Care about DevOps” for EMCworld. To draw an analogy, I go back and look at how Henry Ford revolutionized the creation of not only a new industry, but also the surrounding industries of hotels, suburbia, drive-thru restaurants, and interstate highways.
Even though I benefit from their genius on a daily basis, I hadn’t really thought about any of these men in decades. Sometimes we take their amazing accomplishments for granted once they become a normal part of our lives.
Three amazing individuals. Three amazing innovators that spent their entire lives focused on a singular purpose – airplanes and automobiles.
But we no longer celebrate the ones that dedicated their lives to a singular purpose. Those that continued to iterate and improve on their enormous accomplishments. Too often we celebrate the “Renaissance Men (and Women)” that dabble in many pursuits.
I’m not sure what happened:
- Is it that the Microsoft “monopoly” case has people afraid of having too much market share?
- Do we morally fear that the prospect of “Do No Evil” isn’t possible if you achieve the successes of Google?
- Is it that market dominance is a fading concept, with the barrier to entry for new competition being so low, that people believe they need a portfolio of ideas to iterate upon in parallel?
- Is it that we’ve become such a distracted society that boredom and ego need to be feed at all times?
It’s not as if the world lacks for big problems to be solved or re-invented. We have global problems of food, water, energy, and literacy. Continued »
Last week, Amazon finally broke out the revenues (and expenses) of their Amazon Web Services (AWS) division. As many people expected, it’s 2014 revenues were in the $5-6B range, showing solid profitability. So what does this all mean?
From purely a contribution perspective, AWS is obviously a critical aspect of the overall Amazon business. While it may be less than 5% of overall revenue, it’s much more profitable than other business segments. And it can be the foundation for many other aspects of Amazon’s business – video, phone, tablets, FireTV, etc.
But to me, there are two aspects of their revenue announcements that are most interesting. Continued »
This past week, VMware had a launch of a new area of focus called “Cloud-Native Apps“. For the most part, it was focused on how VMware plans to directly address the use of containers (in multiple formats) within their broader stack and strategy. The announcement highlighted two new projects (Photon and Lightwave), which are being open sourced. It was an important launch for VMware because there are growing levels of interest around containers from both the market and VCs. Meetups with container-centric topics (or DevOps) are growing in popularity. Companies such as Docker, CoreOS, Mesosphere, Hashicorp and Kismatic are all expanding their offerings in ways that could one day compete with VMware in the data center. This is in addition to all of the PaaS platforms (eg. Cloud Foundry, OpenShift, Route 66, etc.) expanding their underlying support for containers and container management frameworks (eg. Lattice). Even Microsoft is getting into the container game in a serious way.
While it’s still very early days in this space for VMware, I had a few questions following the launch:
1 – How far does the Vision/Strategy extend?
It’s understandable that VMware has an “embrace and extend” strategy, as incumbents always need to find the balance between extending existing products/revenue and expanding into new areas. This approach is aligned to more of the “Gartner Bi-Modal IT” view of the future of IT, where the older and newer technologies are running in parallel but managed by a centralized group. This is different from the “Pioneers, Settlers and Town Planners” approach, which highlights how the future looking groups will break free from the exist model and blaze new paths.
So how far will VMware extend this strategy to develop more elements of a container-centric architecture vs. integrating with commonly used elements in the marketplace today? Will they eventually decouple some of these new elements from the legacy elements (eg, ESX VMs), or does that remain a constant long-term?
2 – How far does the Open Source support extend?
It’s great to see that VMware is setting up repos on GitHub and actively seeking contributions from the community (or will be soon). But how far will the open source projects extend? If Project Photon integrates into ESX, will VMware ever offer an open source version of ESX? This was something Adrian Cockcroft mentioned to us on the podcast, and VMware had Adrian speaking at their launch (starts at 11m45s). Continued »
Words and labels and tags in our industry mean something – at least for a while – and then marketing organizations tend to get involved and use words and labels and tags to best align to their specific agenda. For example, things like “webscale” or “cloud native apps” were strongly associated with the largest web companies (Google, Amazon, Twitter, Facebook, etc.). But over time, those terms got usurped by other groups in an effort to link their technologies to hot trends in the broader markets.
Another one that seems to be shifting is PaaS, or Platform as a Service. It’s sort of a funny acronym to say out loud, and people are starting to wonder about it’s future. But we’re not an industry that likes to stand still, so let’s move things around a little bit. Maybe PaaS is the wrong term, and it really should be “Platform”, since everything in IT should eventually be consumed as a service.
But not everyone believes that a Platform (or PaaS) should be an entirely structured model. There is lots of VC money being pumped into less structured models for delivering a platform, such as Mesosphere, CoreOS, Docker, Hashicorp, Kismatic, Cloud66, Apache Brooklyn (project) and Engine Yard acquiring OpDemand. Continued »
A few weeks back, a friend of mine asked me to help him create some live demos for a big event that his company had coming up. As with any demo, we spent some time focused on the target audience, what we expected of their knowledge background, and then the actual story that we wanted to tell. Then making the technology actually work was the last piece of the puzzle.
In this case, he wanted to showcase some next-generation technology, which was targeted at a “DevOps-centric” audience. As we built out the storyboard, we walked through the tasks he wanted to be shown and how they would be displayed. What struck me as odd was how often he wanted to show each layer within his demo (infrastructure, management, apps) and how many times he wanted to showcase a GUI. The audience he was going after would typically never use those tools, instead focusing on either CLIs or more likely APIs to integrate between the layers. It was becoming a demo of functionality that a customer would never use in real-life, but it looked pretty on stage and a big display. I tried to get him thinking like this, like his target DevOps audience would think: