Live from Washington D.C., if the Cube. Covering Inforum DC 2018, brought to you by Infor. Welcome back here on theCUBE. We are live at Inforum 18 in the nation's capital, Washington D.C., where these days, there's never a dull moment, and we'll just leave it at that. I'm with John Walls, Dave Vellante, and Stuart Appelbaum is joining us here. He's the EVP of North America Service Industries at Infor, and Stuart, thanks for joining us here. Oh, thank you, looking forward to it, and you're right. You got your hands on a lot of pies, right?  Hospitality, and you've had some wins in hospitality of late. First off, what's driving that? What do you think is being the... Yes, sure, well, I mean, whether you look at hospitality, whether it's managed food service, or hotels, or restaurants, a lot of the technology that's been out there is dated, right? And the technology is not upkeeping with the requirements and the demand for a really different customer service level. So, you take the look and feel of what we've been able to do as a company over the last 10 years, and build up a lot of knowledge base and seniority around what it means to serve those markets, but then re-architect with new products, right? Cloud-first approach type technology that really allows for us to deliver a, what I would say, a much more better experience for the guest at a hotel, or at a front, at a cash register at a restaurant, or in a managed food service environment in a hospital, right? Those, all those environments are a lot of touches that go on, and the more the technology is modern, the better you can improve those technology and those interactions that go on. You also look at, you know, the idea that these guys trying to manage these, you know, whether it's a hotel chain, or a company like Sodexo, where they have managed food service entities all over, business and industry, health care, it doesn't matter what you see a cafeteria somewhere, there's a high odds that it's either a company like Sodexo another managed food service provider. The complexity of trying to maintain on-premise solutions is just, it's back-breaking for them. So for them to be able to now actually get to a level with a company like Info, who not only has the experience in the space, but also have invested into the next generation cloud-based solutions, really allows us to kind of differentiate ourselves in the marketplace, and the marketplace has been pushing us for that as well. So are these typically sort of install-based in-for customers that you're now moving to a cloud model? Is it sort of a new logo? So I wonder if you could describe that dynamic. Yeah, I would tell you it's pretty mixed, right? Our customer base is fairly broad. We serve hotels, for example, in over 100 countries and territories today. A lot of those customers came up through legacy applications, much like we compete in the marketplace on. So we've done a really great job of migrating those customers up into the cloud with the next generation technology. But what's also happened is as you look at the area in which people serve the hotel space, a lot of them are really legacy applications that have been around for 20, 30 years, and while those companies have tried to encapsulate modern technology and move it into some cloud-level environment, only Info is actually re-architected and built them from the ground up. So what we're finding is a lot of different style of companies and groups. One great example of this is Mandarin Oriental has begun to roll out our company or roll out our products globally. So being able to take a brand that's as exclusive as that that's so focused on how do we make the guest at the forefront of everything that we do to make them feel special? Well, they couldn't do that with the technology that they have today, right? So in order to be able to make those differences and those changes and how they're gonna service their guests, they have to move to a next generation technology. So we're seeing a lot of new logo business in that space. We're also seeing a lot of new logo space in the casino marketplace, right? You think about how massive and big these casinos are. So most of these guys have been very careful and concerned just like our banking customers, for example, in being able to move into the cloud, move to new technology, because can companies really scale? Can they bring that capability and put it in the cloud? Well, we very much started to prove that with these large casinos to the point where we just recently announced about a year ago signing one of the largest or second largest casino company in the world. And 40 hotels with over 50,000 hotel rooms, right? The idea to be able to take these kind of technologies at that scale and pace is driving a lot of new logo, new customer business being driven from our competition, right? Which has not been able to keep pace with that kind of technology in the cloud. So what are the winning attributes? I'm hearing architecture, we heard this morning, platform, we had Nunzio on the design, the whole user experience, there's the cloud component, those are the sort of key factors, what else? They're very much the key, but it's how in 4 OS, which I think maybe people have talked a little bit about, we have this capability to create a model that allows for not only a free flow of communication and understanding between systems, whether it's for a hotel environment or a hospital environment, so that information can be shared among systems and among resources to be able to collaborate and do something with that information. But equally as important at the same time, we put all that information into a data lake so that we can now use Burst and we can use Coleman to really start to help people understand not only what does it look like or what's the interactions occurring at the hotel space or what might you want to tell this customer or say to this customer to, hey, we're going to give you that information upfront instead of guessing what that might look like or maybe guessing what you might want to offer that client, it's a very different approach. Yeah, give me an idea, I mean specifically, you talk about Mandarin, we'll just use them as an example. Yep. What are you helping them do better that they couldn't do before? Because when I think of service, I think of Mandarin, they did things pretty well before. So what are you doing to help them improve their processes and what are they turning you for future? Sure, sure, well, I mean, from a simplistic standpoint, talk about how they're able to interact with you as a guest, right? If you're a Mandarin type of client, right? You're probably very much a more affluent business traveler or a... Dave Vellante. A Vellante example, right? And at the end of the day, while you want all the level of service that you expect at that kind of property, the amount of effort and work that they have to do or you might have to do to make them understand what that is, is very taxing, right? And it's also very hard for you guys to interact and change that. By getting to what we have HMS, which is Enforced Hotel Property Management System, allows them to really streamline not only understanding who you are, what your preferences are, how you like to interact with them, but then also be able to deliver that in the mode of interaction that you'd like, whether it be through mobile, whether it be through text, whether it be through personal conference calls or discussions or touch points, right? That kind of capability in their legacy systems took a whole bunch of manual intervention to make that happen. Now we're able to automate that, make that information real time, so it's not just a few people digging in to try to find this information to go back and try to make that guest feel like they understood it. It's every point, right? Every contact that touches that customer who has access to our solutions is fed that information real time, which gives the customer a much different experience, right? And at the same time, it allows you guys to interact in a much different experience. You may not want to talk to people, you want to check in on your phone, show up the hotel, go to your room, open your door. Well, legacy architectures and technologies with closed type of infrastructure don't allow for that open API capability versus our technologies allow it free flowing out of a cloud scenario, which is even a more complex thing, to give the ability for those hoteliers like Mandarin to say, hey, I'm going to give Valente a very unique experience that is exactly what he likes with all the information that I know about him to be what I would consider the best way I can service Valente. So self-service is an obvious one. I don't want to have to wait in the phone on a hold to check out, for example. Just give me a pad or something that I can just go boom. And there are numerous other examples, but you've got to get the user experience and the design right. Maybe talk about how you guys approach that. Yeah, well, so you guys had a chance to meet with Nunzio and our hook and loop. Hook and loop is very instrumental in what we do in the hospitality space as well, as well in the healthcare space. Any time people are interacting, not only as an employee, but as a guest, whether you're an invited guest from a doctor to get to a hospital to have some kind of treatment or acute care, or if you're a hotel guest where you're coming to stay, right? There is some level of interaction that's going on that requires a very unique, specific, kind of touch point between the two, right? And in that area and then in that space, right, there's a lot of data and elements that go on that if you feed those and understand what those elements are and start to really understand what it is that individuals require in terms of their personal care or their personal interaction or stay at a hotel, the more unique experience and the better experience that they can have. Stuart, we heard about the skills gap, skills shortage this morning. How can Infor and its software help close that gap? Right, well, it's really, you can look at it in a couple different ways, right? If you look at it at the grassroots of some of the industries that we serve that we've talked about, whether it's hospitality or retail or even in healthcare in some scenarios, not talking about professionals in the healthcare industry, but people that are just working day-to-day operations. Simplifying that the interaction on how they use the solutions that they do their jobs every day minimizes the training requirements and the skill labor that has to go on that would occur in legacy solutions and architects. So being able to hire a front guest agent who's got a great personality, who knows how to interact and talk to people, but maybe has never used a hotel system before to be able to put them in front of that hotel system and act just like their phone or their iPad, it gives them the ability to be interactive and understand and be on board pretty quickly. So that's one side is simplifying, working with Hook and Loop, designing, making sure the applications, the workflows make sense. So it simplifies the work effort and simplifies the ability for people who are maybe less skilled in a particular area to jump in really quickly with less training. The other side of it is actually trying to find the right resources, right? And going through the process of having a skilled attribute level of understanding of what your successful people look like, we can help through our talent science solutions find similar type of people. That doesn't mean, now we'll get to the education enablement side of it, that doesn't mean day one, that maybe they have the exact training that they have required, but we found that they are the perfect fit for the job. So if they are going to be interacting on an everyday basis with a guest, for example, and they're a front desk manager, there's attributes around that that are so critical important. Now they may not understand all the facets of the job, and then, but once we find that right resource, you bring them into the talent solution and then really start to understand where are their gaps? Where are the training requirements? What are the certifications by the way, depending on if you're in a complex industry like manufacturing or healthcare where there's certifications and safety regulations you have to occur, how do you maintain all that into one spot and be able to identify and be able to give them and provide them the personal interaction on what is it that they need to maintain and grow in terms of their own abilities to be suitable for the next job or the job that they're being hired for and how do they actively get the learning and the education, the e-learning that goes with it. So we've been able to kind of formulate that into a comprehensive product set that we think is pretty much best of breed in the industry, right? So not only do we have a great learning management system, an unbelievable talent acquisition and science system, a fabulous way to hire, to promote, to retire structure on understanding employees, what their skills are and how to place them, but bringing all that together from a unified front and then being able to standardize that into an experience that makes it a much more different approach from what you would traditionally have had in finding skilled labor and workforce. And automation and AI is it's now a layer on top of all this that you're bringing to the table with Coleman and you started to sort of roll out some capabilities there. What's the reaction been of customers? Is there uncertainty? Is there fear? Is there doubt? Are they embracing it? What's the conversation like? Yeah, and really, instead of saying it's better to think of it, it's not on top, right? This is the underpinnings of how we've built our cloud suites. Injected into the... So we've taken our cloud suites and everything that we've opened from a technology perspective to every information and job that flows through, whether it's a personal intervention into a task or if it's machine to machine goes through that in 4 OS. So all that interaction and data whether it's from a person or from a machine gets captured so you can start to begin to build intelligence on top of that. Now what that means is wherever those interactions and communications occur, Coleman is sitting in their understanding and learning sitting on top of our data like to say, you know what? This is a process that is repeated 100 times a day by 50 different people in a particular firm. Why don't we automate that process and why don't we make that known to the entity and then adjust our process to automate that so no one has to interact with it, right? So being able to have that as an underpinning, not an overlay, right? Because a lot of businesses will come in and say, hey, we'll provide analytics and BI over the top. That's great. Analytics and BI on the top is pulling information out of all different kinds of sources, trying to make sense of that data, trying to make sense of all those sources versus what we're trying to do is every interaction that occurs between systems, we're not trying to identify right at that point what makes sense to store somewhere and put somewhere. It all goes into our data lake and then the machine learning starts to tell you, here's some things you should understand about the data and the interactions. We've heard the theme about human potential, right? Unlocking that. So how does that translate in your world? I mean, in your mind, how do you apply that in terms of the industries that are produced? Right, well, again, it goes back to, and it also goes to our focus on bringing a diverse workforce to the table to improve our capabilities and improve the way we approach things. But it's understanding individual attributes of people, right? And how they may interact and work within a company is a starting point, right? So they may not have a particular skill, but they have a capability or an ability to learn or they may have a personal interaction that is far excessive than what normal people would come in to interview first like a job. Well, being able to do these type of talent assessments and understand as a baseline where they are, all of a sudden you're getting a more broader pool of skilled resources for what you're looking for, right? And then even if that skilled resource happens to be from a different part of the country than what your typical hiring manager is or they look different or their education background is different, it strips that out, right? It is giving you the personal attributes of that individual. So that allows a broader pool to look at. Then from that pool that we could start to say, okay, well here's a great candidate pool of people that may be able to quickly be skilled into a job or into a role and then start to place those people into those positions. And then as the lifecycle of that employee goes on, so do their attributes, right? So what made them who they are? As other roles and jobs, as they build their resume within the company, they still have those capabilities. So as a role and a management place comes up that has a good fit for this person's individual skills and their personal attributes, they're a natural fit for moving up into the world, right? And that's how we kind of continue to get that engine rolling in terms of how do we bring more people in without a prescriptive, only a prescriptive model, right? This is a scientific model of what is going to be the right fit for an employee for Infor, right? Or an employee for one of our customers or another company. And that's where we start with bringing in that that ability to broaden our workforce and identify people who could be successful without necessarily saying, you didn't punch this type of button for the last 10 years so you're not qualified for the job. So I'm hearing a lot of differentiation and I'd love to hear it more in your words from an executive of Infor. Every company out there, every software company, they say, yeah, we have AI, too. I'm sure you hear it. Oh, this company, A, B, and C, they have their new AI platform. Everybody's doing AI. When you talk to customers, how do you differentiate what Infor is doing not with just machine intelligence but across the board from the competition? Well, I will tell you to start with. One is the comprehensive set of our solutions, right? So by being able to go into an industry and have a cloud suite that we formulated that has the capability to manage a very significant portion of their operations already integrated together, already with the last industry model functionality built into it, it gives us a leg up in our competition. So when we walk into a healthcare or a hospital and they have challenges with nurse scheduling, they have financials they need to look at, they have general HR that they have to look at, and by the way, they're also trying to look at are we going to be profitable and how do we become profitable and all these different touch points are a nightmare for us. Well, as Infor, what we present to our customers and brought together was, hey, we have that capability to do all your nurse scheduling, your workforce planning, your time attendance. We can manage your facilities, your assets, your expensive cost structures there. We have the ability to have a very complex set of financials that may serve 15 different hospitals that might also have different infused levels of ownership or investment or management. Being able to come to the table with that as a comprehensive system eliminates a lot of the guesswork. Now, again, once you have that in there, someone coming in and selling AI or BI, they still would have to, if it wasn't us, have to come in over the top and say, well, if it's all Infor, that's good, at least we can connect all Infor. But if it's got Epic or it's got Cerner, it's got whatever solution's sitting out there, well, all of a sudden you're not only having to connect those points, but you're having to connect all over the place versus the way we built it is that Cloud Suite, all those points of connection are already pre-built, right? And they're already dumping it into the data light so that now all you have to do is take some ancillary pieces of data to pull into that perspective. And with capabilities of clinical integrations that we have to be able to follow and track those things, and we just actually announced not too long ago true cost. True cost is the ability to really understand down to a procedure level what something may cost to perform in a particular hospital. And that is, you would think that wouldn't be that hard, but you're talking about people, you're talking about equipment, you're talking about what kind of room, right? What equipment's in that room that creates a certain cost per hour to do a procedure? All those things come to play into determining exactly what is profitable and what's not. So being able to really understand the true cost of care, not only at the hospital level, but by the way, how do we take into account what happened before? How do we take post care into that? And then how do we start to do predictive analytics on that kind of capability? Well, since we have this Cloud Suite healthcare, for example, building around all these different components where we track the resources, we understand the rooms and the cost, we understand the doctor costs, we understand the facilities costs, we understand the care and the time that takes to go into the care, we can now start to really take and give hospitals an idea of saying, hey, maybe if we approach this a little differently, or even with Coleman now, maybe you approach it this way, you can start to do and provide that specific care in a different way that will lower your cost to care, not only for your hospital, but for your patients, and then hence you become more profitable as an entity. So real business impact in the alternative would be, you'd have to what, develop custom modifications or bring in an ISV who's got deep expertise there, bring in another system. You can have a combination of it, right? If some of our competition would have to bring in a different workforce management and scheduling system, they'd have to bring in a different time and attendant system, they would probably have to bring in a different analytical engine and underlying platform to work with it. They would have to bring in a different talent assessment or talent management type of solution. They would have to bring in a different supply chain and materials management system for the healthcare environment, for example. I mean, the list can go on and on where we've went out and built and looked for, whether it was through acquisition where we then brought these cloud-based products into our cloud suite, or we identified gaps or areas that we needed to build from scratch. And we talk about, people don't really think about it, as a percent of revenue, we outspent our competition, 5X, right?  We do that because we know that if we can build the platform in the next generation for healthcare, for hospitality, for retail, then we can really be the leaders in the marketplace. And I think that's what's going to really differentiate us from our competition, who's trying to either come in with a point area, start to broaden it a little bit. We've already broadened it, we integrated it, we built it together and we underpin it with the ability to do artificial intelligence and analytics from the box, right? That's a very different approach. And keep it simple for me, right? Yeah, make it easier for the users, right? Yeah, exactly. Stu, thanks for the time. No, this was great, I appreciate it. Thanks for the rundown. You got it. That's Stuart Applebaum from N4. Back with more here from N4M18. We are live in Washington, DC, and you're watching theCUBE.


ITU presents a roadmap for a national digital identity framework. Today an estimated 1.1 billion people in the world are unable to prove their identity. Without official identification a person cannot access basic services and cannot enjoy health care, education, political and legal rights and countries cannot deliver vital public services. ICTs can help develop digital identification systems to create an inclusive digital society. This guide is for national leaders and policymakers to develop national digital identification initiatives as well as highlighting the key elements that should be taken into account in its development such as overarching principles, governance model, approach of adoption, architectural model critical success factors, digital identity implementation framework and digital identity country case studies. To sum up, this guide addresses the principles, models and guidelines for the development of a national digital identity roadmap. This framework will contribute to the realization of the sustainable development goals in particular Goal 16 which recognizes the need of providing legal identity for all by 2030.


Welcome back to the Cyber Underground, and I cannot say, this is Dave, the Cyber Guy. Sorry, the title is taken by somebody else. My sad news to everybody out there, I have to relinquish my title because somebody else has claimed it, and he has the domain, the Cyber Guy. So cyberguy.com out there is Kurt Knudsen, and I only found out about this because I must profess I watch all news stations to try to get a good idea of what's going on out there, and I actually stumbled across Fox News, and he was a cyber consultant on Fox News. With me today, I have Hal, who still retains the title, the Networking Guy. Thank you for being on the show. Thanks for having me back again. Thanks, brother. All right, so the audience should be reminded we work for the University of Hawaii, Kapilani Community College. You teach networking and cybersecurity, so do I, and we have a great time with it, and that's why we have this show, and hopefully we entertain and inform at the same time and keep people safe, and today we're going to talk about how the Internet has evolved and a big piece of its evolution is coming up again. And of course, Google's right out in front, right? So first of all, we have to ask our audience out there, please come up with a new title for me because I cannot be the Cyber Guy, so I need to be something. Be nice. Okay. I can only imagine the responses now. How about Cyberman? Cyberman. Someone's going to call me the tick or something. Just be nice. When you give me, I don't want a porn name, by the way, I just need a cyber name. So for now, just Dave. Let's talk about, I got some notes here about Google and their new implementation for HTTP3. HTTP3 is what the Internet Engineering Task Force, the IETF is going to call it, but Google called it Quick, Quick UDP Internet Connection, which is great, but they've come up with other implementations. So let's talk about what HTTP is and how it works and why we care, and then let's talk about what's going to happen now. So help me out. With HTTP, people take it for granted. We just open a browser and type in Amazon.com, we go to Amazon, and everything just kind of works. It's this ubiquitous, magical process now that we don't have to think about, but in days of old, 1989, you popped up in AOL, you didn't have just HTTP. There was Gopher and Waze and all these other protocols, and we just finally standardized on HTTP. Why do we do that? What was the benefit? What did we get out of HTTP over TCP, and what is it? Well, HTTP is the protocol that runs the web. So that web browsers used to talk to web servers, and web servers used to send web content back to web browsers. And I guess it evolved from those other protocols because some of those other protocols had different purposes. There were more for file transfer or text-based content, and HTTP evolved to support multimedia. You can have video content, audio content, dynamic web content. It's come a long ways from just the first web pages, which were just kind of black and white text, and not very exciting. It's become a lot more exciting now. There was more informational than participation. More multimedia, more interactive, and so that's how HTTP kind of developed from those other protocols, and it continues to develop. We've had different versions, but underneath the actual web layer, there's what we call a transport layer. So there are these protocols that manage the connection between the two endpoints, in the browser that you're working with, and the web server that you're actually talking to across the internet. So protocol is like a common language between two systems. So you both know what that language means. I send you some data, and you know what it means, because we're both on the same protocol. Yeah. So it's like if you were speaking Mandarin Chinese, and I was speaking Swedish, neither one of us would understand each other. We have to be speaking the same language or the same protocol. So this is just, it's the set of rules of how do we talk to each other. So HTTP sets up the rules for web browsers to talk to web servers, and these transport protocols set up the rules for how your computer actually talks to the servers and how those connections are managed. And there are two main protocols, transport protocols at this layer, TCP, which is transport control protocol, and UDP, which is user data gram protocol. And they really, why do we have two? Well, they were designed for different purposes. So one's connection, and one's connection less. One's connection oriented, that's TCP. And the other is connection less, as you said, that's UDP. So TCP was designed to guarantee every single bit of data was going to be guaranteed to be delivered and received. So it does all these extra steps. It has the client do a handshake with the server before any data is transferred to make sure that they're both connected on both ends. So if I'm a client in your server, I'm a browser and a PC and I'm browsing amazon.com. The first thing we have to do is I send out a signal, hey, I'd like some information. You say, yes, I'm here, and I respond, OK, I got that signal. So now we have a three-way handshake. So now we have a connection. SIN, SINAC, and AC, right? Exactly. After that's done, and that takes a lot of effort, right? There's a lot that goes into that. There's a lot of little flags, a lot of built bits. We send data in packets in TCP, right? So we chunk up the data. So if you have a bunch of data, you put into pieces, basically, right? And you give each one a sequence number. And the reason is because over the internet, you might not have a direct connection. Sometimes you take alternate routes, and each router and each waypoint or hop, as they say, is going to reroute you on the most efficient path it sees at the time. And maybe I'm on my phone, and I'm switching from mobile network to Wi-Fi back. So it's not always the same connection, as you said. So that's why you have the sewage numbers. So as things arrive, you know how they fit together. Because as you said, they may not always come over the exact same path. Right, right. So that's all built into TCP. We have the sequence numbers. We have some security features built in there. And it's a complicated system. It takes what's called a lot of overhead. There's a lot of extra, besides the data that I'm sending you. I have to send a lot more data to make sure this all happens. There's an acknowledgement.  So there's a lot of back and forth, back and forth data. And if you drop one, I'll send it again. Yeah, absolutely. But that absolutely guarantees that every single bit is received on the other end. So it's what we call the reliable protocol, and that delivery is guaranteed. It's like sending a letter with a post office with that little green card that comes back to you to acknowledge, yes, it was received. Signed by someone, and it's guaranteed. UDP is the opposite. UDP, you just send the data, and I hope it got there. Fire and forget. I assume it did. But I'll never know for sure, because I don't get any kind of acknowledgement. So why do we have these two different schemes? Well, the rationale has always been that if you're transferring a file, you need every single bit. If you lose one bit, the whole file's corrupt, and it's not going to do any good. Like a Word document, or an EXE executable file, or something in FTP, a zip file, you don't get the whole thing. It's corrupt, and it's useless. It's useless without every single bit. So for those kind of things, we always use TCP. But if you're viewing, say, a live stream of the surfer Waikiki or something, it's very time-sensitive. So if you should lose a few packets and ask them to be re-send later by the time they get to you, you're already past that point in the stream. It's not going to do any good. So why bother with all that re-sending and acknowledgment? Just send it. You can send more raw data because you're not sending all of these acknowledgments and handshakes. So we'll just send as much raw data as we can and hope for the best that it gets there. Now, gamers use UDP quite a bit. All the time, yeah. Gamers will know because when they hook up their Xbox or their PS3 or whatever system they're using, and they want to do internet gaming, what they have to do is they have to open up ports on their router, TCP and UDP ports, and arrange so you can stream both kinds of data. You can get the files that you really want to all be there at the time. And you also have streaming media and gaming stuff that, like you said, once you pass that certain point in time, no use going back. You just got to keep going forward.  For the most part, you get a fade. But then when the stream is back, you just go forward the best you can. Yeah, that's where we get music too, right? Driving in a car, I got streaming music going on, Spotify, Apple Music. That's UDP. Yeah, okay. Any type of streaming like that is almost always over UDP. So TCP, we built HTTP on top of that. So the beauty of HTTP.9 when it came out was like not even 1.0. The beauty of it was it was a single ASCII line for the request. You just sent some ASCII text out and what you got back was HTML. Well, that's Hypertext Markup Language. And that's the meta-based language or the tag-based language that gets interpreted by the browser. And just to take a little pause here, for everybody out there that doesn't know about web programming, programming for the internet is probably the most difficult programming you can do because it's never just one language. HTML, you have cascading style sheets, you have JavaScript, you have a server-side scripting language like PHP or ASP.NET or JSP. And these things can add up to a lot of work. And then on top of that, JavaScript has multiple frameworks, right? We have the Google APIs that came out. We have what is it? JQuery. JQuery is a framework of JavaScript libraries. And you have to be able to put all those in your file to be interpreted by the web browser. Now the web browser interprets this thing on the fly. Top down left to right reads it raw and will display it as that browser is supposed to display it. That's why if I look at the same amazon.com webpage on multiple browsers, I'm going to see a little bit different web page on each browser, right? There's going to be slightly different colors, slightly different behavior. Things will be in the different places just a little bit because we're all pretty much on the same standard, but everyone does it a little bit differently. And there's always a little flexibility in those standards. So Microsoft Edge might do it slightly different than the way that Mozilla Firefox did it, but they're still hopefully adhering to the standards. They're just maybe using a little flexibility with it. And Microsoft does that more than anybody. They're masters of, we're going to do it differently. I remember, especially our friend Steve, teaches web programming. And he's going to have to teach his students when you're writing JavaScript, you have to allow for different browsers. If you're in Firefox, do this. If you're in IE, do this. And it's a different line of code, but to do the same thing depending on a browser. This is why when I was a web developer back in the day, I used to have to test everything on three or four or five different times. I had to test every page on every single browser to see if it wasn't enough just to try it on Internet Explorer. And okay, it works then, so I assume it's going to work everywhere else. They have to try it on all the different browsers and make sure that it works on all of them. And multiple versions. And sometimes multiple versions as well. Yeah, because as we know, every time, I'm going to pick a Microsoft. Every time Microsoft comes out with a new Internet Explorer, it's major. The difference between 6 and 7, 7, 8, 8, 9 was tremendous. You got many more features and it was interpreted completely different. So I had, you know, I opened up Opera and Firefox and Chrome and multiple versions of each. And now we have Edge to add on top of that. So when you're a web programmer, it's almost a full-time job just testing your stuff. It's pretty terrible. But HTTP allowed us to be able to transmit this and make this a ubiquitous protocol across the entire Internet, right? So we got the chance to start doing things like cascading style sheets, which is making all the graphics move and be where they want and give us some dynamic behavior. And you could use an interactive kind of website now with HTTP rather than just the raw, you know, just text-based stuff. And streams embedded within webpages. You can have video streams, audio streams, all kinds of things. So the assumption up to this point has always been, oh, a web page is like a file, so we should use TCP. But now Google is trying to say, well, wait a second. A web page, I'm streaming all kinds of different pieces of this web page. Is it really a file and should it really be on TCP or can we do this better and more efficiently by trying to treat it as a stream? Because not everything is mission critical. Not everything is critical to get it across. You can try again, and it's not going to fail on you. Okay, let's take a little break. We're going to pay some bills. Be right back, everybody, until then, stay safe. I'm Jay Feidell, ThinkTech. ThinkTech loves energy. I'm the host of Mina, Marco, and me, which is Mina Morita, former chair of the PUC, former legislator, and Energy Dynamics, a consulting organization in energy. Marco Mangelsdorf is the CEO of Provision Solar in Hilo. Every two weeks, we talk about energy, everything about energy. Come around and watch us. We're on at noon on Mondays every two weeks on ThinkTech. Aloha. Hey, Stan the Energyman here on ThinkTech Hawaii. And they won't let me do political commentary. So I'm stuck doing energy stuff, but I really like energy stuff. So I'm going to keep on doing it. So join me every Friday on Stan the Energyman at lunchtime, at noon on my lunch hour, we're going to talk about everything energy, especially if it begins with the word hydrogen. We're going to definitely be talking about it. We'll talk about how we can make Hawaii cleaner, how we can make the world a better place, just basically save the planet. Even Miss America can't even talk about stuff like that anymore. We got it nailed down here. So we'll see you on Friday at noon with Stan the Energyman. Aloha. Welcome back to our exciting episode of the Cyber Underground. I'm Dave, no longer the cyber guy needing a nickname. Help me out. I'm with Hal, the networking guy, and we're talking about Google's new implementation of the next HTTP version. They call it Quick. It's now going to be called HTTP 3. We've gone through one and two. And Stanley Google was also responsible for HTTP 2 as well. And actually, it didn't get finalized until just a couple of years ago. So we're not only advancing, but we're speeding up how fast we advance. So kind of overlapping. Yeah, and we get that asymptotic curve of technology just launching into the stratosphere now. I think Moore actually predicted this. Moore's Law, we're going to go faster and faster and faster until we have this little feedback loop of all the technology making everything faster. And I think we're approaching that rapidly. Just so you know, the cyber guy that I saw on Fox was actually pretty good. Cyberguy.com, I saw some of his articles in there. And we should actually have a show on what he was discussing, because he was discussing Alexa. And with this new Google protocol, I believe Alexa's going to be even more of a danger to our privacy. So they're recording everything that gets said at all times, wherever Alexa's got a microphone handy. Listening for you to give commands. But recording everything you say, even in the background, and uploading everything to the servers at Google. And they do language protocol arrangements. So you could do AI and interpret what's going on in the background and help get language interpretation better for Google. So it's helping us improve speech recognition. On the other hand, everything you say is now stored at Google, which that's scary. So we should do a show on that. And it's less of a problem now with Google's new HTTP 3, because we're going to put everything over UDP, which we just discussed. And once that happens, we increase the bandwidth availability and speed of the internet by about 30%. So let's talk about HTTP 1 again, what it did for us, and then when we moved to 2 about that. So HTTP 1, I remember this in the late 90s, they finally came out with an internet standard. But we've been programming for the web for five, six years. Yahoo came out in 1994. And Netscape did its IPO in 95. And this HTTP 1.1, I think, came out in 1999. It was a long time after we'd started this stuff. And I remember what it relief it was to think, oh, thank god, we've got a standard. And then almost nobody stuck with it. Microsoft went on its own path. But it actually helped a little bit, I think. And with the next implementation that was almost a decade away, we increased the speed of the internet with a host of different things. We got better routers. We got fiber optic connections now. And just so our audience knows, and I'm not telling you anything new, but we were one of the first people, we were the first country internet to have the internet. So we had old copper wire everywhere. When the other countries, like in Europe, first adopted the internet, they did it in the late 90s or even in the early 2000s. And some of them went straight to fiber optic, which was an amazing speed increase over what we had over here. And we've slowly been trying to upgrade our infrastructure. But as we know, infrastructure is hard to upgrade in the United States. Yeah, we have all of this legacy telephone network. And so naturally, the telecom giants want to leverage that, and not just rip it all out and put it in fiber. But any new installations anywhere are definitely fiber at this point, with slowly moving off of the copper. So it's not just the protocols and the program that it makes everything faster. It's also the infrastructure. It's also the way we move data. It's also switching technologies getting better every day. So there's many things driving this, but Google has actually added a lot to this. And they added in about 2009, this came out with another thing called SPDY or speedy, which became HTTP2. And sped up the internet, most estimates are like 50%. And I think that's amazing to look back at 2009. What were we doing in 2009 that became faster? For me, it was things like Netflix. Yeah, there's much more video streaming now than there was even a few years ago. So the things we're sending over HTTP now, used to be pretty much text, and it was images. But now it's all kinds of streaming video, streaming audio, all kinds of dynamic content. It's really changed. So I mean, you understand where Google's coming from saying, the web isn't what the web used to be, and maybe it needs a new protocol to allow it to work more efficiently, given what kind of things we're sending over HTTP now, as opposed to what we did. I can see that in the first decade of this millennium, we had a huge shift to more mobile computing, a lot more file transfers, much more mobile gaming, and internet gaming, and a ton more streaming. And I know that in the 90s, it was mostly adult content, let's just say. It was driving the need for more bandwidth. And many people pushed that, and were very emphatic about, we need more bandwidth. And when they looked into it, it was adult content. But starting this millennium, that shifted. Now, we still have a lot of adult content out there, because let's face it, these guys are pretty sick. But we also have a ton of internet gaming, and an enormous amount of streaming video and music. We've just all gone to Spotify, and Netflix, and all the other Amazon primes got their video service, and HBO, and all the movie channels now have their content streamed over the internet. Even most of the CBS NBC, the major players, they have a service you could sign up for. So you don't even need to subscribe to cable anymore. I mean, the cable companies, I gotta admit, I turned off my cable lock, because I found I was only watching a couple of stations. I don't have cable anymore either. So I bought those stations, and now I get them over the internet. Now I still pay my cable provider for my internet connection. So they still get a little bit of my money, but not like they used to. So everyone's gotta make this huge adjustment, and to compensate for us shifting so much of our economy onto the internet, we had to change the internet. And let's discuss that, some of the changes that we had to make with this new protocol. What a quick accomplish. You did some research? Yeah, so web pages used to be fairly simple. They used to be some text and some images, but now they're much more complex, and they're made of content maybe coming from different sources that are embedded or overlapped. So the way that HTTP was set up using TCP is you'd make one connection, request one web object, receive that, open up another connection, request the next piece. Well if you're looking at some of the web pages we have, now they're made up of like a dozen different pieces. So you're gonna be making all of these different connections. Each one requires the TCP handshake to happen, all the acknowledgments. Oh, but we should mention, the reason why we have so many connections is because HTTP in its first iteration said you make one ASCII one line request, and when you get a response, that's it. Your connection is severed. So we've never changed that until now. And that's why we have so much traffic, is like we have to renegotiate every time I want something else. And like you said, web pages have multiple pieces of content to shift back and forth. Sometimes in the background you don't even know what's going on. You can load the web page, and in the background we call this asymmetric, or there's an Ajax connection, which is the asymmetric XML JavaScript connections. You don't see it's going on, but if you click on something on the page, the page won't refresh, but in the background, another connection opens up, and that adds to the traffic. So how are we shifting away from that with quick or getting better with that? So one of the things that they're able to do with quick is send multiple objects over a single connection. So we're not setting up as many connections tearing down as many connections, and that's clearly going to be a lot more efficient. They call it multiplexing over a single connection. But essentially it's just reusing that connection to send multiple objects. Also switching from TCP to UDP eliminates a blocking issue. So TCP, as we said, uses secret numbers to show how all the pieces are supposed to fit together. Well, if you lose a packet somewhere halfway through and have to resend it, guess what? Everything stops and waits for that packet to come and fit into the sequence before we go and get the wraps. And it might have to be resented and you're waiting. And we're waiting. Everything stops and waits for that. But with quick, that's not the case because we're using UDP, no sequence numbers. So we get everything, we fit it together like a jigsaw puzzle, hopefully in the right order, and then we display it. So it's a lot more efficient. Now we've all clicked on a webpage and had a bad connection and half the webpage assembles and then you have blank white space below. Or you click on a connection, you see a blip of something and then it's a white page for three to four seconds and that's what's happening. It's waiting for those packets to catch up. And that's so frustrating. And hopefully this alleviates that. In addition, it's adding some security, right? It's forcing us to use security where now HTTP you can do HTTP or we can do HTTPS, which is over a different port, now 443, and it's secure. So we negotiate an RSA connection and exchange keys for encryption, right? This forces us to do this every time. We don't have the option anymore. It's always an encrypted connection. And everything, I think every single Google site is encrypted. More and more of the web is encrypted and less and less is unencrypted. So this quick doesn't apply to the unencrypted sites at all. This is strictly for those sites that are encrypted. So in our final seconds here, I'm going to just tell people that what this could do, and Cisco was putting this out there, is that not all systems can handle UDP connections right now. UDP might get blocked by default because no packet of inspection can happen at all through a firewall if you're using UDP and it can't be decrypted. So as usual, security's catching up to the new standard. So if we all do this, we might not have the great security that we have now.  So this new protocol just came out, the final draft is out. We don't know when full adoption is gonna happen. YouTube will let you do this if you use Opera, the browser or the other browser Chrome. Also Facebook. And Facebook will let you do this. And the beauty of it is if you try to make this connection and it fails because of some blocking or firewall, it'll just fall back to your regular TCP, HTTP too, which is okay for now. Well, we're out of time. Thanks for playing. Time went fast. Okay, everybody, thanks for joining us on the Cyber Underground. We'll see you next week for another great episode. Until then, stay safe.


Well, I'm going to turn the meeting over to you except to say that I'm delighted here and to have a report that I know you're going to present and I think we're all agreed on the improvement that has been made but the things that really remain to be done in our relationship with Japan. I think that's one of the most important partnerships we have. Well, I want to thank you very much Mr. President for taking time for your busy schedule to be with us and I want to present this report to you from the Commission. Now I would like to quickly point out that this is a joint effort the Japanese and American Continents work very closely together and the report is really an agreement between both members. As you can expect there might have been some things that would have been said if we had complete freedom to say them but I was very encouraged by the fact that the Japanese have been very forthcoming and very much interested. I think we all came out of this study with a conclusion that this is an extremely important relationship not only in the short term but in the long term. In addition to the work that we did in discussing these issues among the Commission members we had a number of studies done on various aspects of this relationship, a very good study in agricultural policy, a good study on industrial policy and we also had a study made to try and get some idea about what the options would be in the long term, what would happen if we continued a close partnership with the Japanese over the next 10 or 15 or even the next century and if we didn't and I think the conclusion we come to is that this relationship is so important that we have no option but for both of our countries to work very hard to maintain the close cooperation and I think that out of that and really in part out of some of the things that you and your associates have done here our recommendation is that this relationship will benefit from better management and I think the exercise that we went through when you presented the end dollar issue to the Prime Minister this last fall the fact that Secretary Reagan followed up on that George Bush went over it was an example I think of where some of these issues can be managed in a more effective way than simply reactionary process that has come about. Now the Japanese are presenting their report to the Prime Minister at about this time and I've had a wire here from Japanese Co-Chairman I thought I might just read that excerpt from this because he especially wanted to have you realize that the Japanese have concurred in the program and he's going to approach the meeting with the Prime Minister and our plan is to strongly underscore a major point in the report that is the importance of the US-Japan relationship and the fact that the two leaders should pay priority attention to this relationship we will obviously stress the growing importance and opportunities for cooperation of our two nations in global affairs. We will certainly point out some of the problems particularly in the management of the relationships but we will discuss them in the context of the need for a greater bilateral cooperation. Some of the problems left unresolved will undermine our capabilities to make joint contribution to the global economic and political health and advancement. We hope to encourage our Prime Minister to instruct the government officials as well as leaders in the private sector to study the report carefully and implement some of the recommendations and it is our belief that a deep mutual confidence and a strong commitment to the shared goals between your President and our Prime Minister are providing us with a golden opportunity to maximize our cooperative relationship. Public officials as well as the private sector in both countries should seek to find ways to further promote such cooperative relationships and also improve the management of some of the frictions and they are inevitable in the interdependent and close bilateral relationship. We are very pleased that the President, Secretary Schultz and other members of the cabinet, not in itself, demonstrates the importance your government leaders are attaching to our bilateral relationship. We hope that you will convey to your President a deep respect from the members of the Japanese Commission. It was our privilege to serve your President as well as our Prime Minister in this meaningful joint project. So we hope that this will provide some guidance to move ahead with what you already started here and we think you've made a very good progress so far but we also think there's a lot of opportunity to continue the work that's being done and it's been a great pleasure for us to participate in this program. But let me just conclude by saying that unless you feel otherwise we consider the work of this commission to be finished but if any of us individually can be helpful in implementing some of the recommendations that you may wish to adopt we stand ready to do so. Well, Dave, I just end all of you. I just want to give you a heartfelt thanks. I think it's magnificent what you have done and I'm glad to hear the last few words that you said because it's very possible that I might follow my thank you with occasionally saying, by the way, would you? Well, we're ready to help because we think it's an important issue and we're just delighted with the progress you've already started in this area. God bless you all. Thank you very much. It's a good report. Well, my chance to read it. I think it's also a very good process. Also a certain amount of belief. Yes. I understand. I've never been an emeritus before and I look forward to it because as I said, things if you hadn't been visible, we had wisdom growing down here as emeritus. And I'm going to keep my laboratory and stay in Washington. I see that that part's wonderful. And as I said, it's a little note to you, maybe when the shouting and the tumult dies and you are putting your feet up here in the house afterwards, we can get together and then we'll go see that movie. Yes, there's a sort of hiatus, I think. Now, where you're going. I also would like to nominate you for the Presidential Medal of Freedom. Thank you so very much. All right, please indeed, and I can't think of a nicer person. Just a little souvenir to you. Maybe in your long years, this has already happened to you, but no, this is not an arms to lock up. Thank you. Sorry about it. She's just a pin. Isn't this one of his? The one you're wearing. It's very, very exciting. I will. She's well, she should be in Michigan by now. She's true students. Sometimes I think our schedule is bad, I think yours. I think about that old cliched about politics makes change bedfellows. They kind of mess it up a couple of times. All right, well, I always remember when I first came here. Yes, because traditionally, the second day of this was 70 years of absolutely non-partisan. We've got all that commons to deal with can't take science.  Well, some of them can't, we've been, you know, we don't have defense or state of the interview generally out there. We have two great supporters for this new Saturday, we're building this with Asia and Middle East and Africa, and that is Kat Weinberg and George Schultz. And I said in my speech today that that meant a tremendous amount to us to have two people who know and appreciate what this was hoping to do for the third of its countries and our understanding of their cultures and their development of self-respect and our development of understanding and respect for the future of this misogyny and to play a part in the efforts towards peace through cultural understanding. It can be done. If that's been done as part of it, it can be done. The old. Absolutely. Yes. Well said. Thank you very much. Thank you very much. And you'll be elected. Thank you. Thank you very much. Thank you. And it's good to see you. Thank you. Thank you very much. I'm going to need to do a group. This is the 50th, forget some things. I think some have already forgotten that. We all get to fight the evil of the prior. Thank you, thank you. Thank you, sir. Well, this is very kind of a chance. I guess you probably don't know everyone when you go down stairs to go down. That was quite a group picture. I didn't know that. I think the surprise was when, what's her name? Mary Lou. Mary Lou. Jack. She was way down there. Well, this is great. So I talked with Michael and Parker. I live in Arizona and he was out in Parker without money over the first weekend of September. As a matter of fact, we thought that he was going to be the human family. We're going to be on the platform in Orange County when we opened the campaign there. And found out we lost it to a double. To a double? That's true.  It might be my first shotgun. Mr. President, excuse me, could we have another photograph of Mr. Carter? Yes. Thank you, sir. Thank you. Could we have one with Mr. President and Mr. Carter on one, too? Sure. This is great. I appreciate it. I'll put it in there. Thank you. Thank you. Thank you. I couldn't imagine any of you in what you do. Mary, this is Mary and the woman, Mr. President, who have endlessly done this for the office of public liaison. It's my pleasure. My pleasure. Thank you. Thank you, Mr. President. I was just going to tell you, I know I couldn't naturalize what I have been and done for all of my life. If they say there's a mistake about it, there is. I've got some very fine pieces. Nancy once gave me great favor. I found that I didn't shoot left-handed. And that just anything, I guess I was intended to be left-handed, although I'm not. It's raised the other way. Anything that I just do naturally, I do that way. And so for years, I've shot with bold actions. That surprised me. I bought me a weathery. And she had it made for a left-handed shooter. It was the slowest shooting gun I've ever shot.  And that's completely backward. To put the way I should have do it. Well, thank you, Mr. President. Thank you very much. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Coas Boys Clubs of America is charted by the Congress. And we were obliged by statute to present to you a copy of our annual report. I do so now. I urge you to get a good feel of this. Because it contains a budget which is balanced. And we haven't seen that in Washington. I know. Maybe I can learn how to do it. My second presentation is on behalf of all of the boys and girls who are members of Boys Clubs of America. It's a piece of feathered art done by one of our youngsters in our Omaha chapter. And it gives me great pleasure to give that to you, sir. And thank you for all you're doing for us. Now we're going to let the boys introduce themselves to you. Mr. President, as chairman of the Boys Clubs of America would like to have you induct the boy of the year. And he's going to hear this for the first time. So would you mind reading the letter of supply of the Boys Clubs of America 1984-1985. The National Youth of the Year. Presented to Anthony Aguilera. He finished here, chosen for more than one million members of Boys Clubs of America. In recognition of outstanding achievements in citizenship and leadership. As illustrated in a commitment of voluntary service to family, friends, and community. Thank you. On behalf of us five and all the kids across the nation, this was made by the Boys Club of America. It was made to present to you here for all you've done for us in the Boys Club of America.  Thank you. It's the key to the Boys Club. Before doing that, I wanted the President to meet with me. Who is the runner up? It's my key. I can't believe it. I can't believe it's happening. This is nice. Alright, now balance the budget. Let's go with the debit credit. That particular desk has quite a history. That was a British warship at one time. The years ago, they were on a rescue exhibition from England's sailing ships in that time, 1855. No, it was found in 1855. It was sometime prior to that, up in the Arctic. And in 1855, an American whaling captain found this ship with all sails set, as if it had just been abandoned. And he brought it out. And we then refurbished it and dressed it all up and presented it to Queen Victoria. To England. Some years later, it was Queen Victoria who, when it came time to decommission the ship, as some of the planks carved this way, made into a desk, and it was shipped over here. It went in the haze. It was president of this country. And it's been used by presidents ever since. It turned there. The chair's mine. Brought my own. I think it's going to be smaller than they are today. We had to add this rim around the bottom. Our people did that because every time I tried to get my knees on the desk, I kept breaking my knees on the desk, because we raised the planks. Oh yes, I've been an Arkansas, but not as bad as you know. And there, as a matter of fact, you know, I was governor in California. Well, I hope that I can't write very much to convey. Well, y'all can leave now. This part is not part of the history of the book. This is a few supers of my own. Senator Howard Baker, the majority leader of the Senate, his hobby is, you rarely see it without a camera. He's a great photographer. He took this picture up at our ranch. Where does that look at in California? It's up north of Santa Barbara, up in the hills. When we ride, there are some hills there from which we can look inland for the Santa Inés Valley and look out the other way and see the Channel Islands in the ocean. Is it because you had a family ranch or did your father own it? No, no. Did you just bought it? We found it. It goes all the way back to Spanish land grants and the house, which isn't visible there, but which is over this way from where we're standing. The house was built in 1872. It's adobe, and the adobe bricks were made there of the soil right on the ranch. And still standing and we're still using it. It's a small house, but the only heat is in the fireplaces, and that's why we cut a lot of wood. That's in the yard of the ranch. That's my daughter. This is my son, Michael, and his wife. These are my grandchildren. That's my daughter, Maureen, and her husband. That's my son, Ron. What's he accepting now? What's he accepting there? Resident? All right. So I... I think we were just looking in the newspaper. He writes now for magazines. Well, yes, in a way. Maybe it'll give me a chance to reply to some rather inaccurate statements that have been made. Thank you. We're all right. Well... Thanks a lot. Thank you. That picture of George Washington, there is an image of one of the old paintings I understand you didn't have as we go. Yeah. And that was found by an American some years ago in Ireland, and he managed to buy it to bring it back and he felt that it should be back in this country. That's old George. Well, it's good to see you. Thanks a lot. It was nice meeting you. Good to see you, Mr. President. Mr. President, this is Eileen Peters. It was no one to think what would be saddening. She's only liaison with all of you first. I found the letter to George Washington. Well... This one was it? It wasn't. It's fine. It's fine. I'm glad you won the election. Well, it's nice to see you. Good to see you. Thanks a lot. Thank you.


Alright, we'll stay on the topic of containers, this time with Gluster. Give a hand for Kaushal. Thanks. Thank you everyone. Okay, so today I'll be talking about Gluster container storage. This is that is storage for containers running in your containers, similar to what Rook is doing with Seth. So this is what Gluster does for containers, right? So I'm Kaushal. I'm a senior engineer at Red Hat and I work on the Gluster project. I'm a maintainer and I work mainly on the Gluster management frameworks and right now I'm contributing to the container story around Gluster. So in today's talk I'll talk about what GCS is. We'll go into a little bit more of a detail about what GCS looks like, how it performs as in how it does what it does. And I'll let you know how you can try out GCS. Okay, so just a quick question first up. So has anyone already heard of Gluster in containers with something called Hackety, right? So yeah, this is GCS is built on our experiences that we gained with the Hackety project and running Gluster in containers with Hackety. So I'll touch a little bit about Hackety and try to compare what GCS does differently from the Hackety based stack in the stock. But yeah, so let's get started. So Gluster container storage. I'll be calling it GCS for short. Please don't get confused with GCS because in Kubernetes there is already GCS which stands for Google Cloud Storage. It's not Google Cloud Storage. It's Gluster container storage. We would welcome suggestions for a better name. So for now it's GCS. I'll be calling it as GCS. Okay, so what is GCS? GCS is a new effort from the Gluster community to provide persistent storage for containers, right? So we try to provide the two normal demands of container persistent storage that is the shared storage and the what do you say, exclusive storage. The RWX and read write many and read write ones volumes. We try to use the standard container interfaces as much as possible right now. So GCS implements one of the projects in GCS is to implement the container storage interface on CSI and using that we provide volumes when requested. For now we are Kubernetes only but maybe later on if we get help we'll move on to other container orchestrators. And GCS is being designed for a hyperconverged deployment right now. As in your storage runs along with your apps on the same servers that your apps ports are running, right? So yeah, so while the storage ports run along with your app ports on the same nodes, these are not your normal app ports. These need privileges because we do deal with underlying devices and underlying file systems and all. So we need to run in a privileged mode, right? Okay. So GCS, right? It's not just a single, it's not a single project. It brings together a lot of Glastro related projects and under a single umbrella. So I'll go into detail about what each of the project does for GCS specifically. So we bring in Glastro FS that everyone, I hope everyone already knows about, right? So the file system, there's Glastro E2 that's the new management tool that we have been building. There's the CSI driver specifically. There's Ant Hill. Ant Hill is a Kubernetes operator that will deploy and manage Glastro on Kubernetes. And there are other projects like Glastro Prometheus which helps monitor Glastro inside a Kubernetes deployment. So basically you can plug in Glastro into your Kubernetes dashboard and you can drill down into Glastro volumes. Glastro Mixon provides the dashboard configurations, provides the alerts and rules, etc., right? Okay, sir. So now why would you want to use GCS over what we have currently with Hecti, right? So the main theme of GCS is to simplify the whole experience as much as possible, right? So we simplify how the containers get deployed, how Glastro gets deployed on Kubernetes. We simplify the general overall management workflow intended for the admins or users, right? We also go ahead and we are trying to simplify the Glastro FS stack itself. So and try to simplify the stack, the file system stack and ensure that they work well for the container ecosystem. So what we do is that we try to make opinionated defaults, right? So right now the normal Glastro FS installation doesn't do any opinionated defaults. So it just leaves it open to the users to what you want. Everything is enabled. Everything is available. So GCS is in that. So there are, we choose features that need to be enabled. We choose options that need to be defaulted. And yeah, that's how GCS goes. Yeah, and all of this is going to be automated. So hopefully the most admin needs to do is to write a manifest for anthill, deploy anthill, write a cluster manifest on Kubernetes and done. So anthill takes care of deploying everything that is required. So all the projects that I mentioned earlier. So anthill takes care of deploying all of them, managing all of them in the future. They'll also do data operations like replacing a node, upgrades and other stuff, right? And all of this together, right? Allows us to improve our scale in the number of volumes at least. So Glastro FS originally wasn't designed for the container sort of environment. So Glastro FS was designed as a NAS replacement wherein you have one single large volume or a few single large volumes. So, but in containers, you generally deal with lots of very small volumes. So Glastro FS isn't particularly designed for that, but we are doing optimizations. We are trying to figure out ways so that we can scale better. Our goal is to, on it, I guess this is goal for a three node cluster that is like the minimum for, if I believe, open shift that is required. That we can provide 2000 read write, what do you say, read write many volumes and up to 5000 read write once volumes. That's the goal. These are like small, small volumes. These are not really huge. So something that can run in three node cluster, right? So this is what Jesus is going to provide. That is going to be different from the original stack. So I'm not going to talk too much about the current stack. As I mentioned, we have a hackety-based stack. So the hackety-based stack looks somewhat like this. So we have a component within Kubernetes itself. That's so we are pretty much like tied into the Kubernetes release cycle. So it's not so independent. There's a Glastro provisioner within Kubernetes. We have a separate hackety part, right? Hackety manages the Glastro parts. And the thing, one big problem with hackety-based deployment is that we have a hackety-db separate with a Glastro configuration separate. So there are two separate ways of the Glastro pool. Hackety has its own view. Glastro has its own view. And the problems that we see there are mainly about these two going out of sync. And recovery from that is hard. But a lot of work has been done on this. And right now we are a lot of it has been solved. But still there is a problem with this. And in general, this stack relies on the normal cluster deployment as the normal cluster installation as in without the opinionated defaults that the new GCS stack is going to provide. Right? So there are details available below in the slide. The link is available in the schedule. If you want to, you can look at this. So looking at it, it looks relatively simple. But deployment and managing this cluster is challenging. It's not easy. Right? So let's get into GCS itself. Right? So GCS looks like this right now. So there are few components. We have Kubernetes. We don't need to worry about that. So we have Anthel. Anthel is a Kubernetes operator, as I mentioned, that is going to deploy and manage the rest of these things. Right? In addition to Anthel, we have the CSI driver. That is going to be the point of interaction with Kubernetes for us. So Kubernetes talks to the Gluster CSI drivers. Gluster CSI driver will then talk to the Gluster parts. In the Gluster parts, we have the new management tool running Gluster D2. We have Gluster FS. We have the Prometheus exporter inside. And we also have an HCD cluster. That is a single source of truth right now. So the new management tool, Gluster D2, stores the cluster view in HCD. So we have, GCS runs its own HCD cluster and doesn't make use of the Kubernetes HCD cluster. Right? So yeah. Okay. I talked about all of them anyway. So let's go into Anthel first. Right? Anthel is a Kubernetes operator. Right? Which defines custom Gluster GCS resource definition. So Kubernetes provides ways for what do you say, other projects to define their own resource types. Right? Object types. So Anthel defines the GCS resource types in communities and it automates deployment, upgrades and day-to-day management of GCS. Right? At the current state, Anthel is very early. There isn't actually anything, other than the CRDs, there isn't actually anything present yet. But things are, we are working on stuff. Things will come out soon. Anthel is developed under the Gluster project in GitHub at github.com slash cluster slash Anthel. Next up, we have the CSI driver. So the CSI driver consists of, okay, so as I mentioned CSI driver translates the Kubernetes CSI request into the GD2Rest request, the Gluster D2Rest request. That's the main goal of these drivers. Right? So in addition to doing the translation of the request to create and delete volumes, right? It also will take care of doing the mounts. Unlike in Hackety, right? What would happen is the Gluster provisioner in the Kubernetes. Within Kubernetes would take care of reaching out to Gluster or reaching out to Hackety. That provisioner would take care of doing the mounts. But in this case, we do everything via the CSI driver. So it gives us more freedom to do things the way we want. Right? So the CSI driver consists of three different types of parts. There's a node plugin. There's a provisioner and an attacher. Right? I'll go through what each of them does. Attach your provisioner and node plugin. Right? The attacher is for us, at least in GCS world. It's a no-op. It's useless for us. But we just need to provide it because the Kubernetes CSI spec expects it. There is work going on to ensure, to allow that, allow CSI drivers without attachers. So not all CSI drivers actually require attachers' work. So the provisioner part, right? This is the main part for us right now. So this takes care of translate. This is the one part that listens for Kubernetes persistent volume requests or persistent volume claims, forwards them to Gluster. And yeah, that does it basically. It listens for the create and delete volume requests and forwards them to Gluster, translating them to the GD2 requests. So in this part, we have, sorry. Oh yeah, in this part we have four different things running. So there is a Kubernetes provisioner. Sidecar, so these, a few of them are provided by Kubernetes themselves. These are not developed by us. But yeah, so there's a Kubernetes provisioner. The Kubernetes provisioner's job is to listen for Kubernetes persistent volume object requests. And then the provisioner would talk via the CSI spec to the Gluster CSI driver, which would then relay that forward to the Gluster layer behind. So yeah, so there's a provisioner. We have a Snapshot or Sidecar which takes requests, handles Kubernetes requests for volume snapshots, persistent volume snapshots. And there is a cluster driver registrar which registers Gluster FS CSI as a cluster level driver. So it makes the Gluster storage available as a storage class. So that's what the provisioner does. This is deployed as a, right now if I am right, a state full set so that it's always available running. And yeah, then we have, then we have the node plugin. The node plugin basically runs on every Kubernetes node that you have, right? Its main function is to mount the volumes when requested or attach the volumes to the app parts when requested. So yeah, that's all it does. So there's a driver registrar. Again, it makes the Gluster driver available on that node for mounting. So that's, there are two containers. The driver registrar makes sure that the driver is registered for, so that Kubernetes knows to reach out to the driver to perform on. Right? So if the node plugin parts, right, also contain the Gluster FS client bits. So you don't need to have the Gluster FS client bits installed on the Kubernetes hosts. With the previous deployment with HackET, you needed to, you needed the client bits installed on your Kubernetes hosts. So that was one more issue with that. So yeah. So then now let's go into the Gluster part itself, right? So the Gluster part has Gluster D2, Gluster FS itself, and the Gluster FS exporter. So first I'll talk about Gluster D2, right? So Gluster D2 is the newer management framework for Gluster FS. It's intended to provide automated management operations for Gluster FS as an automatically create volumes based on requests from the user, right? So a user can request for a volume of a particular size of particular capabilities. And Gluster FS GD2 will automatically decide upon the layout of the volume and as the user requested and create the volume, right? In addition to that, it also tries to provide intelligent or automated volume management operations about, say, scaling a volume or shrinking a volume, replacing nodes, stuff like that, replacing bricks, stuff like that, right? So basically what it is doing is it is converging the functionality of different tools earlier that were there outside the cluster, right? So we had HackET running outside the Gluster cluster, Gluster pool, sorry. There was a project called Gluster Block which is used to provide the RWA volumes or block volumes, right? These were running outside the Gluster pool, right? They were not directly managed by the Gluster layer. All of this is converged into one tool right now, so Gluster D2. Gluster D2 does the work of HackET, right? Automated volume management. And it also provides block volumes. In a different sort of way compared to Gluster Block, we'll see how it does it in a little while, okay? So yeah, so GD2 provides a REST API like HackET, right? Against which you can program. So this allowed us to write our CSI driver. We have an API that can be reached out to over the network to do operations. So the CSI driver works on that. GD2 also has a very good orchestration engine built in, right? So it's more resilient to failures than the orchestration engine in the current cluster management layer, right? So we can do undoes, we can do rollbacks if some operation failed. We can do an operation and say a note comes back up later. It can rerun the operation if required stuff like that. So it brings in features to do more resilient orchestration of operations. So basically the management framework, what it does at the end is that it needs to go to each node and prepare the break, start processes and do stuff like that. So the GD2 brings in a much better framework to do that. In addition, as I mentioned earlier, there is just a single source of truth for everything. There is no split in cluster information between HackET and Gluster. So all the information is with Gluster D2. So Gluster D2 knows what all volumes we have, how the volumes are laid out, what all devices we have access to, stuff like that. So how many devices we have used, everything, right? So yeah, there is less possibility of failures because of HackET and Gluster going out of sync, right? In addition, GD2 also brings in support for Prometheus and OpenSensors so that you can trace or monitor GD2 with the standard tools that are used elsewhere in the container ecosystem, right? So Prometheus is widely used for monitoring within Kubernetes. OpenSensors implements the Open Tracing API. So again, we provide Open Tracing API endpoint so you can trace operations across the cluster if required, right? Yep. So as I mentioned, GD2 provides normal volumes as well as block, Gluster block. So the normal volumes are used to satisfy the Kubernetes RWX volumes or rewrite many volumes. The way how Gluster D2 helps there is that for normal volumes there is automatic provisioning of bricks. So we go ahead and we create the LVMs, we create the thin poles, we create the file system on top of that, we do the brick mounts. We do all of that, GD2 takes care of doing that. And in addition, one special thing that we bought in was support for volume templates, right? So the normal Gluster installation would contain a volume template with everything, right? All the features that we provide. But for the GCS use case, for the continued use case, you wouldn't need all of them. So if you had all of the features enabled in the graph, Gluster graph, it would be resource heavy, right? So you don't need that. So we can provide a custom simple template for RWX volumes for containers. Cool. In addition, we also provide RWO volumes, as in we also provide block devices, right? So block devices are meant for single users, right? Single client access. This is still a work in progress. Bits and pieces of it have been merged in. It's not complete yet, but yeah. So what this does differently from the Gluster block project is that this tries, does block exports in a very simple way using loop pack devices, right? So what it basically does is that you have a Gluster FS mount on your Kubernetes node. And from that mount, on that mount, we create an image, I mean device file or image file and then do a loop pack mount so that it's available as a block device, right? The Gluster block project did its exports via iSCSI and there was a lot of involved process in getting that set up. So that's more complex. Scaling was a problematic there. This one allows us to scale really easily, much well. So let's see the current status. Yep. So as of this moment, we can scale to again. All of these I'm talking about in a three node cluster, right? You can scale to about a thousand volumes, IWX volumes and hundreds of requests parallel as in hundreds of volume creation requests or volume decision requests happening parallel. So it doesn't bother you. We at this scale, we have begun hitting the limits of LVM scaling itself, right? So LVM, again, like Gluster previously, LVM itself wasn't designed for this sort of a thing. So Gluster uses LVM thin pools to provide snapshot capabilities. So we use LVM. So we need LVM, but right now we are hitting on LVM scale issues. We are trying to figure out optimizations in the way we perform LVM operations itself that can help scale a bit further. And we are also looking at other options if possible for IWO volumes. Yep. Yep. In addition to the LVM scaling, we also sort of hit HCD scaling when all of these requests come together. Again, we are tuning the HCD config itself, how we deploy HCD and we are tuning how we use HCD itself. So as in how we store data in HCD, how we access HCD, right? So we are doing that. And Gluster D2 is also, again, developed as a separate project under the Gluster community. So it's developed under GitHub, Gluster D2. Okay. So now let's look at what we have been doing in Gluster FS itself to help with GCS, right? So the main focus has been optimizing resource usage. So this has been in progress from the last few releases. So Gluster 5, one of the main topics was optimizing resource usage. Gluster 6, the upcoming release is also, there is a lot of focus, again, on optimizing resource usage. So basically, we are trying to reduce the memory that we use. So we are fixing a lot of the memory leaks that we have and everything there. We are trying to also optimize how we use threads, how we deploy it. And yeah. So we are optimizing resource usage. And again, there is this, if I don't know if you have heard of multiplexing before, this multiplexing is a feature in Gluster where we run multiple bricks in a single process, right? So again, before GCS, it wasn't such a priority. It was okay, we wouldn't have thousands of volumes running with GCS, with containers. We can't have thousands of processes running inside the pod, right? So we need to consolidate that. So yeah, we have multiplexing already for that. Multiplexing works for bricks, but there isn't a similar process for self-healing. So the volumes that we provide are redundant as in replica Gluster volumes, Gluster replica volumes, right? So they need to have self-healing demons running. Self-healing demons right now are individual per volumes. So again, there would be as many self-healing demons as volumes that we have. So we need to multiplex the self-healing demons as well. So that's work in progress, okay? And there are other features like fencing. What is fencing? Yeah, so fencing is like a feature where we can ensure that only one client can access a file at a given time. So this is required for block volumes so that we don't have clients or say, right? Say now a pod was rescheduled on some other node. Or we don't want them to like begin accessing the image file before some cleanup has happened or some release of blocks or whatever has happened, right? So things like that. So again, Gluster FS is developed under GitHub Gluster FS, right? Okay. Next on monitoring. Yep, so monitoring is developed under two projects. Again, under Gluster community, there's Gluster Prometheus and there's Gluster Mixense, right? The Gluster Prometheus project provides us with the Gluster FS exporter demon. This runs along with GD2 and exports the Gluster metrics available, right? So it's not just the cluster level metrics that GD2 could provide. It's like per volume metrics, per big metrics, process metrics as in how much CPU is being used, how much disk space is being used and all of that. So the Gluster Prometheus project provides this. And there's a Gluster Mixense project which provides rules and alerts, right? For Prometheus and for Grafana so that you can build dashboards out of it. So right now the Mixense projects provides a dashboard configuration for Gluster FS volume. There are others being built. Okay. So I'm going to skip this. I was just going to talk about how the flow of operations was going to happen for a volume creation, but in simple terms, it's just straightforward, right? So it's Kubernetes to CSI driver, CSI driver to Gluster. Again, the same flow. Create a volume, mount a volume. It's like one flow, single flow. It's the same for both sorts of volumes because everything is in one place. There's no split. There's no HKT so that the request needs to go to HKTR then to Gluster, right? Okay. So, okay. If you want to try out GCS, just keep in mind that it's still in very heavy development. We are planning on doing a one-dot release sometime soon where again it's not fully featured, but at least you can make use of it and just see how it works, right? So yeah, at the moment, we have an Ansible-based deployment tool written. It's not a deployment poll. It's just a playbook that deploys GCS, right? As anthill isn't complete yet, so we are depending on Ansible right now and this playbook deploy GCS.yaml. This performs the full deployment right now. But as anthill grows and gains more features, we'll be cutting down what the playbook does. So in the end, the hope is that the playbook would only deploy anthill and we are done with it, right? So, for more information on how to use the playbook to deploy GCS on your Kubernetes cluster, you can read the readme. So the readme gives you information on how to prepare the Ansible inventory files and how to run the playbook so that you can deploy GCS, right? But if you want to just do a quick test on your local laptop, so we have a vagrant file available which does this. It's vagrant-libert only for now because we do some adding additional tests and all that we haven't yet figured out on how to do for vagrant with virtualbox. Contributions are welcome to help do that. This vagrant-based tool will deploy Kubernetes and GCS for you on a three-note cluster, right? So Kubernetes deployment is handled using CubeSpray. We have a playbook that calls CubeSpray finally, but this playbook has some configurations that we need to enable for GCS to run, right? So we need to enable certain feature gates to allow the CSI driver to work. So CSI driver is still a work in progress in the Kubernetes community so not all the features are enabled out of the box. So we need to specially enable some features for the CSI drivers. Again, more information on how to use this is provided in the readme, right? So, yep, this deployment tool is available under the GCS project. So there is a github.com slash slash slash GCS. Under this we have a deployed directory where all of this is contained. So yep, and that's basically it. Again, as I mentioned, GCS is being developed under Github cluster GCS. So under this project we mainly have the overall issues tracking the full GCS, what do you say, worldview sort of a thing. And there is a waffle board which tracks the GCS related issues across the multiple different projects that I just described. So that's it. Please try out GCS and let us give us your feedback. And I'm open for questions now. Okay. So do we support extending volumes? GD2 itself supports it. The CSI driver doesn't yet, I don't know if the Kubernetes CSI spec supports it yet. So if that support comes in, we can build it. So our, the cluster management layer already has support for automatic expansion. So we just need to do one extra call when that is available. Is it possible that, so I suppose three nodes should have equal storage, equal hardware, yeah. It would be preferable? Preferable, yeah. It would be preferable, but, okay, sorry. The question was, in a three node cluster. It forms this big storage. And to answer the source sum, I provide only one revenue for that. And for some other volumes, I ask to have, for example, three per application. Is it possible? Okay. So I'll repeat the question. The first part was, is it possible to have non-homogeneous hosts? We prefer if you have homogeneous hosts, but GD2 should be able to work with non-homogeneous hosts. The second part was, if you are able to choose the, what do you say, redundancy count, the epic account. Right now, we aren't targeting that because we want to simplify the number of options that users have. For us to build confidence in what we are doing first. That might come in later on, right? So right now, we, the CSI driver is hard-coded to create three replica volumes. It's hard-coded. It's hard-coded. So those three replica volumes can be created on a heterogeneous cluster, as in, but the thing is, since it expects always three replicas to be present, if we can't individually provision bricks on three, on each of the three nodes, the request will fail. So that's going to happen. But yeah. Any further questions? Yes? Not really stable. Okay. The question is, how stable is GCS right now? GCS isn't really stable. We haven't reached something that we would ask users to deploy in production yet. Right? The upgrade stories and all should be pretty simple, but we haven't thought about that yet. We have been just working on getting what we want to deliver in the first release fixed. So the upgrades for GCS would be simple enough as, because it could be just deploying the new version of the blaster parts. Right? All our configuration right now stays in HCD. HCD itself has its own upgrade mechanisms already defined for Kubernetes, so that's taken care of. The GCS parts themselves always rely on the information in HCD. So once we reach that stage, yes, it should be simple enough to do upgrades. Yep. We need to do so. Okay. The question is, how do we intend to do the upgrades? Right? So if parts are mounting volumes and whatnot. So as I understand, there is some sort of, I don't know, gating sort of capabilities in the Kubernetes operator world. I don't really understand the operator part of it well. So the operator would take care of doing that. Right? So what the operator would do would be to like bring down one particular part. Right? Then get a new version of the part up and running, do whatever mounts is required inside that. Till that part is up and running, it would block the upgrades of the rest of the parts, do stuff like that. So it's not exactly clear at the moment, I believe there is some way to get operations to allow this to be handled in a smooth way. Yep. Any further questions? Nope. Thank you everyone. Please provide feedback on Boston.org.