hello everyone I'm Jean Faria we are reporting on the ground near Puerto Rico for blockchain unbound exclusive conversations at coinage end of covering all the action restart week of ten of events cryptocurrency blockchain all the people are here with the local ecosystem the cube is here it's great to have you on thanks for joining blockchain innovation is today global this is a revolution way bigger than the Internet itself programmable money programmable contracts that wipes out finance it wipes out legal it wipes out governance in many ways there's no central authority you have access to open source software it's fully connected so now is the time to make it translate we've all heard about the steam digital transformation its businesses that if they don't evolve and adopt blockchain AI all these other things they have a threat of being put out of business it is extremely competitive a new set of stakeholders investors global players governments are it's happening now you have a chance to be a part of an economy without a permission of a centralized organization have to pay 200 people in 40 countries and it's an unholy mess with withholding taxes and concerns around money transfer costs a hassle it's a nightmare like all currency control so you're only allowed to move a certain amount of capital out the country legally so what happens in all your backups our currency and you can effectively invest in assets around the world this is making it much easier to contribute to help people to get healthy and you don't have to go to school there's a very big influx of young and talented minds at that right and this is really changing the revolution landscape you've got the radical Burning Man hippie guy all the way to a three-piece suit yeah and that diversity is very very rich a lot of people are scared I like whoa hold on slow down we're not gonna prove it the other half saying no this is the future so you have two competing forces colliding for some reason crypto really pokes at people's biases you know why does it have any value and I go well why does the United States dollar have any value I mean you've got Full Faith and Credit of the government that's in debt by 20 trillion dollars you know is that a good idea most people that come here sorry with the what the how and people are scared but the young people are like yo this is happening this is not a moment this is a movement is definitely oh say 1996-97 of the internet bubble it's just starting people know there's something really magical they don't quite know what you know America really grew because you're abused to have all the controls and so the capital by sea left Europe and away in America and now it's happening 300 years later as America has all the controls and the capital starting to go away so a new Liberation's happening incredible resources are now being poured in problems that were ignored for many many and what is beautiful is that block Candy's doing it open-source is accelerating the tech these ideas are being freely shared whereas before there's bottlenecks in the collaboration aspect if we're able to write a contract in a thousand people be able to verify that contract and we're able to transfer money from one person to another without the two parties being involved we've got a perfect scenario security and speed and fairness all at the same time you can create these chains of trust and that can happen anywhere in the world you're on a level playing field if you have 4G connectivity now you can compete globally and be a part of the global economy so if you're someone who's in the emerging developing world and you want to begin to build wealth and you'd like to own a piece of first world real estate and today the minimum is about a thousand dollars but by implementing the Plott chain further they won't eventually get down to one dollar you can buy a piece of real estate and enjoy the returns on that I want to solve the wealth gap and I truly believe we can do it when we can allow anyone anywhere to invest in good quality assets a conduit with the current system there's too many friction costs the killer app right is money it's paying people that is the killer app of the block type right now let's say that money is software and it is software so if you buy something with a credit card what do you think's happening it's all software and what has happened is open-source software has always eventually won with respect to close source software so proprietary money is probably back on its heels because open-source money's coming in something like that will give liquidity to a lot of small business owners America is a country of small business owners across the globe it supports small business owners it's an interesting model yeah you don't have to give up any equity you don't have to give up any poor seats yeah right it's much leaner my super if you're an investor you gotta get a pound of flesh somewhere is it's just getting it on the discounted tokens is there a little liquidity going on when you think about you know private sale presale is 99% a token deal right although equities coming in because a lot of more venture capital is coming in and they're demanding a piece of the action from a company and equity perspective its equity might be future revenue sometimes as dividends or the opportunity get dividends so it's a combination of you have a preference you care you know at the other day equity is I was always preferable there is a provision in the 1934 Securities Act called section 12 G it allows us Spacely to go public by telling the SEC we're doing it without having to delay it to wait for their permission after 60 days it's a derivative so we'll continue to clear comments but but the thing is with tokens who knows how long that'll take I mean is the SEC gonna Shepherd something through with crypto 1 or do they gonna make it take 5 years I don't know [Music] all over the island this is the new Oliver field the world is moving too fast today for a big country to keep up it's all gonna happen now in this next century at the city level and so we work a lot with four smaller countries or small countries because I know estonia armenia baja rains got you know dubai envy so i mean every country wants to be the crypto country multiple small countries are going to come into the space which they know now they can get the capital flowing into that company and they're gonna allow their rules to be lacs they're gonna let capital flow through and then us will have to change or maybe UK will have to change orders against us will have to change in the first world a lot of what we're talking about is a nice-to-have it's it's sort of a bit of a game and if i can participate but where I come from an emerging war that's a necessity they are no other solutions so if you live in South Africa or China or India and you want to get your money into a first world country like England Australia America it's very very difficult and virtually no one can do it but it's a major problem because you want wealth preservation you want but Plan B you want your children to be able to go to a first world university etc etc etc Puerto Rico being a free associated States of the United States of America is like the best place to actually test this possibly some push for that for infrastructure for you know internet for all sorts of different things in terms of building the best infrastructure the new newest best-in-class for your business it's four percent corporate taxes and individual it's zero percent now that's what you got to move here you gotta move here okay but you don't have to give you deliver your US citizenship no taxes are great at the same time they fall in love with the islands so it's amazing because to me Puerto Rico is a combination of LA's whether San Francisco's open-mindedness and Barcelona's you know deep European history it's just a really beautiful place and it's US territory so it's a short hop and a jump to the States if you need to most people in America mainland sort of think they're going to a foreign country because it's treated that way by our government how do I come to Puerto Rico do it right not offend the culture in abil them together what's your experience with the play ball stay good friends lost their relocation services for their business and themselves so they write a big check to you guys for the service but it's you guide them through the entire process and there's real energy here because there's a social movement underneath the entire cryptocurrency movement and that's to basically help your fellow man or women all these activity is really going to give a a shot in the arm to the Puerto Rican economy and we're bringing our funds and we're bringing our advisory the radar Thank You exponent there the hurricane was a horrible atrocity that happened and now we have this blank canvas to create a vision for Puerto Rico so what we're doing is we're connecting every single University on the island to work on open source projects to like make solutions for the private sector they know that if they can buy power on a cellphone like they're already doing for other goods and services now we've got a game-changer this is restart week and one of the other things that we've done is help all of the conference's come together collaborate rather than compete so go into the same week and put all of these satellite groups around it and then we blanket it a week around it so that we had one place for people to go and look for all of the events and then also for some for them to understand a movement about the education piece it's very difficult for people that kind of get caught up to speed because there's some technical things that need to understand to really apply this technology into the business world the other day we had an event where we talked 50 people how to create a smart contract from scratch those are 50 people who are not the same anymore ecosystems developing yet entrepreneurs you got projects you got funding coming in but as it's gonna be a fight for the ecosystem because you can't have zillion ecosystems there are definitely some you know the galaxies and you know regulatory aspects that you know put some concerns and a lot of you know people's mind since its inception you've seen people and media and mainstream media in particular target Bitcoin and they're just adopting the government narrative saying oh everyone in this industry is corrupt Oh everyone in this industry is an ICS camera Oh everyone in this industry is a a drug runner and they have all selling drugs on the dark web and and it's like you know what like you can do some research and don't get better than that traditional media they want to take down everybody that they don't consider you know like a birds of the same feather there actually are a lot of scammers and a lot of like dark forces inside of the cryptocurrency movement so that's why I think we welcome kind of more regulatory influence because you know none of us want to see bad actors in the space we've seen folks go out raise you know really big about to capital with no product roadmap no business talking roadmap no real way to get from zero to X what are they trying to shoehorn a regular business onto the blockchain and just assume that by adding crypto at the end of you know toilet paper they're gonna get something I had another founder tell me that you know Mike tokens are worth 100 million humming yep you don't have a user you just have a product you're tokens I've hiked if you ask me it's it's what little I can tell my house is 100 million dollars it's only worth as much as the top buyer how much we really need hardcore reputation systems in our industry and in the for the world I think 2018 is going to be the year of clarity on regulation and I think that's where Puerto Rico comes in and plays a major role just to see the thousands of people who have come here to support these several conferences has been amazing my most surprising thing though is the amount of people that have told me that they bought a one-way ticket and have no intention of going home so to make Puerto Rico your home I think is a really amazing first step when I go to the supermarket and where I go it's full of American and people from outside and when you ask them where you're from and they will tell you from Puerto Rico this is gonna become the epicenter of this multi-billion dollar market we need to have people prepared for this you have to create the transparency the beauty of the transparency is there's actually privacy baked in and that's what I love about blockchain is it has all of the good things all communities need to evolve in my opinion between technology communities open networks of governance where we have peer-to-peer distribution of finance and of resources in a way that allows people to aggregate around the marketplaces that are actually benefitting the way that they believe the world should work we're going to be tools that far surpassed what's currently available in terms of the messages the websites all these things for 20 years the Internet has been free it's a really beautiful thing for consumption and open-source is the absolute right methodology for software when it comes to your own content a reward it makes sense everybody is going to get to play together across every device the developers are going to get rewarded for creating content people are going to be rewarded for creating things inside the games and the players are going to get rewarded for getting to the top levels of all the games and we're going to reward them through our cryptocurrency if we begin to own ourself sovereign identity then when we're owning our data that's the foundation for universal basic income communications completely frictionless payment completely frictionless and governance completely frictionless and we have to put this all together who wins here the average citizen entrepreneur that is leveraged citizen player that wants to start something whether it's a banking a service provider of some sort an entrepreneur or a new financial instrument or firm you all have greenfield opportunity here the first thing I would tell found us is to reach out ok this community is very very supportive like you can reach out to me you can reach out to other guys LinkedIn Facebook or come to these events and say your idea and you need help because you will need help you cannot run this alone ok you are running a company you're running your team have a good team that's the first thing you got to be vigilant and you keeping your money in a hard wallet not keeping your private keys on your computer if you're using a centralized system those centralized systems are really easily exploitable strategic partnerships Advisors founding team and then show the idea to the people explain yourself frankly and honestly and I think the community will reward you to go and find it ring whether you're a fortune 500 company or a startup it's all about building the community and I believe that whether it's utility Target or security or combination of the two it provides an incredible vehicle to ultimately be the catalyst to your community and if you the to community adding value then you're going to build a company event it's always gonna be led by the business model because you need something to act as the power pull to pull the thing along right and you can continuously pump capital into something but if the model is wrong it's just going to drain and it's going to go to inefficient systems and in the end maybe do some help but but a very small percentage of the capacity of what it could do then the advice would be to entrepreneurs don't fret about the infrastructure just nail your business models right and because the switching cost might not be as high as you think that's right we're in the old days when we grew up yeah you made a bad technology decision you're out of business yeah but the first advice that I give my clients is to stomp this is this business that's too much formal in it yeah right if you're missing out so no just because everybody's out there Nico you should be doing an SEO right yeah 46% of I SEOs have already failed already failed start with the business gather this in the counties down right so free cash flow unique value proposition Prada market fit what sits under business think about the token model right the token model has to go in handy now with your business model and revenue model and once you figure out that business and took the models now it's time to think about compliance I'm gonna raise money in the US and abroad I've decided to go to security choking hypothetical instance absolute what do I do is there for you an incentive mechanism or is a fundraising mechanism or both who's gonna be my user who's gonna use this token right there aren't gonna be moms dads hospitals they was my target and then how they're gonna use it and are they gonna hold it I'm gonna sell it are they gonna trade it so all these different things define that oh c'mon once you get your token actually authenticated realized everything's transparent and it gets on that secondary market it's better to use that to invest in anything you need investment get everybody incentivized around your token all your employees all your vendors everybody incentivize around that token it's a thousand percent more powerful than a dollar so the dollar doesn't go up in value in your token your token can go up and down and as soon as you find just one spark it blows up everybody boats rise equal it's pasta Sara Lee the time to crack open the champagne you still have to demonstrate product market fit you have to help build a market in our particular case so there's a lot of hard work launch it's a start line it's just like it's only a step along the whole process you know what made people get it you showed them the money yeah you showed them the money sometimes people don't you can explain these concepts that are world-changing super high level or whatever people were not actually gonna get it until it's useful to them average business people and senior business people who have typically been shut off to the idea of blockchain are now seeing this as very real and here to stay momentum is just beginning it's gonna be amazing what these guys come up with that's one of the things I love about doing this thing right I'm an old guy and I get to hang around these smart young people makes me feel young again yeah but the other thing that we have and I think you should share it as well as we have to offer to these young guys experience thing we just invented a new category in the ico category an advisor token and a you have to have the stomach for it and I think you just have to be as educated and as you can what government entity can resist for the long term something that's actually trying to provide a better and better and better financial infrastructure you should be able to participate in many different nations who have many different economies that are all really cooperating interdependently to create the best possible life for all human good one dollar will not change your life but if you change your habits you'll change your financial destiny and so my philosophy is get it to a dollar so that every single person can participate and once you start to learn good habits around money and wealth the rest it's a formula like it's a flywheel instead the world will become a better place we'll have better companies positive impact is not counter to profit they go hand in hand the Puerto Rico movement it's a movement while Czech entrepreneurs capital investors the pioneers in the blockchain decentralized Internet are all here this is like the Silicon Valley of the crypto right I think they're calling it crypto island yes TV show we should be honest like it's not lost its crypto island exclusive coverage for Puerto Rico's - Cuba I'm John Ferrari getting the signal here out of all the noise in the market this is what we do this is the cube mission great strip we start week Point agenda open content community thanks for watching [Music]

>> Narrator: Live from San Juan, Puerto Rico, it's theCube. Covering Blockchain Unbound, brought you to by Blockchain Industries. (upbeat Latin Music) >> Hello everyone welcome back to our our exclusive coverage, theCube in Puerto Rico for the big story about Blockchain UnBound. That's the event it's a global conference from investors, bitcoin billionaires and millionaires, as well as entrepreneurs coming to Puerto Rico to discuss the future of Blockchain, the future cryptocurrency, the future of decentral application. Partnering with the island of Puerto Rico, our next guest is Damarius Riviera with Puerto Rico Advantage. And the big story is a lot of people are moving here for either tax advantages or entrepreneurial reasons and Damarius and her team at the Puerto Rico Advantage help set that up. Damarius, welcome to theCube. >> Hola, how are you? >> Thanks for coming on. >> Thanks. >> One of the big rush here is like a gold rush for folks coming in, moving to Puerto Rico but it's hard. You guys provide a service to do that for folks. How fast is it, how does it work? How does the service work? Okay, we're Puerto Rico Advantage came together as me, I'm a local from Puerto Rico and my partners are American from Wisconsin. They're both Act 20 and Act 22 themselves. So when they got here to the island, they took like seven months to find out the opportunity analysis and if the tax incentives work for them. So when they met me, I worked previously in the government before so I know how all of this works and I said let's come with one business that will be a one stop for each client. So when they come to us they get their grants, plus the relocation services for their business and themselves. >> Certainly the incentives right now are really wonderful for business and folks who are building companies and creating wealth. The tax advantages are here. There's been a surge of people coming here. What's it like? What's, how many people are coming through? Was it a lot of volume? You guys busy? Give us some insight into how it's working. >> Yes, a lot of people are coming. They're moving real estate pretty much in San Juan area. It's gone, so the other places like Dorado and Rincon are packed. When I go to the supermarket, everywhere I go it's full of American and people from upstate. And when you ask them where you're from and they will tell you from Puerto Rico. They're already calling themselves Puerto Rican. So it's very exciting and a great opportunity for us. >> One of the things I've been impressed with is the acceptance and the blending of the island folks and people coming in. Take me through an example. Let's just say hypothetically, hypothetically, I wanted to move to Puerto Rico, what do I do? I call you guys up and say hey get me a flat, get me a house. I need security I need a car. Do I need a driver's license? Do I need insurance, I mean what has to happen? Take me through and how do I, and what happens for me? Is it turn key, is it easy? What do you guys do? What do I have to do? Take me through a use case. >> Okay, first when the client calls, if it's interested in Act 20 business, they will tell a little bit about their business and then we can say if their business qualified. Then, we will take them to the CBA and work everything about the grant. It usually takes two week depending on all the info the client gives us and the quickly and I will manage everything in the government agencies. For the residential part, we schedule their meetings when they have kids to the great private schools here. We help them with the real estate, driver's license. They do need driver's licenses. I take them to get their voters ID, everything. We have like a draft, a checklist, with everything they need to qualify for residence, a Puerto Rico resident. And we take them, we make the process very easy for them. >> So they write a big check to you guys, for the service, but you guide them through the entire process? >> Yes, we do. >> So, for individuals, you can do it for individuals and businesses and individuals right? >> Yes. >> Take me through the scenarios. >> For individuals it will be the basic Act 22. So, that one is very simple and we just tell them what they need to do to comply with the 183 days they need to reside here in Puerto Rico to get the benefits for the grants tax incentives. >> So, take me through the business aspect. >> Oh, the business aspect is also very easy. As long as your company gives an export service, it qualifies. So, we even do the, if they need to hire staff, manage their business, everything. We help them with everything. >> And you guys see a lot of business coming from, people that were going to go to the Cayman Islands, or somewhere else, are they coming here? >> Yes, everybody likes because they feel Puerto Rico is part of the United States, but then we don't pay federal taxes so they have that great benefit, so they're moving a lot of the companies here. >> So since the Hurricane obviously there's been a lot of effort in the U.S. and focusing attention on helping Puerto Rico, and there's been stories good and bad, but as the new Blockchain and the Bitcoin cryptocurrency newly minted millionaires and billionaires come in, how has the culture reacted to that? They seem to be open arms. Has it been well received? What's some of the feedback that's been happening here in Puero Rico with the new in migration of folks? >> Yes, it's very well received and it's amazing because this group of the Blockchain just came after Hurricane Maria. So people were amazed like, wow, they're still considering moving here and help the island, even after this big natural disaster. So, it gives hope to a lot of people here and it's helping the island to do a lot of more progress. >> And what's great is the island is first of all beautiful but, with the infrastructure, opportunity to reboot it and reset new infrastructure, all the tech geeks, this is Blockchain, they're like tech nerds. They love the high-speed internet, they want to have the good infrastructure and the schools have now connected Blockchain. I talked to an entrepreneur here two days ago where he's linking all the schools, educational institutions and colleges with Blockchain to create a community. So there's kind of a nerd nation emerging here in Puerto Rico, isn't there? >> Yes, yes, it's amazing that we've been considered for all of that. >> Well thank you for coming on and explaining The Puerto Rican Advantage. Also, her partners are Jennifer Brockman and Angela Brookman. You guys are doing a great service. Thank you for what you do. I think a lot of people that I've talked to really appreciated it. For folks who want to come to Puerto Rico and help out and contribute but also get some real advantages for the business and as an individual. The tax breaks and the benefits are significant here and it's part of the U.S. So, great stuff. Thank you so much. >> Yes, thank you a lot. >> More live coverage here in Puerto Rico. I'm John Furrier, host of theCube. We're back after this short break. (electronic music)

(lively music) >> Narrator: Live from San Juan, Puerto Rico. It's The Cube! Covering Blockchain Unbound. Brought to you by Blockchain Industries. (lively island music) >> Hey, hello everyone. I'm John Furrier. We are reporting on the ground here in Puerto Rico for Blockchain Unbound, a global conference of leaders from around the world who are coming into Puerto Rico with the local entrepreneurs, with the local ecosystem, to talk about the future of the digital nations in the world, digital transformation, also cryptocurrency, Blockchain...all the people are here, The Cube is here, as part of our 2018 kickoff of all the crypto Blockchain shows. My next guest here on The Cube is Gustavo Diaz Skoff, who is the founder and president of the Young Entrepreneurs in Puerto Rico's society, also heavily involved in the ecosystem. Thanks for speaking with me. >> Thank you. >> John: So, what's going on here in Puerto Rico? Also, we just talked with Michael Angelo, who is the co-founder of Edublock, but we're talking about a whole transformation going on in Puerto Rico. What's the young culture like? What's the old guard say? I mean, are people... What's going on? What's the mindset? What's going on in Puerto Rico? We know the hurricane that hit, but, again, looking past that, what's the cultural vibe right now in Puerto Rico? I think the cultural vibe right now is that there's a little bit of a hesitation, but, at the same time, there's a lot of excitement. Events that, like, for example, the one that were hosted yesterday, Law 23, that brought the local and the vicinity communities together to actually clear up and like lowered those stations and actually bonded and brought more energy into the whole push. I think that is the overarching vibe here in the island, it's just like awesome. There's...something's happening. We don't know quite yet what it is, but there is a historical narrative of the island, and there is definitely a very bullish view of the island. So what's really going on here is that the people are excited, but you got the whole world descending upon Puerto Rico. We grabbed a lot last night with the party. >> Yeah. >> We put out a nice sizzle reel this morning, but the vibe was awesome. People were dancing, a lot of people smiling. >> You were there? >> We were there! We just put some up on our telegram channel. >> I was the organizer of it. >> Congratulations, really awesome. >> Thank you. >> John: Outside, nice weather, things were great, but it really is about the cross-pollination. It's about the culture of Puerto Rico, maintaining the culture in Puerto Rico, seems to be the top story that we hear from folks here. Yes, we like to bring in the industry, but don't tell us what to do. We're Puerto Rico (laughing) you know, don't stomp on our land! I'm not being...but I mean there's kind of a vibe like 'look it, Puerto Rico's proud.' But that's got to translate into execution... what's the young guns doing? >> So, this is the reality in terms of what the young guns are doing, and, sadly, sometimes they're a very sad story, and the reality is like when you look at the world economic forums competitive reports, we have the sixth-largest conglomeration of trained scientists and engineers in the world. Holy shit! That's insane. But, at the same time, we have 90 percent of them being unemployed or underemployed, because we don't have like technology companies that are actually requesting and demanding that type of knowledge. And so, that's where we're actually failing in terms of execution, because we're going to end up working for a bank or for a government agency, and so there's not that many opportunities to actually go and build that. And now, just looking at the whole shift and how the world has basically come into our shores, it's like, wow. There is an opportunity to actually use this human capital and work together and just start developing and challenging ourselves locally to keep building, either as an entrepreneur or as an intrapreneur. >> John: You know, Brock Pierce, I thought, said it great today on the keynote he gave here at the Blockchain Unbound Conference, "It's a global 'we' going on; it's a 'we,' not a 'me.'" >> And I think, you know, someone who's seen many waves in my life, this is the biggest wave ever, because it's creating essentially a flat world, it's global, so it's not like the old guard, gatekeeper, migration paths up, so the migration for up the ladder, if you will, in society for a young individual was kind of structured in the past. >> Now the ladder has fallen. It's flat. (chuckling) >> Peter Thiel, who at one point was looking at paying people not to go to school, literally the world is your oyster with this new technology, because now it's a global fabric. There's no central authority. You have access to open source software. It's fully connected. So now's the time to make it translate. What do you hope for for the community in Puerto Rico to make that connection in the actual property flow, the relationships. What are you guys looking for to have happen? >> Yeah. So the answer is going to be a little bit historical, and that goes back to the question I asked off of the camera, was like, "Do you know where the first special economic zone was built, the first SEZ was built?" It was here in Puerto Rico. And for those that don't know, that was the economic model that we used as a human race in 130 nations in 4300 zones around the world to transition our economy from agriculture to manufacturing. And I believe that, right now, we're building that fabric. We're starting to reconstruct the second generation of an SEZ, and, whatever is happening here, to either build better cities, where people are able to access their food, are able to access capital, are able to access opportunities in a way that it's de-risked. I believe it's being built right now. And I think that is where we're heading. Because we already did it 71 years ago, and this is just the perfect concoction to re-do it. >> John: You know, I talk with a lot of leaders. One of them, in particular, Teresa Carlson, runs Amazon Web Services' global public sector, which is government, schools, and whatever. We're seeing for the first time, and this is what, I think, Amazon sees, and they're the leader in cloud computing, which is phenomenal, which, again, levels a lot of gatekeepers, if you think about it that way. She talks about digital nations, that we are now at the front end of the beginning of a wave where sovereignty, at a national level, with this no-border, kind of digital culture, is a huge opportunity. >> Yeah. >> How are you guys recruiting? How are you spreading the love? How are you spreading the word? Because it's not just developers, it's about the communities. >> Well, first of all, I think it's important to actually say that it's better, I think, Puerto Rico being a free associated states of the United States of America, it's like the best place to actually test this philosophy and push for that. I think that the way that we're actually starting to recruit that is by spreading out into the world and saying, "Hey, this is happening, come back." As I was mentioning, in May, we're going to Washington DC to present over 23 organizations that are working on basically all that's happening, and be able to bring more consciousness, bring more tools into the island and be able to build, essentially, the future of it. >> Tell me about the things that you're working on right now. You mentioned before we came on camera some of the things you were doing in Washington DC. What are some of the things you're hoping to accomplish over the next year in your role, inside the community here in Puerto Rico? >> I hope to, with Edublock, be able to help more students get into this space, be able to leverage better connections and relationships with these corporations that are in need now of Blockchain developers, and be able to have that circle of flow of the people here in the island and the people internationally that are looking for talent. That's my main goal. And if I could put a number of it, it would be amazing to have 500 students recruited, or with an internship, within corporations by the next 365 days. >> As you guys at Edublock are creating a separate event forum for what's happening at Blockchain Unbound to the education community, because it's pretty pricey to come to this conference, it's an investor's conference, it's an industry conference. You're seeing a world coming together, a lot of people coming in from the crypto blockchain community. What are people talking about in Puerto Rico about this migration and this intersection of the two worlds? Is it good, bad, confusing? Are people trying to figure it out? What's the vibe? >> They need more information. They need more data. (laughing) We only have a few articles, and that's it. >> John: Yeah. >> My father, for example... >> John: Articles from centralized news organizations, not trusted news organizations. >> Yes, yes. >> What does the decentralized data say? >> The decentralized data say is that this is a good technology, and we need to be careful, like we need to understand it correctly. And we need to raise awareness around the community, because it can either go really, really, really, really, really well, or we can repeat the past couple of years in the island. >> It could fail miserably or be a home run. >> Great stuff. We certainly want to expose the information and share what the stories of the key things that we're...you're doing a great job. You guys are doing great work. We support you from Silicon Valley with The Cube. >> Our job is open, free content, which we're doing here in Puerto Rico. We're with Gustavo Diaz Skoff, who is the founder and president of the Young Entrepreneur's Club here, Entrepreneurial Society, in Puerto Rico. We're on the ground, getting all the top stories and sharing the data with you. I'm John Furrier. Thanks for watching. (digital music)

>>Que presents HP Discover 2022. Brought to You by HP >>Good morning, everyone. It's the Cube live in Las Vegas. Day two of our coverage of HP Discover 2022 from the Venetian Expo Centre. Lisa Martin and David want a what a day we had yesterday and today. Unbelievable >>for today. Big Big day today, >>Big day Today we've got a lot. We got some big heavy hitters on talking with HP customers. Partners, leadership. We've a couple of guests up with us next. Going to be talking more about the ecosystem. He's welcome. Corey Dire, the chief revenue officer, Digital Realty and Cliff Evans, senior director. H P E Green like partner ecosystem Guys. Great to have you on the >>programme. Thank you. Great to be here. >>Thank you for having us excited to be here >>with. So that's so that's harness that excitement. Cory, talk to us about the partnership. The announcement? What's going on there with Digital Realty and Green like? >>Yeah, we're crazy excited about it. You know, we've got customers dealing with data, gravity and the opportunity around that and how they could make use of it. And then they're thinking through digital transformation. How how you doing? Multi cloud and they need a partnership. To do that in this partnership with Green Leg and digital is perfect solution for them. So I'm crazy excited to be here with Cliff absolute with all of you to talk about it and hopefully build out a great partnership in relationship with HP. >>Talk to us. Sure, you're crazy Excitement >>club? Absolutely no. I think it is absolutely fantastic Partnership. I think the term is coming together as organisations. Bringing the two platforms together isn't it is an amazing thing that we have for customers, customers we know they want. They want a cloud experience. But really, they want to do that without really the DC footprint that had previously. So how did they do that in a way that really works for them in a secure client secure, sustainable way. But with the cloud experience. Really, the combination of the two pieces coming together really makes that happen, and that is what that's exciting. So we >>dig in to the two things that you mentioned Cory digital transformation and multiply. When I go back to the early days of cloud, it was that girl, you know, nobody's going to do anything you know ever again in the data centre. You know Charles Phillips, the the CEO of in four, famously said, Friends don't let friends, Bill Data centres, right? Everything's going in the cloud. So a lot of people predicted, You know, guys like you were going to be in trouble. The exact opposite happened. The market took off. So you mentioned digital transformation of multi cloud. Can we peel the onion on that? What? What is it about those two items? Are there other trends? They're driving your business, >>you know, You tied right on to to where it started. All enterprises started going to the club and then they got to the cloud and there was more that they needed to make that rial. I talk about multi cloud. You're going to use different cloud providers for different opportunities and different applications. And so you have to start thinking about how does this work in a world where you're gonna go to multiple clouds, multiple locations and what it really drove? It is the need for Cole location to make this because you've got a distributed architecture in order to enable all of this and then having to have us help you out with it. And partners like HP. That's part of where it comes from. But if you think through going to the cloud, can you stay there? Is that the full solution? You need to secure sustainable solution for that. One of the opportunities for us around that is that if you're building data centres for yourself on Prem, you don't have all the cloud access we do. We've got more cloud access points than anybody. So that helps in this digital transformation. >>How How much home? I'm sorry, Didn't mean to you how much homogeneity is there are our clients or customers saying, Hey, I kind of want the same experience in the same infrastructure. Same same. Or they saying, Hey, I want to do stuff in Digital Realty that I can't get from, you know, a cloud provider, Oracle Rack. You know, something like that, >>I would tell you that they come to us from all the partners. So we are partner community. We are not going up the stack anywhere on that. We do are we do our part. We're really good at doing the data centres really good at building data. They descended sustainable. Our position in the market is sustainability around it. We were the first to sign up on the science based initiatives for zero kind of carbon neutrality and in the future in 2030. And so yeah, so I think there's the partner aspect that they need help with on it to drive that Yeah. >>And I think from that from the HP Green Lake perspective, I think customers they very much want that that cloud experience. But I want to do on their own terms. The partnership allows that to happen on Gapen simply the cloud experiencing with the green light cloud platform to really go and deliver that genuine cloud experience and then building cloud services. On top of that, they get all the benefits that they would have from a public cloud experience, but done in the way that they would prefer to do it. So it's bringing those pieces together on >>I think the other side of you asked if it was it was the same across the board and ubiquitous. It's very bespoke. Solutions weaken D'oh! Every customer we have has a different footprint. Most from the multinationals. So we think through where their data is, where it needs to be accessed where their customers are, where their employees are, what makes the most sense. And then the partnership we have with HP into a whole lot for making very bespoke solution for that customer and help them be successful. Journey >>s O on. That s o. So what we've done with destroy lt is we have a specific offer around how we go to market with this really going how customers So we call it Green Light with co location. It's all about really positioning on offer to customers that says, Look, we can go and do this with you and do it simply and really make it happen very quickly and efficiently. So the customer ends up with a single contract in a single invoice for Green Lake Cloud Services on the co location piece, all in one single contracts. That just makes it a lot easier in terms of organising on a really big part of that as well is that our involvement is also spans right from the design to the implementation to support. So we do the whole thing to really help organisations golf and do this. So that's the big for me. The big differentiator. So rather than just having Green Lake in Cloud Services, were saying, Look, we can now do the Coehlo piece and they can really take the whole thing to a whole new level in terms of that public cloud experience >>in the sari and that that that invoice comes from HPD or Digital Realty is bundled into that >>correct? Yes, directly through the channel. We can sell that in a number of different ways. Customers get that that single invoice on a big part of that as well, just going a little bit deeper on that. So what we do is we We use a part of the company called Data Centre Technology Services, which are a great kind of consulting organisation with tremendous experience and something like 3000 projects across 40 countries from the very smallest of the very largest of data centre implementation. So all of that really makes the whole thing a lot easier from a customer's perspective in terms of designing, implementing and then supporting. So you pull all of that together. It's fantastic >>and I think it's really changed to add on to that partner in prison. So customers, now we're thinking about it differently and data centres differently, and they see us as a strategic partner along with HP. To go after this used to be space, power and calling. Now it's How much connectivity do you have? What your sustainability profile? What's your security profile? How do you secure this data? Date is the lifeblood of all these companies and you have to have a really secure, sustainable solution for them, >>right? That's absolutely critical for every industry. Talk about the specific value prop at a bespoke co location solution delivers to customers. Maybe you got a favourite customer example that you think really articulates the value of this partnership. >>So I think a combination. So so I think we touched on a lot of it, actually. So there's obviously the data centre aspect itself in terms of with the footprint that realty have across the world, you can pick and choose the data centre in the class of data centre that you want in terms of your Leighton see and connectivity that you want. Then really, it's the green make peace in terms of the flexibility that you get with that really is that value. And as I touched on the Green Lake with Cole Oh, I think for me is from our perspective, I think the biggest piece of value that we provide there to really go make it happen. Yeah, >>there's about 70 applications right now that are part of Green Lake Polo that you can bespoke for what you need to. You can think around your specific solutions that you need, and we've got it all right there with HP Green like and follow for us. And because we have a 290 data centre footprint across 50 markets, it gives us the opportunity really be the data centre provider in the Partner for H P, pretty much anywhere but with connective ity everywhere. >>When you say 70 applications, these the 70 services are you talking about talking >>about? Okay, Category 70 services. There's a lot of stuff. >>Cory, when you talked about sustainability a couple of times, is a really important ingredient of the customer decision. Why is it because they're indirectly paying the power bill or is because that's the right thing to do? And they care. There's increased. People care about it more because you go back a while ago. People way always talked about green it, but it was all lip service. Is that changing or is that there? Is there an economics >>changing in a really big way? Almost every conversation I have with customers is how are you doing Sustainability. So if they're doing an on Prem, that's not their core capabilities. They don't know how to do that. On our end, I mentioned our SP R science based initiatives that we signed up for. But how do we enable that? Enable it for how do we build in designer data centres? How do we actually work them and operate them? And then how do we go after all the green sources of sustainable energy including, I think since 2015, we've issued six billion in green bonds around that same support of it. So yeah, >>and your customer can then I presume, report that on their sustainability report a >>good way to think about it. You no longer have your data centre at its sometimes less efficient way than way are we're really good at building sustainable data centres, and then you can actually get some credits back and forth, >>just from agreement. Perspective. So Green Lake. So there's a specific Forrester Impact report that looks a green lake on how it how it performs from sustainability. Perspective on Greenlee really is giving you their 30% reduction in your energy consumption. So there's a big kind of win there as well, I think. Which is then, >>why? Where does that come from? >>So it Zim part that kind of the avoidance of over provisioning such that you going right size things, Then you have you have you have a certain amount of reserve capacity that you're using them just using the extra consumption piece when you need it. So rather than having everything running at full speed, it really is kind of struggling as to how that work. So you get a combination of effects >>with consulting and the thoughtfulness around this bespoke solution that you have. You end up needing fewer servers, pure technology that drives less power consumption and therefore you get a lot of this same really base it down. You >>talked about the savings you talked about the simplification delivery perspective. Talk about the implementation. What's the time to value that Organisations can glean from this partnership >>superfast So So yeah this This does accelerate the whole process from from initial kind of opportunity if you like and customer inquiry through to actual implementation So previously this would take considerable amount of time in terms of to ing and froing between multiple organisations on Now what we do is coordinate that do it efficiently and effectively So D. C. T s Data Sentinel services team very closely. Just have those connections often do those things incredibly quickly and it does accelerate the whole time >>and they're tied in with our team is well around. Where's the leighton? See where the solutions Because we're really thinking about what is your stack looked like from an HP perspective, but then where you need to deploy it so that you have access to the clouds You have the right proper Leighton see across your environment and you really haven't distributed architecture that works the best for you and your company. >>So this is probably answer those questions Probably both, but I'm asking anyway, I've always been a repatriation sceptic, but I'm happy to be proven wrong. You guys have other data. And maybe this is part of what one of my blind spots question is, is what's driving your business in terms of the EU's case? Is it organisations saying Hey, we want to get out of the data centre business way Don't want to put everything into the cloud but we're going to go on a digital realty and being green leg and we're gonna move into that cola Or is it? People say, You know, while we over rotated into the cloud, you were going to come back. So it's >>both. It's both, >>Yeah, in the empire. The credit. >>I think there are a lot of customers with good intentions on going to the cloud, and then there's some cost with it that maybe they didn't fully factor in it at that time. And now you've got the ability around these bespoke solutions to really right size every bit of this. And when they originally did it, they didn't think through a distributor architecture. They thought my own prim, and then I'm just gonna burst everything that a cloud that's no longer the case, and it's not really the most efficient way to your point about repatriation. They start pulling their storage back in. Well, where do you want your data? Where do you want your storage? You wanted as close as you can to the clouds for that capability and in a solution that's wrapped around it makes it very simple for you. >>I think the repatriation is very real and is increasing, eh? So we're seeing a lot of it in terms of activity and customers really trying to understand the cost that they're incurring now from a public cloud perspective. And how can they do that differently? In fact, with combined offer that we have it, it makes it a lot easier to compare. So, yeah, that really is accelerating because you don't >>see it in the macro numbers. I mean, just to be honest, you see the cloud guys combined growing 35%. And is that because your business is in transition from traditional on prime model, too, and as a service model, and so you've got that imbalance and it gets hidden in >>all that, and I think it's I think it's a new wave of things that are happening. Yeah. I mean, there's a there's a lot of things, obviously, that makes complete sense to me in Public Cloud, but I do think there's been an over rotation towards it, so I think now that realisation and it's going to take time to kind of pick that. But it's absolutely happening. There are a lot of opportunities that we've gotten some very big ones I'd love to talk about. Can't quite talk about them just get but really, where there's big, big savings in terms of what they're paying from a public cloud perspective, Really, what they want is that full management cloud service to go make it happen. So the combination of the data centre piece to Green Lake piece and then some management services, whether they're from ourselves or from party community, from manage service providers that we also work with, that gives them the complete package. >>So I have another premise. A lot of it, of course, is traditionally been focused on internal, and I feel like there's a new era coming. It's talks of the ecosystem. Are you seeing customers not only running there it in digital realty and connecting to the cloud in a hybrid fashion, but also actually building new value and building businesses that are customer facing on that that air monetize herbal. Are you seeing that? Is that happening and having examples, even generic? >>Well, basic from our perspective, our partner community, that's what they do. We have a tonne of enterprise customers, but I'll need to connect and integrate the data that you have doesn't do anything for you, Fitz on its own. And it's not interacting with other data points. And it's not around interacting with other customers, other solutions in one night. So it does help build out a partner community, a solution community for our customers in our data centres and across the >>are their industry patterns emerging. In other words, is that data ecosystems emerging by industry or is a sort of or horizontal? >>There's a mix. So I think there's a lot of lot of financial sector stuff. Yes, certainly. And then certainly manufacturing s O. I think it's interesting that you're getting a bit of a combination, but not a lot of financial sector. >>Of course, the big bags early on that they could build their own cloud. Yeah, now they're probably rethinking that. Yeah, well, maybe >>they're also service providers. When you're that large a za bank on their end. They're doing a lot of work. E. I would also say the other part that a lot of people see as an opportunity is around all the HPC and AI applications as well, in addition to manufacturing distribution. So there's a lot of use cases, a lot of reasons, like us from sort of doing this >>wrap us up with value, perhaps that you're talking Torto Financial Services Organisation or a manufacturing company. What is that 32nd elevator pitch value problem? Why they should go HP Making Digital Realty together. >>So I would say green, like Rico location gives you a single contract. Singling voice, easy to go and design, implement support and go make happen. Sorry, that's very simple way say, very just make it easy >>on. And I would just say thank you on that. It's been great to speak with you guys. And yeah, when you think through that part of it also is a bespoke opportunity to put your data where it needs to be closer to your customers. Closer to the action you were thinking through the rape reiteration of it. A lot of it's being built out there on phones and whatnot. So you've got to think through where your data is and how you managed to >>write and enable every every company in every industry to be a data company. Because that's what, of course, the demanding consumers demanding that demand isn't it is not going to turn down right now. Absolutely. Just thanks so much for David. Very much. Thank you. Together in the ecosystem, there are guests. And Dave l want a I'm Lisa Martin. You're watching the key of live from the Venetian Expo Centre in Vegas, Baby. David, I will be back there next guest in a minute.

>>The cube presents, Coon and cloud native con Europe, 2022. Brought to you by red hat, the cloud native computing foundation and its ecosystem partners. >>Welcome to Valencia Spain and cuon cloud native con 20 Europe, 2022. I'm your host Keith towns alongside a new hope en Rico, senior reti, senior editor. I'm sorry, senior it analyst at <inaudible> Enrique. Welcome to the program. >>Thank you very much. And thank you for having me. It's exciting. >>So thoughts, high level thoughts of CU con first time in person again in couple years? >>Well, this is amazing for several reasons. And one of the reasons is that yeah, I had the chance to meet, uh, with, uh, you know, people like you again. I mean, we, we met several times over the internet over zoom calls. I, I started to eat these zoom codes. <laugh> because they're really impersonal in the end. And like last night we, we are together group of friends, industry folks. It's just amazing. And a part of that, I mean, the event is, uh, is a really cool, it's really cool. There are a lot from people interviews and, you know, real people doing real stuff, not just, uh, you know, again, in personal calls, you don't even know if they're telling the truth, but when you can, you know, look in their eyes, what they're doing, I, I think that's makes a difference. >>So speaking about real people, meeting people for the first time, new jobs, new roles, Greg Moscarella, enterprise container management and general manager at SUSE. Welcome to the show, welcome back clue belong. >>Thank you very much. It's awesome to be here. It's awesome to be back in person. And I completely agree with you. Like there's a certain fidelity to the conversation and a certain, uh, ability to get to know people a lot more. So it's absolutely fantastic to be here. >>So Greg, tell us about your new role and what SUSE has gone on at KU coupon. >>Sure. So I joined SA about three months ago to lead the rancher business unit, right? So our container management pieces and, you know, it's a, it's a fantastic time. Cause if you look at the transition from virtual machines to containers and to moving to microservices, right alongside that transition from on-prem to cloud, like this is a very exciting time to be in this industry. And rancher has been setting the stage. And again, I'm go back to being here. Rancher's all about the community, right? So this is a very open, independent, uh, community driven product and project. And so this, this is kinda like being back to our people, right. And being able to reconnect here. And so, you know, doing it, digital is great, but, but being here is changes the game for us. So we, we feed off that community. We feed off the energy. So, uh, and again, going back to the space and what's happening in it, great time to be in this space. And you guys have seen the transitions you've seen, I mean, we've seen just massive adoption, uh, of containers and Kubernetes overall and ranchers been been right there with some amazing companies doing really interesting things that I'd never thought of before. Uh, so I'm, I'm still learning on this, but, um, but it's been great so far. >>Yeah. And you know, when we talk about strategy about Kubernetes today, we are talking about very broad strategies. I mean, not just the data center or the cloud with, you know, maybe smaller organization adopting Kubernetes in the cloud, but actually large organization thinking guide and more and more the edge. So what's your opinion on this, you know, expansion of Kubernetes towards the edge. >>So I think you're, I think you're exactly right. And that's actually a lot of meetings I've been having here right now is these are some of these interesting use cases. So people who, uh, whether it be, you know, ones that are easy to understand in the telco space, right? Especially the adoption of 5g and you have all these space stations, new towers, and they have not only the core radio functions or network functions that they're trying to do there, but they have other applications that wanna run on that same environment. Uh, I spoke recently with some of our, our good friends at a major automotive manufacturer, doing things in their factories, right. That can't take the latency of being somewhere else. Right. So they have robots on the factory floor, the latency that they would experience if they tried to run things in the cloud meant that robot would've moved 10 centimeters. >>By the time, you know, the signal got back, it may not seem like a lot to you, but if, if, if you're an employee, you know, there, you know, uh, a big 2000 pound robot being 10 centimeters closer to you may not be what you, you really want. Um, there's, there's just a tremendous amount of activity happening out there on the retail side as well. So it's, it's amazing how people are deploying containers in retail outlets. You know, whether it be fast food and predicting, what, what, how many French fries you need to have going at this time of day with this sort of weather. Right. So you can make sure those queues are actually moving through. It's, it's, it's really exciting and interesting to look at all the different applications that are happening. So yes, on the edge for sure, in the public cloud, for sure. In the data center and we're finding is people want a common platform across those as well. Right? So for the management piece too, but also for security and for policies around these things. So, uh, it really is going everywhere. >>So talk to me, how do, how are we managing that as we think about pushing stuff out of the data center, out of the cloud cloud, closer to the edge security and life cycle management becomes like top of mind thought as, as challenges, how is rancher and sushi addressing >>That? Yeah. So I, I think you're, again, spot on. So it's, it starts off with the think of it as simple, but it's, it's not simple. It's the provisioning piece. How do we just get it installed and running right then to what you just asked the management piece of it, everything from your firmware to your operating system, to the, the cluster, uh, the Kubernetes cluster, that's running on that. And then the workloads on top of that. So with rancher, uh, and with the rest of SUSE, we're actually tacking all those parts of the problems from bare metal on up. Uh, and so we have lots of ways for deploying that operating system. We have operating systems that are, uh, optimized for the edge, very secure and ephemeral container images that you can build on top of. And then we have rancher itself, which is not only managing your ES cluster, but can actually start to manage the operating system components, uh, as well as the workload components. >>So all from your single interface, um, we mentioned policy and security. So we, yeah, we'll probably talk about it more, um, uh, in a little bit, but, but new vector, right? So we acquired a company called new vector, just open sourced, uh, that here in January, that ability to run that level of, of security software everywhere again, is really important. Right? So again, whether I'm running it on, whatever my favorite public cloud providers, uh, managed Kubernetes is, or out at the edge, you still have to have security, you know, in there. And, and you want some consistency across that. If you have to have a different platform for each of your environments, that's just upping the complexity and the opportunity for error. So we really like to eliminate that and simplify our operators and developers' lives as much as possible. >>Yeah. From this point of view, are you implying that even you, you are matching, you know, self, uh, let's say managed clusters at the, at the very edge now with, with, you know, added security, because these are the two big problems lately, you know, so having something that is autonomous somehow easier to manage, especially if you are deploying hundreds of these that's micro clusters. And on the other hand, you need to know a policy based security that is strong enough to be sure again, if you have these huge robots moving too close to you, because somebody act the, the, the class that is managing them, that is, could be a huge problem. So are you, you know, approaching this kind of problems? I mean, is it, uh, the technology that you are acquired, you know, ready to, to do this? >>Yeah. I, I mean, it, it really is. I mean, there's still a lot of innovation happening. Don't, don't get me wrong. We're gonna see a lot of, a lot more, not just from, from SA and ranch here, but from the community, right. There's a lot happening there, but we've come a long way and we solved a lot of problems. Uh, if I think about, you know, how do you have this distributed environment? Uh, well, some of it comes down to not just, you know, all the different environments, but it's also the applications, you know, with microservices, you have very dynamic environment now just with your application space as well. So when we think about security, we really have to evolve from a fairly static policy where like, you might even be able to set an IP address and a port and some configuration on that. >>It's like, well, your workload's now dynamically moving. So not only do you have to have that security capability, like the ability to like, look at a process or look at a network connection and stop it, you have to have that, uh, manageability, right? You can't expect an operator or someone to like go in and manually configure a YAML file, right? Because things are changing too fast. It needs to be that combination of convenient, easy to manage with full function and ability to protect your, your, uh, your resources. And I think that's really one of the key things that new vector really brings is because we have so much intelligence about what's going on there. Like the configuration is pretty high level, and then it just runs, right? So it's used to this dynamic environment. It can actually protect your workloads wherever it's going from pod to pod. Uh, and it's that, that combination, again, that manageability with that high functionality, um, that, that is what's making it so popular. And what brings that security to those edge locations or cloud locations or your data center. >>So one of the challenges you're kind of, uh, touching on is this abstraction on, upon abstraction. When I, I ran my data center, I could put, uh, say this IP address, can't talk to this IP address on this port. Then I got next generation firewalls where I could actually do, uh, some analysis. Where are you seeing the ball moving to when it comes to customers, thinking about all these layers of abstraction IP address doesn't mean anything anymore in cloud native it's yes, I need one, but I'm not, I'm not protecting based on IP address. How are customers approaching security from the name space perspective? >>Well, so it's, you're absolutely right. In fact, even when you go to IPV six, like, I don't even recognize IP addresses anymore. <laugh> yeah. >>That doesn't mean anything like, oh, just a bunch of, yeah. Those are numbers, alpha Ric >>And colons. Right. You know, it's like, I don't even know anymore. Right. So, um, yeah, so it's, it comes back to that, moving from a static, you know, it's the pets versus cattle thing. Right? So this static thing that I can sort of know and, and love and touch and kind of protect to this almost living, breathing thing, which is moving all around, it's a swarm of, you know, pods moving all over the place. And so, uh, it, it is, I mean, that's what Kubernetes has done for the workload side of it is like, how do you get away from, from that, that pet to a declarative approach to, you know, identifying your workload and the components of that workload and what it should be doing. And so if we go on the security side some more like, yeah, it's actually not even namespace namespace. >>Isn't good enough if we wanna get, if we wanna get to zero trust, it's like, just cuz you're running in my namespace doesn't mean I trust you. Right. So, and that's one of the really cool things about new vectors because of the, you know, we're looking at protocol level stuff within the network. So it's pod to pod, every single connection we can look at and it's at the protocol layer. So if you say you're on my SQL database and I have a mye request going into it, I can confirm that that's actually a mye protocol being spoken and it's well formed. Right. And I know that this endpoint, you know, which is a, uh, container image or a pod name or some, or a label, even if it's in the same name, space is allowed to talk to and use this protocol to this other pod that's running in my same name space. >>Right. So I can either allow or deny. And if I can, I can look into the content that request and make sure it's well formed. So I'll give you an example is, um, do you guys remember the log four J challenges from not too long ago, right. It was a huge deal. So if I'm doing something that's IP and port based and name space based, so what are my protections? What are my options for something that's got logged four J embedded in like, I either run the risk of it running or I shut it down. Those are my options. Like those neither one of those are very good. So we can do, because again, we're at the protocol layer. It's like, ah, I can identify any log for J protocol. I can look at whether it's well formed, you know, or if it's malicious and it's malicious, I can block it. If it's well formed, I can let it go through. So I can actually look at those, those, um, those vulnerabilities. I don't have to take my service down. I can run and still be protected. And so that, that extra level, that ability to kind of peek into things and also go pod to pod, you know, not just same space level is one of the key differences. So I talk about the evolution or how we're evolving with, um, with the security. Like we've grown a lot, we've got a lot more coming. >>So let's talk about that a lot more coming what's in the pipeline for SUSE. >>Well, probably before I get to that, we just announced new vector five. So maybe I can catch us up on what was released last week. Uh, and then we can talk a little bit about going, going forward. So new vector five, introduce something called um, well, several things, but one of the things I can talk in more detail about is something called zero drift. So I've been talking about the network security, but we also have run time security, right? So any, any container that's running within your environment has processes that are running that container. What we can do is actually comes back to that manageability and configuration. We can look at the root level of trust of any process that's running. And as long as it has an inheritance, we can let that process run without any extra configuration. If it doesn't have a root level of trust, like it didn't spawn from whatever the, a knit, um, function was in that container. We're not gonna let it run. Uh, so the, the configuration that you have to put in there is, is a lot simpler. Um, so that's something that's in, in new vector five, um, the web application firewall. So this layer seven security inspection has gotten a lot more granular now. So it's that pod Topo security, um, both for ingress egress and internal on the cluster. Right. >>So before we get to what's in the pipeline, one question around new vector, how is that consumed and deployed? >>How is new vector consumed, >>Deployed? And yeah, >>Yeah, yeah. So, uh, again with new vector five and, and also rancher 2 65, which just were released, there's actually some nice integration between them. So if I'm a rancher customer and I'm using 2 65, I can actually deploy that new vector with a couple clicks of the button in our, uh, in our marketplace. And we're actually tied into our role-based access control. So an administrator who has that has the rights can just click they're now in a new vector interface and they can start setting those policies and deploying those things out very easily. Of course, if you aren't using, uh, rancher, you're using some other, uh, container management platform, new vector still works. Awesome. You can deploy it there still in a few clicks. Um, you're just gonna get into, you have to log into your new vector, uh, interface and, and use it from there. >>So that's how it's deployed. It's, it's very, it's very simple to use. Um, I think what's actually really exciting about that too, is we've opensourced it? Um, so it's available for anyone to go download and try, and I would encourage people to give it a go. Uh, and I think there's some compelling reasons to do that now. Right? So we have pause security policies, you know, depreciated and going away, um, pretty soon in, in Kubernetes. And so there's a few things you might look at to make sure you're still able to run a secure environment within Kubernetes. So I think it's a great time to look at what's coming next, uh, for your security within your Kubernetes. >>So Paul, we appreciate chief stopping by from ity of Spain, from Spain, I'm Keith Townsend, along with en Rico Sinte. Thank you. And you're watching the, the leader in high tech coverage.

>>The cube presents, Coon and cloud native con Europe, 2022, brought to you by red hat, the cloud native computing foundation and its ecosystem partners. >>Welcome to Valencia Spain in Coon cloud native con 2022 Europe. I'm Keith Townsend, along with my cohot on Rico senior, Etti senior it analyst at gig home. We are talking to amazing people, creators people contributing to all these open source projects. Speaking of open source on Rico. Talk to me about the flavor of this show versus a traditional like vendor show of all these open source projects and open source based companies. >>Well, first of all, I think that the real difference is that this is a real conference. Hmm. So real people talking about, you know, projects about, so the, the open source stuff, the experiences are, you know, on stage and there are not really too many product pitches. It's, it's about, it's about the people. It's about the projects. It's about the, the challenges they had, how they, you know, overcome some of them. And, uh, that's the main difference. I mean, it's very educative informative and the kind of people is different. I mean, developers, you know, SREs, you know, you find ends on people. I mean, people that really do stuff that that's a real difference. I mean, uh, quite challenginghow discussing with them, but really, I mean, because they're really opinionated, but >>So we're gonna get talked to, to a company that has boosts on the ground doing open source since the, almost the start mm-hmm <affirmative> Kirsten newcomer, director of hybrid platform security at red hat and, uh, Connor Gorman, senior principal software engineer at red hat. So Kirsten, we're gonna start with you security and Kubernetes, you know, is Kubernetes. It's a, it's a race car. If I wanted security, I'd drive a minivan. <laugh> >>That's, that's a great frame. I think, I think though, if we stick with your, your car analogy, right, we have seen cars in cars and safety in cars evolve over the years to the point where you have airbags, even in, you know, souped up cars that somebody's driving on the street, a race car, race cars have safety built into, right. They do their best to protect those drivers. So I think while Kubernetes, you know, started as something that was largely, you know, used by Google in their environment, you know, had some perimeter based security as Kubernetes has become adopted throughout enterprises, as people. And especially, you know, we've seen the adoption accelerate during the pandemic, the move to both public cloud, but also private cloud is really accelerated. Security becomes even more important. You can't use Kubernetes in banking without security. You can't use it, uh, in automotive without security telco. >>And Kubernetes is, you know, Telco's adoption, Telco's deploying 5g on Kubernetes on open shift. Um, and, and this is just so the security capabilities have evolved over time to meet the customers and the adopters really red hat because of our enterprise customer base, we've been investing in security capabilities and we make those contributions upstream. We've been doing that really from the beginning of our adoption of Kubernetes, Kubernetes 1.0, and we continue to expand the security capabilities that we provide. And which is one of the reasons, you know, the acquisition of stack rocks was, was so important to us. >>And, and actually we are talking about security at different levels. I mean, so yeah, and different locations. So you are securing an edge location differently than a data center or, or, or maybe, you know, the cloud. So there are application level security. So there are so many angles to take this. >>Yeah. And, and you're right. I mean, I, there are the layers of the stack, which starts, you know, can start at the hardware level, right. And then the operating system, the Kubernetes orchestration all the services, you need to have a complete Kubernetes solution and application platform and then the services themselves. And you're absolutely right. That an edge deployment is different than a deployment, uh, on, you know, uh, AWS or in a private da data center. Um, and, and yet, because there is this, if you, if you're leveraging the heart of Kubernetes, the declarative nature of Kubernetes, you can do Kubernetes security in a way that can be consistent across these environments with the need to do some additions at the edge, right? You may, physical security is more important at the edge hardware based encryption, for example, whereas in a, in a cloud provider, your encryption might be at the cloud provider storage layer rather than hardware. >>So how do you orchestrate, because we are talking about orchestration all day and how do you orchestrate all these security? >>Yep. So one of the things, one of the evolutions that we've seen in our customer base in the last few years is we used to have, um, a small number of large clusters that our customers deployed and they used in a multi-tenant fashion, right? Multiple teams from within the organization. We're now starting to see a larger number of smaller clusters. And those clusters are in different locations. They might be, uh, customers are both deploying in public cloud, as well as private, you know, on premises, um, edge deployments, as you mentioned. And so we've invested in, uh, multi cluster management and, or, you know, sort of that orchestration for orchestrators, right? The, and because again of the declarative nature of Kubernetes, so we offer, uh, advanced cluster management, red hat, advanced cluster management, which we open sourced as the multi cluster engine CE. Um, so that component is now also freely available, open source. We do that with everything. So if you need a way to ensure that you have managed the configuration appropriately across all of these clusters in a declarative fashion, right. It's still YAML, it's written in YAML use ACM use CE in combination with a get ops approach, right. To manage that, uh, to ensure that you've got that environment consistent. And, and then, but then you have to monitor, right. You have to, I'm wearing >>All of these stack rocks >>Fits in. I mean, yeah, sure. >>Yeah. And so, um, you know, we took a Kubernetes native approach to securing all of this. Right. And there's kind of, uh, we have to say, there's like three major life cycles. You have the build life cycle, right. You're building these imutable images to go deployed to production. Right. That should never change that are, you know, locked at a point in time. And so you can do vulnerability scanning, you can do compliance checks at that point right. In the build phase. But then you put those in a registry, then those go and be deployed on top of Kubernetes. And you have the configuration of your application, you know, including any vulnerabilities that may exist in those images, you have the R back permissions, right. How much access does it have to the cluster? Is it exposed on the internet? Right. What can you do there? >>And then finally you have, the runtime perspective of is my pod is my container actually doing what I think it's supposed to do. Is it accessing all the right things? Is it running all the right processes? And then even taking that runtime information and influencing the configuration through things like network policies, where we have a feature called process baselining that you can say exactly what processes are supposed to run in this pod. Um, and then influencing configuration in that way to kind of be like, yeah, this is what it's doing. And let's go stamp this, you know, declaratively so that when you deploy it the next time you already have security built in at the Kubernetes level. >>So as we've talked about a couple of different topics, the abstraction layers, I have security around DevOps. So, you know, I have multi tendency, I have to deal with, think about how am I going to secure the, the, the Kubernetes infrastructure itself. Then I have what seems like you've been talking about here, Connor, which is dev SecOps mm-hmm <affirmative> and the practice of securing the application through policy. Right. Are customers really getting what's under the hood of dev SecOps? >>Do you wanna start or yeah. >>I mean, I think yes and no. I think, um, you know, we've, some organizations are definitely getting it right. And they have teams that are helping build things like network policies, which provide network segmentation. I think this is huge for compliance and multi-tenancy right. Just like containers, you know, one of the main benefits of containers, it provides this isolation between your applications, right? And then everyone's familiar with the network firewall, which is providing network segmentation, but now in between your applications inside Kubernetes, you can create, uh, network segmentation. Right. And so we have some folks that are super, super far along that path and, and creating those. And we have some folks who have no network policies except the ones that get installed with our products. Right. And then we say, okay, how can we help you guys start leveraging these things and, and creating maybe just basic name, space isolation, or things like that. And then trying to push that back into more the declarative approach. >>So some of what I think we hear from, from what Connor just te teed up is that real DevSecOps requires breaking down silos between developers, operations and security, including network security teams. And so the Kubernetes paradigm requires, uh, involvement actually, in some ways, it, it forces involvement of developers in things like network policy for the SDN layer, right? You need to, you know, the application developer knows which, what kinds of communication he or she, his app or her app needs to function. So they need to define, they need to figure out those network policies. Now, some network security teams, they're not familiar with YAML, they're not necessary familiar with software development, software defined networking. So there's this whole kind of, how do we do the network security in collaboration with the engineering team? And when people, one of the things I worry about, so DevSecOps it's technology, but it's people in process too. >>Right. And one of the things I think people are very comfortable adopting vulnerability scanning early on, but they haven't yet started to think about the network security angle. This is one area that not only do we have the ability in ACS stack rocks today to recommend a network policy based on a running deployment, and then make it easy to deploy that. But we're also working to shift that left so that you can actually analyze app deployment data prior to it being deployed, generate a network policy, tested out in staging and, and kind of go from the beginning. But again, people do vulnerability analysis shift left, but they kind of tend to stop there and you need to add app config analysis, network communication analysis, and then we need appropriate security gates at deployment time. We need the right automation that helps inform the developers. Not all developers have security expertise, not all security people understand a C I C D pipeline. Right. So, so how, you know, we need the right set of information to the right people in the place they're used to working in order to really do that infinity loop. >>Do you see this as a natural progression for developers? Do they really hit a wall before, you know, uh, finding out that they need to progress in, in this, uh, methodology? Or I know >>What else? Yeah. So I think, I think initially there's like a period of transition, right? Where there's sometimes there's opinion, oh, I, I ship my application. That's what I get paid for. That's what I do. Right. <laugh> um, and, and, but since, uh, Kubernetes has basically increased the velocity of developers on top, you know, of the platform in order to just deploy their own code. And, you know, we have every, some people have commits going to production, you know, every commitment on the repo goes to production. Right. Um, and so security is even more at the forefront there. So I think initially you hit a little bit of a wall security scans in CI. You could get some failures and some pushback, but as long as these are very informative and actionable, right. Then developers always wanna do the right thing. Right. I mean, we all want to ship secure code. >>Um, and so if you can inform you, Hey, this is why we do this. Or, or here's the information about this? I think it's really important because I'm like, right, okay. Now when I'm sending my next commits, I'm like, okay, these are some constraints that I'm thinking about, and it's sort of like a mindset shift, but I think through the tooling that we like know and love, and we use on top of Kubernetes, that's the best way to kind of convey that information of, you know, honestly significantly smaller security teams than the number of developers that are really pushing all of this code. >>So let's scale out what, talk to me about the larger landscape projects like prime cube, Litner, OPPI different areas of investment in, in, in security. Talk to me about where customers are making investments. >>You wanna start with coup linter. >>Sure. So coup linter was a open source project, uh, when we were still, uh, a private company and it was really around taking some of our functionality on our product and just making it available to everyone, to basically check configuration, um, both bridging DevOps and SecOps, right? There's some things around, uh, privileged containers, right? You usually don't wanna deploy those into your environment unless you really need to, but there's other things around, okay, do I have anti affinity rules, right. Am I running, you know, you can run 10 replicas of a pod on the same node, and now your failure domain is a single node. Now you want them on different nodes, right. And so you can do a bunch of checks just around the configuration DevOps best practices. And so we've actually seen quite a bit of adoption. I think we have like almost 2000 stars on, uh, and super happy to see people just really adopt that and integrate it into their pipelines. It's a single binary. So it's been super easy for people to take it into their C I C D and just, and start running three things through it and get, uh, you know, valuable insights into, to what configurations they should change. Right. >>And then if you're, if you were asking about things like, uh, OPPA, open policy agent and OPPA gatekeeper, so one of the things happening in the community about OPPA has been around for a while. Uh, they added, you know, the OPPA gatekeeper as an admission controller for Cobe. There's also veno another open source project that is doing, uh, admission as the Kubernetes community has, uh, kind of is decided to deprecate pod security policies, um, which had a level of complexity, but is one of the key security capabilities and gates built into Kubernetes itself. Um, OpenShift is gonna continue to have security context constraints, very similar, but it prevents by default on an OpenShift cluster. Uh, not a regular user cannot deploy a privileged pod or a pod that has access to the host network. Um, and there's se Linux configuration on by default also protects against container escapes to the file system or mitigates them. >>So pod security policies were one way to ensure that kind of constraint on what the developer did. Developers might not have had awareness of what was important in terms of the level of security. And so again, the cube and tools like that can help to inform the developer in the tools they use, and then a solution like OPPA, gatekeeper, or SCCs. That's something that runs on the cluster. So if something got through the pipeline or somebody's not using one of these tools, those gates can be leveraged to ensure that the security posture of the deployment is what the organization wants and OPPA gatekeeper. You can do very complex policies with that. And >>Lastly, talk to me about Falco and Claire, about what Falco >>Falco and yep, absolutely. So, um, Falco, great runtime analysis have been and something that stack rocks leveraged early on. So >>Yeah, so yeah, we leveraged, um, some libraries from Falco. Uh, we use either an EB P F pro or a kernel module to detect runtime events. Right. And we, we primarily focus on network and process activity as, um, as angles there. And then for Claire, um, it's, it's now within red hat again, <laugh>, uh, through the acquisition of cores, but, uh, we've forked in added a bunch of things around language vulnerabilities and, and different aspects that we wanted. And, uh, and you know, we're really interested in, I think, you know, the code bases have diversion a little bit Claire's on V4. We, we were based off V2, but I think we've both added a ton of really great features. And so I'm really looking forward to actually combining all of those features and kind of building, um, you know, we have two best of best of breed scanners right now. And I'm like, okay, what can we do when we put them together? And so that's something that, uh, I'm really excited about. >>So you, you somehow are aiming at, you know, your roadmap here now putting everything together. And again, orchestrated well integrated yeah. To, to get, you know, also a simplified experience, because that could be the >>Point. Yeah. And, and as you mentioned, you know, it's sort of that, that orchestration of orchestrators, like leveraging the Kubernetes operator principle to, to deliver an app, an opinionated Kubernetes platform has, has been one of the key things we've done. And we're doing that as well for security out of the box security policies, principles based on best practices with stack rocks that can be leveraged in the community or with red hat, advanced cluster security, combining our two scanners into one clear based scanner, contributing back, contributing back to Falco all of these things. >>Well, that speaks to the complexity of open source projects. There's a lot of overlap in reconciling. That is a very difficult thing. Kirsten Connor, thank you for joining the cube Connor. You're now a cube alone. Welcome to main elite group. Great. From Valencia Spain, I'm Keith Townsend, along with en Rico senior, and you're watching the cue, the leader in high tech coverage.

>>The cube presents, Coon and cloud native con Europe, 2022. Brought to you by red hat, the cloud native computing foundation and its ecosystem partners. >>Welcome to Licia Spain and cube con cloud native con 2022 Europe. I'm Keith Townsend, along with Paul Gillon senior editor, enterprise architecture for Silicon angle. We're gonna talk to some amazing folks. Day two coverage of Q con cloud native con Paul. We did the wrap up yesterday. Great. A great back and forth about what en Rico about yesterday's, uh, session. What are you looking for to today? >>I'm looking for, uh, to understand better, uh, how Kubernetes is being put into production, the types of applications that are being built on top of it. Yesterday, we talked a lot about infrastructure today. I think we're gonna talk a little bit more about applications, including with our first guest. >>Yeah, I was speaking our first guest. We have ish Degan CPO chief product officer at Hazelcast Hazelcast has been on the program before, but you, this is your first time in the queue, correct? >>It, it is Keith. Yeah. Well, >>Welcome to been Cuban. So we're talking data, which is always a fascinating topic. Containers are, have been known for not being supportive of stateful applications. At least you shouldn't hold the traditional thought. You shouldn't hold stateful data in containers. Tell me about the relationship between Hazel cast and containers we're at Cuan. >>Yeah, so a little bit about, uh, Hazelcast. We are a real time data platform and, uh, we are not a database, but a data platform because we basically allow, uh, data at rest as well as data in motion. So you can imagine that if you're writing an application, you can basically query and join a data coming in events, as well as data, which might have been persisted. So you can do both stream processing as well as, you know, low latency data access. And, and this platform of course, is supported on all the clouds. And we kind of delegate the orchestration of this kind of scale out system to Kubernetes. Um, and you know, that provides a resiliency and many things which go along with that. >>So you say you don't, you're not a database platform. What are you used for to manage the data? >>So we are, uh, we are memory first. So we are, you know, we started with low latency applications, but then we realized that real time has really become a business term. It's it's more of a business SLA mm-hmm, <affirmative>, it's really the, we see the opportunity, the punctuated change, which is happening in the market today is about real time data access to real time. I mean, there are real time applications. Our customers are building around real time offers, um, realtime thread detection. I mean, just imagine, you know, one of our customers like B and P par bars, they have, they basically originate a loan while the customer is banking. So you are in an ATM machine and you swipe your card and you are asking for, you know, taking 50 euros out. And at that point they can actually originate a custom loan offer based on your existing balance you're existing request and your credit score in that moment. So that's a value moment for them and they actually saw 400% loan origination go up because of that, because nobody's gonna be thinking about a credit, uh, line of credit after they're done banking. So it's in that value moment and we allow basically our data platform allows you to have fast access to data and also process incoming streams. So not before they get stored, but as they're coming in. >>So if I'm a developer and cuon is definitely a conference for developer and I, I come to the booth and I hear <inaudible>, that's the end value. I, I hear what I can do with my application. I guess the question is, how do I get there? I mean, uh, if it's not a database, how do I make a call from a container to, from my microservice to Hazel cath? Like, do I think of this as a, uh, a CNI or, or C CSI? How do I access >>PA care? Yeah. So, so we, uh, you know, we are, our server is actually built in Java. So a lot of the application which get written on top of the data platform are basically accessing through Java APIs. Or as you have a.net shop, you can actually use.net API. So we are basically an API first platform and SQL is basically the polyglot way of accessing data, both streaming data, as well as it store data. So most of the application developers, a lot of it is run done in microservices, and they're doing these fast get inputs for data. So they, they have a key, they want to get to a customer, they give a customer ID. And the beauty is that, um, while they're processing the events, they can actually enrich it because you need contextual information as well. So going back to the ATM example, you know, at that event happened, somebody swiped the card and ask for 50 euros, and now you want more information like credit score information, all that needs to be combined in that, in that value moment. >>So we allow you to do those joins and, you know, the contextual information is very important. So you see a lot of streaming platform out there, which just do streaming, but if you're an application developer, like you asked, you have to basically do call out to a streaming platform to get, um, to do streaming analytics and then do another call to get the context of that. You know, what is the credit score for this customer? But whereas in our case, because the data platform supports both streaming as well as data at rest, you can do that in one call and, you know, you don't want to have the operational complexity to stand out. Two different scale out servers is, is, is, is humongous, right? I mean, you want to build your business application. So, >>So you are querying data streaming data and data rest yes. In the same query >>Yes. In the same query. And we are memory first. So what happens is that we store a lot of the hot data in memory. So we have a scale out Ram based server. So that's where you get the low latency from. In fact, last year we did a benchmark. We were able to process a billion events a second, uh, with 99% of the latency under 30 milliseconds. So that kind of processing and that kind of power is, and, and the most important thing is determinism. I mean, you know, there's a lot of, um, if you look at real time, what real time is, is about this predictable latency at scale, because ultimately your, your adhering to a business SLA is not about milliseconds or microsecond. It's what your business needs. If your business needs that you need to deny or, uh, approve a credit credit card transaction in 50 milliseconds, that's your business SLA, and you need that predictability for every transaction. >>So talk to us about how how's this packaged in consumed. Cause I'm hearing a, a bunch of server Ram I'm hearing numbers that we're trying to adapt away from at this conference. We don't wanna see the onlay. We just want to use it. >>Yeah. So, so we kind of take a bit that, that complexity of managing this scale out, um, uh, uh, cluster, which actually utilizes Rams from each server. And then, you know, if you, you can configure it so that the hard set of data is in Ram, but the data, which is, you know, not so hard can actually go into a tiered storage model. So we are memory first. So, but what you are doing is you're doing simple, it's an API. So you do basically a crud, right? You create records, you read them through SQL. So for you, it's, it's, it's kind of like how you access that database. And we also provide you, you know, real time is also a journey. I mean, a lot of customers, you know, you don't want to rip their existing system and deploy another kind of scale out platform. Right? So we, we see a lot of these use cases where they have a database and we can sit in between the database, a system of record and the application. So we are kind of in between there. So that's, that's the journey you can take to real time. >>How does Kubernetes, uh, containers and Kubernetes change the game for real time analytics? >>Yeah. So, uh, Kubernetes does change it because what's hap first of all, we service most of the operational workloads. So it's, it's more on the, a lot of our customers. We have most, most of the big banks credit card companies in financial services and retail. Those are the two big sectors for us. And first of all, you know, a lot of these operational workloads are moving to the cloud and with move to the cloud, they're actually taking their existing applications and, and moving to, you know, one of the providers and to kind of orchestrate this scale out platform, which does auto scaling, that's where the benefit comes from mm-hmm <affirmative>. And it also gives them the freedom of choice. So, you know, the Kubernetes is, you know, a standard which goes across cloud providers. So that gives them the benefit that they can actually take their application. And if they want, they can actually move it to a different, a different cloud provider because we take away the orchestration complexity, you know, in that abstraction layer. >>So what happens when I need to go really fast? I mean, I, I, I need, uh, I'm looking at bare metal and I'm looking at really scaling a, a, a homogeneous application in a single data center set of data centers. Is there a bare metal play here? >>Yes. There, there, there are some very, very, uh, like if you want microsecond latency, mm-hmm, <affirmative>, um, you know, we have customers who actually store two to four terabytes in Ram and, and they can actually stand up. Um, you know, again, it depends on what kind of deployment you want. You can either scale up or scale out, scaling up is expensive, you know, because those boxes are not cheap, but if you have a requirement like that, where there is sub millisecond or microphone latency requirement, you could actually store the entire data set. I mean, a lot of the operational data sets are under four terabytes. So it's not uncommon that you could actually take the entire operational transactional data set, actually move, move that to a pure Ram. But, uh, I think now we, we also see that these operational workloads are also, there's a need for analytics to be done on top as well. >>I mean, we, going back to the example I gave you, so this, this, uh, customer is not only doing stream crossing, they're also influencing a machine learning algorithm in that same, in the same kind of cycle in the life cycle. So they might have trained a machine learning or algorithm on a data lake somewhere, but once they're ready, they're actually influencing the ML algorithm in our kind of life cycle right there. So, you know, that that really brings analytics and transactions kind of together because after all transactions are where the real, you know, insights are. >>Yeah. I'm, I'm struggling a little bit with this, with these two different use cases where I have transactional basically a transactional database or transactional data platform alongside a analytics platform. Those are two, like they're two different things. I have a, you know, I, I have spinning rust for one, and then I have memory and, and MBME for another. Uh, and that requires tuning requires DBAs. It requires a lot of overhead, there seems to be some type of secret sauce going on here. >>Yeah. Yeah. So, I mean, you know, we, we basically say that if you are, if you have a business case where you want to make a decision, you know, you, the only chance to succeed is where you are not making a decision tomorrow based on today's data. Right? I mean, the only way to act on that data is today. So the act is a keyword here. We actually let you generate a realtime offer. We, we let you do credit card fraud detection. In that moment, the analytics is about knowing less about acting on it. Right? Most of our applications are machine critical. They're acting on real time. I think when you talk about like the data lakes there, there's actually a real time there as well, but it's about knowing, and we believe that the operational side is where, you know, that value moment is there, you know, what good is, is to know about something tomorrow, you know, if something wrong happened, I mean, it, yeah, so there's a latency squeeze there as well, but we are on, on more on the kind of transaction and operational side. >>I gotcha. Yeah. So help me understand, like integrations. A lot of the, the, when I think of transactions, I'm thinking of SAP, Oracle, where the process is done, or some legacy banking or not legacy or new modern banking app, how does the data get from one platform to a, to Hazel cast so I can make those >>Decisions? Yeah. So we have, uh, this, the streaming engine, we have has a whole bunch of connectors to a lot of data sources. So in fact, most of our use cases already have data sources underneath there, their databases there's KA connectors, you know, joining us because if you look at it, events is, are comprised of transactions. So something, a customer did, uh, a credit card swipe, right. And also events events could be machine or IOT. So it's really unique connectivity and data ingestion before you can process that. So we have, uh, a whole suite of connectors to kind of bring data in, in our platform. >>We've been talking a lot, these last couple of days about, uh, about the edge and about moving processing capability closer to the edge. How do you enable that? >>Yeah. So edge is actually very, very relevant because of what's happening is that, um, you know, if you, if you look at like a edge deployment use case, um, you know, we have a use case where data is being pushed from these different edge devices to cloud data warehouse. Right. But just imagine that you want to be filtering data at the, at, at where it is being originated from, and you wanna push only relevant data to, to maybe a central data lake where you might want to do, you know, train your machine learning models. Mm-hmm <affirmative> so that at the edge, we are actually able to process that data. So Hazel cast will allow you to actually write a data pipeline and do stream processing so that you might want to just push, you know, a part or a subset of data, which applies by the rules. Uh, so there's, there's a big, um, uh, I think edge is, you know, there's a lot of data being generated and you don't want like garbage and garbage out there's there's, there is there's filtration done at the edge. So that only the relevant data lands in a data, data lake or something like that. >>Well, Monash, we really appreciate you stopping by realtime data is an exciting area of coverage for the queue overall from Valencia Spain, I'm Keith Townsend, along with Paul Gillon, and you're watching the queue, the leader in high tech coverage.

>>The cube presents, Coon and cloud native con Europe 22, brought to you by the cloud native computing foundation. >>Welcome to Valencia Spain and coverage of Q con cloud native con Europe, 2022. I'm Keith Townsend. You're a host of the cube along with Paul Gillum, senior editor, enterprise architecture for Silicon angle, ENCO, senior ready, senior it analyst for giga own. Uh, this has been a full day, 7,500 attendees. I might have seen them run out of food. This is just unexpected. I mean, they, the, it escalated from what understand it went from four, capping it off to 4,000 gold, 5,000 gold in and off. Finally at 7,500 people. I'm super excited for, you know, today's been a great day of coverage. I'm super excited for tomorrow's coverage, uh, from the cube. But first off, we'll let the, the new person on stage take the, the first question of, of the wrap up of the day of coverage, UN Rico on Rico. What's different about this year versus other Q coupons or cloud native conversations. >>I, I think in general, it's the maturity. So we talk it a lot about day two operations, uh, observability monitoring, uh, going deeper and deeper in the security aspects of the application. So this means that for many enterprises, Kubernetes is becoming real critical. They want to, to get more control of it. And of course you have the discussion around Phen op around, you know, uh, cost control because we are deploying Kubernetes everywhere. And, and if you don't have everything optimized control, monitor it, you know, uh, cost to the roof and think about, uh, deploying the public cloud. If your application is not optimized, you're paying more, but also in the on premises, if you are not optimiz, you don't have the clear idea of what is going to happen. So capacity planning become the nightmare that we know from the past. So there is a lot of going on around these topics, uh, really exciting, actually less infrastructure, more replication. That is what Kubernetes is India. >>Paul help me separate some of the signal from the noise. Uh, there is a lot going on a lot of overlap. What are some of the big themes of takeaways for day one that enterprise architects executives need to take home and really chew >>On? Well, the Kubernetes was a turning point. You know, Docker was introduced nine years ago and for the first three or four years, it was an interesting technology that was not very widely adopted. Kubernetes came along and gave developers a reason to use containers. What strikes me about this conference is that this is a developer event, you know, ordinarily you go to conferences and it's geared toward it managers towards CIOs. This is very much geared toward developers when you have the hearts and minds of developers, the rest of the industry is sort of pulled along with it. So this is ground zero for the hottest, uh, the, the hottest area of the entire computing industry. Right now, I is in this area building distributed services, BA microservices based cloud native applications. And it's the developers who are leading the way. I think that's, that's a significant shift. I don't see the managers here, the CIOs here, these are the people who are, uh, who are pulling this industry into the next generation. >>Um, one of the interesting things that I've seen when we, you know, we've always said, Kubernetes is for the developers, but we talk with, uh, an icon from, uh, MoneyGram. Who's a end user, he's an enterprise architect. And he brought Kubernetes to his front end developers and they, they, they kind of rejected it. They said, what is this? I just wanna develop cold. So when we say Kubernetes is for developers, or the developers are here, where, how do we reconcile that mismatch of experience? We have enterprise architecture. I hear constantly that, that the, uh, Kubernetes is for developers, but is it a certain kind of developer that Kubernetes is for? >>Well, yes and no. I mean, so the paradigm is changing. Okay. So, and maybe a few years back, it was tough to understand how, you know, uh, uh, make your application different. So microservices, everything was new for everybody, but actually, so everything is changed to a point. Now, the developer understands, you know, it is neural. So, you know, going through the application APIs automation, because the complexity of this application is, is huge. And you have, you know, 7 24 kind of development, uh, sort of deployment. So you have to stay always on cetera, et cetera. And actually to the point of, you know, developers, uh, you know, bringing this new generation of, uh, decision makers in India. So they are actually decision, they are adopting technology. Maybe it's a sort of shadow it at the very beginning. So they're adopting it, they're using it. And they're starting to use a lot of open source stuff. And then somebody upper in the stack, the executive says, what are, yeah, they, they discover that the technology is already in place is, uh, is a critical component. And then it's, uh, you know, uh, transformed in something enterprise, meaning, you know, paying enterprise services on top of it to be sure con uh, contract and so on. So it's a real journey. And these are, these guys are the real decision makers. Oh, they are at the base of the decision making process. At least >>Cloud native is something we're gonna learn to take for granted. You know, when you remember back, remember the fail whale in the early days of Twitter, when periodically the service would just would just, uh, um, crash from, uh, from, uh, traffic or Amazon went through the same thing. Facebook went through the same thing. We don't see that anymore because we are now learning to take cloud native for granted. We assume applications are gonna be available. They're gonna be performant. They're gonna scale. They're gonna handle anything. We throw at them that is cloud native at work. And I think we, we forget sometimes how refreshing it is to have, uh, an internet that really works for you. >>Yeah. I, I think we're much earlier in the journey. You know, we have Microsoft, uh, on the Xbox team talked about 22,000 pods running ni D some of the initial problems and pain points of, uh, around those challenges. Uh, much of my hallway track conversation has been centered around as we talk about kind of the decision makers, the platform teams. And this is what I'm getting excited to talk about in tomorrow's coverage. Who's on the ground doing this stuff. Is it developers as we are, as, as we see or hear or told, or is it what we're seeing from the Microsoft example, the MoneyGram example where central it is kind of getting it, and not only are they getting it, they're enabling developers to, to simply write code, build it. And Kubernetes is invisible. It seems like that's become the holy grill to make Kubernetes invisible cloud native invisible, and the experience is much closer to cloud. >>So I, I think that, uh, um, it's an interesting, I mean, I had a lot of conversation in the past year is that it's not that the original, you know, traditional it operations are disappearing. So it's just that, uh, traditional it operation are giving resources to these new developers. Okay. So it's a, it's a sort of walled garden. You don't see the wall, but it's a walled garden. So they are giving you resources and you use these resources like an internal cloud. So a few years back, we were talking about private cloud, the private cloud, as, you know, as a, let's say, uh, the same identical paradigm of, of the public cloud. This is not possible because there are no infinite resources or, well, whatever we, we think are infinite resources. So what you're doing today is giving these developers enough resources to think that they are unlimited and they can, uh, do automatic provisioning and do all these kind of things. So they don't think about infrastructure at all, but actually it's there. So it operation are still there providing resources to let developers be more free and agile and everything. So we are still in a, I think in an interesting time for all of it, >>Kubernetes and cloud native in general, I think are blurring the lines, traditional lines development and operations always were separate entities, obviously through with DevOps. Those two are emerging, but now we're moving. When you add in shift left testing shift, right? Testing, uh, dev SecOps, you see the developers become much more involved in the infrastructure and they want to be involved in infrastructure because that's what makes their applications perform. So this is gonna, cause I think it organizations to have, do some rethinking about what those traditional lines are, maybe break down those walls and have these teams work, work much closer together. And that should be a good thing because the people who are developing applications should also have intimate knowledge of the infrastructure they're gonna run on. >>So Paul, another recurring theme that we've heard here is the impact of funding on resources. What have you, what have your discussions been around founders and creators when it comes to sourcing talent and the impact of the markets on just their day to day? >>Well, the sourcing talent has been a huge issue for the last year. Of course, really ever since the pandemic started interesting. We, uh, one of our, our guests earlier today said that with the meltdown in the tech stock market, actually talent has become more available because people who were tied to their companies because of their, their stock options are now seeing those options are underwater. And suddenly they're not as loyal to the companies they joined. So that's certainly for the, for the startups. Uh, there are many small startups here. Um, they're seeing a bit of a windfall now from the, uh, from the tech stock, uh, bust, um, nevertheless skills are a long term problem. The us, uh, educational system is turning out about 10% of the skilled people that the industry needs every year. And no one I know, sees an end to that issue anytime soon. >>So ENGO, last question to you, let's talk about what that means to the practitioner. There's a lot of opportunity out >>There. >>200 plus sponsors I hear here I think is, or the projects is 200 plus, where are the big opportunities as a practitioner, as I'm thinking about the next thing that I'm going to learn to help me survive the next 10 or 15 years of my career? Where, where do you think the focus should be? Should it be that low level, uh, cloud builder, or should it be at those Le levels of extraction that we're seeing and reading about? >>I, I think, I think that, uh, you know, it's, uh, it's a good question. The, the answer is not that easy. I mean, uh, being a developer today, for sure grants, you, you know, uh, a salary at the end of the month, I mean, there is high demand, but actually there are a lot of other technical, uh, figures in, in the, in, uh, in the data center in the cloud that could, you know, really find easily a job today. So developers is the first in my mind also because they are more, uh, they, they can serve multiple roles. It means you can be a developer, but actually you can be also, you know, with the new roles that we have, especially now with the DevOps, you can be, uh, somebody that supports operation because, you know, automation, you know, a few other things. So you can be a C admin of the next generation, even if you're a developer, even if when you start as a developer, >>Cuan 20, 22 is exciting. I don't care if you're a developer practitioner, a investor, a, uh, it decision maker is CIO CXO. They're so much to learn and absorb here and we're going to be covering it for the next two days. Me and Paul will be shoulder to shoulder. We will, you, I'm not gonna say you're gonna get sick of this because it's just, you know, it's all great information. We'll, we'll, we'll help sort all of this from Valencia Spain. I'm Keith Townsend, along with my host ENCO senior, the Paul Gillon. And you're watching the, you, the leader in high tech coverage.

>>The cube presents, Coon and cloud native con Europe 22, brought to you by the cloud native computing foundation. >>Welcome to Melissa Spain. And we're at cuon cloud native con Europe, 2022. I'm Keith Townsend. And my co-host en Rico senior Etti en Rico's really proud of me. I've called him en Rico and said IK, every session, senior it analyst giga, O we're talking to fantastic builders at Cuban cloud native con about the projects and the efforts en Rico up to this point, it's been all about provisioning insecurity. What, what conversation have we been missing? >>Well, I mean, I, I think, I think that, uh, uh, we passed the point of having the conversation of deployment of provisioning. You know, everybody's very skilled, actually everything is done at day two. They are discovering that, well, there is a security problem. There is an observability problem. And in fact, we are meeting with a lot of people and there are a lot of conversation with people really needing to understand what is happening. I mean, in their classroom, what, why it is happening and all the, the questions that come with it. I mean, and, uh, the more I talk with, uh, people in the, in the show floor here, or even in the, you know, in the various sessions is about, you know, we are growing, the, our clusters are becoming bigger and bigger. Uh, applications are becoming, you know, bigger as well. So we need to know, understand better what is happening. It's not only, you know, about cost it's about everything at the >>End. So I think that's a great set up for our guests, max, Provo, founder, and CEO of storm for forge and Patrick Britton, Bergstrom, Brookstone. Yeah, I spelled it right. I didn't say it right. Berg storm CTO. We're at Q con cloud native con we're projects are discussed, built and storm forge. I I've heard the pitch before, so forgive me. And I'm, I'm, I'm, I'm, I'm, I'm kind of torn. I have service mesh. What do I need more like, what problem is storm for solving? >>You wanna take it? >>Sure, absolutely. So it it's interesting because, uh, my background is in the enterprise, right? I was an executive at United health group. Um, before that I worked at best buy. Um, and one of the issues that we always had was, especially as you migrate to the cloud, it seems like the CPU dial or the memory dial is your reliability dial. So it's like, oh, I just turned that all the way to the right and everything's hunky Dory. Right. Uh, but then we run into the issue like you and I were just talking about where it gets very, very expensive, very quickly. Uh, and so my first conversations with Matt and the storm forge group, and they were telling me about the product and, and what we're dealing with. I said, that is the problem statement that I have always struggled with. And I wish this existed 10 years ago when I was dealing with EC two costs, right? And now with Kubernetes, it's the same thing. It's so easy to provision. So realistically, what it is is we take your raw telemetry data and we essentially monitor the performance of your application. And then we can tell you using our machine learning algorithms, the exact configuration that you should be using for your application to achieve the results that you're looking for without over provisioning. So we reduce your consumption of CPU of memory and production, which ultimately nine times outta 10, actually I would say 10 out of 10 reduces your cost significantly without sacrificing reliability. >>So can your solution also help to optimize the application in the long run? Because yes, of course, yep. You know, the lowing fluid is, you know, optimize the deployment. Yeah. But actually the long term is optimizing the application. Yes. Which is the real problem. >>Yep. So we actually, um, we're fine with the, the former of what you just said, but we exist to do the latter. And so we're squarely and completely focused at the application layer. Um, we are, uh, as long as you can track or understand the metrics you care about for your application, uh, we can optimize against it. Um, we love that we don't know your application. We don't know what the SLA and SLO requirements are for your app. You do. And so in, in our world, it's about empowering the developer into the process, not automating them out of it. And I think sometimes AI and machine learning sort of gets a bad wrap from that standpoint. And so, uh, we've at this point, the company's been around, you know, since 2016, uh, kind of from the very early days of Kubernetes, we've always been, you know, squarely focused on Kubernetes using our core machine learning, uh, engine to optimize metrics at the application layer, uh, that people care about and, and need to need to go after. And the truth of the matter is today. And over time, you know, setting a cluster up on Kubernetes has largely been solved. Um, and yet the promise of, of Kubernetes around portability and flexibility, uh, downstream when you operationalize the complexity, smacks you in the face. And, uh, and that's where, where storm forge comes in. And so we're a vertical, you know, kind of vertically oriented solution. Um, that's, that's absolutely focused on solving that problem. >>Well, I don't want to play, actually. I want to play the, uh, devils advocate here and, you know, >>You wouldn't be a good analyst if you didn't. >>So the, the problem is when you talk with clients, users, they, there are many of them still working with Java with, you know, something that is really tough. Mm-hmm <affirmative>, I mean, we loved all of us loved Java. Yeah, absolutely. Maybe 20 years ago. Yeah. But not anymore, but still they have developers. They are porting applications, microservices. Yes. But not very optimized, etcetera. C cetera. So it's becoming tough. So how you can interact with these kind of yeah. Old hybrid or anyway, not well in generic applications. >>Yeah. We, we do that today. We actually, part of our platform is we offer performance testing in a lower environment and stage. And we like Matt was saying, we can use any metric that you care about and we can work with any configuration for that application. So the perfect example is Java, you know, you have to worry about your heap size, your garbage collection tuning. Um, and one of the things that really struck, struck me very early on about the storm forage product is because it is true machine learning. You remove the human bias from that. So like a lot of what I did in the past, especially around SRE and, and performance tuning, we were only as good as our humans were because of what they knew. And so we were, we kind of got stuck in these paths of making the same configuration adjustments, making the same changes to the application, hoping for different results. But then when you apply machine learning capability to that, the machine will recommend things you never would've dreamed of. And you get amazing results out of >>That. So both me and an Rico have been doing this for a long time. Like I have battled to my last breath, the, the argument when it's a bare metal or a VM. Yeah. Look, I cannot give you any more memory. Yeah. And the, the argument going all the way up to the CIO and the CIO basically saying, you know what, Keith you're cheap, my developer resources expensive, my bigger box. Yep. Uh, buying a bigger box in the cloud to your point is no longer a option because it's just expensive. Talk to me about the carrot or the stick as developers are realizing that they have to be more responsible. Where's the culture change coming from? So is it, that is that if it, is it the shift in responsibility? >>I think the center of the bullseye for us is within those sets of decisions, not in a static way, but in an ongoing way, especially, um, especially as the development of applications becomes more and more rapid. And the management of them, our, our charge and our belief wholeheartedly is that you shouldn't have to choose, you should not have to choose between costs or performance. You should not have to choose where your, you know, your applications live, uh, in a public private or, or hybrid cloud environment. And so we want to empower people to be able to sit in the middle of all of that chaos and for those trade-offs and those difficult interactions to no, no longer be a thing. You know, we're at, we're at a place now where we've done, you know, hundreds of deployments and never once have we met a developer who said, I'm really excited to get outta bed and come to work every day and manually tune my application. <laugh> One side, secondly, we've never met, uh, you know, uh, a manager or someone with budget that said, uh, please don't, you know, increase the value of my investment that I've made to lift and shift us over mm-hmm <affirmative>, you know, to the cloud or to Kubernetes or, or some combination of both. And so what we're seeing is the converging of these groups, um, at, you know, their happy place is the lack of needing to be able to, uh, make those trade offs. And that's been exciting for us. So, >>You know, I'm listening and looks like that your solution is right in the middle in application per performance management, observability. Yeah. And, uh, and monitoring. So it's a little bit of all of this. >>So we, we, we, we want to be, you know, the Intel inside of all of that, mm-hmm, <affirmative>, we don't, you know, we often get lumped into one of those categories. It used to be APM a lot. We sometimes get a, are you observability or, and we're really not any of those things in and of themselves, but we, instead of invested in deep integrations and partnerships with a lot of those, uh, with a lot of that tooling, cuz in a lot of ways, the, the tool chain is hardening, uh, in a cloud native and, and Kubernetes world. And so, you know, integrating in intelligently staying focused and great at what we solve for, but then seamlessly partnering and not requiring switching for, for our users who have already invested likely in a APM or observability. >>So to go a little bit deeper. Sure. What does it mean integration? I mean, do you provide data to this, you know, other applications in, in the environment or are they supporting you in the work that you >>Yeah, we're, we're a data consumer for the most part. Um, in fact, one of our big taglines is take your observability and turn it into actionability, right? Like how do you take the it's one thing to collect all of the data, but then how do you know what to do with it? Right. So to Matt's point, um, we integrate with folks like Datadog. Um, we integrate with Prometheus today. So we want to collect that telemetry data and then do something useful with it for you. >>But, but also we want Datadog customers. For example, we have a very close partnership with, with Datadog, so that in your existing data dog dashboard, now you have yeah. This, the storm for capability showing up in the same location. Yep. And so you don't have to switch out. >>So I was just gonna ask, is it a push pull? What is the developer experience? When you say you provide developer, this resolve ML, uh, learnings about performance mm-hmm <affirmative> how do they receive it? Like what, yeah, what's the, what's the, what's the developer experience >>They can receive it. So we have our own, we used to for a while we were CLI only like any good developer tool. Right. Uh, and you know, we have our own UI. And so it is a push in that, in, in a lot of cases where I can come to one spot, um, I've got my applications and every time I'm going to release or plan for a release or I have released, and I want to take, pull in, uh, observability data from a production standpoint, I can visualize all of that within the storm for UI and platform, make decisions. We allow you to, to set your, you know, kind of comfort level of automation that you're, you're okay with. You can be completely set and forget, or you can be somewhere along that spectrum. And you can say, as long as it's within, you know, these thresholds, go ahead and release the application or go ahead and apply the configuration. Um, but we also allow you to experience, uh, the same, a lot of the same functionality right now, you know, in Grafana in Datadog, uh, and a bunch of others that are coming. >>So I've talked to Tim Crawford who talks to a lot of CIOs and he's saying one of the biggest challenges, or if not, one of the biggest challenges CIOs are facing are resource constraints. Yeah. They cannot find the developers to begin with to get this feedback. How are you hoping to address this biggest pain point for CIOs? Yeah. >>Development? >>Just take that one. Yeah, absolutely. That's um, so like my background, like I said, at United health group, right. It's not always just about cost savings. In fact, um, the way that I look about at some of these tech challenges, especially when we talk about scalability, there's kind of three pillars that I consider, right? There's the tech scalability, how am I solving those challenges? There's the financial piece, cuz you can only throw money at a problem for so long. And it's the same thing with the human piece. I can only find so many bodies and right now that pool is very small. And so we are absolutely squarely in that footprint of, we enable your team to focus on the things that they matter, not manual tuning like Matt said. And then there are other resource constraints that I think that a lot of folks don't talk about too. >>Like we were, you were talking about private cloud for instance. And so having a physical data center, um, I've worked with physical data centers that companies I've worked for have owned where it is literally full wall to wall. You can't rack any more servers in it. And so their biggest option is, well, I could spend 1.2 billion to build a new one if I wanted to. Or if you had a capability to truly optimize your compute to what you needed and free up 30% of your capacity of that data center. So you can deploy additional name spaces into your cluster. Like that's a huge opportunity. >>So either out of question, I mean, may, maybe it, it doesn't sound very intelligent at this point, but so is it an ongoing process or is it something that you do at the very beginning mean you start deploying this. Yeah. And maybe as a service. Yep. Once in a year I say, okay, let's do it again and see if something changes. Sure. So one spot 1, 1, 1 single, you know? >>Yeah. Um, would you recommend somebody performance tests just once a year? >>Like, so that's my thing is, uh, previous at previous roles I had, uh, my role was you performance test, every single release. And that was at a minimum once a week. And if your thing did not get faster, you had to have an executive exception to get it into production. And that's the space that we wanna live in as well as part of your C I C D process. Like this should be continuous verification every time you deploy, we wanna make sure that we're recommending the perfect configuration for your application in the name space that you're deploying >>Into. And I would be as bold as to say that we believe that we can be a part of adding, actually adding a step in the C I C D process that's connected to optimization and that no application should be released monitored and sort of, uh, analyzed on an ongoing basis without optimization being a part of that. And again, not just from a cost perspective, yeah. Cost end performance, >>Almost a couple of hundred vendors on this floor. You know, you mentioned some of the big ones, data, dog, et cetera. But what happens when one of the up and comings out of nowhere, completely new data structure, some imaginable way to click to elementry data. Yeah. How do, how do you react to that? >>Yeah. To us it's zeros and ones. Yeah. Uh, and you know, we're, we're, we're really, we really are data agnostic from the standpoint of, um, we're not, we we're fortunate enough to, from the design of our algorithm standpoint, it doesn't get caught up on data structure issues. Um, you know, as long as you can capture it and make it available, uh, through, you know, one of a series of inputs, what one, one would be load or performance tests, uh, could be telemetry, could be observability if we have access to it. Um, honestly the messier, the, the better from time to time, uh, from a machine learning standpoint, um, it, it, it's pretty powerful to see we've, we've never had a deployment where we, uh, where we saved less than 30% while also improving performance by at least 10%. But the typical results for us are 40 to 60% savings and, you know, 30 to 40% improvement in performance. >>And what happens if the application is, I, I mean, yes, Kubernetes is the best thing of the world, but sometimes we have to, you know, external data sources or, or, you know, we have to connect with external services anyway. Mm-hmm <affirmative> yeah. So can you, you know, uh, can you provide an indication also on, on, on this particular application, like, you know, where the problem could >>Be? Yeah, yeah. And that, that's absolutely one of the things that we look at too, cuz it's um, especially when you talk about resource consumption, it's never a flat line, right? Like depending on your application, depending on the workloads that you're running, um, it varies from sometimes minute to minute, day to day, or it could be week to week even. Um, and so especially with some of the products that we have coming out with what we want to do, you know, partnering with, uh, you know, integrating heavily with the HPA and being able to handle some of those bumps and not necessarily bumps, but bursts and being able to do it in a way that's intelligent so that we can make sure that, like I said, it's the perfect configuration for the application regardless of the time of day that you're operating in or what your traffic patterns look like. Um, or you know, what your disc looks like, right? Like cuz with our, our low environment testing, any metric you throw at us, we can, we can optimize for. >>So Madden Patrick, thank you for stopping by. Yeah. Yes. We can go all day. Because day two is I think the biggest challenge right now. Yeah. Not just in Kubernetes, but application replatforming and re and transformation. Very, very difficult. Most CTOs and S that I talked to, this is the challenge space from Valencia Spain. I'm Keith Townsend, along with my host en Rico senior. And you're watching the queue, the leader in high tech coverage.

>>The cube presents, Coon and cloud native con Europe 22, brought to you by the cloud native computing foundation. >>Welcome to Valencia Spain in co con cloud native con Europe, 2022. I'm Keith Townsend with my cohos on Rico senior. Etti senior it analyst at gig home. Exactly 7,500 people I'm told en Rico. What's the flavor of the show so far, >>It's a fantastic mood. I mean, I found a lot of people wanting to track talk about what they're doing with Kubernetes, sharing their, you know, stories, some word stories that meet tough. And you know, this is where you learn actually, because we had a lot of zoom calls, webinar and stuff, but it is when you talk a video, oh, I did it this way and it didn't work out very well. So, and, and you start a conversation like this that is really different from learning from zoom. When, you know, everybody talks about things that working well, they did it, right. No, it's here that you learn from other experiences. >>So we're talking to amazing people the whole week, talking about those experiences here on the queue, fresh on the queue for the first time, Chris Vos, senior software engineer at Microsoft Xbox, Chris, welcome to the queue. >>Thank you so much for having >>Me. So first off, give us a high level picture of the environment that you're running at Microsoft. >>Yeah. So, you know, we've got 20, well probably close to 30 clusters at this point around the globe, you know, 700 to a thousand pods per cluster, roughly. So about 22,000 pods total. So yeah, it's pretty pretty sizable footprint and yeah. So we've been running on Kubernetes since 2018 and well actually might be 2017, but anyways, so yeah, that, that's kind of our, our footprint. >>Yeah. So all of that, let's talk about the basics, which is security across multiple I'm assuming containers, work, microservices, et cetera. Why did you and the team settle on link or do >>Yeah, so previously we had our own kind of solution for managing TLS certs and things like that. And we found it to be pretty painful pretty quickly. And so we knew, you know, we wanted something that was a little bit more abstracted away from the developers and, and things like that that allowed us to move quickly. And so we began investigating, you know, solutions to that. And a few of our colleagues went to Cuban in San Diego in 2019 cloud native con as well. And basically they just, you know, sped it all up. And actually funny enough, my, my old manager was one of the people who was there and he went to the link D booth and they had a thing going that was like, Hey, get set up with MTLS in five minutes. And he was like, this is something we want to do, why not check this out? And he was able to do it. And so that, that put it on our radar. And so yeah, we investigated several others and Leer D just perfectly fit exactly what we needed. >>So, so in general, we are talking about, you know, security at scale. So how you manage security to scale and also flexibility, right. But you know, what is the you, this there, you told us about the five minutes to start using there, but you know, again, we are talking about word stories. We talk about, you know, all these. So what, what, what kind of challenges you found at the beginning when you start adopting this technology? >>So the biggest ones were around getting up and running with like a new service, especially in the beginning, right. We were, you know, adding a new service almost every day. It felt like. And so, you know, basically it took someone going through a whole bunch of different repos, getting approvals from everyone to get the SEARCHs minted, all that fun stuff, getting them put into the right environments and in the right clusters to make sure that, you know, everybody is talking appropriately. And just the amount of work that, that took alone was just a huge headache and a huge barrier to entry for us to, you know, quickly move up the number of services we have. So, >>So I'm, I'm trying to wrap my head around the scale of the challenge. When I think about certification or certificate management, I have to do it on a small scale and the, the, every now and again, when a certificate expires, it is just a troubleshooting pain. Yes. So as I think about that, it costs, it's not just certificates across 22,000 pods or it's certificates across 22,000 pods in multiple applications. How were you doing that before link D like, what was the, what and what were the pain points? Like? What happens when a certificate either fails or expired up not, not updated? >>So, I mean, to be completely honest, the biggest thing is we're just unable to make the calls, you know, out or, or in, based on yeah. What is failing basically. But, you know, we saw essentially an uptick in failures around a certain service and pretty quickly, I pretty quickly, we got used to the fact that it was like, oh, it's probably a cert expiration issue. And so we tried, you know, a few things in order to make that a little bit more automated and things like that, but we never came to a solution that like didn't require every engineer on the team to know essentially quite a bit about this, just to get into it, which was a huge issue. >>So talk about day two after you've deployed link D how did this alleviate software engineers and what was like the, the benefits of now having this automated way of managing >>Certs? So the biggest thing is like, there is no touch from developers, everyone on our team. Well, I mean, there are a lot of people who are familiar with security and certs and all of that stuff, but no one has to know it. Like it's not a requirement. Like for instance, I knew nothing about it when I joined the team. And even when I was setting up our newer clusters, I knew very little about it. And I was still able to really quickly set up blinker D, which was really nice. And, and it's been, you know, essentially we've been able to just kind of set it and not think about it too much. Obviously, you know, there are parts of it that you have to think about. We monitor it and all that fun stuff, but, but yeah, it's been pretty painless almost day one. It took a lot, a long time to trust it for developers. You know, anytime there was a failure, it's like, oh, could this be link or D you know, but after a while, like now we don't have that immediate assumption because people have built up that trust, but >>Also you have this massive infrastructure, I mean, 30 cluster. So I guess that it's quite different to manage a single cluster and 30. So what are the, you know, consideration that you have to do to install this software on, you know, 30 different cluster manage different, you know, versions probably etcetera, etcetera, et cetera. >>So, I mean, you know, the, the, as far as like, I guess, just to clarify, are you asking specifically with Linky or are you just asking in more in general? Well, >>I mean, you, you can take the, the question in the, in two ways, so, okay. Yeah. Yes. Link in particular, but the 30 cluster also quite interesting. >>Yeah. So, I mean, you know, more generally, you know, how we manage our clusters and things like that. We have, you know, a CLI tool that we use in order to like, change context very quickly and switch and communicate with whatever cluster we're trying to connect to and, you know, are we debugging or getting logs, whatever. And then, you know, with link D it's nice because again, you know, we, we, aren't having to worry about like, oh, how is this cert being inserted in the right node or, or not the right node, but in the right cluster or things like that. Whereas with link D we don't, we don't really have that concern when we spin up our, our clusters, essentially we get the root certificate and, and everything like that packaged up, passed along to link D on installation. And then essentially there's not much we have to do after that. >>So talk to me about your upcoming coming section here at Q con what's the, what's the high level talking points? Like what, what will attendees learn? >>Yeah. So it's, it's a journey. Those are the sorts of talks that I find useful. Having not been, you know, I, I'm not a deep Kubernetes expert from, you know, decades or whatever of experience, but I think >>Nobody is >>Also true. That's another story. That's a, that's, that's a job posting decades of requirements for >>Of course. Yeah. But so, you know, it, it's a journey it's really just like, Hey, what made us decide on a service mesh in the first place? What made us choose link D and then what are the ways in which, you know, we, we use link D so what are those, you know, we use some of the extra plugins and things like that. And then finally, a little bit about more, what we're gonna do in the future. >>Let's talk about not just necessarily the future as in two or three days from now, or two or three years from now. Well, the future after you immediately solve the, the low level problems with link D what were some of the, the surprises, because link D in service me in general has have side benefits. Do you experience any of those side benefits as well? >>Yeah, it's funny, you know, writing the, the blog post, you know, I hadn't really looked at a lot of the data in years on, you know, when we did our investigations and things like that. And we had seen that we like had very low latency and low CPU utilization and things like that. And looking at some of that, I found that we were actually saving time off of requests. And I couldn't really think of why that was, and I was talking with someone else and the biggest, unfortunately, all that data's gone now, like the source data. So I can't go back and verify this, but it, it makes sense, you know, there's the availability zone routing that linker D supports. And so I think that's actually doing it where, you know, essentially if a node is closer to another node, it's essentially, you know, routing to those ones. So when one service is talking to another service and maybe on they're on the same node, you know, it, it short circuits that, and allows us to gain some, some time there. It's not huge, but it adds up after, you know, 10, 20 calls down the line. Right. >>In general. So you are saying that it's smooth operations in, in ATS, very, you know, simplifying your life. >>And again, we didn't have to really do anything for that. It, it, it handled that for it was there. Yeah. Yep. Yeah, exactly. >>So we know one thing when I do it on my laptop, it works fine when I do it with across 22,000 pods, that's a different experience. What were some of the lessons learned coming out of KU con 2018 in San Diego was there? I wish I would've ran to the microphone folks, but what were some of the hard lessons learned scaling link D across the 22,000 nodes? >>So, you know, the, the first one, and this seems pretty obvious, but was just not something I knew about was the high availability mode of link D so obviously makes sense. You would want that in a, you know, a large scale environment. So like, that's one of the big lessons that like, we didn't ride away. No. Like one of the mistakes we made in, in one of our pre-production clusters was not turning that on. And we were kind of surprised. We were like, whoa, like all of these pods are spinning up, but they're having issues like actually getting injected and things like that. And we found, oh, okay. Yeah, you need to actually give it some, some more resources, but it's still very lightweight considering, you know, they have high availability mode, but it's just a few instances still. >>So from, even from a, you know, binary perspective and running link D how much overhead is it? >>That is a great question. So I don't remember off the top of my head, the numbers, but it's very lightweight. We, we evaluated a few different service missions and it was the lightest weight that we encountered at that point. >>And then from a resource perspective, is it a team of link D people? Is it a couple of people, like how >>To be completely honest for a long time, it was one person, Abraham who actually is the person who proposed this talk. He couldn't make it to Valencia, but he essentially did probably 95% of the work to get a into production. And then this was before we even had a team dedicated to our infrastructure. And so we have, now we have a team dedicated, we're all kind of Linky folks, if not Linky experts, we at least can troubleshoot basically. And things like that. So it's, I think a group of six people on our team, and then, you know, various people who've had experience with it >>On other teams, but I'm not dedicated just to that. >>I mean, >>No one is dedicated just to it. No, it's pretty like pretty light touch once it's, once it's up and running, it took a very long time for us to really understand it and, and to, you know, get like, not getting started, but like getting to where we really felt comfortable letting it go in production. But once it was there, like, it is very, very light touch. >>Well, I really appreciate you stopping by Chris. It's been an amazing conversation to hear how Microsoft is using a open source project. Exactly. At scale. It's just a few years ago, when you would've heard the concept of Microsoft and open source together and like, oh, that's just, you know, but >>They have changed a lot in the last few years now, there are huge contributors. And, you know, if you go to Azure, it's full of open source stuff, every >>So, yeah. Wow. The Cuban 2022, how the world has changed in so many ways from Licia Spain, I'm Keith Townsend, along with a Rico senior, you're watching the, the leader in high tech coverage.

>>The cube presents, Coon and cloud native con Europe 22, brought to you by the cloud native computing foundation. >>Welcome to vincia Spain in Coon cloud native con Europe, 2022. I'm Keith towns alongside en Rico senior. Etti senior it analyst for giong welcome back to the show en >>Rico. Thank you again for having me here. >>First impressions of QAN. >>Well, great show. As, as I mentioned before, I think that we are really in this very positive mode of talking with each other and people wanting to see, you know, the projects, people that build the projects at it's amazing. I mean, a lot of interesting conversation in the show floor and in the various sessions, very positive move. >>So this is gonna be a fun one. We have some amazing builders on the show this week, and none other than William Morgan, CEO of buoyant. What's your role in the link D project? >>So I was one of the original creators of link D but at this point I'm just the, the beautiful face of the project. >>Speaking of beautiful face of the project, linker D just graduated from as a CNCF project. >>Yeah, that's right. So last year we, we became the first service mesh to graduate in the CNCF. Very proud of that. And that's thanks, you know, largely to the incredible community around Linky that is just excited about the project and, you know, wants to talk about it and wants to be involved. >>So let's talk about the significance of that link D not the only service mesh project out there. Talk to me about the level effort to get it to the point that it's graduated. That's you don't see too many projects graduating CNCF in general. So let's talk about kind of the work needed to get Nier D to this point. >>Yeah. So, you know, the, the, the bar is high and it's mostly a measure, not necessarily of like the, the project being technically good or bad or anything, but it's really a measure of maturity of the community around it. So is it being adopted by organizations that are really relying on it in a critical way? Is it, you know, being adopted across industries, you know, is it having kind of a significant impact on the cloud native community? And so for us, you know, there was the, the work involved in that was really not any different from the work involved in, in kind of maintaining ity and growing the community in the first place, which is you try and make it really useful. You try and make it really easy to get started with you, try and be supportive and to, you know, have a, a friendly and welcoming community. And if you do those things and, you know, you kind of naturally get yourself to the point where it's a, it's a really strong community full of people who are excited about it. >>So from the of view of, you know, users adopting the, this technology, so we are talking about everybody, or do you see really, you know, large organization, large Kubernetes yeah. Clusters infrastructure adopting it. >>Yeah. So that's the answer to that is changed a little bit over time. But at this point we see Linky adoption across industries, across verticals, and we see it from very small companies to very large ones. So, you know, one of the talks I'm really excited about at this conference is from the folks at Xbox cloud gaming, who talked about, who are gonna talk about how they deployed Linky across, you know, 22,000 pods around the world to serve, you know, basically on demand video games, never a use case I would ever have imagined for Linky. And at the previous Kuan, you know, virtually Kuan EU, we had a whole keynote about how Linky was used to combat COVID 19. So all sorts of uses. And it really doesn't, you know, whether, whether it's a small cluster or large cluster it's equally applicable. >>Wow. So as we talk about link D service match, we obviously are gonna talk about security application control, etcetera. But in this climate Software supply chain is critical, right. And as we think about open source software supply chain, talk to us about the recent security audit of link dealer. >>Yeah. So one of the things that we do as part of a CNCF project, and also as part of, I, I think our relationship with our community is we have regular security audits, you know, where we, we engage security professionals who are very thorough and, you know, dig into all the details. Of course the source code is all out there, you know, so anyone can read through the code, but they'll build threat model analyses and things like that. And then we take their, their report and we publish it. We say, Hey, look, here's, you know, here's the situation. So we have earlier reports online, and this newest one was done by a company called trail of bits. And they built a whole threat model and looked through all the different ways that Linky could go wrong. And they always find issues. Of course, you know, it's, it would be very scary, I think, to get a report that was like, no, we didn't find yeah. Earth clean, you know? Yeah. Everything's fine. You know, should be okay. I don't know. Right. But they, you know, they did not find anything critical. They found some issues that we rapidly addressed and then, you know, everything gets written up in the report and, and then we publish it, you know, as part of an open source artifact >>Are, you let's say, you know, do they give you and add something? So if something happens so that you can act on the code before, you know, somebody else discovers the >>Yeah, yeah. They'll give you a preview of what they found. And then often, you know, it's not like you're going before the judge and the judge makes a judgment and then like off the jail, right. It's, it's a dialogue because they don't necessarily understand the project. Well, they definitely don't understand it as well as you do. So you are helping them, you know, understand which parts and, and your, you know, are, are interesting to look at from the security perspective, which parts are not that interesting. They do their own investigation of course, but it's a dialogue the entire time. So you do have an opportunity to say, oh, you told me that was a, a, a minor issue. I actually think that's larger or, or vice versa. You know, you, you think that's a big problem. Actually, we thought about that, and it's not a big problem because of whatever. So it's a collaborative process. >>So link D been around, like, when I first learned about service me link D was the project that I learned about. Yeah. It's been there for a long time, but just mentioned 22,000 clusters. That's just mind boggling pod, 22,000 pods, the pods. Okay. >>Clusters would be >>Great. Yeah. Yeah. Clusters would be great too, but filled 22 thousands pods, big deployment. That's the big deployment of link D but all the way down to the small, smallest set of pods as well. What are some of the recent project updates from of the learnings you bought back from the community and updated the, the project as a result? >>Yeah. So a big one for us, you know, on the topic of security link, a big driver of link adoption is security and, and less on the supply chain side and more on the traffic, like live traffic security. So things like mutual TLS. So you can encrypt the communication between pods and make sure it's authenticated. One of the recent feature additions is authorization policy. So you can lock down connections between services and you can say service a is only allowed to talk to service B. And I wanna do that. Not based on network identity, you know, and not based on like IP addresses, cuz those are spoof. And you know, we've kind of like as an industry moved, moved, we've gotten a little more advanced from that, but actually based on the workload identity, you know, as captured by the mutual TLS certificate exchange. So we give you the ability now to, to, to restrict the types of communication that are allowed to happen on your cluster. >>So, okay. This is what happened. What about the future? Can you give us, you know, into suggestion of what is going to happen in the medium and long term? >>I think we're done, you know, we graduated, so we're just gonna >>Stop there's >>What else is there to do? There's no grad school, you know? No, no. So for us, there's a clear roadmap ahead, continuing down the, the security realm, for sure. We've given you kind of the very first building block, which at the service level, but coming up in, in the two point 12 release, we'll have route based policy as well, as you can say, this service is only allowed to call these three, you know, routes on this end point and we'll be working later to do things like mesh expansion so we can run the data plane outside of Kubernetes. You know, so the control plane will stay in in Kubernetes, but the data plane will, you'll be able to run that on VMs and, and, and things like that. And then of course in the, you know, we're also starting to look at things like I like to make a fun of WAM a lot, but we are actually starting to look at WAM in, in the ways that that might actually be useful for Linky users. >>So we talk a lot about the flexibility of a project, like link D you can do amazing things with it from a security perspective, but we're talking still to a DevOps type cloud of, of, of developers who are spread thin across their skillset. How do you help balance the need for the flexibility, which usually becomes more nerd knobs and servicing a crowd that wants even higher levels of abstraction and simplicity. >>Yeah. Yeah. That's a great question. And this is, this is what makes Linky so unique in the service mesh spaces. We have a laser focus on simplicity and especially on operational simplicity. So our audience, you know, we can make it easy to install Linky, but what we really care about is when you're running it and you're on call for it and it's sitting in this critical, vulnerable part of your infrastructure, do you feel confident in that? Do you feel like you understand it? Do you feel like you can observe it? Do you feel like you can predict what it's gonna do? And so every aspect of Linky is designed to be as operationally simple as possible. So when we deliver features, you know, that's always our, our primary consideration is, you know, we have to reject the urge. You know, we have an urge as, as engineers to like want to build everything, you know, it's an ultimate platform to solve all problems and we have to really be disciplined and say, we're not gonna do that. >>We're gonna look at solving the minimum possible problem with a minimum set of features because we need to keep things simple. And, and then we need to look at the human aspect to that. And I think that's been a part of, of Link's success. And then on the buoyant side, of course, you know, I don't just work on link day. I also work on, on buoyant, which helps organizations adopt Linky and, and increasingly large organizations that are not service mesh experts don't wanna be service mesh experts that, you know, they wanna spend their time and energy developing their business, right. And, and building the business logic that powers their company. So for them, we have actually re recently introduced, fully managed. Linky where we can take on, even though Linky has to run on your cluster, right? The, the, the, the sidecar proxies has to be alongside your application. We can actually take on the operational burden of, of upgrades and trust, anchor rotation, and installation. And you can effectively treat it as a utility, right. And, and, and have a, a hosted, like, experience, even though the, the actual bits, at least most of them, not all of them, most of 'em have to live on your cluster. >>I love the focus of most CNCF projects, you know, it's, it's peanut butter or jelly, not peanut butter. Yeah. Trying to be become jelly. Right. What's the, what's the, what's the peanut butter to link D's jelly. Like where does link D stop and some of the things that customers should really consider yeah. When looking at service mesh. >>Yeah. No, that's a great way of looking at it. And I, I actually think that that philosophy comes from Kubernetes. I think Kubernetes itself, one of the reasons it was so successful is because it had some clearly delineated, it said, this is what we're gonna do. Right. And this is what we're not gonna do. So we're gonna do layer three, four networking. Right. But we're gonna stop there. We're not gonna do anything with layer seven. And that allowed the service mesh. So I guess if I were to go down the, the bread, the bread of the sandwich has Kubernetes, and then Linky is the, is the peanut butter, I guess, and then the jelly, you know, so I think the jelly is every other aspect of, of building a platform. Right. So if you are the, the audience for Linky, most of the time, it's a platform owners, right. They're building a platform, an internal platform for their developers to write code. And so, as part of that, of course, you've got Kubernetes, you've got Linky, but you've also got a C I CD system. You've also got a, you know, a code repository, if it's GitLab or, or GitHub or wherever you've got, you know, other kind of tools that are enforcing various other constraints. All of that is the jelly, you know, in the, this is, analogy's getting complicated now. And like the, the platform sandwich that, you know, that you're serving. >>So talk to us about trans and service mesh from the, from the, as we think of the macro. >>Yeah. Yeah. So, you know, it's been an interesting space because we were talking a little bit about, you know, about this before the show, but the, there was so much buzz, you know, and then what we, what we saw was basically it took two years for that buzz to become actual adoption, you know, and now a lot of the buzz is off on other exciting things. And the people who remain in the Linky space are, are very focused on, oh, I actually have a, a real problem that I need to solve and I need to solve it now. So that's been great. So in terms of broader trends, you know, I think one thing we've seen for sure is the service mesh space is kind of notorious for complexity, you know, and a lot of what we've been doing on the Linky side has been trying to, to reverse that, that, that idea, you know, because it doesn't actually have to be complex. There's interesting stuff you can do, especially when you get into the way we handle the sidecar model. It's actually really, it's a wonderful model operationally. It's really, it feels weird at first. And then you're like, oh, actually this makes my operations a lot easier. So a lot of the trends that I see at least for Linky is doubling down on the sidecar model, trying to make side cards as small and as thin as possible and try and make them, you know, kind of transparent to the rest of the application. So >>Well, William Morgan, one of the coolest Twitter handles I've seen at WM on Twitter, that's actually a really cool Twitter handle. Thank you, CEO of buoyant. Thank you for joining the cube again. Cube alum from Valencia Spain. I'm Keith towns, along with en Rico, and you're watching the cube, the leader in high tech coverage.

>>The cube presents, Coon and cloud native con Europe 22, brought to you by the cloud native computing foundation. >>Welcome to Valencia Spain and con cloud native con 20 Europe, 2022. I'm your host, Keith Townson alongside a new host en Rico senior reti, senior editor. I'm sorry, senior it analyst at giong Enrique. Welcome to the program. >>Thank you very much. And thank you for having me. It's exciting. >>So thoughts, high level thoughts of CU con first time in person again in couple years? >>Well, this is amazing for several reasons. And one of the reasons is that yeah, I had the chance to meet, uh, with, uh, you know, people like you again. I mean, we, we met several times over the internet, over zoom codes. I, I started to eat these zoom codes. <laugh> because they're very impersonal in the end. And like last night we, we are together group of friends, industry folks. It's just amazing. And a part of that, I mean, the event is, uh, is a really cool, it's really cool. There are a lot from people interviews and, you know, real people doing real stuff, not just, uh, you know, again, in personal calls, you don't even know if they're telling the truth, but when you can, you know, look in their eyes, what they're doing, I, I think that's makes a difference. >>So speaking about real people, meeting people for the first time, new jobs, new roles, Greg Moscarella enterprise container management in general manager at SUSE, welcome to the show, welcome back clue belong. >>Thank you very much. It's awesome to be here. It's awesome to be back in person. And I completely agree with you. Like there's a certain fidelity to the conversation and a certain, uh, ability to get to know people a lot more. So it's absolutely fantastic to be here. >>So Greg, tell us about your new role and what SUSE has gone on at KU con. >>Sure. So I joined SA about three months ago to lead the rancher business unit, right? So our container management pieces and, you know, it's a, it's a fantastic time. Cause if you look at the transition from virtual machines to containers and to moving to micro services, right alongside that transition from on-prem to cloud, like this is a very exciting time to be in this industry and rancher's been setting the stage. And again, I'm go back to being here. Rancher's all about the community, right? So this is a very open, independent, uh, community driven product and project. And so this, this is kinda like being back to our people, right. And being able to reconnect here. And so, you know, doing it, digital is great, but, but being here is changes the game for us. So we, we feed off that community. We feed off the energy. So, uh, and again, going back to the space and what's happening in it, great time to be in this space. And you guys have seen the transitions you've seen, I mean, we've seen just massive adoption, uh, of containers and Kubernetes overall, and rancher has been been right there with some amazing companies doing really interesting things that I'd never thought of before. Uh, so I'm, I'm still learning on this, but, um, but it's been great so far. >>Yeah. And you know, when we talk about strategy about Kubernetes today, we are talking about very broad strategies. I mean, not just the data center or the cloud with, you know, maybe smaller organization adopting Kubernetes in the cloud, but actually large organization thinking guide and more and more the edge. So what's your opinion on this, you know, expansion of Kubernetes towards the edge. >>So I think you're, I think you're exactly right. And that's actually a lot of meetings I've been having here right now is these are some of these interesting use cases. So people who, uh, whether it be, you know, ones that are easy to understand in the telco space, right? Especially the adoption of 5g and you have all these base stations, new towers, and they have not only the core radio functions or network functions that they're trying to do there, but they have other applications that wanna run on that same environment, uh, spoke recently with some of our, our good friends at a major automotive manufacturer, doing things in their factories, right. That can't take the latency of being somewhere else. Right? So they have robots on the factory floor, the latency that they would experience if they tried to run things in the cloud meant that robot would've moved 10 centimeters. >>By the time, you know, the signal got back, it may not seem like a lot to you, but if, if, if you're an employee, you know, there, you know, uh, a big 2000 pound robot being 10 centimeters closer to you may not be what you, you really want. Um, there's, there's just a tremendous amount of activity happening out there on the retail side as well. So it's, it's amazing how people are deploying containers in retail outlets. You know, whether it be fast food and predicting, what, what, how many French fries you need to have going at this time of day with this sort of weather. Right. So you can make sure those queues are actually moving through. It's, it's, it's really exciting and interesting to look at all the different applications that are happening. So yes, on the edge for sure, in the public cloud, for sure. In the data center and we're finding is people want to common platform across those as well. Right? So for the management piece too, but also for security and for policies around these things. So, uh, it really is going everywhere. >>So talk to me, how do, how are we managing that as we think about pushing stuff out of the data center, out of the cloud cloud, closer to the edge security and life cycle management becomes like top of mind thought as, as challenges, how is rancher and sushi addressing >>That? Yeah. So I, I think you're, again, spot on. So it's, it starts off with the think of it as simple, but it's, it's not simple. It's the provisioning piece. How do we just get it installed and running right then to what you just asked the management piece of it, everything from your firmware to your operating system, to the, the cluster, uh, the Kubernetes cluster, that's running on that. And then the workloads on top of that. So with rancher, uh, and with the rest of SUSE, we're actually tacking all those parts of the problems from bare metal on up. Uh, and so we have lots of ways for deploying that operating system. We have operating systems that are, uh, optimized for the edge, very secure and ephemeral container images that you can build on top of. And then we have rancher itself, which is not only managing your Kubernetes cluster, but can actually start to manage the operating system components, uh, as well as the workload components. >>So all from your single interface, um, we mentioned policy and security. So we, yeah, we'll probably talk about it more, um, uh, in a little bit, but, but new vector, right? So we acquired a company called new vector, just open sourced, uh, that here in January, that ability to run that level of, of security software everywhere again, is really important. Right? So again, whether I'm running it on, whatever my favorite public cloud providers, uh, managed Kubernetes is, or out at the edge, you still have to have security, you know, in there. And, and you want some consistency across that. If you have to have a different platform for each of your environments, that's just upping the complexity and the opportunity for error. So we really like to eliminate that and simplify our operators and developers lives as much as possible. >>Yeah. From this point of view, are you implying that even you, you are matching, you know, self, uh, let's say managed clusters at the, at the very edge now with, with, you know, added security, because these are the two big problems lately, you know, so having something that is autonomous somehow easier to manage, especially if you are deploying hundreds of these that's micro clusters. And on the other hand, you need to know a policy based security that is strong enough to be sure again, if you have these huge robots moving too close to you, because somebody act the class that is managing them, that could be a huge problem. So are you, you know, approaching this kind of problems? I mean, is it, uh, the technology that you are acquired, you know, ready to, to do this? >>Yeah. I, I mean, it, it really is. I mean, there's still a lot of innovation happening. Don't, don't get me wrong. We're gonna see a lot of, a lot more, not just from, from SA and rancher, but from the community, right. There's a lot happening there, but we've come a long way and we've solved a lot of problems. Uh, if I think about, you know, how do you have this distributed environment? Uh, well, some of it comes down to not just, you know, all the different environments, but it's also the applications, you know, with microservices, you have very dynamic environment now just with your application space as well. So when we think about security, we really have to evolve from a fairly static policy where like, you might even be able to set an IP address in a port and some configuration on that. It's like, well, your workload's now dynamically moving. >>So not only do you have to have that security capability, like the ability to like, look at a process or look at a network connection and stop it, you have to have that, uh, manageability, right? You can't expect an operator or someone to like go in and manually configure a YAML file, right? Because things are changing too fast. It needs to be that combination of convenient, easy to manage with full function and ability to protect your, your, uh, your resources. And I think that's really one of the key things that new vector really brings is because we have so much intelligence about what's going on there. Like the configuration is pretty high level, and then it just runs, right? So it's used to this dynamic environment. It can actually protect your workloads wherever it's going from pod to pod. Uh, and it's that, that combination, again, that manageability with that high functionality, um, that, that is what's making it so popular. And what brings that security to those edge locations or cloud locations or your data center >>Mm-hmm <affirmative> so one of the challenges you're kind of, uh, touching on is this abstraction on upon abstraction. When I, I ran my data center, I could put, uh, say this IP address, can't talk to this IP address on this port. Then I got next generation firewalls where I could actually do, uh, some analysis. Where are you seeing the ball moving to when it comes to customers, thinking about all these layers of abstraction I IP address doesn't mean anything anymore in cloud native it's yes, I need one, but I'm not, I'm not protecting based on IP address. How are customers approaching security from the name space perspective? >>Well, so it's, you're absolutely right. In fact, even when you go to I P six, like, I don't even recognize IP addresses anymore. <laugh> >>Yeah. Doesn't mean anything like, oh, just a bunch of, yes, those are numbers, ER, >>And colons. Right. You know, it's like, I don't even know anymore. Right. So, um, yeah, so it's, it comes back to that, moving from a static, you know, it's the pets versus cattle thing. Right? So this static thing that I can sort of know and, and love and touch and kind of protect to this almost living, breathing thing, which is moving all around, it's a swarm of, you know, pods moving all over the place. And so, uh, it, it is, I mean, that's what Kubernetes has done for the workload side of it is like, how do you get away from, from that, that pet to a declarative approach to, you know, identifying your workload and the components of that workload and what it should be doing. And so if we go on the security side some more like, yeah, it's actually not even namespace namespace. >>Isn't good enough. We wanna get, if we wanna get to zero trust, it's like, just cuz you're running in my namespace doesn't mean I trust you. Right. So, and that's one of the really cool things about new vectors because of the, you know, we're looking at protocol level stuff within the network. So it's pod to pod, every single connection we can look at and it's at the protocol layer. So if you say you're on my database and I have a mye request going into it, I can confirm that that's actually a mye protocol being spoken and it's well formed. Right. And I know that this endpoint, you know, which is a, uh, container image or a pod name or some, or a label, even if it's in the same name, space is allowed to talk to and use this protocol to this other pod that's running in my same name space. >>Right. So I can either allow or deny. And if I can, I can look into the content that request and make sure it's well formed. So I'll give you an example is, um, do you guys remember the log four J challenges from not too long ago, right. Was, was a huge deal. So if I'm doing something that's IP and port based and name space based, so what are my protections? What are my options for something that's got log four J embedded in like I either run the risk of it running or I shut it down. Those are my options. Like those neither one of those are very good. So we can do, because again, we're at the protocol layers like, ah, I can identify any log for J protocol. I can look at whether it's well formed, you know, or if it's malicious, if it's malicious, I can block it. If it's well formed, I can let it go through. So I can actually look at those, those, um, those vulnerabilities. I don't have to take my service down. I can run and still be protected. And so that, that extra level, that ability to kind of peek into things and also go pod to pod, you know, not just name space level is one of the key differences. So I talk about the evolution or how we're evolving with, um, with the security. Like we've grown a lot, we've got a lot more coming. >>So let's talk about that a lot more coming what's in the pipeline for SUSE. >>Well, how, before I get to that, we just announced new vector five. So maybe I can catch us up on what was released last week. Uh, and then we can talk a little bit about going, going forward. So new vector five, introduce something called um, well, several things, but one of the things I can talk in more detail about is something called zero drift. So I've been talking about the network security, but we also have run time security, right? So any, any container that's running within your environment has processes that are running that container. What we can do is actually comes back to that manageability and configuration. We can look at the root level of trust of any process that's running. And as long as it has an inheritance, we can let that process run without any extra configuration. If it doesn't have a root level of trust, like it didn't spawn from whatever the, a knit, um, function was and that container we're not gonna let it run. Uh, so the, the configuration that you have to put in there is, is a lot simpler. Um, so that's something that's in, in new vector five, um, the web application firewall. So this layer seven security inspection has gotten a lot more granular now. So it's that pod Topo security, um, both for ingress egress and internal on the cluster. Right. >>So before we get to what's in the pipeline, one question around new vector, how is that consumed and deployed? >>How is new vector consumed, >>Deployed? And yeah, >>Yeah, yeah. So, uh, again with new vector five and, and also rancher 2 65, which just were released, there's actually some nice integration between them. So if I'm a rancher customer and I'm using 2 65, I can actually just deploy that new vector with a couple clicks of the button in our, uh, in our marketplace. And we're actually tied into our role-based access control. So an administrator who has that has the rights can just click they're now in a new vector interface and they can start setting those policies and deploying those things out very easily. Of course, if you aren't using, uh, rancher, you're using some other, uh, container management platform, new vector still works. Awesome. You can deploy it there still in a few clicks. Um, you're just gonna get into, you have to log into your new vector, uh, interface and, and use it from there. >>So that's how it's deployed. It's, it's very, it's very simple to use. Um, I think what's actually really exciting about that too, is we've opensourced it? Um, so it's available for anyone to go download and try, and I would encourage people to give it a go. Uh, and I think there's some compelling reasons to do that now. Right? So we have pause security policies, you know, depreciated and going away, um, pretty soon in, in Kubernetes. And so there's a few things you might look at to make sure you're still able to run a secure environment within Kubernetes. So I think it's a great time to look at what's coming next, uh, for your security within your Kubernetes. >>So, Paul, we appreciate you stopping by from ity of Spain. I'm Keith Townsend, along with en Rico Sinte. Thank you. And you're watching the, the leader in high tech coverage.

(upbeat music) >> Despite its 70 to $80 billion total available market, computer storage is like a small town, everybody knows everybody else. We say in the storage world, there are a hundred people, and 99 seats. Infinidat is a company that was founded in 2011 by storage legend, Moshe Yanai. The company is known for building products with rock solid availability, simplicity, and a passion for white glove service, and client satisfaction. Company went through a leadership change recently, in early this year, appointed industry vet, Phil Bullinger, as CEO. It's making more moves, bringing on longtime storage sales exec, Richard Bradbury, to run EMEA, and APJ Go-To-Market. And just recently appointed marketing maven, Eric Hertzog to be CMO. Hertzog has worked at numerous companies, ranging from startups that were acquired, two stints at IBM, and is SVP of product marketing and management at Storage Powerhouse, EMC, among others. Hertzog has been named CMO of the year as an OnCon Icon, and top 100 influencer in big data, AI, and also hybrid cloud, along with yours truly, if I may say so. Joining me today, is the newly minted CMO of Infinidat, Mr.Eric Hertzog. Good to see you, Eric, thanks for coming on. >> Dave, thank you very much. You know, we love being on theCUBE, and I am of course sporting my Infinidat logo wear already, even though I've only been on the job for two weeks. >> Dude, no Hawaiian shirt, okay. That's a pretty buttoned up company. >> Well, next time, I'll have a Hawaiian shirt, don't worry. >> Okay, so give us the backstory, how did this all come about? you know Phil, my 99 seat joke, but, how did it come about? Tell us that story. >> So, I have known Phil since the late 90s, when he was a VP at LSA of Engineering, and he had... I was working at a company called Milax, which was acquired by IBM. And we were doing a product for HP, and he was providing the subsystem, and we were providing the fiber to fiber, and fiber to SCSI array controllers back in the day. So I met him then, we kept in touch for years. And then when I was a senior VP at EMC, he started originally as VP of engineering for the EMC Isilon team. And then he became the general manager. So, while I didn't work for him, I worked with him, A, at LSA, and then again at EMC. So I just happened to congratulate him about some award he won, and he said "Hey Herzog, "we should talk, I have a CMO opening". So literally happened over LinkedIn discussion, where I reached out to him, and congratulate him, he said "Hey, I need a CMO, let's talk". So, the whole thing took about three weeks in all honesty. And that included interviewing with other members of his exec staff. >> That's awesome, that's right, he was running the Isilon division for awhile at the EMC. >> Right. >> You guys were there, and of course, you talk about Milax, LSA, there was a period of time where, you guys were making subsystems for everybody. So, you sort of saw the whole landscape. So, you got some serious storage history and chops. So, I want to ask you what attracted you to Infinidat. I mean, obviously they're a leader in the magic quadrant. We know about InfiniBox, and the petabyte scale, and the low latency, what are the... When you look at the market, you obviously you see it, you talk to everybody. What were the trends that were driving your decision to join Infinidat? >> Well, a couple of things. First of all, as you know, and you guys have talked about it on theCUBE, most CIOs don't know anything about storage, other than they know a guy got to spend money on it. So the Infinidat message of optimizing applications, workloads, and use cases with 100% guaranteed availability, unmatched reliability, the set and forget ease of use, which obviously AIOps is driving that, and overall IT operations management was very attractive. And then on top of that, the reality is, when you do that consolidation, which Infinidat can do, because of the performance that it has, you can dramatically free up rack, stack, power, floor, and operational manpower by literally getting rid of, tons and tons of arrays. There's one customer that they have, you actually... I found out when I got here, they took out a hundred arrays from EMC Hitachi. And that company now has 20 InfiniBoxes, and InfiniBox SSAs running the exact same workloads that used to be, well over a hundred subsystems from the other players. So, that's got a performance angle, a CapEx and OPEX angle, and then even a clean energy angle because reducing Watson slots. So, lots of different advantages there. And then I think from just a pure marketing perspective, as someone has said, they're the best kept secret to the storage industry. And so you need to, if you will, amp up the message, get it out. They've expanded the portfolio with the InfiniBox SSA, the InfiniGuard product, which is really optimized, not only as the PBA for backup perspective, and it works with all the backup vendors, but also, has an incredible play on data and cyber resilience with their capability of local logical air gapping, remote logical air gapping, and creating a clean room, if you will, a vault, so that you can then recover their review for malware ransomware before you do a full recovery. So it's got the right solutions, just that most people didn't know who they were. So, between the relationship with Phil, and the real opportunity that this company could skyrocket. In fact, we have 35 job openings right now, right now. >> Wow, okay, so yeah, I think it was Duplessy called them the best kept secret, he's not the only one. And so that brings us to you, and your mission because it's true, it is the best kept secret. You're a leader in the Gartner magic quadrant, but I mean, if you're not a leader in a Gartner magic quadrant, you're kind of nobody in storage. And so, but you got chops and block storage. You talked about the consolidation story, and I've talked to many folks in Infinidat about that. Ken Steinhardt rest his soul, Dr. Rico, good business friend, about, you know... So, that play and how you handle the whole blast radius. And that's always a great discussion, and Infinidat has proven that it can operate at very very high performance, low latency, petabyte scale. So how do you get the word out? What's your mission? >> Well, so we're going to do a couple of things. We're going to be very, very tied to the channel as you know, EMC, Dell EMC, and these are articles that have been in CRN, and other channel publications is pulling back from the channel, letting go of channel managers, and there's been a lot of conflict. So, we're going to embrace the channel. We already do well over 90% of our business within general globally. So, we're doing that. In fact, I am meeting, personally, next week with five different CEOs of channel partners. Of which, only one of them is doing business with Infinidat now. So, we want to expand our channel, and leverage the channel, take advantage of these changes in the channel. We are going to be increasing our presence in the public relations area. The work we do with all the industry analysts, not just in North America, but in Europe as well, and Asia. We're going to amp up, of course, our social media effort, both of us, of course, having been named some of the best social media guys in the world the last couple of years. So, we're going to open that up. And then, obviously, increase our demand generation activities as well. So, we're going to make sure that we leverage what we do, and deliver that message to the world. Deliver it to the partner base, so the partners can take advantage, and make good margin and revenue, but delivering products that really meet the needs of the customers while saving them dramatically on CapEx and OPEX. So, the partner wins, and the end user wins. And that's the best scenario you can do when you're leveraging the channel to help you grow your business. >> So you're not only just the marketing guy, I mean, you know product, you ran product management at very senior levels. So, you could... You're like a walking spec sheet, John Farrier says you could just rattle it off. Already impressed that how much you know about Infinidat, but when you joined EMC, it was almost like, there was too many products, right? When you joined IBM, even though it had a big portfolio, it's like it didn't have enough relevant products. And you had to sort of deal with that. How do you feel about the product portfolio at Infinidat? >> Well, for us, it's right in the perfect niche. Enterprise class, AI based software defined storage technologies that happens run on a hybrid array, an all flash array, has a variant that's really tuned towards modern data protection, including data and cyber resilience. So, with those three elements of the portfolio, which by the way, all have a common architecture. So while there are three different solutions, all common architecture. So if you know how to use the InfiniBox, you can easily use an InfiniGuard. You got an InfiniGuard, you can easily use an InfiniBox SSA. So the capability of doing that, helps reduce operational manpower and hence, of course, OPEX. So the story is strong technically, the story has a strong business tie in. So part of the thing you have to do in marketing these days. Yeah, we both been around. So you could just talk about IOPS, and latency, and bandwidth. And if the people didn't... If the CIO didn't know what that meant, so what? But the world has changed on the expenditure of infrastructure. If you don't have seamless integration with hybrid cloud, virtual environments and containers, which Infinidat can do all that, then you're not relevant from a CIO perspective. And obviously with many workloads moving to the cloud, you've got to have this infrastructure that supports core edge and cloud, the virtualization layer, and of course, the container layer across a hybrid environment. And we can do that with all three of these solutions. Yet, with a common underlying software defined storage architecture. So it makes the technical story very powerful. Then you turn that into business benefit, CapEX, OPEX, the operational manpower, unmatched availability, which is obviously a big deal these days, unmatched performance, everybody wants their SAP workload or their Oracle or Mongo Cassandra to be, instantaneous from the app perspective. Excuse me. And we can do that. And that's the kind of thing that... My job is to translate that from that technical value into the business value, that can be appreciated by the CIO, by the CSO, by the VP of software development, who then says to VP of industry, that Infinidat stuff, we actually need that for our SAP workload, or wow, for our overall corporate cybersecurity strategy, the CSO says, the key element of the storage part of that overall corporate cybersecurity strategy are those Infinidat guys with their great cyber and data resilience. And that's the kind of thing that my job, and my team's job to work on to get the market to understand and appreciate that business value that the underlying technology delivers. >> So the other thing, the interesting thing about Infinidat. This was always a source of spirited discussions over the years with business friends from Infinidat was the company figured out a way, it was formed in 2011, and at the time the strategy perfectly reasonable to say, okay, let's build a better box. And the way they approached that from a cost standpoint was you were able to get the most out of spinning disk. Everybody else was moving to flash, of course, floyers work a big flash, all flash data center, etc, etc. But Infinidat with its memory cache and its architecture, and its algorithms was able to figure out how to magically get equivalent or better performance in an all flash array out of a system that had a lot of spinning disks, which is I think unique. I mean, I know it's unique, very rare anyway. And so that was kind of interesting, but at the time it made sense, to go after a big market with a better mouse trap. Now, if I were starting a company today, I might take a different approach, I might try to build, a storage cloud or something like that. Or if I had a huge install base that I was trying to protect, and maybe go into that. But so what's the strategy? You still got huge share gain potentials for on-prem is that the vector? You mentioned hybrid cloud, what's the cloud strategy? Maybe you could summarize your thoughts on that? >> Sure, so the cloud strategy, is first of all, seamless integration to hybrid cloud environments. For example, we support Outpost as an example. Second thing, you'd be surprised at the number of cloud providers that actually use us as their backend, either for their primary storage, or for their secondary storage. So, we've got some of the largest hyperscalers in the world. For example, one of the Telcos has 150 Infiniboxes, InfiniBox SSAS and InfiniGuards. 150 running one of the largest Telcos on the planet. And a huge percentage of that is their corporate cloud effort where they're going in and saying, don't use Amazon or Azure, why don't you use us the giant Telco? So we've got that angle. We've got a ton of mid-sized cloud providers all over the world that their backup is our servers, or their primary storage that they offer is built on top of Infiniboxes or InfiniBox SSA. So, the cloud strategy is one to arm the hyperscalers, both big, medium, and small with what they need to provide the right end user services with the right outside SLAs. And the second thing is to have that hybrid cloud integration capability. For example, when I talked about InfiniGuard, we can do air gapping locally to give almost instantaneous recovery, but at the same time, if there's an earthquake in California or a tornado in Kansas City, or a tsunami in Singapore, you've got to have that remote air gapping capability, which InfiniGuard can do. Which of course, is essentially that logical air gap remote is basically a cloud strategy. So, we can do all of that. That's why it has a cloud strategy play. And again we have a number of public references in the cloud, US signal and others, where they talk about why they use the InfiniBox, and our technologies to offer their storage cloud services based on our platform. >> Okay, so I got to ask you, so you've mentioned earthquakes, a lot of earthquakes in California, dangerous place to live, US headquarters is in Waltham, we're going to pry you out of the Golden State? >> Let's see, I was born at Stanford hospital where my parents met when they were going there. I've never lived anywhere, but here. And of course, remember when I was working for EMC, I flew out every week, and I sort of lived at that Milford Courtyard Marriott. So I'll be out a lot, but I will not be moving, I'm a Silicon Valley guy, just like that old book, the Silicon Valley Guy from the old days, that's me. >> Yeah, the hotels in Waltham are a little better, but... So, what's your priority? Last question. What's the priority first 100 days? Where's your focus? >> Number one priority is team assessment and integration of the team across the other teams. One of the things I noticed about Infinidat, which is a little unusual, is there sometimes are silos and having done seven other small companies and startups, in a startup or a small company, you usually don't see that silo-ness, So we have to break down those walls. And by the way, we've been incredibly successful, even with the silos, imagine if everybody realized that business is a team sport. And so, we're going to do that, and do heavy levels of integration. We've already started to do an incredible outreach program to the press and to partners. We won a couple awards recently, we're up for two more awards in Europe, the SDC Awards, and one of the channel publications is going to give us an award next week. So yeah, we're amping up that sort of thing that we can leverage and extend. Both in the short term, but also, of course, across a longer term strategy. So, those are the things we're going to do first, and yeah, we're going to be rolling into, of course, 2022. So we've got a lot of work we're doing, as I mentioned, I'm meeting, five partners, CEOs, and only one of them is doing business with us now. So we want to get those partners to kick off January with us presenting at their sales kickoff, going "We are going with Infinidat "as one of our strong storage providers". So, we're doing all that upfront work in the first 100 days, so we can kick off Q1 with a real bang. >> Love the channel story, and you're a good guy to do that. And you mentioned the silos, correct me if I'm wrong, but Infinidat does a lot of business in overseas. A lot of business in Europe, obviously the affinity to the engineering, a lot of the engineering work that's going on in Israel, but that's by its very nature, stovepipe. Most startups start in the US, big market NFL cities, and then sort of go overseas. It's almost like Infinidat sort of simultaneously grew it's overseas business, and it's US business. >> Well, and we've got customers everywhere. We've got them in South Africa, all over Europe, Middle East. We have six very large customers in India, and a number of large customers in Japan. So we have a sales team all over the world. As you mentioned, our white glove service includes not only our field systems engineers, but we have a professional services group. We've actually written custom software for several customers. In fact, I was on the forecast meeting earlier today, and one of the comments that was made for someone who's going to give us a PO. So, the sales guy was saying, part of the reason we're getting the PO is we did some professional services work last quarter, and the CIO called and said, I can't believe it. And what CIO calls up a storage company these days, but the CIO called him and said "I can't believe the work you did. We're going to buy some more stuff this quarter". So that white glove service, our technical account managers to go along with the field sales SEs and this professional service is pretty unusual in a small company to have that level of, as you mentioned yourself, white glove service, when the company is so small. And that's been a real hidden gem for this company, and will continue to be so. >> Well, Eric, congratulations on the appointment, the new role, excited to see what you do, and how you craft the story, the strategy. And we've been following Infinidat since, sort of day zero and I really wish you the best. >> Great, well, thank you very much. Always appreciate theCUBE. And trust me, Dave, next time I will have my famous Hawaiian shirt. >> Ah, I can't wait. All right, thanks to Eric, and thank you for watching everybody. This is Dave Vellante for theCUBE, and we'll see you next time. (bright upbeat music)