Hey everybody, welcome back to another exciting episode, another edition of A Week in Geekdom here on YouTube, Geo here, and today we're going to be talking about Aki's Olympus Manga. This was published by Yen Press a couple years back, and it is a single story about this retelling of Ganymede. If you don't know your Greek mythology, you should know that Ganymede, one of the princesses of Troy, is said to be one of the most beautiful men in existence. In mythological tales, he gets captured, I guess, or abducted by Seuss, because he fell in love with him, and he was the cupbearer, I guess, or something. It's been a while. But the reason I have this book is pretty interesting, because normally I don't buy into blind purchases when it comes to manga, but for this I was, or I still am, part of a group on Facebook that deals with manga, anime, and otaku culture, I guess, and somebody I cannot remember for the life of me, who was talking about Olympus, but they were going on and on about how this is an amazing book, it's gorgeous, the art, it's fantastic, yada yada, and my brain went like, oh, a good manga, okay, I bought it, and then I got it, and it's a fantastic looking book, but I never got around to reading it, and it just sat on my library for a very long time, I think like two years and a half, something crazy like that. So I finally decided to give it a go and read it, and share my thoughts with all of you. So what this basically is, you have Aki doing a fantastic reimagining of the tale of Ganymede and at the hands of Apollo. As you can see here, they are very elaborate, they have a very intricate character design, is what I'm trying to get at. Here's Apollo, and here we have our boy Ganymede right there. I didn't know what to make of it when I started reading it, I didn't know where the story was going, because I do know my Greek mythology and all that stuff, I loved that ever since I was a kid, so I didn't know where they were going with this. Fortunately, it's a really interesting tale of what happens when you re-imagine these characters in a more philosophical and dramatic purpose. You see Ganymede gets abducted. I believe there was sort of this parade, a victory parade in the city of Troy, and Apollo swoops in and kidnaps him, and it's not necessarily for what you think it is, and it's more about these Greek gods, these figures from mythology and how they muse over their existence of time, space, life, death, the true meaning of beauty, the true meaning of eternal life, and the nature of humans as a species, I guess, and planet Earth. There's a lot of themes and a lot of questioning from these characters. You do get to see Zeus, Poseidon, Hades, Artemis, characters like that, and they have very interesting conversations about the nature of things, and in the middle you have the character of Ganymede who doesn't really know what's happening and is trying to figure out why am I trapped in this ethereal miniature garden that Zeus made, how do I get out, and how do I reunite with my family? The book doesn't really go out of its way to answer all of these questions, instead it presents you a more philosophical view of these characters and their musings, like I just mentioned, but the main selling point that I think a lot of people will be interested in is the artwork. It is insane, super detailed and gorgeous to look at, and I loved it. Even though the story may not be for everyone, I know it wasn't exactly my top favorite thing I've read in a while, I did enjoy the art from beginning to end, the characters look gorgeous, and one of the things I really liked about this take is that, or one of the themes that get explored is machismo and Greek pathology, because if you know about these characters and their statues and all that stuff that exists in the real world, they're depicted very muscular with the poses and whatnot, but you don't get that here. We get very androgynous looking characters that are more, they're skinnier I guess, as you can see here with Apollo, who is said to be one of the most beautiful things ever I guess. One of the descriptions I liked about this character, or this version of this character is that they mention that his eyes are rainbow colored, so I kept thinking, and I kept telling my friends, I wonder if it's like the hollow cards for the Pokemon trading card game, where you move it and there's a whole bunch of colors in it, and it's your purples and reds and blues and all that stuff, so maybe it's like that, and I think, I don't know if the camera can pick it up, but I think Aki did a good job of kind of doing that with the way the cover looks, this hollow foil cover, I don't know, I dug it. You see that more here with Ganymede, but the art is extremely expressive and gorgeous to look at, like I mentioned, I really loved it, even though there are a lot of scenes where you don't really see a whole lot, empty backgrounds, keep in mind it's not supposed to be on earth, sort of an alternate plane of existence I guess, so I don't mind, but look at that character detail, it's impressive, the hair specifically, hair is a very tough thing to draw, and if you can pull it off, it looks fantastic, and really brings your character to life, I think, especially in manga where, you know, all these characters have really iconic hairstyles, so they have some of the backdrops that I keep mentioning, that's the garden, as you can see, there's no sky, it's sort of like a starry space with a huge endless field of white flowers, and I don't know, something about that stuff just struck a chord with me, sort of that, when you have like weird ethereal dreams of scenarios like that, where you're in places that are not like any place you might know on earth, it just has sort of a nostalgic feeling to it that really made me appreciate the story a little bit. One of the things I do like is that throughout the story, you get a lot of exposition with the character Apollo, and how he is, at first, he's kind of an asshole, I'm not gonna lie, I didn't like him, but as you keep reading the story, even he starts questioning some things, and when he's presented human characters aside from Ganymede, he's trying to decipher his true nature and the, or like the state of beings, and you get introduced to Hades, which I think this is easily one of my favorite interpretations of Hades, I'd love the character work, and I can show you right here. Here we have some colored pages of Ganymede, and this just looks badass to me, I love the way Aki drew Hades, just really unique and really gives you that dark, but also alluring, mysterious framework for this character. The thing about that I was mentioning with Apollo is that at the beginning of the book, you meet the character of Hines, and I thought he was gonna be the main character. I completely forgot about Ganymede, because this is the first guy you see. You know, after Ganymede gets abducted, he is granted immortality and is, you know, basically living this immortal, boring life inside this inescapable miniature garden, and part of the appeal, I guess, is for the gods to find amusement in a situation like that, where you are in total control of an individual, and the, I guess, the spiritual and significant ramifications that come out of that. The character of Ganymede, he's fed up, he's angry, he's upset, he's a lot of things, and at the start of the story, Apollo grabs another individual called Hines. You later find out who he is, he's a historical figure as well, but through the different interactions that Apollo has with the humans, he is able to perceive things differently and maybe evolve and see things from a different perspective. He takes them to the garden, but more of an amusement, not necessarily out of love and admiration, because he has no admirations for humans, and he definitely sees them as insects, and you know, they are the superior beings, if you will, the great gods. And throughout the story, Apollo, in his conversations, little by little, there's a big nudge that starts to form, and it snowballs into him questioning things, and the nature of life, and even humans, and being accepting of other ideas and thoughts. That's sort of the theme here with this book. Eventually you meet the character of Hades, like I mentioned, and that character furthers the gap of what they thought as them being sort of the supreme beings, to them now reflecting on death and the nature of time and space. It goes into that route. Unfortunately, one of the negatives for me of the book is that it doesn't really have a conclusive ending. It does tie back into the original story and the original motivations for the characters, especially the relationship between Zeus and Ganymede, but it doesn't give me an ending that I wanted. Maybe on further reads I will get more out of it because of their philosophical chats, if you will. So if you're into that sort of thing, you might want to check this book out. One of my favorite scenes has to be the gods' descent when Zeus first appears. That was badass, and I love that scene so much. And just the way the characters depicted in this book is really unique and badass, and I loved it. Unfortunately, we don't get a whole lot more than that, so it is what it is. But overall, just a quirky, fun, alternate retelling of Greek mythology with fantastic artwork from Aki. So if you can get it, it's an interesting read. Give it a shot. Who knows? Maybe you'll like it. I know I will certainly give it another go at a later time to see if I get more out of the questions and answers that are given in this story. Have you read Olympus? Let me know in the comment section down below. If not, let me know what is your favorite mythological manga or comic that you have recently read or want to recommend to me. I'd be interested in finding out. Guys, as always, thank you for liking, commenting, subscribing, being a part of a week in Geekdom here on YouTube. It really does mean a whole lot. Thank you so very much. And if you're interested in owning a week in Geekdom merch, check out the link below in the description for some t-shirts. I do have some designs that I'm working on that will be uploaded in the near future. So yeah, give it a look. See if you like it. It'll help out a ton for this channel. As always, again, thank you for being a part of the channel and I have got to go, so I will catch all of you on our next episode.


I'm Peter Burris and welcome to another CUBE conversation. We're here in our Palo Alto studios. We've got some really interesting guests, really interesting topic. We're going to talk about something called computational storage. And Nate or Celesi is the CEO of NGD Systems. Hello. And Scott Shadley is the VP of marketing of NGD Systems. How's your seeing him here? So guys, let me set the stage and let's get into this because this actually is kind of interesting. If you think about a lot of the innovations happening in the marketplace right now in the tech industry right now. We're talking about greater densities of data, more advanced algorithms being applied against that data, greater parallelism in the compute, more IO aggregate required. But the presumption behind all of this is that we're going to be flying data all over the organization. And the other presumption is that things like energy consumption, unlimited. Who cares? But we know the reality is something different. There is an intersection amongst all of that that seems to need addressing. Nate, take us through that. And that's exactly what we are addressing. So we are bringing other than the energy efficiency in a large capacity storage. Instead of moving the data to do any computation on the data, we bring the computation inside the storage to do the computation locally in a distributed fashion as you have a number of storage devices in a server. And without the need of moving the data and save energy. The main areas that it's a focus point for a lot of mega data centers is the energy density being watt per terabyte or watt per terabyte per square inch. And that's exactly with our technology we are addressing to have a most efficient energy efficient computational storage into the market. So let me build on that a little bit and see if I got it. So that your traditional large system, you have an enormous amount of data, you have a bunch of logic dedicated to know where the data is, find it. Once it finds it, it brings it and presents it to a CPU, a server somewhere who then takes some degree of responsibility for formatting it and then presenting it to the application. And you're bringing that out and putting it down closer to the storage itself. And so instead of having this enormous bus that's humming along at unbelievable speeds and maybe a 35, 40 watts off the card, you're doing it for. For a fraction of that. So we'll be able to do that with eight terabytes in a eight watt envelope or 64 terabytes to be done in the 15 watt envelope. That's the part that it doesn't exist today. And being able to not only to do the storage part of it, but bringing the application seamlessly without changing the application, bringing it down and acting on the data and just setting the subset of the results to the upper level of the application is what market is looking for that doesn't exist today. So you're still using industry standard memory, you're still using industry standard form factors. What is the special sauce inside this that makes it faster and cheaper from a power stamp? Very good question. So we are using a standard PCIe NVMe protocol for the drive. So with our technology and algorithm and the controller technology, we can address large capacity of the NAND and we are flash agnostic. So it could be any NAND. In fact, later on it could be any NVM. It doesn't need to be NAND. And having additional resources that through the standard of the TCPIP, we can bring application down without making any changes to the application. So we're taking a new approach to thinking about how IO gets handled at the storage device. Scott, it creates some use cases. Scott, tell us a little bit about some of the use cases. Yeah, so from a use cases perspective, you can think about it. If you want to do, you can go as simple terms as thinking about traffic gems. If you have a traffic gem on the freeway when lane of traffic gets stuck, well, if the cars are able to actually relocate and do the movements on their own, you eliminate the traffic bandwidth problem. What we can do is we allow you to say, okay, if I'm going to go look for a picture in a data set, instead of having the CPU ask for all the different pictures, do the comparison in memory, tie up CPU resources, you just tell the drive, go find this picture, it goes finds, compares the picture, tells you all about the picture, sends just that little tidbit back to you. So if you're collecting hundreds of thousands of Facebook photos today, you can analyze those and tell every person that's looking for a different photo, what their photo is, without having to use massive IO bandwidth. So traditional high performance computing? Yes. IoT? IoT, all of the AI where you're looking for things where you're trying to have artificial intelligence be smarter, you have to throw CPUs and GPUs at it, start throwing more storage at it because you have to store all the data you're generating. Why not let the storage do some of that work? You can offload some of it from CPUs, GPUs and you can scale more effectively. So my colleague, David Froyer, has been talking about how, for example, map in Hadoop could be accelerated pretty dramatically, but it's got to be more than just map. How are you supporting a range of application forms? Another use case totally different from these use cases is for the content delivery, video delivery on the last mile or last 100 feet. So today everybody is recording at home in their DVR. What if instead of having 10,000 DVRs and 10,000 homes is sitting in a central place and it has hundreds of thousands of video, but everybody points to it. The new challenge with that is the security portion of it. With our technology, we can do the encryption on the way out and the authentication right at the storage. So the concurrent users can be protected from each other. So let me think about the business model implications of that for a second. So I might enter as a private citizen, I might enter into a deal with Xfinity, for example, in which I agree to be the point of presence for my entire neighborhood. Is it that kind of thing we're talking about? Exactly, so that's the new edge delivery, but with a higher security that doesn't exist today. Because it's a major challenge for everybody. Interesting. For the security and authentication. Even within the same household, it could be multiple users that they need to be protected from each other. Very interesting. So Scott, you've got a fair amount of background in the systems universe. How is this technology going to change the way we think about systems? Yeah, so the beauty of this is we all thought NVMe was going to be the savior of the world. It comes in at flash storage. It gives you the unlimited PCIe bandwidth bus. The problem is we've already saturated that problem. We've got devices where a box can hold 24 NVMe drives, but you can only operate three or four of them at a time, even with 16 lanes of PCIe three. We're going to PCIe four. We've still got a bottleneck because all of the IO still has to go from drive to host and back to drive and be managed because you can't run on traditional storage, anything other than just data placement. Now the drives are smart. They're relocating the data on it, protecting it, whatever else, but they're still not doing what can really be done with them. Adding this layer of computational storage with devices like ours, all it has to do is go ask the question and the storage can go do its thing. So if I've got 24 drives, I can go ask 24 questions and I still have bandwidth to actually write data into that system or read other data out of that system and a random access pattern. So that brings us back to the question I asked earlier that namely that to make this more general purpose, there's got to be a pretty robust software capability or a set of libraries. How is that being handled so that it can be made more general purpose and folks aren't building deep into the architecture specific controller elements. How's that happening? How's it working? So one of the biggest tricks whenever you bring something kind of new and innovative that actually solves a problem that does exist is how to get people to address it, right? Because I want ease. I want to do simple. It took forever to get people to adopt SSDs. Now we're telling them we're going to have smart SSDs. What we're saying and what we're able to accomplish with what we're doing on the library front is very light touch. We're using the NVMe protocol. We're tunneling through it with a host agent which is a very small modification at the host and it has that now communicate to all the different drives. So simplifying that crossover of information is really what's important to your exact statement and we do that through a C library and it's very modifiable to various different workloads. It's not tied to each workload has to be independently written. So the applications and enterprises of all sorts are actually trying to drive that are more data oriented, computational oriented around that data to get the computations closer. You guys are helping for the new systems designs. We still think NVMeOF is going to be very, very important but this can complement it. Exactly. Especially where the, where IO and the energy that thus becomes a crucial issue. What's on the horizon? Well, deploying this and driving the energy efficiency. It continues to be the biggest point no matter what we do, there is not enough energy in the world with the amount of storage and the server and compute that is being deployed. And that's another area that we are focusing and we continue to focus to have the most optimum energy efficient in the smallest footprint in the marketplace. So I got one more question. NGD Systems is not a household name. Where are you guys from? So we started the company about five years ago. We, before that, myself as well as my two co-founders as well as a team of engineers. We used to be a company called Western Digital for a couple of years doing enterprise class SSDs. And before that, I started in 2003 in this field for the SSD. I started a product business line for a company called STC-STEC, which we created industrial SSDs and then later on became an enterprise class SSD. We became known for enterprise class SSDs in the industry. Yeah, and that's our heritage of last 15, 17 years with many years of SSD development, but this computational storage is other than doing an optimized SSD for a category that doesn't exist today and add to it a computational storage capability on top of it. Scott, last word. Yeah, just from that perspective, we didn't really get into a lot of detail on it, but the capabilities of reducing the amount of compute you need in a server, whether it be CPU, GPU or otherwise, and actually being able to use intelligent storage to drive the bandwidth growth, the NVMe over fabric or just the per box density is just something that nobody's really taken a significant look at in the past, and this is a definite solution to move it forward. So I'm going to turn it around slightly and say, software developers always find a way to fill up the space. So you can, on the one hand, look at it from maybe have low cost CPUs, but even if you have the same cost CPUs, you can do so much more because you can move so much more work out closer to the data. Correct, that's right. Great. All right, NGD Systems, very, very interesting conversation. Thanks very much for coming in and being at CUBE. Once again, this is Peter Burris with theCUBE Conversation. We've been speaking with NGD Systems. Thanks a lot for watching. Thank you, appreciate it.


Welcome to our talk, becoming OpenStack Developer while Outreach. This talk is going to be presented by all the participants. I'm Aya Yautava and I will participate as an intern. Hi, my name is Richard Pioso. I'm an industry engineer. My name is Dmitry Tansur. I'm an OpenStack Developer and Outreach mentor. My name is Ilya Yatongov. I'm also OpenStack Developer and also a commenter. In this internship, in this talk, we're going to tell you about the Outreach program, what is it all about and why we decided to participate in it. Excuse me. Can you hear me? Thank you. So we're going to tell you about the Outreach program and why we decided to participate in it. We're going to share our experiences and lessons learned. And finally, we will think about why this program may or may not be good for you. Much like in medieval European trade guilds, as well as probably today's science, the software engineering profession seems to benefit from some sort of apprenticeship before one can fully attain the professional fluency. Other than that, Red Hat builds its business on open source and therefore it's one of the strategic goals of Red Hat to help building, promoting open source and growing open source engineers. One of the, or maybe the main focus of Outreach program is to promote diversity. Right. Promoting diversity is a core value of OpenStack, Dell EMC and Red Hat's cultures. Not only does it, not only is it the right thing to do, it also produces superior software and business results. On top of that, we are open source engineers ourselves. And this is in our direct interest to promote and grow the culture we enjoy and being part of. So what is OpenStack? OpenStack is a large, well-established and highly collaborative open source software engineering project. At OpenStack, we value quality engineering practices, mutual respect and continuous learning. The goal of the OpenStack project is to produce free and open cloud management and infrastructure software. The first reference on the slide provides a bit of OpenStack history. And the second reference defines the OpenStack way, which is it's for opens. Open design, open development, open source and open community. If we look at Stacklytics, which is the bottom reference, you can go ahead and obtain interesting statistics about the current development cycle, which is named STYNE. Outreach is a project running under the software freedom conservancy organization. The idea behind outreach is that it brings together the open source projects that seek contributors, the mentors and the interns to build free software. The focus of outreach is to promote, ensure and help out groups of people, typically underrepresented in the industry. The way how outreach works is that the interns get on board of a typical large and well-established open source project and start working on some feature or on some part of it. Each intern typically gets a mentor that is a person experienced in this software and in this community, sometimes more than one. And this is a paid internship, therefore the intern has the ability to focus on this work. There are many reasons why to become an outreach intern for those who have little or no experience, it's a chance to try out different parts of IT related fields like programming, documentation, design, and to see if they are a good fit for that. Also for those who have some little experience, it's a way how they can start contributing to free and open source software that they have tried before for variety reasons and all of them can learn and work with people from all around the world and in the projects that are not available locally. And finally, it also can help to get a job. It can help to build a digital portfolio that can be shared with prospective employers, which is not always possible when working for other companies that cannot share their work with the outside world. So why would you become a mentor in outreach? Well, first of all, to contribute back to the communities that helped you grow initially, because community is really about contributing and contributing not only the code, but also helping the community grow and helping grow in a healthy way. And mentoring new members is an essential part of a growth and mentoring a diverse community is essentially part of its health. It also helps you personally to grow professionally and personally because you learn things better when you explain them. And working with newcomers helps you looking at your project from competing new angles, seeing what is hard, what is easy, what is complex, what is straightforward. And of course, you get more people to work on your project as well as a benefit. How it all began a little about me. So I'm a software engineering and I have experienced building enterprise information systems in C sharp and Java, but I always used free and open source software for my personal needs. And when I decided apply for outreach, I had to decide how to select the project. And so I decided to try something new, something that I haven't done before, but it had to be in familiar programming language because many projects required some proficiency in the tools used. So for me, the best chance is very with Python. And another criterion was we have mentors in the same or similar time zone. So so that I don't, if I get stuck, I don't have to wait for way too long when they come online. But this was like nice to have. And if I couldn't find matching project, matching all my criteria, I would drop this. Then open stock project, match all my criteria and I started applying. I had some issues with my initial ticket, like the long story short is that I didn't in the final submission, there was no code submitted. It was just documentation updates. So I wasn't able to really show my programming skills. Another different thing when applying was transparency in seeing that there are other people supplying. So I was able to see how many there are, how they are doing, but generally I decided not to pay attention to that, but focus on my application. And speaking about successes, apart from me being accepted, it was still good that despite my challenges with the initial ticket, there was a dedicated list of tickets for outreach applicants that they could start using. So a few words about open stack itself. It's not an easy project to contribute to. It's huge. It has a lot of code and a lot of projects comprise open stack and they all interact in non-trivial ways. The development workflow takes time and effort to learn. And of course, it's hard to just completely impossible to run open stack at home, for example, on your laptop. And on the social side of things, as it always is with big projects, the core team is overwhelmed, they have their own priorities, don't always have time for reviewing your patches. So code reviews can be really slow, days, weeks, months. And feedback, there are always differences in the way feedback is given or received. Some people are more polite. Some people are more direct. Some are way too direct. Some people are just burned down and they cannot express themselves very clearly and particularly newcomers are prone to taking this feedback personally, which also takes some work to come over. The outreach program rules is that every cycle starts with a so-called application period. During the application period, the prospective interns are supposed to work on a project of their choice on a ticket, I would say, of their choice to prove themselves and to get the feeling of the work they are signing up for. Mentors are supposed to provide the interns with those test projects. After the test project is done, it is in the power of mentors to rank the participants and pass the outcome to the organizers for the formalities and budgeting and things. With OpenStack, apparently it was difficult to find this isolated, more or less trivial tasks to offer to interns. But other than that, it's hard to fit the development workflow within the application period with OpenStack because of long reviews and all these social things. It's also important and hard to make sure that the work you are proposing to do is aligned with the upstream community goals because if it's not, then it won't attract any attention for the reviews. As mentioned, code reviews in OpenStack projects are very demanding and they question every single bit. So the way I handled it, first of all, I didn't take it personally. I remembered that I am not my code and reminded that myself regularly. But I shouldn't go to the other extreme. I still need to take responsibility for the code I have written. I still need to engage with the feedback and work with the team to make the code the best as it can be. Another thing that helps is to recognize that code reviews are an essential part of programming. When I'm working on code reviews, I'm still being productive.  And the last thing about code reviews is it was a great chance to learn many new things that otherwise wouldn't come up. And even if the things I learned didn't end up in the final submission, they still can be handy in the future. The next thing about learning new things as the domain was very new to me was asking questions. And I needed to find the balance when I'm asking questions too soon and when I'm trying to figure out my it myself for too long. If I spend too much on the questions, then I'm wasting too much time. And the last thing is working from home remotely as outreach is a remote internship. It's an important part of that. And people need to be prepared for that. It helps that the person is a self-starter and it also goes together with motivation why you are working on the project. Are you excited about it? And that's why it's very, very important to choose the right project at the very beginning and also it helps if there's a dedicated place to work, a room or a corner room, a local library. And still working remotely communication is very important. So regular conference calls helped a lot as well. So I'd like to present a case study. Industry is heavily involved in open stack and influential in standardization efforts. The standards body in this story is the distributed management task force, the DMTF, which creates open standards for managing IT infrastructure. One of its newer and evolving standards is Redfish. A RESTful API for simply and securely managing converge hybrid IT in the software defined data center. The DMTF Redfish Forum, which performs the standards technical work, was interested in promoting Redfish in the open source community. Separately and in parallel, OpenStack's ironic project was implementing support for Redfish to provision bare metal servers. Its developers, including Aya, were facing challenges and found the standard specifications and related documentations, documentation not always ideal. So for example, there was confusing or lacking detail, don't figure. And the industry vendors, including Dell EMC, are contributing to both Redfish and Ironic. They introduced the DMTF Redfish Forum to Ironic and the Ironic leaders to one another and established a collaboration among all three communities. In the trenches writing the code was Aya. And like many young engineers, she may have felt hesitant to reach out to the technical experts, those that had authored the Redfish standard. But now, as a result of this collaboration, they were working alongside her towards a shared goal. Aya's experience has been fed back to the Redfish Forum about what helped to clarify and improve the technicalities of the standard. Also, what helped set up the ties between the three different communities and she with them. And also, it's taught and what taught Aya how to negotiate intricate and complicated technical issues with the community and with fellow engineers. Through Aya's successful internship in three communities, industry, a standards body, and an open source community, tore down silos together and jointly furthered one another's goals. So if you have who tips how to be a better mentor, first keep you in turn, always busy, always challenged, always keep in touch with your intern. Make sure they never get stuck, especially for a long time, no longer than one night. Have them keep focusing, focused even in case of, for example, slow reviews when it's very easy to lose motivation and to lose focus. Have them do their own planning, encourage small steps and recognize small successes and make sure they recognize their small achievements. Another important thing, help them network with the upstream community, introduce them to other community members, introduce to the team leader, points to a few contributors that can help them as well. Make them involve, make the interns involve in cold reviews of other patches. It's a great way to overcome fear of feedback and of course to learn the project itself. As a mentor, you have to understand the different psychological settings, help the interns overcome the biases, help yourself make sure you're not biased, help grow this unbiased setting in the community. It's helpful to see yourself, you and your intern as colleagues or co-researchers other than some master apprentice set up because in the end it has to be fun. We think that when we deal with the prospective interns, it seems that when the intern is genuinely interested in the technology, not just as a prospective work, but just for the sake of it, it's a good sign. Another good sign is that when they come prepared and well understood, well understand in the project they are signing up for and why that project might be a good match for them. And finally, one can't be to essential about the way how open source community works because as Dmitry mentioned, some feedback, some code review can be harsh. The code can be abandoned or reshaped in any possible way. And therefore it's good when the intern is prepared for such kind of development. So I'd like to encourage you to come join us. We've had experience with the internships and we found them to be mutually beneficial and useful. If you're someone who's new to the field and intrigued by getting involved in a respectful open source community, please join us. If you're part of the community and interested in building the team and getting more helping hands involved, please join us. If you're a vendor or involved in a standards body, you can go ahead and have your products and standards specifications verified. So please join us. And there are a couple of references up there. The first one is refers to outreach communities or communities that have been involved in an outreach. And you can go ahead and find those communities if you're interested in joining us. And you're also encouraged to go ahead and propose the addition of a new community to the Outreach Internship Program. And the second reference for OpenStack lists or basically describes OpenStack specific involvement in outreach. So please come join us. If anyone has any questions, we're reviewed. And they were sponsoring together with that with Victoria, an analysis of the gender diversity of OpenStack. So one of the results we have, and we were analyzing all of the outreach interns, was that if someone is mentored, the time they remain contributing to the community is higher that it compared to the average of the community. So it seems that if someone is mentored, it will remain for a longer time. So we are talking around 18 months in average or in media, I don't remember the numbers. It compared to the usual average of the community. And these are great numbers. Of course, we are talking about different populations because in outreach, they were like 40 people and we are talking about thousands of developers. Right. You know, OpenStack. So we need some scientific approach to this. But those are the first numbers and those were quite interesting here. And the question I have for you is, can I just interrupt you if you have any questions? We are all the time, so, basically, question? Sorry, we are... Can you move it outside? Yes. That's okay. Thank you. Thank you. Squidule is kind of busy, so... That's okay. Thank you very much. Thank you very much for your question.


When we decide someone's nice or well-meaning, we choose to suffer it out. We suffer it out.


Hello, and this certainly isn't how I envisioned this or planned this, but I am going to retire. This is not an easy decision, honestly, it's the hardest decision of my life. But it is the right decision for me. For the last four years or so, I've been in this cycle of injury pain rehab, injury pain rehab. And it's been unceasing and relenting, unrelenting both in season, both and off season. And I've felt stuck in it, and the only way I see out is to no longer play football. It's taken my joy of this game away, and this, sorry, I've been stuck in this process. I haven't been able to live the life I want to live, taking the joy out of this game. And after 2016, where I played in pain and was unable to regularly practice, I made a vow to myself that I would not go down that path again. I find myself in a similar situation, and the only way forward for me is to remove myself from football in this cycle that I've been in. I came to the proverbial fork in the road, and I made a vow to myself that if I ever did again, I would choose me in a sense. It's very difficult. I love this team. I love my teammates, the folks in our building, the fans, the game of football. And as part of this team, as a member of this team, and because of how I feel, I know that I am unable to pour my heart and soul into this position, which would not only sell myself short, but the team in the end as well. And it's sad, but I also have a lot of clarity in this. It's been a difficult process, but my wife, my family, my friends, Mr. Ballard, Mr. Uruse, the Uruse family, and Frank Reich have been incredibly helpful, supportive, and I'm so grateful for them. As I told the guys earlier in the locker room, it's been the honor of a lifetime to represent the horseshoe and the city of Indianapolis, both on and off the field. To Mr. Uruse and your family, thank you. Thank you so much. I am so grateful to have been drafted here. Their unwavering support is incredibly appreciated. I cannot fathom another owner who loves their team as much as you do, and we feel that as players. We appreciate that as players. It permeates through the building. And from the moment, and we talked about this earlier, but from the moment I arrived in Indianapolis, I felt like I could be myself, and I felt like I did not have to fill Peyton, one of the great of all times, I felt like I did not have to fill his shoes. I could be me. And I know that starts with the person up top, and for that, I'm very, very, very much appreciated. So many people to thank. So many people to thank. I think maybe fitting that Chuck was the coordinator for the opposing team tonight, because he had so many positive points and moments and such an impact on my life in BA as well, who's obviously not here tonight, but with Tampa, all my former coaches. But it did feel a little bit full circle walking out there tonight and being able to give Chuck Pagano a hug who provided so many great memories for me and Colts fans everywhere. Former teammates, there's a lot of guys I need to thank that I've played with that I'll get around to personally when the time is right. But I'd like to start with a couple guys that stand out. Robert Mathis, who quickly became and will always be my football hero. I love playing with him. I loved watching him play. He was as good a teammate as I've ever had. Reggie Wayne, what a thrill it was to throw to him.  I thank you for the incredibly positive impact you had on a young player in this league. So many wonderful guys like Joe Wrights, Jack Newhawk, so many great linemen that I had a chance to play with. And I was a part of some amazing quarterback rooms that helped me grow and become a man in this game. Clyde Christensen, who ran it for a while with Drew Stanton and Chandler Harnes, Shadi and Scotty Tolzine, especially Matt Hasselbeck. I know that was a great influence on me. I learned so much from all of you all. And so many of you all are lifelong friends. They are lifelong friends. And again, I'm much appreciated for that. So I'm going to take a moment. I think it's fitting that I'm in my retirement press conference in an athletic shirt. I know I look pretty ratty up here after games. So sorry, mom. I can't have a better appearance right now. There are so many people in the Colts organization that make it run that folks maybe don't know about, but they do an incredible job. Doug, Troy and the crew, Pete Ward, everybody in the cafeteria, Tex and the security staff, done an amazing job for me. Everyone in the scouting department on the personnel side or Todd Visfari and Matt Terpening picked me and a bunch of other Stanford guys up my rookie year from Indianapolis Airport and took me to Jason's Deli and Carmel for my first meal in Indianapolis as a Colt. And it was awesome. The training staff and the medical attention I've received here has been incredible. Bone doctor, E.B. Carey, Kyle, Marcus, Kea, Wally, all the doctors. The help and care has been top notch, especially in times that are tough, which is usually when you're seeing the doctor or the trainer. David Thornton, a simple thank you for your compassion. Matt Conti and the PR team. Matt, you have a vanquished job wherever you are and you do a great job at it. So thankful for you. Our strength staff, Rusty Rich, Zayn and Podell. I do feel like I'm missing folks in the building, but so many of you have helped me in so many ways and I'll have a chance to come say thank you and you know who you are. And then some folks out of the building, Tom, Willem, Yost and Karen. Thank you, thank you so much. My wife and I are so proud when people ask us where we're from, we say Indianapolis. It's our home, the support we felt here from lifelong friends, from the people that we love. The 500, this has been an incredible place to make a home and to grow. And many, many of my most fulfilling moments here off the field involve children. Riley camps around the state, getting a chance to be with kids and have fun, go into the hospital and having a chance to talk with parents and children. Reading the kids at schools, hanging out, Children's Museum, the wonderful things they do there. So a big thank you to this city. It's always will hold a special place in my heart. And I guess I'll transition to this current team and why it makes it so difficult, I guess, for me to stand up here and say I'm retired. It's a great group of men. It's a great group of guys. One that, a group that makes coming to work every day feel very, very special. And I feel incredibly lucky for that. And fans and people need to know about the men in that locker room. They're great, they're honest, they're real. There's no bigger fan of them than me. Chris Ballard, thank you. You know, I have so much respect and admiration for you. I've had a lot of tough conversations. I've learned so much from him, the honesty. It's incredible. Frank, so thoughtful, driven, kind. Again, I've learned so much. So there were times last year I'd have to pinch myself and say, is this for real? Or am I allowed to have this much fun on a football field? And that started with you. Nick Siriani and Marcus Brady, it's the same. Going to miss being with them every day. They're good people. All the rest of the staff, they make coming into work a joy and something that I certainly, certainly will miss. And coming back last year and playing, a lot of people had a lot of help me in a lot of ways. And they'll never know how important that was to me. And I'm, again, so, so appreciative. And my teammates, I feel so conflicted because of my love for these men. But it is clear to me that's what's best for this team is me, does not involve me. And I'd like to say a quick note about a few of them as we get towards the end here. But when I was a seven-year-old, my father drove me up to Amsterdam and I watched Adam Venetieri kick for the Amsterdam Admirals in NFL Europe. Then when I was in seventh grade, my father took me to the Super Bowl in Houston and I watched Adam Venetieri kick a game winner against the Carolina Panthers. And then, of course, my first win as a Colt involves Adam Venetieri kicking a game winner against the Minnesota Vikings. And I told him all this earlier today. I stand in awe of Adam Venetieri. He's a great man, a great teammate. And again, he's one of those guys. I'll tell my grandkids I got to play with him. The guys on the O-line, Brayden, Glow, Ryan, Q, Hagrid, LaRave, and Baymer, Josh, and, of course, Anthony. They've been a pleasure to play around. And there's so many more that I've played with in the past. But they were a big part of last year of being very special for me. Obviously, the success of the team. And I'm so grateful and appreciative to have had a guy like Anthony Costanzo be in the building from the day I walked in. Jacobi Bresset is an awesome dude. He's got a bright future. He's diligent, sharp, loves football. I hope I can continue to support him in different ways. I am so grateful for our friendship. On a personal, well, getting a little more personal, but coming back into the building early last year, I was very jealous and resentful of this fun, happy dude that was in my spot as a quarterback on this team. I obviously didn't have a lot of confidence in myself at that time either. But I could not have been more wrong. And he helped me grow in so many ways. He's a lifelong friend. He means so, so much to me. He's a big part of having one of the more rewarding years of my football life last year. I cannot wait to support him and see him lead this team. I am excited for the future of the Colts in large part because of Jacobi and also all the other men in that locker room. There's so many guys on offense and defense that have had a pleasure to play with. Clayton Gathers is, I love watching Clayton Gathers run around and play football. All the running backs and Rafi, the Titans. Eric Ebron was fun to play with. I'm so excited for his future. He's a great friend. Moe, Jack Doyle, Jackie Jack, and I have been through a lot together. I'm going to miss him a lot on the football field, but we're friends forever. And the rest of the guys, I have so, so, so much respect and love. And it runs so deep in me for them. And I hope they feel that because I know so many guys in that locker room have had such a significant impact on my life in so many, so many ways. And lastly, in terms of guys on this team, T.Y. Hilton. I had more fun throwing the football to T.Y. than should be allowed, probably. When I was away in 2017 for the latter half of the season, I had to figure out why I wanted to come back and play football. And I boiled it simply down to the fact that I like throwing the ball to my friends. And I love throwing the ball to T.Y. Hilton. He's the best football player I've ever played with. He's a better teammate than he is a football player. In conclusion, my folks who aren't here tonight, but mom, dad, mayor, Emily Yad, Uncle Will, all my friends. Thank you. And my wife, Nicole. Thank you. I love you. And I guess in a philosophical sense, I want to thank football for so many wonderful moments in my life and the pressure, circumstances, environment that pushed me to grow, learn, change, in so many meaningful ways. It's the greatest team sport in the world. And please, if you have questions, I'd like to ask them. Was this plan today to mention retirement? No, I'll be honest. I was going to tell my teammates after the game. And 3 PM tomorrow was going to talk to you guys. So this is actually the major. I mean, it's difficult. How long has it been building? You didn't wake up this morning and say, I had it. No, I didn't wake up this morning. A week and a half, two weeks. It's been a little bit fast and furious. And the lack of progress on my ankle. And I'm in pain. I'm still in pain.  And for me to move forward in my life the way I want to, it doesn't involve football. What was the point? This was the tipping point. If not for this, you might be having a different conversation. Yeah, I guess the reality is I have this. And I've had had this. And so I don't know if tipping point, but it's shouldered in the ankle and this and this. And it's, yeah, I don't feel like I've lived the life. I can't live the life that I want to live moving forward with this, yeah. Is that first time retirement into your mind in a serious way? Yeah, a couple of weeks ago, a week and a half ago. Not even last year? No. How much of an emotional role has all of this taken on you? Yeah, I feel quite exhausted and quite tired. I do know once I hit the sort of point where I felt like I knew what I needed to do for myself and talked to Nicole and my folks and some close friends and family that, and then had some very difficult conversations with Mr. or, say, Frank and Chris. But it did feel like, in a sense, a weight was lifted then. But it's been tiring. I feel tired and not just in the physical sense. What was the final straw, Andrew? Was it after a workout? What was it you said? If you know what, I'm going to go home and sleep on this. I don't know if there was a final straw, per se. The lack of progress, I think, just built up and run into one. OK, turn the corner. OK, let's run into another stumble buck. Turn the corner. Turn the corner. And I can't remember if there was one thing that tipping point or final straw. But yeah, again, I feel so much clarity and, again, so grateful for the experiences and the positive times that I have had here. How do you know, say, a year from now when the ankle is finally healed, you won't want to come back here? I can't see the future. Zach, I'm not going to sit here and say it. But I very clearly in my mind see that I won't. It's not. Yeah. So you say, do you know what's going on with the ankle yet? It's a myriad of issues. And I, calf strain, posterior impingement, high ankle sprain, it's part of my journey going forward. We'll be getting out of pain and figuring out what's going on and how to feel better, obviously. So I don't have any definitiveness in my mind on it, and we'll continue working on that. It's going to be quite a timeline to deal with that if you continue playing. Yeah, I'm not. So it's like the ribs, the kidney, the shoulder, the ankle, the calf, all that over the years is what led us here to that. Is that correct? And I'd like to say too, this has been my personal journey in football, obviously. And everybody's journey is different.  And I don't. All I feel is love for this game and love for my teammates and walking in. And I know my journey has had some ups and downs. And physically, it has taken its toll over the last four years. And that is why I'm here and in the mental and emotional toll that takes as well. But you never could have imagined walking away from football at the age of 29. Yeah, I'll be honest. I didn't imagine retiring. I didn't imagine retiring two weeks ago. But no, I didn't think of it in that way, no. Last Saturday on the field, what were your emotions coming off? Because you said you were out for two weeks. Did you think then you still were going to play this year? I had a good idea that it might. I thought that this might be my last time throwing on Lucas Oil as a current member of a Colts team. And it was Tomasawa made sure to go out and enjoy it. You've always been one of those people who took the blame on anything, whether it was an interception or whatnot and stuff. Did you ever try to say, all right, maybe I should try to play through this because I don't want to let those guys in the locker room down? That's a good question. And in 2016, after that season, which I played through some stuff, I made a vow to myself that I would never do that again. I got in not a good place. And I felt that the past week and a half, two weeks. And that's also a big part of why I'm here right now talking about this. You said that quite a few times, just in different references. And I mean, this game does require you to put yourself second, and often times, right? And I mean, just having to talk to a team first and elsewhere, which is what you have to do. Just how, when you've done all that you've done, and how were you able to reconcile all that?  Did you ever, yeah, over the years, you know? Yeah, look, I, yeah. It's about the team. I got to put myself second, or just, you know? No, I wouldn't say. I never felt like, I guess in my mind, I never looked at it as me or the team, part of the team, and do my best for the team, and also do my best for myself, in a sense. But it's, I mean, it's the greatest team game in the world. I've loved being in that locker room. It's truly been the honor of a lifetime to suit up next to many of those guys, and that's part of what makes this very, very, very difficult. Andrew, would you like to have more? Not on a negative, but all that you've meant to the team and the city, and the stunningness of the decision. Any reaction to the fans? Did you hear the reaction of Walker on the field? Yeah, I'd be lying if I didn't say I heard the reaction. Yeah, it hurt. I'll be honest, Jeff, it hurt. Saw with the fact that you did get your fair chance, necessarily, in this field? You know what, yeah, I don't look. I certainly feel like I got my fair chance, and I'm very grateful for every snap that I got to take, and the lows, and learn from them, and the highs, and all the positive things that happened in this building, that I got to be a part of, so I don't hold any resentment, I guess, in that way. I do feel like I got a fair chance, and I tried to make the most of my chance, and right now, my journey just doesn't include football going forward, and I'm, again, so grateful to have. I'll feel like a cult forever. I know I will. I'm so grateful, again, for the Ursa family, for Frank, Chris, everybody in that locker room that I've got a chance to take the field with. It's truly been the honor of a lifetime, and I understand the suddenness, and maybe the surprise behind it, I really do. But I also know I have so much clarity about my next steps moving forward, and I'm so excited for this team. It's a great team.  How much is that factored into this decision? Not really. I know it's a bit of an unusual situation, but how much do you anticipate you mention how much you love this franchise, how much they mean to you? Being around still, the season's about to start. What are your plans? Take a full backseat or do you plan on being around? I know. I'm friends with so many guys in this locker room, and I mean, we live here. Yeah, this is our home. So support the guys the way I can, and I certainly need to rehab and get feeling good. And yeah, I got some folks that I need to call and thank them. And it might be a late night on the phone and with some friends and some crying and laughing and some teammates. And I guess before I get off, I should also thank those of you who have covered me for most of my career, all of my career. I appreciate getting to come to work and talk to you guys right now and then. And yeah, I guess a small part of me will miss you as well. But thank you. I very much appreciate it. Mr. Orsay, Chris, Frank, Orsay family, thank you very much, appreciate it.


Love before me, love behind me, love at my left, love at my right, love above me, love below me, love unto me, love in my surroundings, love to all, love to the universe. Peace before me, peace behind me, peace at my left, peace at my right, peace above me, peace below me, peace unto me, peace in my surroundings, peace to all, peace to the universe, light before me, light behind me, light at my left, light at my right, light above me, light below me, light unto me, light in my surroundings, light to all, light to the universe, love before me, love behind me, love at my left, love at my right, love above me, love below me, love unto me, love in my surroundings, love to all, love to the universe, peace before me, peace behind me, peace to my left, peace to my right, peace above me, peace below me, peace unto me, peace in my surroundings, peace to all, peace to the universe, light before me, light behind me, light to my left, light to my right, light above me, light below me, light unto me, light in my surroundings, light to all, light to the universe.