Welcome to the 2016 Lucasoil and CHA Superstakes we just had the non-pro for your old final there were two winners tonight that claimed the championship one of which was Armando Costanietto who rode Watch Me Whip and scored a 222 congratulations to you Armando. Thank you. So tell us you've already got a major title on this horse what was your plan coming into this event today? I just tried to have a clean run and get as big a check as as we could but ended up getting a little bit of luck and getting the big check. Now do you closely watch the cattle do you get much help or is that something that you find that you really are instinctive about or you know how do you work that out? Now me and I use the Don Benuelos and John Micho we all watched chaos together and just kind of tried to get the best you know pick the best cows for the for the draw yeah. Describe your run to us today. We cut a yellow cow first and she was a good cow we knew her she worked good the mare was good went in cut a grey cow second there was a grey cow she was a little fast and but the mare was spot on and ended up working out. The third cow I just saw a little black cow on top and she looked good I thought it would be worth the risk and we ended up cutting her and she she was good. Now you won the faturity the non-pro faturity on this horse you've obviously got a great rapport you trained it tell us about watch me whip. She's good mare tries hard every time a show she's been great at this show we made the open semifinals and we've been doing good every every where we go and she she's just special mare for me. What are her strong points? Just smart, cowy, can stop and just greedy and wants to keep that cow away from the herd and just tries real hard. Now you equaled the title with Nadine Payne what were you thinking when you saw her show? Now I knew she had a good horse and she did her job cut her cows are good and ended up tying just good for her. Okay so your plan now with this horse is to try and go for the Triple Crown and the Summer Spectacular tell us about that. Yeah probably just see how we go I think we just got fortunate enough to win this too and see how we go to Derby and if we win it'll be good. And you had your whole family over here from Brazil to watch you today how did that feel? Yeah it was good I had my mom and dad and grandma cousin or uncles and they everybody's happy. Well congratulations and great effort. Alright thank you.


You're welcome back to the breakfast on Plus TV Africa. On this day in history, in the year 1975, May 28th, the economy community of West African states was formed via the Treaty of Lagos. So 15 members of West African states came together to form this community to say, we want to create self-sufficiency for our states. They want to create sort of like a borderless West Africa where all the states can come together and advance their economy goals and aims. And it was in this day in history that the economy community of West African states was formed. So they say they're going to ensure integration for economy, industry, transport, telecoms, energy, agriculture, natural resources, and all of this. So there were very high expectations of economic integration as well, saying that this regional group, they had a focus to basically make sure that they're having a borderless region exploiting their abundant resources amongst each other. So we know that in January 2007, it transformed their ECOA secretariat to a commission. And they formed a single trade bloc and we know that the economy community of West African states have been clamoring for a single currency that was going to be called ECOA. That really hasn't really kicked off yet, but it's in the works and basically on this day in history, 15 states of West Africa came together to say, let's form ECOA for all the reasons to integrate economically and otherwise. Yes, 1975, long, long, long ago. And every now and then, people would always ask what has been the relevance of ECOA since then. Every now and then, of course, they sent in troops peacekeeping troops mostly to certain countries that are at war to save lives and all of that. The economic value of ECOA has also been questioned every now and then. How much business and how much partnership, how much has the ECOA's bloc itself been able to benefit each member state and all of that, which of course, are genuine concerns. But it's still a good thing that it does exist. Still a good thing that there is that body that unites all the West African states, 15 states. There is that figurehead basically that has also played its role one way or the other. Could do better. Same way, they also questioned the United Nations and all of that, how relevant have you been? How loud is your voice? How powerful is your voice? So how powerful is the voice of ECOA's also with these things? Mali currently is in some sort of crisis. And we hope that there is some peace and we hope that there is some in the next couple of days, some of all of that is settled. We can be having coups every two weeks in Mali. And regarding ECOA's and the intention to have a borderless region, I personally feel that we could do a lot regarding tourism, for instance. So what we're talking about, Nigerians going on vacation, going to Dubai. How many Nigerians have been to Ghana? How many Nigerians have been to neighboring republics, neighboring countries, Togo, Bene. How many Nigerians have really explored these areas? So how many citizens of those countries have come, visited other countries in the West African region? So I feel it to be a great idea if in addition to all the many things that the ECOA should be clamoring for, should be the creation of all, advancement of tourism and integration, travel, schooling, exchange programs. I have lots of these abroad. Like, a Nigerian could spend two semesters here, one semester taking your same course in the University of Ghana, taking your same course in another university. At a reduced price. I think this thing should. It shouldn't be as expensive as it is sometimes. Yes, yes. You need to go to that. It's more expensive than going to the UK or going to Dubai. True. My friends who schooled in Togo told me how we expect. In fact, they charge Nigerian students way, way higher. So these are the things that we should even consider, you know. But I feel that there's a lot of potential for the ECOAs. Just like the NYC, I don't think it should be scrapped. I feel their reviews should be made. But there's a lot of potential for ECOAs and I feel it's still relevant today. Yeah. All right. On this day in history in the year 2020, a couple of days ago, well, on this day in 2020, the George Floyd incident happened. And we had spoken about that. I think sometime earlier this week. The protests across the United States were becoming wider and more violent. And in Minnesota on this day, there was a state of emergency declared following the protest about George Floyd's death. Minnesota Governor Tim Walz declared a state of emergency and activated Minnesota's National Guard to restore order after the protests over the death of George Floyd turned violent night before. Everyone, I believe, knows the story of George Floyd, who died after police officers arrested him before allegedly giving out a fake $20 bill. And one of the officers put his knee on his neck for almost nine minutes, which eventually led to his death. It started another protest in the United States to protect black lives and to express the fact that black lives do matter. It also started another conversation in the United States on racial segregation and racial injustice that has been going on for many, many, many years. Yesterday, I think Nancy Pelosi, I saw her in the video with George Floyd's daughters and all of that. But for me, the question really would be how much has changed? What new laws have come into play since his death? What has changed about policing, about racism in the United States? What has changed about the criminal justice system and racial injustice in the United States since his death? It cannot just be photo ops here and there. There has to be a difference. There has to be new laws and acceptance of all races and equality, basically. A couple of weeks ago, we heard about new laws by Joe Biden to protect Asian Americans from being assaulted after the COVID-19 issue. After Trump said it was a Chinese flu. Yeah, but what has been done to protect blacks also in the United States? So sadly, George Floyd had to die for these conversations to spring up, but I feel like there's a lot more that needs to be done to completely raise a level of racism or at least minimize the level of racism that still does exist in the United States and across the world. But on this day, basically, Tim Walz declared a state of emergency and called in the National Guard to help reduce and protect property in Minnesota after the riots were going totally wild. And that's it on Today in History. We'll take a break here to return to discuss what the agenda ahead is for the new chief of Amnesty staff who have been appointed by President Mohamed Buhari to stay with us.


Today, we are going to go through some more examples of pedigrees, and how we can use them to work out the pattern of inheritance of a particular allele. Now we have talked about how alleles can be dominant or recessive, but we have not discussed how these alleles can be found on autosomal chromosomes, or on X and Y chromosomes. In all of the cases where an allele is dominant, only one needs to be present to be expressed. Contrastingly, both alleles need to be their recessive allele in order to show a recessive trait, except for in biological males for X-linked traits, because they only have one X chromosome and thus only one X-linked allele. Let's now remind ourselves of how genotypes are represented, with lower case letters indicating a recessive allele and upper case letters representing a dominant allele. Remember that biological males only have one X chromosome and therefore cannot be heterozygous for X-linked traits. In this first worked example, we are also determined how we know that this trait displayed in this pedigree is recessive. Now we can work this out in many ways. For example, we could have a look at this individual here in the second generation, who was affected. If the trait in this pedigree was dominant, it would mean that this child has a dominant allele, meaning that at least one of his parents has passed this dominant allele onto him. But both of the parents do not display the trait and therefore do not carry this dominant allele. Consequently, we can say that this trait is not dominant and thus it is recessive. This is a nice summary of how to tell the difference between dominant and recessive traits when using pedigrees. If there is an unaffected child with two affected parents, then the trait is dominant. If there is an affected child with two unaffected parents, then the trait is recessive. In both cases, this is only possible when the parents are heterozygous. Another difference is that dominant traits cannot skip a generation, whereas recessive traits can. We can see generational skipping in the example of a recessive trait presented on this slide, where neither of the parents have the trait, but the child does. Thus the trait has skipped the parent's generation. For the next example, we are asked to prove that this same trait in the same pedigree is autosomal and not x-linked. But how do we do this? Well, to explore, let's imagine that this trait was x-linked and not autosomal. And let's look at this family in the bottom right with their sex chromosomes written below them. Now, as this trait is recessive, the daughter of this family must have two recessive alleles, so let's write those in. This daughter must have received one x-chromosome from her mother and one from her father, meaning that both parents must have an x-chromosome with a recessive allele on it. But the father only has one x-chromosome, meaning that he should also be recessive for the trait, as shown here. But if this was the case, the father would show the recessive trait and would be shaded in. So we can work out that this pedigree displays an autosomal recessive trait by denying the possibility that it could be an x-linked recessive one. Now this is a nice summary of how to tell that a trait is x-linked. For x-linked dominant traits, all affected males should have mothers and daughters that are affected. And for x-linked recessive traits, all affected females should have fathers and sons that are affected. If these trends are held, then the trait is said to possibly be x-linked. But they could still be autosomal. If these trends are not held, then the trait is autosomal. This is why we cannot confirm that a trait in a pedigree is x-linked. We can only deny it. So let's look at another example. And this question is asking us to determine whether this trait, shown in this pedigree, is autosomal dominant or x-linked dominant. First let's look at the second generation, individual two, who is an affected male. All of his daughters and his mothers are also affected. This holds true to dominant x-linked patterns in pedigrees. This pattern is the same for this affected male. And for this one. Consequently, this trait could be x-linked. But as stated before, this does not disprove that it is autosomal. So we say that this trait could be x-linked or autosomal. In summary, today we learn how pedigrees can display different types of traits. This slide nicely summarizes all of the trends that we can observe in pedigrees.


How's everyone doing? Have everybody full? Don't go to sleep just yet? Or maybe I'll help you go to sleep. One of the two. Basically, like Diane just said, I'm from weather.com. We're an IBM company. We're actually what's known as Watson Media and Weather at this point. And that's the umbrella company. And underneath that, we do weather.com and wonderground.com. I'm assuming most of you probably have heard of that site at one time or another. Even if you use the competitor's product, you've heard of us. So with that said, OK, we started out about two and a half years ago now, where we moved everything to AWS and OpenShift. And life was good. We were really enjoying and digging everything that OpenShift brought to the table. And then, as usual, life gets messy. And in this particular case, we got bought by IBM. And so obviously, like a lot of companies, IBM encouraged us to move to the IBM Cloud. And to be perfectly honest with you, it's been great. I'm the first one to admit, hey, I was reticent. I'm a DevOps guy. I don't like people throwing those type of changes at me. And I particularly don't like them picking the stuff I run on. Because I have a production operation site. We do about 23, 24 RPS per page at any given time for any one of our clusters across the world. And we operate seven different clusters. Each of those clusters have about 60 nodes. So we're not a small site. We have a few pieces and parts out there. And in particular, the one thing that we had to get really, really good at was migrating and moving from one Kubernetes platform to another. And then guess what? Then IBM and Red Hat got together. And we're actually moving back to OpenShift. Honestly, we've already done all the work to move back to OpenShift. We're just waiting on the budget people to come up with the money for us to actually do the move. It's totally in a county thing. And one of the ways we did that, and I'll go ahead and start showing you some things. And by the way, anybody who wants to contact me information-wise after this are hopefully if I get invited back at some point, maybe a little better Wi-Fi. Basically, one of the first things we did was we took and we terraformed everything. All of our clusters, all of our configuration, production, non-production doesn't matter. We have everything in terraformed. And yes, we have it for OpenShift as well as the IBM Cloud. So we're not stuck in either one, and we can do both, and we can mix and match. As a matter of fact, what I was hoping to have, but because we couldn't get the budgets in place in time, I was actually hoping to show you guys IBM's hybrid cloud, which I was going to show you Red Hat on AWS and our Red Hat on IBM Cloud. Next time. And that was a big thing. But just to show you, it's not just smoke and mirrors. We do actually have OpenShift already on IBM Cloud. And all that's done through Kubernetes running our terraform. If I want to start a new cluster, all I do is create the terraform files. I actually just clone what I have already and then configure based on the need. I got my new cluster. And that's all the work we have to do. All the Ansible stuff, all the search stuff things, the requesting the search, getting the search put into place, everything. And I do mean literally everything we have through terraform. We have to, we're three guys. WonderGround.com and Weather.com, we have three DevOps guys doing everything. Now we have a whole lot more development teams, including three big CMS teams. And they absolutely are at it all the time and they're very busy. And so one of the other things that we had to do, and it was funny hearing some of the other folks talk about it, but one of the other things that we did was we, I'm sure you guys are familiar with Netflix and the load that Netflix brought. Well, we watched them quite a bit because we want, just like everybody else, we want to learn from the best. And right now on the internet, nobody's really handling more load with containers than they are. So most of the problems that any of us are going to run into, they do. Not an advertisement for Netflix DevOps, but it just makes sense. You go look where people are actually doing some really nice things. And one of the things that they did is a mono repo. And so we're in the process, not totally 100% migrated over yet, but we're in the process of moving all of our stuff, all of our services. This is literally wonderground.com services and weather.com services all in a mono repo. And within that mono repo, any one of these services gets spun up and you'll see a Jenkins.json there. Well, what that Jenkins.json does is it's basically the Terraform equivalent of generating a Jenkins file. And so that's what we do in order. Good afternoon, everyone. Meetings are resuming on the main deck. Please make your way to the main deck. Give a seat. Thank you. You're welcome. And with that, and so basically we, as you might imagine, on the DevOps side in particular, we've tried to, we've turned Terraform into a tool it was never designed to be. And it's working out actually pretty well because it's very declarative. It's just JSON. And yeah, we have to take some liberties and we have worked closely with the IBM. And I'm assuming at some point we will work closely with the Red Hat Terraform team on the Terraform provider, but right now we're able to do both in pure Terraform and generate the whole thing. And we do all this via Jenkins. One of the other nice pieces that we built into our migration environment that enables us to be very flexible is we dedicated a particular Jenkins process to having the build, which is all source code and product related. And the pipeline, where does stuff need to go? And deploy the actual deployment piece that pushes stuff to any particular type of cluster, we have separated and abstracted those three pieces apart. And so what we do within our environment by abstracting all those pieces and parts is we're able to let development do and concentrate on the Jenkins side of things and the automation side of things that are related directly to their build. It's all about building the container for them. They don't really care anything beyond that. And then our QA department manages that pipeline container. They're the ones who know where things should go and when they're good enough to go to any particular environment. And then the deploy side is where we spend all of our time. And the deploy side is the operation side. It is the actual keeping all the stuff and the deployments working properly. And there's plenty, honestly with three people there's plenty of work there for us. And if it was not for this sort of automation we would have no chance with our particular crew. And like all of us we have what we have and you gotta make it work. But what I can tell you is that thankfully both Kubernetes and you can't mention OpenShift without mentioning the underpinning of Kubernetes both have evolved so much and so much contribution has come back from OpenShift into the Kubernetes community that's really propelled and made our life so much easier. It was one of the reasons I love and I don't know if you guys are familiar with the, any of you guys familiar with the IBM cloud? So there are a few of you. Well, anybody who's familiar with the IBM cloud you're used to dealing with work basically worker, we'll call them node pools, worker pools which is just a collection of nodes. Well, you can do that same thing under OpenShift in the IBM cloud with the exceptional difference of in the IBM cloud we do get to use the OpenShift UI, the web base UI which is the one thing I miss the most when I first had to migrate to the IBM cloud away from OpenShift. And so I'm tickled pink to get back into there and why do I love it so much? It's because I can in the non-prod environments as developers are trying to figure out how to run things and how much they're actually gonna need as far as resource. I can give them free reign because the OpenShift console allows me to define everything in such a way I can put the correct controls in place while giving them the freedom to do what they need to do. And that's in a development intensive environment like ours, you guys know how valuable that is. So that said, one of the other big things I was gonna show you is some of the monitoring we put in place. The one that I like the most is we put an aggregated Grafana. We're able to look at all of our clusters through a set of dashboards in Grafana. It's all Prometheus driven. We put the Prometheus exporters in place to collect the statistics that we need. We actually got such good information out of it. We actually changed our HPA and we now drive our HPA off the Prometheus statistics. And because of that, we've been able to go back to the community version of the Node Auto Scaler. How many of you guys are Node Auto Scaling currently? Because you probably realize that's where you get your savings. The more I can do there in my off periods and bringing those number of nodes available down. Well, it all depends because I don't know how it has been for you guys, but our stuff runs pretty efficient. And so we don't push CPU. And so I don't get any scaling on the CPU. We don't push memory. I don't get any scaling off of my memory utilization. We push requests per second. And that's how things drive in our world because we're not CPU intensive. We're information intensive. We're not memory intensive. It doesn't take a lot of information to show a span of weather data. But what we are is that we get a lot of requests and we would bottleneck real quickly if we did not have that custom metrics set to drive our HPA. And once we got that down, we could finally add back in both Node Auto Scaling and an HPA that worked. Because what we were having happen was we were essentially crashing because of the number of requests because there was nothing to drive up to actually allocate a reason to allocate more resources. And then once we were able to put the custom metrics in there where we're doing it by RPS now, now we get the real driver behind our sites. And so we do appropriately scale. And of course there was some tweaking on the statistics because as you probably already know, nodes don't spin up like that. It takes a few minutes to spin up a node. And so when you're spinning up nodes, you needed to have already allocated the node before you needed it. And we do that by playing with the amount of RPS that drives that scaling. That said, I guess you guys are all familiar with the site itself. As Diane has told us, she wanted to hold off until later on any questions. I had a lot more stuff I wanted to show you, but the Wi-Fi is still running just a tad slow. And I'm not gonna torture you guys with that. But this is also, are some of you guys familiar with New Relic? In the IBM Cloud world, we use New Relic a lot. It's not a requirement. It's a choice. And they have some pretty good visuals, but it's still just being driven off of my Prometheus data, our data being spit out by our individual node apps. And we're predominantly node. We have a little bit of PHP on the CMS side, just because that's where that world is mostly at with WordPress and Drupal in our particular case, it's mostly Drupal. But it's mostly node and we have agents in both of those systems, plus we have some agents that work directly off of our custom Prometheus data. And with that said, like I said, the other thing that I'm really proud that we were able to pull off was this aggregated, I'm literally looking at all of my clusters at one time and I can then zoom down to any individual one. This is all standard. The dashboard styling and the actual data behind it, nothing elaborate, nothing you guys haven't seen before. Sorry, I talked with my hands. I bumped into the mic a few times. But we don't do anything special other than we built basically a scraper that aggregates that data together, because we need to look and see how this whole thing's performing as a whole. And as some of you may have already found out in the past, you don't really see that looking at just one cluster when you have, like in our case, seven, eight clusters in production. I guess that's about it for me. I'll keep it short and brief. And if you guys wanna contact me about anything, please feel free. It's been interesting rocking in the Wi-Fi and I appreciate your time. Thank you. All right. All right. Thank you.


Today we're here at Fresh Work Studio to celebrate a new program. We have modernized our procurement system which is Sprint Up. And we're so excited that 58 companies signed up. Out of those, four were shortlisted, one received the award. And here they are. We were one of the companies that went through sort of the concept phases of how Sprint with us can be beneficial to small local companies or any company. We now have a procurement system where small, medium-sized businesses and large businesses play on an even playing field. And that, I think, is what is so, so exciting about this procurement. The investment from Sprint with us is going to be great for our company. We are going to attract talent to British Columbia and contribute to the economic development here, which is really good for the technology ecosystem. This Sprint program is here to support small and medium-sized businesses. We're here to support the tech sector. We're open for business and some people say, this doesn't sound like government, but we are.


Hello, my name is Pascal Avion from FC Micro Electronics. I'm here to present MTP, so MTP stands for Modular Telematics Platform. So what it is basically, it's a set of modules. Connectivity modules, XTE, YN5, Bluetooth, Bluetooth for Energy. This goes in the car? Yeah, this is a pre-development platform. That would be the main brain of the car or what is this? That's the brain of the connected car. It's where all the communication is taking place over all those wireless and wired connectivity standards. Can, Ethernet, FlexRay, that's wired. Wireless with LTE, Wi-Fi, Bluetooth, Bluetooth for Energy. Also positioning, we have precise positioning. And this kind of technology and all that is very old technology in the car industry, right? But it's not very secure and you want to make it more secure? What are you doing here? Yeah, exactly. So on this development environment called MTP, we have attracted working on the Telemaco GP, that is a security processor here. We have attracted an ecosystem of partners, also security companies such as Caramba Security, Argus, and also Epic PT for the software database here. So those companies are putting their solutions, security solutions on Telemaco GP. And we deliver to the market this solution that is pre-integrated, fully working. And we have customers such as FICOZA and they have used this platform in the development of their carcom platform. This is a real product that goes in a real car? It is a real product that is going to a car. And they have been using the same philosophy based on Telemaco GP. They're using what we did there on the MTP. And then they have used some of the modules are the same. Some of the other modules are something different targeted to their applications. So when you say Telemaco GP, which part is that? So Telemaco GP is here in the middle. This is the processor. It's a security processor. Which one is that? Is it running an ARM Cortex something? Yeah, so it's Cortex A. It's a Cortex A7 double core dual core and there is a Cortex M3. So this is the new STM32MP? No, no, no. What do you call it? Or is it not? Telemaco is a family of processors dedicated for automotive, they've created for automotive with high robustness to high temperature. Also for safety relevant system, AZLB, and dedicated around a very strong security core with an HSM. So the HSM is the key element here of Telemaco GP. And that's why also all those partners have been attracted to work with us on security. What's the HSM? The HSM stands for hardware security module. And you're showing some kind of, what are you doing here? So this is what we are developing together with Caramba Security. So Caramba is a security expert company. And we are working together here on a security system to protect the Linux application space in the Cortex A7. So what I'm doing here on this PC. So I'm connected, so here this is a debug console connected to the processor. And I'm going to attack. You attack? I'm going to attack the processor. So first I'm doing, you know, the security is implemented. The Caramba Powerwall application here is implemented on Telemaco. So I will attack the system that is already protected. And this is what's going to happen. So I'm trying to break in the system and send an exploit. So injecting the exploit and it doesn't work. Why? Because it's protected by CarWall. So now I'm doing the same, exactly the same, but using a port that is on purpose, not protected. So this is what's going to happen. I'm attacking this other port. Again, I'm trying to take control of the machine, of this Linux machine here. And what we normally will see. Okay, it succeeded to get the roadkits. So now using this, so I'm connected over ethernet. So using the network, I can manipulate this system that is the car actually. So here, this is a Windows laptop, but I manage the roadkits. So I have the full system. This is Linux. This Linux is running here. So I managed to take control of this computer in the car.  So for example, so we have a little application running here on Telemaco. That is an attack. So I'm doing an attack on the vehicle. Doors are open. Which is doing your own. What does it say? It says airbag deployed. Speed exceeded and the doors open. So it's really what you don't want to happen when you are driving a car. And here we are able to really to hack the vehicle completely. This is when the CarWall is not active. Is this groundbreaking for the auto market? Nobody has this. Nobody has such a wide ecosystem of security on a single platform. With Argus providing the intrusion detection. With Caramba security providing CarWall. And with all the hardware and mechanism implemented in Telemaco 3P. Such as isolation with several cars. Such as the HSM, Secure Boots and also TEE for Linux. So nobody has such a strong security architecture on the automotive processor.