>> Announcer: Live from the Computer History Museum, in Mountain View, California, it's the Cube. Covering DevNet Create 2018, brought to you by Cisco. >> Hey, welcome back everyone, this is the Cube's live coverage here in Mountain View, Califonia, for Cisco's DevNet Create. It's their cloud native developer ecosystem. A new initiative, only a year and a half old, great, cloud native dev ops oriented. I'm John Furrier, your cost with my co-host Lauren Cooney, our next guest is Damon Edwards, Chief Product Officer of Rundeck. Welcome to the Cube, good to see you again. >> Yeah good to see you again as well. >> So, you were just on stage giving a talk. >> I was. >> About ops, dev ops. >> I was bumming people out, that's what I was doing, so all of the Cisco early stuff was about new products, new toys, new awesome stuff, and then my talk was about how silos and tickets ruin everything. Right that, we've got all these great advances on the dev side of the house and delivery side of the house and the new technologies we've got, and everything's high flying and going to be perfect, until it all hits operations and things tend to go wrong. So I walked through a bunch of names we changed to hide the not-so-innocent, we went through some incidents and tales of woe and how the disconnects, and basically the siloed way of working, number one, group like with like in operations, very siloed. But also, number two, that we run our lives through these ticket-driven request queues. Right and request queues or queues in general, if you look on the product side, and then the physics of the queuing, the queuing theory behind it, queues are economically very expensive things. You know, they add a lot of delays, they create a lot of bottlenecks. I ask you to do something, I write it down, you take it off the queue, you know, a week later, the context is all different, right? So you have all kinds of bottlenecks, all kinds of quality problems, all kinds of delays, and it's an expensive way to work. Yet that has become the defacto way that we run our lives. And studies and tickets for what they're good at, which is handling problems, we use tickets as the general work permission system for the entire operations organization, and it's no surprise that silos and ticket-driven request queues, that we get what we get. And so the talk was about how to say, well how can we stop using tickets as the primary way of doing things? How do we look at the organization and remove the need for hand-offs between the silos, and then replace, where we can't get rid of the hand-offs, with self-service, right? Pull-based self-service interfaces where people can get what they need to get done, do those operational tasks themselves, and then move on >> Lauren: Great. >> That's what it's all about. >> Tell us a little bit about what your company does and how you're solving this problem, 'cause it's definitely a problem that's out there right now, and people aren't talking about it a whole lot because it's kind of the ugly underbelly of development ops. You know, they're trying to solve it, but they don't really want to talk about it. >> It's less sexy because you get a promotion for delivering the next big project, right? Saying you fix how operations work, it generally doesn't- you know the board of directors doesn't know your name. So that's kind of problem number one. But how Rundeck factors into this is that we make tools for SREs and systems administrators to, number one, organize all their scripts and tools, connect all their scripts and tools, the platforms they currently have across those silos, create standard operating procedures, and then, probably most importantly use the access control features to start to give access to people who are traditionally outside of the operational boundaries. Let developers participate in operations. Let QA participate in operations. Let business analysts participate in operations. All those requests they normally have of operations, create those services, let them do them. By doing that, you're creating more capacity in operations to focus on issues you really need to be solved, and you're making everyone else happy because you're staying out of their way. They can move faster, have fast feedback, higher quality, all of that stuff. >> You know we've done a lot of crowd chats and we had the questions come up, Is it the culture, or is it the tooling, or is it the people? Thinking all of the above, culture, everyone goes to the (mumbles), yeah the culture's going to be there. You guys are doing tooling. Can you talk about some of the things that you've seen that works. How does someone go, "Hey, first it's self-awareness, "we got to change this." If someone's into that mindset, I want to move to the new model, to be more agile, to actually streamline those silos and that ticket system. What tool do they need to use? What are you guys providing? Where is the steps? What's the sequence of tooling and adoption, and picks and shovels. >> Number one, use what you have, right? So this idea that, okay we're going to solve this problem, we're going to teach everybody to use this one tool, so everyone's going to learn this DSL or this language, it just never works. I mean, you know, three years ago it was one tool, we all know the name. Couple of years ago is was another tool, we all know the name, you know, these configuration management tools. Now we're on to the new container world, I don't know if we need that or not. Everyone wants to do what they need to do, so let them do what they need to do. It's a very lean idea. Focus on how to connect those things. Focus on how to orchestrate and organize what you've got already. And then from there, focus on, you know, how do we two things? Limit those hand-offs, so that kind of is more of an organizational issue. And number two, all those hand-off points, Anything I need something from you John, you know, or you Lauren, I don't want to have to say, "do this for me, and you do this for me." I'm going to wait and you've got five other things you're working on. You should create services that I can pull from. I need something from you, I need something you normally do. Hit an automated service, sort of like, don't do the old Savist managed service way of doing things. Do it the Amazon way, right, which is I can hit an API and get what I want when I want it. And most importantly, it's not just a one way button I can push. But I can actually create those buttons myself. So I can give the thing that I need to do, you can look at it and say, yeah that's going to work, give me back permission to go and run it. Everybody's happy, you guys get more of the scenario, get more capacity and I get what I want without having- >> So is microservices going to impact operations in a way? Cause then what you're getting at is more of a microservices, more of the primitives are going to be in the ops side. So there's a development mindset anyway. Is that standard dev ops now is ops? >> Well you need to handle the operational concerns as early in the life-cycle as possible. Meaning developers have to build from- it's kind of like in the car world, you build a car for manufactureability. You have to build the services for operability, and so that's number one. And with the new microservices decoupled world, you have to move to this model of operations because the old model that did work balances across these silos, it just doesn't work in this decoupled world. It makes everything kind of grind back to a lumpen mass of who-knows-what. So if you want to let the organization decouple, you have to be able to decouple your operations to match. >> So how long is it taking for customers to realize the value of your solutions that you bring to the table? And how much time is it saving them? >> Yeah, I mean, for Rundeck specifically, because it doesn't force you to learn new languages, you can start with what you've got today. So literally it takes days, right? Start plugging in things that you have. You can set up the access control. You can set up the options interface, and next thing you know, I've got this self-service interface and I can turn around and let somebody use it. So, you know, Rundeck doesn't do the culture and the organization change for you. This becomes a tool that greases that, makes it a lot easier to get that. >> What specifically in the tool that works for customers that's resonating in your tool? What's the big impact when people engage with you guys? When do they know when to bring you in for the tool? Let's just say that the gurus can... hey, here's the culture, you know, you do some yoga, whatever you got to do culture-wise, make that happen. You come in, what do you do? >> Sure, so for us, we're kind of more the bottom-up, right? It's usually a team that says, "hey we're getting overrun with these requests." Or it's a team that's saying, we've got to get like- it could be as simple as our restarts are a mess. There's too many ways to do things across all these tools. And then it's, hey, these people keep bugging us to do this. Or, that team keeps bugging us to refresh this environment. Or, this team, we need to give them access to something that goes wrong in production, to run some health checks and see what's happening. Really, those kind of operational, support-type use cases. It's generally at the team-level, be brought in to solve these different problems. And then where, really, the gas gets poured on, is when the upper management is following all the dev ops and SREs conversations and realize that things need to change, then they usually see Rundeck as, ooh, we can use that, right? That's going to help us unlock things, and let's do more of that, and it spreads from team to team. >> So you're really not trying to come in and boil the ocean over. You come in on a very specific entry point, and then get momentum and scales. >> Yeah, we get organizations that aren't touching their culture at all. It's literally just, we're doing things the old, classic, off-shore, application operations call center model, and we're just going to get better at that, and use Rundeck to create more capacity, standardize things, bring some more people into this process, and that's it. And they're very successful as that. And then, the really exciting ones is when the coder gets caught up into larger organizational transformation. >> You mentioned SRE, site reliability engineers. Google uses that term. So I've got to ask you, we talked before we came on camera about "no ops", having a no ops culture because dev ops is more developer. And we were kind of pooh-poohing that, and you were kind of more aggressive. I won't say what you said to me because it's a children's show here. >> Damon: Yes I'm sure a lot of children watch the Cube. (laughs) >> The ops guys, no pun intended. So, Google is really hardcore on this. Do you have an opinion on this? Ops, no ops, dev ops, the role of ops? >> I mean it's ridiculous, ops happens, right? I mean, ops everyday. John Alspot was a formerly dexy, and now he's kind of a researcher, does this thing at conferences where he says, "Everybody raise your hand, if I locked everybody out, "so hands off the keyboard, you can't do anything. "How many of your companies "would still be in business tomorrow? "Or in a week? Or in a month? Or in a year?" And people's hands kind of going... You know, a day and a week, you know? And the reality is operations happens, right? These are complex, moving systems, interacting with complex things in the world, and you have to be able to operate them. So, you know, the original no ops idea was, oh I don't want to have a separate thing called operations, I want to distribute operations where it makes sense, have engineers everywhere. Google has an interesting view, which is, no we have a distinct organization. But they call it SRE and they use more software engineering discipline to do. We have a whole methodology behind it. But they're very much proving you can still have a separate engineering and operations organization and do it right. And then there's folks like Netflix and Amazon who are more like, no no we're going to distribute it within these cross-functional teams and organizations. >> And they're still ops no matter how you slice them. But here's the thing, my observation... People get confused automation and operations. Just because you're automating something doesn't mean it goes away. >> Damon: Right. >> You might automate some tasks and things- >> Damon: Or it could make it worse. >> Yeah so talk about that pull-push, that tug between that. Because it's the tension that's positive, because you want to automate things that you're doing multiple repetitive tasks on. But that eliminates some tasks but you're still operating. Talk about that dynamic. >> Well, there's certain things computers are very good at. Repetitive, no-end tasks, computers are great at. But it takes human creativity, or sort of the super complex connecting-the-dots. Humans are good at that. So how do you automate as much of the things as possible that the computers are good at? And that gives you the time and the cognitive bandwidth to focus on the creative. That's creative in building things, creative in "oh crap, we've got to solve this". Right, and the tool should be there to support that. The idea that you can automate all of that away, it just is not- >> Give me an example, if you look four or five years and think about how we're moving fast with the evolution with the cloud and everything else happening. (mumbles) IOG, AO, all this great stuff's happening. You got blog chain, you got cryptocurrent, a lot of things going on. That is super positive, it also could be detrimental. Where does the human piece come in? Where will always be the pieces where human creativity, human intuition, human judgment... Where is it always going to shine? What specific things do you see never going away? >> It's what you said, the intuition and the judgment, right? In the day-to-day work activities, you need to use that intuition and judgment to get things done, to see the different signals, and understand what they mean, to create new solutions on how to solve these new challenges. You know, that is where the human beings are needed. So, it's both in the delivery time, and in the idea of operations. If you think of an airplane, there's still pilots. You think of a nuclear power plant, there's still operators. Tons of automation, tons of alarms, tons of things to assist them, but it still comes down to the things that human brains are good at. So there's always a role- >> So categorically, how you see security, latency is one, multi-cloud, workload movement, is the areas that you start to see the categorical areas that are never going to go away. >> Yeah, and at a certain point you're going to have things where the platforms get better, and you kind of climb the stack, and more things that only human beings can do in the past you can start to automate things. Like deployment, deployment used to be a human task, now we start to standardize things, have standard parts, have virtualization, now the cloud, now the cloud native technology. That allows you to... Okay, you've standardized things, you've build the right tooling, now you can focus the humans on more important problems, and move at a higher velocity and better quality. >> Lauren: Great. >> Great stuff. Okay, what's going on for you? What are you up to now these days? What events are you going to? What are you working on? what are the cool things you're excited about right now? >> What am I excited about? The dev ops enterprise summit, I've been involved with that for a number of years, that is the best collection of enterprise, big corporation thinking around the whole sphere of transformation. >> John: And it's growing too. >> Yeah, it's growing. There's one now in London, one now going to be in Las Vegas, you know, 1000 to 2000 people. SREcon. SRE is a... It's like a specialized implementation of all the dev ops thinking. I think that's another great place to be. And then devopsdays, Velocity, all the traditional conferences. >> Great community. You've got to say being involved in the dev ops from day one, watching the pioneers, a few with arrows in their back, but now have gone mainstream, super exciting. I think Cooper Netties brings that mainstream, just highlights everything. >> Yeah, that's that platform I was talking about. A lot of the concerns that human beings had to struggle with on a day-to-day basis are now being put into the orchestration and scheduling and the containerization of things. >> Damon, great work. Congratulations on all the work you've done. You've been a real contribution to the industry. >> Thank you. >> Good luck with the business. Thanks for coming on the Cube. >> Yeah, thanks for having me. >> Alright, this Cube live coverage here in Mountain View for Cisco's DEVNET Create. Really the Cisco's foray into cloud native. Really getting at that dev ops culture, solving big problems, programming the networks. Cisco's bringing that together with their communities. Of course, Cube's here covering it. More live coverage after this short break. (electronic music)