long. You will be kicked or dragged off the stage if you exceed the time. There will unfortunately be no time for questions because we have so many talks. So without further ado, let's start with Harshal, who is going to talk about TweetStormy.com. Oh, and I have a couple of other announcements to make just quickly. There is a talk in the Banquet Hall downstairs by Arpitha about sleep in the brain at 1745. There is also an ongoing off-the-record talk, which is about AWS cost optimization, which has already started from 5 p.m. But if you want to catch the end of that, it's happening. One last minute thing. Ah, yes. The first shuttle for the party venue leaves at 6.10 p.m. People should gather near the registration desk. Shuttles will leave every 20 minutes. The party is at BrewSkiPub. You must wear your badge to have access to the party. You must not lose your badge because you will need it again tomorrow to get back in the conference venue here. Okay. Over to you, Harshal. Hi, everybody. So you might have seen me from the morning. I was a volunteer. What am I doing up here? Let me warn you. It's not related to DevOps at all. So I'm a drug addict. Okay. Now that I have your attention, that drug is Twitter and like most of the audience here, I think this is a relevant audience. So I've been working on a very little, very, very little side project. If you are a pro Twitter user, which I think this is a relevant audience for, I think you might have seen a lot of threads on Twitter. Those are called tweet storms and like a lot of famous internet things. They were invented or the term was coined by Mark Anderson of Netscape and you might have heard of his VC firm. So I'll show you a few famous tweet storms. This was won by a guy called Sidharth about sexism, but not in the way you would expect. There are other famous tweet storms as well. MKBHD, a famous tech reviewer, just goes on. Here's another by Dan Abramov. He's a open source contributor. So I'll show you what I mean.  So I'm looking for beta testers. That's why I'm here. You type here and instead of manually sending a tweet and then replying to it, you can see the tweets in advance like maybe when the logic is more advanced after 140 characters or before you can break so that each tweet in itself is coherent and preview the tweets. We have a good mobile view as well. It won't. It will be a completely free project just like for learning and so I'm a computer science student and you might have heard of the principle of the principle of least power. Everything that can be made in JavaScript will eventually be made in JavaScript. So I was like fascinated. Let me learn Angular. That sounds fancy and let me learn Koa. I already knew express. So I do when made the front end. I was like very tired. Oh, what is this?  Then I decided to go with express itself because I didn't have the patience to learn anything else. So that's it. We'll be launching very soon. If you are a pro Twitter user and would be interested in this kind of thing, please go and join the wait list or email me the contact info is there in the photo and sorry for putting you through this blatant advertisement. Thanks. Okay. Our next talk is going to be darker on arm by Siraj Nawad. Is he here Siraj? No. Okay. We skip that one. If he shows the player maybe then in that case we'll go to the next one in the talk for now, which was identifying anomalies using graphite functions by Aditya. Just sign the disclaimer. Hi. So I wanted to talk about the way we are using graphite to figure out how to expose metrics and basically find out when things are going wrong in a way that you don't need a developer to understand what is going wrong. Now to give you some background, I work at capillary technologies. We have some services or some integrations with a lot of external vendors for a lot of various things. We also run a lot of services in house. So we do have a few modules which require to integrate with maybe 20, 30, 40 services externally or internally. Now at any point of time, we would like to figure out if these services are running fine or not running fine. Now the first part, like many of the talks I've already talked about is that collecting the data. So we started doing that and we started using the Kodahail library and graphite on top of that to get our metrics. We quickly ran into a scenario wherein we were exposing upwards of 800 or 900 metrics for a couple of modules to basically find out how the system is running. Now we drilled down, we tried our best, we got it down to something like 200. Now if you have something like 50 services running and you want to find out the health of each service and some which are there of the module itself, you would require a couple of metrics for each module in particular. So we were still looking at upwards of 100 metrics which needed to be monitored on a regular basis to find out if things are working fine or not working fine. So obviously someone who doesn't really have insight into the system can't really make sense of that. So we tried using graphite functions to make sense of what is happening. Now I'm not sure if everyone here has used graphite functions but it's a little cryptic to start off with but you can basically write regular expressions to get all your series of a specific type to show up on one dashboard. We ended up having dashboards with upwards of 50 graphs which doesn't make sense to anyone. So then you start off applying functions on top of this to start making sense of it. Now one of the basic things that we tried doing was you apply something called as a maximum above an average above function. Now what would you want out of something like that? You would basically say I have 50 graphs running over here out of which if any of the services that I'm interacting with let's say takes a time of more than a second or two to respond, I would like to have those services drop on my graph so that when something goes wrong, I just look at the graph. I have one or two or three services showing up on the graph and I know exactly where the things are going wrong as opposed to looking through 50 and if you go through the legend of 50 items, it is basically incoherent and if you are like me who is basically colorblind, it's very, very difficult to find the difference between the shades of all those 50 graphs. So you apply something like a maximum about an average above graph and you bring that down to two or three or four graphs, which is very, very easy to understand. So now assuming you want to take this the next step, you typically would apply statistical means to or a machine learning algorithm on top of your grasp to find out if things are working fine or not working fine. Now going by the typical mathematical approach, you could apply some statistics on top of it. One of the ways that people do this is applying exponential smoothing functions. Graphite by default gives you the functionality of something called as a whole twinters operation. Now let's say you apply that on a time series data that you are getting. Basically what this does is it looks over the data that you have over the last certain amount of time. It finds out the possible deviation that you might have in that data, which is acceptable. You can set how strict or lenient you want this to be. And whenever the deviation exceeds these limits, you see a spike. This in combination with your max or max below graphs, basically give you pointers to find out exactly when something is going wrong and where it is going wrong. So now we are in a position wherein we just tell certain people, some particular team to just look at these graphs. If anything shows up on the graph, you basically raise an alert. So that's how we solved a lot of our monitoring issues. Our next speaker is Rahul Menon. Rahul Menon speaking on self-driving Kubernetes. Hi, my name is Rahul. I work with Waisapay. So I'm just going to take about three minutes of your time just to tell you about what self-driving Kubernetes is. It's basically running Kubernetes in Kubernetes. I see a lot of value in it mainly because as you saw the demo this morning, you can actually scale out your Kubernetes cluster just by executing one single command. It helps with deployment, upgrading, scaling, a lot of things. So I've been trying to work on this for the last three months or so, trying to get this thing working and out into production. I've still not succeeded, but I can see the light at the end of tunnel. So I lost my train of thought. So if you have been following up with the Kubernetes community, this is a project in the Kubernetes incubator called Bootcube. So this essentially what it does is it brings up a temporary Kubernetes server, an API server, a scheduler, and a controller manager, which then tells your Kubelet to actually spin up your API server, your controller manager, even your HCD cluster. You can actually host the HCD cluster, which your Kubernetes server stores things on in Kubernetes. And people behind this has obviously been KoroS. I've been trying to follow with the project maintainer and trying to get bugs sorted out. As from the demo this morning, if you actually want to upgrade your Kubernetes cluster, you could actually do a live edit like shown this morning, change the version and apply it. It's that simple. If would go down your API server, when upgrading the API server, you get a minute or two, I'm sorry, a second or two of where your API server does not respond, but it's back and your cluster is functional and it just works. So yeah, that's pretty much what I had to say. Anybody wants to talk about it? You can find me outside. Yes, I do have a blog post. Yes, sure. We can talk after as well. Our next speaker will be Juber, giving a digital transformation. Is he here? No, okay. He transformed himself out of the venue. So then it's Jananjay with a cloud for robots. Okay, guys. This is sort of continuing of the work we did at ETH back in 2013, which was presented at PyCon. And back then, Docker didn't exist. So we set out to build our own cloud platform using Linux containers and twisted. And as you may imagine, it was quite a mess. We managed to scale to about 15 nodes. And that was sort of the end of it. We went back to our research and our jobs. Then we decided to take another shot at it at the beginning of last year. And the vision we have is quite simple. Robots, as you see in the slide, were supposed to be a part and parcel of our lives. We all grew up with the Jetsons and we all grew up to robots surrounding us. And that's really not happened. I mean, this is where robots are. They're in factories or they clean your floor or they cost a few million dollars and kill a few people. And that's not what we want from robots. Robots, the way I see it, are assistants to our day-to-day life. But building a robot ex-company is really, really hard. You need to put together people from so many varied disciplines to get a simple product out. And that's often really hard to do. So we want to take an approach similar to smartphones. Think about it. 10 years ago, you had devices that had a bunch of processing power and were connected to the internet. And it was all monolithic. You had just a couple of companies like Nokia and BlackBerry. And it was really hard to build a mobile phone. But today, someone sitting in Shenzhen can make a mobile phone because they know how to make great hardware. Someone sitting in a garage can make apps. And all the complexities are handled by a single platform. And that's allowed us to democratize mobile phones. It's created the mobile revolution. We actually think there is some scope to do this for robots. So in May this year, in fact, in 10 days from now, we're launching the first service powered by our cloud, which is basically autonomous drones and delivery drones that use the power of the cloud to do complex computation storage and processing. And as we progress forward, we see this vision in a way that allows us to orthogonalize and federate and commoditize robotics. If you're a guy who knows how to write a great application using JavaScript and knows nothing about robotics applications, algorithms, or hardware, you can still contribute. If you're a person who is an expert in building hardware, you can focus and provide drones as a service. If you are a person who wants to write crazy algorithms for routing and navigation, well, you could come on board and create routing, navigation, and picking algorithms. The idea is to sort of open all of this up to as many people as possible. And since this is a root conf going into a deck stack, well, we are working on our own fork of open shift and communities. And we've added a bunch of controllers. So each robot is now responsible for its own compute in a bulkheaded design. And what this allows us to do is sort of scale in and scale out. And cloud computing does not mean providing an API to a bunch of machines. It actually means consuming compute storage and network orthogonally as required. And I think this is a key enable enablement required for robots to sort of succeed and for us to see them everywhere. And yeah, that's all I have to say. So look out on reputa.org. We'll probably open source components of a lot of these things and we hope to push back to the community. And if you find this interesting, hit me up and have a chat. Thank you. I've got a minute, so I am going to play a little video. So basically right now we are full stack and our full stack extends to designing our own hardware, designing our own chips, designing our own devices, and also writing front end code, writing all of that in one piece. So well, that's the version. Imagine the potential of connecting these agile machines and giving them infinite computation and storage. Thank you. Pratik. Anshu Pratik. Aha, here he comes. You need to just sign this quick disclaimer. Also, if Sriram is here, maybe you can sign the form ahead of time. Hey guys. So someone, I think Aditya already talked about using Grafana functions. So it slightly builds on top of that. So essentially my problem was we had outages, right? Everyone has outages. When we go and look for the post-mortem of the outages, yes, there was a graph, there was alert, there was everything, everything which was required to tell people that there's going to be an outage was there, but still we would come to know about it in the post-mortem. Yes, everything was there, but still we missed it. So the problem was there was too much noise. Okay, this is alerting, that is alerting. How do we get around it? Let's say we want to alert around latency. This is how the typical latency graph looks like, right? When it comes to monitoring, do I really care about whether it's one second, two millisecond, 200 millisecond, 900 millisecond? No. What I care about is what was it there in the last minute, five minutes ago, and what is it now? As long as it's same as where it was, let's say a few minutes ago, I'm all fine. Beat one minute, beat 1500 minutes. I do not care. So what we did was, and then other thing that we had to do is if you want to put monitoring, you essentially have to, let's say, especially in AWS, you have to put a cloud watch alert or whatever monitoring tool you have to put, you have to put on each and every specific resource. That becomes time consuming. So what we did was we imported all of the data into Prometheus. Prometheus at times is database. I think we spoke about it earlier today. So out here, let's say two specific pieces that we started off with. For my two regions, I have the NLD host graph. So out here, it's like all zero. This is all zero. This was a deployment that was happening a few minutes back. So now this essentially filters out the noise. The moment there's anything non-zero, I know that I should get alert on that and I should action upon it. This is what I was talking about specifically in terms of latency. So this is how we just saw how the typical latency graph looks like. And this is my graph specifically for the alert basis. So here if you look at it, everything is between zero and one. I have set my threshold to three. If anything goes above three, that's the only time I care about, okay, there's an issue and it should alert. Other than that, as long as it's all fine, yeah, it's going up and down, basically the delta is going up and down. Last second, it was 200 millisecond. Right now, it's 190. Next second is 320. I don't really care about that as long as, you know, it's been in the threshold. So this is what we do now. Essentially, this is a delta function. So if we take a quick look at it, drop common labels, so that removes the rest of the data that information that I don't care about. Delta function for all of my ELB latency alert, here I have removed the other ELBs that I don't care about. And I'm doing it over five minutes. So this is one way of doing it. The way it started off, this is built on top of Prometheus. So let's say this is the same graph in Prometheus. Right now the alerts are based on top of Grafana, Grafana 4.0. The latest Grafana basically has you can put alerts over there. Earlier it was not there when I started off. So this is way, like you can put alerts either in Prometheus or in Grafana. Now we do it in Grafana. And let's talk about noise, right? So this is all the Grafana alerts that I get now from this system. And if you look at the count, essentially let's say May 3rd, May 4th, every day, the number of alerts if you see, they are in single digits. Only like when there's any specific outage, let's say this was the day I had 12 alerts. And that's, let's say if you talk to any monitoring guy, that is like pretty, pretty, pretty less, right? Otherwise we get like down in alerts. So yeah, this is how it is. We are planning to expand this to further more things right now. These are all the four basic alerts that takes care of covering most of my things on a higher level. For other things, we have more rest of the monitoring still in place. This is just to ensure that my downtime is minimum. In fact, with the help of this, especially with the latency alerts, we are now able to avoid down times and outages because the moment any of them start spiking, I know immediately something is going wrong. And now we can act upon it even before the outlet starts. So since the day that we put it about two weeks back, the day we started putting this, we actually caught one particular outage in progress while doing an deployment. We were able to avoid it. So yeah, that's how it is. What we are trending towards is detecting these anomalies and preventing the outages rather than you know, fixing the outages post-mortem. So yeah, that's what it is. Thank you. Thank you very much. Our next talk is by Sriram and it's entitled restful email. Okay. My colleagues actually just put my name on the board. So I have to speak for it. My name is Sriram. I work for Endurance and I'm not having slides as such, but you can go ahead and sign up on our platform, Bluehost, and we're launching a new product called restful.email. So basically we give the developers the power to send emails, where API calls, track, and get their quota as such, and also determine whether you have successfully, the recipient has successfully opened the mail and click through rates as such. This is launching pretty soon. Go ahead and explore the tool and I encourage all of you just to check out DevCloud and use it. I think digital ocean doesn't have the integration. So that's like one of our selling points. So just go ahead and check it out. Anything else you guys want to know? I can, I have questions because I think it's just like 50 seconds. That's it. Okay. Go check it out. Yeah. Thanks. All right. The next talk is nursery rhymes as applies to DevOps by Shakti. Yeah. So the motivation is to use nursery rhymes that everyone knows about to share DevOps experiences and best practices. So I've tried to put this together. I hope you enjoy that. Please read. Great. Let's begin. Jack and Jill went up to the server to run the test with Docker. Jack pushed code and broke his test. And Jill never spoke to him thereafter. Tester, Tester, have you any bugs? Yes, sir. Yes, sir. Three code dumps. One for my master scrum. One for my lead. One for my manager who's a friend indeed.    Oh, BSD has had jails forever. Humpty dumpty sack to debug. Humpty dumpty squashed a bug. All the team members and stakeholders gave Humpty a big tight hug. Goosey goosey DevOps, sir. Where shall I wander? GitHub or Bitbucket. This had on something sooner. Cloner project folder code to make it better. See collaboration working closer and I shall be an eye opener. Twinkle twinkle unit test. How I wonder where you exist. I will write unit test until the project is late to rest. Code code code your way gently down the screen. Come it early. Come it often and life is but a dream. See my little hands go hack, hack, hack. And my little test run back to back. I just have one word to say to you. Come learn DevOps and say I'm happy for you. One, two, pick your crew.  Five, six, write your scripts. Seven, eight, test them straight. Nine, ten, make them your zen. Eleven, twelve, time to sell. Thirteen, fourteen, customers are keen. Fifteen, sixteen, customers are seen. Seventeen, eighteen, repeat your routine. Nineteen, twenty, get paid a plenty. Project issues in the way, in the way, in the way. Project issues in the way, my fair user. Fixing bugs right away, right away, right away. Fixing bugs right away, my fair user. Merging PRs as I say, as I say, as I say. Merging PRs as I say, my fair user. All the tests are passing, hey, passing, hey, passing, hey. All the tests are passing, hey, my fair user. As a client you should pay, you should pay, you should pay. As a client you should pay, my fair user.  DevOps really save the day, my fair user. Last but not the least, when you say clap your hands, give me two claps. Okay. If you're happy and you know it, clap your hands. If you're happy and you know it, clap your hands. If you're happy and you know it, then your face will surely show you it. If you're happy and you know it, clap your hands. If you apply software patches, clap your hands. If you apply security updates, clap your hands. If you apply software patches and you apply security updates and your application still survives. Clap your hands.   If your package install worked and your gem install worked and your NPM install also worked, clap your hands.  If your code is compiling, clap your hands. If your CI tool is running and your builds are always passing, then you're happy and smiling, clap your hands. If you have a plan A, clap your hands. If you have a plan B, clap your hands. If you have a plan A and if you have a plan B and you always use plan C, clap your hands. If you notice the containers crashed, clap your hands. If you build the containers from cash, clap your hands.  Thank you. Okay, the next talk we have is SSH key management with Python and Jenkins by Mehul. Hello. Yeah, so I wanted to show on a small little script that I've written. One of the problem points that I usually face with, even though we are a small team, managing the SSH keys was becoming a problem as an inventory in the number of servers that we have started increasing. At times people would change the SSH key and we didn't really have it available all the time. Sharing of the SSH keys was becoming a problem. I tried to look for a quite a few scripts around which would allow me to update the SSH keys and manage them. I didn't find anything useful. So we had two requirements. One is the user should be able to upload the SSH key by themselves. And second would be that we work with the X-PACE cloud and Google Clouds. And especially Google Cloud has some provisions with API that you can update the SSH key to the API. And that makes some of the things very simple. So what I did was I just set down one evening and wrote a simple Python script using a couple of packages that are already available in Python. One is called SSH Pup Keys. You just pass the SSH key to this library and it passes the SSH key and it separates it out in a way that you can use it. So what I was doing is take the SSH key from the user and first take the user name part and since I tied it with Jenkins, I was able to validate if the person is uploading SSH key for their own name. So what we had was that the user name on the server, user name in Jenkins and the email address for the user would always be the same. So whatever SSH key you uploaded would only be yours. So that validation was being done whenever SSH key was being uploaded. And I used a library called SSH authorizer. Basically the library takes the list of hosts that you have and pushes the key that you pass to it to the given host. That gives you, and then at first I thought, like, I have the script. How do I give it out to the user? So first I thought about building a small web API for that. But then I realized we already have Jenkins and I didn't want to build authorization layer and that would be a lot of work to do. So at least we have Jenkins and Jenkins can handle this. All the users in our company have the developers have the access to Jenkins. So I just wrote a Jenkins task where user can pass the SSH key that they have. It will be passed by the script and if everything validates correctly, it will be passed on to the server. And if it's in case the next step that I'm looking to do is to pass it on to Google Cloud using their APIs. So basically the good part of what it is, while the machine is running, you can replace the API key even if you don't have the access to it. You just need the access to the APIs. So yeah, that would be it. Sorry. It would make a little more sense if I had shown you what I'm doing.


Hello Navy and Marine Corps team. Robin and I and the whole team and the Secretary want to wish all of our sailors, Marines and their families a happy and healthy holiday season. Remember to be safe and to look out for your brothers and sisters and their families, particularly those who will have an empty chair at the holiday table. Whether you are home for the holidays or continuing to watch around the world, the American people stand with you and your loved ones in gratitude for everything you do.  Thank you for your service in 2019 and for all that you will do for us in 2020. Be safe and Happy Holidays!


This is stock number 9295B. We are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used. Half-ton truck headquarters. Remember we are the guys with the trucks on 41. Check us out there at truckson41.com. Today we are checking out this super clean 2007 Chevy Silverado 1500 crew cab short box. This truck has the 5.3 liter V8 motor. From this HD video, you will be able to tell that for the age and miles on this truck. It is in really nice shape. Black is the color. It has the factory alloy rims, and it has like new Cooper Evolution 26570R17 tires with just about all the tread left. I'd say 90 to 95% of the tread is left on those tires. We shoot all of our videos in 1080p, so if you have HD capabilities on your computer tablet, or smartphone device, turn them on now because it's like you're right here looking at the truck with me. We like to do the videos so that you can get a really good idea of the overall condition of the vehicle. Because we realize it is a 2007, it's not going to be perfect, but that's why we do the videos. So you can see any of the imperfections and make a smart buying decision from the comfort of your own home. If you don't have the time to make it here, or if you just live too far away and don't want to make the trip without getting a good idea of the overall condition of the vehicle, you can watch the video. Get that idea and make the trip. Cab is in really nice condition. I didn't see any dents or dings down this side of the truck. Rear rockers are in pretty nice condition. Wheel wells are pretty nice. Back tires have just as much tread as the front tires. Frame and underbody for being a 2007. In really nice shape you can see those bed rails. In really nice condition in the frame and underbody. Not too bad. A little bit of corrosion, but it is a 2007. With about 100,000 miles on it, so pretty common. But actually in really nice condition for being a 2007, I've seen a lot worse. As we go around to the back here, the rear bumper is in pretty nice condition. Full towing package, which includes the receiver hitch and seven pin wiring. Couple little dings on that left side there. Tailgate is in pretty nice condition as well. Has a Lakeland hard tonneau cover. No major cracks or imperfections in it. Bed is in pretty nice condition. Couple little scuffs and scrapes, but hey, it's a truck. That's what trucks are made for. That tonneau shuts nice and tight. And as we go down this side of the truck, just as clean as that passenger side. Like I said, we want to give you the most accurate representation. If that means taking a six or seven minute video, then so be it. Back tires are like new as well. And down the rest of this side of the truck, pretty clean. Has factory chrome step bars that are in nice condition.  There are no rips. There are no tears on these seats. Both these seats are heated. Both these seats are power. Factory all weather floor mats in the front. Power windows, power locks, power mirrors. Heated seats, memory driver's seat. Has the auto headlamps and turned dial four wheel drive. As we hop inside here, you can see that this truck indeed does have 99,461 miles. The steering wheel is in really nice condition. For being a 100,000 mile truck. Cruise controls on that side. Audio controls on this side. Has the six disc CD changer, the Bose sound system. Dual climate control and stability control as well. Passenger seats in really nice condition as well. No rips or tears on that. And you can see that the headliner is in nice condition as well. Has the power sliding rear window. Home link system for your garage doors, security systems and lighting systems. Has the compass temperature mirror as well as the on-star capabilities in the mirror. 2007 I believe was the first year that they went to digital for the on-star. Back seats are just as clean as those front seats. No rips or tears back here. It does have the latch child safety system and that power sliding rear window. Like I said, these seats do fold up for extra storage. You can see that the carpeting is very nice and clean back here. No rips or tears. You got rear audio controls with the headphone jacks. And we'll take a quick look under the hood. This one does have the 5.3 liter V8 motor. Engine bay is very clean, runs very smooth. This was the first year of this body style. This truck has been fully safety and inspected by our service shop. Has a fresh oil and filter change. All the fluids have been checked and topped off. And this is 100% ready to go. Really nice condition. Highly recommended from a condition and quality standpoint. And to see more pictures of this truck or one of our other 400 new and used cars, trucks, SUVs, minivans, Wranglers, half tons, we quarter tons, you name it, we got it.  Videos of every single used vehicle. All at SummitAuto.com If you want to just check out our used vehicles, it's truckson41.com It takes you right to our used page. And thanks for checking out the video. If you want to make this truck yours, give us a call right now<PHONE_NUMBER>. Ask for one of our sales associates standing by to take your call. Once again, that number is<PHONE_NUMBER>. Thanks again for checking out the video. If you want to check out more, go to youtube.com slash SummitAuto. Remember to like, subscribe, and share on this truck and every vehicle that you see there. In fact, in a second you'll see a link to subscribe to our YouTube channel on your left. A link to more half ton truck videos like this one on your right. And if you have not been to our website, on the bottom, we'll link to our website. To this vehicle, click those check us out. And we really look forward to helping you with this super clean 2007 Chevy Silverado 1500 Crew Cab Short Box LTZ-Z71. Thanks again.


What's good Josh boros back again with another video, so we're gonna check out see him punk is a cancer Chelsea Green return WWE return Roman vs. Wyatt and other wrestling news I have been hearing some reports that maybe see him punk wasn't telling the whole truth about what happened with him and The young books the EVPs on that infamous night where see him punk buried a lot of the rock The locker room, so we're gonna check this out Appreciate all the love and support you guys Michelle on channel. Let's get right to this video It's going on guys It is WrestleMania here backwards some more news join us now as we look at the wildest news stories and rumors You need to know including a double wrestler refuses to work with punk Chris Jericho called CM Punk a cancer in a UW Damn Sammy Zayn wrestling Roman Reigns at elimination chamber the real reason why Seamus was injured Chelsea Green WWE rumors and much more be sure to subscribe and hit that notification bell for daily wrestling videos and follow us on Facebook for exclusively is also check out wrestling me at our code UK and her own wrestling channel incredible Nalisa the intro and gets straight into our first story Now first two looks at AEW wrestlers refuse to work with punk Atop of today's news is the latest feedback concerning CM Punk and his relationship with AEW First let's take a look at the comments reportedly made by AEW wrestlers about their thoughts on CM Punk returning to AEW While the current belief is that AEW is trying to buy up punk's contract and send him packing Dave Meltzer is reporting in this week's observer that in Norfolk on 26 October It was noted that several of the top people were saying that punk would not be back A few names were mentioned with Chris Jericho being the name mentioned most but that many if not most of the Key top names who are saying that they wouldn't want to work with him According to Meltzer one top star noted punk won't be back His value on screen isn't 100% worth the hassle and black cloud he's caused backstage Another top star noted that the team has decided he's out and regardless of some being willing to work with him The collective decided that he was voted off the island. Damn. Next up Chris Jericho blasts the amp Geez man.  That is very interesting to hear You know, obviously, you know, what CM Punk at the media scrum was not called for whether he felt like it was justified At the time he probably should have handled that backstage Because no one is talking about that pay-per-view event only other than what happened with CM Punk at that media scrum Punk At Chris Jericho to the list of wrestlers who feel CM Punk isn't worth having around a story making the answers that Chris Jericho Confronted CM Punk after the alleged backstage brawl between punk a steel and the elite would Jericho calling Punk a cancer Vifal select is reporting Jericho told punk he's detrimental to AEW and that punk told Jericho to leave Vifal added that it reached out to Jericho, but it hasn't heard back Punk sources confirmed that Jericho punk story. Next up WWB hot-shodding a Bray Wyatt versus Roman bro, uh, it's When you look at it on paper Whether what the EVPs were doing was probably not writing You know, maybe them leaking stories to the news outlets and all this other stuff but at the end of the day That was not handled in the best professional way and it ultimately caused a lot more Problems than good and you know Obviously people in the locker room are not gonna be too Happy on what happened there and this goes into the conversation of should he join WWE at some point And you know some people's criticism is I don't know if we want that Yeah, I've heard or seen reports that some of the higher-ups and WWE don't want him because of what happened in AEW so it's really one of those things where I don't know where seeing punk future may lay. He may not end up wrestling I think he may end up probably retiring from wrestling as a whole broke is People are not gonna want to work on them, you know, especially in AEW. I think that's done The only thing is the buying out contract. What's the stipulations with that? And if people in WWE the hires up higher-ups, do they really want punk there? Do people in the locker room in WWE want punk there? That's really what it comes down to man Rain's match is a WWE gonna hot shot a Bray Wyatt versus Roman Reigns match Oh boy, WWE Universe's rabid reaction to Wyatt's return PWInsider reported earlier that Wyatt is listed as SmackDown's number one baby. Oh, yeah He's Drew McIntyre being second a sure sign of the WWE's he's they biggest baby face And now Dave Meltzer is reporting on Wyatt's success And he's not even really wrestling Roman Reigns sooner rather than later Wyatt has become a top merch seller over the bloodline while it would be best to keep them apart for a while The idea is that Reigns versus Wyatt could be the biggest program in a long time since Wyatt is so hot right now There's no question how popular Bray Wyatt is right now However, why would the WWE when a booking against Roman Reigns right now? Wyatt's new persona is still being explored and fans have no idea whether the rumors of Bray building his own faction Are you the Wyatt 6 are true? Yeah, makes more sense for the WWE to develop Wyatt and give him some time to get even more over with the fans before putting him into a Storyline against Roman Reigns Likewise, they seem to have Roman Reigns his next few months worth of programs mapped out while it's unclear whether Reigns will wrestle the Rock at WrestleMania 39 Plenty of strong backups including Cody Rhodes and Seth Rollins Yeah There's no denying the value of a Wyatt versus Reigns program But it needs to be timed right so that the WWE can maximize its effectiveness Do you think Bray should wrestle Roman Reigns soon? Let us know in the comments down below Here's the thing. Do I think it should happen? Yes soon. No the story is there The story is there Roman did beat Bray for the Universal Championship once he came back The story is there they could really do something interesting But we need to really flesh out Bray if you're gonna do this, right? You gotta do it correctly. Don't Force it don't of course we would love to see it But it needs to take time it needs to take place in a situation where everything is aligned up And it's like okay now we can have this happen because at the end of the day if you're gonna do this One or two things got to happen Well really one thing has happened Bray would have to win you do not bring him back to book him into this situation And he loses he has to win is either he has to win or it has to be a situation Where maybe he loses the first match, but he ultimately gets the championship from him. He can't lose the few That's what I'm saying. So this is why it's we don't want to go that route of what happened when he came back as The fiend gimmick we don't want that because they booked him in this corner He needed to beat Seth Rollins at Hell in a Cell. He didn't So it's just one of those things where it's like just wait wait play it out. See what happens Didn't go from there.   Hmm a Smackdown superstar Sami Zayn has come a long way from his days as a nuisance to the bloodline to his current status as an honorary Ooce however Zayn recently revealed that there were no long-term plans for him in the faction Sami spoke with the UK Mirror about this saying that this is one of the more filled out long-term stories I've ever been a part of and it's long even by WWE standards Usually we might do two or three month stories But I've been aligned with the bloodline in some respect since April Yeah, we're still only kind of scratching the surface as to where this is going Zayn talked about how the storyline developed and its initial pitch The initial idea was to have some on-screen interactions every now and again because it made sense as a self-proclaimed locker room leader I have a good rapport with the head of the table So we're kind of cooking up that idea Wrestling fans warmed up to the idea of the always aggravating Zayn Worming his way into the group and playing comic relief While this could have been a bad mix Zayn Zayniness are actually made for entertaining television Sami talked about how the WWE Universe's strong reaction to its presence helped further the storyline But one of the things I'm realizing is with live audiences These stories tend to take a life of their own and you kind of don't know where they're gonna go and that's actually what's exciting about it I see all the fans trying to predict it and they don't know and in a way I don't know because the reactions start taking it in a different direction One thing fans can be thankful for is that that Triple H has allowed this story to develop It's not telling how Vince McMahon would have handled things Especially in the light of his habit of writing TV the way fans want things to go even when the audience reaction suggests otherwise Next up is Sami Zayn I will say this he's doing the best work He's done is so long. He's so entertaining in that group. And I think a lot of us are I mean He's he's gotten so over. He's one of the top babyfaces because he's aligned With Roman Reigns in the bloodline the honorary oops I will bro I forgot what smackdown it was but the smackdown where we thought oh Sammy's about to catch the beats they about to kick him out the the bloodline and you looked at his emotion And I started to get emotional like bro that he had these puppy dog I was like, bro, you're about to kick me out only for him to get the honorary U shirt and the crowd goes crazy But I'm telling you when the shoe drops and they turn on him It's gonna make him a make a star for sure wrestling Roman Reigns at elimination chamber as good as a Sami Zayn bloodline Storyline has been most fans believe it's gonna end badly for Sammy with the bloodline turning on him Yeah, however, this could lead to a Sami Zayn versus Roman Reigns match at elimination chamber Some fans think that it's exactly what's gonna happen pointing out how the February premium live event is taking place in Zayn's hometown on Montreal While that looks to be possible that could be great I'm past the point of trying to predict what the endgame is But I think at this point we have such a level of investment that whatever happens I think fans are gonna just be there along for the ride It's been really a lot of fun and seeing how much the fans have been loving it has really been rewarding Although the idea of Sami Zayn beating Roman Reigns for the undisputed championship seemed impossible Yeah, WWE seems content with providing fans with entertaining championship matches Even if the outcome are you Roman winning is inevitable next step. Yeah, that's the thing I can see that happening. They set that up. Sami won't win But they'll tease it like he probably will for some people that may be kind of annoying but once again Whoever beats him it has to make sense Yes, Sami beating him would be interesting. It would probably be one of the biggest pops It would be insanity At the same time, I don't know how they booked it. So maybe maybe that's the story they tell who knows. I don't I don't know I just don't see it happening But you never know. Maybe Triple H does pull a notable here. We we will see but I would definitely be interested in that for sure Real reason why Sheamus was injured Why did the WWE write Sheamus off smackdown with a cave-aid injury? He suffered two weeks ago at the hands of the bloodline All turns out Sheamus is taking time off for a very important reason He's getting married. Yeah, I heard he was getting married PW insider reports that Sheamus will be getting married to Isabella Reveille this weekend Okay, I'll announce their engagement last year after Sheamus asked for a hand in marriage during a vacation in Ireland Sheamus and his fellow brawling brutes of Ridge Holland and Butch are booked to face the bloodlines Jimmy and Jey Uso Along with Solar Sokoa at the upcoming crown jewel show Sheamus reportedly won't be on the 28th October smackdown Gage side seats reports that Drew McIntyre is attending the wedding and will also be absent from smackdown Now Sheamus could be back in time for a crown jewel, but it's currently unknown whether he'll be back at the show If not, the WWE could either turn the match into a traditional tag match or have another WWE superstar step up to take Sheamus's place Where sending Sheamus and Isabella all our best wishes for their new journey in their lives That's awesome, man. Happy to say this on that one. That's pretty dope man, congrats Regarding WWE superstar Sasha Banks, who's may walk out on the WWE has led to endless rumors about her future in the company By now fans have heard just about every rumor including that Banks is waiting for a contract to expire That she's renegotiated a deal or that she's even quit wrestling all together And whilst we don't know we can confirm that Banks and fellow wrestler Kalisto recently won a prize for the best industry newcomer at the World CBD award show As Meltzer reports, she and Kalisto own a CBD brand What is known is that Banks has kept herself busy since walking out on the WWE leaving her various theories Including that she is done with wrestling or that she is still interested in returning to the squared circle But that she's taking time off much as she did in 2019 after she and Bayley dropped the women's tag team championships at WrestleMania 35 We also have this tidbit from Dave Meltzer to add to the bevy of Banks rumors Noting in the recent tweet where the boss was shown training and socializing with wrestlers from the rcw promotion in spain Which I believe is the company axiom originally came from and made a name with She's still under contract to WWE, but there's no word on when she'll return as there were said to be hang ups in negotiations for a new deal One of the more curious aspects of this story is aware about Saneomi Like Banks, Naomi was rumored to be back on her way to WWE after reaching some sort of reconciliation with the post of vince bookman regime Naomi hasn't went back. There's been little to no news The WWE obviously has no reason to release any information about a Banks and or Naomi return if it intends to make their comeback a surprise In fact, fans can count on a WWE releasing disinformation to keep fans on their toes And finally more chelsea green in wwe And here's the thing about that too. I know a lot of people are doing the speculation. Oh, maybe she'll come back here Or maybe they'll come back here and it's like honestly if she decides to hang it up That's just her they both decide to hang it up. That's just them You know, if they do decide to come back, that would be awesome for the women's division as a whole. So Um, honestly, I'm just trying to just plan it by ear. I did the same thing with break I wasn't sure, you know, I'm saying I you know, especially when vince was in control I definitely wasn't wasn't on board for that But I wasn't sure if he was if he was too cool if he wasn't That's cool, too You know I'm saying at the end of the day all you can do is cherish the work that they've done For the company, you know, the the great matches that they've had in the past and kind of go from there, you know I'm saying I don't want to it's cool to speculate but when people get their expectations up A lot of times they end up feeling, you know feeling disappointed when it doesn't happen. So B rumors They may recall recent rumors that wwe was interested in bringing green back to the company Chelsea is currently working in pack wrestling But a new report from pw insider suggests that she could be wwe bound very soon Ringside news noted although a return is an official there is belief that green wouldn't give up being a regular feature on impact wrestling Unless she was offered a deal by wwe It was also reported that back in august that chelsea green was working in impact without a contract Do you think green should return back? Let us know in the comments down below. I'll see you next time But this was a good one, man This was uh, this was a pretty good video, you know a lot of information that uh, I wasn't too Well, I wasn't privy to uh, I will say this the whole seam punk thing man. That's Oh, no, bro. I don't know guys. I don't think he I don't I just don't see him going to wwe. I don't see tony con even letting that happen I do think they're gonna try to do something where he can't compete For a while.  That's what it really comes down. Should he be in the wwe? At this present moment with how everything is still kind of fresh how people feel about him I don't know maybe later on but once again, he's getting older He's you know, he's body's not what he used to be. So I'm not sure, you know So comment down below. Let me know and do you guys feel like seam punk is a cancer? And should not be in wwe and honestly should hang it up I know I believe I've asked this question before but I want to really Dive into it now with you know, other situations where other people coming out to him He's not good, you know in aw when I rock and winner Do you guys agree with that sentiment that he is a cancer? Do you just feel like maybe emotions got the best of him? And you know things just got out of hand and maybe he deserves or not deserves But maybe he should have another chance in wwe, you know And also, how do y'all feel about bray Wyatt versus roman reigns so soon? Do you think they should hot shot book this one since bray Wyatt's super over? Do y'all think they should wait build it up and would y'all have bray Wyatt Actually be roman reigns. Let me know down below But I appreciate all love support on the channel road to 100k appreciate y'all can give me see you next one. Peace


Hi everybody, welcome for this new Jenkins infrastructure meeting and today we're going to talk about the LDAP OTAGE that happened last week and some ideas about how we could manage identity management. So first, let's talk about the LDAP OTAGE, I mean, I guess you see basically what happened. So two weeks ago we had an issue with the Kubernetes cluster where we had to recreate everything from scratch and we discovered that our LDAP database was not back up since February. So the first step was to restore the database then we realized that people were not recreated in the process. Those icons were available for someone else, which means that it was a big deal for, especially for plugin maintainers, for recent plugin maintainers. And so the first step was to first recover every account that was left. So we first focused on maintainers, then we used JIRA and Artifactory Database to restore those data. And once all user accounts were recreated, we tried to reset every password. And for maintainers, it was quite easy. It was a totally different scenario for the whole database. The main reason to this is because we have a lot of accounts in our database, we also have a lot of garbage in the database. And sending 100,000 email address in one day is not something easy, especially when we usually only send something like around 500 per month. So it was quite challenging. And this process also highlighted a few limitations with our account app, which is the application that we use to create, modify and delete accounts in our LDAP database. So now that we restore and we are back to the previous situation, the idea is to identify how we could prevent this to happen again in the future and what would be the different options. So last yesterday, we had a discussion with the Linux Foundation, where Tracy and Alec were also in a discussion. And so the idea was to see with the Linux Foundation infra team what would be the option if we could use, if we could delegate that responsibility of identity to the Linux Foundation instead of managing it by ourselves. And also in the discussion, they also remind us, maybe not remind us, but tell us that told us that we could also, they could also host our JIRA instance on the Linux Foundation. So basically everything we discussed for around one hour about why we would use the Linux Foundation identity management, what would be the limitation, and what would be the different services that we would move to the Linux Foundation. So first, any question until now? You really want to add something on this? So yeah, so then I continue. So regarding the identity management, yeah, someone who is Tracy, we can't hear you, Tracy. Better. Yeah, I've just put in the chat the link to the document where I just want to capture everything with the identity management and the transition. So it's work in progress, but I'll keep updating it with this conversation. And if folks want to go in and comment or use that as just background to what we're trying to do, just put the link to the chat in the notes. Thanks. The thing is, at this moment, we are really open to multiple solutions. So either we totally move identity management to the Linux Foundation, or we find a way to remove the account app. This morning, I was playing a little bit with a tool called Key Cloaks. Basically, it's a tool that seems to be quite easy to deploy on our community's cluster. And so you can have user federations. So we could, for example, use it. So we could, for example, reuse that database and use Key Cloaks to create user in the database, modify user, delete users. And what we can also use it for is to, for example, have it in front of the database. So while we are migrating to a different solution, the Key Cloak could be the central piece for a while. It seems to be supporting a lot of features like user requests and accounts. They can have to reset the passwords and an email. I mean, like all the features that you would expect from an identity management today. But yeah, that's one of the options. The other option would be to see if we really need it because the main reason why we introduced that in the infrastructure was to use it with Tira. But I do it through the byte on my side. Sorry. Is it the same for everybody? Yeah. Sorry. So yeah, we are really at the moment where we are trying to find, identify all the different options. So I really encourage you to look at the notes and put some comments there. Yeah, it sounds a lot of them. Yeah. It sounds okay for you. So I guess we can continue. Otherwise, we don't have, I mean, the main focus were on the account management stuff. So if you don't want to ask any question, I can just continue on the last topic that I want to talk today. I think everybody wants to add anything on this. Well, so in terms of Linux Foundation as a potential ultimate. I assume that's a long horizon because there's a lot of work to transition 100,000 accounts to anything. So the first thing in the discussion was why they can provide, they can provide the identity management. We would not have the control on it, so it would be a black box. So basically, a user just created a Linux account and the Linux Foundation accounts to access Kubernetes project, to access any other project, and it would be the same for the Jenkins projects. So one of the challenge here, first will be to map the Jenkins account with the Linux Foundation because there is a big probability that your username is already taken by someone else in the Linux Foundation. That's one of the things. The other thing is until today, the Linux Foundation always provided, always used identity management for their own services. So they don't know at the moment how we would use those services. And it will not necessarily be easy to create groups and change groups, member and stuff like this. We don't think it's a big deal because we do not create, we don't regularly create groups, except the default one to access Tira and maybe for, let's say, artifactory, but otherwise, this is not something that's regularly changed. But I do not expect it to be like a quick win where we're just working it three days and it's done because that is used in a lot of places. So the biggest challenge I think will be to see how we do for Tira. So if they host Tira, then it's easy because we don't have to handle, we don't have to care for the identity. We just use our identity and that's it. And they provide us the Tira. And if we don't want to use Tira anymore, for some reason, maybe there is other options. And also, they also have experience with their own identity management to manage chief work. So this is artifactory. So this is also something that they already did in the past. So I don't, we plan another meeting with them next Monday. If you have any questions, feel free to ask. So we don't know yet at the moment how much energy we have to put in this project. I'm particularly interested in the Tira thing because if I understand correctly, we need to confront a Tira upgrade within the next six or nine months. We've got a Tira version that we need to update anyway. So good excuse to consider hosting that by Linux Foundation. Great. So that's definitely, so the discussion was just a reminder. So right now we have three options, either we keep maintaining Tira by ourself and then we have to upgrade the database, we have to upgrade Tira. And so it will require some work from us, either we move to Tira clouds, but there we have a bunch of limitation, limitation that I identify our Tira, you know, our Gira, so there is a ticket with that, but the main issues is the number of people who can look in on Tira. We cannot use adapt to a ticket on Tira clouds. So you have to use Tira accounts, there are some limitation with the domain that you want to use for you for your accounts and stuff like this. So it's not necessary to be able to move to Tira clouds. And also discussion about using GitHub issues. So yeah, I think it's kind of related, it's kind of linked all together. But yeah, from for all users, most of the accounts accepted for maintainers where it's way easier to maintain because the amount of maintainers is something like 1,700 user account, which is definitely easier to handle than the 100,000 user account that you have in adapt. But so yeah, I think the discussion about the ticket system you can consider for the identity management. Yeah, on the Gira side, I think I want to say, like I'm in favor of, you know, aggressively getting rid of services that we shouldn't be managing and figuring out how to do that. So we can kind of focus on the things Jenkins should do well. So on the Gira side, I think we can separate some of those discussions. We're already using GitHub issues and Gira cloud. I think we need to figure that out so it becomes clear to the community. That being said, I don't think Gira is going away anytime soon, not with the requirements for security. So I'd be keen to say, well, can we just move Gira to be hosted by Linux foundation and pass on the login as well and do that with a view to maybe getting it done by November. Yeah, there's been a recent discussion on the developers mailing list that some people really love Gira for their plugins. Some people hate it. So it's going to be hard to get a consensus on one single tool. But we I think we can enable people to use both, but definitely moving the services outside of the Jenkins infrastructure management would be really nice. I would be also in favor to move Gira to the Linux foundation. This was something that we discussed one years ago and it was not clear at that time if we could do that. But apparently it's something that the CDF can provide. So I would definitely be interested to see if we can go down that path. The other thing I also think that you have to be clear is what are the priorities for the Jenkins infrastructure projects? Because right now we have the identity management that we have, that the batteries in terms of priority. We still have to finish the automation release project because we have a strong deadline about being able to release stable release and security release. Because once the security needs to happen for the stable release, we need to be able to provide security release as well. So automated release is still on the path. So yeah, there's something that you have to keep in mind. And just this was the last thing that I want to discuss on the automated release. I'm just wondering. So that week we agreed that we would test the security process that we would test the security process using the next weekly release next week. I'm just wondering what's our, I mean, what's the current state with the windows containers? I don't know if it's Alex or me, the blocker in this project, in these parts. All right, for the release specifically, is that what you're asking? Yeah, I'm just asking for the packaging windows, the package windows are on effects. So we can use the default .NET 3.5 container as the build part. We don't have to build our own image for that. And then we can use the inbound agent or what used to be called the JNLP agent. So I just don't know how to just set that up in the pod template. But I can give you the image names to use if that's helpful. Yeah, if you can put that in the notes and then I'll send you the PR with the changes made in order to make this working. So you know what to change next time. Sounds good. That way we're using the official Microsoft image. So it should include all security fixes and everything going forward. Perfect. I think we covered all the part that I had. So I think we're all good for this meeting. So I called three times to see if you want to talk about something specific. That's the right moment considering the amount of people in the video today. Well, so Olivier, do we plan a separate retrospective activity and a separate eventual retrospective meeting on the outage? Howard, what's the vision there? So we definitely have to do a different retrospective regarding the outage. I just would like to see before doing the retrospective to see what are the different options that we may have to solve here. Because we had that meeting with the Linux Foundation yesterday, which was planned really late. I mean, I was at this correct like one or two or before it happened and Trisha organized it in the last minute. We have a second one next week on Monday and then we'll know a little bit more about what does it imply to move to the Linux Foundation for identity management and how many time would it take to have to move it and stuff like this. So I think it would make sense to just do the retrospective once we know a little bit more about what are options. Is it, does it sounds right to you? Yeah, I just want to be sure we go through it because there certainly there's plenty to be learned from the experience. I think we have, we have two retrospectives to do here. We have one regarding the Kubernetes cluster and what happens. And we have one regarding the outage. Right. Yeah, that's fair because they're intermingled and yet too separate, you know, not having detected backups missing, et cetera, is a big gap, not having tested backups yet. Just wondering how would you prefer to do retrospective and we plan to do it next week during the Jenkins Infra meeting? How do we, should we do it by document what would be your preferred way? For me in the past it's worked well to gather as much as we can into the document beforehand and let everyone who is interested contribute their ideas and concepts into the document. So it's been deeply vetted before and then yeah, I would love to hear it if we could be ready for next, next in for, in for meeting. That would be great for me. Let's run this. Can I just add something? I think would it, and this is just a suggestion, prior to doing the retrospective, would it be, and this may have been done and I just have not seen it, would it be good to do some type of a like business disruption report? And in that report, we actually show a timeline of what happened. I think that that would be good for retrospective because if people know where the deficiencies were as they happen, we can then make suggestions. But that's, I don't know if that's been done and if it hasn't, it's just a suggestion. I think that a detailed timeline is in the document that Oleg started. Yeah, Oleg started for the LDAP outage, but I'm not sure that it also covered the Kubernetes part. Yeah, but good idea, Mark, and absolutely we should. The timeline is a crucial part of the retrospective. Thank you. The reason that I use that suggestion is because as I'm sort of thinking from the Kubernetes cluster perspective, how we made better things, I have ideas, but I don't know exactly how the timeline went. I was a piece of a part of it, but I don't know the full scope of everything. Okay, I'll do this. Okay, I can, I can, I can do this. Okay, I think we are good. So in the last topic, one time, good time, great time. Thanks for your time. Have a great day and see you on RC. Bye-bye. Have a good one, everybody.


So this is a great, great, great, great movie. It's showing you the direction that all of this is heading. It's a direction of trust. It's a direction of loosening, of thinking you know anything about anything in this world. That the world tells us if you don't know about the world you could die or you won't be able to survive. But actually this is taking you more and more and more into that what the Course calls salvation. I do not know the thing I am, what I'm doing, where I'm going, how to look upon myself or the world. The ego would say that's gullible, that's dumb. It would have a few choice words for salvation. Like yeah right, don't even think about it. But actually Jesus is calling us into that state. And I think one of the things that a lot of us will talk about is living a spontaneous life. There's something about even seeming to have this Mexican scenario going on in the dream now. There's somehow, deep in our mind, we must be valuing the holy instant more than predictable linear time. Predictable plans. You know they always say if you want to make God laugh, tell him your plans. The planning is tied in with this construct of a human being. Humans are designed to plan. In fact in the parable of David I was in university for ten years and it was a good time of undoing. But there was a bachelor's degree that was earned in there and it was a bachelor's of urban planning. That was literally my degree in the world was planner and then it started to get funnier and funnier. Because as I was going through it all I thought this isn't really what my life is going to be about. And I thought this is a lot of work for nothing is kind of what I kept thinking. Because I had the sense that it was going way beyond whatever I was putting my efforts into. That it has nothing to do with what I seem to be learning. And it was a bit frustrating and disconcerting to be studying and doing coursework and have this deep feeling like now this isn't it. But this too shall pass and we'll go off in other directions. So the one thing you can say about miracles, Jesus talks about fifty characteristics and principles of miracles at the beginning of the book. That miracles are involuntary. When you think about even the human body there's certain things that seem to be part of the human body that's like our actions that seem to be under conscious control. And then like we could say like things like heart rate and different things for a long time were thought to be involuntary. Now we know that you can control the heartbeat. Everything is under control of the mind and consciousness but miracles are not under conscious control. Miracles are involuntary. When you find yourself just happy for no earthly reason there's miracles happening. When you find you're in the flow, you know how they always say go with the flow? I've been saying that for decades go with the flow. That's the miracle. It's like a current. It's like a flow and there's no control over it. You can yield into it but you can't control it. Miracles can't be controlled. And so it's good to start to open up and start to think wow what would my life in this world be like or what would my days even be like if I had no control over the world? If I wasn't trying to plan it or direct it or control it based on past learning, based on everything I've learned in the past all the programming and conditioning, what would it be like to be free of the conditioning and just watch, let life unfold, watch the day unfold without any sense of trying to direct any of it, without trying to plan it. That's part of this phase of the dream we're in now. How spontaneous can you be? How radical are you prepared to be with spontaneity? You know, it's kind of a nice invitation because you can see the context. The purpose is to take the mind out of thinking it knows about time and space, even that we can understand things in a linear way. So a lot of our movies, one of the movies I mentioned earlier today, Mr. Nobody, is what I call a quantum movie. It's all chopped up. I remember the first time I watched Mr. Nobody I just sat there and was like, what is that? And then it was like three or four days later Jesus started filling in the whole thing and says, watch it with me. I'll point it all out. It was totally, I could not understand any of it. I just was like, what is happening? That movie was so chopped up. It's like taking your spaghetti and just slicing it up with a knife. It's just a whole bunch of pieces, but then came all the commentary, which was spectacular. Suddenly everything clicked, everything, every little nuance of the film had a meaning. You could see the meaning beyond the phases because it didn't have that linear component to it. And that's what we have to learn to let go of, is trying to make sense of things in a linear way. We have to let go of causes and effects in the world and start to realize that our thoughts are causative and only our thoughts, that there are no causes. Nothing causes anything in the world. It's just our thoughts. And when we can come to that realization, we're free because no longer are we at the mercy of conditions that are believed to be external.  What a beautiful picture. What a beautiful unified picture. All the characters played their parts perfectly. Nothing was out of place ever. It was always in the divine flow. The flow is all there was. That's all that had any meaning was this beautiful flow. No possession, no control, no analysis, all the things that we found difficult that we had to struggle with were all part of the deception, self-deception, and the flow was all that there was. Just this beautiful, beautiful, abstract flow. So this is really a great movie to kind of really give you a feel for where this is heading. Like, it's okay to let go. They say, let go and let God. It's okay to let go.  You actually live. You find yourself living. You won't struggle with survival if you let go. You'll laugh at the very idea of survival. What was it all about? Survival of what? A body? Yeah, that's what survival was about. Who's concerned about survival of the spirit? The spirit just is. So it's this big let go. And these movies are just such wonderful reminders that it's okay to let go. It's safe to let go. Your life doesn't fall apart.  Your mind recognizes itself. It comes whole again. As it always is and has been and will be forever. So there's not really a change. Enlightenment is but a recognition, not a change at all. It's just a recognition, recognize, come back to the thought. Cognize is thought. Come back to the thought that you are a thought in the mind of God. Always have been. And nothing could change it. Nothing could throw you off the hook, off into something else.


and this is our cabin. It's hurricane season in Nova Scotia and we are getting hit in the next 48 hours. Crystal, it gets even worse. This is insane. Oh my God. We are currently in a race to get the exterior of our cabin water tight. We have to finish the siding before the hurricane comes. How are we gonna do that? Well, we're gonna get to work right now. Thank you to Squarespace for sponsoring this week's video. With the hurricane arriving in 48 hours, it's time to get to work. Last year, we had our first experience with the powerful Hurricane Fiona and we plan to be more prepared, starting with the siding. Here it comes again. That's how you know it's a storm that's a ruin. The real question is, is this weather going to stop us from finishing? So wild. Not a good start. For the past month, we have been transforming the exterior of our cabin. This week, we were hoping to see it come together, if weather permits. Hey, did you think about, not only do we have to side our house, but we need to take all of our furniture in? Yay, no, I forgot. I am definitely starting to question if this is a good idea. It is getting so intense out here already, although there's still like two days until the storm. Yeah, I'm getting wet even on the porch now and the water is just creeping up. And after a few hours of heavy rain, it cleared up and Bella's on the prowl. Bella, I was just going to say this is too entertaining. It's been like a half an hour. They've been frequenting this tree forever. Yeah, like a long time. It's stocking up for winter. It's a good tree, lots of pine cones. We're keeping the cabin safe from predators. Good girl, Bella. Are you going duty now? Go get the squirrel, Izzy.  So scary, right? Oh yeah, there's this tree. But I had to just stop for this moment and take this in because the sky is lighting up as the sun sets and we very rarely see these colors because we're so nestled in the trees. It's the perfect end to today and it is the calm before the storm. Siding never ends and hurricanes come quick. We're at the top peak now. So we are cutting 60 degree angles. Oh, I don't know what's happening right now. I think we're both. How do I get this? Oh, we're working hard, everyone. We're working hard in the dark. Chris, are you serious? You can't get it to move? No. Are you just trying to spin it? You obviously see the way I don't think. And try to spin it again? Okay, who sees it? Do it again. Do it again.  And we might need to call it a night soon. Let me tell you that much. Where? Nothing good happens after 10 p.m. am I right? I think the saying's 12 p.m. But you know what I'm trying to say. Anyways, we're on the angles now or don't. Blah, blah, blah, blah, blah, blah, blah, blah, blah. Blah, blah, blah, blah. Yeah, we're feeling a bit blah, blah, blah. But we got to get this done. With every board, we are closer to completion. Time to clean up, Jazzy. And a hurricane. Good morning, everyone. And good morning, Mr. Sun. Didn't expect to see you all out there. It's a gift. It's wild that the next day can be just so beautiful. It's hot.  This year in Nova Scotia, we only have one season. Rainy season. Okay, we have three out of four sides that need to be complete and watertight before tomorrow. Today, we're changing our location. We're gonna start on the backside because it's the biggest and the most surface area ever. And we've already started moving our tools, so. Construction zone. Whoa, look. Construction zone. Look, Pat. Sunshine.  After weeks and weeks of trial and error, setbacks, and weather delays? Yeah, I think we're gonna. Just a little tight on the left, but it fits perfect. Nice. Perfection. You know what?  I am a rock star. Just a sliver or more? You got it? Yeah. Here we go. Yeah, girl. Here we go. Yeah, girl, get it. Get it, get it, get it. She ain't just pretty face. She's also muscle. In the middle of doing the siding, our neighbor just popped on over. And what a legend. Came back with her chainsaw and took down one of the trees near the solar ray. Thanks! Because it has been swaying a lot in the storms and it is awfully close to the panels. And we've been wanting to take it down for a little while. What an absolute gem. Comes down the driveway. We didn't hear him or see him. All we hear is a chainsaw. We pick our heads around the corner and he's taking the tree down. Shout out to our neighbor, Peter. What a gem. Keep it going, keep it going, keep it going. Oh, I got it. I think we're back. Keep it going, keep it going. We have made it to the top in record time. We are now at the angles. But we have a slight problem. Clearly last night that light didn't do anything because we were cutting the angles on 60 and the angle is not 60. Our miter saw only goes up to 60 and we can't find our protractor anywhere. Classic. So that's 60. Okay, that's got sh** on me. Oh. We think it's 70 or 65. We'll see. It's like missing this much everyone. I'd call you the protractor. Protractor. It's 5 p.m. in 12 hours at 5 a.m. The Eye of the Hurricane will be passing over top of us. And as I'm looking around here with nightfall, only just a few hours away, we are gonna stop where we are and start putting everything away and secure it because there's too many things that look like they could just take off. And we've got some pretty nice windows in here now. I wonder how many people are stressed out watching us side our cabin when they see everything around. Yeah. Like, comment if you're one of those because I can just imagine. I know our pack so well. They're probably being like, girls, take care of this. Who cares about your siding? I know. Well, we made the most of this not rainy day anyway. Glorious. To be Hurricane Ready, you have to protect anything that can be damaged or fly away. We are moving as fast as Luna at the clown bus. 10 seconds ahead, y'all. Who made this? Ready for the 10 second tidy. Ready, set, go. We always say ready can be the last. Why are we putting that there? Going nowhere this year. I need another. And just like that, everything is secured in six. Hurricane Prep is looking a lot different this hurricane season. But one thing has stayed the same. Storm chips, water storm chips. Storm chips first appeared on social media back in 2014. Since then, it's become a part of Atlantic Canadian culture, bringing a sense of belonging. We're going to come here. We're going to pick up my storm chips.  Thank you. Happy hurricane. Happy hurricane. It doesn't dig into their chips as soon as they get there. No. I couldn't eat whatever I want. Snack, girl. You just yelled at me. I'm going to. The rain is coming down harder now, eh? I got it all. I got the chips at least. Must protect the snacks. Are you ready for the hurricane, Izzy? You have a hurricane treat. Definitely forgot to walk the girls today. Lamb chop. Hashtag lamb chop. Not only is a lamb chop a toy, but also a pillow. It's really starting to pick up now. And the house got a little shake there as we were sipping our coffee. So it should be an interesting day. How'd you forget about your babies? Delish. 10.25 AM. And the hurricane is supposed to come between 3 and 6. So now we just have a waiting game. This is the tropical cyclone, and this is Nova Scotia. And you can see it's track coming right over the southern part of the province. Whoa. The trees by that out here just look like.  I don't even know where it is. Oh my gosh. So many trees just fell. Did you hear those? Yeah. It's like.  When this storm passes, we'll obviously go out and check everything around our whole land, help out the community. And I'm honestly scared of what we're going to find. It's getting really bad. Well, might as well do something productive while we wait for the storm to hit, starting with cleaning my oven. Yep. Still windy. A little fridge makeover anyone? Ta-da. A clean oven, clean fridge, but how about a clean dog? Cute. She loves us, I promise. Good for dogs. Good to go. Good to go. After a few hours of cleaning, Jasmine heads out to investigate the storm. Yep, still stormy, but not too bad. As we wait for the worst to come, we stay busy cleaning the couch, staying up to date with the radar, and finally organizing all of our clothes. Jazzy even survived a trip to the outhouse. With two years of serious natural disasters, from forest fires to major flooding and our first hurricane last year, we seem more prepared to weather any storm, knowing that eventually the skies will clear. It's 9 p.m. It feels as though it's past now, and this cup of tea is kind of like a little reflection of what it's doing outside. It's kind of just relaxing now. A couple gusts here and there, but I feel like the worst of it was today. Yeah, yeah. It was intense for like a period, and then. Right here. You see that? Yeah, you get some gusts, yeah. But I feel like because we're so in the trees, even all the way around us, that there's not really any open area for the wind to pick up, you know? Get some momentum. Yeah, and it kind of changed path at the end I read to just recently. Oh really? Yeah, yeah. Wow. As it was passing over. I don't know who's looking out for us, but they are working overtime every hurricane season. Let me tell you that much, and forest fire season and everything else. Yeah. Just the last moment, I. It's been an entire year, and the vulnerability we experienced last year, we aren't experiencing this year, simply because we are finally at a stage with our cabin build that is comfortable and reliable in times like these. Off-grid power, no more pulling generators and giving them oil changes in the middle of hurricanes or polar vortex. Yes. It feels good. Whew, thank goodness. Yeah, I know. All we could belly ache about today was a little bit of rain and wind. Once a Category 5 hurricane, Lee made landfall as a post-tropical cyclone late in the afternoon, but its impacts were felt in Atlantic Canada long before then. Down trees, violent waves, and widespread power outages are just some of the ways Lee showed itself along the South Shore Saturday. The wind also left over 100,000 without power in Nova Scotia with tens of thousands also losing electricity in New Brunswick. I've never seen the water levels this high in our entire three years living here. This river and this stream is no longer. This is a wet land. This part of the land is flooded. This is insane. I have never seen it like that. Look at that. This is the trail we normally walk on. Not a trail. Crystal! It gets even worse. Come look at this. Oh my God. Okay, well, that's the lake that normally does not start there at all. The river is completely now a lake. All of these trees are never underwater. These trees are never underwater. Oh my gosh. That is part of the river that we swim in. You won't even know. All the rocks are underwater. You can faintly see them right there. Oh my gosh. Oh my gosh. This is where we go for our river swims. It is now a pond. If you see the treeline behind me back there, the river starts about eight feet after it. So look at how deep this is. It's Chris. This is insane. Oh my goodness. Hit the rocks. I don't want to go for our swim. It's so flooded. It's so deep. Oh my gosh.  While the water levels here are higher than we've ever seen, we are lucky to have our cabin well away from the water.  And our hearts go to everyone affected by the storm. Well, part of our land is a marsh, but what isn't a marsh is where our cabin is. Yeah, thankfully, because it's taken a few years and something I truly, truly think is overlooked by so many people when they first establish something or get a piece of off-grid property is- Or just property. Yeah, is water management and just understanding what it is throughout all the seasons and everything that it could endure like storms and stuff. Build farther back is what I've learned from bodies of water. Oh yeah, any waterways. I know, looking at a lake is nice y'all. I get it, I get it. I wanna be sitting on that Muskoka chair in the middle of that lake right now basically, but it's gotta go back. Yeah, and honestly looking around here at the cabin after the wild few days we've had, there's not much water at all. And where there is water, we are putting a French drain. So it goes to show that we're putting it in the right spot and we're finally at a place where all of our hard work of leveling and water management is paying off because there is no water near our cabin. So that's something to celebrate. Is it ever, right? I had zero idea about water management. No, yeah. You know, it could be like overlooked or it could be just simply you are not educated. I would say we are both not educated in the beginning and now we realize how important it is because we've dealt with water. Yeah, it always has to go somewhere, so. Well, sun's out. Tool's out. Let's get this sodding done. Yeah, let's do it. Once and for all. With our workstation set and the weather now clear, it's time to finish this project for good. The best part about triangles, they get smaller as you keep going. Do I ever have a lot of friends up here? Wasp galore, please don't sting me. Not gonna lie, a wasp came a little bit too close for comfort. So I took my drill battery and I went, boom. And now one of its family members is either trying to give a CPR or eating it. That'll let you decide. Oh, my son. The last piece. Looks good. That was a big sigh. Smoothie break. I basically did that entire wall myself. She's joking. It was a team effort. Here's a picture to prove it. My favorite side is finally done. And I have to say, it definitely did not disappoint. It actually exceeded my expectations. Exceeded. Oh, my goodness. Permanent smile, everyone. I can't even talk. I'm smiling so big right now. That is incredible. Just to thank this old, rickety, abandoned cabin. And now look at it, y'all. It's wild to think about how far we have come, from an old, unloved cabin to our own little remote paradise. And after too many weeks to count, working on the exterior transformation, we can finally take a breath and marvel out its beauty. Never in our wildest dreams would we ever think we'd have a home this beautiful. And the support of all of you, it's better than we could have ever imagined. Woo, woo, woo, woo. Thank you to Squarespace for sponsoring this week's video. With no prior experience or skills, you can have your very own website up within just a few hours. You can get started with one of their professional website templates, and then customize it to make it your very own to suit your unique needs. To have your brand, your idea, your creations, stand out on any device anywhere. You can sell your products in an online store, and they can be physical, digital, or services that you offer. With your new website, you can even accept appointments. Offer online or in-person private workshops, classes, or sessions. Are you ready for your website?