Past, Present and Future of DRLM project
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 490 | |
| Author | ||
| License | CC Attribution 2.0 Belgium: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/47476 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
00:00
Field (computer science)BackupOpen sourceProjective planeSoftware maintenanceGrass (card game)Multiplication signInformation technology consulting2 (number)WhiteboardHypermediaRevision controlComputer animationLecture/Conference
01:24
Uniform resource locatorBitProjective planePresentation of a groupRevision controlComputer animation
01:58
Dynamic random-access memoryPhysical systemData recoveryServer (computing)Physical systemSoftware testingData recoveryData managementRevision controlValidity (statistics)Valuation (algebra)Lecture/Conference
02:56
Uniform resource locatorRevision controlSlide ruleProjective planeMultiplication signExecution unitData managementPhysical systemMultiplication tableBuildingLecture/Conference
03:29
Dynamic random-access memoryPhysical systemData recoverySoftwareData managementHuman migrationPresentation of a groupProjective planeData managementBitCentralizer and normalizerTraffic reporting40 (number)Automatic differentiationLecture/ConferenceJSONComputer animation
03:54
Client (computing)Error messageScheduling (computing)BackupComputer-generated imageryUniform resource locatorExpert systemTraffic reportingError messagePhysical systemMedical imagingClient (computing)BackupConfiguration spaceScheduling (computing)Installation artData recoveryServer (computing)Task (computing)Digital rights managementPresentation of a groupAtomic numberVotingWhiteboardComputer animationLecture/Conference
05:09
Client (computing)Scheduling (computing)BackupComputer networkPhysical systemData recoverySystem programmingRollback (data management)SoftwareComputer hardwareMiniDiscPhysical systemSoftwareData recoveryTask (computing)Plane (geometry)NP-hardVirtual machineProjective planeComputer hardwareComputer animationLecture/Conference
05:45
Physical systemComputer networkData recoverySystem programmingBackupRollback (data management)Computer hardwareSoftwareMiniDiscInstallation artClient (computing)Server (computing)Distribution (mathematics)PhysicsComputer-generated imageryTemplate (C++)Uniform resource locatorInclusion mapHill differential equationPhysical systemTemplate (C++)ArmClient (computing)Revision controlHuman migrationMedical imagingDecision support systemThumbnailComputer animationLecture/Conference
06:38
Server (computing)Computing platformVisualization (computer graphics)Virtual realityData conversionFile formatMiniDiscHuman migrationLatent heatPhysical systemComputer hardwareAxiom of choiceArmPhysical systemComputer hardwareBootingVirtualizationSoftwareAdditionProgram flowchartLecture/Conference
07:17
Computing platformVisualization (computer graphics)Virtual realityMiniDiscData conversionFile formatLatent heatHuman migrationPhysical systemComputer hardwareAxiom of choiceInternet forumServer (computing)Radio-frequency identificationInclusion mapOperating systemPhysical systemHuman migrationMultiplication signBackupSoftware testingComputer hardwareGoodness of fitCASE <Informatik>Data recoveryPoint (geometry)Task (computing)Moment (mathematics)Theory of relativityExecution unitDistribution (mathematics)Program flowchartLecture/Conference
09:06
Radio-frequency identificationServer (computing)Visualization (computer graphics)Computing platformVirtual realityMiniDiscData conversionFile formatLatent heatHuman migrationPhysical systemComputer hardwareAxiom of choiceComputer-generated imageryBinary fileBackupRevision controlDatabaseControl flowInstallation artClient (computing)Configuration spaceDefault (computer science)Parameter (computer programming)Repository (publishing)Presentation of a groupRevision controlBinary codeServer (computing)Distribution (mathematics)InformationPoint (geometry)Program flowchartSource codeXML
09:49
Revision controlBackupInclusion mapProgrammable read-only memoryClient (computing)BackupDistribution (mathematics)Multiplication signFunction (mathematics)DatabaseConfiguration spaceInformationPhysical systemComputer filePairwise comparisonSpherical capError messageLecture/Conference
10:44
Binary fileBackupDatabaseControl flowRevision controlInstallation artClient (computing)Configuration spaceReal numberDefault (computer science)Server (computing)Parameter (computer programming)Repository (publishing)Sanitary sewerComputer networkUniform resource locatorComputer-generated imageryMaxima and minimaFunction (mathematics)InformationSelf-organizationReading (process)Revision controlScaling (geometry)Graph coloringClient (computing)BackupLine (geometry)Projective planeServer (computing)Configuration spaceParameter (computer programming)Default (computer science)Interface (computing)Operator (mathematics)Source codeXMLComputer animationLecture/Conference
11:52
Computer-generated imageryBinary fileBackupControl flowDatabaseRevision controlClient (computing)Installation artConfiguration spaceDefault (computer science)Real numberServer (computing)Repository (publishing)Parameter (computer programming)GEDCOMRoundingDuality (mathematics)Product (business)Branch (computer science)Information technology consultingStaff (military)Goodness of fitRoundness (object)SoftwareRevision controlMedical imagingLaptopPhysical systemSource codeXMLLecture/Conference
12:36
Computer-generated imageryBinary fileBackupRevision controlDatabaseControl flowInstallation artConfiguration spaceClient (computing)Default (computer science)Real numberServer (computing)Repository (publishing)Parameter (computer programming)Demo (music)VideoconferencingInformationData recoveryEmulationMultiplication signDemo (music)Link (knot theory)Revision controlSelf-organizationSource codeXMLJSON
13:01
Uniform resource locatorRevision controlDemo (music)VideoconferencingInformationClient (computing)BackupData recoveryEmulationDynamic random-access memoryDiscrete element methodData storage deviceObject (grammar)DatabaseProjective planeMultiplication signRevision controlSoftware frameworkRule of inferenceLimit (category theory)Lecture/ConferenceJSONProgram flowchart
13:33
Revision controlDatabaseData recoveryProjective planePhysical systemModul <Datentyp>Revision controlDifferent (Kate Ryan album)Core dumpRight angleClient (computing)Plug-in (computing)Data storage deviceSoftwareWorkstation <Musikinstrument>LaptopBinary codeMultiplicationGodInternetworkingGoodness of fitEndliche ModelltheoriePlane (geometry)Lecture/Conference
14:48
Data storage deviceObject (grammar)DatabaseRevision controlPlug-in (computing)Binary codeRevision controlPoint (geometry)Goodness of fitLecture/ConferenceProgram flowchart
15:27
Revision controlModul <Datentyp>Object (grammar)Data storage deviceDatabaseDiscrete element methodPhysical systemScheduling (computing)Task (computing)Integrated development environmentSoftware testingPlug-in (computing)EncryptionComponent-based software engineeringTelecommunicationFunctional (mathematics)Common Language InfrastructureCore dumpPhysical systemProjective planeBackupComputer architectureDatabaseRevision controlPoint (geometry)Military baseMaizeFunctional (mathematics)Digital rights managementCore dumpSoftwareInterface (computing)Different (Kate Ryan album)Line (geometry)Lecture/ConferenceProgram flowchartComputer animation
16:07
Functional (mathematics)Physical systemTask (computing)Scheduling (computing)Data storage deviceSoftware testingIntegrated development environmentCore dumpEncryptionComponent-based software engineeringTelecommunicationRevision controlWeb pageCommon Language InfrastructureInstallation artElement (mathematics)Electronic mailing listTelecommunicationMoment (mathematics)Physical systemEncryptionSoftware developerIntegrated development environmentBackupPlug-in (computing)Software testingData storage deviceLecture/Conference
16:34
Physical systemScheduling (computing)Task (computing)Data storage deviceIntegrated development environmentSoftware testingComponent-based software engineeringTelecommunicationEncryptionFunctional (mathematics)Common Language InfrastructureCore dumpRevision controlTelecommunicationConnectivity (graph theory)Multiplication signEncryption
16:59
Data storage deviceCore dumpIntegrated development environmentCommon Language InfrastructureFunctional (mathematics)Physical systemTask (computing)Scheduling (computing)Component-based software engineeringTelecommunicationEncryptionRevision controlDrop (liquid)Installation artUniform resource locatorBuildingSoftware testingSoftware repositorySoftware developerCloningHacker (term)Default (computer science)Integrated development environmentBuildingSoftware testingBitComputer configurationSoftware developerTransport Layer SecurityElement (mathematics)Traffic reportingCuboidMedical imagingSoftware repositoryCore dumpConfiguration spaceComplete metric spaceProjective planeWorkstation <Musikinstrument>NumberLaptopLibrary (computing)Lecture/ConferenceJSONXML
17:55
CloningRevision controlGamma functionHacker (term)Library (computing)Projective planeRevision controlPoint (geometry)Text editorInstallation artIntegrated development environmentPlug-in (computing)CodeLaptopLevel (video gaming)Moment (mathematics)Computing platformLecture/Conference
18:48
Software testingBuildingSoftware repositoryRevision controlSoftware developerIntegrated development environmentComponent-based software engineeringCloningHacker (term)CurvatureDatabaseDrill commandsGraphical user interfaceStatisticsHill differential equationSoftware testingPoint (geometry)Perturbation theoryIntegrated development environmentEvent horizonProjective planeRevision controlSource code
19:18
Demo (music)Integrated development environmentSoftware testingMultiplication signWeb pageLecture/Conference
19:40
Modul <Datentyp>Revision controlPhase transitionComputing platformBootingComputer configurationBackupRevision controlProjective planeMathematicsSelf-organizationRule of inferenceProduct (business)Video gameSoftware testingSoftware developerDistribution (mathematics)Lecture/Conference
21:02
Modul <Datentyp>Revision controlPhase transitionComputing platformBootingComputer configurationBackupFeedbackWritingCodeExplosionService (economics)Design by contractInformationPresentation of a groupTraffic reportingProjective planeOpen setSoftware repositorySoftware testingXML
21:27
Shared memoryMultiplication signLecture/Conference
21:53
Software developerSlide ruleMultiplication signSlide ruleInformationOrder (biology)Event horizonProjective planeProduct (business)Real number1 (number)Lecture/ConferenceJSON
22:28
Revision controlDatabaseHigh availabilityWordVotingLecture/Conference
23:20
Link (knot theory)Server (computing)Proper mapPhysical systemPlug-in (computing)Volume (thermodynamics)TelecommunicationClient (computing)BitData recoveryPoint (geometry)Revision controlBackupService (economics)DatabaseProcess (computing)Front and back endsEncryptionIP addressMultiplication signDynamic Host Configuration ProtocolSoftware frameworkComputing platformMedical imagingData storage deviceLevel (video gaming)Set (mathematics)Intelligent NetworkWeightArmObservational studyWebsiteFrame problemConfidence intervalLecture/Conference
28:44
EmailSoftware developerSlide ruleOpen sourcePoint cloudFacebookJSON
Transcript: English(auto-generated)
00:05
Let's Thank you Hi everybody, good morning. Thanks for coming to this early first talk of this Deb room It's the second year of the backup and recovery that room here in the force them. So
00:26
Very pleased to be here again for a second time Today I'm going to talk about past the present the future of the alarm project. So just let the start My name is Deetak Uluveda
00:40
I'm the co-owner and co-founder at brain updaters Brain updaters are is a small company consultancy company that is based on Providing solutions on top of open source projects so We I'm also a co-founder and a maintainer of the DLM project we're going to talk in this talk and
01:03
I've contributed a few with relax and regard grass in is going to talk and Johan's after me and few ports to config to HTML project so These are the original DLM team
01:21
we have new people in the project now in ethics and Few contribution from Johan In the room also today, so let's start with the agenda of the talk We're gonna talk a little bit about the past. What's the origin of the project? Very very fast. Don't worry about that. It's too early today
01:43
Then what's the present of the project? What is the URLM and what is? Coming on what is in the in the last release version and what about the future of the of the project so Let's start with the past Well the past starts with a requirement of own one of our biggest customers that need a proper solution for
02:06
for Linux systems and their disaster recovery so It's a pharma industry and needs a lot of stuff on validation for The history of the systems they proved when test a lot of tools for the rest are recovering and
02:26
Every every try failed so Asked us and we proposed to use relax and recover and develop a management layer on top of that for them because they need some Some management solution for on top of that for the centers
02:40
so This started a summer of 2013 and at the end of the year we we had the first use you ready to use version of the LM for them and That was the very beginning so to see what's today The
03:01
Real use of the project for them I'm not going to talk because we don't have time today for that, but you can check these slides that what? the the ripples global manager for Unix systems Say it about the project and what is the project for them at the company, so let's pass just a
03:23
Small time table out what's the from the beginning to today the last expression? so Let's start talking about the present of the project First of all I hopefully I Read that everybody knows more or less. What is the end relax and recover so
03:44
We're going to talk later all that and the alarm is just a layer on top of of that for management. Yeah central management So let's talk about a little bit about some of the features that the alarm adds On top of relax and recover that it's automatic error reporting so sorry
04:03
if Any backup fails it's going to be able to To open a ticket or report an alert for for your monitoring systems and can be extended with any monitoring system it's going to be able to Perform an unattended installation of relax and recover and all these dependencies on all the base configuration stuff
04:24
From the DRM server, so you are going to just say add client install client I'm going to do all the boring stuff for you And also it's going to it has a backup schedule you can sell some schedule some tasks
04:41
On that I'm going to perform the backups weekly Monthly daily hourly whatever you want so and there is a lot of important It is going to be able you are going to be able to export and import the extractable images So you are going to be able to? Export and import from the same server, but you can export any much from one their own server in the percenter a and
05:03
Importing the center beyond whatever it is And you can recover that system on that so What's the alarm? Mainly the alarm is a disaster recovery solution
05:20
So you are going to be able to recover a system fully from network? So whatever is a virtual machine hardware You are going to be able to recover the system though, so it's it's mainly task is disaster recovery, but
05:41
The years past and we used a lot. We are not just the developers were also users of the project so we Found that it's a very interesting to for the deploying new systems So we are we are able to deploy new systems with a base Image of a previously installed system. What is called a template or?
06:04
Golden image we can have different images For of our base configs base systems, we can import adding a new client and deploy that operating system, so it's good way to use
06:21
for that and Also is a very interesting tool for performing migrations Why because it is a vendor agnostic solutions, so you can migrate from different virtual Systems the decision systems are from VMware to attend to KVM whatever because it's not it's vendor agnostic
06:41
Yeah, you don't need to use tools linked to the vendor. There are tools to do that, but mostly can fail Depending on where you coming and The destination of the of the system, so this is a good tool to do that We are going to be able to swap
07:01
all hardware for to new hardware very fast also and Also, if you want to roll back from a virtualization that it's not working properly and you need to go back to physical It's easy to do that with your land You just need to boot from network again on the on the system and recover that it's very fast
07:21
So and you can say well there are other tools to do these migrations there are other tools still for doing Operating system deployments good tools. Yeah Why do you use the alarm for that? well
07:42
Anybody in the room does testing of their backup systems test it every year every six months Every Test it the recovery you more or less. I'm not your boss, so You don't need to lie to me well with your lamb
08:04
When you are migrating your new systems While you are installing new systems on your on your company you are going to test your disaster recovery solution So while you are using daily for this kind of tasks. We are going to be sure that
08:21
Hopefully never happens, but in case of disaster They're going to be sure that your disaster recovery solution works because you use use it daily With your systems your new hardware that it's going to be installed The first time you are going to have few problems. Maybe but you are going to solve them
08:40
At installation time, but it's there is no worry on that But there is a worry when you are need we need to this to recover the system in case of disaster Because you need to go online again, so if you use it daily with this Migrations new system deployments you are going to be sure that the day this system That you installed few times on that hardware
09:04
Using the alarm you are going to be able to recover fast, so that's the point to use a ramen for that So talking about the present We're going to see few things few highlights what the new version 2.3.1 now it's
09:24
Has now it's we replaced the the API that was backed by Apache server. We have a small Golang binary that is doing the same thing and Apache was a lot of pain for each release of new version on the edge distribution
09:42
So now it's just working. What did what needs to work and working flawlessly so no problems on that We added some Some better Improved the command line interface with more information So now we are going to see if the client is online or offline just listing the the alarm that
10:04
clients that you have in the database We are we had some super for new distributions at the deviant-10 and We also showed that when you release backups. We are going to see The duration of the backup in the command and in the output and also the backup size
10:24
It's it's important because if you see a very small backup or a very short time backup Maybe it's designed that something in the configuration is wrong So it's fast to fast to see if something is wrong with your Your backup maybe this doesn't have an error, but at the configuration
10:41
It's just keeping some files small files and not the whole system So it's it's good to have this information that come online So more or less these are the outputs of what I'm saying It's knowing showing the rear version and the client version if the if the backups are scheduled for the client and the green and red
11:01
Color is saying that the client is online or not If it's not a line you are going to not going to be able to do backups, etc And in the backup side we are going to see if this is a small backup maybe check it if it's okay, okay, you know if it's a small server could be okay, but If the these parameters can be adjusted in the configuration
11:22
So if you know that your backups are small, you can adjust that in the configuration It's not going to say you're worrying. Yeah, it's okay by default and the duration of the backup so that's what have we have today on the You know, I'm going interface and few other things that we have been improving
11:42
Last last six months and also we had a contribution from From a from a guy that tested the project using for in the in his company and And Did a pull request to run DLM on top of a docker container. So it's just it's undeveloped branch yet
12:03
It's working, but we do not recommend for production because needs some host networking stuff because the DLM version 2 needs Some things that it's not container really so But it's good to have a lot of your you offer a consultant and your need to deploy lots of system
12:24
It's good to have a docker image with your alarm Just to start do whatever you need to do and stop So your laptop is clean and you have your installation with your golden images, etc On your laptop to do to use that so it's a good point for use. Yeah
12:40
So I have a demo we don't have time today to show the demos matter published on a cinema About the whole DLM version 2 works Just check it. It's on the first mm and also In the link all the links for for all the demos of today's out, but we don't have time to
13:02
Show you today. Maybe we can Talk about it later and check it later. Okay so Now, let's talk about the the future of the project well Version 3 what's going on? Well, we used the first time we we need it to be very fast
13:26
To release the first version of the LM and we use the relax and recover framework for that it's a pretty amazing framework, but For our use has some limitations. Yeah, so we thought that we need to go far or go farther and
13:43
What's coming and what's what we want for the future for the project And we are going to we're doing a completely right of the of the project on Gola with Golan Why go long because it's more multi architecture. So we are we can have binaries for different systems. Not just Linux
14:04
Etc, etc. So It's going to be a modular design of the new version The storage back end is going to be s3 compatible. It's a minio the device is going to be MariaDB from SQLite and
14:21
We don't know it's a modular design It's going to have a plug-in system. The agent is going to manage some plugins The IPI is going to communicate our CRPC The client is going to be in your laptop or whatever workstation you have and you are going to connect to the core On your network different course are going to be able to manage so
14:41
It's going to be more flexible and more powerful for that and even we don't know Maybe it's just not going to do just a recovery for Linux It's going to be able to do more because you are going to be able to run the agents for Windows Mac OS Aax Hpux, whatever one we can start this Golan binary on that and if we have a plugin for that, it's
15:06
It's good So we don't we don't know We just going to release the version 3 first with relax and recover as it is now It's our point on our target now, but we know that it's going to be
15:21
Really for the future and also it's going to be able to be deployed on Kubernetes and we have in mind that this architecture is going to work to Do backups of Kubernetes systems Kubernetes databases. So that's the the point of the project also in the new version
15:40
So what we have until now for now, we have a functional DRM CPL common That is going to be the outcome online interface for for the project We are able to deploy the alarm course On different systems from the from the common line interface. We're going now We are being able to deploy agents in the network and that is going are going to communicate with a core
16:06
etc and We have a base plugin system that's working and it's doing a small backup and storing on the storage back end today. We have that and
16:20
We also have a testing environment to test all the things that we have and And a development environment so What is important for us is that all the communication? On the development we are developing all all these on top of TLS with all the components are going to be communicating and with encrypted communication. This is
16:45
the most important thing that we thought if we start developing with encryption if we have Problems we are going to solve problems the first time not okay that was working without Encryption and no it's failing what happens know what happens if it's going to be released
17:00
It's going to be released with TLS and now we drop the option I think in the in the element environment to not check the With TLS just it's by default with TLS, okay Let me explain a little bit the other dr3d is the development testing and building tool of the LM It's a github repo
17:22
with few docker images and compose Configurations that it's going to be able to deploy the complete environment based environment of the LM With with this with this repo, so just cloning building all the docker containers and starting
17:41
With your configuration of the of your github account Previously forked repos of the LM core common plugins, etc They're going to have a complete development and very on top of docker and the development box It's also a container with with beam and vs code editors in place with all the plugins need to develop on the project
18:03
So you don't need to install Golang libraries packages Anything on your laptop or on your workstation? It's going to be persistent in this report, but it's going to be clean Built in your laptop. So everybody is going to contribute to the project with the same libraries same versions
18:23
Everything is the same. So if you have a problem we have a problem Everybody is working on the same on top of the same platform on the same environment. So this is good because Everything is going to be the exact Every pull request is going to be tested on the same environment, etc, etc same versions same libraries
18:42
So that's the point that it's going to be easier to contribute to the new version that the version 2 of the LM But well, that's that's the point it's a the experience that we had previously that Why we offer this today for for the for the people that is going to use test or develop on top of that
19:03
So we also have some Some demos of of this development environment and the testing Of the project what it has the version 3 now are posted here in the in the event Page
19:20
we don't have time to To show today, but you can check it and you can see the whole testing and how it working the whole it's working different now and How to contribute with and test it with a development environment and repo So just there for for you to check
19:41
So the future of the project we are going to keep Developing the two versions the version 2 and the version 3 The version 3 is going to have changes but not the big changes that we are going to have in the version 3 Maybe some things that we are going to release for develop for 3 that are compatible with version 2 are going to be
20:00
ported to that and we are not Doing an end-of-life of the version 2 Until the version 3 is going to be really production really Okay, so and maybe for years it's going to be useful for some situations this version 2 of the LN But we are looking on the future We are going to make and put all our efforts to to develop the new version
20:23
Okay, well maintaining the version 2 Testing and development whatever needs for the new versions of the distribution of Linux etc etc Or most effort is going to be a version 3, but we are maybe have Some news there on the version 2 if some sponsored developments comes
20:46
this year, but anyway Depends on the customers that need some some things that are not in roadmap we are going to develop more things or not on the on the on the version 2 but All news and all the interesting really interesting stuff is going to come on the new version, okay
21:06
So hopefully You use it you test it or you want to contribute to the project So it's easy to do you can come to our github Repos open issues test it and report
21:23
Whatever you you have the problems Discuss discussing new new ideas to the project we are We always appreciate that so we are open to to new proposals and
21:40
If you use it or you are going to use it and enjoy it, please share your your experience So more people is going to be able to to use that so It's time for time for Q&A because we have small time for that and
22:03
If you missed something because I passed slides very fast if you want to check it We have I think more eight minutes more or less To talk about the project. Here are the slides of the of the of the event and all the information of the event today here the
22:21
Experience of a real customer in production a big customer with your lamp It's what they say about the project two years ago. No, it's not me. So you need to trust me and If there is any question, I'm be glad to to answer anything
22:41
Yeah, well The Question was if we are going to to use Postgres as a database back-end for For my for VLM, we don't know for now. We just
23:01
Have a target to use Maria DB instead of SQLite that we had on version 2 to be able to have High availability if we one of the back-end etc, and We don't know it's it just we have a connector now for to a Database and could be done with Postgres maybe or whatever other that is
23:24
We we think but for now we are focused on on have a working version So we are focused on the on those specifications. That is Maria DB Mineo for the storage back-end etc, but we don't know it's it's going to be possible. So we may be the
23:42
Choose you whatever you want. Maybe in this situation is better for use postgres and this other situation It's better to use Maria DB, whatever. It's possible and could be done Yeah
24:03
The question is how the database is going to to grow nowadays for VLM We only have a very small database that it's just keeping the reference of the backups the images etc so we
24:22
We have a very small database and hopefully The new one is going to be it's going to be bigger, but not as big as we can expect for that We expect that it's going to be a small database and the data is going to be Compressed encrypt on the storage back-end. So we don't we don't think that it's going to be a problem the
24:43
To have a huge database because we have a very small database now So it's just for keeping the the clients Reference the back-end reference the the jobs that we have scheduled, but it's it's really really small database So we don't we don't mind on that for now
25:04
another question well Nowadays the realm is a service for managing the historical Linux
25:20
Well, the question was what's the link between Kubernetes because I mentioned Kubernetes on the realm well Last year's I I started to use Kubernetes The new way of containers with Docker etc. Etc. So at every conference I assisted or every
25:41
every time when they asked for database backup People said okay put this outside of Kubernetes why Because we don't have a proper solution to recover that inside that That's that's the the the real situation now all the backup solutions know what is for Kubernetes, etc
26:05
Whatever container request written are meant for snapshotting the underlier Why this is good for static data But with an open back up open open it database. It's going to be a mess We are not going to be able to recover your database consistently
26:20
So the point with your land version 3 and Kubernetes is going to be able to have an agent It's going to be able to run inside these spots for Kubernetes spots sharing the IP address sharing the volumes So we are going to be able to run Tasks on on that agent using a plugin for that database inside Kubernetes and
26:42
Perform a proper Backup on top of that and a proper restore if you want without being to redeploy the the whole pot, etc Etc. Just recovering and backup and recording your data. What? Was always done until now with the containers So that's more or less the link that we thought that we need to change the
27:03
Little bit the concept of what the realm was Because the future is going to be containers and orchestrator etc, and it's there is a No still not a proper solution for backup and just recovery inside that So that's the point that we thought to see father in the future and start now
27:26
Rethinking the whole the whole thing now as I said we started with version The version 1 and version 2 still has the Relax and recover framework that was amazing for for us But we thought that in the future
27:41
We are going to have some some problems for to implement. We've seen that it's difficult to containerize DLM because the the framework and the Linking with the HCPs, etc. Etc. No, it's going to be a service And the agent the the agent system is going to be there
28:01
They're going to be server agents and client agents So a server agent is going to be the HCP TFTP Whatever and it's going to be able to be deployed as a container also and linked Using the communication inside the LM agent system So it's going to be easier to deploy that and extend on On top of orchestrate on platform and today's cloud services
28:25
so that's that's the point and more or less the link that why we rethink Rethink it all the LM stuff so Time's up. Thanks for coming and Hopefully you enjoy the next Alex today and this dead room. Thank you very much