Welcome to the weather forecast for the week beginning Wednesday, December 16th I'm Chief Meteorologist John Innsworth for Longmont Public Media Tuesday, December 22nd just before Christmas and a day after winter begins and when we have the closest Conjunction of Jupiter and Saturn in the southwestern sky go check out the skies over Colorado for information on that and Certain newspapers are carrying that too, but we have the first quarter moon in the evening sky So it's gonna make it very pretty Whatever snow we get Looking at drought. Well, we still have that Looking at last weeks. We have still severe drought around Longmont area and north of Denver along I-25 Going to this week. It's a little worse south of Denver A little worse in the southern part of the state. So we just need a big shift and a Fetch of moisture coming in some regular storms the entire west that is from California all over the Northern Plains Down in the West Texas. They're quite dry We did get some snow on Monday, so we have less than an inch around Longmont New snow We haven't gotten rid of the old snow So it's time to pile up a little bit on Boulder more like an inch in most locations It wasn't a big storm, but we'll take anything we can get Looking at the actual amount of precipitation liquid equivalent It was about a half inch to an inch in places in the mountains great news up there out in the plains Just a tiny amount All right, so our next storm is coming in on Friday not much of a storm, but there's this trough pushing down into the west and we'll be Living with Northwest flow again, we're being the storms now, but we just don't have that moisture source Looking at the DFS ensemble notice our normal high temperature 42 our normal low temperature of 17 of flattened They are not dropping. So that's kind of nice and through this time we are Bouncing up and down inside that range for the most part we start out the live normally cool or before Christmas We get a touch of above normal We're back in the cold side of normal right around Christmas Eve Christmas day for Friday The models are in agreement that a lot of runs or an agreement that we have a period of precipitation coming in And our Christmas Eve Systems moving even Trailing into Christmas morning is looking a little better more model runs have something happened and not so this could be Depending on your definition of a white Christmas. Yeah, by Christmas. Is it quite snow on the ground or is it snow? falling on Christmas morning I Grew up in Phoenix. So if I see anything that looks remotely like snow So let's put this in motion before we get to Friday We're kind of warm with that ridge passing by the end of the week here comes that trough digging down in and That's replaced by a bit of a ridge again Going to the weekend by the beginning of the week pretty strong ridge over the state Center down here south of us. So we are warm even with Northwest flow. That's what it's keeping us in the normal range There comes our Christmas Eve System digging down in the west and see Christmas Eve and Christmas Day We're pretty coffee. There's a low passing on Christmas Day itself But the initial system will probably push the moisture out take a look at falling snow and rain So going from Thursday noon into Friday, it's not much. It's mainly in the mountains Western slopes We go into Saturday Sunday little bit of stuff up in the mountains System is coming into the Pacific Northwest by Monday Tuesday. You can see it again, it's act together up there and By Wednesday Thursday Getting Christmas Eve now. There's that little system coming down How much there was Christmas Day at second lowest passing and there's just no moisture for work there That's the solution. We need some atmospheric humidity for the next 10 days taking us up to noon time on Christmas We have snow up to a foot and places in northern mountains some of the favored Faces of mountain ranges are getting some five six eight inches of snow on the plains. It's really light and spotty That's a bolder. Maybe it's a inch between now and then Okay, the amount of precipitation is really really light on significant waters So the next seven days we bounce around a lot 40s 30s up to 50s We have a little period of snow on Friday. I might even bump up that precipitation higher than that For frequent weather updates and local news check out long mountaineater long mountaineater.com I've been chief meteorologist John is worth keep looking up


My annual holiday cookie party is my favorite day of the year and this is my guest's favorite part, the cookie decorating table Here's what you need to pull it off, bake or buy some blank sugar cookies, get tons of frosting and plenty of decorations This will show that your guests can get extra creative When they're ready to leave, have them put their cookies in a bag, put their name on it, say goodbye, roll up this paper, party's over Happy holidays


Hello, hello. Is my audio working? Hello, Filip. This is Janis. Hello, Janis. Yes, Filip. Are you presenting Piraeus? Yes. Is it from the famous Greek port, or I want to ask on the other presentation? Is it the Greek port or not? Yeah, it is named after the port in Greece, yes. Right, right, right. I was sure, I was sure. I didn't want to jump on the other meeting, but I was pretty sure that it was Piraeus. My team is from Piraeus. Oh, wow. I'm Greek. My parents are actually from Piraeus. From Piraeus, yeah. I was the only once in my life. Did you do the naming? Yeah, you know, we were looking for something with Kubernetes context and, you know, ships and containers, et cetera. Nice. I saw you come up with Piraeus. Nice, nice. And I think it also has a very long history, right? So it was already in the antique time. It's pretty ancient, the port, yes. So yeah, it has a history indeed. Good morning or good afternoon. Good afternoon, Alex. Hi, Alex. Hi, Philippe. Thank you for joining. We'll wait for a few more people to join the call and then we can start. Good morning or good afternoon. We're just waiting for a couple more people to join the call and then we'll start shortly. It's coming up to five minutes, so I think we should start. Today we have two key things on the agenda. We have two project presentations, the follow-up presentation of the Piraeus Datastore project and a presentation from Janis on the dataset lifecycle framework. So Philippe, do you want to go first? Yes, of course. Okay. Then let me share my screen. Okay. So today I will try to outline what is really the scope of the Piraeus Datastore project. And in very few words, it is an operator, a CSI driver, and at a later point in time it will be this failover control. So this is what the rest of the slides is about. And just to remind you about the context, all this Piraeus stuff is about getting the lint-store storage system connected to Kubernetes. And lint-store itself relies for storage replication on a component called dbd, which is a kernel part. Let's focus on this area. So the first thing, the operator, the Piraeus Kubernetes operator is in charge of installing all the components and also configuring them. And for every lint-store cluster, there is a lint-store controller needed. So that is just one container running in deployment. And yeah, it gets installed and configured by the operator. Then there's a satellite that needs to run on all the nodes of the cluster, also installed and configured by the operator. Then the dbd kernel module that can be brought in by the Piraeus operator, but it is in a way optional. No configuration needed. Then there is an etcd instance necessary. Well, let me put it that way. The lint-store controller can use an etcd instance and that makes a lot of sense because then all your metadata is stored within the Kubernetes cluster. So I would say this is the recommended way. If you insist to use an external SQL database, that is possible as well. Then the storage devices. Well, you have to install them. They need to be there. And if you wish, the operator will discover any not used block devices and add them to the lint-store system as available storage pools. Yeah, the CSI driver is installed, of course. The snapshot controller is optionally installed. And also the stock scheduler. And that's the stock scheduler with the patches for lint-store. And by the way, I just learned that the modifications to the stock scheduler are now, there is a merge request out for a stock upstream. Okay, so that's the operator. Hey, quick question. The operator itself, is that using one of the operator frameworks or SDKs? I think so. Is there more it's on the core? Yeah, I'm on the call. And yes, it's using the operator SDK from, yeah. Cool. And then how does an operator install kernel modules? So this is basically just a kind of an optional step in the, or one of your basically configure the init containers for the satellites. So the satellites are a demon set. And optionally, there's init containers which can pull in the kernel modules. And depending on how you configured it, it's either kernel modules that are already available on your system or one that are brought in from our side. So pre-compiled, but this is only supported for a limited set of distributions. Oh, I see. So the previous operator pulls down pre-compiled kernel modules. Are those in a repo somewhere or how does that work? Let me jump in here. So the previous operator has the option to also compile the kernel module on your box. So that only works if the worker nodes have the kernel headers locally. And then it compiles it within that init container. And then it loads it into the kernel from the init container that must run in privileged mode. Okay. And with the pre-compiled, that works for defined distributions. So for let's say, you know, the rel kernel, etc. And then it comes with all these RPMs packaged into it. Okay. Understood. And just one other question, not completely related to previous, but I see that you are installing and managing NCD. Is that based on one of the current NCD operators? Or is that your own implementation of an NCD operator? And no, that's basically just a dependency on one of the already existing operators. We looked around a bit and used the one that fit our use case. It's basically kind of the, how should I say, to have the complete package. So you only need basically the Peraeus operator to get started. That's why we included this NCD. Probably you want to later in a big installation, you have that one deployed yourself using already an operator somewhere. So you can reuse that. Got it, got it. Okay. Understood. That's helpful. Thank you. Okay. Thanks for the questions then let's move on. Yeah, so here we have a bit more description about the kernel modules. So as, as mentioned, in many cases, you want to get this DVD module loaded because that gives your storage replication. In some cases, it just ensures that the NVMeo Fabric drivers are loaded. So if you choose that your storage architecture is based on that. Yeah, I think then the lins to conversion data. I think we already I already touched that so either the, the at CD within the cluster or an external at CD or an external SQL database. In that area, we support Postgres databases and Maria, the DB, and the snapshot controller might be provided with your Kubernetes distribution and stock. We already touched on that. It's very helpful if your lins to is going to use DVD, because then it can hint to Kubernetes where to place posts that require persistent volumes in an optimized way. Right. The CSI driver is also part of the previous data store project. And currently it has these capabilities. So provisioning attaching snapshot thing resizing. It is read write once file IO mode. So the storage stack. You can also use the CD does block devices. So it by default it gives you XFS file system on top. But if you wish, you can have another file system. If you wish, you can modify the amount flags or the MKFS flags, etc. You can also give your persistent volumes in block IO mode. And that's especially interesting with cube word, of course. And although our stuff is read write once. We allow access from two nodes for a very special case for the life migration. Because during life migration KVM. Has the block device open on the source node. And already opens it on the target note before it closes it on the source node. So for that use case, we have like special case that so that we can support life migration of VMs under cube word. Yeah, interesting. Does that does that sort of maintain IO consistency? Is there some sort of IO ordering that's that's maintained between sort of the local and the remote? Is that a generic question or to the life regarding to the life migration? Which regards to the live migration sort of if a read write once block device is being accessed into places at the same time. How do you make sure that you don't have sort of out of order IO hitting the back end? Well, in in case of the life migration and KVM. It is that KVM just opens it on the target node but doesn't access it. Then it stops accessing it on the source node still has it open. Then it migrates all the memory pages. And then at some point it stops it closes it on the source node. So it KVM actually doesn't access the block device in parallel from both nodes concurrently. So that makes it easy for us. But the mechanism behind it is called the dual primary mode in dbd. And there we have full paper on that how that works. And it deals with these parallel accesses to the same block. So the problem is concurrent write accesses to the same block or the same LBA happening on two nodes. And yeah, there's a full paper on it and lots of details. But nothing we want to introduce in modern workflows. Excellent. Thank you. Okay, then I'm moving on here to my to my roadmap slide. So I think I already had it on the first slide that we plan to do this h a controller for rapid failover of stateful sets on and the persistent volumes. That is still in planning stage. We need to do some foundation work on the DVD side. We need to do some plumbing work on the lintster side. And then the, the final thing as the h a controller. So I expect that we will be there. Unless maybe September over time frame. And there is a GUI in the works. It is called Lin view. That is done by a group outside of Lin bit. And we need to look into that and probably will integrate deployment of that Lin view GUI into the operator. So just to clarify the project you're proposing to put in the sandbox is the is the period operator, right? Yes, it's the operator and the CSI driver and the future a h a controller, which doesn't exist as of today. Gotcha. Thank you. I have that here on this slide. The operator, the CSI driver, the h a control. If the Lin view GUI can also be part of that. I need to bring in that group. I don't, I cannot answer that from top of my head right now. And then the, the third item I have here in the roadmap is this. Read write many leveraging Linux kernel and NFS server and client. But that is like a, you know, a far old goal. So maybe some something we will work on in 2020. Maybe it happens. Never. I don't know. Yeah, so that is what we plan here for the future. Then what, what is the current community? How did all that come together? And it literally came together with a little bit in dark cloud. I'm talking about the idea to, to bring Lin store closer to Kubernetes. And what we created in the process so far is we have this this landing page. We have the, the operator, the CSI driver, which is all on GitHub. There's the Slack channel where we interact with the users of the stack with the account. So that, that is all part of what we would want to give to the CNCF, either sandbox or even further. Yeah. And, right, that, that also touches on how all that should go into these foundations around there. So a version of DVD is already on the Linux kernel, but we need to upgrade that. So this is already ongoing since many years. And we are right now talking about getting periods into the CNCF. And then there are first talks of getting Lin store into the solar foundation. But we are here we are in the progress of learning the details that we put it that way. Okay, that sounds, that sounds really good. So, so, Philippe, I'm not sure if you're aware, but we've, the CNCF has recently changed the sandbox application process. So, if you want to proceed with this, there is a relatively simple online form you can you can fill in to to provide details. And the TOC votes on that. I don't know if it's monthly or bi-monthly they vote on that to, to, to approve those sandbox projects. So, so I guess that should be your, your next step now. Okay. And I will find that with Google in a few clicks, right? Yeah, yeah, Amy, did I, did I represent that correctly? Maybe she's not there. Yeah, but I'll, I can send you, I can send you a link as well in an email. It's, but it should be, it should be on the main website, so the CNCF too. Okay, perfect. So yes, okay, then we will take that next step. I, my idea was I, I try to speak with the storage seek first to, to understand if there is any anything more, but yeah, then I go to the form as next step. Perfect. Thank you. Thank you very much. Thank you. Anybody else have any other questions for, for Philippe before we move on to the next presentation. Hi Alex. Oh, this is Amy just stepping back in. I stepped away. I believe I answered the question in chat as far as like where the form is. But happy to be able to take this offline. Okay. Yes, thank you. I found the link. Lovely. Excellent. Okay, carry on. Hello. Hello. Yeah, we hear you. Oh, okay. This is Alex, Jim from the cloud. I just want to mention that we just get informed that way our topic topic about previous just got to pick up by the coup con China, which is we hold virtually online on July 31, 31, sorry, 31. Cool. Cool. Thank you. Yeah, I just put a question there. Something to think about is we also have Rook, and Rook is a orchestrator of story systems. So I'm wondering if this kind of, you know, we could think about this extension of maybe they can think about maybe how work would benefit them or not. You know, it's just another idea. Well, our impression here is that that Rook is so strongly associated with Seth. That our feeling was it would be better something independent of Rook. Sure. Yeah, understand. So, so incidentally, I think that was the case in the early days of Rook, but that's no longer the case and they have support for several other storage back ends as far as I understand. So you might want to have a have another look at that if it's still interesting to you. It really depends on the storage system. But you should look at it, take a look at it if it helps. If not, then we'll just take, you know, no, doesn't damage or hurt you in any way just curious. Yeah. All right, if there are no more questions, we can move on to the next presentation. So, Janice, are you on the call? Yeah, yeah, yeah. Brilliant. So the floor is yours and presents the data set lifecycle framework. All right, very good. Thanks Alex. So let me start. Thanks for the presentation. And so the desktop. Okay. Can you see my screen. We can thank you. Yeah. So, yeah, so basically we are just to briefly introduce, we are a small team of committers from IBM Research Europe. And this is, sorry, let me, I don't know how to move that. Anyway, so yeah, I don't know how to move the zoom. Okay, so we are trying to make it somewhat easier for the data scientists and the engineers to have access to remote data sources. Currently, we have implemented connectors to S3 and benefits, but we're expanding. And from the side of the data provider, we're looking to bring a, let's say, easier way to expose data sets and provide access to their, to their end users right. And also, another bit that we're looking at is how to enforce how to make sure they have governed access to these, to these remote data sources. So one of the more technical objectives that we have, right, we are introducing the concept of data set right so we, it's a new custom research definition of course, that is actually a pointer to remote S3 or NFS data sources. So we've added the ability to look up data sets from remote catalogs like a high meta store. And at the same time, we were looking to minimum to have to introduce minimal changes to the end user workflow. So, as they, the users would be shouldn't be input and shouldn't modify their workflows in order to leverage the data sets. Now, the bit that we just finished is the transparent data casting that I will give some details in the next slide. So basically, and we want, we want to bring a pluggable interface for casting frameworks to implement in order to be supported in the framework. One of the things is that the framework itself would work without, without those plugins, but we have, we have created first plug in based on safe that we leverage root for its deployment. So we give the instructions on how to implement your own casting plugin. And this would be an on the, on the fly deployment of the cast port without, without the user realizing or the user remaining completely oblivious to the fact that this data set is provided by a cast from a casting plugin. So also imagine that if you are casting data on the local cluster, we can give hints and we're looking into this problem about the workload scheduling don't imagine the workload scheduling so imagine knowing where your data sets are cast in which notes on the Kubernetes cluster, then it would be pretty straightforward to give him to the scheduler to bring this post closure to the cast data. And of course we're looking to integrate with spark could be flowing all the ML and deep learning frameworks and so this is the overall approach that we follow. So this is the on the one side, there is a user or a data provider that creates the data set CRD right so they say is my data set with this name. And then the operator takes care of this definition and provides the pvcs or the config maps or and the config maps and cigarettes and so on so forth. And for the post to just use this data set they just need to do that right like other label which is data set dot zero and number and then dot ID, the name of the data set they created and how to use it. They could use it as a mount point or they can use it by environmental variables, you know if they're using these three API for instance, they would use the, they would get these credentials there and the connection details there. And now, the other bit is the, as I said the casting plugin so imagine that we can install a parallel some casting plugins which provide that functionality of casting the data sets and we have implemented solution that works on for S3 buckets. And in the end, as I said the co scheduling of the pods to the to the guest data sets. These are the components and how is it how it looks like so as an example flow so the user goes and creates a data set definition right so it says this my bucket this is on the cloud IBM or AWS or whatever. And this is the username password for the for the bucket, then the data set operator watches the creation of these data sets and creates the necessary pbcs for the corresponding data set. Now when they go and create their pods with the labels we have created an admission controller that basically just says okay, you have annotated us using a data set. We're going to do a look up and then you will have your pod completely transparently using this data set pbc with only that addition right only with just adding a label on the pod. This is now how the transparent casting works right so yeah. Yeah, sorry to interrupt you if we could go back one slide. I'm missing a step as in sort of, is there is there a data plane or some sort of tool that you're using to create a PVC from from the S3 buckets. Yeah, so basically the data set operator right we we leverages the corresponding CSI plugins. So basically the data set operator looks for data sets. And reacts to the creation of data set objects right so this is of type S3 right so the data set operator realize that it's an S3 base so it creates a CSI PVC out of S3 right so it's a data set operator that creates the let's say the native Kubernetes components. And from from this data set so basically we have it requires to have installed the as part of the framework, we are installing let's say the CSI S3 and the CSI NFS. And to be working can do this lifting of creating actually the pbcs right the data set operator is just one level above a matching you know the data set type to the correct storage class of CSI. Does it make sense. Okay. Yeah, the data set operator is the orchestrator let's say, in this in your question right. So, the, this is a core framework right so this is our core framework and I'm going to show how the transparent counseling works right so the user goes and declares the data set right so within within the data set operators the data set controller makes a check and says, is there any plugin available in the cluster. No. So, basically, I'm going to create a shadow object that we call it data set internal, which has the same credential same endpoint with the original data set. So it goes back to the data set internal controller, which receives the definition and create the native components right so it creates the pbcs the conform maps the secrets, based on the type of the data data set, right. Now, if there is. Sorry, I don't know how to move this bit right, but so in the case that there is a data set available. The data set controller delegates the creation of the data set internal to the plugin. It passes these details and says, you know, you should take care of that, the definition of the data set, but in the end just give me the data set internal that I should create so the this plugin. So in our case, Chef, you know provisions provisions, Chef by a rook, and it creates a data set internal at the end, and then it gets handled by the core framework again so it goes back to the data set internal controller, and it creates again the corresponding pbcs from the S3 and FS. So, yeah, so we're integrating with various open source projects as well as I said before. Yeah, we have a public GitHub repo for you to have a look. And if you don't have questions, I can give a very short demo to show how this works so you can tell me if we should go with a demo or have any questions. Yeah. Yeah, my question is that, you know, I, I've seen a lot of use cases, but this was new to me. So I think there was some, maybe I would have for me, maybe for others, it would be nice to see a lot of the wise. So there's a lot of maybe assumption of the why you need that information, and that flow. I don't, I, I'm not familiar enough with the use case to understand that flow. So, maybe another time, I don't know, or maybe just an email, whatever. Just a little blurb on the why the pipeline works that way. So why, you mean some reasoning a bit on the, on the, on this flow, or what's the use case in general. Yeah, what is the user expecting out of this, like, you know, the ingestion, the workflow, what is the expectation from the user I'm not. Maybe others are, but I, I've, I've been around for a long time, but I've never seen this type of workflow. So it's new to me. I would love to learn it. Okay, so basically the, the use case that we're trying to handle is these cases right so when you have users who so currently the current landscape right so as far as we know right there is the CSI. There is the cloud object, the store and to the face that we have seen as a proposal, and it is possible to create pvcs out of, you know, S3 or NFS or some other type of data sources, but our motivation for the work was that if the user just wants to use on their pods, some data data sources without them configuring from the very beginning you know installing the plug in installing the CSI drivers and all this stuff and they just want to have a pointer to do a data set for them to work right. This is what we're trying to tackle right so a bit higher level of the CSI to give some more abstraction to the end user right so and from the flow of the framework right it's so the operators decay right. Almost all of the, as far as I know right, almost all the frameworks based on the operator SDK pattern is that they're actually just pods on the Kubernetes cluster that they are responsible. They are reacting to creation deletion and modification of a new custom resource definition that they have introduced or some native components that already are present on Kubernetes right so. Thank you. Yeah, this is David. I'm working for European by Informatics Institute. If I may confirm that from users perspective, this is exactly what we are looking for a little bit background that the EBI European by Informatics Institute is data custodian for all the public, publicly available by Informatics information, we have about the 27 petabytes of data at this point and doubles every two years. And one of the hurdles for us to move to the clouds, especially public clouds is that we have big trouble to move the data over to the clouds and it also does not make sense from economic perspective to dump the data into either Google or Amazon or whoever and the cost to store a copy of the data in the cloud is really prohibitive. So what we want to do is have this kind of data pipeline to ingest the data as we were depending on what the workload running in the cloud needs. So this is exactly what we are looking for. Thanks, thanks David. So basically, it's very much on point right so imagine that there is a provider that just gives you know disks right and the Kubernetes cluster. And there are users who want to use, as David said, the remote data sources, but at the same time. We want to optimize that by trying to bring as much as closer to the to the pods by casting it the remote. Now we're mainly working with the street but you know we have support for NFS as well. So trying to load as much of the data in the local disks where the pods are actually running and this is very common on, you know, deep learning workloads that they're keep on reusing the same data sets, right. So we want to completely make it transparent for the end users that they don't have to deal with you know configuring optimizing mounting the data sets. It's all done for them, right. So, so, so, so, so, yeah, if I could just summarize just to make sure I'm understanding this because this is actually pretty interesting. So, so effectively, you use the CRs as a catalog of data sets. And if, if a data scientist or somebody wants to run a workload in a cluster that utilizes that data set, then you either sort of orchestrates that the file system is available within that cluster, or you implement caching to to to make sure it's available in that in that cluster because the data set could be remote presumably. So, this is spot on so there are both my answer is both because on so we tried to tackle two issues right one is the usability right so as you said that the scientists would go and say capacity and get data sets on their name space and they will see the available ones.  Imagine that there could be a case where there is another persona creating the data sets for them, right. We are power users of the framework because we developed it and we create ourselves the data sets and the pods right, but in there is a case that the actor the actor creating the data sets in the cluster could be different right the data provider, and they have the credentials and they have the access and they know what they want to provide the end users, and the end users can just label their pods and use that data set mounted inside their pods right without them doing anything. So usability on one side. And now what we added with a casting is that, while the framework on its own works and does exactly that thing, right. So we bring the hooks for a casting frameworks to transparently with minimal effort as support casting in this pipeline without the user realizing it's happening at all. So the API right for for a casting plugin is that you need. It would be passed a data set, and you are responsible for creating a data set internal. So provision, you know, your services provision your post provision whatever you think needs to be provision but in the end gives us give us the data set internal and all the the other orchestration stuff happens by us so imagine the casting plugin won't have to do mounts or implement this 3F, you know, utilizes 3FS on their own. It's already part of the core framework so it tries to tackle both things right and the third step that we want to do now is the scheduling right saying if we know the data sets where our cast in the in the cluster maybe we can direct the pod to be scheduled on them on the node that has the data cast so to achieve a bit more data locality in that case. Does that answer your question. Yes, very much so thank you. That's really helpful. Thanks. So I think I might have interrupted you. No problem. You can go back to the previous diagram. I just have one question. When you create this PVC is that a it's a it's like an empty PVC you don't have any data source and was already populated. Yeah, so the cases that we are handling is so we support the rights right if you write back on this PVC it would be synchronized on the cloud right we just but the case that we're looking at more is when these data are pretty populated right so imagine that you have image net on on an S3 bucket right so when what the PVC that we create contains this bucket mounted so it would be, it would reflect the contents of the remote S3 bucket right so it's it's not empty it's it has mounted the content of the packet but if within your pod you write stuff to it it would be synchronized as it is as it is an S3 FS mount right so yeah it contains the data there. So when you provision the PVC is the dynamically provision or isn't it statically dynamically exactly so it's a it's a dynamic PVC right and we rely on the CSI S3. So there is there is a CSI plugin for S3 that we have modified a bit to suit our needs and yeah it's a dynamic PVC right yeah I can I can actually very very very quickly show you that right so this is the an example data set right so this is my image net right and I do. Okay. And if you see get data sets, you will see that it's there and that I said, in turn. The internal there you go. So we have this PVC right so it was just created Janis 17 seconds ago, and if we create not this. If we go and use that right so we want to use data set Janis as mounted. So this is optional, as I showed here so you can mount it somewhere you want to or you can leave it to the default. So we create a pod. If we go inside the pod now, give it a second to start. There you go it started. So if we go inside the pod. MNT data sets. You will see that it's the data set that creates the, it has mounted the remote, the remote S3 bucket so it's the raw data. So this is the convention that we use so inside the pod there would be an MNT data sets right. So yeah, this is this how it would look like right so, as I said we're looking to optimize the flow of the end user as much as possible right so they won't have to deal with, you know, they don't have to change the workflow at all they just need to. The only thing that they need to do from the user's perspective is to annotate their pods like this right the tool to labels. You can see a PVC definition. My PVC definition. Describe. Yeah, so basically it's, it's using this dynamic PVC right this is a dynamic PVC right so the data set object. It's like this. So you create this as an end user you give your credentials your endpoint and the bucket, the region. It's just a this is the new Kubernetes component that we're bringing right and then the orchestrator make sure to create. I think there should be the secrets there. So it created a secret with with the credentials. So, so it created the credentials as a secret right and then it was passed to the CSIS three to provide the mounted endpoint that provide the mount point. Okay. Right. Yeah, so we actually we have a Kubernetes cosy sub project in Kubernetes 6.0 now. I think there are a lot of similarities here. Definitely should talk about and see how to collaborate here. Okay, so I will be. I think I'm scheduled for next week on the Kubernetes. Yeah, yeah, we have. Yeah, we cancel the last last week's meeting because of the holidays. Yeah. We are looking to, we're looking to apply for sandbox as well on the CNCF and as far as I know there is a full request that we need to make right Alex, please correct me if I'm wrong. I don't remember a form I remember. I remember a request that we need to have with the template right. So, the sandbox project application process has changed recently so now it's just an online form that you. Okay, okay, so I need to look at the chat that you sent. Yeah, I've just reposted the link to the form in the chat window. Yeah. Okay. That's it from me. Please reach out if you have any more questions or use case that you want to discuss but yeah that's that's our project. Yeah, thanks for for listening. Thanks. Thanks. Thanks. That was a really interesting presentation some some new use cases and well done for doing a live demo. Thanks, thanks, thanks. Thank you. Okay, then. Does, does anybody have anything else to add or any other items they'd like to cover. Alexa was just curious whether anyone has anything planned for either of the upcoming cube cons. For the sick. We have, we have an intro session shed yield for the keep coming you and and we've just been, we just got in confirmation of a slot that we got for the China session as well. Erin and I are trying to book the slots to sort of pre records that that session. Awesome. So they both, they're not live. I think I need to read up on it. The way it seems to be working is that we're pre recording the sessions. And then there will be sort of live Q&A. But yeah, the sessions are being. Think for the China virtual meeting, you're not required to be there, but everything's pre recorded. But for the European one thing you are required to be there for Q&A as well. Yeah, I guess the timing for the China time is probably tricky. I think the time is also like European time not US time. Anyway, well, let us know Alex if you need a hand preparing any of the material or doing anything else. Let us know. We'll do. Yeah, we're all I'll share the deck for comments on the on the signaling list. That's a good idea. Cool. All right. Thanks everyone. It's we've come up to time. So thanks. Thanks everyone for the presentations and look forward to meeting in a couple of weeks. Thank you. Bye bye.


Everybody Matt here for late in sports cards ripping two boxes of 2022 Bowman's Best Baseball. These are for Daniel L. Good luck Daniel Tomar Chateau nice nice. That's a green refractor Otto to 99 Brooks Lee You go Daniel solid hit start off your break Oscar Coloss blue to 150 and one yep as rookie refractor Ryan Alvarez and Seager why is your green and Jackson holiday? Bobby wit and rookie Otto rookie refractor Otto Stephen Kwan. There you go Daniel got one of these in your last break, too Nice Kwan Josh will buy his UFO in Brooks Lee And you bet Brian bubble impact I cutter and judge and Bryson stop rookie refractor Excellent shurio O'Neill Cruz Shurio and trowel This is Eddie slainard Otto Ryan Acunha purple and Raphael Devers Brooks Lee many diamonds to 299 Abrams me Wander rookie Cunha Mookie Cunha Ian Lewis Otto Ramos and Joe Ryan Kumar atomic Jackson holiday and Ella Cruz Brooks Lee and holiday adds John Kenzie Noel Otto and Luis Robert gold refractor to 50 Cunha refractor Alvarez Jose Ramirez Gavin sheets Kinsey Gore rookie atomic insert Lou Bob Freddie Freeman and Alan Serta base Otto Jeremy Pena rookie UFO Yachty die-cut and Reed Detmer's rookie refractor Christian Vickero Refractor and Royce Lewis rookie refractor All right, here comes big hit J rod rookie masterpieces and gold refractor Otto to 50 Luis Mesa Wilson Contreras purple refractor Brooks Lee many diamonds Ellie Della Cruz refractor Thomas Stephen Kwan rookie Trumar two packs left William Burgoyah Otto Mike trout UFO and footholds Jack Swinsky Joe Ryan rookie atomic refractor and Brandon Marsh rookie refractor that'll do it for your boxes. Thanks Daniel I will get these right out to you


What do you really need to do to get an internship as a college student? In this week's video, we have with us Justin Wynn, founder of Get Your Grind Up and host of the Declassified College podcast. And that's exactly what Justin specializes in helping college students get internships. So Justin, what's something that college students need to know about getting an internship that often isn't really going to be told to them in the traditional manner? Yeah, I think what most people will tell you is you just need to keep applying and if you apply, you're going to get a job. But the reality is only I believe like 85% of jobs are filled through referrals. So how do you get those referrals? It's going to be linked in and it's such an incredible platform for students, especially if you're starting from a network of zero. I was able to grow from zero all the way. Now I have about 7500 followers and I get 200,000 views on my stuff every single month. So it's been an insane platform for me. I've gotten five internships from it and you can do kind of the same. So it's all about using LinkedIn, leveraging it and networking, which a lot of times college students don't think about and that's the path to help you get powerful internships. Yeah, it's that and also this mentality switch that I had when it came to networking in general. People always talk about you need to shake as many hands as possible. I think of it from a different perspective of you need to make sure that people remember you because you can remember all the people that you want. But if that hiring manager doesn't remember your name, then it doesn't necessarily matter. You can know them all you want. But unless they can see your name, pick out your resume from that list of 200 other resumes, then it doesn't matter. And that's what is the key when it comes to networking. Awesome. Awesome. Great advice. And we have a full podcast episode with Justin that we'll link to here in the comments below the video. We hope you enjoyed this video. Please subscribe for our weekly videos and we hope that we can continue to help you engineer your own success.


A message for your safety and security from the SCP Foundation. At this time, an event known as an omega case scenario has occurred. The effects of this event are the immediate immortality of all animals, including humans. The situation is being evaluated, but it is clear humans still feel pain. May still be affected by disease. May still be injured. What is advised you? Take normal measures to protect yourself from harm. Remember you may still be injured. Remember some injuries do not heal and will now be with you forever. It is also recommended that for your mental health, you avoid burial sites for the foreseeable future. SCP Foundation. Secure, Contain, Protect.


Today, harvesting hurts the forest, is done with extremely heavy machines run on millions of liters of diesel that cuts down 20% in vain just to get access. They damage remaining trees and roots next to the path, lose vitality and grow slower. It is damaged to the ecosystem, can damage the soil permanently, release mercury that is transported to the lakes and decrease biodiversity. Due to climate change, the forest is stressed, getting more invasive species that kills the trees. This leads into dead forest. 41.1% of the U.S. living forest biomass at risk, it spreads and a dream for wildfires that last year emitted 6.5 gigatons carbon dioxide. This has to change now. Let me introduce you to air forestry. We are reinventing the forestry by moving up the harvest of trees to the air. And today we are launching our product forest system. And it consists of four subsystems and the first one is our drone. And it's 6.2 meters in diameters, this was only 5 meter tape so it's bigger than the stage. If we could bring the drone to this place, sorry, the stage is too small. The drone has a lift capacity of 400 kilos and it's optimized to fly with 200 kilos. It's well enough to handle all trees in sinning operation in the forestry. The drones consist of six arms that are manufactured of carbon fiber. It makes it ultralight and the drone have tilted rotor blades that we can have extra precision and we don't need to tilt the drone to fly in sideways as the traditional drones do. That means we can integrate with objects on the forest floor much better. And the drone flies out with our next subsystems, the harvesting tool. And thanks to computer vision, we can detect and select exactly the trees we would like to see now. And when the computer has decided, we descend the harvesting tool down to the tree top and hugs it. And then we let the gravity do the rest and release it down. And all the branches go away on the tree. Well at the bottom of the tree, we cut the tree off and lift the complete tree log out to the roadside for further transportation to the industry without touching the forest floor or other trees. And it's called really fast, so I will show you once more. It's so fantastic. Everything started at my farm where we did parallel development of the tool and the drone and we used my forest as a test facility so we can early be in the reality from day one. This is Linnea, one of our first employees, she has PhD in control system, how to land drones on boats and cars that are moving in 80 kilometers an hour. She did with us the initial test of our propeller and motor and drivetrain to verify the parameters and put them in separate parallel development of the control systems. So we are building our own control systems for the drone. We also at this stage could verify that we can half the energy consumption to move a tree from the forest to the roadside, half the energy consumption. And that was a key insight why we founded the Air Forestry. We can reduce the energy so much. It's incredible. And we started Air Forestry in 2020 and we have already attracted a top talent team of 25 persons. So I have all the competence in house today to delivering this system. Another very important insight was when we had first assembling the harvested tool and I hold it in my hand and I think for myself, 60 kilos device with sharp edges. If I release this on a tree top, the branches will fall off and that happened. And since this we also have added extra functionality and optimized the tool to have minimized friction so we will run smoothly down through the tree log. And our third subsystem is the operating environment where we are operating all drone flights from. And an important thing was also to increase the working environment for these ones in the forest to increase the safety and not be alone. And today 98% of the ones working with forest are men. So we have a woman design, the working environment, so hopefully we will have more women working in forest in the future. And the fourth subsystem is the battery solution. So with now we can bring out green electricity to the forest that are powered with solar panels and wind farms, making it 100% fossil free. So now I'm really proud to present the IR forestry system that consists of the big helicopter drone, harvesting tool, the operating station and the battery storage and battery mobile solution. And the next step for us now is to put these together and start harvesting a tree and that will be really, really soon. So stay tuned. With IR forestry, we can harvest trees, adapt, restore and stop invasive pests from spread. In any harsh and remote terrain, every storm from archipelagos to swamps to steep slope, without damaging the soil, roots or nature. Meaning we've got a more volatile and more healthy forest with better production. With IR forestry, we can complete eliminating the diesel in the forest operations, equal to 10 million tons carbon dioxide savings each year. And by removing the access route, traditional machines needs to take up in the forest. We can let more trees remain and grow, meaning the forest can store up to 200 million tons carbon dioxide extra each year by using the IR forestry systems. And now we can design the forest floor exactly how we want. So we can get more productive, more resilient and more beautiful forest. For me, for you, for everyone, to enjoy with our children and for future generation. So let's reinvent the forestry today, right here, right now, together. Thank you.


Oh, today I'm talking about minimum viable run books. The idea that you could use collaboration, automation to improve your process. So I had to ask a deep question, who am I? I'm a native, I love craft beer, love to cook, love to pay people to cook for me, expecting a baby boy in August and I work at VictorOps. So what is the topic for today and why I chose it? So it's a blend of the dev process of minimum viable product which is a process to iteratively improve as well as instant run books and kind of blending the two together into a single practice. So why, what's the purpose of it, right? It supports your team members, it mitigates confusion, reduces delays and also helps you continuously improve, but when we talk to a lot of organizations, they don't do it whatsoever. If anything, they barely have it. So when an incident occurs, it's like, oh my gosh, what the heck, what the heck is going on? What's the format? Where's the firewall? Why is this failing? What's the fix? Who's Tina Fey? And it's pandemonium all the time. So the idea is that you want to provide them with something to work with here. So you want to get started and just get focused on run books and building them out. And then this is really just to keep in mind that your start and your finish is always the same, right? You always pick up where you left off, where that last incident occurs. The idea is to just start and continue to go. So the first step is to gather all that tribal knowledge.  You're trying to rip that knowledge and get them to throw it up and put it into somewhere where we can capture it digitally. So you have Slack, you have HipChat, you have email going back and forth, anything that's text rule that allows you to copy it and at least put it somewhere. So that way you have that, what you would call a minimum viable run book in place. And once you have that collaboration, you want to convert it into action items. So yes, they may have checked the host number. So turn it into an action. Where's the service? Is Tom online? Convert it into an action item to where you can have it be something ready to go. And keep in mind about what it looks like. Always have the who is involved, what they're supposed to be doing, where should I be looking and how do I go about resolving this incident when it hits me. And be sure to put it and wrap it up in a place where it is easy to access. So what does that look like? A URL. Put it in a wiki. Call that collaboration. That's converted into actions into a link that you can send out and share. And remember, although it says run books, we want to keep away from heavy documentation. We want to keep it as lightweight as possible. And once you get it, just ship it already, right? Just send it. Send it on its way. Let it do its job. Even though it feels a little archaic, it beats having absolutely nothing in place and just let the URL do its job. So how do you let the URL kind of get there when you need it most? You got to not let it sit in the corner and put it to work. So you want to get these URLs displayed right when the alert occurs, whether it's a platform that does it for you, a webhook to an email whenever the alert hits, just having this mindset of if this alert, then this run book. And then get feedback, right? Keeping it iterative. Best way to get feedback? Ask for directions. Am I going the right way?  Go left. And then you just adjust accordingly. And then what that allows you to do is once you've adjusted, it starts to open up areas where you haven't really thought of yet and you can gather that feedback and new ideas of how to improve this run book process. So once you've already got to the point where you've adjusted the first time, just continue to do it over and over again. And understand that you will continue to iterate and reach a point where even though you have some shippable and packaged object or product or piece of value, just know that even when you think it's done, you're still sending it through that iterative process again to get it going and continuing to improve. So just keep in mind when it comes to run books, having something is absolutely better than having nothing because keep in mind that people are waking up in the middle of the night managing these alerts. So even having just a text thread, something archaic beats absolutely having nothing. So as a recap, you got super smart people. They're already collaborating. They're already doing stuff. Gather all that knowledge, convert it into some actionable items. Once you take those actionable items, put them on to wikis as a central repository if you will. Send those wikis out or send those URLs out as those alerts hit. Be sure to always be open and gathering the feedback is what you're going for and then bringing it back and improving those wikis every single time it hits. That way you know what you're doing. You won't be blocked anymore, why things are failing, what the fixes are and whether or not Tina Fey should be fixing your network or not.


I have essentially two questions. The first one is the tax side was almost completely absent from the presentation. For example, when we think about transfers, if some of the transfers to other poor people are financed out of indirect taxation on consumption goods, there are some calculations which are showing that when you look at the balance, the balance is negative. And it may be the case that poor people are paying more in terms of taxes than they are receiving in terms of transfers. So it seems to me that we cannot simply push the taxation thing aside and only focus on transfers. My other point is really about another thing which is another concept which I thought was missing, minimum wage. Which as a matter of fact, in the most Latin American country, there is a minimum wage. Now it is true that in Mexico, if I remember well, it is rather low, but in a country like Colombia, it must be something like 70% of the median income, which is one of the highest in the world. And moreover, this is legislation which is very severely controlled. So this is definitely a very important element in determining informality or formality. And this leads me to another point which is that, and I'm very much aware of that because in my country, this has been a huge, huge discussion, which is the fact that above the minimum wage, the non-wage costs, like social contributions, presumably over time at an equilibrium, will be passed on the workers. Simply because if there is enough competition on the labor market above the minimum wage, let's say after twice the minimum wage, so the issue on the side of firms, the issue is very much linked to the existence of minimum wage. And I think it is really important to take that into account and more generally to admit that there are other, there are many other determinants of formality and formality than the status of contributions. I have a question for Santiago Levy. Could you maybe elaborate a little bit more on how the universal social protection systems could incentivize people to move to formal employment and also in relation to taxes because you also mentioned the example about the reduction in payroll taxes and how that had incentivized formality. But governments can only reduce payroll tax or any other taxes until a limit because somewhere the taxes need to come from. Thank you. Thanks. Just quickly. I think it's maybe important to distinguish between employment and self-employment to remember that the bulk of the poor are really self-employed, meaning they are small farmers. And there are situations where social assistance to self-employed can be effective if it helps them build assets. In the case of Procampo, the assets were there, there was a large multiplier effect to the transfers. The bright approach is to build the assets first in such a fashion that the transfers be put to work on the assets that people accumulate. So I think we are maybe coming to be too hard on the social assistance and when we think of who the poor are, there may be more scope to use social assistance in a productive fashion providing we use them in such a fashion as the assets are being built, as the transfers are being made. First of all, I wanted to thank the participants because the challenge was already trying to gather all the information about social protection left aside trying to include taxes. So I think they did a great job. However, lots of things were left behind and I wanted to mention two. One of the first ones is related to eligibility and the use of proxy means testing. To which extent this is creating problems in order to target the poor and to which extent can we move away from it to an income test, at least in Latin America. And linked to this, nothing was mentioned about protection in the case of unemployment. So there's, in some countries, there's a presence at least of unemployment insurance. In some others, I think we still have systems of severance payments only. And if you put together this with the fact that we have proxy means testing rather than means testing for those who are not affiliated, actually there's no protection in case of unemployment. So which directions could we follow in this sense? I appreciate all the efforts in gathering data and the three presentations were very good in that sense. But I think we should perhaps go beyond coverage. I know it's hard to summarize multi-country evidence, but I think if we are, for example, you mentioned the case of Brazil, if we're reducing a very regressive social insurance program for diplomats and, or in my case, scientific researchers in Argentina, which is outrageous in international terms, is that bad? If we're reducing entitlements, if we're shifting them to cash transfers for poor children? So I think there's the issue of the budget constraint that Francois mentioned and how we're financing that. If you're expanding programs that's not sustainable and then you end up in a macroeconomic crisis, that's also not necessarily something good. So I think we should try to go beyond coverage and talk a little bit about incidents in terms of income groups, but also in terms of age. I think in Latin America, we've seen a great expansion for, you respect, other people. And we can also consider what would have been the alternative use of funds. Paul Mosley, University of Sheffield. I'm fascinated by your vicious circle of informality and poverty induced by social protection story. But maybe it oversimplifies a bit because there are other determinants of formalization and productivity apart from just social protection. So in the Latin American country, I know Best, which is Bolivia. Sure, in the sectors where informalization is increasing because of structural change, such as mining, productivity is falling there. On the other hand, there are other sectors such as construction and manufacturing where because of structural change, there is a tendency for formality and therefore productivity actually to rise. And so in spite of having been a huge expansion of social protection, productivity overall across the entire economy is actually rising. So maybe the vicious circle isn't as prevalent as you say. The title of this session was social protection and age, but I'm afraid we didn't hear too much about age. So I wonder if the panelists could give us some of the insights about what the role of age might be because we all know it's becoming fashionable also in age circles to put some more resources to the protection in its various forms. So is that a good idea as such? If that's a good idea, what should be the specific role of age? Is that the cash transfers are of course the big fat nowadays, perhaps age funding should be used more like the purposes to which our commentator was referring to. And I also wonder if we have any reason to suspect that the eight finance programs might be somehow different from the other programs, either because of the funding modalities or different funding modalities or because of the different environments they are working in. Absolutely in agreement with Francois. I mean, each country has a different situationality. The minimum wage really matters a lot in Colombia. And clearly then the incidence of social security contributions is going to change because the minimum wage implies that it can be shifted back. So that clearly is part of the story. And also to link with Paul, there are many other determinants of informality here. We have to talk about taxes. We have to talk about small tax regimes for small firms and large firms, about the size dependent tax regimes that are very, very prevalent in Latin America that are also a very important component of the fact that many firms remain small. I didn't speak about any of that because this was only on social insurance, but clearly the taxation side, the issues associated with access to credit, the issues associated with income taxation mattered importantly. And this was a way overly simplified only focusing on social insurance. So if you wanted to do this more and more fully, this is what I actually tried to do in the book, you have to look at the whole incentive structure coming not only from the social insurance part, but also have to look at the taxation part, the part associated with labor regulations, which nothing was mentioned here about severance pay and all that stuff that also affects firm level choices. On Francois's point about looking at the overall system of taxation fully in agreement, what you want to do at the end of the day is look at the incidents of the structure of consumption taxes, labor taxes, and transfers, and the net of all that. And certainly what you want to do is after you look at the net of all that, make sure that the net of all that is progressive, not that each individual component by itself but that the net of all that. As it stands today, I think that the system, I didn't speak much about that but I agree, it's not really that distributive. It's not really that distributive. I think that at most, maybe 1% of GDP is really being redistributed through all this. So that's another reason why I think the system is sort of not good. On Allen's question, I fully agree, perhaps I was misunderstood. My main query is not with social assistance or with poverty or transfers for poverty. That's not my main concern. My main concern is the dichotomy in social insurance that segments the labor market. Clearly transfers to the poor can be translated into assets, land assets like in the case of Procampo, human capital assets like in the case of Progresa, and clearly you want to build their assets, both physical assets and human capital assets. The problem that I'm focusing on is that those assets, particularly the human capital assets that you're building through the targeted poverty programs, are not getting the rate of return that they should be getting in the labor market because not the social assistance component, the social insurance component is making that difficult. So fully in agreement that we should focus on them. But we're not getting as much as we could potentially get from the building up of assets. And this is data that some study we did at the IDB, it's interesting. We've just done a 20-year longitudinal study of the first cohorts of people that benefited from Progresa. And we're asking whether the labor market outcomes of those cohorts of people that have more human capital than their elders are better. And with the exception of the people that migrated to the U.S., the answer is no. So it's a very sad story. It's a sad story that says you've invested in all these human capital assets through social assistance, but the labor market is not allowing that these assets actually produce a rate of return that should be getting. So that's my main query. And I don't want to come hard on social assistance on the country. I want to come forward. So maybe I should stop there because of... Thank you. I will pick some other questions to start with. There was a question about eligibility and moving to income tests instead of proximate tests. I'm not quite sure about that. I think that the target of the program in general terms has been working well. So that was probably one of the things that we learned in this period, was how to implement these programs, how to target these programs. About the question, Guillermo's question, if I understood his thinking about, well, we can change the architecture by other ways, by, for example, changing the benefits, and that probably would be a good idea. So I think that's where the political economy and the story of the development of social protection systems in Latin America shows the difficulties to do such things. So that I think we must take that into account when discussing these issues. And I completely agree that, first of all, that we left aside taxes and minimum wages and there were important changes, for example, in the case of Latin America, in Uruguay, in Argentina, in Brazil, increases in real minimum wages were very important. And in this period, they did not have the potential adverse effects because they were equality-enhancing and the labor market was very dynamic in this period, but it was a special context in the region. So, and I cannot comment on it, I'm sorry. Okay, my two minutes are going to be really brief. Going back to Ellen's point, our discussion, I think it's really important. Basic services, education, healthcare, housing and so on, are perhaps even much more important than transfers in cash. But this is not what we, what was the theme of the panel today, but she makes the really important point that we need to get that right too. And perhaps that is her priority. On the tax side, I think it's important, but for most low-income countries, I think we could take the basic assumption that the tax transfer system is neutral in its effects and all the kind of work that the CEQ kind of initiative with non-elastic is producing for different countries shows that tax transfer systems are roughly neutral basically because low-income countries don't have significant personal income tax. So basically if most of the taxes collected through consumption taxes and company taxation, corporate taxation is perhaps the only element that is more progressive. So perhaps neutral is what we should assume. We have here sort of points about whether we should worry about the specific way in which we do eligibility tests. I'm really not concerned so much about that. I think the key issue is the regularity with which this eligibility test is done because if you look at most low-income countries, you measure poverty at one point in time, one day in the year when you do a survey. But the numbers of people that pass through poverty in the course of one year are significantly higher. So if you have a method that identifies eligibility every two years, it's never going to do proper targeting. And I think that is the point that Martin Ravellian was doing in the morning. Perhaps we should worry much more about the regularity rather than finding methods of eligibility that can be implemented at much closer space in time. Finally, two things. On the integration of social insurance and social assistance, I am skeptical about that. I have a nice picture at home that I look at it every so often where this is in Brazil, in Brasilia in the federal government building. You have the federal police inside and you have the state police outside demonstrated against the change in pensions. And so you have two elements of the Brazilian police which is pretty fearsome, fighting against each other. The state police are breaking the windows and the federal police inside are trying to protect parliament. I think it's really hard to do this because you're going to have to reduce significantly the very generous benefits that go to social insurance. I'm skeptical about integration. I think it sounds better in terms of rules and regulations, but it's really hard in terms of the politics of it. Finally, on aid, I'm going to get into trouble here, but what is the role of international assistance in supporting social assistance? I think anything that has to do with public goods is helpful. For example, the rapid response initiative of the World Bank, which is rapidly improving the capacity in low-income countries for implementing social assistance is a very good thing. The protection to promotion initiative that provides information on the effectiveness of social assistance in low-income countries is also a very good thing because there are public goods who are learning how to do poverty. But I'm afraid a lot of the international efforts, particularly the UN, focuses on a policy bubble. I think we're at the point where it's really unhelpful, and I wish they took a vacation. Saving the world must be really tiring. Why don't you take a vacation for a bit? I think low-income countries are doing really well. Just leave things as they are. I know I'm going to get into trouble for that. Thank you.


Where should you host your Unify controller? Well, there's a few options on this. We're going to start with the easiest one. The easiest one is get yourself one of these Cloud Key Gen2s, specifically as a Gen2 plus, for a small business, for a small office, or even some home users. This is the easiest, set it and forget it. Get this device, plug it in. Easy to update, easy to maintain, and we'll easily manage your Unify setup. These are great options, but a lot of people ask, well, do you deploy them with every time you set up a Unify for a client? Well, that is the point of this video, not necessarily. If the client wants to maintain everything themselves and wants to purchase one of these and doesn't want to pay any type of monthly fees for maintenance or hosting, this is an awesome device. It sits inside your office and can plug into your network and manage all of your devices right there locally. You don't have to rely on third parties or external services. So that is a good option for people that want to do everything themselves. Next option, you could just load this on some computer that you have in your office or in your server stack, but that requires you to have the knowledge to do so and understand that you need to update and patch it, which of course is really important. But your threat surface is still minimal because it's internal, so it's less likely unless someone has a breached computer in there and they try to get lateral movement over to it, it's less likely to get breached because you're not directly publicly exposing it on the internet. I bring that up because the other option, I see a lot of people go with and it's not a bad option, is hosting it in some type of cloud service such as Azure, AWS, or digital ocean. And that's a great solution, but the onus is on you. You have to maintain that server all the time. You have to maintain its exposure to the internet and any threats that may come with it. So you gotta make sure the operating system as well as the Unify controller is always up to date because it's completely exposed to the internet. So that can be a little bit risky. One of the other options, if you want to look for a hosting is Hostify. I've done a review of this as well. Hostify is gonna be more than your digital ocean droplets. So yes, it does have a higher monthly fee, but that monthly fee goes towards them maintaining the backend. So you don't have to deal with the backend management. It's just done for you, including all of the updates. So that's not a bad way to go if you're managing a lot of sites and go, this seems like a reasonable way. I don't have time or want to deal with server updates and pushing updates. I just want someone to do it all for me. That's the niche that Hostify is. It's not a bad solution. It's a pretty good solution. They've got solid hosting platform. It does come at an expense though, because people are gonna say, I'm looking for the least expensive option. That's not gonna be Hostify, but if you're looking for a very solid set and forget it. And if you're someone who's busy doing other things in your core competency as an updating servers, think about the risk you're having of just having servers out there. And we've gotten contacted by clients who their servers were somehow crashed and we see that they hadn't been updated in sometimes two years. And we have some guesses. Sometimes it crashed. We don't think it was quite just a crash, more it was probably someone attempted to hack and broke it. That's, we've seen some weird stuff out there and it's usually always on these really old not maintained servers. Once again, all that problem comes on you. You have to maintain it if you put it in one of these droplets. That's where the Hostify solution comes in. Let's bring you over to the option that we use. So if it's a MSP client for us, we're gonna put them in our stack as part of the solution. So we set up all their wifi and we add them to our controller. The advantage to that as opposed to putting one on site with every single client is every time there's an update, we can update it once and every client and we have a lot of them in our MSP stack gets the update as well. All the firmware updates, one spot to manage. We don't have to go and try and manage all those controllers and once you start talking about the number of sites we have, that's a lot of time. If I were to run out to every single client and have to update and maintain both the underlying operating system and the controller every time there's an update versus you can host all those sites and we have quite a few of them all in one place. The other thing that does is we limit the exposure. The actual control interface is behind a VPN inside of our office. We don't publicly expose that. That's a nice advantage. So now we don't have to worry about someone trying to guess their way, logging into the Unify controller and it's just one, you know, anytime you can reduce your threat service, that's the idea for the ideal way you should do it. And by doing that, the only thing we do have to open is just a couple of ports you need for communication so the devices can phone home back to our server here. Now, the nice thing about the way Unify works is we can both import and export sites. So it's very dynamic. We prefer them to run in our controller. We have a very small fee for that. If the client says, I prefer to controller be on site at my office but we'd like you to maintain it that's gonna cost them more money. So we can actually export the sites and bring it over there but frequently it's the other way around. They just want us to take care of it for the most cost effective solution and hosting it internally gives us both the visibility and when you're searching for a client, just having them all in one list, all of our MSP clients through one dashboard, being able to jump to that one particular client, that's great. This is also why we do so much restricting around the controller and why it's not publicly exposed to the internet at all because obviously with great power comes great risk. So those are a couple of different options for hosting Unify controller. Hopefully that clarifies things of it. I mean, I didn't mention it but yes, for those of you that are going by just have one device at home. Yes, you can just run it even on your own laptop and only start it up when you need it. The controller does not need to run 100% of the time for example, to keep the wifi running or to keep your switches running. It does need to be running though to keep statistics. It does need to be running if you have a captive portal all the time. Other than that, if it shuts down or when we do updates, I can do updates in middle of the day because it does not take down our clients. And the one exception is going to be if they're running captive portal. We don't have that many clients at all that run it but the ones that do, yes, we will put a Unify controller internal. That way it doesn't have to leave externally to do the captive portal type of authentication. But we, I'm not a big fan of captive portal unless it's absolutely necessary. And frequently we find other solutions than the Unify controller for it. You can use the Unify with other captive portals or even set them up in services like PF Sense and other firewalls all have captive portals, many of them do. So you don't have to have it necessarily tied to the Unify device directly. It can be passed through in part of the network routing. So hopefully this clears things up a bit. And thanks. And thank you for making it to the end of the video. If you liked this video, please give it a thumbs up. If you'd like to see more content from the channel, hit the subscribe button and hit the bell icon. If you'd like YouTube to notify you when new videos come out. If you'd like to hire us, head over to laurancesystems.com, fill out our contact page and let us know what we can help you with and what projects you'd like us to work together on. If you want to carry on the discussion, head over to forums.laurancesystems.com where we can carry on the discussion about this video, other videos or other tech topics in general, even suggestions for new videos that are accepted right there on our forums, which are free. Also, if you'd like to help the channel in other ways, head over to our affiliate page. We have a lot of great tech offers for you. And once again, thanks for watching and see you next time.