 Hello, good afternoon. I'm going to start the sessions about the OpenStack Book Show. So my name is Leon. I'm a software cloud architect. I work for Intel. In today's session, I'm supposed to have presented a session to get a caddy from the OpenStack Foundation. However, I just heard that she heard her back. So she had to leave early. So I'm going to present this myself. But fortunately, I have my other co-workers with me, like Shamal and Ger, who are the co-authors of those books as well, but they are here. So feel free to ask questions if you guys have any questions. So basically, what I'm trying to introduce here is over the past three years, the Enterprise Work Group, we have produced a series of so-called eBooks. So we're starting the very first eBooks two years ago, more than two years ago. And over that time, this is the third eBook that we have produced so far. So actually, I don't have much thing to tell you, because if I tell you everything, what's the point of having you to read the eBook, right? So anyway, so in this eBook, what we're more targeting is about how to design, migrating, and deploying applications on the OpenStack. So maybe before we go to this eBook, I can give you a brief introduction on what we have done in the previous two books. So the previous two books that we have done, the first very first eBook is the OpenStack, a Business Perspective. It's more about educating enterprise users or operators who are new to OpenStack, and telling them what is OpenStack and what is the benefit of using OpenStack. So if you are pretty new to OpenStack, that is a book that for you, if you want to present anything, tell your CIO, what is the benefit, why you want to put OpenStack into your organization. That is a book that you want to look at. And that is a very short, short, short book. And I think we have something here. I'm not sure that we have the extra books here for the first one. So the second book is about the path to cloud. It's more about, so the first book is more about what is OpenStack, right? So the second book is basically telling about how to implement OpenStack in your organization. So we're not just looking at the technical perspective. We look at what other considerations you need to be aware of, such as organizational changes. The team, how do you form a new team in order to bootstrap your OpenStack environment? What is the staffing requirements? And so what is the adoptions strategy, whether you want to go private or public? And what is the consumption model? Whether you want to go for a DIY vendor solutions or a managed cloud solution. So those are the things that we talk in the second book. So in this book, we're more focusing for the application perspective. So assuming that, let's say, you already have your OpenStack environment in your organization and you plan to design and migrate or deploy applications on as a thing, OpenStack Cloud. And this is a book that tells you some of the things that you need to be aware of. So in this book, it shows something about what is the traditional versus cloud-native application, what are the differences between them. And if you want to migrate the application to cloud, what is the planning strategy and what is the patterns? So the patterns can be, do you want to do a cloud hosted way method or do you want to do a cloud optimized way or the cloud native way? So different migration path has different things that you need to be consider. And also, what is the infrastructure considerations for the application developers? So if you deploy applications in a cloud, whether you want to run it in a hybrid environment, hybrid architectures, or you want to do it in a pure private solutions or pure public solutions. So those are the things that you can find from this ebook. And then the other section we talk about is API and SDK for the application developers. And that section is kind of like, I mean, to some people, maybe that is a very interesting section. Because in that section, we basically talk about, given the capability that we have in OpenStack today, it's mainly API driven. How can those API features be built in as part of your application programming logic? So for example, if you're doing application developers, you might want to do some application that is more compute intensive tasks. Or maybe you want to do dynamic provisioning of the storage. How can you use the API, OpenStack API, such as a compute API, to spin off additional compute resources to do the computation tasks dynamically inside the code? Or for example, in the ebook, they also have one example. Talk about using the web album, the folder album example. As part of the applications, you actually upload the pictures and using the Swift Object Storage API to put that images into the Swift Object Storage. So those are the things that can be useful for the application developers. And those API SDKs, not just for application developers, it can be used by anyone who needs the API or SDK to develop any kind of your application. It can be running operations as well. And then we also talk about what other OpenStack services can be used as part of your application development lifecycle. So for example, let's say in your environment, you probably need a database. So in a conventionous enterprise world, you probably have a separate database team that want to spin off the database environment for you to use, but in OpenStack, there's this trove database as a service that you can use. So if you as an application developer, and how can those features be useful for you to speed up your application development, and other services like heat orchestration, how can your provisions environment, the application environment, so that it can run your application on top of that? So if you need those features, you probably need to be aware that those features need to be provided by your ops team, by your OpenStack operation infra team so that those features are made available for you to use. And then we also have a few pages talking about containerizing applications. There's a separate white paper. Talk about OpenStack containers and containers on OpenStack. So we are not duplicating the content, so there's a link inside of, in that chapter, the reference to the white paper. And then we also talk about how do you move application from cloud to a different cloud? What are the things that you need to consider aware of such as a different cloud have different services, even from across AWS or Google Cloud, for example, in AWS, the compute services is called EC2 and the different flavors and AMI images. If you move into OpenStack private cloud, the equivalent service is Nova Flavor and Glance Images. So those are the things I talk about in that chapter. And then the last chapter we talk about moving from private cloud to private cloud migration is checklist. So we have a few recommendations on what you need to be aware of when move from public cloud to private cloud, things like considerations on the bandwidth considerations, storage considerations, those are being talked about in those sections. So these are the contributors and some of them are here. Any questions? Sorry, I can't hear you, can you speak loudly? Oh, okay. So Shimano girl, you have any? In the chapter where you're talking about moving from cloud to cloud, bringing your containers, does it discuss the securing your containers, how you do the managed security? Security of containers, I don't remember if we talk about that one, right? Maybe next versions. So I think, all joking aside, I think it might be the next version. So obviously there's a trend here. We started from the business perspective of why OpenStack, why cloud? We went to how do you move to OpenStack? We're now talking about how do you deploy applications and modernize your applications to run optimally on OpenStack. And while we were building out the outline for this book, containerization and container-related topics came up pretty frequently. And so we decided that if we dove into those topics, we'd be writing like 150 page book. So we decided to kind of take the container orchestration and things that are related to not cloud native application development patterns but deployment models into a separate thing. So we have a whole bunch of books here. So feel free to come and get it. The foundation don't want to bring them back again. All right, any questions? I'll be here for a couple of minutes. So if you have any questions, do approach us. Thank you.