� citizens have no food to eat in these places ? ༼ Lind rồi conseguequinho , ༼aniu ็ຊຂງ, ༲NIEhhhhhhh ་ rode , ๋ 真的, it's completely demand. and i am lying בר評 Education work is done, My body had never been fed so much when i look at the books and read only. wast in ka barmaarth maa tha, mere vakeel par yu kar kumbhan ji, pd cobra hijita row bhoth tarrinn జ� unused 價품  SEÑ igne జ,  Guatemarank , జజ monese జజ the name జm జజ m జజ nani జజ m ॆIND


Hey, good morning from the Radiant City Center. Excited this morning to join with you in the room, those of you online. Gonna join and start in the scriptures this morning in Psalm 16. Just read a couple passages out of Psalm 16. The Lord is my chosen portion and my cup, you hold my lot. The lines have fallen for me in pleasant places. Indeed, I have a beautiful inheritance. I bless the Lord who gives the counsel and the night, also my heart instructs me. I have set the Lord always before me because he is at my right hand, I shall not be shaken. Therefore, my heart is glad and my whole being rejoices. My flesh also dwells secure. For you will not abandon my soul to shield or let your holy one seek corruption. You make known to me the path of life. In your presence, there is fullness of joy. At your right hand are pleasures forevermore. Just open up our hands to the Lord this morning.  And that you would runneth over today that these, the lines that you have placed in my life have fallen for me in pleasant places. And I have a beautiful inheritance in you. And I bless you, Lord.  You instruct me. I have set you before me. You are always before me. I've set my eyes on you today. And therefore my heart is glad. I pray for the swelling of the love of God to fill your heart. I just, just even the sense your heart swelling and enlarging with the love of God. We just receive an increase of the love of God this morning. We open up our hearts and our souls. Pour your love in us. Increase our ability to receive love today. Let our hearts swell, grow, and enlarge in love. And you make known to me the path of life. And in your presence, there is fullness of joy, not a measured joy, not a degree of joy. There is fullness. And we receive the fullness of joy. God, would you pour out joy on your people today? In the midst of difficult circumstances, in the midst of pain and loss, we say that you pour out joy. And there is fullness of joy, God. We ask, Lord, for greater degrees, God of joy in our life, not a happiness, not just a smile. I'm asking, Lord, for joy, joy, Lord, in us, in our inner being, God, grow us today. And at your right hand, our pleasures forevermore. We love you, Lord. And we bless you. We bless you, Lord. Can we just say that? We bless you, Lord. We love you, Jesus. You are before us. And we look and gaze and we lock the eyes with you today. We don't look to the left. We bless you, Jesus. Let us make a joyful noise to the rock of our salvation. Let us come into His presence with thanksgiving. Let us make a joyful noise. It is great. He is a great God, a great King above all gods. In His hand are the depths of the earth. The heights of the mountains are His also. The sea is His for He made it. I have a burden today that we're going to intercede. I'm reminded in Exodus 33 where Moses says, do not send us up from fiction here at radiant for a presence and a desksgiving. So let's just come in with that posture today. Coming before the Lord and saying thank you. There's a thanksgiving cry and spirit and posture and response to your presence. And we say thank you, God. Thank you for the way that you are the rock of our salvation. Thank you that your presence is forevermore. It's eternal. And God, it has saved us. And God, we're crying out as your people believe on your people that this is going to be the latter rain. There's the former rain and there's the latter rain. And God, we're believing for a pouring out and a refreshing of your spirit and of your presence in these days. God, that there will be a refreshing of rain and a refreshing of your presence on your people. God, we're in great need. God, that we will be marked by your presence. And we today respond in thanksgiving to your presence. So God, we say today collectively, your saints, that we would lift up a joyful noise. The team's gonna lead us, but I would love for us to have our voices in the room if you're in a car or at home, but we're gonna respond joining together musicians and our voices in thanksgiving, making a joyful noise to the Lord. Let's respond to him that there will be an overflow.  We remember how you redeemed us, sucked us out and you have put us on the steady rock of God. Is the spirit of overcoming. So we remember as at Meraba, as to bow down to the Lord and we would come before the Lord this pastor and the sheep of his hand and there today that we would, when it talks about Meraba, it's talking about quarreling from Exodus 17, things that resist God, rather we resist the enemy and he will flee from you.  And God, we say that we will not put you to the test and we humble ourselves voluntarily. It's not just in the act of kneeling low.  And we say, God, would you humble us as your people that we would not have hardened hearts today and we wanna hear your voice. We say, release your voice over here. Release your voice right now. We say, soften and tenderize. Just convert these things into prayer, tenderize my heart, soften my heart. Create a low spirit within me. Cry before you Lord, share your presence.  We ask, we cry out, God, we need your presence in this day. Let there not be hardened hearts invite you even into that groaning desire more. We're desperate for more. If there's crumbs before you, God, we wanna, we say, yes, we'll take the crumbs. Whatever we can get, God, we want more of your presence, the church God. And as your children, God, I pray that there will be a holy gripping of the fear of the Lord that we would not harden our hearts as in the day of rebellion. Do not resist you, we resist the enemy. I pray that our hearts will be soft toward your spirit and how quickly we can drift. How quickly we can become cold.  Finding many, growing cold. And God, I am praying. And it says to stand in the gap and there's a purpose in the posture of our response to God that we go low. And it says to stand and stand in the gap. In James five, it says, is anyone among you suffering? Let him pray.  And if he has committed sins, he'll be forgiven. In verse 19, my brothers, if anyone among you wanders from the truth and someone brings him back, let him know that whoever brings back a sinner from his wandering will save his soul from death and will cover a multitude of sins. I'm believing right now that we're standing in the gap for those that we know that are even growing cold. Maybe they're in belief of God, but they're growing cold. Maybe they're losing their faith. First Timothy four says in the latter days, some will depart from the faith or they begin to wander. And we're gonna stand in the gap for anyone that is sick, anyone that is suffering. And by the prayer of faith, we're asking God to intervene. And so I'm inviting you to stand in the gap right now. And we're gonna believe and call on the name of the Lord, those that are growing cold, those that are hardening their hearts, those that are departing from the faith, those that are wandering that we would war in truth, war by the spirit, not in the ways, not in the ways of weapons, but God, we say in the weapons of our warfare, which is in the spirit and by the spirit and by worship and through prayer and intercession, God, we say those that are growing cold, those in our families, parents, siblings, cousins, aunts, uncles and grandparents, God, we war in faith and by the prayer, those that are departing, those that are being deceived, those that are being indoctrinated by demons, we say that that would be cut off in the name of Jesus. And we say that you would reveal truth, that you would soften hearts, those that are wandering, those sheep, the ones that have wandered off, God, would you go and pursue them, find them and bring them into your bosom and that you would return them first. And we need intercessors to stand in the gap. We are the sheep of your pasture and there have been wolves. There have been wolves that have cloaked themselves. The breakthrough happens.  There's each one of us should have one person. We may not get through the whole line, but a one sentence prayer, together, those that are salutes rapid fire this, the grip of addiction. Lord, I pray that you would remember your son, Amos, that while I pray that you would soften her heart and bring her back to you. God, I pray for my friend Luke and I ask that you would break addiction and party culture off in his life in Jesus' name and would you bring him back to your kingdom? For bill, Lord, would you pray to the idols of science and self and reveal yourself to him in Jesus' name? Jesus, I pray for Shondra. I pray that you would break witchcraft off her life in Jesus' name and that you would break addiction off and reveal yourself to her. We just break off culture and just the things that she has just died to you there, Lord. I pray that you would bring her life. Lord, I pray for Elijah that he would come running to you for his identity and stop finding his worth and things in this world that instead find him. God, I just pray for Colby Jesus, Lord, that you would break off any religious trauma, Jesus, any spirit of witchcraft, homosexuality, Jesus, and addiction. She wrestles with you and us. Her heart is cold, God, would you just stop when her heart would she choose you? Break in with the power of the love of God and you would break off all chains of depression and hopelessness and fatherlessness. God, I ask that you'd be his father in Jesus' name.  Jesus, I pray that you would break the spirit of anxiety off of Emma and that you would break off any bitterness towards you and towards the church and you would bring her back to you in Jesus' name. Jesus, I lift up before you, my Aunt Sherry, Lord, and I ask that you would soften her heart, free her from an idol of self and free her from religion in Jesus' name. Her past relationship with you in Jesus' name. The heart of the prodigal and bringing back to you. Yeah, Father, I pray for my cousins, Austin, that we got to ask that there be a dissatisfaction in their spirit from the world and you bring them back to you in Jesus' name. God, I just pray over my sister and her family, Father. I pray that you would break the spirit of bondage off of her, an idol worship, Father, and I pray that you would reveal yourself to her in truth. My brother right now, Patricia, I just pray in Jesus that you would just encounter him right now, pray that you bring him back, back to you, Father, I pray that you just show him. Father God, I pray over Lauren and I just pray that he would break off every invention over her. I pray for Jake, Lauren, I pray off the chains of addiction to Jesus and I just pray that he would run into the arms of his loving Father. For my cousin, Zeke, right now, that you would just show your love to him and that there would just be breaking off of just the fear of just break off and he would come home back to you.  Thank you for standing in the gap and we're gonna close just in this song that we were singing that chorus. Those that have gone astray, that we're believing in faith. Even as we worship, it's a song of intercession that we're believing over every name that was prayed and on the microphone, let's sing this together as we close. God, those that are not standing on the rock, would you save them? God, would you intervene in their lives and save them? We pray, God, for every soul that was prayed for here and God, help us to care and to intercede and to partner with them in prayer even beyond this moment. God, that you would, we would partner with you in the bird. Everyone said, amen. Hey, great to be with you here, praying, love it. Thank you for the muscle of intercession and joining together.


Clencher, are you ready? Yes. Clencher, are you ready? Go. Clencher, are you ready? Yeah. Clencher, are you ready? Are you ready? Yep. Clencher, are you ready? Right. Go. Pumble, pumble, pumble. Don't disengage. Close distance. Close distance. Don't disengage. Clench. Good job. Nice arm drag. Ready. Clencher, are you ready? Cool. Go. Come see me. I do strong sit. Good? Ready. Clencher, are you ready? Clencher, are you ready? Change your angle. Change your level. Clencher, are you ready? Right. Your feet circle back.


My background is actually really diverse. I started as a jazz saxophonist, and so I was very, very lucky at sort of a young age. My music education was actually not formal lessons, but just picking up my saxophone.  It was a very good kind of education because it wasn't something where there was a classroom that was separate from the professional life of making music. And that was very, very important to me as sort of growing up as a young musician and artist that it was always only about making music. And the learning process was in the process of making music. They weren't two distinct things. It wasn't sort of a time that you practiced and studied with a teacher versus a time that you played concerts. There was just, for jazz musicians, there's only concerts. There was no practicing. I only have one goal, which is to have the top music program in Australia and to launch multi-media composition, electronic music and audio engineering program that's unlike anything in the entire world. I want us to be the global center of multi-media composition, electronic music and audio engineering. And it's important that we create an environment which the student can cultivate an authenticity and a truthfulness to the things that they're passionate about, and they can develop the courage to pursue them and we can give them an environment in which they can learn and pursue their own learning as strongly and as passionately as possible. I'm always listening to something that touches me emotionally and then I can learn something from in terms of audio production. I'm still as fascinated by it as I was when I was nine years old and I heard the first jazz saxophonist improvise. My mother brought me to the library and I heard my first live jazz for the first time and I saw the saxophonist improvising and my mind was just blown because I could not understand where that music was coming from. And my entire life from that point on has been trying to figure out where it all comes from. And even though I've had sort of the finest education and pedigree that money can buy, I feel like I'm no closer to the answer, but I'm just as enthusiastic about the journey.


I can't tell you how many times I've talked to people who said I can't overcome this sin or I can't change this thing about my character or I'm struggling in this area and I tell them you need to seek the face of God you must get into the place of prayer and they go back and forth and back and forth and though their prayer life is inconsistent they expect their spiritual strength to remain consistent. How is that possible? If your prayer life is up and down you will be up and down.


I'm Eric Peterson, I work at Time Warner Cable, this is Matt Fisher. We also, today we're missing Clayton O'Neill, Clayton wasn't able to make it today, but we owe him a big thank you for putting this presentation, a lot of it together, proposing it and doing a lot of this work. Matt and I are both principal engineers and I do a lot of the horizon stuff, Matt does a lot of automation stuff as well. So a little bit of background about Time Warner Cable and our journey with OpenStack. We started in November of 2014, there's a team of about four of us, so it's a fairly small team and as you can imagine when you're first starting with OpenStack you've got a lot of decisions to be made as far as what is your network going to look like, what is your storage going to look like, picking out vendors, all kinds of different things that you need to go through as you're deciding, you know, how is our OpenStack deployment, how is it going to look like, what's it going to look like. Another piece of information here, we went to production in July of 2014, last year at Atlanta we were moving from, what was it, Havana to Ice House, so there's quite a big move that we were going through last year to try to upgrade everything, get everything ready for real production deployment. Something that's kind of interesting as well is our CICD infrastructure didn't really start to mature and develop until we were actually in production. And so it's kind of maybe doing it again, maybe we would have that maybe before we were fully in production, but it's important to know that once you get OpenStack in production you need to be able to figure out how do we make changes to this, how do we configure this, how do we keep on pushing new features forward, how can you do that in a way where you're not going to impact users, where you can keep things running smoothly and keep everybody happy. Some more information here, some numbers for our CICD stats. We've got over 4,300 reviews on our Garret instance, so this is an internal Garret that we have, same kind of thing that you use when you commit code upstream to the OpenStack review system. We've had over 300,000 node pool slaves spun up. So these are individual machines that run jobs for us, anywhere from like checking code, compiling things, doing some QA stuff. These nodes could even be used during a deployment also as well. We've done hundreds of deploys, thousands of line of puppet, Ansible Python, tons of that stuff. I don't even know how we could even count all the different stuff like that that we use. So this line here, over 16,500 lines of upstream changes. That number is probably a little bit old. I think a week or two ago we were over 17,000. So we try to contribute back to the community quite a bit, as far as changes that we see that we think everybody would benefit from. We try to share our work. This is a little bit more of an overview about what we've got for our production and our staging environments, our developer environments. You can see on here we've got production and staging over there on the far right. They look fairly similar to one another as they should. Over on the left we've got developer environments and these are more like a virtualized version of this staging and production stuff. And in the middle we've got Garrett and Jenkins, our infra stuff that we call our infra that help orchestrate all these changes. So I'm gonna go and drill down a little bit more into what we've got, into what our production environment looks like. So we've got two regions, you can see in the large periwinkle squircles. That's a UI term, Matt. So we've got two regions and up at the top we- That's right, periwinkle and squircles, both, yep, I'm the horizon guy. Yeah, so at the top we've got Keystone and Horizon. They share a global glare cluster that's shared between both regions there. So those nodes, you can tell we've got three nodes in each region. Seems to be fairly straightforward there. We've got HE Proxy, which helps front all of our API endpoints. And then we've got our control nodes. Our control nodes down there, that's really where a lot of excitement happens. And that's where Nova, Neutron, Cinder, Glance, all that good stuff is going on. And you can see also we've got the clusters there for my SQL and Rabbit and just note that those are just within the region. They do not span the region. We've got compute nodes and stuff nodes down below, we've got more nodes and more types as well. This is just kind of the basic common node types that we kind of refer to when we talk about different components within our cloud. And then at the far corners there, we've got our build servers. That's our Puppet Master servers. They also run a lot of our Ansible jobs and help coordinate things. They also work as Cobbler servers. So when we're bringing in new hardware, getting a new machine kind of bootstrapped and ready to go. They work with our build server to get a lot of their information. So stepping back to this previous slide that we talked about. First we're gonna talk a little bit about this virtualized developer environment. And you can kind of see that the staging and production blue boxes there, they kind of look the same as what we've got over there on the left hand side. And so we've got a virtualized version of our production cloud that each developer can deploy and use and do whatever they want to with. So a lot of the developers will have a project. You can kind of see the team member box up there, squircle. You can view that as kind of an open stack tenant or project. And then a developer is gonna stand up a lot of their infrastructure. And they can even have two regions within their development environment. A little bit more about our virtualized development environments, they're based on Vagrant. And there's an open stack provider for Vagrant to help you stand up VMs. One of the things I hope that you're seeing here is that a lot of the environments are built with the same tools. So when you stand up your development environment, you're using a lot of puppet, a lot of Ansible, same kind of stuff that we're gonna use when we get to production. And so developers should be doing the same kind of, the same mechanics, the same stuff using the same tools all the time as they go from their development environment into kind of our staging, into our production. All these things should be consistent. Team members can have multiple environments. So yeah, as many as you want. And you can kind of pick and choose which node types you want. So this really depends upon the task you're trying to do. So if you're trying to change something within Keystone and you've got your own virtualized development environment, maybe you only need to stand up some Keystone nodes and a couple of other things. And you don't really need to be too concerned with compute nodes. So you can really pick and choose kind of what you need in your virtualized development environment. The other thing is that they're shareable, right, for trouble shooting. So if I have a problem in my environment and there's some crazy puppet thing that I don't understand, I can give it to Matt and say go take a look at it, I don't understand this error. The other thing that we'd like to talk about a little bit is our Garrett system. So Garrett is the same tool that you use when you submit code upstream to OpenStack. So you put code up for review, everybody else can take a look at it. There's some extra jobs that run on it. So we have our own version of Garrett, a lot like what exists upstream for OpenStack Infra. Some of the different aspects about doing code review. And I'm sure that if you contribute code upstream, you can vouch for a lot of these things. But it helps the code quality. I know if I've got to put code up to get it checked in and somebody else has to look at it, I'm going to take a little bit more time to make sure I don't make too many obvious, terrible mistakes. The other thing is mentoring, shared ownership, and also some pre-merged testing, some automated testing to be able to look at your code and kind of be able to do some tests to say like, is your change, does it look reasonable? Is it going to do the things that you expect it to do? One of the important things, if you're going to run a Garrett server like that, you're going to have this process. One of the things that's going to be very important is to have your own Jenkins instance to be able to run a lot of automated jobs. So we've got our own Jenkins instance. And it actually runs the build slides that are actually supporting Jenkins. They actually run in our staging and our production environments. So we're eating a lot of our own dog food here and we're kind of our own consumers as well. So something that, another tool that we've used with Jenkins is node pool. So I'm not sure if everybody knows about this, but node pool is a, it's an open stack infra component that you can use. And it enables Jenkins to have many, many build slaves as many as it needs. It can spin them up, it tears them down. It does all kinds of things like that. So early on that number slide that I went back to, I think it was 300,000 build slaves, those are all served up through node pool. So node pool continually gets a VM ready for Jenkins to go do some work with. The other thing that we noticed there was, we encountered an issue where node pool would try to reuse the same virtual machine over and over again. And so we had to write our own Jenkins plugin to help with the scheduling of node to make sure it doesn't get reused. So node gets used once, it performs a job, whatever you need it to do, compile, whatever, and then it gets thrown away. And so this Jenkins plugin that we have is on our GitHub repo and it's offered for other people to take a look at, reuse, do whatever you want with. The other thing about Jenkins is when you reach a certain scale, when you're first starting with Jenkins you might use the UI to build a couple of jobs, you'll go into the, it's got a nice little GUI, whatever, you type some things in, it's fine. When you get to the point where you start to have hundreds of build jobs, this UI stuff is no longer a tenable way to get work done. So we use Jenkins Job Builder, Jenkins Job Builder. It's a YAML based file format and you get to declare your jobs. You can reuse a lot of the same kind of macros and different things like that. And so it's worked really well for us to be able to create a lot of different job types, have a lot of reuse and a lot of commonality. To be able to scale up to really some big, large complex Jenkins setups. Our Jenkins Job Builder configurations, they are also, even when you wanna change the job config, that also generates a review. And what we check in to get for our Jenkins Job Builder configuration files, that's also authoritative. So in other words, Jenkins is gonna perpetually kind of continually go out and check, get and say like, do I have the right job configuration set up? Am I deployed? Am I configured correctly? And we've got that all enforced and set up. So with that, that's next for Matt. Okay, I'm gonna talk a little bit about the automated testing we do. Eric alluded to a little bit of this earlier. The first is pre-merge tests. So anytime a change set is uploaded to Garrett, we kick off pre-merge tests. And we use this during using the Garrett trigger plugin for Jenkins. This is I think how upstream works. And if you've done upstream code, you know when you check code in, tests get run. We run some basic tests, puppet lint syntax, basic unit tests, we run talks tests, the type of tests, of course, depending on the repo you've uploaded if it's puppet code or Python code. One thing that's a little unusual that we do is puppet catalog compiles and diffs, puppets are really big part of our process. And so we have some of a specialized tool that Clayton really worked a lot on. And I want to kind of go into more details on that. So I know not everyone here is a puppet person. So some basic background, puppet, the puppet build server, puppet master essentially compiles a catalog for every node. The catalog consists of things that puppet is going to do. So packages that need to be installed, services that are supposed to be running, configuration options, things like that. To get that catalog, the input is puppet code, which we haven't get. Puppet config, which we use higher for, which is also in get, and something called fax. And fax are bits of information about a node that are specific to the node. Like an IP address, a host name, how many CPUs it has, the manufacturer, things like that. We actually collect those fax every day and store them in a database. And so since we have the code in get, we have the config in get, and we collect these fax, we can let Jenkins do a before and after catalog compile for every single node type in our environment. So what does that get us?  Then it applies your change, and it builds all the catalogs again. Then we use some RIPaneers, and apologize for the pronunciation. Puppet catalog diff module to essentially generate a diff and tell us. Eric promised us that this was, puppet change was only going to install one new package, and I see 30 other things in there. We might have to have a conversation about Squirkles or whatever Eric likes to talk about. This is an example, it's a pretty basic example. This was from a massive refactor that I did recently. I think this is over a thousand lines of code. Most of them were deleted, some of them moved around. What's interesting, if you look at the arrow, you can see the following diff files were generated and the list is empty. So for a refactor, this is exactly what you want to see. No diffs, no changes. We see this and we're pretty sure that we can just probably deploy this and we're not going to have any problems. And this was deployed a month ago, so I'm pretty sure it's working. For locally generated changes, diffs are pretty cool, and what the real benefit for is for external modules. We have over 70 puppet modules, a lot of the open-sac ones as well. We try to keep them updated at all times, but there's just hundreds of commits. And if you want to go update these modules, even if it's just ten of them, and you want to keep them up to date every week, you just don't have time to read every single diff. And so we really rely on this catalog diff to tell us what the heck is going on. What are these 50 changes in Puppet Nova? Are they going to break us? Let's go look to the catalog. You can see here that we actually have a diff list. We see this Puppet Nova change is going to affect control and keystone nodes. So let's actually dive in and look at a real diff from a control node and see what is in this change set. This is the change set from a control node. Again, there's two sets of changes here. They're highlighted in yellow. The bottom two set is the default database collate type changing. This was a discussed upstream in the Puppet mailing list and in meetings. So I knew about this change, and this was fine. We were okay with this. The other change is the no-vnc-based-proxy URL. I actually not really sure what that is, and it might be something that would break us. I need to know is it changing the default, or is it removing it, or what? So this is one where I'm going to go back to this module and look at that commit for the no-vnc-based-proxy URL. But the other one I'm cool with. So what are the pros and cons of this tool that we've created? The first real pro for us is we can validate all the code in all of our environments. We do a rolling deploy to dev staging prod. We don't want to find out that a change we made breaks prod when we're in the middle of a deploy. We want to be sure that this catalog is going to compile on a production server and not have to debug it later. Finally, if you compare this to simple syntax checks and unit tests, we get way more detail, more information, and it's a much more valuable tool for reviewers. Right now, in terms of speed, we generate before and after catalogs and diffs for over 50 node types. And we can do that in about four minutes. That's way faster than an integration test. It's not an integration test. But we don't want people waiting hours to be able to check code in. So this is kind of a good pre-merge check start for us. There's a couple of things it doesn't do. Puppet modules also tend to have a lot of Ruby code for providers. You can't debug any Ruby code in this. You also, this one's very important to us. You don't know when a puppet change is applied. It's not going to tell you that it's going to restart a service. It's not going to tell you that it might upgrade a package or install a new package. And finding out things like rabbit is going to restart. We need to know that before we go to production. So that leads into the next kind of testing we do, which is our integration testing. About two months ago, we started doing some basic integration testing. We basically build up, using the virtualized environments, our base node types. The Puppet Master, which is called a build server, a load balancer, a keystone node, a control node, and a compute node. We're basically just testing to these nodes build. And what I mean build is, you spin up a raw VM and Puppet runs and lays down everything. So on a keystone node, that's a full keystone environment, full MySQL, and everything. When Puppet is running on these nodes, Puppet is actually talking using the OpenStack APIs. So it does give you a slight good sense that OpenStack is probably going to work on these nodes. But we're not really in depth into what level of testing we do here. We do this using the node pools, multi-node slaves.  You can't bring up the load balancer node until the Puppet Master's ready. And you can't run the control node until the keystone node's ready. So we've actually kind of written some Puppet code that'll bring these nodes up, and if keystone's not available, it'll essentially pull until the keystone node is ready to go. Right now this takes about 45 minutes. And again, it's a post commit, not pre-commit, which is not ideal, but we've actually found bugs this way and caught them before we go to production. What we really want to do in the future with this is add a bunch more testing and be able to go look at the Puppet runs and figure out this service is going to restart. This package is getting it upgraded. Those kind of things. What we'd also like to do is this runs every hour right now.  When this test passes, it automatically gets deployed. That would be our eventual goal once we have more testing here. I do not understand the animations on this slide, sorry. You need some help with squirtle. We've covered our virtual environments for deployment. We've covered code reviews, Garrett. We've covered our pre-merge and post-merge testing where we use Jenkins and node pool. So let's talk about how we actually manage this code for Puppet and for OpenStack. For some Puppet config info, we have a Puppet master per region, per environment, so that means we have a prod East Puppet master. We have a prod West Puppet master, same for staging and dev. We're not using the dynamic environments. We just run everything off a single master branch for now. We minimally use Puppet DB, SSH keys, or SSH known host keys, and some Icinga exported resources go there. We use HiRA for environment-specific changes. This might be a prod versus dev change. This might be an East versus West. East and West have different NTP servers, for example. For any secrets like passwords and SSL certs, we use HiRA e-AML. We don't want decrypted secrets in our get tree. And R10K is actually what's responsible for downloading all the modules and installing them and maintaining the right versions. So how do we do that? We have a repo called PuppetConfig. This is a single master repo. One of the big pieces here on the left you'll see is our HiRA data. The other two important files in here are Puppet files. Once you combine these, this is really what controls how things get deployed and what gets deployed to a different environment. If you're not familiar with a Puppet file, it's essentially a Ruby file that contains a URL to a get repo and a tag or commit number. And tools like R10K just walk through it and essentially get clone the URL and get you on the right version. I'm going to talk a little bit more about Puppet file YAML later. That's kind of something we added on. First, let me go through. This is what a Puppet file looks like. I'm not going to explain all this, but it looks pretty basic. You can read it and tell what it's probably trying to do. But what about Puppet file YAML? Why do you guys have that? What's it for? What earlier I said, Puppet file is actually Ruby code. And so we added the thing at the top of the Puppet file to dynamically load a Puppet file YAML so that we can have both of these. And the reason we have Puppet file YAML is that in the old days, if you checked in something, if you updated the Puppet module, your change got accepted into master. But it wasn't going to get deployed until you made a second change in this repo, changing the repo pointer that I talked about earlier. That's kind of annoying. It's actually really annoying. So we actually wrote an automated Jenkins job that any time a Puppet change is made and checked in, the Jenkins job goes back out and modifies the Puppet file YAML. This format for a file is just a little easier for us to deal with.  So we can tell what possibly broke if we're having a problem. In terms of the actual deployment, the only thing that R10K is using is that Garrett URL in the ref. Everything else is just for our purposes. So that covers how we do Puppet. But what about OpenStack code like Horizon, HeStone, et cetera? I'm going to let Eric cover that. Yeah, deploying OpenStack code. So we run on Ubuntu, and we use Ubuntu as the Cloud Archive repo for all the packages. So when you're installing things with a Debian package, it's nice in some regards. It installs things, it manages versions, it gives you some default configurations. It'll start the service for you. It'll maybe set up the database in some cases, whatever. Some of those things are quite nice. Sometimes they're not as nice. So in our case, we want to control if a service is going up or going down. When is it going up or going down? And if it's going to touch a database, we want to know when that's going to happen, if it's going to be changing anything about the tables. So we've had quite a bit of success using the default packages from Ubuntu and canonical, but they haven't always been completely ideal in every situation. So the first thing we did is we tried to build our own version of Keystone. Matt's lucky he's got a background working with building Ubuntu packages. So he's very knowledgeable in this stuff. And this was a task that he took on. But building your own Ubuntu packages, or Debian packages, whatever, it's not without pain. So you've got to chase down all the dependencies. You've got these archaic build tools. It can become quite a time sink after a while. One thing we also used is PBuilder. It was driven by this Jenkins, Debian Glue that we found is a helpful thing to help us make progress a little bit faster. So that all went pretty well. We were able to build our own Keystone packages and get those deployed. And now it's time for me to maybe disclose I've been working on Horizon for maybe three years, maybe a little bit more. And I'm familiar with doing Horizon in a certain way. And so when I deploy Horizon, I usually put it in a virtual environment. And you'll hear virtual environments and containers and all these different similar concepts talked about quite a bit at the summit. But when we deploy things, we deploy Horizon in its own virtual environment. And so when we do that, we set up the Horizon base known, gets Apache installed, and some basic configuration. And that's all done via puppet, basic stuff. And then Ansible will come along. And Ansible will go out, and it'll set up a virtual environment for Horizon to run in.  And so what does it look like, if I can show you an example, this is what one of our Keystone nodes looks like. And as you can tell, you can look up there and you can see maybe 10 directories, something like that. Each one of those is a Horizon deploy. As part of my deploy job for Horizon, I make sure that the last 10 are retained. And then when you look down there at the bottom, there's a current and that's a sim link pointing to the most current deployed directory. So by doing this, I'm able to deploy more than one version of Horizon at a time. If I have a bug or there's a problem, I can switch that sim link out. I can have it done in a matter of seconds. I can go forward. I can go backwards. I can deploy things within a matter of minutes, if not faster. The next thing that we tried to do with virtual environments, we've started picking up designate and deploying designate in our environment. So designate was kind of this new thing that we weren't really sure about. And so when you're deploying a new component within the open stack, this behavior that virtual environments and isolation that they provide is kind of an appealing thing. And so we've done that with designate. The designate work was largely based upon the puppet designate work that's upstream. So that was a fantastic starting point to get us going. But what we did is we've kind of forked it a little bit, kind of taken our own little patch to make it so designate can run in its own virtual environment as well. This is a patch that we're kind of holding back right now, just because it adds quite a bit of complexity. It's not really necessarily something that the community might be ready to grab on to 100%. But we'd certainly be welcomed to, we'd welcome any discussions and be interested to participate in moving it forward. The other thing about using virtual environments is you're going to need to take on some more tooling things too. You're going to need to have maybe a way to capture some, like a Pi Pi mirror or something like that to help make sure that you've got all the packages that you need and manage those things. So I think we promised you, we actually talked about getting code on the boxes at some point. So we're probably going to go into that. We've actually walked through our whole process now and we're ready to talk about getting Eric's virtual environments or packages onto environment. We deploy to a shared dev environment to the middle screen, that's five or six times a day as needed. And then we do a boring, weekly deploy that never has any problems. That goes to, my team's laughing, that goes to staging production generally weekly. We do those based off of tags. So we make a tag and we deploy off the tags where we know we're at a certain point in time. We know exactly what we're going to get and we're not holding back master. But how do we actually do this? Our starting point is Jenkins. Jenkins provides a great UI and Jenkins is really used to drive Ansible. It gives us access control, audit control, and allows multiple people to sort of share and looking at the output, what went wrong or what went right. We also use Jenkins pipelines to handle the two regions. So press the button on one region, wait for it to finish, and then we go on the other region. Ansible is actually there underneath. That's what Jenkins is wrapping. Ansible updates the puppet repos, gets all the new modules for us, handles node ordering, which I'll talk about later, and runs some pre and post health checks. You may remember Eric's discussion of this slide beginning a talk. I'm actually going to walk through this slide sort of piece by piece and tell you when we have a piece of code, where does it start and then who's first and then what's the ordering. So the first step here is we turn puppet off on every box in both sides. We let the run finish and we completely turn it off. We ended up having to do this because we learned a lesson basically due to the shared Keystone Horizon Cluster. If you update one region and you put new code on it and you run Puppet on your Keystone node, it might be doing something like changing an endpoint. The other region Puppet's still running, it's got the old code, it's going to be changing the endpoint back to what it thinks it should be. And back and forth, and it's essentially Puppet arguing with itself. So the first thing we do is shut off Puppet everywhere, wait for all the runs to complete, and we're ready to go. The deployment starts in the build server. That's where the Puppetmaster runs. Ansible updates that Puppet config repo we talked about to point it at a specific tag. And then R10K walks the Puppet file that we talked about and checks out all the right versions of all the modules that we want. They go to the pin that we want them to. After that, Ansible runs Puppet on this node to bring it up to date. Hopefully if anything really horrible has gone on, it blows up now. This is a box that frankly we could lose and rebuild in 20 minutes, and it's not a problem if we completely mess it up. But build servers actually usually don't have any problems, so we move on to the next node. We go to the load balancer first. One load balancer. We don't want to do two at a time. We don't want HA proxy or keep live D restarting at the same time. And even better, if we break the node, we want to break one node and not both nodes. Once that works, because load balancers usually always succeed as well, we go to the second load balancer node. OK, now we get to the interesting part. We hit the first Keystone node. Now Keystone has this Galera cluster, which we talked about before. So we actually have health checks built into Ansible to check the health of the Galera cluster before and after the Puppet run. We want to make sure that if we've messed up Galera on this node, that sort of doesn't spread across everywhere else. Puppet runs, the node's updated at this point. And we basically do the same exact process on the remaining two Keystone nodes one at a time. OK, more interesting thing. So the control node is very similar to the Keystone node. It's also part of my SQL cluster. We also want to run nodes one at a time. We really want to make sure, especially here, because we might be changing like a neutron config that everything is good. So we checked status before and after. And we roll through these nodes. For the compute nodes, the compute nodes are actually pretty safe. There's actually not a lot of packages on here and not a lot of services. And we have a lot of them. So this is a case where we do run in parallel. We think we run 20 at a time. And it's just because we don't have all data to make everything serial. And we haven't really had any problems with compute nodes. We do stuff nodes. We do these one at a time currently. We just don't have enough, we haven't put a lot of time into the ansible checks. I think if we did, we could parallelize these a little bit, especially as we grow our self-cluster. This is taking longer and longer. That's something I'd really like to make better. I'm not showing you some nodes in the diagram. I'm not showing you Swift nodes. I'm not showing you our single node. There's probably a couple others, maybe. Manaskar nodes. We just ran out of space. Once that is complete, and this region is complete, we run some automated verification tests. At this point, if we've blown up this region, we still have a little bit of hope. We still have another region that we don't want to blow it up. So we want to make sure everything's valid. VM's spin up, everything looks good. I'm assuming there's no problems found. You just go to Jenkins, press the button, roll through the next region. I'm not going to go one by one, but it basically follows the exact same pattern. Again, we finish. We do a full validation again of both regions to make sure we didn't break anything. We do have some options when we do deployments. We have the ability to deploy to specific nodes, so that process you saw walking one by one can take a while. So we want the ability to say, this change only affects the build server. Deploy both build servers, leave everybody else alone. Or if a deployment fails for some reason, we say, we got halfway through. Let's restart at this point and not waste time. We can also force Galera or Rabbit to restart. We've done this during upgrades or my SQL changes. We also have the ability to trigger a managed reboot. So Puppet will sort of, especially for updating the kernel, we will update the kernel, reboot the box, and we'll wait until the box comes back online until we move to the next box. So that's our process. We actually have a lot of things we'd like to make better. The pre and post health checks at Ansible Doves are really cool, and we really just haven't spent enough time on them. Rabbit Cluster, we have a lot of problems with. I'd love to know that we've blown up Rabbit before we've blown up the entire cluster and people start getting paged, and that's the next inevitable thing once you blow up Rabbit. So Ceph's the same thing, Ceph health checks. Brian's going to get those for me. And we'll find out if we've changed something to Ceph and the same with Swift. The other thing I think our team would really appreciate is more parallelization, just to make this whole thing faster. Ceph nodes again, Swift nodes probably as well, could be run in parallel, especially as you grow your cluster. Serialization just becomes painful. Finally, we really want to be able to do more targeted deploys. So I talked a little bit earlier about integration, my integration test, looking at the catalog and saying, this is changing, this is not. I would love to be able to tell from a deploy, this is only going to affect Swift nodes. And I'm 100% certain of that. And therefore, we can only deploy it. We only have to deploy to Swift nodes. And if we had that ability, the guy who owns our Swift cluster, he could do all the deployments to his cluster. We could say, yep, it looks good. He can do the deployments. He could be responsible for checking the health. He could manage all that. Right now, we just don't have that level of visibility, we're trying to work towards it. Finally, the release note process for us. What is in this deploy? What are you changing this week? Manager asks us that all the time. This is a painful process that our team has to do. You involve looking at JIRA, reading Git logs, harassing engineers who didn't properly make tickets. And this could really use some automation tooling. OK, what you've seen today is our entire process from beginning to end. You spin up a virtual environment. You make a code change. You submit it for review. Premerge testing, integration testing, and then deploy to the shared dev staging prod environment. And then finally, it's verification testing at the end. So hopefully, at least some of this process is interesting to you, or maybe you have the same problems we do. So that's it. Maybe there's any questions? We'd be happy to answer them. I know you have a question. Can you put the slides up anywhere yet? I have not. I'd be happy to put the slides somewhere for you, Med. I think you're thinking of Mike Dorman. We definitely use a Puppet Master. Yeah? Yeah? Yes, that's fine. But we do use a Puppet Master. Yep. You talked about Ansible and Puppet at the same time. Can you clarify for which tasks you use Puppet, for which it's better to use it? That's a really popular question. So we feel we use each tool to their strengths. We use Puppet to configure servers. We use Puppet to provide things that need to be run automated on a regular basis. We use Ansible for things that are more like, I want to do this thing. I want to do a deployment. And Ansible runs out, manages the deployment. We also use Ansible for things like upgrading OpenStack. We use Ansible for things like managing, upgrading databases. We also have a bunch of one-off Ansible jobs, like if we have a compute node die, we have a way to evacuate all the VMs off the node safely, that kind of thing. If you need to do things in a certain order, Ansible's pretty good at that. If you need to make sure they're in a certain state, Puppet is good at that. Yes? Yeah, you use Job Builder, which is awesome. What do you do to make that master a little bit more stateless in terms of shipping logs out, if that's your dashboard, to let you know what's rolled out? How do you sort of escrow those logs? Have you tackled that problem yet? We have not, I don't think. So I'm sorry, what was the question? So you let Jenkins, configured by Job Builder, orchestrate all the things? Yeah, so we use Jenkins Job Builder to configure Jenkins. Yes. Do you do anything to get those logs off of Jenkins, to let you know what's on the runway in the state? We should, because they fill up, and you have to basically trim how many you can keep. I'd like to do what Infra does, which I think it is push all the logs off to another server, Swift or something. OK. And then as far as shipping relocatable VMs, what do you do for the PyPy dependencies? Do you just run an internal PyPy mirror, or? Yes, we don't mirror all of PyPy. Correct. So we don't have enough, that's a lot. And so we mirror, for example, for the designate virtual environment, we mirror what you need for designate and for horizon, we mirror what you need for horizon. We've got a certain repo, and if you check in a text file there, we'll go through that. We'll treat that as a requirements.text. And then we'll build a repo based upon what those requirements are. And so you'll want to provide us a pinned down version, so you do like a PyP freeze. And then you'll just check in that as a text file, and then we'll build a repo for you based on that. And then we'll keep all those wheels around. That's one more. So the question was, in the shared hardware dev environment, do we deploy the tagged version that's about to go weekly? We actually don't. And I think we probably will, especially with that integration test, we could go into Jenkins and say, run an integration test with this tag, and then we could go back and say, we expected these things to happen, and that's definitely what we see in the logs. That's something we want to move to. But generally, the shared dev is kind of ahead, because we tag off, and then maybe we don't deploy to the next day. We don't want to make everyone wait. We deploy master to share dev five, six times a day. Right now it's ad hoc, but eventually I think it'll be just on a per-check-in basis. For the benefit of recording for YouTube, if anyone has another question, please pose it from the audience mic, or have the speaker repeat it. Thank you. Anything else? Oh man, it's a lot of jumping. Yeah, I've actually got one more. Do you guys ever have to tackle the problem of shipping a patch that hasn't landed upstream yet? And if so, how do you do that? Yes. All the time. We do that all the time. That's right. So we use git upstream, which is a tool that's by, I think it's by the infer team. But yeah, it allows you to more or less mirror a repo that's upstream, and then you can carry a local patch. And it's got some magic in it. When you check in your local change, if you match the change ID with what's upstream for review, it'll automatically merge them later and collapse those changes down.  So it gives us the ability to carry patches like that. So we have those jobs set up for all our public modules and for the interesting open stack modules that we do a lot of work on. Do you know if git upstream accommodates the ability for ever going to land, forever going to run at my site, but never going to land upstream patch? I have some site specificity that counts for that. Yeah, and that's what it does. That's what it does. And so it'll try to carry your changes, always kind of at the tip of whatever the master branch is. Trying to rebase you to the top. Yeah. As long as that's successful from a git point of view, you could hold it forever. Cool.


Hello, I'm just out here at the long drive Walking now to a new beach. I haven't been before at the National Park. It's a bit foggy and rainy But it's like that almost every day a year.  I hope everyone's doing alright. We've got someone from Kenya Where's everyone else from? Arkansas Holland, Canada, Long Island, New York, Arizona Holland, Norway, R.I. I'm not sure what that is. Alabama, Kansas City, Missouri East Sussex. We've got people from all over the world. It's great, you know, I think that's one of my main missions is to bring like-minded people together and Looking back After everything I've done, I think it's safe to say that I have achieved that now There's loads of berries here. I don't know if those are brass breeze and black breeze, but they They look like that's what they are. See your name. I don't know how to pronounce that name Let's see Cerepiece Cerepiece, I don't know how to pronounce that if you can help me out then Maybe I can pronounce it correctly for you. I'm just out at Pembrokeshire National Park in Wales Heading to a beach that I've never been before called Marlowe


Hey guys, it's Julia and welcome back to my channel. If you're new here, hi. I make book content, sometimes witchy content, sometimes mostly book-related videos, but also some other little things every now and then, some vlogs, that kind of thing. But today I just have like an update video for you guys and some books that I like, I'm looking forward to getting to.  So I mostly have been away for a few reasons. One is school, so I officially finished off my second year of university. So I'm really happy about that. And I am pursuing a undergrad criminology degree right now. So in case any of you guys are wondering, but that's what I'm studying right now. My cat, Broody, who you guys who have followed me for a while definitely know of, he passed away, I think, about a month ago, or over a month ago actually. And that punched me in the gut. You know, just gutted me, cut out my insides, and then threw them, but it's kind of an aggressive image there that I just probably put in your heads, but it was a lot. So I've been just trying to deal with that. And then since I just got home recently from university and he's not here and it's a really hard. But thank you to everyone that has sent me condolences or anything like that. I really appreciate it. Some of you guys probably don't even know because I only talked about it really on Instagram and Twitter. So yeah, that was going on. In other news that's a little bit more exciting. I have a discord server now. If any of you guys want to join that, we just talk about books, gaming. You'll get notifications for my live streams. You could chat with other people. There's lots of categories in there. There's some music ones, some quotes. You'll find something you like in there probably. So if you want to join that, I'll have that down below, as well as I started Twitch. So I've been mostly in my free time. I've been gaming and I've been streaming a lot on Twitch, and I really, really love it to be honest. I really like the community there, and I've made so many friends so far, and I just have such a great time. Not only streaming, but watching other people's streams and interacting with the Twitch community, and specifically the Dead by Daylight community because that's the game that I've been mainly playing. So thank you to anyone who's come over to my Twitch or said hi. I really appreciate it. And yeah, we recently hit affiliate on Twitch, so now I have channel points and some email slots, and I can get subscribers now. So a lot of exciting things. Since I am home for this summer, I am gonna, like I do have, I'm gonna be starting a new job soon, and I'm gonna be of course like streaming on Twitch, and hoping to get back into, like, reading more consistently, as well as making more content for my YouTube channel. So if you guys have anything you really want to see from me, any specific recommendations, anything like that, definitely let me know. I've made a lot of recommendations videos in the past, and I think I want to like redo some of my older videos. Like I'm not gonna delete them, but I think I could do the same kind of videos I used to. But like now that I'm older and I can actually talk about things more, and you know, I'm not like 13 with braces, so maybe. Some books I'm excited about though. I am really excited about the song of Achilles. I took a mythology course this year, and it was like my favorite course. And I just love mythology in general, but I definitely like fell like headfirst into it this year. Like the amount of plays that I've read in Greek, like just Greek tragedies. I love them. They're, I love it. So I'm really excited to read the song of Achilles, and honestly any other mythology inspired books. I have, I think, a new one about the Trojan War from the women's perspective. I'll put that on the screen. I don't remember what it's called right now, but I bought that recently. I got it at Costco. It was on sale. But not the point. I'm so excited to read this, and I like held off on buying it till I found it for the right price. And now that I have it, it's just like hopefully I'll get to this soon. I also want to pick up Cersei by Madeline Miller because I heard that one's also phenomenal, and I do really like Cersei. Because you know, goddess of necromancy, like why, how, why wouldn't I? Also, from Andrews McNeil Publishing, they sent me this, which is The Apricot Memories by Tess Gennari, not sure. But this one seems cool. It's just a poetry collection, and I really like Andrews McNeil's poetry collections usually. This one has all like cute pink pages and like little poems, and this is just gonna be like such a fast read, but like I'm, I hope I'm gonna really enjoy it, and I love poetry collections. I love flying through them, and you know, sometimes they're exactly what I need, and then sometimes it's a flop. So we'll see how this one goes. I'm excited about it, though. I also am excited about I'm a hero. This is, oh, I really don't want to butcher that name. I really don't want to. Okay, that's the author's name. I don't want to butcher that. So yeah, this is supposed to be a horror zombie manga, and I'm really excited about it. I've owned it for a little bit. I have the first two volumes. I'm not sure how many are in this series, but I have the first two little bind ups, and I'm pretty excited about it, to be honest. I think it's going to be a fun time, and yeah. I need to also read more like Jinjo Ito. However, don't own that many of his books. I only have one, and I've already read it. So the point is I'm excited about horror manga. So hopefully this one will be good. I'll let you guys know what I think about it. If you've read it, definitely let me know. I would love to know what you thought about it. So yeah, I think that's all for my updates and like what's new and stuff, but definitely let me know any content that you're interested in seeing from me, and yeah, I would love to get on like a YouTube schedule of some sort, or at least upload like a certain amount of days a week, because I do miss YouTube.  And thanks for everybody for sticking with me, and I will see you all super soon with a new video.


Okay, yeah. This is a really important one for me, because like as I was saying when I founded Paranthropology Journal, I wanted to focus on those kind of more high strangeness kinds of things. And the 14 approach provides a nice kind of method. It gives us a way of thinking about those without bracketing them out in the way that social sciences have tended to do in the past. Just make sure, so in case people don't know, quickly cover who Charles Fort was. He was a writer in the kind of towards the tail end of the 19th century. And he wrote these four books, which were basically collections of all of these accounts of strange and usual phenomena that he'd found documented in various scientific journals and newspapers and things. So he gathered all of these things together and he called them his dammed facts, these things that sciences I'm sorry, your video cut out. So I'll use that opportunity to kind of interject and just leave in a couple examples. I mean, the reigning frogs and this kind of stuff, which we can't get around the fact that this is documented. This is in the news that we can correlate it with other news events. This seems to be an accurate reporting of what's going on at this time. And they said there was a solar eclipse or was it solar eclipse? They said these hordes invaded and they invaded and right along beside that they have, hey, you know, all these farmers out in the field observed the frogs, you know, flying from the soap. Why would we dismiss one account than another? And that was kind of Charles Fort saying, yeah, why would we? We can't let's just at least record these, right? Do you want to respond on that? Yeah, exactly. He's just saying that there's all of this stuff that happens out in the world, but our scientific models have actively ignored for the past, you know, 200, 300 odd years. He thinks that they've been pushed aside so that we know for whatever reason, because they don't fit in with our established models or whatever. And really, what he wants us to do is challenge science with all of this damned data to put it on the table again, and also to encourage us to think about things in slightly different ways. So one of the things I've taken most from Charles Fort is his idea of intermediatism, which is his kind of philosophical perspective on the nature of reality, as you could call it, his ontology really. And he says that everything kind of exists on a spectrum or kind of sliding scale between realness on the one hand and unrealness on the other, so that everything that exists in the world exists somewhere on this spectrum, which basically means that anything that exists is not 100% real and it's not 100% unreal as well.


What's up everybody, Jason here for jasperjaysrace.com. 2023 Immaculate Baseball 8 box picker team number nine just sold out with this random number block that has four teams, guys. Diamondbacks, Rangers, Pirates, and Padres, guys. You get a piece of these teams via a serial number break. We go by the first number on the left side of the dash. So, those are examples of how it works. Remember, any non-numbered cards get randomized to the group. And of course, any and all redemptions go to spot zero. Here's the dice roller. Here's the customer names and the numbers. So let's click dice roll and it is a six out of four, 10 times. One, two, three, four, five, six, seven, eight, nine, 10. All right, 10. Brian, down to Brian. Nine, zero, one, two, three, four, five, six, seven, eight, nine, and 10. All right, 10 times. We got eight down to seven. Eight down to seven, and I couldn't. Brian basically got nine out of the 10 spots. So basically, I'll show you one number you didn't get. And basically, it is number six. Dennis has number six. Everything else is gonna be yours, buddy. So, I appreciate it, guys. Now, coming up next in a separate video is going to be the Immaculate baseball break itself. Good luck, and let's have some fun, guys. Thank you.


So Douglas says, we have about 150 users that are currently in our tenant using AD sync. We have another 50 users that are Azure AD native. We want to migrate the 150 users off of local AD sync to Azure AD native without losing their user names. Users are heavy users of one drive, and so this needs to be migrated alongside. What is the best method? What is the best method? Well, I mean, it's really, it's a native process, right? It's really something that's built in to the product itself, the sync product. So it's just something that you do as part of that, and I think I provided a link there. Let me check here. Yes, you did. Okay. It seems to have gone away for me, but it's even worse there. I can see it, and that's all that's important. Yeah. That's all that's important. It's definitely there. Exactly. Okay. Yeah, it really is. It's all part of a native process to do that. So it's not something that they have to take a lot, spend a lot of time in or go to a third party. Although I think there are some third parties that could actually help you out there. And Christian, you might know more about that. But there is native functionality built in. Yeah. I mean, that's the migration has been, it's a commoditized area. This is kind of an easy process if you have that third party tool. I'm not sure on the native as far as migrating over the changes of those user IDs, natively, what happens with the OneDrive? Yeah. So that's just it. It's a delta cleanup, right? So it's getting those final changes after you are migrating. 150 users isn't that big of a deal. To be honest with you, it's not. I mean, in the whole scheme of things, I mean doing 150,000 or even 15,000, that's way different. That's way different. Yeah, that's the territory where I'd say if you definitely want to look at a third party tool when you're looking at, so if somebody has a similar scenario, but with 1,500 instead of 150 users, then I agree that heavier lifting and there are likely going to be other assets besides just the AD changes and OneDrive. It's probably be messier. Who would have thought that we get to this point in the game and we're still doing migrations, huh? Yeah, there was a lot of conversation about that like six to eight years ago that even further back than that, that migrations were going away. Has everybody been in the cloud and then there's just an update? It's like, no, and that's why there were a small group of us that were, they said, let's stop calling it migration and just call it moving because moving content will happen. Like, I don't know if you reorg if you're absolutely required acquisitions, right? Consolidate organizations, yeah. Consolidate cloud applications. There's data all over the place. People will go continually go and create new instances and then want to merge things over. I mean, all that shadow IT is not going away. You can minimize it, but there'll always be reasons to consolidate and move profiles and data. When you go back to those six years like you talked about, Christian, actually a lot of folks just wanted to get to the cloud and what they did was they synced their AD. Okay, so that was the first thing they did and they were like, hey, let's try moving some mailboxes and either it worked or it didn't work. And if it didn't work, they're like, ah, we'll come back to this later. And that later became two years, three years, four years.  And now we want to move mailboxes, you know?  Ha, ha, ha, ha. Redundancy never hurts. Yeah, yeah, until it does.


Hi, hello Carla. How are you? I'm fine. Thanks. I'm very good Barbara. Thank you. How are you? I'm okay. I'm okay. You're in Madrid, right? Yes, I am in Spain, Europe. Yes, and things are interesting there. Yeah, we are very very entertained right now. Yeah, that's it. Yeah, well we're becoming more entertained here in the United States and I'm thinking a lot about our community and about your team and more than ever I am so grateful to all of us and who we are together and what we have together and the knowledge and the skills that we have that the world needs right now. Yes, it's a pity that we are not the virus like spreading all over. Exactly, well maybe we can become a virus, a good virus. A good virus, yeah. To spread all over. So I know you've been talking to your team and we've been talking to your team and I know the community is anxious to find out what we're going to do. So do you want to go get your team and share your thoughts with the community? Yeah, of course, right away. Okay, I'll stay here and wait for you. Okay, where did she go? Hello, we are the conference team from Spain 2020. As you all know, the present circumstances worldwide force us to take this terrible, sad and tough decision up, reschedule in the conference to 2021. So, City, same team, different year. Until then, please take care, be safe, stay connected. Spain 2021, because good things are worth waiting for. See you next year. See you next year. See you next year. Hello. That's amazing. Spain 2021. You rock and I cannot wait. Your team is so awesome. They've been so much fun to work with and I'm so glad you're wanting to just defer another year while the applied improv virus spreads over the world and we all beat this thing together. Yes, absolutely. Thanks to you. You all rock too. The whole community rocks a lot. We've got a lot of support and we are very grateful for that. You rock. I think the community is probably going to have a lot of questions. I'm absolutely sure. Right. Maybe the same questions we are coming up with. Exactly. So what we want to say to the community is hold your questions. We know there are many questions like what about my proposal and what are the dates and what are we going to do instead? Those questions will all be answered. All will be revealed. We're going to be playing Keith Johnstones. What comes next? Or in Spanish known as Right. So we're going to take things one step at a time. Please know that more information is coming. We're not going away. And anything else? More than ever. More than ever. If you want to contact us, we'll be at home. We're here. We're here for you. Okay. Go team. More to come. Stay connected. Breathe. Stay connected. Wash your hands. Stay at home. Can we touch on the screen? Okay. Thank you, Barbara. You've got your back. We'll talk to you soon. Carly, you know, you said something before that reminded me. You said you rock. You rock. And you know what? I feel more than anything. Thanks to you. Thanks to you. Take care of you. Thanks to you all. Thanks to you all. Take care.


After I'd been sick for a very long time, one of the first acupuncturicide scene gave me a slap in the face when he said, Alex, your illness is a gift. Now, I did not understand what he meant at the time and frankly, I didn't really want to hear it because I'd been sick for so long that I didn't want an illness or any symptoms anymore. But what he meant was that each illness, each symptom is a canary in the coal mine signaling that something is out of balance in your life. Something has gone wrong. Something has been overlooked. There's still a problem. There's a fire in the kitchen and you're not paying attention to it. Every illness is a gift. And I see this especially with my patients that have cancer who say that if they have the right mindset, cancer was the best thing that ever happened to them because they went after those passions. They rekindled those friendships. They ended those marriages that should have been over and they rebuilt that dream life and went after the dream they'd been wanting to go after since they were a child. And so if you listen to your illness and your symptoms as a gift that they are, it can lead you to the permanent healing that you're looking for.


Greetings, folks. Dave Hamilton from Mackie Cab here in Las Vegas at CES 2024. Last night, we got to check out some new things from our friends at Belkin. Some great chargers and then this cool tracking stand. First, the chargers, right? So they have the Boost Charge Pro, the 3-in-1. Now you can twist this. This is all Cheat 2, all of these chargers, by the way. That's 149 bucks. Then there's this convertible stand, right? $59.99. That comes with a power supply. There's, of course, all of their battery packs, 5K, 8K, 10K. Very cool stuff. There's that 2-in-1 charge pad again. Cool, right? So this is all great. We love that. Then, I mentioned, this Auto Tracking Stand Pro. This is going to be $179.99. Comes out by summer. So you pair it up with your phone and you get your phone into camera mode. And then you put it on there and boom! Look, it follows me. That's me, as you can tell. And then watch what happens as I step to the right. I know, right? With a pelvic. Never mind. Let's go back to the left. There I am. Let's duck down. There it is. It follows me. Watch this. She turns it around and the thing turns around so that it's getting me with the correct camera. How do it know? Magic stuff. $179.99 by summer-ish. That's for the Belkin Auto Tracking Stand Pro. More cool stuff coming. Make sure you stay subscribed. Thanks to our coverage sponsors, CCC Backup, Collide, Mac Updater. Thanks to them for allowing all this to happen. And stay subscribed. Enjoy all the videos. Let us know what you think. Subscribe to the show, mackeycap.com. And don't get caught. We'll see you next time.


background about me. I'm senior at BYU, I'm graduating in April if all goes well and well I won't be walking or anything, so that's kind of a bummer. I've been working with Mormon Environmental Stewardship Alliance, otherwise known as Mesa, for the last couple of months and I've been able to work on a climate change, climate action campaign with them. So I wanted to share some of the research that I did and some of the things that I found and a lot of it's, a lot of what we did was through social media and mainly Facebook and promoting posts and trying to get more information out there. So but to start off I want to go through a couple of assumptions that I have and that I think are true since I looked them up but just to ask this question is climate change an important issue? I want to say yes and I have a couple of sources here, some of my favorite ones that I like to go to when I'm talking about climate science or climate change and I'm sure that most of you guys have seen these already or have seen better ones. I think my favorite one on here is ExxonMobil's page on energy in the environment and climate change. Just to show that this is established science and we really need to be moving forward on a lot of these issues. We know that climate change is altered and will alter our world significantly because humans have already cloud paved or burnt about three-quarters of the land's ice-free surface and we alter over 80% of the marine environment as well and our combined weight like in mass of humanity is tenfold greater than wildland and vertebrates and our livestock weigh more than twice what we do. So basically we take up 90% of the weight on Earth of all mammals, birds, reptiles and amphibians on Earth. I'm pulling this a little bit from my professor Dr. Abbott's research and so he has all of the sources and I can send those out as well. I just wanted to give a little bit of background about I know that we talked earlier about how some people might not think that an SUV or their children's living SUVs are really going to make a change but we've seen that we do and that we alter the environment 10 to 100 times more than the natural processes do. So because we're about because we're able to alter the risks significantly it's definitely more than possible to push it towards a tipping point which is what we are seeing. And I wanted to add some of the LDS views on this as well. There's actually been a couple of talks and symposiums where members and general authorities of the church have talked specifically about climate change and global warming and this is one of my favorites from President Oaks. He talked in a BYU commencement speech in 2017 I believe about. He named global warming specifically. His talk was more about the moral imperative and moral how we need to fight back against the world in terms of morality but he did this quote is directly from his talk and I think that it's really relevant to those island nations and to all of us around the world. And so I hope that throughout this presentation we can see a little bit more about what general authorities and members of the church are saying about climate change. The next question is Mormon theology pro environment. I want to say yes it is. We've seen it in scriptures. If you don't know LDS and stewardship has a huge resource library of everything relating to the environment by different topics. It's really wonderful and I hope that everyone gets a chance to look at that. So there's it's been in scripture since scripture has been and just recently in 2014 it became a gospel topic in our church manual under environmental stewardship and conservation and there's also several other articles. There's the church newsroom which has a lot of great resources for it as well and then there's articles in the tribune and local news and the church news as well. So these are some of my favorite links to these environmental topics. And then top it all off President Nelson himself has said that we are beneficiaries of the divine creation and we need to be there. The vice versa for future generation. So if that's not enough I think that a lot of members need to see this and that they should recognize well I hope to see more in the future that general authorities talking about it more openly and that we can talk about it more in our individual church relationships. So lastly do Mormons identify as conservative? This one I'm sure is obvious to you all as a yes. Here's a little graph from the Pew Research Center and they you can see that Mormon here I don't know if you can see my mouse or not but you can see that Mormon is the furthest right on conservative and Republican ideologies and that also most of our yeah so you can see that 70% of Mormons lean Republican and we uphold many conservative values and I think that that shouldn't go against environmental issues. To me conservatism we talk about property rights, a focus on family and our future generations and conservative though in itself the word we have conserved and we should be conserving and protecting our resources. So here's those sources for those and so I'm wondering or I've been wondering this whole time why is there such a big disconnect and you can see from this Facebook comment that I was going to blur out the names but since it's a public page and everyone can see it anyways I decided not to take that time but we can see that LDS concerned about the environment to me that is like mixing oil and water and I didn't write this response but if you shake the oil and water you can get the two to start mixing so I'm hoping that through this campaign we're able to shake things up a little bit and yeah hopefully get moving on some of these really important issues and so I here we go sorry I'm a little bit more about why I've simmered it down to three things so first would be politics just the fact that right-leaning ideologies will tend to push back against environmental issues and environmental moving towards sustainability and next would be culture in our church I see a lot of inaction we don't talk a lot about environmental issues and how they affect others and how we can be more charitable in those ways there's not much talk in church lessons it's not in the not in come follow me yet hopefully soon it'll be included and there's just not a lot of discussion and we also have I've noticed in Utah there's a culture of driving to church even though you it's only a five minute walk and coming from Michigan that never made much sense to me because it was like a 20 to 30 minute drive but so I feel like it's a blessing to be able to just walk to church but that's my own personal opinion and then lastly of science I found that a lot of people that do respond to us on Facebook have issues with the credibility of science and overall that's been a huge issue for me as an environmental scientist is that people don't trust peer-reviewed articles they don't they're having trouble just trusting news as well and so it's really difficult to get the clear sound science and make it available to everyone right so I want to show a little bit some examples of the things I've been posting things I've been putting together um I've just been trying to mix all the issues that we're facing and some of the quotes from general authorities or members of the church things that I've pulled from Valley Asserts to Rich of Research Library and other research that I've done and so um if you guys all have time feel free to feel free to read through them on Facebook they're kind of long because um Sorin wanted a lot of more information on each post in case people were curious about the issues um but I've compiled issues relating to air pollution wildfires as you can see here in this first picture um just different quotes from church leadership Greenland ice sheets and Arctic ice melting um trying to incorporate children and a reverence for the creation of the earth and also just different quotes this one's on my favorites from Gordon B. Hinckley that says this earth is his creation and we make it ugly we um we offend him um we got a lot of good responses on that one but so there's many examples um we've been trying to cover issues such as permafrost environmental disasters influence on water supply and drought um and trying to tie it back into since most of our membership is based in Utah we want to tie that tie those issues into what they're currently facing so post-it all these things a lot of them have a lot of articles and news articles and I tried to make it as easy to read and easy to understand as possible we still run into some fun comments which I'd like to share with you guys so there's been a couple of good ones and a couple of great reactions um well I don't know if you'd call this great but it's a good one and I'm glad that we're able to represent that voice but we also have a couple of fun ones like these well I I say fun in a light way some of them might not be as fun for others but I think this one's my favorite I quoted the commencement address and then someone commented that um we are lying about what the leadership of the church is saying even though it was a direct quote and I'll show some of the responses to these that we've done that were funnier but we saw a lot of issues with climate change and the science behind it or they try and push it on to other countries such as China and Russia which I feel is just an absolvement of responsibility but then I've seen this quote a lot about um how climate change is made up catastrophe used to tax us and regulate our freedoms and then we see it um in a fancier version with a quote from doctor in a covenants as well and this was on a post that was promoted and so I think a couple thousand people saw it and so we got you can see that a lot of the people that are seeing this post agree with comments like this now let me just get some crazier ones but I won't spend much time on those or just some funny memes that people have created on both sides and so I've seen as looking through all of these comments um and kind of regulating and promoting discussion about them um you see a lot of different ideas and what people are thinking about the environmental movement and as it relates to um the LDS population so I to me I see a lot of fear in these comments and a lot of worry but and you can see that on um climate alarmism on the other side as well but you can see that there's a lot of fear and maybe a little bit of unwillingness to learn more about the subject um that some of these fears and ideas are very deeply entrenched and so for me this comment is kind of a low blow to me as an environmentalist because I don't understand how plastics draws became one of the main platforms that we have but when we're still using plastic cups and everything else plastic so I'm hoping that the environmentalist movement can also try and expand the horizon on that. So here are some of the fun responses that we've formulated um this one was funny because President Benson actually says a lot about the environment and so I think Soren wrote this one he put together a lot of quotes and all of these are links to different talks from President or President Benson and other general authorities of the church talking about environmental stewardship and this one was also interesting we've had a couple of little keyboard warriors on our side as well that talk about um so this one says climate change is not going to kill anyone ever and the World Health Organization disagrees I'm quoting but it seems like um with everything that we do post there's always a rebuttal and so um we're just hoping that some of these conversations can change a couple of minds little by little but I'm hoping that more communities communicate more clearly and people can really engage in honest and open discussions and so after seeing all those comments um I get pretty bogged down easily from them but maybe you guys are doing better but I wanted to share some of the more hopeful ones and the good things that people are commenting so this one just says thank you for showing leadership on an important issue of stewardship um I definitely agree with this one that the LDS church needs to put aside some of its other controversial beliefs and get behind these environmental issues yeah and then on a couple of them we just get a lot of amens which is comforting but also I hope that this becomes more than just something you say amen and move on from I hope that people are able to really incorporate this into their lives so I'm really grateful for other organizations that are working on this and trying to change the church culture and hopefully these actions have good repercussions and that people can keep moving forward so I want to not take too much time more but I want to ask you guys what do you think we can do better and offer some of the things that I've thought about and like we've got like two to three five minutes or so you guys can chat I know Lincoln had a question for you as well I can Lincoln's question was um what is your primary call to action and I assume Lincoln you mean the organization of Mesa oh he says sure well feel free to unmute yourself and clarify if you want to expand personally how do you what do you feel people to do um as for Mesa I'll speak to them first our call to action is to join the organization get more involved in public issues but for me personally I would say that I would agree with that and that we do need to get more involved and hear more voices and talk with each other and foster that communication um but I think that some of the biggest things that we can do are acting politically voting towards things that we believe in and that promote environmental stewardship as well as fostering that within our church communities and talking about it more in our gospel discussions and just showing a reference for the creator I think that for me personally like going on nature I learned so much more about God and that's why I chose environmental science as a major and so I hope that people can have those experiences and really recognize the importance of environmental science. Thank you. I'll just put all of these up and then if you guys think of anything else that you'd like to talk about or have questions about these are some of the things that I've thought about just connecting doctrines and teachings to policy people. These are fantastic. My friends, oh thank you, one of my friends that works in the same lab as me she's working on a letter to church leadership to the general authorities of the church to talk more about environmental stewardship and environmental issues in general conference or just eventually income follow me or some something else in the church culture that we can do. Are you able to share this presentation? I believe so. However they're sharing the the video of it I guess I'll talk with my clan and see how we can send it out. We can maybe make like a google doc file or something to have everybody drop into. Yeah that would be great. Am I on mute? No I can't. Not anymore. I don't know how that happened and I'm sorry if I had any background but I'm kind of poking my head in but I'm the director for LDSR Stewardship and I've been doing a ton of conversations with upper level members of the church and I'm guessing most people in this group probably know that Sister Eubanks spoke to our organization in the fall and so we've got some really great content there but I sat in a meeting a few weeks ago with Elder Renland and he's interested so I have a feeling that this might come out this conference. That's really been the goal all along is to get this over the pulpit and conference and I think they're on their way. The area authority in Salt Lake is really interested in trying to get solar panels on churches and we've talked about possibly cutting some sod out of the design of the church buildings. Who knows what kind of state we're in right now because there's so much upheaval but there definitely is talk going on at upper levels. They're thinking about this. They know it's important and they especially know it's important to reach out to the younger generations of the church that this will be one of the key factors for keeping people in the church. So just some of my two cents on that. Thank you. No that's great. I was actually going to ask you anyways. Okay. I'm glad you're on this. This is fantastic. I love what Mesa's doing and your studies especially. This is really great. So thank you. Thank you.


Telemedicine drug prescriptions limited by feds. In response to the opioid crisis, the Biden administration required consumers to visit a doctor before acquiring ADHD or addictive opioids on Friday. After three years of telehealth doctors' appointments by phone or computer during the pandemic, the plan might change how millions of Americans acquire some drugs. The Drug Enforcement Agency announced late Friday that it will reintroduce federal standards for potent medications that will waive during COVID-19, allowing doctors to write millions of prescriptions for oxycontin and adderol without seeing patients.