>> Announcer: Live, from Vancouver, Canada it's the CUBE, covering OpenStack Summit North America 2018, brought to you by Red Hat, the Open Stack Foundation, and it's ecosystem partners. >> Welcome back, I'm Stu Miniman and my cohost John Troyer and you're watching the CUBE, the worldwide leader in tech coverage. Happy to welcome back to the program long time friend of the CUBE back from the earliest days, Randy Bias, Vice President with Juniper, Randy, great to see you. >> Absolutely, great to be back with you guys. >> All right, so Randy, we've been talking about, you know, community, and everything's going good and attendance might be down a little bit but how we fit in with containers and kubernetes, and everything, so we expect you to tear everything up for us and tell us the reality of what's happening in this community. >> I'll do my best (laughing). >> All right, so before we get to the kubernetic stuff, you're working on, we used to call it OpenContrail? Which you were involved in before Juniper acquired it, went through a rebranding recently, Tungsten, which I was looking up, came from the word heavy stone, give us the update from the networking side. >> Yeah, so the short history is that there was a company called Contrail, and they created a software defined networking controller, it was acquired by Juniper in 2012, 2013, and then that was open sourced, so Juniper for a long time was running with sort of two editions, Contrail which was the commercial offering, and OpenContrail which was the open source, and then shortly after I joined Juniper, identified that, you know, we really needed to go back to the drawing board on the way that we had organized the community, and transition it from being Juniper-led to community led, and so over the past year, I spearheaded that effort, and then that culminated in us announcing at the end of March at ONS that, you know, OpenContrail was now Tungsten Fabric. We renamed it, we moved it into the Linux foundation, under its governance, and now Juniper is one of many people of the community that have a seat at the table for the management, both from a business and technical perspective, and we're moving forward with a new reinvigorated community. >> Yeah, so networking sits at really the intersection of this multi-cloud world that we're living in. There's so many players trying to be there, you know Cisco, really moving to become more of a software company, when I interviewed their number two guy at their show, he's like, when you think of Cisco in the future, we're not even going to be a networking company, we'll be a software company. VMware, of course, pushed heavy through, then the Nicira acquisition, where does Tungsten fit, kind of compare and contrast for us, where it fits among some of these other offerings out there in the marketplace. >> Yeah, I mean, I think most enterprise vendors are in a similar transition from being a hardware to software companies. We're no different than any of the rest. I think we have a pretty significant advantage in that we have a lot of growth in the cloud sector, so a lot of the large public clouds are our customers and we're selling a tremendous amount of hardwaring to them, so I think we've got a lot longer runway. But, you know, we just recently hired CTO, Bikash Koley, out of Google, and we're starting to see some additional folks out of Google, like my new boss, Morgan, and what that's bringing with it is a very much a software first type perspective. So Bikash and Morgan really built everything for the Google network from the topper rack all the way out to the win and it's almost all software-based, disaggregated, hardware, software, opensource software running on top of white boxes, and so that kind of perspective is now really deep, start beginning to become embedded in Juniper. And at the head of that is Tungsten. So we see Tungsten Fabric as being sort of a tool that we use to create, you know, a global ubiquitous network fabric, that anybody can use anywhere, without talking to Juniper at all, without knowing that Juniper's part of Tungsten, and then as they grow up and they get to a point where they need multi-cloud, they need federation, or they need kind of day two enterprise operations, you know, we have a commercial version and a commercial distribution that they can use. >> Randy, we talked a little bit about OpenContrail and last year, at OpenStack Summit and moving it to a more of a community based governance model, and now that's happened with the Linux Foundation, can you talk a little bit about the role of opensource governance, and corporate governance, and then foundations, and just going forward, you know, what's an effective model for 2018 going forward, for a foundation-led project and maybe in the context of Tungsten Fabric, and how is that looking? >> Yeah, so again, OpenContrail's now Tungsten Fabrics, might be new for some of the viewers, lot of people still coming to terms with that. And so one of the things that we noticed is that, and when many people go and they say, hey, we want opensource first, the AT&T's of this world, part of what they're saying, one of the aspects of being opensource versus we want to be one of many around the table, we want to have a seat at the table, we want to have the option to contribute code back, and we want to feel like it's a group effort. And so that was a big factor, right? It was an opensource project, but it was largely the governance was carried by Juniper, all the testing infrastructure was Juniper, you know, all of the people who made architectural decisions were Juniper, all of the lead contributors were Juniper, and so, going to Linux Foundation was critical to us having a legal framework, for the trademarks, the code, the licenses, the contributor license agreements, are all owned and operated by the Linux Foundation and not by Juniper, so we basically have a trusted third party who can mediate all those things and create a structure, a governance small structure where Juniper has one seat at the table, and all the other community members do as well. So it was really key to getting, to moving to that model to increase people's interest in the project and to really go the next level. There just wasn't any way to do it without doing this. >> All right, so, Randy, let's talk about OpenStack. You were watching the keynote yesterday, you were, you know, in the Twitter stream, >> Randy: I don't usually watch keynotes, man. >> Stu: But you know this community, so-- >> I do know this community (laughing). >> Give us kind of the good, the bad, and the ugly from your standpoint as to, you know, where we've gone, you know, what's doing well, and what you're frustrated as heck that we still haven't fixed yet. >> Well, I mean, it's great that we have so much inroads amongst the carriers, it's great that, you know, that there's a segment that OpenStack has been able to land in. I mean, at some points when I was feeling particularly pessimistic on some days, I was like, oh man, this thing's never going to go anywhere, so that's great. On the other hand, you know, the promise that we had of sort of being the Linux operating center, operating system of the data center, and you know, really gaining inroads into private cloud and enterprise, that just hasn't materialized and I don't see a path to that. A lot of that has to do with history, I'm not sure how much of that I want to go into here, but I see those as being bright lights. I see the Ocata containers effort and sort of having this alternative structure that's more or less like the umbrella structure that I lobbied for while I was on the board. So for several years on the board, I said we need to really look more like the Apache Software Foundation, we need to look less like the Linux Operating System in terms of how we think about things. Not this big integrated monolithic release, you need more competition between projects and that just wasn't really embraced. And I think that that, in a way, that was one of several things that really kind of limited our ability to capture the market that we really wanted, which is the enterprise market. >> Yeah, well, I know, and one of those sticking points there that I've talked to you many times over the years about is how do I actually deploy this? You know, getting a base configuration and scaling this out, simplicity is tough, getting to those environments, you know, getting it up in two weeks, is good for some environments, but maybe not for others. >> Yeah, I mean I think there's sort of a spectrum, right? At one end of the spectrum, you say hey, I'm going to have a very opinionated approach like kubernetes does, and we're going to limit what we say we can do, you know, we're not all things to all people. And I think that opinionated approach, like the Linux operating system worked very, very well. And then other end of the spectrum is we've got no opinion like the Apache Software Foundation, and then it's up to vendors to go and cherry pick the pieces they want and turn that into some kind of commercial offering, whether it's Hortonworks, or Thi-dare or Du-per or whatever it is, the problem is that OpenStack wound up in the middle where it had the sort of integrated monolithic release cycle which it still does, which started to be all things to all people, and it was never as great as it could be, so it's like we got to support Hyper-V, we got to support VMware, and as the laundry list of all things we have to support grew longer, it became more and more difficult to have a compelling, easy to use, easy to scale offering that any enterprise could consume. >> Randy, a lot of talk this week about edge computing, with several different definitions, right? But it does strike me that, you know, there's a certain set of apps, that you write 'em and that they live fine in a big public cloud, and a big data center somewhere. But there's a lot of hardware that's going to be living out in the world, whether that's at the base of a radio tower, or in a wall, or in my shoe, that is going to be running hardware, and is going to be running something, and sometimes that something can be OpenStack, and we're seeing some examples of it, many examples of that already. Is that an area of growth for OpenStack? Is that an interesting part of how this fabric is going to expand? >> Well, I probably have a contrarian view here. So, I spent a bunch of time at Juniper, one of the things I worked on for a while was edge computing and we're still trying to decide what we want to do there and you know, kind of to the first point you made is everybody's edge is different, right? Is it on the mobile phone, is it back in the data center, the difference is that the real estate gets more expensive as you move out, right? And it's in terms of latency, and it's in terms of bandwidth and it's also in terms of cost of storage and compute. There's a move closer to the mobile device that becomes progressively more expensive, and so that's why a lot of people sort of look and say hey, wouldn't it be nice if we can get you out the closer lower latency and bandwidth and so on but as we looked at it, a lot of the different use cases it became really interesting in that, it wasn't clear if there was that much value between 5 milliseconds and 20 milliseconds, right? I mean, that's pretty, either one's pretty close, sure there's a lot of difference between 20 and a 100, but maybe not so much between 5 and 20. And so we kind of came to the conclusion that at least for right now, probably, the bulk of use cases are fine with 20 milliseconds, and what that means is that regional systems like AWS's Lambda at the Edge, they're in metro, those are probably good for most cases. I don't know that you need to be on the tower, I don't know that you need to be in the central office, so I think edge computing is still nascent, we don't know exactly what all those use cases are, but I think you might be able to service most of them from regional data centers, and then the question really becomes what does that stack need to be and if you have a regional data center that's got plenty of power, plenty of space, then it might be that OpenStack is a good solution, but if you're trying to scale down onto the tower, I got to have some doubts about whether OpenStack can really scale down that far. >> Randy, analytics is something we've been seeing, the networking people used for many years, at this show, starting to hear a lot of discussion about AI and ML, would love your view point as to what you're seeing in that space. >> You know I have some friends who started off in AI in very early days and he had a very pessimistic view. He said, you know this stuff comes and goes, but I'm actually very positive and optimistic about it because the way I look at this is there's a renaissance happening which is that, you know, now ML is really available to masses and you're seeing people do really interesting things like, we have a product called AppFormix, and what they do is they take ML and they apply it to operations and I love this because as an operations guy, you know, I used to have these problems in production where something would go out and the first thing I'd do, is I'm trying to do correlation and then root cause analysis, like, what was the actual failure? Like I can see the symptom on this end and now I have to get all the way back to what caused it, and the reality is that machine learning, AI techniques and protocols can do all the heavy lifting for operators very, very quickly and basically surface a problem for somebody to do the final analysis on. And so I do think that ML and AI apply to very specific vertical problems, it is just a place where we're going to see a tremendous amount of revolution in the next couple years. >> All right, and that hits right at really that intersection between kind of the developers and the operators there-- >> Absolutely. >> What are you seeing from an organizational standpoint, companies you're talking to these days, how are they doing adopting that change, dealing with that, you know, often schism or are they bringing those groups together? >> Well, I think you remember that like in the early days, I used bring my deck along and I would talk about assembly line IT versus the robotics spectrum all of IT and I would sort of make that sort of analogy to sort of the car manufacturing process, and I think what machine learning is really going to do is take us to that next level past that right? So we had the assembly line where we have all the specialists, we had the robotics factory where we had people who know how to build a robots and software, and it's really sort of like, just churning out with a lot of people on the line, and I think the next level after that is, you know, completely fully automated applications driving themselves, you know, self-driving applications, and I think that's when things get really interesting, and maybe we start to remove the traditional operator out of the equation and it really becomes about empowering developers with tools that are comfortable and that leverage all the cloud era and stuff that we built. >> All right, so Randy, you're credited with the pets versus cattle analogy, what's the latest, you were talking about some of the previous slide decks, what's Randy Bias looking on down the road? >> I mean, the stuff just comes to me, man. I can't like predict, but the thing I've been talking about a lot lately is services of platform, I think we might've talked about that last time, which is just this notion that if we look at where Amazon's invested and what's interesting, it's certainly not at the infrastructure layer and it's really not at the PAS layer, it's that thick layer in between with like database as a service and NoSQL as a service, and messaging service, and DNS and so on, where you can kind of cherry pick those things as you're assembling your own PAS for your application, and I still think that's the area that is under-discussed, and the reason is is the people back into basically doing that, building kind of the service as a platform system, but they're not like going into it, kind of like eyes wide open. >> Yeah, so just following up on that last piece, one of the criticisms I have this week is when you talk about multi-cloud, most of the people talk about, oh well people are clawing things back to their data centers. Juniper plays across the board, strong partnership with Amazon, yet you're here, what are you hearing from customers, you know, what do you see as kind of the balance there and, you know, the public cloud's role in the world? >> I mean, they're still winning, right? I don't think there's any doubt, I haven't seen a decline back here talking about, but we are starting to enter into the era of, okay, this stuff is out there, and it's running, but I need to find my governance model, I need to understand who's using what, I need to understand what it's costing me, and that's the sign of the maturation process. And so I think that, you know, we saw in the early days of cloud, people jumping the gun, creating compliance services, and you know, SAS products that would basically measure how much you're spending and think that it's time for that stuff to come back in vogue again, because the tool needs to be there for people to manage these extended supply chain of IT vendors which include the public cloud. And I think that the idea that would claw them back as opposed to like just see that as holistic part of what we're trying to accomplish doesn't make any sense. >> Well learned. Well, Randy Bias, always a pleasure to catch up with you. >> John. >> John Troyer, I'm Stu Miniman, getting towards the end of two days of three days of live coverage. Thanks for staying with the CUBE. (bubbly electronic music)

>> Announcer: Live from Las Vegas, it's theCUBE! Covering AWS re:Invent 2017. Presented by: AWS, Intel and our ecosystem of partners. (lively electronic music) >> Welcome back everyone, this is theCUBE special exclusive coverage of AWS re:Invent 2017. CUBE's our flagship program, we go out to the events and we extract the signal noise. I'm John Furrier your co-host. With me today is Justin Moore, an analyst. We have two sets here in Las Vegas. Our next guest is Sumeet Singh, Vice President of Cloud Analytics with Juniper Networks, formerly of AppFormix, which was bought about a year ago. CUBE alumni back. New team, Juniper, welcome back. Last time we chatted with you you were entrepreneurial. >> Yeah. >> Taking names, kicking ass, now you're-- >> Bought out Juniper Networks, yeah. >> You bought out Juniper Net, what's going on? >> So we've essentially been building, building more and more and it's actually been a totally awesome experience. So, Last year when we spoke, we were essentially looking at a whole lot of private cloud deployment. Looking at OpenStack, looking at (mumbles), looking at VMware, and since, what we've now started really expanding into is, of course, the multi-cloud and hybrid cloud scenario. And looking at how to secure these clouds on prem, in the cloud, multi-cloud, as well as bring rich analytics into real-time operations insight as to what's going on in all of these environments. And how to optimize them. >> Yeah, that whole multi-cloud hybrid cloud thing is really exploded in the last 12 months. I'm hearing from customers a lot more that they are pursuing a multi-cloud strategy, but it seems that there's just this proliferation of things that you've now got to monitor and secure. So, how are you helping customers to do that? >> So, I mean, you're going to start with the basics. Right? So, the first thing that we got to realize is there are, of course, those companies that are born in the cloud. But then, there's a whole bunch of others who have for long run their own data centers and run their application stacks on prem, who are now looking to migrate to the public cloud and build all that multi-cloud scenario. In that situation, I would say, you need a little bit of hand-holding. You need to understand how your application's running on prem, which ones can be moved to the cloud, how can they be moved to the cloud, you want to ensure that those policies that you were implementing on prem you'll be able to implement those same policies in the public cloud, as well. The monitoring really starts on prem. All of those policies that operation starts on prem, and then you take them and you build them and you >> I'll get your take on, we'll have to get your take too, Justin, on something that's going on that I see clear visibility on. Infrastructure operations, data center cloud, get your house in order, networks, migration, hybrid cloud, multi-cloud, and then all that stuff. Then you've got this developer tsunami going on, a renaissance of real new development, new kinds of development, multiple databases using in app, IoT, so, the software development methodologies are changing for developers. That's obvious. What's the impact to the infrastructure guys, because you're starting to see Lambda and Server List as a way for saying complete infrastructure is code. How does that change the notion of, what the hell the data center is? Because you could argue that's just an edge now. So, what's the software, what are some of the software practices you see that are notable? >> The ones truly amazing, like in all these things that you're saying, is that you no longer need to use one approach to build anything. Any product that we put out, or any service that you put out, now uses a combination of all of these things. It could be Lambda, it could be IoT, it could be a wholesale application that's office started using (mumbles), that's spanning that multi-cloud environment. So, it's the beauty of all of this is the power of choice. We have so much more choice available to us. Right? But then, when choices, with choice comes that explosion and that complexity. It's >> Complexity is key, but speed is also there. You see. So, the question is, at what point does the cream rise to the top, and the people that are slow get run over. >> We're just seeing another evolution in obstruction, really, it's like, we don't write an assembly code anymore. We're writing directly to the hardware. We added in high-level programming languages, and now, in terms of the infrastructure, developers don't care about infrastructure as much as people talk about dev ops, and the thing like dev ops is a thing, developers don't want to deal with the infrastructure. They want to deal with code, cuz that's where they live. And the infrastructure folks, well, a lot of them are actually becoming developers now. So, they're learning how to use tools like, using development tools to actually get their job done. Which is where we're seeing infrastructure is going. So, there's a lot more ob abstraction into pure software, so you don't have to worry about the underlying obstructions, at least, not very much. >> All right, Sumeet, question to you now on that is, that requires the network guys, Juniper, you're part of that, and all the analytics to think differently about what you're instrumenting. To do what he said, to make it free, you gotta enable a lot of policy, a lotta data analytics, take us through what's the current state of the art there. >> So, the current state of the art, is essentially, if you talk about Juniper products, we have our family of SRX products, where you can have on prem firewalls, as well as virtual firewalls in the cloud, and using these tools, you can have consistent policies on prem and in the cloud. You can free up transit VPCs. Then there are the obligations in the multi cloud world, and do all kinds of fancy things. But where we also going with our solutions is to make them much more simpler to consume. It's truly all about simplicity, right? Because now you have all this choice, and you can have Lambda, and you can have all these new ways to bring up your applications. What becomes key is that the policies that you wanna implement become automatic. Right? And the way to do that is, the way we are doing that is, essentially, doing this auto-learning of your environment. Right? Automatically understanding, Automation, right? But, not, automation in two parts, as in automatically detect what's going on, but then automatically apply the policies as well, no matter where the workload is and where it's scaling, we automatically apply the policies to it. >> So, it's a lot of investment in this mart of underly-- Making something simple is actually quite complex to do. So, you need to understand what are the right things to automate, and what are the few things where you actually wanna give humans that choice, without it becoming overwhelming, so that, okay, I have to choose between one of 800 different ways of doing this. That's just not something that humans cope well with, whereas machines are actually really good at that. >> And that's the value here. We want to hide all the complexity under the hood. You know, use those advanced logarithms, use, you know, where they be on prem or in the cloud, but running all the analysis, implementing all the right policies for you, right? And new, new workload comes up it should automatically get the policy, right? And we are now able to do that both in the private data center, as well as in the public cloud, and bridge those policies together for you, automatically. >> The common theme we're seeing in cloud, we had a guest on from Thorn, where they automate, essentially, police officers writing down notes in a notebook to fully spotting with machine learning and all this great stuff, to find missing and exploited children, manual sucks, basically. Manual's slow-- >> The workload's too dominant now for you to think about manual. >> I want real-time. So most organizations, what's going on there? How do you guys help there, what's the progress? >> Oh. So, this is actually a great question, by the way, so, and this is part of the reason why we like, as a company, as a start up, maybe, we're like, doing all this cool stuff, and, you know, not really thinking about all the, hey, this is slowing me down. The reason why we went to Juniper, if you look at the history of Juniper, and the product portfolio, and the stock at Juniper, when it comes to automation, when it comes to things like ABI, when it comes to things like policy, they've always kind of like led the pack in that networking space, and now this is the opportunity to take that that wealth of knowledge, and scale it out, and take it to a little bit broader multi-cloud, hybrid cloud space. But, that's truly where it is, and even if you, kind of like go down low level to the devices, all Juniper devices are able to stream real-time elements. We are able to do ML in real-time, even on the physical devices, right? Similar for all virtual devices, and now, with our Formix, we even bring in the performance and operations inside, from the running infrastructure, whether it's on prem and in the cloud, not just networking, but the compute, the databases, your applications, your clusters, all of that, to build for you this end-to-end view, right? Not just the networks, your servers, Vms, workloads, the underlying network, the connectivity, all of it. >> How does that, because the developers, they live in application land, and again, they don't really care about that infrastructure, but as it turns out, sometimes it's quite useful to know which particular network devices, or what the infrastructure is that underpins things, like where you sometimes need to be able to drop into assembly code to really optimize things, so are you making that information about the infrastructure visible to developers in a way that they like to, to know and consume? >> Absolutely, so, one key thing about, you know, our product portfolio, and how we are releasing our services, essentially, we've wrapped everything around, you know, these role-based access interfaces. Where both the operators are able to get their views, they're able to construct views that the developers are able to see, and then both can implement their own policies, right? If, let's say, there's some infrastructure that's down, or is unhealthy, then having that global topology view helps you in real-time totally, and in real-time informs you what the impact of that outage is. Like who are the developers who would be impacted, what are their obligations? And, you know, we can bring that insight, and consume it to run the automation. So, if, let's just say, some infrastructure's unhealthy, can you read off the graph? >> Sumeet, talk about what you guys are doing here. How's Amazon, big learning conference, but it's a massive show, 45,000 people here, across multiple hotels. A lot of sessions. What do you guys talk about? What's the big cloud piece for you guys? >> For us, really, first, it's just visibility, right? We have a product portfolio that gives you visibility. Like, both for your physical infrastructure, and your virtual structure. Then, the next thing is, of course, You know, yeah, you have the visibility. But then, at our scale, no human can consume all that information. It's too slow. It's too slow. So, you've gotta have the machine-learning built in. So, it's promoting that visibility into insights in real time, and then, it's about how do you secure your workloads? So, consuming all of that insight to implement all of the policies, implement all of the automation, to ensure that everything is running as you want it to. >> What's your Juniper message to the developers here? Is there a new face to Juniper, a new vibe? You mentioned Juniper's always had great products, like, you move packets around at lightning speeds, you know, wire speeds, all that great stuff. How do you, what's new? What's it mean for me as a developer, what is Juniper, how's it make my life easier? >> What's new is that now it's easier for developers to consume our products. Our products are now available in the Amazon marketplace, right? Our visibility products, our machine-learning products, our security products, right? You can just click, install, and start using them. That's new for Juniper, right? I mean, traditionally you would think of-- >> You probably get Juniper goodness just by treating it like a library. >> That's it. You can just download, not even download, right? You're -- >> It's server-less. It's router-less. It's device-less. >> There you go. You can just start consuming them. And then, if you do have that knowledge of how do you use those devices on prem, then you can apply that knowledge in the cloud, and then use them all. >> Must be computing back in, what, like 20 years ago. I mean, is it just like a grid now. >> Oh, yeah, pretty much, yeah. >> It's a fabric. >> It's the same, if you already know how to use it one place, you know how to use it everywhere. >> Yeah, but, I mean, it's, really, the value of the cloud is making it even simpler, right? Running all of that automation, like we talked about Lambda, like even within our products family, we can, we use Lambda to constantly see what's changing, and that's how we process lots of our internal transactions, as well. >> Sumeet, congratulations on your acquisition and your entrepreneurial journey, and now you're at Juniper. Looking forward to keeping in touch. Sumeet Singh, Vice President of Cloud Analytics, and now at Juniper Networks, formerly AppFormix, CUBE alumni, thanks for coming on and sharing your commentary. I'm John Furrier, and Justin Moore, here on theCUBE, main stage in Las Vegas at AMS re:Invent We'll be back with more after this short break. (lively electronic music)