All right, welcome to my session on building a managed database service using Kubernetes operators Before getting into the weeds. I want to start off explaining who I am and why I should listen to me So my name is Jimmy Zolinski. I'm the founder of a company called off said at off said we build a database called spice DB And what spice DB does is it stores your authorization data? So when you build a permission system for your applications Eventually, you hit a couple different types of problems Maybe you want to make dynamic changes to the system without changing code in various places or Maybe you have multiple applications that need to share the same data in order to determine an access decision in your code And that's that's the type of scenario in which you would reach out for an authorization specific database So my background is in product engineering and operations. So I've worked as a product manager in the past I've worked as a software engineer building Distribute system projects and then I've also worked in operations running those distributed systems in production So despite my background being in product, I still write code every day and carry a pager over the services that I build Prior to founding on said I worked at a company called CoroS which got acquired by Red Hat and at CoroS I actually co-created a CNCF project called the operator framework Alongside some other members now members of the outside team and what the operator framework lets folks do is basically more easily build Operators that they can customize Kubernetes and extend it in ways that make sense for running their their domains So as a part of CoroS I was also a maintainer of OCI which is the container specification And I've done a bunch of work in the container registry space over the years. So That's a bit about my background All right to level set the for the talk Before anything, I always like to kind of level playing field make sure that everyone is using Understands the same terminology or what we're talking about before diving right in So To be able to even discuss this topic. We have to kind of cover two major Subjects right the first is what's a managed database service and the second is what are Kubernetes operators? so managed a base service is going to be pretty much You outsourcing the operational side of a database to a particular provider So instead of you spinning up a database and managing on top of your own hardware or even cloud hardware This is going to be someone else doing that for you I'm purely giving you the details you need for your application to connect to that database and Then you're basically out of the out of the way for that So you don't have to maintain a pager or anything like that To make sure that the database is operational and able to serve traffic there's kind of two different types of Providers that you can outsource to there are cloud providers that obviously have the expertise in running software on top of cloud environments so examples of that would be Amazon RDS and Google Cloud Platforms Cloud SQL These providers offer the typical relational databases But they also have individual services for more specialized databases The other type of expert that you can outsource this to are the actual database providers themselves So folks like cockroach labs selling cockroach DB Dedicated and my own company also said selling space to be dedicated But there are plenty of other database providers in the space that also do similar Elastic search and Redis also come to mind as kind of examples of these database provider Experts that offer these types of services All right, so then what are Kubernetes operators? So operators are custom controllers For Kubernetes that encode application specific logic. So that basically means extending the Kubernetes API and teaching it about effectively new concepts that are specific to your domain the point to all of this is to basically effectively improve how Kubernetes is able to handle running the application but Even more greater concept is actually encoding your domain into Kubernetes so that The Kubernetes control plane actually becomes the central interface for everything it becomes the source of truth and you can always use The standard tools like your your dashboard or kube control to query that and understand what is running in production All right, so Without further ado I'm going to talk about my anecdotal experience building space to be dedicated The reason why I'm going to use this is not only familiarity But also because we've actually built the service semi recently There are a lot of other Managed database services that are probably built on top of kubernetes, but because of the recency of this I think it's probably more applicable to someone looking to build a similar service Today if they're trying to do that for building their own product or just building a platform engineering team internally at their business So the rest of the talk is going to be basically me describing the system we've built kind of like this the decision-making process we went through and Kind of the way we've kind of divided things up and how we think about The different problems that we had to solve So at a 10,000 foot view we can kind of break down this problem into three major phases Provisioning runtime and then the day-to-operations The provisioning side is going to be kind of how we create the customer environments so that means everything related to creating and updating clusters and what lives on those clusters and The finer details to that is actually how you decide to split up and differentiate between what is What defines the cluster and what defines the configuration that lives on top of the cluster? This is actually pretty subtle when you're trying to Understand what things should need to be updated with the lifecycle of kubernetes itself versus things that can be iterated on with changes to the application So that that's one of the subtle aspects another big one is how you're going to promote changes to these different customer environments How are you going to roll out kubernetes updates or any changes to the aforementioned cluster? Configuration and how are you going to do that in a way that? can be progressive and So that your customers if whether they have maintenance windows or they're very sensitive to updates You can get the updates at the regular cadence that they're expecting And we move on to the runtime phase the runtime phase is about basically What things have to be running? Live when customers are using these systems This is where the managed database as a service kind of differentiates from a lot of other workloads that you might be running on kubernetes Because the customers are actually going to be modifying the the cluster itself in real time and That basically means that we need to be able to not only manage our own configuration But also be able to respond to end users Deciding they want to take operations like scaling their database cluster up or down The other unique kind of problem in this space is going to be handling the availability and performance requirements of running a database Databases are typically very performance and latency sensitive workloads, and they're also stateful workloads so all these things kind of complicate the actual production runtime of of the system and Basically being able to run a service in a way where when different events like Scaling up or scaling down happens or you lose a node in kubernetes To be able to handle that in such a way that you don't lose any performance or drop any requests is very tricky and Something that every database of the service is going to need to manage Because you can't necessarily make Changes in the application code that is talking to your database instead. You need to make the the actual runtime As robust as possible because you don't have any control of the application code Connecting to the databases you're managing Finally, we have the day two operations which are basically the the actual operations that our SREs are going to be managing So this has to do with basically handling backups Specifically, as I said customers can modify these environments So that means we not only have to be able to reproduce our clusters But also be able to reproduce the state that the customers changed And then we also have to power our own operational workload So that means we need to be able to Aggregate metrics across customers who need to understand the health and state of the customers page our engineers and things like that when something is going wrong on a customer environment So I'm going to dive deeper into provisioning now I'm going to list out some of the technologies and some of the core concepts that we've chosen to go with I would say a lot of these different technologies are personal choice. I'm not saying you should choose one over the other But I'm going to include why we ended up with the ones that we have But these reasons are kind of organization specific and if you have a company, for example, that has a ton of Terraform expertise Go ahead use Terraform. I think that's going to be a better choice for you if if that's what you have the expertise in at your company, but for us, for example We picked Pulumi We're very comfortable writing go code and we actually wanted to build ultimately one binary that is kind of our infra Program that can manage all kinds of different things. So Pulumi just gets embedded into that process So we actually have commands for provisioning things But we have other commands for for accessing different systems that would be a part of our operations teams basically everyday work So that's why we ended up picking Pulumi For actually reconciling configuration in a cluster we use Argo CD Flux is another example of a CNCF project that also kind of does this continuous deployment We ultimately aligned it on Argo specifically because it has a nice web UI for checking the health of all the environments but also it has kind of Nice functionality for actually applying the changes like dry runs and pruning and you can actually write Lua to kind of extend Argo in some scenarios where We specifically for when you're creating operators you're going to create custom kind of definitions of healthiness in the status fields and Argo can be extended with Lua to actually understand those to know Whether a custom resource that you've actually created for your operator is healthy or not So that's super useful functionality there For the actual configuration we use on the cluster itself. We use customize We previously used Q a lot But we ultimately migrated to customize because it was really easy to structure Integrates directly with kubectl. So our engineers have to install any additional tooling It's way easier to onboard engineers because if you understand kubernetes You probably a kubernetes YAML at least manifests. You are going to understand using Customize to some degree And it lets us actually really reuse a lot of tools off the shelf Because you can kind of point to any manifest in a git repository and use that as a reference and kind of extend that Use them customize so as we adopt more and more of the kind of standard community tools We can kind of just point customize to those tools and get them vended Almost for free or with very little modification and yeah, if you're using Q you kind of have to do all the legwork of kind of importing and Transpiling basically YAML into Q and you're kind of on your own for a lot of a lot of the tooling and structure But I imagine some of that will change over time So it's not necessarily cut dry if you're watching this video six months from now Maybe the the state of the world for Q has improved dramatically Finally, we also use github actions and we use github actions Mostly because we can automate a bunch of the github APIs for opening and merging pull requests And that ties very much so into the concepts. I want to talk about The high-level concepts that we have are largely around kind of our promotion process, which we call the ring model the ring model is specifically about Basically bucketing customers into groups of stability so that we can slowly roll out changes one phase at a time to that bucket of customers So for example What we actually do is we have a staging instance and the staging instance gets every change push to it as part of a continuous deployment and then when things look good we Promote that to what we call ring zero and ring zero is other testing environments Whether it's doing performance testing or just staging environments at all said Then what what happens is once that kind of passes the Q8 there then we actually promote to ring one Which would be our rapid kind of released phase So customers that have adopted into getting updates sooner, but potentially less stable releases And then kind of so on and so forth. We promote to ring two which is more stable and then ring three which is more stable, etc So that's kind of how we structure how we roll things out This was inspired by the internal model used at github. We have some ex-hubbers Auth said and that that actually inspired us greatly to to solve this problem this way So we know it scales because being used by big companies like Microsoft so And finally we have kind of get ops, but get ops by bots is kind of how I want to talk about it because while get ups is great Making changes in some of these repositories can be very verbose and error prone It can take a really long time So what we actually do is we have automations all around it so you can manually Kind of click from a drop down to say I want to promote this ring to this ring and Then bots handle the rest so you get kind of like the the benefits of having everything checked into git And if you had to manually override anything you could But also a lot of the error prone Side of copy and pasting specific versions into specific places all automated away So in the general case you pretty much don't have to open your editor to to make the changes That you want to see propagated to the system Um, so here is a drawing of our customized configuration We kind of split it into three topical folders We have the bases the features and the overlays if you're familiar with customized overlays are typically used for the Kind of end results. That's going to be a renderable thing that you can actually apply to a cluster So we have a dev one or actually variations of dev ones And then we have kind of customer specific ones the customer specific ones we keep In a separate repository the info repository that tracks all the customer environments And the dev one lives in our mono repo alongside the configuration itself But then overlays are composed of at least one or more base and then a set of features So, um, examples of features are like postgres database or, um, ecr for getting your your images on this cloud provider or gcr if you're using google cloud So we actually break everything down into these different, uh, features that you can then compose together, um And uh, to actually build a working system And then the bases are kind of like the base layout for a cluster That installs the things that we want to assume are always going to be there So in the the actual like regular cluster base, we have Basically the monitoring stack that we went to use to deploy to absolutely every cluster to make sure we kind of have a Baseline of understanding the health of every cluster That's not specific to any workload that we deploy to it This gets used both on a an info cluster that we run centralized for our infra like operations team But also then on all the customers as well But then we also have this dev base and this dev base is basically filling the gap between, um, something like Docker desktop kubernetes or kind and making that Exactly similar to what we get when we run polumi to generate a cluster On a cloud provider for an actual production environment. So that kind of fills the gaps there so that, um The clusters look exactly the same. They have the same starting base Then we apply the base and then we apply whatever features are specific to that that environment So here is kind of the architecture of the didox pipeline In our mono repo, as I said, we have a configuration that lives in there that makes it so Developers can iterate on configuration and also the code for the different projects and kind of spin that stack up locally and running on their machine And test everything out and then when that looks good that gets committed to a mono repo And then what happens is we have this other info repo which tracks customer environments and customer environments are actually Organized into rings and then those rings reference a specific commit shot Of the mono repo So that you can actually point it to a particular snapshot of the configuration of the mono repo at a point in time So that's how we kind of get Basically all the version tracking and the ability for us to promote different versions of the configuration to different customer environments Inside of that infra repo. We also have The binary that manages palumi and that's what's going to provision the individual clusters We have configuration files for each Each customer environment in there as well So that's kind of the the central central source of what is represented in production Every cluster is also deployed into its own Cloud provider account. So if you're running on amazon, each customer runs in an ad of us account That's individual to that that particular customer. That's just the level of isolation we've chosen for the system But that's not necessarily a hard requirement for for every managed database as a service We're just a security product. So we take kind of isolation a bit more seriously than a lot of other people So then finally we have our centralized infra Kubernetes cluster. This is what runs argo. It runs Thanos So that we can actually collect metrics and and query and understand the runtime of our customer environments But what argo is going to be doing is it's going to be pulling the infra repo and asserting that Each of the customer environments is synchronized to the proper state that the customer environment is configured for So this makes sure that if there's Anyone that logs into a machine and they are debugging something if they skew the configuration It's going to be restored eventually by argo. That way Even if a machine gets gets compromised We kind of have something that's going to reset the cluster And basically make sure that nothing is nothing is the way it shouldn't be So that's our high level of kind of the GitOps workflow that we have Time to move on to the runtime environment In the runtime we have built two custom operators. So this is going to be the kind of The with Kubernetes operators portion of the talk, which is kind of the meat and potatoes So we have decided to split Basically our system into two different operators The first operator is open source and it is basically all of the configuration And operational know-how to automate running spice dv the database itself We make those open source because we want our customers Or any open source users to also be able to operationalize and run spice dv just as good as we can So this includes scaling spice dv making sure that it doesn't drop traffic making sure spice dv knows how to Basically self cluster It handles Running migrations that the data changes across versions It makes sure that it has an update graph and make sure that you go from a supported version to a supported version and Basically assures you that you have zero downtime as you go through the upgrade process So this kind of logic all lives inside the spice dv operator And then what we have is is the z operator, which is our proprietary operator. And this includes automations that largely Are reliant on assumptions about how we've laid out our clusters So if the functionality Is tightly coupled to opinions and decisions for how to run a kubernetes cluster Then we keep it in the proprietary one. So Purely because it's not applicable to anyone else's deployment. It's only applicable to ours So that's kind of the decision-making framework for us on where we cut cut things off on the open source and proprietary But at the end of the day the users they get this next js front end that we've built And that's the customer facing interface, but it's actually an interface to kubernetes So what we're actually doing is making it so when a user logs into the the dashboard for Spice to be dedicated They're actually seeing a view of kubernetes And the resources that live on the cluster and when they say for example choose to create a new space to be cluster they're actually talking to a javascript Application that is going to talk to the kubernetes api and create custom resources And that is how the core of everything is functioning. It's all using kubernetes as the source of truth And then of course we kind of have all the additional tooling that compose our Kind of opinions for how to run kubernetes. So that's using things like contour insert manager And like the prometheus operator things like these So at the core the concepts of our runtime include Basically centralizing everything into the kubernetes control plane. You want to use that as your source of truth It makes it a convenient api For for managing all these things for us our data like the actual control plane That's being used for customers to make changes is one in the same with the control plane that Our operations team is managing so that gives us a convenient way to To basically interact with the system. We don't have to build some kind of admin interface into the dashboards that we can kind of Get our operations team access to the customer control plane. No, it's just one in the same control plane for us So that's where a lot of the benefits come from But also the the power of the operators being that the customer driven changes Actually live also in the cluster So this is what's enabling the fact that a customer can log in start making changes to the infrastructure And those can apply immediately because all those automations are not a living operator That has to get paged and go to the cluster and make a change to it instead It is a kubernetes operator that's running in the cluster that can manipulate the desired state of the deployment and just run with it So with that, we have basically the namespace layout of one of our clusters Some of these namespaces get applied to absolutely every cluster and some of these namespaces are exclusive to a particular cluster. So The awesome monitoring namespace for example gets deployed to absolutely all clusters That we run this includes kind of like the all the infrastructure we need for paging alerting Doing metrics tracing applications that are running on the on the cluster And this goes all the way to non kind of space db customer clusters This also runs for example in our infra cluster so that we can make sure that the infra cluster is running and healthy Even though the infra cluster is only running our internal tooling and not spiced db workloads So this is fully generic and can be reused across the company But then gets specialized by kind of the resources that get created in other namespaces So then we have the Aucid system and Aucid region So the difference between these two are the system is what I would say is the customer facing control plane so multiple In region in customer environments where they actually are running in multiple regions. So say you have a Europe and a north america kubernetes cluster deployment. So you have two individual clusters What ends up happening is you pick one as your control plane and that's where the offset operator runs That's where the dashboard runs Anything that's kind of driving the information on the dashboard Is going to live there and what ends up happening is when you choose to provision something there The offset operator actually understands the configuration for the other regions that make up the customer environment and it will create resources In the appropriate cluster So Aucid region is kind of the thing that standardizes a cluster to be able to run space db So primarily it has the space to be operator in it And that's going to sit there and watch For the request to create clusters or make changes to clusters That the offset operator is then going to create as a reaction to a customer making a change in a dashboard And it's going to create those clusters inside of the tenant namespace So the tenant namespace is where all the kind of runtime customer data is This is where the systems they provision live It's the one that the operations team is mostly going to be inspecting Because these are these places where the customers are actually live making changes This is what we typically focus on for backing up Data like customer specific configuration the things that they have actually changed on the system Every other kind of like smaller namespace in here are the kind of cluster dependencies So we use the Prometheus operator and kubestate metrics Just to like make sure that we're kind of got the standard standard operational kind of deployment for collecting metrics and observability from the cluster I kind of mentioned earlier that we use cert manager and contour as our ingress and pki infrastructure And then we actually create two deployments of contour In the internal and external namespaces these namespaces are for internal and external traffic So because customer environments are often in VPCs like virtual networks That traffic goes through a specific load balancer And then internet-facing traffic goes through the external load balancer So that's how we kind of differentiate those and do peering to internal networks at our customers companies And then finally we have Valero, which is going to do backups and then All the kube system e namespaces that you get from the different cloud providers Cool so kind of transitioning now to The final topic the final phase the day two operations These technologies are kind of the standard ones and The reason why you pick the standard ones is kind of like the high-level concept. I want to Mention which is that the observability data isn't just for you Because you are building a system that is kind of customer-facing infrastructure Some of this data you're going to pass on to your customers. They want to know what the Latencies are of the database. They want to know how much cpu they're using They want to know how much capacity they're using if they're going to have to scale up If you're going to have to scale up is that going to affect their bill? So it's not pure purely your decision on what kind of technologies you're going to choose for for these stacks because They're going to integrate potentially with Customer systems They might want to ingest logs or traces or metrics from their database as it's running into their own systems So that they can also page their engineers if something is going wrong inside of the managed database service So for that we're using all the standard kind of Prometheus ecosystem For observability, so that's kind of the Prometheus operator kubes date metrics thanos Grafana The works there And then we use jigger for traces, but generically just open telemetry And then as I described before backups Need to be not only data. So we're using kind of the box standard cloud provider Datastore backups so the things that come with The data store themselves, but we're also building apis so that our Customers can basically export data out of live systems or stream that data to a replica that they have themselves Maybe on a completely different premise on prem or backup environment So we're we're kind of tackling this on both fronts But the unique thing is actually not the backup of the data But the fact that you have to also back up the configuration because if you restore the cluster And replay all plume and your configuration changes, that's not going to include any of the changes The customers have made to the control plane themselves So that's where valero comes in and we're actually Continuously backing up the changes that customers are making to the clusters So that if we have to restore a cluster, we can restore absolutely everything And the kind of nice thing is it's all kind of decoupled in different ways So we can restore just the customer data if we needed to restore it to a older version of maybe the cluster An older version of the configuration all the namespaces that run in the cluster because everything is broken out of these three different Categories we can actually mix and match versions to produce stable versions or unstable versions Of the environments for our users So with that Like to conclude you can find me on social media on these three places on Twitter blue sky and then you can always email me If you're interested in any of the projects I talked about We have a link to spice to be dedicated The open source space to be operators available for Exploring and kind of like learning how we went about automating the actual operational side of our database That's actually built on another library that we have open source called controller idioms And what controller idioms does is it wraps up high level behavior that you're going to need to implement for idiomatic Custom controllers and kubernetes operators into a library that you can just reuse So examples of this are kind of custom informers Setting statuses according to other properties That of like other resources you're managing Things like being able to pause your Your operator so that the operator stops reconciling so that a human can come in and debug Kind of like these higher level patterns that you would always need to implement that are not like the core logic of The operator we've kind of abstracted in a way that you can import And then also if you're more interested in spice to be itself you can always join the space to be discord or Look at our github organization We have plenty of other open source projects all around the cloud native ecosystem things Regarding basically all parts of the stack operators grpc The database itself Clients for the database things like that. So thanks for your time


So my daughter Ember over there is involved in a science fair and for her project we created some smoke bombs which obviously we can't set off inside so we created a video demonstrating the creation of a smoke bomb so since we took the time to make that video for this fair I figured I might as well share it with you guys as well. So here's that video I hope you enjoy it. Here I have two piles. One regular sugar, one potassium nitrogen. Start him.  Eat it! Eat it! Eat it!  Here's dad the preserve what he needs. What's that peppermint? Now we're gonna test the sugar. Here's some sugar. Thank you Connor you won't be needed any more. Now let's see how they racked under heat. First the sugar. Now the potassium nitrogen. Let's try mixing the two together. Mix together and add some heat. Now that's what I call a chemical react.


in the back there. My presentation is about my journey with Git in my contribution to Nextcloud, so I'm doing it this year as the Rails Girls Summer of Code team with my wonderful partner, Arcty, and you're going to hear more about that program later from the team that did it last year. I think when you start to contribute, getting your mind round Git can be one of the larger things to tackle. It seems like this huge imposing tool that everyone seems to know about, and you're not quite sure where to go, and if you're making a mistake, maybe everyone's getting angry with you, but as you start to learn and pull back the curtain, you start to see a few of the levers and buttons that make it work. So it starts with Git clone. You get this download of all these files on your computer, and you think, oh, okay, great. What's this? Time to explore. You have the opportunity either to fork it, or you can check it out in your own branch. If you don't have, sorry, you have the opportunity to have your own branch, or you can fork it if you don't have the permissions, and get everything on your machine so you can start working. And then you need to have some idea about it. So if only you had more information when you had a brain. These are a collection of the commands that I use to find out more information about what I'm working on. And these are the heart of my commands for when I'm making my commits to the wonderful contacts app. So unfortunately, five minutes is a little bit short to explain what all these commands do, but if you're not sure, I definitely recommend looking at the slides and checking them all out later. These are the ones for when I'm feeling a little bit cowardly or a little bit unsure of what I'm doing, and I'm kind of thinking, oh, I better stash that and make sure that I'm up to date. And then I can get my changes back later. And these are the ones where I'm out in the woods and I'm like, oh, yeah, not your word. And they really help you get out of sticky situations. And this is if you need to squash any wicked witches that you find in the code base. It's kind of really useful. So you've made all your commits. You've got your work up there, and now it's time to make the pull request, which can be incredibly nerve wracking.  Or if you, by accident, have written back code and then you're getting negative review. So before you send your lovely commits off, a few tips would be to add some keywords, make sure you reference the issue, add labels, add reviewers. I think one of the things when I was getting started with making pull requests is I kind of thought this is the face that the review would be pulling and that they would be judging my code very harshly. And then you wait. And you wait a bit longer because normally they're not online exactly the same time as you. But eventually it's coming back. And generally this has been my experience that it's a very positive response. You get a little bit refactoring. You learn a little bit more. But generally it's a positive and a very friendly code of view. So congratulations. You're now officially can call yourself a contributor. And my takeaways would be to ask lots of questions. Don't be afraid. Commit often. And with very relative commit messages so you can look back for yourself and remember what you did but also so that others can see what you were doing.  And if you make a mistake, it can generally be reset. There's very little you can do to really mess it up. So you'll also have a great time. And as you can see, I managed to get a copy of the group photo from yesterday ahead of time. So thank you very much.


Welcome, both of you. So this should be fairly straightforward. I know because of Memorial Day last week, we didn't get a chance to have a meeting. So I just wanted to catch up on where some things were from both of y'all's perspective, and I can share some of the stuff that I've got as well. Since we didn't get much of a chance to talk last week, how's the desktop happening going? Yes, so I just posted a status on the g-raw link just a few seconds ago if you can just scroll up. Yes, so that's the second one. Anyway, so I'm just going to summarize it. Basically, the PR works, but in a non-conditional way. So I have almost something that is working locally. I need to finalize the testing and so on because I started using the Docker Compose of write file, basically trying to make it conditional if the Docker socket would be mounted or not, so that we can test both cases. And I'm almost done with it, so I have a test that is going to be also enabled only when we are in that situation because, for instance, the Docker pool or run wouldn't work when the socket is not mounted. And what I wanted to say about that too, and then finalize the Jenkins file so that we use the simpler way and the make that we can run both combinatorials in CI constantly. So it's also triggered a lot of thoughts because maybe the Docker case is even more convoluted than the upcoming others like AWS because I needed to somehow expose the Docker socket to the user space and Jenkins is not a root, not running as root, which made it more complex than it would have been because I need to control something like this, which is like, you know, system level, which I think we won't have to do for automatically configuring things like AWS or Azure or digital ocean or whatever because we just will need somehow, I mean, some kind of key.   So the alternative of what I've been doing because I've been using Indeed Socat to create a somewhat hackish solution by forwarding the unique socket to locally exposed STTV port. The alternative is, I'm not sure it's acceptable. That's why I ended up doing that. The alternative is to ask users to basically do a CH mode, A plus RW on slash var slash run slash docker.soc, which I'm not sure is going to be a very successful approach because maybe people will be afraid. So that's it. I'm not sure what you think about that, but... Is this written down and some of the pros and cons of this? Not per se as a JEP, but I've put some comments here and there in the code, but I definitely are so intended to probably start a JEP at some point. But I'm not sure yet. I don't know what you think, what you people think here. Either I start a JEP for describing the specific case of Docker or I wait a bit more and implement the AWS case and then try to write some generic JEP to try and explain how we would configure, automatically configure things like clouds. So there's, I guess, maybe both, I'm not sure. I definitely think the latter is more important, sort of describing how we other configure the cloud. I'm sorry, Tyler, I really have a hard time understanding what you're saying, so I'm not sure for others. The song is really weird. Sorry, Gary. For everybody or only for Tyler? For me as well. What's happening here? Can you hear me? Yes, we can. Tyler, can you say again what you just said, slightly slower maybe? I always suggest doing a JEP for the cloud configuration in general. Yes. And just for Docker in particular, I think if you write down in the pull request or in the JIRA some of the comparisons or some of the ways that we could configure this, just I want to make sure you understand what the pros and cons are from the user perspective. I don't think we need a JEP for Docker in particular. When I originally put this Docker configuration in for the milestone one, it was really to make sure that we had some sort of example. It's not the destination as far as I'm concerned. I thought it was going to be the easier first one to take. Actually, I thought the same, so I understand where you're coming from. But in the end, I ended up realizing it might be the worst case. The most complex one to set up. Because indeed of the case that you are, as we are using as a user, then it's not accessible and so on. It kind of made the whole thing more complex. My hesitation is about the automatically configure part. I mean, to me, it feels like what we should be providing is a package of essentials. And if your environment that you're installing in is an environment that's defined as there is a Docker host, but there is not a public named cloud service or something like that, then we need to be providing a package and some format, whether that's a compose file or what have you, that includes all of the configuration of agents as part of the package rather than necessarily as part of the plugin. Yeah, I see what you mean. So it would mean in our case that right now what I'm indeed leaning towards is to configuring things in the indeed somewhat runtime way. And you're saying we should better rather to publish in many images and we can do this kind of static way. Is that what you're saying? Yeah, I mean there might need to be some runtime code to handle the trigger handle the actual configuration perhaps. I'm just saying that the trigger for this in the actual source of information should be something that's static in the image, whoever you wanted to find that that we ship. Yeah, in my mind I was I think that makes a lot of sense. And it makes it a slightly more indeed Docker compliant. I mean in the in the meaning that Docker should not be. Yeah, we should not be trying to do too many things at runtime, but you know trying to test thing upstream and it would make sense that in that that that meaning. Yeah, for example, there's some code in Docker workflow plugin that does try to auto detect the host environment and so depending on detection of stuff it automatically switches the behavior of the with container step to use which which Docker option is it to use volumes from option to Docker instead of a plane volume mount to try to share volumes. But it's really tricky. It has to do a lot of magical stuff where it's like inspecting the proc file system and we've had like 13 pull requests to change that behavior to account for subtle changes in Docker, etc. It's just. Yeah, I like that. I like that. So I'm going to try and see how we can adjust the work or maybe just push what I have and then iterate again to kind of keep the history for future archaeology. But yes, thanks for the feedback. It's interesting. And for other things. So maybe you can jump to Olivier on that one, Tyler, because I believe Olivier has tight tight agenda. So you should be free to go as soon as possible. We're going to introduce the topic. Yeah, right. Sorry. So because we now are starting to have the telemetry logging working working. I mean, from the cold side, nothing is deployed yet. We will soon have a need to actually make it useful for developers. So we want to provide access to handful or selected developers to actually use that data. And so we don't have really anything yet about that. So we are trying to see how we could use the existing setup in the Jenkins project communities cluster in fraud to see how we could push logs there in some way and make only the logs from essentials accessible to plugin developers, some plugin developers, and not everything from the Jenkins infrastructure. And that's what Olivier has been having a look at a bit. So last week, I had a look at that. And so there is no easy way to separate the logs from the Jenkins infrastructure forever green. But what could be easily done is to deploy a new free MD next to your service and just send the logs to the Log Analytics. So it can be quite easy to deploy a new Log Analytics workspace and send the logs there. We need to agree about the schema that you want to send on Log Analytics. And so, yeah, I think there is no big issue to do that. But I wouldn't reuse what we already did for the Jenkins infrastructure project. And there is another thing that I have to forget to tell is that there is no easy way to integrate that with our current setup. So what we can do at the moment is we can use Microsoft Agents as guest user on the dashboard. So we can provide a read-only access to that dashboard. But that's so for me too. I want to step back from this approach in particular. Did you evaluate using any external service like Century or Bugsnab or anything else instead of trying to look at these as actual logs but instead look at these as errors? Because for now we wanted, from what I understood, you thought would be needed to try and integrate to the current setup and make things simple. But if you think it makes sense to try and basically send logs elsewhere, I can look into that. What I'm saying is it sounds like it's not as simple. Yes, exactly. So because initially our hope was that we could be able to send things with just a specific tag to the existing Azure Log Analytics. But it seems not indeed to be the case. So now indeed we have that information. We can indeed try looking for alternatives like sending it to existing SaaS solutions or I guess it's the... Is there any budget for that? I mean, what do you need to do to use the SaaS service or should we look for, what would be the approach to use the SaaS service? What has worked fairly successfully in the past is to find the service we like and then ask them for access. Because that's typically got in us. I mean, that's how we got Pedro Dudi and the other dog integrated. There's a lot of people that are willing to give us a very cheap free account for... Because in that case that a dog also provides a way to analyze logs and create dashboard based on your logs. So this is something that you can request? Yes, definitely. I mean, yeah. I'm not sure what you exactly mean, Tyler, if you mean that we would just create a free mem account and use it for testing. Or we would ask maybe then that dog to... If they are ready to sponsor the Jenkins project with some non-simple, a bit more... So we already used datadog, but what I was thinking more was when I first sketched out this telemetry service, it was using Sentry. Yeah, or so because... Sorry, go ahead. There are services which are much more specialized for handling exceptions and errors. So if we stop calling them logs for a second and call them errors, and you search for services that handle errors, there's a number of them which might be better suited to our needs that if it's not easy to integrate with our existing infrastructure, it would be worth spending an hour to evaluating a couple of them. Okay, I will do that then. And I remember for what is worth about... We already discussed a bit datadog with Olivier, and he was basically saying that there's nothing... I mean, it's similar to the other existing community solution. Datadog would require to create a kind of a new account because there's no way from the analysis to segregate data depending on who's logged in. At least I don't need to make a levier for more things. Sorry. Do you need a levier for more things? No, I don't think so because if this is now to test solutions, I just need to create a account for and so on. I don't think I need to bother Olivier. I need Olivier for the existing access to the infrastructure, but I don't think I really need to bother him if it means testing Datadog or testing Century more realistically. Yeah. Okay. A little bit, Olivier. Thank you for dropping by. Thank you, Olivier. What else do we have? But at least there is that kind of solution. So there was a quality bar ongoing. I guess you want to have a look at some point with your kind of PM cap, Tyler, to try and see if you think, I mean, there's nothing obvious missing that would be a really, really short showstopper at that stage, and I guess that would be because then we can further the analysis, like detailing on each P1 case, what are the risks associated to it, and so on. Is that something you need me to get to this week? Sorry. I'm not sure I guess. Is this a thing I should be looking at this week? Depends.  I can do everything else. It depends on your schedule and your level of activity. I swear, I guess at some point, we will want to have a look at that and say, yes, the milestone one is done for real and we have tested everything and thought about the risky aspects, but I guess I can do everything else in the meantime. Everything on the left can be done and I'm not blocked by this person. Jesse, do you have things that you've been working on related to Jenkins Essentials or are you just sort of floating around? No, nothing in that area. Okay, I know we discussed a little bit last week on this ingest YAML file. If I can find it. There we go. And I know we chatted a little bit about a tool that would generate this from some bill of materials and just as I think I mentioned this last week in the GitHub channel, I don't really need any tool to generate this right now. I can create a hard-coded version that we can work with just to move forward. Yeah, I mean, once we have stuff running and are actually actively pushing core and plug-in changes into this, then you'll become more urgent to have them running for us. Right. And writing a tool to do that is probably very little work. It's just there's no defined source of input for it yet. Okay. For my side of the piece, you may have seen some of my work on getting the essential over ingest YAML into the update source. I started re-rubbing, adding to JEP 307 to accommodate how the update levels are created inside of the update service on Thursday and Friday of last week. I anticipate that that's going to be what I'm going to be spending time working on this week. And then what I don't have a good sense of is whether I should prioritize this, the deployment of the backend services or if I should spend some time on these other tasks. I don't know how useful it is for us to have a production environment right now. That's a good question. Because for the upcoming talks I have, I was wondering if it would make sense to have some, you know, demovable environment like, you know, only starting the client to docker run something, which would automatically connect to the evergreen.jentkins.io or evergreen.beta if you want to make it clear. Your talk is next week, isn't it? Yes, at the actual talk, but I have beta talks before. That doesn't mind, because the other one I'm going to do locally or something, but it could make sense. I'm not sure. I'm saying it's the 13th. You're looking for the exact number of hours we have left. Yeah, I've got to start the countdown timer. Okay, I forgot. If you want to have something to where you can talk with people at EclipseCon, when a prototype is getting evergreen.jentkins.io deployed, so that one could actually just pull the image and at least pull the initial version of stuff that's hard coded. I think that would be cool. The reason why I was really definitive about my answer just a few seconds ago is that anyway I will to have a really full pre-alpha demo, I would say, what would be awesome is to have the service deployed and a way to update the update level so that I can actually trigger an update. But we are kind of still a bit far from that. Thank you very much. The work that I'm doing right now I think would allow you to run that through an update cycle locally. Exactly. So that should be done this week for sure. That would be great. Even with duct tape here and there, I mean, I can explain we are still on an early stage but that's very okay. But yeah, if I have something to demonstrate that would be great. I'm sure you've got a duct tape version of this for EclipseCon. Confirming in friends-driven development, as always. So outside of that, in theory, in a couple weeks after EclipseCon, Claibus has hired another developer that would be able to work on this with us. So finally we might have somebody else besides Baptiste and Jesse in this call. But that will be that's looking like she's going to start after EclipseCon, so you won't get any of that benefit for EclipseCon, Baptiste. That's okay. I'm playing with duct tape for a week, so that's okay. So outside of that, I don't know if there's anything else that we need to discuss. It sounds like we're not blocking each other necessarily right now, but maybe towards the end of the week we should talk about error tracking services, Baptiste. That's okay. Can you please repeat? Towards the end of the week, I'm going to jump in and hang out and talk about what you've learned about error tracking services. Yes. Okay. Well, if that's it for the day, then I'll see you all later. Bye-bye. See you.


What I've noticed with the 2022 midterm elections is that you're starting to really see some resistance from within the Republican Party to Donald Trump Which is encouraging to me not necessarily because if Ron DeSantis were to win I think that's like better. I think that politically he could be worse than Donald Trump and more dangerous But in terms of it being better for democracy, I do think that DeSantis Challenging Trump and beating Trump is actually good Not because I think that he wouldn't be Fascistic if he were to become president. I think that that's that's certain. That's a certainty But what I'm anticipating is The situation or what I'm hoping for I should say is the situation Where DeSantis challenges Trump and he beats Trump and then because Trump is so angry Well, he cries fraud and if you are saying that a majority of the GOP base that just Opted for DeSantis over you that was fraudulent. Well, his claims of fraud are going to look a lot more Flimsy among the GOP's base at least so I want to see factionalization I want to see some real claws come out against Donald Trump And I think that for the first time in a while we're starting to see that so I haven't watched this yet But the Daily Wire shared this Candace Owens Reveals how her perspective of Trump has shifted since the end of his presidency What I'm saying is that Trump needs to take a good look in the mirror And he needs to exercise a tiny bit of a tiny bit more humility when he gets something wrong So this is the Daily Wire people coming out and saying We don't want Trump anymore Ben Shapiro did the same thing where he directly criticized Donald Trump and on top of that Matt Walsh is not mentioning Trump's name But he's alluding to the fact that all of the Republican Party is bad except for the Florida Republican Party inadvertently or not inadvertently implicitly is the word I'm looking for endorsing Ron DeSantis and now you have the Washington examiner here Saying act accordingly a conservative Washington examiner calls on GOP to draw to dump Trump Citing his chaos and dishonor you have Fox news Publishing this op-ed by Liz peak Ron DeSantis is the new Republican Party leader Republicans are ready to move on without Donald Trump and Then you see Oliver Dossi for CNN business saying it is not an accident Murdoch's media empire celebrates DeSantis as future of GOP after midterms So you see the Daily Wire you see Fox news and Murdoch's Empire all making a pretty sharp shift Towards DeSantis and they are essentially handing DeSantis their support on a silver platter So if he doesn't challenge Donald Trump, that would be very stupid I know that challenging Trump right now according to the polls looks bad But he has the media apparatus behind him So if he doesn't take up this opportunity, he's an idiot because somebody else can emerge that the GOP base likes more than him So we'll watch a little bit of Of this here. I want to see her reasoning here, but you see that sir and they're turning on Trump and I think that this is them trying to Prime the base to leave Donald Trump finally will it work? I don't know But I hope they Trump actually got upset with me because and here's the great irony the richest irony the daily beast ran a headline Regarding that live Instagram that you just heard from me and the headline was Candace Owens says Trump is pro-vax because he's too old to understand the internet. I never once called Trump too old I didn't never want to that Trump could not understand the internet and Yet somehow he got that information and believed it to be true He thought that I said that he was too old and then he couldn't understand the internet and did not Quite to get the information that actually I mean, I remember the quote. Didn't she basically say that? Either way seems like he reacted negatively to that And we'll see what she says thing was the fence of him so that his supporters would still believe in him Not only was he just mad by the way he then During a golf session with some mutual friends of ours had a person next to him who was egging this on Saying to Trump and I know this because again, this is a mutual friend.  He was actually rude to me based I'm telling you this personal story because I think it is something That made me for the first time question him as a person so you have an individual that's the only time you begin to question him As a person is when he's rude to you not all of the other terrible things that he does Jesus Christ so many conservatives are just Shamelessly self-centered and if it affects them directly, that's when they're like Okay, now I can I can reevaluate the situation But still this is interesting because Donald Trump it shows you how Pettulent he is how big of a man baby he is Because I mean look if you want to run for president again, you can burn bridges, especially with people in media, but he's just Shitting on them And he I guess he's expecting their loyalty But to him like disloyalty is probably one of the biggest sins So yeah, Arianna says I like imagining a civil war on the right Yeah, I think that maybe Cracks are starting to form We'll see how much right wing media kind of eggs on these tensions between him and DeSantis But certainly they really don't want Trump anymore and I don't I don't blame them Not only is Trump a loser for them electorally He's genuinely bad for democracy and they probably don't want to keep pretending That the election was stolen from Trump because they all know that that's not what happened. He lost fair and square But I mean, they've got to be sick of them, right There's defending you right And that individual gave you a completely kind and fair interview You said something yourself that your base didn't like and you somehow transformed that into something that I did wrong That's unacceptable That is that is not being a leader that is not owning things that you did wrong that is not owning that you Misunderstood something about your base. That's not growing. That's not developing In fact, he should have tried to understand why the base was so upset with him Which would have led to the fact that his base is not pro covid vaccine It's that ironically like the one thing that got the base to turn against him was uh him being right for once Uh saying the vaccines are good And we know that the reason why he said that is because it's all about him He wants to be able to uh take credit for the vaccines and I don't blame him He can get some of the credit Um, it saved Hundreds of thousands if not millions of lives So I understand why he wants to take credit for that But I just it's so interesting that the one time in his life maybe that he actually is correct That's when all the pushback comes What a world Well, I understood that I could have told him that but at that moment I realized that he's not listening Who is this guy next to him trying to egg him on to be angry at me for trying to defend him Has he ever listened though and to be fair I I think I would agree with her assessment That by trying to rationalize his pro vac stance She was trying to defend him Um, it wasn't a very good defense, but it was a defense nonetheless, but I just love how now she's like He doesn't listen. Uh, he's really uh, he's making it personal. It's just it's hilarious. It's like, yeah Where have you been kandace? We've all seen this but I mean you uh You were grifting off of him so you couldn't admit it but now that the daily wire is trying to push Uh, I don't know if they they're pushing desantis as explicitly as the murdoch empire is but they're pushing a Not trump narrative, which is effectively the same because who else would be able to challenge trump, but desantis Say that he's not a shill to say no actually I think that he genuinely does support the vaccines. He did genuinely support the vaccines So all of this going on made me again question Him if he was becoming too angry, which is to say that when trump went into the election in 2016 He was having fun, right? He was naming people giving them fun names enjoying the base having a good time I would even say in 2020 you could feel the energy. It was electric I think after the 2020 election and because of the shock of all the things that happened and The answers that we never really feel that we got This like sinking realization that we might be actually losing our country I think but it pushed him into an angry space where he doesn't trust anybody or he doesn't listen to anybody where he's he's Almost likely to believe that everybody's trying to turn their back on him and stab him in the back And again, I don't believe that that's leadership, but I never spoke on that because I thought to myself I I think that's a lot of ego that trump is having right now, but maybe I'm being egotistical maybe Trump egotistical what Donald j. Trump him being egotistical By the way, I'll turn off dog cam because we're just looking at poopy's butt Uh, he's very clearly camera shy right now. So um, by the way When was this posted november 9th the day after the election? So I need people to understand that this is all very calculated the right Really wants the base to abandon donald trump. Um, now i'm done with candice. Let's let's get to some of these, uh These other outlets here So the conservative washington examiner called on the republican party to dump former president donald trump during an autopsy of Tuesday's disastrous midterms Well, there are still still votes to be counted and expected red wave Never made its way to um to shore. Can I just read the article instead of? Uh media aides, let's see Okay, so this is apparently an editorial uh board op-ed here So voters show they want sanity and don't want trump Wow, that's uh They're saying it which uh, you know good for them But just look a little bit closer Especially at the races for governor and the pattern emerges Florida was a refuge of sanity when the world went mad governor ronda sand is actually the opposite is happening by the way Um governor ronda sand is said in his victory speech Tuesday night. We have embraced freedom That's hilarious coming from ronda sand is so florida voters love the message and whereas then president donald trump Barely beat joe biden by three points in the state only two years ago Desantis crushed his opponent 20 points on tuesday other republican governors who brought order instead of chaos also won So, uh, trump's hand-picked candidates flopped Um, so what's the what's the main? Conclusion an election that leaves the house and senate so closely divided may seem like it does not send a clear message But this one does these midterm elections have made it crystal clear that voters want to move past the chaos and dishonor of the 45th president they want the security and sanity that a competent and effective leader can provide The republican party needs to recognize that too and act accordingly. I would love to read the comments here Uh, I don't know if they have any comments, but They're straight up just saying it's time to dump trump. Now. Uh, this is from fox news here, uh The biggest loser donald trump who's hand-picked loyalist candidates in a number of races struggled to beat vulnerable democrats Once again the former president may have cost republicans control of the senate in a year when it was theirs to lose Many will conclude on the basis of the midterm uh 2022 results that the republican party is ready to move on without donald trump as its leader So many people are saying um and again bringing in desantis Let's get to the final paragraph because that's usually when they summarize everything Let us hope that the millions of americans who have supported trump in 2016 and again in 2020 begin to see That his time has passed if they like his policies They need to move their allegiance to ron desantis who has never lost a campaign and who emerged the big winner in these midterms So yeah Once again, they're saying all right. We love trump and his policies, but it's time to move on What are the comments say though? There's quite a bit. I voted for trump twice And would reluctantly vote for him again if he were the republican nominee that being said He is truly interested in what is best for america and the republican party. He should step aside Um, if he is truly interested in what is best for america and the republican party He should step aside and put his support behind desantis So this one has 344 likes to 23 dislikes. That's I mean, we're talking about fox news's core audience here Um agree 100 percent great article and I agree I voted for trump twice, but with the fight that we're in now for the heart of our country We need someone less ego to be a leader. Wow so the 24 election has uh It has to be more than a running a candidate bent on restoring his popularity So they're finally Beginning to wake up a little by little this might not be like the dam bursting open But this is at least the trickle where you start to see The winds change and you know some some cracks in the dam I'm thankful for four years that trump gave us, but I don't believe he is electable any longer I love to see this. Um now just getting to the shift from murdoch in general so um Rupert murdoch the media mogul who controls some of the most powerful organs and conservative media Appeared to make clear wednesday that he would prefer to cast aside Former president donald trump in favor of florida governor ron desantis As a leader of the party the new york post a tabloid murdoch controls hailed desantis's election night Uh election i victory on its front page wednesday morning Uh, so the new york post um headline was de future Uh alongside a photo of desantis and its family celebrating their major win in the sunshine state And i've just got to say they're kind of shameless, right? They're all shifting To desantis from donald trump. They're all coming out with these op ads Candice owens is all of a sudden right now a day after the election sharing How trump was rude to her And you can tell that management is instructing them to do this Um, isn't that interesting like for me. I don't have a management It's just me. I uh am one of two people that runs my show Um, and whatever we want to say, we do say we don't have anything from Executives telling us hey mike now it's time to shift to this like I just say what's on my mind But you see all of these propagandists taking their marching orders and like good little stooges. They're doing it But you know what i'm glad that they're doing it I'm glad that the new york post fox news the washington examiner the daily wire I'm glad that all of these outlets are turning on donald trump because he is a threat to democracy And honestly if gop voters shift to ron desantis from trump I think we have a chance not because I think that desantis Is any less destructive as I emphasized earlier. I think that if desantis were to be the gop's nominee Um, I hope he loses. I'd fight like hell against him Uh, even if joe biden was the nominee and I wouldn't be very excited about that But just having him beat donald trump In a gop primary would do wonders because again if trump Doesn't go quietly into the night after he's defeated by a fellow republican that kind of Secures it. That's uh, that's it for him, right? He can't cry fraud. He lost fair and square and he's not going to be able to admit that he lost fair and square It's a wrong quote to sanctimonious So it's going to be interesting to watch folks A favor and click the join button on youtube to become a member Because mike's doing a great job getting to watch his videos before everyone else is tremendous Many people are saying this Join today folks. You won't regret it


says, just wondering, there is a way to show just a part of screen when recording on teams. If I want to show something to talk about, but do not want my notes, also on screen to show. So how do you do that? Assuming that you get enough screen real estate, and you can have your notes and the part that you want to share on one screen, then, or multiple screens for that matter. When you go to share, don't share the desktop. Use the share the applications option, and then you can select your target window that you want to share out, and that should do just what you want. It gets a little tricky when you have to switch between tabs or applications, right? So you're going to have to stop sharing and then reshare, but. Well, there's a, for people, so like I have two monitors, and so when I am presenting something, I generally will have the PowerPoint presentation, the video over it, but I'll have a browser open on my second monitor. I'll have the presentation seen over there, and then I'll share the monitor. So then I just alt tab in between the browser, if I'm going to demo something or show something in the presentation, and I can then have my notes over on my primary monitor. And so if the issue might be exactly what Norm said, where you share out the application rather than the entire monitor so that you are limited to what you see, it also improves the performance of teams. So it's less of a drain on your resources by sharing the application specifically. And I suppose the one thing I didn't say that, it's important to realize that people are getting these ultra wide monitors now, and when you share the desktop and you just have a small, you know, Internet Explorer window, it's a really bad user experience. So I'll use something called Fancy Zones, which comes with Microsoft Power Toys, it's free, and then you can just, it is very fancy indeed, and you can set up zones. So I have this set up, and then I'll snap my application to a predefined zone. So I know that the user experience is going to be something that I expect like a 1080p type resolution. But I'll drop the link in there. Fancy Zones is pretty cool. I use the color picker out of the Power Toys every day, like every single day. So Sharon, Jonathan did his session at Cabo last Friday on Power Toys. I'm not sure if they recorded that, but that might be, they did. Oh, they might be a resource for them. You can go watch the fabulous Jonathan Weaver. Oh, do you have the link? Can you share the link to that in the notes there? I'm not, we don't have them yet. They recorded everything, but I don't know if they're going to post it. But yeah, we can do an update on that for sure. I'm sure they'll post them somewhere, but yeah, he put a brand new session together on Power Toys. He's been using them like every day. So. Very cool. Well, it makes for a great video talking about something that's not yet published. So, thank you. By the time somebody watches this, maybe like by the time they watch this video, it'll already be published and they'll go Google it. And then you'd be saying, that's exactly what I need. That's awesome. In the future, yes. It's future self.


Alright everyone, we got some breaking news for you, no fancy preamble, we need to get right into the story because it's huge. So Shin Megami Tensei was accidentally updated, the Shin Megami Tensei 5 game, the Japanese website was accidentally updated tonight and it was captured by PersonaCentral.com. The site's down right now so I can't even show you it but I do have it loaded on this laptop here. So we're gonna go off of this, we're gonna read it all to you, it's been verified by many sources that this was real, this has happened. Let's get into it, it says the official Japanese website for Shin Megami Tensei 5 was mistakenly updated with new release details for the upcoming game, including its release date of Thursday, November 11th, 2021, that's right, it's like a week before Pokemon, crazy. As the information came from a Japanese website, it's possible that this release date is only for Japan, however the game was previously stated to have a worldwide release so it presumably close to other territories, essentially it should release the same day if not the day before. Totally with an error made prior to the E3 2021 Nintendo Direct on June 15th, information for the Nintendo Switch exclusive RPG and next mainline entry in the SMT series has been displayed erroneously on the Japanese webpage. The details are the following, description, the latest mainline title in the Shin Megami Tensei series, Shin Megami Tensei's first release in 1992, the series has gained in popularity for its dark world view, anarchic scenarios and original combat systems with demons and deities as allies. Shin Megami Tensei 5 combines the unique charm of the series with the high quality visuals of the latest hardware. The game will deliver a new demon experience like never before. The main character is a high school student living in an ordinary life. It wanders into another world called Daat, so DA apostrophe AT. The hero fuses with a mysterious man and becomes the Naobino, which is N-A-O-B-I-N-O. A forbidden being, throwing himself into battle between gods and demons. In the mysterious world of Daat, where the desert is found all over, various gods and demons are scattered about, including demons as large as mountains and giant birds flying in the sky. As you explore Daat, you'll face over 200 demons. In addition to familiar demons, several demons, newly drawn by Masayuki Doe, the character designer in the title will also appear. Daat is an untamed land and is under attack by powerful demons. The protagonist clears his way through to pursue the truth, make use of various means to advance, such as growing the power of Naobino and sometimes utilizing the power of the demons themselves. The end of the game can diverge in many ways. What is the future you will choose? There will be a limited edition. This limited edition was on the Japanese website. There's no guarantee this will be anywhere else, but it's called Shimigami Tensei 5, first limited edition, the forbidden Naobino box. The first limited edition of the Shimigami Tensei 5. This box contains the game's charm, packed with plenty of demons and music that embody Shimigami Tensei 5, so like a soundtrack. It also includes an item resembling the hero, so a statue or a coin or something, considered a forbidden being in the game. It's an RPG for Nintendo Switch from November 11th, single player. The standard edition is 8,890 yen, limited edition is 14,800 yen and the digital version for some reason is more expensive at 9,878 yen and it's rated 15 up, which is going to be a T plus game here in the United States. So there you go, that's the breaking news and my word, am I excited? Talk about a big time RPG coming to Nintendo Switch. This is one of the biggest, it's exclusive, it's supposed to have been one of the very first games ever announced for Switch, it's now coming out. This is huge, it was leaked accidentally by Sega themselves on the Japanese website. This is absolutely insane, what breaking news in the middle of the night, this is clearly not how they wanted this news to get out there. Somebody hit send on the official website in Japan before they were supposed to. Really it was going to be a big E3 announcement exclusive to Switch, wow. Speaking of E3, what we're reacting to this and so much more at E3 itself. We have a four day show going on for you guys, it's going to be insane, we have $3,500 plus worth of giveaways, a whole bunch of crazy stuff happening. Well I'll link to the first two days, we already have the stream set up so you can go set your notifications for that. Also link to this story and also the original Japanese webpage for it even if it's been updated and put back, doesn't matter, we've already seen it. So yeah, this is really exciting stuff, hopefully you guys are looking forward to all of this and all of our E3 coverage. I hope to see all you guys either in the next video, next live stream, we have a live stream Friday, 8pm central, otherwise we have our standard videos coming out sometime tomorrow. So thank you guys so much for tuning in, I am Nathan Der Robbenjens from Nintendo Prime and hopefully you enjoyed this late night breaking news. Oh by the way, I know I just got up for a second, Birdman, thank you man, it's on you for this one.


All right, let's do a role play, right? So you're property owner. Ring, ring, ring. Yep. Hello. Hey, Sean. Hi. Who's this? Hey, Sean, Ricky Caruth here, whatever real estate and whatever area. How are you doing today? I'm good. Cool, man. Me too. I'm enjoying the day. Isn't it gorgeous out there? Yeah, it's pretty nice. How'd you get my number? Oh, I found it online somewhere. Listen, I didn't want to take up too much of your time, but there was a house right around the corner from you that just sold. Just calling to see if there's anything in the world I could do for you today. No, I'm good. Thanks. Cool, cool, cool. Is there an agent that you would work with if you were to do something? No, we've lived here for a while. We're good. Gotcha, man. Cool. Well, listen, I'm sure at some point in the next five or 10 years, let's say, I'm sure you're probably going to buy or sell a piece of real estate, I would imagine, right? Yeah, I suppose. Yeah, I guess. I don't know. Cool. Listen, hey, I'm just here to help. I'd love the opportunity to work with you when that day comes. Would it be hard if I just stayed in touch with you? Sure. Yeah, I guess. Oh, I'm kind of late. What's a good email for you? What's a good email? OK. All right. Cool, is this your cell phone number? Great. Well, listen, man, it's been good to meet you, get to know you for just a sec. If you need anything in the world whatsoever, I'm going to stay in touch with you via email. So I'm just, again, I'm just right down the road, by the way. I'm like right down the road. I'm a phone call away. If you need something, you need help moving a piece of furniture.  I'll tell everybody I said, hey, and we will talk to you soon. OK. All right. And then you're just adding that to your database and just trickling them, I guess. Exactly. And so that's kind of a script. I mean, so that's the script. But what ends up happening is you end up relating with something. You find some common ground. And normally you get into conversations that spiral into just different areas of the conversation. But it all kind of comes back to the same place. But yeah, like, and the ones that are kind of standoffish, like you were, doesn't bother me at all.  And I'm just here to say, hey, I'm, nope, nope. You know, like, I'm safe. I'm a safe person. I'm not trying to give you to do anything or anything like that. I'm just using your property. This is what I'm doing. I'm using your property as an excuse to see if I can get into a conversation and get to know you. That is it. I have zero expectations if they're going to buy, if they're going to sell. I don't care about any of that whatsoever. Again, the number one reason why people choose a real estate agent is because they had a friend in the business with a great reputation. So I want to be that friend in the business with a great reputation. In a way, it can be that friend in the business, the great reputation, as if I call and talk to them and create that friendship and then have a great reputation. So coach me right now. What would you do tomorrow if you were me? What would you do today right now? Should I get up and leave this conversation right now and go somewhere else? What would you do? I would study my MLS every single day, right? The hot sheet. I would understand the new listings coming in. I would look at closed sales, pinning, expires. I would just glance at that every single day so that I could slowly become a market expert really overnight. Then I want to pick out some subdivisions I really want to zero in on and really learn them from front to back. Go look at all the active listings firsthand, walk through the houses, talk to agents that have sold in those subdivisions and stuff. And then I'm going to call all the owners. I'm going to hit them with everything. Direct mail, social media, phone calls. If I can get into, if I can do some open houses in that subdivision, I'm really going to crush that subdivision and really milk it for everything I can until I've just completely exhausted that subdivision. I'm going to do the same thing to the next one. And then we'll go from subdivision to subdivision to subdivision just absolutely just expanding my footprint. Because I'm going to pick up a few friends in this subdivision, a few friends in that subdivision, a few friends in that subdivision. And I'm going to keep on going until I've got a good 5,000 people in my market that own property that I want to sell that are friends with me. And that'll take me a good five years to do that. But again, I'm not going to sell anyone the dream. This is not the dream. The dream is after you've put that work in for a decade or two that you've got a database big enough to rely on for past client referrals and referrals over referrals. Whereas these people aren't, they're not interviewing three agents. They're calling you. They're calling one agent. And that's the dream to get to that part of your career. But there's so much bearer of entry to get to that part of your career that you might as well not even talk about it. You know what I mean? It's so true. So I would study my MLS every day. I would absolutely crush each subdivision one at a time, studying the history, studying every little thing about it, calling all the owners. So when you say send to the MLS, just so I can kind of get conceptually. What's that information you're trying to glean? I mean, obviously, than the obvious data. I'm going to the hot sheet. You going deeper? You talking about just the general market, the hot sheet and stuff? I'm going to the hot sheet. I'm just looking at new listings, glancing through them, seeing if anything sticks out. When you do this, you're going to see listings that you may have buyers for. And you're like, oh, man, look, this might be good for so-and-so. And you send it to them. Or you're also going to see things come up in subdivisions and condo complexes that you represented a buyer that's already in there, that owns in there. And you're going to say, man, that's cool. Something popped up in there. I'm going to send this to them and check on them, see how he's doing. Reminds you to call certain clients and stuff. But not only that, you become very hands-on with the market. You've kind of got your pulse on the market really closely. And when people start asking you about the market, it's good that you're going to spit stuff off the top of your head. I remember when I was doing this, when I was at the top of my game, like in my market, like in it, people would say, oh, well, what about this building? I'm like, oh, there's four for sale in there, ranging from, I could just sell all the stuff off top of my head because I'm watching the hot sheet every day. I see the listings as they come on. I see the same listings go under contract in a week or two. Then they close at whatever price. When you're looking at that every day, you just subconsciously become one of the major market experts of the area really quickly. So you become this market expert. Then you're dominating each subdivision. You're spending all morning calling on the phone, making calls, having conversations at a very high frequency.  It's real simple stuff, bro. So when you're calling, because I've talked to a couple of people who've done it. And obviously, I'm not afraid of the phones, but that's back when I was selling mortgages and stuff and calling people at dinnertime. When you say banging and clanging in the mornings, like, A, what's a good number? Like, how many people do you call it, too? What are you talking about? Are there like scripts? I mean, we're just going to pretend I'm at ground zero here, because I am, right? So yeah. So all my scripts are on zero to diamond.com. Everything's totally free. You just go there and do it all the same. You're really totally new to me. Like I said, I just kind of stumbled across you. And I was like, I heard, I don't know. I think somebody else who a friend of mine was watching you. And so I kind of was like, OK, I'm going to see what he's watching. So I'll check it out. I've got courses here. I've got tons of courses there. They're all totally free. You can go there and download everything, the scripts, how to get numbers, videos of me making calls, the whole nine yards. But when I'm calling, seeing if it's who I'm supposed to be talking to, right? Like Mr. Johnson, for me at that point, it's time to get after it. Because once I realize that this is the name of the game, how many property owners can I talk to, then game over. And that's what it was. I did this until I was selling 100 properties a year and I didn't care about anything else. So basically your method was just that. You started your morning off just dialing. I want to organize my business at 8 o'clock. I really schedule my day on a legal pad. And then I want to study MLS for a good 15 minutes and really wrap my head around what's happening new in the market from yesterday. And then I want to start thinking about who I'm going to call about 8.30 and really get all my ducks in a row with the numbers and the dialer and scripts and data that I need for the calls. And then by 9 o'clock, I'm dialing 9 to 12. So I don't care how many numbers I dial. What I care about is how many hours I dial. So I may have a three hour session where I call 100 dials and talk to five of them talk to me for 30 minutes apiece. And then the next day I may dial 250 numbers where I had only one person that talked to me for 20 minutes. So I can't dictate day to day how many people are going to pick up, how many people are going to want to talk for a while, good call sessions, bad call. I can't predict that part. So I don't care how many dials I make. What I care is that I was on the phone for those three hours that I dedicated to my business to do for that day. Now, if all of this is on the zero to diamond then. So because I'm kind of clueless to all this. I've got some great people who have mentored me. I know you probably know how EXP works. I've got some great people who have mentored me. The downside, I guess, to my mentors is they've been it just forever and so they've got such a great database. They've got such a network that they're not dialing. They're not even doing social media for that matter. They literally just kind of live in that database that they have and so I'm like, hey, what do I do? And they're like, you're really good at social media. I'm like, that's so great. I guess I don't care because it's good. You get a lot of people who see your face and I think Facebook gave me $31 last month and I'm like, yeah. What you have to do with social media, bro, is you have to engage with other people.  Have a really clear bio that shows who you are, what you do, where you're at. A lot of real estate agents in their bio, I can't even tell what market they're in. You know what I mean? It just says real estate agent. I'm like, well, where are you? I can't really tell. You need to have it really clear where you are, what you're doing, and that way when they go to your bio, they know exactly who you are and what you're doing. But you need to be engaging and try to create those back and forths and then that could go to the same place, like how are you doing? Enjoying the day, I sell real estate, something I could do for you. Great, you have an agent you might work with. Okay, cool. Can I stay in touch? Great, what's a good email? It's all the same stuff. Right. No, that's awesome. Hey, I appreciate it. I 35 with the top down, could you tell a hater that you're getting like?


Stellentize salary decrease in 2022. Stellentize, the manufacturer of Fiat, Ram, and Peugeot automobiles, announced in a report on Friday that CEO Carlos Tavares 2022 compensation will decrease by 14% to 14.9 million euros, or 15.71 million dollars. It was revealed in the filing that Tavares did not earn a retention bonus in 2022, while receiving one in the neighborhood of 2 million euros in 2021.


scary obviously anytime a ball comes back like that to have the x-rays come back negative how much of a relief is that yeah it was big I mean getting that news you know in the middle of the game when we got it was was good to hear so we'll just kind of hope for the best now in between the starts here and hopefully I won't have to miss anything. Judge said on the field he felt like the Ben and Tendi home run really loosened everybody up did you see that throughout the course of the at-bats after you were able to get on the board there? Yeah I thought I mean you know obviously good at bat there by Benny you know I thought the guys had you know all day up and down the line I've had some good at bats you know couldn't really pour it on there but I I didn't think the at bat quality went away we had some balls right on the nose at some people so you know yeah I think Benny said a good tone for us and and guys were able to really really capitalize from there. Another good out from Wayster, I don't know if that first inning that can really affect some guys and he now had a couple good ones inside. Yeah yeah it's really good to see and you know you know giving us two innings there after two two days ago you know it's not exactly how I'd want to do it but he was so efficient you know that was big that set us up you know to kind of roll out the guys how we wanted to do it from that point on and you know credit to him you know you know that first outing was rough was not good and it's easy to have it snowball on you up here and you know it kind of put his foot down the next time and I thought he went out tonight and was real efficient again. Aaron how about the bullpen just overall you weren't planning on two innings and we've asked you a lot of questions about strongly bullpen the last five six weeks. Yeah they were great you know all kind of doing their part picking each other up and for the most part you know we should have some guys in play for tomorrow you know headed into an off day so you know once once Jame was out of there after two you know we knew it was gonna have to be a shared load and everyone kind of did their part and you know got us to the finish line so great job by all of them really. Home run from Rizzo yesterday another one tonight what do you think's clicking for him at the plate?


Hey guys, welcome to another video which is going to be should be short just me talking Just wanted to show you how long it takes for Oil pressure to build up after your car has been sitting for a long time. Now a long time can be a month also You know, well, I was gonna say years, but not really. Let's say you have a race car You know you use you kind of Put it away during winter time and you only use it for track days autocrossing When it's when it gets warm basically, right? So starting from say April all the way up to October Maybe even November, right? So the car will sit for Seven to eight months Which is quite a bit So let me reason for this video is not to just start your Engine after it has been sitting for a while because you will get what's called a a cold starts and During the cold start the first half a second maybe, you know, not not not long But it's enough to possibly do some damage to the bearings rod bearings main bearings Because there's not enough oil between the bearings and the journals because it has been sitting for quite some time, right? Now, I'll give you an example. I sometimes do oil pens, right and one time It was a V8 Some V8 car whatever It was a classic car and I did an oil pen the oil pen was smashed in so it needed a new pen obviously so But what happened was after taking the pen off and examining it it had cracks where the the rear main seal is and so what I was originally going to do was You know fix the pen somehow Just to fix the dent where the bolt is on the bottom or cut it cut the bar I actually ended up cutting off the bottom of the pen and welding on a new piece that I cut off from the from the new pen because those pens were not available and Blah blah blah blah blah, you know, they were too big so but the bottom and Fit right so but I had to do a lot of welding and stuff and also did Welding on the cracks and all that stuff and I had to paint it prime it paint it You know and all that so that took probably about a week or so during that week The oil the car was up in the air on a lift and the oil Kept on dripping for that week Obviously was drained before the oil pen was off and The oil kept on dripping for a week. It would keep on dripping for longer That's how how long it takes for that oil. That's everywhere, you know inside the heads around the black area Basically all over the engine, right? That's how long it takes for it to come down Now if you start your car every day or maybe every other day Then that that's not issue start your car Go go driving, but if it sits then That engine up top especially it's it's almost dry now. Obviously, there's gonna be, you know Some oil left something to be super dry like it was just built But you know it has a lot less oil is what I'm saying So to avoid that cold that first cold start after it has been sitting for for months and months Pull the fuse pull a mission fuse in the case of Subaru's it's very easy Actually, you want to pull the plug on the crank sensor, which is right in front underneath the alternator Then you just crank the engine until oil pressure builds up and that's it Then you can start it now on a classic car Well, you know American American muscle really where there is Where those cars have Carburetors chances are those cars will not start right away, you know after a second or two of cranking Actually, the chances are pretty big actually So really wouldn't worry about oil pressure on those kind of cars, right old carburetor cars But on a fuel injected cars They will start right up even, you know, it has been let's say the battery is good has been sitting for a year You're going so remember don't start your vehicles without any oil pressure really I know it's you know It's not gonna do much if you would but it helps. Okay save your bearings Let imagine if you were to do that I'm not a hundred times The cold start or or more You would I bet you you would do some Damage to the bearings because it's that split second once once the car when you just crank You know everything the rotating assembly just you know rotates slowly right just by the starter But at that split second where it starts the oil pump still needs to pump the oil So it's actually for this for a split second or maybe maybe even a second up to a second I would say there is no oil until that oil that you know the oil the oil pen needs to start pumping the oil kind of kind of priming itself then it needs to pressurize the system by Circulating the oil right throughout all the engine and then until and until it starts dripping from the top You know, I bet it takes a few you know some time, you know second to maybe even three I don't know but it happens so fast the crank will spin a few times at least 20 times 10 20 30 times maybe I don't know and During those Dry spins you may scratch the surfaces of the bearings So find out what you need to do to your to your car so it won't start Disconnect. Let's see some of the things you can do Pull the plug on a crank sensor if it's accessible pull a ignition fuse Pull a fuel pump relay or fuels if you do if you kill fuel it still may start actually so maybe test that Before you try it. Yeah, I'd say crank sensor and ignition sensor There's probably the way to go If you know a better way type in the comments. All right, so now I'm going to show you a short video of my 06 STI building up oil pressure After it has been sitting for about eight months Not a single start during those eight months. Just sat in the garage all cold and lonely You know, you'll notice something it takes as long as priming a brand new build engine All right, check it out and I'll see you next time all right cranking for the first time in eight months or so watch how long it takes for this thing to Disappear Building up oil pressure building good took a while, huh?