QuickBooks Online 2024 Accounting Process and Forms Overview Get ready and relax because it's so easy using QuickBooks Online you'd think it'd be a crime. But it's not. Unless you're doing bookkeeping for bad stuff or something. But what, let's get into it. Here we are online in our browser searching for QuickBooks Online Test Drive, the primary tool we'll be using for the first part of the course looking for the results that have Intuit.com in the URL Intuit being the owner of QuickBooks Online We'll be using the United States version and verify that we're not a robot. So here we are in the sample company file. We're going to duplicate some tabs like we're going to do every time right clicking on that tab up top. We want to duplicate it so we can put our reports in it. As it's thinking I'm going to right click and duplicate it again. And then as that's thinking I'm going to go to the middle tab down to the reports on the left. Open up one of the favorites that being the balance sheet. And then I'm going to tab to the right and go to the reports on the left. And this time open up one of the favorites the profit and loss or income statements sometimes called the P&L. That's the setup process we do every time. Let's go back to the first tab. So we've gone over a quick navigation of how the QuickBooks System works. We're to find certain things. Now we want to give an overview of the accounting cycle, the accounting process. Now when we set up a new company file you have certain elements in the setup process that of course aren't things that are going to happen on a typical cyclical cyclical type of method. So if you're a bookkeeper that sets up multiple company files and works with different clients then the setup process is often one of the more difficult types of processes and the one that is basically unique to the whole system. Once set up then you're going to do the day to day type of accounting processes and the month to month the cyclical type of things. If you're going to work somewhere else in an accounting office then you're typically going to be diving into a system that has already been set up. So you're not going to need to set up a new company file and do all that first time stuff. Your goal is to deconstruct the cyclical items that have been happening over time to see if you can replicate them making things run smoothly going forward and possibly make improvements usually going to be incremental improvements as you go forward. First a word from our sponsor.  Like our trust me I'm an accountant product line. Yeah it's paramount that you let people know that you're an accountant because apparently we're among the only ones equipped with the number crunching skills to answer society's current deep complex and nuanced questions. If you would like a commercial free experience consider subscribing to our website at accountinginstruction.com or accountinginstruction.thinkific.com So let's go the first let's just think about the goals of the accounting process what are we trying to do when we're doing our bookkeeping here there's two primary goals we might categorize them into at least one is the creation of the financial statements that's one goal the other goal is to facilitate transactions as seamlessly as possible. Now the first goal the creation of the financial statements primarily being the balance sheet and the income statement. This is the end result this is what we're trying to create this is what all the forms are entering into the system so that we can build these primary financial statement forms and related reports all other reports typically tying in to one or multiple line items on these major financial statement reports these reports being useful of course because one if you're small business then you might just primarily be using them for the obligation of tax preparation at least in the United States so we might be using them to comply with our tax obligations of our income taxes and you're going to at least need an income statement in order to do that we also would use these reports for our internal purposes to manage our business to see how well we are doing these will be the primary tools for that and then we might have external users that might need these reports as well we might need a loan or something like that provide the reports to the bank and and those types of things that we could use the financial reports for but in the United States everybody's going to need some type of financial report at least for the tax preparation part of it now the other goal with the facilitating of the transactions that means that I'm going to go back to the first tab that all the people that you're dealing with customers and you're dealing with employees and you're dealing with vendors the people that pay you the people that you pay and the people that you pay the employees as well you would like to facilitate the transactions so that they run as smoothly as possible possibly automated if possible so that the account so that the accounting process is as minimal as it can be while doing everything it needs to do so that the business people the owners of the business possibly you as the owner of the business can then focus on whatever you do in other words if you if you sell guitars then you want to be focused in on how you can increase the sales of guitars not focusing all your time and all your attention on the bookkeeping process so we would like to be as bookkeepers in a way in a system that we're making things as seamless as possible and interacting with it with our transactions with our vendors customers employees as smoothly as possible in a way that it's going to be fast and also that we're not creating problems or angering you know the vendors and the employees and the and the customers in any way by how you know how how things are going to be set up so those are going to be our major objectives from simply the bookkeeping side of things so let's go through the general process if you were to set up a new company file would be that you're going to first you know set up the company file with QuickBooks and then once that is set up you're going to have to then set up the the underlying foundational items which you can often think of as under this cog under the lists so the lists you'll recall is kind of an accounting term but it's kind of specific to QuickBooks as well because some of the primary lists used to be housed under the drop down of lists and the old desktop version so one of the main things that you'll have under the list if I go into the lists is the chart of accounts you could find the chart of accounts elsewhere as well but but I'm just looking at the lists because these are the primary you know set up things to have to set up so the chart of accounts you will usually be given a default chart of accounts by QuickBooks if you just set up a new company file but it's it's usually got way too much stuff in it and so you might want to trim it down or hone it down over time we'll talk more about how to do that and the second part of of the course when we get into creating a new company file from scratch but the in essence the chart of accounts you have to have it because these are the accounts that are being used to create the financial statements the balance sheet and the income statement so these are the accounts that the transactions are being assigned to whenever we enter a form like an invoice or a received payment now if you're starting if you're jumping into a company file that's already been set up then of course the chart of accounts hopefully is set up properly you're not going to be adding and subtracting accounts all the time once it has been established you want consistency once it's been established and you're going to try to use the same accounts as it goes if I go to the drop down again let's go back into our lists and so we have the recurring transactions these are things that could make it a little bit easier if you have recurring transactions you could set them up we might have a section on them in and of themselves later the products and services however is another big one that needs to be a foundational item set up before you can properly enter forms often times so the products and services are the things that you're that you're selling whether they be services like landscaping service the work that you're doing bookkeeping or products like you're selling guitars or something like that you have to have those in place because if I hit the drop down up here and I start to do my data input like invoices or expense forms or bills then I would need to have I need to have a product and surface or service to choose from so once those are set up most businesses have their own products have a set thing that they do or sell and and it'll be easy going forward but you have that's an underlying thing that basically needs to be set up beforehand so then we've got our custom form styles so you could adjust your invoices for example to put your logo on it and that kind of stuff some more other formatting is more important possibly to the forms for data input some of the form customization in other words is just for looks to put your logo on it some of it might be adding fields that will actually have an impact on the financial statements payment methods so you you might if you're going to be accepting credit cards or something like that then you you might have to set up or adjust the way the payments methods are going to be facilitated again once you have that set up it should be easy going forward that would be a set up kind of process thing and then the terms display the terms that determine the due dates that would be something like on your invoices if you invoice a client for example then the question is how long do they have before they have to pay you do they have 15 days 10 days 30 days and so we can set different terms here attachments you could display attachments if you're using tags then tags is kind of like similar to class tracking it's another system that you can use to track your your mainly your income statement by by by tags we might we might have a section just on tags in general so you can look at that but it's just kind of a special area and then custom fields another thing that again if you're using custom fields possibly so that it makes it easier to search for data input once entered you want to set that up upfront and then and then it'll be set up and you'll be good to go going forward now once all that is set up and you have all your lists set up I'll go back to the dashboard then you're going to be in the part of the accounting process where everything should be somewhat cyclical which would be a similar process that if you were going to work for a company which has already their accounting system set up that would probably be where you're at in other words if I hit the drop down here as we saw before we have the different cycles customer cycle vendor cycle employee cycle if you work at a larger company it's likely that you're going to have a very much more detailed and complex things to do but also a limitation in terms of how many things you are involved in so in other words I you might be working just in the customer cycle in accounts receivable for example for a larger company or you might just be on the vendor cycle for accounts payable or you might just be doing payroll within a company if on the other hand you're a bookkeeper you work for smaller businesses the complexity of everything that you're doing will be less in in each of the categories but you're going to be doing everything right in that case you'd be doing all you know you might be working on the whole thing if you're of course doing the bookkeeping process and then all this kind of stuff of course would be a cyclical type of process so if I'm on the customer cycle what would typically happen well it depends if we're on a cruel basis or in a cash based system but as we saw a little bit on the bank feeds we're going to basically this is going to be the QuickBooks desktop flow chart again but it's going to mirror the cycle of the forms that we're going to be using in basically any accounting system breaking out the cycles the vendor cycle the customer cycle and the employee cycle so if you're working within a company and the normal accounting process then you're going to be looking at each of these cycles on the vendor cycle that's the money that ultimately goes out where you might just be entering check forms or expense form electronic payment type forms or you might be entering bills and then tracking the accounts payable paying off the bills on the customer cycle side of things then if you have a very easy process you might just be recording the deposits as they come through something like a gig work but you might be on a cash based system where you have to record the sales receipts possibly and then track them and make the deposit of them or if you're on the accrual cycle you can create the invoice receive payments and record deposit and then on the employees side of things then you're going to have to process the payroll which will record the payroll expenses and liabilities and then you have to pay off the liabilities so you can from an internal bookkeeping standpoint you can access the forms that would be used here in this drop down and then and that would be the data input side of things which would actually record the transactions and that the each of these forms will make a journal entry almost all of them like an estimate is an internal form that doesn't have a journal entry but most of them will create a journal entry meaning they will have an impact on the financial statements the balance sheet and the income statement at least two accounts will be affected for every transaction that we make every data input form that we create and then to facilitate our communication with the vendors the customers and the employees we usually do that in the centers so when I'm dealing with customers I would then go into the customer center here and we would usually be going if I had a common communication with them I can go into that particular customer and I can say okay this is this is whatever this person here and then we can we can see what has happened not a whole lot of activity down here and we can answer their questions right I can go back to my customers now on the customer side I think this one has an amount let's just go into Amy's here so we're so here we have a lot of activity that is happening so if there were questions about a particular invoice or have they paid something and so on this is where we can go and we can basically see the activity and hopefully be able to communicate with our customers that being another one of our bookkeeping objectives to try to keep the people that are paying us happy at least from our end by making sure that the transactions that are being facilitated are being facilitated smoothly so we can you know see the transactions here we can send out our statements and so forth we'll dive into this center in more detail later but this is where we're tracking the accounts payable for the invoices that have already been sent out which is going to be really important if you're on an accrual based system some businesses it's not as important right because if you if you just have if you just doing one time one off sales to people and like a Shopify store or something like that then you probably don't need to I don't need all of the customer information I probably just would like to have them on my newsletter or something because I'm not tracking the accounts receivable they already paid me and it may not be likely that they're going to have another repeat transaction from me right but if I'm tracking accounts receivable and if I'm in a type of business where I have repeat customers then my communication with the customers becomes quite important and then on the expense side of things when I enter bills and whatnot that's in the expenses or what I would say the vendor center and you can go to the to the vendors over here so the vendors similarly for small businesses oftentimes might not be as important to track this information if you're in a system where you're paying the vendors as the bills come up either with a credit card or cash bills come up you paid the utility bill you paid the gas bill you paid the telephone you don't you paid the rent even you don't really need to have a lot of communication with these companies as long as you're just paying them as it comes up however once you start tracking accounts payable then it becomes more important because now like with the accounts receivable side on the accounts payable you want to make sure that you're doing your cash management to pay them as late as possible possibly for cash management strategy without making them angry at you at that which is difficult right so there's a contradictory kind of motives there and usually larger companies are companies that have that accounts payable but also if you're dealing with vendors that are your primary vendors that you purchase from all the time then clearly you want to make sure that you're facilitating the transactions as smoothly as possible and you can track them each of the the vendors in here so I can go into the vendors I can see the bills and the payments of those bills and then if you deal with employees payrolls its own kind of issue but once we would be processing the employees down here so they got the two employees that would be set up we can have multiple ways that we can set up payroll possibly in the system or we can have an external provider like an ADP or a paychecks but if we're running it within QuickBooks then of course we can make sure that the payroll is going out smoothly which is a whole thing in and of itself will touch on in future presentations now the first half of the course we're going to imagine that we are in a system where we're jumping into a system that's already been set up which is this company file so meaning this is the sample company file that already has data within it similar to as if you went to work for a company that already had data within it in that case we're trying to deconstruct what has already happened and then in the second half of the course once we have an understanding of how the process works we'll go into try to create those foundational kind of things such as we saw under the lists up top such as the chart of accounts the items lists the products lists now as we go through this first half of the course we can actually kind of see those foundational things by by basically like auditing them in essence going from the end result and drilling back down in other words we can go to the financial statements over here and we can say okay this checking account has one thousand two oh one in it if I click on it what is included in that checking account and I can I can let's close the hamburger over here you can see the types of forms we've got deposit forms we've got the bill payments we've got the expense forms now the checking accounts going to look chaotic because there's more types of forms in the checking account than any other type of account but the point is that you can actually drill down by clicking on this expense form for example which will take you to the source document so now see how I'm deconstructing I'm going from the end result and I'm drilling back down to how the end result was made and now I can look at the source document and say okay this looks this was put in place here here's the category this is the account that must be in the chart of accounts right in order to have that account here I can't get my list from here but it must be in the chart of accounts let's go here under my lists it's got to be in the chart of accounts in order for me to apply it here so we're kind of we're seeing how everything is built by basically deconstructing the engine so I'm going to close this back up and I'm going to go back if I looked at the income statement for example you can see that on the income is usually going to be a little bit easier to see although still confusing here because they have a job cost system example but if I go into here you can see the detail and here are invoices you don't have as much chaos going on as we did with checking account which has different a lot of different types of forms that are applied to it because cash is the lifeblood of the company and here you would expect to see invoices and sales receipts that's about it unless you have like a really simple system where you're using deposit the deposit as your income recording form I can drill down here and I can go back to that invoice and then then I can see the invoice here and I can receive the payment everything's kind of connected I can see the payment that was made on the invoice so I'm going to close this back out and say do you want to leave without saving yes and then back to my forms and so that's and so that's going to be the primary method will do for the first half of the course will go through each of these cycles customer cycle vendor cycle employee cycle will analyze each of these forms will look at the impact of the data input of those forms on the financial statements deconstruct from the financial statements back to the forms and as we do that will also get some understanding of these fundamental items that must have already been set up in order for us to do that data input such as the chart of accounts such as the products and services and then in the second half of the course you want to start a new company file from scratch so that we can then apply the foundational items that we need to make the company run smoothly meaning like the chart of accounts the products and services the terms you know and all that kind of stuff


Good afternoon. I'm Benjamin Gilbert. I'm a software engineer working on Fedora Core OS. I also still work a little bit on Core OS container Linux. Test. Test. Can you hear me? Oh, you can hear me. I'm Jonathan. I work with Benjamin, also on Fedora Core OS. Cool. Get us to events. Try this guy. Interesting. We've got two simultaneous copies of this going. There you go. Sorry, let me play with this for one sec. I can see what's going on. Oh, I see. It's only moving. Sorry about that. Okay, so what is Fedora Core OS? It is a new edition of Fedora that we're building specifically for running containerized workloads at scale. If you've heard of Core OS container Linux, this dates from Core as Incorporated, which Red Hat acquired, what, a couple of years ago now. And container Linux has been pursuing a similar model for several years. It's a small integrated OS specifically for running containers. So we're continuing that sort of model plus integrating technology from Fedora Atomic Host. Here's the mission statement. But I think there are a couple of elements that are important here. Fedora Core OS is targeting several different sort of workloads in this space, or use cases in this space. It is targeted at clusters, but it does not necessarily require running in a cluster. And obviously we're interested in running in the Kubernetes ecosystem, but we're not going to require that either. It's also possible to use Fedora Core OS to run containers of standalone. You may have heard of REL Core OS. So what is the relationship between these operating systems? REL Core OS is specifically intended as a component of OpenShift. It updates along with OpenShift. It's versioned along with OpenShift. It is based on the Red Hat Enterprise Linux package set. So there's not actually a separate skew, as we say. You can't download and use REL Core OS as a standalone operating system. It's something that's just integrated into OpenShift, and you shouldn't have to think about it. Fedora Core OS is targeting a slightly broader set of use cases. It shares some of the components in tooling. It shares a lot of the same people working on it. But it is standalone. As I said, it's targeting a slightly broader set of use cases, and it's based on the Fedora package set. So there are a few elements that's important to understand about how we think about actually both of these operating systems, Fedora and REL Core OS. And the key one is immutable infrastructure. These philosophical elements are not things that are embodied in code exactly, but they affect how we design the operating system and how we want it to be used. So immutable infrastructure. The idea here is that you'll need to make some customizations to your operating system, right? You might need to set the host name, configure static IP addresses, configure your container runtime. And the idea is that all of those customizations should be encoded in a single file, which is the provisioning config. And then that provisioning config is given to the node when it first starts, and it applies all of the configuration. After that, we think that you shouldn't go in further to configure the node. You can SSH to the node and change things. You can use configuration management tools if you'd like. We don't stop you. But the problem is that then your provisioning config gets out of sync with the actual state of the node. So what we think you should do instead is change the provisioning config and spin up a new node using it, and then tear down the old node. So essentially, once a node exists, you treat it as immutable. And the reason for that is then if you want to scale out due to changes in demand, then you can just launch new nodes with your current config and not have to think about configuration per se. So another philosophical component is that software should run in containers. The operating system is for supporting hardware. It's for providing the container run times. But if you're running your own software on the node, it should always be in a container. Toward that end, we don't ship interpreters. We have bash, obviously. And Awkin said, if you count those, we don't ship Python, we don't ship Perl, we don't ship Ruby. If you want those things, run them in a container. Similarly, ABI compatibility for libraries within the host is not something we worry about too much. The operating system is self-consistent, but if you copy some random binary onto the node, it's not guaranteed to keep working over an OS upgrade. And speaking of OS upgrades, OS versions themselves are in implementation detail. Think of the node as something like an appliance. It should auto-update itself. I'll talk about that more later. But really, you shouldn't have to think about it. And in particular, when a Fedora major version upgrade occurs, if you go from Fedora 30 to 31 to 32, that should just be a regular upgrade. You shouldn't have to think about that at all. Okay, so what does this operating system look like in a little bit more detail? It's targeted at cloud instances and bare-metal servers. We aimed to have it available on a wide variety of clouds, all of the usual suspects, really. Workloads, as I said, should run in containers, which means that the operating system image itself can be pretty minimal. There's not a lot in it. It's an image-based distro. So you're not running DNF. You're not installing RPMs. You get essentially a monolithic file system image, and then it is updated atomically. So if you've heard of an RPM OS tree, you can think of it a little bit like Git for the operating system. You have some revision, and then when an update comes along, you pull that down and apply it atomically to the disk and reboot into it. So you're never running in sort of a half-upgraded state the way you might be with DNF. On top of RPM OS tree, we add automatic updates. So RPM OS tree, by default, will upgrade when you tell it to, same as DNF. We are adding a system on top of that, which automatically fetches and installs updates, and again, we'll talk about that a little bit more later. So specifically, what clouds? The targets that we're focused on right now are listed there. That also includes virtualization systems like QMU. One note, though. Some clouds, often, you'll find if you launch in, let's say, GCP or Azure, many Linux operating systems will include those clouds agent. The agent does different things depending on the cloud. On some platforms, it has to check in with the cloud before the cloud believes that the OS is booted successfully, for example. Sometimes it provides additional management functionality so that from the cloud's web interface, you can add users to the node or maybe even run code on the node. In general, we are going to try to avoid shipping those platform agents. A lot of the functionality is not all that meaningful for a sort of more specialized operating system like Fedora Core OS, and not all of that code is uniformly well-advised. And so what we are generally trying to do, we have a piece of code called Afterburn, and it is sort of a generic minimal cloud agent. So on those platforms where you have to do something special to get network configuration or hostname or to tell the cloud that you are ready, Afterburn will do that, and we will use that instead of the cloud agents. On the bare metal side, it is pretty much what you would expect. You install the operating system to disk and run it, except for one thing. In some sense, Fedora Core OS is a cloud-native or cloud-first operating system, and in the cloud you don't have an installer. There is nothing like Anaconda.  And so bare metal for Fedora Core OS doesn't have an installer either. What we do instead is essentially a shell script. You run a thing, and it fetches a monolithic bag of bits, and effectively just DDs them to disk. Consequences will get to in a minute. But the idea is that the install process is as simple as possible. One other note. Container Linux supports live pixie, so you can essentially just run your entire production OS from RAM and never install to disk at all. We are going to have similar functionality for Fedora Core OS. This is actually fairly widely used on Container Linux as a way to even further minimize the footprint of the operating system on disk. So what is in Fedora Core OS? Of course it has all the latest Fedora Bits, system DE, kernel. It's not based on Gen2. We have all the basic hardware enablement software that we need. There's basic administration tools. Like Benjamin was saying, we don't expect you to log into Fedora Core OS that much to play around with it because everything should be set up right from the beginning with your Ignition Configure from the provisioning step. We'll talk about Ignition after. But we have SSH, of course. There's R-Sync, guitar, all the basic stuff. You can check the journal to do some basic debugging and stuff. Of course, there's Container Engine. So we have Podman, Moby, and SystemDN spawn. And then we're still discussing how we'll provide the Kubelet and Cryo 2 nodes. So watch out for more discussions about that. Okay, so how do you actually provision a Fedora Core OS node? So Fedora Core OS uses this tool called Ignition. Ignition is very similar to... an idea to cloud in it for those of you who are familiar with how Fedora Atomic Host was provisioned. So Ignition takes in a configuration file. This file is a JSON document and is provided using whatever the user data mechanism is for the platform you're targeting. So in most clouds, you can pass in some user data. So what can Ignition do? You can write files. You can write SystemD units. You can create users and groups. But then you can also do fancier stuff like partitioned disks, create rate arrays. You can format file systems. So for those of you coming from the rail Fedora side, it's sort of a mix between cloud in it and kickstart. And that's part of the reason why, as Benjamin was saying, the bare metal image and the cloud image are actually the same thing. Ignition is sort of taking the place of kickstart and cloud in it almost. So the reason why we can do those kind of powerful manipulations is because Ignition runs in the init ramifest. So it runs even before the system is really booting. It runs exactly once. And most importantly, if anything fails during the provisioning steps, if anything in the config can't be executed, it'll fail the boot. So that means that if your node came up, you're pretty confident that your configuration has been obeyed. Okay, so how do you write an Ignition config? So like I said, the configs are in JSON. It's super mechanical. It's not that pretty. It's unsugarred. So we have this sort of layer on top called the Ferrochorus config language. So this one is meant for humans. It's in YAML. So it mostly maps onto the Ignition config, but it has some additional sugar for things like, if you want to set your time zone or if you want to set whenever update windows for when your node should update, things that the Ferrochorus config transpiler will convert into things that Ignition understands. I sort of jumped the gun because the next bullet actually explains what the transpiler is. The transpiler is the thing that converts the YAML into JSON. So it converts the Ferrochorus config file into the Ignition config JSON that Ignition actually understands.  Oh, I missed a closing bracket here so I have to reprovision the node. Okay, automatic updates. So this is basically one of the key features of Ferrochorus. It's inherited from the continuous Linux philosophy of automatic updates. And the basic idea is users should not have to think about updates at all. The machine should just take care of updating itself. It should be able to just pull in the latest bug fixes, the latest security patches. A consequence of that, if we really want this to work, is that we need automatic updates to be rock solid. We need it to be super reliable. Because if it's not reliable, users will just turn them off. And if users turn them off, they don't get the latest fixes. They don't get the latest security patches. So that basically means we can't have any breaking changes and if we do envision any sort of breaking change we need to have a really long deprecation window that we publicize widely. So how do we make sure that we don't break changes? We don't introduce breaking changes. So a lot of CI, obviously if the build doesn't pass CI it's never going to make it to the users. But then we also have some sort of process level mechanisms. So Benjamin, after, is going to talk about managed update rollouts and the different release streams that we have with different semantics around breaking changes. And then finally we have automatic rollbacks. So the node is capable of, let's say it pulls down the update. It reboots into the new update. And if there's something wrong with that new update, for example, some service doesn't come up, it'll detect that and it'll roll back to the previous update, the previous version that it was on. This also includes the ability for users to specify additional checks that the boot has to pass before it's considered a successful boot. So you can imagine if in your scenario you can have a service that you really need to be up. And if that service is not up, even if everything else is working you don't want it to propagate across your fleet. Okay, so I'm going to do a demo now of the, I guess the provisioning workflow and also the automatic updates. Oh, this is going to be interesting actually, because I can't see, let me switch into mirror. I guess we'll revert the settings. Is it not? It's just dead now, isn't it? Okay, fun. Let me try something here. We're trying to make it mirror. Oh, there we go. You can go ahead though. So you talked about the immobility of the nodes, but then you also talked about kind of bringing up a parallel system. Yeah, sure. You talked about the... You can't change the nodes once they're up. We also talked about having updates and a live reboot system. And I just, those were kind of, I didn't quite understand how that worked. Right, we think of the system as immutable from the perspective of the config. So the user, again, is free to change configs and things, but probably shouldn't. The node itself will continue to update. So it's not truly immutable in the sense that it's a fixed bag of bits that never changes. It's just that we don't want the user poking around at the system after it's done. Can everyone read the font? Okay. Okay. So this is a PhotoCoreOS config. So it's YAML. It's through every field, but basically we're telling, we want our config to create a user, a core user, and we want it to have a specific SSH key as an authorized key. And then we also want it to write out a systemDunit file. So now we have this YAML file, and we'll convert it to... Actually, let me bring that up. We'll convert it to the ignition JSON. To do that, you use this tool called PhotoCoreOS config transpiler, shortened to FCCT. And actually, I'll just use my bash history here. So you give it the YAML file. This is the file that we had just opened. And then we want it to output to JSON. Enter. And I'll just show you quickly what that looks like. So essentially the same information is there just in JSON, but in the future you can imagine more complex things in the YAML that gets translated to many more things in the ignition config. Okay, so let's boot up a machine with this config. So actually, I'm going to boot up two machines. One is going to be on the previous version of PhotoCoreOS, and the other one will be on the latest version of PhotoCoreOS. And the reason I do that is the one that's going to be booted on the previous version will be for demoing automatic updates. But for the purposes of provisioning with an ignition config, I'm just going to use the latest AMI. Because you should always be using the latest config normally. You wouldn't have a reason to use the previous one. Or the latest AMI, sorry. So, okay, this is a lot of goop. But essentially the key part here is we do AWS EC2 run instances. And right here the user data, that's where we're passing the ignition config to the cloud. So let's run that hopefully conference Wi-Fi is on our side. Okay, cool. Okay, so I provisioned two instances. So the second one is the latest AMI. So I'm just going to fetch the IP for that, actually. So remember the ignition config basically had the authorized keys that we wanted to add in a systemdunit file. Just a dummy foobar in it. Okay, that's fun. Might have to wait a little bit more. Let me just double check here. 380, 140, 187. Okay, so we're in. So the fact that we logged in, that means that the SSH config went in. And then let's check our systemd service. Okay, our bar has been food. Very cool. So now let's look at automatic updates. So I'm going to log into the second instance that I put it up, which was actually the older version. So it's this one. Okay, so this is interesting, actually. Okay, so right now it's on the previous version. So I didn't actually show you the archmage status of the other node that I booted up, but it was on 0801. And this one is on 0725. So it should be in the process of updating, and we can check that by looking at the status, the journal entries for Zincati and Appianmostry. So Zincati is a service that actually checks for updates, and when it finds an update, it'll tell Appianmostry, okay, upgrade to this latest update. That's what happened. Okay, filter query Cincinnati. Okay, so Zincati will retry in five minutes. Do we have that luxury? Well, what I can do is... Okay, so now Zincati detected a new update, and then it's telling Appianmostry to deploy this new commit, and now Appianmostry has deployed it, and now the node is rebooting. Yeah, so what just happened there was that we start the update client without respect to whether networking is already up, because if the first attempt to check in fails, try again in five minutes, it's fine. But of course, for a demo, it's not so fine. Yeah, let's see how quickly AWS nodes reboot. What's funny is when I tested this earlier, it honestly reboots fine within the first two or three minutes. It doesn't hit that race condition, but the one time you do it live... Okay, so there's already a good sign here, which is in the login prompt thing, it already tells you the latest version you're on, and this is the latest version. So we know the upgrade went well, and if you do an Appianmostry status, you can see that it's in the new deployment. So if you're not familiar with Appianmostry, this is basically saying I was in this previous version in 0725, and now I'm in this version, 0801. And let's go back to the presentation. Cool. It's married now, so... Yeah, cool. Okay, we do a couple interesting things with respect to how we publish install images and upgrades. So as I mentioned before, when you install Fedora CoreOS, you're essentially just fetching a monolithic set of bits and copying them directly into your desk. In many Linux distros, you can go to some FTP or web server somewhere and browse around and see all of the release images. We intentionally do not enable that for Fedora CoreOS. The older release artifacts are still there, but we think it's important to exercise closer attention to which images are being published. So the starting point if you want some Fedora CoreOS bits is a JSON document at a public endpoint. And it's highly nested, so I didn't put it in the slides, but if you look at that JSON document, you index by the CPU or architecture you want, the platform you want, such as AWS or GCP, and then perhaps even the region of AWS that you want. And when you get down through all those levels of nesting, what you get at the end is, okay, here's the Fedora CoreOS version, here's the perhaps cloud image ID, or here's the URL to the download you want. And the idea is that if you have scripts, for example, that fetch a QM image and deploy it to your machines, those scripts start with the stream metadata and always know what our recommendation is for the OS version to run. In fact, the download site, which is just a traditional download web page on getfidora.org, reads the same JSON document. So the idea here is that if we put out a bad release for some reason, and then we find out about it, someone files a bug or whatever, we can stop new deployments from using that release because we'll point the stream metadata back to a known good release. So this always represents our recommendation for what's the safe release to run. On the update side, we have something similar. So you saw it in CAUTI just now. Before performing an update, it checks in with a service run in Fedora infrastructure, which gives it permission to update and tells it, essentially, here are the versions you can update to. That lets us roll updates out gradually. General Linux did the same thing. When CAUTI checks in, it picks a number between 0 and 1, and it says I'm interested in being this aggressive for this rollout. And, you know, if I'm a client and I say I'm, my aggression is 0.4, and the server says I'm only rolling out releases to 0.3 and below, then I won't get that update yet. I won't even be told it exists. So what that lets us do is just roll out releases gradually over time, and that means that if someone reports a regression to us or we find out about it in some way, we can stop the rollout without having bladded this update to however many, to the entire fleet of nodes. And other things in CAUTI can do, so that's sort of a distro-wide piece of functionality. But individual nodes, individual clusters can also be configured to have their own services that they check into. So if you're running a cluster, you probably want to make sure that every node in that cluster doesn't update at the same time. And the way you can do that is have ZenKETI call a service in your cluster and say, may I update now? And that service can make sure that it gives permission to exactly one node at a time or two, maybe it only gives out permission in the middle of the night, whatever it is you want to do. We will provide at least one implementation of an example service or you can provide your own. Release streams. Jonathan mentioned automated CI before. CI is good, it can't catch everything. We are shipping the Linux kernel, we are shipping SystemD, we are shipping multiple container runtimes. That's a lot of code being written by a lot of people and CI is just not going to catch all of the interesting bugs. So when we roll out a release, we want to be able to do it in a way that users can test it with their workloads, with their network configurations, on their hardware and let us know if there are problems before it hits the entire fleet. So the way we do that is we start with Fedora 30 right now plus the set of update packages and every two weeks we snapshot that and we make a release on the testing stream and the idea is users we would encourage to run a few percent of their nodes on testing report problems to us. After two weeks, we take that testing release and we maybe make whatever fixes are necessary add security fixes, whatever and roll it out to the stable stream and that will be rolled out over time to everybody. We also have the stream next which is intended to give extra baking time for longer changes. So for certain types of things, a two week test period is probably not enough. That's things like new substantial kernel releases, Fedora 31 as a whole and so those sorts of things will be on the next stream for longer to get more time to get feedback. As it says, we hope users run a little bit of testing, a little bit of next in production next to their stable nodes and in order to make that work we will apply critical bug fixes and security fixes to all three streams. So you're not in a situation where I'm running next and that's fine but there's this unfixed security vulnerability. One other thing that's interesting that we're doing is we're enabling machine counting by default. There's a trade off here. One of the things that we've found with Container Linux, with Fedora Atomic Host, Fedora as a whole, in fact, it's very difficult to focus development time if you don't know how many users you have and what they're doing. So for Fedora Core OS do we spend more time on AWS? Do we spend more time on digital ocean or packet? Making those platforms better, that kind of thing. On the other hand, privacy is important. This is free software. People don't want their machine spying on them and we understand that it is very important to us as well. So we're trying to strike a balance here. By default, Fedora Core OS will report some sort of generic information about nodes that are running and by what time really mean not identifying information? So this is things like, I'm running on AWS. I'm running an M4 large instance type. My OS version is X. The original installed version of the OS version was Y. These are things that hopefully are applied to enough people that it shouldn't fingerprint a node. If you want, you'll be able to opt into reporting additional information, like if you're on bare metal, what type of machine you have. There's probably fewer of those. So it might theoretically fingerprint you. Or, of course, it will always be possible to completely opt out of this reporting. The key point here is we will only look at this information in aggregate. We will not look at individual records and no unique identifiers will be reported at all. The way this effectively works is that once a day the node says, oh, I need to report in and give this information. But there's no unique IDs. We feel it's important to have this on by default because otherwise we won't get an accurate sample. But hopefully we're preserving the privacy properties that we want to be preserving here. And we will carefully document in the Getting Starting Guide and everything else that this is going on. Okay, so how do we actually build for a CoreOS? So actually this is shared with Red Hat CoreOS. The main tool is CoreOS Assembler. So it's sort of this collection of capabilities that together make it really, really easy to build for a CoreOS locally. So it's both used for developers, for development purposes, and for production. So essentially, just with three steps you can build for a CoreOS locally. You do COSA in it, and then you give it this repo. So that for a CoreOS config repo is where all the definition files for what goes into for a CoreOS live. So, you know, all the packages. And then soon we'll have lock files. So actually, specifically what version of each package we want in there. And then fetch, fetches the packages and build it, of course. So a cool thing about CoreOS Assembler is it can run fully unprivileged. So under the hood it uses RPMS3, of course, to convert the RPMs into an OS3. And then Superman. So Superman is both used for doing the unprivileged stuff, but also for actually creating the disk images that become the cloud or the bare metal images. A big difference between for a CoreOS and Red Hat CoreOS compared to, let's say, the rest of our traditional Fedora is it does not use Anaconda to build images. So there's various reasons for this, but the idea here is, like I said earlier, Ignition is sort of the only tool we want to have to specify how you want your machine provisioned. So how do we actually run the CoreOS Assembler in production to build the production images is a for a CoreOS pipeline. So it's simply a Jenkins pipeline that will run CoreOS Assembler in OpenShift. So everything happens in OpenShift, and then we push those out to the S3. Okay, so where are we now? There is a preview release of Fedora CoreOS available today. It's not ready to run in production, so please don't. What we'd like people to do is try it out, report bugs to us, report missing features. Be aware that we're reserving the right to make backward incompatible changes during the preview period in order to fix things or improve the design. In more or less five months from now, we're planning to have a stable release, at which point we will recommend that Fedora CoreOS is ready to run in production. So specifically what's next? We need to finish implementing the all three of the streams that I mentioned. We're working on adding additional cloud invert platforms, support for architectures other than x86, live pixie support that I mentioned also, earlier, also live CDs, some work around network configuration, additional sugar for the config transpiler. Machine counting right now is actually only a stub. It reads the config file and makes sure that it's valid so that you can configure your nodes, but it doesn't do anything yet. We will have much more documentation and we are also working on some details around integration with OKD and Kubernetes generally. This is worth calling out specifically because the OKD for effort is getting spun up at the same time. In the short term, the plan there is to essentially branch Fedora CoreOS and bolt in whatever needs to be bolted in just to get OKD to a minimally working state to have a demo. After that we will start working on integrating that OKD work back into Fedora CoreOS. There's one distro that's used for OKD use cases for other Kubernetes distros as well as for non-Kubernetes use cases. I listed there are a couple of open issues in order to make that happen. Finally, a note on the distros that we came from. Fedora Atomic Host has not updated to Fedora 30 and will go end of life late November or so depending on Fedora schedules. Container Linux will continue to be maintained for about six months after the stable release of Fedora CoreOS and we will announce exact timing when we get closer to that point. For Container Linux users will provide migration tools and docs and as much help as we can to help people migrate their existing workloads from Container Linux over to Fedora CoreOS. Here's the usual list of places you can go. The website is the download site. It also links to the Getting Started guide. The second link is essentially the focus of development for Fedora CoreOS and then there's some other places you can discuss Fedora CoreOS with us as well. Thank you very much. Looks like we have about two minutes left. We can maybe take a question or two and I think both of us will be available outside after the talk. Thanks. My question is about what updating and releasing Fedora CoreOS will look like. So, do you plan on releasing, for Amazon case, regular AMIs and then if I wanted to update Fedora? And how often will you release those AMIs? I'm hearing nods, so that means often. Sure. So, the exact timing is subject to some change, but all three streams will release at least every two weeks. In addition to those scheduled releases, we can have out-of-cycle releases. So, if there's some major security update that needs to go out immediately, we'll do special releases on all three channels for that. And that will be an update payload and it will also be new AMIs, new QMU images, everything. Okay, so you plan to release the OS trees and the image builds at the same time. Yes. Perfect. So, you mentioned towards the end of that about OKD and the integration of this. When you say by branching Fcause for this, do you mean specifically like there's going to be a separate OS tree stream and a separate image stream for this or is there going to be like some kind of overlay, package overlay or container overlay? What do you mean by that? Because that's kind of confusing, especially I came from just hearing the Silver Bull talk and he was talking about all kinds of weird things you can do on top of the RPM OS tree core for this. We don't actually know right now. It may be a separate OS tree. That was, I think, what we were talking about at first. Then we started talking about just doing package overlays. The latter approach is cleaner because it requires less extra stuff. We want to go for the smallest possible branch. Not clear what that's going to be yet. Two quick questions. One, automatic updates. Is that going to destroy custom things? Second question, if you add all the bug fixes to stable, how does that keep it stable? Right. So the first question, if you have customizations in Etsy or you have something in opt, for example, that will not be destroyed by an upgrade, the parts of the system which are modified by an upgrade are read-only, so you can't accidentally get yourself in trouble there. And the second question, sorry, remind me. I'll have to keep it stable if you add in all the objects in the stable. Carefully. So it's a tough, we've been dealing with this on the container linux side for several years. It's a tough call. If there's something which is a large change and probably not that urgent, we would roll it through testing first. If there's a change which is small and urgent, we would probably send it direct to stable. If there's a change like fixing spectra and meltdown, which is important and also a giant patch series, we may have to hold our nose and send it directly to stable, and that's not ideal, but it's a judgment call. Yeah, we will... Yeah, we'll do that when we feel we have to, but with security updates and really critical bugs, there's a judgment call sometimes. Anything else? Cool, thank you very much.


Live from San Francisco, California, it's theCUBE at VMworld 2014, brought to you by VMware, Cisco, EMC, HP, and Nutanix. Now here are your hosts, Dave Vellante and Stu Miniman. Welcome back to San Francisco, everybody. We're here at VMworld 2014 or at Moscone South, just inside the lobby to the right, come by, say hello, love to see you. So this is the fifth year for theCUBE at VMworld, and we've seen the transformation of VMware from what used to be called the software mainframe. The marketing guys got a hold of that term and have really evolved it into the software-defined data center. And Stu and I are really excited to have Bindi Gillon. He is the chief architect at Nutanix, hot company, one that we introduced you to quite some time ago, and we've been following the ascendancy of Nutanix. Bindi, welcome to theCUBE, good to have you. Thank you, say hi. So a lot of talk about convergence, hyperconvergence, software-defined, you guys got ahead of that whole curve. We saw some announcements today, everybody's trying to parse through those and understand them. Give us the update on Nutanix and then we'll get into the sort of architecture and the technical piece because you were essentially at the de facto CTO of the company, so please. I mean, we have come a long way since we started. I mean, early on we were talking about converging the hardware, so the storage hardware and the server hardware and why converging them makes sense. There are many people who thought that may not work because the compute side and the storage side have different refresh cycles and all of that. So we have gone through all of that now the entire world understands why convergence is a good thing, why server side flash is a good thing. Now we're talking more about web scale. Once you actually take monolithic San and NAS boxes and the capabilities and sprinkle that capability into hundreds of servers, what you have to now grapple with is the scale at which the storage functions have to be developed. And that's the web scale movement that we are at the forefront of. Yes, Stu and I have been tracking and folks at Wikibon, the whole hyperscale Stu piece bleeding into the enterprise. It's something that you've covered extensively, you've written about it. Obviously you've written about server sand. So it's happening. Yeah, Dave, when I joined Wikibon, and I came from a heavy enterprise focus and very different architectural design from the web scale guys. So really exciting when you get to talk to James Hamilton from Amazon, talk to Facebook, what they're doing with open compute.  But Binyam, I'm wondering if you can share with the folks, your team, I've talked to guys in your organization that are former Facebook and Google architects, worked on some pretty amazing technologies that those really big companies and are helping bring those to the Nutanix portfolio. Right, I mean, so what we have done is instead of tackling just the storage problem at the get go, what we have said is, let's take a pause and see how have the web scale companies evolved the data center. So if you look at what they did, they did not start off with a NetApp or an EMC or NASA sandbox, what they said is that they need massive scale. And to do that fundamentally, first they did is they changed the storage architecture. So that means you converse the storage piece and the compute piece. The way they did that though is they shipped the compute piece to where the storage lied. And that is the invention of big data, that's the invent of MySQL, that's the invention of MapReduce and all of that. All that goodness does not directly apply to enterprise data center because there's a lot of legacy applications that need POSIX interface, a lot of applications that still need the notion of a virtual machine. So we took those web scale concepts and said, first we will build a web scale foundation on which now you have strong consistency. That's why we had to delve into multipack source that was distributed. We had to build MapReduce from ground up that would look at your metadata and then give you a lot of the features of DDU, Snapshot and all that. And then we said, we have this web scale foundation that will get rid of silos in your data center and now we build storage on top. And that's what we have done with the employees that have come from these various backgrounds that bring that mindset and the religion of web scale to us. So, Bini, the other thing I want to let you address is those really big companies, a lot of times they're talking about a single custom application or maybe a handful of applications, most of the enterprise is usually, I mean, dozens or hundreds of applications. So why is the architecture still applicable when I get away from a single app to go to virtualization and kind of the typical enterprise environment? So yes, so it's not about the architecture, it's about the discipline. So I'll tell you what, if you want to do one thing right and get web scale is follow the scale out principle. The scale out principle says that if you have a service running on a given node, that service should use resources that are proportional to the size of the node and not proportional to the size of the cluster. So as you're increasing the size of your cluster, the services should not become hotspots and bottlenecks. And that fundamental religion is what is important. Now you say, okay, I understand that, how do I keep metadata? And suddenly your answer would be that you need NoSQL, you need MapReduce. And so those are the things that we learn from the big guys, not necessarily exactly their application stack and how they build it, right? And then we say, enterprise is a complex environment, right? And great companies like VMware have created a lot of solutions around that. So how do you take the goodness of VMware, the goodness of Microsoft and KVM ecosystem and also going forward into the cloud and provide web scale to those environments in a seamless way? You know, when you put Nutanix in a box, it just works. You don't have to do anything special on the high provider. So that's the key. It's the ability to scale out seamlessly. You say seamlessly, everybody. When I hear seamlessly, I think, oh, I can add capacity and not take any downtime and not take any application disruption but there are architectures. I won't name them right now in the queue, but I might later, where the customers have said, well, yeah, it's scale out, but when I scale out, I take some downtime or I take disruption or I have to go through hoops. I presume that's not the case with Nutanix but I want to push on that a little bit. I mean, philosophically, that to me is not really seamless scale out. What's your take on that? I mean, again, if you look at Google, if they add a new node, Google doesn't take a downtime. I mean, those are fundamental things that it's a no-brainer to make sure that you enable that. In fact, we focus a lot on a single click upgrade for an entire cluster, no matter how large it is. Upgrading not just our software stack but also upgrading things in our ecosystem, like the hypervisor, the device firmware and stuff like that in the same way. And that is, you know, the fundamental tenet around web scale is making sure that there are no silos because when you have broad convergence into the data center, what you have to understand that is you don't have a single monolith that everybody can point to and get to the data. Now you have scattered that all over your data center and you better be sure you're not creating silos around that because the biggest pain point in the data center is not about just adding nodes necessarily, it's about agility, right? So I have a virtual machine running here, an application, I want to move it from one place in the data center to the other. Well, in VMware, you can just click on the VM and do vMotion, you're done. Well, not really. What if this virtual machine had 10 terabytes of data sitting here and now that's sitting in a different silo? And silos could be performance silos, capability silos, hardware silos. Protection silos. Yeah, protection silos, all sorts of silos. And then you say, okay, the data is sitting there, my application needs to go to the other end of the data center. What do I need to do? You need to implement fine-grained data migration, right? And that's where the complexity of a metadata layer, that's built on NoSQL, just like Cassandra, that enables us to do it on a fine-grained level. The hard-working set follows the virtual machine, not just within a data center, but also when the VM moves or the application moves to a different data center, doing deduplication, compression, at a fine-grained level across data centers and clouds, that dissolves the silos in the data center. Yeah, we've done studies at Wikibon that quantified the cost of migration, an example, the cost of migrating a storage array well north of $50,000, 20 plus percent of the original cost of the array. So based on what you just said, I'm presuming that you're able to take that cost down dramatically. Yeah, so if you're running on the Nutanix virtual computing platform, and you're moving things around, you don't have to think twice. There is no cost, there is no planning you need to do it. Just do it. Just do it. Do what you want to do. Yeah, I mean, Dave, when we did the server-sand architecture, you know, David Floyer said, taking out that migration cost is one of the key tenants of server-sand, and of course, Nutanix is a great example of that kind of architect. Benny, you talked about the cloud a couple of times. When I first talked to Nutanix, you guys were VMware, it was the environment that you worked on. You guys announced something, I believe it's called CloudConnect, relatively recently. Can you talk a little bit about that, and how do you extend from kind of the data center beyond the individual data center to the cloud? And what did you guys talk to me for that? It comes back to solving silos, right? So now today we have a divide between the public cloud and the private cloud that is growing. What the enterprise admin wants to do is I want to move applications from my private cloud to the public cloud. I want to burst my applications into the cloud space, and also some amount of freedom of choice. You know, they want to go to Amazon, they want to go to Azure, and stuff like that. So what we have done is, you know, taken our architecture, our software, and put it on EC2. So now we have our controller virtual machine running on EC2 and providing the same services as it provides in the private data center. Again, the reason we can do it is because we don't have a hardware crutch, and it runs beautifully on Amazon as well. So now, currently, we put the cold and old data onto Amazon, but going forward, it's about moving workloads from one location to the other, and all seamlessly. Yeah, so, I mean, at this show, we've seen some of the challenges that VMware is having with competition. You know, it's a multi-hypervisor world in many ways, Microsoft's been gaining sure Red Hat's doing well in their spaces, Amazon and Azure, of course, in the public cloud.  From kind of an architectural standpoint, and what you're looking at, how is Nutanix positioned for multi-cloud, multi-hypervisor, VM container bare metal world? Are you guys a VM only, or how does your architecture span? So, I mean, if you look at our intellectual property, it's all in software, right? Now it's a question of how do you package that software?  I mean, nothing stops us from taking our software and run it on a laptop, for example, or in a container in a docker on bare metal. What we want to do is focus on the enterprise pain points, and if VMware is at running in a lot of servers and our customers are running VMware, so that's where we provide our value. And now we have seen the shift from VMware to Hyper-V and the need for open source KVM. So we have provided our functionality there and there's no reason we can't go to Docker as well. All right, so Vinny, I know we're running short on time here. You came from IBM research. I mean, IBM got over a hundred years of creating some of the best innovations in the IT industry. I mean, way too many to name. I worked for Lucent for a bunch of years back in the 90s. Bell Labs is the one I always greatly respected being an engineer at training. What did you learn working for research that you've brought to Nutanix? How do you guys kind of look at the future and look at the research that you guys are doing? Yeah, I mean, so one of the main things to learn from research is you need to empower engineers, empower technical leaders with the ability to fail, right? So the permission to fail is the recipe to succeed, right? So fundamentally, you have to understand that there are hundreds of startups out there that want to build a Nutanix killer now, right? Now they have the permission to fail. Most of them would fail and some of them would succeed. How do you bring that culture into the company as a first class citizen and say everybody is allowed to take big bets, take risks, and make it work as if it's a research organization. And that's what keeps me up in night and make sure that that culture is what we maintain as we are growing, doubling every year. So I wonder, Bini, if we could, maybe sort of one last touch point. How should we think about the Evo rail? Everybody's talking about, oh, it's kind of going after Nutanix and others, so we had Sam from Delon this morning. He's like, no, no, no, no. Very complimentary. Nutanix is like IO killer. They're unbelievable at IO and we're positioning. So how should we, what's Nutanix's point of view on this rail announcement? So it's a very good thing for us, actually. It's a great validation for what we have been talking to our customers. We've been telling customers, look, you need a control plane that is different from the control plane you're used to. A lot of the things around analytics about VM management need a different look at it. So we have built Nutanix Prism UI earlier this year. We announced VM analytics. So we look at the health, CPU, memory, network, storage, layer for virtual machines. All of that now becomes easy for us to actually tell the customers, look, you've got to be open to a new control plane. And by the way, this control plane is going to be the same web scale as you're used to on the data plane from Nutanix. Awesome, hyperscale coming into the NEC prize.  Vinny Gill, thanks very much for coming on for theCUBE. Appreciate it. All right, keep it right there. We'll be back with our next segment right after this. This is theCUBE, we're live from VMworld 2014.


You have what they want You have what they will never have You're empathic You have love and compassion.  It's the reason why they use the push-pull tactic Because they want to make you theirs They want to own you like an object or a toy They want you to belong to them But you willingly participated in it. You chose to be with them You may have even fallen in love with them, but they could never reciprocate those same feelings back to you Because they never wanted to love you.   They made themselves look good at your expense And they hope that after they've taken everything they wanted from you.   They don't want to be exposed. They don't want the truth to come out Because then people would realize that you're not the problem They would realize that this person who portrays themselves as an angel or saint is the problem That is why they don't want you to say anything That is why they want to destroy you That is why they don't want you to watch this Because they don't want to be told what they are And they don't want anyone else to know about it Because they want to continue on their path of destruction But now you know the truth about the narcissist You know something that most people don't know and anyone else who knows what you know It's going to go through the same thing that you went through The narcissist wants to destroy you Because they're envious of your qualities and abilities They're envious of your productivity and performance They're envious that people like and admire you because they want that for themselves Which is why they're constantly thinking of ways of how to manipulate and exploit you So that they can take pride and pleasure in your notable achievements While a normal person would focus on trying to be productive They would focus on trying to contribute But the narcissist is thinking of gaining advantage over you. They're thinking of destroying you So that they can take credit for your accomplishments and success By using you involuntarily For their own support and encouragement for the furtherance of them in too So that they can move to a higher position and level at your expense When you stand up for yourself The narcissist will try to shut you down Because you've told them that their behavior is not acceptable and they don't like it They don't want to accept it But there's no point talking to them about it There's no winning with the narcissist There's no opportunities for advancement They're just going to take advantage of you Which is why the best thing you can do is gray rock or go no contact Because now you have the education You understand how they operate You understand that they want to destroy you And they may try to over you But it's only because they want your supply it fuels them it keeps them going and They're checking if you're still alive They're checking if they've destroyed you They're monitoring your pain and suffering They're seeing if you've managed to recover and move on and if you have managed to do that They will come back They will try to get a little more out of you. They will try to finish the job They will try to destroy you once and for all because that's their goal when they try to come back to you They're not coming back to engage in unity and harmony. They're not coming back because they love you or miss you They're coming back because they've realized that they didn't completely destroy you the first time Which is why you should never respond to the Hoover attempts Because although they may act like they don't know what they did wrong They are fully aware of their actions and the effect that they're having on you. They want to destroy you From the moment they set their sights on you you became the focus of that anger and frustration They singled you out as the person to beat a post persecute and replace You just didn't know it But now that you are aware of it You need to protect yourself You need to gray rock or go no contact You need to blog them on social media because they want to destroy you So as long as you're in contact with them It's not going to end well Thank you for watching. I hope this video resonate with you Please like comment share and subscribe If you would like to donate My PayPal link is in a video description Coaching inquiries you can email me at coaching at laksafivert.co.uk Thank you for watching and I'll talk to you soon


We are ready. Good afternoon. I'm Mike Farnworth, British Columbia's Minister of Public Safety and Solicitor General. I want to thank you for joining me here today. And I'd like to acknowledge that we are on the traditional territory of the Laconguit-speaking peoples, the Esquimalt and Songhees First Nations. This last month has been unsettling for British Columbians. We've witnessed gun violence in public spaces and broad daylight in different parts of the province. This morning, a gunman killed two people and injured two more in multiple shootings in the city of Langley and the township of Langley. This senseless act of violence is extremely disturbing and completely unacceptable. My thoughts are with the victims, their loved ones, and the communities impacted by this despicable act. These people are members of our community, and I understand that British Columbians are worried and fearful when events like this happen in our neighborhoods. We don't know the motive behind the shootings. We don't know the motive behind the shootings. However, with today's tragic events, I want British Columbians to feel assured as more info becomes available, we will make that known to the public. I want to thank the Langley R-C-M-P, the Lower Mainland Emergency Response Team, and all other first responders for their quick response. This remains an active police investigation, and it's important that the public continue to assist them in this work. Now, despite these tragic incidents, I want to reassure everyone that the police work hard every day to make British Columbia a safe place to live and to work and play. Every single member of the BCR CMP and all our independent municipal departments put themselves in the face of danger. They work hard 24 hours a day, seven days a week to keep us safe. And their passion and commitment to public service is redoubled in the face of the types of events that we have witnessed in the last couple of years. I want to thank you for joining me today, and now able to take questions. Thank you. Thank you. A reminder to reporters on the line, please press star 1 to enter the queue for the opportunity to ask a question and a follow-up. Our first question today comes from the room. We go first to Richard Zussman, Global News. The emergency alert was used. Will you be reviewing it all the way in which it was used in this situation? But only the second alert without a mention of Langley that led to some confusion and the fact that the alert only ended 3.30 this afternoon, sort of lingering after hours and hours. Will there be a review and what do you make of those circumstances? Whenever there is a situation such as this, there is always investigation and there are always reviews. The police were dealing with a very fluid and dynamic situation. This is only the second time in the province that an active shooter alert has been used. And so of course they will review how things were done and the way they were done. But the bottom line is this, they made decisions based on the information that they had on the critical ensuring of public safety. The area where the shootings took place is a very high traffic area. The area where the shootings took place is a very high traffic area, very densely populated. Communities use it going all the way from Chilliwack, Abbotsford, coming through the valley and likewise coming from Richmond, Vancouver, going out that way. So there would be a wide-ranging alert in place. But as I said, reviews are always undertaken in situations such as this. Follow-up, Richard? Considering, and I know RCAP has clarified some of this, I'm saying that it mentioned transient populations. Some advocates are concerned that these alerts won't get to transient populations because they often don't have smart phones or data on their phones. So in circumstances like this, will there be a consideration of changing the way that alerts are done? And feeling the heat that we're feeling now, what consideration is being given to potential alerts later this week for the heat levels that we're seeing across the country? And I'm not sure exactly because while they're related, they are different. In terms of the alert, the police have protocols in place in terms of when they issue an active shooter alert. As I said, after every situation, there's always a review done to look at how you can do things better, what lessons can be learned. At the same time, these alerts are one tool. The police have many different methods to use other methods to notify people and they're aware when they become aware, for example, on transient populations, that there are other ways to also ensure that they are alerting people. When it comes to the heat, the considerations about using the alert for heat situations, as you know, we have put in place recommendations from the coroner's report in terms of when heat warnings and then heat emergencies are communicated. They are put in place by experts and they're based on both the daytime temperature and the nighttime temperature and they vary around different regions of the province. For example, in the case of Vancouver Island and the lower mainland, they're based on a temperature of 29 degrees for a high and 16 degrees for a nighttime high. In terms of the warning, it's over two days and over the emergency, it becomes three days. In the interior, it is a higher temperature, it's over two days for an extended daytime high and the nighttime low, I believe, is 19 degrees. So those things are in place and those decisions are what guide the experts in terms of when it is time to issue an alert. For the next question, we'll go to the phones. We are from Matthew Claxton, Langley Advanced Times. Matthew, please go ahead. Hello. I wanted to ask our local sources say that at least one of the incidents took place directly outside or on the grounds of a supportive housing institution. The homeless are uniquely vulnerable to this kind of violence because they're so exposed. What can and is the government doing to help prevent these kinds of attacks on the homeless? First off, this is an ongoing police investigation and the police will be continuing this, no doubt looking at every aspect of the tragic events that unfolded in the last night and early this morning and then we'll be coming out going, you know, with exactly what happened. At the same time, whenever there's a situation such as this, there's always one, there's the police investigation, but there's always reviews done in terms of ensuring what lessons can be learned. The use of alerts is one way of ensuring that the population, that people know what is going on. At the same time, there are ways of communicating and contacting people and in this case determined that it is, that it may well be targeted at the homeless population. So there's a variety of ways in which the police will respond, but as I said, we always look to learn what lessons we can from tragic situations such as this. Matthew, do you have a follow-up? The police have not yet released what type of weapon the shooter was using. What type of weapon the shooter was using? What's the rationale for not releasing that when the situation is over? The gunman is dead and certainly we should know if it's a long gun or a pistol or whether it was a legal or illegally acquired weapon. This is an investigation that is still underway while a shooter is deceased. The police will be doing a full-scale investigation to determine was there a single weapon, were there multiple weapons, what exactly did the police do and did they have in their possession? I expect in due course that information will come out, but right now the focus of the police is on the investigation and getting as much information as they can to understand exactly what took place. Our next question comes from the phones as well. Lisa Eustace, City News 1130, please go ahead. The first alert came out 30 minutes after what police have said was the last shooting. Why was there such a delay? This is a dynamic and ongoing situation where the police are dealing, they don't know whether they are dealing with a single individual or is there another individual as well? It's an active investigation. They make decisions based on what is happening on the ground and the best information that they have. After the investigation is completed, obviously there is reviews to understand how and why the alerts were issued the way that they were done. But the one thing that is pretty clear, the police are obviously going to err on the side of caution in terms of ensuring public safety. Lisa, do you have a follow-up? Yes, with the information that was included, especially on that first alert, the second as well, there was many people who said they didn't know what to do. There wasn't enough information there to say should I stay away from what they should do. Do you think that there was correct and specific enough information to let people know how they should react to the information they were receiving? The alerts went out, the police made a decision on what goes into the alerts. They assessed what is happening on the situation. I think most people would understand that if they see an alert and the alerts are saying stay away from a particular area, they will stay away from the place, recognizing that where the shootings took place was a very high traffic area with a significant commuting population taking place at that time, from all the way from Chilawak and Abitseford, going west to people going east in that direction.  As I said, there is always reviews after. We come back to the room for the last session of the session. I will now turn it over to Keith Baldery, Global News. Regarding yet another matter, the escape from the prison by those two bogus contractors, why isn't the correctional facility in efforts to identify these people, at least a video still of their faces of these two individuals or do they not have to do that? This is a major criminal investigation involving a high-profile escape from a correctional facility. The police are very much involved in that investigation and there may well be legitimate reasons why they have not released videotape at this point and it's probably best to direct that question specifically to them. That being said, I have said that I expect answers to those questions because the public have those same questions as I do. But right now is a major investigation and the police are handling that investigation. Follow-up, Keith? Further to that, you said on the weekend you were investigating the police and there was an investigation. Do you have any sense when some of those answers might be forthcoming? Not at this point. Other than I can tell you, this is a major investigation involving the police on a high-profile alleged killer and the police are putting all kinds of resources into one, locating the whereabouts of this individual, but also finding out exactly how it happened. Thank you, everyone. That concludes today's


Welcome folks. We have the Dow Industries right now trading up well, let's read out card. I know without my growl I get that get a little discombobulated here. We'll get that ground next week I'm getting there though to master love you have to practice love The out of relationship is a whole mastery and the only way to reach masteries with practice to master relationship is therefore about taking action Not about attaining knowledge Market wise out here. Let's take a look at it folks. We have the Dow Industries down 149 Nasdaq up 33 S&P's up seven and a half gold gold contract down $13.80 trade at 1864 an ounce We have silver down 34 cents $22.39 an ounce lights we crew down 99 cents $90 73 cents a barrel notes and bonds a 10 year note up five ticks trade in 108 flat 30 year up six ticks at 113 22 and King dollar King dollar right now Where are you King dollar? You've been all over the place, man How does this happen when I get there it is King dollar down 79 ticks at 106 144 the euro 105 the end straight at 149 the British pound is at 122 to 1 US dollar iPhone numbers<PHONE_NUMBER> it was called folks. I know it's going on in your world now in the world that he has some peas Let's take a look at them. What do you have well? And take a look at this S&P what you're gonna see is that we came right down to the breakout area yesterday You did reject lower price at the 422 area Yeah, and I had big volume. They had 104 million and you're going into like 88 Couple days before that you had 118 that being said bottom line was that we bounced off it, okay? Now we checked at 425 this morning and you can have some decent volume So it's telling me that we get a bounce on that's for sure now. We'll see where that bounce goes We get a big gap that's laying out here at the 430 area 438 area actually 438 Yeah, the 438 area We go take a little let's go take a look at the E minis Entry day because where this dollar goes for the next hour is where the S&P is going to go So if we take a look at the E minis But we have that was a good bar this last 10 minute bars a good bar man So if I take this And go from highs to lows today we just did a point three a two Just spiked it See that there wasn't how the any volume on the way down here today, you know, this was interesting So the probability is that you're still going to try to get higher So let's go to the note bond market first because the note bond market is correlated with the dollar So if we take a look at the 10 year you're going to see the 10 year 1.8 million contracts not holding price that well though We did we are we got to 108 14 and I wrote 107 31 you know, so That doesn't look to me they that can press in so the high of yesterday the high of the low is 108 08 no Yeah 108 oh 8 You know, so if you dig it into this again, let's say in that that bottom can get tested Then let's go over to the dollar because the doll is the number man. It's just pretty amazing how the currency is running everything Well, it makes sense because it the interest rate structure is what's actually running it. That's keeping the dollar strong So we take a look at this dollar what you're going to see this is this is what you want to look at folks Now I'm giving you this on on a weekly basis, but this is going to be the number If you we take a look at it what you're going to see is this you have two different areas Mark both of them the first the first area though is the area that we actually went into this week Which is the low of the downdraft and that downdraft was pretty dramatic We went from 113 to 106 in one week. Okay, so just like an act just like an equity This is the currency, but just like an equity when you do that you have that type of price spread I mean this side there's a month's the sell of it so the bottom of this is 106 281 We're at 106 162 so 206 106 281 yeah 106 281 If you close below that one of 106 281 that would be a failure in price And that'd be saying that okay, that's what that's what's trying to do the whole time It failed and we'll see whether they get any follow-through next week on the way down You know if you don't fail there if we close above that then that swing point is going to be game And the swing point above it isn't to that 107, you know It's been relentless though. There's no doubt about that. We take a look at let's go over to the oil market and take a look at oil so CLA Oil contract out here at a high of 93 today a low of 90 You get 322,000 contracts. I don't think this is done yet. It's a good. It's a close call But I don't think this is done yet, you know, you had high volume all the way up to you know, almost 93 You know, you get lighter volume yesterday, but you'll be a pulling back with light volume compared to what it's going into That's how this is set up inside the MDX 100 The strength versus the weakness you get Walgreen boots is up 580 about five and a half percent microns up four and a half percent Let me just look at micron because I want to I think this is just a dead cat bounce My micro was the one that was down bad yesterday Yeah, that's microns down with volume is today monster so that's just They cut people on the wrong side today.  You get Oh bank. I'll bake a hues bake a hues off 3%. Let's look at Baker Hughes Because it become interesting if they start smoking these oil stocks, that's gonna be a heads up Yeah, that's down with late volume though Stay right there folks. We're coming right back and bottom line folks. Okay. We got our man, Mr. Peter Bruno Peter is gonna be doing a show on TFNN It's gonna be Wall Street money hour and Peter has been in this business a long time He was actually on the same station. I was on for like 20 years in the West Coast Peter and I coming right back


Hello, and welcome to another episode of the Minor Issues podcast. I'm Mark Thornton at the Mises Institute. Now I have no plans whatsoever to buy an electric vehicle, but you can't help but notice all of the problems that electric vehicles have exhibited so far. The fact that they're largely, if not entirely, fueled with fossil fuels. The fact that their infrastructure charging stations are problematic. That there's almost no reduction in pollutants. That the government's program is a giant subsidy for rich people. Or that the impressive technology in electric vehicle batteries, all of those resources could have been devoted to other, more pressing issues. And of course, then there's the rush to try to find the precious metals and the rare earth elements necessary to produce these vehicles, which scarred environments and had severe negative impacts as well as positive impacts on the affected population in those areas. Now this environmentalist agenda of electrical vehicles has been pushed on Americans with the sole help of very heavy subsidies. That's a quick and dirty way of achieving your goals, but it leads to very bad misallocation of resources and impoverishment and things only get worse over time rather than better. Now I've noticed recently two elephants in the room with electric vehicle sales. The first I put under the category that bigger is not necessarily better. That in designing subsidies, the government has produced a system which is heavily beneficial to very large vehicles with very large battery capacities. Electric vehicles, solar power, all of these things tend to do much better with small lightweight, short distance, small capacity issues so that it would favor things like hybrid automobiles and compact electric vehicles, golf carts, police cars on the island of Manhattan, specific uses which would enhance or at least ameliorate issues of economic efficiency. On the other hand, fossil fuels are well documented to be the preferable economic fuel when you're talking about heavy lifting, long distances, large capacities, trucks, planes, ships, where fossil fuels obviously have a comparative advantage. The problem here is that the government's actual subsidy has dropped hybrids and encourages large vehicles with large battery capacities. In a sense, the government subsidy is fighting electric vehicle comparative advantages and at the same time losing any possible pollution reduction advantages. So the first elephant in the room is that the subsidies encourage big cars with big ranges, not the smaller, cheaper vehicles where the biggest positive environmental impact might have existed. The second elephant in the room is that because electric vehicles and their batteries are so large, the cars essentially have become elements of mass destruction. I thought that in changing from an oil gasoline-powered engine and gas tank, if we took those two things out, that electric vehicles would naturally be lighter, easier to move around and so forth. But now the batteries have become so large and heavy that electric vehicles sometimes weigh hundreds or thousands of pounds heavier than fossil fuel vehicles. This of course creates a lot more wear and tear on our roads and higher taxes to keep them up. And also obviously it creates much more dangerous vehicles for the driver, for the passengers, for pedestrians, and of course people in other cars. There's going to be more death and destruction because of these very, very heavy batteries that are necessary to produce these long range driving features for electric vehicles. So when you look at the electric vehicle market and you see this problem of pushing large luxury cars rather than efficient smaller cars or hybrids, and then you take into account the fact that the electric vehicles are much more dangerous in terms of driving in accidents, it makes you wonder about who set up the subsidy and its broader economic implications. In other words, very heavy electric vehicles, that's a problem. Much more dangerous electrical vehicles, that's a problem. But it also I think most importantly tells us a little bit about, or maybe a lot about, the people who are bringing these things and forcing them onto the American consumer. Those small things should have been dealt with, they should have been expressed to the American people in the first place, but they weren't. And I think that minor issue tells us a whole lot about our government, who's running it and who they are running it for.