Hi, I'm Jennifer. In this video, I'll show you how to use filters to find and access information you've saved. By using the filtering option, you'll be able to find the information you need faster. Any filtering you do will only apply to the archive you've selected and will only apply to you as a user. Let me give you an example. Let's filter out all the sales proposals stored against Abigail Hart's name. This is the company card for BridgeCom, the company that Abigail works for. Start by opening the Activities archive. Here, you'll find all the documents, activities, and emails saved for this company. To enable the filter, click on the Settings icon on the right-hand side, or you can right-click on any of the columns. Either way, a new dialog box will appear. At the top, you will see options to enable grouping and filters. Check the box to enable filtering, then press OK. You'll see that all the columns in the Activities archive now have a funnel icon visible. Let's filter out all the activities and documents registered by Abigail first. Click on the funnel icon on the column, Contact. A menu will appear showing you a list of all people registered as a contact on this company card. To find the person you're looking for, you can use the search field at the top of the dialog, or you can scroll through the list and select the contacts you want. We'll select Abigail and then press Filter. The Activities archive now only shows the activities and documents registered to Abigail. Next, we'll use a second filter so we can find the sales proposal saved under Abigail's name. Click on the funnel icon on the column type. Then you can search for the sales proposal or find it in the list and then click Filter. Super Office CRM now shows you all the sales proposals connected to Abigail. To remove the filters, simply click the funnel icons again and press Clear. We have now shown you how to filter information from your archives in Super Office CRM. Thank you for watching. For more information on how to improve your productivity with Super Office, please visit our community website.


Good afternoon. I will be talking about something completely different today. This slide is for computational biologists in the audience who usually look at raw digital data. This is what the raw analog data look like when you put it into your computer. If you then slice this tumor, this is what you get. You get something that is very complex. It has a number of different cell types that you can see here. Some of these are tumor cells. Some of these are stromal cells that have lots of fat, blood vessels, lots of collagen, lots of extracellular matrix. All this complexity goes into your analysis. I remember when we were first deciding what kind of tumor should we put in, we decided for varying cancer that it should be at least 80% of tumor content of cancer malignant cell content in this tumor. But it was actually difficult to find tumors with 80% tumor cell content, and that should tell us something that tells us that the majority of tumors actually have other stuff in there. This other stuff is what I will be talking about, and hopefully I will convince you that this other stuff is also very important, and we have been neglecting it to some extent in the TCGA analysis. But maybe it requires the cancer-associated analysis. This is a section through a tumor, and you can see the cancer cells here in pink. You can see also that it is surrounded by some sort of fibrotic stuff. This is the stroma that is usually present, and the question is, what is stroma really doing in tumors? Some people believe it's actually preventing from cancer progression. It's kind of encapsulating the tumor. Others would say, well, stroma actually infiltrates the tumors and, in fact, helps the progression and invasion of tumors. In fact, tumor cells can glide on top of these pink sheets, like on highways, and progress and metastasize more efficiently. One important distinction between cancer cells and stroma is that cancer cells are highly proliferative, and stroma is not. So what you see here is Ki67 is a marker of proliferation, and you can see the cancer cells are highly proliferative, but you can also see some nuclei here in this white space, and they are not stained with the marker because they are not proliferative. This is the stroma. So the cancer cells are proliferative, and this is also what is typically targeted with chemotherapy because most chemotherapies target proliferating cells. One other distinction is that, as we know, cancer cells are very genomically, genetically unstable, and this is a bit of a problem with all the chemotherapies that we are applying because of their flexibility and genomic instability. They quickly re-adapt and start using different pathways. This is not the case with stroma. Stroma is slow proliferating. It is not directly targeted by chemotherapy, although indirectly often crumbles with the tumors. It's genetically stable, and what is important, one thing about being genetically stable, then actually we may use it to our advantage when it's targeted because you may expect that genetically stable cells are not capable of re-defining themselves as quickly as the cancer cells, and as I will try to convince you, they're just as important as genetic alterations in tumor progression. One thing that we noticed is that enhanced remodeling occurs in stroma during tumor progression, and there has been, in the past five to ten years, a study of the study has shown, if you compare cancers and you're trying to find on the expression level what are the genes that predict poor survival, most likely you will end up with genes that are not genes that are expressed in cancer cells, but genes that are expressed in the stroma. And why is that? Well, that tells us that there is something in the stroma that is very important and that predicts poor survival or maybe actually contributes to that poor survival. One gene that I'm specifically interested in is collagen 11a1. This is a very rare type of collagen that we found was expressed very highly in tumor. Here you can see tumor is blue, and then you can see these brown things. That's an expression of collagen 11a1 in in situ hybridization, and you can see it's kind of dispersed throughout the tumor, but when you look at the peritumoral stroma, which is also a stroma, you can see that there's very little of it, and then once you go more than one millimeter away from the tumor, you don't see any collagen 11a1. Because collagen 11a1 is not expressed in the normal stroma, it doesn't matter how much stroma you have in the tumor. What matters is that there's specific stroma subtype that expresses this collagen, and it's usually inside the tumor, but not all tumor cells, and we still don't know what is it with that stroma cell type that expresses collagen 11a1. An interesting thing about collagen 11a1 is that if you look across different cancer types and you compare normal tissue to their corresponding cancer, you will find that in most cancers, you see much higher levels of collagen 11a1 than in their corresponding normal tissues, and this is not very common, even if you look, so this is not because there's more stroma in cancer than in normal tissues. If you take a very common stroma marker, such as actually even activated stroma marker, smooth muscle acting, you don't see that, you see kind of comparable expression in normal tissues because this acting is expressed in normal tissues and in the stroma, but with collagen 11a1, you see this huge disparity, and if you look at individual cancer types, such as breast cancer, and you ask which ranked the genes that are most differentially expressed between normal breast and invasive ductal carcinoma, collagen 11a1 will be ranked as the most differentially expressed genes. In colorectal cancer, it's ranked as number three, but it gets even better, so it's not just normal and cancer, but if you look at during cancer progression, and this is an example of ductal carcinoma in situ and invasive ductal carcinoma, the difference is that ductal carcinoma in situ has a base membrane around and it's still enveloping and it has much better prognosis. Invasive ductal carcinoma, the tumor cells have already penetrated through the base membrane and this has worse prognosis. If you compare these two entities and look for genes that are differentially expressed, as I have done here with four different databases that I could find that compare these two types. Again, collagen 11a1 is one of the most differentially expressed genes during this type of progression of breast cancer. This is an example in ovarian cancer. You see that levels of collagen 11a1 are higher as you go from stages. These are different staging systems in ovarian cancer. You have stage one is the lowest stage confined to the ovary, to stage four, which is a widely metastatic disease outside the peritoneal cavity and collagen 11a1 levels rise through metastatic progression or stage progression. And even better, it actually is the highest levels of collagen 11a1 are actually during recurrence. So you see very little, this is in situ hybridization where we compared in matched patients, in this case, 10 samples. Now we have done it with 48 samples and the result is the same, that you have very little collagen 11a1 in the stroma of the primary tumor. You see a little bit of it in metastasis in the same patient. But then in the recurrences, you see a lot of collagen 11a1. So as I said, it is expressed in different cancer types. So this is now where I utilize TCGA data and I asked what genes are co-expressed with collagen 11a1. And I did that for bladder cancer, so I ranked the co-expressed genes, but their sperm and score correlation. Then I did the same for breast and for colorectal. And I did it for 12 different cancer types, all of which are adenocarcinomas. I was interested only in epithelial cancers. And you can see that some of these genes in different cancer types are actually the same genes. And I noticed that it was similar genes over and over in different cancer types. So then in all these 12 different cancers, we ranked the genes across 12 cancers by their priority score, basically. And you see that the closest across cancers is collagen 11a1, then collagen 5n1, Faberblast activating protein, and so on. The list is about, we selected a cutoff, and the list is about 190 genes or so. Then we asked, what are the top 10% genes that in bladder cancer, for example, have the top 10 priority score? And we put them in pink, then we ask the same for breast cancer, then we ask the same for cervical cancer, and so on. And when you do that sort of analysis, you find that, I don't know if you can see, but the pink, you can see most of the pink is up in the top.  So that means that these genes are very homogeneous. It's a very tight correlated set of genes. And this goes across different cancer types. We're talking about 12 different cancers with very different genetic alterations. When we did this with anti-express genes, which were not very highly correlated anyway, we didn't see this sort of association. So what is the signature now? It's a very interesting, tightly correlated signature. What does it represent? It's there in tumors. Is it a specific cell type that it represents? So as I said, tumors have many different cell types. We looked for this signature in different cell types, and we actually cannot find it in the normal cell type, as we can say, except cartilage, maybe. But really, so we don't think it's a specific cell type. We actually think it is more a process that exists in tumors and that is exacerbated during cancer progression. And that process we think is myofibroblast activation and I will not go into how we got to that. So what is myofibroblast activation? Well, fibroblast, resident fibroblast in tumors, are activated by TGF-beta growth factor. And they become myofibroblast, which are more motile, more stiff. And if that is true, we actually put this signature and asked what are the upstream, most likely upstream regulators of the signature? And TGF-beta1 actually comes up as the most likely, so that makes sense. TGF-beta1 activates these myofibroblasts. And one thing that is interesting about the fibroblast is that they produce collagen here in blue, which is kind of relaxed collagen fibers. But myofibroblast tend to produce this straight, stiff collagen fibers. And that's actually important for activation and kind of feed forward a loop of making them even more stiff and more stiff. And I won't go into the biology of that. But here, just to see if whether we can really see it in real tumors, you can see here collagen 11A1 is in brown. And you can see one of these boxes, number one. You can see the trichromes staining, which stains basically collagen and muscle. And then you can see number two, where collagen 11A is not expressed. You can see nice blue and wavy. But this is where collagen 11A1 is expressed. It's nice and straight, as we would expect. We also showed, if we all express collagen 11A1, we make the cells stiffer. Now, it's a very good gene to target because it's expressed specifically intratumorally, but not outside of tumors. But there's one little problem, and that is that it's also expressed in the cartilage and a little bit in your eye. We also show that you can target it with SHRNA, and the tumors are smaller and not as metastatic. So it would be a good target, but how do you distinguish it from cartilage? One way to distinguish it, and this is why it's such a great target, it's actually not the same one as in cartilage. So cartilage, collagen type 11 consists of three chains, three polypeptides, collagen 11A1, our friend, collagen 11A2, and collagen 2A1. Now, when we look at tumors, only collagen 11A1 is highly expressed. But the other two chains are not. That means that in tumors, collagen 11A1 must be homotrimerizing with itself, or heterotrimerizing with something else, but not with this. Because clearly, these are not upregulated. And actually what we find in this signature is that other collagen 5A1, 5A2, 3A1, and several others are highly upregulated in this signature. And what is common to those collagen? All of them have very slow processing of their N-termini. And this is a part of collagen processing that collagen needs to go through. And because of the slow processing, these N-termini kind of hang out of the fibers, and that prevents attrition of additional fibers. So you end up with these nice thin fibers as you saw. So we don't know why these fibers have to be thin, and what mechanically why is this important, and how this affects tumor progression at the moment. But what I've shown you is that collagen 11A1 is upregulated in normal tissues and levels increase during progression. The signature that we have identified is present in multiple solid cancers, regardless of cancer origin. So that means the resident's trauma is the same, or goes through the same process of fibroblast to myofibroblast activation. And it is enriched during innovation. We think it's activated by TGF beta signaling. And fibers are stiff, stretched out. But what is most important is that we think that this is also targetable. Because it does have a unique composition of collagen fibers in myofibroblast. So we think that this may be a good opportunity for therapeutic targeting. And I would like to thank my colleagues and my lab members and my sources of funding. Thank you. So, very good question, I don't know how you suspected. Yes, we have myofibroblast in scar tissue. So we did look in scar tissue wound healing in fibrosis. So it is slightly expressed in kiloids, not so much in scar tissue. And not during wound healing, not during fibrosis. To some extent you see a slight expression, but this is nowhere near what you see in cancer. So we think that unlike smooth muscle acting, which you will see or FAP, which you will see upregulated in all of these benign non-malignant processes, collagen 11A1 is not. It's tumor specific. Very good talk. I just wanted to make a comment that we studied the protein expression data in pan-cancer analysis. I presented the results last year of the symposium. And we have found what we call a new subtype, a reactive subtype, where we have seen stromal markers are elevated in the reactive subtype. This was first discovered in breast cancer. And we saw that the prognosis was very good for those patients with this particular subtype. Then we expanded it to pan-cancer and we found that for other cancers, the prognosis was poor. So the prognosis is cancer dependent, it's context dependent. One of the markers of the reactive subtypes was collagen 6. We don't have collagen 11 in the proteomic database, but I saw that collagen 6 was highly correlated with collagen 11A. So I think one of the things that we should keep an open mind about is that this may have a good prognosis and better outcome. Or it may have worse prognosis depending on the disease type. That is correct. I will just comment that for the signature that we have been studying, we found that in all of these cancers, it actually had worse prognosis. It wasn't a great predictor of worse prognosis, but it's still predicted worse prognosis. Except for lymphoma, B cell diffused lymphoma, which has been published several years ago, where this exact signature actually shows better prognosis. But we think it's because lymphoma, it's actually the cells that are present there are not replaced by cancer. So we think because this may be resident cells in the lymphoma. So I don't know for your signature, but surely we will be finding stromal signatures that are associated with better survival. And not all stroma is the same. I think this is very important to realize that what we are looking here is a small subset of stroma. This is very intriguing data. I have a question with respect to your trimeric hypothesis. I think to be more convincing, have you looked at GTX data to actually show that the differences that you see across those three strands are non-different across and for GTX data? But I think that would be sort of more... Right. GTX data doesn't have cartilage as far as I remember. So that's one problem that these genes express in normal tissues only in cartilage. So I couldn't really find them. Thank you. So our next speaker is Dr. Winyin Zong from Pfizer, who's going to tell us about integrated analysis of TCGA and how it identified targets and patient populations for antibody drug conjugates.


Hi everyone, my name is Lu Xiumin, I am now working back at hands and mainly focusing on virtualization related projects. Today I will show my topic, deep optimization of VMM live upgrade. It will be divided into five parts. First, I will introduce the background. VMM live upgrade is an efficient way to upgrade the VMM software, CUMUL and KVM for a new version without interrupting the guest. It can be used to add critical bug fixes and new features to the VMM. It is well known that service downtime of live upgrade is a major concern of cloud providers. Also, live upgrade has done much better than live migration and uses less resources. But in some cases, especially for large virtual machines, the total downtime can be as long as several seconds, which is obviously unacceptable for sensitive applications. So we take efforts to further minimize live upgrade downtime. Before that, I will introduce our basic VMM live upgrade framework. First, we will work as an expert to load a new CUMUL binary so that we can inherit any FD from the old CUMUL, including memory FD. And by this, we don't need the iterating memory copy. This picture also shows the flow path of live upgrade, which is similar to live migration. First, load a new CUMUL and do the initialization. When finished, notify the old CUMUL to suspend the guest, which is the start point of the downtime. You need to suspend it to pause the CPUs and stop the devices, and then save and load the device state in parallel in the old and new CUMUL. We will use true RAM to sync and transfer device states between old and new to optimize the downtime. Finally, the new CUMUL gets the full VM state and start up its end of the downtime. We also divide the KVM module into multiple duplicated modules, which can be loaded simultaneously. Thus, we can upgrade KVM by loading new KVM modules. The occupied KVM module will not be overrided, and then migrate VMs from the old one to the new one. In order to do the optimization, we should analyze the downtime of live upgrade first. This picture shows the breakdown of the downtime of a VM, which has 64 CPUs, 256 GB memory. One module will host the native device, and two modules will host the broad devices. The load is in the old CUMUL. Mainly consists of VM stop and VM state seed. The app is in the new CUMUL. Mainly consists of VM state load and VM start. We can see the main time costs of the host user devices stop and start respectively in VM stop and VM start. Then, device state transfer also takes some time. Then, I will introduce our optimizations. Now, we have known the hot spots, and the most direct question is, is it necessary or efficient to stop and start devices, and transfer device state by directly reusing the live migration framework? For CUMUL internal emulated devices, yes, we still needed the process, but the number of them are usually limited, and the time costs are relatively small. But for external devices, such as real host user devices, whose data pass a little VMM intervention, it is unnecessary and can be optimized. Let's take real host user devices. If decay and spdk for example, as we said before, we can inherit any fd from the old CUMUL by using no close x curve lag. So here, for real user devices, we inherit channels, specifically main channels and slave channels. And show the fds mainly kick and co-fds and inflight fds of spdk between the VMM and the real host user back end. Then, we will use them directly in the new CUMUL and escape the related init processes. After inheriting the fds, we can make VMM live upgrade transparent to rehost user back end. First, don't stop the back end in the old CUMUL, just keep it wrongly. Second, skip all set communications, such as set family table, set VMM number, address, set features, and so on. And also, some get communication, meaning get VMM base and get inflight fd. We skip these communications to the back ends in the new CUMUL. By this, the back ends are on way off in live upgrade. What's more, there are some issues worth looking. First, since the back ends are keeping wrongly and may trigger in clouds, we are co-fds even after the guest has paused. Then, the new KVM may miss in clouds, which I received and pending in the old KVM. Our solution is, simply supplement interrupts unconditional when finishing the live upgrade. Second, if the back ends crash or send a slave message to the mast, it is uncertain what CUMUL will receive the messages and across the mass. To avoid this, we limit the new CUMULs to start to listen on the slave channel only when finishing the upgrade. And if there is any back end crash or slave request, just use this upgrade. As far as I know, the slave channel is rarely used in DDK or SDK. Also, crash really well. So, this message will have little influence on the success rate. Third, since we don't upgrade the memory table during live upgrade, there will be still memory table date in the back ends. To solve it, we can still do the update, but without additional effect, such a back end will start. Or we can unmap the guest graph at a fixed and very high address optimization. And since the vertical related state in the data plane is kept in the guest and back ends, there is no need to transfer this state from the old to new. Except the data plane state request is mainly the complete state, which is much less changed during the VM lifetime. So, we can pre-transfer it before VM pause and keep track of the complete change right before the pre-transfer. So that if any change occurs, we can re-transfer the complete state after pause as before. By this, we can skip the state transfer of warehouse user devices within the downtime with high probability. Yeah, warehouse user is one important case, but our optimizations can also be applied to warehouse, warehouse, and so on in a similar manner. And even for KVM, we can add a mode, namely KVM upgrade in which we will inherit the KVMFDs and skip the related init processes in the new KVM. Thus, there is no need to sync the VCQ state from the old KVM, transfer it, and put it back to the new KVM. They can be skipped. By this, we can make KVM only live upgrade more lightweight. Go to the experiments and I will show the effects of our optimizations. First, we have compared the downtime with and without our optimizations on the swing workloads, idle, CPU strength, and FIO. In this picture, the left is a relatively small VM, which has 16 CPUs, 64 GB memory, with one module warehouse user network devices and two module warehouse user block devices. And the right is a large VM, which has 64 CPUs, 256 GB memory, with two network devices, and 10 block devices. We can see the downtime of a small VM has fallen by about 80%, and for a large VM, the downtime has fallen over 90%, dramatically dropped from about one second to only 17 microseconds. Besides, we can see that after optimization, there is almost no increase in the downtime when under the FIO workload. Compared to idle, we also measured the effect of our optimizations on packet loss. In this picture, the left is a ping result before optimizations, and the right is after optimizations. We can see that before optimizations, we were lost about 40 packages just in one upgrade, and the max latency is over 2 seconds, much higher than the wasted build-on time surely just now. And after optimization, there is no any packet loss, and latency is close to the wasted build-on time, about 19 microseconds. That's all. Thanks. If you have any questions for this topic, you can also contact me with this email. Thank you.


Good afternoon. For those who are new, I'm Dr. Theron Sherman, and in today's briefing, we will be discussing SCP-3691. There isn't any objectionable material in this document, so let's begin. Item number SCP-3691 Object Class Anomalous Correction Uncontained Special Containment Procedures All known footage of incident 3691-A has been recovered by the Foundation. Witnesses to the event have been amnesticized per standard Foundation protocol. A non-anomalous replica of SCP-3691 has been placed at the site of discovery. Description SCP-3691 is a bronze casting of Auguste Rodon's Le Pensoeur, known in English as The Thinker, which was situated in Albany, New York until June 13, 2022. The statue's creator is unknown. No records exist of the statue being commissioned or built since the city was founded, and no plaques of any kind are present on its base. SCP-3691 had been, since the time of its discovery, unable to be moved or damaged in any capacity. Although the statue was found to be physically immovable, an early hypothesis as to the nature of the anomaly was that the effect was memetic. Attempts to move the statue induced frustration in all individuals assigned to the task. This hypothesis was abandoned when no evidence of any secondary memetic properties was found. SCP-3691 displayed a significant deviation from its established anomalous effects during Incident 3691-A. Incident 3691-A On the 13th of June 2022, SCP-3691 became animate, slowly standing up to face a nearby camera installed by Foundation personnel. Footnote, the event was caught hours later as SCP-3691's monitoring had been deemed a low priority task due to its lack of activity prior to the event. The following interaction was recorded on camera. Begin log! 0 minutes, 0 seconds! SCP-3691 becomes animate! The statue stands up and looks at the camera! 1 minute, 5 seconds! SCP-3691 size! 1 minute, 10 seconds! Sorry, had to... 1 minute, 30 seconds! SCP-3691 walks away from the frame! End log! Following Incident 3691-A, SCP-3691 was reclassified as uncontained. Efforts to locate the entity are underway. Thank you for listening.  Please become a patron or visit our merch store at the link in our bio to support our work. Secure. Contain. Protect.


Welcome back to Los Angeles. Lisa Martin and Dave Nicholson here on day three of theCUBE's coverage of KubeCon and CloudNativeCon North America 21. Dave, we've had a lot of great conversations the last three days. It's been jam-packed. Yes, it has been and yes, it has been fantastic and it's been live. Did we mention that? It's been live. You're live in Los Angeles and we're very pleased to welcome one of our alumni back to the program. David Cefie is here, the CEO of Trilio. David, welcome back. It's good to see you. You're having me. It's good to be here. Isn't it great to be in person? Oh man, it's been a reunion. It has been a reunion and we've been talking about these great little, have you seen these wristbands that they have? I actually asked for two because I'm a big hugger, so. Me too, excellent. So here we are, day three of KubeCon, that's actually probably day five, our third day of coverage. You're losing track now. I'm losing track too, it's Friday. I know that, that I can tell you. You guys announced 2.5 a couple of weeks ago. Tell us what's exciting before we crack open Trilio. Sure, sure, sure. Well, it's been exciting to be here. Look, the theme of resiliency realized has been, it's right up our wheelhouse. Just signal that more people are getting into production type of environments. More people require data protection for cloud native applications, right? And this 2.5 release is an answer to what we're seeing in the market. It really is centered predominantly around ransomware protection. And for us, when we look at this, I've done a lot of work in cybersecurity, my career. And we took a hard look about a year ago around this. How do we do this, how do we participate, how do we protect and help people recover? Because recovery, that's part of the security conversation. We talk about all the other things, but recovery is just as important. And we look at everything from zero trust architecture that we provide now to adhering to NIST standards and framework. That's everything from immutability. So you can't touch the backups now, right? That's fine. To encryption, right? We'll encrypt from the application all the way to that, to the storage repository and we'll leverage key management system. So it's kind of like, you know, Bitcoin, right? You need a key to get your coin. You as an end user only have your key to your data alone and that's it. So all these things become more and more important as we adopt more cloud-native technology. And as the threat landscape changes dramatically. Oh, man, I gotta tell you, right? Every time you publish an application into another cloud, it's a new vector, right? So now I'm living in a multi-cloud world where multiple applications and my data now lives, right? So people are trying to attack backups through consoles and administrative consoles to the actual back-ups themselves. So new vectors, new problems, need new solutions. And you mentioned something. You asked the question, how do we participate? And we are here at KubeCon, a cloud-native foundation. So what about, what's your connection to the open-source community and efforts there? How do you participate in that space? Yeah, so it's a really great question because we are a closed-source solution that focuses all of our efforts on the open-source community and protecting cloud-native applications. Our roots have been protecting cloud-native applications since 2013, 2014, and with a lot of very large logos. And through time, there are open-source projects that do emerge. In this community, for example, Valero is an open-source data protection platform. For all of its goodness as a community-based project, there are also deficiencies, right? So Valero in itself focuses only on label-based applications. It doesn't really scale. It doesn't have a UI, it's really CLI-driven, which is good for some people and it's free. But if you need to really talk about an enterprise-grade platform, this is where we pick up. In our last release, we gave you the ability to capture your Valero-based backups.  That's where we really stand out. But when you're talking to customers in any industry, what are the things that you talk about in terms of really categorizing the key differentiators that really make Trilio stand out above the competition?  There's no doubt about it. A lot of the legacy folks that you do see, perhaps on the show floor, they do tuck in Valero under the covers. They can check a box or can satisfy some customer needs. Some of the pure play people that we do see out there, great solutions too. But really where we shine is, we are the most flexible, agnostic solution that there is in this market. And we've had people like Red Hat and Sousa and Verrantis, Digital Ocean and HPS Morel, and the list goes on. Certify, say Trilio is the solution of choice. And now, no matter where you are in this journey or who you're using, we have your back. So there's a lot of flexibility there. We are completely storage agnostic. We are cloud agnostic.  A lot of times, many moons ago, you may have started with just a label-based application. Then you have another department that has a new technique and they wanna use Helm. Or you may be adopting OpenShift and you're using Operators. To us, it doesn't matter. You have peace of mind. So whether you have to protect multiple departments or use an end user as one single tenant or using various techniques, we'll discover or protect and we can move forward together. So if you looked at, if you look at it from a workload basis and you look at your customers, are the workloads that you're protecting, what's the mix of what you think of as legacy, virtualized things versus containerized things? And then the other kind of follow-on to that is, are you seeing a lot of modernization and migration? Or are you seeing people leave the legacy things alone and then develop net new in sort of separate silos? Yeah, so that's a great question. And I gotta tell you, the answer varies. That's the honest answer, right? You may have a group or a CIO that says, look, our CTO says, we're moving to this new architecture. The water is great, bring your applications in. And so either it's, we're gonna lift and shift an application and then start to break it apart over time and develop microservices. Or we're gonna start net new. And it really does run the gambit. And so, as we look at for some of those people, they have peace of mind that they can bring their tier one applications in and we can recover. And for some people that say, look, I'm gonna start brand new and these are gonna be stateless applications. We've seen this story before, right? I joke around, it's kind of like the movie Groundhog's Day. You know, we started many moons ago within the open stack world and it was started with stateless too. Stateful always, always, always finds a way. But for the stateless people, we start thinking about security. I've had conversations with CISOs around the world who say, I'm going to publish a stateless application.  You know, what's happening in runtime may be completely different than what I intended. So now we give you the ability to capture that runtime state, compare the two things, identify what's changed. If you don't like what you've seen, you can take that point in time, recover it into a sandbox and forensically take it apart. You know, one of our superpowers, if you will, is our point in time backups that are all in an open format. Everyone else has proprietary schemas. So the benefit of an open format is you have the ability to leverage a lot of third-party tooling. So take a point in time, run scanners across it, re-orchestrate it. God forbid Trilio goes away. You still have access and you can recreate a point in time. So when you start thinking about compliance-heavy environments, think about telcos, right? Or financial institutions. They have to keep things for 15 years, right? Technologies change, architectures change. You can't have that lock-in until you continue to thrive. And on that front, one of the marketing terms that we hear a lot, and I want to get your opinion on this, is feature-proofing. How do you, what does it mean to you and Trilio and how do you enable that for organizations? Like you said, for the FSIs, they have to keep data for 15 years and other industries that have to keep it for maybe even longer. I mean, right, the feature-proof terminology, that's part of our mantra, actually. When I talked about a superpower being as agnostic and flexible as can be, right? As long as you adhere to standards, right? The standards that are out here, we have that agnostic play. And then, again, not just capturing an application's metadata data, but that open format, right? Giving you that open capability to unpack something so you're not, there is no vendor lock-in with us at all. So all these things play a part into future-proofing yourself. And because we live and breathe cloud-native applications, you know, it's not just Kubernetes, right? Over the course of time, it'll be other things, right? You're going to see mixed workloads too. They're going to be VM-based in the cloud and container-based in the cloud and server lists as well. But as long as you have that framework to continuously build off of, that's where we go. You know, it shouldn't matter where your application lives, right? At the end of the day, we will protect the application and its data. It can live anywhere. So conversations around multi-cloud change, we start to think and talk across cloud, right? The ability to move your application and data wherever it needs to be, too. Well, you talked about recoverability and that is the whole point of backing up Biddy. You have to be able to recover. It's something that we've seen in the last 18, 19 months. Anyone can back up data. That's right. That's right. If you can't recover it or if you can't recover it in time, we're talking like going on a business potentially. We've seen massive changes in the security landscape in the last 18, 19 months. We're in somewhere. I was looking at some cybersecurity data that showed that just in the first half of this calendar year, from January 1 to June 30, 2021, ransomware was up nearly 11X. DDoS attacks are up. We've got this remote workforce that's going to probably persist for a while. So the ability to recover data from not if we get hit by ransomware, but when we get hit by ransomware is critical. When? You're absolutely right. And to your point, anyone can back up anything. If you look at it at its highest form, we talk about point-in-time re-orchestration, right? Back up is a use case. DR is a use case, right? How do you re-orchestrate something that's complex, right? The containers, these applications in the cloud native space, they're amorphous. They're living things, right? The metadata is different from one day to the next. The data itself is different from one day to the next. So that's what's so great about Trilio. It's such an elegant solution that allows you to re-orchestrate a point in time when and where you need it. So yes, you have to be able to recover. Yes, it's not a matter of if, but when, right? And that's why recovery is part of that security conversation. You know, I've seen insurance companies, right? They want to provide insurance for ransomware. Well, you're going to have enough attacks where they don't want to provide that insurance anymore. It costs too much. The investment that you make with Trilio will save you so much more money down the road, right? Prashanta Kochavara, who's our product manager, actually gave a talk about that yesterday. And the economics are really interesting. So how has the recovery methodology who participates in that changed over time? Yeah. As we are in this world of developer operators who take on greater responsibility for infrastructure things. Yeah. Who's responsible for backup and recovery today? And how has that changed? Everyone. Everyone's responsible. So, you know, we rewind however many years, right? And it used predominantly, it's this admin that was in charge of- Backup administrator. Right.  Cloud native space in application lifecycle management is a team sport. Security is a team sport. It's a holistic approach, right? So when you think about the team that you put out on the field, whether you're DevOps, you're SRE, DevSecOps, ITOps, you're all going to have a need for point-in-time re-orchestration for various things. And the term may not be backup. Right. Something else. It may be for test dev purposes. Maybe for forensic purposes. It may be for DR, right? So I say it's a team sport and security is a holistic thing that everyone has to get on board with. Yeah, re-orchestration is exactly the right way to talk about these processes. It's not just recovery. You're rebuilding. You're rebuilding. A complex environment that's always changing. That's one of the guarantees. It's always going to be changing. Right. I can promise you that much. Can you give us, leave us with a customer example that you think really articulates the value of what Trilio delivers? Yeah, so it's interesting. I won't say who the customer is, but I'll tell you it's in the defense agency. It's a defense agency. They have developers all over the place. They need self-service capabilities for the tenants to mine their own backups. So you don't need to contact someone, right? They can build. They have one dashboard, single pane of glass or truth to manage all their Kubernetes applications and gives them that infrastructure to progress, whether you're DevOps or now you're IT ops. This group has rolled it out across the nation and they're using and they're working with very sensitive environments. So now we have their back. And what are some of the big business outcomes that they're achieving already? The big business outcomes? Well, so operational efficiencies definitely first and foremost, right? Empowering the end user with more tools, right? Because we've seen this shift left when people are talking about DevOps, right? So how do I empower them to do more? So I see that operational efficiency. The recoverability aspect, God forbid something goes wrong. How do you do that and the cost of that? And then also being native to the environment. The Trilio solution is built for Kubernetes. It is built on go. It is a stateless Kubernetes application. So you have to have seamless integration into these environments. And then going back to what I was saying before, knowing peace of mind, the credibility aspect that it is blessed by Red Hat and Sousa and Morantis and all these other folks in the field. That you can guarantee it's gonna work. Well, that helps to give your customers the confidence that they're, and that confidence might sound trivial. It's not. No. Especially when we're talking about security. It's not at all.  I have the right solution. We're gonna be able to recover when things happen. We fully trust in the solution that we're using. And we'll bring more into production faster. That helps everyone out here, too, right? It feels good, you have that credibility. You have that assurance that I can move faster and I can move into different clouds faster. And that's where we're gonna continue to put, we're gonna continue to push the envelope there. You know, coming, as we look into going forward, we're gonna come out with other capabilities that's gonna continue to differentiate ourselves from folks. We'll talk about in time the ability to propagate data across multiple clouds simultaneously. So making RTOs, look at the split, seconds and minutes. And so I hope that we can have that conversation next time we're together. Look forward to it. Because it's really exciting. Any CTA that you want to give to the audience? Any upcoming or recent webinars that you think they would be really benefit from? So I guess one thing I'd put out there is that I understand that people need to continuously learn. There is a skillset hole in this market. We understand that. And people look to us as not just a vendor, but a partner. And a lot of the questions that we do get are how do I do this or how do I do that? Engage us, ask us to consume our products is really, really easy. You can download us from the website or go to Red Hat's operator hub or go to the marketplace over at SUSE. And let's begin to begin. And we're here to help and so reach out. We want everyone to be successful. Awesome, Trilio.io. David, thank you for joining us. It's been an exciting conversation. Thanks for having me. Good to see you all. Likewise, good to see you in person. Take care. We look forward to the next time we see you and unpacking what other great things are going on on Trilio. We appreciate your time. Thank you so much. Good to be here. For David's FIE and David Nicholson, the two Davids, I'm in a sandwich. I'm Lisa Martin. You were coming to you live from Los Angeles. This is KubeCon, cloud native con North America 2021. Stick around. Our next guest joins us momentarily.


Hey guys, it's Liana and I'm here today to talk about the worst books of the year. So I was going to try to stack them up and hold them up for you to show you them, but I've gotten rid of probably half of them so I could only hold up half of them. So I decided not to hold up any because I'm lazy. So I've got six books to talk about today, which are all terrible, but I've decided to do it in the order of progressively getting worse. So they're all bad and they're all the worst books that I read this year, but we're going to go from best to worst, best of the worst because they're not good. But you know what I mean? It's going to be the least bad to the most bad. I think that's the best way to say it. So yeah, without further ado, I don't think I need to explain this. These are books that I did not like. Oh, I guess disclaimers. So you're supposed to say it's okay if you liked them, even if I didn't, which I think goes without saying.  Just means that we don't have the same taste. Okay, great. Now you probably won't be shocked by this list because for all the books on this list, I have either filmed a rant review for it, like a full one, or I have at least ranted about it in a wrap up in the month in which I read the book. So if you've all been paying attention to my channel, then you probably already know what's on this list. And you're just going to hear me say the same negative things again. Okay, okay. Six books. Let's go. Sixth on the list. So because number one would be the number one worst, right? So we're going to do six, five, four, three, two, one. Okay. So number six on the list is The Diviners by Libba Bray. This is a more recent read. Um, I, I'm already going to, I already know I'm going to struggle with explaining some of the books that are from the more closer to the beginning of this year. The Diviners is a recent read and I did not like it. Um, I did give it three stars, I think. It was a generous three because it was like, because two seemed too low, but three felt very generous. You don't know. The Diviners is a YA book that is about like supernatural paranormal psychic type stuff in 1920s New York, which sounded like a cool premise. I was excited to read it in Halloween month because it seemed like it'd be my jam. And it was really long and drawn out, quite like boring and dragging at times. The main character, the main main character was insufferable, selfish, like absolutely wretched human. I could not stand her. She was such a spoiled brat. And the author decided to use every single bit of like 1920s jargon slang throughout the book, but especially when Evie was, Evie, Evie, whatever her name was, was talking, I could not with her. And then there were some good moments and some of like, like the concept of the book I still like. I just didn't enjoy the experience of reading it. And there were bits of it where I liked what was happening, but there was just too much happening. And like, it was just all over the place and none of it was developed enough. And the characters that I did like, we didn't spend enough time with. If I just, I've heard that the next book in the series is better, but there's so many other books that I would rather read. So I've never heard anyone say anything negative about this book. So I was shocked because I've only ever heard praise. So I was like, I'm guaranteed to like this. And I was like, what? Is this the book that everyone's been reading? Because, okay, number five, right? Number five on the list is The Falconer by whoever that's by. I gave that away. I think it's Elizabeth somebody. I might be way off on that. So The Falconer is why a fantasy that's like Irish myth steampunk thing going on, which I knew about the like Irishiness. Oh wait, maybe Scottish. Is it in Scotland or Ireland? It's been a while. I read this like the last spring, I think. Is it Scotland? I don't remember. It's Celtic-ish. Anyway, yeah, the cover, it just looks like Merida with a dagger. And I was like, yeah. And then I didn't know about the steampunk thing. So when that started happening, I was like, oh, well, okay, I guess that's fine. The steampunk thing did not add to the story. In fact, the world wasn't really a steampunk world. It did feel like Victorian-ish kind of, is it Scotland? I think it's Scotland. And there was just like randomly steampunk things thrown in just for shits and giggles. They would be, it was like totally courtly society and totally everything is like how you'd expect in like historical fiction famously. Except that out of nowhere, instead of having normal tea, they would have this weird steampunk machine making tea for them. And we would just have a paragraph about that. We just like took a break from the story to talk about that contraption and then went back to the story. It's like if you're at someone's house and it's like a house party and everyone's like talking about politics and religion and all the things you're not supposed to talk about and having a good all time. And out of nowhere, the host is like, I got this curig. Can I tell you about how it works? It's got these ponds and it does this cool thing. And we've been loving it. And everyone's like, okay. So back to politics and religion. The book did that multiple times. And I was like, why is this here? This does not seem relevant. And the world isn't very steampunky in a way that like affects the plot. It's just like here and there is a gadget. I was like, why? It was very insta-lovy. There was a character that I thought I was supposed to be shipping her with. And when that started happening, I was like, oh, maybe I can do kind of like this because I was pretty bored until that happened. And then that ended up not being the character we're supposed to ship. It was this like grumpy gruff, like hates himself. Faye dude. And I was like, aren't we doing this again? Oh my God, I've seen this. And it's always cliche, but at least I've seen it done better here. I was like, are you kidding me? This really? There's no chemistry. There's nothing here between them. It's just like weirdly brooding and angsty. And you like threw those words in there and thought we would salivate. I didn't.  It literally ends on not a cliffhanger, like mid-scene, like commercial break in an action TV show when they're like about to like fall off a building or about to get stabbed or about to get shot. And then they're like cut to commercial. And like you have to wait three minutes, but then they come back to it. The book ends like that. And I was like, uh, am I missing some pages? Like I've seen cliffhangers, but this you just stop. It's just mid-action just stopped.  Forget it. I'm not reading the next book. This is terrible. So yeah, that's, that's the falconer. Next on my list is, uh, oh Clockwork Dynasty. I can't, I don't really have anything like that ranty to say about this. I read it during Booktubeathon or 48, 24 and 48 or I don't know. I did like a couple of readathons this year. And I read that during one of them. What's it booktubeathon? Maybe cause it was definitely for a challenge that was like reading a book that's like about something you'd want to do. Cause it's, that's why I originally bought it. Cause it's about like an anthropologist and it's like mixing two timelines of like 1700s Russia with present day, this like an anthropologist archaeologist person. And then I again, it's like steampunk and there's these automatons from the 1700s. And like those timelines are converging. And I was like, oh, that sounds so cool. It's like historical Russian anthropology. Like this sounds like it would be my jam. It was painfully boring honestly. And it felt like it was like trying to do something epic, but it didn't. Like I kept feeling like the author, the way that they would phrase things. It felt like this is supposed to be somehow significant and deep. And I was like, it's not. It's just boring and weird. And I just feel kind of like cold and empty reading this. Like there's no soul. It's just this, it was a really weird book. And it had nothing to do with anthropology honestly. So like the anthropology major in me was annoyed because I was just like, how dare you?  This is not what anthropologists do. So I was, yeah, I was just annoyed and just kind of empty feeling after that. So it didn't think it was that well thought out or that well built. It didn't make that much sense.  And I was like, I don't remember who wrote Clockwork Dynasty, but you shouldn't read it. So don't look it up. The next book on my list is Heart of the Fae, which I have now, despite saying that I wasn't going to film a rant review, I have like a couple of videos now where in which I have ranted and I'm about to again. So despite the fact that I have not done a rant review, because it's an indie author and I refuse to do that, to film a rant review about an indie published book. For the third time, I'm going to rant about this book. So that might be worse than just filming one review and being done. But whatever, here we go. Heart of the Fae by Emma Hamm. I read fairly recently and I knew it would be a fantasy romance. So like I knew to expect the romance and whatever. And it's the Irish mythology beauty and the beast retelling with romance. The plot made no sense. The dialogue was so weird. Like no one talks like that. And the characters would just say things that like either didn't make sense just like in the way that like people just don't talk like that. But also often didn't make sense in that like they weren't even talking about this. And all of a sudden they're bringing something else into it because the author needs the plot to develop this point. It felt like the author was writing, writing, writing and was like, oh, I haven't highlighted enough how they feel about XYZ or I haven't mentioned enough what they think about XYZ. So while I'm here, just shove that in because that's where I'm at. And you're like, wait, why are we talking about this right now? Did someone bring that up? What's happening?  And then when you reread, you're like, yikes, that's not where that goes. Let's rearrange it. That never happened. First draft got published is what it feels like because there's a lot of typos too. And oh yeah, the author several times. So I know this is not a typo several times. Use the word anyways with an S and I was like, that's not a word. That's not a word. Yikes. And then the dialogue again, the dialogue would sound weirdly modern and then also weirdly old-timey at the same time. So it depended on the word or the sentence or who was speaking and it would switch back and forth sometimes mid sentence. And I was like, what tone are we going for here? Because they would use all these extra like SAT style Shakespearean words to discuss something and sound, you know, say something with 10 words when you and I would use two. And then within the same page, they would say something weirdly casual and modern. And I was like, what, what? And then there was this whole thing about how, so the main character, she's like a healer, but her, her father, the morees of this beauty and the beast, he's actually, he owns a brothel and all of his daughters are just girls that he's collected who work in his brothel. Everyone is a prostitute except our main character because she's too special. She's a healer.   So you just do that. And like the author keeps thinking it sound like this. We're supposed to think this is like good for the women because like this is like actually a nice brothel. He treats them well and how liberated of them to like use their bodies for money if they want to. But then also like, you're definitely prostitutes and they're definitely being used by this man who just like adopted girls to be prostitutes to make money off of. And it's like trying to like have its cake and eat it too to be like, how progressive. But also like, no, like, no, this is weird. This is super weird. And I don't feel comfortable with this at all. And the way they talk about him as Papa, I'm just like, oh, but yeah. So the whole reason like our main character goes on submission is because Papa has this like these like blood beetles that she's like this illness that's going around where they live. And that's like the most interesting part of the book is this blood beetle thing. So she needs to find a cure ASAP because Papa is dying. So she makes a deal with a fairy.  If you do that, I'll give you the cure. So the dude that she has to bring back is our beast. And like, there's no chemistry between these two. And when she shows up and it's like, you got to come back with me because I said, because these people are dying. And he's like, who even are you? Like, no. And she's like, how dare he? He doesn't care about anyone except himself. He's the worst. What a beast. And I was like, you literally just showed up at his house and was like, let's go. You got to come with me to save some people you don't know.  Please leave. And I was like, why would you be surprised that he would react like this? Like, that's what I would do. Someone came to my house and was like, I know you don't know who I am, but you've got to go with me right now.  So she hangs out on the island convincing him to go. And he's almost instantly like, oh my god, something about her. She's just like, I can't stop thinking about her. And like, the two of them are in lust immediately. And I was just like, why? Why is any of this happening? So it was just like really disjointed.  Will they, won't they? And I was like, what happened to Beetle Plague? Like, isn't Papa dying? Isn't Papa dead by now? Like, you have totally forgotten about that. And then like, when the plot needed her to, she would suddenly up and remember like, you know what, there's a crisis. Like, we need to hurry up on this because I need to get back because Papa. And I was like, oh, so we do still care about that. Okay, cool. So it just, the whole thing was just a huge mess, honestly. I don't understand. I saw pretty good reviews. And like, I recently discovered Grace Draven's books, which I really like. And I've never really been into romance. So I read Grace Draven and I was like, oh, you know what, maybe I'm into romance and I didn't know it or I just wasn't reading the right stuff. So Emma Hamm's books, because they were like fantasy romance and the way the covers look, but also just what I saw, what they were about. It seemed like it would be in that vein. I was like, ooh, more like Grace Draven. I was like, good, there's a bunch of these books. Yikes, major, major yikes. The second number two on the list is y'all should know. Crater's Blade by Sebastian de Castell. I very recently posted a very long rant review about this book. And I, I mean, honestly just go watch that review because that book was a disaster. It started out out pretty decent. It's like an adventure where like, it's kind of in the vein or like, I thought it would be, and people always talk about it as being like, lies of Waklamara. And I was like, okay, so we have these like dudes who are like gallivanting and on a mission and blah, blah, blah. And it starts out that way. And then, whoa, it just falls off the rails, yikes. There's like weird coincidences, kind of terrible world building, horrible, horrible representation of women. I cannot even stress that enough. And not even bad representation of women, just strange representation of women. Like honestly, like I was, I was less offended than I was like, what the fuck?  Because I go into it at length in my other review, obviously. But there's like this weird scene where this like, prostitute is raping him to heal him and he's fine with it.  And I was like, what is even happening right now? Then like the plot, like what ends up being like the twist is like this massive coincidence that honestly paints some of the other characters as like kind of creepy and weird. And I was like, what is happening? How does this book have like mainly five star readings? Like who is reading this and why do they think this is okay? Because it wasn't okay. It wasn't like it was a good book and then it had like some problematic moments that I couldn't forgive. No, the whole thing was like, what, what, what? So yeah, if you like me, we're on the hunt for another Liza Block one more type story and had this like on your TBR is like a, that'll be one that hits that spot. It will not. It's terrible. Don't read it. Yikes, don't. And then the moment that I have all been waiting for, number one on my list, should have come as no surprise to anyone. A Court of Frost and Starlight by Sarah J. Mass. This book, I don't even understand how it exists. There's so much about it. I also have a full rant review about this that I filmed like right after it came out. It's, if you haven't heard of it or whatever, like I don't know if you've been living under a rock, but this is the novella in the Court of Thorns and Roses series that came out in May this year. It is a book about winter solstice, aka Christmas that came out in May. And it is a novella that cost as much as a normal hardback full length novel. And we were told that it's basically required reading because with this author, that's how it works. There's no novella that's just like a novella, like it becomes required reading. So this, she's finished with the Akatar trilogy, but she's still gonna write books in that universe. This was supposed to bridge the gap between those two series. I don't know what gap it was meant to be bridging because I didn't learn anything of any like plot significance in this novella. I don't understand what I was supposed to learn from this that I would need to know to enter the next book because nothing happened except shopping and fucking and more and more of both.  So we just follow our characters from the Court of Thorns and Roses series as they, after the war in A Court of Wings and Ruin, they're now just in Valaris being like war is over, so time to like hang out and buy gifts for winter solstice and Thera is a housewife now. And her biggest stress is that she's worrying about the budget of the household slash. She also has literally all of the money in the world and is like, what do I do with all this money? And then there's this whole thing about her like not being able to paint anymore because she just doesn't feel it. And then she starts painting again. Like that's a whole plot that by itself is like a whole plot. And like there's this whole thing about like the art studio that she happens upon. They're just talking about like it needs, it's like being sold or like it's in disrepair because like the people like lost all their money in the war and she's like, oh that's so sad. And I was like, you have all the money.  Make a donation. I don't know. Do something about it instead of being like, oh no. Like I was like, you're the queen or whatever.  Do something about it. And meanwhile, Reese and her are fucking, everybody else is like making eyes at each other. The smut scenes were like vomit. Just, oh my god, so gross. And not just gross because like I'm not into like a lot of smut in books. But this was just weird and gross and honestly really troubling in terms of like consent and like male female power dynamics. And like it just like made my skin crawl to read. Like I was like halfway between like laughing and throwing up because I was like, this is like hilarious. That this was published. What were they thinking?  It's disgusting. So it was a dumb book that had no purpose and cost a lot of money. And we'll step out some fancy pretty people shopping and fucking. I don't know why in exams. It's like honestly upsets me. That it exists. I got rid of my copies because I had two copies. Huh, why, why? Anyway, those are the worst books I've read this year. Let me know in the comments down below if you read any of the books that I listed how you felt about them. If you were considering reading any of the books that I just listed and I have now talked to you out of it because Lord I hope I did. If you've read the books on this list and you thought they were good feel free to let me know that too because sure, why not? We can talk about it. You can tell me why I'm wrong. I would love to know what I was missing when I read these books. So yeah, let me know anything and everything in the comments down below and I'll see you in my next video. Bye.


do you know who that is? do you know who it is? listen listen to dad yeah what he's got his own show now yeah that's Uncle Daryn this is almost as good as yeah let's keep watching


Hi everyone, Joe for jasperjakeswakes.com coming at you with a quick little mini promo here. We just loaded up a random number block for NT Football, the 2019 edition, and I said, hey, listen, first four spots that get taken, we're going to randomize those names, I already pulled the spot out, we're going to randomize those names, give away an extra spot, so big thanks to Brett, Eric, and Brian for doing that. New dice, new list, name on top after, it's going to be very quick, name on top after nine, five and a four, nine times, we'll get an extra spot. One, two, three, four, five, six, seven, eight, and ninth and final time. There you go, Brett had the odds on his side, Brett, an extra spot for you after nine, thank you very much. We'll see you in the break a little bit later tonight, bye bye.


Hey, you want to talk about custom IP prefixes, you want to talk about private endpoints, and you want to learn some more about DNS in an hybrid situation, stay with us on Wired for Hybrid. Hey everybody, Michael Bender here, and happy to be here in Wired for Hybrid. I am a senior content developer at Microsoft in Azure Networking, and I'm here with my good friend Pierre Roman. Hey Pierre. How are you doing? I'm good. Hey, we're doing this show. What is this about? This is something that I think a lot of our audience is really going to get into this. You can go places and find out what's new and what's happening, but where are you going to get you and me together on the big screen talking about Azure Networking and bringing our decades, I age myself, of experience on-prem, in the Cloud, in a hybrid. We're going to bring you what's new in Azure Networking. We're also probably going to work in some deep dives into some cool new tech that we see coming in 2023. Some special edition episodes. Special edition episodes. Definitely stay tuned. We're planning on doing this on a monthly rotation with what's new and then throw some other things out there. That's what we're looking at. What do you think Pierre? Sound like fun? I think that's great. Distilled to like a 15-ish minute. What's new in the last month with Azure Networking? That's a fantastic idea, Michael. I'm on board. Awesome. Hey, we don't want to waste your time, so let's get to it. Pierre, what is new in Azure Networking from Ignite? This one is new and not new. Does that make sense? It was GA, but now it's GA for every region, including the US government regions. For anybody in North America, it's fairly important. It's the custom IP prefix or bring your own IP, now available to all regions and including the US government regions.  Typically, these are for highly secured environments where who you're connecting to, that address cannot change. But if you decide to move that workload to the Cloud, either you have to route it internally or you can bring your own IP into Azure. In this case, it goes through a onboarding process where we start broadcasting your own IP addresses for you so that you don't have to change any DNS settings at your end at all because it's the same IP address, it's just being hosted somewhere else. You don't have to worry about maintaining your IP reputation. So if you're in a company that does mailing lists, if you're MailChimp, for example, I'm not sure if they're doing it the war, where they're doing it from. But a company like that, you don't want to have to get blackballed for some reason because that IP address is suddenly a brand new IP address that's flooding email systems everywhere. So you don't have to do anything like that because it maintains your IP reputation. All of our B2B partners, your business-to-business business-to-wherever, that have rules to allow traffic coming from your IP addresses, none of these have to change because your IP has not changed. So it's a great way of having your IP range hosted in Azure while you maintain ownership of it but you don't have to worry about routing it through your network, through an express route, for example, into your Azure system. Very cool. So this is truly that next step to making your hybrid environment seamless. Not that there aren't little seams there, but this really is that next step to, you know, okay, is this live or is this Memorex? You know, is this in your data center or is this in the cloud? That this changes that for those outside things. So this sounds really cool. So this works for IPv6 too, right? That's correct. So IPv4 and IPv6, the only kind of prerequisite is that you must own and have those IP address or that range registered with Aaron or RIPE online. And so if you're using an ISPs address or anything like that, don't even try it, it's not going to work.  Very cool. Very cool. How about you? Do you have something new for us? Yeah, I've got a couple of things. So we've got a couple of things around private endpoints that have come around for the customization of properties. So, you know, just kind of really to bring up people up to speed, you know, what a private endpoint is, it's that net, it basically creates a private network interface using a private IP address inside of your virtual network. So it allows you to connect privately and securely to your Azure workload. So it allows you to basically have Azure storage or Azure SQL right inside your virtual network through an IP address. So traditionally how that would work is that you create a private endpoint and it would random, random, whatever random is, it would pick an IP address out of your range of addresses, which for many workloads that works kind of fine. But let's say you are one of those organizations where you're putting in security rules that require filtering at the IP address level. It's like, it's either this IP address or nothing's going through. If you have a private endpoint, that IP address... It's dynamic. It's dynamic. So it changes. So now you have these rules that get broken and then, you know, we all write scripts. A lot of times we have those scripts that have IP addresses in them specifically and they're not using DNS. Because of that dynamic feature, we can run into some problems. So now what we can do is we can deploy our private endpoints, putting in a static IP address from your reserved IP addresses. So this is gonna make for those instances, for those security rules, for, you know, really just think about, we've had those situations on-prem for so, so long where you need to have a static IP address. That's why DHCP has had reserved addresses and all those things since the beginning. Same thing in the cloud. We have those needs for a reserved static address. So if you have that need for a reserved static address for your private endpoints, you can now do that in Azure. The one caveat here is the only time you can set it up is when you create it. Okay, so if I've got, exactly, if I've got private endpoints right now, I'd have to basically recreate them or create new ones and then repoint my systems to that new one. Correct, correct, yeah. So there's, you can do it in the portal, you can do it in Azure CLI, you can use Azure PowerShell, so you can do it across the board. But the one thing is, you know, right now the only way to do it is at creation. So I think that's a really cool thing for, you know, lots of organizations, probably more an enterprise sort of thing, but, you know, as- I think anybody who deals with security and security rules will be on board with that. Perfect. You have another one too with private endpoints, didn't you? Yes, I did. So, one of these issues I've had over the years, and it kind of goes back to my old days when I worked for a Fortune 500 telecom and I worked on the Windows side and we had the Linux team and they named their servers Bart and Lisa and Homer. We know in Azure that a lot of our names, you know, those were pick names. I have no idea who Homer is. I know who Homer Simpson is on TV, but I have no idea in my network what Homer does. Yes. In Azure, we often have this problem where we create a resource and it auto-generates a name. So like with private endpoint, when you create a private endpoint, it creates a name, Microsoft.privateendpoint-guid. Oh yeah, that's very easy to remember. Yep. And, you know, the challenge for, I think for everybody is as your environments start to scale, you're gonna have hundreds of these and when you're trying to find a resource and it goes by a GUID, you know, that's keystrokes, that's time. And so now what you do- And it leads to error because nobody can remember a 32 character GUID. Exactly. Exactly. Now with private endpoints, we can create a custom network interface name during the creation of the private endpoint. So what's interesting here is this is it's called you rename the private endpoint, but you're renaming it while you're creating it. So you can do it with Azure CLI and Azure PowerShell right now. So instead of having that long thing, Microsoft.privateendpoint-guid, let's say I wanted to be my web app PE-VNet01. So when I see that, I know that, oh, hey, this is the private endpoint for my web app, web app that's in VNet01. So from a naming convention standpoint, boom. I know exactly what that is. I can find that. You know, it's easy to go through. So there's a couple of different ways you could do it. With PowerShell, there's a specific parameter that you put in for the, when you create the private endpoint with PowerShell, it's a dash custom network interface name parameter. And then Azure CLI, very similar. And of course, Azure CLI seems to be somewhat more user friendly. It's dash, dash, nick, dash, name.  But I do, I do understand- It's not like you have to type this every day too. Yep. And you use tab complete. So it fills in the parameter for you. So, you know, that's the beauty. And most of this stuff is going to be automated, right? Absolutely. You're gonna have this in your- Infrastructure as code type of deal.   So, but- Those are two very, very interesting and kind of like removing splinters that we've had in our fingers for a long time kind of updates. Yep. So I'm glad to see that in GA now. Yep. It's great to see these type of things coming along because it's obvious that, you know, you and I spend a ton of time with customers over the years and, you know, even before my days of Microsoft, you know, always knowing people in the industry and, you know, a lot of times hearing the pain points and everything's not great, but things like this kind of show that, hey, we are listening to you and we are trying to make your experience better. And now that the, like you kind of lead me into this one, it's almost like we rehearsed this. The pain points and listening to our customers, it's a known fact that managing naming resolution across a hybrid environment has always been a pain. Absolutely. Like a death by a thousand cuts or death by a thousand C name records. But now this became globally available or GA right at the beginning of Ignite. And it's one of my favorite. It's the Azure DNS Private Resolver. And the way it works, the Private Resolver is an engine. It has an input queue and it has an output queue. All of your other environments, so if you've got hybrid, so on-prem, you would configure your DNS on-prem to do a conditional forwarding to the input queue of the resolver. Your private DNS zones that you may have everywhere in Azure, or if you've got another DNS zone that's hosted in a third party or another cloud that you've got all connected, all of those DNS would go to the input queue. And if the resolver can't find the address within the environment that it's got set up, it uses the output queue to go to your, whatever forwarder you set up, or your internet routes server. So it's a way without having to manage because what we used to do is spin up a couple of VMs and install a DNS on that, and then create all of our zone transfers and stuff. You don't have to worry about anything like that. It's all done with conditional forwarding type of rules or DNS rule sets in Azure to say, if it's this directory or this domain, this is the server that's hosting it. If it's this domain, this is the server that's hosting it, but it puts it all into like one umbrella as a private resolver. Makes hybrid name resolution really, really easy going forward, so it's easy to grow with it. And you don't have to worry about having to manage new instances of a DNS. So it grows with it. It's a managed service, so it has multiple instances in the background. You don't have to manage any of that. And from what I understand, I don't have the exact pricing, but it's a single price per month. So you don't have to worry about if you're going two, three, four VMs to run your DNS. You don't have that cost doesn't vary. It's like the set cost per month. So very easy or fairly easy to set up and addresses a ton of headaches when setting up hybrid name resolution. That's awesome stuff. And it kind of goes with that comment I made previously to where the bring your own IP address is helping to get to that seamless point of like your hybrid environment is just your hybrid environment. And this is that next step here. And the thing that I love the way that you put, you describe that because it took me back to my days of teaching of teaching DNS that every IT pro that works on Prem knows exactly what you're talking about and they're going to be able to do this because this is how we did this on Prem. So now they can work with Azure DNS, use private resolver and set it up the way they've set up conditional forwarding previously. I see this as being one of those, sometimes the IT pros feel kind of like left out and world in the cloud sort of thing. This is one of those things where they're bringing along their knowledge that they have to be able to put these two things together to take their organizations to hybrid. So super cool stuff. Absolutely, absolutely. And again, like you mentioned, it's where we're stopping the pain points one at a time. Hi, Michael, we want to keep this short. So next month we're going to have a new slow of what's new in Azure networking. We haven't like set up on a date but stay tuned with this channel, hit the bell to subscribe and be notified when our new episodes would come in. And Mike, we'll see you next month in the cloud. Take it easy PR, take care everybody.