![]() ![]() If you are keen on more details about the migration process and how to contribute, please, visit the ELevate site and the AlmaLinux Migration wiki page. This way maintainers and application vendors can contribute metadata to the library and users can customize the metdata set they download. ![]() Oracle have been gracious enough to contribute an initial data set which we have built upon and we’ve also put together the Package Evolution Service to allow the community to contribute and collaborate on additional metadata. This metadata is what describes the steps required for a package to “evolve” from one release to the next. Second, Leapp needs several configuration files, the biggest of them is some metdata called the package evolution data file pes-events.json. Work has already begun to get those merged upstream too since we like to avoid forking as much as possible. First, We’ve put together some patches to Red Hat’s Leapp utility (which you can find here) to support migration from CentOS. Let’s take a little peak behind the scenes at how all this works. If you want to get started quickly, check out the ELevate Quick Start Guide. It is recommended to do a trial run in a sandbox to verify that migration worked as expected before you attempt to migrate any production system. We HIGHLY recommend that you follow system administration best practices and make sure you have backups and/or snapshots of your system before you proceed. Get it? EL evate? Yeah, anyway…īefore we get started, let’s be smart. We are extremely happy to announce our migration project for major version of RHEL-derivative distributions. ![]() Hey, all! We’d like to share a very cool project/initiative that we’ve been working on with the community. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |