>> Hi, my name is Andy Clemenko. I'm a Senior Solutions Engineer at StackRox. Thanks for joining us today for my talk on labels, labels, labels. Obviously, you can reach me at all the socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, and it'll take you to my GitHub page where I've got all of this documentation, socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, (upbeat music) >> Hi, my name is Andy Clemenko. I'm a Senior Solutions Engineer at StackRox. Thanks for joining us today for my talk on labels, labels, labels. Obviously, you can reach me at all the socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, and it'll take you to my GitHub page where I've got all of this documentation, I've got the Keynote file there. YAMLs, I've got Dockerfiles, Compose files, all that good stuff. If you want to follow along, great, if not go back and review later, kind of fun. So let me tell you a little bit about myself. I am a former DOD contractor. This is my seventh DockerCon. I've spoken, I had the pleasure to speak at a few of them, one even in Europe. I was even a Docker employee for quite a number of years, providing solutions to the federal government and customers around containers and all things Docker. So I've been doing this a little while. One of the things that I always found interesting was the lack of understanding around labels. So why labels, right? Well, as a former DOD contractor, I had built out a large registry. And the question I constantly got was, where did this image come from? How did you get it? What's in it? Where did it come from? How did it get here? And one of the things we did to kind of alleviate some of those questions was we established a baseline set of labels. Labels really are designed to provide as much metadata around the image as possible. I ask everyone in attendance, when was the last time you pulled an image and had 100% confidence, you knew what was inside it, where it was built, how it was built, when it was built, you probably didn't, right? The last thing we obviously want is a container fire, like our image on the screen. And one kind of interesting way we can kind of prevent that is through the use of labels. We can use labels to address security, address some of the simplicity on how to run these images. So think of it, kind of like self documenting, Think of it also as an audit trail, image provenance, things like that. These are some interesting concepts that we can definitely mandate as we move forward. What is a label, right? Specifically what is the Schema? It's just a key-value. All right? It's any key and pretty much any value. What if we could dump in all kinds of information? What if we could encode things and store it in there? And I've got a fun little demo to show you about that. Let's start off with some of the simple keys, right? Author, date, description, version. Some of the basic information around the image. That would be pretty useful, right? What about specific labels for CI? What about a, where's the version control? Where's the source, right? Whether it's Git, whether it's GitLab, whether it's GitHub, whether it's Gitosis, right? Even SPN, who cares? Where are the source files that built, where's the Docker file that built this image? What's the commit number? That might be interesting in terms of tracking the resulting image to a person or to a commit, hopefully then to a person. How is it built? What if you wanted to play with it and do a git clone of the repo and then build the Docker file on your own? Having a label specifically dedicated on how to build this image might be interesting for development work. Where it was built, and obviously what build number, right? These kind of all, not only talk about continuous integration, CI but also start to talk about security. Specifically what server built it. The version control number, the version number, the commit number, again, how it was built. What's the specific build number? What was that job number in, say, Jenkins or GitLab? What if we could take it a step further? What if we could actually apply policy enforcement in the build pipeline, looking specifically for some of these specific labels? I've got a good example of, in my demo of a policy enforcement. So let's look at some sample labels. Now originally, this idea came out of label-schema.org. And then it was a modified to opencontainers, org.opencontainers.image. There is a link in my GitHub page that links to the full reference. But these are some of the labels that I like to use, just as kind of like a standardization. So obviously, Author's, an email address, so now the image is attributable to a person, that's always kind of good for security and reliability. Where's the source? Where's the version control that has the source, the Docker file and all the assets? How it was built, build number, build server the commit, we talked about, when it was created, a simple description. A fun one I like adding in is the healthZendpoint. Now obviously, the health check directive should be in the Docker file. But if you've got other systems that want to ping your applications, why not declare it and make it queryable? Image version, obviously, that's simple declarative And then a title. And then I've got the two fun ones. Remember, I talked about what if we could encode some fun things? Hypothetically, what if we could encode the Compose file of how to build the stack in the first image itself? And conversely the Kubernetes? Well, actually, you can and I have a demo to show you how to kind of take advantage of that. So how do we create labels? And really creating labels as a function of build time okay? You can't really add labels to an image after the fact. The way you do add labels is either through the Docker file, which I'm a big fan of, because it's declarative. It's in version control. It's kind of irrefutable, especially if you're tracking that commit number in a label. You can extend it from being a static kind of declaration to more a dynamic with build arguments. And I can show you, I'll show you in a little while how you can use a build argument at build time to pass in that variable. And then obviously, if you did it by hand, you could do a docker build--label key equals value. I'm not a big fan of the third one, I love the first one and obviously the second one. Being dynamic we can take advantage of some of the variables coming out of version control. Or I should say, some of the variables coming out of our CI system. And that way, it self documents effectively at build time, which is kind of cool. How do we view labels? Well, there's two major ways to view labels. The first one is obviously a docker pull and docker inspect. You can pull the image locally, you can inspect it, you can obviously, it's going to output as JSON. So you going to use something like JQ to crack it open and look at the individual labels. Another one which I found recently was Skopeo from Red Hat. This allows you to actually query the registry server. So you don't even have to pull the image initially. This can be really useful if you're on a really small development workstation, and you're trying to talk to a Kubernetes cluster and wanting to deploy apps kind of in a very simple manner. Okay? And this was that use case, right? Using Kubernetes, the Kubernetes demo. One of the interesting things about this is that you can base64 encode almost anything, push it in as text into a label and then base64 decode it, and then use it. So in this case, in my demo, I'll show you how we can actually use a kubectl apply piped from the base64 decode from the label itself from skopeo talking to the registry. And what's interesting about this kind of technique is you don't need to store Helm charts. You don't need to learn another language for your declarative automation, right? You don't need all this extra levels of abstraction inherently, if you use it as a label with a kubectl apply, It's just built in. It's kind of like the kiss approach to a certain extent. It does require some encoding when you actually build the image, but to me, it doesn't seem that hard. Okay, let's take a look at a demo. And what I'm going to do for my demo, before we actually get started is here's my repo. Here's a, let me actually go to the actual full repo. So here's the repo, right? And I've got my Jenkins pipeline 'cause I'm using Jenkins for this demo. And in my demo flask, I've got the Docker file. I've got my compose and my Kubernetes YAML. So let's take a look at the Docker file, right? So it's a simple Alpine image. The org statements are the build time arguments that are passed in. Label, so again, I'm using the org.opencontainers.image.blank, for most of them. There's a typo there. Let's see if you can find it, I'll show you it later. My source, build date, build number, commit. Build number and get commit are derived from the Jenkins itself, which is nice. I can just take advantage of existing URLs. I don't have to create anything crazy. And again, I've got my actual Docker build command. Now this is just a label on how to build it. And then here's my simple Python, APK upgrade, remove the package manager, kind of some security stuff, health check getting Python through, okay? Let's take a look at the Jenkins pipeline real quick. So here is my Jenkins pipeline and I have four major stages, four stages, I have built. And here in build, what I do is I actually do the Git clone. And then I do my docker build. From there, I actually tell the Jenkins StackRox plugin. So that's what I'm using for my security scanning. So go ahead and scan, basically, I'm staging it to scan the image. I'm pushing it to Hub, okay? Where I can see the, basically I'm pushing the image up to Hub so such that my StackRox security scanner can go ahead and scan the image. I'm kicking off the scan itself. And then if everything's successful, I'm pushing it to prod. Now what I'm doing is I'm just using the same image with two tags, pre-prod and prod. This is not exactly ideal, in your environment, you probably want to use separate registries and non-prod and a production registry, but for demonstration purposes, I think this is okay. So let's go over to my Jenkins and I've got a deliberate failure. And I'll show you why there's a reason for that. And let's go down. Let's look at my, so I have a StackRox report. Let's look at my report. And it says image required, required image label alert, right? Request that the maintainer, add the required label to the image, so we're missing a label, okay? One of the things we can do is let's flip over, and let's look at Skopeo. Right? I'm going to do this just the easy way. So instead of looking at org.zdocker, opencontainers.image.authors. Okay, see here it says build signature? That was the typo, we didn't actually pass in. So if we go back to our repo, we didn't pass in the the build time argument, we just passed in the word. So let's fix that real quick. That's the Docker file. Let's go ahead and put our dollar sign in their. First day with the fingers you going to love it. And let's go ahead and commit that. Okay? So now that that's committed, we can go back to Jenkins, and we can actually do another build. And there's number 12. And as you can see, I've been playing with this for a little bit today. And while that's running, come on, we can go ahead and look at the Console output. Okay, so there's our image. And again, look at all the build arguments that we're passing into the build statement. So we're passing in the date and the date gets derived on the command line. With the build arguments, there's the base64 encoded of the Compose file. Here's the base64 encoding of the Kubernetes YAML. We do the build. And then let's go down to the bottom layer exists and successful. So here's where we can see no system policy violations profound marking stack regimes security plugin, build step as successful, okay? So we're actually able to do policy enforcement that that image exists, that that label sorry, exists in the image. And again, we can look at the security report and there's no policy violations and no vulnerabilities. So that's pretty good for security, right? We can now enforce and mandate use of certain labels within our images. And let's flip back over to Skopeo, and let's go ahead and look at it. So we're looking at the prod version again. And there's it is in my email address. And that validated that that was valid for that policy. So that's kind of cool. Now, let's take it a step further. What if, let's go ahead and take a look at all of the image, all the labels for a second, let me remove the dash org, make it pretty. Okay? So we have all of our image labels. Again, author's build, commit number, look at the commit number. It was built today build number 12. We saw that right? Delete, build 12. So that's kind of cool dynamic labels. Name, healthz, right? But what we're looking for is we're going to look at the org.zdockerketers label. So let's go look at the label real quick. Okay, well that doesn't really help us because it's encoded but let's base64 dash D, let's decode it. And I need to put the dash r in there 'cause it doesn't like, there we go. So there's my Kubernetes YAML. So why can't we simply kubectl apply dash f? Let's just apply it from standard end. So now we've actually used that label. From the image that we've queried with skopeo, from a remote registry to deploy locally to our Kubernetes cluster. So let's go ahead and look everything's up and running, perfect. So what does that look like, right? So luckily, I'm using traefik for Ingress 'cause I love it. And I've got an object in my Kubernetes YAML called flask.doctor.life. That's my Ingress object for traefik. I can go to flask.docker.life. And I can hit refresh. Obviously, I'm not a very good web designer 'cause the background image in the text. We can go ahead and refresh it a couple times we've got Redis storing a hit counter. We can see that our server name is roundrobing. Okay? That's kind of cool. So let's kind of recap a little bit about my demo environment. So my demo environment, I'm using DigitalOcean, Ubuntu 19.10 Vms. I'm using K3s instead of full Kubernetes either full Rancher, full Open Shift or Docker Enterprise. I think K3s has some really interesting advantages on the development side and it's kind of intended for IoT but it works really well and it deploys super easy. I'm using traefik for Ingress. I love traefik. I may or may not be a traefik ambassador. I'm using Jenkins for CI. And I'm using StackRox for image scanning and policy enforcement. One of the things to think about though, especially in terms of labels is none of this demo stack is required. You can be in any cloud, you can be in CentOs, you can be in any Kubernetes. You can even be in swarm, if you wanted to, or Docker compose. Any Ingress, any CI system, Jenkins, circle, GitLab, it doesn't matter. And pretty much any scanning. One of the things that I think is kind of nice about at least StackRox is that we do a lot more than just image scanning, right? With the policy enforcement things like that. I guess that's kind of a shameless plug. But again, any of this stack is completely replaceable, with any comparative product in that category. So I'd like to, again, point you guys to the andyc.infodc20, that's take you right to the GitHub repo. You can reach out to me at any of the socials @clemenko or andy@stackrox.com. And thank you for attending. I hope you learned something fun about labels. And hopefully you guys can standardize labels in your organization and really kind of take your images and the image provenance to a new level. Thanks for watching. (upbeat music) >> Narrator: Live from Las Vegas It's theCUBE. Covering AWS re:Invent 2019. Brought to you by Amazon Web Services and Intel along with it's ecosystem partners. >> Okay, welcome back everyone theCUBE's live coverage of AWS re:Invent 2019. This is theCUBE's 7th year covering Amazon re:Invent. It's their 8th year of the conference. I want to just shout out to Intel for their sponsorship for these two amazing sets. Without their support we wouldn't be able to bring our mission of great content to you. I'm John Furrier. Stu Miniman. We're here with the chief of AWS, the chief executive officer Andy Jassy. Tech athlete in and of himself three hour Keynotes. Welcome to theCUBE again, great to see you. >> Great to be here, thanks for having me guys. >> Congratulations on a great show a lot of great buzz. >> Andy: Thank you. >> A lot of good stuff. Your Keynote was phenomenal. You get right into it, you giddy up right into it as you say, three hours, thirty announcements. You guys do a lot, but what I liked, the new addition, the last year and this year is the band; house band. They're pretty good. >> Andy: They're good right? >> They hit the queen notes, so that keeps it balanced. So we're going to work on getting a band for theCUBE. >> Awesome. >> So if I have to ask you, what's your walk up song, what would it be? >> There's so many choices, it depends on what kind of mood I'm in. But, uh, maybe Times Like These by the Foo Fighters. >> John: Alright. >> These are unusual times right now. >> Foo Fighters playing at the Amazon Intersect Show. >> Yes they are. >> Good plug Andy. >> Headlining. >> Very clever >> Always getting a good plug in there. >> My very favorite band. Well congratulations on the Intersect you got a lot going on. Intersect is a music festival, I'll get to that in a second But, I think the big news for me is two things, obviously we had a one-on-one exclusive interview and you laid out, essentially what looks like was going to be your Keynote, and it was. Transformation- >> Andy: Thank you for the practice. (Laughter) >> John: I'm glad to practice, use me anytime. >> Yeah. >> And I like to appreciate the comments on Jedi on the record, that was great. But I think the transformation story's a very real one, but the NFL news you guys just announced, to me, was so much fun and relevant. You had the Commissioner of NFL on stage with you talking about a strategic partnership. That is as top down, aggressive goal as you could get to have Rodger Goodell fly to a tech conference to sit with you and then bring his team talk about the deal. >> Well, ya know, we've been partners with the NFL for a while with the Next Gen Stats that they use on all their telecasts and one of the things I really like about Roger is that he's very curious and very interested in technology and the first couple times I spoke with him he asked me so many questions about ways the NFL might be able to use the Cloud and digital transformation to transform their various experiences and he's always said if you have a creative idea or something you think that could change the world for us, just call me he said or text me or email me and I'll call you back within 24 hours. And so, we've spent the better part of the last year talking about a lot of really interesting, strategic ways that they can evolve their experience both for fans, as well as their players and the Player Health and Safety Initiative, it's so important in sports and particularly important with the NFL given the nature of the sport and they've always had a focus on it, but what you can do with computer vision and machine learning algorithms and then building a digital athlete which is really like a digital twin of each athlete so you understand, what does it look like when they're healthy and compare that when it looks like they may not be healthy and be able to simulate all kinds of different combinations of player hits and angles and different plays so that you could try to predict injuries and predict the right equipment you need before there's a problem can be really transformational so we're super excited about it. >> Did you guys come up with the idea or was it a collaboration between them? >> It was really a collaboration. I mean they, look, they are very focused on players safety and health and it's a big deal for their- you know, they have two main constituents the players and fans and they care deeply about the players and it's a-it's a hard problem in a sport like Football, I mean, you watch it. >> Yeah, and I got to say it does point out the use cases of what you guys are promoting heavily at the show here of the SageMaker Studio, which was a big part of your Keynote, where they have all this data. >> Andy: Right. >> And they're data hoarders, they hoard data but the manual process of going through the data was a killer problem. This is consistent with a lot of the enterprises that are out there, they have more data than they even know. So this seems to be a big part of the strategy. How do you get the customers to actually wake up to the fact that they got all this data and how do you tie that together? >> I think in almost every company they know they have a lot of data. And there are always pockets of people who want to do something with it. But, when you're going to make these really big leaps forward; these transformations, the things like Volkswagen is doing where they're reinventing their factories and their manufacturing process or the NFL where they're going to radically transform how they do players uh, health and safety. It starts top down and if the senior leader isn't convicted about wanting to take that leap forward and trying something different and organizing the data differently and organizing the team differently and using machine learning and getting help from us and building algorithms and building some muscle inside the company it just doesn't happen because it's not in the normal machinery of what most companies do. And so it always, almost always, starts top down. Sometimes it can be the Commissioner or CEO sometimes it can be the CIO but it has to be senior level conviction or it doesn't get off the ground. >> And the business model impact has to be real. For NFL, they know concussions, hurting their youth pipe-lining, this is a huge issue for them. This is their business model. >> They lose even more players to lower extremity injuries. And so just the notion of trying to be able to predict injuries and, you know, the impact it can have on rules and the impact it can have on the equipment they use, it's a huge game changer when they look at the next 10 to 20 years. >> Alright, love geeking out on the NFL but Andy, you know- >> No more NFL talk? >> Off camera how about we talk? >> Nobody talks about the Giants being 2 and 10. >> Stu: We're both Patriots fans here. >> People bring up the undefeated season. >> So Andy- >> Everybody's a Patriot's fan now. (Laughter) >> It's fascinating to watch uh, you and your three hour uh, Keynote, uh Werner in his you know, architectural discussion, really showed how AWS is really extending its reach, you know, it's not just a place. For a few years people have been talking about you know, Cloud is an operational model its not a destination or a location but, I felt it really was laid out is you talked about Breadth and Depth and Werner really talked about you know, Architectural differentiation. People talk about Cloud, but there are very-there are a lot of differences between the vision for where things are going. Help us understand why, I mean, Amazon's vision is still a bit different from what other people talk about where this whole Cloud expansion, journey, put ever what tag or label you want on it but you know, the control plane and the technology that you're building and where you see that going. >> Well I think that, we've talked about this a couple times we have two macro types of customers. We have those that really want to get at the low level building blocks and stitch them together creatively however they see fit to create whatever's in their-in their heads. And then we have the second segment of customers that say look, I'm willing to give up some of that flexibility in exchange for getting 80% of the way there much faster. In an abstraction that's different from those low level building blocks. And both segments of builders we want to serve and serve well and so we've built very significant offerings in both areas. I think when you look at microservices um, you know, some of it has to do with the fact that we have this very strongly held belief born out of several years of Amazon where you know, the first 7 or 8 years of Amazon's consumer business we basically jumbled together all of the parts of our technology in moving really quickly and when we wanted to move quickly where you had to impact multiple internal development teams it was so long because it was this big ball, this big monolithic piece. And we got religion about that in trying to move faster in the consumer business and having to tease those pieces apart. And it really was a lot of impetus behind conceiving AWS where it was these low level, very flexible building blocks that6 don't try and make all the decisions for customers they get to make them themselves. And some of the microservices that you saw Werner talking about just, you know, for instance, what we-what we did with Nitro or even what we did with Firecracker those are very much about us relentlessly working to continue to uh, tease apart the different components. And even things that look like low level building blocks over time, you build more and more features and all of the sudden you realize they have a lot of things that are combined together that you wished weren't that slow you down and so, Nitro was a completely re imagining of our Hypervisor and Virtualization layer to allow us, both to let customers have better performance but also to let us move faster and have a better security story for our customers. >> I got to ask you the question around transformation because I think that all points, all the data points, you got all the references, Goldman Sachs on stage at the Keynote, Cerner, I mean healthcare just is an amazing example because I mean, that's demonstrating real value there there's no excuse. I talked to someone who wouldn't be named last night, in and around the area said, the CIA has a cost bar like this a cost-a budget like this but the demand for mission based apps is going up exponentially, so there's need for the Cloud. And so, you see more and more of that. What is your top down, aggressive goals to fill that solution base because you're also a very transformational thinker; what is your-what is your aggressive top down goals for your organization because you're serving a market with trillions of dollars of spend that's shifting, that's on the table. >> Yeah. >> A lot of competition now sees it too, they're going to go after it. But at the end of the day you have customers that have a demand for things, apps. >> Andy: Yeah. >> And not a lot of budget increase at the same time. This is a huge dynamic. >> Yeah. >> John: What's your goals? >> You know I think that at a high level our top down aggressive goals are that we want every single customer who uses our platform to have an outstanding customer experience. And we want that outstanding customer experience in part is that their operational performance and their security are outstanding, but also that it allows them to build, uh, build projects and initiatives that change their customer experience and allow them to be a sustainable successful business over a long period of time. And then, we also really want to be the technology infrastructure platform under all the applications that people build. And we're realistic, we know that you know, the market segments we address with infrastructure, software, hardware, and data center services globally are trillions of dollars in the long term and it won't only be us, but we have that goal of wanting to serve every application and that requires not just the security operational premise but also a lot of functionality and a lot of capability. We have by far the most amount of capability out there and yet I would tell you, we have 3 to 5 years of items on our roadmap that customers want us to add. And that's just what we know today. >> And Andy, underneath the covers you've been going through some transformation. When we talked a couple of years ago, about how serverless is impacting things I've heard that that's actually, in many ways, glue behind the two pizza teams to work between organizations. Talk about how the internal transformations are happening. How that impacts your discussions with customers that are going through that transformation. >> Well, I mean, there's a lot of- a lot of the technology we build comes from things that we're doing ourselves you know? And that we're learning ourselves. It's kind of how we started thinking about microservices, serverless too, we saw the need, you know, we would have we would build all these functions that when some kind of object came into an object store we would spin up, compute, all those tasks would take like, 3 or 4 hundred milliseconds then we'd spin it back down and yet, we'd have to keep a cluster up in multiple availability zones because we needed that fault tolerance and it was- we just said this is wasteful and, that's part of how we came up with Lambda and you know, when we were thinking about Lambda people understandably said, well if we build Lambda and we build this serverless adventure in computing a lot of people were keeping clusters of instances aren't going to use them anymore it's going to lead to less absolute revenue for us. But we, we have learned this lesson over the last 20 years at Amazon which is, if it's something that's good for customers you're much better off cannibalizing yourself and doing the right thing for customers and being part of shaping something. And I think if you look at the history of technology you always build things and people say well, that's going to cannibalize this and people are going to spend less money, what really ends up happening is they spend less money per unit of compute but it allows them to do so much more that they ultimately, long term, end up being more significant customers. >> I mean, you are like beating the drum all the time. Customers, what they say, we encompass the roadmap, I got that you guys have that playbook down, that's been really successful for you. >> Andy: Yeah. >> Two years ago you told me machine learning was really important to you because your customers told you. What's the next traunch of importance for customers? What's on top of mind now, as you, look at- >> Andy: Yeah. >> This re:Invent kind of coming to a close, Replay's tonight, you had conversations, you're a tech athlete, you're running around, doing speeches, talking to customers. What's that next hill from if it's machine learning today- >> There's so much I mean, (weird background noise) >> It's not a soup question (Laughter) And I think we're still in the very early days of machine learning it's not like most companies have mastered it yet even though they're using it much more then they did in the past. But, you know, I think machine learning for sure I think the Edge for sure, I think that um, we're optimistic about Quantum Computing even though I think it'll be a few years before it's really broadly useful. We're very um, enthusiastic about robotics. I think the amount of functions that are going to be done by these- >> Yeah. >> robotic applications are much more expansive than people realize. It doesn't mean humans won't have jobs, they're just going to work on things that are more value added. We're believers in augmented virtual reality, we're big believers in what's going to happen with Voice. And I'm also uh, I think sometimes people get bored you know, I think you're even bored with machine learning already >> Not yet. >> People get bored with the things you've heard about but, I think just what we've done with the Chips you know, in terms of giving people 40% better price performance in the latest generation of X86 processors. It's pretty unbelievable in the difference in what people are going to be able to do. Or just look at big data I mean, big data, we haven't gotten through big data where people have totally solved it. The amount of data that companies want to store, process, analyze, is exponentially larger than it was a few years ago and it will, I think, exponentially increase again in the next few years. You need different tools and services. >> Well I think we're not bored with machine learning we're excited to get started because we have all this data from the video and you guys got SageMaker. >> Andy: Yeah. >> We call it the stairway to machine learning heaven. >> Andy: Yeah. >> You start with the data, move up, knock- >> You guys are very sophisticated with what you do with technology and machine learning and there's so much I mean, we're just kind of, again, in such early innings. And I think that, it was so- before SageMaker, it was so hard for everyday developers and data scientists to build models but the combination of SageMaker and what's happened with thousands of companies standardizing on it the last two years, plus now SageMaker studio, giant leap forward. >> Well, we hope to use the data to transform our experience with our audience. And we're on Amazon Cloud so we really appreciate that. >> Andy: Yeah. >> And appreciate your support- >> Andy: Yeah, of course. >> John: With Amazon and get that machine learning going a little faster for us, that would be better. >> If you have requests I'm interested, yeah. >> So Andy, you talked about that you've got the customers that are builders and the customers that need simplification. Traditionally when you get into the, you know, the heart of the majority of adoption of something you really need to simplify that environment. But when I think about the successful enterprise of the future, they need to be builders. how'l I normally would've said enterprise want to pay for solutions because they don't have the skill set but, if they're going to succeed in this new economy they need to go through that transformation >> Andy: Yeah. >> That you talk to, so, I mean, are we in just a total new era when we look back will this be different than some of these previous waves? >> It's a really good question Stu, and I don't think there's a simple answer to it. I think that a lot of enterprises in some ways, I think wish that they could just skip the low level building blocks and only operate at that higher level abstraction. That's why people were so excited by things like, SageMaker, or CodeGuru, or Kendra, or Contact Lens, these are all services that allow them to just send us data and then run it on our models and get back the answers. But I think one of the big trends that we see with enterprises is that they are taking more and more of their development in house and they are wanting to operate more and more like startups. I think that they admire what companies like AirBnB and Pintrest and Slack and Robinhood and a whole bunch of those companies, Stripe, have done and so when, you know, I think you go through these phases and eras where there are waves of success at different companies and then others want to follow that success and replicate it. And so, we see more and more enterprises saying we need to take back a lot of that development in house. And as they do that, and as they add more developers those developers in most cases like to deal with the building blocks. And they have a lot of ideas on how they can creatively stich them together. >> Yeah, on that point, I want to just quickly ask you on Amazon versus other Clouds because you made a comment to me in our interview about how hard it is to provide a service to other people. And it's hard to have a service that you're using yourself and turn that around and the most quoted line of my story was, the compression algorithm- there's no compression algorithm for experience. Which to me, is the diseconomies of scale for taking shortcuts. >> Andy: Yeah. And so I think this is a really interesting point, just add some color commentary because I think this is a fundamental difference between AWS and others because you guys have a trajectory over the years of serving, at scale, customers wherever they are, whatever they want to do, now you got microservices. >> Yeah. >> John: It's even more complex. That's hard. >> Yeah. >> John: Talk about that. >> I think there are a few elements to that notion of there's no compression algorithm for experience and I think the first thing to know about AWS which is different is, we just come from a different heritage and a different background. We ran a business for a long time that was our sole business that was a consumer retail business that was very low margin. And so, we had to operate at very large scale given how many people were using us but also, we had to run infrastructure services deep in the stack, compute storage and database, and reliable scalable data centers at very low cost and margins. And so, when you look at our business it actually, today, I mean its, its a higher margin business in our retail business, its a lower margin business in software companies but at real scale, it's a high volume, relatively low margin business. And the way that you have to operate to be successful with those businesses and the things you have to think about and that DNA come from the type of operators we have to be in our consumer retail business. And there's nobody else in our space that does that. So, you know, the way that we think about costs, the way we think about innovation in the data center, um, and I also think the way that we operate services and how long we've been operating services as a company its a very different mindset than operating package software. Then you look at when uh, you think about some of the uh, issues in very large scale Cloud, you can't learn some of those lessons until you get to different elbows of the curve and scale. And so what I was telling you is, its really different to run your own platform for your own users where you get to tell them exactly how its going to be done. But that's not the way the real world works. I mean, we have millions of external customers who use us from every imaginable country and location whenever they want, without any warning, for lots of different use cases, and they have lots of design patterns and we don't get to tell them what to do. And so operating a Cloud like that, at a scale that's several times larger than the next few providers combined is a very different endeavor and a very different operating rigor. >> Well you got to keep raising the bar you guys do a great job, really impressed again. Another tsunami of announcements. In fact, you had to spill the beans earlier with Quantum the day before the event. Tight schedule. I got to ask you about the musical festival because, I think this is a very cool innovation. It's the inaugural Intersect conference. >> Yes. >> John: Which is not part of Replay, >> Yes. >> John: Which is the concert tonight. Its a whole new thing, big music act, you're a big music buff, your daughter's an artist. Why did you do this? What's the purpose? What's your goal? >> Yeah, it's an experiment. I think that what's happened is that re:Invent has gotten so big, we have 65 thousand people here, that to do the party, which we do every year, its like a 35-40 thousand person concert now. Which means you have to have a location that has multiple stages and, you know, we thought about it last year and when we were watching it and we said, we're kind of throwing, like, a 4 hour music festival right now. There's multiple stages, and its quite expensive to set up that set for a party and we said well, maybe we don't have to spend all that money for 4 hours and then rip it apart because actually the rent to keep those locations for another two days is much smaller than the cost of actually building multiple stages and so we thought we would try it this year. We're very passionate about music as a business and I think we-I think our customers feel like we've thrown a pretty good music party the last few years and we thought we would try it at a larger scale as an experiment. And if you look at the economics- >> At the headliners real quick. >> The Foo Fighters are headlining on Saturday night, Anderson Paak and the Free Nationals, Brandi Carlile, Shawn Mullins, um, Willy Porter, its a good set. Friday night its Beck and Kacey Musgraves so it's a really great set of um, about thirty artists and we're hopeful that if we can build a great experience that people will want to attend that we can do it at scale and it might be something that both pays for itself and maybe, helps pay for re:Invent too overtime and you know, I think that we're also thinking about it as not just a music concert and festival the reason we named it Intersect is that we want an intersection of music genres and people and ethnicities and age groups and art and technology all there together and this will be the first year we try it, its an experiment and we're really excited about it. >> Well I'm gone, congratulations on all your success and I want to thank you we've been 7 years here at re:Invent we've been documenting the history. You got two sets now, one set upstairs. So appreciate you. >> theCUBE is part of re:Invent, you know, you guys really are apart of the event and we really appreciate your coming here and I know people appreciate the content you create as well. >> And we just launched CUBE365 on Amazon Marketplace built on AWS so thanks for letting us- >> Very cool >> John: Build on the platform. appreciate it. >> Thanks for having me guys, I appreciate it. >> Andy Jassy the CEO of AWS here inside theCUBE, it's our 7th year covering and documenting the thunderous innovation that Amazon's doing they're really doing amazing work building out the new technologies here in the Cloud computing world. I'm John Furrier, Stu Miniman, be right back with more after this short break. (Outro music)

>> Announcer: From Miami Beach, Florida, it's The Cube, covering Acronis Global Cyber Summit 2019. Brought to you by Acronis. >> Welcome back everyone. We are here with The Cube coverage for two days. We're wrapping up, getting down on day one in the books for the Acronis Global Cyber Summit 2019. I'm John Furrier, your host of The Cube. We are in Miami Beach, the Fontainebleau Hotel. I'm personally excited for this next guest because I'm a huge Red Sox fan, even though I got moved out to California. Giants is in a different area. National League is different than American League, still my heart with the Red Sox. And we're here with an industry veteran, seasoned professional in IT and data, Brian Shield. Boston Red Sox Vice President of Technology and IT. Welcome to The Cube, thanks for joining us. >> Thank you. It's great to be here. >> John: So congratulations on the rings. Since I moved out of town, Red sox win their World Series, break the curse of the Bambino. >> Hey we appreciate that. Thank you. >> My family doesn't want me back. You got to show >> Yeah, maybe I'll put this one up for the, maybe someone can zoom in on this. Which camera is the good one? This one here? So, there ya go. So, World Series champs for at least for another week. (laughter) >> Bummer about this year. Pitching just couldn't get it done. But, good team. >> Happens. >> Again, things move on, but you know. New regime, new GM going to come on board. >> Yup. >> So, but in general, Red Sox, storied franchise. Love it there. Fenway Park, the cathedral of baseball parks. >> Brian: Defnitely. >> And you're seeing that just play out now, standard. So just a great place to go. We have tickets there. So, I got to ask you. Technology, sports, really is modernized faster than I think any category. And certainly cyber security forced to modernize because of the threats. But sports, you got a business to run, not just IT and making the planes run on time. >> Sure. >> Scouts, money, whatever. >> Fans. >> You got fan experience. >> Stadium opportunities. >> Club management, scouts are out there. So you got business, team, fans. And data's a big part of it. That's part of your career. Tell us what the cutting edge innovation is at the Red Sox these days. >> I think baseball in general, as you indicated, it's a very evolving kind of environment. I mean historically I think people really sort of relish the nostalgia of sports and Fenway Park being as historic as it is, was probably the pinnacle of that, in some respects. But Red Sox have always been leaders and baseball analytics, you know. And everyone's pretty familiar with "Moneyball" and Brad Pitt. >> John: Is that a true story, he turned down the GM job? >> I'm told it is. (laughter) I don't know if I fully vetted that question. But over the last six, seven years, you know we've really turned our attention to sort of leveraging sort of technology across the businesses, right? Not just baseball and analytics and how we do scouting, which continues to evolve at a very rapid pace. But also as you pointed out, running a better business, understanding our fans, understanding fan behavior, understanding stadiums. There's a lot of challenges around running an effective stadium. First and foremost to all of us is really ensuring it's a great fan experience. Whether it's artificial intelligence, or IoT technologies or 5G or the latest Wifi, all those things are coming up at Fenway Park. You and I talked earlier about we're about to break ground for a new theater, so a live theater on the outside, beyond the bleachers type of thing. So that'll be a 5,400-seat arena, 200 live performances a year, and with e-sports, you know, complementing it. It just gives you an example of just how fast baseball is sort of transitioning. >> And the theater, is that going to be blown out from where that parking garage is, structure and going towards >> So the corner of Landsdown and Ipswich, if you think of that sort of corner back there, for those that are familiar with the Fenway area. So it's going to be a very big change and you'll see the difference too from within the ballpark. I think we'll lose a couple of rows of the bleachers. That'll be replaced with another gathering area for fans and things like that, on the back end of that theater. So build a great experience and I think it really speaks to sort of our ability to think of Fenway as more of a destination, as a venue, as a complementary experience. We want people to come to the area to enjoy sports and to enjoy entertainment and things. >> You know Brian, the consumerization of IT has been kicked around. Last decade, that was a big buzzword. Now the blending of a physical event and digital has certainly consumed the world. >> Absolutely. >> And we're starting to see that dynamic. You speak to a theater. That's a physical space. But digital is also a big part of kind of that complementary. It's not mutually exclusive for each other. They're integrated business models. >> Absolutely. >> So therefore, the technology has to be seamless. The data has to be available. >> Yup. >> And it's got to be secure. >> Well the data's got to be ubiquitous, right? I mean you don't want to, if we're going to have fans attending theater and then you're going to go to Fenway Park or they leave a game and then go to some other event or they attend a tour of Fenway Park, and beyond maybe the traditional what people might think about, is certainly when you think about baseball and Fenway Park. You know we have ten to twelve concerts a year. We'll host Spartan games, you know. This Christmas, I'm sorry, Christmas 2020 we now have sort of the Fenway Bowl. So we'll be hosting the AAC ACC championship games there with ESPN. >> John: Hockey games? >> Hockey games. Obviously we have Liverpool soccer being held there so it's much more of a destination, a venue for us. How we leverage all the wonderful things about Fenway Park and how we modernize, how we get basically the best of what makes Fenway Park as great as it is, yet as modern as we can make it, where appropriate to create a great fan experience. >> It's a tough balance between balancing the brand and having things on brand as well. >> Sure. >> Does that come into your job a lot around IT? Saying being on brand, not kind of tearing down the old. >> Yeah absolutely. I think our CEOs and leadership team, I mean it's not success for us if you pan to the audience and everyone is looking at their phone, right? That's not what we aspire to. We aspire to leverage technology to simplify people's experience of how do you get to the ballpark, how do I park, how do I get if I want to buy concessions or merchandise, how do I do it easily and simply? How do we supplement that experience with maybe additional data that you may not have had before. Things like that, so we're doing a lot of different testing right now whether it's 4D technologies or how we can understand, watch a play from different dimensions or AI and be able to perhaps see sort of the skyline of Boston since 1912, when Fenway Park launched... And so we sort of see all these technologies as supplemental materials, really kind of making it a holistic experience for fans. >> In Las Vegas, they have a section of Las Vegas where they have all their test beds. 5G, they call it 5G, it's really, you know, evolution, fake 5G but it's a sandbox. One of the challenges that you guys have in Boston, I know from a constraint standpoint physically, you don't have a lot of space. How do you sandbox new technologies and what are some of the things that are cool that people might not know about that are being sandboxed? So, one, how do you do it? >> Yeah. >> Effectively. And then what are some of the cool things that you guys are looking at or things they might not know about that would be interesting. >> Sure. Yeah so Fenway Park, we struggle as you know, a little bit with our footprint. You know, honestly, I walk into some of these large stadiums and I get instant jealousy, relative to just the amount of space that people have to work with and things. But we have a great relationship with our partners so we really partner, I think, particularly well with key partners like Verizon and others. So we now have 5G partially implemented at Fenway Park. We expect to have it sort of fully live come opening day next year. So we're really excited about that. We hope to have a new version of Wifi, the latest version of Wifi available, for the second half of the year. After the All-Star Break, probably after the season's over. But before our bowl game hopefully. We're looking at some really interesting ways that we can tease that out. That bowl game, we're really trying to use that as an opportunity, the Fenway Bowl, as an opportunity to make it kind of a high-tech bowl. So we're looking at ways of maybe doing everything from hack-a-thons to a pre-egaming sort of event to some interesting fan experiential opportunities and things like that. >> Got a lot of nerds at MIT, Northeastern, BU, Bentley, Babson, all the schools in the area. >> Yeah, so we'll be reaching out to colleges and we'll be reaching out to our, the ACC and AACs as well, and see what we can do to kind of create sort of a really fun experience and capitalize on the evolving role of e-sports and the role that technology can play in the future. >> I want to get to the e-sports in a second but I want to just get the plug in for Acronis. We're here at their Global Cyber Summit. You flew down for it, giving some keynote speeches and talks around security. It's a security company, data protection, to cyber protection. It is a data problem, not a storage appliance problem. It's a data problem holistically. You get that. >> Sure. Sure. >> You've been in the business for a long time. What is the security kind of posture that you guys have? Obviously you want to protect the data, protect privacy. But you got to business. You have people that work with you, supply chain, complex but yet dynamic, always on environment. >> That's a great question. It's evolving as you indicated. Major League Baseball, first and foremost, does an outstanding job. So the last, probably last four plus years, Major League Baseball has had a cyber security program that all the clubs partake in. So all 30 clubs are active participants in the program. They basically help build out a suite of tools as well as the ability to kind of monitor, help participate in the monitoring, sort of a lot of our cyber security assets and logs And that's really elevated significantly our posture in terms of security. We supplement that quite a bit and a good example of that is like Acronis. Acronis, for us, represents the ability for us to be able to respond to certain potential threats like ransom-ware and other things. As well as frankly, what's wonderful about a tool like this is that it allows us to also solve other problems. Making our scouts more efficient. We've got these 125 scouts scattered around the globe. These guys are the lifeblood of our, you know, the success of our business. When they have a problem, if they're in Venezuela or the Dominican or someplace else, in southeast Asia, getting them up and running as quickly as we can, being able to consume their video assets and other things as they're scouting prospects. We use Acronis for those solutions. It's great to kind of have a partner who can both double down as a cyber partner as well as someone who helps drive a more efficient business. >> People bring their phone into the stadiums too so those are end points now connecting to your network. >> Definitely. And as you pointed out before, we've got great partnerships. We've got a great concession relationship with Aramark and they operate, in the future they'll be operating off our infrastructure. So we're in the point of rolling out all new point-of-sale terminals this off-season. We're excited about that 'cause we think for the first time it really allows us to build a very comprehensive, very secure environment for both ourselves and for all the touchpoints to fans. >> You have a very stellar career. I noticed you were at Scudder Investments back in the '80s, very cutting-edge firm. FTD that set the whole standard for connecting retailers. Again, huge scale play. Can see the data kind of coming out, they way you've been a CIO, CTO. The EVP CIO at The Weather Channel and the weather.com again, first mover, kind of pioneer. And then now the Red Sox, pioneering. So I got to ask you the modernization question. Red Sox certainly have been cutting-edge, certainly under the last few owners, and the previous Henry is a good one, doing more and more, Has the business model of baseball evolved, 'cause you guys a franchise. >> Sure. >> You operate under the franchisor, Major League Baseball, and you have jurisdictions. So has digital blurred the lines between what Advanced Media unit can do. You got communities developing outside. I watch the games in California. I'm not in there but I'm present digitally. >> Sure. Sure. >> So how has the business model flexed with the innovation of baseball? >> That's a great question. So I mean, first off, the relationship between clubs like ours and MLB continue to evolve. We have a new commissioner, relatively new commissioner, and I think the whole one-baseball model that he's been promoting I think has been great. The boundaries sometimes between digital assets and how we innovate and things like that continues to evolve. Major League Baseball and technology groups and product groups that support Major League Baseball have been a fantastic partner of ours. If you look at some of the innovations with Statcast and some of the other types of things that fans are now becoming more familiar with. And when they see how fast a runner goes or how far a home run goes and all those sort of things, these kinds of capabilities are on the surface, but even like mobile applications, to make it easy for fans to come into ballparks and things like that really. What we see is really are platforms for the future touchpoints to all of our customers. But you're right, it gets complicated. Streaming videos and people hadn't thought of before. >> Latin America, huge audience for the Red Sox. Got great players down there. That's outside the jurisdiction, I think, of the franchise agreement, isn't it? (laughs) >> Well, it's complicated. As this past summer, we played two games in England, right? So we enjoy two games in London, sadly we lost to the Yankees in both of those, but amazing experience and Major League Baseball really hats off to those guys, what they did to kind of pull that together. >> You mentioned Statcast. Every year when I meet with Andy Jassy at AWS, he's a sports fan. We love to talk sports. That's a huge, kind of shows the power of data and cloud computing. >> No doubt. >> How do you guys interface with Statcast? Is that an Amazon thing? Do they come to you? Are they leveraging dimensions, camera angles? How does that all work? Are you guys involved in that or? >> Brian: Oh yeah, yeah. >> Is that separate? >> So Statcast is just one of many data feeds as you can imagine. One of the things that Major League Baseball does is all that type of data is readily available to every club. So every club has access to the data. The real competitive differentiator, if you will, is how you use it internally. Like how your analysts can consume that data. We have a baseball system we call Beacon. We retired Carmine, if you're familiar with the old days of Carmine. So we retired Carmine a few years ago with Beacon. And Beacon for us represents sort of our opportunity to effectively collapse all this information into a decision-making environment that allows us to hopefully to kind of make the best decisions to win the most games. >> I love that you're answering all these questions. I really appreciate it. The one I really want to get into is obviously the fan experience. We talked about that. No talent on the field means no World Series so you got to always be constantly replenishing the talent pool, farm system, recruiting, scouting, all these things go on. They're instrumental. Data's a key driver. What new innovations that the casual fan or IT person might be interested in what's going on around scouting and understanding the asset of a human being? >> Right. Sure. I mean some of this gets highly confidential and things, but I think at a macro level, as you start to see both in the minor leagues and in some portions of the major leagues, wearable technologies. I think beyond just sort of player performance information that you would see traditionally with you might associate it with like Billy Beane, and things like that with "Moneyball" which is evolved obviously considerably since those days. I mean understanding sort of player wellness, understanding sort of how to get the most out of a player and understanding sort of, be able to kind of predict potential injuries and accelerate recoveries and being able to use all of this technology where appropriate to really kind of help sort of maximize the value of player performance. I mean, David Ortiz, you know, I don't know where we would have been in 2018 without, you know, David. >> John: Yeah. >> But like, you know >> Longevity of a player. >> Absolutely. >> To when they're in the zone. You wear a ring now to tell you if you're sleeping well. Will managers have a visual, in-the-zone, don't pull 'em out, he can go an extra inning? >> Well, I mean they have a lot of data. We currently don't provide all that data to the clubhouse. I mean, you know, and so If you're in the dugout, that information isn't always readily available type of thing. But players know all this information. We continue to evolve it. At the end of the day though, it's finding the balancing act between data and the aptitudes of our coaching staff and our managers to really make the wise decisions. >> Brian, final question for you. What's the coolest thing you're working on right now? Besides the fan having a great experience, 'cause that's you kind of touched on that. What's the coolest thing that you're excited about that you're working on from a tech perspective that you think is going to be game-changing or interesting? >> I think our cloud strategy coming up in the future. It's still a little bit early stage, but our hope would be to kind of have clarity about that in the next couple months. I think is going to be a game-changer for us. I think having, you know, we enjoy a great relationship with Dell EMC and yet we also do work in the cloud and so being able to leverage the best of both of those to be able to kind of create sort of a compelling experience for both fans, for both player, baseball operations as well as sort of running an efficient business, I think is really what we're all about. >> I mean you guys are the poster child for hybrid cloud because you got core, data center, IoT, and >> No doubt. So it's exciting times. And we're very fortunate that with our relationship organizations like Dell and EMC, we have leading-edge technologies. So we're excited about where that can go and kind of what that can mean. It'll be a big step. >> Okay two personal questions from me as a fan. One is there really a money-counting room like in the movie "The Town"? Where they count a big stack of dollar bills. >> Well, I'm sure there is. I personally haven't visited it. (laughs) I know it's not in the room that they would tell you it is on the movie. (laughter) >> And finally, can The Cube get press passes to cover the games, next to NESN? Talk tech. >> Yeah, we'll see what we can do. >> They can talk baseball. We can talk about bandwidth. Right now, it's the level five conductivity. We're looking good on the pipes. >> Yeah we'll give you a tech tour. And you guys can sort of help us articulate all that to the fans. >> Thank you so much. Brian Shield, Vice President of Technology of the Boston Red Sox. Here talking about security and also the complications and challenges but the mega-opportunities around what digital and fan experiences are with the physical product like baseball, encapsulates kind of the digital revolution that's happening. So keep covering it. Here in Miami, I'm John Furrier. We'll be right back after this short break. (techno music)

>> Narrator: Live from Orlando, Florida, it's The Cube, covering PentahoWorld 2017. Brought to you by Hitachi Ventara. >> Welcome back to The Cube's live coverage of PentahoWorld, brought to you, of course, by Hitachi Ventara. I'm your host, Rebecca Knight, along with my cohost, Dave Vellante. We're joined by Reni Waegelein, he is the IT manager of Veikkaus. Thanks so much for coming on The Cube Reni. >> Thank you for having me here. >> So, Veikkaus is the Finnish national betting agency wholly owned by the government. >> Yeah. >> Tell us more. >> Yeah we have, we used to have like three companies, now we are merged as one and we operate every money gaming thing, all the money gaming in Finland. So that includes from casino to lottery, to scratch tickets, sports betting, horse betting, whatever that is, and we gather money, of course, pay out some good winnings as well. But everything we make under the line, that goes to good causes, and I mean everything. >> And you are IT manager. >> Reni: Yeah. >> So what does, what are your responsibilities? >> Yeah, responsibilities like the developing the whole of the idea things we have, from architecture to doing the IT procurement development, and harnessing how we work. >> So the public policy on betting is, hey, let's have a single state-run monopoly. >> Reni: Yep. >> And we'll take the winnings and put it to the public good, right, makes sense. >> Reni: Yep. >> And is there any competition from internet, for example? >> Of course, yes, and the internet, well, it's like a full competition, although we are a legally-based company in Finland and we operate and sell only to Finnish people. The people itself, they have all the freedom to choose whoever they want to play with, so in that sense, it's full competition and have been so for many years. >> So you have to have great websites. >> Reni: Yep. >> Great customer experience, >> Reni: Yep. >> User experience. >> Reni: Yeah. >> Competitive rates, all that stuff. >> Reni: Yep. >> Okay so, and good analytics. (laughing) I mean that industry is obviously very data heavy. >> Reni: Yep. >> Always has been. So how do you analytics and data to compete? >> So we have been doing, like, the product analytics for quite a long time and then we established a customer-ship. So in Finland we have a 5.4 million habitats, and we sell only for the 18+ year old people, and at the moment we have more than 2 million registered customers already. So, you can imagine that we have that vast amount of data from the customer, and we use that data, for example, promoting the service, promoting games, targeting, making some recommendation. We build our own recommendation engine, for example, and utilize all of that kind of data. But, as you know, the gaming is also like a two-edged sword, that's a happy side, but there's also the dark side. So it does cause problem, so we try also to use the data so that we want to identify the bad patterns when somebody is about to lose control of gaming. So we use also the same data that we want to see, for example, for these players who want to see all the activities of marketing, for example, we don't want anybody to get into problems because of gaming. >> So that's a really interesting tension here, is that you obviously want to make money in this, but you also have to watch out for the Finnish society. And as you said, if there's a compulsive gambler or an addicted gambler, you need to act, I mean, is that? >> Yeah, yeah that's really big part of our responsibility, and if we didn't have any data or if we couldn't process it fast, we couldn't know who is problematic gambler and who is not. Since vast majorities, of course, is enjoying it, it's a nice habit. Play a game of poker every now and then or go to the casino for once or twice a month, for example. But then there's the small portion of people who we want to protect so that they don't get into the debt. That's not our intention. >> And the level of protection that you provide, is you stop marketing to them, is that right or? >> Reni: Yeah, yeah. >> It's not like you intervene in some other way. >> Yeah, of course, we want to promote that if you want, you can stop and close your account, or this kind of activities. >> So you promote cutting the cord basically? >> Yeah, yeah, yeah. So instead of marketing, we say that this might be a problem to use, so yeah. >> Let's take a break. >> You should take a break, yeah. >> So, as Dave was saying, you're really, because you are competing with private entities you really have to have a great interface, great customer experience, great rates. How much does this put Veikkaus really on the vanguard of this kind of technology, more so than what other government agencies are doing, in the sense that, you really have to stay on the cutting edge of these things. >> Yeah, we have to be like double-backed, you say. >> So how much do you then you talk to the health agency, or other government agencies about what you're doing and sharing the best practices about capturing customer attention? >> We are actually talking more to the new players out in the field who already live and breath true to data, so that's where we can learn and, I would say that we are also in to like a lottery area itself but also in quite many other industries as well. So we have been doing this for awhile, so we have had the luxury that we have already gathered some experience and opened some paths and, well, maybe learned also from the hard way how not to do it. We of course didn't succeeded in the first runs but you just have to go and have a trial and error in some areas as well. >> And you have multiple data sources obviously, maybe talk about how you're handling those data sources, are you ingesting, how you ingest those into Pentaho, what you do with it, how you're operationalizing the analytics. Where does Pentaho fit in that whole process? >> Yeah Pentaho we use, that's like ETL process, so to get this 360 view of the customer, we have like a various data sources. After the merger, we tripled the amount of different sources, and I think more than quadrupled the amount of data. So of course, just to make the data and work of the analysts easier, we need to make some transformations to the data and in that area the Pentaho has it's place. And in the future, what we are also expecting like the future versions to help us with is the tech in the more real time data. So for example, we can put in the real time data feed for the one physical place so they can see like which machines are used well, which are not, or is there any other activities that they can learn right in their place. >> So are you in the process of instrumenting the machines at this point? >> Reni: Yep. >> And so you're putting, how does that work, is it rip and replace, is it some kind of chip that you put into the machine? How do you instrument the machine? >> It's a good thing, so that we have actually we design our own slot machines, even. >> Dave: Okay, okay so. >> So we, we can like build up from the ground up. >> Dave: Design it in. >> Yeah. We designed the hardware supports like, it's, they are big IOT machines. >> Dave: Right. >> But also the software will support us. >> And then you've got connectivity, is it hard-wired? Is it physical or is it wireless connectivity? >> We use, well, whatever is available, so... >> Dave: Depends. >> Yeah, yeah. And when we are developing like a new type of games, for example, when the slot machines should have like online all the time, like jackpot available, then of course, we have to think about what's the quality of service of the network, as well. So far, we have been like using whatever is available. >> So what does the data architecture look like? I wonder if you could paint the picture, so you've got the machines, let's just use slot machines as an example. So you have the slot machines, you've instrumented those, you're doing real time analytics there, and maybe talk about what kinds of things you do there? And then where does the data go? How much data, do you persist the data? Maybe talk about that a little. >> Yeah so we get like the slot machines and other resources as well, and have like Kafka Hadoop area where we collect everything. Then there's a Pentaho doing the ETL work and we store the, all the data that goes through it to the Vertica. So we have HP's Vertica there, in that Vertica they've like lots of users, they have like a SAS analytics, use that and the Hadoop as well, so then we have some reporting, financials, finance department they also utilize it. But then we are also building up some new things like Apache's Kudu is one thing that we want to set up there just to make the life of analysts much more easier so they are the moment having little bit hard time in some areas how to utilize the data, and especially how to use like the different analyst tools from different cloud vendors for this data since we are still at the moment on premise, so everything is on premise partly because of the government requirements. >> Dave: Okay. >> So some part of the data they require that we keep it in within the Finland. >> Right so could we call that your private cloud? >> Reni: It's not private cloud yet. >> It's not, okay. >> But we're, we are going. >> Dan: Someday. >> Yeah, yeah. >> It will be a private cloud, okay, so you have edge device, which is the slot machine, and then you do you send all the data back to Vertica or no, probably not, right, I mean. >> Not yet. >> Dave: But do you want to? >> But it will be. >> Dave: Really? >> Yeah, it will be. Of course we have to make some decision like what data will be important and what is not, so not all the data is valuable, but especially when it's like connected somehow to the customer, or the retailer as well, that data we also keep like more than a year. So we are not doing all the analytics just for a short time of data but also want to seek out the long trends and make new hypothesis out of it. >> And the Vertica system is essentially your data warehouse, is that right? >> Reni: Yeah. >> Okay. And then are you doing sort of, well you mentioned recommendation engine so you're doing some >> Reni: Yeah. form of it. That's a form of AI, as far as I'm concerned. Are you doing that, where are you doing that? Is you doing that in your data center, and is that another layer of the data pipeline or is that done in the? >> Yeah, it's done partly on site but also in AVS. >> Yeah >> So we used Amazon services in some areas where we can use those, so the recommendation for example, and part of the cost of AI, that's part, some blocks are also on the AWS. >> So it's a three tier. >> Reni: Yeah. >> So there's the edge, then there's the aggregation at Vertica, and then there's the cloud modeling and training that goes on, and Pentaho plays across that data pipeline, is that right? >> Yeah, yeah, it's our one major player in our data platform in this sense so that it will take care quite a many different kind of transactions so that we have the right data in the right place. >> Dave: All right I'm done geeking out. (laughing) >> All right, so Reni before the cameras were rolling, we were talking a little bit about the difficulties of cultural change within these organizations and you were talking about something that you're working on in Finland that's not necessarily related to Veikkaus, can you tell our viewers a little bit about what you're doing? >> Yeah, we are also setting up a Teal Finland, so promoting this like next phase of organizational, well you cannot call it belief, but vision and perspective so we want to also promote these kind of activities. So I know that especially with the big data movement, you have also seen the cultural changes so not the normal organization ways of working are not, just are not efficient enough so you have to liberate today, you have to give the freedom, how to use the data, what kind of hypothesis, what kind of activities are done, and this cultural change is also with the Teal movement. It's like getting next big leap so this is, well it's a side project but it's also really heavily work related. >> And how open is the Finnish tech community to these ideas, I mean is there an adversarial relationship within the people who don't necessarily welcome the change, I mean how would you describe it? >> I believe it's a really open, we have already, I believe, a handful of companies who work and who operate by this, from this perspective and more is popping out. And we are establishing one cooperative, like to support this movement, and maybe to create new spinoffs which can be for profit. >> All right, let's get to the heart of the matter here, (laughing) how do I beat the house? >> I knew you were going there, Dave. >> Just, just between us. >> I knew it. (laughing) >> Obviously I'm kidding but different games have different odds. >> Reni: Yeah. >> Right, I mean, and those are, you're transparent about that, people know what they are, but what are the best odds? Is it slots, best chance of winning, or poker, or... >> Yeah, slots is good side and also whenever you go to Cassie you know, it has a top notch, so 90 point something, so... >> Of probabilities and, >> But of course I have to say that the house wins eventually, so yeah, yeah. >> The bookeys always win so. >> Rebecca: Right exactly. >> So the higher the probability, the lower the pay out, and reverse, presumably, right? >> Reni: Yeah, yeah. >> The lottery would be. >> Lottery you're a check out if you're yeah. >> Dave: Low odds. >> Low odds but, >> Dave: Telephone numbers if you win. >> Yeah. >> Dave: Yeah. >> But David, you can't win if you don't play, okay, just saying, just saying. >> And every week there's somebody who wins. >> Rebecca: Right! >> Yeah. So why it cannot be me, or you? (laughing) >> Or me, or me, maybe! >> So what do you do to the guys who count cards, you like break arms or you put them in jail, no? >> It's Finland, this is no, no, come on. >> Nobody does that, right? >> Reni: No, no, no. But of course, yeah that's probably something we could in future also to use data more efficiently than we use it at the moment, so that's one part like how people behave versus machines behave. So for example in the online poker, the card counting program, that's one problem I think every, for the industry. >> Dave: Right. >> Are you working with behavioral finance experts in this to sort of understand people's behavior when it comes to this? >> Yeah we work, for example, with psychologists to understand this and the same goes with problematic gambling as well so you have to know about how people behave. >> And do you have customers outside of Finland or is it pretty much exclusively? >> No, sorry, it's exclusive club, you have to move to, you know you have to move to Finland. (laughing) And then we welcome you. >> Awesome. >> He's going to immigrate, I think, any day now. Well Reni, >> Reni: But hey, it's one of the best countries. >> Thank you so much for coming on The Cube, it was a lot of fun talking to you. >> Yeah, thank you. >> I'm Rebecca Knight, for Dave Vellante, we will have more from PentahoWorld just after this.