Over the past two weeks, I’ve been to two conferences that are run by an open source community. The first was the CloudFoundry Summit in Boston followed by KubeCon+CloudNativeCon Europe 2018 in Copenhagen. At both, I found passionate and vibrant communities of sysops, developers, and companies. For those unfamiliar with CloudFoundry and Kubernetes, they are open source technologies that abstract software infrastructure to make it easier for developers and sysops to deliver applications more quickly.

Both serve similar communities and have a generally similar goal. There is some overlap – CloudFoundry has its own container and container orchestration capability – but the two technologies are mostly complementary. It is possible, for example, to deploy CloudFoundry as a Kubernetes cluster and use CloudFoundry to deploy Kubernetes. I met with IT professionals that are doing one or both of these. The same is true for OpenStack and CloudFoundry (and Kubernetes for that matter). OpenStack is used to abstract the hardware infrastructure, in effect creating a cloud within a data center. It is a tool used by sysops to provision hardware as easily scalable resources, creating a private cloud. So, like CloudFoundry does for software, OpenStack helps to manage resources more easily so that a sysop doesn’t have to do everything by hand. CloudFoundry and OpenStack are clearly complementary. Sysops use OpenStack to create resources in the form of a private cloud; developers then use CloudFoundry to pull together private and public cloud resources into a platform they deploy applications to. Kubernetes can be found in any of those places.

Fake News, Fake Controversies

Why then, is there this constant tension between the communities and adopters of these technologies? It’s as if carpenters had hammer people and saw people who argued over which was better. According to my carpenter friends, they don’t. The foundations and vendors avoid this type of talk, but these kinds of discussions are happening at the practitioner and contributor level all the time. During KubeCon+CloudnativeCon Europe 2018, I saw a number of tweets that, in essence, said: “Why is Cloud Foundry Executive Director Abby Kearns speaking at KubeCon?” They questioned what one had to do with the other. Why not question what peanut butter and jelly have to do with each other?

Since each of these open source projects (and the products based on them) have a different place in a modern hybrid cloud infrastructure, how is it that very smart people are being so short-sighted? Clearly, there is a problem in these communities that limit their point of view. One theory lies in what it takes to proselytize these projects within an organization and wider community. To put it succinctly, to get corporate buy-in and widespread adoption, community members have to become strongly focused on their specific project. So focused, that some put on blinders and can no longer see the big picture. In fact, in order to sell the world on something that seems radical at first, you trade real vision for tunnel vision.

People become invested in what they do and that’s good for these type of community developed technologies. They require a commitment to a project that can’t be driven by any one company and may not pan out. It turns toxic when the separate communities become so ensconced in their own little corner of the tech world that they can’t see the big picture. The very nature of these projects defies an overriding authority that demands the everyone get along, so they don’t always.

It’s time to get some perspective, to see the big picture. We have an embarrassment of technology abstraction riches. It’s time to look up from individual projects and see the wider world. Your organizations will love you for it.

Standing in the main expo hall of KubeCon+CloudNativeCon Europe 2018 in Copenhagen, the richness of the Kubernetes ecosystem is readily apparent. There are booths everywhere, addressing all the infrastructure needs for an enterprise cluster. There are meetings everywhere for the open source projects that make up the Kubernetes and Cloud Native base of technology. The keynotes are full. What was a 500-person conference in 2012 is now, 6 years later, a 4300-person conference even though it’s not in one of the hotbeds of American technology such as San Francisco or New York City.

What is amazing is how much Kubernetes has grown in such a short amount of time. It was only a little more than a year ago that Docker released its Kubernetes competitor called Swarm. While Swarm still exists, Docker also supports, and arguably is betting the future, on Kubernetes.
Kubernetes came out of Google, but that doesn’t really explain why it expanded like the early universe after the Big Bang. Google is not the market leader in the cloud space – it’s one of the top vendors but not the top vendor – and wouldn’t have provided enough market pull to drive the Kubernetes engine this hot. Google is also not a major enterprise infrastructure software vendor the way IBM, Microsoft, or even Red Hat and Canonical are.

Kubernetes benefited from the first mover effect. They were early into the market with container orchestration, were fully open source, and had a large amount of testing in Google’s own environment. Docker Swarm, on the other hand, was too closely tied to Docker, the company, to appease the open source gods.

Now, Kubernetes finds itself like a new college graduate. It’s all grown up but needs to prepare for the real world. The basics are all in place and it’s mature but there is an enormous amount of refinement and holes that need to be filled in for it to be a common part of every enterprise software infrastructure. KubeCon+CloudNativeCon shows that this is well underway. The focus now is on security, monitoring, network improvement, and scalability. There doesn’t seem to be a lot of concern about stability or basic functionality.

Kubernetes has eaten the container world and didn’t get indigestion. That’s rare and wonderful.

Industry: Software Asset Management

Key Stakeholders: CIO, CFO, Chief Digital Officer, Chief Technology Officer, Chief Mobility Officer, IT Asset Directors and Managers, Procurement Directors and Managers, Accounting Directors and Managers
Why It Matters: Software-as-a-Service (SaaS) is now a strategic IT component. As enterprise SaaS doubles in market size over the next three years, this complex spend category will continue to expand beyond the ability to manually manage it
Top Takeaways: With this acquisition, ServiceNow will have a cutting-edge & converged Software Asset Management solution for both SaaS and on-premises applications in 2019. Enterprise organizations managing over $25,000 a month should consider an enterprise SaaS vendor management solution to optimize licenses, de-duplicate vendor categories, and gain enterprise-grade governance.

With ServiceNow’s acquisition of VendorHawk, the era of SaaS Vendor Management is emergent.

ServiceNow Acquires VendorHawk

On April 25th, 2018, ServiceNow announced its acquisition of SaaS Vendor Management solution VendorHawk in an all-cash transaction scheduled to close in April. This acquisition highlights the increasingly strategic role of SaaS from an IT service management perspective and validates the need for Software Asset Management solutions to support SaaS. In addition, this acquisition continues a string of acquisitions that ServiceNow has made over the past year including acquisitions of:

• Qlue, an artificial intelligence framework for customer service
• Telepathy, a design firm focused on massive adoption of applications
• SkyGiraffe, a no-code mobile app development platform used to make all ServiceNow applications mobile-friendly

The VendorHawk acquisition falls in line with these acquisitions in that VendorHawk will help enterprises to support the widespread adoption of SaaS.
Continue reading Market Milestone: ServiceNow Buys VendorHawk and SaaS Management Comes of Age

Key Stakeholders: Chief Learning Officers, Chief Human Resource Officers, Learning and Development Directors and Managers, Corporate Trainers, Content and Learning Product Managers

Key Takeaways: L&D vendors offer a vast array of innovative functionality and technology for their clients. Unfortunately, clients are overwhelmed by the breadth of offerings and desire guidance on what technology to use when, all in the interest of increasing adoption and the effectiveness of learning. An extensive body of learning science research exists that should be leveraged to provide clients with the much-needed guidance. This approach will reduce the existing adoption gap and improve the performance.
Continue reading The Adoption Gap in Learning & Development: How Learning Science Can Bridge the Divide

(Note: This blog is an excerpt from Tom Petrocelli’s current report: Infrastructure as Code: Managing Hybrid Infrastructure at Scale)

Key Stakeholders: CIO, Sysops, System Admins, Network Admins, Storage Admins, IT Operations Managers

Why It Matters: New software architectures continue to add complexity to it infrastructure management. At the same time, organizations expect IT to deploy applications faster. New tools are needed for IT operations to perform in this environment.

Top Takeaways: Infrastructure as Code, or IaC, offers a path to faster and less error prone management of new software infrastructure at enterprise scale. IaC abstracts the myriad of ways IT professionals interact with systems into a simple, plain text, code file.

Infrastructure as Code

Today, IT is continuing to virtualize infrastructure even more with container clusters. Containers often fulfill the same role as a server, even though they do not require an entire stack including an operating system. Like a server, they are a unit of computing that houses services that comprise an application. Unlike a server, containers often contain a single purpose service called a microservice. Microservices architectures lead to a large number of containers, within virtual servers, running on physical or cloud servers. For large enterprises, this new model expands the number of virtual, physical, and cloud devices under management, adding complexity to the infrastructure.

Managing tens of thousands of heterogeneous nodes, where only a few thousand, fairly homogeneous ones existed before, represents a massive challenge to IT. This is further compounded by the presence of (often more than one) cloud services alongside on-premises servers. To add to the challenge, new development methodologies have increased pace of modern software development which constantly alters the IT infrastructure.

To cope with this greatly enlarged management burden, IT managers and professionals are increasingly turning to Infrastructure as Code (IaC). IaC is part management technique and part toolset. The philosophy behind IaC is to write code that defines the desired state of the infrastructure. While this could be carried out using shell scripts or homegrown programs, increasingly IT practitioners are turning to purpose-built tools that allow for infrastructure to be defined as a program (i.e. code) and then executed by automation servers, often with the help of local commands and agents on the physical and virtual servers or service calls of cloud services.

Key Infrastructure as Code Functions and Challenges
While provisioning, configuration, and code deployment may be the most common functions of IaC, it is hardly limited to such a small set of capabilities. IaC can accomplish most of what sysops, network administrators, and other IT operations professionals have to do by hand, via shell scripts, or through management consoles through the following capabilities.

While there are some clear advantages to DevOps, there are also some issues with the approach. Some of the problems are technical but many are social or managerial. A mixture of IT silo politics and skill deficits may lead to a toxic DevOps team environment that no amount of technology can overcome. However, problems associated with IaC itself are relatively straightforward and can be managed with training, support, and planning. Some of the standout issues for IaC include:

Key IaC Vendors

There are a number of vendors offering products in the IaC space. While they all offer the basic functions of provisioning, updating, and configuration, many have a number of other features as well. No product offers the full list of these features, so it is important to choose a vendor based on the automation priorities of the organization.

*Participated in Amalgam’s research process

Conclusion

As enterprise IT infrastructure has evolved from a simple, single mainframe to the highly distributed, hybrid cloud, multi-cloud, microservices architecture, managing a datacenter has become terribly complex. Along the way, the tools available to sysops and admins have likewise evolved into entire management platforms, the so-called single pane of glass.

Key Stakeholders: CHRO, Chief Learning Officers, Talent Acquisition Directors and Managers, Learning & Development Directors, Training Managers, Corporate Education Managers, LMS Managers

On April 11th – 13th, Amalgam Insights attended Skillsoft Perspectives as both analysts Hyoun Park and W. Todd Maddox, Ph.D. looked at the latest advances in Skillsoft’s platforms, key narratives from Skillsoft’s customers and partners, and opportunities for pushing the future of corporate learning. Amalgam spoke with key executives and customers while attending keynote sessions and even presenting as well. Continue reading Skillsoft Perspectives 2018 – A Vision For The Future of Corporate Learning

On April 9th and 10th, Amalgam Insights attended the fifth Cloudera’s Industry Analyst and Influencer Conference (which I’ll self-servingly refer to as the Analyst Conference since I attended as an industry analyst) in Santa Monica. Cloudera sought to make the case that it was evolving beyond the market offerings that it is currently best known for as a Hadoop distribution and commercial data lake in becoming a machine learning and analytics platform. In doing so, Cloudera was extremely self-aware of its need to progress beyond the role of multi-petabyte storage at scale to a machine learning solution.

Continue reading Cloudera Analyst Conference Makes The Case for Analytic & AI Insights at Scale

From April 2-4, 2018, the Enterprise Technology Management Association (ETMA, previously known as TEMIA) met in Nashville. This meeting brought together over 40 vendor organizations focused on various aspects of technology management including network, telecom, mobility, software, cloud infrastructure, utilities, and the Internet of Things. ETMA’s members are mainly focused on telecom expense management, managed mobility services, and related technologies.

Continue reading The Enterprise Technology Management Association Focuses on Making Tech Affordable

As part of Amalgam Insights’ research process, we also keep track of the wide array of analysts, consultants, and thought leaders who are most relevant across our practice areas. Beyond the most well-known firms, such as the likes of Gartner, Forrester, and IDC, there are a wide array of bespoke and custom firms that conduct world-class work. To help provide context on how Amalgam Insights looks at our peers, partners, and competitors and to help technology buyers make better decisions, Amalgam profiles a firm or thought leader each Thursday to provide guidance on those who we think of as influential and innovative thought leaders.

This week, we profile SMB Group, a team of industry analysts focused on the technology adoption and management challenges in small and medium businesses.
Continue reading #ThoughtLeaderThursday – SMB Group

(Editor’s Note: Todd Maddox, Ph.D. has over 200 published articles, 10,000 citings, and $10 million in external research funding in his 25+ years in cognitive psychology. Maddox is available for interviews on this topic at info@amalgaminsights.com)

By now, I am sure you have heard about the incident at a Starbucks in Philadelphia, where two black men were arrested for waiting for a third man inside the store without purchasing any items. Starbucks CEO Kevin Johnson issued an immediate apology calling the arrests “reprehensible.” He’s gone further, meeting with the two men in person and apologizing, as well as saying that all U.S. Starbucks will be closed on May 29 for racial-bias education for its employees.
Continue reading Will Starbucks Make A $40 Million Training Mistake? The Psychology and Brain Science of Effective Racial Bias Prevention Training