Welcome!

@DevOpsSummit Authors: Liz McMillan, Yeshim Deniz, Zakia Bouachraoui, Pat Romanski, Elizabeth White

Related Topics: @DevOpsSummit, Microservices Expo, Linux Containers, Containers Expo Blog

@DevOpsSummit: Article

DevOps Express | @DevOpsSummit #APM #DevOps #ContinuousDelivery

'Being able to take needless work out of the system is more important than being able to put more work into the system'

"Being able to take needless work out of the system is more important than being able to put more work into the system." This is one of my favorite quotes from Gene Kim's book, The Phoenix Project, and it plays directly into why we're announcing the DevOps Express initiative today.

Tracing the Steps. For years now, I have witnessed needless work being performed across the DevOps industry.  No, not within our clients DevOps and continuous delivery practices.  I have seen it in the buyer's journey – from the folks taking their first baby steps into DevOps to those organizations trying to master their craft.

For example, it is easy to trace the inefficient steps of the community at any DevOps event you go to. People jump from exhibitor booth to booth trying to assemble a tale of how multiple technology vendors can be coupled together into a tool chain that will integrate builds, monitor quality, enhance security, accelerate deployments, and clean their dishes.  Every booth and every conversation at the events lives in a silo – only to be assembled by the brave who head back to their offices full of conviction that something better lies ahead.

101789575_thumbnail.jpg

Decidedly Different. At Sonatype, we took a decidedly different path.  While our Sonatype Nexus solutions enjoy over 100,000 active installations, we understand that our solutions don't operate stand-alone.  Our solutions are always integrated with others across the DevOps toolchain: Jenkins, Puppet, Chef, Docker, Sonar, JIRA, RunDeck, etc.  The DevOps community did not just want to hear how cool our Nexus products were, they wanted to know how others integrated, ran and supported all of these products into their environments.

In 2015, we introduced our first of now three DevOps Reference Architecture sets.  Combined, those sets now have over 118,000 views on SlideShare.  These pictures described real-world deployments from IBM, PayPal, Barclays, Adobe, eBay, Cisco and over 50 other organizations.  They showed people how to get started and help validate choices they would like to make (or may have already made).  In short, these pictures helped people.

Screen_Shot_2016-09-02_at_2.47.45_PM.png

A Needed Discussion. We wanted to move beyond those pictures to discussions.  We then set up a series of webinars with our friends at CloudBees, SonarSource, Codecentric, and even Dave Farley (co-author of Continuous Delivery), to discuss continuous delivery practices, challenges, and culture.  Well over 5,000 people attended the webinars.  It was clear that the community was craving information and we knew more had to be done.

Germinating Innovation. Next came the idea for DevOps Express.  We sat down with our friends at CloudBees and imagined extending our collaborative efforts to a number of other vendors.  We were tired of seeing buyers fend for themselves as they evaluated, purchased, integrated, and supported a collection of DevOps native solutions.  As DevOps minded professionals, all of this behavior looked like "needless work" in the system.

To take out the needless work, we needed to bring others in.  We set out over this past summer inviting 12 other battle-tested, DevOps-native solutions into the DevOps Express initiative.  The goal: ease the buyer's journey from beginning to better.

Taking Aim. Our aim is to better integrate our solutions.  Our aim is to ease the buying experience.  Our aim is to give people a roadmap for their journey.  And our aim is to support them as much as we can along the way.  While there is no silver bullet to offering "DevOps in a Box", as technology vendors, we knew there was a better way.

Beyond the reference architectures that we have now contributed to the DevOps Express initiative, we are also providing a set of 12 integrations to improve the user experience for our customers in the community.  These include:

Don't be confused, the DevOps Express journey is not just about the elements of a tool chain.  Our vision extends to the consulting, integration, and transformation practitioners.  It also extends to the locations where these toolchains reside -- whether on-premises or in the cloud.

We are just as passionate about removing needless work from the system as you are, and we hope you will join us on this journey.  Stay tuned, there is much, much more to come.

To learn more about DevOps Express, please visit www.DevOps-Express.com.

More Stories By Derek Weeks

In 2015, Derek Weeks led the largest and most comprehensive analysis of software supply chain practices to date across 160,000 development organizations. He is a huge advocate of applying proven supply chain management principles into DevOps practices to improve efficiencies, reduce costs, and sustain long-lasting competitive advantages.

As a 20+ year veteran of the software industry, he has advised leading businesses on IT performance improvement practices covering continuous delivery, business process management, systems and network operations, service management, capacity planning and storage management. As the VP and DevOps Advocate for Sonatype, he is passionate about changing the way people think about software supply chains and improving public safety through improved software integrity. Follow him here @weekstweets, find me here www.linkedin.com/in/derekeweeks, and read me here http://blog.sonatype.com/author/weeks/.

@DevOpsSummit Stories
With more than 30 Kubernetes solutions in the marketplace, it's tempting to think Kubernetes and the vendor ecosystem has solved the problem of operationalizing containers at scale or of automatically managing the elasticity of the underlying infrastructure that these solutions need to be truly scalable. Far from it. There are at least six major pain points that companies experience when they try to deploy and run Kubernetes in their complex environments. In this presentation, the speaker will detail these pain points and explain how cloud can address them.
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations might slip up with the wrong focus, how to manage change and risk in all three areas, what is possible and what is not, where to start, and especially how new structures, processes, and technologies can help drive a new DevOps culture.
When building large, cloud-based applications that operate at a high scale, it's important to maintain a high availability and resilience to failures. In order to do that, you must be tolerant of failures, even in light of failures in other areas of your application. "Fly two mistakes high" is an old adage in the radio control airplane hobby. It means, fly high enough so that if you make a mistake, you can continue flying with room to still make mistakes. In his session at 18th Cloud Expo, Lee Atchison, Principal Cloud Architect and Advocate at New Relic, discussed how this same philosophy can be applied to highly scaled applications, and can dramatically increase your resilience to failure.
As Cybric's Chief Technology Officer, Mike D. Kail is responsible for the strategic vision and technical direction of the platform. Prior to founding Cybric, Mike was Yahoo's CIO and SVP of Infrastructure, where he led the IT and Data Center functions for the company. He has more than 24 years of IT Operations experience with a focus on highly-scalable architectures.
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regulatory scrutiny and increasing consumer lack of trust in technology in general.