Welcome!

@DevOpsSummit Authors: Liz McMillan, Dalibor Siroky, Pat Romanski, Elizabeth White, Stackify Blog

Blog Feed Post

Things I heard (and said) at #DevopsSummit

#devops #cloud #sdn      

It was a long and full day for me at Devops Summit. I could fill a week or more with blogs on ideas I both agreed - and of course, disagreed - with from sessions and panels.

But for now, here's a digestible selection. 

Ephemeral Infrastructure

From John Willis (@botchagalupe) session on networking and devops (which is something you'll be hearing more and more about, even if we are calling it something else, like maybe SDN or a part of the more overarching SDDC or even <gasp> cloud):  "servers became ephemeral infrastructure"

This is the descriptor I've been looking for, "ephemeral infrastructure." Whether it's servers or switches, the use of the term "virtual" implies virtualization, a la Hyper-V or VMware. And maybe for servers that's okay, though as we move toward container-based architectures (a la Docker) and into the network with its virtualized (but not virtual machine) form of multi-tenancy, there needed to be something to call it that distinguished it from physical infrastructure without conjuring up images of virtual machines (sorry, pun not intended). John nails it, I think, with the term "ephemeral infrastructure."

The Silos that Lie Beneath the Silos

Problem of #devops is you can't break down IT silos until you first break out of systems silos.

This was my simple observation and I touched on it in my session: infrastructure services aren't islands, they're part of a larger process and there exist dependencies and relationships between them that need to be bridged before we start worrying about bridging IT silos. That latter statement was one I heard multiple times in many different devops sessions said many different ways, though the best was definitely during a presentation by Jeff Sussna (@jeffsussna) discussing the need for empathy in moving forward with successful devops initiatives.

The fact is that we talk about Devops as cultural change and about bridging gaps between dev and ops (two of IT's four silos) but until we can break out of the systems silos that operations has built we're not going to get very far in practical terms. We need to recognize that just as applications have interdependencies and can impact each other in terms of scale, stability and performance, so too can the systems and infrastructure upon which those applications are deployed. And we need to recognize and manage those dependencies as a first step toward bridging other, more significant, gaps between IT groups.

Continuous is the new Cloud

If I had a dollar for every time I heard the phrase "Continuous <delivery, integration, deployment, improvement, <insert IT-related thing here>>" today I'd be flying home first class, let me tell you.

Within devops itself seems to be a variety of sub-categories, if you will, that bring the focus of devops onto a specific IT concern, like deployment, integration and delivery. There are a whole lot of them right now, and the formula seems to be to tack "continuous" onto the front of a traditional IT concern and then it becomes devops.

It's the new cloud, because many of these continuous "things" are not so much emulating cloud, but attempting to achieve the same goals - seamless application deployment through abstraction of infrastructure that enables operationalization. And because it's likely to experience the same hype cycle as cloud, watch out for continuous washing.

SDN and Devops

John Willis did a session on essentially SDN and how its operational aspects are related to devops. While I'm not in agreement with his view on limiting SDN to OpenFlow, the truth is that SDN is still in its nascent phase and it is in fact evolving toward a more devops-oriented approach to operationalizing the network. In that respect, John hit on what's key: network provisioning and management must evolve along with operations if it's going to meet the challenges ahead.

While most enterprises may think they don't need webscale infrastructure and networks, if they're going to take advantage of the Internet of Things, they will. The explosion of applications and services that go along with "things" is going to require a lot more scale and stability in the network, and a devops-like approach is one of the ways in which IT can realize both.

Read the original blog entry...

More Stories By Lori MacVittie

Lori MacVittie is responsible for education and evangelism of application services available across F5’s entire product suite. Her role includes authorship of technical materials and participation in a number of community-based forums and industry standards organizations, among other efforts. MacVittie has extensive programming experience as an application architect, as well as network and systems development and administration expertise. Prior to joining F5, MacVittie was an award-winning Senior Technology Editor at Network Computing Magazine, where she conducted product research and evaluation focused on integration with application and network architectures, and authored articles on a variety of topics aimed at IT professionals. Her most recent area of focus included SOA-related products and architectures. She holds a B.S. in Information and Computing Science from the University of Wisconsin at Green Bay, and an M.S. in Computer Science from Nova Southeastern University.

@DevOpsSummit Stories
As Marc Andreessen says software is eating the world. Everything is rapidly moving toward being software-defined – from our phones and cars through our washing machines to the datacenter. However, there are larger challenges when implementing software defined on a larger scale - when building software defined infrastructure. In his session at 16th Cloud Expo, Boyan Ivanov, CEO of StorPool, provided some practical insights on what, how and why when implementing "software-defined" in the datacenter.
ChatOps is an emerging topic that has led to the wide availability of integrations between group chat and various other tools/platforms. Currently, HipChat is an extremely powerful collaboration platform due to the various ChatOps integrations that are available. However, DevOps automation can involve orchestration and complex workflows. In his session at @DevOpsSummit at 20th Cloud Expo, Himanshu Chhetri, CTO at Addteq, will cover practical examples and use cases such as self-provisioning infrastructure/applications, self-remediation workflows, integrating monitoring and complimenting integrations between Atlassian tools and other top tools in the industry.
"Storpool does only block-level storage so we do one thing extremely well. The growth in data is what drives the move to software-defined technologies in general and software-defined storage," explained Boyan Ivanov, CEO and co-founder at StorPool, in this SYS-CON.tv interview at 16th Cloud Expo, held June 9-11, 2015, at the Javits Center in New York City.
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and cost-effective resources on AWS, coupled with the ability to deliver a minimum set of functionalities that cover the majority of needs – without configuration complexity.
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, which can process our conversational commands and orchestrate the outcomes we request across our personal and professional realm of connected devices.