Welcome back to Prokona Live. Jeff Frick here with theCUBE. As you know, we go out to the signals, or we go out to the events, we extract the signal from the noise, we're day two here at Prokona Live, Santa Clara Convention Center, the heart of Silicon Valley. John had to step away, so I'll be going solo on this, and we're excited to invite to theCUBE Lane Campbell, CEO and co-founder of Blackbird. Welcome to theCUBE. Thank you very much. So Blackbird is a new name I saw in my notes. What was it called before? Well, we are a merger of two companies. PalominoDB has been a long time sponsoring contributor at Prokona for about seven years, and is focused on my SQL database operations and consulting. DriveDev was an operations shop with a DevOps focus, and we decided to merge together, take everything up the stack, build a company that could operate everything with a heavy database focus. Awesome, so when did you complete the merger? Probably 30 years from now, but technically we did it in January first. Okay, very good, congratulations. Never that fun to complete all the processes behind the merger. Absolutely. But good deal, so we caught you, I guess in between two keynotes here at the show. So why don't you tell us a little bit about what you were covering earlier, and what are you going to cover in the not too distant future as soon as you get to your slides after we finish the interview? Absolutely, I'm doing a melange of Amazon Web Services talks this time, so I just finished scaling my SQL on Amazon Web Services, where I talk about both options of Amazon's RDS and EC2 opportunities, and the next session is a deep dive into RDS, so the relational database service. Okay, great, so we were just at Amazon Summit last week in San Francisco, we were at Amazon re-invent last year, we'll be at Amazon Summit New York City in a couple of months, I think July, and then of course back at re-invent in October. So clearly Amazon is changing the world, the cloud service has been completely transformative, and the enterprise is disruptive, everyone's running to catch the Andy Jassy and the team at the show just released, it's like an avalanche of feature improvements, feature improvements, as the breadth of services gets wider, the depth of the services gets deeper, and then I think they announced their 43rd consecutive price decrease at the show, so there's just relentless innovation, both in terms of the feature set as well as the pricing pressure. So how did you get involved in working on the Amazon side, and what are you seeing in the marketplace with some of your customers, and how is it transforming? Absolutely, we started with Amazon when clients were going to it, and it was obviously something we needed to support, particularly we've always been a very bespoke company, we do make sure to support our customers, but like Amazon we can't do everything, so Amazon will start with a core, and then they'll evolve based on customer need, they'll start digging out new features, new functionality, and so we did the same thing, and as more customers used Amazon, we moved to Amazon, as more customers used RDS, we started using RDS, and yeah, at this point I would say about 75% of our customers are in some sort of cloud, whether it is Amazon, Google Compute, Rackspace Cloud, and even some folks are building their own private clouds as well, and realistically that's the way it's gonna go, in a few years every piece of infrastructure will be abstracted, and this isn't a really exciting time to be part of the move towards that, as we evolve our own maturity matrix for customers to show them where they stand on the DevOps maturity matrix, being in a virtualized environment where one can evolve very agile configuration, management and infrastructure as code is crucial, and so we, at this point, we're helping a lot of our customers get to that point, we're helping a lot of our customers not need operation staff and managing everything ourselves, which is much easier in a virtual cloud environment, and also letting people know when it's not the right choice for them. So, on the Amazon side, right, they have the service, so your value add then is helping customers, is it a configuration piece? Is it how they set it up? Is it what apps are they using?  So Amazon themselves are utility, that's all they want to be, and they're not interested in running systems that sit on their environment, and so we will help customers from a strategic view deciding which virtualized environment, whether it's Amazon or something else, is the right choice. We will help them choose which of their architectural components should use an Amazon service versus their own service that they would run anywhere, and once we do that, we help people migrate to Amazon, and we can run it, the whole thing. Okay, so you help them run it operationally? Yes. And then are you guys playing an open stack as well? We do have a few customers in open stack, it's growing a little earlier, but yes, absolutely. So talk a little bit about when customers are talking about making the moves to the cloud and they want to use Amazon or they want to use a service like that. What are some of the strategic gates you walked in through and making a decision as to what should be where, what workloads should be in a public cloud, what workloads should be maybe on their own or behind the firewall or where a hybrid is more appropriate? Absolutely, and I will say that up until recently we have predominantly worked with startups who are about in their mid-level of maturity, so not as much enterprise clients who might have a much more hybridized environment. Realistically, a lot of the folks that come in don't have large operation staff, they don't, and the staff that they do have want to be working on features, right? What we call development velocity, and so we look for customers who recognize that and at this point, I don't think a virtualized environment is optional anymore, and more often than not, unless they are an enterprise or unless they have a large commitment to an existing data center, going with something like OpenStack doesn't make a lot of sense. But that being said, we do make sure with anyone that we are bringing in that we set everything up with a mitigated risk so that it is easy to get them out. Even though we've never had an issue with any specific provider for risk purposes, it makes a lot of sense to use multiple clouds or to use an on-premise and other hybrid. So if their startups are most of the applications that you're getting involved with, they're new applications that they're building as part of their startup game or whatever, I wonder if you can give any examples. So we're very much in their retail vertical and the gaming vertical. We do have a few others in healthcare, and sometimes ITs, sometimes infrastructure, but predominantly most of the verticals we work with are either retail or gaming, and in those environments, we will either be brought in for a system that has grown past. Often that's already in Amazon, but it was not architected for scale, and we will come in and help them get to that next level more often than not. We do have, of course, some greenfields. We're doing a large infrastructure change right now for a new acquisition for Shutterfly, and in that environment, we're going right to RDS and using that. So one of the potential knocks on a cloud environment or infrastructure as a service is is there a point in time where the cost of rent suddenly becomes more than it would be the cost to buy, where often for speed of implementation, getting started clearly renting a service is the easier and lower friction. Do you find that with your customers, or is Amazon able to keep up in terms of the pricing reductions where they tend to stay kind of Amazon pure as opposed to hitting kind of this breaking point where maybe we really should put in our own infrastructure and it's getting prohibitively expensive to continue to kind of rent the service. Absolutely. In RDS, there was a point where people were getting priced out of RDS, which is more expensive than the instances underneath. And at that point, we had a lot of customers coming to us asking to move. The new, I think they dropped most of their prices in RDS by 40% last week. So it's amazing, right? So it gets a lot better. Some of the larger systems can be very significant, but at this point, you can get a managed database server that is fully redundant for about $6,000 a year. And it's pretty impressive. What we will find is we'll help customers manage costs. One of the things people forget is you have a whole new component of infrastructure management in how do you, whether it's using reserved instances, spot instances, auto scaling up and auto scaling down, removing snapshots. There's so many opportunities to manage costs that people forget about and we make sure that that happens as well so that people don't get runaway bills. So to really fine tune their instance at AWS or kind of cost optimized based on, because there's a lot of choices, right? There's a lot of variables in a lot of Amazon purchase. Yes, and there are absolutely tons of ways to save money. It's essentially just another facet of automation becomes the cost management part of it. And that's one of the most amazing things of Amazon is particularly for a customer that can leverage elasticity, whether it's because of peak seasons retail during Christmas, education during semesters. Any customer that can rely on the dynamicity of Amazon can scale up, can scale down, can shift out and really pay when they need to pay and not pay when they don't. So you've been doing this for a while. From kind of a longer term perspective, right? There's a lot of new entrants into the public cloud space. Clearly, Google Compute and Cisco just announced a billion dollar initiative I think last week for their new public cloud. You've got HP cloud, Azure, there's a lot of clouds out there. But clearly it appears that Amazon's got a giant lead. I think Andy said it was their eighth year of the AWS Summit. What's your kind of perspective as a kind of a service provider looking at the market and trying to deliver value to your customers as to Amazon's position relative to everybody else kind of jumping in the game? So at this point, we predominantly work with either Amazon, Google Compute or Rockspace. And that is where we focus. We don't do a significant amount of windows so we haven't really played too much with Azure. At this point, we are predominantly working with what our customers already have. If it is completely greenfield, which it's pretty rare they'll bring in a service provider that early, we would tend to focus on a combination of those two. And that of course will depend on the strategy and the goal. We don't want to overbuild something before they actually have the revenue and the business model supporting what they need. There's a lot of options out there. Like anything, it's a matter of managing risk. And I am a CEO but I was a database administrator by trade and managing risk is core. So I will not go to a new database release in its first year and I will not go to a new cloud and probably it's first three to four years unless there's some extraordinarily compelling feature that just makes you be willing to accept huge amount of risk, right? Okay, so let's shift gears a little bit and talk about, we're here at Percona Live. Show's growing. I think as somebody said it's the 10th year of the show. Why is this an important event? What's the feeling you're getting here at the show from the community? So I started coming to these back when it was an O'Reilly show and it was the O'Reilly MySQL conference versus Percona who took it over. Open source is a huge deal and it still is extraordinarily relevant. I believe very firmly that open source technology and the access to code, the access to tech and to software and the access to open source education is what's going to help us get into the next level of the technological workforce. At this point I'm not sure. You probably know the numbers since I know you do this more than me but even in Silicon Valley there are 300,000 Latina families who don't have access to computers and internet. So any organization like Percona Live and like MySQL that is based on open source needs to be supported because that is going to be what helps a child in Kenya solve cancer, figure out cancer and get us to the next level. So that's why it come out here. We support closed source databases too but wherever possible we're going to come support an open source product. So let's shift gears again because I know you're passionate about diversity in tech and you've talked about some of the digital divide with families and people having access to the tools and then of course the education and the focus on STEM. We're big fans of women in tech and diversity in tech. All of us have, we don't have a lot of women hosts but we all have a lot of daughters. So we're pretty passionate about it and growing up here in the heart of the valley. Clearly girls need to learn how to code. So can you talk about some of the things that you get involved with to support that effort in terms of diversity in tech? Absolutely. One amazing incident actually is that Percona Live last year they did not have a code of conduct and we had a bit of an issue and some conversations had and this year Percona Live now has a code of conduct which helps women come out and feel like there's a clearly written statement that they will not be harassed, they will not be intimidated, that they are welcome and that is a huge step in and of itself and it was really an issue last year in the year 2013. There always is, there always is. It's amazing when you actually start looking at women speaking out about harassment and even abuse at conferences how it quickly devolves into them being attacked, stalked, harassed, it's pretty radical. So I was very happy that Percona took that on and got that in place. I was on the content committee for this conference and I was in the beginning, there were only about five proposals out of 400 from women and they were really very nice about helping me extend it and get out there and get more women presenting at the conference here which is great. I'm speaking at a bright role hosted data-driven women event in about a month and wherever I can, getting out there, I think that's he just invited me to code his craft to talk about that at their meetups as well and that's he's an amazing organization for bringing women into tech. Good, it seems to be getting more exposure so just a shout out for, we've got a great women in tech, playlists of women in tech that have been on theCUBE if you go to SiliconANGLE.tv, look under playlist, women in tech, I think we just looked before we came on air, we have 97 women of all roles, responsibilities, seniorities, size of companies who've been on theCUBE and you'll be joining that list shortly. Excellent. So we're big fans and it is amazing in 2014 that this is still an issue but we do see more and more at these conferences that there's often kind of a women in tech lunch track or special networking event or things to really encourage to women to be not only involved but really kind of take a leadership position. We saw that back at EMC World last year with Cheryl Sandberg as well, so that's great. So what's kind of next? You've been doing this a long time, you've been involved in this community a while, what's kind of the next big hill to take in terms of the MySQL community? Well right now for us it's DevOps and I don't know if you're familiar with it but this culture of bringing the development operations teams together as we have more infrastructure as code as we get to a point where you cannot compete if you cannot continually push code out, push change out, that's why we merged and with every customer we're working on we're pushing development velocity, getting them to have the ability to push code out as fast and as rapidly as they want and as safely as they want. We just announced today an open source toolkit for continuous delivery for databases that is starting with MySQL and we feel like that's going to be the next step. Big data of course is there. We are in the middle of ramping up a Cassandra team which is a very good addition in the data ecosystem to a relational system like MySQL and the demand for it is insane so we're very excited to have just brought on our second full-time experienced Cassandra DBA and are building that out as well. So in the clients, right, there's a lot of huge trends right now. There's kind of mobile-first, right? It was racing to get to mobile-first as a driver. There's the dev ops culture and agile software development just gets stuff out in this continual pace of improvements and bug fixes and rolling and then finally the data-first which is kind of the newer trend. Within your clients of those three things what's really the primary driver if you had to pick one of the three? I will answer that in a way that doesn't answer your question but goes further. That happens often. Excellent. Right now I believe it's dev ops. In a few years no one will know what that is anymore. It will be ubiquitous. It is an opportunity right now and then it's going to be data. At this point, we're in the cloud environment and it is the next revolution, this virtualized environment infrastructure as a utility just like the electrical and industrial revolutions but data really is it. And how to get the data in right now we're in the basics. How do you get all of that data in there? How do you keep it available? How do you manage these huge farms of data? But soon it will be about the machine learning and the continued evolution of pulling insights from it and that's what we're going to be seeing. Awesome. Well Lane thanks for coming on theCUBE. Thank you for having me. We've been here with Lane Campbell, the CEO and co-founder of Blackbird we're at Percona Live 2014 Santa Clara, California. You're watching theCUBE. We go out to the events, extract the signal from the noise, get the smartest people that we can find in the room, bring them on theCUBE, ask them the questions you'd like to ask them. So thanks for staying with us. We'll be back after this short break with our next guest.


What's up everyone it's your girl Kenzie here from Leighton Sports Cards and I'm ripping a personal for Ryan B We've got a 2021 Panini contenders football hobby. All right best of luck Ryan Here we go 2021 contenders We do have a discord we do Man it should pop up here in a second. Yeah, there's the link to our discord You just have to be a sub on twitch or a member on YouTube, I believe Here we go. I'm just a reminder Ryan. No Vet base ship out of this first hit up. We've got rookie ticket stuff 5 of 15 Jalen Phillips Here we go off to a good start here Jalen Phillips Yeah, and you know people sell cards on there I look for advice. So definitely that'd be a great place, you know to get some more information for sure rookie the year Devante Smith de hop. We have a chubba-hubba. It's gonna be the on-card rookie Otto Chuba Hubbard Murray on the MVP stray hand power players round numbers Chain movers of Randy Moss that is 43 of 99 Ricky of the year Kellen Maughan Chain movers Aaron Jones We have Raiders rookie ticket of divine Diablo Raiders MVP contenders Donald All right, so two more autos here for you, Ryan Gronk power War and moon We have Elijah Molden on the rookie ticket auto Supernatural rookie Zach Wilson six months of subs and pants. Nice KJ Ricky the year Niko Collins Chain movers CMC We have a Kylan Williams rookie ticket auto Packers MVP Herbert Oh Ryan Oh nice Yeah, I can't see that stuff unless I'm on the actual switch tab on the computer So thanks for letting me know KJ. That's awesome and Winning ticket of Russell Wilson Alrighty Ryan that will do it for your boxing singing for hopping in we'll get these cards sent right out to you


Here in this diagram, we are looking at how a basic power plant works. A power plant generates electricity, and it burns a fuel and converts first the chemical energy that is there in the fuel here to heat energy. And that heat energy or thermal energy is converted to mechanical energy over here, and mechanical energy is converted to electrical energy in this generator. So basically, a power plant is divided into three components. The first component is boiler here, which burns the fuel, coal, oil, natural gas, or any fuel, and produces the heat. The water that is going into this boiler boils and becomes the steam. This steam at high pressures and temperatures has a lot of energy, kinetic energy. And this energy basically comes into this turbine and turns this turbine wheels. And we use this high pressure steam to do that. And this high pressure steam gives up the energy here and then turns into low pressure, low temperature steam. And this when turns, this turbine when turns, this turbine is hooked up to a generator. This generator is nothing but a magnetic field. In other words, that magnetic field is created by these poles north and south, and these yellow ones are basically the magnets. And between these two poles, this electrical conductor, a copper wire, which is turned many rounds across or around the armature, turns. The two ends of this wire are hooked up to a load or to transmission line. So when this conductor is turned in a magnetic field, you get the electricity. To turn this conductor, we are using this turbine, because both of these are hooked together. Once this moves, this moves and generates the electricity. To move this turbine, we need high pressure steam. To produce this high pressure steam, we need thermal energy or a fuel called or oil or natural gas. And that's how these conversions are taking place. Now let's get to this turbine. This turbine, the high pressure steam, after turning this turbine, converts into low pressure, low temperature steam. That steam is sent to a condenser. A condenser is, this is the condenser which has cold water on the outside. When the steam is going through this cold water, this steam turns into water or condensers. That is the reason we call this condenser. And this low pressure steam that is condensed into water is put back into the boiler, which again turns into steam. And obviously when we convert or when we turn this steam into water, that energy is coming into this cooling water. And this water turns into warm water. And this warm water is again sent all the way up to this cooling tower. The purpose of this cooling tower is to cool the water that is condensing this steam. So this is simply like a shower head. Almost hundreds and thousands of shower heads at the top of an almost 10-story tall building. And when these droplets fall down, what happens is the air that is going across this or around these small droplets picks up the energy from these droplets and hot air goes out and cold water comes down. Basically, almost about 30%, 40% of the energy that we put into this device is actually dumped out into the environment, into the atmosphere through this condenser or cooling tower. That is the reason this turbine part is notoriously inefficient, and boiler part is pretty good actually. It's about 90% efficient. This is about 40% efficient. But once we turn this thermal energy into mechanical energy, conversion into electrical energy is pretty efficient, which is about roughly this generator efficiency is almost 95% efficient. And as I said, this turbine is only about 40% efficient. And this boiler is roughly about 89% to 90% efficient. So of all the three components, this is the lowest efficient or least efficient component. And this is the most efficient component with 95% efficiency. That's how a simple power plant works. One other point that I want to make is when we burn this fuel, of course, this thermal energy is going out here. That is one type of pollution. And when we burn these fuels here, the gases that are produced here are emitted through the stack. And this is where the chemical pollution or the pollutants are emitted into the atmosphere. This is of concern for all of us in a power plant.


Today, we will talk about the case study of EO4U platform and how we try to achieve the multi-cloud observability. This was a work for three individuals, but unfortunately, Lucia is not with us, so who we are? Next slide, please. I am Arman, and I am coming from ECMWF. I worked as a cloud computing engineer in ECMWF. And I have my colleague here, Francesco. Do you want to? Hi, everyone. I'm Francesco Maria Contrera. I work for Cineca, which is a night performance computing company. We have also cloud facilities, and I work mainly with the cloud. So our journey started with the EO4U project, which is an European-funded initiative for creating a platform to let people access Earth observation data. So you can search process and also visualize this data with advanced tools. It is a very large platform, so you have to also, we decided to have a complex architecture, which uses a multicubernet cluster upon two different clouds. So one is hosted on Cineca, and the other is Wikio, which is managed by different partners. One of the key partners is ECMWF. So you know that when we have a very distributed platform, you have to face many challenges. So you have to, for example, if something can go wrong, you know that it will. And so you have to face errors, faults, but you have also to allow people to, developers, for example, to debug their applications, their microservices, in a very distributed platform. So you know that observability comes in, and you know that there are some pillars like metrics, logs, and traces. And when we started our journey, we found that there are some standards, both in terms of architecture, in terms of tools that we can use in our journey. So starting with the metrics, we have, for example, in the simplest case, you can think about a single cluster case, where you can use tools like Prometheus, which is the fact of standard in retrieving metrics. And then you can use also Grafana for visualizing them in a very nice dashboard. Obviously, when you have to scale in this case, you have to consider high availability. You have to consider maybe also how to keep this data for a long time, to retrieve for doing some analytics. And also, you do not want to go to every single cluster to see the metrics separated. But you want to have a single access point to have visibility in the entire platform. So in this case, we move to the multi-cloud when we have to add another tool, which is Thanos. Thanos is extending Prometheus while keeping compatibility. So practically, it is solving all the previous issues. And while you can, for example, use in Grafana the same Prometheus data source and just point to the Thanos deployment, and it is just working. So Thanos is adding a Sidecar with the Prometheus server so that you can scale your Prometheus servers. And at the same time, it is able to upload the time series data inside an S3 storage. So you can retrieve this data when you need it. And you can keep all the other Thanos components in a separated cluster. So you can keep all the, for example, the courier, your Grafana instance, and all the other components inside an observer cluster. So you can, in a sense, ensure some high availability. For example, if one entire cluster goes down, you can continue to have visibility on the system on the entire platform. For example, a few days ago, we had some maintenance on our cloud. So some machines were not available, and we were able to see that from our dashboard. So at the same time, we can keep the data, as I said, before for a very long time. And we can add also the possibility to down sample the data for the oldest data so that we can speed up also the visualization of all data in Grafana. So obviously, there are some drawbacks in this platform. For example, the sidecars are consuming more resources. And the sidecars are uploading the data every two hours. So you have to directly query the sidecars from the courier. And to do that, we have to add another sidecars, an employee sidecar in front of the courier so that we can also encrypt the communication between those two endpoints. So this is for the metrics. And then we have the other two pillars. But for this, I want to leave the stage to my colleague. Thank you very much. And as we talk, this was the metrics. And the next pillar is the logs. And the single cluster case, we also talked about the standards. And the standard was pretty clear. It was often referred as the EFG stack with Elastic Search Fluent D and Kibana. But in our case, we just stick with the open search instead of Elastic Search and use the Fluent D as well with Fluent BitAsians. So the standards for the single cluster case was more or less clear. But moving on to the multicluster case, can you next slide, please? We had to define some standards in order to keep things tidy, because now we have an observer cluster which hosts TANOS and open search. And we have the production clusters that are sending logs to it. And in order to keep things a little bit tidy on the open search cluster itself, we came up with some index naming conventions to send specific logs to the specific indices. You can see examples on the downside. We also used some field mappers, state management, and templates based on the application types, such as, for example, Ingress Nginx. And we kind of tried to adopt a dynamic approach where we have the logging operator managing all this Fluent D and Fluent Bit and cluster flows so that when we are pushing a new cluster flow or a flow to the clusters, it will automatically propagate it to the clusters that we have so that we can see the logs on the open search itself. And obviously, we have the backups on object storage. And we also use open search as a data source in Grafana. Next slide, please. And the next pillar in our story was the traces. This was the, let's say, hardest point in order for us to understand coming from the humble beginnings. But we realized that the open telemetry gains a lot of support. And it becomes the de facto standard right now nowadays. And it also has some processors that enrich the data that are coming from. We are mostly working on Kubernetes, so this was a nice add-on. We already had some experience with Jager. But the good thing with open telemetry is that it sports broad variety of pecans. So you can actually write data to Jager. You promise to use Thanos. And these are the tools that we were using anyway. So this was a nice selection. And you can see the architecture for the single cluster case, where you have the open telemetry operator managing the open telemetry collectors as a demon set, which gets the data from the ports that are emitting tracing information, sends it to the Jager collector, where we can restore that. We can keep the data in memory. And we have the Jager courier to visualize the data and everything. And this is also managed by the Jager operator. But next slide, please. But in the multi-cluster case, this was not scaling very well. So we just said that, OK, we can deploy the Jager collector in each cluster and the open telemetry collector as well, so that we can send the tracing information to the Jager still. But we can use OpenSearch as a backend storage so that each Jager collector can write data to OpenSearch, where we have it in the observer cluster. So it fits really well. And then from there, we can still have Grafana and Jager courier so that we can add Jager as a data source in Grafana, which enables a little bit specialized dashboards and visualizations as well, so it was a nice add-on. And basically, we also set some standards there in order to keep things tidy in OpenSearch so that we can have query speed in a considerable speed. But there were some issues like multi-tenancy in Jager, which we have an open issue. You can see it in the downside, where you cannot actually write different indices. So it is a little bit less tidier than the logging itself. Next slide, please. So our journey, basically, start with the humble beginnings, as I said. And we figure out the best standards for the single cloud. And we try to apply that logic into a multi-cluster use case that we had. And we had these challenges about integrating the several tools, because we talk about OpenTelemetry, Jager, Thanos, Prometheus, FullEntD. And there is a lot of tools that you need to consider. And you need to deploy those tools. And also, there is a management phase of managing all those tools and version updates and day two operations. So this is still an open topic. Another challenge was the multi-tenancy, because it's always hard to deal with it. And we also had some issues with the documentation. There are amazing documentation out there, but there is still an effort needs to be spent there. And we actually are honored to contribute a couple of documentation available on the open source environment. And we also had some issues with the networking, like Francesco mentioned, for example, in the Thanos case. And in order to tackle them, we came up with some design principles. And we put some ground rules again. So we set open source ecosystem and open licensing so that we can plug and play this toolkit that we have. We also tried to automate everything with GitOps and infrastructure as code so that we can deploy them and must and manage them and must. And we have this Kubernetes first approach, although that we have some resources on OpenStack and as a virtual machines. And we have some kind of a way through for managing Kubernetes resources. So for example, if you have an operator, official operator for something, we start with that. If there is no operator or it's not mature enough, we go with the official hem chart. And if not, if those two are not there, we implement our custom solution only then. In order to keep things tidy and efficient to manage. And I must say, we started with GitLab CI CD and Terraform, and we tried a lot of things. But it was not agile enough for us to deploy all this. So we ended up using GitOps tools. Next slide, please. Introducing OpenObservabilityStack. So by leveraging all this open source ecosystem that is available to us, we came up with this idea of observability stack. I must say, this is not a product, but an umbrella project which has documentation, some code available that you can use so that you can both administrators and developers alike, they can build their own solutions just like us. And this is automated into multi-cloud deployment. So we also had this multi-cloud, multi-cluster case as a use case. So we tried to keep that in focus so that you can also have the same methodology that we did and apply it to the multi-cluster case that you have maybe in your use case. Next slide, please. And how we do that? By using some tool called Fleet by Rancher. It's a GitOps tool, and it has a couple of components, but I want to highlight the three of them, which is called cluster labels, cluster groups, and Fleet cluster, controller cluster. If you are using Rancher to manage club communities clusters, this Fleet controller cluster comes embedded inside, so it was a nice add-on for us, which we were using Rancher anyway, but you can install Fleet controller cluster by yourself as well. The other thing is the cluster labels, which is basically a label that you can set to the clusters so that you can build groups out of those labels. And in our case, we were using two distinct labels called observer and observerV in order to identify which clusters are the observer clusters and which clusters are the observerV clusters that needs to be observed. Next slide, please. And by adopting this logic, we actually simplified a lot of things because when we need to deploy the things from scratch, it's actually quite easy because the cluster is created with a specific label that will instruct Fleet to deploy the specific parts of the observability platform that we have. And once you build a new cluster, it will auto-enroll this cluster as an observerV if you have the label so that the newly provisioned cluster observerV will have the tools that we mentioned in the previous slides automatically. It also automates the configuration changes and the upgrades as well. So if I decide to have a new cluster flow for ingress logs or specific application logs, this will be propagated to every cluster that I have with the labels on it. So it is basically, all I need to do is to change the git object and push it as a commit. And it also ensures consistency because I don't want a cluster flow in one cluster, sending different logs than the other cluster that I have the newest config. And the last pillar is the plug-and-play architecture because I know people were invested in different technologies at some point and they want to stick with it. So this approach allows you to plug-and-play your own set of tools and apply the same logic to them as well. Next slide, please. And this is how we ended up with the EO4E Observability Platform, which you have the Observer and Observer logic and you have the Observer clusters running different things and you have the centralized Observer cluster which has the monitoring, logging, and tracing data that are sent by the Observer. And this gives us a single access point for operators and developers alike. It has the following tools that we mentioned and we actually provisioned a cluster just now to show it in the next slide, please. Live demo. Hope it will work, but if not, we have some backup images anyway. So it will be fine. Thank you very much. And I will give the microphone to Francesco for the live demo. Thank you. So, okay, this is our, okay. This is our home dashboard. So practically, as you can see, just a summary of our system. On Rancher, we have multiple clusters, okay, in this case, multiple clusters and we can control fleet from just NAS dashboard. So we can just see what, okay, just loading, but it is, we can see what is happening inside the system when we update our configuration which is propagated toward the clusters, as Armakan said before. So from this, we have just a summary of all the clusters and we have a platform. We can, for example, see, we have dashboards for visualizing the data more in a more, in a finer way, so we can go to some clusters. And so, we decided also to add something new. So we tried also to deploy a new cluster a few minutes ago. And so by just seeing Rancher to create one cluster, then the GitOps are automatic because as Armakan said, they are integrated in Rancher. So the fleet agent and all the other components are automatically deployed. And so you have just to create the cluster and as you can see, all the metrics are flowing and logs, et cetera. So it is straightforward to keep consistency as Armakan said inside all the clusters. And then we can see, so this is just a general dashboard for viewing general information for the clusters. We can have also more finer way to look at our system. We have, for example, here for the NGINX, we have both log and traces. So for example, now, okay, this bit processing. So for example, we can choose one cluster and then we can see logs on one side and on the other we have traces. We can select, for example, one trace by using a request ID. So for example, you can take this. Oops, sorry. So by just selecting one trace, so we can see that here there is now just one trace and I can go and see, so the trace the data. So we have visibility on the type system by looking also at the specific components for the observability components. For example, I can see about the logging. Oops, something didn't happen here. Sorry. Maybe it was the new cluster, maybe. And yeah, so just refreshing, okay, no, okay. Sorry, this is the beautiful of the live, okay. And yeah, we have also something about the Thanos and yeah, something is, and yeah. This is just an overview of our platform, okay. So we have some minutes for some questions if you want to ask for something. You want to say anything? Can we come back to the presentation? Yeah. So yeah, okay, thank you. Yeah, thank you very much, everyone. Thank you. Testing, testing. Hi, thank you for the presentation. Given that a couple of the components you mentioned, Fluentbit and the Open Telemetry Collector are going to both be supporting the full Open Telemetry protocol, how do you foresee the evolution of your stack? Would you consolidate functionality into just using one of those, or would you continue to use both for the different tracing metrics, et cetera? This is a question that I was asking to myself as well, like I use Open Telemetry Collector and it can use Prometheus, it can use Open Search as a data backend and we had some investment on Jager and therefore we said, okay, let's keep it because this is a tool that we know of, but I also see a lot of evolvement go into that direction, but not, I don't want to pick any tool but I also see what you saw earlier as well and I can see in a future tense, we can evolve into that part, but it also depends on the use cases and the requirements that you have because Jager has some also nice features that you have like dependency graph on the services, et cetera, which are really easy to visualize for a developer perspective. So I must incline to say why not if that road goes well and we can migrate to that, why not? But as for time being, we have some investment on Jager anyway so we decided to keep it, but this is a question that I asked myself as well, thank you. Hello, great talk by the way. So my question is how do you make sure that your observability cluster is still functioning properly? There's like two parts here because one is that obviously if it's still running, you can check it from externally, but if you misconfigured say alert manager for example and it's down there's, you basically lost alert, your alert manager to notify you that something's gone wrong, you want? Yeah, I know.  Like you need to observe the observer as well and you can achieve it with a simple logic. Maybe you can have an agent based monitoring solution enabled so that they can check the nodes itself or the end points that you have. But at the end of the day, yeah, I mean, this becomes something like a pet that you need to take in an account that the lifecycle of that cluster is vital for all the other things that you observe. So the observer cluster doesn't need to be a single cluster, this I can say. You can scale the observer cluster as well, but you must take into account the complexity of doing that as well. So it is kind of a trade-off. You can say that, okay, I'm gonna keep it simple to observe the observer and if something goes wrong, I have a problem and I have something that I need to take care of, maybe just a simple webhook to Slack channel or whatever the alert mechanism that you have so that you can have an alert so that you can alert the CIS admins or you can go wild and you can have multiple observers in different network segments so that you can have some kind of a high availability in that sense, but it depends. We keep it simple. If this will answer your question, we keep it simple. If something goes wrong, we take it as a pet and we try to fix it. All right, thank you. Hi guys, great talk, by the way. Just a question related with the Thanos architecture. So any technical reason to use the Thanos sidecar feature instead of, you know, the Thanos receiver and rely on permitted remote, right? Yeah, we thought about that. Obviously, when we started this project, we didn't know exactly how many cluster we have to manage. So we're trying to save some resources on the observer side, which is heavy on using resources. So in this case, we decided to go with the sidecars which are well-supported yet in the primitive operator that we used and we just deployed all the other components on the observer cluster. So in this case, we have just one query or two if we want to replicate on the observer side and then we leave the sidecars to do all the processing of retrieving all the metrics. So in a sense, we are reducing the pressure on the observer, at least for the metrics, because logs and traces are taking lots of resources, in particular logs, are taking lots of resources on the observer side so we can reduce a bit the pressure. So thank you for your question. Hello, guys. Thank you for the presentation. I want to know how long did it take from the humble origins, single cluster, single cloud, to the multi-cluster, multi-cluster you are now and how many people are in the team? Well, OK. Go back to the first slide. Ah, OK, if you go back to the first slide, you can see we have three people working on this dedicated. Unfortunately, Lucia is not with us, but it took three of us to build this from scratch. And there was a lot of time trying to figure out what is the correct path to go with, and this actually took longer than the actual implementation phase. So we invested a lot of time on figure out what we need to use. And this took like a couple of months, maybe, in order to do the research, proper research to do that. And then we spent a couple of weeks to actually implement it and use it on the fly. So one week plus two months. Thank you very much. Just one thing. Yeah, we worked from Chinaca, both Francesco and Lucia. And there is something very important that we are a very heterogeneous team. Also in the project, there are many partners. So these technologies give us the possibility to configure and develop our platform without replicating all the roles for accessing the clusters every time. So this is very important because Fleet gave us the possibility to develop very fast, very quick, without thinking about all the roles and the access to the clusters. Any other question? Are you able to share the amount of cost of this stack compared to the overall clusters you are monitoring? Can you repeat? In fact, you have 100% of costs for the wall clusters and the availabilities and everything. Only the availability stack, or what does it represent on the overall cost? In a sense of the infrastructure cost of maintaining that, we are using community clouds in this project. So this project is funded by EC Horizon Program. So we actually have, let's say, quote, unquote, unlimited resources that we can use. So we can use the other cloud and VK resources, let's say, without paying anything. But yeah, for that reason, we don't have that kind of a metric available right now that we can give you. But in order to give you a scale, the observer cluster is 10 nodes, three masters, and the remaining are the worker nodes. And every node has something like eight cores and four cores and eight gigabytes of RAM, or something very similar. Sometimes we scale it up. Sometimes we scale it down, depending on the load that we have. But this is more or less the size that we have. The biggest problem is the storage, because you need to allocate a lot of storage. So I don't know how that will scale in a public cloud where you need to actually pay them. Thank you very much. Thank you, everyone, for having us. Thank you so much. Thank you.


role of MRI spine in pod spine. Author is Dr. Shubu Malani and co-author is my son, Dr. Vajra, Dr. Ajavari. I'm second year M.D. radio diagnosis student in GMSA Ornbad. The study of the MR appearances of the TB spine to evaluate the role of MRI as an investigation modality in tuberculosis of the spine and to observe its value in early diagnosis and management to evaluate the role of MRI in determining the extent of spinal tuberculosis as compared to brain radiography. Introduction the tuberculosis of the spine is an infection by the mycobacterium tuberculosis involving one more, one and more components of the spine, namely the vertebra, the vertebral disc, paraspinal soft tissues and epidural space. The early recognition and pro treatment are therefore necessary to minimize the residual spinal deformity or permanent neurological deficit. The spinal TB is the most clinically important form of the extra pulmonary tuberculosis as it may produce serious neurological sequelae due to the competition of the spinal cord as a result of this itself as well as the results in deformity. Materials and method. The study was done from 2020 to 2023 in 30 patients diagnosed with the tuberculosis of the spine. The diagnosis was established on the basis of at least one of the following criteria. The histological, histological evidence of the cassitin, granuloma, the histological demonstration of the acid first basilar in the lesion, the growth of mycobacterium on the culture of the tissue. The satisfactory therapeutic response to the chemotherapy in patients with the clinical or the radiological evidence of the spinal TB. Plain radiographs and the MRI of the spine were carried out in all the patients. The MRI was done using 3 tesla G-16. The MRI was featured where MRI features were observed on T1-mated and T2-mated and star and post contrast by gadolinium contrast and T1 sequences with the sections in the sedative coronal and axioplans. The features on the plane radiographs and MRI were compared. In my study, the 30 patients in the results were evaluated as per following parameters, the comparison of X-ray and the more findings, the clinical features, the vertebral level, the types of vertebral lesions. According to clinical features, patients are classified on the basis of the clinical features. The most common feature of the patient being back pain, which is around 80% of the patient. Second being the spinal deformity, which is 46%, a third being the fever, which is 36% and fourth being parapheresis and bravulator involvement. The most common vertebral level involved is the dorsal vertebra followed by the lumbar vertebra and the rare vertebra involved are the cervical vertebras and multiple levels as described here. The types of vertebral lesions, the most common type of lesion being the paradiscal, a second common being the central and followed by the posterior elements and the anterior some ligaments. The comparison between the plane radiographs and the MRI findings of the studies we have done, where the plane radiographs, we can see the findings pick up in this most patient and in MRI the findings were picked up in this much patient. So, the level of involvement as we can see here in this chart discussion, the plane radiograph features, the spread of infection is typically described as subligamentus beneath the anterior longitudinal ligament. Usually, spreading the posterior elements and often involve multiple levels, the reduction in the vertebral height is often seen in the irregularity of the anterior superior end plate due to subligamentus. There may be some irregularity of the anterior vertebral margin. This is classical appearance with the TB spondylysis. The ivory vertebrae can result with the ossifications or the associated features include gimpus deformity and vertebral planar. As with other extraordinary TB, the chest feel may be unrevealed in no permanent lesion seen in up to 50% of cases with the source being the primary lung lesion that is clinically silent. The MRI features the occipital pleuses of the spine are as follows. The vertical body end plate involvement appears as heterogeneously enhancing end plate irregularity on the post-conference sequences. The vertebral lesions appear hyperintensive on T1 weighted images, hyperintensive on T2 weighted images and shows heterogeneous enhancement in post-conference T1 weighted images. The marrow edema appears as hyperintensive areas on T2 weighted and stir images. The intervertebral disc involvement appears hyperintensive on T1 weighted and hyperintensive on T2 weighted images and shows heterogeneous enhancement on post-conference T1 weighted images. The pre-vertical, paravirtical and sauced abscesses appear as heterogeneous lesion with peripheral enhancement and central non-enhancing hyperintensive areas on post-conference T1 weighted images. The granulation tissue appears heterogeneously enhancing soft tissue on post-conference T1 weighted images. Here we can see the case one. We have the images of the 44 year old male showing the hyperintense at the level of L3 vertebra. Here we can see the hyperintense at the level of L3 vertebral lesion in T1 weighted sag and core sections. The same images appear as hyperintense on T2 weighted images. Pre- or paravirtical abscesses are noted. Here we can see the image of 75 year old female patient showing hyperintense lesion involving D9 and D10 vertebra on T1 weighted images and hyperintense on T2 weighted images. Now the post-conference T1 shows enhancing margins of the bony erosions with the enhancing granulation tissue. Here we can see in these images. Here we can see the images of the 10 year old male showing the erosions of the D8 and D11 vertebral body with the waging of the disk space obliterating at the level of D10 and D11. The pre-vertebrate and bilateral paravirtical abscesses we can see here. Now the post-conference T1 weighted images show enhancement in the margins of the abscesses and also the margins of the area of erosions of the vertebral bodies. Here we can see the case four where the images of the 11 year old female patient showing the kyphos coliotic deformation involving L1 and L2 vertebral bodies. My co-intense areas are in the L1 and L2 vertebral bodies on T1 weighted images, same lesion type as hyperintense on T2 weighted images. The pre-vertebrate and paravirtical abscesses are noted. Case four post-operative X-rays. Here we can see the post-operative cases of these same patients. The case five being the images of the 13 year old female showing the large pre-vertebral collection. Here we can see the collection in these images, large vertebral collection, likely abscesses. Hyperintense areas in C1, C2 and C3 vertebral bodies are erosions. No erosive in spinal cord environment is noted. Here we can see the sparing of the spinal cord. The outcome of this study shows the most common clinical features is a back pain followed by the deformity with the most patient being of April. The most common vertebrae involved is dorsal followed by lumbar and cervical with the sacroiliac being the least involved. The parandiscal type of the vertebral lesion is a common there central and rarely it involves osteoarthritis elements. On comparing both of the modalities, bone destruction is equally assessed whereas the soft tissue involvement extent of the lesion, the type of lesion and four disc involvement are better visualized on MRI. The conclusion being it helps in early diagnosis and therefore management. The MRI offers the excellent visualization of the bone and soft tissue components on the spine tuberculosis helps to identify the disease and distance asymptomatic sites. The MRI imaging clearly demonstrates the extent of the soft tissue disease and it affects the ethical cord or foramen.


Meanwhile, U.S. President Joe Biden says he was heartened by Russian President Vladimir Putin's call for collaborative efforts on removal of carbon dioxide to combat climate change and looked forward to working with Russia. Speaking on the second day of a virtual summit on climate change, Biden said great progress had already been made. But more efforts were needed by governments and the private sector to ensure a smooth transition to a clean energy future. We've made great progress in my view so far. I'm grateful to all the leaders who have announced new commitments to help us meet the existential threat of climate change. This summit is a start, a start of a road that will take us to Glasgow for the UN Climate Change Conference in November where we're going to make these commitments real, putting all of our nations on a path to a secure, prosperous and sustainable future. We also, I'm very heartened by President Putin's call yesterday for the world to collaborate and advance carbon dioxide removal, and the United States looks forward to working with Russia and other countries in that endeavor. It has great promise. This challenge and these opportunities are going to be met by working people in every nation. And as we transition to a clean energy future, we must ensure that workers who have thrived in yesterday's and today's industries have as bright a tomorrow in the new industries.


2016 is actually a very peculiar year from the point of view of economic policy because it has been a year which is marked with high optics, very high sound, but actually on the ground a lot of things that are anti-people which have been happening. I'll give you the example of make in India. The Prime Minister claims that now we're going to generate employment, generate a high rate of growth through this policy of his. In fact what he's doing is diluting the land law. The land law is being diluted in every single BJP rule state so that lands of farmers can be grabbed from them. Similarly, the Forest Rights Act is just not being implemented anywhere and land diversion is happening at such a massive pace that actually it's not make in India, it's take from India. There's been a lot of hype about the Indian economy that it's the fastest growing and all that, but even before the demonetization led that such a body blow to economic growth, this is not a good year. Our exports have been falling or stagnating in many sectors, imports have fallen but not to the same extent so our trade deficit has grown and at the same time many of our sectors are becoming less competitive even while the exchange rate is actually depreciating. As you know that large part of the export sector is served by the small and medium enterprises. We all know how badly the small and medium enterprises have been hit by the demonetization. Though this government has been talking a lot about supporting the SME sector and creating jobs but this one thing that they have done about demonetization clearly shows that they have absolutely no regard for jobs and they have no interest in supporting the SME sector. So I would say that this is a kind of a double whammy because exports have been on a decline from almost for two years or exports have been down and the main reason has been the sluggishness of the global economy. So we can go sector by sector, essentially we get a picture of serious difficulty in the productive sectors and even with reference to the services sector things seem to be much worse than what they were let's say about one year ago and real wages of workers in the organized sector and organized sector as you know is the most sought after sector for workers. Real wages there have been stagnant. In fact there has been a marginal decline. If you go by then it says Jetta and so on. The most vulnerable section of the workforce, the daily wage earners, they are not getting any job for last one, one and half months time, they are poor people if they don't get income then obviously they would not have money to spend and if they can't spend money since they spend larger proportion of their income on consumption expenditure. The consumption expenditure would come down even for the richer section of people because of shortage of cash because of inconvenience. Now demonetization has primarily had created two problems for farmers. One farmers who had just harvested their crops were unable to sell them, in particular farmers in areas where public procurement doesn't happen, small farmers, marginal farmers who are forced to normally sell their crop to private traders. These farmers face the problem because private traders were not buying the crop. This immediately resulted in a massive fall in agricultural prices, farmers lost their incomes. Of course one of the biggest tax reforms in independent India has been pushed through parliament in a way where the constitution has been amended to facilitate the goods and services tax. And this in my opinion has gone through without much thinking, if you look at the VAT pattern what you find is that most of the commodities that are taxed a large proportion of that if you just take do a calculation you find that almost 50 percent is commodities like petrol and gas and utilities which are going to be outside the ambit of GSD. Now even the most generous estimate that has been worked out is worked on a 30 percent assumption that these kind of goods account for just 30 percent. So what you can see is a huge underestimation of the proportion of consumption that is going to be outside the ambit of GSD. Finally another very very important and disturbing intervention which has happened in this year has been the dependence on biometrics for food distribution. You take the case of Gujarat and I give you Gujarat as an example because it is a much doubted example by the present regime. But in Gujarat what they have actually done is that they are using biometrics and the failure of identification because of a problem in the technology itself has meant that vast sections have not got their rations. So there's been a big drop in rations and offtake in Gujarat under the public distribution system. Therefore 2016 has actually meant a lot of hardships for the people. It has meant that the government has made big promises and delivered absolutely nothing. In fact it has taken away from the people. The Indian economy needs a big push otherwise as of now it is looking like the future is very big. The future situation is horrifying in the sense that in the next year most likely the unemployment, the poverty, the inequality would rise further and the Indian growth story is virtually over. Next month somewhere in the middle of January you will get an advance estimate from the CSO of what has happened to the economy or at least to the GDP in the whole year. Unfortunately the CSO would be operating also with data at best till the end of November. Most of that data will really be at the end of October. So you will get a rather funny projection of the economy which is much of it is from the first two months a little bit of October added on maybe a slight bit of November added on but then projecting the next three or four months on the basis of that rather than what has happened after the demonetization. So expect that to be saying that not much has happened maybe come down by 0.2, 0.3, 0.5 percent but from all accounts that would be wrong.


Hello. So my name is Josephine. I run a stock on base startup called Food for Thought. The main focus of this concept is food and work. In order to execute my business idea, I am in need of a kitchen and a partner, which will be a most talented chef that can complement the skills that I have. So the approximate number for what I need in the kitchen and this partner is 400,000 US dollars. This number is equal to the number of unemployed people we have in Sweden. So about 400,000 Swedes do not have a job to go to every morning. That's a big problem. So to make this more feasible, I'm focusing on a part of this group. Many of the people within this group are women who have immigrated to Sweden from different countries. It's a diverse group of academics and non-academics, but you also see a lot of women with low level of education, little language skills, and almost no experience of the Swedish labour market. And I used to meet this group a lot in my former job as a so-called job coach, where my task was to support women writing CVs and find jobs. It's a very difficult thing to do to write a CV if you don't have anything to put in your CV. So I was very frustrated and not so happy in this job. And I started searching for solutions based on creating jobs instead of searching for them. Luckily, I have a big interest in food. So through this, I started seeing a pattern that many of the women have informal culinary skills. It's something that they have been doing from early age in a comfort zone in their homes. So a year later of concept development, I have reached a concept that is based on creating meaningful jobs through selling high quality food based on their own recipes and organic food from local farmers. This can create a financially sustainable business. I also have initiated a collaboration with the municipality in Stockholm called Botkyrka. In addition to that, I have initial funding from Tilveksverket and we have started to employ three women by the hour. So I can finally stop using the term target audience or target group and start using their names, which is FISA, ASUMAN and SEHR. And together we work with prototyping and concept development which in our case means cooking and developing recipes. And I'd like to end by explaining the relationship between our social aim and our financial goals. So there's many times there's a taboo between making money and saving the world. And in our case, the money making aspect is crucial to the empowerment process. The meeting between our co-workers and clients is the ultimate receipt of their skills. When someone is willing to pay for the food that you just made at a market price, that's the ultimate approval of your competence. And that's the value foundation for our business. Thank you.