Good afternoon, everyone at KubeCon in Europe. I'm sorry to not be there today, but I'm really looking forward to talking to you about what's going on in the TAG network and service mesh working groups. My name is Ken Owens. I am a vice president of cloud security and engineering at FISO, a financial services company. I have with me today Lee. Hello, hey, my name is Lee Kelko. I'm the founder and CEO of layer five. Ed Warnacky is also pictured here. He is another co-chair of TAG network. Ed sends his regrets today. And so, you know, just to kind of level said, we like to do this at every KubeCon. This is the, I think, eighth or ninth one that Lee and I have done together. And so on the second virtual one, hopefully we'll get to see you guys soon, maybe in the U.S. But in the cloud native world, a lot of things change in a way you think about doing enterprises and security and networking is a big one, right? And so the TAG network's mission statement is to really enable the widespread and successful deployment, development and operational resilience and intelligent network systems in a cloud native environment. So what that really means for Lee and Ed and I is that we really want to help to kind of clarify and inform what projects are needed as you go into the cloud native environment as you're here. Very quickly in this session, we have a lot of things that we've been doing over the last several years. We want to collaborate with individuals and we really want to attract developers and engineers that are coming up with great ideas in the network space. Gaps that you uncovered as you looked at going cloud native, as you deployed Kubernetes, as you find networking enhancements that are needed. We'd love you to bring those to us, whether it's service mesh related, whether it's firewall related. We don't really have a negative opinion about any of these technologies that are in use today and we know they all need to evolve and get better. So we're definitely want to invite you and we try to, for the most part, you'll see that the tag network group is very impartial. We're not trying to take over a project. We don't want to own, but we have our beliefs come from the CNCF beliefs that we're not going to make any kind of kings. Our goal is to just really work with you and to help steward your project through the different gates and phases of the CNCF project, which used to be easier than they are today. It's a lot more complicated today to get project through the CNCF and so we are here to kind of help you do that. And just like I mentioned before, Lee and I have been doing this for quite a long time. We were the original chairs for the CNCF working group way back in 2019 before the pandemic hit us. We had started with the cloud native, cloud networking interface, CNI. We were very involved in getting CNI and helping to do it CNI into the CNCF. As you can see, we were pretty busy that year. We got a lot of different projects in. We didn't stop as we rolled into 2020. We continued working with projects and you can see, you know, service mesh interface was sort of one of the, that was one of the big projects we had for that year. As we went into the rest of the year, we were doing chaos mesh and open service mesh. As we look at, you know, going into 2021, we brought in some emissary ingress and the KHEV. As you look at, you know, North America, we brought in the service mesh performance that you hear us talk a lot about today, Submariner, Silium and Messery, which are all big, big efforts that we are going to be talking about today in this session. At China, at the end of last year, we talked about FabEdge and that is now a CNCF project and something that we're excited about, especially Lee and I, we've been talking with Istio since 2019 is we're proposing that they are a CNCF project in, you know, this year. Other things that we like to do is Lee and I are very active in the community, right? And so we had an opportunity to provide a white paper to one of the nice, one of the bigger IEEE, Institute of Electrical and Electronics Engineers committees had a special session on cloud-native networking, which we were able to provide a willing nice paper into that bridge magazine. The bridge is part of Ada Kappa New, which is a part of IEEE and it's an honor society for electrical and computer engineering. And we are hot off the presses, we are continuing that effort and the research that Lee is working with the university and continuing to evolve and we have some more research we probably will be presenting in that IEEE publication as soon as possible. So, Lee, if you want to add anything to that. Yeah, it only gets more interesting as we go. The, you know, I think the last publication that we had done, it was, it laid the foundation for some of the, well, this next one about adaptive optimization. So is the current one under study? Actually, I think we have a slide on Mechmark a little bit later in this talk. And so part of the reason that Ken is stepping through each of these is, if you can't hear it in his voice, there's an implicit call to participate. And so the, yeah, this next research paper is, well, it's a doozy. Cool. So we'll get into some of our projects, right? So we've been working with a couple of different specifications and in this environment, it's really important to define specifications and be very clear about what it is you're trying to accomplish, right? And so one of the first things that we did was a service mesh interface, SMI, and that's a standard interface for service meshes on Kubernetes. As you know, trying to standardize anything is across a evolving technology like Kubernetes was not an easy thing to do. And this was a big body of work that we did. A lot of kudos to Lee and a lot of the work that he helped coordinate across the community to get that going. And then we published the SMP last year as a standard that kind of just helps describe a common terminology around how do you measure your performance of a service mesh? And then, you know, as we continue and continue down this path of trying to create specifications, one of the biggest issues we have in the industry is kind of getting this interoperability between different types of service meshes, right? And so we're trying to standardize the first step there is, and especially with Cloud Native, we really feel like APIs give us that common playing ground, right? So if we can kind of start with a set of standards around APIs that enable the services, that would then help us really build that federation model from day one versus, you know, waiting six or seven years and not having a model and then trying to create a new model from scratch. So we're trying to go after this problem very quickly. So on that topic of standards, right, we thought it would be good to talk about, you know, patterns. And patterns are similar to standards in that it's sort of trying to outlay what are the steps and what are the components and what are the set of like common controls or common behaviors or a common set of configurations that would be needed to support different types of use cases, right? And what do you want to say use case or pattern? We like to turn pattern. We think it's more of an engineering discipline to think about patterns instead of, you know, other common terms you could use here. But we have this GitHub site service mesh patterns. The value here, right, is that we're trying to look at enabling the business language around service mesh adoption, right? And so you have the behavior you're trying to capture and you're trying to look at it from a user, which is an application developer usually, right? How is that application developer going to get to take advantage of these patterns? They have to be agnostic, right? We can't just define one pattern for one technology, another pattern for another technology. We're trying to say these patterns are independent of the technology, independent of any solution that you're buying, right? We should be able to deliver the same experience to a development user community or the end user community without having to specify what the parameters are for that technology. And then the most important piece of this, and this is something that Lee and I have been tackling with in the industry for a decade or more, it has to be reusable, right? The world definition of how good your pattern is, is it defined in a way that can be picked up by different groups of individuals and they can use it without having to recustomize it for their use case. If they do want to add to it, Lee and I are great, super smart people, right? But we may have forgotten something and whoever's working with us on these patterns could have forgotten something. And as time goes on, you can believe there'll be new innovations and there'll be new things that come up that we hadn't thought about. And so the second big important thing about patterns is they can be added to, right? You're not creating something that has to live forever. These are living and breathing and they change over time. And as you can see on here, we call them building blocks, right? They're basic building blocks. And as new things come out, as new integration patterns come out, we'll be able to modify those with the community's environment, not just Lee or I doing it, but it'll be a community effort. Yeah. And to Ken's point there, some of those users of the patterns, sometimes they'll be referred to as a template or that's like the way in which they end up treating them occasionally as well as a common point of reference for measuring a couple of things, answering questions like, are we doing it right? And by it, that could be, and Ken's probably going to talk about these, but that could be using a function of the service mesh in this case, so a circuit breaker potentially, setting retries. And you could set 1,000 retries, you could set one retry. What's the common practice? And maybe more importantly, what are the considerations to account for as you're trying to find that magic number for how sensitive your circuit breaker is or the security posture of the mesh, how frequently your identities are generated, what the administrative domains are, how those are carved out between maybe you're in a multi-cluster environment. And so, yeah, to what Ken had described is to the extent that we can and to the extent that those of you are participating, these inevitably end up having best practices built in. And to what Ken was saying before, if you're taking, sort of, rationalize over a service mesh pattern and a service mesh specification, one is a lot more formal and can take quite some time to define those APIs that Ken was talking about. And in these patterns, we're looking at templates, we're looking at best practices, things that are reusable, just like Ken was saying. So, yeah, anyway, it's, there's a lot of patterns out there. There's a lot of things that the mesh can do. And so, it's a lot of patterns being described and collected. This is what we're really excited about, right? Because Lee presented last year in China, KubeCon that we had a few of these service patterns, right? So, we had circuit breaker, we had retries. I think we might have had manual TLS, but we didn't have multi-cluster yet. We didn't have a lot of filters created yet. I think we might have talked about, like, a JWT transformer. And so, as you can see, we've been adding and formalizing these patterns. We actually have a catalog now. And that, to me, is just really exciting for this community to know that, like, there's a community of patterns being developed and they're open. They're open for people to use. They're open for people to contribute to. And before we move on to something, we're going to move on to what we're doing next, right? So, that's okay. You can pull it back up. You know, with this, it's exciting because we know there's a lot of use around EBPF and a lot of stuff around OPA. And if you're not familiar with OPA, that's okay, right? OPA is Open Policy Agent. It's really critical when you get to a service mesh, especially. But in my opinion, just the cloud-native pattern itself, policy and declaring those policies become so critical and so important, right? And there's some interesting things that you could do in a pattern with collating events and doing a single tenant type of a test, doing some preprovisioning and seeing what happens after you do that preprovision and analysis, right? From an appointment side of things to kind of make sure your intention is being met versus, oh, I wonder if it's going to be met. Like, you know, let's actually define what we want, deploy it and see if we actually met what we met to meet in a preprovision state before we turn it live, right? Before we make it a neighbor. And so, to me, this is really exciting that we've been working on this. And I was going to ask you, Lee, to kind of talk a little bit about, like, I know this is coming soon, and, but before we get to the coming soon, please talk a little bit about what, like, the state of the current patterns that we have and some of the adoption you're seeing, and then you can kind of give a little bit of an overview of where the exciting pieces of the new policies that are coming soon. Will you see that being beneficial and how soon you see that being available? Yeah, of the current patterns that are there, they are, well, when a pattern is first described, it is, for certain, like, compatible with a given service mesh. The goal of each of the patterns is to be service mesh agnostic to the extent that, you know, that particular service mesh is capable of that, of the given function of the patterns that we're seeing on the screen here. You know, nearly any mesh that you could, well, actually, I should, so the circuit breaking of retries and of mutual TLS, like, all the service meshes that I can think of, that's, they've got that covered. And so as these patterns are being defined, while each mesh generally has mutual TLS circuit breaking and retries, they have that capability, they don't all implement it the same way, which is what Ken was speaking to about service mesh interface and service mesh performance, the specifications to try to get each of the service meshes, well, to try to be able to define patterns like this in a uniform way is really reinforced by standard specs, standard APIs. And so they don't all implement these capabilities in the same way. So as the patterns are worked on, verifying their compatibility is part of the current ongoing work. Since last we've met, or since last we've given a deep dive into the service mesh working group, have been a number of additional WebAssembly filters that have been brought in. And like Ken was saying, these are open source, these are available to all. The WebAssembly filters, I was just talking about compatibility of the patterns to individual service meshes. If you think about the WebAssembly filters, these are provided in context of the service mesh running an envoy data plane. And so last I counted, I think there's about five or so, depends on how you count an open source service mesh project versus vendors offering of that project. But there's at least five or so meshes that are running envoy data planes, which means that there's at least five or so that support these filters. In an interesting way, as Ken was speaking to EBPF and OPA, there's a lesser number of service meshes that are natively cognizant of EBPF and utilize EBPF as a foundational data plane traffic filter. Some of them support EBPF optionally, and some of them, I was going to say, some of them only support EBPF, but I don't think that that's true. Ken had said that that Cilium had come into the CNCF since last we met, or last we gave an update at KubeCon. And I don't think that it's true that Cilium service mesh only supports EBPF as its CNI. I have to go, I have to go, look at that. One other thing I want to mention that Ken called out in really, I don't know if everyone would have caught it, but he was talking about this pre-provision policy. Normally, I have to expect, as people think about OPA and policies, that you're genuinely thinking about authorization use cases, securing things. The logo kind of intimates that to you, that it's, things are secure behind here, right? That there's a Sentinel. But at its core of its capability, OPA is, well, it allows you to define rules and evaluate those rules, those policies. And those policies don't necessarily have to do with authorization. So to Ken's example, if you want to make sure that, you know, that your environment is ready to go, it's possible to define that, this is the right word, that attestation in a policy, codify what it means to be ready, and then use the engine to evaluate it. And so kind of some interesting things. So we're, yeah, we'll see, we'll see what happens in six months when we speak again, if the coming soon is. Yeah, definitely. If you guys are interested in helping, you know, test some of these patterns and contribute, we definitely, as Lee mentioned, like always looking for environments, definitely reach out to us. And, well, and so there's service mesh performance. It's a CNCF project. It is, it's currently sandbox level. Ken was highlighting one of its sibling projects, SMI. And so service mesh performance is, well, I guess, you know, in some respects, much to my continued surprise, kind of a popular project. Like, so many people have this question around the overhead of a service mesh. A lot of people get the fact that the service mesh can provide a lot of value and that is becoming commonplace kind of where you find the Kubernetes you find a mesh. So they want characterize and understand the service mesh layer in terms of its performance. One of the things that this particular project has been enabling is a specification to express that in a standard way, but it's also been espousing. Well, it's been espousing the fact that it's not just speeds and feeds that you need that you should measure. That's about that's like kind of half the game, the ball game. The other half of the ball game is the value that you're deriving. So part, you know, like part of what you're trying to measure is you're the overhead in context of how things are performing from a quantitative, like sort of cold hard metrics perspective. And then the other portion of that is to assign value to the functions that are being provided by your infrastructure. And a lot of times that can be done in context of business performance metrics or application level metrics of how many shopping carts are open, how many are actually being successfully closed, how many are being impacted by your infrastructure and to help give people language to speak to about those two things overhead, you know, performance in context of overhead and performance in context of value, the value being derived. Meshmark is born as a cloud native value measurement index. And so Meshmark falls under the service mesh performance umbrella as a component of that project. And it is, well, it's actually the subject of a talk this week at service mesh con. And I believe that would have already happened as everyone is getting this update. So I kind of described the effort that Ken and I have spoken to about Meshmark.  And that is that Meshmark is so as a performance index, as it's measuring those cold hard overhead, the cold hard performance characteristics of your cloud native infrastructure, your compute, your compute, your network, your storage, and having a kind of a heavy emphasis on network. There are many utilization classes to quantify, to measure and to understand how well the infrastructure is running. So some of those classes, the classes themselves tend to focus on a particular type of resource. So if the network is being measured, that would be a utilization class because the network is a resource. You can measure the network in a number of different ways. Maybe you're measuring latency, maybe you're measuring throughput, or maybe you're measuring number of errors, or like an on and on and on and on. And maybe some of those are more important to you than the next. So maybe as that utilization efficiency number is being calculated, maybe that's really, maybe the one for latency is really important to you or not. And so you can, the Meshmark itself allows for you to assign a weight or a discount, a positive or a negative weight. And so there's a fair bit more to this. Ken has been involved in the Service Mesh Performance Project and Meshmark for some time and Intel, or a collection of folks at Intel have really been helping push this forward. And so, so quickly on that, you know, lead in touch on that, but you can also use things like cost, right? Cost can be one of the utilization classes, right? So the utilization classes are generic by nature, because you can kind of select the different parameters, you know, like in my case where I work, security would be a very important utilization class, right? And there's different aspects that we would, that we would add to these to the Meshmark performance for that and weights. And so it's a, it sounds complicated, it looks complicated. But when you apply it, it makes a lot of sense. And you're kind of doing this in your job, you just don't realize it, you're kind of inherently applying a couple of metrics and your own weights in your head to what you think should be there. The issue is you probably don't apply it equally and the same way every time. And you probably forget other things that are important at the time, but maybe another time you remember them. And so this sort of gives you a, what's nice about this is like what you were saying gives you a standard way of doing it. And it's backed by, you know, real information that you can show to your leadership. Hey, this is why we picked this choice. We looked at these parameters, we gave them these weights. If they disagree with the weights, you can change the weights and rerun it and show them it doesn't change the result, but at least they see why and what you're doing. So it's a really important effort. So, sorry, I just wanted to kind of throw that in, Lee. Yeah, totally. The financial aspect, yeah, that's a great example and the security aspect of how it isn't just about speeds and feeds. In some respects, I guess you could consider dollars, speeds and feeds, but their dollars are definitely a resource. You can spend them in different ways, OPEX, CAPEX, and yeah, yeah, anyway, the two of us are both excited about it. So, you know, check out the service mesh contact. One of the other initiatives that gets stewarded under the service mesh working group is Nighthawk. Nighthawk is, well, I don't want to, it is a load generator. It's a layer 7 performance characterization tool. It was born in the same Petri dish as Envoy. It was born kind of adjacent to Envoy written in C++. It's been quite helpful as we do a lot of performance related analysis. This one gets me pretty excited as there's some, there's work that is ensuing around adaptive load control and I hesitate to begin to describe that work because Ken will have to shut me up. But visit the URL on the adaptive load control stuff, I think. Yeah. And it still has the coolest image or icon of you consider all the projects in the CNCF, I think. Yeah, I think so. So, we've been talking a lot, you know, so in the service mesh working group, we do the focus as a service mesh. There's a lot of things to cover. Ken just mentioned security, which we ended up talking about performance so much that like there's security, there's performance, there's observability, there's uniformity, like there's like conformance. Are each of these service meshes conforming to service mesh interface? The set of APIs that that project defines. Well, there's tests that have been defined and instrumentation tooling in the mesh re-project for validating whether or not the service meshes are adhering to the specs. SMP service mesh performance that we were just talking about. One of the outside of it being a spec and outside of mesh mark and publications, research publications coming out from that project. So, too, are a few of the contributors working within the CNCF labs, which behind the scenes is the Equinex data centers. So, they've been using mesh re they've got automation in place to provision any number of double 10 different types of service meshes and deploy sample workloads, generate load, do a performance characterization and retrieve the results of those tests. And those have been running for a little while. So, we're about up to 40,000 test results collected. Some analysis is being performed and some of those results are being published on the dashboard there. Ken was mentioning the patterns, about 60 patterns defined now. I suspect there are others that Ken was saying, please come and contribute, please come in, you know, sift through the catalog. Probably missing some, you might have some that you'd like to define. So, the initiative, well, it might not seem that way up front. The initiatives are definitely intermeshed. They're definitely related. And as we go to wrap up, Ken, if we didn't do it already, we're calling for participation, we're calling for people to come and join us. Join us, you know, if you can make the meeting times, we meet twice a month. So, that's a great place to come over, participate, be impactful. Or, if the meeting time isn't conducive to your sleep, there's a slack and there's also the mailing list. So, don't hesitate. If you saw something that sparked your interest, the folks that are involved are quite amenable to a suggestion and looking to collaborate. And so, Ken, I don't know if I missed anything there. No, anything else to add was, we do have the meeting minutes listed on the slide and being that we are an open source project, we are open to anyone to come and take a look at what we've been doing and working on. And Lee does a great job of collecting interesting topics for the meetings. We get a good set of individuals, a core group that we put together over the last several years and happy to have you join us and get involved. At any point, we're happy for that participation and you can learn more about us with those meeting minutes and kind of what we talk about and who's involved. Ken, question for you. I get this a fair bit, but you were saying, hey, there's the meeting minutes, come jump in. Clarification, do individuals, people that want to come participate, do they have to belong to a CNCF member organization to have a seat at the table to come and add to the agenda? No, absolutely not. We are very open to participation from anyone who's interested. You don't have to be a member company, you don't have to sign any blood with the Linux Foundation to come in and join us. And we do ask though, there is a, I don't think we have access to them, I get in trouble for pulling this up, but we do have, in the CNCF, we do have like a code of conduct. And so we do expect you to follow the code of conduct and if you're not a member organization, you should treat everyone with respect and that kind of, all that really good stuff that we want to make sure we're doing as people, as humans on this earth, we don't want to be, we have enough mess to deal with without having to be mean to each other, right?  Oh, nice. Well, that's it then, I guess go off and be good humans and come and participate in TAG Network.


Pike County is expected to experience severe weather during the evening and being sure to stay prepared is important. With the temperature, we're the right now the warmest temperature in eastern Kentucky and the way the air flow, the outflow of the weather is happening, the convection. We're looking like we're in a, uh, we're in a position that we could probably sustain some, uh, inclement weather. Appalachian Wireless, where your connections matter the most. Right now, get up to $550 off select devices on new or renewed line with the Appalachian Unlimited or Mix and Mash plan. Offer good in store only. We are you. We are Appalachian Wireless. The weather is expected to come in waves with possible strong winds. Residents are advised to secure any outdoor objects that may be carried away by strong gusts of wind. Stay away from windows and keep an eye on local weather stations. Some parts of the county were hit with thunderstorms earlier in the day, but conditions are expected to worsen for the rest of the county. Yeah, if you if you have a weather radio, uh, stay tuned to that weather radio. Stay close to your weather radio. If you have, um, uh, any kind of weather apps on your phone, uh, stay in tune to those, uh, try to make sure that, uh, if you have, um, if you have cellular devices, um, that if that's where you get your warnings from, make sure that they're charged. While today's weather is expected to be hazardous, April is tornado Awareness Month and Pike County Emergency Management is going to be distributing weather radio starting Wednesday, April 10th at the Shelby Valley Senior Citizen Center. For mountaintop news, I'm Kelsey Fidel.


What's up guys? Today we're back with part two of this battle against Yu-Gi-Moh that junior slash Alberto sent us. It's gonna be pretty awesome. First of all, we're gonna be opening the Galactic Overlord First Edition Booster Box. We also have 24 Unlimited Lord of Tachyon Galaxy packs all in this video, all against Yu-Gi-Moh. So make sure you guys go check out his video. And the giveaway for this video will be all the super rares we pull in all 48 of the packs. So there's a lot of super rares in here. You guys have a lot of chances. There's gonna be two different winners. One for the Galactic Overlord and one for the Lord of Tachyon. So let's go ahead and open this box up. Alright, now we can kind of mix these up a little bit and we can do both. Hopefully we can pull a Ghost Raer. Hopefully we can beat Yu-Gi-Moh. Last time we let him win, obviously we weren't trying to win. Now we're trying to win. Now we're getting serious. So I'm gonna move this a little bit out of the way so that we can, there we go. I almost flew out of my hand. Okay, let's try and get a Ghost Raer, Ultimate Raer, Secret Raer. Super rares for you guys, so hopefully something good there. And let's see what we can pull. Hopefully you guys enjoyed the streams or stream. Maybe I did another one. I don't know. I'm recording this on Saturday. We did the Soul, or not the Soul, but the Pokemon Silver stream Friday at like midnight. So that was pretty fun. Let's do a Lord of Tachyon Galaxy. That was on Twitch. So make sure you guys check out my Twitch channel down below. And that was pretty fun. And we're gonna do some more like dualings on YouTube, I think, some stuff like that. So let me know if there's any other games you'd want to see. I did order a PC, finally. I had a lot of help from you guys. And I did order one. And it's custom, so it's gonna be like five to six weeks before I can get it. But then maybe we can play some more powerful games. And I'll be able to stream them without any issues. But a Fly Oak. Heretic Seal of Beneishment. And a Bouncer Guard. Okay, all right, all right. Okay, so far we have pulled nothing. But hopefully we can end that here. Can we get the Galaxy out? No, Lord of Tachyon Galaxy. No, number 107. Not Lord of Tachyon. That's the name of the set. Tachyon Drag. Galaxy has Tachyon Dragon. There we go. Secret Rare. I always get this one. The Brotherhood of the Firefist Coyote, mind-drain. I don't think this one's very good. Though the Firefists are not very valuable. But a Secret Rare, just out of these, the Unlimited packs though. So that's okay, that's okay. All right, here we go. Come on, guys. Like the button for luck. We need to beat Yu-Gi-Mou because we let him win last time out of the goodness of our hearts. But now we're getting serious, okay? There's no creep. Oh, there's the Doom Donut. There's no creepy cone you need to beat us now. Ooh, oh, whoa. Oh, oh, oh. Oh, we pulled a Misprint Ultima. Look at that. Look at that. The name is so far off. I've never pulled anything like this.  Whoa, that is so cool. He's gonna be hyped about this, I think. That should bring the value up quite a bit, I would say. That is really cool. Cause it's not slightly off. That thing is out of the box. Like it's partially out of the box. That is really cool. That's a great pull. So this is a good start. Maybe the whole box will be Misprints. That is a great start. Yeah, Yu-Gi-Moh, yeah, that start for Yu-Gi-Moh. You gotta beat a Misprint Ultra Rare now, buddy. We think you can do it. We've got a Misprint Ultra, now let's get a, oh. Okay, now let's get a ghost. Ooh, okay, headgeared. He's got the headgear on, get ready for boxing. Okay, let's go to the next pack. Wow, that's pretty exciting. A Misprint Ultra Rare. That is super crazy. That name was way off. Lady of D, okay, the Lady of D. Oh, why is it, man, these are sticking together. What was that video where they kept sticking together like crazy? That was brutal. This is a 48 pack video, so it's gonna be a little bit longer, guys. Don't forget that the final round of this battle is the Duelist Genesis that we're opening up. It is gonna be, guys, this is insane. It is gonna be really awesome, that's all I gotta say. Ooh, a Harpy Channeler. This is like the best Ultra Rare in the set. Okay, look out, Yu-Gi-Mil. Look out, buddy. We've got an Ultra Rare. We've got a Misprint Ultra Rare. We've got a, not a regular Secret Rare, but other than that, we're doing good. Wow, that's crazy. Yeah, and if we pull this good in the Duelist Genesis, if we pull Stardust at all, it's gonna be crazy. All right, Overlay Owl. Come on, baby, Injector Earwig. Blade Bouncer. Storm. Light Ray Gear-Free. Ooh, Heretic Dragon of Sue. By the way, if you guys are YouTube members, don't forget to spam those Petite Moss, this Chickalates in the chat for luck. And if you are not a member, don't forget to like the button for luck, that as well. Gora Wing. Yeah, but if you are a member, you can use those Epic, what are they called? They're called, not emojis, that's what I was gonna say. Ooh, there we go. This one you guys can win. Ghost Fairy Alphobia. There we go. I don't know, you guys don't have to remind me what those little things are called. They're like emojis, but they're for the chat. Return. Mini Guts. Heretic. Berserk Scales. Ancient Dragons. Ooh, here's another super rare for you guys. Evoltile El Gnero. Super rare. Okay, what's in the rest of the bag? All right, next Lord of Tachyon pack. Let's pull something epic here. Let's pull something good. We got an Eagle Shark. Five Brothers. Doton, Doton, goo. That was crazy. Another of the Fire Fist. Panther Shark. All right, Shark Fortress. XC's Monster, by the way. I have XC summoned now. If you guys check out the dual link stream from last week, I XC summoned. Yes, it was the first time ever. I did it on stream. So now I'm an expert. XC's Wrath Overlay Owl. The Doom Donuts. Firefly. Light Ray Diablos. This is a misprint box. This box is misprinting. Ah! The Ultras are all misprinted. Trico Connection. Oh my, this one's even worse. No way. This is crazy. Where's the other one? Yugimo. I really hope that he didn't get these from the same case because then Yugimo will have the misprint as well. We don't want Yugimo to have the misprint so we can win. But then that would be good for Junior if they're both are misprinted. So, check that out. That one's like about to be onto the borders. That is insane. That is insane. Misprint opening. I'm hyped about this. Okay, so glad to go, Lord. Looks like the Ultras are misprinted. So that might be actually all of our Ultras. So I don't know if we'll get another one or not. Maybe the secrets are like that too, I doubt it, but they'll be really crazy. Kayo. XYZ Revenge. Okay. All right, on to the next misprinted pack. Come on. Come on. This is so crazy. This is so crazy. Nothing like a good misprint, you know, error pack, you know, something like that. Blade Bouncer. Guy, Guy, Guy, Gardner. Ooh, Hammer Bouncer. There's another one you guys can win. Super rare. Also, don't forget, guys, this Friday is a huge video, a video that I have been waiting to release for a while, but can't release until Friday. It's gonna be pretty big. It's gonna be pretty awesome. I hope you guys are there. And then we're gonna have another huge video, probably the day after. Like, huge, like massive. Little fairy. Okay, CXZ's. Mecha Fan and Beast Mega Raptor. Radius. So we have got a super rare, it's another one you guys can win. So make sure you guys like the button down there. Hit that like button. All right, all right. So we've pulled two Ultras. Maybe there's like, it's like an error box and there's like 50 Ultras in there. That'd be pretty cool. Desert Scales. Overlay Owl. Miniguts. Heretic Seal of Convocation. Overlay Eater, Bounds of Guard and Seal Ceremony. Lord of Tachyon. The Lord of Tachyon Galaxy. Give us a crazy card. We need an Ulti. We need a Ghost Secret. Shwitter. So it sees Block. Altitude Knight. Ooh, a Gauntlet Launcher. Okay, it's an Ultra. I don't think that's a great one, but it's an Ultra. We'll take it. They are loose packs, so you never know what you can get out of there. Could be crazy. All right, can we get another misprinted card? Come on. That's the goal here. And to beat Yuukimo. And to get a Ghost for her. And to get an Ultimate Rare. A lot of options. Watt Tail Dragon. Whoa. Evo Price. Ooh, Asset and Phantom Bouncer. Come on, Tachyon. Come on, Tachyon. Give us Number 107 Galaxy Eyes Tachyon Dragon. Spellbook of Miracles. We're killing stuff over here. Big whale. Speaking of whales, we never got the whale. Very sad. Okay. Galaxy. This is going too slow. There's 48 packs. This is gonna be a long video. This is gonna be a very long video. It's gonna be like 20 something minutes. Resort Scales. Mini Guts. Rocket Arrow Express. Injector Ladybug. Okay, Injector Ladybug. That's fine, that's fine. Here we go. Come with me, Dragon Carnation Radius Aerial Recharge. Ooh, Hysteric Sign. I think it's actually like a dollar or two, maybe? Pretty good super for you guys. That's a good one. All right, baby. The Overlay Owl. Bless us with a Ghost Rare Doom Donuts. I don't even remember what the Ghost Rare is in here. It's a cover card, but I don't remember what it's called. It's like Neo Galaxy Eyes or something like that, isn't it? Neo Galaxy Eyes? It's like number something, but Neo Galaxy Eyes. Okay, Black Falcon, Little Fairy. Come on, Summon Breaker. Breaker is a magical warrior. Out to do night. Concello Sombrae. I remember Sombrae from when we opened like 300 of these packs. Ah, Galactic Overlord, come on. Come on, we got a Butterfly Oak. Moonlit Papallion, Doom Donuts. Nitwit Outwit. Nah, Light Ray Gruffer. Red-Headed Oni. Oh, we got a Bootin. Love Bootin. All right, Lord of Tachyon. Oh, that one was like almost opened. That was weird. Okay, let's see if we have anything good here. Come on, Fire Formation. Yeah, that was weird. I don't know what to deal with that one. Come on, Galactic. Give us a good pack. Give us an Epic Pull Blade Bouncer. The Newt, Bright Star Dragon. That wacky magic by Resorcer. Hieratic Seal of the Sun Dragon Overlord. These packs look a little sketchy here. I wonder where he got them from. Well, you guys see this? That does not look good. I don't know, we've had some pulls in it, but that's weird. This one here, these last couple felt a little bit sketched. So I don't know, I don't know. I'll have to ask him where he got them from. I wonder if they're all from the same spot, cause like we already pulled foils on some of them and like good ones, we pulled the Harpy Chandler. If there's no like secret rear in here or something, then maybe we can be concerned. No, there's no like ultimate secret or ghost or anything. It's just Ultras and stuff. Then maybe there's something going on. All right, Insector Earwig, Blade Bouncer. Storm, Dr. Firefly, Hieratic Dragon, and a Rayton. All right. All right, let's see about this pack. Yeah, that one seems okay. Yeah, that seems like a normal pack. Five Brothers Explosion, Doton Doton. Sparks, Switchler, Battle Unboxer. Shark Fortress again, okay, Mimic. All right, we're getting down to like maybe the last third, last quarter of these packs. Probably the last third, I don't know. We probably have more than 12. Maybe a little bit more, it's in between there. Okay, well, I couldn't pull that. Return, Lady of D. I don't want him to sneak out, Doom Donuts. Hammer Shark, I haven't seen that one yet. Noble Knight, Artegous. You guys can win this one, super rare. Guys, you got a chance. That's a pretty cool-looking card. 1800 and 1800, look at that. He's got that cool-looking flavor text. Next pack of Tachyon Galaxy. Come on, here we go. Fairy Lymphs, Glassjaw, do a bear roll. Spellbook of Miracles, okay. So, we've pulled a secret rare out of Galactic. Was it Galactic Overlord or was it Lord of Tachyon that we pulled that secret rare? Oh, so we already did pull a secret. So, yeah, I mean, it's probably fine. I don't know what to do with that one, Tach, was. Wattail Dragon, Xeze Wrath. Cause we're getting the right stuff. Unless they have like a Ghosturian or something. Galactic Overlord. Wattail Dragon, Lago, Berserk Scales. Overlay Owl, Final Insecton, Bootin. Hierotic Seal. Okay, we're getting down to the very end, guys. Can we get something? We haven't pulled anything crazy since those misprints. That was basically the big stuff. Got the Parsec, that's pretty good. Kaio, we got the Rhino. Gaga Got Wind, okay. So, we're on Cold Street right now. There was the Green Dust, and I'm gonna pretend like I didn't see that. Come on, Ghostur. Come on, baby, Lady of D. Bright Star Dragon, Wattail Dragon. Library Graffer. Bound Wand, we got another Super Rare. Yeah, we started off super hot with those misprints and that Harpy Channeler. And the Secret Rare, even though it wasn't a great one. But we've definitely slowed way down. Can we pull a Ghost and an Ultimate? Can we get an Ultimate? Magnum Shield, whoa, do a Barrel Wall. Oh, I always pull. Oh, well, this is the Second Secret Rare, but I always pull the Brother of the Firefist. Two Secret Rears out of one out of 24 packs. So, I don't think those were resealed. We did get the kind of bad ones, but maybe, I don't know what that pack was. That pack looks so sketchy. Well, we got two secrets. So, even though they aren't the best, that's still pretty good. Blade Bouncer, Flame Tiger, because you usually only get one. Pippin, Xeze Rat, Giga Cricket. Oh, Injector Exa Stag. I've never seen this card, but it looks awesome. You've got to love the Ultimate Rare, Xeze Monsters. They look really good. Plus, this guy looks like a stud. I like how they say they're insects. I mean, look at that guy. He looks like a robot. He's an insect. That's super cool. So, that's a great pull. That is big. That box turned out to be pretty good. I don't know what the value on it is, but it looks really cool. It doesn't necessarily mean anything, but it's still awesome. Maybe eventually it'll mean something. All right, Glass Drop. Wait, it skipped all the way there, but that's a third secret rare. Pinpoint Guard? What in the world? Three secrets. Okay, these packs, I think, are fine. Three, I don't think this one's very good either, but that's three secret rares. That is super cool. Wow, that's awesome. Three secret rares. Misfrant Cards, Ultimate Rare. Guys, this is a good opening. This is a good one. We can win this battle against Yu-Gi-Moh. Yu-Gi-Moh's taking the L now. Eva Price. Oh, a secret rare! Another one, they're all coming at once. Did we go Ultimate Secret Secret? Is that what just happened? No, it was Secret Ultimate Secret Secret. Wow, Photon Strike Bouncer. That is a lot of good pulls in a row. That is crazy. Oh my goodness. Wow, now we just need an Ultimate Rare for Lord of Taki on Galaxy, and we have like dominated right here. Or Ghoster, obviously. Keio. Man, these are like sticky, but then they fly off. It's like the opposite, because one of the boxes is slick, and one is sticky. I think I got behind or something. Or maybe I'm not. Resort Scales. Mini Guts. Return. Ancient Dragon. Booten. Influenced Dragon. And Insector Ladybug. All right, we're getting down to the last like five packs here. So a little bit of a longer video. Hope you guys have enjoyed this battle. Make sure you guys go check out Yu-Gi-Moh's video after this, so you can tell him that we easily killed him. We beat him. Wasn't even close. Fairy Cheer Girl. And Shark Racking. Spellbook of Miracles. Oh my gosh. All right, final four packs. Here we go. The final four. Let's do this Lady of D. Insector Earwig. Nidwit. Overlay Eater. Installer Belt. And Sutterer Moni. Oh yeah, somehow I messed this up, so we have three Lord of Taki on. So let's do these. I think these just rip weird in general. Is that the deal? I don't know. Fire Formation. Oh. Oh, Sombre. Sombre. Cancel Sombre. Dun-Namifun is a part of Sombre. Do you guys get that? If you get it. Let me know in the comments. Here we go. Douten Douten-Goo. Ooh. Ooh, Spellcard. Fire Formation Gyaku. Another card you guys can win. That is another Super Rare. There's a lot of giveaway cards here. Super Rare Fire Formation Gyaku. Remember that being used in Duelings. Okay, here we go. Glad to go over Lord First Edition, the last pack. Pretty much we've gotten everything except the ghost. So maybe if we get a ghost it'd be crazy. Let's go. Lady of D. Bright Star Dragon. Wattail Dragon. Aqua Mirror Cycle. Absorbing Jar. And a Jumbo Drill. Another giveaway card. So many giveaway cards. There you go, Jumbo Drill. And the final Lord of Taki on pack. We had an error opening today. We pulled Ultimate Rare. We pulled four Secret Rears. I mean, this has been a crazy one. This has been awesome. Parsec. Farking. Here we go, final pull. Hit the like button if you like. Spam the Petite Moss or the Picanho Moss and the Medulche Chickalates. In the chat, if you're a member, here we go. Okay, wait in there. But we did really good. Let's go over what we got for Junior and how we beat Yuki-Mil. Okay, first of all for the giveaways. There's two different giveaways. Here's the Glad to Go Over Lord giveaway. You can win all of these cards right here. And all of these cards are for one winner. And then we have the Lord of Taki on. All of these cards are for another winner. So all you gotta do, make sure you guys like the video, be subscribed. Check out Yuki-Mil's video. Let me know who won. It was me, obviously. We killed him. And then finally what we got for Alberto slash Junior. We got Gauntlet Launcher. Harpy Chandler, one of the best cards in the set. That was a great pull. We got four Secrets from basically 48 packs. That is crazy. We got an Ultimate Rare, which is really cool. I think it looks really good. And two Misprint Ultra Rares, which is absolutely insane. So this was an awesome opening. There's almost no way we lose this one unless he pulled Misprints as well. Because that was just amazing. Or he pulled a ghost. And it'll be close. Like Misprint versus Ghost, I don't know. You guys have to let me know. But that's it for this one. If you guys wanna support me, check out my TCG Player EBA affiliate links. Join the YouTube membership, anything like that. Or just watch the videos and like the videos. I appreciate all you guys doing that. And I'll see you guys later. Peace.


The Senate has amended the Electoral Act 2022 to allow statutory delegates to participate and vote in political parties, conventions, Congresses and meetings. This followed the passage of the amended bill on the act at the Committee of the Whole, which was sponsored by Deputy Senate President Ovi Omuagege. Presenting the bill, Omuagege said that it sought to amend the provision of section 84, subsection 8 of the Electoral Act, which, according to him, does not provide for the participation of what is generally known as statutory delegates in the Convention's Congresses or meetings of political parties. This error, which led to us coming back to look at the correction, was something that happened inadvertently. I don't think it was the intendement of this Hello Chamber. Neither was it the intendement of those who perfected the document to send to Mr. President. But I believe in the course of a work like this, things like this are bound to happen. And I think this one is no less one of them. And that is why we are trying to do this amendment to ensure that what the political parties are known to do by allowing statutory delegates, in addition to the delegates that will be elected by the various political parties, constitute the Electoral College for all the elections that we talk about. To have the privilege of leading the debate on this very important bill, we seek to amend the Electoral Act, point 22, to make provision for delegates who have not been elected ad hoc delegates, as prescribed in the Constitution of a political party and the Electoral Act to participate in the Convention's Congress or meeting of the party. Mr. President, this bill was read for the first time on the floor of the Senate today, Tuesday, the 10th day of May, 2022. Mr. President, my colleagues, the issue here is narrow and very straightforward. Mr. President, as couched, Section 84, Substitution 8 of the Electoral Act 2022, does not provide for the participation of what is generally known as statutory delegates in the Convention's Congresses or meetings of political parties. A deal for an act to amend the Electoral Act 2022, and for other matters connected there to 2022 and 23rd reading taken, and the bill is passed. Thank you very much, the Zungish colleagues. Let me explain a little bit what we have done. Electoral Act of 2022, or amended Electoral Act of 2022 that we passed this year, has a deficiency that was never intended, and that deficiency would deny all statutory delegates in all political parties from participation in Congresses and Conventions, and therefore such a major, such an unintended clause has to be amended before the party primary starts in the next eight days. So this is an emergency effort to ensure that nobody is denied his or rightful opportunity as a delegate.


A Wise County Virginia man was convicted this week in a 2018 crash in Letcher County that killed two Pike County women. 39-year-old Travis Hilbert had faced two charges of second degree manslaughter in the deaths of 61-year-old Barbara Newsom of Pikeville and 90-year-old Kathleen Tackett of Belcher. I was in the courtroom in Letcher Circuit Court for a hearing on Wednesday when Hilbert entered his plea. And do you further understand, sir, there would not be an appeal to a higher court from the judgment of this court if you plead guilty or so? All right. Now all you know is- Travis Hilbert has been lodged in Letcher County jail since May of 2018 when the wreck that killed Newsom and Tackett occurred. He was on his way back to Virginia when he lost control of his truck towing a horse trailer on US-119 at Payne Gap near Jenkins and crossed into the path of the women's vehicle. Newsom died while en route to the hospital. Tackett died several days later. In this video I shot at the scene, Hilbert struggles through his field sobriety test and is arrested by Kentucky State Police. Twenty months later in Wednesday's court hearing, Hilbert entered an Alfred plea to two amended charges of reckless homicide in Newsom's and Tackett's death and second degree assault in the injuries suffered by another passenger in the vehicle. An Alfred plea is entered when a defendant maintains they are not guilty but admits there is enough evidence to convict them. An Alfred plea is treated in the court system in the same manner as a guilty plea. As part of the plea agreement, Hilbert could face up to 16 years in prison. Now with that 16 year recommended sentence, Hilbert will be eligible for parole after serving 20% of his eventual sentence. If he sentenced to the recommended 16 years, he'll be eligible for parole after serving a little over three years in jail. He'll be sentenced in March. Reporting for Mountain Top News, I'm Chris Anderson.


Hey friends today is the opening day of Disney Springs. I am super excited to be here I want to check out everything right now. It is 10 a.m. And it's not too busy at all here temperature checks are right behind me So we're gonna go through there get our temperature checked and then get down into the Springs. So Let's go do this And it looks like we're going back into the garage Thanks On a nice little loop around Welcome back to the water out here Thank you We need to be wearing our face mask get our temperatures checked and also practice the physical distancing It's really cool that Advent health is actually performing all the temperature screenings. I think that's awesome Good morning I'm gonna pull your hat out too I'm gonna get close but I will not touch you Have a great day That was pretty simple and very easy no lines nothing like that Everybody seems to be already complying with the social distancing.  I Think that is super cool. And plus he's wiping the banister with sanitizer as it's going like round and round That is what we have been missing. Oh, look at that beautiful It feels so great to be back in Disney Springs or just out doing something and I don't mind the math so far It's only been 10 minutes and I really can't judge that but I got my sanitizer with me Much better sanitizer. This is from the Bearden company advanced tan sanitizer. I like it And just take a look at those crystal clear Springs Beautiful Seriously, though, I thought there would be a lot more people here. It's been open since 8 a.m They've been letting people in and it is now 1006 Not too many people at all a lot of helicopters trying to get some aerial shots going on though. Oh Look, there's blaze pizza huh Wow, seriously, I don't see anybody here. It's a little shocking, but it's good We ran into a group of people here. Look at this world of Micah Let's huh paging this tomorrow Then we got Danny 702 Tampa J Jackie Super Enthus Vincent vision and the cool kids They have little arrows that's pointing the direction you should walk So keep to the right if you're heading this way and then go to the left if you're going this way And look people are actually abating by them And once again the Springs are beautiful One thing I think I really want to check out is actually heading to Joffreys to get some Joffreys coffee because Technically today's like the first day that we can get it. So that gets me a little bit excited As we make our journey over to Joffreys You notice it's starting to pick up a little bit more over here a lot more people heading to the other side of actual Disney Springs The line to get into Joffreys isn't too bad It just looks bad because of everyone that's practicing the social distancing and actually staying exactly on their markers But it looks like we're about four four Separators or four markers away. Oh Here we are. Are they little coffee beans? Oh The markings for social distancing is coffee beans I think yeah, she said come on in and stand on the next coffee I like that Normally I would definitely go with my normal Starbucks nitro cold brew But like I said, you're at Disney Springs for the first time in a while My's well come to Joffreys and I'm gonna try their nitro. I Have my nitro. I'm excited and now I'm gonna either go down by the water or just kind of tuck away to the side there So I can just take my mask off and drink it and not be in any social gathering areas And we found a nice little place to come sit over here where there's nobody around and we can enjoy our coffees now That's what they recommend to do if you are drinking or anything like that Just don't be in the common areas like over there There's a gigantic line of people waiting to get into Boat House and we don't want to be sitting over there drinking our coffees Look at how we are all hanging out socially distancing This wasn't planned either this literally just fell this way everyone just like sat but within the distance amount perfectly Crazy in fact as I take a little bit more of a look This is the first line I've actually seen all day at Disney Springs and it's a line to get into Boat House Look at that crazy Goes all the way back I think we're gonna move along a little bit We do have a lunch reservation and STK, but before we head over there I wanted to come over here and take a look at characters in flight or Aerofile and then just look at the water itself. It is such a beautiful day out Wonderful day for Disney Springs to reopen. Look at this. I love it And now we are in line for STK and definitely not as long as line as the Boat House Wow, this is it Much more better. Everybody is doing their social distancing. Looks very good Here is a look at the menu. It's the all-day menu and I don't know if this is different But this is exactly what they're serving Oh, you're getting the tuna tata, huh? You're going with the wagyu burger? Oh, very interesting. Yeah, not too bad. 10 bucks. Wow, you can't beat that at all They have a wagyu hot dog for 10 bucks too. Oh So excited. Which way do we go? Wow, it's so pretty in here Thank you, and we do have a health and safety advisory right there Look at how beautiful it is in here and they're doing a really good job with the social distancing They have every other table marked off that you can't sit here you can sit there and you see they have the arrows and Actually the X's mean from one X to another is six feet. So If a table sitting here They can't sit there even though they're both open and a part of every other table But because they're within six feet you can't sit there And now that we are officially seated at our table it's time for the unmasking and My glasses my glasses got stuck And a part of the grand reopening here they gave out these little cards For one complimentary standard drink at the bar. That is pretty awesome So I think what I'm gonna go with is the steak sandwich and they have this nifty little lunch special menu And look at that like before we said the burger was only 10 bucks and the steak sandwich is only $19 a shaved coffee rubbed ribeye With caramelized onions. I'm not getting the horseradish cream. No, probably Along with my steak sandwich, I wanted to get a bud light but they're not serving any bud light at this time So I'm gonna get a corona light. I don't think I've ever had a corona light before Hope it's good Jackie went all in and she got a bloody Mary and Vincent's got the water The delicious water is hot outside. Yes, it's very hot Stay hydrated h2o They had no corona light So no bud light no corona light instead. I went with the medello, which I've had this before I do really like it and I got a nifty little glass. I got my sanitizer already spritzed up Let's do this And the food is here. We're gonna slide this out of the way Right there gentle.  Oh, yeah, that looks great. I am gonna love this The bread is so soft. Oh boy. You're gonna dip it in there. Oh, yeah And I'm going in That is the best steak sandwich I actually ever had I'm like really impressed with it. Wow Unbelievable I legit don't want this sandwich to end I really I'm even considering ordering another one, but I think that's a little that's a little much If it wasn't if it wasn't lunch and it was dinner, I think I'd be like can I have two steak sandwiches, please another for dessert Yes, I'll have another I'll have another And now it's time to cash out. Look how fancy this is Table safe and they have a little plastic wrap on it. You can just insert your card and my bill came to 33 55 That's not too bad. Two beers and a steak sandwich with a discount. Thank you All finished up at stk phenomenal. I absolutely loved it. The mask is back on and I'm ready to Head out or make my way out of here And take a look on the way out almost hardly nobody here and it's 12 30 Before we actually leave I want to show you down here near splitsville and amc There's nothing open down here yet, but they do have the signage up Hopefully the movie theater is going to open up soon. At least they're preparing for it And almost all of the shops They're not open yet It just seems like very quiet over on this side of the park or disney springs And I think that's gonna do it for me. Like I said, it was just a little fun day out today We got to check out stk go to joffreys and just enjoy disney springs I'm just happy that something's open and that we can get some kind of normalcy back Anyhoo, I hope you enjoyed the vlog. I enjoyed making it. So we'll see you next time. Bye You


Let's go ahead and get started. We've got a slide up here just to showcase some of the other things that we've got going on here. And as IBM, we've highlighted one of the sessions that we've got going on tomorrow. We have the 240 right here in this room. We've also got a booth where you can get more information about our products or offerings. You can get some golf balls and hats as well. There's a lot of different things there. I'd like to thank everybody for being here this late in the afternoon. We'll just call this the pre-party. So break it out if you got them. But no, we're really excited to have you here and we appreciate you spending the extra time. You know, it's been a long day, but there's been a lot of good information that's put out throughout the day. Today we're going to get about 40 minutes of a little bit of a shortened session. We're going to cycle through three speakers. Myself, Alex, I'm a product manager for the Smart Cloud Foundation products. We've also got Andrew Trossman, a distinguished engineer who's going to talk to you about OpenStack. And then James Peng, who's here to talk about the products that are available as well. So we're required to put this up. We're going to talk a little bit about a product called Smart Cloud Orchestrator that we're very excited to announce later this month. So our lawyers make us put this out because it's got that coming soon label to it. So my parts can be really short so we can give you the technical details which I know everybody here loves. But I just want to give a quick overview of what we're doing at IBM and how our cloud strategy is coming together. Now, I'm sure you've heard a lot today and we've got a similar view of the world as been put out by all the various analysts and in this structure. But the way we do it is we come about with three different kind of views or dimensions into this space. Starting with Smart Cloud Foundation, which is a set of enabling technologies to allow you to build on-premise solutions for infrastructure as a service and platform as a service that's highly scalable, workload aware and secure. Our next dimension is with the Smart Cloud services. So again, we want to provide infrastructure as a service and platforms as a service for you, but in this case, we want to allow you to not have to worry about the overhead of managing that. We don't want to make you have to worry about security or any of those issues there. So this is an opportunity for you to have those same benefits, but then IBM takes care of the back end of this. So it's a private cloud, public cloud, hybrid cloud, whatever you want it to be, but IBM is managing the back end of this. And last is this notion of Smart Cloud services. So one thing I don't think a lot of people realize is that IBM is actually one of the top ten software as a service companies out there. Through a series of organic growth, also through acquisition, IBM's got over 60 different software as a service solutions, some of which are around business process as a service, or business analytics as a service, collaboration as a service, variety of different entry points or solutions to help you be able to do your business better and engage your customers in a more efficient way. The other thing that's unique about our services or our solution business is that it's everywhere in the world, whether you're doing business in China, India, Brazil, South Africa or the United States, we do business there. Our solutions are there and available. This is one of those competitive advantages that IBM has just because of the size of who we are and what we do. But one of the key things that underlies this is the need to be on an open infrastructure, have an open reference model, so that we can communicate back and forth across these dimensions, and more importantly, so we can communicate with any of the other investments made yesterday or make in the future. We're trying to get away from that world where we have siloed vendor locking situations, make sure that your cloud is interoperable and communicate with the rest of the environment. As I said, I'm with Smart Cloud Foundation, so there's a couple of things that I want to highlight of what we're doing. One of our goals is to create a comprehensive set of capabilities to allow you to build your private cloud. And one of the key pieces of this is it needs to be a progressive situation. You're not going to come in the first day and say, we want to buy the Cadillac every time you come in and say, I want to buy the Cadillac. That would be a great world if that's all we built. So we want to make sure that there's a progression here for you to come in, get the capabilities you need, and then be able to add on those as you go forward. The other key to this is it has to be a situation that's heterogeneous, not just different hardware and different servers, but you're going to make different network choices. You're going to make different database choices. And those things all need to be able to work together not just today but also in the future. And ultimately have that designed in an interoperable and open model. So the overview is going to be over in just a second. Just give me a few minutes here to give you a history lesson of what the IBM products. So I said something about a progressive platform or portfolio. And this started a few years back with a product called Smart Cloud Entry that's in the market and has been in the market for a number of years. And this is a basic cloud offering. It gives you basic management capabilities. It gives you basic usage and metering capabilities. And it also gives you very powerful hardware management capabilities. The next product once you've got kind of that infrastructure and service layer done is to move to Smart Cloud Provisioning. Kind of starts to step you into this platform as a service opportunity. This product brings in the ability to do multi-tiered applications to develop in what we call patterns.  It's really about automating your business and automating your services to make it more efficient and faster. Now these products both have been in the market for a while and they're very powerful. They've got a lot of benefits. Of course I'm drinking the water from IBM but at the same time we realize there are some issues here. Well we have some great differentiators here. They weren't necessarily as interoperable as we wanted. So people like Andrew here and other distinguished engineers with an IBM and other great developers that we had said hey there's this great opportunity of starting an open stack. So we started to search that and we started to build along those lines to make those investments. Like I said we've got a coming soon label coming up with this last product which is Smart Cloud Orchestrator which takes us not only the next step in the capabilities that differentiate IBM around things like complete data center orchestration and automation and incredibly easy interfaces around your processes. Probably more importantly it allows us to take that step into complete interoperability on open stack. This is a leader within IBM not just because it's a great product and then it's a step forward in our cloud foundation portfolio but also because it's our first open stack product. Not just the first for the Smart Cloud Foundation meaning that provisioning will soon be on open stack and entry will soon be on open stack but also our services will be on open stack and our solution will be on open stack. So this is just the first of many investments that IBM has made that's coming into reality today around this investment that we have with open stack. So with that I want to turn over to Andrew who's going to go into deeper details and deeper dive into those investments how they're panning out for IBM and why they're important also to open stack as well. Great, thank you. So we have right now they're that's fine just they're over 250 people in IBM that are focused on open stack now. A year ago this same time I could count that many the number of people on maybe two hands that were involved in open stack. So a lot of this has been very, very, very recent. A lot of the products that Alex just showed you originally were before we embraced open stack and actually myself and a few others here in the crowd today were the early guys getting involved in open stack and we recognized certain things certain technologies that we had that we wanted to donate to the community and of course that donation is done by porting and building patches that we then contribute into the product. So I just want to step back a little bit and look at that this is an orchestrated product why are we doing an orchestrator what is that? And this chart here is a workflow that actually came from a real customer of ours when this is a workflow that they use when they deploy their systems into their data center and the point of this chart is not to show you all the little details but to show that there's a whole lot of crap that has to be done just provisioning of a VM to get it into a data center there's lots and lots of other processes and systems that you need to integrate with particularly for enterprise data centers next please So in our smart cloud orchestrator tool actually one of my buddies one of the open stack founders he used the phrase smart cloud orchestrator is like visual basic for the cloud and that's what we're trying to do is to really simplify the way that you can exploit the cloud for all the wonderful things that many of you folks have done with the cloud to make it easier and so one of the things that we do here is when you want to create an application invariably an application is going to be a collection of a bunch of virtual machines with a bunch of software on them that all need to work together so here's a simple drag and drop tool that you can just drag onto your canvas and you can drag VMs onto the canvas you can connect those VMs together and you can put software into each of those VMs next please as we move up so that's kind of we refer to three different levels of orchestration at the base level we call resource orchestration that's really about orchestrating server storage compute and network and really that's what the core of OpenStack is all about and that's why we're standardizing it there as we move up we get into what I just showed you which we refer to as patterns or workload orchestration but as you go further up we refer to it as service orchestration and this is where we can start integrating other systems like CMDBs and service desks and backup systems and monitoring systems and invariably even infrastructure like firewalls and load balancers etc and we have best in class workflow tool we acquired a company called Lombardi award winning software and internally we call it our business process manager it is a fantastic tool from the point of view of the designer so this is a nice GUI tool for creating workflows and in the workflow it can be completely unattended automation but you can also have human human steps integrated into those workflows and it's just as easy it's all drag and drop you can create little user interfaces all using this tool then on the runtime side it's a highly scalable robust platform for doing these kinds of automations next please so this is something we call our common cloud stack internally this is a collection of technologies that we've integrated together from which we provide a bunch of different offerings and Alex mentioned some of the product offerings that we deliver and the point here is that because everything's built off of this same set of technologies wherever possible we use open source and open standards to make all of our pieces interoperable not just interoperable with our own technologies but with third parties and customer products as well so at the bottom you see the typical infrastructure as a service coming from open stack we have something we call our IaaS gateway and this is something you know if there's interest to bring it into the community it's certainly something we'd be happy to do and essentially what it does is it helps us federate multiple clouds because most of our customers have lots of clouds deployed across the globe sometimes it's for geographic reasons sometimes it's for different purposes like dev test versus production usually you have to have many of these and you want to simplify the management of them and the consistency of your images across them without having to do silly things like you know sending terabytes over wan links as you move up you'll see the background in that bright colored green we have this online marketplace that we're developing and what the idea is that throughout our stack there's content automation it can be as simple as I have images and open stack compatible images that we want ourselves to deliver to our customers partners, vendors as well as open source be able to make these images available so somebody can download them and say here's an open stack compatible image that I can go and use to you know run a patchy or something as you go up there things like you might want to be able to download chef recipes, chef cookbooks another you know software stacks the next layer are these patterns and we're embracing some of the standards like TOSTA you might want to be able to download or if you're a vendor you might put a make your stacks available so people can then download them and then deploy them in our environments and lastly is the workflow at the top and that's that business process tool that I mentioned before next please I'm not going to get into too much detail here but in each of the Cinder, Quantum and Nova there's some technologies where we're we've made contributions and we're going to continue to make contributions but we also have some IBM technologies that we maintain of our own one example is over here in the storage space we have a technology called GPFS it's a cluster file system that's been around for many years and we've built the Cinder drivers but it's a technology that's been scalable robust and battle tested for many years next please another key thing that many folks have found in trying to use OpenStack is that the support for VMware is not quite on par for what people have typically deployed most people when they deploy VMware they're going to have vCenter and you're going to set up your data sources, your clusters and all those kinds of things and the current OpenStack drivers really just can't work with that as you saw we already had a number of cloud related assets so what we've done is we've taken those cloud those existing assets for talking to VMware and using the same OpenStack driver plug-in model we've plugged those in into OpenStack so that we can manage existing vCenters as in in place without making any changes there's a lot that needs to happen in this and this is something where we've been working with VMware and a collection of other partners to improve what's in the open source over time but right now this is something that we had to put out for our customers to actually that works now next please and here's one other key component actually there are a number of components that we have that I think add additional value to an OpenStack environment and we've got James here from our platform computing acquisition and these guys were for 20 some odd years doing high performance computing and I'm going to let James tell you a little bit about how we leverage that technology for OpenStack okay thanks Andrew so as Andrew said a year ago you can count the number of people that work on OpenStack in two hands so a year ago my team I'm from the platform computing team in IBM and we joined IBM as part of our acquisition a year and three months ago and a year ago our team also didn't do anything with OpenStack but now we're we're knee deep in OpenStack as part of the overall IBM effort to first contribute to OpenStack and second to also drive adoption of OpenStack and also to leverage the OpenStack so that we are also creating interoperable clouds and sharing all the good stuff around an open community so a little bit of background about this thing called EGO so this EGO technology is a resource manager and what it is is a matchmaker between supply resources and demand your applications your workload demand as I mentioned to a lot of this IBM partnerships and acquisition EGO is not a new technology it's battle proven it is in the high performance and grid computing in which platform computing have been involved with for almost 20 years and there are literally thousands, 2,000 plus customers using the grid and the high performance computing products that have been using EGO structure so it has been doing that resource management in a different market in a different context but if you look at this spirit of OpenStack it has a lot of semblance to grid computing, scale computing and even high performance computing and this EGO technology is one of the things where after we joined IBM it looks like hey this could be interesting this could be interesting in creating enterprise resource management capability for OpenStack based clouds so there are two areas of EGO that it does as it adds value to the OpenStack context one is placement VM placement, policy placement of VMs based on resources, based on load based on where it is in the rack for example and the other associated would be migration where should I migrate VMs based on SLA and based on policy so that's the runtime mobility aspects that EGO brings to an OpenStack environment which is the VM placement and replacement now the other aspect of EGO as a resource manager is being able to arbitrate the use of the resources among different tenants because at the end of the day a cloud as much as we think there's infinite resources well it's actually not infinite especially if it's inside your own data center there is a box around it so what's the best way I can prioritize the use of these resources among different departments among different projects among different groups and these map to the concept of OpenStack called tenants how can you define shares among different consumers and that's an EGO concept so that's the other aspect of EGO in terms of what it does so in terms of some of the policies that EGO already has and again a lot of it we're trying to as part of our effort to port it over to the OpenStack context includes things like packing putting as many VMs on as few hosts as possible, striping which is the office, striping that VMs as many hosts as possible both in order to meet certain SLA's for example minimizing memory fragmentation etc and then other things that we talk about being aware of low, being aware of things in the racks, all of these things are intrinsic in the EGO technology but at the same time one of the things we learn and I think in the OpenStack community for folks who are building clouds also I've learned is you can't be restricted by whatever is out of the box the customer whether it is a service provider whether it's your admin, whether it's your infrastructure team needs to be able to write your own policies because your policies map your own organization's SLA to your own organization's business needs so one of the capability of EGO is extensibility being able to expand it so that you can create your own site specific policies so how do we integrate this EGO component into OpenStack so this gives you a picture of how that's done and what a great thing about OpenStack is it's open, right you find interface around the schedule around the NOVA scheduler and so we leverage that component of NOVA to work with EGO and one of the things we did have to do was to create a Python layer and that Python layer was new but that enabled us to then talk with the NOVA scheduler so that's what you see on the left-hand side on that side so that takes care of the initial kind of the initial placement and intercepting every call that's coming in so then we can then apply our policies against whatever are the new VMs so we know what's going on so then the other aspect of it is the runtime, when do you do migration when should you grow and shrink your resources so that's where we introduce a second component called the runtime policy engine and that runtime policy is new code, it basically monitors the environment and based on some of the pre-configured policies it would then trigger migrations based on those policies so those are the two areas that we bring into this architecture in order again to add to bring enterprise level resource management to an open stack based environment and the final thing I just want to highlight is the hardware management module we follow the open stack parameters on how to gather metrics and so on but in case the customer wants additional metrics that are not being provided by open stack the ego itself also have agents and these agents you can also deploy in a complimentary way so they can collect your own site specific metrics such as application licenses as a metric to do placement so that again shows the example of embracing working with the community at the same time providing additional extensions and value add to enterprise customers so I'll just wrap up a couple of illustrations in addition to the runtime so because I have a lot of time when we first did this initial development focus was on runtime where should I do the placement and when should I do the migration a lot of focus was around there but as we getting more and more engagement with enterprise customers and enterprise service providers it becomes clear that you have to deal with the resource arbitration the priority of the different tennis in which you are serving so one of the things that comes with ego is it has a concept of reservation and this is actually based on capacity so it's not kind of like this runtime VMware type reservation where you give a time and then you run something it's not about that it's actually guaranteeing that the resources is available at that time in the future so it comes with a whole reservation based system what we call advanced reservation which is very typical that you see in the HPC and grid computing environment so we bring that reservation concept into this into the open stack world so that you can have very well defined predictable SLAs and then the other aspect just to wrap this up is the idea of again going back to the consumer aspect the multi tenancy ego itself has this concept of multiple consumers and these map to the tennis and these can represent different departments, different projects and you can then define shares among them and you can define things like minimum and maximum and what maximum means these are the amount of resources that you want to borrow from somebody else from another tenant if that tenant is not using those resources so ego comes with these concept of borrow understanding and sharing policies and so with these kinds of attributes we think that this will help enterprises take open stack to the next level which is providing enterprise level resource management so I think just before we take some questions I think one of the key things to what James was showing you is it's open right open stack provides open interfaces that allow us to plug these kinds of capabilities in this capability is open in terms of it can work across different hypervisors and it's also open in terms of there's control given to the end user so that you can define the policies that meet your needs so I think that's going to really be something we've seen a lot of our customers see is really valuable and we hope you'll find that too so we have some questions I see a question over here the open source so for specifically for the ego stuff or the whole okay so the open source components if you look in our the smart cloud orchestrator so the whole stack it's basically open stack we also enable chef and hopefully puppet in the very near future ego is proprietary code yeah the ego itself is proprietary some of the metric collections that we're working on those things open source in our deployment so our deployments in smart cloud orchestrator today is with cupid I don't have that information but we do have one of our guys from our performance team is is at the summit this week and so I can certainly hook you up with him if you want to connect with me after I'll connect you with that guy so can you be a little bit more specific in which product which one smart cloud provisioning smart cloud entry or the public cloud okay so the public cloud is alright so public cloud is a little different today the public cloud is not using open stack yet that's something that we are in the process of doing and IBM I mean IBM has a historical value which is maintain backwards compatibility so those APIs are going to continue and they're going to be maintained for a fairly long period of time I don't know precisely how long but so as the public cloud does adopt open stack those will become new APIs but the legacy ones will continue to be maintained any other questions can you speak up louder please the baseline do you want to just repeat the question the question about the reservation is it this advanced static or is it also based on predictive data that you can change over time in other words the reservation itself can change over time so out of the box the idea here is that exactly the name is actually called advanced reservation which is to guarantee a certain capacity a certain time a certain point in time just like a hotel reservation system so having said that if based on runtime information and based on different policy changes those reservations can be changed we've had these in the grid world where customers have taken some data some workload data and using that to feed and then they adjust the reservations accordingly in the future it can support both models but I think the second model is more it's more customized than the first one which is really out of the box other questions for both the schedules and the policies is there some sort of format that's explorable that would be used in other other implementations like an XML format or something that would define the policy and the scope actually right now the ego component is actually technology preview the way you configure the way you define the policy is through XML format right exactly so as a tenant I also have to give a parameter called minimum my guarantee and then because I'm playing in a cloud world at this point if you also tell me how much I could lend out to others if I'm not using it so all of that is in control of the tenant but typically in an enterprise environment it is some kind of central IT person or group being an arbitrator talking to different business units and then working out the priorities and working out the borrow and lending policies so in smart cloud orchestrator that's currently in beta to be announced whenever that's based on Folsom and it is Nova networking our plan is to start aligning our release cycle as close as possible to the open stack releases so sometime this summer we're going to have an update with Grizzly then Havana in the fall and along the way we're going to start making use of Quantum other questions how do we monitor the infrastructure so one of the things with IBM is we have no shortage of products we like to buy companies we take those companies we create new products we also like to market a lot of crap out of everything and so we've got a brand called smart cloud and so we actually have a product called smart cloud monitoring and jokes aside that's exactly what we try to make it as simple as possible so you can buy our smart cloud foundations core cloud products based on open stack you want to do monitoring great add smart cloud monitoring oh you want to do usage and accounting great add smart cloud cost management and there are a number of these half a dozen or more that kind of help round out the overall offering other questions anybody anybody ever use an orchestrator tool yeah anybody use runbook automation tools yes a few anybody got a question who's thirsty open stack is that going to be I sort of don't want to have yeah Alex let me make sure I understand the question are we going to have our own distribution of open stack yeah it would be and it would be in the context of those products that we talked about earlier so we've got smart like I said smart cloud entry provisioning an orchestrator which by the end of the year we intend to have them all on open stack and those would be on a common base open stack that's within IBM the key is that it's not going to be anything different necessarily than what open stack is we're not going in there we're not changing any of the bits of open stack but we're adding to that and extending above it capabilities that are differentiating so like I mentioned the smart cloud entry has got very detailed and powerful management hardware management capabilities provisioning ads some pattern capabilities orchestrating ads BPM but it's all on top of it a common open stack component there so if I step back for a moment so there are three products that are in the field today smart cloud entry smart cloud provisioning and smart cloud orchestrator and they kind of build on each other today smart cloud orchestrator is the first one to pick up open stack in the summer we're going to start adding for each of the other two the idea is to get them all lined up on the same technology base in terms of the open stack we are not having we have no plans right now to do an IBM distribution of open stack but we do ship it as part of any of those three products that answer your question of those three products yes but it's embedded but it's also exposed yeah I mean we're not hiding right and we're not doing anything unnatural to it we do have some plugins to it maybe maybe a little bit a little bit unnatural but that's for later any other questions before we all run out and get dry how does he well so I think he fits very nicely into what we referred to as workload orchestration so it's more about I mean the term we've been using internally are patterns and so we think that's fantastic because the most important thing is to start standardizing so that people can create those templates make them available in a marketplace or somewhere online so we can distribute them and get that kind of consistency and I think one thing to add in here is along that notion one question is how is the best way to interact with business user on how to create those templates Andrew showed a couple of screenshots of Smart Cloud Orchestrator mentioned the best of breed BPM capabilities and the pattern creation capabilities you know that's one aspect that I think is very crucial to understand here is how can we create a user interface that makes it so that this crowd doesn't always have to be right in new templates but that we can start to pass that off and use the development resources in better ways in ways that are more entertaining and exciting for the developers and I think that's one thing that is a very big differentiator for us we talk about how can we make it easier to build and consume so that people can code things that are the next gen instead of the next template Other questions? Everybody having fun?