Hi everyone! It's me Sophie Casai from Jordi Shaw and a lot has happened since the last time you see me in series 16. It's last season, there has been a few big changes in my life. I think physically I have changed. I lost a lot of weight, I lost like 2 and a half stone which was a really big challenge for me obviously being in Jordi Shaw and having to get fit and healthy. There's another big change that's happened to me since the last series and that's obviously I'm single now. That is probably one of the biggest ones yet. I've been in Australia so many times and I love it here. This is like my second home. We've already filmed a series out here before but now we'll get a chance to do it in the gore course. The gore course is like magalov to the English. The best thing about Life Down Under is you get to wake up to the amazing sunshine every day. You can constantly go out and not have to worry about how bad the weather is going to be, bad things about the weather.  Something that's really bad, the kebabs. What is wrong with the Australian kebabs? They are horrendous. You wake up with kebab breath and you've got kebab breath for a week. I'm starting to learn all the different hangover curas in Australia and there's so many juice shops. A juice shops is a hangover heaven.  There's also something called is it hydrolyte? That is a good saviour too. Scariest thing I have seen is I'm lying in the bed and I'm like I can hear something. Is that my ears?  And there was the biggest.  Who knows? But it was that big and it was staring at us in the face and it was buzzing. It was scary. I get asked a lot if I would ever move to Australia. Yes, in a harpy I would do it. I do feel like I need a congar England more, but you will definitely see me being an old age pensioner in Australia.


What's up everybody Jason here from jaspercasebricks.com this sells out chrome hobby picker team for and chrome choice for With this little mini box break of 13 penny select. It's mini box break round on teams number 18 And how this works guys is first will randomize the customer names and teams all teams and just remember no better in common ship out of the mini box Then we'll distribute hits out and at the end of this break will randomize all 30 customer names Then we will match you up with the list below of 11 teams if you come in the top 11 You will win a team so Dodgers choice number four all the way down to nationals hobby number four, so it's a little mix There you go top 11 will win those teams and then we'll start the break So let's do the break first guys. Let's roll it And it's Nate guys two times one two Robert down a mark two times here now one Two and then these mini boxes guys you could chase Christian yellow triggies in here Mike trout silvers and this stuff go for a ton guys as well Remember stick of what you got really quick quick glance of what you got right there Boom All right, and don't trade the other guys Here's a little mini box you got two autographs inside Scheduled Mac or I know you say you know some volume someone wants to just type in for me, please It was a scheduled day off Wade Boggs and Elvis Andrus other silvers That can we got Jose Dominguez. There you go. That's Dodgers Los Angeles You got Brian Wilson silver Derek Robinson just having 50 very nice Mac Awesome Can you see both of these silvers? I appreciate you guys. There you go. Oh Now let's see Who's going to win some teams? Yeah, did I miss a truck? Trumbos there Yeah, that's right silvers go for a lot of money. I guess let's roll it now again, and it's a one in a four Yeah, I think it was Trumbo Trumbo, I remember at the time. I used to get confused with them two at one point I learned a four or five times remember top 11 get a team one two three four 15 final time Boom five times Boom Sean down to Brian Let's see what people match up with the guys top 11 get in Oh So there you go guys So Sean are sorry. Yeah, Sean You get the Dodgers in choice for Robert Primrose.   So there you go guys I'm gonna input these names into the list and we're going to start and we're gonna go by this schedule here guys Well, I'm in choice HTA going out first then Bowman hobby. Like I said, I'll be free by eight o'clock guys I'll be off around nine ish So if we can fill up another small break or so whether it be Like I said impeccable. I mean sorry opulence filler We need to sell it that one that's already done a single digits and one more after that So let's get it going jazby's case breaks calm


Today's talk is about reliable open stack. Me, I am Chaitanya and Ajay is supposed to come and he will join anytime. Sorry about that. So, basically reliable open stack, designing open stack for high availability. And how many of you are actually interested in high availability aspect of open stack? Wow, that's nice. And what kind of models are you using? We'll go over it, it's hard to answer. So, basically outline of the talk is as follows. I'll talk about high availability. And you know, we'll see what is high availability and what kinds of high availability options are there for open stack right now. And we'll actually divide high availability into three sections. One is platform high availability, that means your cloud is always available. That's platform level high availability. The second one that we are going to talk about is VM level high availability. That means is your virtual machine always up, is it running? Virtual machine by is basically your workload. And third section is basically about application level high availability. Hello, Ajay. Ajay, when I say application level high availability basically, your cloud is up, your VM is up, but is your application that is running inside your VM, your web server or whatever web app, is that running healthy? That is the third level of high availability. So, we'll go over approaches to all these three problems of high availability. Ajay will start with standard and I will take over later. Okay, sounds good. So, before going into the high availability, let me just do some basic definitions that we are going to be using for the talk and let me just do a distinction between high availability and failover. What we mean by high availability is a system which is always on and it can tolerate failures and the system can heal itself.  And that's just between few seconds in the failure that the system should take to auto heal. What I mean by failover is essentially you can tolerate the fault temporarily. For example, if you run a service in two nodes, you can tolerate the failure of one node, but now the second node, if that was to fail, the service would go down completely. And in this case, somebody has to come in and again heal the system to make it running on two nodes again. So, what we draw a distinction is if you are not doing auto healing, that's more like failover rather than continuous and dynamic high availability. Also, for the purposes of the talk, let me just state a high level goal, what we are really trying to achieve here if we would just step back from availability for a second. At the end of the day, enterprises really want a web scale private cloud that they can run which is always available and they should be able to start small and then grow based on the demand. So, when you think of a cloud, you should not always have to start with a very large cloud. You can start somewhere small and then add more nodes and infrastructure as your need actually grows. So, let me first start with some of the standard approaches before we go into what we are doing at ZeroStack and how we are improving the reliability. So, in case of standard approach, this is actually something that most of the people here are probably familiar with and we are starting with stateless services. In case of a stateless service, you can start with multiple controller nodes. So, in this case, there are two controller nodes and we are running NOVA as an example as a service. And in order to now provide higher availability, you would run a HAProxy which would have the virtual IP for the service and the request would go to either of the NOVA instances. And you can have separate compute and storage nodes which may or may not be converged depending on which solution you are using. But if you look at the standard architecture, there are a couple of problems that you have to deal with or worry about. First problem is that in the beginning you are starting out with a set of controller nodes. You can start out with a one controller node or three or five, whatever number you choose but as your rest of the infrastructure scales, the controllers are not scaling automatically. You would have to worry about scaling the controllers as and when the infrastructure is scaling if you want to really run more instances of a service. Second problem is, in this case, one of the obvious things is HAProxy itself is a single point of failure. So, now you have to worry about high availability of HAProxy itself and deploy some techniques for that. And the second problem is that now if you do it for every service, you are doing it for NOVA, you are doing it for Cinder, Glance, now for every service you are adding an extra HAP. So, if there is a request that comes in and the request requires multiple services to talk to each other to actually complete it, you are adding an extra HAP for each one of these. Third problem is that if really one of the node fails in this system. So, for example, in this case, the one of the NOVA node fails. Now you are back to this failover scenario. There is other node which is running, which is fine for the time being, but if the second node was to go down, you really have no service running and at this point you need some sort of intervention to actually set up another node and make sure it's running a instance of NOVA and you are stitching it back to the base HAProxy. So, the fact that it requires manual intervention, that becomes another problem in a scale-out system where you want the system to run hundreds to thousands of servers, but you don't want people to come in when something fails because the larger the infrastructure, the higher is the probability that something would fail at some point of time. So, so far we looked at the stateless services. If you look at the stateful service reliability in terms of standard approach, here in specific to OpenStack, we are looking at either MySQL or AMQP, which is RabbitMQ or any other AMQP service. Again, you would set up some sort of replication because here you care not only about the service-level replication but the data-level reliability. And one of the standard things is to set up replication between data, between two different nodes, for example, there is a DRBD-based solution or you can even use a shared storage which could be an external SAN or NAS-based shared storage itself. And again, the service can be active-active or active-passive depending on which solution you are deploying. Now, if you go with this solution, again there is a problem. One, there are these special nodes needed. It's like having personalities to different nodes. You have nodes which are your compute nodes, you have nodes which are your storage nodes, you have nodes which are running your controller or which are doing MySQL replication. And these special nodes are fine if you have a small-scale environment. They are fine if you are doing this for some test and dev only. But if you are really running something in production, you can't be dealing with these special nodes in the system. And in case something was to fail, again manual intervention is needed. The service would run on the second node in case of failure but now you are back to that fail-over scenario where you have failed over but you have to fix the system by yourself. And again some admin has to come in and set up the replication with another node and make sure the system can tolerate another fault. Similar problem exists if you go with the shared storage model. There is one extra complexity that you have to worry about the external shared storage itself which in some cases could be expensive and another silo to maintain. And in case of a problem, again you have to worry about some sort of manual intervention. So just to give a summary of the standard approach and this is something I think many people have used in the past and for some use cases it may be okay but for a good scale-out solution they don't really work that well. And in most cases in case of an error some sort of human intervention is needed and there are well-known results that say almost 40% of errors happen when human beings go into a data center trying to fix some other problem and they'll create something else or mistype something and you have to deal with these kind of errors. And the more special nodes you have in a large scale system the more you have to worry about it because now some node failing has a different semantics than some other node failing. So we looked at all this and we thought about what can be a better scalable approach to high availability. Where you don't have to deal with all these manual steps. And I would let Chedanya go through some of the solutions that we are building to help with higher availability. See everybody is trying to build private cloud. And OpenStack is the solution for private cloud. Now compare private cloud with public cloud. In public cloud if you are, I don't know, Amazon might be using MySQL to manage their platform. And if it goes down, I don't really care. My workload is still running. That's what we want to get to with OpenStack. So what we built for high availability is basically a distributed control plane. What is a distributed control plane? It's a small distributed service that runs on all nodes in your cluster. All nodes in your private cloud. And this distributed service manages OpenStack services. It takes care of, you know, health monitoring the monitoring OpenStack services. It takes care of migrating OpenStack services. And it takes care of how to bring up the OpenStack services, etc. details. And this distributed service is fault tolerant. So we'll see how it how it is done. And one more thing that we try to achieve at ZeroStack is this distributed control plane can use any node in the in your private cloud to run a service. For example, there is no concept of, you know, MySQL nodes. There is no concept of NOVA nodes. Any node can be used for any purpose. What this achieves is basically, you know, your active node died. Then you moved to passive node. And that node also died. Then you moved to some other node, etc. If you have a 100 node cluster, we want to achieve 97 faults out of that. That means you have 100 node private cloud and we want to support 97 failures in that private cloud. 97 machines go down and your private clouds should still be functional. That's our goal, ZeroStack goal. We'll see how it is done in ZeroStack. And yeah, this distributed control plane not only, you know, uses any node to run OpenStack services. It also heals any node, heals problems because of, you know, one node going down, any node going down. What is this healing? Basically, you have some data sitting across, you know, your 100 nodes in the cluster and one node went down.  So somebody needs to take care of, you know, fixing this under replication. Then only you can actually support one more node failure. So distributed control plane actually takes care of, you know, initiating healing. So it fixes under replication. Once the under replication is done, fixed, then basically it is a brand new cluster with 99 nodes. Okay, now it can again support one more node failure. And then once, you know, that failure is also healed, then you have actually 98 node cluster. The procedure is same basically. After a node failure, there is a time where, you know, you do the healing of your cluster. And once the healing period is done, then you can actually take one more failure. So that's how we achieve 97 node failure sort of a 100 node cluster. So how is such a distributed control plane implemented? That's the core of this talk. How can you do such a thing? Okay, yeah. Yeah, first concept that we use for, you know, implementing such a distributed control plane is basically leader election. Even your 100 node cluster, basically one node becomes the leader. It uses a fault tolerant leader election algorithm, which is tax source is there and there are several other fault tolerant algorithms that you can build on top of other, you know, fault tolerant key value stores. Once you have this algorithm that actually picks a node as the leader, then that node takes care of the entire responsibility for the cluster, your 100 nodes in the cluster. And he brings up all open stack services in the cluster one by one. At the beginning, every node is basically a fresh Ubuntu installation, nothing else. Now it actually starts open stack services on all nodes in the cluster in your private cloud. Now once open stack services are configured and started, you have a cloud running. Now this leader, he keeps on monitoring the health of all services. Like he goes and thinks, you know, is my the node where my skill is running, he actually makes some query. The node where keystone is running, he actually makes some keystone operations. Basically, he knows everything that is going on in the cluster and he makes sure that all services are running and healthy. And he actually makes sure that, you know, services are distributed across the cluster. For example, you have different tracks in your data center. Then he makes sure that, you know, keystone instances are running across racks, such kind of things. Okay, so, you know, a typical configuration with the four node cluster something looks like something similar to this, where two nodes are one node is running, no one, sender, and you know, another node is running, neutron, glands, etc. This is how a four node cluster looks like. Hundred node cluster will have one service running per node. And one of them, everybody is actually participating in the leader election algorithm. So one of them becomes the leader. Leader is that green guy. And now how does he handle failures?  Keystone is healthy, MySQL is healthy, etc. Now, if he finds that some node, he cannot reach to some node or he cannot actually, you know, he cannot query some operation like MySQL operation, for example. He couldn't do MySQL query. That means, leader got disconnected from somehow. Something happened in the cluster and leader is unable to talk to MySQL. MySQL could be down or later could be down. We will figure it out. So what he does is he computes, okay, these are the nodes that I can talk to. What is the best plan for running services in such a configuration? Okay, if MySQL goes down, the node which is running MySQL goes down. That means he can actually talk to 99 nodes in the cluster. But MySQL is the only guy who is not, you know, that node is down. So he actually creates a plan saying, where should I run MySQL in this 99 node cluster? He actually picks one node, random guy, and he decides to run MySQL on that guy. That's what we call by service mapping. Service mapping is what are the nodes and what are the services that are supposed to run. Now he goes, next is basically he tries to migrate services. So that, you know, the current layout, active layout of the cluster is actually matching his plan. He does that by stopping some services on some nodes and starting services on some nodes, etc. And if it is a node failure, then he actually initiates, you know, healing. Healing is basically what do I need to do to fix up a service so that it can actually take one more fault. If it is a distributed storage kind of service, then he needs to fix under replication. If it is a distributed key value store he is using, then he needs to actually migrate data out of it. Somehow he needs to fix the system so that it can actually take one more failure. That's what we call by healing. I'll show you a demo how it happens. So let's assume the node, you know, in a for node cluster, the node running heat say failed. Then he recognizes the failure and he migrates MySQL and heat into some other nodes of the cluster. This is simple. That's how, you know, service and node level failures are handled. Service failure is basically a simpler version of node level failure. Only one service is crashing maybe. Okay. Now let's look one more step further. We saw how service failure is handled, how node failure is handled. But how about leader failures? The guy, the node which became the leader, which started everything in the cluster in your private cloud, that itself went down. Then how do we handle this scenario?  So the leadership election algorithm picks one guy as the leader and rest of the 99 guys are not leaders. What do they do? They keep on monitoring the leader's health and if they figure out that leader is actually, you know, faulty, leader is unavailable. They start a new leader election round, that is basically re-election and they try to bring up a leader. Now, one more guy becomes the leader. Then this new guy somehow needs to figure out what the world guy is doing and he is already down, so he cannot even talk to that guy. So how does he figure out what the world leader was doing, what is his service map, how he is running services in the cluster. So he actually, you know, the way we do it is basically leader always stores his state in a replicated storage and it's a distributed wall. How many of you know what wall is? Write a headlock. You heard about it, right? So anytime leader is about to do some operation, like migrate MySQL from node A to node B, he is going to write an entry in the wall. You know, saying that, hey, I am going to migrate MySQL from node A to node B before he does that. And he actually, he writes it once the write is successful into distributed wall, he actually then issues commands to migrate the service. Like, you know, shut down MySQL and unmap its disks or whatever and then goes to and issues an RPC to node B and says that, you know, mount whatever the MySQL volume there and then start MySQL there, etc. This is how the distributed wall mechanism works and distributed wall is basically a replicated wall. So if the leader goes down and the new leader is elected, this new leader still has access to, can read distributed wall content. So he actually reads the wall content and he actually restores the state of, you know, previous leader. So basically he actually comes to learn about what the previous leader was trying to do. And previous leader state is basically, you know, service mapping, what are the nodes and what services they are supposed to run or what am I trying to do, etc. So let's look at it in action in a four node cluster. Say for example, leader died, then what happens? Immediately after leader died, you know, all non-leader nodes, that means all the other three guys, they figure out, okay, leader is dead and they try to restart. They try to become a leader for the cluster and only one of them wins because of leader election algorithm. And that guy takes the responsibility of the leader and he restores his state and he figures out that, you know, the node which is running the leader, previous leader, he was actually running, you know, NOVA service and Cinder service, so he migrates them out. And this is how we actually, you know, handle leader failures. Yeah, sure. Yeah. I see. Okay. Your question is? We can do it after the talk. Okay. Just hold on to that. That's a great question. We'll handle it after the talk. Yes. Okay.  But how do you detect a failure in a distributed system? You know, you cannot detect a network disconnect, you cannot differentiate between a network getting disconnected and node going down. Process did not crash, but its network cable got disconnected. Both are same if you, basically, if you try to programmatically figure out if a node is dead or disconnected, you cannot figure it out. That's the nature of network systems. So basically, what I wanted to say is you cannot differentiate between node going down and network cable got disconnected. Then how do you ensure, you know, how do you make a decision that MySQL should be started on some other node? The guarantee that you need to provide there is basically, you know, there are no two instances of MySQL running at the same time. If the node that got disconnected is also, is actually running MySQL, say, and now you decide to start MySQL on some other guy using the same shared volume, then you have two MySQL instances trying to run on the same disk and it is going to just break the system. How do you ensure this? The way we do it at ZeroStack is basically using leases. So when leader assigns some node, picks some node to run MySQL, he actually issues a lease saying that you can run MySQL only for five minutes. Okay, let's assume that five minutes is the number. And after five minutes, the node itself will stop MySQL service. Nobody is actually asking it to stop MySQL service. It just tries to kill MySQL service after five minutes. That's how leases work. It's nonsense if, you know, if you just start MySQL on some node and it immediately shuts down after five minutes, then your system is coming down. The way we keep it alive is basically leader, period, he knows the mapping, service mapping, so he refreshes leases on all nodes every time, every minute, you know. So if leader is refreshing services, that means there is a refresh within five minutes of, you know, starting MySQL, then the node will actually get the refresh lease and it will actually make it six minutes and it will make it seven minutes like that. As long as the leader can keep, ping, keep refresh the guy, you know, keep refreshing the guy, then service will not go down. If leader gets disconnected from that node, all leader needs to do is wait for five minutes so that MySQL will be down. That node will stop MySQL and then I will stop MySQL at some other point. That's how we do it, but five minutes is a big wait time, so we actually do it in ten seconds, less than ten seconds. So leader lease time is basically service specific. MySQL has ten seconds lease, some other service has five seconds lease. It's all configurable. That's how we actually do, you know, that's how we detect node failures. So here I'm going to tell some implementation details about how ZeroStack does it. ZeroStack actually uses a distributed key value store and we built our later election algorithm and we built our distributed wall on top of a distributed key value store. There are lots of options for distributed key value store like ZooKeeper is one, etcd is one and, you know, Raft is a good consensus algorithm. You can use that, PAXOS is one. There are lots of options. Now, one more thing, I don't know if you guys notice. If you are moving your MySQL service all around across the nodes, then it doesn't have a fixed address. Then how do we handle that case? We actually use virtual IPs for every service. So when MySQL is moving, its IP address is also moving to the node. So on the new node where MySQL is started, we actually assign a virtual IP for that node and then we'll start MySQL. That's all part of MySQL startup. And if you are using virtual IPs, you have to make sure that R-Pentries are actually, you know, expired after a timeout. And we have, all our timeouts should be configurable so that you can actually decide on the responsiveness of each system or of each service also. That way you can actually build a better system. So given this entire design, you know, what are the benefits out of it? These are the benefits basically. You don't have any single point of failure because there is no such thing as controller node. Anybody can become a leader and high fault tolerance. Once the healing process is done, you can take one more fault as if, you know, your cluster, 100 node cluster was actually a 99 node cluster. So, and as I said, there are no special controller nodes in our system. And we actually do automatic healing. So we actually, you know, if we remove a node out, we can actually fix the under-replication and we distributed key value store itself, stores its data across nodes. So you need to fix under-replication. So we do automatic healing. And the best part, if there was a failure, you don't need, you know, admins to actually go and look at the failure. And of course your mileage will vary. Okay. And yeah. So just to summarize this part of the talk, I think the main goal that we started with is to get high availability in the platform. Now there are one set of approaches which we define as failover approaches with some manual healing. And I think that's most of the standard recipes and tools that a lot of people use. The second set of approach that I think we talk about and what we think is a better approach for a scale out private cloud web scale system is you use some sort of a leader based self-healing mechanism and you have a control plane that takes care of fixing the system if anything goes wrong. And essentially the left-hand side, I feel it's easier to do manually if you are doing a small scale environment, you know exactly where what is running, but if you are running for larger scale, it's actually better to have some automated system which in reality would be harder to debug if you are debugging manually. But the fact that software takes care of it, that means you don't have to worry about it. And that's what we have built at ZeroStack. So with this, let me give you a demo. I'll just go through a video demo and let me just set up the overall scenario for the demo. And here I just want to talk a little bit about the overall ZeroStack solution because that's what we are going to use for the demo, so it becomes easier to explain. So the way ZeroStack solution works is there are two parts to it. One is a converged hardware node that you rack and stack in your data center or call or wherever you want. And you can even do it on multiple different sites. Once you rack and stack that node and you assign it some sort of IP address so that it can talk outside, there is a ZeroStack control plane or a ZeroStack cloud platform which is running as a SAS layer. And everything else happens through that SAS layer. The high availability part that we talked about is essentially running a control plane on the ZeroStack nodes which are on-prem. The SAS layer is essentially there to help you consume the cloud, to monitor the cloud, to do operational intelligence on it.  So the idea is that the overall cloud would look and feel like you deal with a public cloud but everything is running on-prem. So let's just go through a demo and rest of the things I'll explain as part of the demo itself. So in this case what has happened so far is somebody has gotten the ZeroStack converged system and they have deployed it, they have racked and stacked it and put it in their data center. Once you do it, you go to the ZeroStack cloud portal and you register the company. In this case we register a company called HA Inc. You get a validation code that says this is a customer specific code that you have and you can enter it on the machines that you have put in your data center. This is a way to associate those machines with your customer account. Once the nodes are now attached to the customer account, when you log into the cloud portal again, you actually would see those nodes in your environment. So in this case we entered it on four machines and you can see all four of them in your environment. Now you go through some very basic setup. It literally takes about two-three minutes to enter some network information. We provide different pools of storage in terms of high SSD and disk-based pools. And you go through a little bit of setup in terms of creating a cloud admin account, is the person who knows everything about the cloud. And the overall setup is pretty much you are making very few decisions in terms of storage and networking. Everything else is taken care of by the control plane itself. So here is a summary of the cloud that it's building and it shows you how much capacity was there overall in the cloud. And once you look at that, you start building the cloud. This is a step that takes about ten to fifteen minutes. So I'm not going to make everybody wait fifteen minutes to look at this. So we have shortened this step and it will build the cloud in probably thirty seconds or a minute. But at this point it's literally creating a cluster across these machines, initializing that control plane across them and bringing up open stack services, stitching everything together. And in about fifteen minutes you would have a fully functional private cloud running on those machines. If you want to add another node, you just rack and stack another node, you assign it IP addresses, it will show up in your account. So it did the configuration of the cluster, now it's deploying open stack services and it says your private cloud is ready and now it's ready to launch the cloud. So I'm just building all this before I go into the H8 demo. This is just to show a little bit of the setup so that I can show when something is failing, what is failing and what was running in the system. So here you can see the infrastructure view. So there is one region, one availability zone and there are four hosts because we created a cloud on four hosts. You can actually create it on 32 nodes or 100 nodes. It wouldn't make a difference. The unit of consumption is first you create a business unit which is like a PU within your organization and you can have an admin associated with the business unit itself. And you can also, so user one here is the admin for that business unit. So once you do that, now you can create projects within that unit and project is like a mini virtual data center which is where the users come in and users are consuming essentially the projects that they are part of. Since we just created the cloud, we are just going to create a quick project so that we can start creating workloads in it and then we'll do the high availability in action once we have put on some workloads in the cloud. So as part of creating the project, obviously it's customizable. You can set the dimensions of the project, how much VCPUs, how much VM. You can associate different users with the project. So that's pretty much like a unit of consumption here and you can create external network within the project. So when you initiate VMs, they can get IP from that external network. All this is just to get to the main thing which is high availability. So now we have created the project and within the project now you can see there were no VMs. Then we go ahead and create some workloads. So now we have created some VMs in the background and now when you log in the project essentially has five VMs running and you can look at networking or images or volumes and all of these things are live. It's basically a fully functional private cloud running now. And VMs have external IP addresses. You can ping outside. This is just to show that everything is working here. It's a cloud with real VMs running and now we are going to go through a failure scenario and to stress the system, it's literally a four node system. So it's a single unit where it's a four node system and the services are running across four nodes. If you put a hundred node system, you would see one service on some of the nodes and there would be nodes with no services on them. But since it's a four node system, you can see that there are four nodes and you look at the service map and different services are running across different nodes. So in this case you can see there is a glance, there is RabbitMQ and these are the services that are running on Z host one. Then there are other hosts in the system which are running heat and neutron. And now we are going to go and just shut down one of the machines. So in this case we actually chose to shut down a critical machine which is Z host three which is actually running MySQL and NOVA. So we just log into the machine and we shut it down. You can even pull power out of the machine. It would be the same thing. It's just that we have redundant power supply. Pulling one power out doesn't shut down anything. So we have to go and manually do the shutdown command. So now if you wait about ten to fifteen seconds and you run the same command again saying show me the service map you can see here the services are now running across Z host zero one and two. Node three is part of the cluster but there is nothing running here. The machine is gone and now the services have automatically migrated. And now we'll go and try to create some workload again. So now we are going to just go log into the UI and we are going to create another VM and show that everything is working even though one of the node is down. So we are just creating a new VM. We are going to give it a floating IP and we are going to check network connectivity and make sure that everything else is working. You are essentially running a private cloud with somewhat lesser capacity because one of the node is gone but everything else is completely functional. So now the VM is up and running which is the VM that we just created. We will go into the console and see the overall connectivity of the VM itself. That it basically tests all the services in the system that all the services are running fine. And we also look at one of the existing VMs and that is also working fine. So that pretty much ends the demo part and one of the things here you would notice below every entity here there is a timeline that shows what is happening to that entity. So when you bring up a VM it shows all the VM level operations at the bottom. If it is a project it would show all the project level operations. So with every object we are storing what is happening as time series with that object and you can do a lot of analysis on top of that. So one thing I think many of you may be wondering we actually shut down one of the nodes and the services migrated but what happens to the VM? That node was running some VMs here and unfortunately that VM is obviously down. That node it was running a VM that is down. And there are a lot of people who come back and say that with some of the solutions like VMWare there is a feature called high availability which is VM level HA what it essentially says is if there is a node which is running some VMs and the node goes down you should be able to restart those VMs on some other node and that is something which would provide you this HA where if some VM goes down it would automatically come back up with the same disks on the other node. So the problem with doing VM level HA is again the same problem with networking where how do you detect a node is actually down because it is hard to distinguish between a network disconnect versus a node being down and the same problem that Chetanem mentioned before is that if you think a node is down just because you cannot talk to the node the VM could actually be running there and now if you start the same VM somewhere else using the same backend storage you are going to have corruption in literally two minutes. So the way to solve the problem is essentially you again have an agent on the host which is now making sure that the host is connected to the network and you can define the connectivity and availability how you want to. It could be that it can talk to the remaining nodes in the cluster or it could be that it can talk to the internet whatever you define but once the agent realizes that this node is not being able to connect outside that agent would essentially stop the VMs. So in this case the agent would detect that it cannot talk outside and as part of that it would shut down the storage connectivity making sure that if there was any storage that this machine was talking to that it cannot talk to it anymore and would also shut down the VMs that are there on the host. If the host is literally dead then you can actually make sure it is dead by issuing an IPMI command and making sure the host is really dead there is no agent to even take care of things and obviously the control plane that you are running would detect this and after some time out which is the time within which agent would act you bring up the VMs on some other node. So this will give you a VM level high availability where you don't have to worry about restarting the VMs yourself. Now moving on to the ultimate high availability that I think at the end of the day everybody cares about is the application level high availability. Everything else is just to achieve this goal here. Infrastructure level, VM level you ultimately want app level and that is something that we are looking at for future but I just want to point out few things that can make your life easier if you are thinking of the application level availability and there are two main failures here one is the infrastructure level failures which we are going to focus here and the second is app level failure which is fine and that is something we are not targeting here. I think for that you have to have your own application plug-in liveness check and other things but for the infrastructure level the standard way people do most of the app level availability is you run it across multiple A's you design the app either active active or active passive where you can run it across A's and you run some load balancer in front. You can run it on top of this and what you can do better on top of this is if you look at the problem with just this design is within the A's itself any of the A's is where you deploy the app you really have no locality if you just go and deploy a bunch of VMs and this is specially noticeable if you do something like a private cloud you deploy a bunch of VMs they would go somewhere in a large data center or VM request if a request comes to your one tier of VMs goes to the second tier goes to the third tier by the time it gets done it may have traversed in actual networking hops maybe 25 different hops and switches and that is where one of the problem comes in that you don't have as much control over it and you suffer from performance penalty in terms of your availability penalty the problem is given that you have no control and if you do not have the ability to use the same host but in the case of a single host failure actually can take down a full tier so in this case in rack one both of your tier one VMs are running on the same host if that host goes down actually the app is not available it doesn't matter if everything else is up in different groups and you can have affinity within a group across tiers and anti-affinity across groups and that can give you much better performance and much better failure tolerance if something was to go wrong. We're almost out of time so just to conclude, the current techniques that are there, they are good for some small use case but we believe they don't scale very well for a web scale architecture and the key ideas to get a scalable HA is you don't want to have special nodes in the system, a symmetric design is much easier to deal with, you want automatic healing and you want some sort of consensus based approach to take decisions and VM level HA would help you with better failure tolerance and you actually need lot of good detection and isolation for that and app level HA can help you with better performance and reliability. I would be happy to take questions, I think we're almost out of time, we can always talk outside. Yes, we can talk outside and feel free to drop by our booth T43, would be happy to give lot more detail there. Thank you so much.


Clinical psychologist Dr. Ellen Hendrickson says responsibility is typically a positive trait because it shows you're dedicated, trustworthy, accountable, and concerned about others. It's the polar opposite of avoiding responsibility by blaming others or making excuses. But it's possible to go overboard. Do you do everyone else's chores? If someone bumps into you, do you apologize? Do you believe it's your fault if someone you care about is irritable? Indeed, it's a mark of maturity when you own your mistakes. However, you become overly responsible when you own other people's faults and blunders. Dr. Ellen stated that feeling overly responsible can be a main symptom of obsessive-compulsive disorder, OCD. She gave the example of a client who was certain she was to blame when a tree fell on her car during a severe rainstorm, claiming, I shouldn't have parked it there, I shouldn't have known. Let's view this from a different lens. Let's say there isn't any OCD present. That causes non-diagnosable yet toxic overresponsibility. According to Dr. Ellen, like many maladaptive beliefs, it typically begins in childhood. Children who are blamed for matters they have no control over, like their parents' feelings or financial circumstances, begin to feel they are truly responsible. To know whether or not you are overly responsible, it's good to know that things you shouldn't be responsible for, so here are some things to keep an eye out for. Other people's feelings.  Do you think that it's your responsibility to fix their problems and remove their pain?  According to a licensed couple and family therapist, Dr. Aziel Romanelli, these kinds of beliefs lead to reactionary behavior in close relationships. When your loved one talks about something distressing, you stop openly listening and you think of ways that you can relieve their suffering. It is this automatic reactivity that keeps you in a symbiotic relationship where both people are reluctant to share their pain as your agony equals their problem. You might find that you start to avoid sharing your frustrations because you believe it'll ultimately hurt your loved one. In a healthy relationship, you know their emotional happiness is not your responsibility. It doesn't mean you ignore their suffering, but instead you set good boundaries and let your loved ones know that you are there to support them while they deal with their personal issues. When your loved one has bad habits, do you bend over backwards to help them, ignoring your own time or resources? Even if they tell you that they like to work it out themselves, you believe that you know the best way to break their bad habits. Licensed professional counselor Sarah Alan Benton says there is absolutely nothing wrong with helping your loved ones to drop their bad habits, but it starts to become a problem when your self-worth is connected to being needed and you believe that your purpose is helping others to the point of burnout. This is known as savior complex or white night syndrome. Individuals with this syndrome are willing to assist those who are desperate for help, often at the expense of their own needs. Wanting to become a rescuer means you prevent your loved ones from accepting responsibility for their own actions and helping themselves. Others mistakes. Do you blame yourself when someone else makes a mistake? Do you wake up at night wondering how did I cause them to make that mistake? As you play this self-blame game, you feel more emotionally depleted, fatigued, miserable, and upset. So what causes us to self-blame? According to licensed marriage and family therapist Dr. Gary Bell in his podcast A Life of Regret, it's simpler to blame ourselves for other people's mistakes than to examine the issue and assign responsibility where it belongs. Also, we might often find ourselves turning a blind eye to a blender by our loved ones. We don't want to blame them and remove them from their pedestal, or face the reality that perhaps they might not make our lives better. Others needs. Take this scenario. You're watching a basketball game on TV with your friends while munching on that delusious pepperoni pizza. It's now down to one slice. Would you allow your friend to finish that last slice? Or would you grab it and savor every last bit of it? If you chose the first option, you are portraying cooperative behavior. Or what the researchers in the Journal of Personality and Individual Difference is referred to as Others-Centeredness. Researcher Ryan Byerly defined Others-Centeredness as a tendency to put others' interests ahead of one's own that is based on a specific way of thinking. Individuals with Others-Centered Thinking view their personal interests as equally important to others. Interpersonal interactions are, however, very important to them. This is different to when you are excessively concerned about the well-being of others, which is known as unmitigated communion. When someone has unmitigated communion, or high other focus, they may prioritize others out of concern that they can't be satisfied unless they fulfill other people's needs. And finally, other people's dreams. Imagine this.  And many of your commenters say you should visit the newly opened Harry Potter theme park in a distant land.  Do you think you're responsible to grant your audience this wish even though your current finances don't allow it? Here's a more common example. Parents who view their children as a second chance to fulfill their own dreams. According to Brad Bushman, one of the researchers of My Child Redeems My Broken Dreams on parents transferring their unfulfilled ambitions onto their child. These parents regard their children as extensions of themselves rather than as separate people with their own hopes and dreams. They link to achieve their dreams. They want their kids to do so. Remember, it's not your responsibility to fulfill other people's dreams. When you bear too much responsibility for things you shouldn't be, you may become frustrated, resentful, and feel taken advantage of. Though changing such behavior is challenging, it is possible if you acknowledge how it can negatively impact your interpersonal relationships. Can you relate to any of these points? I can. If so, share with us in the comments. The references are listed in the description below. Thanks for watching, and keep an eye out for more Psy.


Who, if any, are the white girls you didn't get to talk about in this book and you hope to write about in the future? That I don't talk about? That you didn't get to talk about? Oh, that I didn't get to. That's a good question. I've always wanted to write about Lily Tomlin. I think she's so significant that she and her wife, Jane Wagner, are so significant in terms of not just women in comedy, but they're the equal of Richard Pryor, really. When I wrote about Richard, I wanted to do two parts, and the second part would be about Lily. They weren't out as a couple then, and so it was just difficult to negotiate how I would write about them, but I still want to write about them. I think they're phenomenal people and very, very funny and deeply devoted to each other, intellectually and emotionally. I just love them. I'd love to write about them. A friend suggested I really love 70s girls, so I guess I love Diane Keaton. I think she's great. Her new book is fantastic. It's coming out soon, and Jean Rhys, I think, is a great writer I would have loved to have written about. So maybe we'll do part two of the ever-estimable Dave Eggers will publish part two of this book. We'll do it.


Welcome to Sailor.org's professional writing course, part of our professional development program of study. The courses in this program are designed for adult learners who want targeted skills they can immediately apply in a professional setting. In this course, you'll learn skills toward writing effective documents in the workplace, even if you've already got years of practice. We'll look at the most common business documents such as emails, memos, proposals, presentations, and we'll think about how to shape these for maximum impact. The single most important thing? Audience. Who are your readers? What do they want? What do they need to know? And if you really know the answers to these questions and you keep your focus tight, your final draft will make a positive impression. You'll have an opportunity in each unit to practice your skills through writing.  You can go back and review any part of the course at any time during the test. This course can be completed in about three and a half hours, but to improve your writing long term, you'll need to practice. Write often and review what you've learned. We've put an editorial checklist at the end of the course, print it, bookmark it, save it. Whenever you're composing an email, a cover letter, even a Facebook post, the checklist will help you catch errors before you broadcast them to the world. I hope you enjoy the course and more importantly, I hope you enjoy seeing the improvements in your own writing.


We've come a long way from our start triangulating and directly measuring sizes in my backyard in our segment on the earth. In this segment, we split redshift, our final rung of the cosmic distance ladder, into two parts. The original was based on the Doppler effect. The second is cosmological redshift based on the expansion of the universe. It is important to remember that this kind of redshift can only provide distance information if we have a cosmological model for the expansion. And we do. It's called the Lambda Cold Dark Matter Benchmark Model. It is covered in depth in the How Old Is It? video book.


I read this book when it first came out and I remember being floored at how good it was. I mean, Silverburg can be hit and miss. This was a hit. The story is about these bizarre, powerful aliens who show up on Earth one day claiming to have the best of friendly intentions, but very quickly showing that they came here to take over. The story is very large and sweeping in scope. It spans a couple of generations and we watch how people learn to cope with this alien occupation. The aliens apparently thought it would be easy. If you're not seeing the political and social parallels here, then I can't help you.


And former U.S. president Bill Clinton is out of hospital after being admitted last week for a urological infection. He will return to New York and remain on antibiotics according to his doctor. The former president had been in California for an event for his foundation and was treated at the University of California Urban Medical Center's intensive care unit after suffering from fatigue and being admitted on Tuesday. He led the medical center accompanied by his wife Hillary Clinton. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


interest me about this place is it still look it's got the neon sign up there but I can't make it out it gets colder when the spiders ain't so bad so that's what the fourth bar I'll figure that out a boat you know what this used to be the bar bats in here so I got one on film with this bar you're kidding that's what it is the bar wow there's the dance floor over there it is on oh my god it's really dark I know cool it's a friggin bar mm-hmm probably I was gonna go up there I started up but it's all covered in them big banana spiders so so when it gets colder when the spiders ain't so bad we'll come back I'll do the upstairs some of the things you find you know that looks like a stairway so this is the back part of the stage see the stage we was in there it just cut it and dropped it off but they left the damn numbers on it the last registered in November 2007 alright guys so the sign must have been on that post right there I'll see if I can bring this stuff up bring us up on Google or something so you didn't come with me that was bright up there I didn't know used to be nice at one time up there so they used to up and down for both I'm just wondering if that was like if maybe it was a strip joint and the upstairs was extra I don't know but it set up like that we'll find out funny these doors I mean to me when you see these doors they look like public wash room yeah kind of weird really there's some history on this on the internet that's what I just said I'll Google it and we'll see what we find that will be interesting and spoiler alert sitting back there this is something on it okay okay I'm sorry I'm blinded never said anything you didn't say come on I did I smiled I was like well you should say come on well I thought and then I was like because I heard some steps would if they are they're really solid yeah felt like concrete to me okay but bear with no problem yeah that's why I smiled but I thought you was coming because I thought I heard footsteps been behind me I'm gonna have to go over his numbers on it's flipping back and forth so I don't know if there's power in something would be running so but most of times there was nothing running it would take the face out yeah that's what I thought was okay there's another one onto the next adventure yep all right it's telling me to get out of the car because look what I did guys tell that that's a bunch of friggin cobwebs I'm trying to get her to get them off of me I think she's trying to get something out of it I think so turn around make sure there's nothing on your phone oh don't please don't tell


calendar items so really how do we build on previous work i know council member brown and myself um had an opportunity to serve on the housing blueprint subcommittee and there's a lot of really great foundational work there um and then also looking at how we use our limited staff time and capacity to take on um where the council sees hopefully a commonality in terms of policy objectives and priorities um and then looking forward towards a strong kind of knowledge based for decision-making and study sessions um in terms of how do we ensure that we have as much knowledge as we possibly can when thinking about some of our policy directions um given that it's often very difficult to get to the place where you feel completely comfortable all the time um it would look at terms of how do we have a work plan that would be uh effective and collaborative governance um and what i along with staff are interested in proposing is a full day facilitator facilitator led retreat um to develop that sort of intermediate work plan for the remainder of this year um but simultaneously one of the opportunities we have is to have a current sort of work plan to man to manage the upcoming council meetings and the priorities for what we want to accomplish but then looking at how do we go um a different route this time in terms of updating our strategic operational and accountability plan um separate essentially separate from the work plan but um concurrent to it and that would be a more inclusive process that would look at some of the longer sort of three years uh interim but longer term needs um have some strategic direction and um incorporate the community in the priority setting and this would be facilitated as a um uh council and community and staff process over a four to six month strategic planning um timeline susie so i will just add to um give real tangible context to the need for a work plan for the remainder of this year and i will use homelessness as an example this is not sustainable it's destroying staff morale quite frankly to have these long meetings and to continue to push staff to move forward with items that we are not prepared to do so that needs to happen and the council does need to um ensure that you are talking about staff capacity when you're thinking about policy objectives for the rest of the year thank you susie i appreciate that and um acknowledge all the hard work and very difficult timelines and uh pressure the staff has been on so i appreciate your comments as well i also um i want to um go ahead and we'll go ahead and move forward with the timeline and essentially um in a more visual uh demonstration we have is the opportunity to hold a one day retreat to develop a 2019 work plan um and that would uh be uh that temporary or sort of interim work plan and then having the one day retreat to really talk about as a council what do we envision the strategic planning process to look like and then between july and and december having that process take place with a community engagement priority setting and facilitated council sessions um with ultimately um returning in the in the in february of 2019 that we would have a strategic and operational accountability plan before us for potential adoption that would cover the years of 2019 to 2022 so um excuse me mayor um 2019 or is it 2020 i don't want to get that oh sorry 2020 sorry yes thank you 2020 in the year it was by fast okay so the recommendation before us this evening that i um am seeking our council approval on is to calendar a special city council meeting to develop a work plan for the remainder of 2019 and to initiate an inclusive planning process to build a three-year strategic plan and obtain consultant support to facilitate these planning efforts um before we potentially move into um the remainder of the discussion i maybe would ask if any of the council members have specific questions and um and then we'll go ahead and open it for public comment in return for action and deliberation council member matthew quick one if you could go back to that previous slide or just everyone look at this slide so may 2019 is a one-day retreat to develop a 2019 work plan would that be for the remainder of the 2019 calendar year yes calendar year i suppose fiscal year and then june 2019 hold a one-day retreat to develop a strategic planning process and that's three-year planning to develop the process that then would be carried out over the next six months and that would be for a three-year plan got it so it's sort of a work plan management proposal based on sort of the rapid movement of the council for the end proposal for the next few months while also initiating a more inclusive community process at the same time right i guess the only other thing that occurred to me in june 19 we will have just gone through the whole budget process for the 2019-20 fiscal year 2020 fiscal year so that will set the stage for the first year of our strategic plan strategic plan i think the budgets will absolutely right that's right because uh you'll be making some major budget decisions and learning about what the you'll be able to work with the next plan okay are there any additional questions councilmember brown and then councilmember crown it's a common deep question i guess so i'm i'm all for proceeding in this manner in particularly getting us to uh our work plan for the immediate future i think that is absolutely critical um with respect to the longer term strategic planning process i also agree that we ought to be doing that but i do have some reservations about um approving that now without any consideration of the the potential cost how you know when would and how would consultants be hired i mean an outside facilitator for both of these meetings makes sense to me but i'm concerned about um talking about a consultant for some big strategic planning process um when that that could be quite pricey and um so i'm i'd rather just stick to the basics of what we know we need an outside facilitator and then make those decisions about future costs at a at a work plan meeting and this this is just approving it in concept with costs potentially returning i think that's essentially what's what's being proposed here because the there'd be the two retreats that would be facilitated but the second retreat with respect to the long term three-year plan the council would discuss the process and therefore also talk about what that would mean as far as cost and approach and then make a decision after that i'm just wondering the uh idea of a three-year work plan compared to two-year work plan that's been happening i guess i don't know when did the two-year work plan start and why three year now i can answer that the three-year work plan was proposed because the two-year work plan started right after we were elected and it was a really short turnaround that was the first one that was the first one and so this allows a buffer time for a new council to if thinking it forward beyond our time to have that a transition time of getting adjusted to the council role the council work and the work of our city so it kind of gives a little bit extra time in that regard and i'll let susie answer it also um causes the expiration to be on a non-election year which i think is really important so we don't have brand new council members much like you were when we first did this work plan two years ago that were just you know forced into decision-making before you had an opportunity to get more up to speed on city business but my other question is um i'm not i'm not sure it makes total sense but maybe you can help me out to have the strategic planning process after the budget is set for this year it's like when you want to have strategic planning what we're going to go forward to and maybe learn about priorities of the council and then budget for it no so that may 2019 is ahead of hopefully the budget process or at least the final ratification of the budget um and the june 2019 is really just to develop the process for which we will actually go through likely a six to eight month process to do the strategic planning not in and itself developing the priorities so which day in may would that be that be that the third week in may we're looking on the consultant's availability potentially so or did you find a date no okay no but you know the intention is to um have it on perhaps one of your off tuesdays for for instance 21st it looks like in may we have to figure out who is available to do the work and there's you know there's prep that's needed as well and what's the cost of the consultant to just um revisit what council member brown saying but a ballpark 30 000 25 000 not for one day for one day no for the whole strategic process i thought we were talking about having oh uh we would not know how that information at this time but it could be anywhere from 20 to 30 000 maybe this really depends on what on the process and how extensive it is and what you want to include in it so and that that conversation will happen when we decide and have a special retreat on determining the process that we all feel is inclusive to the level that we want it to be but also gets us to the place we want to be for a strategic plan and i don't think that's uncommon for an organization to invest in generally for a strategic planning process and the budget hearings are may 8th so we still might have that one day after the budget hearings possibly but the the one day retreat is to develop a work plan in terms of council priorities for the remainder of the year um without sort of and then while having the strategic planning process happen underway same time thanks america um i two questions one is just trying to understand given the two-year work plan is there any way to get a report back on um what was laid out in that work plan and then what was achieved or how far that the council the previous and current deviated from that work plan just to understand whether or not um when those work plans because it sounds like there's a lot of work going into creating this work plan and um i just want to have a good understanding of whether or not these work plans how often they're adhered to because i think it could be a big waste of time if we put all the effort into creating this plan and then we don't and and if in previous years it hasn't been adhered to or stuck to then i would say that i mean a lot a lot of it has been completed actually a good chunk of it uh and uh certainly when we do the retreat we can you know update you on that as well or any other time but and there i believe there was a memo had that had gone out in the past in regards to updates on the work plan that i'm sure we could we could recirculate that too councilmember matthews and then i maybe i'll open it up to public comment i just had a second question okay go ahead is there any opportunity for us to see um kind of calendars of what's being worked on at this point in time so that we have an understanding of currently what staff are working on so that we're not because obviously there's going to be some time in between when we're going to have this retreat when we're actually going to have the 2019 work plan accomplished there's going we're going to be wanting to take actions on different things between now and then so is there a possibility to get a calendar so that we can see what staff are working on have a sense of how we can be respectful of staff's time as we're bringing things forward and i'm assuming when you're saying staff's time you're anticipating city manager staff or all department the heads the workers oh i i think i mean i i'm just not quite clear in terms i mean we have our water department doing their water where i mean so what um were you hoping to get answered just primarily the work of the city manager's office is that yes okay well i mean it would be good to have as many you know challenges as possible so we can have a good understanding for bringing things forward you know if it's water related how does that fit into what the water department's currently working on if it's public works related how does that fit into the plan that they're currently working on and and what these different department heads are addressing because obviously we have a lot of issues that we and there's going to be the desire to bring other issues forward so i'll just remind the council that we did agendize many individual department presentations to help understand what they've been working on which have been postponed because of the amount of agendized items particularly around homelessness so that will be forthcoming in terms of what they're working on and what the work that they do includes and and hopefully hopefully this is helpful i would fully imagine that to prepare the city council and the community for this one day retreat a strong basis of that conversation would be what is currently calendared and you would get that ahead of time so you could consider that that within the context of whatever you're prioritizing for that full day retreat so i mean i certainly can come back maybe with the city manager's report over the next couple meetings and talk about that process and when you might be getting that information as individual council members to facilitate with the work that you need to do to prepare for this may retreat okay so if we could maybe we'll see if there's any member of the community that would like to address us okay i see one is that correct okay we'll have one member of the community you have up to two minutes okay thank you um first of all susie i really uh just wanted to say that i really sympathize and appreciate uh i've been going to a number of whatever meetings i could go to i went to harvey milk for the uh for the facilitation day and just sat in on that i've been to the hot meeting where the staff outreach to the association of faith communities and the reason i'm saying this it might sound like i'm trying to toot my own horn here but the the real reason i'm saying this is that it really seems to me that we need to hire marci staff but i'm saying that facetiously because i know so completely nothing about a lot of these processes but if we could usher in staff to help the staff that's one thing and it's probably a ridiculously simple solution that i'm suggesting but i really have noticed that our entire city is so dependent on these people and they are just a very few and they're doing just tons and tons and tons of stuff it's just not humanly possible thank you so much for everything you've attempted and i think i just want to also say i've seen surprising discussion point i've seen members of the city council that i completely disagree with and basically despise a lot of their longtime policy actions nevertheless weighing in on issues and there have been new discussions thanks to city staff leading a lot of this and i think real concern even if we completely disagree but i just want to end by saying i i can't overstress that i think we are in a paradigm shift that our way of doing business has been dependent on financial models and i wish i had more time but i just really think we need to have content models the homeless issue has brought enormous difficulties but it's also been ignored for the last 16 years and just shut you know pushed away anyway sorry i didn't really get to say that can i just add one thing the the other thing just to to get back and answer you know uh vice mayor's coming question a little bit it's also important to recognize that you know over 80 percent i think we did this analysis before like 83 percent of our time is spent on the things that we have to do the day to day things i mean because we're not spending all of our time working on all the special projects or the new initiatives or all the new direction uh the majority of it is spending on the day to day things i mean susie even in our office susie has certain responsibilities and duties that they do they have to do every day i mean so do i so does tina we have to run the organization we have all kinds of personnel issues there's a whole variety of different activities that we do every single day to run the organization uh and all those various functions and duties and responsibilities and so the amount of time that we can spend on new initiatives and project is really a very limited resource and that's the part that we will we'll talk about that more at the retreat but it's not like uh we've you know we've got staff that is simply dedicated 100 percent for the purposes of working on new initiatives and new projects that we just don't have that and throughout the city or in the office thank you and we'll return for action and deliberation so councilmember michael uh i'd like to go ahead and make the motion then to calendar a special city council meeting to develop a work plan for the remainder of 2019 and initiate an inclusive planning process to build a three-year strategic plan and obtain consultant support to facilitate these planning efforts i'll second the motion okay so motion by councilmember meyers seconded by myself um any further discussion did you have a discussion a point councilmember no no just the the seconding seemed strange but that's okay nothing we need to talk about i'll just only echo that um bringing the person being the person who brought forward the item it feels great for me to second the item and i'm all for strategic planning and work planning so that being said we'll go ahead and uh take the vote all those in favor please say i any opposed okay so that passes unanimously i want to remind the council that we are only now adjourning to the remainder of our closed session which was a postponed uh a potential litigation item that will return to the court year conference conference for correct that's right it's specific it's to discuss pending litigation the hatch pomerance versus the city of Santa Cruz lawsuit okay so we'll adjourn to uh closed session


So let's do this one now. It says determine the energy of a mole of photons with the frequency of 3.9 times 10 to the 13th hertz. Okay, so there's a few things in there that hopefully you've caught on to. So they're thinking, or they want you to do a mole of photons. So for this equation, of course, you're going to have to remember the energy equation equals NH frequency. Okay, so when you're given frequency, it's best to use this equation instead of converting it to wavelength using the Rieberg energy equation, which seems a little backwards, obviously. You also have to know that you're going to use Planck's constant, but that's going to give it to you, right? So 6.626, very square kilogram. Yeah, it's on that revision that I gave you before. So we're looking for the energy associated with a mole. So the other thing is a mole, right, is the number of photons. It's going to be 6.022 times 10 to the 23rd photons. If somebody wants to get that door, they'll be lost. So I don't have to do it for them. You wouldn't see the game. I know you need very much more, but so just plug it in and then you should get what you want. So N in this case, it's not one photon. It's a mole of photons, right? So 6.022 times 10 to the 23rd. And if you want to think about it, it's photons per mole. In fact, let's write that out. You can see all the units. Times Planck's constant, 6.626 times 10 to the negative 34 meters squared kilogram per second. Hertz, remember, that's another way of saying first again. For the constant, don't you have to have time seconds again? Or was it? No, that's a different problem. And again, if you thought that, why don't you cancel out your unit to figure it out, okay? So do that first. Okay, so 3.9 times 10 to 13. Are you going to cancel any of those units out? No, but hopefully you remember that 1 meter squared kilogram per second squared equals 1 joule. That's cool with that.


What's going on guys welcome back to the channel critical overload here shows I'm about a few different horror topics in this video here today We'll be talking about screams 7 we'll be talking about Chuckie season 3 We'll be talking about saw X and we'll be talking about Maxine just a little description of what Maxine Reminds me of and what many of you might enjoy if you are a fan of this movie So just to jump into scream 7 Christopher Landon who we know is directing scream 7 replacing radio silence recently talked About how he got the opportunity to direct the upcoming 7th entry during a recent sent down with serious XM He said it came out of the blue for me My understanding is that there were conversations Happening for some time, but I think it was just an opportunity that really Arrows because the other directors who did the last two films Tyler and Matt they wanted to do something else So they were ready to kind of do something different That's when they obviously had to find someone new and I've known Kevin Williamson who wrote the original film for a long long time And he's a friend and you know, I think he threw my name into the hat and everybody kind of said Yeah, that makes sense that seems to make sense and I was just thrilled that I got the call Because it felt very um it felt like Kids it felt like kids Mac it felt like a thing that like was always meant to be He's more or less echoing what I was saying in my video that dropped the week All of that news got confirmed about Christopher Landon and radio silence. So Radio silence had other interests. They wanted to explore things before doing scream again Their contributions to this franchise will always be appreciated despite many people of course I know who don't appreciate it. That's fine. You can not appreciate it. I will many others will But the show must go on Williamson stamp of approval if Williamson really did have a hand in land and being considered Does give me hope that this will be an amazing movie It does not mean it will be an amazing movie because I know a lot of you think that Kevin Williamson has signed up on these Past two movies and I know a lot of you think the past two movies were terrible I I don't think that but I know a lot of you do not care for Williamson stamp of approval because you disagree with his take on the Last two movies because you think they're terrible. So that's my point that you could end up watching scream 7 and find it To be terrible. I personally think that it'll end up being amazing. However diving into Chuckie season 3 Chuckie season 3 has a state of the season Allegedly airing on October 2nd according to rotten tomatoes, which has seemingly confirmed those episode titles that we were discussing earlier this year We have episode 1 murder at 600 We have episode 2 let the right one in episode 3 Jennifer's body episode 4 Halloween 3 and then there's a episode title State of the season, which is airing on October 2nd before the series debuts on October 4th before the season debuts I should say I can only guess this episode is going to either set Expectations for season 3 and maybe it's a recap of the last two seasons to set expectations for season 3 Or it's an update on their plans for season 3 post strikes since they didn't get to finish everything due to the ongoing strikes The episode could actually just confirm the four episodes that we have come in our way While also shedding light on if season 3 will get to finish or not to be honest I'm just I just give us a long season 4 at this point You know if you're gonna have to go back and finish shooting the second half of season 4 or season 3 I just take that and tap it on or tack it on to Season 4 whatever you want to do with season 4 Of course, they can be a time-jump if there needs to be But what do you guys think the state of the season episode will include if it's even legit because it could be BS But Ryan tomatoes according according to Ron tomatoes in this episode list There will be a state of the episode or state of the season episode that airs on October 2nd two days before the season debuts on October 4th now I would say this though I want to speculate really quick on the Jennifer's body episode title as an episode title that does has me thinking That Nika will either possess Tiffany this episode or there's always a chance that Tiffany herself could legitimately die And we'll quite literally have Jennifer Tilley's body on our screen since we know she plays this lovable evil queen of ours Diving into saw X saw X comments from Kevin Grudert who we know is directing Are just getting everyone including me more excited for this upcoming entry saw space tweeted out a series of recent Comments from the director who also addressed the series future and kept discussing surprises We could see any upcoming movie now. Some of these might not be in order It's from a recent edition of SFX magazine. I believe I'm just going over the tweets from Saw space here He said we've learned one way or another that John Kramer is what it's all about This was an opportunity to really focus on him and his story and a really key incident that happens in his life So it led us to a story that is surprisingly pretty emotional compared to the other saw movies Not that there isn't emotion in the others, but it's mostly the emotion of fear There's other stuff in this one. There's hope and there's hope destroyed. I truly believe this is the most standalone since the first movie. It's not about knowing or remembering anything about the others It's a richer experience if you know saw because otherwise you won't necessarily know who Amanda is when she appears There's no obvious new direction to go after this film talking about the future of the series right here There's no obvious new direction to go after this film But I think there's probably or there probably will be more saw movies particularly if this one's successful Well, of course, that's how the business works of course. We all know that in saw X There are surprises to come it builds more on what's in the past than planting seeds for the future There are extended sequences that are not the normal kind of thing you see in a saw movie Really, it's more of an emotional driven epic than anything else So you see when you're talking like that that gets folks like me and many others with these type of comments It gets us intrigued it gets us on the edge of our seat And I know there's a section of saw fans out there who have been clamoring for the series to kind of shed this this reputation is gotten unfortunately over the years for being torture porn and It sounds like we have a chance here to have those people who write these movies off as torture porn to Look at this one and say ah, I see they found their footing again. You could argue that they started to Lean into that a little bit more in the subsequent sequels and just kind of being more so concerned with what type of twist Are we gonna throw in now because that's that's the stick with saw, but if we're gonna see a side of Tobin Bell's character of John Kramer in a way that we haven't really gotten to see since those earlier movies Then again, that's where you have that opportunity for us to get something very emotional Something that might pull at our heart strings because we know John's whole Dilemma is that he is sick these people are doing him dirty And he's going to get revenge against them similar to how there's a lot of people involved in that first movie Who were doing a lot of dirty things John was involved with those people and he went after them So if you can give me an emotional driven story that can just make the villain very layered That's something that can easily Subtract those always just torture porn comments leaning on that emotional side of it that character development can really do a lot especially with how John's situation is relatable to a lot of people who go through something as unfortunate as cancer Not that they would be mindless and Maniacal killers in the process of it all but you get what I mean Last thing we're going to talk about here is Maxine So Maxine window will be the conclusion to Ty West's X trilogy that began last year with X and Pearl so This film like I said at the beginning of the video I want to tell you guys which movie you are going to kind of come out of Maxine thinking that reminded me of Insert movie title the movie Maxine on paper already reminds me a lot of is scream 3 In a lot of ways. There's a lot of DNA that is scream 3 Scream 3s if you will You're not going for any one of you who already jumping to conclusions. You're not gonna get any Roman Bridgers You are not getting that so go ahead and stop thinking that because you're not it's not happening You're not getting any half siblings. You're not getting none of that So what I mean is it's just the the things you have present in scream 3 When you watch Maxine you're going to come out of Maxine saying hey that was like scream 3 I don't want to say in what ways it is like scream 3 I don't mind telling you how it's not like scream 3 so you guys can still be surprised by the killer Because you're not gonna have any Roman Bridger type of things, but the stuff that I've heard about this film as I recap my notes. I'm thinking to myself. Whoa This is like scream 3 but to me already on paper It just seems like it'll be a better movie because I can admittedly say while I love as many of you probably know If you follow my Twitter, I love Sydney's arc in scream 3 so much That's why it's considered my favorite to me anyway However, there are other contributing components of that movie besides just cities arcade I think are severely lacking compared to the others so therefore I do not consider that movie to be the best I think it's still the weakest Sydney's arc doesn't save everything. It just makes it something. I cannot Completely write off especially with some of the other things that it has going for it But it's still the weakest but Maxine when you guys watch Maxine There's a lot of stuff in Maxine that's gonna make you go. Oh, that's scream 3 And I hope those of you who don't like scream 3 because I'm not someone who doesn't like scream 3 I can just I just have no problem meeting.  I just refuse to believe otherwise until I start seeing footage that'll contradict these notes But you guys let me know something about this down in the comment section below if having a record Make sure you subscribe turn on post notification numbers video in the description. I'll have links on social media accounts I'm on Facebook Twitter and Instagram. You can message me there Of course, let me see movies news or reviews. I'm gonna cover in the future and with all that in mind guys I will see you in the next video


Hey everybody, welcome back to Magic Orthodoxy. My name is David and this is a Magic Review. Hey, today we're going to look at parallels from Think Nguyen and Alec Azam. All right, so what is parallels? Parallels is a two DVD set full of card magic. This was a big, huge hit at Blackpool. Let's watch the trailer. Think Nguyen is a true rising star of card magic. The magic he creates is visual and totally baffling. Born in Belgium, he now travels the world lecturing, performing and teaching his incredible card mysteries. Now, for the first time, Think shares some of his most amazing creations on DVD. Parallels is a collection of original routines, moves and techniques that you will absolutely want to add to your collection. That's the first one. Five gloves. And yeah, if you need the other one, it's quite easy because just like this and you do it. One, two, three, and there we go. My name is Peter Nardi and this is parallels by Think Nguyen. All right, so that was Think Nguyen. Like I said, this is being released from Alec Azam. Okay, and you're going to get two DVDs with this. This is the day two DVD set. Couple questions we always ask about all our magic reviews and the first of which is, what's in the box? What's in the box? Two DVDs. Just like I said, it's two DVDs. So you're getting a folder, two DVDs, two discs. Each disc is like an hour plus, so it's almost three hours long, three hours of card magic. That's all it is. Three hours of just nonstop, heavy hitting, creativity, awesome card magic. All right, so what's the overall quality and production value of the video? Alec Azam makes great videos. Okay, you're always going to get multiple camera angles. You're always going to get HD. Your talent is always going to be miked. You always get live performances. So even though it's in the Alec Azam studio, Think Nguyen has an actual spectator that he's doing his tricks with, including David Loosley who's sitting right there. And so there's always close-ups on the things that you need close-ups on. And it's well lit, so it's a very good quality video. Is it well taught? Like I said, David Loosley is there too. David Loosley is there probably because David is just really good at being a second set of eyes. I think that's one of the things that he really brings to the table. He's a second set of eyes. He's there for you to ask those questions that you would ask if you were sitting there like, let's go over this again. Like, how was that? Let's watch that. Let's break that down. Let's slow that down. So he's always there to help with that. And I like that. And I think when you can have two creative minds together, just riffing off each other and kind of like, you know, examining each little nuance, I think that adds a lot to it. So you get the live performance with a spectator. Think Nguyen then actually performs the trick again in the breakdown session with David Loosley. So you get to watch him do it twice, okay? And then a lot of the times there's even little after effects, little side jogged videos where David actually encourages us to think to keep going, you know, keep explaining, keep showing us more. And then really getting these tricks broken down so that you can thoroughly digest them. Skill level. What's the skill level for this? You're going to have to be an intermediate to advanced level magician to do this DVD. Sorry kids, that's really what it's focused at. That's really the approach that you need.  What's taught on the DVD? Like I said, every single one of these tricks is taught two times, okay? You're going to get a Tempus production, which is a four production that switches four for four, a mirror production where you kind of find the four of all the selected card. So the spectator finds the five, you find all the fives. There's an effect on here called Ong's Dice Effect where he has an invisible die. The spectator rolls it and there's a, you know, a thing with numbers. Fairy dust production where the magician cuts to all four of the spectator's card. Then there's another fairy dust trick. I didn't really understand how they were named, where a thing will actually teach you how to make a card float up out of your deck without using any IT or loops. There's another trick on there called Cute Location, which is a triumph that you do under the table. There's a trick on there called Nailed It, where you find the selected card under the table. Then there's the Parallel Cut. She loves me. She loves me not. A moment in time, four to seven and a bunch more. All right. So there's several productions that he's teaching. Okay. If you're going to break down what these tricks are, there's several productions that he's teaching. And then I would also argue that there's a good portion of these tricks where you kind of don't need the spectator. You know, I think there's some tricks that we do where you kind of do need the spectator. They really do select any card. But with some of these tricks, the only card the spectator can pick is the one you want them to pick. So it really wouldn't matter who you did these tricks for. Every single outcome would be the same. You know what I'm saying? So they almost kind of feel like performances where the spectator is just there watching you perform these little miracles. You say pick a card, but they pick the five. You want them to pick the five because you set this trick up to do with the five. Positives. All right. So what are the positives to Parallels? Think Nguyen has such a unique style. Viewers will be mesmerized by each new effect. This is strong advanced level magic sure to bring something new to the table for the season performer. Is it worth your money? It's 30 bucks, 30 bucks. So like I said, $30, two discs, $15 disc, that's about average. Like, you know, three hours worth of card magic. It's definitely in the wheelhouse. Definitely priced correctly. Definitely worth your money. Who would like this? Fans of card magic, fans of card magic who are looking for something new, you know, something creative. I think Nguyen might not be a teacher that comes across your table very often. You know, if you like these style, sandwich effects, collector's effects, productions, that kind of thing. This is definitely in your wheelhouse. You know, your character is the experienced magician, the skilled magician. You have all these like watch I can find cards just by feeling them and touching them and look, I've made all four aces up here. That's you. This is probably speaking right to your wheelhouse. All right. So that is my review of Parallels from Think Nguyen and Alec Azzam. I want to thank Murphy's Magic for allowing me to have this trick so that I can do the review for you. And if you would like to purchase this trick for yourself, you can find it from one of your very favorite Murphy's Magic retailers. Thanks. Bye.