 Live from San Francisco, extracting the signal from the noise, it's theCUBE covering Oracle Open World 2015. Brought to you by Oracle. Now your hosts, John Furrier and Dave Vellante. Okay, welcome back everyone. We are here live on Howard Street for theCUBE. Day four of Oracle, day three, if you count Monday, but Sunday was day zero. This is theCUBE, so look at Angel's flagship program. We go out to the events and extract the signal from the noise. I'm John Furrier, the founder of Silicon Am, Joe McCos, Dave Vellante, founder of wikibon.com. Our next guest is Praveen Afana. They get there right? Astana. Astana, I got that right. And Mohammed Afshar, welcome back to theCUBE. Praveen, first question. You run the portfolio of the private public cloud. Larry announced a special announcement yesterday about the private cloud, big long name, but you also have a private cloud solution. Can you just break down the nuance there? I want to dig into that, because it's been getting a lot of buzz. One, the name, Larry named it, that was key, but also specifically nuanced around the cloud and you already have a private cloud. So can you take us through that? So here's the way it works. Larry called it the private cloud appliance for PAS and IAS. And it's a very accurate and specific name. That's the one thing, you know exactly what you're getting with that name. So we already have a private cloud appliance that also it's been having for a number of years. And the difference is this. Our private cloud appliance is a general purpose appliance that anybody can use. It has Linux, OpenStack, can run Windows, run multiple workloads. And you can expand it and run your private cloud. The fully elastic, fully elastic, yeah. Now the private cloud appliance for PAS and IAS just does just that. It's actually, Larry described it very well and I'll just repeat it because I can't do better than that. Which is, we took a slice of our public cloud and just put it inside a machine. That's what this appliance is. So around the PAS and IAS services that the public cloud doesn't look the same. And let me have Muhammad elaborate on exactly what this machine does. Because the PAS is a critical component of that. Absolutely, absolutely. I mean with the private cloud machine for PAS and IAS, what we've done as Praveen said is really to package up what we have in the Oracle cloud. First of all, the infrastructure as a service which is compute and storage. And then also the PAS services. We have a very, very rich layer of PAS services, 40 plus PAS services that we announced at Open World. And actually previously we've been working on them. There are updates to them, et cetera. So we've taken both of those solutions which is the IAS and the PAS from the public cloud and package them up for consumption on premise. And that's pretty revolutionary thing. So whether you're running Java applications, whether you're running Python applications, whether you're running Tomcat applications, whether you're on JBoss applications, whether you don't want to integration, all of the PAS capabilities that we've been talking about available and packaged up on premise. Absolutely, that's the goal as well as the infrastructure as a service. So you get access to cloud innovation directly from Oracle cloud into your data center. But I'm not buying a box. I'm renting. We can talk a little bit about that. So obviously one of the things customers have asked us and we can talk a little bit about the use cases and why people have actually been asking for this because they have. But one of the things that customers like is the cloud-like experience. So every customer I've talked to in the open world whether it's a bank, whether it's a telco, whether it's a government office, they like the idea of getting access to cloud innovation. They see a lot of innovation in the cloud, but they would like that packaged up on their premises because of geographical restrictions, because of compliance reasons, because of control. A lot of the banks are not comfortable yet with putting everything certainly in the public cloud and for some things they really want to keep them on premises. So for that reason we really launched this product and of course people ask well how you're going to offer it and we're going to give people the option, but you can have it operated by Oracle as a service. The same way you have with the cloud. You go in through a web page and you get cloud. It just reminds me of the old extra net days. I mean it's how you slice things. It's all on the semantics. I mean if a customer wants to have cloud, it's all about the consumer. It has nothing to do about the box. Exactly. It's all about the consumption. In fact there's a saying, right? What is cloud? It's running it on someone else's server. I mean it's not some magical thing. It's the server, someone else's server. All we are saying is hey, where should it matter where that server sits as long as you have a cloud like experience? So the business model of cloud, the how the consumption is obviously defines cloud, but also interesting about the stack. So one of the things we love about cloud is self-service integrated stack and a lot of magic happens. So scaling, talk about that because Amazon has shown that integrated stacks work. People like to use some building blocks and then build on it. You mentioned open stack. Node.js was mentioned in the keynote. Very popular. Docker containers. This is the cloud native culture. So as long as you offer that and you have the consumption of cloud that takes away the whole, what is it, sit equation? Precisely. If it's some geopolitical or some compliance thing, that's a different factor. But to be cloud native, that's got to be very, very flexible. So that's a real developer centric piece on the tech side. So we've talked about consumption. What is the developer angle on this? That's really big. Yeah, absolutely. It's huge. I mean, we actually do both audiences. Remember, a lot of customers have significant investments in things like WebLogic. I mean, it's predominantly used around the world, number one app server. So we've provided Java cloud service on-premise that gives you all the automation around installation, configuration, scaling, backup, patching, et cetera, as well as the brand new multi-tenancy capability we announced in WebLogic. So we have that within Java cloud service and we bring that on-premise. Now, people want to develop cloud native infrastructure. So we have something called the application container cloud service. And I think you saw it yesterday, which has Node, we have Python and Java SC and various other runtimes. And that gives people the ability to develop cloud native apps. You can define auto scaling rules. You can define a number of policies and you drop your app in and it gets distributed and scaled out to all of the infrastructure. And it's exactly the same whether it's in your data center or whether it's in the public cloud. And I have the choice, you said, of doing it as a service or on-premise. So if a flash drive fries, I have the option of saying, you guys fix it. Yeah, exactly. Absolutely. Just like the cloud. And I can pay you to do that or I can do it myself. Absolutely, yeah. So one of the important things about what we're doing, and this is really important when you're talking about production, is to have the same operational model between the public cloud and the on-premises cloud. That's very important because what I've found in talking to customers is the operational model is where things break. If I have to do a certain way on-premises, then I got to change and learn something new to do it in the public cloud. It's very difficult. Either I need two different people or I got to learn a whole new way of doing things. You know, it's like learning two languages. You don't do it. So we maintain the same operational model on-premises as well as in the public cloud. That's a key important. So let's talk about why that's so important and why it's different. So when Amazon came out with the first cloud, everybody noted, wow, it's homogeneous. So if we could get homogeneity throughout, we could have this notion of hybrid, on, off, whatever. And nobody ever got there. You're there, you're finally. Exactly. So Amazon actually never got there. They never got there. Amazon has no interest in getting there. They want everything swept into the public cloud. We have definitely done that because we have, as Mohammed said, listen to our customers and we provide a variety of options to our customers. That's the key thing here is for those customers who want just that private cloud experience, we have the private cloud appliance, PCA, where they can run open stack, windows, all that stuff, multiple workloads. For those customers who want to do, you know, extend their middleware into Paz and have it integrated with IaaS. That's an important point. We call ourselves the integrated cloud. The Paz and IaaS integrate together. That's what we offer this private cloud appliance where IaaS and Paz. And, you know, the same operational model up and down. So you think about all the things that Oracle does. Let's call it N, N being everything you guys do on-prem. And the strategy is N on-prem will be the same N in the cloud. That's the strategy, correct? That's the strategy, yeah. What percent of N is available in the cloud today? Is it 50% of N, 40% of N? So we're actually, so if I can paraphrase your question, right, obviously packaging up all the goodies and all the innovations in public cloud and putting them into this private cloud machine is multi-year exercise. It's a continuous exercise, remember, because there are regular updates that go to the public cloud. There are new solutions that get rolled out. So we have a pretty phased approach. So what we're doing is we're gonna launch the actual service offering, which is infrastructure as a service offering, Java cloud service, which everybody uses with goodies like WebLogic, multi-tenancy, as well as our integration cloud service because everybody needs integration because they have lots of different things. And then we're gonna onboard, for example, the application container cloud service, which we've had a lot of requests from customers for and a number of other cloud services as well. So there's a very regular cadence to onboard all of these things very rapidly. At some point, it's like everybody says mobile first. Are you at the cloud first? Development stage, your mentality. What's the internal DNA like? I think that's what we knew. Cloud native is the way we think about it, not location. So cloud native means I'm developing for an elastic infrastructure. That's really what cloud native ultimately is. And so you can develop it for the cloud. Many customers actually would have run it on premises after they've developed it in the cloud. And so we offer that. I think one of the key differences we have compared to all the other players in the industry is, A, the breadth of our portfolio, B, the real understanding of being cloud native everywhere, and having consistency between the on-premises and off-premises stuff. So it's the same thing. There's no one else I know that can provide all of that. Now, some companies have tried to put appliances on-premises that are similar to what they have in the public cloud. They quickly go out of date. They don't have the same code. Our appliances maintain the same code. How big is the appliance? So the appliance will range. You can start it with, I think... You start it with fixed configurations, right? But it's basically rack-based. So you can start with... It could be a super cluster. I mean, depending on what the needs are, right? It has a specific hardware profile. Because remember, what we're trying to do is make sure we give you exactly the same thing. That's our commitment. It kind of depends per customer. No, it doesn't depend per customer. From a software perspective, which is IaaS and PAS, as public cloud. Our commitment is to stay as true to what we do in the public cloud as possible. And there, we're using x86 servers. So we're using x86 servers here within... I was just thinking from a footprint standpoint, I'm like, this is pretty cool. If I put it in a telephone closet, the smallest of telephone closets, or is it going to be any of them on a negative side? Grow as you grow. So you can start with a quarter rack or half rack and then just keep trying to plan my facilities based upon what I'm doing with it. So it's like you said for me. So it's the diversity of offerings. It's the homogeneity, the exact... And it's not a financial gimmick. Not if you guys do financial gimmick. Put a box in and we'll put extra capacity in there and whatever. But it's financial engineering. This is true radical service. Here's the thing. You saw, at a very important point here I want to make actually, is you saw the demo that Larry did about portability of workloads from on-premises to off-premises with a single click. That is critical. So because we have the same software and hardware on-premises and in our public cloud, you can easily move workloads, some of them while they're even running. So what does that mean? That means that we can offer true bursting compared to a lot of people who bursting is a PowerPoint, a word in a PowerPoint slide. So hard to do. They can technically burst, but they have to have someone on the other side to burst too. That has to be configured. They can technically burst. The bursting didn't know where. Except it may burst. The bursting didn't know where. So talk more about, give us an example of how somebody would use that in a real world. So there's a couple of examples. One is, hey, you've gotten a certain amount of infrastructure on your premises and then you say, hey, my demand is exceeding my infrastructure. Well, I can now move it to the Oracle Public Cloud while it's running without buying a box and have it scale as much as I need to handle that unexpected load. Or disaster recovery. Or I really want to be able to connect with other applications I have in the cloud. In this world of ours where you have mobile, social, everything, you may want to connect with something in the cloud to make a new campaign or CRM thing happen. So you can just move it up there and do that connection and bring it back. Ravine and Muhammad, I want to ask you a question on this particular point. We're a big, we're an Amazon customer. Maybe we should look at Oracle. Now that you have the cloud, there's a lot of SMBs like the cloud. Oracle, in fact, Amazon's customer base, majority of, you know, some mid-sized companies and a couple of big whales in there, Netflix and whatnot. But the issue is I need to have elasticity. So I mean, so I'd have elastic means to me is, okay, I'm running my crowd chat service. We have EC2, we got S3, we got auto-scaling, elastic means talk, red is all this stuff, cool stuff in the great stack. But if I have a, all of a sudden, 100,000 people hit my site, I got auto-scaling built in. So I know, because they get a lot of servers, they can spin up and manage that load. How you address that concern on the deployment side of the box? Are there the cores inside of the engineered system? I mean, you have to have some horsepower to meet a minimum kind of like threshold of what auto-scaling means. There's a couple of things. Firstly, in our public cloud, we have that capability, by the way. So we have that all built in, it's tremendous. I can see that. Petrogenous infrastructure, you can run our solutions, you can run open source solutions, you can run kind of basically anything you want. On the private side, so that's really around a, offering a service and then giving you capacity that you can burst through internally within the frame itself, right? That's really the notion. Now, if I, at the moment, I need like, maybe half a frame and then I need 47 frames, then clearly there's some limitations because you never told us you might need to burst to 47 frames. But you could burst to the public side. So I had to basically do some capacity planning on that. A little bit of capacity planning with your file. How many cores are in that? Just the box, the M7's got. How many cores in it? I mean, it's got, hell, a big time. 42 cores, 32 cores. A resilient core. But you didn't tell box. But you know, actually, so there's a couple of things here. First of all, most customers I've spoken with, you know, they don't have 500% like spikes. You know, there may be like 50% or 100% spike and then you can do some planning. You can do our portability for that sort of thing, right? But one of the big differences between, because you brought up Amazon, and one of the big differences between what we are doing at Oracle and what Amazon has been doing is, we are really gearing towards mission critical. Yeah. Right? Everything runs on Oracle. You know, landing gear is always 100% of the time you have to be deployed. You know, ambulances always have to be dispatched. Mission critical runs on Oracle. Oh, okay. And that's what we want to do now. Okay, so I've been on this for a while. So, I'll ask you. I won't tell you, I'll ask you. Can you run mission critical Oracle in Amazon? If you do all the work necessary to do it, because they don't give you the SLA, right? So you've got to build a high availability in there. You've got to build the storage. The science project. You can be done. It's a science project. That's why we believe that our cloud provides the exactly right. So it is possible. It is possible. It's just hard. Yes. Okay. Very hard. I've been saying you can't do it. Nobody's doing it. You can do it, but nobody's doing it. Absolutely can do it. Yeah. And Amazon is a partner of Oracle. Yes, but you need specialized hardware to do it. Yeah. Right? So... Yeah, it's... A lot of elbow grease and knowledge. That's exactly right. Okay. So anything's technically possible. Yes. But... Remember, even like the showcase, which is people like Netflix, right? Yeah. Well, guess what? They've had outages, right? And they've architected things beautifully, which means if you're anybody else, you're going to have even more problems. So we really designed our cloud for that, for many of the customers out there who are Oracle customers, as well as non-Oracle customers who demand a certain level of SLA, business critical applications, they run their business. And they say, hey, I want to have access to all this innovation in the cloud, but I'm running my core banking. And I'd like IAS, and I like the abstraction provided, but I like it on-premise. Can you do something for me? And that's really where we come in. It makes total sense for Oracle. It's peaceful. I got to ask the cloud-native question. You mentioned mission-critical. Obviously, Oracle, they run some critical infrastructure and critical apps as well, so I get that. So now for the DevOps equation. Back to you know, you look at some of the machines you're offering here. I mean, it makes DevOps easier, infrastructure as code, which is something that we always talk about. That is more of a free-form developer. You talk about Docker, rather. That's the developer environment. So there's some experimentation going on in the cloud. So as you move into mission-critical, what does DevOps mean for mission-critical? Because it's an operational staple. No one's going to let the devs get access to it. Maybe they will. So how do you define cloud-native with mission-critical, with the need to program infrastructure as code? So look, I think the biggest point about this is that I think it's a good thing moving from to a continuous delivery, continuous integration mentality, right? Because A makes sense because your whole organization gets used to this concept of delivering things. And of course, what you mentioned, which is hey, infrastructure code because the data center is becoming programmable. So that code that is the programs can then be part of this continuous delivery, continuous integration architecture. Our goal is very simple. We want to give you cloud-native infrastructure so you can have your choice of CI or CD infrastructure. We have that built in. We have something called the developer cloud service that does actually do it for you. And it's programmable. Yeah, it's programmable. And you actually put your assets in there. You have the integration and the delivery. So it gives you a great mechanism by which you can actually manage that. But hey, if you've got your own CI infrastructure, you can use that on our cloud. You can use it on the private cloud machine for Paz and IS. All right, guys, we've got to get the rabbit. I want to get your final word. What's your thoughts on Oracle Open World this year? Obviously, this is a hot area. You're in the lion's den, if you will. Very competitive, pass space, middleware, database, all in the center of the action. So I'm new at Oracle. I've been here two months. Welcome to the lion's den. I can tell you something. I mean, it's stunning. As someone who just come in, the stunning how much technology we have and how we listen to the customers and take care of their business needs. And everything we're doing is just doing stuff. Awesome. Mohamed, final thoughts? I think on this particular topic of the private cloud machine for Paz and IS, every customer meeting I've been with, whether it's a bank or a telco or a smaller customer, they love getting innovation from cloud, from premise. So from my perspective, it's great. Remember, I'm always locked up downstairs in customer meetings. So that's about as much as I can tell you. Praveen, you're new. So I'm going to ask you a question. Every company has some sort of cadence, Moore's Laws, Intel, you know, go faster, smaller, faster, cheaper. That's kind of their culture. What's the Oracle culture like? When you come in, you got fresh eyes here. What's the cadence? What's that unique thing, an Oracle, that makes it a unique culture? I mean, for me, just what I've learned, it's really solving the business needs for the customer. I mean, I don't see any company that does it as well as Oracle does. And that's what drives everyone. It isn't about, hey, we have some cool technology, now how should we use it? It's, here's a customer problem, how do we go fix it? All right. Praveen Mohan, thanks for conjoining us. We're at the Cube. We're breaking down the events here. We're on the last final leg of the three and a half days of Cube coverage. Four days, we'll be right back after this short break. It's the Silicon Angles at the Cube, we'll be right back after this short break.