I'd like to thank everybody who is joining us today. And welcome to today's CNCF webinar, Challenges in Deploying Kubernetes on Hyperconverged Infrastructures. So two things, yeah, we'll go back, let me do our KubeCon slide. I do want to also remind everybody that KubeCon, CloudNativeCon, North America are flagship event and it is coming up in November in San Diego. It should still be very sunny, lovely in November. And this is, as many of you who have attended before, this is a time for the community to come together to further their education in advanced CloudNative computing. You can go to kubecon.io for more information, get your ticket, and we're expecting about 12,000 people and to sell that out. So before we get started, I'd like to also go through a few housekeeping items. During the webinar, you are not able to talk as an attendee. There is a Q&A box at the bottom of your screen. Please feel free to drop your questions in there. And the team from Diamante will go ahead and answer them throughout the presentation. Now with that, I would like to kick it over to Narendh, who is going to introduce today's presenters and kick off the webinar. Thanks, Kim. Good morning, good afternoon, good evening, folks, wherever you are, greetings. So I am Narendh Narendra, Director of Product Marketing at Diamante, along with me, I have Naveen Seth, who is the Founding Engineer at Diamante and Hiral Patel, Founding Engineer at Diamante. All right, so today, we're going to take you through the background of AWS EC2 Evolution as an example. Hi, Naveen here, and I'll be discussing the challenges and some of the option solution technologies available from network and storage and when this transformation goes, is cloud native applications that's happening and this is from context of HCI platform. Hi, this is Hiral, and at the last I'll do a demo for deploying a container workload and also the virtualize KVM workload onto the same HCI infrastructure using the same Kubernetes cluster and we'll wrap up with Q&A. All right, thank you, Hiral. So let's take you through some evolution here for the next few minutes. Credit goes to the two stalwarts at Amazon Web Services, also known as AWS Jerry Hargrove, who is very famously known as AWS Geek, looking him up as AWS Geek and you'll find lots and lots and lots of beautiful pictures about how things work, how things are architected at AWS and this picture, this is a part of the picture from one of Jerry Hargrove's drawings. Credit also goes to James Hamilton, who is a distinguished engineer at AWS, been at AWS forever and there's a bunch of publications that he has done through MB Drona and others that we're gonna use today to walk you through some of the evolutionary aspects of the EC2 compute instance at AWS. So it all began this way for all of us, anybody in IT, this is a standard picture, right? And this is the crawl phase of what Jerry calls it as for an Amazon compute instance and this is specifically Amazon EC2 instance and if you go back to history, the first incarnation of EC2 came about in 2006, all right? And up to 2013, this was the constant picture for any compute node or host at AWS. And if you look at this picture, it's got hardware, on top of hardware is software, software that runs networking, that runs storage, provides management, security, monitoring. There is a layer of hypervisor and on top of the hypervisor, you deploy virtual machines which are also known as instances. But in effect from 2006 all the way to about 2013, if you look at what James Hamilton has written, he basically sums it up in one sentence which is networking is in effect in the way and blocking the efficient optimization of valuable resources in the data center. So why is this? A server is the most expensive component in a data center, a server and all the components that go into a server. And think about it, every data center for a public cloud provider like AWS, there's hundreds and hundreds of server in any data center. And if that's the most valuable asset that you have, something else coming in and coming in your way of efficient utilization means a lot in terms of the cost, means a lot in terms of the capabilities at which they have to provide to the customers. So let's take a look at now and see how this EC2 instances evolved over time. So this is the big picture from AWS Geek of which I took a part of it to explain and kick this conversation off. And you can find this again at awsgeek.com. So let's walk from the left hand side or crawl from the left hand side and try to walk by the end of it. So what we see on the left hand side here is the picture from EC2 instance circa 2013, all right? In 2013, Amazon introduced the Nitro card or the Nitro system. By using the Nitro system, they offloaded the networking component which was running in software onto a hardware offload known as Nitro. And this Nitro system was built on carts, meaning commercial off-the-shelf components. And basically just by doing this, they got 20% additional bandwidth on the network. And this is the C3 instance. So there's the evolution from C2 to C3, 20% additional bandwidth and 50% latency reduction. So your latency went on by 50% reduced performance variability which means you could expect much more deterministic performance when you ran something, ran a virtual machine on top of the system compared to an EC2 system, all right? So that was the first technique that they used to offload the network, of course, the taste was good. So next comes C3 instance and that was one year later in 2014. And with the introduction of Annapurna, at that time the storage subsystem or the storage system which was running in software got moved to hardware offload and that was also a cart system meaning off-the-shelf system, ASIC based. And by now moving the storage component to the hardware layer to offload the system, they gained 12.5% more compute out of the environment. What that means is if we have 100 data centers previously, they basically eliminated at least 12 of them. That's huge, huge, huge cost savings, first of all. On top of that, it's not only about cost, it's also about performance, it's also about latency reduction, it's also about QoS type of treatment to traffic across the data center. So that was C4, all right? So now in 2015, a year later, the EC5 instance was introduced and following the same suit, the management security and monitoring layers were pushed down to the hardware layer, again with another hardware offload mechanism. And do note here that by moving that, Amazon achieved separation of control and data plane, which is very critical so that there is granular control of the system overall and 100% compute availability. So essentially again, more savings, more performance, more compute, which means more margins, more wiggle room to play with and more applications to be onboarded onto the same infrastructure because of higher performance. So there is a few things though that we need to compare and contrast here. By the time we got to the C5 instance, the Annapurna system, which was used for the management, security and monitoring was based off a custom ASIC, not COTS, all right, that's just, that's what it is, that's what the picture says. As well as one other aspect here is the hypervisor layer stayed on from left to right. However, the hypervisor on the first three is different from the hypervisor on the right-hand side because the right-hand side hypervisor is known as the nitro hypervisor with additional capabilities to enable certain other applications to be run on the system, all right. So by separating control and data plane, they also were able to easily do billing of instances and so on, all right. So now this is the evolution that's happened over a period of time. So in summary, half-loading, storage, networking capabilities onto COTS-based systems or custom ASIC-based systems provides us better, reduces performance variability, provides us with better performance, reduces latency and so on, all right. So let's have that in our mind and the evolution in mind and let's see how data center is awarded over a period of time. So here for your reference, these are the four variations or the form factors of the AWS Nitro Cards for your reference. There's the URLs, take a look at them at your free time. So now let's go and take a look at how data center looks today, how hyperconversion infrastructure in a data center looks today and what are some of the parallels that we can draw from public cloud providers like AWS and see where we can land or where we should be heading towards in the data center. So here's a picture and I'll walk you through this from left-hand side to right-hand side in the next couple of minutes and there's a little bit of a reality here. There's a little bit of a fiction here and then there's a little bit of a reality here. So I will tell you why I am saying that in such a funny manner. All right, so let's start from the left-hand side here. So it's known, first of all, hyperconversion infrastructure is the de facto infrastructure that's being deployed in the data center today in every enterprise, in every service provider environment for any IT workload deployment, all right? So with hyperconversion 1.0, the pioneers of HCI, visa-based, Nutanix, VMware, as you all know, networking, storage, compute onto a single node or single server, they're basically bringing more efficiencies in terms of packing things into a server. At the same time, what we also observed with hyperconversion 1.0 is that host is heavily taxed in terms of utilization and performance. There is applications starvation due to the way that virtual machines run on an hypervisor environment, the noisy neighbor problems persisted. SLAs could be only guaranteed to a certain extent or maybe not at all at some times. And it costed a whole bunch of money still to deploy these systems. Keep that 1.0 picture in mind. Now let's take the learnings from AWS and say what if we offloaded the networking component in an HCI 1.0 environment and made that HCI 1.5, right? So that is the second picture from the left-hand side. All right, let's fast forward. What if we also learned from the storage evolution in AWS and offloaded that onto another storage system in hardware, okay, that's HCI 2.0. That's basically following AWS Azure and AWS in terms of outpost and Nitro that you might have seen some announcements on, right? So if this is a what-is scenario where if we had offloaded both networking storage onto HCI 2.0, we would have gotten much more efficiencies in parallel with what AWS got with respect to networking storage and so on. However, hypervisor still remained in the picture. Not only that, let's also take a look at the current HCI solutions that we have in the market today, right? In all of the HCI solutions that are available today, the instant storage, which is also known as is always in a pooled storage environment. It is never in a cloud providers have been able to solve this problem with hardware offloads and other mechanisms to actually provide an instant storage on the host. That brings a lot of efficiencies. That provides the QoS capabilities that is critically needed for a workload to run in the environment. So that's absolutely missing today, all right? So Diamante looked at these progress being made in the industry as well as the learnings that we picked up along the way and we adopted these things right from day one in our approach to building the hyper-continuous infrastructure for Kubernetes. So at Diamante, we have networking and storage offloads along with open-source Kubernetes packaged together for a cloud-native infrastructure. We are able to achieve 95% host-illus utilization. The hypervisor is completely eliminated. There is no noisy neighbor problems. All those are taken care of due to the way the hardware offload works for both networking and storage. SLA guarantees can be provided to as granular as 100 microseconds of latency came out there. They're not given a white piece of paper every day or a blank piece of paper every day to restart their IT environment. They will always have a set of legacy workloads which may not be containerized at all, which are yet to be containerized. So they would need to run a virtual machine-based environment. So how would we solve that problem? In the CNCF community, the community has together brought forward the notion of CNV or container-native virtualization. And Kubeboard is one of the projects in this, under this umbrella. Within Kubeboard, the idea is to, using, leveraging Kubeboard, the idea is to run containers and virtual machine as equal citizens on the same infrastructure, which is Ipoconverse 3.0 plus here, with Kubernetes as the orchestrator. And why is this important? This is important because regardless of the workload, whether it's a container, whether it's a virtual machine, they both can be orchestrated using Kubernetes.  It's the same mechanism, it's the same tool, it's the same learning, it's the same training that you need to have. And this is very important because simplicity drives efficiency, simplicity drives debugability, simplicity drives a whole lot of things. And this is where the CNCF community is heading towards. And you might have seen some announcements a couple of weeks ago from VMware in terms of taking certain Kubernetes components and plugging them into the vSphere environment. The most important aspect to observe there is that for anybody to run a virtual machine, they have to go through the vSphere way of doing things, whereas when somebody wants to light up a set of containers, they will have to go through a different path. And that results in two sets of tools for two different workload types, two different training, two different, you know, multiple training sessions, et cetera, et cetera, et cetera. So that kind of comes in the way of simplicity, essentially. Now, with that background, let me hand you over to Naveen to walk through some of the critical requirements to run containers in ACI environment. Sure. Hey, thanks, Naveen. Thanks for walking through the whole evaluation process that happened over these few years. Let's now look at the requirements that came up during this process, right? I mean, if you step back five years or so, container technology had just started being touted as the next wave of disruption. The way applications will be deployed and delivered. And this with oncoming change, the requirements for an ACI platform had to be revisited. So let's look at from just containerized applications perspective, right? You have multiple applications running. What are the new requirements from network and storage side from this perspective? You want multiple applications, but you want guaranteed SLAs for these applications from network and storage. You want consistency in performance, predictability in performance. So what does it map to? On network side, if you look at it, the technology had already started, it was already out there. SRIOV was already proven. They were already off the shelf chips that could guarantee performance, that could give hardware cues to your application, right? These allowed you to program minimum guarantees, maximum limits at each container level, at each virtual function level. That virtual function could always be extended to container. Let's extend this on the storage side. Around the same time, NVMe started becoming standardized. So now you could have the same way you had it on networking side, you could have virtual functions, which could map to namespaces at the storage layer, where you could have hardware cues for each of these virtual functions. And then you could basically guarantee, minimum guarantee, as well as put maximum limits on each of these virtual functions, basically meaning for each application, you could guarantee a certain amount of IOPS, you could limit a certain amount of IOPS. Now, going back to referring to Narene's one of the slides, this evolution that happened, there was a physical aspect also that was out there. Networking side, the bandwidths were going from 10 gig to 25 gig or 40 gig, 50 gig and even 100 gig with sub millisecond latency. Similarly on the storage end, we are talking about a million IOPS becoming very normal, again at sub millisecond level. So with all this in mind, now you have to really review, revisit how your HCI platform is going to look at. Move one year forward and Kubernetes starts getting a strong foothold as the orchestration platform of choice. From multiple applications running on a node, your transition to multiple instances of applications running on multiple nodes and handling of application failover is now part of the core design of this orchestration platform. Through different SIG groups and CS playing of course an important role here, the CNI and CSI standards evolved. I mean of course, flex volume being a precursor for this on the CSI side and on the scheduler side, a way to extend the scheduler, which was way more aware, could take decision more intelligently based on its knowledge of the resources of the underlying hyperconverging infrastructure. So let's look at networking and storage side requirements that came up because of that. On the networking side, IP address or network endpoint being another way of referring to it, it should be dynamically manageable without the user having to provision it for each and every application instance that comes or goes away. But then look at the other way, there could be certain application that would require static configuration. They want an endpoint to be persistent with the instance of an application. Ability to have visibility of these endpoints at the network layer to allow monitoring or even enforcing policies. You want separation of control and data plane.  Availability to support availability zones itself, multiple data centers, campus clusters. Similarly on the storage side, sorry about that. Similarly on the storage end, you wanted static and dynamic provisioning from storage perspective, from volume perspective. You wanted synchronous mirroring where your applications would have persistent data across different nodes and that should be synchronous. The application failover should not have to worry about a delta between the state of data across these nodes. You want rich feature set from enterprise customers perspective. You want snapshots. You want ability to restore these snapshots. You want to take backup and you want ability to restore the state to the backups. And of course, availability zones should also be able to extend, the storage feature should be able to extend across availability zones. Now let's look at the HCI requirements for Kubernetes clusters from availability zones perspective. Now high availability zones from enterprise customers perspective normally maps to campus clusters. These are data centers, not that far apart. Let's take around 50 miles or so. Now the requirements from network and storage a little bit different. On the networking side, you want your administration to be able to configure different subnets across different zones. So when applications are coming up on different zones, they get IP addresses. They get endpoint assigned dynamically, automatically on the subnet where that application comes up and the network should be laid out such that these are outtable across these data centers. On the storage side, you want your mirrors to be created, to be placed across these zones so that a failover on one zone allows you to move the application to another zone and having the data available synchronously in that zone as well. Now all this works very well for containerized applications. But what about application that are still on this path of transformation? They yet to be containerized applications. You don't want to have a separate infrastructure that deploy such applications. And through Kube word project under CNCF, there have been some great work done here. Ability to run applications in a virtualized environment but inside a container framework referred to as container native virtualization. On networking and storage perspective, you don't want anything to change from the way you did your cloud native application itself. You want the same feature parity. You want the same performance and you want a single pane of managing these applications. You have learned Kubernetes already to deploy your applications natively. You want these applications, the yet to be containerized applications to be also managed exactly in the same way. You don't want to learn a different framework for deploying such applications. Now stepping back, given all these requirements defined for HCI, the management of these components is also an integral part of an HCI requirement. Again, not very different from the offerings in the cloud, whether it be for configuration management, user management through Active Directory, or user policy enforcement through RBAD, should also be considered when designing or evaluating a platform for deploying cloud native application under this new paradigm. So given all these requirements are defined, let's look at one of the solutions that's out there that does take care of all these feature sets. I'm going to give it to Hero who's going to demo some of the features that we just now discussed. Thanks. Thank you, Naveen and Nareen for the great introduction. In this section, I'll go ahead and give a demo of multiple demos. So there are three demos that I've set it up. First, we'll go over the setup that I'll be using it. The Kubernetes cluster, which is deployed onto the HCI appliance. And the same cluster we'll use to deploy a containerized workload, which is a WordPress application. That's an example. I'll use it to deploy it. And we'll use the same Kubernetes cluster and deploy a KVM to showcase that yet to be containerized applications can also be deployed onto the same infrastructure using the same Kubernetes cluster. And in the fourth section, which will be the last demo, in that one we will showcase the benefits of hardware offloading for the network and storage resources and how we can use those benefits to provide the IO isolation per application, per VM instances along with the QS for the performance. Now let's go ahead and take a look at the demo setup that I'll be using it. So I'll use the three node cluster. As I mentioned, this is an HCI platform appliance on which we have clustered the three node Kubernetes cluster. As you can see, there are blue and green components. Blue are all open source Kubernetes components. We have one node, node one, which is running all the master components of the Kubernetes. And the green components are basically nothing but these components provide the functionality from the HCI platform standpoint to do a resource pooling for the network and storage standpoint. And also the CNI and CSI plugins to provision the network and storage resources to provide the guaranteed QS, guaranteed performance and making sure that you provide IO isolation for each and every container deployed onto this infrastructure. There's also a scheduler extension component which makes sure that it is aware of what all the resources this given infrastructure is able to provide, making sure it is aware of whether it's a high availability cluster, whether it is a single zone cluster and making sure it is able to schedule the resources in such a manner that it provides a high availability for a given resource from an application standpoint. Now let's go ahead and kick in the first demo where I'll go ahead and deploy a WordPress application. Before I deploy the application, I'll just give you a pictorial view of how the application deployment will look like onto the Kubernetes cluster that we have built across the three nodes. So when we deploy a WordPress along with the MySQL which is using a MySQL as a data store, so here I'll deploy a three instances of the WordPress, which will be running onto the three instances, node one, node two and node three and will deploy a MySQL which will be using an underneath persistent volume onto a DMIT IO layer. As you can see, Kubernetes construct called storage class to dynamically provision the persistent storage onto the DMIT IO layer. As you can see there are on onto the picture, green disk, those are nothing but the three replicas of the persistent volume that MySQL will provision. These three replicas are synchronously replicated. What does that mean? That means it gives a high availability of the volume or data store onto this replicas for a MySQL to fail over in the instances of the node going down or the MySQL instance itself goes down because of some reason. Now, the DMIT IO layer also provides a way to take the snapshots of these replicas. Because these replicas are synchronously replicated, you can use either of the replicas to take a snapshot into given a time frame. And these snapshots can also be used to backup into the third party backup storage like NFS or AWS. Now these used in future to restore onto a given volume or also to create a new volume for log analytics or any further analytics that end user wants to do it. Now let's go ahead and apply this instance, the WordPress instance that we'll be using it to the demo. So as I mentioned before, it is a three node cluster using as a standby right now. We'll use this fourth node into the later part of the demo. So we'll go ahead and mainly use the three nodes of the cluster, Qubectl which is the open source Qubenator CLI which gives you the details from the Qubenator's cluster standpoint. And there is another CLI here is a DCTL CLI which is a DMIT infrastructure level CLI which give you the more awareness from the infrastructure resource and resource pooling standpoint. So here you will be seeing more information from the platform standpoint like millicores, memory provided onto or available onto the server, storage and VNICs which are the underneath infrastructure level resources that can be used to schedule a specific workload onto a given node. Now let's go ahead, first one is nothing but a MySQL password. So we have created a secret for it, MySQL deployment and WordPress will be deployed as a stateful set. Let's go ahead and create a secret and deploy a MySQL deployment instance. For what is the port spec looks like with provision? We have mentioned that we will be using a dynamic provision and we'll use a storage class that is construct that is provided by the Qubenators to provision the volume onto the DMIT. Here it says that storage class will be using as a mirror. That means we will go ahead, let's look at what is this the mirrored storage class looks like and be a volume provisioner. And this provisioner is aware of these means we need a three replicas onto a given cluster whenever we provision the storage. The file system it will be using is the EXT4 file system and this is the performance tier or guaranteed QoS that it requires is the best effort based. We'll go into the details of the different performance tiers that you can provision onto the infrastructure and how we are able to give the IO isolation and guaranteed QoS into the later section of the demo instance is running. So this is the WordPress MySQL instance that we deployed and we had requested that we needed a three-way mirrored volume or mirrored replicas for a given MySQL instance to be deployed. Now if we zoom in into this volume which was dynamically provisioned, we will see that it has provisioned a three-way replicas onto a three different nodes of the cluster. And these all replicas right will happen to the MySQL instance will be replicated onto all Plexus or all replicas of this provision persistent volume. Now let's take a look at the part state Floyd one MySQL instance it is into a running state it is running into the node one and we have three instances of the WordPress stateful site running because we have three node cluster and we had requested for the three replicas. So we have all three instances of the replicas running onto the three different nodes of the cluster. Run the yet to be containerized application onto the same Kubernetes cluster. This gives us who are able to deploy the same how we are able to use the same node and also deploy the containerized workload along with the KVM workload. Here I'll just give before we go ahead and deploy it I'll just give a little bit deeper view into how we are able to achieve that and how we are able to use the same infrastructure to the KVM workload along with the container workload. The design is very much similar to the Kube word where the philosophy is we want to run a KVM inside a container. So they can coexist onto the same infrastructure along with the container workload. In this we are using a KVM as in this our solution is based off the KVM hypervisor. Now looks like the KVM is becoming a default runtime manager for deploying the VMs. Nowadays, like Google is using it, AWS, NitroCards are also supporting the KVM as a hypervisor to deploy the VMs. We will use this to deploy the VMs like the container workload. As of the HCI and by us offloading the network and the storage resources, we are able to achieve the consistent IO isolation and quality of service for the both containers and the VM workload using the PCI pass through mechanism. Another one is the NVME VM. So every application or every container or every VM which get provision onto the HCI adapter, DM and HCI adapter, it gets in its own isolated or its own isolated VS per a container or per VM. So here, let's say if the VM requires a network and the storage resource, both of them will get its own SRLV function for VM for network and the storage. So this gives you the way of provisioning or make a consistent way of getting an IO isolation and also guaranteed QoS for a given application or for a given VM instance. Now, this is little more technical. I won't go into each and every component detail, but this is kind of a high level picture which gives you the details on how the orchestration can be used to deploy the container or a VM instance onto the same infrastructure. So here, there are two workflows as a part of the regular container native workload and the red one is the KVM deployment workload. So KVM deployment is here in this case which is actually implemented using a Kubernetes construct called CRD, Custom Resource Definitions. So KVM objects are exposed as a custom resource definition onto this Kubernetes cluster. So whenever a KVM object gets created, the custom controller, KVM controller, which is in the green component underneath the API server will watch onto those instances and it will act on it. Here we are seeing other components like scheduler, network controller and storage controller. So whether you deploy a container or you deploy a VM, underneath, it will be used in a similar manner. They are in case of provisioning the storage or network for the container or the VM, the code path will remain same. This gives us the benefit of having the same features like storage classes, dynamic provisions, static provisioning for the storage and network to be exercised for both pod and the KVM workloads. So if you see at the end on the right-hand side, the containers and the VMs are running next to each other. They can coexist onto the same infrastructure just because we are able to extend the Kubernetes to deploy the VM and the container workload onto the same infrastructure. Now this is the pictorial view of how I will go ahead and deploy the KVM. So if you remember from the first demo, we had deployed a MySQL and one of the WordPress instance was running into the Node 1. In this demo, I'll go ahead and deploy a KVM instance onto the same Node instead that you are able to deploy the KVM and container workload onto the same Node of the same Kubernetes cluster. Underneath IO layer is exactly the same. The way we will provision, in this case, I'll take an example of provisioning the persistent storage using a static provisioning just to showcase the static provision onto the Kubernetes cluster for the KVM. And you can still use the same storage features like snapshots and also taking a backup of these snapshots and restoring this backup into the persistent volume. Kubernetes CRDs to support KVM as a primary object onto the cluster. So this is the KVM CRD. And this is the custom KVM controller that we have written to watch onto the KVM CRDs being created onto the Kubernetes cluster and then take an action on it. Comes into our mind. The first is how we're gonna do the boot image management. We're gonna be able to pull the images to boot the VM from it. So in this example, we'll use a web server-based management for the boot images. So I've just deployed an Nginx which is hosting a CentOS 7.4 QCAU image for VM to boot from. So this is the Nginx web server which will be hosting the CentOS QCAU image. And this is how the KVM pod spec will look like. You can see it is same as the pod spec. The way we provision the network is using a notation and it will use underneath a CNI plug, same CNI plug-in to provision the network onto the same infrastructure. Because for the VMs, you want to make sure the IP addresses which are allocated once they're purchased for reboot or redeployment of the same instances on case of node failures or zone failures onto the same Kubernetes cluster. So end-user doesn't have to worry about IP address changes and node configuration changes and things like that. As I mentioned before, we are using a web server-based of pulling the image. So this is the HTTP endpoint from where the CentOS 7.4 QCAU image will be pulled and booted. It will be used for VM boot up. This is the way we are able to expose the resources for a VM instance. The number of CPO cores that we'll be using is 16. And memory will requested for 32 gig of memory. Graphical VMC remote console way of graphical remote console way of accessing the VM. This is just the index for it to use it, for which index to use for the graphical VMC index. And here, these are all the same volume construct that you would, persistent volume construct that you would see it into a container, regular container or regular pod spec. Here, there are two persistent volumes we have specified. One is a volume images and another one is a data volume, which is a volume one. So persistent volume that I will use to persistently save the configuration or the boot image. So the reason we want to use the persistent volume is once the VM is booted, if the end user is making any configuration changes, like it is making any changes into our result local or the way the application should start once the VM is booted, you want to keep those configuration changes persistent onto the persistent volume to make sure that they are persisted across reboot. They're persisted if the KVM instance moves from one node to another node or it moves from one zone to another zone. This volume two is the volume one is the data volume. This volume is exposed as a PCI pass through inside the VM. And we are using a block device as an SS type and this support was added into the flex volume to make sure that we are able to do the PCI pass through for a storage persistent volume storage and also able to get the guaranteed QoS and IO isolation for the VM instances same way we are able to get it for the container workload. And instance using the same pod spec. Let's go ahead and provision the endpoint, which is the EP one, I like to create a persistent volume. This is a volume image one is the persistent volume for storing the boot image. And this is our block volume particularly provisioned onto the cluster and both of them we provision onto the node one where the WordPress and MySQL instances are running. Let's go ahead and create the PVPVCs to bind this volume. And I will go ahead and some KVM controller would have created the KVM pod for the given KVM instance that we created. Here as we see the same KVM instance we deployed it onto the same node where we have one of the WordPress instances running and also the MySQL instances running. Now this is the IP address got attached or it was reserved for a given KVM instance. As you can see it is underneath using an SRIOVVF for this given instance. These are the two storage wall these are the two persistent volumes that got assigned for a KVM instance. And as you can see the first one wall one one was the block device. So there is no device parts will exist onto the host because we are doing a PCI pass through and in that case host will not see this PCI device on the host and it will be passed directly inside the VM. And second instance we are using for persistently saving the boot image. Now we'll access using a serial console to the VM and as you can see you are able to log into the KVM instance that we just deployed. And we will able to see the same IP addresses being configured inside the VM for the interface that we exposed as a PCI pass through device. Next demo which is the last demo of this section. We would like to do and I'd like to do showcase the IO isolation with QoS for performance which showcases the benefits of offloading of both network and storage to the hardware and how you can get the guaranteed QoS or guaranteed performance for a given container or a VM workload. So we will take advantage of using a four node cluster to dedicate a node one for all the KVM instances deployment. So we just use the same Kubernetes construct to label the node for the KVM deployment just to make sure that all the KVM instances that we deploy onto the cluster only goes onto the node one and all the container workloads we will dedicate on the node two, three and four. Here we will basically deploy around 27 containers across three nodes and nine KVM instances on node one. And we will see how we are able to guarantee the IO isolation and also the performance for a given workload KVM or a container workload using a hardware offload for network and storage. State the usage of a performance tier and the guaranteed IO isolation and the performance for the container and VM workload. So we have divided the performance tiers here. One is the best effort, high and medium. As you can see their reserved effort is zero and network bandwidth is zero. That means if a system has any to give, they will get some storage IOPS and network bandwidth based on the best effort. High is going to get the maximum which is 20 K and 500 meg and medium is the next level which is 5 K and 125 meg. You can use the same construct to get the maximum to limit the maximum storage IOPS and maximum network bandwidth also. But in this case, we'll just demonstrate the min requirements. So these are the way of setting the min requirements for a given workload. I'll use the performance tiers and deploy three instances of KVM using a best effort, three instances of KVM using a high and other three using a medium onto the node one. First node as a type KVM and make sure that we use the same KVM node label to deploy all the KVM workloads. Here the node is labeled as a KVM. The instances of KVM which will be getting deployed onto the node one which we labeled as a KVM node. You see there are nine instances of KVM CRDs we deployed and let's take a look at the container states. As we can see the nine instances are going into the container creating state. I'll just showcase a dashboard which we can see two locations of KVM instances that got deployed. So this is the dashboard from the infrastructure standpoint. The application tab will be able to see it. Just logged out. I'll just re-login to the node. Hyperbenchmarking containers onto the same infrastructure. So here we'll deploy a 27 instances of FIO benchmarking and hyperbenchmarking pods across three nodes of the cluster at the different applications. Let's go and take a look at the nodes while the other container workload is coming up. As we see we had deployed a KVM instances onto the node one of the cluster. Here, as we can see because of the flow network and storage hardware offload, we are able to get a one million IOPS or more than a million IOPS for a given node throughput. If you see it that is in this case we are not running KVM is not running any network traffic. It is only running a storage traffic. So you'll be only seeing the storage IOPS and which is close to a million, you are able to get it just because of the hardware offload for the storage. As we see these containers, here we see a nine KVM instances that we deployed using a different performance tiers. Three with best effort, three with medium and three with high.  It's the traffic. We will see the numbers in such a manner that high workload will be getting the maximum IOPS onto the node right after, next year will be the medium and after that will be the best effort. 1040K IOPS need and right latency. To see how much latency we are able to gain for a given specific performance tier So as we can see, second latency, there are around 480 microsecond latency for a read workload. And as we can see here, they also get 260K IOPS effort which are running around the 16K IOPS with the higher latency because you will be giving the high priority to the higher workload. The hardware is giving the high priority for the high workload, which requires the maximum IOPS. And the next is the medium which is getting a 66K IOPS and with the 1.9 millisecond latency. This is the same behavior we will see onto the other nodes where we deployed it. So here, as you can see, all three best effort are into their own range with high, getting the maximum and then the medium into the next category. Yeah, this is what I had from the demo standpoint. Now we can wrap it up with the Q and A. A few questions that came through the Q and A channel on Zoom. We've answered all of those questions. Feel free to, if you have any more questions, you know, feel free to plug them in now or let's roll to the next one. As well on the top of the hour. For about DMRT, go to DMRT.com. Email us at info at DMRT.com or follow us on Twitter at DMRT.com or we're also on LinkedIn. So in closing, thank you for your time. We appreciate it a lot. Hope we were able to share some insights from the industry. So in closing, DMRT is an enterprise Kubernetes platform with hardware offloads based on, you know, COTS hardware and software prepackaged with open source Kubernetes with million IOPS for one RU and sub 100 millisecond latency. Check out our website for all the use cases solutions. Of course, plan.enqlubcon, we'll see you there and you can expect more from us at qlubcon. So until then, have a great day. Back to you Kim. Thank you all. Have a great day.


All right, we're the behavior panel and we've never been in the same room before this is the first time actually and So we've got a couple things planned for you. We're gonna Don't we call mean tweets? We're gonna read some of those out and we're each gonna read mean mean comments that were made about us in the comments section and Chase do you want to go first? There's plenty of them. So yeah, I have a great time. Yeah, this is a good one It's too big for me. Take turns. Yeah. Yeah, let's do it This one's my favorite It's Wendy G Welsh Chase's hair looks amazing. The rest of you are brilliant Because because when we were setting this up Scott was looking for we'd already got together and Scott was looking for somebody else and he said mark Do you know anybody who does body language? There is this guy called chase. He has great hair, but he doesn't his body language stuff is so terrible Yeah, that's right. So let's look at him. He's quite actually a picture.  Okay. Here's one and and this is from rock boy eight pebbles And this is this is a comment seven hours ago on the Bob Lazar interview And it says mark you are so in the box. It's a wonder. We're still not in the stone age How does that mean? I don't know what it means. I think they think like because I won't I can't possibly imagine that Bob Lazar actually I'm like, I'm keeping I'm I'm repressing the whole of humankind. Okay. Yeah, that's your mark. Yeah, Mark All right, no, I'll go. All right. This is from bandit. This is four days ago I would pay a million dollars if they would do a version of this where they all attack each other Like mark explaining why Scott has a backwards hat on when he's maybe like 63 years old Oh Here's my favorite about me and this is from Raptic gaming Greg Hartley gives off a store mannequin type book Wow, that's good. That's a good vibe. Okay. What else we got? What do you get? All right? Chase's makeup looks exactly like David Bowie's video life on Mars All right, you got one more I'm going Go ahead This is from I can't say the name but it's what the hell is Scott got his head that wig is awful Okay, so this is from Paula or something like that. It's on the Burke Ramsey one mark always goes long and with hand gestures Wrap it up. Scott says I shouldn't have said all of that. That's not good. Ha ha ha ha ha funny stuff Yeah, yeah, I did the second bit doesn't make sense, but you may have a point on the first bit where she had yeah All right, does chase have makeup on because right now he looks like a rodeo clown This one is a combination Here's one that covers us it says Scott's covering something from his past up Greg and Chase super noticed it especially Greg I've got that's what I was gonna go with next Okay, oh Wow Well, he's one on me then Greg, did you kill anyone?  So here's one from two days ago from your Kabul Andreid Mark so annoying his comparison doesn't make any sense Well, I don't know what the combat that doesn't say what I said that I don't think there was an Adelvi It was on on the other. Oh, I don't know what the comparison. I'll tell you here's one. Wow, Scott You're not come across well here. I'm surprised and disappointed Really a cold judgmental dismissive attitude I gotta agree with the comments. It is way too much and unprofessional But that's me Chase looks like he got burned to a crisp and then stung by ten bees Here's one this is directed at me, but it really should be directed juice Great show Greg your whistle sucks Okay, we're doing for everybody who's this one chase looks sad Greg looks serious Scott looks chill and Mark looks curious, okay Here's one from a guy called Mark. Well, you guys, please just start the whole show off by leaving Chase's microphone off You got that Scott has dead eyes no depth of emotion and he will not let you in Well, this is the hallmarks. Yeah Dead eyes Chase can look at Mark like either a proud brother or dad. It's so cute lol That's his tail up made That's very nice. That's very Roger rem jet says Greg in a suit looks just like junior soprano Guess their style here it is. How can you read over 2,000 comments? Scott has said more than once we read every comment. I believe Scott, but my head just can't get around it Boom Susanna And K says Mark turned into Fauci Oh Shamanic revolution says which leaders of the G7 mark He most of us. He most of us. Come on. Okay. Come on. Just tell us Here's my final. Here's my last one. I'm sure chase aka Do you know what I'm saying? Is turning his saturation up on his camera to look even more tan and it looks worse As you sit next to mark on screen. He's got such a bright room and wider Okay, one more one more here from Julie Miller. Thanks Julie for this Knitting away and then Mark says he doesn't respect it where Sorry ruined ruined your evening there Julie. I'm sorry. I remember that. What was that for that was from the Richard? Oh Yeah Here's my last one great sweater. Yeah, let's see if I got Scott the way he is sitting with his hands on the table Reminds me of a toddler trapped on one of those feeding chairs Get down from the table, but can't until his mummy lifts him out That's a great one. That's rather than that put some real work into that story. Thank you guys. You're great. Thank you Now we don't start a trend Yeah, we got we'll get we'll do more another time. Let's get started. Cheers guys chase everybody great to be together first That's it, that's correct. That's great. All right. There's what we're gonna do that bet


In 2017, Joshua Jackson sold his West Hollywood home he once shared with ex-girlfriend Diane Kruger for $5.76 million. Initially the stylish residence located on North Orlando Avenue featuring an attractive stucco and cedar exterior, appeared to be a difficult property to part with, with features like brass chandeliers inspired by the iconic Sputnik design, decorative concrete and glass subway tiles, charming Julia Balconies, dual-sided fireplaces, hand-crafted wooden built-ins with a mid-century flair. This residence was full of modern design trends, however...


Welcome to Barbell Logic, Rewind. This is Scott and I got Matt over here with me and I wanna do this in the pre-roll again. We do this for free, we love doing it, but it's a big help to us if you'll go to your favorite outlet, whether that's iTunes or Stitcher or whatever it is, YouTube, even if you're watching these videos on YouTube and give us a good review, that's a big help to us. It helps us get more listeners and helps us spread the gospel of strength. We're gonna talk in a minute here about Reynolds Old Man Texas Method.  And I have people ask me all the time what it is and so we're gonna expose that. Let's talk about Old Man Texas. First, we'll be telling you a little bit about what Texas Method is, right? Texas Method is the textbook example of intermediate programming. In an office program, we go up in weight every time we go in and train. So we train and apply stress, we recover and we adapt and we can express that adaptation the next time we go in and then we become an intermediate. We can't do that anymore. We can't recover between the sessions but we can recover over the course of a week. We can apply a big stress on Monday in the classic Texas Method. It's five fives, big stress. We have a little deload in the middle of the week. We might do three fives at 80% of Monday, perhaps. And then on Friday, we're gonna do about 10% more, approximately 10% more than Monday for a big set of five. So that's the classic Texas Method which is a man killer for older people and less than optimal athletes. So you've tuned that down or maybe up, modified it for the rest of us. So when I think about Texas Method, I think about to stay in the heart and soul of Texas Method, you've gotta have a volume day on Monday, a lighter day on Wednesday. It's not a deload day, it's a light day. And it's not a deload. In an intensity day, a heavy day on Friday. And so can we keep that feel without losing our soul? And so it doesn't become something that is not Texas Method, but make it so that it's something that guys who are middle age and older, because Texas Method was written for guys like Chase Lindley and Steven Gunn. These guys are 19, 21 years old who also have a lot of time on their hands. You can train and recover. They're big and strong and they're just like walking bottles of testosterone. So what happens when we're 50 or 40 or 60 and we can't handle that amount of volume? So much has been talked about this lately and so I am confident that the stance for the vast majority of lifters who are over 40, say over 40, that we know that they can handle the intensity pretty well. They can stay heavy. Yeah, so that big, heavy set of fives is not a big problem for an older person. That's usually fine, but the volume kills them.   And then after a while, you can't squat three times a week. You can only squat twice a week. But in the beginning, usually the frequency can stay the same. The intensity continue to go up. So the driving metric is intensity, but the volume has to come down a little bit from the traditional Texas method that five sets of five. And so when I say old man, Texas method, and I don't just give it to old men, as a matter of fact, you just kind of, matter of fact, you may have named it old man, Texas method. No, I think you named it after me. Oh, that may be, that's true. That sounds better, right? It could be young woman Texas method too, right? They're low testosterone by definition, you know? Only the interesting thing is that most women, especially middle-aged women, as well, can handle a little more volume because of the neurological inefficiencies that women have. The intensity, it's harder to make that the single driving factor, because it doesn't give them enough stress. So a single set of five at deadlifts doesn't provide the same amount of stress on a female as it does on a male. Yeah, they'd be a lot better with two, three sets of three or whatever. So you were saying in the keeping of the spirit of the Texas method, you know? I think that it's more like that the Texas method demonstrates like three really important things for intermediate programming, which is, you gotta nail a guy with some volume, then you gotta give him a break for a minute. But he still needs some more volume to grease the groove and he probably needs a little more stress because he couldn't do seven sets of five on Monday, right, so he still needs a little more stress.  And then by Friday, he's recovered enough. So it's a tinker toy box, you know, of tools or toys that show us how to program for an intermediate person. It is, and actually I've heard Sully say this too, although you start walking a fine line that you can't think of Texas method as the stress recovery adaptation. So it's not like the Monday is the stressor and the Wednesday is the recovery and the Friday is the adaptation, it's not that. You have to have Wednesday, it's not just a recovery thing, you have to hit them with Wednesday. Yeah, so Wednesday, what most people don't know about who haven't done it, is that Wednesday is actually never easy. It's always hard because you're not recovered from Monday. If Wednesday is easy, you move to intermediate too early. Right, right. Or the weights are just way too light still on Monday or something. So it's Monday is supposed to beat you up enough that Wednesday you're not recovered. Yeah, the first time I programmed that for somebody, they do their five fives or their three fives, you know, in the case of Old Man, Texas, and they'll be like, man, I'm looking forward to Wednesday and I'm like, yeah, yeah, you bet. And then they do it, it's almost as hard as Monday.  And they do 265 and like, oh, this is so slow. It's felt worse than Monday. Like right, that's the point, right? So because the idea is that the stress recovery adaptation cycle no longer takes 24 to 48 hours, it takes an entire week. And so we actually have to accumulate fatigue over the course of the week and then really recover essentially over the weekend. And so that we can be ready to go again the following Monday. So did we even say what it is? So Old Man, Texas. No, I'm about to. Go ahead, sir. So these are the changes that I make. So we've laid out what Texas method is in the spirit of Texas method and keeping into the spirit of Texas method. Here's what Old Man Texas method looks like. Monday rather than five sets of five on squats just becomes three or four sets of five on squats. And that just depends on really two things, age and how far on the bell curve they are on the athletic spectrum. So if they are 45 and relatively athletic, they can do four sets of five as opposed to three sets of five. And if they are 60 and very much general population, normal, not very athletic, three sets of five is four sets of five seems to be too much, right? Now five sets of five will kill them. And so we do three sets of five on squats. On Monday, we do the same reduction. So 10 to 20% reduction on Wednesday for two or three sets of five, again, depending on recovery and what we're seeing on a week to week basis. And so usually I'll start them at three sets of five on Wednesday. And when the weight becomes heavy enough that the stress is intense enough then I can drop a set out on Wednesday and just go two sets of five as opposed to three. And then Friday is one heavy set of five for squats. So the only thing that's different between old man, Texas on squat and normal Texas method is the Monday session basically. Right. Yeah, so I wanna reiterate this. Wednesday is not a D-load, right? So you said they get an option of 80 or 90% of Monday and they can do two or three sets of five. If you're setting this up for yourself you don't wanna set it up so that Wednesday's rest. You don't wanna do that. Like it needs to be an RPG eight and a half. So if you do two sets of five and you're done with that second set of five and like I smoked those, you better do a third set. Yep. And you probably should go up another 10 or 15 pounds and make sure you've gotta get a little bit of grind on that, right? And so any of it does heavy three sets of five, four sets of five, five sets of five as an intermediate on Monday cannot be recovered by Wednesday. It's not possible that that's what being an intermediate is. And so then that's the squats and we continue that on for a good long while. Over time, it also gives me a really good opportunity to get a little bit of peaking. And so I can actually move from three sets of five on Monday eventually to five sets of three. And then sometimes I'll even go to four sets of three and then three sets of three and then maybe two sets of three with a couple of backups. And so again. For your Monday. For my Monday, right? And then I may go up to work up instead on Fridays after I've run this for a few months and I'm trying to peak somebody. Maybe they're doing the strength lifting meat in the fall. Then we'll work up instead of a max set of five on Friday, we'll do a max set of three. And we'll run that for a while. And then eventually we'll do a max double and then we'll kind of be peaked going into the strength lifting meat. So you can do that. It gives you that opportunity as well. Peaking process from going from the three sets of five or four sets of five on Monday and one set of five on Friday with the lighter Wednesday to a true peak to a let's test our max is usually about a six week period, maybe eight. So six to eight weeks total. You know, people that I'm coaching right now I've got actually quite a handful of guys are doing squats in their triples right now as opposed to fives. Now do I think that triples provide enough stress long-term to keep initiating that adaptation that I need? The answer is no. But it certainly works well for a short period of time to peak them and get them that strength expression. And so at some point, I think one of the things that I talk about with Jordan Feigenbaum a lot is one set of five enough or one set of three enough to be a stressor enough to drive strength adaptations. And in general, my answer is yes. But over the long-term, if all ever do is a top set of three and it tops at a three again, it tops at a three again. Like that's, you know, like I can't keep making the way to go up forever. What a guy might get progress on triples for like six weeks. Maybe. Yeah, the high end, the aggressive end. And so what Jordan would argue is that a top set of three is actually an expression of strength. It doesn't really create the stressor enough to cause a stress to cause the adaptation. I actually don't agree with that entirely, especially when you're not adapted to it. So as long as you haven't been adapted to that top set of three, it's a super heavier weight than you've ever used in the past. I certainly think it can be enough stress to drive adaptation, especially among an older population. But I don't think it lasts forever. No, it doesn't last forever. And not only is it maybe a stressor or even what Jordan says in expression, it's good practice. Like sure, you know, so if you're gonna be peaking for me, you need to be unracking lots of times. Like you win a lot of first reps. So eventually you get down to the singles, you know, so they're practicing moving a heavy single. Because when, you know, as a novice, you've always got five reps to get a good one in, you know, and they're all submaximal, even if it's hard. So we don't get that luxury, we're an intermediate and it's gonna go to the main. Yeah, that's another reason as a meat approaches that I like things like five sets of three as opposed to three sets of five, because it gives you five first reps instead of three first reps. That first rep is the only thing that matters in a meat. Yeah. Right. So that's why we do squats on the Old Man, Texas. The way we do presses and bench presses is we often will still alternate press and bench press, but we start to play with the rep ranges there as well. And so I'll often do most older guys can handle four sets of five or even five sets of five on press and bench press because it doesn't recommend. So they might press on Monday, five sets of five or four sets of five. They would bench press on Wednesday, three sets of five. They would then on Friday work up to a five rep max or I can start them out doing five sets of three if I want more volume and work them towards a five rep max or top set of three. And then the next week it would flip flop and they would bench twice and press. Once the idea there is there's no light day in the pressing, the pressing and the benching. There's a volume day and a heavy day and a volume day and a heavy day. So any variation of three sets of five, four sets of five, five sets of five for the volume day and for the heavy day it could be multiple sets of three. It could be as much volume as five sets of three. It could be one set of five. It could be two sets of three. It could be down to one set of three over time. The key for the intensity day, the heavy day is that the weight continues to go up. Right, so in the beginning you said you might have a guy press on Monday five fives at a hundred percent. Okay, just for example. And then on Friday you might have you move five triples for like a hundred and ten? A hundred and six hundred? Correct, okay, okay. Exactly right. Yeah, I haven't done that, but I dig it. And then the idea is like what you're doing on the intensity day is that the weight constantly goes up. And so when the volume is such that the weight can't go up anymore, then we're gonna drop the volume first and keep driving the intensity up. And so every time I do the intensity day, so let's say instead of using percentages, let's use pounders. Let's say, let's say for sake of argument, they're gonna bench press their intensity day on Friday is 200 pounds. And they're gonna do 200 pounds for five sets of three. So that's 15 reps at 200 pounds. And then their next intensity day is gonna be three, four more workouts later, right?  The next time you do bench intensity, the intensity has to go up. And so if I'm gonna do 200 pounds, four workouts before I've gotta go to 205, four workouts later, if I can still do five sets of three, I'll just, I'll hang on. You bet. And when I can't do that anymore, I'll go four sets of three or three sets of three or one set of five or, and so, but I like triples there as we move along. We've done tons of fives. Remember the person that's doing this often has come from all of these fives on the linear progression. And so basically the press and the bench press are just alternating between volume and intensity.  So next Wednesday is a midweek press. So what do you do with your midweek press, which is next week? Usually three sets of five. Just regular three sets of five at maybe 90% of the intensity day. Sure. Something like that. Yeah. Or a slight increase from the five sets of five day. It's gonna be in between those. Yeah. Yeah, it works pretty well. And what I don't do, and I'm not even saying that this is wrong, it's just that what I don't do is I don't introduce supplemental movements yet. What a lot of people do is they'll do like close grip bench press for the bench press movement that day. Is it wrong? No, it's probably not wrong. It's just that for me, because I think so systematically, so kind of I've got this pragmatic sort of systematic progression, then the rep ranges become the variable that I'm playing with to drive the adaptation and the adaptation I'm trying to drive is that the intensity goes up. So as long as I can do that, I'm making progress. As soon as I introduce another movement, I've introduced another variable and it makes it a little harder to quantify which is the thing that's driving the intensity up. There is a time to introduce the supplemental lifts. For me, it's after this step.  I don't really like introducing variants or anything yet. It's an unnecessary complication, like you can still make progress, just bench pressing. You do dumbbell bench presses at that point probably. Of course. And so it's actually, you kind of get a chicken or the egg sort of question where could you do other programming that would make you a little stronger, faster? I actually think yes. Maybe. Like swing the pendulum all the way, coming out of linear progression, especially coming out of let's say you do six weeks of Texas Method or Oman Texas Method, some Texas variant. If you put somebody on six weeks of max effort training, their maxes are gonna go up a lot. Yep. The problem is, is that you're putting the cart for the horse. You're skipping some important steps there and some important needed stressors to continue to drive this train long-term. So what I need to do is I need to continue to, so if we look at it from the systematic perspective, if what I'm doing is I'm doing nothing but three sets of five on the linear progression and I'm adding a little bit every time. And then I get to the point that I can't do that anymore and now I'm moving to where I'm making progress once a week, then to add anything else to that, to add a supplemental lift or to add max effort lifting or to add any of those things, is jumping over some necessary steps that I'm missing the progression that I would get out of that. Those stresses become important for me. So what exactly are those necessary steps you think? Yeah, so I think that you have to make, to me when I'm looking at the long-term athletic development model, the lifter. I use that term, that's actually a term that I'm stealing, I didn't come up with that LTAD. The original concept of this was actually from the Soviets, the Soviets had the PASM, the process for achieving sports mastery. And so there's some good papers written, Tom Mysolinsky wrote his master's thesis on this. It was actually on the development of the Russian conjugate system, which is different than West Side says it is. But the Soviet Union, they were always looking at the long-term model. So like, what are we gonna get out of these people, out of these athletes over the course of decades rather than what can I get out of them today? And so the easiest way to understand this is in the United States today, in sports primarily, we allow our kids to specialize very, very early. And so you get these boys who are in the fourth grade and their dad decides they're gonna be a major league baseball player. And so they pull them out of all the other sports and they only play baseball year round. So they play school ball during school season and they play AAU ball and they travel with teams all the time. And inevitably what happens is that they get burned out on baseball and they quit or they're just not developing all these like various motor patterns as they're going through puberty, which is important.  And they wouldn't let them specialize for as long as possible. So they all played soccer and they all did gymnastics and they all swam and they all did calisthenics and they like seven or eight of these things, they all did trampoline. And so they just exposed them to as many motor patterns as possible. And then at the end, when they couldn't hold them back anymore, then it was the last possible moment where they could let them specialize and they would let them specialize. Now it was dependent on the sport. So if you were gymnastics, you would specialize a little earlier than you would in others because you kind of hit your peak at 16, 17, 18 years old. Whereas if it was weightlifting, they wouldn't let them specialize till they were 17 or 18 and they would hit their peak at like 22 to 26. And so what we would often see is that at junior Olympics, this is like in the 70s, in the 60s, 70s, early 80s, we are killing, America kills the Soviets in the junior Olympics. And when we get to the actual Olympics, they kill us. Because they have more well-rounded athletes.  There's no reason to do an eight week long program post LP. That's an eight week long program is an advanced program. Is there a time to do eight week long programs? Yes. At what point does that come? Well, when month long programs don't work anymore. Right. And so what I'm gonna do is I'm gonna pick these basic lifts. So for normal, especially older people, they're gonna concentrate on four main lifts. It's just the squat, the deadlift, the bench press and the press. They're gonna do that linear progression for as long as they can. When they can't do linear progression anymore, they're gonna move to a weekly progression that is the same lifts. Introduces just the tiniest little bit of variable which is this change to where I get volume on Monday, lighter on Wednesday, heavy on Friday. Some variation of that. And so if you're 19, that's five sets of five on Monday and if you're 50, then it's three sets of five on Monday, right? And I'm gonna milk that as long as I can. And then when that doesn't work anymore, then I'm usually by that time, I'm gonna try to peak one of my lifters. I'm gonna peak them and either run a mock meet at some point or I'm gonna convince them to get into a power lifting meet or strength lifting meet and do that so that I can peak them at that point. They can no longer do weekly long progress. And now I have to go to month long progress. And when I get to month long progress, that's usually when I go to a four day split. So now we're moving from the frequency, the total number of workouts frequency increases. So you're doing two upper, two lower days, but the frequency per week, but the frequency of the lifts themselves, like the squat will go down from three times a week to two times a week. Because if you're only doing two lower body sessions. So that's the next step. And then when I go to the four day split, the four day split is when we introduce the supplemental list because now a basic four day split is gonna look like your kind of primary squat day and you're gonna do a variant deadlift after the squat. And on the deadlift day, you're gonna have a variant squat and then the deadlift. And the same thing for the bench and the press.  So you might do a pin press, press lockouts. So, I mean, maybe there are stages that you don't wanna leap frog, right? Like you say, and do this total athletic development. Sure. Lifetime development kind of model. But it's also, if I have a tool that will work, why not use it? I'm sure. So a week long program, why not do a week long program before you do an eight week program? I mean, it just seems like. Yeah, it doesn't make sense. If I can make progress weekly, why would I make progress every eight weeks? Not only that, what if I can't make progress weekly, but I can still make progress monthly? Why would I make progress every eight weeks? Right. So to jump to a block training program, a 12 week long block training program or a 12 week long DUP program or a 12 week long sort of West side max effort or high, low sort of program, you're jumping the gun. Also for the guys that like the high volume that like moving to five sets of five, six sets of five, seven sets of five, eight sets of five. There are coaches that like volume. No one enjoys it to train. Right, that's what I'm saying. Nobody does. Now, is there a time when we're increasing volume, the primary driving metric is tonnage probably, right? We're looking at tonnage being a, the product of the weight on the bar times the work, total work reps. Super important. Super important. However, if I can continue to make progress by driving in the intensity metric up, why would I introduce six sets of five, seven sets of five? Because it sucks, right? Now, is there a time when you're gonna have to do volume? Yeah. Yes, but when you get there, you're not happy about it. Yeah, let's wait till we have to. Yeah, so I would rather milk the intensity first. Let's continue driving intensity up for as long as we can before I have to change the metric and introduce volume or frequency. And essentially what happens is when you get to a program like block training, that's a volume based program. It does have an inverse relationship where it starts with very high volume and relatively low intensity. It moves to very high intensity and relatively low volume, but over the course of the majority of the program, it's a relatively high volume program. DUP, daily undulating periodization, it's only high volume because it's so high frequency. So you actually don't do a lot of volume in any one lift in any one day, but you do all of the lifts pretty much every day, four days a week. Yeah. And so the frequency itself, and so that becomes the driving metric. So I can actually have programs in the back of my pocket, my sleeve that I can play or I can say, okay, when the intensity cannot constantly go up, I can use volume or frequency to drive the stress needed to break homeostasis to get the adaptation. So what Old Man Texas Method does is it continues to use intensity as the driving metric force, right? Instead it spreads it out over the course of a week. One, the intensity always goes up on Monday and the intensity always goes up on Friday. Now the Friday day for the squat is the most important day because that has to keep going up. It has to happen. So is there a time in that sort of Old Man Texas or even Standard Texas where I may have a top set of five and then back off sets of five? Sure, maybe. Because the stress becomes too high, right? So not for everybody, but that's possible. But the intensity day on the squat and the intensity day on the presses and the bench presses must always go up. And it's necessary actually for you to get your next five-fives or three-fives on the next Monday. Like if you don't do that heavy on Friday, you're gonna have hell getting the heavier five set of five on Monday and three set of five in the case. So it takes us, people overlook that. Now in Texas, it's actually, that's a place on the Texas method or Old Man Texas method is the place where I will actually start to do multiple sets on the deadlift. Yep, so I still may have an intensity day which might be one set of five or it's often one set of three or even two sets of three but often on the volume day for deadlift, I'll do two sets of five and then three sets of five because they just at some point they need the volume to keep driving the deadlift up. Remember that when we started this with linear progression, they were doing one set of five on the deadlift but they were doing it three times a week and often now you're alternating the deadlift with something else. If it's Old Man Texas method, it's not gonna be the power clean. It's probably the row. It might be the chin or it might be a combination thereof. And so if I am deadlifting every other session then it means that one week I'm gonna deadlift on Monday and Friday which is awesome. But on the other week I'm only gonna deadlift on Wednesday.  I often just have them go ahead and pull twice a week anyway. Monday, Friday, Monday, Friday, Monday, Friday, Friday. Which works okay. Yeah, I've done that as well. And that's fine. That's not that big of a, I don't have a problem with that either. So coach, we got linear progression go up every other day. Got Texas method or other HLM or whatever in their week long programs. You go up once a week. Where are the damn 14 day programs? Well, so yeah, you can still spread that out. So HLM works really well. Yeah, you can spread that over like 10 or 12 pretty nicely. You can't exactly, you're right. So I should really like HLM and I would actually probably go to HLM after I can't. High low medium. Sorry, high low medium. And again, what I'll often do. When you say usually don't, you mean for these early intermediate guys they just jettisoned out all that linear progression. That's what you mean, yeah. So I'm not saying that every person does the exact same programming. In the beginning they do, right? It's linear progression. And actually as we move more towards the advanced side it becomes more and more personalized. But most of my guys are gonna do, most of my guys are gonna do linear progression for as long as possible. A Texas variant for a while. And then a variant of heavy light medium which is really just an extension of Texas method that's not quite as stressful because the stress becomes. It comes down. Yeah, right. So, and then I can also peak them easily on the heavy light medium and then we move to four day split. And there's lots of options for a four day split and we'll talk about that in an episode soon for sure. I think there'll be a lot of people that will be glad to hear a little bit about what this whole Man-Texas method looks like because I get a lot of questions and I don't think there's an article anywhere about it.  No, no, no. Thanks for listening. Talk to you soon.


Facebook, Google, Dominating Facebook channels, and content, and the select of oversight. And making sure that we can be across these kind of sources of information.  And it's called blockchain, and I would say it's the new technology of trust. Because it will be a new impact between each other, a new trend. Because it's leveraging the open internet, leveraging the cryptographic functionality, and you will see how long it will get faster, more secure, especially when it comes to the information and also to establish a new way of trust. So something important to do, being more to a central model, you will see a totally different model. And let me explain that in a small animation that I think we are at the beginning of a major change. If you look at today how we interact, is we transfer over the internet information through the open internet. We always copy music, PDF, PowerPoint, whatever, if you want to change this between two parts. So there's a lot of duplication, and most of the cases somebody verifies that this is being processed in the right way. And that is the process on which it generates a lot of complexity. All the parties have to read one side of their position. They have to maintain their own hopes. And then after a week and a half, especially in the financial services industry, you buy and sell. So it takes a few days to have a lot of these involved. And it takes time, and it's important. And now with the blockchain, what's the desire is that we are moving now in a world that physical assets can be transferred. That means we don't want to have a duplication of assets, whatever is out there. We don't want to use a third party. It's almost like a self-regulated base. Few exchange doing a deal, doing a third party. And so the blockchain thing at the end, it's something very direct peer-to-peer. The information that is stored on the Internet cannot be changed. And it's happening without a third party. So in a little minutes, potentially, maybe Facebook, Uber, playing houses. Other third parties that usually between two parties are involved. Just the key point, what is the blockchain? I think you can discuss this in four talks. One is everything is digital, there's no paperwork anymore. Everything will be stored in a way. And the difference is that the network, that means you and I and other parties will verify in an automated way a third party will have to verify. So it's a very decent trust. And I will have an example in a minute about the media industry that the media at the end will make sure that those news are provided for the right months and also for the project. And it's secure. So you cannot add or change this information if it's out there. Very fine. It's secure through graphic and private law. So it's a completely different way of how we interact going forward. And it means, what's the difference? At the end, the middle man, it can be a buyer and a seller. It can be an eBay that will disappear. There will be a direct relationship between an investor and the company, somebody will invest. And that's for me a real example right now in the industry because the venture capital industry is getting diminished by this because there's no way to get out of this and walk in that companies can sell their virtual stocks through the blockchain. And it's getting more funding right now. And then from the front of the blockchain, then the venture capital. So venture capital is the middle person is already under pressure. It's the same also between reader and producer, the middle man is changing this information. And this is a serious business because they are very comparable with what happened in the years ago. We're talking about 2,000 startups working in old industries on a free media, logistic out there building up new solutions. And if you look at how much money already is invested, very similar than today in the start of companies 10 years ago, 500 million per year. But that number, that was the outlast. 700 million invested in blockchain this year will be over. Because with the technology, there's no access to capital that was not in place before. So we see a democratization of access to capital that usually we saw bottlenecks to private equity firms. Venture capital firms will be free. So there's something that I want to put you on here or put this on the record because this has the impact on geography, on region, on financial. Let me walk you through one example. I'm not talking about financial services. Financial services banking is far over. I would say very close to that is immediate. And Susan mentioned that now we run into some content introduced out there, and nobody can verify the level of control of the blockchain. So there's a company out there. There are many other decentralized startups out there that are putting out news networks called Decentralized News Networks that is a platform for producer, writers, reviewers, that means the producer provides funds. There is a community of past check, review, and the community is there. Also, they get paid for that. They provide based on God and business information and provides information to the community. And there's an incentive for that because everybody gets paid for it. So there is a way also to increase the adoption for that. So there's collaboration that's decentralized and there's a factual way also to put information out there. So something that's really fascinating to watch, I think the adoption of those kind of technology will be faster than I would say a paper. I don't have over three years to get a piece of news. I think it will be possible because it's a monetary effect that the user gets instead of a company like Facebook for marketing. And this can be applied for all in all in three, like financial services, logistics out there, and other industries. At the end, we're talking about significant benefits from this sector, exactly. We're talking about simplification. We're talking about simple speed for transparency from point of view. But the technology itself, at the end, it's a new technology all across. That is our community both in England and there is a momentum across the region and I think it's unstoppable. Thank you very much. I must say I still feel comfortable. I suspect that there's a chance, man. I also feel secure because if there's no graph in the internet, perhaps. It's a record because everything will be a record on the internet. So the traceability of all this is even higher from an ML on the market than you would expect from that perspective. You see, and it's a global theme. It's not limited to global countries, et cetera, including across the world. That's great. Thank you. And what I'm hoping is when we get time to question the people in the audience who will have a specific thing to ask, the whole idea of decentralizing here fascinates me partly because it seems to eliminate the whole idea of the fashion. The fashion editors, training, crafts, you know, if everything is a hobby, then who do you trust? You see, all the time, could get incentivized to be part of the region because they get hate-coupling. So that's a different role that the editor could play in the future. As a former editor, I'd probably make more money with your blockchains. Absolutely. I could say, first of all, I know that media access to information can be very convenient. Anyway, thank you.