everybody forced here ripping 20 22 elite football hobby six box number 20 random team style you can always find the results at latentsportscards.com appreciate everybody for joining let's get started here Tyler Beatty Ravens recated 999 elite deck Johnathan Taylor Colts James Winston Saints number 24 of 75 from Andre Stephenson epic materials Patriots not numbered playmakers Russell Wilson Broncos a mantra Washington rookie Broncos in 999 high-life CD lamb Justin Herbert on the spellbound 159 to 349 chargers elite deck Justin Jefferson Vikings Kirk Cousins Vikings of 399 Chris O'Lave nice pen pals green ink horizontal there you go Saints great hit there green ankle Lave playmakers Jonathan Taylor Colts Colts can use him tonight Wanda Robinson rookie to 10 for the Giants good box here rookie on deck James and Williams Lyons DMN Pierce Texans rookie to 49 nice hit Texans elitist Barry Sanders Lyons a Samori to write to 999 Packers rookie rookie on deck Sam Howell Washington cross rookie Seahawks to 33 elitist Malik Willis wanted to go on elements guys and it's just gold standard chronicles and select after that Martin Amerson turn of the century rookie Otto Browns to 75 rookie Jalen Tolbert Cowboys to 399 my life T Higgins all right moving on John Mechie Texans rookie to 88 Seahawks pen pals Kenneth Gainwell rookie Otto Seabirds not Kenneth Gainwell Kenneth Walker the third playmakers Alvin Kamara Kenneth Walker the third Kyrie Williams rams rookie to 999 rookie on deck George Carl Aftish chiefs he's got a chance of rookie of the year or defensive rookie of the year Kyle Pitts Falcons at 399 elitist Kenny Pickett Steelers good to see him get the starting job definitely better than last week Trevon Walker rookie to 999 Jags elitist TJ Watt Steelers Matthew Stafford full throttle to 499 or 349 rams elite deck Rogers Packers Broncos Russell Wilson a 399 CD lamb on the Jersey card for the Cowboys playmakers Mahomes I believe so pure strong junior rookie to 25 for the Patriots are probably like USA probably won't be on peacock unfortunately rookie on deck Matt Corral for the Panthers Algea rookie Packers to 399 elitist Breeze Hall Jets turn of the century Packers rookie Otto Quay Walker 50 of 99 Panthers McCaffrey one of 99 a live Jamar Chase Charles Cross rookie Seattle to 999 elite deck Derek Henry hey nice shady yeah man funny enough on Tuesday so my brother lives like along kind of near like the St. John's River the neighborhood that he lives in is underwater like just about entirely some parts there's like four feet of water over the road James Cook rookie bills to 75 and we had to clean out the fridge in the house we had a kayak like half a mile to get to the house there's like two feet of water in the garage no water in the house somehow I honestly the luckiest thing that ever happened crazy yeah a lot of other people's house under water leave deck Justin Herbert no water in the house but the garage there's a mess so clean out dude cleaning out that fridge was honestly the worst part of that day so bad so gross Karen Williams rookie Ramson 999 oh boy well congrats on your trout gold man I hope you guys are doing okay I know it's tough times a George Pickens pen pal Steelers nice hit Steelers got him a creary rookie for the Titans the 399 Micah Parsons die cut yes you buy a box out of your rip tonight it'll be a few hours from now though playmakers Justin Fields rookie on deck Kyle Hamilton high life DK Metcalf Colts Michael Pimmons Jr. to 399 elitist Traylon Burks Titans second quarter still Trevon Walker Jags the 999 Tyree Colton 99 for the Dolphins that's not working that's someone else I'm behind you playmakers Nick Chubb Browns Charles Cross Seahawks rookies and 999 Hawkinson Lions blue 10 of 88 he had a ridiculous game last weekend Micah Parsons Cowboys patch card 17 of 25 Breeze Hall rookie throwback for the Jets there and it's pretty crazy that's pretty crazy rising over the roof that's ridiculous got rookie on-deck Chris Olave yeah man growing up as a kid so it's the house I grew up in and my mom technically owns and my brother let's like lives there and takes care of it basically she isn't in Central Florida anymore but all growing up as a kid stuff never happened it never flooded and then in 08 it flooded real bad for like two three weeks got Sam Howell rookie turn of the century auto 20 of 99 for Washington did it again with Irma pretty bad I'm like Willis rookie to 99 Titans but this is like this is probably two feet higher than it's ever been and that's kind of insane that the record was broken by like just about two feet that's just nuts Debo Samuel star status you betcha convince my mom to sell that's probably that's pretty nice she bought off her her grandfather my great-grandfather he built it she bought it from yeah got a rookie Britann Brown for the Raiders to 999 believe that Justin Herbert it was weird like we were kids could we couldn't afford it basically so like we were we were pretty poor growing up for for a while my mom had a decent job and everything but it's just yeah she she bought it knowing that like well it's gonna be tough for a long time to 349 but she's like I want to keep the house right hard work pays off sometimes you guys playmakers Justin Fields to 31 a rookie for the Bears is Tristan Ebbner Tristan Ebbner and I'm glad you guys are like safe at least Peer Strong Jr. Patriots rookie pen pals rookie on deck Chris Olave Saints I still can't believe Southwest Florida Desmond Ritter rookie to 999 Falcons like just interstates destroyed it just it's it's kind of it's like we it's really weird never seen anything like it highlight Deontay Johnson elite deck Debo Samuel Niners sauce gardener rookie for the Jets to 999 playmakers Kyler Murray Cardinals one Dale Robinson to 399 for the Giants alright guys elements is sold out so we got gold standard chronicles and select divisions case Ravens Lamar Jackson patch card nice patch there to 49 rookie on deck Kenneth Walker the third die cut down cook 12 of 24 Vikings elitist free-solver the Jets Miles Sanders of 399 Eagles Justin Jefferson to 399 for the Vikings elitist Ronnie lot Niners to a back to the future auto dolphins 9 to 49 nice hit Dolphins thankfully they didn't kill him freaking dolphins nice to a hit there we'll get that matter for you Dolphins Sam Howe rookie to 99 for Washington you're right though you call it as a dolphins family is the most dolphins things ever happened like you are right actually I didn't think about it like that someone's gonna make some ridiculous decision do literally drop the ball yep I just hope that he is like okay like not for football like just okay yeah sauce gardener rookie tonight 399 jets they're like oh yeah he's fine had a concussion it's like yeah yeah he definitely had at least that like what are we talking about here guys life exchange whether realizes it or not you lead a straight London for the Falcons joke man Carl Aftos rookie for the chiefs to 999 all for guaranteed contracts in the NFL owners make enough money off the players is a Conmar rookie auto for the dolphins easy easy got a Brian Robinson junior rookie die cuts Washington he should be playing as we can write Brian Robinson junior to a 1099 dolphins nice box for the dolphins or nice couple blocks I should say you'll eat that Kyler Murray craftsman Brandon I you patch card 1099 the Niners elite deck Aaron Rodgers their Packers playmakers Camara Saints rookie on deck Carl Aftos chiefs record rookie jets numbered 80 to 89 I live Debo Samuel there's a Kenneth Walker the third Seahawks with a bit of damage on the bottom I'll send a box and rapper for the Seahawks to 999 a Micah Parsons defensive rookie of the year 9 out of 10 on the blue nice hit cowboys playmakers Camara for the Saints cleaning out a fridge up to the Paris Monoclox like six days I define some gloves like four trash bags full of stuff killing water my rookie to 999 bills I think there's a fridge in the garage that we couldn't get to because underwater so I was like man will we come back to that don't even over the fridge don't over the fridge just throw it out just get it to the dump somehow Davis knows the 399 Texans I was like oh luckily I mean something with oil so clean as much as we could have it out but I was like this hopefully the smell of oil will overtake the smell of Garrett Wilson a rookie die-cut for the Jets that's really cool a list playmakers that Crestcott Jonathan Taylor back to the future Colts auto now 36 799 it's nice vets in here Patriots Matt Jude on a 399 field vision deck 349 for the Cowboys one more here thanks everybody for your patience I know we're a little bit behind we're not crazy behind but it says a little bit I don't like being behind but we had to fill those mosaics earlier gold standards at 13 to go now that's nice good stuff there you'll be this Jerry Rice Jerry doing a break during the day every time I come in he'd be watching like Jerry Rice or Steve Wilcox or something like that Maury Brad 399 Andrew Booth Jr. Ricky for the Vikings him and Uzi was always watching that stuff together man oh my god Cooper Cuppie lead deck God Ricky for the Saints Alante Taylor to 999 playmakers Vikings Justin Jefferson Josh Allen spellbound bills to 75 what's the can-miss sporting event this weekend guys could be anything baseball NFL college football grease haul a rookie on deck what's the can-miss sporting event this weekend UCLA Utah I guess I'll have to take your word for it a looses you go Collins to 88 for the Texans James Cook bills Ricky pen pals bills elitist Sam Howell Washington is brother Dalvin actually yeah I didn't know that yeah bangles and 99 and 999 Ricky Daxon Hill I assume it was like a running bag where did James Vante Smith de-hop 399 Cardinals George that's right that's right running back you over there elite deck Josh Allen them and Bama running back you turn of the century Bears rookie out of Vilous Jones Jr. with a nice orange color match there six at 25 I should have known it with a draw like I knew that but I like just didn't know I guess him at a 399 Colts that's like something that like oh yeah and around draft time I know all of their schools and now I just don't know playmakers Trevor Lawrence Jags I got you Jake scholar Thompson dolphins rookie to 999 that's the new backup right that's the dude right there start him rookie on deck David O'Jabbo they just need something against those wins right now hold down the board hitmen die cut Colts to 24 oh that's a Jake Jake isn't it weird seeing his last name Jersey for the Eagles Jalen Hertz like Evan that's his boy right there Mike Evans my guy almost killed me in fantasy but killed me luckily Cooper Cup saved me Travis Kelsey at a 49 for the Chiefs yeah Niners D and that Alan Robinson doing nothing for Sam help me out quite a bit okay here we go quick recap relics Eagles Devonte Smith or not Devonte Smith that's Jalen Hertz patch card Niners Ayuk to 99 patch card Jackson for the Ravens to 49 elite coverage Cowboys Micah Parsons to 25 Jersey card Cowboys CD lamb Patriots Remandry Stevenson get Autos now Belich Jones junior Bears of 25 Bill's Penn Pals James Cook back to the future Colts auto to 99 Jonathan Taylor is a con with Penn Pals dolphins pier strong junior Patriots turn of the century Sam Howell auto to 99 Washington George Pickens for the Steelers nice hit there quay Walker to 99 for the Packers Kenneth Walker the third Penn Pals Seahawks Martin Emerson is 75 rookie Auto Browns a green horizontal Penn Pals Chris Olave for the Saints that's a really nice hit and back to the future Auto Tua to 49 for the Dolphins nice hits thanks again everybody we've got some more people coming up


Former President Olesha Gunobasanjo has said that the performance of Nigerian leaders before independence is much better. He spoke during the National Daily Awards in Lagos where he said though political activities were raging like fire, pre-independence Nigerians were determined to ensure that they chose the right leaders who made the right decision for the country. Meanwhile, the Lagos State Governor of Babajideh San Walu and the Inspector General of Police Usman Nath Khalibaba were among the eminent Nigerians who received the award for outstanding performance. In fact, in also making choice of leaders, I would say Nigeria in those days also make right choices of leaders. And if your choices are right, the consequences will be right. Your performances will be right. And if your performances are right, then you will attain excellence. I want to extend this congratulation message and this award not for me, for the entire team in Lagos. And I want to say that several, several people that are here today are deserving of the excellent and the excellence award that has been given to all of us. I think I have been motivated enough to do more than what I have done or to do more than what I am doing. I also feel this award will also motivate not only me as an individual, but it will motivate the force, the personnel of the force so that we can do more and the safe Nigerians from the predicament of insecurity. On his part, a former Minister of Health and Social Service, Prince Jillo's Adeluyi said that the people generally looked up to leaders, hence it's important that they demonstrate capacity and character. Speaking on motivation behind awards, the editor-in-chief of the National Daily newspaper said despite the challenges and opera in the country, it will not be out of place to honor patriotic Nigerians who are making a difference in the different sphere. Some awards are commercially driven. What's in it for the organizers? What's the return on the investments of their cash outlay? Now, we are going down the hill negatively. When we have an organization like the National Daily, young as they are, embarking on a new direction and dimension, we must all support that, at least to improve that aspect of the Nigerian space. Why we use the opportunity to show appreciation to many top public figures and dignitaries in the country whose gestures have been worthy of emulation, whose actions over the years and most especially within the period under review, which is the year 2022, have contributed in no small way in uplifting humanity. We also take into account ordinary people who are doing extraordinary things. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


Friends, next in this session we are going to discuss the effect of hyper conjugation on bond order or bond length. So, we will write down here effect of hyper conjugation on bond order or bond length. So, friends we already know that this bond order is inversely proportional to bond length. Bond order is inversely proportional to bond length. So, any one of these comparison if you get you can write down the other one also. For example, you see with one example I will try to explain this. Suppose we have to compare the bond order of carbon carbon double bond in this with the carbon carbon double bond in this. So, if it is alpha and beta. So, we have to compare the bond order of alpha and beta. And if you get this you can get bond length also. So, to understand this comparison what we will do we will try to draw the hyper conjugative structure of this. If I write this molecule like this. So, the hyper conjugative structure will be what this sigma comes over here and pi comes over here. So, the hyper conjugative structure here it will be C H 2 double bond C H single bond C H 2 negative H plus here. So, we have to compare this bond right this bond we have to compare. So, pi is converting into sigma right pi is converting into sigma. So, what happens here we can have three hyper conjugating structure where we have the sigma bond present ok. And one structure has double bond here, but here in this no hyper conjugation no hyper conjugation present here. So, for this molecule the bond order will be 2 right, but for this molecule the bond order will be somewhere between 1 and 2 right. I think it will if you see since the mode the hyper conjugating structure that we are getting here in all those hyper conjugating structure we have carbon carbon single bond present here right. So, we can say the bond order of this carbon carbon double bond here it is close to 1 right it will be somewhere between 1 to 1.5, but we are not again going to calculate the exact value, but we can definitely say that bond order with value will be between 1 and 2. So, if you compare the bond order here. So, bond order of alpha is greater than bond order of beta and we can also say if you have the bond order. So, bond length of alpha is less than bond length of beta. So, bond order comparison if you have accordingly you can write down the comparison of bond length ok. So, one thing we can conclude here that if more number of hyper conjugating structure in which the double bond is converting into single bond then its hyper then its bond order will be less. Suppose one example if I in this molecule there is no there is only one double there is no hyper conjugation here here we have hyper conjugation right. So, in this it is very clear since there is no hyper conjugation bond order is 2 and here it will be between 1 and 2, but what happens if 2 molecule will show hyper conjugation. For example, if I take this 2 molecule C H 3 C H 2 C H double bond C H 2 this molecule you have to compare the bond order of this right. And another molecule is this I will write down here C H 3 C H double bond C H 2 this one beta right. So, these 2 bond order you have to calculate. Now you see if here we have number of alpha hydrogen is what 2 number of alpha hydrogen here it is 3 and if you draw the hyper conjugative structure of this. So, that will be C H 2 double bond C H single bond C H 2 negative charge H plus we have here. And here it will be C H 3 C H H plus double bond C H single bond C H 2 negative charge. But this kind of how many this kind of a structure possible here and how many this kind of a structure possible here. Here we have only 2 structure possible like this where we have carbon carbon single bond because we have 2 alpha hydrogen, but here there are 3 similar structure possible where the carbon carbon has single bond. So, if you compare since more number of hyper conjugating structure we have here in which we have carbon carbon single bond present. So, if you compare the bond order of alpha and beta. So, bond order of alpha is more than the bond order of beta why because in beta we have more number of hyper conjugative structure where carbon carbon single bond is present. Here we have carbon carbon single bond, but here the number of a structure with such bond is lesser in comparison. That is why the bond order of this is more than this and bond length will be reverse the order of this. I hope you understood this concept that I have discussed here. If you do not have hyper conjugation fine, but if you have hyper conjugation then you have to check that whether the bond whether the you know how many hyper conjugative structure we have in which carbon carbon single bond or double bond is present. According to that you can easily decide. Suppose if you comparing the bond order of this, this one and this one here right. Suppose we are comparing the bond order of I will write down this star mark, this star mark and this tick mark these two carbon bond length if you are comparing. So, due to hyper conjugation what happens here you see this sigma bond is converting into pi single bond is converting into double bond. So, bond order is increasing here also the single bond is converting into double bond. Bond order is increasing, but the number of hyper conjugative structure we have in which we have this kind of bond is more over here right in comparison to this. Here we have two such structures, but here we have three structures possible. Hence we can say the bond order of this bond is more than to that of this. So, bond order comparison it always depends on what carbon carbon bond you are looking at. That is why I have mentioned alpha beta and alpha beta here according to that. So, you cannot actually say that because of hyper conjugation the bond order is decreasing right. We cannot say this it depends what carbon carbon bond we are considering. So, I hope you understand this will write down I will write down few examples here we will compare the bond order then. So, all these molecule we are comparing the bond order you can pause the video and solve it I am discussing it now. So, here you see here we do not have hyper conjugation right. So, alpha hydrogen is 0 here no hyper conjugation here alpha hydrogen is 2 plus 2 4 right. So, we have hyper conjugation because of that this double bond has tendency to convert into what single bond right and hence the bond order of we have to compare the bond order right. So, I will write down the heading bond order and bond length will be reverse of this the order of bond length will be reverse. So, because of hyper conjugation this double bond convert into single bond order of first will be more than together of second number of alpha hydrogen here 2 number of alpha hydrogen here 2 plus 3 5. So, more hyper conjugation here we have where this double bond will convert into single bond. So, bond order of first is more than to that of second here you see this bond order correct this one and this one here what we have resonance possible. Here we have hyper conjugation and here we have no effect right. So, because of resonance what happens this pi will convert this bond comes over here right. So, we have conjugation like this right. So, this single bond has tendency to convert into double bond. This single bond has tendency to convert into double bond here we have hyper conjugation double bond has tendency to convert into single bond right and here we have single bond. So, if you see the bond order of alpha is maximum then we have beta and then we have gamma. In beta the bond order will be any value between 1 and 2 right it is near to 1 in this it is exactly 1 right it is slightly more than 1 and it is it is what close to 2 order will be this ok. Here again we have resonance this pi will convert into sigma and here we have hyper conjugation resonance is always dominating right resonance is always dominating this has more tendency to convert into sigma bond order of beta is more than to that of alpha ok. Now, in this last question you see this is alkene right. So, bond order is 2 beta will have maximum here here we have resonance right. So, this bond order will be minimum and gamma will be in between. So, because of resonance if double bond is converting into single bond the bond order is lesser than the hyper conjugation in which the double bond is converting into single bond. So, 2 things you have to keep in mind here the effect which is taking place whether it is resonance hyper conjugation and because of that effect whether the double bond is converting into sigma into single bond or the single bond is converting into double bond. Like here you see in this example the single bond is converting into double bond because of resonance that is why the you know the bond order of alpha is maximum here, but here you see because of resonance the double bond is converting into single bond right that is why it is you know it is a bond order is minimum over here alpha ok. So, you do not have to generalize this thing that because of hyper conjugation or resonance bond order increases or decreases right it depends on what kind of a structure we have and what bond we are considering right what bond you are looking at to calculate the bond order right. So, all these are the discussion of bond order ok. One more example I will show you here ok this molecule you see here you see we have hyper conjugation possible and here we have resonance right. So, because of resonance what happens here the sigma bond is converting into single bond is converting into double right this if you draw the you know resonating a structure of this one you will get this structure we have a free radical here double bond. So, single bond is converting into double bond here what happens the hyper conjugative is structure of here it is and we have h plus here right. So, again you see the sigma bond is converting into double bond single bond is converting into double bond ok. So, both kind of things are there right, but since the resonance is more dominating effect. So, this molecule has more tendency to convert into double bond right and that is why the stability of this or the bond order of this is more than to that of the first one ok. This is how we discuss bond order and bond length will be what exactly the reverse of disorder if you have to calculate the bond length. The next thing we are discussing here is bread's rule right what it says it says sp2 hybridized carbon head position highly unstable unstable not possible sp2 hybridized carbon at bridge head position is highly unstable and not possible what is bridge head position you see if I draw this a structure right. So, if you have carbocation present over here on this carbon right. So, you see this carbon or this carbon that you have here it is what it is now sp2 hybridized. If it is sp2 hybridized then it should be trigonal planet and to maintain this trigonal planet structure this bond should come to this side because trigonal planet is nothing, but this structure ok this one right. So, this bond has tendency to come over this side right, but which is not possible here because this is connected with this carbon this carbon and this here right this is a bi-cycloding bi-cyclocompound ok. So, because of this what happens this positive charge here what happens we have maximum angle strain here right and because of that angle strain this molecule is not stable high angle strain. So, that is what the bread's rule is this position is the bridge head position is the bridge head position and at bridge head position sp2 hybridized carbon is highly unstable ok. One more example if I show you this one this is also unstable and not possible bridge head position not possible what about this one this is possible this is stable this is not the bridge head position you see this is structure we have here right. So, this is possible this molecule is also possible here also it is a stable here it is not stable the positive charge here it is not stable ok. Even if I consider an alkene also like this if the positive charge is not there suppose I will give double bond here this alkene is also not stable because again it is sp2 hybridized. So, this kind of a structure only it is not possible ok this kind of a structure is possible this double bond it is possible ok. So, sometimes they will give you this question and they will ask you which of these you know structure or carbocation does not exist or highly unstable. So, what we have to keep in mind at bridge head position sp2 hybridized carbon should not be there sp2 you must remember do not remember this carbocation because here you see it is not a carbocation, but it is sp2 hybridized ok. So, sp2 hybridized carbon is not possible at bridge head position.


India has been undergoing a change in its health from the past several decades. This can be noted from the increase in the non-communicable disease to the decrease in the infectious diseases. One of the most prominent communicable diseases reported in present-day India is diabetes mellitus. To know about diabetes mellitus and also about the four different types of it, watch this video fully. First of all, let us see what is diabetes? Diabetes mellitus. It is more commonly known as diabetes. It is nothing but a disease that happens when the body can't process blood sugar, which is also known as glucose. See, when we eat, our body breaks the food into glucose. Then the glucose is sent into the bloodstream to fuel the cells in the body with energy. This triggers the pancreas to release a hormone called insulin. This insulin only helps the glucose to enter the cells. What we have seen till now is the normal process which happens in everyone's body. Then what will happen in case of diabetes? See, in case of diabetes, the pancreas either won't make enough insulin or the body cells won't use the insulin produced by the pancreas properly. This leads to high levels of glucose in the blood, which in turn causes symptoms of diabetes. Now, this is the basics about the diabetes. Now, let us see its types. See, there are four different types of diabetes. We will see them one by one. Firstly, let us look at type 1. See, type 1 diabetes occurs when the pancreas doesn't make enough insulin. This means that one has to take insulin every day. It is usually diagnosed in kids, teens and young adults. Also note that it can happen at any age. See, it is caused because of the autoimmune condition. This means that the immune system attacks the cells that produce insulin in the pancreas and destroys them. Other factors that cause type 1 diabetes include genetics and environmental factors. See, a viral infection can also trigger type 1 diabetes. I am saying it once again. Here note the point that it can happen at any age. So if a question comes in the prelims stating that type 1 diabetes happens only in young adults, the statement is wrong. It can happen at any time. This is all about type 1 diabetes. The next one is type 2. Type 2 diabetes occurs when the pancreas is not making enough insulin or the body isn't using the insulin well. This type is more common over the age of 40. But know that this can also happen at any age. See, the cause of type 2 is insulin resistance. It is a condition where the cells in the body do not respond to insulin and the cells will not be able to take glucose from the blood. So the pancreas pumps out more insulin to get blood sugar into cells. This is because insulin only helps glucose to enter the cells. Over time, cells stops responding to insulin. This is only called as insulin resistance. And eventually the pancreas gives up producing insulin and blood sugar will keep on rising. This is all about the second type. Now moving on to see the third type. The third one is gestational diabetes. It is developed during pregnancy. It usually disappears after the baby is born. But it increases the risk of developing type 2 diabetes later on. Now we will see its cause. When a person is pregnant, the placenta makes more hormones. In some women, these hormones can cause insulin resistance which leads to high blood sugar. This is all about the third type. Finally, pre-diabetes. Technically, it is not a distinct type of diabetes. So what do you think it is? See, it is a condition where a person has elevated blood sugar levels that aren't high enough to qualify as type 2 diabetes. So this pre-diabetes increases the risk of developing type 2 diabetes. With this, we have seen all the four different types of diabetes.


This paper presents a holistic approach to align heterogeneous geospatial data sets by integrating spatial, lexical, structural and extensional similarity metrics and automatically aggregating them using approval voting. The approach is validated with real geographical semantic webs and reduces the dependency on specific information for more robust alignment under unbalanced distribution of various information. This article was authored by Liu, Pei Yuanqiu, Shiliang Liu and others. Thank you for watching.


Hey, Psych2Goers. Do you get overwhelmed with how much work you have to do? Does your energy go to waste because you're not spending enough time on the things you need to do? Do you wish that you could produce more without suffering from burnout? Well, you're not alone. Our society pushes the culture that promotes limited sleep and constant work, which isn't healthy in the long term. But having a flexible routine or schedule can have you achieving your marks, producing quality work, while minimizing burnout and creating a more balanced life. Here are 12 ways to be more productive. Number one, create a morning routine. A morning routine might sound counterproductive because you might feel inclined to just jump right out of bed into action. That's great, but morning routines actually helps set the tone for your day. Try creating one that helps you feel grounded, focused, and can channel your enthusiasm into your work. Maybe try a healthy breakfast after a good night's sleep and a quick meditation to start. Number two, initiate before you're inspired. Who doesn't love a good motivational quote once in a while? They're inspiring and really light a fire inside of you to go out and do that thing. But waiting to start something until you're motivated is not going to help you get motivated. You'll be waiting for a long time. It's better to start and let that inspire you to do more.  Number three, break tasks into smaller ones. The best way to eat an elephant is to take one bite at a time. Yeah, it's odd imagery. But when you think about the tasks you have to complete, you don't want to do, you feel overwhelmed because it seems like too much. It's easier to complete the task when you break it down into small, clear tasks. You may even start getting ideas on how to do more work with less stress and effort. Some tasks are more important than others, and some tasks we'd rather not do. However, once this task is done, you'll feel so much better.  The frog is the biggest, most important task that you're most likely to procrastinate on if you don't work on it early. Number five, don't multitask. As good as you might think you are at it, try not to do it. You might be successful with low level tasks like chores, but with tasks that require more mental engagement, you'll tire yourself out faster than focusing on one task. A Stanford University study found that multitasking is less productive than doing a single thing at a time. The study also found that people who are regularly bombarded with several streams of electronic information cannot pay attention, recall information, or switch from one job to another, as well as those who complete one task at a time. Number six, limit distractions. Anything is more interesting when you have work to do and you prefer not to do it.  It's normal to have distractions, but you don't need to tend to them immediately. Try keeping a separate list of random things that come to you that you think are important and do them later.  We all fail. It happens all the time. We think that throw to success is smoothly paved, but failure is the price you pay for it. Success is amazing, but it can ironically make you stagnant and comfortable where you are. Learn from both failures and success. What led you to missing your goal and how can you improve next time? What have you gained from it? Or what helped you achieve your goal and what can you do next time to replicate similar results? Number eight, monitor where your time goes. From YouTube to Netflix to video games and social media. Binges are something a lot of us participate in. You can be preoccupied with this activity and then suddenly it's 2 a.m. A better way to be more productive is to limit these binge sessions. Be aware of where your time and energy goes and how you feel when you've participated in these activities. Do you feel energized, depleted, stressed? How do you want to remedy that? If you plan your time, you can complete your tasks and still have guilt-free chill sessions. Once you get going, it's almost impossible to stop. Your newly discovered overachiever will want to do everything that has ever existed, but you will need to slow down and take breaks. A great method that helps incorporate breaks, limit procrastination and improve productivity is the Pomodoro Technique. A period of 25 minutes of deep, focused work is followed by a five-minute break. It's very important to actually detach from work when you take breaks. Maybe do a few stretches, take a short walk or do some breathing exercises. Number 10, learn to say no. Not only is this habit good for your self-confidence and establishing authority in your life, it's also good for your productivity. You might be tempted, or forced, to agree to doing something you don't actually have the time for when your productivity plate is already full. Don't take on something that has nothing to do with you. Saying no is a life and time saver. 11, use the 80-20 rule. The Pareto principle, or the 80-20 rule, states that roughly 80% of your results and outcomes come from 20% of your efforts and methods. Basically, you need to focus on 20% of your to-do list that is responsible for 80% of the results you need. Let's say you're learning how to play guitar. Instead of learning strumming or hammer-on, consider learning basic chords and transitions. That way you get 80% of the result in 20% of the time. Number 12, make fewer decisions. Making decisions can be surprisingly time consuming and take a lot of brain power. A way to solve this is to automate and make things easier for you to do without much thought. Don't have enough time to cook every day? Try a meal prep or a food delivery service. Don't know what to wear? Look up capsule wardrobes, or try keeping your style to minimal, similar clothes. Artist Dandy Warhol was almost always in a black polo or turtleneck top. You have many decisions to make. Don't let irrelevant decisions take up your extremely valuable time. Do you want to try any of these tips in this video? Let us know in the comments below how you get on. As always, the references and studies used in this video are listed in the description below. Remember to like and share this video with people who might benefit from it. Until next time, thanks for watching and take care.


This study examined the effect of tool pin eccentricity and welding speed on the microstructure, texture and mechanical properties of friction stir welded aluminum alloy AA5754H24. It was found that increasing the welding speed from 100 to 500 millimeters per minute decreased the average grain size of the nugget zone from 18, 15 and 18 microns at 0, 0.2 and 0.8 millimeters eccentricity, respectively, to 12.4, 10 and 11 microns, respectively. Additionally, increasing the welding speed from 100 to 500 millimeters per minute also improved the tensile strength of the welded joints, which was attributed to the increase in the number of dislocations and the decrease in the amount of voids in the welded joints. Furthermore, the yield stress of the welded joints increased from 35 MPa to 40 MPa when the welding speed was increased from 100 to 500 millimeters per minute. This article was authored by Mohamed M. Z. Ahmed, Ahmed R. S. Essa, Sabah Ataya and others.


First things first, can everybody hear me? Excellent. One second, technology has let me down. Let's try that. A few introductions, who am I? I'm James Page. I'm a technical lead in the Ubuntu server and OpenStack team. I've had the pleasure of that role for nearly four years now. Prior to that, I worked in UK financial services for a fairly well-known brand driving open-source adoption and a virtualisation strategy, which was interesting and very cost efficient. In terms of Ubuntu and OpenStack, I've been involved in OpenStack on Ubuntu really since its first release into Ubuntu, which I think was the Bexar release. It seems like a long time ago now, and the project has moved a long way in that period. We've done some really interesting testing with it over that period, which is what I'm going to be talking about. Let's start with some scale testing history. Last cycle, we partnered with AMD, and we had a number of these C microchassies, 10 in total available to us, each with 64 servers, all four core, eight threaded, 32 gigabytes of RAM, and SATA disks, and we tried to push an Icehouse cloud as far as we could and as quickly as we could. We found lots of bugs. We found lots of bugs in our deployment tooling, in OpenStack itself, but our headline figure six months ago was that we were able to get a 370 node cloud to 100,000 instances in just under 11 hours, which at the time was a pretty cool figure. We were very proud of that. We managed to move that on to 168,000 instances sometime later on a lot more hypervisors. The cloud by then was grinding pretty hard. We were stressing the infrastructure quite extremely, but we did flush out lots of interesting features in OpenStack. For example, how the OpenStack dashboard behaves when you have that many instances in your cloud and the admin screen start collapsing because they can't figure out, they can't get enough data back quick enough from over a neutron and things like that. We fed most of those changes back upstream. This fixes in for a lot of stuff and we've improved our own deployment tooling. For example, the 500 nodes took around about 13 hours to deploy six months ago and we've now repeated that test and things have improved. This cycle, HP were kind enough to give us two weeks in their discovery lab with some moonshot chassis. For those of you who don't know, these are very high density, small footprint chassis. The cartridges we were working with were the M350s, which are Intel atom based servers. They're all 4 core, 8 threaded, 16 giga-gram with micro SSDs attached. They're fairly good from an IO perspective, gigabit networking. We had three of these chassis to play with. 540 servers in total available across those three chassis, so very dense deployment. We repeated our testing. We went back and we did a nice house test to see where we could get to with that. The first thing I will say is that that 13 hour figure had reduced to two and a half hours. The time from no cloud to cloud you can run stuff on was just over two and a half hours, so there's a significant improvement. Some of that we can credit to SSD, so the speed of IO is really important during install. A lot of that was improvement in our deployment tooling to make it much more efficient when you're managing this many numbers of servers. I'll talk about that tooling a little bit. Our headline figure with Icehouse was 100,000 instances in just under six hours. That was on more hypervisors, so we did a little bit more bandwidth. Then we moved forward to the current lease and we looked to Juno. Turns out that pretty much behaved the same way. After a little bit of tweaking we found some interesting scaling regressions, specifically when you get to very high instance densities and how many RPC messages flow across message buses and stuff like that, which I'll touch on in a minute. It reproofed the scale of OpenStack during the Juno release. We saw some really good improvements, specifically in Keystone. Scale's very much better on a single unit compared to Icehouse. It has much more leverage in using OS processes rather than venting the threads, so that's given us some really good performance improvements there. We've seen actually some improvements generally as well. Our 14.04 release kernel, the 313 kernel we've released with, has improved over six months. We've got six months of stable fixes gone into that kernel and the efficiency of running KVM instances has improved a lot. The overhead in terms of processor of running instances has greatly reduced from a couple of hundred instances on a node maxing out that node to that being, if they do not do much, less than 5-10% utilisation. A really good story in terms of how things incrementally approve from releases we've been to over the period of a long-term support release. So what does that look like? This was the cloud we built on the HP Moonshots. The big blob in the middle is Compute Nodes, if you haven't guessed. We ran with eight cloud controllers running Mova services for neutron controllers running neutron API services in back-end RPC. Just a single Keystone and Glance. They're not particularly heavily loaded. Once you've got Glance messages out to hypervisors, for example, they're all cash, so it's very efficient. So we didn't need to scale those out and consume resources there. We actually ran in a split broker configuration, which I'll talk about in a minute with BravertMQ, which gave us some benefits in terms of message performance and throughput. Just a single MySQL instance. SSD really helps there. We'll touch again on that in a minute. And we just had a single Neutron Gateway node and Layer 3 routing. So how do you get to this level of clouds quickly? And what are the things you need to be thinking about when you're designing a large cloud? So the first one of those is really messaging. OpenStack is a busy place from a messaging perspective. Creating instances, lots of messages. Periodic tasks, lots of messages. Telling all your hypervisors about the instances of running in them and their port and MAC addresses. Neutron gets very busy. So you really need to think about how messaging is delivered to support OpenStack services. Same applies for database. The backing persistence store for your cloud is critical. It's critical for the operation of the cloud. If it disappears, it's going to be bad news. If it's performance constrained again, it's going to start having problems. Network is also critical. A lot of things consume a lot of bandwidth, both from a back-end administration perspective and the instances that your tenants are going to be running in your cloud are going to be consuming a lot of resources as well. So you need to consider that in the total picture of your deployment and the underlying storage. So the spindles that instances are going to be residing on, the performance of those is critical. If you're going to be doing Cinderblock services, BotDevice services, you need to consider how you achieve performance in the back-ends used with Cinder to deliver service to your tenant instances and your customers. And you need to consider the OpenStack services themselves and how you scale those out, how you provide HA resilience and security. So let's focus in on the first one of those topics. Messaging. RabbitMQ has been the default messaging solution in Ubuntu OpenStack. Since we've had OpenStack in Ubuntu. It's a mature product, gone through several major releases since 1204. And it deals with the load pretty well. Deals with the very heavy load that Neutron needs to support cloud operations. For example, on the 500 node cloud we had with the Neutron chassis, we often saw 10,000 to 15,000 messages a second running through the RabbitMQ instance that was supporting Neutron. So it's very, very message-intensive with the reference ML2 implementation for SDN. Nova's a little bit quieter. Maybe an idol of 300 or 400 messages a second and then picking up to maybe 1,200, 1,500 messages a second. It's not as noisy from a messaging perspective. So we also need to consider how we provide resilience. Fortunately, RabbitMQ is built on Erlang. Erlang has some nice native resilience features. So we can leverage that via RabbitMQ itself to use native resilience features in RabbitMQ. That allows us to mirror cues across brokers, which all communicate in a cluster. If one node dies, then another can pick up the load and all the clients should reconnect and your cloud should continue to function. However, you're still going to be constrained by the performance of any one of those brokers and there is an overhead to mirroring. So it's not a cost-neutral thing to move from a single node to a cluster node. What other approaches do we have to dealing with messaging? The other option is to run with split brokers. So we know Neutron is particularly busy, so pushing that out onto its own broker makes quite a lot of sense. It means you're not going to be disruptive to other services like Nova and Neutron, which are less intensive from a messaging perspective. But there's some limitations here. So Solometer, the metering tool, very much relies on notifications delivered via messaging and it likes to do that on a single message bus at the moment. So supporting Solometer in a fluent way of running split brokers is not currently supported. It would be a nice feature to see in Solometer. You might see that, I don't know. But it would be pretty cool. In terms of security, RabbitMQ supports native SSL and that's probably the best way to secure at the moment. I know that the FFSNP project as a whole is looking at how to secure messaging and other options are being looked at, including encrypting the messages themselves, which then makes it very transport neutral. So whether it's RabbitMQ, Cupid or any other option that comes along, then that works really well. RabbitMQ does scale quite nicely vertically, so adding more memory, more processes, allows you to deal with more messaging and more clients. It also really benefits from SSD. It will aim to get all messages onto disk so that if there's any type of failure, that they're persisted. So having something underneath that really helps with the IOPS does help that. This is the deployment that running the split brokers is what we did our most recent scale test on with Icehouse and Juno. This is the Juju GUI view. Juju is the service orchestration tool for Ubuntu. You can see on the left and right-hand side there, we have NOVA, a neutron-dedicated message brokers, and then the stacks of open stack services around that. We also ran clustered cloud controllers and neutron API servers to provide resilience in the cloud as well. So what other options are there in addition to RabbitMQ? Some of you may have heard of ZeroMQ. ZeroMQ is a brokerless messaging solution. It provides an abstraction there on top of TCPI sockets that has a lot of semantics that are familiar in a messaging system. It's point-to-point, so if you need to broadcast a message out to a number of nodes, the client is responsible for delivering nodes to the endpoints. So there's a certain amount of open stack deployment topology discovery that's required, so each client needs to know about what things need to know about what data. And it has some real promise. In September, we spent a week or so sprinting on this just to see how it worked and whether it was worth progressing further. It works fairly well with NOVA at the moment, but there's some inefficiencies in the driver implementation, which means it doesn't work well with Neutron. It doesn't deal with massive fanouts at all well. There's some inefficiencies in message sending. So it's not ready for Scout out just yet, but I think it would be an interesting space to watch in the next cycle. So moving on to database. Again, system full state, really important. MySQL is the fully supported MySQL offering in Ubuntu. It's a very traditional approach to clustering. Active Pass if we share a block device. Something a lot of people are familiar with using the cursing pacemaker cluster stack on top of that to provide virtual IPs and stuff like that. But there are some other options, so Pacona and MariahDB both provide active active MySQL options. So these aren't scale out solutions, but they do provide improved HA. So a right to any node in the cluster is a right to all nodes, and it won't return until that's happened, but you are constrained by the slowest node in your cluster. So you need to make sure it's balanced.  We generally work on clusters of three to avoid split brains. Two nodes is not great without any type of arbitrate to ensure that network splits don't result in two things, trying to do the same thing at the same time. It's also tuning options around MySQL as well. Concurrent connections is a really key thing that a lot of people forget. I think the default in MySQL is something ridiculous, like 150. You don't get far on that. You need probably more like 10,000 for a busy cloud than any number of neutron and nova services. Again, native SSL by MySQL, if you want to use it, has the overhead of SSL on each connection, so it needs to be considered within your total deployment as to whether your infrastructure can deal with that. So there's some other things that leverage messaging and database within OpenStack itself to attempt to provide increased scale, and the one that's been in place for the longest time is Nova cells. It's been in OpenStack for a few cycles now. I know it has some fairly large users. Basically, what that allows you to do is federate messaging and database within an OpenStack deployment.  Then there's connecting tooling, which is part of Nova called Nova cell, which does the message routing between API cells and compute cells. There's multiple tiers with that. The idea is that this allows you to limit the load on any given underlying database or message broker service. Obviously requires a bit more infrastructure potentially, but it has the potential to build larger clouds. We've done some testing around this. We did some testing on the moonshots, and we had some success, but we also found some issues as well. It's still described off stream as experimental, and I think I'd agree with that. The other limitation is there's no similar construct in other projects. I think for Cinder, it supports cells in terms of it knows how to deal with that when Nova is using it, but it doesn't have some of the scanning issues that Nova has. Neutron doesn't have any similar concept with the MLT reference driver right now. If you want to do cells with Neutron, that is possible, but you're still using a single message broker to provide all your Neutron services across the cloud, so you've still got a potential choke point there. What about the OpenStack services themselves? Most of these just scout out. A lot of them are lightweight API and RPC services, so with HAProxy on the front end providing load balancing for API requests. It's a pretty easy story to scout out most of these things. A message broker with the topic in queue configuration that OpenStack sets up allows RPC workers to be distributed across nodes and deal with and scale out horizontally to deal with loads coming from compute hypervisors or wherever that might be coming from. Up until Juno, there were the Neutron network gateway nodes that provide north-south routing of tenant instance traffic in and out of cloud were a bit of a pinch point. You could do some scale out horizontally, but there was limited support in terms of resilience. That's changed for Juno, so Juno introduced the concept of RouterHA on the edge and the distributed virtual router which pushes east-west traffic routing down into the hypervisor layer rather than it being on dedicated infrastructure points. That's really held. Fairly new. I haven't tested that at any scale yet, but I'm hoping to do that next cycle. There are pinch points within that infrastructure, so during instance creation your Nova controller and Neutron controller nodes are going to get very busy. They deal with a lot of RPC messages for instance setup. During our testing, we run with a concurrent instance creation of 100 instances at any given point in time we'll be trying to be created and on the cloud controller nodes we had in our moonshot test that was driving a CPU load of 60% utilisation across all 8 nodes and then combined that with periodic tasks coming back from the hypervisors including power state sync stuff like that, that easily spikes up to 100% across 8 nodes on a regular basis. I think there's some opportunity to do optimization within OpenStack itself but it's a busy place. Even a cloud not affecting change is a busy place from a messaging perspective. In our reference implementation architecture we use Apache for SSL termination. It's proven in terms of its scale and we use that to front as a proxy to underlying OpenStack services. It's well security sported in Ubuntu is the other reason so we know we're going to be up to date in terms of security patches and stuff like that. This is a pick out from the HP moonshot test which shows the load on a single Nova cloud controller instance in those 8 during the background of 60% of instances being created and then the spikes periodic tasks run across the cloud. Hypervisor The default hypervisor in Ubuntu has been KBM for as long as I can remember and has been involved in Ubuntu anyway. There are other options so Zen's there if you want to use it. It's not something we particularly test. Following on from earlier announcements today you also have options with Lexi. There's been a Lexi driver via Libvert for a while now and we've been developing a native Lexi driver during this cycle which takes the Libvert layer out as a small direct control and influence things like unprivileged containers and stuff like that to provide increased security. Other things to think around on your hypervisor layer so your instances are going to require some storage. That storage is going to sit on blocked devices on the server typically so having good IO performance can really help with contention. This cycle we've been looking at Bcash as an SSD based caching layer on top of spindles to see how that improved performance. It looks pretty promising. We've got that in 1410. We're going to do further testing on that this cycle and see if that's a good way forward in terms of not having to put pure SSD in your compute nodes which is not a great idea. You can also back off to other storage devices so Nova now has a native Seth backend this cycle which looks interesting but again you're just moving load on to your network so some interesting challenges around that. The fourth aspect I mentioned that first slide was network so typically I found that gigabit is sufficient in the control plane so for messaging, database, API calls even in a large cloud you're not going to be stressing gigabit networking hugely especially if you start splitting out internal networking, admin networking and public networking so you can split those out and provide different network access points into those services quite easily and that's supported in OpenStack. The real pinch points are going to be on tenant instances so if you get up to any level of instance density with any significant workloads then 10 gigabit on the back end support tenant network traffic both between hypervisors and to the outside world is a pretty good idea and the same applies down to the storage ware as well if you get any amount of block IO against the Seth backend that's going to start pushing gigabit pretty hard you're going to check on that before you can actually exert the spindles to any any extent on the back end so having 10 gigabit there is a really good idea the other thing we've been looking at this cycle is IPv6 support and this isn't really IPv6 support for tenants this is how do I run and open stack cloud on IPv6 we've done quite a bit of testing around this we found that the support in Noveson and Keystone is pretty good initial and glance requires some hacks right now and Swift is not there it's tricky, there is a hack but it doesn't scale particularly well and for a front end that's going to be potentially serving a lot of public accessable API requests it's not a great solution right now a lot of this is in a deficiency in the dependency of open stack I think we're going to try and spend some time this cycle to see if we can actually fix the underlying issue rather than trying to work with workarounds all the time so we can see how that works out we've also been doing some work in this space with a company called Stam who have quite an innovative SDN solution and it's all based on the Linux kernel it's not upstream in open stack yet and I know they're working towards doing that so we've been doing this on behalf of a partnership with the telco we've been working with so last element was self storage so we talked about the 10 gigabit client access layer into a self cluster being pretty important you might want to consider having dedicated high bandwidth for the back end cluster network as well so this really saves you if you lose any number of self modes in your cluster those resyncs between the remaining nodes to restore replica counts of blocks stored in your self cluster will then be performed over the dedicated back end network rather than impacting on client performance on the front end it's really about risk mitigation if you can afford to take that impact on the front end then fine just run single networking if you want to offload that to a different network then you've got options there as well in terms of the underlying storage within a self deployment on separate block devices for a while with the intent of using SSDs with back end spindles that works pretty well you'll see some benefit especially with IO spikes but self is really about the heavy lift in my opinion it's about dealing with thousands of instances accessing thousands of block devices all at the same time getting a good consistent performance so those help smooth the bumps but they're never going to give you the extremes performance that a direct attach and for example it's going to give you okay so how do I tell my overstat cloud scales to the extreme so I'm going to talk first about how you deploy a cloud to this level and the first thing I would say is deployment repeatability is critical if you ever want to tune a cloud to get this level of performance so having a fast repeatable deployment process is really really important we do that using a few tools that we've developed over the last few years so we do all our bare metal server provisioning with a tool called MAZ metal as a service we do our service source creation on top of that with juju and then we have a number of open stack charms and seff charms and myskill charms and ravellend and juju charms which are the encapsulation of all the devops knowledge on how to deploy those individual services and how they relate to each other so what that gets us to is a single line deployment that deploys 509 clouds so in this line we're using a small tool we have called juju deployer we're going to tell it to bootstrap an environment we're going to use this configuration file called openstack.yaml which is a yaml file containing charm definitions, configuration options and relations between those things and numbers of units and that sort of stuff that you know or I'm a huge split topology and if we want to change something so we want to turn on layer 2 population and switch to VxLan networking we can just delta that into the yaml terana if I redeploy it two and a half hours later we have completely new clouds that we can then re-benchmark retest you won't get it right first time so having this is really really important so verification and benchmarking again is really important we've been using Tempest for a while as the upstream functional testing project generally proves pretty reliable this cycle we've been using rally for benchmarking from projects started by our friends at Mirantis we've found it really good for doing general benchmarking, boot delete cycles in and over whatever it might be and we used rally to drive the 100,000 instance test as well so kind of boot and forget type activity as well it also has some pretty good reporting showing you beta and provides JSON so you can chop and change it and analyse it how you like last thing you really need is really good monitoring so understanding how your cloud is behaving is virtually impossible unless you can see the stats of all the servers that are running within your cloud so we used ganglia for the last year test it's quite lightweight from a monitoring perspective it's very asynchronous and it allows us to look for patterns so on the right hand side there the two graphs there from the nova claire controller nodes and you can see the effect that a periodic task has on networking throughput on nova claire controllers so that allows us to see patterns, analyse a code see what events in OpenStack that's having on a regular basis is causing that and then deep dive into actually understanding that and trying to resolve those issues the top was going from 0 to 250 nodes in about two and a half hours so I'm right somewhere okay so that's all I've got to say haven't got any time for questions or do we need to move on? no we can take a couple of them any questions? no, change your mind gentlemen I have a question regarding to that two rabbit mq brokers so how do you configure that brokers I guess some components point to one broker the other point to the rest yeah basically so your nova's configured to point all your nova components point to one broker the neutron components point to another then how about the cilameter well exactly yeah you can't you can't configure cilometer in that deployment because it relies on a single broker for notification so it's the limitation against the broker alright sorry, before you go we wanted to finish on a high so with a real live customer story we've been working with telecommunications providers, financial services for a little while and we're lucky enough to have two gentlemen here from Sky so I'd like to introduce Will and Matt from Sky to tell you some of their story with Xtreme Appasite thanks Mark good afternoon guys so let me do a couple of introductions first and foremost I'm Will Westwick I head up Enterprise Technology an infrastructure strategy and enterprise architecture for Sky I'm Matt Smith I work for Will and I'm the cloud platforms and engineering manager doing the deployment and implementation and support of our OpenStack implementation so Mark asked me a couple of days ago just to spend a couple of minutes talking about where Sky is as a business today why OpenStack is important for us and what we're doing with it and then just share just literally a minute or two of some of the lessons we learn and our experiences with Ubuntu and Canonical so first of all for the benefit of everybody in the room who is Sky so Sky is Britain and Ireland's leading home entertainment and communications company we have over 10 million subscribers today so it puts us up the top notch there with paid TV globally I think fundamentally what we're about is millions of families giving them better choice for TV we have a choice around content and it's not just about linear streaming it's also about video on demand as well so it's about giving people choice and improving that TV experience we are also the fastest growing communications company in the UK as well so we have over 5 million customers now on broadband and telephony services which is a real fast growing area for us and fundamentally for us the most important thing for Sky content is at the heart of everything we do so we own some fantastic riots right across from sports the English Premier League, Formula One entertainment shows such as Game of Thrones and so on but the interesting thing for us today is Sky's business is evolving it's changing rapidly around us we have our set of emerging connected products and services that are basically taking the focus away from traditional broadcast technologies and into the IT data centre and that's forcing us to look at actually how we approach our data centre technologies and make us actually think about an open cloud approach to infrastructure with open cloud we look for flexibility and we look for innovation and commercial sustainability and that led us to making a big bet on OpenStack and we made that bet and from there we hope to gain a lot of benefit from the fast pace of innovation around the OpenStack community and also flexibility for our anagility to help us with our application to support and application deployment so once we've made the bet on OpenStack we had to choose at that point do we go straight from trunk do we go for a distro and if we go for a distro which distro is it that we actually choose and that's the choice we've made I think Matt's going to talk a little bit more about that so we chose Canonical there's several reasons for it major factors one of them was commercially favourable favourable against the competitors out there so we went round to all the competitors and Canonical lots of discussions Canonical sort of tipped the edge a little bit we really admire the Canonical's software product philosophy in that you can have the same product supported, patched, bug fixed with a subscription and run exactly the same product patched bug fixed without a subscription and there's no sort of penalty for doing that so we can have a development environment non-supported environment fully supported, fully patched and both exactly the same exactly the same product so a key flexibility for us recognise a Canonical ability to deliver so we see that Canonical's done pretty much the majority of the open stack implementations in the world and some of the largest and that gives us a sort of key leverage in using those skills in getting it deployed in sky with a minimum of fuss the long-term support that Canonical provide for 14.04 in Icehouse is what we're deploying really fits in with our time scales and life cycle of our open stack deployment and another thing that's sort of a bun-two is recognise as the number one OS for the cloud and we use that internally for our OS leveraging the same skills for open stack deployment fits really well I just add to that part of that very broad deployment breadth we saw that as a significant play for helping us de-risk open stack so open stack was new some deployments are successful some aren't so successful so what we wanted to try and do there is select a distribution and a partner to help us de-risk it as much as possible to ensure the implementation was successful and speaking with the Canonical team it's a good cultural fit with the guys at sky so we have gotten really well with people and it's sort of gelled very well very good partnership with the Canonical team and in choosing an open stack distro you need to choose the deployment tool so James described juju and mas so we looked at the other tools that other distros provide and we thought juju and mas were the forerunners and give us the quickest way to deploy had some good experience with juju and mas and with the team so we ran into a bug with juju reported it to Canonical they put it on launchpad.net we watched it being fixed around the world so some chap in Australia fixed it for 8 hours went on to a chap in Chile went round the world so the bug fixed a point release and 2 weeks later we've deployed it and upgraded and everything fixed that type of flexibility from a partner a technology partner is essential for us today as we start to build very very very strategic products for us around over the top video around connected set top boxes and so on we need to make sure we're working with technology partners that can respond almost real time 2 weeks is what we're looking at so identify a problem fix it and drop it and same tools so we removed all HA capability out of open stack and redeployed it in a few hours with the guys from Canonical with no downtime at all really really good stuff one thing I'd like to mention is thanks to the team that have been helping us so Ante we'll start off somewhere and one thanks very much you've done a top job any questions for we've got a few minutes for questions please first we've got a gen 1 deployment node count of 100 Canonical's reference architecture just on the networking we're I wouldn't say deviating but we're having additions so I think on the node count piece four availability zone spread across two data centres basically two regions if you like and our approach to open stack incremental approach generation by generation so Matt refers to our gen 1 drop so the first footprint if you like and the first configuration is generation 1, 100 nodes spread across those four az what we'll then start to do is build that out and extend it as part of a generation 2 and a generation 3 and so on so we're sure that we had a reference architecture that could expand but also capture changes in open stack as each new release drops and as the technology and the platform emerges basically any other questions at the back there the green hat we did some testing like James has done so we're using GRE and maximum instances per node was something on 128GB was something like 135 instances and no errors so it's a good experience one of the biggest challenges I think we're going the stage that we're at now one of the biggest challenges we're going through is actually working with the application teams around application migration on to open stack the design the architecture of the design the implementation we've actually found with Canonical's help quite easy that's not the hard bit the hard bit is getting your applications to adapt and the architecture of those applications to adapt so that you can get them on to a cloud platform and actually to be optimised for cloud and get the advantages from it that's the challenge that we have today Alrighty well I think that's all we have time for thank you so much to Will and Matt for giving us a little insight


What is your funniest and most memorable moments working together? Watching Claire demand chocolate and watching her get angry. Why do you? I'd never get angry. No, you don't get angry, but when the red mist descends. I know. I find it just wonderfully entertaining, because it's never with me. No, I'm never angry at you. No. Well, I've been angry at once. Well, really? Maybe I never showed it. What for? What did I do? No, I don't think I've ever been angry at you. Really? Yeah. With sweet things. Yeah. And at a certain point in the day, we both start the day really well. We're not going to do it. We're not going to do it. And then if there was ever any eye contact at any point, there would be a silent communication of what's going to happen. Let's get the minerals out. And then it was all hell, break loose, and then there was a moment where we'd hate each other and ourselves. And our lives. And we'd go into sugar coma. And it was bad. Will you know what to get for Christmas now? Just get laser chocolate. No. Go on. Shove it down at Christmas. Oh my. In the end of episode four where Margaret comes back having met Tony, she explodes into her room. We put on a track and I had to coordinate kind of going around turning all the lights on and time to the music. And then I sat back down. And I sat back down. I went right over. My heels went right over. Fully. Fully. Did like a fully whatever. What do you call it? Like a back roll? Like a back roll. Like a full blown. And the heels flying. And everyone went desperately silent. And like didn't laugh. I was like, guys, you have to laugh because it's like you just left me on the floor. So that was probably, we were in like fits of gear and we kept watching it on playback for like weeks. Then you just have to redo the scene again, pretend it's never happened. Straight face. Yeah. It was the first day of filming as well. I'm super clumsy. I don't have much coordination. So it was, I don't think it was unexpected really. You guys both have very posh British accents in the show. Can you show us how to do your best accent? There's only one thing you need to know about that accent and it's that you need to say one. One. How do you say was, Matt? Don't get me started on was and was. I mean for God's sake. You don't know which way is up, do you? Well was apparently is the right way but it was. Was one. Was one. Was one. Was one. That was a real, like the B in my bonnet. It really was. It really was the thorn in his size. So how did you know what was the right way to say things and how did you learn how to say it in the right way? There's a guy called William who's there with a cattle prod. He has a taser gun. He just says me. And then you say it correctly. Yeah. He hits you on the face of the fish and then you just hit right. I'm actually thinking this is happening. So the camera's on your face, taser gun's below the whisk. Yeah. He actually goes, he shuts in. No, say one. He has never done that. But you're not in me. Tarnishing his good name. No, but that's essentially what happens. Do you get into character with the voices? You know, try and keep yourself within the voice. You did that sometimes. Did I? Yeah. I'd see you going. Talking to yourself. People do very strange things on film sets. Before they say action.  Naturally everyone's going, what are you doing? It's so weird isn't it? And then because it's not how life is. And now acting. Yeah. And now fake emotion. Oh my God. Practice all the time. On set. It was such a weird accent to do. And we ended up having to treat it like a dialect.  And she's a really weird accent. And it's got a lot of German accent in it because of the heritage. Practice all the time. Where Matt and I would actually on set go round all the time in the accent. Speaking with a dialect coach. And you'd have to maintain it because otherwise it felt really weird. Can you give me a line of Britishness? Or what would you like me to see? It becomes very easy because you have to practice so much. Apparently you guys got tasered if you got it wrong. So there was a voice coach that would tase you. Oh my God. I know it literally off to everything. I'd be like, ah I forgot the beacause. Sorry William. Yeah. Things like beacause and I don't know. Actually, things like that.