Hello and welcome to my talk. Today I want to talk about the Debian games and free software games in Debian and the status of games in Debian in general. Where am I? I'm a Debian developer from Germany and I've been using Debian since 2002. In 2012 I started to contribute to Debian and one of my first packages was a game of course. At the same time I also started a little project called Vinox UAD where you can play multiplayer online games from the Debian repository including games such as Open Arena or the Battle for the Wiesnacht, Team Worlds and so on. I contributed to, as I said, I started to contribute to Debian in 2012 and at the moment I maintain or contribute to around 500 packages mostly games and Java packages but also to the long term support section in Debian. So what can you expect from the next 45 minutes? First of all I want to talk about the fundamental differences between commercial games and free software games because most people think that commercial games are the norm, which they are, and they don't know very much about free software games. So they ask, can I play a game X on Linux? And 10 years ago I would have said, it will be difficult. Nowadays I tend to say rather yes. It is possible. It is definitely better than it was 10 years ago. I also want to talk about how you can find games in Debian that's not as easy as it sounds. There are multiple tools available for you and there's also a project called Debian Games Blend. I want to explain why we put some games in the main repository in Debian, some in Contra and some in not free. What is the difference and why are they there? Why are there games which we cannot package at all? I will tell something about new games in Debian 10. Well, at the end I also want to explore some new ideas, what we can do to improve the status of Debian games. If you look at the global game marketplace you will see that they deal with thousands of games which are a million dollar business. Many of them attract millions of players around the world. There are big titles, blockbuster games, so-called AAA titles, which consist of, for example, Dota or Counter-Strike, SimCity, Call of Duty, Overwatch and so on. These games attract a lot of people and they make a lot of money with it. I've told this before, last year in Montreal there was a project, it was called the next generation multiplayer online role-playing game by Blizzard Entertainment. They decided after they spent three years developing the game that it was not good enough. Before they made a decision, they employed about 100 developers and creators of artwork, software developers, who worked full-time on the project, and then made this decision, okay, it's not good enough. And they took the assets, all the images, sounds and what they have done before and made a new game. That's called Overwatch now, which is quite a popular game again. Blizzard Entertainment gets it mostly right all the time. They have four or five franchises, but they always attract millions of players and make a lot of money with it. So if you take a look at FOSS games or free software games instead, you will see that the revenue of these games is close to zero. Most developers receive no money at all or receive no donations. And some of them, if they are lucky, they can sell their game on Steam or very, very, very few can attract enough people to support a crowdfunding campaign. For example, ZeroAD tried that and they could raise some money, but that's the exception and not the norm. Successful games attract thousands of players, for example, well, MindTest is a very popular game nowadays. It's a clone of Minecraft, but it has a very active community and obviously it's not as big as Minecraft, but it's still, compared to other games, a very active community. You also have to say, OK, FOSS games are a niche. That's the truth. It's not as big as commercial games, of course, just because nobody funds those projects.  But yeah, they make no money with it. So you can't expect the same amount of quality that you see in commercial games. When I talk to people who only know commercial games, they are a bit disappointed. But you have to see this in perspective. Well, there are good arguments for free software games. The most important one for me is that we have the source code and also, in most cases, the right to modify images, the sounds, all the assets. So that means even in 10 years' time it is possible to develop a new game or to modify the game. Or as we have seen in the past, it is possible that we can maintain games for 20 years or longer. For example, FreeSIF was developed in 1996, I guess. And still to this day, 20 years later, it is still developed and there's a vibrant community around it. And that wouldn't be possible if sources were closed. It is also a great way to learn about developing in general and it is not only meant for developers, but also people who are not into coding but more into creating artwork can share their work. And it is easily accessible for them in my opinion. So this artwork is reusable for other projects. And that's also not possible with proprietary games, of course. So if you think about it, there are game libraries which are not only used for games. They can be used for everything and a special for projects like the Open Robotics project. There is a story I packaged once a free Orion and I needed bullets to complete the packaging. There is a 3D multiphysics library which makes it possible to simulate deformances. And we have compute different objects to hit each other in space. And someone from Open Robotics contacted me and said, hey, cool, you have packaged bullets and we use it for our robotics project. You can see that not only the libraries are meant for games, but can also be used for different projects. And that's quite cool, so we are not only packaging for a niche, but it can be reused. Another important aspect is that it is excellent integrated into Debian, which you not always have with commercial games. So we apply the same rules as with other programs. And, for example, we are very careful when it comes to licensing. We review not only the code, but also all the assets. And that is a very time consuming task. But it also is very important that we only have software and artwork that is free available. Yeah, major games communities. I mentioned before, MindTest and The Battle for Bison, but there's also SuperTaxCard, Xenotic and COAD and FreeZiv. These are the biggest communities in the free software world at the moment, I think. And they are between 10 and 20 years old. MindTest is a bit younger, it's only 5 or 6 years old. But they are very active and they still produce a lot of new content these days. I have counted 600 different games and emulators last time I checked. That's the number of games, free software games in Debian. And all software and artwork complies with the DSG. Most games are written in C and C++. We also have some Perl games. Most important one is Frozen Bubbles. One Haskell game is Raincat and a few Java games. We are very proud of that. We also have D games, which are quite rare. And the maintainer of GCC suggested that we support them to Java, because he hates to support D, but they are very great. And if you want to look at them, you can find them in the package games, like iPhone, shoot them up. And, well, they are really fun, I think. Popcorn reports more than 2,000 installations for popular games. Is this a good number? I think yes. Because even more popular applications outside of the game universe can have much fewer installations. What I should mention, too, is that we are talking about PC games mostly, because web and HTML5 games are quite rare in Debian. As I know, there's only one game in the archive which could be possibly played in a web browser. That's Cave Express. But it's quite hard to sustain the tool chain. So you need to maintain a compiler that compiles the C++ code into JavaScript. And this hasn't worked all the time. So, yeah, if you're up to the task, please do it. So one of the most difficult problems in Debian is how can you find games? I say this because 10 years ago I tried to get an overview of what games we have in Debian. And this was not very easy, because most people suggested to use the terminal and to use tools like app or aptitude to find them. And, well, not all users are into this kind of stuff. They would prefer something more graphical. So nowadays I would suggest that they use tools like Synaptic, Known Software Center, or if you are into KDE, KDE user, you could also try Plasma Discover or Muon. Yeah, why do I say that? It is... Most people think that users of games are also hard-core Debian users. Most people think Debian is about servers, or it's about this desktop environment and this desktop environment. But people who want to play games are most often very casual users. So they don't want to spend much time to find games and just to relax and enjoy themselves. Yeah, we should make it definitely easier for them. There's another project which I mentioned before, it's called Debian Games Blend, and I come to that in a few minutes. So let's take a look at Known Software Center. You can see a lot of symbols, you can see game names and game descriptions. What you can also see is that some of them are translated and some are not. So the language, which you cannot understand, that's possibly Klingon, and you can see that, for example, the game Killbots has a translated text and, well, then there are others which are in English. So this is a bit confusing. Why is that? Why is it so? Those information are derived from so-called desktop files or AppStream data files. And most games do not ship such AppStream data files, so we derive all the information from desktop files, but they are poorly translated. So most of them are only in English and few of them contain German comments or French comments or Spanish comments, but I know of very little games, for example, who are translated game descriptions, which are translated in Chinese. So in an ideal world, you would see that all these icons and all these games would show Chinese translation text, but we don't have that yet. So there's a lot of work to do in the translation area and at the moment we are not there. What you can also see is the difference between icons. Most of them look quite good, I think, crisp and clear, but take a look at Corruptor or Lure of the Tempris or, for example, Magikor, the game on the left. The resolution is very poor or they are just screenshots, so they can be improved because people tend to play games or are attracted to games with nice icons, so more eye candy is always good. But if you don't have a good eye candy, people mostly think, hey, bad eye candy means it's not a good game, so here we can improve too. The Davy games blend. That's something I started in 2014, I guess, and that's just a collection of meta packages. So if you wonder, okay, you know the tools now, GNOME Software Center, Muon and so on, and you can also use aptitude. But then there's another alternative, you could install just a meta package. If you're into games chess or games cards, then you can just install the corresponding packages. If you are more into Tetris games, you would install games high in Tetris. Or if you don't know what you really want to play, I suggest to install games finest, which contains more than 100 games, that's a lot, you know? But in my opinion, you cannot narrow it down to 10 games, which are good because people tend to say, hmm, I like strategy games and the others say I like road-playing games and there are other ones who like first-person shooters. But those 100 games are of high quality, I believe, and some of them should be enjoyable for everyone. That's our platform page at the moment. As you can see, it consists mainly of the game description and two links to the packaging at tracker.deben.org. In my opinion, this site could also be improved, but as usual, we need more people who want to invest time into it. So we not only need people who try packaging, but it would be nice if there were more people who would like to design a new page, for example. And I think if it is done well, you can definitely promote first games better. But in the meantime, I think it's a solid okay thing and it's informative, definitely. Well, since last year, a lot has happened. We've got some new games and we had to remove some others. For example, G-Tatrainet was removed and a special game, which I liked a lot, OO Lights, that's the clone of Elite, was also removed because the maintainer couldn't provide support for an embedded library, which is called Lipmoss.js. There were security implications and AppStream didn't want to remove the embedded library. So he decided, okay, I didn't want to do all the work and it's enough and well, it was dropped. And there are other games like the aforementioned G-Tatrainet, which depended on GNOME 2 libraries. In this case, we cannot do very much because nobody is interested in porting them to GNOME 3. We even got a response from one of the AppStream developers who said, wow, it was cool that you maintained my game for 15 years. But nowadays, well, I probably should rewrite it and port it to another language or something like that. It's a shame, but that happens all the time and it would be cool if we could improve on that. But, well, not enough people. And another game we had to remove from Debian that was a sprite editor, the last game on the list. And the author decided to change the license to a non-free license so there was not much willingness from our side to maintain it anymore. On the other hand, we... Some other people packaged new games, including DD-Dat, which I've heard is a popular game in Taiwan. I believe one Taiwanese contributor even packaged it. There are other games like Icebreaker, which were reintroduced. So this is a good example for not... You shouldn't worry too much about if games get removed. You can always reintroduce them. And Icebreaker is such an example. There's also Lugaro, which I can recommend. Lugaro was formerly known as Open Lugaro, but the name is a bit misleading because it wasn't open. The assets were still non-free. But this changed last year. And Wolfwire Games decided to change the license. And so we could introduce it into Debian Main. Well, now I've talked about Debian Main all the time, but there are also games in Debian Contrib. So why do we ship games in Debian Contrib? Most of these games are game engines, which are free software, but they don't have any free assets. So in order to ship them in Debian Main, we had to either create new content, or had to cool wins upstream to change the license. Nothing of that happened. Examples are L-General, Q2 OpenMW, and MRB. And for L-General and Q2, I created a new data package. So those engines on those games could be moved to Debian Main, but OpenMW and MRB are difficult because they are commercial games. These commercial games are consisted of, I guess, several gigabytes of data, and they were never made free. So in order to play them, you have to download them somewhere. Well, why are we so picky about that all game content must be free? There's actually a debate. Popular men, which is so unsaid, since the art in the game is not software, it is not ethically imperative to make the art free, though free art is an additional contribution. Some in our team disagreed with this view and said that it is imperative that for a game to function, it also requires data or software images, and they must be free. So without those assets, the game wouldn't function. And that's why we decided to put them in Debian Contra. The engines are free. But the assets are non-free. In my opinion, we should use Debian Contra as a staging area and work on it to either produce free content or take free content from other sources and rearrange it and create our new packages. Sometimes a demo version would be enough. It doesn't have to be always a complete game. Then we came up with another solution, better Simon and Alexander. Simon developed a tool which is called Game Data Packager, and it is written in Python 3, which is able to download content from different sources, mostly good old games, gog.com, or you can also use images from certain CDs or DVDs. And the tool just checks, verifies, is the data valid, and it creates hash sums of files, and they are stored in YAML files. And we have currently 215 supported games, and you can just easily use a command line tool and if you own the original content, then it will create a depth package for you. Why is it useful? Most people want to have a clean, tidy system, and if we can package it in a Debian package format, that's definitely more favorable than just putting those files in your home folder. So last but not least, non-free. Non-free is evil. Packages must be placed in non-free and compliant with the DFSG or are encumbered by patents or other legal issues that make the distribution problematic. The minimum requirement is they should at least be distributable. Most non-free games are assets game data packages, but we also have or had some games like ZengBand, I don't know how it is pronounced correctly, that's a fork of ZengBand, a very popular rogue game. The only difference between ZengBand and ZengBand is, beside the rules and there are more characters and more possibilities to play the game, is that they kept the original license which forbids to make money with the game. That means it is non-free. So if the author of ZengBand tried to convince the original author of the code to re-license it like the ZengBand folks ZengBand folks did, then it would probably be in Maine nowadays. But it didn't. And then we also have Steam. Yes, I should mention Steam, of course. This is the most popular non-free game package in Debian with more than 5,000 installations. Steam was definitely the game changer for Linux. I guess it was released 2012, Steam for Linux. And as of today, according to SteamDB info, more than 3,208 commercial games are supported on Linux. So they worked natively. Should we care? I definitely think so, because Steam is not only the largest digital distribution platform for PC games, but it also attracts new developers who want to create new content that works on Linux or they want to make their existing games available on Linux simply because there's a market. And as I don't know if you know the Humble Bundle project, they sell bundles of computer games and they make it mandatory that they should also run on Linux. And compared to Mac OS users, Linux users are less than Linux users, but they spend more money on those games than Mac OS users do. And that was a very important finding. A few years ago, people thought, oh, if I port my game to Linux, I can make money. That's obviously a good thing and more people joined the train and it goes forward. Well, Steam is not the only digital platform, but it is definitely the most important one. There are other gaming platforms, for example, Lutris, which is not in Debian, but it's free software. And the goal of Lutris is that you have a unified interface where you can just click on a game and then it is installed with all necessary tools like emulators or content and it just works. Or if it is a Windows game, it would install Wine, configure the game and you're good to go. As I said, it is not in Debian yet, but it looks promising to me. But we also have another package which is called RetroArc. It's quite similar. It is also a unified interface and it focuses on emulators and other media players. It's very similar, but it's already in Debian, so you should definitely check it out. I've sponsored PlayIT a few months ago, or two months ago. That's another project which tries to simplify packaging non-free games, which are either DRM-free or not DRM-free. Most of these games are from good old games or Humble Bundle. And the only thing you have to do is install the package, run PlayIT, name of the game, and then it will... I'm not sure if it will download the package automatically, but if you have the executable file, you can just type PlayIT, name of the program, name of the game, and it will create a Debian package for you which is then globally installed on the system and you can play the game, which makes it very easy even for casual users to keep this system tidy. Then I should also mention Wine. Wine is not an emulator. That's the acronym. And Wine made it possible for me in 2008 that I could play World of Warcraft on a Linux machine, which was, well, I was the only one in my online clan who played on Linux in those times, in those days. Nowadays, it is much more common. There's also a company which is called Crossover that provides commercial support for Wine games. So you have your Windows game and you can just install it on your normal Linux system and it will run most of the times. For example, if the game is supported on Mac OS, like World of Warcraft was, it will also run on Linux. That's the experience I have made. Another good way to play Windows games on Linux is to use Play on Linux, which is also front-end for Wine and it is free software, but also in control because it downloads non-free assets and non-free stuff, so we had to put it there. But it's a very good front-end which makes it also very easy to install Windows games on Linux. Who are we? The Debian Games team is mostly responsible for most of the games in Debian, about 400, and we are a bunch of guys who try to maintain the older games and try to package new ones, but we are short on manpower, women power these days, so we can always welcome new members. I myself joined the team in 2012 and it was quite difficult in these days because I couldn't find any sponsors. Nowadays it's a bit easier because you can just go to mentors.debian.net and if you are lucky you will find someone who can sponsor your packages, but nowadays it was definitely harder. How shall I put it? We try to integrate games and try to make it better, but it's very simple. If you want to contribute something, don't think about how or what should I do. You should have a clear motivation. So it's not enough to just say, okay, I'm here and I want to do something, that's a recite for failure in my opinion. You should have a clear opinion of what you want to do. You don't have to be a coder. You don't have to be someone who writes a lot of codes. You don't need to be a programmer. We also need people who create icons, as I said before, because they improve the visibility of games and we need people who write documentation, we need people who translate descriptions. Like I said, if your users can't read the descriptions, that's always a poor experience. So we should try to translate more game descriptions and that would be nice. So you don't need to be a programmer. Don't be afraid to do the seemingly lesser work in Debian. It's important, very important in my opinion, to make games look good. What else can we do? First of all, if you don't want to contribute on a regular basis or if you're afraid to do it, just block about your gaming experiences. Just play the game and tell people about it. You can also package new first games, but you also appreciate if you fix the bugs in our packages. Well, there are a lot of them. Even more importantly, important is report bugs. What I often see is that we release a game and then a few months after Debian was released some people report bugs which we couldn't detect before because those are runtime bugs. It is very hard to find them. We need more people who just install a game, try it out and tell us if it works for them. I've also thought about four new projects. One of these projects is improving our home page, the Blanz home page. We could also create a completely new home page at GamesDebian.org for example which would make it more obvious that we have a game section on Debian. At the moment it is quite hidden under the Blanz framework. Perhaps we could move it to a more prominent place. I also thought about the game contents database which would be similar to codesearch.net that is a Debian project for searching code but you could also create a database for image files or sound files and list them all in these databases and with their license and a preview of the image so that people could find new images which they then could reuse for other projects. Last but not least, a live image about Debian games would also be nice. People tell me we don't need it but I think it would improve the visibility of our game so if you could just hand out some images and say hey, here are 100 games which we support already in Debian let's try them. So far so good. I rushed to all my slides and I'm out of slides. Do we have any questions? My name is Andreas Tiller. I want to agree with you that Blanz pages are not very modern anymore and I would love if somebody would do some better design. This is all templated. You can start today and find better templates. For all Blanz, others would be profit as well. You might know that Ode Streicher has thought Debian Astronomy is some different design but for me it's too less information but you need to decide. Another hint is because you said you had trouble to find a sponsor in 2012. I started in 2013 the effort Sponsoring of Blanz it's just in the Wiki page where you can prove that you have understood the Blanz concept and if you have Blanz package I try hard to sponsor your package. That's a well known project and I knew about it back in 2012 but I tried directly to convince the team members of the gaming games to sponsor my packages and I was a bit disappointed while we have a games team and nobody of the games team sponsored my packages so I had to rely on Debian developers from outside the team to sponsor my packages and when Vincent Cheng became Debian developer he was merely the only one who sponsored my packages then so I had to rely on two people and it was a bit disappointing so I just remember it. Nowadays it is definitely better but I fear not everyone knows that we have a mailing list or that you can reach us on ISC so if people want to contribute they often find it difficult to find the person who they should talk to and I think we could improve that but I don't know how at the moment whether it's definitely something we could do better. Do you have ever encountered some kind of legal issues because just like you mentioned there are many game engines on the Debian package list but most of them may be reverse engineered or reprimanded from prior works so is there any kind of legal issues that they would try to sue the distributor because you distribute some kind of pirated source code? I assume these are all clean room developers I'm not aware of any game engine that is a complete rip-off, a.k.a. remake of an older game so they try to create something new something which is similar to the old game but also new there's nothing that is exactly like the old engine so for example Take El General that's a clone of Panzer General which was a game from the 90s developed by an American studio and I'm aware that a Russian developer well he almost created a clone of the original engine but he was able to sell the new game and still to this day he can sell this game and it looks absolutely similar to the original game but we don't have this problem that General is very different and our source code is visible to all so as long as this is the case and we know the author has created it and licensed it on a free license I don't see a problem for Debian but if we are aware of abuse or wrongdoings we should remove it because there are PlayStation 2 and PlayStation 1 emulators and some legal issues were some lawsuit was filed in the United States and if I remember correctly the EPSX I believe the PlayStation 1 emulator was taken down from several sites because the lawsuit back then was settled out and it was illegal to do this kind of source code I don't know, I can't say much about that at the moment so I can only reiterate if we are aware of wrongdoings we will remove it but at the moment I'm not aware of any game engine that is a problem for us I was told I can only answer one question but we can talk about anything later can you put the microphone close to your mouth please how's that? so in 2012 and 2013 the FSEF worked with Creative Commons and Mozilla and Open GameArt to run a contest called Liberated Pixel Cup and we raised I think it was just about $13,000 when I was put up for people to make free game art and free games to go with them as a contest and I thought it was a really successful project we'd love to do it again but we need more partners to work with I wonder if you think people would be interested in pursuing something like that we could announce such contests on our different media channels we have a new site we could announce it we should talk with our publicity team about that that's the way forward I think you need to communicate it through the community or you should post it to Planet Debian perhaps if you post it on a mailing list it probably gets lost so I think there would be interest in such contests but we must ensure that people get to know it or are informed correctly if you just released some information you probably never knew that there was a contest and are quite disappointed because they wanted to contribute something but they didn't know it I don't know at the moment it would be difficult to think but the publicity team in Debian is the right place to force that we were running out of time I gladly answer all the questions afterwards I would like to thank you for listening and for coming here see you, bye bye one thing Keith Packard is sitting next to me there is another talk about games and Steam and I can highly recommend it to everyone who wants to know more about Steam and the development there go to it


So it looks like it's time to get started. Welcome to another OpenShift Commons briefing, everybody. Your usual host, Diane Mueller, is helping a bunch of kids learn about the outdoors of British Columbia. So I am your guest host for today. Today we're going to have a briefing on some of the work happening inside of Red Hat on an operational dashboard for OpenShift V3 and Kubernetes. Kubernetes is underneath both OpenShift, well, it's underneath OpenShift. And Julim and Serena Doyle have been working on creating a single pane to manage both for all their operational needs. So I'm gonna turn over the rest of the presentation to Julim and Serena. They've asked that you hold questions until they ask for them. If you have a question while they're in the middle of talking though, one or the other will be monitoring the chat session. So go ahead and put your questions in there and take it away. So thank you, Steve. And good day to everybody and thank you for joining us in our operational dashboard for OpenShift V3 and Kubernetes briefing. And my name is Julim and I have here with me Serena Doyle and we're part of the Red Hat user experience design team. And thank you for joining us today. So without further ado, I'll jump right in. What we're going to talk about today is give you a quick overview about some of the underlying technologies and some of the ways we're approaching how we're going to actually monitor or operationalize the management of OpenShift V3 and Kubernetes. And as Steve mentioned, if you have questions, we will be pausing throughout the presentation and feel free to also use chat during that time. So just in case folks aren't aware, OpenShift V3 is an on-premise version of Red Hat's pass and it's built on top of Red Hat Enterprise Linux. And it's built around the central idea of being able to run applications built in Docker containers and being able to run them on top of OpenShift. And the notion behind this is we'll use Kubernetes which is a technology that Google opensource in order to schedule and orchestrate the containers. And one of the things that folks are using this technology for is to improve their DevOps or development in the enterprise or in any kind of on-premise or public cloud environment. If you're interested in getting started with OpenShift, please take a look at that URL and take a look at it. I'm gonna jump briefly and then dive in. So Kubernetes is an open-source orchestration system for Docker containers in a clustered environment. As mentioned, it's going to handle the scheduling of the nodes within the cluster and actively manage the containers and other entities in order to make sure that the cluster matches what the user's intended. And again, there's a link there if you'd like more information about it. And where we're gonna spend a lot of our time today is around a technology called ManageIQ. Now ManageIQ is the upstream project that Red Hat has around providing best of breed management across multiple environments, whether it's virtualization cloud or a containerized environment. For OpenShift V3, there are two consoles. For the operator or the administrator, we are providing the operations console for actually managing your OpenShift V3 and Kubernetes workloads from ManageIQ and from a downstream or from a Red Hat perspective, the Red Hat branded version of ManageIQ is cloud formed. So if you look at that picture that you see on the left, I mean, sorry, on the right, it basically shows that whether you're in a bare metal environment, a virtualized environment or a cloud environment and the cloud could be with an open stack, it could even be AWS or Google or any of the other clouds that are supported that run containerized workloads, you should be able to use ManageIQ or cloud forms to manage these workloads. Let me jump ahead. So some of the different concepts with regards to OpenShift and Kubernetes to keep in mind is that in a containerized environment that's clustered, you have a whole bunch of different entities. These include containers, images, namespaces or projects, the nodes or the machines that are actually running the pods and containers and pods are basically groups of containers. Some of these concepts that you see on the screen are basically some of the different components that will be managing from a ManageIQ or a cloud forms perspective. And I'll become a little bit more evident as we share with you some of our proof of concept that we're about to share with you. So as mentioned, what we're planning to share with you are some design concepts. We have a running prototype that Serena is going to show you and what we'd like to invite from you is any kind of feedback or thoughts that you have on what we're about to share with you today. And just... Let me ask a minute of questions. Thank you. I'm going to pause and see if anyone has any questions. Thanks. Any questions? Sorry, I'm not able to see. Nope, not yet, so just noting, yeah. If anybody wants to ask questions, feel free to put them in the chat. Otherwise, we're going to continue on and switch off, I'm going to start sharing. Yeah, so before you go there, let me just briefly talk about some of the use cases we're going to show. As I mentioned earlier, we have the ability with ManageIQ to manage the whole OpenShift V3 and Kubernetes environment. Now, from a management perspective, this is the full lifecycle of your application containers, everything from being able to deploy all the way to troubleshooting it and retiring it. Today, we are going to focus on the monitoring set of use cases. And what I mean by that, we're not going to be doing any kind of active management of provisioning or deployments, but rather we're going to focus on taking a look at the health, the status of the OpenShift V3 and Kubernetes entities, the health of the cluster, the state of it, the relationships of it, how a container connects to a pod, to a node, to the underlying infrastructure, utilization type information, and being able to identify issues in the environment. And now I'm going to actually turn it over to Serena to share with you our prototype. Okay. Great. Want to start sharing? Oh, sorry. Yep. Yes. And once again, if you have any questions, please feel free to use the chat. Okay. So I'm just going to start this off with, and et cetera is not appropriate, or is not in working mode right now or how it will be released. Essentially what we have is this is a prototype of what ManageIQ's navigation scheme is currently, when containers would be dropped into it. And the operational dashboards that I'm showing you are essentially what we have designed for the first deliverable of cloud forms, first deliverable of containers in cloud forms. And as you mentioned, we're trying to get feedback and validation with customers and then in the coming months to see if we can enhance it. We are limited by what's currently supported by Kubernetes at this point though. So there are a lot of things that I think you mentioned in the use cases, which we will be doing at further date, but some of those things were limited to and can't provide those right now. So just to give you a quick overview of the global dashboard, this is looking at your entire environment. So any of the container-related objects in your environment. So the top piece up, I'm going to show with my mouse, you can see my mouse going in here. You're not sharing it. I'm not sharing? No. It seems to me that I'm sharing. I can see your mouse moving. Can you see the dashboard as well? Yeah. Okay, great, thank you. So the top, there's about two, there's nine cards on the top, the top strip, I would call them. And essentially what they are, they're cards just trying to give you a quick overview of the container-related objects in your environment. So the first card on your left says that there's three providers currently in your environment. We have one that's an open shift and two Kubernetes providers. All of these things will be able, you can drill down into each of these items. So if you're not in the prototype but in the product, you'll be able to. So you'd be able to drill down into your single provider that's over open shift or you can drill down into your two Kubernetes providers. The next two cards are nodes and pods. So there's 52 nodes in this environment and three of which three with the error icon next to it. Means there's three nodes that have issues. You would be able to drill down into those and see the three specific nodes with issues as well in the product. Anything we have with pods, at this point we only have nodes and pods which are able to report back that they have errors or some status. So the rest of the six cards which are containers, services, registries, images, projects and routes, all we're able to do at this point for the first release is just say how many of those object types exist in your environment. So I'm going to pause for a moment and Dean Richardson had a question asking if this is CloudForms functionality anticipated for 3.1 or later release and our understanding that it's currently being planned for the 4.0 release at the end of this year is the current plan. Thank you. Okay, so I'm going to traverse to the lower, the middle, the middle left. One second for that question, hold on. Julian, I think he's actually is, Dean, can you please clarify? Do you mean 3.1 of OpenShift or do you mean 3.1 of CloudForms? Oh, sorry. Because we have a 3, OpenShift 3.1. It is, yes, I'm sorry. It is planned for the OpenShift 3.1 release because OpenShift 3.1 comes out around the same time as the CloudForms 4.0. It will come out before it. But the dashboards will be in managed. But that is correct. The functionality that you're seeing right now is going to be within CloudForms and not within OpenShift. Right, and that will all be part of Red Hat's cloud application suite as well. So you can get OpenShift and CloudForms separately, but you can also get Red Hat application suite, cloud application suite, sorry. And that will include, that will bundle together a whole bunch of stuff, but part of that will also be CloudForms and OpenShift. That's correct, yeah. Thank you. Okay, so on the middle part of the page on the left-hand side is node utilization. So we have two utilization charts, the first one's CPU.  And then what the donut chart is depicting, the amount of used CPU. So what we're doing here is, we're showing the used inside the donut chart. We're coloring the chart based on two different thresholds. So the chart should be colored blue until you hit your warning threshold, which at this point we have 75%. And when it hits 75%, it's gonna turn orange, but then once it hits 90%, like in this case, it's 92, it turns red, just so that the user can visually quickly identify threshold usage or where you've met your thresholds. On the bottom of this card is essentially the Sparkline. So the last 30 days, what your CPU utilization has done for your nodes throughout the last 30 days. Then we have the same thing on the right-hand side, but it's from memory. So it's the same exact concept. The amount of available is up on the upper left. The amount used in the percentage is shown within the donut chart. And then underneath is the last 30 days with a Sparkline of usage. So we just want to pause and ask for any questions. And I know on the chat there were some questions that came up. One of the questions that came up is, will OpenShift have its own management console as well? Perhaps a stripped-down version of this. And in, with regards to that, OpenShift will have its own management console and it's targeted more towards a developer, whereas managed IQ or CloudForms is more targeted towards the operations person or administrator. Now, the second question was asked, by E&P, will you be providing support for installing OpenShift via CloudForms, i.e. within the Services tab? And the plan is yes. As of right now, CloudForms does support installing OpenShift v2. However, for v3, it is being planned, but I don't know the exact timelines yet. They're also talking about integrating OpenShift and deployment through RHCI install. That is correct, yeah. And let's see if I'm missing something else. Okay. Were there any other questions with regards to the prototype that you're seeing with some of the dashboards that Serena showed? I have a question. The node and memory utilization, that's showing utilization for both the entire environment, whether it's an OpenShift or Kubernetes provider like environment, correct? And this screen, yes, it is. But we're gonna show it. We will show you a provider-specific screen as well. Where it would be filtered. I'm gonna close. Okay. So I'm gonna quickly go and keep monitoring. There's actually one more question. This screen shows all the nodes. The nodes may be configured based on labels such as region zones and maybe more. Because can this UI drill down and categorize based on those labels? What were the labels again? So these are related to services. Not at this point. It is definitely in the works and plans. Okay, yeah, so remember that what we're looking at right now is just, it's all of your entire container environment, right? So I'm gonna quickly show again, the bottom is utilization per node. So this is showing CPU utilization. What we do here is we have one block to represent each node. The way that it's sorted at this point is the nodes with the highest CPU utilization is on the upper left and colored red. And then as you go down to the bottom right, you see the ones that have the most available. What we will also be able to do is you can hover over and see which you'd be able to see the node names. You can also drill down. So if you wanted to look at the ones with the most problems or highest utilization, you'd be able to drill down and see details of those specific nodes themselves. So again, at this point, we have this information available for CPU and memory. In future releases, once Kubernetes provides support, we'll also be including network and storage information in the same manner. Just to pause one more time. Thank you, Scott, for your kind comments. Nentioned he liked the dashboard. It looks, the look and feel is nice, easy to see, important top level information. Vera, Michonde had a question. Can we add capacity in new nodes based on threshold set for utilization? For example, CPU utilization raises 75% spin up node time. So with regards to that, and it sounds like it's being able to scale out or scale up type question, the plan is to have that capability within CloudForms and I believe also within OpenShift. And from being able to visualize the threshold, we don't currently have that, but it's something we have planned for later. And also to be able to set the threshold to your desired values. Well, that's the scaleability part and the policies. From Nicholas Schultz, will developers or users of OpenShift be able to gather stats from inside their Docker containers? Will they be able to monitor specific container performance? OpenShift better. From OpenShift, I'm not certain. Steve, would you know? Yeah, that is definitely on the dashboard. I mean dashboard. It's definitely on the timeline for something that we know developers need access to see what is happening inside of their containers. So yeah, the developer dashboard over time will have some of those metrics for your projects and stuff happening inside of your projects. Right, thank you. And Dean Richardson asked, will this demo environment be available for essays in the field? If not, can demo flows via screenshots be made available? Yes. Screenshots, yes. The demo environment, not yet. And so are we gonna share the presentation then? This is being recorded. Oh right, so they're- So you- Well in the deck, also in the deck that we've created, I've put these screenshots into that deck. Yeah, we can make the deck available as well. And we can put that in, we'll ask Diane where to put it. And then Jeff Hoffman has a question. When you scale down, will containers reorganize themselves across the environment or is this still a manual effort? That's a great question. I'm not really sure. I suspect it's a manual effort at this point. But Steve, would you know the answer to that question? Yeah, I don't know the specific answer to that question, but my guess would be that that's more of a Kubernetes functionality since it's in charge of scheduling, right? So it's gonna schedule what containers end up where. I don't know specifically though. Okay. And there's another question. Actually, I think Kevin Connor made a comment that there's work going on to integrate Hocular for retrieving metrics. Some of that is supposed to be present for OpenShift Enterprise 3.1. And that's with regards to being able to set thresholds in order to scale up. Let me see. There's another question from Veer. Can we use manage IQ to move the pods across nodes? Pods across nodes. That's a good question. I'm not sure just yet. I think that might be something that we can try to add to an ask product management to see that's something planned in the roadmap. And Kevin goes, not autoscaling that is currently being discussed with Google. The intention is to include this for autoscaling but likely OpenShift Enterprise 3.2. Thank you. All right, and then we move on. Okay, so I'm gonna go to the right half of the screen where we have four cards that are showing trends. The first one is network utilization and it's going to be a live chart. So what's gonna happen in the last 15 minutes? So you should be able to see this moving when you have your dashboard open. The next one is network utilization but over the last 30 days. So this chart will be actually very similar to what we have for memory and CPU. The reason we don't have a donut chart showing your percentage available or percentage used is because right now we don't know how much is available through Kubernetes. And the bottom two items are the total number of pods and the total number of images and their trends throughout the last 30 days. So you'll be able to see that again, it's just the total number, not the amount new or anything like that. It's the total number that are existing on each one of those days. So what I'm gonna go to next is the single provider. So for OpenShift, right? If you had a single OpenShift provider, the default view will be a dashboard or an overview. And it's essentially just the same thing as that global dashboard was, but it's filtered for this specific OpenShift provider. So again, we go through all the blocks but I already explained them all. I'm gonna go, is there a question? Yes, there is. From Veer Machandi, the question is, can we drill down to the individual quad levels to see what containers of pod is running? Would we be able to look at JVM metrics running inside a container? For example, there are assumptions that such features would be part of, would all be part of the CloudForms console. Okay, so one of the things that we don't have access to in this demo today is there's a whole set of inventory views. So if you look up in this prototype, if you look up to the top, container providers, projects, nodes, pods, roots, replicators, images, registries, services, and containers, all of those things have, we have inventory views for each of those. And yes, we'd be able to drill down from those directly from these areas. The caveat for us right now is that our dashboard prototype is in a different code location than where our inventory views are being developed. So we don't have the ability to go from one to the other in this specific concept. So just to expand on what Serena mentioned in these inventory views, they were shown at the Red Hat Summit recently. I don't know if it was recorded or not. Do you know? We can find out. It was in a mark. Yeah, I don't know. I'm not sure if there is, but one of the things we can do is have a follow-up discussion or presentation in this briefings to show those set of views to you. Now with regards to being able to look at JVM metrics running inside the container, I know the plan is to be able to do that. And I know from a Hocular perspective or a Fabric 8 perspective, they actually do have a working prototype that does that. I'm just not sure on the timelines on how some of these land inside OpenShift. Any other questions? Okay, so I'm just showing you the alternate where if it's a Kubernetes provider, you can see the same thing. At some point in the future, we will likely tailor the contents of these views to be a little bit different for the Kubernetes provider versus the OpenShift provider. But at this point today, we don't have those differences at this point. The final one I'm going to show you is the providers, I'm sorry, the project dashboard. So once you're looking at a single project, this is again what you'd be seeing from an overview perspective. Very similar layout, right? We have these cards again up on the top left, which are container-related objects. So you have an idea of how many of them are associated with the project that you're looking at in context. And then we have the same thing, node utilization. So this is CPU and memory utilization of the nodes that are associated with the project that you're looking at, as well as the heat maps again, utilization per node used by this project. We also have something a little bit different on the top right, which is quotas. And this piece up here might be reworked a little bit. We might have some additional items or take some off as well. But again, this is what we have currently. And then the bottom four cards are exactly the same trend cards that we had on the global dashboards. But again, they're filtered in context to the project that you're looking at. So are there any questions on the dashboard? Or comments? Or comments? Do folks have any thoughts around what they've seen or would like to see added? Are you grabbing those quotas from OpenShift directly or because you can also do quota management inside CloudForms today based on the, some wondering if there's a tie-in for that. So the next question, Lucy, with regards to the quotas, the quotas are actually the Kubernetes and OpenShift quotas, and they are not the quotas from CloudForms. Ian, P asks, do we have table views as well as graphs? Yes, and those are in those inventory views. So actually, if that's something that's of interest to this audience, we could ask Diane if she wanted us to come back and do another presentation and show you all the information that's available in the inventory views. But like I said, we don't have access to those at this moment. And we have another comment from Veer Machandi. Mountain persistent volumes to nodes could be a feature that can be added and monitoring usage of persistent volumes by OpenShift pods. I believe Serena mentioned the plan is longer term to have storage and networking be more a part of what you've seen in the dashboards today. Currently, we don't have that capability or visibility, but the plan is to actually include them. Any other comments or questions? Yeah, I had another question. One of the things you can do in CloudForms is customize the dashboard based on any data that CloudForms can collect. Is that something that is, I assume that's not available now, but is that in the plan? In the future, yes, that's a desire. The question is where, you know, what priority will that hold? Just to note that these dashboards are different than the containers, I'm sorry, than the CloudForms dashboard where the CloudForms dashboards are actually running on reports, right? This is a little bit different. These are completely fixed and there are no, at this point, there are no reports associated with each of the individual parts that are shown on the dashboard. And one of the things that we probably should mention is we're using slightly different technologies from the native CloudForms to actually generate this dashboard. So today, as Serena mentioned, they're not customizable, but in the future, they likely will be. Sorry, I'm just going back to the presentations. Do you see things moving around? So the last thing I wanted to show, if there was no more questions is there, and this isn't just a screenshot. Again, if we came back and wanted to show the inventory views, maybe we could get a live view of this prototype as well. So this is essentially a topology view, and it's just showing all of the container-related objects in a graph. At this point, for the first release, there's no plan to, well, we don't think that we'll be able to have highlighting, et cetera, of issues or errors or things being up or down, but that's something that we are talking about enhancing in the future. When pods or containers are created or instantiated, you see them automatically appear here, the way that they've implemented it at this time is they kind of jiggle around a little bit so your eye is brought to it and you can see it. This same topology view is going to be, or a very similar version, is going to be also included in satellite. Yeah, in cockpit. In cockpit. Sorry about that. So I don't know if anybody has any comments on this type of view as well. It seems like there's, people have strong stances for and against, so if anybody has any feedback, we'd love to hear on that as well. So while we wait for a few more questions, there are some questions from Judd at Dell, and the question is, can code push events be correlated with performance data? The answer to that is absolutely. We are collecting event data, and that is going to be in CloudForms or managed IQ, and whatever performance data that can be collected can be correlated as of right now because we don't have that much data. We're not able to produce those set of reports or charts to show, but that's something that we do plan for longer term. Now from Veer Machandi, the question is, or comment was pruning resources on nodes is another feature that will be useful for administrators if it's made available via this console? And we absolutely agree with you, and I believe that's part of the active management piece of lifecycle management of a containerized environment. And today, we don't yet have those set of use cases addressed, but it's something being planned. With regard to container update events, those are definitely related to code push events, and on the dashboard, do we have any? Not right now. Not right now. Sorry, I forget what we don't have. So that's something that we're planning for the future. And another comment from Veer is maybe coloring the node circles on the topology view based on usage labels, grouping related nodes by regions, zones, et cetera, will be useful. Yeah, so just so you know, yeah, we have been talking about how we design for usage because color, because of color blind issues, I'm not sure that we can just primarily count on the color itself, but we have definitely been talking about those concepts. Also how you filter by labels, et cetera, regions and zones. That's something that we've been talking about at this point, I don't wanna detract from what we've done here because I think it's great for a step, but at this point, all you can do is either toggle, you can toggle these types to be shown or not. So that's what this bar here is up here on the top left. If you don't wanna see your container groups, you can toggle it off, et cetera. So that filtering is pretty limited at this point, but it's definitely gonna be enhanced as we go along. Dominic, can you maximize that again, please? Oh, sure, I'm sorry. For folks who are looking at this presentation, how would you use this topology view? Do you have a need for such a view? In looking at this topology view, one of the things I think that would be nice is if you could show dynamic connections between services. Right, so I'm gonna see like, I can't quite, oh, so there's the node and it's got, there's this long graph coming out of the center of the middle left node. Where it's got a lot of stuff coming out of it. Do you see that one? Yeah, no, the one up. Up here, up here. No, oh, according to this graph, there's a node coming out of a node or they're connected through, they're on the same host? Is that what's happening? I don't get that graph. But anyway. I think it's a little confusing right now. Yeah, so this host has two VMs associated, right? Yeah. And then, so you're asking about this node here. Well, what I was actually talking about more, I thought that was actually one node and a long graph coming off of it with a lot of services. Okay. If services are talking to each other, it would be good as the admin to know what services are talking to which services and how much data is flowing between them. And some other dashboards I've used, these are more application developer dashboards. You can actually see like how much data is flowing from your app servers to your database, right?  It's just something I think the interaction between the nodes is, between the endpoints of the graph is important. Yes, we've heard that and that's something that we're definitely planning. Let me ask you this, would it be better to have the services or a specialized view that's more targeted between these service endpoints to actually see that information? Or would you still want to see it with all these other entities connected to it? I would imagine for sure you'd wanna see it on a node, but on a node basis as well though, right? Because it's not just which, I do wanna see which services talking to which service, but as an admin, I would imagine I would also wanna see, are these co-located on the same node? Are they in the same district? Like I would wanna know more of how that, I don't know that I need all the graphs, it's kinda hard, let's see containers. I think I'd probably wanna, I think I'd kinda wanna see all of that stuff. Maybe they've become smaller or something, but you'd still wanna be able to know, are they happening on the same machines or what's the relationship between quote unquote machines? But I'll leave that to other people to say it. Some of the other things we're talking about is being able to put something in, like more in context. So you wanna see your environment based on a specific node or on a specific, hierarchy potentially. And so it would kind of fade everything out, but it'd bring up any of the relationships associated with that one object in the front. So that's another thing that the future we're talking about in Florentine. And just to pause for one moment, Bob, because Demba had a question, can the topology view be cropped and zoomed? Not at this point. That is the intention going forward. I mean, we would not promise that for the first release, say that. Right, I think one of the caveats we probably should mention is this topology view is sort of an early concept for it. And we're still in very early stages of it. We'd definitely love to get more input on it. And so if you have any additional comments, we'd love to hear them or things that we ought to be doing. Actually, for this specific view at ContainerCon next week, Alyssa bonus from Red Hat is going to be demoing this live. So I don't know if anybody is there. Hope you're going to see that. Right. And that's next week at ContainerCon in Seattle. Bob also mentioned this topology view will be useful for large environments. Vera asked, it is showing containers at the bottom level. Is that a pod? Oh, yeah. One of the things we should mention in the topology view is that where you see the word container groups, that's actually pods. And we have some terminology things that we still have to update. And somebody asked a question, combined topology with heat, if not already. We've heard that. And thank you for that comment. So that was the last slide that we had in our deck. Again, I'm not sure if there's any other comments. We'd be happy to answer them. Otherwise, I think we can pass it back on to Steve. One comment. When you have the type of container info, perhaps the container can indicate what is running there. That's right. So one of the things to mention in the live demo is that we actually do have some views where if you're clicking on the object, you can actually see details information about the object. So for example, if you're clicking on a container, you should be able to see information about the image and other information about the containers. And because we don't have the live working prototype, we're not able to show that to you, but I believe there is a cockpit recording that actually does show that. And if folks are interested in that recording, we're happy to send the link to you. I'm gonna type in our email address in the chat and please feel free to reach out to us if you'd like. And if you have any additional comments or questions. Okay, it looks like we're done. Give it one more second. Okay, thanks. Those dotted lines, I'm sorry. Those dotted lines, what were they for? Were they for just services only? In that topology view? I think in that topology view, some of them only had dotted lines, not solid lines. Sorry. No, I have to share. You have to share, because I don't think anyone can see. No, no, no, thank you. We're trying to get the image shared again. Yes, I believe those dotted lines basically means we've lost connection to it or something is unavailable. And that's the same thing of the ones that are not connected, I guess. They're either not connected or a friend or they've lost connection. There could be a number of different reasons. And would I, if I hover over like the containers and the nodes and services, would I be able to see the actual names of them or they like any more detailed info, like if I hover over them? Yeah, at this point, you see the name. What we're trying to do and I'm not sure how much will be done for this first release or not. There's also a design that when you select one, you'll see all of the associated information on the right. There'd be like a details panel that shows up, which shows you all the information associated with it. Isn't the cockpit already implemented? Okay, so if you look at some of the cockpit recordings and I believe those are already in the public space, you should be able to see that information. And this topology view is actually based on that implementation that was done in the cockpit. So some of these capabilities will be coming. Okay, thank you. Thank you. Any other questions, comments? And viewer, thank you. And thank you everybody for taking the time out of your busy schedule to take a look at what we had to share. Yep, thanks, Julianne and Serena. We'll be posting this, we will, I'll say we, I mean, Diane. Diane will be posting this up on YouTube. And again, thanks for showing us some of the exciting things coming for Kubernetes and OpenShift. Thank you very much. Thank you. Have a great day. Bye bye.


Meanwhile, gunmen have abducted Al-Hajlawa Yaqobo, the commissioner for information, culture and tourism, Nassarawah State. A source, who is a resident of Nassarawah Egon, confirmed to reporters that the commissioner was trailed to his house by the gunmen. It said the bandit took the victim to an unknown destination between 8.45 and 9.00 p.m. yesterday. Don't forget to hit the notification button so you get notified about fresh news updates.


The Newsroom Protect and Telecom Professionals and JSA radio, the Boys Protect and Telecom on iHeart radio. I'm Jamie Tumato-Cutayo. Welcome to the New Jersey Fiber Exchange and JFX Launch. Very exciting day here. And we are here at the VIPs of our industry, sitting down next to this amazing resource and with none other than the driving legend, Mr. Mario Andretti. The Chief Operating Officer of Tata Communications, Fiber Exchange. These are our video screens on each side. Those knowledgeable in the sport rank him among the greatest racing drivers of all time. People who never follow racing easily recognize his name. He is synonymous with auto racing and with driving fast. Excuse me, sir. Who do you think you are, Mario Andretti? From racetrack to Madison Avenue. Not in Indy cars. From the pits to Hollywood, Mario Andretti is part of American culture. He became a household name by winning races in the 1960s, winning many races. But creating a legend takes more than merely being victorious. The Andretti legend was created by how he won, and because he won in so many different types of cars. Other drivers have won more races in their particular specialties, but when one looks at total victories in all major forms of automobile racing, Mario Andretti stands alone. The Mario Andretti story is an American story. For seven years after the end of World War II, Mario and his family were forced to live in a refugee camp. They finally left their native Italy for America in 1955, when Mario was 15 years old and settled in Nazareth, Pennsylvania. The family had $125 in cash and didn't speak English. There happened to be a primitive dirt track in Nazareth, and very soon Mario and his twin brother Aldo were building and racing their own stock car. Mario was immediately successful, and after his apprenticeship on the dirt track ovals of the Northeast, he drove his first Indianapolis-type car in 1964. The next year he moved his career into high gear. He finished a strong third in his first Indy 500, scored his first major victory later in the season, and went on to win the year-long national championship for Indy-style cars. A year later, Mario was in victory circle eight times and easily won his second national championship. In the next two years, Andretti went from being known in American racing circles as an excellent Indy car driver to being known internationally as an exceptional Indy car, stock car, sports car, and Formula One car driver. In 1967, he entered the Daytona 500 and shocked the stock car racing establishment by stealing their most prestigious race. A month and a half later, he co-dropped to victory in the 12 Hours of Sebring Sports Car Race, one of the most important road races in the world. Then at the end of 1968, another chapter opened for Mario. He entered the United States Grand Prix, and although it was the first time he'd ever raced a Formula One Grand Prix car, and the first time he had ever seen the Watkins Glen Road Circuit, he qualified on pole position. It was a staggering achievement. In 1969, he won the Indy 500, and he won it in style. A practice crash had destroyed his car and could easily have killed him. Undaunted, he drove a year-old backup car to victory. Then two years later, he won his first Formula One Grand Prix race. He'd been racing at the top levels of the sport for only seven years, and yet he had now won in every type of car. And whenever Mario Andretti stepped into a car, he meant to win. He drove flat out, and his love and passion for driving was evident for all to see. Andretti was known for his style as much as his success. Then in 1978, he capped his career with the most prestigious championship in racing. After winning six Formula One Grand Prix races, Mario had become the world driving champion, only the second American to do so. His passion for the sport still burned, and he kept on winning. In 1984, at 44 years of age, and driving against competitors 15 and 20 years he's junior, he won his fourth champ car title. And yet he continued, and continued to win. His last race victory came in 1993 at an almost impossible to believe 53 years of age. It wasn't until the next year, when he was 54, that Mario Andretti decided it was time to give up racing full-time. Assessing his legacy is easy. He drove the careers of three men.  And he won in every type of race car, and on every kind of race track. That was the legend of Mario Andretti. You've clearly driven from engine cars and sprint cars. What was your favorite car to drive, and your most memorable career highlight?  Thank you. That's a very good question, and it's a complex question, because I was so fortunate to be there for a long time. I've done a lot of boards in my career. So it's hard to find the favorite car to drive. But when it comes to the sport, the sport that obviously was my profession in motor racing, I can tell you that every car I want to race with fell in love with. That particular day was my favorite car. So when I look back, and look at my victory, that's really how it comes to my heart. Second part of your question is career highlights. I must tell you, here again, I was very fortunate. But there's always something that's very special, and I was born and raised in it. And the background that the family did not include motor racing or anything, any such thing. But as a young man, I fell in love with the sport. And in 1954, 14 years of age, when I saw the biggest race at that time, which was the Italian round three, the Monza. And that's when the ball was cast. That's when I said, God, if you could ever restore something on me, you could be a racing car driver. And that's where I reached the World Championship in 1978. Obviously, it's, you know, you talk about living the dream. That was it. So you can see it, I think, blessed and very fortunate. And so when you were 14, that was the moment when you first considered that this racing, racing is your career path, it's your dream. When did you know you would really sell out the sport? Well, first of all, yeah, starting an age 14, I felt that I never had a plan B. So obviously, that's what I worked toward. You know, trying to get involved in the sport. It started somehow. And then I did. Age 19 is 1959, is when I started my first season in the sport. And it was a very special beginning with my two brother, Aldo. We had one race car, two race drivers, and we were winning the races. And it started about two or four years later. When we started, I moved out on the ramps and started racing, competing against, you know, some of the best in the business. That's when I felt, you know, I think this may work for me after all, because you have to be realistic. And you have to measure up to the competition that has been there, you know, the high pounds at the moment. And that's when, that's what gives you hope, that's what gives you motivation. And that's what, you know, I have a youngster in any field of sports or competitive field. We always imagine yourself in this competition. But when you feel that, oh, I'm winning here and there. And the encouragement is, I think I can do this. I think I can make a living in this. And what did you do? Today, you're the only one of two drivers to win races in Formula One, IndyCar, World Sports Car Championship, and NASCAR. You won the 1978 Formula One World Championship, still the only American to do so. Four IndyCar titles and many, many more. We're talking over 109 career wins on major circuits. Oh, I think it's a lot of pride. And I mean, ultimately, you know, a lot of time and effort in what you're doing, passion, your work. So what's the reward? You know, the ultimate reward is to be able to excel at any given day, being the guy, the person who kind of does the best. And the thing is that, that sort of, I would say that excitement is what drives you to repeat it again. Once you experience being at the top, you want to keep it there. You know, and that's your motivation, because nothing else comes close to it. So, again, that's, and I think just the love and passion for my work was no problem for me to stay motivated. And I look forward to going to work. And I look around for my friends. And many of my friends look forward to going to work. And unfortunately, not everybody does, but the ones who do probably do very well at their job. And these words are so true for our industry. We're surrounded by a lot of hard workers here who really enjoy what they do for sure. So they're speaking to our hearts. With your IndyCar win in April 1993, you became the first driver to win IndyCar races across four different decades. And the first took in all the wheel races of any kind in five decades. What's your advice for Korean longevity? And in particular, maintaining your legendary brand throughout the years? Well, here again, you know, a lot of the passion and the promise to come from within. My advice is if you act, especially in your own life, you know, just pursue it no matter what. And you'll be surprised. I mean, the odds of mine really becoming the race driver of what I'm still claiming about as a teenager was so, I mean, almost impossible. But I mean, I even had an issue with the problem of my own father, which did not understand the sport.  So I didn't have his blessing. In fact, the first season, 1959, my brother now, our night, had to race without knowledge.  So as far as the price is, if you really believe in yourself, believe in something, you know, just don't be discouraged. There's always going to be, you know, some issues and runs on the road and all that sort of thing. But ultimately, if you believe in runs and achievement, you will. Believe in just the way it is. And there's no written formula to take you there except just your own desire. How come so many people talk about your talk? It's an industry thing. So, um, even though you're talking now post career, we have our viewers now, Valley of Celebrity Apprentice, a few seasons back. Giving Donald Trump points of pride through New York City. You guys have to check this video out on YouTube if you haven't seen it. What was it like to meet the now Republican presidential candidate? And is he the same man off camera as he was on? Yeah. Now, that's another question. Obviously, what we were filming this week is the best event of the season. It was fun. It was fun because, you know, I took him around to see the race car. And he was so worried about his hair. And I assured him that I would mess it up. You know, so I tried to film it very fast. You know, to keep that intact. And so we were looking at, you know, all of it. And I thought that after the primary season, it was such a good ride. He would nominate me as the VP. You know, but out in here, the name works for me. And I'm kind of glad in a sense. But here we are. Yeah, I mean, I don't know what to say. People have been in interesting situations to watch. You know, this road to me to the right house again. Sure, for sure. Well, this is a good thing. I would not fail that he was in the car if I would have messed up her hair or not. Well, talking speed and drivers and rides of our lives. Gil, you built this amazing building from the ground up. And it's true. And it's true in Drady's style. In record time, under one year, this building has brought it to the ground up. In time, time, cable ending season. Right at the door. So what was your long process with the idea of driving where you were at? Well, it's an interesting ride. You know, we started this process about two years ago. And it was John Hedek and I who started talking about this and now, of course, to what the partnership could look like in terms of building a tier three site at a cable landing station. And that's just building cable landing station campus. We talked about it for a good few, six runs and worked with Mark since he was here also, he was here to be aware. Everyone agreed to make sense of the building. And last October, he programmed. So today, September, he built this building a lot of months. At the work pointy, like any sport you have in the team behind you that supports you, and I've got Frank Perugia, who was a designer for the site, inspiration to us all, worked to help us out. Felix Seda, who helped him as well. Greg Gretel, where the Seda's family and us worked with his title behind. But the issue behind this building was a combination of me and Linderia. I sold Linderia in 2008, and I retired. I retired, I played golf, I worked with my family, I traveled. But it was a void of marketplace. They wanted to do something else. We always wanted to have something to go back to, and this building for me represents a legacy. We thought that we were going to have a lot of family for whatever. And something that goes back to our industry that allows people to move things they can't do before this building was built. And Mary, for your benefit, we're sitting in a facility where people travel across the ocean. Our community is open to people when they're stationed and stored, and people's live in the UK. We've got a cable company here from Brazil. This is the first and last stop, the fastest way to get done in Brazil happens in here. And we're here in a room full of friends, and all are really in the same way. And like you and Gracie, we all work together. We cooperate, we compete, but at the end of the day, we have food, drink, we celebrate, and we chat through these conferences. Deals are getting done. So what are the interconnection possibilities here? So as I said before, being in a cable-landed station is really the most robust part of the network that exists. You connect to back-hop providers like Altea, Stale, Water Tower, Wing Street. We all have products that's here. And they can bring you directly if you want to go anywhere else. So the simplest forms. Traditionally, New York City was a point of failure in how we could meet with other countries. We've not been in New York City but putting this building here, and having a place in these networks to now directly go and connect financial centers, connect immediate centers in Aspera. It's the most important location it's in our facility to do all that you've got. Location, location, location. Is that what they say? Particularly to real estate. Also, speed of networks. This is when it becomes critical. So tell us, Gail, what makes this location critical to subsequent activity and speed? Well, again, adding a part of electronic communications in the facility built in Aspera allows us to rapidly keep their deals. So truly a connection point to other big banks to a lot of these products as well. You know, we don't want to sell this building ever to one tenant. We're not in the sense of a big deal that we lose the whole way. And I wanted to also say to the college we have the mayor of Wall here to read coffee back there. I wanted to make sure everyone realized it was here. I want to thank Wall Township for their support in letting us build this building in the right way for the case. Lots of great folks in this room is wanting to make sure I got it. And the job for Tata Communications. As we know, Tata is a brand known for fastest and secure global communications. And as noted by Gail, your cable literally comes ashore just steps away. Which makes this location on the Jersey Shore critical for speed. And with the NJFX's added marketplace, businesses and networks can come in and connect to a global fiber network and quickly be taken anywhere around the world. So John, tell us more about your network, reach and your speed. Sure. Tata Communications has two cables to learn next door, right? Your cable service provider has a whole year to bring around the world. Literally on Tata's cables we can start here in Wall Township in Jersey send us out of light and have it come here and hit the Go Through Japan hit our US West Coast sites and end up back here if we wanted to do so. One second. It's great to have this tier 3 facility right next to the cable management station because I did go forward. This is going to be more of the model you're going to see around. As networks grow in capillarity and reach is really important as enterprises move more applications, dating, storage into the town they really want to be able to reach data needs and having a tier 3 facility right next to that set of cognitive solutions is really a first to the market that I think is really going to see legs and it's really going to influence how things are built in the future as well. For sure. Absolutely. And how do you see the NJFX in the room and data center to tier 3 networks adding this extra layer of speed and capabilities? For you. A lot of what I've been talking about in NJFX is not just a pure data center building basically a platform where you can know that which cognitive solutions whether you're trying to reach something that has to be in the US for the four or five companies so I think having a rich quality data set getting a set of providers over here that offer many different applications needs and services and making this location more valuable for enterprises and consumers is really going to create that platform and that community that people are going to want to have space power and services out of here. And they're doing it in high school in the old school, right? No positive energies to be given? We are. So our model really is the original NJFX model. We don't charge very easy cross teams. Why? I love all the guys in this room. All the guys in here are trying to get deals done. I don't want to get in the middle of their deal chatting back and getting something done. When the bottom line is we as a real estate place should not be in communication business. What we want to do is support our customers. Sparkle, Tata, Level 3, and Winstree. When the deal gets done why surprise the company with very few? It's a surprise batch. So for particular business we should do some real estate playing all the time for space power and all the time. I have one last question and this will be for online panelists but if there's a question out there in the audience feel free to raise your hands and we'll come to hear from you guys. So my question again for you is for you to put all this launching you dream in in your own way made a career in getting from point A to point B with unbelievable speed and you're trusting brands as such. John, good to start with you. Looking at your professional growth over the years. Were there any hurdles along the way that you had to overcome and important lessons for that you can share with us? For any career that could be major this morning, whatever your recognition of success is you have no purpose. I think one of the ones that I will point out today in today's day and age that is a bit more of a requirement like is it continue to struggle with social media and always on non-attunity and as a business you're always presenting new opportunities to investigate potentially built it's a period of things coming out to you all the time. So to me it comes down to how you go about the discipline and the focus on what's truly important to achieve your definition of success you can take that potential for that perseverance to only focus on those and let a lot of that noise and distractions go away. True, true. Larry, there must have been a time during your staggering career that was particularly challenging for instance in 1979 with the new Lotus 8 car was particularly competitive or the 1982 Controversy Prep with Kevin Hogan tell us a little bit about how you overcame your challenge. Well, as you can imagine when you're living in a highly competitive world you're going to have some glitches here and there. As a matter of fact if it was easy obviously it wouldn't be important but the thing is when you get knocked down it's how you get up and brush yourself off and go on and win again it's all about believing in yourself and knowing that it's not going to be better roses per se always but after the hard war the rewards are there that's what keeps you motivated driving on again it's if you're fortunate enough to be there for the wrong tool in our business there could be many interruptions if you're unlucky and you're injured for a long period of time where it was something that was very prominent in all the leg days that I've raised in and I'm just counting my blessings for the fact that I've done a lot of bullets I was able to continue on out of the 19 races in my life I've spent 40 years holding these two races because of injury and that's because I was really in many ways very very lucky and I know that and I'm forever thankful but again as John said there are different ways of measuring success in our business to measure success to some degree there are many trophies you have but it's also with the relationships that you build that last a lifetime because of opportunities to meet people individuals and appreciate cultures around the world it just blows your convention to incredible images so all these things are part of what I feel you can consider success and I think I've been blessed with pretty much all of them I'm still living the dream today you have a question who is the toughest person you ever raced against who is the toughest person you ever raced against there's another question who is the toughest person I ever raced against there weren't too many drivers my career was two weeks it would have been easy but every decade or whatever even has just that new you know like drawn on your side always in almost every decade a certain standard in a certain discipline and again I've had many and I usually this mentioning because I'm always thinking that I'm going to forget come on but the juggist tour it's easier for it but I actually know Michael is a pain in the ass because he was so good so again I look back and I've raced against some of the icons of our sport in the last two years and that's the question with every possible way what question have you seen the film Rush which is the formula one scene of the late 70's and just the exciting time rivalry between Jameson you're in the mix with that what was your take on that what was your take Mario on the film Rush now I'm going to be a silk credit you're going to hear because as you can imagine the film Rush was portrayed in real life of two individuals that were absolute stars at the moment but typical Hollywood sort of going their own ways describing certain situations and it did not really illustrate the facts exactly as you were and some of the critical facts about the New Berkeley when Robert was born about the supposedly the meeting and supposedly I'd taken place among the drivers not to start the race because of the conditions that never happened I was there were a lot of things that were not exactly true to the story runs the casting was a phenomenon about the two characters the rest of the casting was terrible some of the proper language that was used by one particular team owner and manager was never existing that meant it's very polished and very proactive very eloquent and so the movie Rush is now one of my favorites but it did not really I think it was a good story Hollywood's file but as far as even sort of showing what the original one is about it was not really represented in a lot of steps and that's why I didn't get any nominations and it went to never never that's my side of and our last question your turn as we can all see this point in the casting facility so Gil, were there any points throughout this year of building where you had to puster up strength and persevere anyway that's a great question because there were many moments where we were worried about what was going to happen but across the line April 8th, April 9th when we were still paving the road out in front we still had painters sitting here we had a hundred men working in the building of attrition we had HAC units and we said to ourselves when is the date for this party? September 21st months ago and when we did get it committed to all of you we would have Larry went right here thank you again for being with us I promised our partners Tata who came in from the UK to support the event and we had a party that we'd come to we promised our friends we'd play golf in the morning and we had a lot signed up Jim Ortini, Love Corbin all came in put down their suits put on our hats, grabbed paint blushes and we started working my team stopped didn't stop working 12, 14 hours a day for the last three weeks and even three days ago we looked at each other and said are we going to make a mistake and here we are thank you all for being part of this full day for us this was not easy but well worth it we're glad to share this with you thank you each one of you thank you gentlemen thank you for joining us JSA TV at JSA


So, there was this very interesting philosopher called John Rawls, and John Rawls had a nice interesting definition for what a just society is. And he said, if there was a society that you knew everything about it, and you would be willing to enter it in a random place, that's the definition of a just society. And he called it the veil of ignorance. So, for example, think about income inequality. In economics, we have this thing called the genicoefficient. You have the wealthiest, the less wealthy, the less wealthy, and the poor. The question is, how much wealth does each of those part of the populations have? And in countries where the distribution is very skewed, it's a very high genicoefficient, where it's more equal, it's a lower genicoefficient. Now, if you're very rich, you might want a distribution that is very skewed. If you're poor, you might not want such a skewed distribution. Now, if you don't know under the veil of ignorance, what do you want, right? Now you have to consider all the possibilities, and that's what's so beautiful about the veil of ignorance. So, recently we did a study with about 7,000 Americans, randomly sampled across the country, and we asked them, what society would be such that you would be willing to enter it in a random place? We didn't tell them about roles, but we defined that. And what's interesting is that the US genicoefficient is very high. The income inequality is very high. The wealthiest 20%, on 84% of the wealth in the US. And what's more disturbing is that the bottom 40% own 0.3% of the wealth. So the wealthy are very wealthy, but the poor are incredibly, they basically have nothing. So we asked people, please build, we gave them some web tools, and we said, please build a distribution that you would be interested in willing to live on. So the genicoefficient, let's say, is like this. People don't understand it. They think it's like this. But when we asked them to build a wealth distribution, and they would be happy to live in that country, it's even more equal. So it's kind of interesting that Americans are actually much more equitable under the veil of ignorance than we think they are. But the most interesting thing was that the differences between Republicans and Democrats were very small. So for example, in one of the questions, we showed people a distribution of wealth. And one of them was based on a better and more equal distribution in Sweden. And one of them was based on the US. And we say, where would you rather live? 92% of Americans preferred the improved Swedish distribution. For Democrats, it was 93%. For a Republican, it was 90.5%. So what it means is there's a difference between Republican and Democrat, but it's tiny compared to the real difference between the inequality in the US and what people think it is, and what they want it to be. So on one hand, this is a very depressing result because it says Americans don't understand the country that we're in, and they really want another country. On the positive side, it means that Americans actually deep down inside want a distribution that is more equitable. And perhaps what's happening is that politicians and politics is just using labels that are obscuring reality. The moment people are talking about death tax and inheritance tax and death panels and all of those things, people have this impression and normally think about their values. But perhaps if we could change the discourse to be more about fundamental values, they would be better. I'll give you one last analogy for this. In psychology, we often do blind tastes. Imagine you have two beers, if you have the label of the beer and the price of the beer, your understanding of the beer would be different. The label would change your impression of it. But what the role's story does is to strip away all of those beliefs. You just really have to confront your deep down belief. And I think that if we could do that in the political process, if we could get people to confront their deep beliefs about what's fair and just and so on, and only later tell them, hey, you prefer Sweden. What does it tell you about your politics? Maybe people would make better political decisions as well.