Daily Tech News show is made possible by its listeners. Thanks to all of you, including Alexander Nisev, Hector Bones, and Tim Ashman. Coming up on DTNS Watch OS 9 and iOS 16 arrives September 12th, followed by new iPhones, watches, and AirPods Pro. We're going to talk about all that. Plus, tracking your face is the next wave in virtual reality. This is the Daily Tech News for Wednesday, September 7th, 2022 in Los Angeles on Tom Merritt. And from Studio Redwood, I'm Sarah Lane. In Salt Lake City, I'm Scott Johnson. Out of Atlanta, this is Terence Gaines. And also out of Atlanta, Nika Monfort. I'm somewhere, but I'm the show's producer, Roger Shane. Indeed, we got a packed house today for the Apple announcement, so let's start right with some tech things you should know. Huawei announced the Mate 50 and Mate 50 Pro phones, both offering typical Android flagship specs, with the Pro offering a 120 Hertz OLED display, the standard Mate 50 has a 90 Hertz OLED. While both offer only 4G cell connectivity, they are the first phones to support China's Baidao satellite network, which allows for sending short texts and uses navigation without a cell signal. Both are available now with the Mate 50, starting at $4,999, which is about $718 US. The 50 Pro starts at $6,799. Ring doorbells began rolling out support for end-to-end encryption for the battery-powered version of not only the doorbells, but also the camera. It introduced this feature on its hardware devices in July 2021, hard-wired devices in July 2021. This makes video footage from the devices only available on enrolled iOS or Android devices, using end-to-end encryption disables video previews, notifications with video snapshots, and sharing footage to third-party apps and devices. Qualcomm refreshed its mid-range and entry-level mobile systems on a chip with the Snapdragon 6 Gen 1 and Snapdragon 4 Gen 1. Both SoCs will use ARM's Cortex A78 CPUs for their performance cores, but won't use the ARM V9 architecture like the Snapdragon 8 Gen 1. Qualcomm says the 6 Gen 1 should offer 40% better multi-threaded CPU performance and up to 25% better GPU performance than its predecessor. The 4 Gen 1 will offer 15% better CPU and up to 10% better GPU performance than its last-gen chip. Albania's Prime Minister Id Rama said the country cut diplomatic ties with Iran, citing a major cyberattack in July that shut down several Albanian government services and websites. Rama said an investigation showed quote-unquote undeniable evidence that the attack was orchestrated and sponsored by the Islamic Republic of Iran. The security firm Mandian expressed moderate confidence, in their words, that the attackers acted in support of Tehran's anti-dissident efforts. Well, some people haven't waited for it, and we're getting it in some form anyway. Twitter confirmed a TechCrunch report that its upcoming edit tweets feature for Twitter blue subscribers will let users edit a tweet up to five times within 30 minutes of posting. The company said this number could change based on user behavior, which I don't know why you would want to do that five times in 30 minutes, but whatever. Twitter will first roll out the feature to blue subscribers in New Zealand, later coming to Australia, Canada, and the US. All right, let's talk a little more about VR before we get into the Apple announcement. Scott, what do we got? Sure, headsets on, everybody. Meta announced it will hold its Kinect conference and live stream it on October 11th at 1pm Eastern. So jot it down if you're interested. Kinect is held for AR and VR developers. Meta only said it will talk about what's to come in the near and far future. But CEO Mark Zuckerberg had said previously that the company would launch a new VR headset in October. So I guess we'll see. In any case, expect to get more details on its high-end project, Cambria's headsets, and the Horizon Worlds VR app. Elsewhere in the VR world, HTC announced a $99 facial tracker for the Vive Focus 3 as well as a 249 eye tracker. Both are available now. Yeah, so Meta's project Cambria is supposed to come with eye and facial tracking. So HTC looks to be getting a little bit of a jump on Meta here. HTC announced a $99 facial tracker for the Vive Focus 3 as well as a $249 eye tracker, both available now. Yeah, so if you're not clear, it's a $99 HTC facial tracker and a $249 eye tracker, both available now. Let's actually talk about these.  Has a response time of less than 10 milliseconds. So pretty close, not much lag, and only adds 11.6 grams to the weight. So not a lot of weight. Plugs into the Vive Focus's USB-C port though. So it is going to take up that port. Well, the eye tracker has a dual camera system, as you might expect, that can track direction, origin, blinks, pupil size, and position. It adds 54 grams and attaches magnetically. It can be used to tell you where you're looking, but also replicate realistic eye activity. And the biometric data, the sensors can be integrated into apps using Vive Wave SDK, that development kit. We'll get that. According to upcoming OpenXR support as well, as Unity Unreal Game Engine and native integration.  I mean, it's nice if you're into the metaverse. Again, I'm not going to be a naysayer before trying some of the stuff out. I am a MetaQuest user, an enthusiastic one. But yeah, it's that replicating me thing. I'm not sure what apps I'm using in VR yet. Don't fight the future, Sarah. I'm just saying. You've got to have the sensors first, then the developers make the stuff, and then you go, oh, that's how it works. That's great. So the next time I'm doing VR exercise, and I'm like blinking uncontrollably because I'm sweating so badly, I'll know. Yeah, everybody's trying to make social happen. So we'll see if they succeed. If you're feeling social, you can get in touch with us. You don't even need an avatar. You don't need to trap your nose or anything. Just go to Twitter. DTNS Show is our handle there. Or Instagram. DTNS pics. DTNS P-I-X. Let's talk Apple Watch first. The Apple Watch SE is now the bargain model at $249, or $299 with cellular. The Apple Watch Series 8 adds a temperature sensor, which can be good for a lot of things, but Apple emphasized its role in tracking ovulation for those trying to get pregnant. It also has added crash detection to the watch, so there's an improved gyroscope and accelerometer that with little machine learning can detect a car crash, and then it'll count down to 10 before automatically calling emergency services. It also has added international roaming support to the Series 8. Has 18 hours of battery life, 36 in low power mode. That's pretty similar to what it was before. And the price is $399 or $499 if you want the cellular connection. Both the Series 8 and the SE are available now, shipping September 16th. They announced another big new watch, and by big I mean literally the thing is huge, but before we get to that one, what do we think of the Series 8 and the SE? Any thoughts on these? Kind of upset that it doesn't look any different. I was looking for, I was bid into the rumors. I wanted to square it more of the edge, but the crash detection and some of the other features, it's still worth it for me. Yeah, same for me. I am holding on to a Series 5, but last week it stopped charging, so I was very much looking for it to when this was going to be available. I too was looking for a different design, which is why I was holding on to the 5. I was hoping maybe 6 and then 7 came and nothing, but now was the time for sure to upgrade for me. And I do have a little bit of question behind, particularly on the temperature sensor, the ovulation part of it. The data, they did mention that it is end-to-end encryption. A lot of women, I am a woman, but a lot of women are very aware of these type things now, particularly with the ruby-wade overturning of how protected is my data. They did say it was device-only. You can decide what to share and what not to share. And Apple is pretty good with security and privacy, but that particular thing still does have me a little bit on edge. That feature I probably won't be using, but I am definitely looking forward to the new watch. I was thinking that same thing during the event, Nika, because once they started getting into the ovulation stuff, I was like, oh, here we go, because we've had a lot of news over the last couple of months of people saying, well, hold on a second, who's got my data? Where is it going? And you have to assume that Apple leaned really hard into the privacy aspect of that, not that they wouldn't have anyway, but that was a big point of that part of the conversation. Yeah, just if anybody doesn't know, it's encrypted on the device, so it's encrypted from the get-go. It's only acceptable with a passcode or biometric ID, and if you do choose to sync it to iCloud, which you don't have to, it's encrypted end-to-end there as well. So I'm not sure what else they could do to protect it, but like you say, Nika, you still may be a little nervous about that, and that's understandable. I did really like that Hermes watch band. Not something I'm going to buy, but just looked cool, just looked really cool. I might be alone in the audience and wondering this or hoping for this, but I was really hoping for a sub $100 entry-level base functionality watch. I think that's when the market explodes. Not without bolts, guys. Not. I know. It's like hoping against hope. I get it, but I still want it on. But they're pushing kids and family, and $99 would be a very compelling price for kids and family, if they could ever make it happen. It'd be compelling to me. I also just, you know, the whole 18-hour battery life or low-power mode, which I don't use very often because I like to use so many other features besides kind of giving me the time and the weather. I don't know. I mean, I'm not getting 18 hours of battery life on my Series 7, and I charge it pretty religiously, but I don't know. Maybe some people don't use it as much as I do. All right. People are saying they wanted a better-looking or a newer-looking watch. We got one of those, right, Sarah? Yeah. We have a new Apple Watch model, everybody. It's the Apple Watch Ultra. And a 49-millimeter titanium case with 2,000-nits display has a bigger face. So if you were like, hey, love the Apple Watch, but I want it to be bigger and do more things, this may be the watch for you.  Apple heavily targets this for outdoorsy activities. If you watch the event, they showed people mountain climbing, swimming, scuba diving even, you know, all sorts of, you know, triathlon-type stuff. It can do two bands of GPS, L1 and L5. It offers WR100 water resistance. You can get it in one of three bands, and they made a big deal about the bands. There's the Canvas band, the titanium alpine, the elastometer, the titanium ocean, or all cloth trail bands, all designed to withstand the elements. Every model has cellular mode, and price is set at $799, available September 23rd.  I like a big, beefy, gnarly, garmin-sized watch. I do. I really do. Like, this is the most appealing form factor I've seen in a long time with smart watches of any ilk, in particular the Apple Watch. I always felt like the other ones were just not my, I don't know, not my style, but I like a big, chunky watch with orange markings and a gnarly wrap. The orange button is like, that's how you know.  And I did that thing where I almost convinced myself I would get it because I said, oh, this will be like $1,500. And they got to the end and said, all right, starting at $799. And I went, oh, maybe I can justify it even though why would I? Why would I ever do that? I was just asking for a $100 watch and suddenly I want this $800 watch. I feel like, I saw lots of, because I love to follow Twitter during Apple announcements, as we all do. And so much chatter about people saying, well, all I do is sit around and blog. I don't need this. And I think that the outdoorsy stuff, you're going to use some of those features or you're not going to. The capability, though, of the watch is pretty unparalleled. It's a nice watch. Yeah, well, I was going to say, unlike some of the other devices that Apple has, period, this is one of those devices, this Apple Watch Ultra, to where people can specifically, clearly say, I need this or I don't need it. Out of all the other devices, you can kind of, well, for me, I can talk myself into pretty much any device Apple sales with this one is kind of like, clearly, I'm not the target audience for this device. So I'm either not going to get it or I do all these things. All these things can come in handy or at least very one or two or three of these things come in handy. I need this watch. This has zero appeal to me. I don't do any of these activities. And it's very, it looks, they said it's for the Explorer. And it looks like it's for the Explorer. It's very rugged looking. It looks like if you're on a trail and you take a spill or you knock it up against something, it'll take the head and keep on moving because it does, it looks like it could, it could take a punch, so to speak. Yeah, it's a chunky little watch. Right. This is a competitor to Garmin. If you've never considered buying a top level Garmin watch for outdoorsy stuff, this is not for you. This, this is for, for somebody who likes to go diving, go hiking, climb mountains, be outside. In fact, Roger pointed out to me that it's, it's really good for people in emergency services. First responders, EMTs, firemen, Coast Guard. If you're going to be doing searches out in wild lands or fighting fires, that kind of stuff. This is, this is one of the most niche Apple products I think I may have ever seen. At the same time, I know at least a couple people who have, because I'm somewhat new to the Apple Watch ecosystem just a few months in now. People saying, you know, but I kind of got big risks. I would really like a bigger face. Listen, you know, $800 is not necessarily what you want to spend for the bigger Apple Watch face, but that is a part of it. And I think that will appeal to certain folks. No, that's a good point.  And I think for some people who want a big face on their watch, I should clarify, that could be worth it. You're right. I was expecting it to be much more in price. I was thinking $1,200, you know, at the least. I was surprised at the price. Yeah, the price. I think it's competitive in that market seeing what some of these garments go for. And I'm with Tom. It just seems like a fascinating aim to go after that particular, I would assume kind of niche market compared to like, you know, the main watch market, which is already a little niche when it comes to smart watches. So, I don't know that one, even though it was rumored, still came out of nowhere for me. We also got new AirPods Pro with a new H2 chip to improve active noise cancellation. There's a little bit of better driver to improve the audio. A new extra small ear tip, along with the other three you get. So, maybe it'll fit a little better in smaller ears. Apple added swipe controls to the stems. So, you have both swipe and force touch, depending on what you want to use. You can also now charge it with your Apple Watch and MagSafe chargers now. And the case has a speaker and U1 chip. So, you can find it if it's lost. Used to be, you can only find the buds. Now, you can find the case. It'll also use that speaker to do like low battery alerts or when it's fully charged, stuff like that. There's a lanyard loop on the side, if you want to secure it that way. $249 available September 9th, ship in September 23rd. I'm probably going to get this because I've been waiting for new AirPods Pro, but I was surprised that they don't look any different than the old ones. Same. I was definitely looking forward to some new AirPods Pros. I'm super excited about the extra small tip. If you see, a lot of times, you'll see me kind of pop the earbud back in because it's a bit big. So, I'm looking forward to that, but I am a bit surprised that it didn't get any sort of design change. I do like this speaker on the case because for people like me who lose things all the time, trying to find it, having it to be able to ping it and actually hear the case is definitely an upswing for me. No, I'm definitely interested in these as well. So much so that typically, most of the time, I'm reaching for my AirPods Pro. Now, I also have the larger AirPods Max. I don't know if you can see that behind me, but I very rarely use them. I only reach for them when I can't find my AirPods Pro. So, what I may end up doing is, especially since they mentioned the spatial audio and noise cancellation, cancels out more audio. That may be equivalent. I haven't done any sort of calculations whatsoever, but if that is somewhere close in the neighborhood of the isolation for my AirPods Max, I may just sell my AirPods Max and opt for these newer generation AirPods Pros. Yeah, this is a product category that I actually skipped when they first announced it. And part of the reason I did is it seemed like other manufacturers very quickly came to equal it with some offering of their own. And it was fast. It felt like just like everybody had something way cheaper that did basically, you know, point-for-point feature coverage that the AirPods Pro did. So, I just missed that one entirely. I am interested in this one because it does feel like a pretty big leap forward. The price didn't go up in some huge way. So, yeah, like, I think finally the, you know, the second generation, I usually don't wait. I wait at this time. This is a weird for me, but I'm excited to see these and hear them. Yeah, I don't use AirPods. I use Jabra's as my wireless earbuds. Same idea. I feel like a lot of what Apple touts, and you could even, I don't know, think of like HomePod announcements in the same category. They said, you know, best audio ever. And I think, you know, good audio is very important to me. It is. But a lot of the time, if I'm out and about using earbuds, I'm listening to podcasts. I'm sure you want the audio to be nice, but the spatial audio kind of stuff is sort of lost on me unless I'm really, you know, just going to sit down and listen to Pink Floyd for the next couple of hours.  But you have other options that are a lot cheaper. Apple also announced phones. Indeed they did, Tom. Star of the show. We were all waiting for it, even though the watch stuff went on for quite a bit this morning. The iPhone 14 is a 6.1 inch and the 14 plus is a 7, 6.7 inch version of the phone. So bigger than ever, everybody. Sticks with the A15 Bionic chip for both models. The camera's improved with the 12 megapixel main camera with the F 1.5 aperture. Front facing camera also has autofocus, which is actually kind of funny. I thought that it already did. Also has a larger aperture. So, you know, selfie lovers, you'll look better than ever. Something called the Photonic Engine uses deep learning so you can take better low light photos.  Video gets an image stabilization feature called Action Mode as well. The phone can handle crash detection, much like the new watches. The US version will only get eSIM versions. So you don't have a physical SIM tray. Some people out there were saying, yeah, I hated those. Other people saying, uh-uh, if I travel, I want that physical SIM tray. That eSIM thing is gonna lock us in more than ever. Kind of depends on how you live your life. Big reveal, though, with satellite connectivity for emergencies. So what you do is you point it at the right part of the sky. The phone is designed to help you do that within the app. You're not supposed to just know where satellites are above you. Then you can send short messages or answer pre-prepared emergency questions if you happen to be in a situation where you need to get a hold of somebody. It takes about 15 seconds to send a message in a clear sky or minutes if that sky is partially obstructed. Satellite support launches in November. It's free for two years if you go ahead and purchase one of these new phones. And Fitness Plus is coming to the iPhone. For those who don't have an Apple Watch, and I have some questions about that because I'm not always holding my phone when I'm doing fitness-y things. iPhone 14 starts at $799. 14 Plus starts at $899. Pre-orders start September 9th, shipping September 16th for the 14th and October 7th for the Plus. Yeah, it's that true-depth camera on the front that's getting the autofocus. I think that may be what's new there. I'm also curious on the Fitness Plus, does that mean I can just, if I own an Apple Watch and subscribe to Fitness Plus, you can do some stuff on the phone that's just watching, like stretching and stuff. Is that all this is? Why did it take until now to get that, if that's all it is? I'm curious about that too. My guess is there's probably also some tracking stuff you could do as well while holding the phone, like running or I don't know.  Like I need an Apple Watch. And I get why, if for example, I'm doing one of my VR workouts that can connect to the Watch, you know, you get my heart rate, calories burned, all sorts of stuff. If I'm not holding my phone while doing the same exercise, which I wouldn't. You'd be watching it on your Apple TV. But I have the phone strapped to you with a handy thing that you bought at the Apple Store for $12.99. Yeah. And maybe it's 6.7 inches. It's like having a small television attached to your head at this point. Yeah, I don't know. And one of the biggest things of Apple Fitness Plus is you get to see on the screen what's going on on your Watch. So it's very, how are you going to be able to track, you know, how many calories you're burning?  Let's not get too distracted at this though, because we got satellite connectivity, folks. Everybody wanted satellite connectivity. We finally got it. Yeah, that's what I thought was funny that Apple's like RCS messaging. Yeah, we're not going to connect to that, but satellites though. That's the key. I mean, no joke. This is good if you need it, right? If you're stuck in an area where you need to send an emergency message, it's a little kluge in that you have to hold your phones. You can't be in a situation where you can't use your arms, right? Because you're going to have to move it around to get it pointed at the satellite. It doesn't automatically connect. But if you need that message to go out, then you're going to want that. You're going to want the ability to do that. This is a very complex and I would imagine not cheap system for Apple to be a part of, and they're giving it to you for two years for free with purchase. So you notice they didn't tell you how much it was. Yeah, they didn't. They just said it was free for two years. Just enough for you to, you know, so much of this is like, it kind of felt like Apple was really leaning into like, your life is in danger. We're going to help you any way that we can. And we've built in lots of stuff that maybe you'll never need. Hopefully not. But if you do, we've got it. Yeah, we got you covered. I kid you not. I'm watching TV every night and there's always a news story. Somebody's rescued. They got to send the helicopter in. Yeah, well, there's your problem. You're watching the news. And the opening stories with the Apple Watch with the different people and the different scenarios. Oh, right. Where it came in. I was like, this is kind of drab to open it up. Right. It felt like if you use an Apple Watch, you're going to be in trouble, folks. You're going to have a heart attack. You'll be a car crash. The woman who said, yeah, we crashed our plane. Thank you. I was right in my watch. Before we get our thoughts on the iPhones in general, let's let's pick up on the iPhone 14 Pro and Pro Max. These are the ones with the 30% smaller notch that is now called Dynamic Island. And I for one love that name. I also love what they're doing with it. They're basically taking the notch and putting a little bit of a screen in the middle of it, right? So it's separated into two chunks and they're using that screen and the screen around it to center notifications that will animate in and out of it to make it look like a little notification dock. So it no longer looks like a problem in the screen. It looks intentional. The Pro and the Pro Max have a new chip unlike the other, the 14 and the plus. The Pro and the Pro Max have an A16 Bionic. They have a 48 megapixel camera with quad pixel sensors. It can use different sensor modes for different photos. So you can do things like 12 megapixel binned photos. So you can you can combine those pixels and capture more light. A lot of things you can do with 12 megapixel in this bigger sensor. It also has 2x zoom at a 48 meter focal length. Cinematic mode can now do 4k 30 frames per second and 4k 24 frames per second. The Pro is starting at $999. The Max starts at $1099. Storage up to a terabyte though it's going to be more expensive at a terabyte. You can pre-order this September 9th available September 13th. All right. So we got four new iPhones as usual. Who's buying one? Well, I skipped a year. So it's time. I've never done that before. I've always gone the year and do the payment thing and not just basically I rent my phone. So I've always done it.  I'm going to stick with this. It'll be fine. To be honest, outside that island and some photo stuff, it's not that different than last year's either. But the island is a big deal. It's kind of cool. Like what they're doing with it is very cool because you've got to have your physical holes and you've got to cover them up. So they're doing that and at the same time saying, look, instead of just having something covered, let's make it useful there. That space should be more than just a place to cover the places we need our cameras. And our mics or whatever. And so they do that. And I love it. And it's cool. But I also know that next year, the 15, the standard 15s will have it. And they're holding that back because it's a sales. Don't forget that 48 megapixel sensor. That's a big deal. It's a big deal. You're right. You're right. Although somebody who's never been a notch hater. I just it's just something I don't see. I don't care. But but if you do, this is genius. Oh, yeah. I saw some comparisons to, you know, the Mac line of touch bars that came and went and were beloved by some, but not many. Now, this is better than that. Now, it remains to be seen how how great this is going to be. But it seems like a dynamic island. I live on dynamic island now. As a person who loved as a person who actually loved the touch bar, I'm actually loving the dynamic island as well. I miss my scrubbing. I'll be honest, scrubbing through videos. That's the one thing. Anyway, I'm getting more into iPhone photography as well. So I'm definitely looking to step up my camera game. So this having the better cameras, this having that new feature with the dynamic island. I'm all in, even though I currently have the 13. So I'm going to move up a year and step up my game a little bit. And I'm in the same boat as Scott. I have the 12 pro and I didn't upgrade to the 13 because it didn't seem a big enough leap for me. So it's definitely time. I too am on dynamic island. I think the name is fantastic and the look and the feel is the same. I also caught, I don't know if you guys heard it. There was a little bit of a 16 chip shade to some of the other manufacturers. The mentioning that they are still, their competitors are still trying to mimic the performance of the 813. And it's like, yeah, we're on 16 and they're still trying to pick up what we're doing on the 13. I thought that was pretty funny. But I'm all in on the 14 pro as well. If you name one of the competitors and give me a chart that actually has like numbers to tell me what you're talking about, I'll take that shade a little more seriously. But they always say like 50% better than a competitor. But they're like, okay, but which competitor? Because if it's a low end one plus from 10 years ago, well, of course, you're going to have 50%. They don't want to give them that extra shine. It's like, no, we can't need to have competitors. I get it, I get it. Oh, and don't forget they always on screen. Yeah, Amos is pinging me in chat. They always on screen on this and still claiming 36 hour battery life, or still not 36 hours, but still claiming decent battery life. So that will be interesting to see what actually happens. The actual quotes again was always, what they say, all day battery life. That's right, all day. However long your day is. Yeah. You remind me, it's not like a Jupiter day, like an Earth day, we're okay. A Mercury day. Well, before we go, we want to check the mailbag real quick. We asked everybody yesterday about their upgrade cycle. What makes them upgrade? How often do they upgrade? So thanks to everybody. We got so many good emails from folks. We're just going to pick one to highlight for today. We might read more in the future, though. What do we got, Sarah Byron wrote in and said, I usually upgrade when the device is supported. It happened with my iPad gen one, iPad gen three. And next will be my iPhone 6S with the new Apple iPhones are released. Byron wrote this before today. I did have to upgrade to an iPad Pro 12.9 M1 when my iPad Pro 12.9 needed to be fixed. And I couldn't be without an iPad for too long. Byron says, I gave up on an expensive Android tablet since the manufacturers would barely support them for more than a year. The last one was an Amazon Fire tablet. I just use for testing now on the few apps that don't have an iOS version. All right. Well, folks, if you are free Thursday, September 8th, right before DTNS is live, 3pm Eastern time, I'm going to be on a free and publicly available panel with actual scientists to talk about how memory makes it harder to fight COVID-19. Talking about everything we've learned in contact tracing and all these things in the exposure notification system. They got one of the folks who worked on the Apple Google exposure notification system. And we're going to talk about all of that. The panel is part of the Association for Psychological Sciences Global Collaboration on COVID-19. So get the link from our show notes or head to psychologicalscience.org. And I will talk to you right before DTNS tomorrow, Thursday, September 8th, 3pm Eastern. Well, thanks to everybody for being on the show for the Apple announcement. It was a fun day, even if you don't like Apple stuff. It's just, you know, you got stuff to talk about. We'll start with you, Scott Johnson. Let folks know where they can keep up with your work. Well, if you're looking for podcasts that cover all sorts of stuff, including something a little ancillary to tech, which is gaming, which we talk about here occasionally when stories come up, you might like something over at the Frogpants Network. Check us out at frogpants.com. Check out all the podcasts. Find something right for you. That's frogpants.com. And I'm Scott Johnson on Twitter, if you want to find me personally. Excellent. Well, one half of the Snob OS podcast loves Apple stuff. Terrence Gaines, let folks know where they can keep up with your work. Definitely, they can find me and my other half, Nika, on the Snob OScast. Go to www.snoboscast.com. We record on Thursdays. We, episodes come out on Fridays. There you'll get more in-depth of the Apple announcements. You know, we love coming on DTNS, but we got to get in there and get our zings in there quick. But if you want to listen to an extended version and get all the info information, all the insights, all of the recap, definitely check us out there. Well, speaking of the other half of Snob OS, Nika Monford, always good to have you on the show as well. Let folks know where they can keep up with you. Absolutely. As Terrence mentioned, you can definitely check us out on the website and to hit us up on Snob OScast on Twitter. You can find me personally over on Twitter at TechSavvyDiva. Well, we have a brand new boss to thank, Robert. Robert doesn't know if you were watching the Apple announcement today, but you just started backing us on Patreon, so we want to give you a big ol' round of applause. Yeah, Robert. Robert brought you the Apple coverage today, right? That's how well-timed Robert was. Well done, Robert. Thank you for that. Robert couldn't do without you. We couldn't do without any of our patrons. Speaking of patrons, stick around for our extended show, Good Day Internet. We'll be talking in more detail about how we feel about Apple announcements in general and what we'd like and don't like and what we might buy. But just a reminder, DTNS is live. You can catch the show live Monday through Friday at 4 p.m. Eastern, 200 UTC. If you'd like to join us live, we'd love to have you more information at DailyTechNewShow.com slash live. Back to it all again tomorrow. But just from Robert Young joining us, talk to you then. This show is part of the Frog Pants Network. Get more at frogpants.com. Diamond Club hopes you have enjoyed this program.


Hi, I'm Amanda and I'm 38 years old and I am a heart warrior I like to call myself heart hero. I had aortic stenosis. It was congenital so I was born with it They didn't really discover it until I was I think around 15 months old So from the time that I was 15 months old until now I was in a cardiologist's office once a year I would always have a line of medical students lined up to listen to my classic aortic stenosis And aortic stenosis is where you have a bicuspid valve instead of a tricuspid valve And it was something that they just monitored when I was younger and they weren't quite sure where it was going to Take me later on in life. They told my parents that I might not be able to have children Playing competitive sports or being really active would probably be out of the question So every year that we would go to my checkups after the long line of the medical students would line up to listen to me We would wonder okay, what is the report going to be? Is it going to be time to Replace this valve Do I have a little bit more time before I'm going to have to do that? What's going to be the deal so? Flash forward to when I turn 30 I found a high-risk OBGYN went and visited her and She said I think you're gonna be okay to have children Go right ahead so and I should mention too In college I was a cheerleader So I lettered in college and I also taught aerobics and I taught Zumba so I think with Me growing technology also grew and that's what helped realize. Okay, you can teach aerobics You can cheer you can have children So the funding and the awareness that was raised along with me growing up I'm really thankful for because that was able to buy me some time and able to help me have a child and To cheer in college. So I had my first child a son back in 2012. Everything was great He turned a year old and I went in for my annual visit and my cardiologist said, how are you feeling being an oh goodness Should I be feeling any differently because I feel fine. He said well your echo is showing that your aerox stenosis is very severe and You're probably gonna need surgery Very very soon.  I was petrified They were able to do a heart cath on me That was my very first time having a heart cath and I was so scared to do it But I'm so glad that I did Because it was able to show that it wasn't nearly as severe as they thought and I had a little bit more time And they said if you want to have one more child because I felt like that was just in the cards for me To have one more Go ahead sooner rather than later. I need to go ahead so By the grace of God, I was able to have a daughter in 2015 and When she was three I started to feel extremely tired and I just thought huh it's just because I have at this Three year old and this five year old and I'm running after them constantly and they have a crazy schedule So I went in and saw my general practitioner and she said let's go ahead and do an echo because it's been almost two years Since you had one and she did the echo and she said I Think it's gonna be time to do this. So then I'm like, oh great now I have two children and my husband and I just don't know if I can Do this but I went in and I met who was Divinely my surgeon Dr. Bolomonakos and his whole team I Walked in and I just felt okay. I feel like I can actually go through With this I feel a sense of peace and I feel a sense of comfort Let's please do this but I went in And I went in at seven o'clock that morning and I didn't get done until seven o'clock that night But here I am and I have a beautiful new accessory That I didn't know if I was gonna be able to embrace I remember telling my husband right before they wheeled me back that my chest was never ever gonna look the same Again, and I wasn't quite sure how it feel about that There was a nurse who was in the hospital during my recovery and she said whenever you're ready to look at your scar It is beautiful and it's not gonna define who you are Someone who might feel like they're really alone in the situation I would say please talk about it when I was younger and even into My early and mid-20s I never wanted to talk about it because I felt like a freaking nature and I felt like I was a science experiment But I found the more that I've talked about it The more I realized so many people have it in common with me And that was how I found my cardiologist who I have right now and that's how I found my surgeon So just please don't feel like you're alone. The more that you talk about it the more you're gonna realize how normal it truly is and You're gonna find your support system and your support team who will help you get through. I Just want to share that if I can do it you can do it We are women and there's so many things that We do and so many hats that we try to wear and it is okay to Ask for help and it is okay to say I need to take a break and go check on myself because heart disease is the number one killer of women and I just want us all to band together and wear our red and look out for one another and just really Take charge of everything that you can and don't be afraid to talk about it Join us on Friday February 7th for the Go Red Columbia press conference and day party at the Charles R. Drew Wellness Center from 12 to 2 p.m. Registration is open and free at GoRedColumbia2020.eventbright.com


It evolved from those conflicts to probably the biggest and longest lasting labor management partnership for sure in the country if not in the world. The Kaiser partnership is I think a shining example and the best example of how you bring labor management together to produce results that truly is something we can learn from and replicate. We co-lead the team, we co-lead the pharmacy and I'm a co-lead for the clerks out front and then Bowell is a co-lead that runs the whole pharmacy. It's not my voice over hers or hers or mine, it's together. It makes everything better because we have that partnership. I know that if there's things that I may have missed then she'll cover me or vice-versa. Kaiser Permanente works with 28 different unions to provide good pay and benefits but also educational programs and avenues for employees to help improve quality and care throughout the company which is why they're considered one of the premier health organizations in the country. The labor management partnership is the relationship or structure where we all work together. You have a forum or a place to go to say let's talk about that, let's hash it out, let's get other people's perspective on it. What better place than to go to the people that are actually delivering the care before you get into the room? You know, the person that roamed the patient, the person in the lab, the person who gives the free blood pressure checks. The people that are doing the work get a chance to say we can do it better, we can do it better, here's how. You know, it's nice if we all get along but most importantly we're here to get the results. What I love about this model is the notion that no matter where you're working in the system that you have a place at the table and that your voice is heard, you're respected and through your union is how you're provided access to make the company better and the care experience better.


OK, that's pretty bright. Should we start? OK, so let's start. Hello, everyone. Thanks for coming so late. I was expecting even less people. It's nice to see you. We'll talk to you about container clusters on OpenStack with OpenStack Magnum. I'm Spiros Trigazis. I'm Felon, Felon Wa. And Felon is also a core reviewer of Magnum. Yes, so I'm the PTL of Magnum for the past three releases, like past two and the current one. I'm also a computer engineer at CERN, and a member of the Cloud team. And Felon is a recent addition to the core reviewer's Magnum group. So this presentation initially will be about Magnum generally. And then we will discuss briefly some issues that we had when deploying Magnum production. And at the end, we'll have a demo each, one from the CERN Cloud, one from the Catalyst Cloud. So what is Magnum? Some of you might not know. Magnum is an OpenStack API service. It means that it offers just a simple API that we offer to users. And they can create container clusters with one click.  It means that all compute nodes that are hosting the cluster and running Docker, Swarm, or Kubernetes, or Mesos, they're owned by the same tenant. So the isolation is ensured either by virtual machines or difficult physical hosts. The added value of Magnum is managing credentials for the clusters so that users can access them remotely from the APIs that the container engines are offering. Since this is an OpenStack project, a very important aspect of it is the integration with other OpenStack services. Kubernetes has the Cloud provider that I will explain later. And most people in the OpenStack world know about. And there are also other components, like RexRay, for example, which is to manage sender volumes with Docker directly and using maybe Docker Swarm or just the Docker daemon. The main focus of Magnum is lifecycle operations of the clusters. So we don't interact directly with the API. The interaction with the API is done by the end users, which run their applications on the clusters. And we just create them, delete them, scale up, down. We monitor the health. And we try to also implement upgrades and more advanced features like having clusters in different availability zones and manage the lifecycle of the operations of the parts of the clusters in different availability zones separately. Before going to the cluster template, a term that we have in Magnum is container registration engine, COE, which is also the identifier noun in the OpenStack client. So if you use the common client of OpenStack to talk to Magnum, you must specify COE. And COE stands for container registration engine. And in Magnum, that means Kubernetes, Docker Swarm, Mesos, or DCS. Some terminology of the Magnum service, we have the cluster templates and the clusters, which are the main components, the main objects in the service. The cluster template is basically just an entry in the database that describes the different configuration parameters that users can pass to clusters. For example, specify flavors, specify the image with the operating system that is going to be used to deploy on the compute nodes. Options like volume drivers, network drivers, Docker storage drivers, flavors, and other gate features that we add as labels. And then they graduate as normal fields. Then there is the cluster. A cluster is created by a cluster template and inherits all the options. Plus you can pass some extra ones that we will describe later. So the cluster has a number of master nodes, worker nodes. And in the OpenStack, like in the OpenStack Cloud, this is represented by HeatStack. So all the orchestration is managed by Heat. It's delegated directly from Magnum. And in the HeatStack, they contain lot balancers, private networks, and virtual machines, or volumes. Each cluster, to integrate with OpenStack, the clusters need to talk to the OpenStack APIs to solve this and not expose the user credentials inside the nodes, where maybe the nodes get hacked. Or in any case, they must not put their OpenStack credentials anywhere. It would delegate the powers of the user with a trust user, with a trust user. The trust user, it's a made up user in the Magnum domain. And the trust for this user, it's actually giving to that trust user all the capabilities that the normal user has for that project. Then to talk to the API, we have a certificate authority, which is stored either in Barbican for the more secure solution, or the Magnum database, where Magnum can also accept the certificate requests so that after the user has retrieved the certificate, he or she can also talk to the API of the Container Orchestration Engine securely with TLS. The main orchestrator, as I mentioned, is Dr. Kubernetes Swarm, or Mesos, slash DCS. DCS is just an API over Mesos, but by far the most popular one is Kubernetes. We try to support different operating systems, but the most prevalent is Fedoratomic. Personally, because we use it to turn, and since we validate it, and we use it heavily, other users also use the same one. Other clouds use the same one to have, for us, as a community, to track issues together and find the same bugs and not just spread bugs across districts. We also have implementations for CoreOS, and for DCS and Mesos, we use Ubuntu or CentOS. Apart from spawning clusters in VMs, which is the standard way, for example, to do it in Google Container Engine, with Magnum, users can also deploy clusters in physical machines with Ironic. Actually, Magnum doesn't know anything about Ironic because it interacts with a Nova API. So if the cloud offers physical machines with Nova, with the Ironic driver, this is transparent to the user, and the only difference is specifying a different flavor, which corresponds to a physical machine. The first operations, as I mentioned here, is the last bullet, is a cluster scaling, which scales clusters up or down. So features of Magnum, I mentioned already that Magnum's added value is managing the credentials. So each COE, for example, the Docker swarm, it's a combination of many Docker engines, and the Docker engine exposes an HTTP API. This API, we protect it with TLS, which is where we use a self-signed certificate authority. And similarly, Kubernetes has its own API server, which we protect with the same mechanism, and we just distribute the certificates across all nodes. Actually, the nodes are those that talk to Magnum to retrieve the certificate, instead of just passing in user data or in any other way, sensitive data as the certificate key. Other features include the providing multi-master clusters to have HA. At the moment, we don't have a very clean way to support the HA across availability zones, but with recent patches from a catalyst, users can specify the affinity between the nodes so they can achieve... If the cloud is configured in such a way, they can achieve availability using affinity between the nodes. There is work in progress to support this more explicitly by the user. Recently, we started Simplify Clutter Creation by allowing the user to pass the flavors and the Docker volume size, which is the block storage volume where when a container or an image is retrieved in the nodes, it's stored inside. So since those fields are describing the size of the cluster, we decided to make them fields of the cluster object instead of the cluster template, and as you can see in the bottom right corner, you can just create a cluster with one command that specifies the size of the cluster that you need. So how does a cluster look like? In standard Magnum deployment, the most minimal cluster template and the smallest cluster creation that a user can issue will have this result. Some worker nodes, it doesn't make sense to have only one, you should have more, but you can start with only one master, and all these nodes will be in a tenant network, so this probably is backed by an SDN deployment of the cloud, and then all nodes will have a floating IP. This is the default as the project started, and the most standard way to expose applications inside those clusters is to expose the application from on the host board directly, but this is not optimal. The full feature set of a cluster looks like this, and then I will move to the optimal options. This again has a public network where all nodes get floating IPs, and also private network, which is used for inter-node communication, and it has also a lot balancers for ETCD in case of Kubernetes, or the API for all cases, like in Dockershaw or Mesos, you just have an Octavia or Neutron load balancer in front of it. And also for extra storage in some clouds, VMs get a very small disk, and containers at the same time can be very big, container images, or many containers can be created with many different images, so we attach a volume in each node to extend the storage, which is available for Docker or other container runtimes to store the images. This is the most minimalist-laded cluster that someone can create. Actually, we're very proud of it because although it happened almost by accident by designing the smallest possible cluster, it was one of the latest editions of the Google Kubernetes Engine, which is all nodes to be only in a private network, which is completely isolated. For example, if someone wants to do some number crunching inside the cluster, it doesn't want to expose a service. And actually in public clouds, this is very useful because it means that you will pay less since you don't burn floating IPs and you don't, if you don't need them. This is the optimal configuration for with a single master in a cluster, which means that the compute nodes, like the workers, are in a private network isolated. The master is on the private network also to achieve communication between workers and masters and only the master node has a floating IP. And then when a user runs an application inside the cluster, he or she can create a service in Kubernetes with type load balancer. And OpenStack will create a load balancer with Octavia, give a floating IP to the public network and also create listeners in the private network. So this is the most isolated option because from the internet only with the port exposed for the service users, attackers and even users can talk to the cluster. And this is the last variation which is for like a production application should run like with at least three masters for the control plane of Kubernetes or Docker. An API in front of it, the master's, the worker nodes should be isolated in the private network and all services should be exposed as with a Kubernetes service type of load balancer which will be exposed to the internet. I will hand it to Feiland now to talk about some features in Kubernetes and what we work on. So until Rocky, now there are some features that we would like to highlight. The first one is the Calico support. So currently when user creates the cluster template, user can specify using either Flano or Calico as the network driver. So with Calico, you can get the network policy support in Kubernetes cluster. And we also support the autoscaler for core DNS that means as before, yeah, we just hard code only one port for code DNS. But for now, when you scale your Kubernetes cluster, the autoscaler can help scale your code DNS port as long as we decide it's a cluster to make sure you won't lose the service discovery. And currently we also support a low-based access control for your Kubernetes cluster and the Kubernetes dashboard. And we also support the hipster and influx DB and Grafana, but it's not enabled by default. You have to enable it with the label. And CERN also adds support for traffic ingress controller. And actually, user can also use the Octavia ingress controller, but it hasn't been fully integrated in Magnum, but there is Octavia ingress controller already. And for Kubernetes version, for Queens, Magnum supports v1.9, and for low-key, we support v1.11.x, and actually, we also support v1.12, but it's not default. We probably put it into a stain, the stain release. And for usage, user can either use command line to create your cluster or access the cluster with Qt control. And the dashboard is also righted by default when you create the cluster, it's enabled by default. And here is a list for the work we would like to do in Stain and mostly is undergoing, just need some polish and more review. So for rolling upgrade, generally the patch is in good shape and we are just doing some testing and code review. It should be merged into this release in Stain. And auto healing. For auto healing, we are changing the design, but it should be in Stain as well. For node groups, we are also auto healing. For auto healing, currently there is no patch just in design stage. For node groups, we also help patch Friday for code review and it's also in good shape. The next one is the Kubernetes Kstone house integration. So with that feature, a user can use the role already created in Kstone and reuse the same role for your user to do the house and also in your Kubernetes cluster. So you can see the same feature from GKE, some typical role like the cluster administrator and cluster developer cluster, we were something like that. And we would like also support premises operator and the logging solution. Currently, the design is using IVEK, FluentD, LactiSearch, and Kibana. And another work is we would like to add the heat container agent for all worker nodes so that we can improve the performance for bootstrap the whole cluster, Kubernetes cluster. And we would like to add more straight security rules for worker nodes. Currently, we are probably opening all the posts for worker nodes. In Catalyst, we have got some feedback from our user to complain that. But yeah, it should be changed in stand release. And we are also working on the self-hosted Flannel, that means just put Flannel support as a particle, as running on top of the Kubernetes cluster and deploy a Taylor. And another work we would like to do is release all the Kubernetes Docker image in CI automatically. Currently, we have to manually build all the Kubernetes cluster image and release on Docker Hub. So here are some experiments. I have mentioned that in the talk on Tuesday in the journey in Catalyst to deploy Magnum in our cloud. So the first one is at least for Kubernetes, we want .11. Don't use the overlay or overlay to add the storage driver combined with Docker volume size. For that one, sometimes if you are using both, so sometimes you will see like you can't create any port, any container on the worker nodes. I don't know the reasons now, but that's the solution. If you are using overlay or overlay tool, just leave the Docker volume size parameter empty. And that means for that case, your Docker, the Docker running on the worker node will share the same root disk with the operating system. That means you may need a large flavor for your worker nodes. And another one is the heat container agent multiridance bug. That is embarrassing bug, I think. We fix it in different components related to heat. So if you're running Magnum with, I think, before heat queens, you will run into this bug. You can't deploy a cluster successfully for multi-region environments, because for that case, the heat container agent will try to talk with another wrong heat in different regions. For example, you were running great cluster in region A, and the heat container agent may try to talk to the heat in region B, and it will get a 404 error. See, I can't find the stack, so I just fail. So that means as long as you have multi-region, you'll probably run into this problem. And there is another bug in Kubernetes is in V1.11. There is a bug sometimes randomly Kubernetes, the cobalt will loosing the internal IP and the external IP for whatever reasons. The bug has been fixed in V1.12 and has been charged peak to V1.11 and could be released in V1.11.5, but it's still under review and seems the reviewer don't think it's a critical bug, but actually it's a critical bug. So yeah, that triggers another topic is for some case, you probably need to build your own Kubernetes image. Though yeah, as a public cloud, even a private cloud you want to avoid to do that, but just in case. So that's the experience we have got based on the feedback from our customer and when we run the OpenStack Magnum in our cloud. Yeah, do you want to cover the? So some of the issues that we identified in running Magnum at CERN were mostly coming from the networking part, I would say. The first one was, since this years, we had to reboot the whole cloud two times, and one for Spectre Mildan and one for L1TF, and that means rebooting the hypervisors and also the VMs that were running the Kubernetes clusters which revealed a couple of configuration issues that we had with Flannel. But by default, the configuration of Flannel is to accept all forwarded requests with IP tables, but when we're restarting it, all the routes were un-setting and this was causing in some nodes to lose connectivity for inter-pod communication. So pods in different nodes could not communicate with each other. In the CERN cloud, we don't run the cloud provider because we have some restrictions from the networking infrastructure and we cannot provide a lot balancing as a service. We have other means to provide a lot balancing. I'll say it opens back. And at the same time, we have different storage solutions that we offer to users in the cylinder. But the most critical issue for us was that creating clusters with a cloud provider enabled that mean in every 10 seconds, the controller manager of the Kubernetes clusters would have to talk to Nova Neutron and check the status of the VM and the ports that the VM had and the IPs. And if any of these calls would fail, it would start doing the request every five seconds. So in case that you had, for example, a cluster with 100 nodes and let's say 30 nodes were down, you had different requests happening every five seconds just to verify if this node is up. This node might be down because it was overloaded or even the user stopped it because he wanted to change something or debug something. And this would create like 40% of the load on the open stack APIs. This way, this reason we decided to disable it. Another issue that we had was we were seeing a lot of clusters being created and we were seeing a lot of activity in the Magnum database, but we could not identify what's the actual status of the cluster. That's why upstream we are introducing a centralized monitoring. And before that, CERNU had implemented the wrong solution that was creating all APIs to verify the status of all nodes. So if you're an operator, you might want to monitor what's the actual status, not only if the VMs are up and running. The biggest issue that we had when we started to reach some critical months and some in the usage of the project was configuring correctly the heat service. As I said, the heat service creates all the VMs, but not only the VMs, it passes all the configuration and applies all the configuration in the nodes. And each container cluster node has a heat agent inside that pulls the heat API to ask for if there is something available to apply on the node. So that means we needed to scale at least to four times eight 32 core deployment across four VMs in all our availability zones and bump the RAM of the VMs to 16 gigabytes. But the most tricky part to configure was, we had some issues, one heat was trying to connect to the database instance that was explicitly set up for heat. It was configured to accept 1,000 concurrent connections, but when there was a high activity, let's say around 10 o'clock in the morning that people are in their offices and they start doing some work or even earlier, they started to hit the DB very hard and the heat engine was actually timing out because it couldn't get any connection from the database. I will have posted the configuration instructions in the mailing list and that in our documentation for this. Another issue that we had was that some users wanted the latest and greatest feature of Kubernetes. So they wanted the latest stable or sometimes better release, but others were more conservative and wanted to run in a more validated configuration their services. So we started investing a lot of development time to be able to select exactly which Kubernetes version we want to run in the cluster and I will have this configurable by running all Kubernetes components as containers. And to simplify our lives as operators, we started using only the stock images provided by the Fedora and Ubuntu projects so we don't have to have our own CI to build operating systems and actually releasing operating systems. That was from our experience running Magnum for a couple of years now, actually two and a half and I will show you some demo to prove that this actually works. Okay, sorry. I just rebooted and lost my GitHub. I'll do this one more time. So earlier this morning, I created a cluster with 16 nodes and now I will create one more as to make it, to have it building as a demo what's working and what doesn't in my existing one. Okay, the cluster is building and you can see here that it's in progress and as I said before, each cluster is a stack so you can see also the stacks that are in progress. I show my colleagues clusters. Now the most important part that I mentioned before was that you can retrieve the cluster configuration which is the TLS certificates to talk to the cluster securely. So this is done by a single command. I'm passing force because I retrieved the certificates before and now with minus, minus force, it will override them and if I export my code config, I will be able to talk to the Kubernetes cluster now. I can do version first so you can see here that the server is running 112 and the client that they have locally in my machine, actually it's in my VM, it's 110 and if I list the pods, I won't have any pods in the default namespace but if we move to Kub system so the work that we do in Magnum to deploy components you will see many more. So this is the internal DNS of the cluster so you can have a resolution of services, DNS name resolution based on names of the services that you create. This is the hipster component, the dashboard and all these pods that you can see here is the CSI plugins for CFFS that was demoed yesterday by my colleagues but also CDMFS which is a dedicated storage that we have at CERN. Also these are at the bottom, the Grafana and inflex to be containers. So what I can do also is I can run one and now I have a deployment. Also what we can check is the ingress controller that we have which is in Kub system. It's this ingress traffic but we don't have any pods of this because it has dedicated the node selector which is the whole ingress. So to start using ingress we need to label some of our nodes. So if I show my nodes I can label one with this label and now if I list in Kub system my pods we can see that I have a traffic pod and if we also list the services we can see that ingress is exposed with node port which means that if we create ingresses for the service that we run in the cluster we can talk to them in those node ports using the ingress traffic controller. I think I exceeded my time. I should dedicate more time for the demo. Do you want to do a demo of your cloud now? So this is the dashboard of Catalyst Cloud and currently because we are using Horizon Pack and there is a conflicts between Horizon Pack and the latest version of Magram UI. So we can't use Magram UI Rocky release. We have to use Magram UI pack. So it's not really the latest version but just give you guys an idea how this looks like. And we have got some feedback from our customer about the dashboard is they don't want to get too much options when creates cluster but they don't want to see much information about the template and the cluster. For example, when click the cluster they would like to see as much as possible information from the cluster but we are running an old version. So there are some information missing on this dashboard. And generally for create a cluster in our cloud as we mentioned in our Tuesday session currently in Catalyst Cloud we are using the image from Docker Hub and we are based in New Zealand. So when pre-image and the request has to go out of New Zealand and then back. So it takes longer time. Generally for one cluster it takes around 15 minutes but insurance environment takes about I think 10 minutes. Yeah, so that's the idea. I want to show to create another cluster because it takes long but just show you the dashboard. I think that's it. I think that's it, we don't have anything else. So thank you for your time and I think we have some time for questions. To use what? Contrailer. Yes, we are deploying and evaluating Contrailer and we start also looking at the CNI plug-in of Contrailer to have a big unified networking plane between physical machines, VMs and containers. So we are evaluating it. Most services are in Rocky. Actually Magnum that I'm the PTL is not in Rocky but apart from Magnum, Barbican and Chit everything else is in Rocky. The rest of it is in Queens. So it's Queens and Rocky. What was your... In Catalysts we are using Magnum and Rocky and Chit Queens because the multi-region for all the adversaries. Okay, so thank you. Thank you.


This is just a little shout out to the parents and carers of children and young people who are Struggling with or anxious about the return to school or college this week And I hear you and with you and walking that journey alongside you I've created a whole bunch of resources which hopefully are helpful to you and your child But actually today the message is just you're not alone We can often feel really alone in this and that we're the only one walking this and everyone else is Managing and that child is skipping into school, but believe you me There's a whole army of us who are facing these challenges So you're not alone if you are a parent or carer who is in this situation Pop a comment or a like just so that we can be together in this Good luck. It's gonna be alright together. We're gonna make it through


Best greetings of the time to all of you. I am Mr. Shashikant B. Gosavi, Assistant Professor, Department of Civil Engineering, Valtran Institute of Technology. Today I am presenting the online educational resource on production rate of earth moving equipment. The learning outcomes of this online educational resource are at the end of this session the learners will be able to analyze the production rate of earth moving equipment. The second learning outcome is calculate the learner will be able to calculate the productivity rate for completing the work of earth moving equipment. You can see the picture and feel how complex are the activities happening on to the site. You can see the time printed at the bottom over there at 7.22 am the work starts and then at 7.47 am the activities start rolling in with proper daylight. It will be almost on the flag end of completion by around 4.58 pm and then the work will be winded up. In many cases along with this you will also have the diesel energy systems to help you to work even in the dark hours. You can see that there are plenty of equipment, there is a excavator which is working, there is a loader, there are several workers which are working on to the site, there are dozers which are spreading the respective material, there are dump trucks and then there are several activities which are happening all over the place. The analysis of the production rate is the aim of this OER and the operational analysis of selected type of equipment is at most essential. There are 7 major activities of earth work which will be considered like clearing and grubbing which is always the first activity followed by excavating. Then there will be loading of the material which is excavated, there will be hauling transportation of the material from the work site to dump site and vice versa. There will be backfilling in some of the cases, there will be grading in some of the cases and in some of the cases there will be a need of the compaction also and therefore lot of many equipments will also be coming into the picture. The productivity rate comprises of following main steps like data collection for any site when you are moving ahead for the analysis of the production rate, you need to know very well the site topography, you need to know the soil characteristics that the respective earth moving equipment is going to handle and you need to have clear idea about which equipments are being employed on to the site. The numerical analysis of earth moving operations such as travel distance particularly for the hauling, rolling resistance to the respective manoeuvring system it may be on the wheels or it may be on some other base and most importantly you need to have the idea of cycle time. Further we need to determine productivity rates based on the user input parameters. In order to conduct the analysis the user input consists of following database. Equipment type is one important thing the capacity of that particular equipment is required to be known well in advance several specifications are known to are supposed to be known site topography and the topographical features is another important thing which the analyst has to give the consideration to and the material characteristic is very very important particularly in regard to fragmentation and moisture content and cohesion, adhesion and so many things. The equipment productivity rate are calculated based on soil characteristics site topography and volume of earth moving. While satisfying these particular equipment constraints such as rolling resistance, maximum rim pull and horsepower capacities these are important to be considered when you proceed further for the productivity rate analysis. The operational analysis of the equipment has two constraints as we have spoken earlier the first constraint is defined as the loaded weight. The loaded weight must not exceed the maximum allowable weight set by the manufacturer. In addition to that this constraint of loaded weight is expressed by using LW which should be less than or equal to RW where LW is the loaded weight and RW is the rated weight. The rated weight is normally in the equipment manufacturers information. The second constraint is defined as the total resistance. The total resistance must not exceed the allowable rim pull or drawbar if the equipment is wheel mounted or crawler mounted respectively. Rim pull is particularly applicable for the wheel mounted and drawbar are corresponding to the crawler mounted and therefore TR has to be less than RP and TR has to be less than DB is another constraint where TR is the total resistance. RP is allowable rim pull for the wheels or if it is the crawler mounted then DB is the allowable drawbar. The operational parameters are categorized into four main groups. The first one of that is spatial relationship which includes several parameters like topography, obstruction in earth excavation, clearance heights, required heights, required reach manoeuvrability and location of hauling units. The second parameter is soil characteristics like rolling and grade resistance which provides traction and soil stability. Potential changes in the characteristics during performance of the work, required force to loosen material, need for ripping and pushing attachments and abrasiveness and other rough earth qualities such as rock material that may cause problems in equipment. The third parameter is contract provisions. Quality of the earth involved as well as quantity of earth involved are equally important. Time constraints and weather conditions are required. Requirement for payment and subsequent cash flows is another important factor. Legal constraints on the weight and size of equipment is something which is required to be known to us. Other restrictions such as traffic, hours, dust and noise also influence the operational parameters. The last one is the logistical considerations. It involves availability of required equipment and operator mobilizing and demobilizing time, use of equipment in preceding operations and ideal time, economical equipment cost and support facilities. If we will go for the calculation of the productivity rates, these are determined based on equipment specifications, data and specific parameters related to location. Productity rate is equal to volume multiplied by operational efficiency divided by cycle time, very simple formula where volume is actually required amount of earth moving operations which is in cubic meters, operational efficiency is minute per hour and cycle time. The time needed to complete an earth moving operation which is the total of fixed and variable time and includes the time needed for completing one cycle while being empty and loaded depending on the type of equipment. Please pause the video for a while and answer following question. What will be the unit of productivity rate? Just in the previous slide we have seen the formula. In the formula there were some datas, each of them were supposed to have some units and you are supposed to answer this question. See the productivity rate is actually based on volume, operational efficiency and cycle time in the relation as has been shown over here. Volume is in cubic meter, which is in numerator here, operating efficiency is minute per hour and cycle time is in hour. So if we will put the unit of volume operational efficiency and cycle time, you can easily understand that unit of productivity rate will be cubic meter per hour. I have used this Nizar Marquis and Ahmad Grade and integrated expert system for linear scheduling heavy earth moving operation as a reference which comes from Journal of Construction Engineering, Volume 2016, article 2312057. Thank you very much.


Hello, everybody, John Walls here. Welcome to theCUBE and our continuing coverage of AnsibleFest 2021. We now welcome onto theCUBE three representatives from Red Hat. Joining us is Ashash Badani, who's the senior vice president of products at Red Hat. Ashash, thank you for joining us today. Thanks for having me, John. You bet. Also with us is Stephanie Shiras, who is the senior vice president of the platforms business group. Also at Red Hat and Stephanie, how are you doing? Oh, good thanks. It's great to be here with you, John. Excellent, thanks for joining us. And last but certainly not least, Joe Fitzgerald, who is the vice president and general manager of the Ansible Business Unit at Red Hat. And Joe, good to see you today. Thanks for being with us. Good to see you again, John. Thanks for having us. It's like the big three at Red Hat. I'm looking forward to this. Stephanie, let's just jump in with you and let's talk about what's going on in terms of automation in the hybrid cloud environment these days. A lot of people making that push, making their way in that direction. Everybody trying to drive more value out of the hybrid cloud environment. How is automation making that happen? How's it making it work? Yeah, we have been focused at Red Hat for a number of years now on the value of open hybrid cloud. We really believe in the value of being able to give your applications flexibility to use the best technology, where you want it, how you need it, and pulling all of that together. But core to that value proposition is making sure that it is consistent, it is secure, and it is able to scale. And that's really where automation has become a core space. So as we continue to work our portfolio and our ecosystems and our partnerships to make sure that that open hybrid cloud has accessibility to everything that's new and relevant in this changing market we're in, the automation space that Ansible drives is really about making sure that it can be done in a way that is predictable. And that is really essential as you start to move your workloads around and start to leverage the diversity that an open hybrid cloud can deliver. You know, when you're bringing this to a client, and Joe, perhaps you can weigh in on this as well. I would assume that as you're talking about automation, there's probably a lot of successful head nodding this way, but also some kind of this way too. There's a little bit of fear, right? And maybe just they have these legacy systems, there's maybe a little distrust, I don't wanna give away control, all these things. So how do you all answer those kinds of concerns when you're talking to the client about this great value that you can drive, but you gotta get them there, right? You have to bring them along a bit. It's a great question, John. And look, everybody wants to get the hybrid cloud, as Stephanie mentioned, that journey is a little complicated. And if you had silos and challenges before you went to a hybrid cloud, you're gonna have more when you got there. We work with a lot of customers. And what we see is this sort of shift from, I would call it low level task automation to much more of a strategic focus on automation. But there's also the psychology of automation. One of the analysts recently did some research on that. And you know, imagine just getting in your car and letting the car drive you down the street to work. People are still not quite comfortable with that level of automation. They sort of want to be able to trust, but verify and maybe have their hands near the wheel. You couldn't take the wheel away from them. We see the same thing with automation. They need automation, they want automation, but they need to be able to verify what it is doing, what it did do, what it's going to do. And once they build that confidence, then they tend to do it at scale. And we're working with a lot of customers in that area. Joe, you're talking about a self-driving car. That'll never work, right? I mean, you know, it brings an interesting point though. I, you know, again, I get about kind of surrendering control a little bit in a shesh, I would assume in the product development world, that's very much your focus, right? You're looking for products that people not only can use, but they're also comfortable with that they can accept and they can integrate. And there's buy-in not only on the engineering level, but also on the executive level. So maybe walk us through that product development, staging or phases, however you want to put it, that you go through in terms of developing products that you think people not only need, but they'll also accept. I think that's absolutely right. You know, I think both Stephanie and Joe let us off here. I talked about hybrid cloud and Joe started talking about moving automation forward and getting people comfortable. I think a lot of this is, you know, meeting customers where they are and then helping them get on the journey, right? So we're seeing that today, right? So traditional configuration management on-premise, but at the same time, so I'm going to think about, you know, how do we take them out into the cloud, bringing greater automation to bear there? But so that's true for us across our existing customer base, as well as the new customers that we see out there. So doing that in a way that Joe talked about, right? Ensuring the trust but verify, up as in play is critical. And then there's another area which I'm sure we'll talk a little bit more about, right? Is ensuring that security implications are taken into account as we go through it. Well, let's just jump into security. That's one of the many considerations these days, but ensuring that you have the secure operation, you're doing some very complex tasks here, right? And you're blending multi-vendor environments and multi-domain environments. I mean, you've got a lot, you're juggling a lot. So I guess to that extent, how much of a consideration is security and those multiple factors today for you? And again, I don't know which one of the three you might want to jump on this, but I would assume this is a high priority, if not the highest priority, because of the headlines that security and those challenges are gongering these days. Well, there's the general security question and answer, right? So this is the whole shift left, dev sec ops, sort of security concerns. But I think specific to this audience, perhaps I can turn over to Joe to talk a little bit about, do you know how Anseld's been playing the security domain? No, it's a great way to start. Yes, people are trying to shift left, which means move sort of security earlier on in the process where people are thinking about it, the development process. So we've worked with a lot of customers who are trying to do dev sec ops, right? And to provide security automation capabilities during application build and deployment. Then on the operational side, you have this ongoing issue of some vulnerability gets identified, how fast can I secure my environment, right? So there's a whole new area of security, orchestration, automation, remediation that's evolved. And the challenge people have is, just like with networking or other areas, they've got dozens, in some cases, hundreds of different systems across their enterprise that they have to integrate with in order to be able to close a vulnerability, whether it's deploying a patch or closing a port or changing firewall configuration. This is really complicated. And they're being measured by, okay, there's this vulnerability, how fast can we get secure? And that comes down to automation, it has to. You know, Joe, you mentioned customers, if you would maybe elaborate a little bit about the customers that we've been hearing from on the stage, the virtual stage, if you will, at AnsibleFest this year, and maybe summarize for our audience what you're hearing from those customers and some of those stories when we're talking about the actual use of the platform. Yeah, so AnsibleFest is our annual, you know, automation event, right, for Ansible users. And I think it's really important here from the customers, look, we're vendors, we can tell you anything you want, and you know, try and get you to believe it. Customers, they're actually doing stuff, right? And so at AnsibleFest, we've got a great mix of customers that are really pushing the envelope. I'll give you one example, JPMorgan Chase. They're talking about how in their environment with focus over the past couple of years, they've now gotten to a level of maturity with automation where they have over 50,000 people that are using Ansible Automation. They've got a community of practice where they've got people in over 22 countries, right, that are sharing over 10,000 playbooks, right? I mean, they've taken automation strategically and embraced it and scaled it out at a level that most other organizations are envious of, right? Another one, and I'm not gonna go through the list, but another one I'll mention is Discover, which sort of stepped back and looked at automation strategically and said, you know, we need to elevate this to a strategic area for the company, and they started looking across all different areas, not just IT automation, business process automation on their practices internally, and they're doing presentation on how to basically analyze where you are today and how to take your automation initiatives forward in a strategic way. Those are usually important to other organizations that maybe aren't as far along or aren't as scaled down motivation. Yeah, so Stephanie, I see you nodding your head and you're talking about when Joe was just talking about assessment, right? You have to kind of see where are we? How mature are we on our journey right now? So maybe if you could elaborate on that a little bit and some of the key considerations that you're seeing from businesses, from clients and potential clients in terms of the kind of thought process they're going through on their journey, on their evolution. I think there's a lot of sort of values that customers are looking for when they're on their automation journey. I think efficiency is clearly one. I think one that ties back to the security discussion that we talked about, and I use the term consistency, but it's really about predictability. And I think I have a lot of conversations with customers that if they know that it's consistently deployed, particularly as we move out and are working with customers at the edge, how do they know that it's done the same way every time and that it's predictable? There's a ton of security and confidence built into that. And I think coming back to Joe's point, it is a journey providing transparency and visibility as step one, then taking action on that is then step two. And I think as we look at the customers who are on this automation journey, it's them understanding what's the value they're looking for? Are they looking for consistency in the deployments? Are they looking for efficiency across their deployment? Are they looking for ways to quickly migrate between areas in the open hybrid cloud? What is the value they're looking for? And then they look at how do they start to build in confidence and how they deliver that? And I think it starts with transparency. The next step is starting to move into taking action. And this is a space where Joe and the whole team, along with the community, have really focused on pulling together things like collections, right? Playbooks that folks can count on and deploy. We've looked within the portfolio. We're leveraging the capabilities of this type of automation into our products itself. With Red Hat Enterprise Linux, we've introduced systems roles. And we're seeing a lot of, by pulling in that ansible capability directly into the product, it provides consistency of how it gets deployed. And that delivers a ton of confidence to customers. So Ashash, I mean, Stephanie was talking about the customers and obviously developing, I guess cultural acceptance and political acceptance within the ranks there. Where are we headed here past what we know now in terms of the traditional applications and traditional automations or whatever? To kind of where is this going, if you would give me your crystal ball a bit about automation and what's going to happen here the next 12, 18 months. So what I'm going to do, John, is try to marry to ADS. So we talked about hybrid cloud, right? Stephanie started talking about to join the hybrid cloud. I'm going to marry automation with containers, right? On this journey of hybrid cloud, right? And give you two examples of some successful progress we've been making on that front, right? Number one, especially for the group here, right? Check out the Ansible Collection for Kubernetes. It's been updated for Python three, of course, with the end of life for Python two, but more important, right? It's the focus on improving performance for large automation tasks, right? Huge area where Ansible shines and taking advantage of Turbo mode where instead of the default being a single connection to a CUBE API for every request that's out there with Turbo mode turned on, the API connection gets reused significantly, obviously improving performance. Huge other set of enhancements as well, right? So I think that's an interesting area for the Ansible community to leverage and obviously to grow. And the second one that I want to call out was just kind of the, again, back to the sort of, you know, the notion of the marriage of automation with containers, right? Is the work that's going on, on the front of the integration, the tight integration between Ansible as well as Red Hat's advanced cluster management, right? Which is helping to manage Kubernetes clusters at scale. So now Red Hat's ACM technology can help automatically trigger Ansible playbooks upon key lifecycle actions that have happened. And so taking advantage of technologies like operators, again, core Kubernetes construct for the hybrid cloud environment. This integration between advanced cluster management and Ansible allows for much more efficient execution of tasks, right? So I think that's really powerful. So wrapping that up, right? This world of hybrid cloud really can be brought together by just a tighter integration between working Ansible as well as the work that's going on on the container front. Great. Well, thank you. Ashash, Stephanie, Joe, thank you all for sharing the time here, part of our AnsibleFest coverage here. Enjoy the conversation and continue success at Red Hat. Thank you for the time today. Thanks very much, John. You bet. Joined here by three executives at Red Hat talking about AnsibleFest 2021 coverage. I'm John Walls and you're watching theCUBE.


One of my early works as a law lecturer was a book titled, which I co-authored, titled, Media Law in Nigeria. The book has been out of print for a few years now, but I'm pleased to announce that it will be back on sale before the end of the year. I really need to recoup all of the money that I spent on the elections. Please, there shall be no free copies as I intend to reap the fruits of my labors. I'm a believer in the freedom of the press. Whatever, whatever, whether it's the responsible press or the irresponsible, I just believe in freedom of the press. Every morning, I receive a summary of most of the newspapers. I also receive trending news on social media from my media assistants. Added to that is a special pack that contains the latest memes, cartoons, or insults from the print or social media. That is also handed to me every morning. I thought I should share some of them with you this evening. Some of those memes, cartoons, and some of those insults, and some of the interesting things that I get every morning. Some are funny, most of them extremely rude. So let's start with the debate between Pito B and I and others. And for those who have seen this, this is what is called the wear and wear controversy. I'm also sure whether can we play this so that people can hear it. Why wear wear wear wear wear wear wear wear? It's because we have currently spent 2.7 trillion in two budget cycles. You wear wear wear wear wear wear wear wear, last time wear, here today. You are mistaking the wear and wear. Just for the record, what I was saying there was why are we where we are. So I'm saying, where, where are we, where, where are we, where, where, but this is what the media made of it. But what is more interesting? It appears that every photograph of me talking with the president must be characterized as though I am saying something mischievous. Now take this one, for example, here I am with Peter, talking about Peter Odie. So this is me. Boss, we have checked Peter Odie's records, he's clean. What does the president say? The president says, then let's tell the people that he was the same Peter that denied Jesus three times. That's what the president said in answer to that. Well, and then there's the one where, here, and here the president and I are talking again and we are trying to deny our promises to the Nigerian people. So the president says, so this is the list of promises we made to Nigerians during the campaign. The president answered, but this is not my handwriting. There's the other one, and this is what the president has to say on power. Sir, Nigerians are still complaining about lack of power. What should I tell them? Go and tell them that all power belongs to Jesus. I'm just a man, I can't kill myself. Finally, look at me, look at me, look at me there. They say, is that not Oshiba Joe? On the left there, that very crooked looking fellow on the left, that is supposed to be me, right there, right? Dancing next to them, but that's even good. There's the other one. This picture is supposed to be me, and that is supposed to be my friend. So they say, Oshiba Joe denies family ties with this man in the photo. So the man there, sitting down there, by the way, his cap looks exactly like my own. It's just white. So that is supposed to be me there. I'll no bother you with the others, the other tweets, all sorts, Ruga, Pastor, Minister in charge of culture, all sorts of things. The media is powerful, very powerful. Very, very powerful. But the social media is perhaps even more so. My elderly aunt called me in February, just before the elections. And she said to me, she said, Yemi, why did you resign your appointment? I said, Auntie, I haven't resigned, I didn't resign. I said, no, no, no, no, you resigned. I saw it on WhatsApp. I said, Auntie, I am telling you I did not. I said, no, no, no, why is it on WhatsApp if you didn't resign? But that just tells you just how powerful what people read is. So we have a completely wild and unruly social media. But most frustrating, I must say, is print and broadcast media sometimes, especially the deliberate or advertent lack of curiosity about the facts. I'm not sure who said these wise words, but I recommend it to all my friends in the media. It says, if someone says it is raining and another person says it is dry, it's not your job to quote them both. Your job is to look out of the window and find out what is true. It's not your job to say, Mr. X said it's raining, Mr. Y said it's dry. No, no, your job is you just tell us, OK, so which one is right? Mr. X or Mr. Y? So take the allegations, for instance, that the president doesn't have school certificate. Now, the president said, I sat for and I obtained my West African school certificate in 1961 at the Katsuna College. The examination body then was the Cambridge University, not any unknown university, the same Cambridge University. I would have thought that what any newspaper or TV station would do is just do this simple investigation required to establish whether it is true or false. Some of our TV stations even have contacts, they even have their correspondents in England and America, everywhere. So they could very easily have just gone to Cambridge University and found out, is it true, is it not true? But nobody did that. So the matter goes to court. The first time I saw it on a television station, guess what the television station carried? He said, Emma was asked in court, one witness, Waiak Mann, not Cambridge. Emma, they asked him, is this your signature on the certificate? He said, no, the television station said, Waiak official denies Buhari certificate. That's false, completely false. Waiak official only knows about Waiak certificate. This is a West African school certificate by Cambridge University. But because nobody bothered to find out or didn't want to find out, the public believed a lie for so long, even after the president had brought his certificate from Cambridge, West African school certificate. So with the ubiquity of social media and the anonymity, every day the problems of a free press are becoming more and more complex and even more dangerous. So there was a video recently, I'm also sure that we have that video of an occurrence in India showing some people jumping out of a building. This video was a video of something that happened in May in India. As you can see, a lot of the writing is even in Hindi. But it was represented on social media as Nigerians jumping out of buildings in South Africa on account of xenophobic attacks. I don't know how many people saw the woman or heard the woman on social media who now started cursing the president, cursing the vice president and all our generations. She said, I watched one thing on social media when Nigerians were jumping out of a burning building. If you don't do something, this tells us just how fake news of provocative information can cause chaos and civil strife, war or even death. Again, I thought perhaps somebody in the media, maybe radio, maybe TV, would seize the initiative and correct the fake news. Well, it was BBC that came to the rescue. I think that we as media people, all of us are now media people, on social media, print TV, must begin to do something serious about fake news before it consumes us all. On a lighter note as I close, let me note that I'll be looking forward to seeing how my remarks this evening will be reported. I intend to compare the number of headlines, some proclaiming, oh, she bought your blast media practitioners. Or perhaps some will say, oh, she bought your vows, improved engagement with the media. Or she bought your, so it sits greater support from the media. Or on social media, now this is social media.  Anything is possible. I will leave you to decide which one is the more accurate rendering of our engagement this evening. But I want to say how very thankful I am for all the help and support we get every day from the press. And to say that for good or for ill at all times, whether you report nicely or not so nicely, you will always be friends and will always be partners. Thank you very much. God bless you. Thank you.


Mae ydych chi'n gweithio i gael gyrtiw 3.1.2 yn y bydd Genny Gilruth, mewn gwirionedd 3.712 yn gweithio i gael gyrtiw 3.712, yn y bydd Graham Simpson, i gael ysgrosledd i Gweithfeyrru, rwyf yn cwestiwyr eich gweithio i gael gyrtiw 3. Mae gyrtiw ysgrosledd yn gweithio i gael gyrtiw 3.712 yn y bydd Genny Gilruth yw 62, No 50. There were no abstentions. The amendment is therefore agreed. The next question is the amendment 3712.1 in the name of Neil Bibby, which seeks to amend motion 3712 in the name of Graham Simpson on Scotland's ferries be agreed. Are we all agreed? The Parliament is not agreed, therefore we'll move to a vote and members should cast their votes now. The vote is now closed. The result of the vote on amendment number 3712.1 in the name of Neil Bibby is yes 50, no 62. There were no abstentions. The amendment is therefore not agreed. The next question is the motion 3712 in the name of Graham Simpson as amended on Scotland's ferries be agreed. Are we all agreed? The Parliament is not agreed, therefore we'll move to a vote and members should cast their votes now. The vote is now closed. The result of the vote on motion 3712 in the name of Graham Simpson as amended is yes 79, no 32. There were no abstentions. The motion as amended is therefore agreed. The next question is the motion 3750 in the name of George Adam on approval of an SSI be agreed. Are we all agreed? The Parliament is not agreed, therefore we'll move to a vote and members should cast their votes now. The vote is now closed. The result of the vote on motion 3750 in the name of George Adam is yes 108, no 0. There were four abstentions. The motion is therefore agreed. I propose to ask a single question on three bureau motions. Does any member object? No member objects, therefore the final question is that motions 3747 to 3749 in the name of George Adam on approval of an SSI be agreed. Are we all agreed? The motion is therefore agreed and that concludes decision time.