Hello, in this lecture, we're going to continue on with the master budget. We're going to move on to the selling expense budget here. Let's take a look at the process real quick. We do need to go in order in this case. We started off with the sales budget. We need to do the sales budget before we can do anything basically in the budgeting process. Then we looked at the production budget. How many things are we going to need to produce? How many units do we need to produce in order to meet the sales? And that would allow us to think about how much stuff we need to purchase in terms of raw material and how much we're going to need to pay in terms of wages, which are probably the largest to expense if we are manufacturing stuff. Then we had the factory overhead, which included a variable and fixed portion. And now we're moving down here. These are kind of more of the miscellaneous type of budgets, and they'll be different depending on the type of industry that we are in. We will generally have some type of selling expenses. And it just depends on how we incur those selling expenses in different types of companies. So we're going to have to look at the problem and see what we have in there. In this case, we have a sales commission for part of our selling expenses. And it says here that the sales commission is 9% of sales. So sales commission percent of sales paid. So what that's trying to say here is that we are going to pay sales commission at 9% of the sales. Therefore, we're going to start off with the budgeted sales. And we're going to get that amount from the sales budget, obviously, which we did all the way up top. So within July, I'm going to select equals, and I'm going to scroll all the way up to where we did the sales budget and point to that number. So we're going to scroll all the way up to the top. And I'm looking for the sales budget. Here's the sales budget. Here's July. And so it's over here on the 494. This is dollars not units. So this is the dollar sales. That's what we're going to calculate the commission on. I'm going to select tab. Now we are in August. I'm going to do the same thing for August. So we want the sales numbers from the sales budget. So I'm going to scroll all the way up and hit equals first, then I'm going to scroll all the way up to the top. And we're going to go to the sales for August, which is in dollars 478 400. And then we'll do the same thing for September. So we're going to say this equals scroll all the way up to the sales budget. And we're looking for that 42 four. All right, so we've adjusted this to put the dollar sign in there. So we can see that we are talking about dollars here. And there's always we always want to keep that straight when we're going through the budget. When are we talking about dollars? When are we talking about units? Okay, so now we're going to multiply that times the sales commission percent. And we're going to give a 9% sales commission. So 9% all the way across for July, August and September. We can then calculate that out. So that means that if we had sales in July of 4944 times 9% sales commission, we're going to pay sales commission of 44 496. Same thing for August. We're going to say 4,490 times the 9% and tab. Also note that the 9% is a percent, of course, because of the formatting of the sales, meaning if you go to the home tab and the numbers group and you want to hit the percent sign if you want it in the format of a percent, otherwise you can just type in 0.02. Also note that you want to have the decimals where they should be in order to display the amount of decimals that you would like to see. So then we're in September, we're going to say this equals the sales 4924 times the percent of 9%. So that gives us the sales commission and we have some more blank space. So I'm assuming we have some other stuff related to sales. So we're going to have to go down here and what we're looking for in the materials is what stuff is related to sales versus the administrative type of information. So commission, of course, would be a sales type of activity. We can also see down here that we have a sales manager monthly salary. So obviously anything that says sales in it is probably going to be somewhere in the sales budget. This is going to be a fixed cost in nature and that it doesn't change from month to month. So July, we're still going to pay that. Supervisors 3-5, 3-5 for August, 3-5 for September. Therefore we can now, that's all that we have in terms of sales, stuff that says sales in it in our information. So we can add this up. So we're going to say July, we have the 44 commission, 44, 496 plus the 3,005 of the salaries gives us a total sales of the 47996 and we're going to multiply this out as well through August, this plus, this I should say, tab and then September equals the commission plus the salaries and enter. Also note once again that this could be have surrounding in it, meaning if I go to the home tab, numbers group and I increase the in decimals, this one came out happened to come out or even, but just be aware that it is possible that we could have some decimals there because we're talking about a budget. I'm very happy to just round it to the nearest dollar because pennies will not be generally material to decision making. So now we're going to move on to the general and administrative expenses and once again this will be


Great. Thank you. Before we go find out whether open source one or not. Let's go back one step and just say thank you everybody for joining us. I'm Karsten Wade and I'm from community architect working on operate first. And let's go ahead and dive in. So we all know the story about how open source one, right. First, originally you had a mainframe and you could buy the software and the hardware from one vendor. And only the manuals were there to help you use it and there was no way to improve this tool. But in the opening and of the computing in the components of the data center by by open sourcing all of these open source was able to return back to everyone, the value of creating and running software. And suddenly now everyone can be involved in the open source development model and it's it's wide open to the in the hands of the people. So we can rest on our laurels right or or can it. So there's been a shift in the day since open source went from a foothold to really taking over and opening up the data center. Starting with the operating system, it grew outward to provide all the core data center services. But one of the important powers of open source was that theoretically anyone could get the software and make it run. They can operationalize it and do things with what is otherwise a cold lump of code. While many were writing the software, everyone had access to the code to do things with it to turn their computer that was essentially just a warm heater to actually operating and doing something. So this level the playing fields for all for using these tools, but this leveling meant that we could compete or innovate or get lazy whatever we wanted to do. We had a fair and equitable chance to make that happen as we wanted when writing software, especially from scratch is hard, but learning operations one acts action or standard operating procedure at a time is far more accessible. So as more and more value was found in the operation of the code and not just the creek writing of the code. And that came along with the dawn of the era of cloud computing, and that brought an increasing ability to capture that economic and innovative value with all that workload data, and its ability to improve operations all inside these proprietary environments. This provided the public cloud operators with a recursive feedback loop that essentially paid them to learn through micro failures. They provide the compute and infrastructure as a service level that also allows them to be continuously learning from the telemetry. So to be learning from what had always been exhaust of the back of an IT shop, because of the scale of logs and data versus the ability of humans to parse that into meaning. So the open source movement had done was succeed in involving the way we develop the software as a people, but we never saw the problem of operating that software in a truly compatible way, making it possible for all open source to come self operating, whether operating at small scale or operating at large scale, whether it's go figured out slice and dice new configs from old it's all in the wrist to the complete reinvention of operations as an engineering discipline. It does little good for the improvement of open source software when developers cannot get access to and learn from a live production cloud. This learning has been restricted to employees at large organizations that implement these dev ops and SRE practices. This restriction of knowledge for the what and how and the why of operationalizing open source software means the developers of the software being operationalized with proprietary ops, do not gain from that knowledge. Again, the open source developers don't gain from the knowledge of that operationalized software. They have no chance to actually watch that code running in production environment. So open source projects have a natural method for incorporating knowledge back into the code base to try and true process here. And we're open source projects are purposely built to allow for natural progression of curiosity that needs a fix I wonder if I can contribute that fix. What should I change. How do I make it work. Oh, my change broke. Oh my god, others can use my change. How do I release it. All that interest gets turned into a contribution. But that doesn't work on the closed operations side of open source software, which I'll lump back here as a software as a service essentially, and that quickly chokes off that interest toward making a contribution. And, and that interest was making the software better. So software as a service drives out this funnel, because you can get stuck right at the beginning, where you don't have access to the stuff that runs the service. What operate first brings in is the power of open source, the ability to turn users into contributors. And now that you can see all the operations, you'll be able to contribute to not just the operations but to the part that you that are most important to you as a user developer. And that opens up that wealth of data developers for improving our software. This means for developers have read only access to all the data, and by all the data we need the metrics the logs the support issues created just as you would have access to every line of code in an open source project. And open source communities thrive because of these easy onboarding processes, meaning we can turn just a small fraction of users and contributors, where you can read about a problem or report a problem and then if you really want to walk that mile, you can resolve the problem. So this is what operate first is. It's a concept to incorporate operational experience into software development by extending development to include operating, testing and proving that code in a production environment, a live production environment, ongoing lifecycle testing, no pipeline looping end. And I'm going to notice here that that this is a method that that doesn't just mean open source it's, it's beyond it's a DevOps methodology it's something that people are doing already internally. So it's us taking this operate first methodology and applying it to open source ecosystem. And we know from the parameters that by the very nature of open source development, if you can provide meaningful data back into development from a live production environment, it's going to have exponential improvements, not just to that code base but beyond. Open source developers who gain meaningful data, as they tweak an upstream library are using it's a 7% improvement in performance, those developers are going to have an easier time convincing upstream to accept their patches. That's just the tip of the potential. So now let us. I'm going to start here and shift over. Let's talk about community building in the operate first context. We want to be inclusive to all personas to be inclusive in this context means to welcome those that wants to get started on a journey in a certain area and be inclusive to those who already mastered a certain area. So somebody who wants to learn how to run a cloud environment and wants to get their hands dirty and those who already know how to do all this and wants to share their knowledge and want to train people. So really be inclusive on that complete spectrum from beginners to professionals and experts in a certain field. What personas are we targeting? It starts with operations with service reliability and engineers and DevOps people that run, maintain all the components. Then we have developers that create workloads and want to run applications in that cloud but also those developers that develop certain building blocks of the cloud. Being inclusive to those who use the cloud without any users you will have a very sad deployment that is a service that nobody really uses. Only if you use it you will run into those corner cases. Being inclusive to people that do product support who help users and connect them to developers and operations people to solve problems and create better documentation. Being inclusive to architects, architects in the sense of building a certain use case and want to run and deploy this use case in the community cloud open for inspection, open for usage by users, open for inspection by developers and work together with the ops people to make this deployment stable and a pleasure to use. And then at some point also inclusive for all the robots and the small integration tools that help users and ops people alike and someday feed into AIOps tools and will have this self-healing and self-driving cloud environment. So how does this operate first community cloud production environment look like? We started out with one cluster at the Boston University or mass open cloud. That's in a physical data center. It's comprised of a large bare metal cluster running in that environment. But we also extended that into a deployment running in Europe at Hetzner. So we already have something that spans multiple geographies one in the United States and one in EMEA. We also have clusters running in the actual cloud in AWS. And we're looking forward to extend that into other bare metal data centers at universities and into other cloud providers such as IBM cloud. Now with all these different data centers and clusters you want to run workloads there. On the forefront we have the open data hub which is a project for doing cloud native data science. So you will have things like Jupyter Hub there, Kubeflow pipelines and other data science services. This service is available for everybody in the community to use and inspect. Then there's other workloads such as Thoth which provides services for AI DevSecOps and build pipelines. We have some projects from the Java community such as AP Curio, Quarkus and a POP, a Python index. And we have a lot of other smaller deployments so workloads are running across these multiple data centers. Obviously you want to manage and automate all this stuff. There's ACM Advanced Cluster Manager which is being used for deploying clusters and managing clusters. We use GitOps for deploying workloads and deploying clusters configuration. For that we have Argo CD and then we have Prowl, a CI tool from the Kubernetes community. We have Tecton pipelines for running our build pipelines and we have the observatorium components for doing monitoring such as Prometheus and Loki for storing logs. So all these tools are there. They're open for usage, buy and inspection from the community. And we consider everything as a service. So Open Data Hub and the Tecton pipelines or the monitoring stack. They are not only used to run the cloud but they are also exposed as a service that everybody in that community can reuse and build on top of these services. And at that top there are these operators which you can run in your cluster and everybody can use that as a service that an operator provides. And we have relaxed requirements for running these operators. In your typical production cloud you might need to convince the people that run the cloud for getting a community operator installed. But in the Operate First cloud we really embrace beta and alpha versions of operators or community operators available for trying things out and see how they integrate with all the other components there. So it's really open for a variety of different operators. And obviously we want to create lots of operational data because without all the data open for inspection you would always start from scratch. So whatever we create here is preserved for later inspection and for people to build upon that knowledge that we create and to inspect the data that is being created. And then maybe train some AIOPS models on top of that data. Since it's really, really hard to get a hold of data that is proprietary, we try to be as open as possible and create all the metrics, create all the logs, create all the incidents, all the tickets and give them back to the community so that they can build upon it. The same is true for blueprints. Blueprints are basically architectural decisions that rewrite down and distill into documents so that you can follow that train of thought. If you run into a similar problem or if you're facing a similar decision such as how do I store my secrets? How do I manage single sign-on? And these decision records can be used as a basis if you want to create a similar deployment of that Operate First Community Cloud. So we invite everybody to partake and join the community and help building out this variety of tools and best practices. And now a demonstration of the Operate First Community Cloud in action. Demo one, onboarding a cluster to the Operate First Community Cloud. In this demo, we onboard an existing OpenShift cluster to the Operate First Community Cloud environment. Steps, one, add cluster to Argo CD, two, enable single sign-on, three, enable monitoring. Let's get started. In this demo, we're going to explore how we manage OpenShift clusters within the Operate First Community Cloud by showing you the cluster onboarding procedure. We're starting here at the welcome screen of ACM, which stands for Advanced Cluster Management, which is a RedHeads product based on Open Cluster Management project. On this screen, you can see the fleet of clusters under Operate First Community Management. ACM allows you to directly provision OpenShift on various providers, as well as connect existing clusters to the fleet. Adding a cluster to ACM means executing a single command as a cluster admin on the target cluster. In this demonstration, we'll focus on this demo cluster, which is already connected to ACM. As you can see, it's running OpenShift 4.8, it's running on AWS, and it's powered on. In order to onboard this cluster under our GitOps management, we're going to follow this Jupyter notebook guide. We use Jupyter notebooks since it works nicely as both static documentation and as an interactive guide that can be followed and executed. By the end of this notebook, we'll get a Git commit that we can open as a pull request against our Git repository. As you can see, this particle guide has some prerequisites to have an OpenShift cluster up and running and to have that cluster connected to ACM. We've already done that prior to this demo. This whole guide is written in a script-like pattern where we can set all the necessary variables in the first cell and then just execute the rest of the notebook. For the sake of this demo, we'll take a closer look at each of the steps, but in real life this is not necessary and we can execute the cells as they are. In the next step, we're going to fork and clone the Apps repo. As you can see, I already have a fork available. Let's clone it and change our working directory. In Operate First, we manage all Kubernetes resources via Argo CD. To connect our Argo CD instance to this new cluster, we use ACM integration capabilities. ACM can set up the Argo CD cluster connection, create a service account on the target cluster and set up proper permissions. We instruct ACM to do so via a shared KIDOPS enabled cluster set resource. So all we have to do now is to label the managed cluster resource for this demo cluster by the appropriate cluster set label. We will add this resource to the ACM application folder in the Apps repository. Next task on the list is to enable SSO on the demo cluster so users can log into its console using social login. Let's see how the situation looks now on the cluster before enabling SSO. I'm going to open the console for this demo cluster and also a console for this other SMOKE cluster we have so we can compare it. On the demo cluster, we're only prompted for credentials which we don't have. On the SMOKE, on the other hand, we have this Operate First identity provider tile that can be used for direct access. In order to enable SSO on this new cluster, the first thing we need to do is to configure our SSO server instance to accept the new cluster as a client. We can do that by a keyclo client resource. We will use the cluster name as a client ID and a generated UUID as our secret. Next up is to propagate the same credentials to the onboarded cluster. We create a secret resource containing the client secret and encrypt it by a source. Then we patch the OpenShift's OAuth resource by adding a new identity provider. As you can see, we reference our keyclo server as the issuer, specify the client ID to match the cluster name and reference the secret we created above as the client secret. Now we can assume we have SSO in place on the cluster so we can define a cluster admin user group granting cluster admin role to few users in case of emergency. As you may have noticed above, all the resources that should live on the onboarded cluster as part of a cluster management live in an overlay in the cluster scope folder. Since we are effectively creating a new overlay in this folder, we need to define a customization file so Customize knows which manifests to bundle and how to combine them. Here you can see we are pulling resources from a common overlay which defines shared resources like user groups. We are also pulling some other resources from a base. There we keep track of all privileged resources for all of the clusters. You can find username spaces there, operator subscriptions and so on. We will store this customization file in the cluster scope folder as a new overlay. In addition to the basic onboarding, we are going to enable proper monitoring on this new cluster. We will leverage OpenShift user workload monitoring which is a centralized Prometheus-based stack. Enabling it is as simple as pulling in a config map patch into the cluster overlay from cluster scope base. To complete the monitoring stack, we deploy an GitHub alert receiver instance which consumes cluster alerts and turns them into GitHub issues that makes them publicly accessible. We already have all manifests in place for that. So in order to add the alert receiver to the new cluster, we need to create a cluster-specific overlay in the alert receiver folder and adjust a few labels and such. Now we will put things together by defining application resources for Argo CD.  We embrace the app-of-apps pattern here. So we have a centralized application watching for application resources for this cluster in our kit repository. That way we get all the application resources managed via kithops as well. We define where the application resources are located in Git and that they should be placed on the cluster running Argo CD instance. Now we create the corresponding folder and populate it with applications. The first application resource we create now is an application for the privileged resources. We call it cluster resources. This application is set to consume manifests from the overlay in cluster scope where we placed our alert config and other resources in previous steps. Then we created another application this time for the alert receiver and again sourcing the overlay we created above. Now all that is left is to commit all the created files and create a pull request. Once the PR is created our CI will pick it up, run some checks on it and we wait for it to be reviewed. We use Pro for CI and review. We lend all the files via a pre-commit and attempt to build all the changed manifests via Customize. We also use Pro to streamline the review process so once CI has passed and the PR was properly reviewed, Pro will label the PR and merge it automatically. Seems like our PR was successfully reviewed now so let's wait for Pro to label the PR and merge it for us. Since Argo CD is watching for changes on our repositories, it will also notice the new commit and attempt to sync the resources for application with automated sync policies. Now let's take a look at our Argo CD instance. Once the PR got merged we can see our cluster appearing in the list of clusters available to Argo CD. We can also list applications deployed to this cluster. As expected we have two applications available here, one for cluster resources and the second one for the alert receiver. Both are syncing now. We can dive into the individual applications to check on which resources are being applied. Among others we can find the namespace for our alert receiver here, secret for SSO credentials and the alert configuration. In the alert receiver application we see that the deployment was successful and it is doing well. Let's also check on the cluster console real quick. This is the login screen from before. Let's refresh the page to see if the SSO was enabled. As you can see we have the SSO tile available now. Let's try it out. We've been successfully logged into the OpenShift console without being prompted for a password. Now we can consider the cluster onboarded and available to users so they can request their namespaces via github. Demo 2. Onboarding a project to the Operate First community cloud. In this demo we onboard a user project to one of the Operate First clusters. Steps. One. Project onboarding. Two. Deploying application. Three. Testing application. All performed via GitOps. Hey all. Now thanks Tom. We have a cluster available here in Operate First for us to deploy our project. So what we will do now is we will work as project admins and see how we can deploy our project to a cluster. On Operate First. And we will do this the Operate First way. To do this we have a guide, a hitchhiker's guide to Operate First similar to one that Tom used earlier to onboard the cluster to Operate First.  And once they are merged in that repo the manifest are applied. Let's start. Here we have a bunch of variables that we need to set. And let's start with the user variables. For the GitHub username I have set my handle here. And for namespace name let's set it to demo Jupyter Hub. Why Jupyter Hub? Because Jupyter Hub is the application that we are going to deploy in this namespace. Demo Jupyter Hub namespace a small display name so we know what's deployed in this namespace. It's like a small description. And next for the team name I like demo team. For the cluster we can choose the demo EMEA cluster which was earlier onboarded by Tom.  Once we have applied all the variables what we want to do is we want to work to Operate First app's repository. And clone it. Let's go there and hook it. This is the repo where we have all the manifests that are applied to all our clusters. And let's fork it. I've already forked this. What we want to do is we want to clone it. We don't really need to copy the address here since the guide has already set up the commands for us. All we need to do is just run it. Which is true for the rest of the guide as well. All we need to do is just run all the cells and it should create and push all our manifests for us. Let's see. Now we're going to create a manifest for namespace. To do this we will use the Operate First CLI, the OPF CLI tool that we have created. This lets you create manifests for the namespace and it will also create an OpenShift group for us. And anyone in this OpenShift group will have the namespace admin privileges for the newly created demo Jupyter namespace. And this group is called the demo team. Let's run it. And next what we want to do is we want to add this namespace to a specific cluster. So here in the next cell we have specified this target cluster. And earlier in the variables we set up the demo cluster as a target cluster. And what now we want to do is we want to add me and Humair as namespace admins. So this cell will do that. Let's run it. And next we want to finalize everything. We want to make sure all the files that should be modified and created are having created and modified. To do so what you can do is you can go to the files here and go to cluster scope directory and see the specific files were created. But we have already tested this. So let's just add this to our repository and push them so we can create a pull request with it. Pull request with the changes that we have done. Now let's see if the changes were pushed. Awesome. We are going to come in ahead. Let's open a pull request. In this pull request you can see we will be going to add a bunch of manifests. Let's add a description for this pull request. This will add me and Humair as project admins for namespace demo Jupyterhub. And then we specify the cluster. On cluster Emia demo cluster. Perfect. Once we create the pull request it needs to be reviewed by one of the operator first ops members. And all the CI tests need to pass as well. So after these tests have been passed and it has been reviewed by one of the ops members it should be merged into the repo. Humair merged it in. Thank you Humair. And now since these changes are in the apps repository Argo CD will detect these changes and try to apply them to the cluster. Let's go back to the cluster console and see if these changes were applied. Let's refresh. The changes usually take about a minute or two. Awesome. We can see here the demo Jupyterhub namespace was created. But we don't really have anything deployed in this namespace yet. Now we want to deploy Jupyterhub. How do we do that? In our production environment we have Jupyterhub set up and we use the open data operator to deploy it. But since operators are a cluster scope resource what we need to have is we need to have higher privileges. And as project admins we don't really have those privileges. I mean here I am a cluster admin so I can just go and search for the operator and click install and it would install the operator for me. But we want to do this the operator first way. And how a project admin on operator first would do it. So to do this we have created a pull request. This pull request what it does is it will be adding a subscription to the open data operator. This is how we will be installing the operator on this cluster. You can see we have a subscription file here. And we need to get this PR reviewed and merged. Let's wait for the CI to pass. I can see Homer has already approved it. It's awesome. Awesome. Now the CI has passed. The PR should be merged in soon. And awesome. Now that the PR has been merged in our Go CD will again detect these changes and it will try to apply these changes. The change is being opened up operator being deployed on this cluster. Let's check the installed operators. Let's give it a minute. This operator is going to be deployed in the open shift operators namespace. Let's give it a minute. Oh we can see a pod being created here. And oh yes. The open data operator has been installed. We should be able to see the pod running for it. Let's go to the Jupyterhub namespace. Now what we need to do is we need to use the installed operator to deploy Jupyterhub for us. How do we interact with this operator? We interact with the open data operator using kfdev files. Here is an example file. But since we deployed Jupyterhub in our production environment we already have a manifest available for us. So we're going to just paste it and create it. Typically or normally we would do this in Git. But in the interest of time we are just going to apply this manifest here. And a project admin person would have these privileges. So we can just do that. Once we have applied it we can see Jupyterhub pods being created. Let's see. Oh they're ready. We should have Jupyterhub deployed now. Now let's try and use it. We have a route available. Let's click on it and log in. So Jupyterhub is an application that we can use to deploy a Jupyter notebook server for us. Let's click on the minimal Python and start a server. Jupyterhub users don't normally have access to the open chip console but we do. So we are going to see what's happening under the hood. We can see a pod is being created and we also have a PVC available here. PVC is where all the persistent data will be stored. Let's see. The pod is still creating and it should be available now. Awesome. We have a Jupyter lab environment available. We can create a new notebook and see if it works. Let's try running a simple command. Let's print hello world and see if it works. Awesome. So this works. Now let's go back to the open chip console. You can see everything's running and that's about it for this part of the demo. This is how we would deploy an application the Operate First way. Demo three. Performing SRE functions on the Operate First community cloud. In this demo we see how Operate First ops team members perform SRE functions. Steps. One. Set up alerting rules. Two. Break application. Three. Check alerts. Four. Fix application. Hello everyone. In this demo we will run through a scenario on how to handle service disruptions at Operate First. We'll be working on the project that Anand has set up for us within the Jupyter Hub namespace where he has given me access during his project onboarding demo. Before we introduce a problem with this service first we need to have our alerting in place. For this particular scenario we'll be alerting on when a user runs out of storage for their notebook. So thanks to Tom during cluster onboarding he enabled what's called user workload monitoring for us. Traditionally for alerting we would have to deploy a separate Prometheus instance plus alert manager with an alerting and rules files both to manage and maintain. With user workload monitoring the weight of maintaining such resources is lifted from the project admin. So now if I want to alert on something regarding my service I can just create what's called a Prometheus rule and just leverage the Prometheus that is already available to the entire cluster. So to do this we will navigate to Prometheus rules. For that we have to go to API Explorer. Type in Prometheus rule in our search. Click Prometheus rule instances and create Prometheus rule. So I already have a rule prepared for us for this demo. I'm going to just paste it in here. And essentially what this rule will alert on is when a PVC in this namespace is over 50% capacity it will alert. So why this alert? Because when a Jupyter Herb user pod fills up on their PVC they will be unable to restart their server. So this is definitely a useful alert to have. So let's go ahead and create this rule and we can see it now listed under Prometheus rules. Okay so where do we want to send this alert? Well when Tom onboarded this cluster he added an alert receiver that forwards all of our alerts at her repository in our org called alerts. We do this for all our alerts, cluster alerts. Having it available in this repository keeps our alerts open to the public and gives further visibility into the state of the cluster and the operate first cloud as a whole. Awesome so now our alert will go to this repo. So next we will pretend to be a data scientist and work in our notebook server. I have a notebook server already spun up following the same steps as Anand in the last demo. Let's open up a terminal. Now I'm going to fill up our storage with some large files by running this command. And we expect this to then use up more than 50% of our storage and thus trigger the alert. We'll give this command a second to execute. We can see that this file has been created. Awesome so now our storage has got this file taking up most of our space. And if we go to now the alerts repo and we can give it a second for the alert to fire. Okay cool so now our alert has showed up and it was sent to this alerts repository. Now this is a pretty tame alert but imagine if this alert was something more serious. For example imagine if this alert was about a production to better hub instance going down. In such an event we would have to start an incident. So let's go ahead and pretend that this alert is very serious and we will start an incident to resolve this alert. We also manage our incidents on GitHub. Once again to keep it open to the public. Our incidents go in our SRE repository within the same org. As you can see here by filtering on the incidents label I can see our past incidents. To create a new incident we go to new issues and we have a template that we can follow by clicking get started. I already have an example incident form like this filled out if I switch to the new tab. As you can see over here I can link the alert that has been firing as part of the kind of additional information under relevant links. I can see that there's other information which cluster is affected, the users that are affected and some basic description about the incident. I'll go ahead and submit this incident and then we can update this incident thread with comments on the steps we take and information we collect. We can also comment on how the incident is resolved and since this is on GitHub someone searching for a similar issue can benefit from our gained knowledge. Alright so now let's look at the alert itself. The way we have defined our role we can see that it actually will add to mention the user that is responsible for this PVC. In this case that user is me so this is my GitHub username and I can see indeed that I have a... If I go to the notifications I can see that I was notified of this alert but it's not highlighted because I already have the thread open. Cool. We can also see that there is a runbook linked to this alert. If we follow this runbook we can see that there is a section for insufficient disk space for a notebook pod and then it lists the steps I need to take to resolve this problem. And in this case it's just to increase the PVC size. So let's go ahead and do that. So I'm going to go back to the OpenShift cluster and go to persistent volume claims, find my PVC and just simply go to the YAML and update how much space this PVC has. In this case I'll raise it from 2 to 6. Awesome. And if I go back to the alerts repo and if I refresh click this alert give it a second to update. And as you can see that the alert has been automatically resolved. We can navigate back to our incident that we created. We can comment that this alert has now been resolved. And also mentioned that an RCA will soon follow if there's a root cause analysis that is needed. And I can go ahead and close out this incident. And that's it. And this is how we would go about resolving an incident in our operate first cluster. And hope you guys found that helpful. Thank you. Alright everybody. Thank you. It's always impressive to me every time I get to watch that process. So let's, we've only got a few minutes left until the top of the hour. I don't want to keep anybody over because, you know, in this clock driven world, that's what we thought. But do we have any questions we want to, that came up in chat anywhere or anything we want to field for all my little faces. So if you are an attendee and you want to put any questions into the chat, you can feel free. So that there's a separate Q&A section for you or not. Questions. Thank you. I love your virtual background there myself. Actually, actually it's a live background. It's animated. AI is capable of doing these things. We don't have any questions flowing in. I mean, we can we have some questions prepared, so to say on the SRE and GitHub we post. So maybe we want to call out the action, the, like the call to action boxes on the operate first website where we have tasks prepared for all future community members to starting to tackle. That's one question. Yeah, let me, and I'll go ahead and answer the question. I'll ask the question out loud and then we can see who wants to jump in with an answer. But the first one is what other applications are deployed on the operate first environment. And so in this particular, this community cloud because an operate first environment is is defined as much by by the method of connecting the developers and the operations together in an open environment. And so this is a particular reference implementation, so to speak. So what are their applications do we have a boy deployed in the operate first community cloud. I mean, can anyone join in. And how would you get started. Who can wrap up those applications off the top their head. So it's the answers a bit twofold. So one is the applications that we deploy by we meaning the people who manage these clusters. So some of the people on this call and a few others. And those that's one of those applications for example is Jupiter hub. And there's a lot of others, a lot of applications that are offered by open data hub offerings and then there's some that are a lot of you probably may have heard of like Kafka, and Anna, and we make these we manage these ourselves but then there's also a second part to the answer, which is that people who get on boarded. They can, they also deploy their own applications right so they deploy their own applications and manage them themselves and they can once they have permission themselves access the way on and showed, which anybody can do because it's done through than anybody, you can continue to manage your applications via get using get ops, or you can also just deploy things live. Right. So those are the applications that's a bit like the user applications managed by them. And I think an important connective PC or is that we're in terms of this kind of open sourcing of operations, rather than going backwards and trying to take code that's existed in the past we're moving forward from here and, and a lot of ways the future of how, how the SR reactions how DevOps and and machine learning everything to come together is within this AI ops environment. And so the, this is one of the tools that we have out there are data science tools. And there are learning pathways being put up and accesses, you know already available for for people to come and start to use the data science tools, which includes people who would be otherwise, you know, who might who might come from a different background than a regular data science background, but who might be doing say log analysis and other technology work when it comes to the when it comes to the other managed services that we offer and provide to other users we can mention also, that some pipelines, cute flow, and services like that so basically our initial support was aiming the data science folks, but we have other services that some of our users provide so that is the thing that Marcel mentioned during during his presentation, like the Quarkus services Epicureo or pulp. And we got another question is this service free. Yeah, that's, and that's a really good point because that's a good segue from what what Tom was just saying as well because the, I mean this is an open source project right and we're, we're sort of the services are available to users. And, and in particular what we say users, you know, of course that could be anybody but in particular, the core the users we're looking for. So that the people to bring applications like Tom mentioned, if you've got an open source project, and you want to come run it in a live production cloud and have an opera and opportunity to get access to all that to all that data that that exhaust from before. And that that's how you can you can do that here and so so it's so it's freely available, but there are the the cost is you've got to come in and bring a code and start and do the work to with us to get it into the environment. Right now the environment is a it's a Kubernetes based environment you saw the pieces of it, and having an operator or writing an operator to plug in is a good way to go in the future. There's no one way to do an operate first environment. You'll see us are working with other other groups to bring up other types of environments either in our either in our community cloud or in their community clouds as we will share around these blueprints and so forth in between systems. Did you already mentioned that people can just, at least for the Jupyter service they can just come in and log in using their GitHub account and they will be able to spawn their own servers. And that applies to also other many services, most of the services are publicly available. And if the service is not publicly available for whatever reason, the only required onboarding is to ask for the access so that's the old does the barrier that is there for certain services, but the rest is publicly available. It can be publicly available. It is publicly available. Right. And what I mentioned before is that we're, we've got all these services and capabilities. But but the sort of the user experience depending on who you are and how you're going to get there and understand what to do is something that we're working on with with the website right now so you know so this pathways are going to continue to evolve. In terms of what's there so but there's between here and there's a lot of videos on our YouTube channel that explain how to use the different tools and how to get how to get access to them as well so in terms of kind of DIY learning environment it's ready to go right now. And we're working on that helping you with your learning as well. So regarding the is it free to use question I would I would say that yes it's free to use but you also bring your usage to the table so in by using it you bring some real value to these services that are being offered because we essentially want to try them out or provide them to real users and then create some real usage patterns create some data by using those services. So there are many ways to be part of this community it's either you use these data science service or the Kafka services that are available and by using them. You can use the usage of those services or you go to the operate first website and join the SRE pathway and you help maintaining and running these services so it's also free in terms of I want to be an aspiring SRE person and once you exactly and who may and Anand currently just showed in your browser in your Git console in your terminal console and you can just spin up your terminal terminals or Jupyter notebooks and really do the SRE work there. Also, in terms of yes it's free as a learning resource. So if you want to show how to get to the operate first website and click to those get up issues that are available for starters for beginners. We could do that that would that could be a good I was just I was actually just looking for something we could do to wrap up since we're right. We're getting close to the top of our, up of our hour does anybody have that have that handy to bring in. Yeah, so we're we're we're operate dash first dot cloud. And you can find all the things you need on there. We have and community mailing list web forum, basically for for discussions amongst. I use as an contributors. Let me see. Just quickly share the website. Yeah, I think the chat is not recorded because people will also watch this not real live and then at least they see the website and know what to do. Yeah, yeah. So basically these are the two ways that's that's that's Tom and Anand and we just showed if you want to do the operations bits and pieces you click on the right button. Basically, you take the right pill, and you are on off on the SRE races and if you want to deploy your community service like we just showed how to deploy Jupiter up there. You click on the left button as an open source developer and you being guided how to host and yeah, supply your projects to that community. Okay, and I think that's a probably a pretty good spot for us to wrap it up. Do we have any more questions. No, I don't see any. Okay, great. All right, well, thank you everybody for joining us today. We appreciate your, your time and efforts and come to join us for a journey where we're just just beginning to tell the story to everybody out there and any input you thought is welcome and as well as your if you've got any interest in bringing your open source projects. We're come join us on the mailing list or come find us in the, in the select channel, and you can find all of us where we're in the social medias are various other places. And I think that's about it. Marcy do you have any other, do you have anything else we need to finish up with, otherwise I think we're all out. Great. Yeah, I think we're good. Thank you so much to the whole red hat team for your time today and thank you everyone for joining us just as a quick reminder this recording will be on the Linux foundations YouTube page later today. So we hope to see you back here for future webinars. Thank you so much again.


Hey guys, what's up? It's Andy Elliott. In this video, I'm going to show you the top five rookie car salesman tips. Let's crush it. Take a pen, take a piece of paper right now. If you're a veteran in the game 20 years, take some notes you're about to learn. If you're brand new just getting in the business or you're about to get in, take some notes. This is going to change your life. Number one, mindset and attitude. Number one, the mindset. The mindset's probably the most important thing. No one's going to be selling anything without being on fire here. Write this down. They can buy, they came to buy, and they will buy as long as I do my job. Write that down. I want you to think about this right now. One of the biggest things that you get with a lot of veterans is they pre-judge everybody. Everybody that pulls up, they think they know what their car is worth, what they owe on it, if they got good credit, if they don't, if they'll take that car, if they won't, if they're buying today or if they're waiting next year, if they're tire-kicking, man, they know it all. They know it all so well, but look at them. Are they breaking the records in the country? Are they crushing it? Are the number one salespeople in the world? Probably not. How can you do it? This is your time. Number one, it's your mindset. You believe that every single person that calls or that comes in in-person is a buyer and is ready to buy as long as you do your job. So that's going to be the mindset part. Secondly, let's talk about attitude. The attitude that goes with it when you meet somebody, the first thing you got to have is the best dang attitude in the world. Write this down. People don't have to prove to you that they can buy before you give them your best. Man, write that down. Give them your best right out the gate. Run out there. Great energy. Great fire. It meant passion in your eyes. You love what you do. You're brand new. Cool. Let them know you're brand new. Hey guys, what's going on? I'm brand new. My name is Andy. Guys, don't beat me up today because I don't know nothing. I'm here to serve you at the highest level. Woo! They're like, dude, this guy's got a good attitude. You don't know nothing. I'm okay with that. I want to tell you this. I told people I was brand new the first two years in the business.  You got salesmen in the month, plaques all over your wall. I said, I know. I just love being brand new. I never want to be a veteran in this business. I want to stay brand new forever because all the veterans, all they did was sit around in their office grumpy, wham, wham, wham, complain, crying, and whine.  But if you look around and you're in your dealership right now, look at all the cubicles in the offices, right? How many people do you see right now studying and training and wanting to be the best like you? Probably not very many of them. All right, guys, number two, this is going to be work ethic. Top two right here, work ethic. You need to be known in your company for the hardest worker. Listen, time and experience, don't care about it. If you're in the dealership, you need to be known for the work ethic. People need to know you for your relentless work ethic. Every day you need to be known for your work ethic. You're not over the coffee pot talking to John about the football game last night. When you go into work, you trade your time for money. It's time to trade your time for three times as much money. Every day, go up and get better. Yes, every day, increase your work ethic every single day. You need to be known for that. Remember this. What people say about you when you're not around is who you are. When I first started the dealership, I was 18 years old. I went in, I didn't know anything, and by the way, I didn't even deserve to have that great job. So you know what? Since I didn't have the skill, I didn't deserve to be there. I decided I was just going to outwork everybody, and if I was known to be the worst salesman in the state, that's fine, but I was going to be known to be the hardest worker in the state in that dealership. And working hard got me better a hundred times faster. And plus my managers, even if I wasn't the best at certain things, they respected my work ethic. How many people do you know right now that you respect for how hard they work? Get that title for the hardest worker in the dealership. That's going to be rookie tip number two. All right, guys, number three, I feel like this is very important. Write this down. It doesn't matter how much money I have to go buy clothes. It doesn't matter. You can go to the Goodwill with $5 and dress yourself decent.  Put it into the fund that you have set up to buy yourself some new clothes. Get yourself a nice belt. Get yourself some nice shoes. Get yourself some nice slacks.  I know in some dealerships you guys get to wear polos. I'm okay with that. Make it pressed. Make it sharp. Make it look nice. If you have $10,000 right now, you're going to invest it with somebody. You took that money. You walk into the investor's office. You look over at the guy.  Doesn't look like he brushed his teeth. He's got eye crusties in. His hair's not fixed right. He's got a wrinkled shirt up on. You're going to trust him with your $10,000? Even if he's a good speaker, would you trust him? No. You're going to say, hey man, I appreciate it. Thanks for taking the appointment today. You're going to go over.  You can sit down with and have a conversation with and feel comfortable spending or giving your money to. That's your customers. They need to fill that way with you. So time and experience doesn't mean nothing. You can start dressing nice today. I assure you. So rookie tip number three is going to be dress for success. Don't dress for the job you have. Dress for the job you want. Don't dress for the paycheck you're making. Dress for the paycheck you want to be making and you will be making soon. All right guys. Rookie tip number four. Use a mentor. This is extremely, extremely, extremely important. Guys, I'm 42 years old at making this video. When I was 18 years old, I looked to the left, looked to the right, looked around and tried to find somebody that I could emulate. Somebody that I could be like. I could look at the way they spoke, the way that they talked, the way that they sounded, the way that they dressed, the way that they worked, their strategies and the way they maneuvered when negotiating, closing techniques, word tracks. I tried to find it and I couldn't find it in my dealership. It didn't exist. So I found a guy, his name was Grant Cardone. We're going back 23 years ago, 23. And I chose a mentor 23 years ago that at 18 years old, I watched this man who seemed like a good speaker. He seemed like he could convince people to do things that he wanted him to do. He was fired up. He was positive. He had a great attitude. He dressed nice, had great work ethic. He had the things that I felt like that I needed to be successful.  Every time there was a live event that he would go and do training at, I would fly there and be there. I studied every single day to make sure that I could elevate my skill and compete up. Write that down. Your goal as a rookie is to compete up. Your goal is as a rookie, not to compete with other rookies.  Choose a mentor that will show you how to get that skill fast. And by the way, write this down. This is very important. My mentors. My mentors. This is me talking to me. My mentors in life are people who have gone where I want to go. Does that make sense? Choose a mentor that is gone where you want to go. A person right now, I broke the record $716,000 in one-year selling cars. If you're wanting to make a lot of money, have a great life. It's very easy to do. Choose a mentor who's actually done it. Everybody follow, take their courses, train, self-invest. Guess what? You will get there 100 times faster. Most people will never get there because they don't have anybody that they're emulating. There's nobody in their mind that they want to be like. And by the way, when you choose a mentor, understand this. It's not about being a second-rated version of you. It's about being a first-rated version of yourself but studying this person to death so you can understand, number one, how they do everything that they do and how you can do everything that they do in your own way or just like them. There were certain things that when I was studying my mentors in life, I did exactly what they did to the team. I copied it. It worked. Why wouldn't I take it? I was watching a conference with Tony Robbins the other day. He said, guys, success leaves clues. It's so simple. The people that have made history before us, that have done the things that we want to do, they did it and gave us the tips on how they did it so that we could do it. Many people don't just follow that simple process. They sit on the couch. They complain. They have the victim mentality. They feel helpless and they don't think that that can happen for them. I don't want that to happen to you.  Number one, choose a mentor. Number two, study him daily. Courses, train live, anything and everything that person has, attack it and train relentlessly. All right, guys. Number five, guess what it is? You know it. Train relentlessly. I just said it at the end of number four. What does the term relentlessly mean? I feel like some of you guys hear the term train. You're like, oh man, I watched a couple YouTube videos. Listen, there's a difference between training and really training.  Kobe Bryant. We're going to take Kobe Bryant, okay? Bless his heart. Most amazing man in the world. Mamba mentality. Amazing. 11 years old. Doesn't score one basket in his league that summer. Didn't score one basket. He was the worst player in the league. Guess what happened? Talk to his dad. His dad said, son, we're going to out-train him. It's real simple. Most people at your age that are training, that are playing basketball, they're playing for two hours a day twice a week. That's four hours. Listen, Kobe, we're going to train for two hours a day and we're going to do it six days a week. Then they went to three hours a day, seven days a week. By the time he was 14 years old, he was labeled the number one player in the state. I want you to think about it. From 11 to 14, two years past, he went from not being able to make a basket to being the number one in the country. Imagine this, the number one in the state, the number one against everybody who played at at 14 years old. As an adult right now, I want you to think about it. You got your family, your future, kids, wife, husband. I'm not sure what it is that is driving you to want to be great.  You have to train relentlessly. I want you to write this down. Your obsession, your obsession, write it down. My obsession towards training or my lack of obsession towards training is how I feel about winning. Listen, I want you to write that down. My obsession or my lack of obsession that I have towards training is how I feel about winning. I'm totally and completely obsessed with training and I've been obsessed my entire life. And if you would like a great mentor to show you how to get what you want in life, be relentless about training every day, not some days, every day. And I want you to think about this. If winning, if winning, it is a person to be winning as a person.  Are you obsessed with training? If you're obsessed with training, winning will be attracted to you. Winning will want to be with you. And guess what? Winning will win. Guys, these are the top five tips for a rookie sales pro. I'm going to explain this to you. If right now you're wanting to level up, shoot me a text,<PHONE_NUMBER>. Don't be afraid and say, man, I'm real busy. I ain't got time to text Andy. Got a lot of stuff going on. Really? Like what? Let me ask you this. What are you struggling with? What do you want to get better at? What is the hole in your game? What do you want to excel at? Look at your year-to-date right now. Is it 100, 200, 300, 400, et cetera? Is there more potential in you? Is there another level? If there is, you believe it. Shoot me a text,<PHONE_NUMBER>. Let me know what I can help you with. Let's kill it.


Hey it's Lenny Gale with Life is Knowing Y'all. Today we're going to compare the Explorian, the Vitamix Explorian E310 to the Vitamix Ascent Series. And in this video we're going to walk through the ins and outs, compare the containers and the body and the blade and the motor, but just know we're not going to do a blend off, we're not going to put anything in it and show you the difference because the output, the blend quality between these two machines, even though the Ascent has far more features than the Explorian, the blend quality is going to be the same. So stay tuned for close-ups and comparison between the Explorian E310 and the Vitamix Ascent Series. Okay so let's go top to bottom comparing the Explorian E310 and Ascent Series. Top, on the Ascent there is a clear lid so you can see in and see what's what is blending and it clicks shut so you know that it's shut. The Explorian has that classic rubber lid so the Explorian E310 comes with a 48 ounce 1.4 liter container. It's narrow compared to the wide 64 ounce 2.0 liter so it's going to be more narrow compared to the big one here. Let's talk about the the blade on the containers. We have a 3 inch blade versus a 4 inch blade. If you look at the body of these two machines there are some significant differences. The Explorian has switches where the Ascent has touch screen buttons for both start, stop and pulse. The Ascent lights up it will tell you how much time has passed. You can do a countdown timer. There are pre- program settings on on this particular Ascent whereas the E310 is really just the basic Vitamix. Switches and a knob, a pulse button on off switch and again that same blend quality but just with less features. So if you look around you can see the differences on the side and on the back. There is an on off switch on the Ascent for that extra added layer of safety so when you plug in the Explorian it's on right away. You plug it in and you can flip the switch and turn it on. The Ascent you have to plug it in and then turn the switch on the side and then you can activate it by pushing the buttons. The Explorian has that older 2.0 horsepower motor versus the 2.2 horsepower on the Ascent. Now it's a bit of a difference but in reality like we said in the beginning you cannot tell the difference in blend quality. The reason one is bigger than the other is the need to drive the bigger blade on the bigger container. Four inches versus three but other than that they're the same Vitamix power that you come to expect. So cosmetically they are a different look as well. The sides are different, the back is different, the Ascent is really made for that open kitchen to be beautiful on all sides so this would probably be better up against the wall in your kitchen. Explorian E310 again it's no frills, no extra features, no extra bells and whistles so you're not going to get the Bluetooth connectivity to be able to control the the machine with your phone. You're not going to get the ability to use those eight ounce and 20 ounce personal blending cups like this. This only fits on the Ascent series. Now you can use the personal cup adapter with the Explorian with a 20 ounce cup and this works for adding ingredients, blending and go. So this works with the Explorian and this as well as the 20 ounce attachment that also goes on here comes with the Ascent or is compatible with the Ascent. One nice thing about the Explorian any legacy container so a narrow 64 a 32 ounce a 32 ounce dry grains those are compatible with the Explorian. The Ascent series the containers are dish washer safe. Explorian they're not but you can still run a cleaning cycle a couple drops of soap warm water 30 seconds and they still self clean which is what we end up doing anyway because we use our machine so much putting it in the dishwasher. We use our vitamins more than we use our dishwasher so we end up doing the old-school cleaning cycle which works just as well then actually putting it into your dishwasher and then the warranty that's a big one so Explorian E through 10 comes with a five-year warranty versus the Ascent is a ten-year warranty. It's the same quality of warranty free shipping both ways everything is covered you call them up if there's an issue and there's a not a very good chance that there will be an issue about one half of 1% of Vitamix machines get sent in for service over the duration of their warranty these things last a very long time but you get what you pay for and with the Ascent you're paying a little more for the little more features like we said and that extended ten-year full warranty with the Explorian E through 10 you get that five-year full warranty still great five years is a long time and we can't make any promises but there's a good chance that your machine will last a lot longer than the duration of its warranty we hear from many many many many people telling us they've had their machine for 10 15 20 years still runs great same quality i don't like to use the term workhorse because like i don't like the idea of horses working it makes me sad but these things really are um that so many people have bought their Ascent through us and they love them they love them for the features the look the warranty but you are going to be recommending the Explorian E through 10 as well it is for someone looking to get into the Vitamix family their first Vitamix someone that wants a new Vitamix that is more affordable that is under four hundred dollars um this is a great machine and it's also great for for people living alone we always what machine should i get i live alone well every Vitamix including these two Explorian and the and the Ascent they can make everything soups smoothies whole food juices nut butters ice creams hummus doughs batters baby for everything but the question we get is which one should i get if it's just me i don't want to make huge batches well the Explorian E through 10 is great for that 48 ounce narrow container has a smaller minimum batch size than the 64 ounce container that comes with the Ascent it's a great machine for someone who lives alone grandma grandpa mom dad bachelor bachelorette someone who wants to get their first Vitamix but doesn't need all the features all the bells and whistles of the Ascent series and Explorian E through 10 is also really great for someone who likes tactile to feel feel the switches feel the dial and doesn't necessarily need all the extra the touchscreen seeing the timer counting up counting down the bluetooth the extra features the basic if you're coming from a C series if you if you've had a C series or if you've used someone's C series those old school switches knob that's it the old 5200 the classic this is the upgraded version of that knobs switches narrow container rubber lid no frills but everything that you need to make all the things that you want to make in your Vitamix look these are both great machines it depends on your budget it depends on your needs but no matter where you go you're going to have a great Vitamix and when you get it you're going to come to us hopefully and and uh right so okay so when you decide which one is best for you come to us and use our link to Vitamix our referral link to Vitamix when you check out it'll ensure that we get credit it helps us immensely every little bit helps and that'll make sure that you get free shipping get you any extra discounts that are unlockable and a starter kit from us so an ebook a recipe guide all sorts of extras my phone number if you need help and uh we really appreciate it so again if you like this video like and subscribe and what else and let us know if you have questions in the comments or if you just want to tell me that I look stupid with this beard it's it's buy request I take requests for facial hair now oh only from only from Shalva um yeah do we miss anything I mean I think we covered everything it's already going to be like a long video of me just talking so like I'm gonna have to cut so much of this this is probably like eight minutes of like blah blah blah blah blah including this yo the ascent e310 is she's shaking her head no I can't talk like that oh yeah yo the exploring e310 is awesome uh okay let me say this when my friends come to me and we don't make a ton of money uh my peers like I'm not like we're not like middle-aged like retirees like ever like we're on a budget like what of course they want a Vitamix which one should I get I used to recommend the certified recondition get it it's great machine five year warranty whatever this is the one i'm gonna recommend for those people now the entry level Vitamix you will be so happy you won't regret it for a single second


Hi guys, you are watching oxyvlogs if this is your first time here and you would like to know more information about life in Dubai How to get a job in the city keep watching this video and today I want to talk about one very important topic how to look for a job in Dubai when you are on a visit visa So you are in Dubai on a visit visa. You are looking for a job Your visa is about to expire you feel desperate and you start sending messages to different recruiters Saying that you're looking for a job your visa is about to expire Please give me any job before that happens Honestly guys, it will not help you to lend any job because no one cares about your situation with your Problems hiring managers are busy people. They have their own concerns in their head They receive thousands of CVs per day from other people who are in the same situation like you so they even will not pay attention to your message and Personally, I receive so many messages like that as well But guys this doesn't look professional at all and this is one of the biggest mistakes many of you make So be professional in your approach You know that your visa is going to expire you feel desperate and you want to deliver this message to the hiring company So do it professionally without showing desperation after all it's not the end of the world You can always come back to Dubai and continue looking for a job You still can attend some interviews and even if your visa expires If the company is interested in you, they will get in touch with you After you come back to your home country and if they want to hire you they will provide you with a visa and Some companies even can provide you with the one-way plane ticket So in order to look professional and confident you need to go through the job search process in a systematic manner First of all, you need to have your professional CV and cover letter Mention in your CV and cover letter that your visa is going to expire on a certain date Also mention your home country contact details so the employer can reach you after you go back to your home country Start sending your CV and cover letter to particular job openings that Match your qualification and skills In addition to that try to go to as many work in interviews as possible Speak to the hiring manager tell them that your visa is going to expire soon and You are waiting a positive response, but don't show the desperation and also Give them your contact details so they can reach you after you go back to your home country If they want to hire you and after the interview Don't forget to send an email to the hiring manager thanking him here for the interview And hopefully this approach will help you to learn the job faster And if you don't get a job don't give up even when you go back to your home country Continue looking for a job Also, if you have any plans go back to the UAE Mention that in your resume. So guys, that's it for today. Thank you for watching. If you have any questions Please leave them in the comments below and I will see you in the next video. Bye. Bye


Over the next few weeks, we're going to focus on the document, Signature Behaviors of the 21st Century Sailor 2.0. The Navy Senior Leaders signed out in February 2020. This document provides an unambiguous description of the 10 attributes that shape professional behavior and leadership in the years to come. Number 10 on this list describes a leader's duty to contribute to team success through actions and attitudes. Modeling professional ideals and values through personal behavior is a time-tested leadership trait and proven to encourage growth, trust, and loyalty within the organization. Additionally, possessing a positive and supportive attitude is equally as important for a leader, especially in the face of complex and unprecedented challenges. We'll talk about the other attributes in the weeks to come. Lead well this week.


Right now, on top of a tower somewhere, a man is on guard, watching for smoke, working for you, protecting your forests. The danger is real and constant. The possible damage, great. It's a necessary, hazardous job, and happily, there are men willing to do it. Here too, men stand guard, ready for action on a moment's notice.  When this kind of emergency arises, the skills and equipment needed to deal with it must be ready. There's no time to get ready afterward. We make laws by which to live, but law without authority is no law. So these men too are working for you, upholding these laws, guarding you against crime. Here, still another man stands guard. As his general orders put it, keeping always on the alert and observing everything that takes place within sight or hearing. This man and others like him are working for you too, and for themselves, since what they are guarding belongs equally to us all. Less tangible than forests or property, but in the end, far more important. They guard our freedom. This post is somewhere in Germany overlooking a sector of the Iron Curtain. Over there behind Barbed Wire Barriers is a captive country, a Soviet satellite. It's a lonely post, but this man is far from alone in his job. Some miles away, in an impressive complex of buildings, is the headquarters of the Army organization of which he is a part. The location is Heidelberg, Germany. The headquarters, that of the United States Army in Europe. USERER, and this is part one of the USERER story. The Army presents The Big Picture, an official report produced for the armed forces and the American people. At USERER headquarters, an officer takes a moment during a busy day to examine a new information poster. It is one in which he has a particular interest. We'll let him tell you why himself. For 40 years, this man has been my vocation and avocation. Welcome to the United States Army in Europe, which we call USERER. I will explain shortly what that means. But first, my name is Bruce Clark. I'm a general, a general in your Army. I have not always been a general, for in fact, I started as a private in 1918. I'm speaking to you from my desk in Heidelberg, Germany. I am the commander-in-chief of your soldier son, your soldier husband, your soldier father, and my soldier son, too. Our loved ones in Europe. I am speaking for them because I think I know how they feel. They are proud over here in a foreign country. First, because they are Americans. Secondly, because they're a country. Second, because they're a country. Third, because they're a country. We have an enemy over here who is threatened to engulf us, who is only waiting, alert, ready for that one moment, that we let our guard down. Your loved one is here as one of those guards. As a soldier, he is proud that he's part of the greatest peace time ever assembled by our country in numbers and firepower and weapons and equipment, in might. It is a might that each night we sincerely hope that we shall never have to use, for we of the United States are a lawful nation, a peace-loving nation. But let the enemy make no mistake, we are ready. You have seen to that by giving us the United States Army in Europe. Usurer is something the public, you know too little about. This is a report to you on Usurer, the United States Army in Europe. Sit back and let us show you a power mass of proficiency and strength such that the world has seldom seen and hope with us that it will never be used. Heidelberg, tiny, ancient, peaceful. There is a quiet, contemplative sense of things here. And well, there might be. The University of Heidelberg had already been a center of learning for a hundred years when Columbus set out to discover a new world. During World War II, by mutual consent, the historic town was spared the devastation that bombing brought to so many more strategic German cities. So today, it retains unblemished its traditional flavor and charm. Almost paradoxically, Heidelberg is also the headquarters for Usurer, a military establishment of tremendous importance and striking power. Command center for hundreds of thousands of fighting men, missiles, guns, tanks, and aircraft strategically placed throughout Germany, Italy, and France. Among Usurer's border patrol units, the reconnaissance or recon squads, training alerts are frequent. The men never know in advance when an alert is coming. They move with swift and practiced economy of motion, spurred by the knowledge that each second could be vitally important in an actual emergency. After the alarm is sounded, the entire unit is in position, ready to move out with full combat gear to wherever the trouble spot might be. Tanks and armored personnel carriers. Jeeps. And men. The highly mobile Usurer recon units are ready. 24 hours a day, 7 days a week, to deal with any border development along the Iron Curtain, a part of the Usurer story. Elsewhere in Germany, an army colonel boards a helicopter to take a look at some of the 200 miles of barbed wire border which the men of his armored cavalry regiment patrol. The route of the flight is familiar, both to the colonel and his pilot. They've been over it together countless times before. The view is not pleasant. An endless barrier of barbed wire. Behind it, freshly plowed fields. These are not plowed for planting. They are plowed to remove all possible concealment and to reveal the footprints of anyone who tries to approach the barrier, seeking freedom on this side. The fences are electrified with enough voltage to kill anyone who grasps a strand of the barbed wire, making of the satellite country on the other side a single vast concentration camp. Coming in low, the hovering helicopter provides a good look at one of the watchtowers. The communist sentries work always in pairs with a double assignment. Watch for escaping citizens and watch each other. Viewed from this height, actuality can take on the sharp clarity of a symbol. For example, a typical border bridge demolished by the communists. Its main span lies in rubble on the valley floor. On either side of the break, a wide modern highway, grass growing up in its joints, a highway which leads now nowhere at all. Or consider this Czechoslovakian farming town. St. Kinsburg was its name once, and once it was active, productive, alive. Today the only thing moving in it is the shadow of a patrol helicopter. It was too close to the border, too good an escape hatch. Its people evacuated, St. Kinsburg is earmarked for destruction. Such is this section of the iron curtain, different from the rest of it only in specific geography. From here the kernel will go on by land transport to spot check some key border points in person. One such key point is located in this concrete bunker, a border station, from which observer teams keep constant watch across the barrier. Here, machine gun, radio, telephone, and powerful binoculars are the tools of the trade. And from here observers can flash the news of any border development on to usera headquarters some 200 miles away within four minutes. There are other such posts, manned around the clock, at points all along the barrier. The kernel is traveling with a five-man roving patrol, which uses two jeeps, both mount loaded machine guns, and radio equipment which can make instant contact with the border stations, other patrols, and observation posts. Here, near the border, the vehicles of patrol units have the road to themselves. The lack of traffic would be understandable even if there were no military restrictions. Every road to the border, big or little, is a dead end. Periodically a stop must be made to take a close look at some particular feature. Repeated detailed inspection through field glasses, day in, day out. And anything the least bit different, a reinforcement of a section of the barrier, a change in the patrol schedule of the guards on the communist side. Anything is to be reported on the spot by radio. These roving patrols provide added assurance that should the need ever arise, the alert will be swiftly passed to the armoured recon units on whom would rest the responsibility for the initial delaying action. The check completed, it's back into the saddle and move out to the next stop. For the men who maintain this constant patrolling, this may not be exciting duty. Century duty seldom is, unless something goes wrong, but it is necessary. A break in the solitude comes when the patrol reaches a checkpoint manned by men of the West German border police. These men effectively maintain surveillance over a wide area with the help of their keen-nosed, sentry and tracking dogs. Landus Grenza, the sign says, the frontier. And the border is that all right, a place where one way of life leaves off and another begins.  But along other sectors of the iron curtain are other roving patrols like this one, constantly on the move, checking, watching across the barriers, reporting change or lack of change. It has been called a war of binoculars. So go the days of the men who make up the recon patrols. Days composed of strictly followed schedules and constant alertness. Hours of looking at terrain already familiar, searching for the unfamiliar. Watching over empty roadways, quiet between the trees, making sure they stay that way. In this report, we can only touch the highlights to impress upon you that in Eucharist, your interests are strongly defended. Have you any idea of the strength and power of one of Eucharist's armored divisions? Let me show you. It isn't often that anyone gets to see this. This is a full armored division. To give you an idea of size, each of those small dark squares includes more than a thousand men. This division with its 14 battalions and its special troops forms a striking force of roughly 15,000 men with tanks, self-propelled artillery and vehicles numbering in the thousands. Everything is ready as the commander of troops reports to General Clark, sir, the division is formed. Never before on film has the full massed might of an armored division been assembled in a single formation. From the deck of his command jeep, Eucharist's commander in chief will troop the line. And as we follow, you will see in one continuous scene the massed men, machines and weapons of an armored division. 10,000 men jump to the business of getting the division ready to move out. Minutes, the men are in position. The division is ready to roll. These are M-48 tanks, the fast-moving cavalry of the 20th century. These are fast being replaced by the even harder hitting M-60s capable of defeating any present day enemy armor. Personnel carriers, enough of them to race thousands of fully equipped armored infantrymen into battle and deliver them ready for action from behind their shields of armor plate. These are the sights and sounds of a full division on the move. Hundreds of jeeps, trucks, support vehicles like the armored assault bridges which you see in the background. Mounted honest John missiles. A seemingly endless array of mechanized firepower. 105 self-propelled howitzers on the move. With ample room for a supply of ammunition these can provide the highly mobile artillery support which a fast-moving force must have. Last in line come the formidable 155s. Impressive as it is, is still only part of the story. More and more, the rugged and versatile helicopter is playing a major role in military operations. Without need for airstrips or parachutes user-recopters can move troops swiftly over short distances and set them down where the action is. Fresh, untired by forced marching or rugged terrain fully equipped and ready to put their weapons into operation. Weapons are the latest and best. Light army observation planes are available to direct the mortar and artillery fire of ground forces with pinpoint accuracy to its target. Still more supporting fire is available from helicopters armed with racks of rockets. Copters armed with machine guns and rockets and linked by radio with ground units can be used to help neutralize specific targets in support of an infantry assault. Training is constant too with the bigger rockets which are part of USERA's Sunday Punch. The mobility of the honest John on its truck-mounted launcher together with its nuclear capability make it a major item in the USERA field arsenal. These missile crews reflect the increasingly technical skills which modern weapons systems require of the American soldier. Once in position, only minutes are needed for the team to zero in on target. Uncanny accuracy is the hallmark of the sleek lacrosse guided missile. Another important part of USERA's preparedness is here, several hundred feet above the earth. USERA units are not only ready for action where they are, they are prepared to get up and go. In an era of swiftly developing situations, the capacity to react immediately and in effective force is a necessity. USERA's airborne units provide that capacity. Today, however, not all operations involve large, regular forces of combat troops. Increasingly, insurgency and guerrilla operations threaten the security of free nations. Our answer in Europe to this problem lies with the men of the 10th Special Forces. The small Special Forces team does not require a large and open-drop zone, and in actual practice would seldom have one. Accordingly, they train to land where the landing is dangerous, developing a skill in parachute control which lets them touch down without harm in a field studded with upright wooden stakes. With this introduction to the men of Special Forces, we come to the end of part one of the USERA story. In part two, you will see the highly demanding training which goes into the making of these skilled and dedicated specialists in unconventional warfare and other vital aspects of the USERA story, the United States Army in Europe. Big picture is an official report for the armed forces and the American people. Produced by the Army Pictorial Center. Presented by the Department of the Army in cooperation with this station.


When we started this program, nobody was sure that it would succeed. We didn't even know students would be keen to come. But we, since the start, have really been inundated by student interest. They've really grabbed hold of this. The DHB's grabbed hold of it. The small sites that we've talked about have grabbed hold of this opportunity. And everyone's put in a tremendous amount of effort. We've expanded the program in Northland. Initially we only had year five students. Now we've got year six students and they're spending the entire year as well. And we're increasing the number. So we're going to have a cohort of 44 students spending their entire year in Northland as of 2019. Pukauakau is really important for Northland, but it's also important for the Auckland Medical School in general. It was the pilot program, if you like, and now we've got programs in Tauranaki and in Whakatane. And I think it's important because students need to know the different type of medicine that's practiced in the rural areas, the different connection that you have with the communities and the different experiences. I think to become an all-round student, if you have a full basket of information, you're able to be more proactive in the way you address your clients. So that's the hope, is that the little strands of information we give are supportive to their journey working with the community. It's amazing how you can get integrated into a community by just being here, by meeting patients, by talking to them about their stories, comparing and contrasting the amount of times that I have been suggested to go to a place for dinner or go visit that beach on your way.  I think those are just the little gems that you get from talking to people. Living with all the other students, it's very different to any of the other experiences that you have in med school really, because you're there 24-7, so you get to bounce ideas off each other or study together or whatever. And it's just, yeah, like a lot of the social stuff outside of work, you get to spend a lot of time together doing the beaches, partying, whatever, going away on trips. And yeah, just kind of set you up, gives you real good mates to go through the rest of your med school with and the rest of your careers with. In 2017, we expanded a similar program in the Bay of Plenty involving Whakatane and Tauranga, and next year, 2018, we're going to have a program running out of Hawara and New Plymouth, and so we've got great support from the Taranaki District Health Board to start that program. So we've spread throughout the Upper North Island in regional and rural settings, because we really believe in the mission of providing doctors for all of New Zealand, not just Auckland. You see the most amazing pathology in small towns. Science and medical driven. The stuff that we see and the stuff that we deal with is such a ridiculous contrast to what you have in Auckland. I've had people that have left Whangarei who were doing 10 times more at a more junior role than they are now in a more senior role. So the experience, the responsibility, the confidence you get with the job is amazing. You get thrown in the deep end. If you want a challenge, you just do it. And everyone's grateful for what you do up here, which is really cool. Great job to this action. We're in it for the long game because the big goal here is that the students who spend time here will ultimately come back and work here and specialise here and build their families and whānau here. I can definitely see myself having a future in Whangarei. Me and my partner have just bought a house in Whangarei. We've set some roots down. I have so many friends here from a completely different life paths and our main aim is to come back. We know that we're going to have to leave for a while for special training. And that's just life. That's how medical training happens. But we'll hang on to the house and hopefully come back and have kids here and have a family. And that's our plan. Be a great place to live.