Okay, ready? Okay, good afternoon. My name is Marcos Hernandez. I'm a staff engineer with the Networking and Security Business Unit. I support the NSX platform here at VMware. And I'm also part of the VMware Integrated OpenStack team here at VMware. So today we're here to talk about the new plugin that we have developed for Neutron and that integrates into VDS and NSX for vSphere. So that is the content that we're going to present today. The agenda is very simple. I figure that it would be a good idea to level set on NSX and make sure that everybody has at least a high level understanding of what NSX is. So we're going to cover some of that. And then we'll jump right into a technical discussion, the technical deep dive on how Neutron is leveraging NSX vSphere through this new plugin. That is, by the way, offered as part of our VMware Integrated OpenStack product but can be used by any OpenStack distribution as it has been upstream. And it's a fully open source. Okay, before I get started, anyone here know what NSX is or has been exposed? That's pretty good. That's more than 50% of the room. So we're not going to spend too much time there defining or restating the value prop of NSX. But for those of you who do not know what NSX is, NSX is a network virtualization solution that offers in hypervisor or on top of hypervisor networking services. And the idea behind NSX is that we have promoted to software the networking services that are required for workloads that were typically offered in hardware. So what that means is that if you need a Layer 2 through Layer 7 services for your applications to actually do something useful for your users in the traditional provisioning and model, this would require changes and configuration and some sort of orchestration in the physical switches and the physical routers, your load balancers, et cetera. So with NSX, we promote all these network services to software and we call this virtual networks. Now the services can be instantiated via API calls. So the full networking stack can be automated. So you can create VMs, create applications, and as you do that, you can also create the networking services that are associated with that application. So you can do that in a single or several API calls. So we have turned the network into an API target. So the idea there is automation and provisioning speed. So NSX still requires a very solid, a very robust underlying hardware. VMware, we don't sell physical switches so we still need a physical network to run on top of. The vendor that provides that physical network is irrelevant to the operations of NSX and the topology of that physical network is also irrelevant to the operations of NSX. What we need is IP connectivity for all the hypervisors that are included in the NSX domain but the network has to be reliable. And the joke which you've probably heard a million times if you've heard my pitch before is that if the network, the physical network is crap, the virtual networks in NSX are just v-crap. So you have to have a reliable network for NSX to deliver on the promise of automation and reliability that we are promoting here. Then the other aspect of NSX is that we are, in a sense, we're a software-defined network solution although we don't necessarily like to identify ourselves as such. And the reason is that we don't necessarily touch physical switches. There are a couple of exceptions but generally our action point is the hypervisor. That is really where we're focusing all of this effort. But we have, just like some other SDN solutions, we have externalized the data, I'm sorry, the control plane and the management plane. So we do offer an external control and management plane that is also what you will point your cloud management platform to and this is the place that you use to enter the network and interact with the NSX services. It is highly available, highly scalable. The control plane is based on the NYSERA technology that we acquired 18 months ago and we have now adapted this control and management plane to work in a VCR environment. So when we talk about the neutron interactions, I want you to remember that we are talking about integrating with this control and management plane, that we're not necessarily talking to the hypervisors directly and I'll explain later why this is important. So automation is the name of the game and our control and management plane offers that. I think it's important to double click on one of the components in NSX, which is our Edge Services Gateway. As you will see a little later, we use this ESG or VM gateway in multiple places throughout our integration, the technology of the plugin that we have developed for neutron. So it's important to define what this gateway is and what it is not. This is a router in a VM that offers a good number of advanced network services, but not all the services are visible to OpenStack. For example, the example that I always present is our ESG supports dynamic routing protocols, supports OSPF, it supports BGP, but if you're integrating with OpenStack because that support doesn't exist in neutron, your OpenStack based cloud can really, all those features are really invisible. So it's just a little reminder that because of a platform claims to support features X, Y, or Z, at the end of the day, the least common denominator becomes the consumption layer and what your consumption layer can actually instantiate and consume. So that is very important and the last thing that you want to do is create automation with a cloud management platform like OpenStack and then go out of band to your infrastructure and start enabling services that are not visible to your cloud infrastructure. So this is a router in a VM that supports all these services and as these services are added to OpenStack, the good news is that NSX will be ready to support them and turn them on. So as we add load balancing as a service, VPN as a service, dynamic routing protocols when that finally comes, they're underlying infrastructure that you're providing when NSX will already support that, so it's just a matter of enabling that particular service. Okay? Okay, so that's a very, very quick introduction to NSX and what it is. We'll revisit some of these concepts as we go through this presentation. If you were in the previous session with Dan Wenland, you probably saw this slide. This is just a reminder that even though this plugin was first offered with VIO, VMware Integrated OpenStack, a product that we announced a couple months ago, our participation in the open source community is nothing new. We have been very active since 2012 when Dan and the NYSERA team started the Quantum Project, which is now Neutron. We've been very active and we are consistently one of the top 10 contributors to Neutron and other projects in OpenStack. So just a reminder that we have a lot of experience here and in the room, right now there are some teammates that are actively writing code for Neutron and supporting the plugin. So if you want to talk about what's happening there, we have all that expertise in the room today. Okay? Okay, so what is this VMware Neutron plugin? It's a production grade plugin that has been developed by us and that is fully upstream and open source. It is offered as an out-of-the-box option that is automatically configured using a wizard-based approach with VMware Integrated OpenStack, our own distribution. But because it is open source, it can be used by any open-stack distribution. In fact, we're in conversations with our partners that are open-stack vendors and they are testing and integrating this plugin as part of their own packages and their own offerings. So we are not really in the business of selling open-stack. What we really want is to help you leverage the best capabilities of our infrastructure on the vSphere and NSX side if open-stack is the strategy that you decide on for your private cloud implementation. So we're going to double-click on this a little later, but the Neutron, the collection of Neutron services that leverage the NSX infrastructure communicate using the plugin communicate to NSX Manager. NSX Manager is the management plan for NSX and it is also the API entry point into NSX. So when you use our plugin in your open-stack distribution or when you use it with VMware Integrated OpenStack, you're not pointing to all the hypervisors to instantiate and deliver networking services. You're just pointing to NSX Manager as a single entry point into the system. And then from there, NSX Manager goes around and orchestrates all the different network services. So why NSX? There's another option for configuring our plugin, but you're going to see that we are going to keep coming back to NSX as a preferred method. In fact, I think I have run NSX here just to remind you that even though we have VDS as an option, you should run NSX with this plugin. So if you look at the left column here, these are the attributes of NSX as a network virtualization solution. This is the reason why we want you to use NSX and what you probably want to use NSX. You want more agility. You want mobility for your applications. You want security, multi-tenancy, and simplified operations. If you compare that with the goals and the purpose of what OpenStack is trying to accomplish, it's the exact same thing. So we believe that we're fully aligned with the OpenStack strategy for adding infrastructure as a service in your private cloud, and NSX we believe is the best choice to do that when you do OpenStack and when you have this infrastructure and investment already in place. And that is the last slide for my architecture pitch. So let's get right into the technical deep dive. So what you see in this green or gray box is OpenStack and the various projects. And there are some missing, right? But at a high level, that is what OpenStack is. So that is your OpenStack control plane in a way. Just a little reminder that this plugin is not the only hook that we have into the VMware products or the VMware platforms. If we look at what is happening here with vCenter, we also offer a Nova plugin for vCenter. So when you create an instance in OpenStack that actually triggers the instantiation of a VM in vSphere, and this is all done by vCenter, or instigated by vCenter. Also we have a couple of drivers for Cinder and Glance that also talk to vCenter to create block storage and image catalog services, respectively. So it is not just Neutron. The focus of our session today is the network interactions between Neutron and NSX and how that happens and what are the services and elements that we use. But just a reminder that there are other plugins that you can use and then you can leverage. Okay? It is also important for all this to work as advertised, it is also important to satisfy and meet some very basic design requirements. We want you to configure the infrastructure in a way that will guarantee success. Okay? So we have this notion, and if you've seen NSX before, you will see that this concept mapped to this description here. We have this notion of functional clusters. So we have a management cluster, an edge cluster, and then we have all our capacity clusters or compute clusters. Management clusters are... It's a vSphere cluster. It's an aggregation of ESXi hosts, configuring a vSphere cluster that will host the OpenStack control plane, right? Or the NSX components, if you're not using VIO, right? We can also hold your vCenter and your date to operational tools, etc. So we want you to define and declare a separate management cluster from your capacity compute cluster. Okay? We have the edge cluster which can be combined with a management cluster. That management cluster that I talked about can double as also as an edge cluster. And in this edge cluster or combined management edge cluster, you're going to put all your OpenStack routers. And we'll tell you in a moment what NSX elements we're leveraging for that. But this edge cluster is where you put all your OpenStack routers. It's always a good idea to have your routers in a dedicated cluster like this, because that will allow you, especially if you're talking about a leaf spine architecture, where you typically reuse VLANs across the different leaves. It will allow you to normalize your compute clusters and the one that is kind of odd and unique because you're trunking external VLANs to communicate with your external users is the edge cluster. So that is the only one that is subject to modifications. Everything else can be standardized. So that is why we recommend, as part of the NSX best practices and also in the plug-in configuration, to have dedicated capacity and resources for your edge services. And like I said earlier, management and edge, if you're dealing with a small environment, can actually be combining a single cluster. If you've seen the NSX technology or if you've been exposed to it, you will know that we have this notion of a transport zone. A transport zone in NSX, and we only support one right now in the current iteration of the plug-in, this picture illustrates what a transport zone is. So you have your compute clusters from one through N here on the left. You have your edge cluster, which like I said will host all your open stack routers. And we have the management cluster where you have the VC infrastructure, the open stack control plane, so a transport zone is a ten entities, an ocean in NSX that defines the diameter of my logical overlays. When I create a network in Neutron, if you're using NSX, one of the options is to create a VX LAN that can be used anywhere in the transport zone by VMs that are anywhere in the transport zone to connect on the same broadcast domain. So that is what a transport zone is. It defines the diameter. So you include clusters in the transport zone, and in doing so you're saying, okay, VMs that are instantiated within these clusters will be able to share the same broadcast domain properties if I connect them to the same VX LAN. So right now in this version of the plug-in, also VIO, we support only one transport zone. And this is an NSX thing. Currently, it's a soft limit, but it's one that should be honored. You can only have 256 hosts in a transport zone. So by consequence, this first iteration of the plug-in, if you're using just one V center and one NSX domain, we can only scale right now to 250 hypervisors. However many VMs you can cram in there. So for most customers, this is more than enough. We're talking about mega scale. This is obviously a very, very small footprint. But it's the first iteration of the plug-in and we're looking to scale that. Okay, another prerequisite, whether you're working in VDS mode or NSX mode for the plug-in, is we need the presence of a virtual distributed switch. How many of you know what a VDS is? VDS, okay. Like probably 50% again. Okay, VDS is a software switch that lives inside ASXI. And the traditional application for VDS or any other V-Sphere software switch has been to connect VMs to VLANs. The VDS offers additional networking services and it's actually the foundation for NSX. So to run NSX, you need a VDS, a virtual distributed switch. So VDS is kind of a gateway drug to NSX or something like that. So we need you to... Am I being recorded? Okay. Okay. Scratch that. But anyway, so VDS is a requirement for the plug-in. You need a virtual distributed switch. And it is distributed because... No, it applies to every hypervisor, but the management of that switch is centralized from the center. And there are two configurations that we support today for that VDS. The one, the easy one, is you create a single VDS and you include all your clusters, management, edge, compute. So basically when you create a port group, which is what we call this layer two, that map to VLANs or VXLAN, when you create a port group for this VDS, it will be seen by all the hosts that are in those clusters, because they're sharing the same VDS. Very simple. There's another option where you create a compute VDS that strives across your compute infrastructure and then a separate VDS for management and edge. Right? So those are the two options today. We're looking to support and add more options in the future. Okay? If you have leaf spine, if you have different configurations, maybe a single VDS is not adequate and you need to break them down by functional cluster, et cetera, et cetera. Okay? So one of the requirements is for management and edge to be on the same VDS. And when I show you how we implement metadata services, you will see why. Okay? So these are the prerequisites. Management, edge, compute clusters, single transfer zone, and then virtual distributed switches and you have two options to pick from or to choose from. Okay. So let's revisit some of the basic workflows that are available in Neutron and the corresponding service that is created in NSX. So when you go in Neutron and you do, let's say that you want to create a multi-tier application with web and app and have some routing services and some security services.  Let's say this is your web tier. When you do that, when you create that Neutron network, you instantiate what we call a logical switch. And this is a VXLAN that exists within the confines of that transfer zone. And then any VM that exists in that transfer zone can connect to that VXLAN. So you go to OpenStack and you launch two VMs and you connect the NIC of those VMs to the network and you have that topology there. If you create another network in Neutron, that will create another VNI, another VXLAN, another logical switch in NSX. This is a Neutron terminology and then the NSX taxonomy. And then you can create additional VMs and put them on that logical switch on that app network. Right now you have two isolated networks. If you enable the HCP for these networks, which you can do from Neutron as well, NSX and the plugin will instantiate one of those edge services gateways that we defined at the beginning and will enable at the HCP scope for these networks. So Neutron, via the plugin, is actually leveraging an NSX component and not the native Neutron the HCP agent that you get with the reference implementation. This is one example of where we're changing or replacing a component of the reference implementation with a more robust component that can actually scale scale better and offer high availability and scalability. Okay? So at the HCP if you enable the HCP in one or more networks, this will leverage one of the NSX edge services gateways. Then if you map what you do during the instance creation, of course, but if you map a VM to a security group in Neutron, this actually leverages and this is perhaps the most valuable reason why you should consider NSX as a replacement or as an alternative to your network layer in your OpenSec Cloud. When you create security groups in Neutron, we're actually using or creating distributed firewall rules in NSX. The distributed firewall is an internal, stateful firewall that is enforced and for security on every hypervisor. So before a packet actually touches the network, the firewall has to make a decision whether to allow it or deny it on the network. So hence the notion of distributed. And it is a stateful firewall. It is not OVS-ACLs, it's nothing like that. It's a stateful firewall inside ESXi that is protecting your VMs using micro segmentation. So security groups map to distributed firewall rules. And finally if you want external connectivity, you're going to need a router, a Neutron router. And that router is created as another ESG, as another NSX service gateway by the plugin. Right? So that router is put on the external network, it gets a floating IP that addresses that external interface and you can also use additional floating IP to create the net rules for outside to inside access. Okay, so these are the basic workflows that are supported in Neutron. There are more options that we're going to go through that. And this is a corresponding element in NSX that is used every time. Okay? Okay, let's take a step back and talk about the options to installing and deploying the plugin, this Neutron plugin for NSX. There's an option, there's the NSX option, and that is the one where we're focusing today. But there's also a VDS mode. And as you can see here in this table, there's a huge difference between the two. Right? So if you want to test the waters, kind of understand how our OpenStack own OpenStack distribution works, you're probably going to want to test it with VDS mode, but just know that the limitations are I mean, there are a lot of limitations. You can essentially just create provider networks and services, that's it. I mean, nothing else, right? And that's done on purpose, right? Because we really believe that the scalability and the enterprise-grade support that you're going to want for your private cloud implementation necessitates something like NSX. And in NSX, you get the full gamut of features. Everything is supported, right? From, you know, not just creating networks that are VLAN-backed or VXLAN-backed, but also layer three services, okay? So again, that's why I'm wearing this, run NSX. So, okay, so if we look at the topology supported in this model, I think I'll show you a picture. I think it'll be better, but I have a summary here of what we can do when you use NSX and we use this VCR, the NSX for VCR plugin. Okay? So option one is you can create multi-tier networks with the ATP services, right? And this networks, this green network or orange network can be VLAN-backed or VXLAN-backed, okay? So you can have VLAN-backed networks also known as provider networks fully instantiated and supported by the plugin if you're not ready operationally for overlays, right? Or you can have VXLAN-backed networks. Topologies are fully supported. You can have the ATP services provided by our Edge Services Gateway for either one of these options and implementations, right? Again, if you have centralized routing services, you create a neutron router, you connect your networks, you get NAT, source NAT by default, right? You can connect to the external network which we call provider space. And we also support NAT topologies, right? Which is table stakes with neutron. You know that in neutron you can disable NAT in this type of applications and, you know, basically have a routable IP address space in your tenant environment, right? So we support that as well. Okay. So that's option number one. Option number two which is here on the right shows the presses of a distributed router. A distributed router is a notion in neutron and it's also supported by NSX that creates optimized traffic flows for east-west communications, right? So if you have a WebVM that wants to talk to a database and they're in the same hypervisor, you don't have to go through the neutron router for that purpose, right? It's a lot more efficient just to have them communicate inside the hypervisor without actually hopping on the network. But from the tenant perspective, you still have a routing hop. If you sit on that WebVM and you do a trace route, you're going to see a routing hop, TTL minus one, all of that will still be there. But it's just that the routing path is optimized. So we support that. We support that in NSX. It's called distributed router and you can create a two-tier topology with a distributed router and a centralized router to have optimized east-west traffic engineering and north-south connectivity, okay? So that is fully supported there. There's a little bit of a caveat and I will talk about it in the next slide. In this model, we only support, I mean, we cannot enforce this. You can do it with VLANs but it is highly recommended that you use distributed routing with VXLAN back networks only. That is where you get scalability. A single distributed router in NSX can give you a thousand layer three interfaces. So, you know, a lot more than a traditional VM approach or what you can do with the layer three, neutral layer three engine, et cetera, right? Okay? And in both cases, we only support static routing because that's the only thing that neutral supports today. Okay? So, just a word of caution here. When you create a distributed topology that uses both a distributed router and a centralized router from a NSX perspective, these are going to be seen as two different routers, right? But neutron, we do some little bit of gymnastics in the back end to represent these two routers as a single one. Okay? So, from a neutron perspective, the distributed router and the centralized routers are just one router, just single UUID that describes it. But in NSX, we're actually using two different routing functions and these are two independent routing entities. So, what that means is that if you have a very curious tenant who starts trace routing, traffic from the inside to the outside, that tenant is going to see two routing hops between tenant space and provider space, right? So, he's probably going to wonder, hey, why do I have two routing hops if I only have one single neutron router that I provision? So, it's just a way we implement it right now. Okay? And it's just a quirk, it's just a cosmetic effect. Okay? Okay, I think it's important to talk a little bit of dynamic routing because as I talk to customers more and more, there's a need for this in the enterprise. In the traditional not traditional, but in the original way in which OpenStack treated or neutron treated tenant networks, NAT was mandatory, right? The use case was overlapping IPs, I give the exact same network address space to my developers and I just reuse that over and over. But as we adapt OpenStack to the enterprise, we're finding that overlapping IPs is really not a very popular use case. Anyone here disagrees with that? Okay. Great. I'm right. So, thank you. So, and the reason for that is that, you know, in the enterprise, right, unless the use case calls for something else, in the enterprise, VMs are long lived kind of, you know, they had VMs, if you will, right? And they're typically known by name, by IP and they can, they there are requirements to access that VM from anywhere to patch it, monitor it, you name it, right? So, typically those VMs will sit on routable IP address space. Therefore, these routers, you know, cannot do NAT, they just need to route. But then that creates a problem of a very dynamic and fluid network environment, which is exactly what NSX provides, right?  If you're doing routable IP address space, you're going to need to tell your, the rest of your infrastructure what those networks are, right?  So, there are multiple ways to solve for this in the absence of that dynamic routing protocol, right? One of the ways is you summarize, aggregate and just do a default route from your provider pointing to the next hub here. But the true solution will come when Neutron finally adds dynamic routing support, right? And we heard today if you were in the Kilo update session I think it's not it's got, I don't know if you know, but it's probably going to be it's not going to be Kilo essentially. That's what I understood from the session this morning. So, but, you know, just know that NSX has that functionality and we're just waiting for Neutron to be able to see it and use it, okay? But if you there's one way, one thing that is not perfect, but NSX can help you accomplish, right? And that is you create a set of NSX gateways outside of OpenStack enabling, you enable dynamic routing between those gateways and your physical infrastructure, right? And then you use the NSX API to inject static routes pointing to tenant space every time a new network is created. So the benefit there is that you don't have to if you have like a old Cisco router or whatever that doesn't have an API instead of like going into a CLI having to configure static routes on physical infrastructure you just make a script that calls NSX and we inject the static route here programmatically, right? You can actually automate that. So there are ways to, you know, use NSX to help you create orchestration. In this case it wouldn't happen inside OpenStack, it happens outside of OpenStack, but it shouldn't break anything, okay? Okay, I only have five minutes so I'm going to speed up a little bit. So in NSX whether you're using a distributed router or a centralized router we require a VM, right? It's just a fact, right? For centralized routing services is that it serves as gateway that I define at the very beginning. For the distributed router, even though this is hypervisor to hypervisor in kernel optimized routing today we require a service VM that can be used with dynamic routing protocols to establish the adjacencies in OSPF or BGP, whatever. We're looking to change that by the way in the next version of NSX that service VM won't be needed in static routing, right? So it's just an optimization there, but today those VMs are needed. So it is important that in that edge cluster where you're going to put all your OpenStack routers you preheat the cluster with pre-configure or pre-provision NSX routers. Why?  You don't want to have to wait for the entire process of deploying a VM without that router. So what we've done is we pre-populate the edge cluster and you can configure how many routers you put in that cluster based on your concurrency and your performance targets. But you can pre-populate that cluster with a bunch of routers and then when in OpenStack you provision a router in NSX all we're doing is reconfiguring an existing router. So that creates that illusion of instantaneous satisfaction. Like I said, we're looking for ways to do that and have more elegant implementations but based on the implementation today it's a requirement pretty much. Unless you don't mind waiting two minutes to get the router that he wants or she wants. We also use the Edge Services Gateway for the ATP services. Like I said, this is one of the elements that we replace from standard neutron implementation. If you have API NIPs because these Edge Services are routers at the end of the day and because we don't support VRFs today, you have to provision another the ATP router. So that's just the way it is. One of the enhancements that we're working on is to add VRF support. We're also working on a bare metal gateway that will use DPDK and there are some multiple work streams that are looking to optimize all this. But today with our VM approach to virtualizing the ATP services and centralized routing services if you have overlapping IPs your only option is to spin up another router and we have intelligence in the plugin that we will evacuate networks and we'll spin up new routers based on the number of networks that you connect to it. It's pretty sophisticated and robust. The point being we use a gateway for the ATP services. Okay, security groups and I talked about this already security groups in OpenStack map to distributed firewall rules in NSX. This is a very, very powerful feature. We have at least two customers that are looking to go into production with our own OpenStack distribution and NSX that are just using security groups. That is the killer app for NSX. They put the VM some VLANs and they use NSX to bring the benefits of microsegmentation to the VM and all the other things that go along with that like redirection to introspection services, etc. So that is an option for you. If you're not ready for overlays, if the networking team has some apprehension about how to operationalize overlays based networks you can just give them their VLANs that they love and still use things like microsegmentation, advanced service redirection, all that by means of the distributed firewall. We also have a feature called Spoof Guard that can be used. I'm just going to bypass this.  We're using it for some other reasons but it is an NSX feature that we heavily, heavily leverage as part of our plugin integration, sorry. Okay, so finally to wrap it up, just a word on date to management and operations. This is not directly related to the plugin. These are actually tools and capabilities that can be used by any OpenStack implementation. But just a reminder that it's not just about being able to provision VMs. It's what do I do with all this after I have OpenStack? How do I troubleshoot it? How do I characterize performance? How do I dimension for growth? So we have instrumentation native to our portfolio that can help you do that. One is our CM tool called Realize Log Insight that have 56 predefined dashboards that can help you troubleshoot and characterize performance in an OpenStack cloud. And if you operate an OpenStack cloud you will know that doing that without some form of syslog aggregation it's impossible. It's just a non-starter. So that is Realize Log Insight. Then on the analytics side we have Realize Operations which is an analytics engine that can help you simulate capacity understand how growth rates and also troubleshoot and detect alerts and gaps security gaps and configuration gaps in your infrastructure. And we're monitoring not just the infrastructure, we're monitoring processes inside your OpenStack control plane like all the different Nova services, etc. And we're reporting that to an aggregation dashboard that will show you topologies, will show you the layout of your OpenStack tenants and the performance and utilization of each one. And finally there's one that I didn't include but it can also help you with the metering and all the showback, chargeback and shameback of an OpenStack cloud without having to resort to like a kilometer or something like that and that is called Realize Business. So the whole point here and I will conclude my session with that is that we offer if you're invested in vSphere as your virtualization layer, if you're looking to implement a software-defined network solution with NSX, this plugin can help you integrate and get to that enterprise-grade cloud and all these other satellite services can actually let you operate this cloud. Okay, so thank you so much for your time. I'm going to take a minute. I have time for questions. Any questions? Are we sharing the slides? Yes, we are. Yes, absolutely. I actually have it in my backup I think and NSX today, the question is can you talk about IPv6 support? We're also subject to the gaps in Neutron. Where IPv6 is and it's not supported I should say in OpenStack. But in NSX IPv6 support is also fragmented. So we don't have, we have for example IPv6 routing we support that but we don't support DHCPv6 we don't support IPv6 in our distributed router. So there's a matrix of support and obviously that's going to be important, right? In the current implementation of the plugin, we decided to basically call it what it is and we said no IPv6 support in the 1.0. Yes, question. Hi, I have a quick question. Thanks Marcus, this was really interesting. This is a question about your slide 9 or 10 where you have different blocks of OpenStack talking to your vSphere block to the Neutron. So for anybody who is planning to take OpenStack to production sooner or later they're going to come up with, come to the terms with the fact that you want line rate speed and probably leverage your existing networking gear. So if I want to do 40 gig, why doesn't VMware ecosystem allow the vCenter block to connect through the Neutron plugin and use, say, Cisco Nexus 7K underneath? Yeah. I think I understand the question is why does the plugin talk to NSX manager and not just my physical switch? Yes, that's one part but what if you didn't mandate me to use NSX but you still supported having vCenter talk to your OpenStack cloud through your Neutron server plugin? And then from there just go to the physical switches. I think that's a very interesting question but the answer is would be we'd try that by the way. We'd try that. Well, that's what Martin initially wanted. So I installed OpenFlow in all the switches and let any control plane manage all the switches and then all these vendors said no. To try to get to that I mean it's difficult so where you're going to see is monolithic solutions like ours that are just trying to optimize the interactions with our own products. Having said that there's a program in NSX to support the top of rack management of the top of rack topologies and we're going to announce support with Arista, HP, Dell, Cumulus, Burkait, I mean very, very soon. So that could be a way to get to there. It is in your roadmap. Yeah, it's actually committed and it's coming like in a matter of weeks. Okay, thank you so much again for your time. I'm being asked to end it. Thank you.


Try my new microphone. I'm gonna see if I can hold it right. Guys, let me tell you one of the best player moves in the book. Okay? Take up a cool hobby. What are some cool hobbies? Acoustic guitar? Great hobby. Cooking? Great hobby. Painting? Not so much. That's more here to mess, man. But, you know, just becoming that, you know, reaching out to your artsy, fartsy kind of bohemian, Quentin and the best man kind of thing. Think about being a corporate raider by the day then on the weekends going to the great indie coffee house in the bohemian side of town and the kind of women you'd run into. So, yeah, man, great skills that I learned how to do. Being a bartender. Glad I had that in my repertoire. Knowing how to make actual cappuccino. Great. That's a dope skill. But if I were the young dude, if I were out there today, man, I would learn how to cook at least six dishes and go take some bona fide cooking classes and get some real, you know, cutlery and things like that.  But don't underestimate the ability to whip out a guitar and just play some chords and just hum. Boy, if you can't sing, just speak. And write and just speak to poetry, man. Panties fall. Panties fall with the quicks. But by far, the best, cool hobby to get into 2020 and beyond is photography. With social media the way it is today. Let me just sit there. I'm about to get it. With social media the way it is, with so many people wanting to be seen, you just look at what happens when you see me out vlogging and walking in the mall or something. People always want to jump on camera, get on camera, get on camera.   And if you actually learn how to shoot some amateur photos and learn how to color grade, it, it is, oh my God, I'm just bugging because I'm like, if I were you guys, I'd be killing it. Like when I was in school, in college, I used to be a tutor, right? Tutoring in chemistry.  Say that again, women are always looking for plausible deniability to be in your presence.  I love this. There's this cool spot in town. You'd be great for this photo concept to have that lowest women's guards down and gets into their vanity. I'm getting excited about this because it's so true.  Photography is a great hobby to pick up and watch how it works. Photography and even photography and videography, because you can actually show them the product right then. Now, here's the trick. You need to know how to shoot, man. You need to know how to do some basic shots. You need to do some industry terms. What kind of shooter are you? I'm a DSLR. I'm a full frame eye. Pick your camera. I'm a Canon. I'm a Sony. Not many Nikon people don't look, but if you missed like video, if you were just trying to go get like a red digital camera, too expensive for trust. And if you learn how to do a quick video edit, can you imagine how many of these little Instagram chicks would love to see you shoot some cool pictures and then throw a quick color grade on there, throw a quick LUT. They'll learn that too. Throw a quick LUT on and they'll be like, oh, that look cool. It ain't even fair. It ain't even fair that you, that y'all can get out here and do this, man. And you can use the camera to vlog, to make your own videos. Trust me, dude. A cool hobby, cool hobby will do so much for you. Hell, leave it on your own suit, Saturdays.   Boom. You're ready to go. Trust you, Godfather. Trust you especially since I moved here to Atlanta. Walking around with my camera and my gear has been insane, insane, and fricking insane. And I'm on this side of the camera. You just got them sit up there like smoothing and moving and they tooting the bed. Fellas, trust me. Trust me, trust me, trust me. Cool hobbies for the win. Peace.


So I'm here with G. LaCroix from LearnLinux.tv. Hello. And this is going on both for channels. So if you're watching this on LearnLinux TV, you already know where we're at. We'll have links to each other's channels in the show notes here. So if you're checking mine, check out his channel and vice versa.  And people expect answers like maybe Debian, Arch, or Ubuntu. It's actually RetroPie. And that's what I wanted to go over. I've been wanting to do a video about this for a long time. I've really never been able to because I just didn't really know how to do this. But basically, Tom knows a lot more about this kind of stuff than I do. He actually taught me everything I know about video editing. So if you notice on my channel, it's actually slightly more professional now. That's actually why. Early on in my channel, everything was done in one take and I was professionally done. So he has to know how he set up this little environment for us to record. We thought some cross channel promotion would be cool because this is a very fun topic. It goes in line with his channel about how tos and tech and gadgets. And also mine, it's a Linux distribution technically. So it's something that I wanted to do a video about as well. Yeah, and I learned Tmux from this guy, everything I know about Tmux completely and a lot of other. He covers some of the in-depth sysadmin stuff. And so you'll see some more cross promotion here. But this is a hardware part because I like to RetroPie and this guy did way better than I did. I just talked about having one. This guy, he got the right hardware for it. So we're gonna get right into this in a second, but I am a big retro gaming collector. I have physical games. I'm not a freeloader that just runs ROMs. And I'm not necessarily seeing there's anything wrong with that, but I actually have the physical hardware. Yeah, Nintendo might have a problem with that. But sometimes there's some challenges with this stuff, like save batteries that don't work in cartridges anymore, disks that no longer read, systems that no longer boot media. RetroPie is very useful to keep the retro games alive. So I've been very passionate about setting this up and getting it done perfectly fine. So in this video, I'm going to show you specific hardware. So I'm not gonna have a bunch of different cases to show you the pluses and minuses of each. I'm gonna show you one specific case, one controller, obviously the Raspberry Pi that powers the whole thing. So I'm gonna give you what I recommend are the best pieces of hardware to combine to get the best possible experience. So getting right into that, right here, I actually have a case and controller that comes in one box. This is by RetroFlag. It'll be in the show notes. And so it comes with a really good controller.  Some of them are pretty good. The Buffalo one has been very good as well. But the one included in here is very good. So I'm gonna do an unboxing of this, but this is actually the case. And I'm gonna go ahead and go ahead and open it right now. Show you what it comes with. So here we have the controller. Try to line this up to the cameras here that it comes with. I'll show this off first. So this is basically the, obviously it's modeled after a Super Nintendo. In this case Super Famicom because it's got the colored buttons which are specific to the Japanese market. Maybe European too, I don't remember. So you can also buy the English Super Nintendo version of this as well, which will include the color scheme from the English version. The case is functionally exactly the same. But this is a solid controller. So when you plug this into a Linux machine, for example, it actually comes up as a Xbox 360 controller. So I don't know what they did, but something in the circuit board tells you, this is an Xbox controller. It's clearly not an Xbox controller. It doesn't look anything like that. But this is something that, it's just a really great build quality. It feels, you can feel it yourself. It doesn't feel so light. It feels kind of heavy like the original controller did. Buttons, the key travel. It's really solid and I've seen that before. Some of them, especially like the start select buttons felt like I was going to break them like I was bending plastic. But this, I could have some good time on that. Yeah, it's very, very solid. So in one, in the main point here is this case. This case is cool. Yeah, so this case is modeled after the Super Famicom or the European Super Nintendo, which had this form factor, the English Super Nintendo had its own look in its own market. And you could buy one or the other. So I'll have links to both. Again, functionally, they're exactly the same. There's an Eject button. Yep, the Eject button is for storing SD cards. Yes. So you could put your SD cards in here and store them. Looks kind of weird. I'd be kind of afraid to close this on top of an SD card if it wasn't exactly something that I put it in there. But I don't really have a use case for that, but the case is really good. Now this case has something called Safe Shutdown and Safe Restart. And what that allows you to do is you could actually turn this off. Up is on. If I turn it off and I didn't shut down RetroPie, this actually runs a script and it safely shuts it down for you. The power light will blink. So the power light's right here. It'll start flashing to let you know that it's shutting down. And then once it's confirmed it's shut down or the timer goes off, however it works, then it cuts the power. So to take a look at how that works, I'm gonna open the case. And right here on this little corner, upper left, or depending which way the camera is facing, but this actually intercepts the power button or the power cord. So the power cord goes in here.  It actually goes here, which goes into this little chip, which then connects to the circuit board. I'm not really sure how exactly that works. For some reason it knows to keep power long enough for it to shut down. That's one feature that this has that's really amazing really the reason why I recommend this case because the issue becomes, if you give this to a family member and they don't know much about computers or something and they don't know to shut it down. So if you're using a different case and they just unplug it, well there might be some file system corruption because they didn't shut it down properly. So this case makes the experience a little bit more foolproof. Yeah, it actually initiates a shutdown script when you hit this. So moving that button is a process where we get the shutdown script. And it looks like we have two USBs in here. So besides the connector, we have two USBs that would interface with. So there's the front USB. So you look how the controller ports would normally be right here. So on the inside these connect to the Raspberry Pi on the inside. And that just maps the controller ports up here. So actually plug your controller in to port. And it's labeled one and two but retro Pi is not gonna know which one you plugged it into. So if I'm not mistaken, the order whether you're on player one or player two is just the order in which you plugged them in. So not necessarily gonna correlate with this. Yeah, it's detect order. Detect order, exactly. So another thing I wanna mention too is that there's an NES version of this. So it's modeled after the Nintendo Entertainment System has the same features, safe shutdown. I don't recommend it because I have seen personally because I own this case, power distribution issues where it'll have random resets. It'll lose power. You get the little power indicator on the actual display telling you that the power is not working or not enough. And I'm not really sure why other people have complained about this too. Maybe they'll get it fixed. But don't buy that one because there's issues and the issues might just be the plastic. So you'll see that there's little cutouts for the cutout right here for the power. That's not very far recessed but one of the theories with the NES cases that's too deep and it can't make a connection. Yeah. And it's a prop, it could be just a mold issue where when they did the injection molding that it's just, it's a hair thicker but you're right, it's recessed in there for the USB power that could be enough to cause the power issues on there. And it doesn't seem like they would use different circuitry for each one, but you know, that's right. We can get the, this is referred to as the Famicom one you said. The Super Famicom. Yeah, Super Famicom one. So. I don't know how they label it on the Amazon. We'll make sure we leave you a link to the right one. So another thing to show too is that there's this little switch on the bottom. And it's really, it's marked on here safe shutdown. So it's a no brainer. You can, that's an ability to bypass it. So it defaults to off. So the safe shutdown feature, you actually need a plugin for that. We can show you how to do that in this video. But in order to take advantage of that feature, you actually have to turn this on in order for that to work. And you have to have the plugin. Both things have to be in place for that feature to work. Otherwise, if not, and you shut, you hit the power button, it's literally going to cut the power abruptly the same as if you just pull the power cord out of the back. So that has to be set up in order for that to work properly. So that's another thing to keep in mind. So another thing, obviously, I have a generic power cord here. I just ordered one from KanaKit. And it's very, you need a very specific power cord ampage. It's like 2.5 amp for the Raspberry Pi 3. If you don't have that, you'll get the power issues and maybe your games don't run as well or you have, I'm not sure what all the issues are, but it's just not going to run efficiently. And you'll stress out some of the weaker adapters not all of your USB adapters have 2.5, some of them are only 1.5 and two. So this is important. It's not that expensive. Just order the one for the Raspberry Pi. I think there's like four or five, I think they're like $4 or $5 or less than 10, something like that. And it's rated for the power that you have. You don't want to just get an Android charger or something and just think it's going to work. It's possible it could. It's also possible it might not. And it could lead to file corruption if it's not being powered. So you definitely want to make sure 2.5 amp power cord for that. And then of course I have the Raspberry Pi 3 which is the brains of the operation. I'm not very good at my unboxing here. I'm carrying the box. But basically here we have the Raspberry Pi 3 board which is going to be what, you know, the magical thing that makes it all work. SD card goes here on the bottom, which I also brought one with me. I brought a 128 gig SD card. This is overkill. You only need eight or 16 and you're probably fine. I use 128 because I run a lot of PS1 games. So those things are ginormous. So if you're not doing that, then you really don't need 128. So it's just 128. Yeah that comes on a preference of how many games you plan to load. Now do you leave the chip at the stock speed or do you increase the speed on the chip a little bit? I haven't done that. I haven't done any overclocking. I'm not really an overclocking kind of person because I'm more, I want the long term stability. I don't want it to basically over time wear out the board even though they're inexpensive. And I'm not really sure how much of a performance increase you can get.  And I've seen many YouTube videos. They will show you, well, this is what you do for how to increase the performance of Nintendo 64. I'm telling you, I have spent hours on YouTube. As of today, I can guarantee you I've watched every single one of these videos that have claimed to improve Nintendo 64 performance. They do not work. Now I do feel like they did work when they were recorded. So I don't feel like these videos are misleading anybody but they literally in RetroPie newer versions they disabled some of the features that these YouTubers were actually utilizing to get that performance boost. So tread carefully if you're doing anything newer like than PS1, PS1 for me works great. I have no problems with it. Anything newer than that though, you're gonna actually have possibly some issues. So hopefully one day that'll get better. I know Nintendo will probably do like a Nintendo 64 classic console. I'm sure as soon as they do that all the hackers are gonna get ahold of it and they're gonna reverse engineer it the Nintendo 64 emulation will be completely flawless by then but until now I don't recommend running PlayStation portable or Nintendo 64.  I've run Nintendo Game Boy, Game Boy Color, Game Boy Advance, Genesis, Sega CD, 32X, PS1, Super Nintendo, Virtual Voting, PC Engine, I've run PC Engine mainly for Castlevania Rondo of Blood because it's the best one. I like Bonk. Yeah and I have that on there too. So all those games run flawlessly but it's when you get the further up the 90s you go the less the performance will be. So with that said that's basically everything you need. We'll have links to all the stuff you need and to buy all this, to get all the stuff you need for it. I did when I built my first RetroPie not that I overclocked it but I knew I potentially might because I'd seen it suggested for a lot of people. If you, I can leave links to probably the heat sink kit. They still have a heat sink kit to go on and it's really inexpensive. It was like a couple dollars when you're buying the kit so I wouldn't have glued them on there but I've never overclocked it. My RetroPie is probably two years old now. Not kind of what I've had no problem with it. Never a problem putting a heat sink on something. I don't use it daily but it probably may not hurt to put a heat sink to dissipate it. It's not like it needs a fan but just generally because you're getting the heat away from the chip, they're a little stick on so we don't have them for this project but you can always get there to be in better shape. You can run a fan on it. I could tell you this. I have heat sinks on some of them and some of them not. I have multiple of these. This will probably be like my fourth or fifth RetroPie in my fleet right now. I have some of them have it, some of them don't. I've not noticed anything really different. I have run some fans from time to time. Again, I never really noticed much of a benefit but my mindset is if you can dissipate the heat, you may as well because it's only going to help you. It's never going to hurt you. So if you can do that, feel free but we're not going to include that here in this setup here. So. All right. We're ready to assemble it now. We're ready to assemble it. All right. Okay, so now we're ready to assemble. But before we do, I want to let you guys know about a very important first step before you get started. There is a screwdriver that's actually included with the kit. When you buy the case with the controller you also get the screwdriver as well. So the first step is that you toss this in your nearest trash receptacle and dispose of it. Do not use it because, but I don't know why but this screwdriver is so cheap. It will strip your screws. They will be hard to get off. Do not use it. Very poor quality. It's just, it's a disaster. There we go. There we go. Get rid of it. So get a actual decent Phillips screwdriver because that's what you're going to need. And for those of you who didn't recognize this these are the screwdrivers that you can get at Harbor Freight. So shockingly the Harbor Freight screwdrivers are quite a notch above that one. Yes. So don't use the one that comes with it. Strips, it's bad. So I'm going to grab, I'm going to get this Raspberry Pi board. I'm going to go ahead and lay this in here. So I'm just going to move the wires out of the way. So it lays this way. And what you'll notice is that the, once I actually get it lined in, lined up here we go. You'll notice that everything is kind of recessed right here. We're not worried about that yet. The ports in the back will have to line up. So you can see that they do power, HDMI, audio, everything lines up. So the first thing you're going to do is you're going to get these black screws that it comes with. And what you're going to do is then proceed to screw the Raspberry Pi into the board. And make sure you leave this top screw empty so nothing goes here. Now that I actually plugged in the USB cables this time now I can actually proceed to put the screws in. Remember that USB cables, then screw it. USB cables and then screw it in, yep. So the next thing that we want to do is make the decision whether or not we want to use the safe shutdown. So just so you don't forget right now it's off. That's the default. I'm going to flip this to on. It is a feature that I want to use. And now we need to connect the actual circuit board here at the front to the Raspberry Pi. So you want to make sure that you get this in there right. There is a little instruction sheet that's included with this. So basically you could just look at that. But what you're looking for, there's two of these blank little holes right here. And they face toward the network port. Okay. So basically just make sure that we line this up perfectly. Push that down in there. At that point everything from the board level is installed. Now what you want to do is make sure that the power is off. So I have had this little port or this switch here flipped down. Just going to make sure that because when you put on the top cover you basically want to make sure that lines up. So I'm going to just kind of, this is kind of awkward here because this sticks right up and it's really hard to get this in there. So you got to kind of try your best to comfortably push this down to make room to actually get the case on. And at this point, we also have this little cover. I'll go over that in a minute. So we're just going to leave that off for now. Just kind of press it firmly and you'll see that all the ports here should line up. We have our network port and two more USBs over here on the other side. That's actually the side of the board. So directly to the side of the board. So at that point I'm just going to turn it upside down and then I'm going to screw in these little silver screws onto the bottom to basically secure it. So now I have all the screws in. Now there's one last thing to do.  You'll notice though that two of the recessed things here actually covering the screws. So you should not actually put these in until you've had a chance to boot this up, test it out, make sure you have everything wired in because it's going to be really hard to get those back up. I have no idea why they decided it is a good idea to do that. But whatever, you know, it's a good case. Otherwise just don't put these in just yet. Just kind of wait a bit and then test it out, make sure the safe shutdown works and all those different features work before you actually do that. In case you plug something in wrong. Which I have done twice my first time setting this up. So. All right, and we have a card here already prepared with Etcher. Yeah. We'll insert right here. Like it's pretty easy to get the link. We'll give a link to where you can get the image and you download and use Etcher to break the image to the SD card. There's a little groove right here on the side. Yep. That's where the SD card goes. I already have all the ROMs and everything I need on here, but we'll show you how to create one from scratch in just a moment. So I'm going to go ahead and slide this in there. Just push it in. So now the SD card is installed and this guy's actually ready to boot up. So we'll start with etcher.io and I'll leave links to this in the description below. So you can download etcher for Linux, Windows or Mac and it's great utility for flashing images to thumb drives or even SD cards in the case here for the RetroPi. And then retropi.org.uk slash download. Leave a link to this as well. This is where you can get the Raspberry Pi zero image or the Raspberry Pi two or three image. We're using a Raspberry Pi three. So I download this one here. Then here's what it looks like to run etcher. We're going to select the image. I'm going to go over here to downloads. Select RetroPi open. I have a flash disk in here and hit flash and it copies the image to there. And yes, I know I did this for an example because the flash disk I happen to put in is a one gig and this is a two gig image. And like Jay had mentioned, if you really want to put a lot of ROMs in here, you're going to want to get a larger card like a 64 or 128 so it can accommodate all the different games you may want to load on there. And no, don't ask where to download the games here on your own for that. So I plugged it in and the magic is happening. Beware of the invasion. Is that something custom you did? That's actually a custom splash screen that you can download within RetroPi. There's an extra splash screens thing in the settings. And then you basically just, yeah, you just basically set it to that. There's a bunch, over a hundred of them in there. That's neat. It's trying to access my local network. Which we have no networking turn on on us, so. Yeah, so if it doesn't get an IP address if you've already set up networking, it's going to keep trying and trying and eventually it fails. So let's go ahead and try some MAME. So I have a lot of games that I'm into here. So I'm a big Mortal Kombat fan. So of course that's what I'm going to gravitate to. So I'll go ahead and do that. You got King of Fighters too, that's great. Oh yeah, Samurai Showdown. It's a great one for arcade fighters. Street Fighter of course without everybody who has anything arcade has Street Fighter by default. So I don't even mention it. I spent so many quarters with this game. This glitch right here is perfectly normal with this game. It's a MAME issue. This happens on all platforms with this specific game that only in that one specific spot. Doesn't always happen, but. All right. That's cool. And that's it, you are on your retro pi game. That's cool. So just a couple other things I've set up here just to show you guys. So that was arcade and then we, I have all these systems set up. So pretty much everything, you know, that's a value to the 90s, at least most of them. Some of these I won't show you because, you know, Nintendo. But, whoops. Yeah, this controller's got a little bit of a sticky D-pad here. But basically here's PlayStation. So I have all these games set up. And yes, they all work. I've tried every single one of them. I have had no performance issues with any one of these games at all. So if I wanted to load up Final Fantasy VII, for example, it works. And I even downloaded these games such that you can change disks and multi-disk games without any issues. So actually hitting the menu, it'll actually allow you to switch disks. Oh, that's nice.  It's kind of interesting to me, like this game when it came out blew me away. I thought it was like the best looking game ever. And I was so fascinated by it. And to now be playing it on what's considered a retro gaming solution is actually kind of fascinating to me. Because when this came out, everybody was talking about it. I bought it on release day. It took it home. My entire weekends were like spent doing nothing but playing this game. It holds up pretty well.  There's pre-rendered environments, but the retro pie is keeping up with it, no problem. And I could tell you, now getting too much of it into the gameplay, even PlayStation 1, which you think might be a performance bottleneck on such slower hardware, it works perfectly fine. I've had no issues working so far with any of the games that I've tested. Yeah, this is great. Who can get shot by a machine gun twice and still be standing by a fantasy? That's pretty cool. All right. So thanks for tuning in. We're gonna go play games now.  All right, thanks. Thank you.


I beat I beat Denver in a one-on-one. I beat Denver 1v1 in 2k I love you down there. Okay, so quick story time me and Denver boy one-on-one in a video and I Actually did so I'm feeling pretty good right now. I feel like I'm on a hot streak with my life I really wasn't gonna record wheel of 2k today, but knowing that I clapped his absolute sheets I think now more than ever is the time to play now the pack market is absolute garbage these 20th anniversary packs are in store I am daily uploading this series right now So this will probably still be in the store when you see this video, but either way I'm hoping I don't get a wheel spin that has me open in packs I'm hoping I can get something that will let me trade out Kawhi Leonard for maybe uh, maybe I could get a pack of punch And I could get galaxy opal Kobe and the new Jordan down or I could get an equal or worse and trade out Kawhi for Additionally, I do need a better backup shooting guard I think I want a better starting power forward and backup power forward and honestly Jermaine O'Neill is kind of short for the center position He keeps getting bullied. So there's lots to do, but without I'm listening to the game audio this time just so I can see if I can get the buzzer beaters and shit I always mess that up by not doing it. It looks like Oh Our 2k wheel gives us any 95 to 98 player, but they had to have been in NBA free agency I know free agency is over and that's like so many players in the league right now I'm kind of torn who I want here. You know what actually kind of want. I want the angel Russell He does have a big diamond I would put him in where Kobe is and he would be like the shooting guard or point and Russ could go I actually want to do that because he has a galaxy opal 2 and eventually I'd like to get that actually if I'm gonna do that I might as well get Kyrie.  Oh my god. I'm a hundred percent getting that I know y'all today's video is sponsored by one of my favorite sponsors on this channel raid shadow legends If you're not familiar raid is a brand new totally free-to-play RPG game on your phone It's getting huge by the way almost 10 million people have downloaded this game in the past three months There's an awesome storyline with amazing graphics where you can fight through dungeons You can play other people head-to-head online There is awesome champions to collect and again like I said, it's totally free It has almost flawless reviews on the app store with over 200,000 reviews You can see that for yourself. Also, there's an awesome rewards program for new players right now You can get a daily login reward bonus for the first 90 days of playing real quick I want to show you some of my favorite champions. So I maxed out a lot of them But this is my war priest right here. She is a savage. I love her this guy's kale He's probably my best champion I wish I could have hair like that and then I just recently got the sorcerers right here. I like her Yeah, definitely. I've been sponsoring raid for about four months now So I generally do love this game and it's always on my phone You guys got to check it out. The link is in the top of the description Additionally, if you click that link you're gonna get 50,000 free silver to start and an epic champion I know that might not make sense right now, but trust me that is a huge head start in this game You're gonna want to do that. You got to check this out guys games of blast link in the top of the description I'll see you there. Enjoy the rest of the deal. I actually just got a motor city jersey, but it's Blake Griffin's not D Roses. I almost got D roses motor city jersey. I decided to do Griffin instead Soon me. All right, my free agent pick up is Derek Rose. Technically, let's throwback it It counts. It's all the same. I'm pumped. This is gonna be dope All right, so he's not gonna start because there's no way I can just if I starting him over the step career However, potentially down the line if I can get the galaxy opal Derek Rose if I can upgrade this Derek Rose into the galaxy Opal then I would consider it. All right. I like this. This looks good to me So we've got two losses because I took those two straight heartbreaker losses We got a win last game though And hopefully we can secure a win again here and I would never forget a 2k challenge real after forgetting it that one time I'd never forget it again. Our challenge is going to go. It's gonna be 30 plus. It's gonna be 30 plus 30 plus points any player. So Somebody on my team has to completely go off. I really hope we can do that I usually spread out my scoring really well. So this is gonna be really hard, but hopefully we can get it I'm assuming Kerry will get it if it's possible and the opponent squad doesn't look too insane He's got galaxy opal Kobe galaxy opal Tim Duncan I kind of a feeling that my yelming is gonna have a field day with this Tim Duncan. That's when I'm helping We're playing in the dungeon for the fourth straight game, too. That's something that's exciting stuff. Okay. All right, Michael Jordan Okay, got the screen coming. Ooh, I should have got that out to y'all. Oh Y'all is so open completely missed him dude. Y'all Thank you very much Holy shit, it's Michael Jordan on y'all in the post. That's an animal every single time. All right, let's see a screen dirt Got it. Ooh got a switch That means That means that no one's on y'all me if anything I'm scoring 30 with y'all me now that I think about it He's got five already. It's very doable. I don't want to force it to the point where I don't take open shot Green Let's go Team ac you're you're homeless.  Oh I'm feeling I'm gonna get scored on a lot by that Get out of here. It's not DM me up so close Okay, good penetration Y'all mings got it over to Dirk see I could have been greedy and tried to take a bad shot with y'all to hit My 30 plus but I was smart. I took the easy bucket Good screen there. Oh, nobody going on dirt See I need y'all to do those. I need y'all to come up for the screen so you can get the buckets Oh, give me the ball illegal screen That's the first time I think I've ever seen someone else get it called on them Uh-oh, he's gonna pull up. He's gonna pull up somebody somebody's gotta be open We got way too many people in the paint 12 to 12. It's looking like we got a good game on our hands boys This is definitely some solid competition.  Hit that hit that Oh Oh my god And one I also know this release really well because I used to play with this in 2k 14 all the time There it is. Hey, what did I tell you? Belle Delphine is a thought Good db rose here comes the screen. He just shit on me Oh, give it to kevin love Easy 1716 queen screen Lonzo ball taking the contested tune he drills it This game is getting away from us Ooh wide open curry at the top of the key We're gonna need we're gonna need a lot more of that if we're gonna get back in this All right, another wide open free for curry. All right, y'all Yelp got him jumping 34 24 all these wide open under there.  So I'm doing the same and he's just drilling threes in my face I guess come here. Y'all come here.  Y'all with 12 got to get him 30, especially because okay And we got the rip up to y'all run the court Give me an animal. That's that should be a playground.  Hopefully I can get y'all 30 points and it won't matter all too much. Jesus This is what I'm talking about. Y'all you're a god That's a good right back Toss it up Not what I meant to do, but you have to get that bucket. Let's go. Dude. I'm getting a ran.  I'm getting wrecked. This guy's really good He scored like 20 points with Lonzo off the bench Dude, Jordan's just trying to embarrass my whole team for no reason Over to kawaii took a long two on accident. Hey, I just cut it to 13 It was a lot uglier than that a while ago Okay, and Jordan just got a rip.  This is just like randomly became a game curry Just posterized lesbruck. It's a nine point game somehow I just scored eight uncontested there in that last 35.  It's a nine point game We just got to keep getting stops and that's one right there up to Jordan. No No, yes Let's go double cut your verse. It's a seven point game. Good. Shit. That's another turnover Yup, absolutely We love it if you want to do that And lebron on turk in the post. No, thank you 60 to 55 our opponent is crumbling. Looks like I'm not gonna get the Yao Ming thing. Uh-uh, uh-uh And I'm not gonna get the win. Okay Okay Curry's kind of open Over to y'all Let's go 24 for y'all. Can I score six points with y'all in a minute 30? Come here y'all. Come here y'all Y'all going up strong That's 26 for y'all. I need four more and five points to win the game. There's too much going on right now Let's get y'all in that paint. Oh, no, I gotta take it free bucket. I gotta take it 70 to 67. Come on y'all Oh, I should have taken that y'all's wide open great life 28 points. I need two more points of y'all and I'm down by three get it to y'all. Yes 30 oh wait, no, no go go go go. How what are you doing foul him? That happened to me that other game too for some reason this was not working Lonzo hits two Honestly, this is kind of a close.  Good try, but I don't think we're gonna get it. Yeah I'm honestly just really really happy. We got 30 with y'all, dude We take that out But in my books, it is a win We got 30 points with me y'all and that means our challenge is complete We had to spin the loser's wheel and we do not get to keep Derek Rose I also lost my series. So we're re say next episode boys. We'll be restarting the series Whatever this lands on is the sad forfeit that we have to add to the team for losing that game But I'll recuperate it with the 20 kmT we get downgrade. Okay, that's actually and I almost got removed most recent player Which would have been really bad, which I think would have been quiet Um, but we get downgrade one player. I just have to get a worse version of one player on the squad It also cannot be 11 12 or 13. So I have to get a worse version of I think there's a 94 kobe. I might have just gotten saved by that See we grabbed the 94 kobe, but then I'm gonna instantly replace him. So this yeah, this is perfect for a whopping 5000 mt We get ourselves 94 diamond kobe. So we'll have to take the 95 I'll put in the 94 But before I go anywhere, I'm getting myself a new backup shooting guard. I have 20 kmT to spend I want Clyde Drexler. Oh my god. I want Clyde Drexler. So bad. I already have Clyde Drexler in my collections I was using him earlier. He's less than 20 kmT. So I'm just gonna use the one I have obviously because I can't buy another one All right, I like that a lot still want to get Kauai out of that dude. Kauai always plays like a bomb I gotta get Kauai out of there. Uh, Kevin loves gotta go and Dirk. I'm sorry Dirk. I love you But you kind of have to go too. All right boys. Um, that's it for this episode I'm sorry for taking an L But I think it worked out pretty well in our favor Additionally next episode if I complete that challenge wheel again That means that we get 30k to spend from completing the challenge So this team could start it really can't get that much crazy better, but it could start getting real insane real quick That's it for now. Thanks for watching guys. I'll see you guys in next episode. Peace out