OK. So good afternoon, everyone. So very glad to have this chance to share with our latest contribution and the solution proposals for the OpenStack Power Hybrid Cloud, Open Hybrid Cloud solution. I'm Dennis Koo, Chief Architect of Huawei Cloud Computing Solution. I will be the main speaker for this session. And my colleague, who is the hybrid cloud architect Leo Lee, will assist me for the live demo of this session. So basically, it is well known that the key benefits that could be brought by the cloud computing technologies like TCO savings, the business agilities, can be brought by the IT infrastructure consolidations that is powered by the cloud operating system of OpenStack is especially achieved by means of the unified management entry point and standardized APIs for the on-demand infrastructure as a service. So the larger the range of the resource consolidations, the higher levels of resource automations and utilizations, as well as the better resource elasticities can be achieved in order to satisfy the rapid changing requirements on the business and market. So as we know that before the introduction of OpenStack, the legacy virtualization technologies like the VMware and Zen servers, they can be used for a small range of resource consolidation, which is based on the legacy, small cluster virtualizations and unified management. So after the introduction of OpenStack, the range of resource consolidations is enlarged to the whole data center range that is covering multiple clusters and even availability zones, meaning that the multiple clusters of virtual machines can be managed and automated through a unified single pane of glass, OpenStack, or the service consoles for all the cloud tenants. And also, of course, the scalabilities of each single cluster is enlarged to several tens of physical hosts to more than several hundreds of physical nodes within each cluster or AZ. So furthermore, as introduced by Huawei's proposed by Huawei's OpenStack cascading proposals, it can be further enabled to consolidate multiple data centers resources in the infrastructure layers to be a unified logical poolings that is covering multiple deployment site and instances of OpenStack. That is another major project that is covered by the so-called tri-circle project, also led by Huawei. So by adhering to the very same philosophy, is it possible to adopt the very same architectures to even further enlarge the infrastructure consolidation range to other third-party heterogeneous cloud? Our answer is yes. It is fully feasible. And in the following session of this slides, we will show you how the working mechanisms and architectures is working behind and how to what extent we can actually achieve the capabilities of cross heterogeneous cloud consolidations and how smooth experiences can be achieved via the unified management portal of OpenStack dashboards. OK, so it is well known about the common benefits that could be brought by the hybrid cloud to enterprise-private cloud constructions, especially, first of all, in terms of enabling, extending, and migration or scaling the resources from the private cloud to the public cloud, especially to satisfy the cloud burst requirement to handle the temporary large scale of resource requirement and enable the Dev and test in public cloud while smoothly migrate that whole certified environment without changing any configurations smoothly from the public cloud back to the private cloud. This is one of the typical application scenario of hybrid cloud, especially focusing on the users of a private cloud. Another major usage scenarios that have been identified is the private cloud to public cloud backup and recovery, which is featured by backing up the co-daters or non-confidential daters from the private cloud to the public cloud without the necessity of building his own NAS or massive storages within his cell phone data center sites. And of course, another major issues possibilities is trying to deploy the different sets of applications in different cloud point of presence. For example, mission critical and application backhand databases located within the private cloud while the non-mission critical or more temporary resource and bursty traffic patterns workloads being placed within the public cloud. But with all the relevant workload, with unified IP addressing, security planning, and governance, of course, both private and public cloud environments. So besides the benefit to the hybrid cloud, benefits to the private cloud, is there any value added to the public cloud scenarios? Our suggestion is that also it could be equally applicable to public cloud for these in order to build up some differentiators for public cloud operators. One of the potential cases might for the multinational enterprises, who will be one of the major type of customers of the public cloud services for telecom operators or other cloud carriers. It might be possible, for example, for a T-System public cloud that is trying to offer the public cloud services to China or Japan branch of German companies without the necessity of building T-System data centers in the territory of China or Japan. He can just leverage the local public cloud resources and utilize the hybrid cloud to establish the connectivity between the two clouds in order to offer a better interactive cloud services like video workspace to the remote cloud tenants without building his own data centers, which is close to users access proximity. Other cases might be useful cases, might be seamlessly moving workloads from non-open step public cloud or private cloud to the open step based public cloud. These migrations could be anticipated to be migrated in a very seamless manner so that the duration of service interruptions or the level of service continuities can be achieved as far as possible as the provider can do. And the final cases benefits for the public cloud hybrid scenarios is for satisfying, of course, the temporary bursty traffic requirement in case there is a shortage of resources for self-owned physical available resource pooling. So how about the technical readiness? And is there any blocking point for achieving this ideal usage scenarios of hybrid cloud? We think that there are still lots of challenges ahead. First of all, then is the challenges about the consistency, the capabilities, and API exposure, as well as the interactive consistencies across all different types of cloud capabilities that is covering both OpenStack, as well as the AWS from Amazon, VCloud from VMware, and Azure from Microsoft. So as can be seen, in various dimensions, including the image types, the metadata capability, the data volumes, the security rules, and the API differences, there is lots of differentiated available capabilities in all these dimensions across these heterogeneous cloud choices. So it is really hard for any cloud tenants or cloud administrators to provide the real unified management experiences across all these heterogeneous cloud backhands. And especially when the back-end capability is not available, it is even more difficult for the pure software based adaptation to smooth these differentiation. And the second biggest challenge is because the addresses, majorly the addresses of networking plannings and security policies are not fully unified, managed across the cloud boundaries. And the ACL and communication metrics need to be set up manually after the adjustment and all movement, migration of the relevant workload between the cloud presence. So these kinds of rescheduling of workflows across the cloud will bring tremendous complicated manual work efforts in the networking management environments. Third challenge could be the difficulties of moving the workloads across clouds with a single point, with a single one-click triggering of the whole migration tasks. Because of the images, first of all, the image types and format across these different types of hybrid cloud is quite different. And also the networking, the layer 4 to 7 networking capabilities, including the security group, firewall, and load balancing are also not fully managed across the cloud. So it will also bring lots of difficulties of moving workloads around the clouds and especially to do some automatic tasks of scaling the workloads without changing the networking and security attributes during the whole procedure. And fourth challenge is, of course, always will be the security potential breaches that could be introduced when trying to establish the secure guaranteed tunnels between the interconnected cloud resource poolings, both in the interconnecting networking channels, as well as the boundaries of the anti-doss borders of the public cloud offerings, as well as the potential security attacks between the tenant boundaries within the same hosted environments. So it will be also very crucial for guarantee the private cloud or the extended cloud environments when he is trying to apply the additional resources from another cloud and security governance range. So how could finally these key challenges be finally handled and also what the potential architectures behind could be satisfying these challenges and key requirements? Our answer is that by adopting the same philosophy of cascading or multi-site open stack by means of a unified cloud brokers that is setting on top of a series of heterogeneous cloud back-end, no matter whether these cloud back-ends is provided by a self-constructed data center or some third-party heterogeneous cloud already in presence, this including other third-party open-stack-based cloud or full heterogeneous cloud like Amazon's and vCloud, Azure's, and et cetera. So that these unified cloud brokers we're serving as the unified API entry point, no matter what type of cloud back-end is sitting behind and also sharing the very same service catalog, service orchestrations, and open stack, uniformed, open stack API exposures, and most of the importance, the quota management for all the tenants across all the underlying cloud resource providers. There will be unified and flexible deployments across all clouds and seamlessly workload movements between the clouds and very easy to invoke scalings across the cloud boundaries and, of course, the fully guaranteed securities. With more deep dive into the cloud brokers, under these end-to-end open-stack hybrid cloud is the cascading open-stack-based umbrella or the unified entry point of resource quota management and API exposures, as well as the service catalog that is covering all the back-end hybrid clouds. These cloud broker layers is fully standardized cascading open-stack-based, which is also named as the tricycle that is used to orchestrate and connect multiple clouds, no matter what is the semantic differences that is sitting behind these unified cascading open-stack umbrella. And what about the cloud broker? Underneath these unified umbrellas of cloud, what about the cloud gateways? That is also working in signage with the unified entry point of a cloud broker. Here, as can be seen, the cloud gateways is also consists of a key, first of all, the key controlling layer components from the open-stack, leveraging all the key elements and building blocks of open-stack of Nova, Sinda, and Neutron, talking the full standardized open-stack languages to cloud broker, while at the same time underneath these key fundamental compute storage and networking services, there is a series of crucial building blocks behind, including the cloud drivers, which is used to adapt the fundamental resource invocation API capabilities to the back-end heterogeneous cloud, including AWS, vCloud, and other future possible cloud backends. And V2V cloud for necessary cross-cloud image translations, hyper-switches for establishing the cross-cloud overlaying networkings and the border gateways, especially to guarantee the security and establish a highly security-guaranteed context and cyphered protected tunneling across the clouds. And of course, storage gateways, which could be used for migration, workload migrations, and real-time or incremental disaster recoveries across the cloud boundaries. So here's the standardized cloud gateways. It's just deployed on top of heterogeneous cloud back-end clouds corresponding to a specific OpenStack AZ. And here we just give you the more deep dive explanations of unified networking across the clouds that is covering the enabling the one networking across all the clouds with unified IP address management, layers 2, 3, connection across the clouds, and also the DTRS security channels across the clouds, as well as the multi-tenant overlaying VXLAN, layer 2 or layer 3 interconnectivities between the clouds. And of course, with the introductions of the so-called storage gateways, which is actually an overlaying storage layers on top of heterogeneous back-end cloud native underlying storages and the upper-layer virtual machines so that all the intermediary IO attempts will be intercepted by these storage gateways in the guest operating system building blocks, while at the same time making it possible to do the necessary incremental snapshot backup and disaster recovery across the whole cloud boundaries. And of course, while at the same time, it is necessary for enabling the API exposures in extra to the fully standardized API sets. And of course, by the way, for the purpose of the cross-cloud migration, workload migrations, the V2V gateways is also optionally present here in order to handle the task of a fully automated V2V translations across the different VM images types. And finally, of course, is the Docker. Here's the Docker over OpenStack hybrid cloud illustrations where each of the tenant will be deployed. It's a dedicated master or Docker container schedulers that is based on the Kubernetes. And also here's the OpenStack service orchestrations and workflow managers like Marano can be used to automatically deploy all these container resource management and schedulers, as well as surrounding VM environment for all these microservice Docker containers. And here specifically, by combining and running all the Docker application distributed on top of the OpenStack, it will be seamlessly bridging and combining the benefits of fully orchestrated storage and networking with that of the agile, fully guest OSD coupled Docker deployment on top of various kinds of hybrid clouds. With very seamless user experiences. And there will be, of course, comparing to the VM-based hybrid cloud approaches, this Docker-based hybrid cloud solutions will need no more VM image translations between the different hypervisors. And also there will be no so-called hypervisor drivers visible to the end users, the guest environments. OK, so that's just a brief overview of the key architectures that is employed to support the architectures of the OpenStack-powered hybrid cloud. So next, we would like to give you a live demo and show the what extent can be achieved for these seamless experiences and unified workload management across all these heterogeneous cloud where fully standardized OpenStack dashboard of Horizon. This is actually a modified, as can be seen, in the right side screen. This is a fully standardized OpenStack dashboard with just slide modification and enhancement to reflect the different specific availability zones that is corresponding to specific heterogeneous backhand cloud, including Amazon cloud in Singapore. And two heterogeneous cloud, one OpenStack cloud, deployed in Shenzhen, China. And the other V-cloud, VMware V-cloud, also deployed in Shenzhen. This is a fully live demo with all the operations really performed without any simulation. And the next following key, we will have a demo of five major cases. First one will be the unified management of multiple clouds via these Horizon-based portals, as can be seen. OK, so I will launch your instance from the OpenStack dashboard to any underlay cloud. So I choose the AWS cloud and give a name, test, and select an image, and select the KPL security group network, and the user data. So all these things is a standard OpenStack message. So we can use this message to launch any instance to Amazon or V-cloud. Yeah, during this demo cases, you can observe the fully unified user experiences without any difference on the operation capabilities on different types of backhand clouds. Because we are using the cascaded or the native OpenStack to be deployed, or you can consider it which is OpenStack-based cloud gateway, which is natively deployed in the third party heterogeneous cloud, like AWS and V-cloud, so that all your operation capabilities is 100% OpenStack compatible. So no need of any cross-heterogeneous cloud adaptation or loss of some certain capabilities, not compatible capabilities. OK, so this is done. We can continue to the next. Yeah, so just within minutes, you can see with the single virtual machine, it can be seamlessly provisioned in any of the backhand clouds. And also, back to the initial dashboard, we can also see that. Yeah, you can see after the provision, you can see from different key dimensions, including CPU, the number of virtual CPUs, RAM, volumes, and volume capacities. It's different resource distribution in different backhand clouds in terms of percentages for the specific cloud tenant. This is fully leveraging the ecosystems and the capabilities of the OpenStack communities. Yeah, so next demos, we would like to adopt an open-source online shopping systems, which is based on Megantel. Megantel is an open-source online shopping for fashion goods. And also, we are previously deploying these online shopping systems, so-called as e-more, e-more systems, on top of the OpenStack-based private cloud. So that cloud can be, for example, under the event of a rushing hour or promotion day or some Christmas holiday events, it is required to apply a huge amount of resources in a very short period of time in order to enable the cloud burst across the cloud boundaries of OpenStack, private cloud, and the Amazon public cloud. This is enabled, as demonstrated by this graph, enabled by deploying additional web front-end instances in the Amazons while maintaining all the load balancing and the backhand databases within the private cloud, so that all the interconnections, especially the big layer 2 connectivities between load balancers and the newly extended web instances, will be guaranteed and fully automated without any human configuration. OK, we will start the operation of these cross-clouds web app scaling. We don't have enough time, so maybe we just launch the instance and go to the next demo. So you say we have a load balance here. The load balance already have a floating IP bounded to the load balance. We could have 10 more minutes. So we connect to this IP so we can say the web server is working. And now, to do the test, I will remove the members from this load balance to add, to scale new member from Amazon. So here, I just delete this member from load balance, the right side. So we can see this server will go down. OK, one moment. Yeah, so before we extending the Amazon web instances, we are deleting the web front end from the OpenStack private cloud to demonstrate to you that after the extending of web front in the AWS, it is working again. Yeah. OK, so I scaled to new web front to Amazon. Yeah, OK, so you can see there's two new automatic launched instance to Amazon. And then you will also automatically join the load balance of our website. So three minutes later, this website will go back. Yeah, it will take a while for the launching of the web instances in the AWS and for the initialization. You see, Amazon is also doing this. This is AWS portal, as can be seen. It is being spawning the relevant instances in real time. OK, so I think we can go to the next. OK. We only have five minutes. We will return back for checking the results. And the next cases, we're going to use another interesting application, which is an online editor of Etherpad. This Etherpad, we will use this specific applications for the migration across the cloud, as well as the geographical redundancy across the OpenStack, across the VMware, OpenStack, and AWS. These three heterogeneous private and public clouds. OK. So first, we check this server, I think it's already ready now. And I will change to this. Etherpad is another project in OpenStack. So we have already deployed this Etherpad. Yeah, it is originally deployed in the vCloud, in the vCloud instance. And we will try to migrate these vCloud. And maybe you also need to enter into the vCloud client to check the instance. Yeah, this is the vCloud client. Five instances here. And this server, the Etherpad is here. And we just changed something. This is a migrate test from vCloud to OpenStack. OK. So we check. This Etherpad is saved. And now we just click Migrate from vCloud to OpenStack. Yeah, so within two minutes, it will be migrated in real time from vCloud to OpenStack. This is not a live migration. It's a volume-based migration. You can consider it as a cold migration, but without any persistent data loss during the migration. OK, you see the first Amazon website is coming back. OK, now it is working. This is auto-spanning. The newly extended web instances. And this one, the migration, you'll say it is done because we are doing the migration. So the Etherpad is reconnecting to the service. And so it needs about two minutes to do it. It's still migrating. OK, we can continue with the next one? Yeah. Yeah, the disaster recovery. Here, we are trying to demo you the cross-cloud disaster recovery from OpenStack to AWS. OK, so we have the same Etherpad application. We can first raise it and call it dr. Yeah, we will enter some customized content to check that when filled over, we can recover that content as the regional input. From OpenStack to AWS, OK? So this dr will do an incremental backup from OpenStack to AWS every 10 minutes. So to do this demo, I will do a manual backup to check it. So here the relevant volume will be incremental snapshot synchronous from the OpenStack to the AWS. And then we can base on these incremental snapshot and the regional volumes to recover the whole volumes and virtual machines, booting it from the AWS. OK, I will shut down this OpenStack dr service to simulate crash. Yeah, a real disaster recovery situation. So you can see this dr, it will service down here. And then we do recover to Amazon. So with this specific demo cases, actually this cross-cloud disaster recovery is achieved by means of so-called overlay storage gateway that is sitting between the virtual machines and the underlying native storages of the H2 Genius cloud, including vCloud and AWS, so that all the relevant IO attempts can be synchronized in real time or in incremental snapshot manner in asynchronous matters from one cloud to the other. OK, you can see the migration test is finished. Now this user path is already migrated from vCloud to our OpenStack. OK, so the dr, we are a little, I think, two minutes, but we don't run out. OK, so we just finished with the last demo case of container across the three H2 Genius cloud that is deploying the Docker containers, irrelevant of the back-end cloud types sitting behind. Do we still have time to do this? Maybe a short. OK, I think maybe. OK, so you can see here, we have a cluster here. And it is pre-deployed to multiple different cloud. So this is a Docker environment across three different cloud. So we can just deploy the Docker application into this environment. Yeah, here we are using the online blocking systems of WordPress, which is packaged in a Docker manner to be deployed across all these three H2 Genius cloud of OpenStack VMware and AWS. OK, so now you start to deploy across different cloud. Yeah. OK, so you did about one minute, so we don't have time. OK, so finally just a quick summary and a recap of the key ideas of these sessions is that the Unified OpenStack API and the ecosystems that is covering H2 Genius public and private cloud is fully feasible and possible by means of these cascading-based architectural approaches. And it can achieve consistent experiences and capabilities across all these H2 Genius cloud that is covering unified Layer 2-3 networkings, unified APP configuration networking management, one-click disaster recovery and migrations across the cloud, and also Docker-based container, lightweight agile deployment across the clouds. So finally, we are just proposing if you have more interest on the detailed demo cases and walking behind mechanisms, you can visit our booth, Huawei booth, with always waiting for you for all the relevant detailed explanations. And also, we are going to propose some incubate projects for these OpenStack-powered hybrid cloud that is featured by several incubate project proposals like the H2 Genius cloud AWS Azure and VCloud adapter, the V2V services, and the hyper network. Basically, these capabilities, the user plane capabilities will be left to the vendor-specific implementations. Here, we are just trying to organize the controlling layer, or the API service layer, standardizations in the open source group underneath the unified OpenStack umbrella. OK, thank you all. That's all for our demonstration today. Thank you. Thank you.


What is this now smells like contract negotiations team keep it clean. What is up, baby? It's angry man with another video. Hey you watching this right now. I love you. I love you so much I really do. I love you so much and I appreciate you know that know that so Somebody else who we love and appreciate Well, a lot of us there's some people that really don't but So more Jackson more Jackson's been a quarterback for the Baltimore Ravens for the past four and a half years They drafted them at the end of the first round in 2018 I mean and y'all know the rest of the story And there's been so many different parts and twists and turns of that story But that's what it is Lamar Jackson is right now is currently in contract negotiations with the Baltimore Ravens And so many people are wondering what is his next move going to be what is the Baltimore Ravens next move going to be? What is going down next so many people have looked at Instagram stories and figured I Lamar Jackson stand so many people have looked at media stories and figured all right Lamar Jackson's leaving But the truth of the matter is this that me I don't know what's gonna happen next you You don't know what's gonna happen next. We we just really don't know We don't know what's gonna go down with Lamar Jackson and the Baltimore Ravens next We all have our theories. We all have our assumptions We all have these things that we feel is is are gonna happen with this whole thing But we just really do not know And I think one thing that's been driving a lot of people extra crazy is the fact that both sides Have been very quiet on it. And when they do speak on it is something that's very vague. That's nothing too Nothing too extreme Nothing too detailed. It's all very simple stuff And again, that's the expectation from two sides that like keeping stuff on the hush hush With Lamar Jackson and his camp and the Baltimore Ravens They like keeping stuff on the low. So we get it and We're gonna see what happens next. We just got to wait it out. But jeremy fowler um a couple days ago He wrote an article on espn dot com And this part of the article was called will jackson return to Baltimore says quarterback Lamar Jackson future was a convenient talking point in mobile And most are in the same spot that they were six months ago Most believe the Baltimore Ravens should place the exclusive franchise tag on Jackson And try to work at a long-term deal knowing he secured for one more year. So That's been something that a lot of us have expected For the Baltimore Ravens to put the franchise tag on Lamar Jackson and that can buy them some more time figuring out exactly what they are going to do next And that can buy them more time to figure out a let's get Lamar Jackson signed to a long-term deal Let's really try to work this thing out. Let's try to hammer these things out Hand out the details of this contract the guaranteed money the years all that good stuff Or on the other hand it could buy them some more time. All right, we trying to trade Lamar Jackson Let's talk to these teams and figure out who can give us the best draft capital Maybe a player involved too. Is he going to go to the afc? Is it going to be the nfc? What's going to go down? So that gives the Baltimore Ravens more time For whatever's going to happen And if they're really undecided then it gives them more time to come up with a decision So no shocker's there back to the article He says and if it becomes clear that reaching a new contract is next to impossible The ravens can entertain trade offers closer to the draft So yeah, we just covered that part and with that Yeah, that's that would make sense because if they're going to trade Lamar They're going to want to trade him this year so they can get picks this year Hopefully they don't they don't trade Lamar this year, but that is a huge possibility that they do trade Lamar this year So they can get that draft capital Continuing says uh, and it could become a standoff because I wouldn't expect him to sign a tag for a while And afc executive said and they will be so far apart in the guaranteed money Again, that's something that we've been talking about on here literally for years for years Ever since um, it became possible that the ravens may not agree to a contract extension with Lamar Jackson before His deal was up Talked about it for a while on here that if it gets to the franchise tag Then I would expect things to get ugly Very ugly. I do not anticipate Lamar Jackson wanting to play on a franchise tag I do not anticipate Lamar Jackson playing on a franchise tag Um, so we'll see what happens. Anyway continuing with the article Uh, it says yes. Oh and real quick the franchise tag. They have uh, some of the deadlines with it for March 7th So a month from now March 7th is the deadline to apply the franchise tag to designate a player as your franchise player to to apply the franchise tag to one player But I want to say it's the middle of july is the deadline to where you can come up with a long term You can reach a long term deal with that player after the middle of july You can't sign them to a contract extension. That's it It's just franchise tag for the year. That's why so many players they hate it They hate it because it's a one-year deal and it's all guaranteed, which is great But Something goes wrong. Some happens. It's like your your future is not taking care of So but anyway, um back to the article it says yes, baltimore and jackson Lamar Jackson, of course could possibly be 100 million dollars apart there a massive gap to bridge So with that part That that that's a lot of money But he did leave some leeway in there because he said, uh, they could possibly Be 100 million dollars apart there. So he didn't make it a concrete thing that they are 100 million dollars apart He said they could possibly be 100 million dollars apart. See what I took from that is Think about this like if they 100 million dollars is a lot of money obviously and if you that far apart in contract talks It ain't looking good. Um, but even if Even if that's not the exact number of how far apart they are if you take that number and split it in half How much is that? It's 50 mil That's still a significant amount of money To be far apart on it. It still is so My thinking is for this If when there's smoke Oh, it's it's probably some fire burning there somewhere It probably is again. Is it 100 million dollars? We don't know like I said earlier There's so much stuff that we just really do not know. We don't know But with this article with this part of the article Even if it's half of that amount 50 mil That will still be a lot of money to be far apart Even if you take the 50 mil split that in half if even if it's 25 mil apart that they are That's still a lot of money. That's significant money Even if you split well if you split that in half what that's uh, 12.5 mil. I think I think it's 12.5 mil Whatever it is That wouldn't be as significant as the other ones, but you get what I'm saying um, so that's That's that's a big number and this is potentially a really big number to be far apart at but hey again You got time You got time if you really want to be technical Yeah, you got to the middle of july to get this thing worked out That that's your ultimate deadline But so much depends on what you really want to do what you really want to make happen Are you trying to sign him to a long-term deal? Are you truly trying to sign him to a long-term deal or are you planning on trading him?  What is your goal? So that's just something that we don't truly know Back to the article. It said those trade calls are coming I don't get the sense that that process has heated up in part because teams are assuming Jackson will be tagged. It's still very early on this one. Yes It certainly is and I think um to assume that Lamar Jackson will be franchised tag That would be a wise Assumption and one that a lot of us we we feel the exact same way on Um, but it's one of those things that we just got to wait it out and see And then the last part of the article is something that I think a lot of ravens fans It feel like we kind of see it coming. Um, it's like one of those Anyway, let me just read it says elsewhere the ravens typically don't take big swings at wide receiving free agency As we know, uh, but I talked to a few coaches in mobile who think Baltimore should add a pass catcher In large part because it's top two wide outs. Rashad Bateman and Devin Duvenay are coming off injury that part. I disagree with I don't think you should take a take a swing at a pass catcher because of the injuries That's like way at the bottom of the list for me My I think you should so you can diversify your offense. But anyway, uh, he said the ravens need fresh legs And a do it all wide receiver Sounds nice, right? Then he says like Alan Lazard would be a fit So, I mean again, Alan's all wouldn't be bad. Um, but I just, um I feel like that's that that is such a ravens mover receiver like Alan Lazard So We'll see we'll see. I think I saw something yesterday. I don't know how true it was or not that said He's looking to get paid around like 15 to 17 mil per year All right, Alan if if that's what you're trying to get paid you sir will not Be your raven you will not You you could the ravens could fly you out Take you to jimmies like they do.  You want some crab cakes, buddy? You want crab cakes? How about it? You could they could do all of that but When you tell them how much you want and if that's the number You better put them crab cakes in the to go box because it ain't happening That contract is definitely ain't having not as multiple if we're receiving 50 Please you know that ain't going down But anyway, shout out to uh shout out to LeMaw And shout out to the ravens too. We're gonna we're gonna see how this thing ends up man. It is It's crazy man, but anyway, hope y'all enjoying the pro bowl. Um, I I haven't watched it at all I watched the clip of that video from a couple days ago where they were doing a little throwing challenge And snoop he did his thing. Um, but I have not watched not one second of the pro bowl I thought I was in support of my guy snoop. I know mark andrew's there just in tucker I'm on the Humphrey. They haven't seen little updates on twitter and stuff, but I have not tuned in not one second and I probably won't but I still love y'all team keeping clean I'm tuned in with y'all and I love y'all and I rock with y'all man So like I said earlier at the beginning of this video, thank you You right you right there. Thank you. I love you and I appreciate you We out


At Audiology Associates of Prestonsburg, you can live your life the way you want and find the freedom of better hearing. With 40 years of being in the hearing care industry, you'll experience patient care that is specific to you with exceptional follow-up care that ensures your hearing and balance needs are being met. Audiology Associates at 1428 Northlake Drive in Prestonsburg. The Floyd County Sheriff's Department is now conducting their annual indoor simulation training for local churches and businesses. The simulation will teach security team members how to respond to active shooters and deescalate dangerous situations. This is the Milo. We've had it last year. I think we've had it a couple of years now. It's an interactive Milo device, an electronic device that doesn't use live ammunition and actually uses laser beams and such that people can actually get there and we teach them how to safely operate or handle a weapon. Teach them how to safely bring a situation, deescalate a situation, bring it under control in such a way that maybe lethal force cannot be used or shouldn't be used. That's our job is to try to teach you when and when not. Maybe teach you in a way that some things are out of your control and you just have to know when to call the police. By us doing it with church members, church security teams, security teams for schools, it gives them an understanding of maybe some things they may face. The simulation has various scenarios and gives local churches and businesses a chance to train for an active threat. Last year, Deputy Peter and I were the instructors of this class and it's very hard to kind of go through. Without him this year, I'm missing very badly. But one of the last classes we taught, he always said, never think it cannot happen around here. It was one of the last classes that we did teach together. And he said, don't ever think it couldn't happen, but we just want you to be better prepared in case something does happen. So we get complacent a lot of times. We start thinking that our life is just perfect and things are not going to happen. That's what we want everybody to think that when you think that things won't happen, believe me it can. And we want you to be more prepared. We want you to be able to face the situation safely if at all possible. To schedule an indoor simulation training, call the Fully County Sheriff's Department at<PHONE_NUMBER>. Reporting for Mountain Top News, I'm Brianna Robinson.


It was all business as the Brainerd Lakes Area Economic Development Corporation held its annual meeting today at the Arrowwood Lodge in Baxter. The meeting is held every year to discuss the previous year's achievements in business development in the area and the new businesses opening up in the coming year including a new brewery and winery. Also discussed at the meeting was the current state of the Minnesota economy and what the future holds for the region and the state. Well the good news is we have a strong economy here right now and we've got a diverse economy so we've been able to weather some of the economic challenges. Going forward though we have to pay attention to the challenges. We were the former chief of staff for Governor Tim Palanti was the keynote speaker of the meeting and talked about keeping Minnesota competitive in the global market. We were said that while there are many challenges facing Minnesota in the coming years including the growing talent gap there are also areas where Minnesota is highly regarded the top one being the good quality public education system. If you've enjoyed this segment of Lakeland News please consider making a tax deductible contribution to Lakeland Public Television.


Before going into prayer line, you know when Everyone started going in lines And like the line kept getting closer to me I started feeling a lot of tightness and a lot of fear inside and like a lot of shaking and When I got up there, and I noticed that he was coming closer to me. I felt like really tight and I felt myself like going be like Going back going going back and Basically didn't have any control over myself after that So when he was praying what happened instantly? Right after the prayer right After he was he put his hand on my chest once he lifted it I felt The pain and tightness lifting also Wow, and I know that there were unfortunately We weren't able to get the video clip today, but through that you were screaming. Was that you? No, that was not me, but you were conscious of all that was happening. Yes, I knew all of it was happening Okay, so after he finished with that prayer and declared you free You said that there was this burden this heaviness that lifted off. Yes. What were you experiencing before he declared you free in your life? What was going on? I felt a lot of loneliness and Isolation and I also felt like there was like a wall standing in between my prayer life my education basically anything really that's in my life and So just to confirm and to tell everybody once you receive prayer with Apostle John Sheehan He declared you free. You felt like that heaviness was lifted And did you see that breakthrough in your life afterwards? Yes, I mainly saw it through my prayer life at first I began going to morning prayers and I began attending power of evangelism Now the reason why I wanted her to share about her deliverance because She said that she always thought when she heard power evangelism She thought it was a great idea, but something was stopping her from going but right after you received that prayer You went yes, was it scary for you? Kind of But it was like it was really awesome a really good experience So let's go and explain how that you went to the power of evangelism and tell us a little bit what happened since it was your first time basically At first I was sort of just like watching everything happen, but then it got Sort of near the end where we were like wrapping up everything. We had I believe a couple Someone decided to go and see if they needed prayer. There was a lady who? Had back pain Mainly in her spine and neck pain and also shoulder pain. It was at a level 10 and I had someone guide me through prayer I was the one who was praying for her. It was honestly so cool So tell us you said that it was it was so cool for you What did it do for you after you saw that you you were praying for her, but did you receive the healing? What happened? I just like Became like hungry for it, you know wanting to see like more healings more people, you know coming to Christ You know knowing like his goodness and she received healing. Yes, she received healing come on Come on you guys give God a hand of applause This is an incredible testimony because right from the beginning she was facing a lot of opposition She was facing a wall that in education in her spiritual life like something was stopping her There was a limitation but this two weeks ago She received prayer with Apostle John Chi and what happened that? Limitation was lifted off so don't ever if there's something going on in your life If there's a limitation if there's something you can't get a receive a breakthrough We have to look and examine and see maybe this is a spiritual issue. I need to come against it I need to go to my church. I need to be hungry to Fight for it and so she went to the prayer line and it was removed and right as that empty not the emptiness, but the That spiritual wall that was she was facing it was lifted off and immediately She went into power evangelism and now she's getting hungry more and more for God That is our God We can go from one level to another level and that is because of God's healing of God's breakthrough that he can give Us in our lives. Amen So one other thing to tell everybody what would you advise those that are seeking a breakthrough or looking for a new level in their life? Well, honestly, you just need to take the initiative if you see that you were having problems in your life Where you see that you're not moving forward. Just know that that's not normal That's like mainly like a spiritual thing and you should seek a prayer try to get delivered and That's awesome. Thank you, Jessica so much


President, ladies and gentlemen, thank you. Brain drain. The brain drain is affecting many countries, regions, and local communities in the European Union. If it's not properly treated, the brain drain may affect the sustainability of the European project and may destroy the quality of life in both sending and receiving countries. Left unaddressed, it will have long-term and permanent effects on the future of the European Union and is likely to become a strategic threat. The issue of brain drain in the European Union is complex, calling for a pragmatic policy response from the European Union, Member States, local, and regional authorities. Local and regional authorities play a crucial role in addressing this issue, since local communities are the ones they are directly affected by the consequences of brain drain. Let's talk a little bit about the history of brain drain. This is not a new issue. It's a very old issue. Migration of educated people is more than 2,000 years old. For example, 2,000 years ago, there was a brain drain from Athens to Alexandria in the context of policies promoted by Ptolemy the first sauteer.  But no chance. The University of Arezzo, the University of Pisa, 1343, or Florence, 1349, were founded after migration from the University of Bologna. Also in the 1970s, the Bagwati tax proposed a tax on the income earned by the skilled migrants in the destination country to the benefit of the source country. But of course, this measure also didn't work, even is still present in the political discourse. So today, what is the solution? There is no universal solution. But we can discuss now about brain drain in the context of brain gain and brain circulation. And Commissioner Switzer already mentioned. And we have another advantage in this very moment. Yes, the freedom of movement, it's a fundamental value of the EU. It's a religion. We cannot debate about the vulnerability of the freedom of movement, but always about. What is the main point? We have to respect the freedom of movement, but everyone is free to move voluntarily inside the European Union. But no one should be forced to leave the country to the poverty and other economic reasons. I think this is the key. How can we respect the freedom of movement, but no one should be forced due to the economical conditions to leave his own country or village, or so on? So if we do not properly trigger the brain drain, we have a potential threat to the future of the European project. You know that the countries below the EU 28 average GDP per capita are mostly sending countries of skilled workers, like Romania, Bulgaria, Latvia, Lithuania, Croatia, or Poland. On the other side, the countries above the EU 28 average GDP per capita are the main destination countries of skilled EU movers, like Germany, UK, France, Italy, Netherlands, Spain, Austria, Belgium, Ireland, and so on. So in that very context, we do have to take in consideration the positive and the negative impacts of the brain drain. Solutions. How can we tackle the brain drain? And I'll be very limited due to the time which I have it. First, multi-level governments and multi-level approach. European and state level, local and regional level. Second, political commitment for cohesion policy. It's a must to keep at least the same amount of money for political cohesion policy because this cohesion policy should remain a long-term investment for all regions and is the main instrument to keep Europe together and to deal with brain drain. Third, education, education, education. That's the main source, the main advantage to keep people home. And you have a lot of examples of good results. Best practice is a local, regional level from this point of view. In the end, we have to deal with brain drain. Having in mind, we have to fight against a continuous, excessive brain drain. This is posing a great danger to our countries, to our region. Excessive, continuous brain drain. And you have to know the people who are living in the country, their ultimate dream is to come back. And they have to take an account of this. And we need to work together to deal with brain drain. In the end, I'd like to give special thanks to my expert professor, Hinta, from Babish Bay University.


Hello, everyone. Welcome to our talk with me today. I have you Piscar from Giga Ohm. My name is Rajiv Thakur and I represent Portworx by Pure Storage. You're welcome to our talk on platform engineering. Right to beer. Thank you. Thank you.  But I thought we can give our viewers a bit of a zoom into the world of platform engineering and how this function has evolved in all organizations going forward. It's, it's quite a mainstream function for innovation, right? What's your perspective on this platform engineering team from your point of view. Right, right. So I think platform engineering is still very close to DevOps. It's kind of a different way of achieving the same goals, the same outcomes, because DevOps really was about, you know, lessening the distance between DevOps, meaning we could deliver software, you know, faster, quicker, more often, etc. Now, the operations part of this was always important, right?  And that's kind of the gap that platform engineering is closing. It's still about DevOps, but it is about creating a service internally that allows, you know, development teams to deliver software and run it. So these platform are called internal dev platforms, internal development platforms, and really what they do is they take what's out there in the market, combine it in a smart way, create a service out of it, quote unquote, so that a dev team can get started quickly, can deliver quickly, and, you know, can put software, their software into production and keep it there, keep it reliant, keep it secure, keep it performant. Very well said.  And I think whenever I talk to, you know, the head of platform engineering teams at multiple companies or platform architects who are very instrumental to making, you know, architectural choices that go into an IDP right and making investments for their developer teams to actually have the tools they need to build the apps that are building the future of their organization. I think one thing that's always resonating to me is all platform engineering teams are looking to build sort of a practice that has a cloud operating model and an experience that's sort of giving that on demand self service experience for all of the pieces of the dev platform. Could you talk a little bit about that as well you mentioned speed, you know, that's kind of related to having this cloud operating model. Yeah, sure. So, I mean, there's so many elements to this right. And if it were easy, it would have been a solved problem already. Unfortunately, it's not we're in the middle of this. So yes, it's, you know, it's a fairly accepted rule. There's a fairly well thought out definition of all of this, but it's still in, in terms of maturity, it's still evolving it's still very much changing year over year, which also means it's, it's kind of hard to grasp but what are the most important things that we should care about right. Obviously there's infrastructure. You know software still runs on hardware surprise surprise. So we need to care about all of that, but it's kind of the layer cake that is built on top of it like the public clouds have done with their service offerings that we're now kind of seeing being replicated and kind of, you know, all of these tools from that toolbox are being slotted into a very opinionated single platform that people can use. So instead of giving you know people the public cloud toolbox and say hey go go have at it, figure it out. We're now creating these platforms and making those decisions to make very opinionated platforms the IDPs. It you know we're still creating platforms that have very much the deaf tooling aspect of it so it's still very much aimed at developers and everything they need to put, you know, put software into production. So that's the ICD pipelines that is git repositories that is observability to see how their software is doing to make adjustments to troubleshoot. It's very much you know security scanning pre production so making sure images are safe and have been scanned to create as bombs etc etc, but it's also very much the operational part making sure that once we're in production that we have the tooling to be performing to be secure to be compliant to to be able to do blue green deployments etc etc. That's all like I said you know the list goes on and on this is very much still a work in progress as to what we need to put into an IDP, but we're at least kind of seeing the outlines of what used to be very much the pipeline area, the very deaf focused pre production focused area now being combined with the productionizing of these apps making sure that they actually are able to know to run in production and stator. Yeah, no very well said I agree and I think the point of view that you're bringing is that you know while they are building IDPs, they have to make sure that there's continuous app development happening by developers, and the security policies are still you know dynamic and and you know always always available to make sure apps are built securely. I think one thing that we're also noticing you know, which is what you reemphasized is that you know the cloud actually, you know, taught us how you can bring services to consumers and users of services right and infrastructure is now not something nobody's scared about they just expect it to be available. Right and that's, that's what the cloud taught us so having that operating model everywhere whether it's for, you know, storage or networking or compute, or even databases or for your app tooling and you know dev dev app services to just do test test and dev or even for security right is just a standard expectation that is from every platform engineering team out there when they build IDPs. And the other nuance that I want to add here you is because there is so much choice in, you know, choosing a cloud provider or also due to sometimes availability of a cloud provider in certain regions across the world, because most most of the cloud platform engineering teams actually build a global practice and an IDP that's global. They have to think about, you know, residency needs, and also their data residency needs as it relates to a service availability from a developer or even, you know, a specific on prem vendor for infrastructure. So we've seen IDPs being built with this mentality of platform engineering that is, you know, build once run anywhere, and port anywhere right so it's this concept of how do I build an IDP that is truly cloud neutral right, no matter what investments or constraints I have from one region to the other in a specific cloud provider and info provider. The IDP should still deliver that same experience everywhere. Yeah, I like that because especially, you know, no cloud is the same right. So some clouds are better at databases and clouds are better at, I don't know message cues, some of our are better at bare metal services so you don't necessarily want to just use one cloud. Very realistically, you're not you're probably multicloud you're using multiple clouds, but then kind of integrating the different pieces that you use from each of those clouds becomes an issue. And the IDP is uniquely positioned to help solve that problem, because now you're kind of creating an overlay, at least from a usability standpoint, so that all of these different services from all of these different clouds can be used in a single portal, making it so much easier to consume all of these services, because that's kind of a thought that's been sticking in the back of my mind we went from you know on prem to DevOps to platform engineering cloud is somewhere in between. And the beauty of an IDP is that, you know, people that are knowledgeable, make the choice for a certain set of features or a certain set of products for that specific area, meaning that I as a developer no longer have to think about okay am I going to use, you know, RDS as my database layer or am I going to do something else. All of these choices have been made already for me by the experts. So I can just get on with my work right and I don't need to provision a database from scratch I can just point and click somewhere in the IDP, and then you know automatically a database instance shows up. And like that's that's kind of the magic of having an IDP one but also selecting the vendors that are able to deliver on those services right. Yeah, no very well said I agree and you know one other thing that I think platform engineering teams also care about you is this you know, enterprise grade capabilities and really the platforms resiliency because you know these apps while they may be standardized, you know, they are truly, you know, stateful apps, and you know, initially folks are building stateless apps on containers due to the nature of containers. But you know put works as in the leader in this area for deploying stateful apps on on Kubernetes and you know helped multiple customers from all verticals, you know, achieve that sort of zero RPO. You know, these modern apps have delivered some game changing experiences, including in the pandemic where, you know, vaccines were being you know delivered and you know, at light speed right and that's just one example from the healthcare industry, because of what we did with COVID, and you know all the needs of the entire human population where there was a need to accelerate, bringing a new vaccine to the market and we've held multiple healthcare providers, you know, build that kind of a platform which is not only fast containers, but also this resiliency, where there's full fault tolerance right if one data center or storage goes down, your apps are still you know unaffected, because you know that's that's where stateless comes in. So, how important is these stateful applications, which are, you know built on containers that are stateless, right by nature, when it comes to building an IDP from your point of view. That's crucial. I mean we, yes we started out with stateless apps on containers, both because it was technically, you know what we could do, and especially the storage side of Kubernetes wasn't as mature back in you know the early days. But also we quickly realized that almost no app is stateless, because what do applications do they process data right that's that really, if you look at it that's all they do and that you know that makes infrastructure and storage specifically one of the bed rocks of all of this like all we do with cloud native with cloud with IDPs with platform engineering, all of this simply comes down to you, you know having these resources available in a way that makes them consumable by the developer directly. And that's why I love writing the work that I write for giga ohm specifically specifically around Kubernetes data storage is because we take something very fundamental that I know, you know I've been trained as a storage engineer, and we apply it in a way that is very abstracted for the developer to consume directly. One of the biggest, or the best examples of this is pds as a progress data services, where, you know, you're just as a developer just able to deploy a database on storage somewhere, and it happens. They don't need to think about it like that for a developer is is just fantastic. Right, but it's, it's so it's super interesting to me to see that it's still very much dependent on these lower layers of actual infrastructure. In a way that is, you know, self service on demand. It's easy to deploy. Someone has actually thought about it, you know someone who's the expert and made same default choices for security for performance for scaling for, you know, whatever. And that expertise is kind of codified put into the templates and into the defaults. So I as a developer, no longer have to think about that. Like that's kind of where I hope an IDP as a concept will evolve to that vendors like Portworx provide their expertise codified put it into software and deliver it as part of an IDP so that your expertise can now be used by whoever's using an IDP right that's kind of my ideal state, you know maybe two to five years or two to three years into the future. So that we can actually use all of this expertise all of these different vendor vendors have like that that would be ideal. So that's why you framed it and you know thanks thanks for bringing you know data storage into the conversation. Obviously, that's very close to us and what we do here at Portworx as we're building that platform as well to deliver these services to platform and then you know sort of help make the IDP successful for the data storage needs. So if I were to summarize kind of the five care about of platform engineering teams based on our discussions for the you for the users here and viewers. I think it's you know if I may say it's all about you know building that cloud operating model, which is kind of neutral in the sense where whatever organizational choices are made by the CIOs or CTO teams to invest in multiple clouds or on prem and hybrid environments. The IDP kind of supports that bring in the same experience everywhere for infrastructure and that operating model is common at the same time. You know all of the classic enterprise great requirements around security, you know, resiliency and stateful labs that will be deployed on containers, all of those have to be remembered. So these are things that platform engineering teams will care about, including the newness, you know that platform engineering teams and developers need right which is self service access to everything. So they can do continuous app development and also the flexibility to build once and and you know run it everywhere and also port it when necessary. So really enjoyed this conversation you and could you transition a little bit to kind of the criteria you used for Kubernetes data storage the readers have come out so I'm glad the viewers can download it and everything. Absolutely. So, again, I mean, we're still talking about storage right, even in a cloud native world. So we're kind of assuming things like, you know, it, it has snapshots, it's performance, it's, you know, it has some kind of data optimization technology or multiple of them in there.  That's kind of table stakes right. But we do specifically look for certain features if we're talking about Kubernetes data storage solutions. And those are solutions that don't necessarily run on Kubernetes although co-locating would be nice from an architectural point of view makes it much more flexible easier to deploy. So what we're specifically looking at is solutions that offer storage to Kubernetes environments. And so that means the integration between Kubernetes and the storage environment kind of has to go both ways. And that integration has to be top much so that the storage environment knows that they're talking to a Kubernetes cluster with you know certain pods or certain storage classes, etc. So in that extension, we need to have some kind of CSI compatibility for various reasons, you know, cloning snapshot and etc. So that we can expose those functionalities that the storage platform already has directly to the Kubernetes users, to the developers, because in a lot of cases it's the developers that want to create a snapshot and if they have to call someone, or you know file support that says hey go make me a snapshot please. Doesn't make sense right we want it to be self service on demand. And so that's why we look for these kind of integrations. And then naturally this kind of extends into data replication as well. Yes, we assume data replication is part of the solution but it hasn't been exposed to Kubernetes can we leverage those replication services directly from a Kubernetes, you know, YAML file to a kubectl or whatever, so that the user itself so the developer can take advantage of those features instead of having to go through a storage admin. Lastly kind of that extends naturally into data footprint optimization so some kind of compression dedube etc. Because it's still storage. We assume it's able to be optimized to to make for a better solution overall in terms of cost. And then we're we also very much look at telemetry visibility observability insights stuff like that, from a couple different perspective. So firstly, we want to know that our source infrastructure is healthy and you know we don't run out of physical space etc etc the cloud solves part of it of this of course but in a non-prem environment that is still very important. But also we want to give information about the performance of application specifically back to the user back to the app developer. So having that layer of integration and visibility is also very important. And then lastly I'll touch on this a little bit because you know this whole webinar is about developer experience. But we take an overall look at how well the developer can interact with the storage environment directly or indirectly, because I think that's kind of a key factor for successful adoption of specifically a storage solution for Kubernetes because the user of Kubernetes is the developer and not necessarily the storage admin understood. No, thank you. Thanks for reemphasizing all of your evaluation criteria and you know put works is very honored to be recognized by people amongst other players in the space, and we continue to focus on, you know building our platform to serve all of these and you know hope that we recognize in the future as well as we solve joint customer problems to bring stateful apps to market on Kubernetes storage, keeping all these requirements in mind for platform engineering teams. So I would like to thank you for joining us today, and for everyone as well to listen to us in this webinar. If you want to download the cloud native storage and enterprise, Kubernetes storage radars from geek ohm, please visit putworks.com, and you'll you'll see the link right there to download them. Thank you again you. You're welcome. Have a good day everyone. Bye.