Hi,
I've played with LDIF export/import years before IPA, but there's still big
knowledge gap.
A SOHO installation is not rare and we need a detailed howto for in-place
migration (with obvious downtime)
This documentation is more critical because upstream (RHEL) doesn't support
this path.
Example stuff:
* Checking used backend (like was provided in this mail thread)
* Listing which services should be down (i.e: ldif offline export, or
online DS with other IPA parts down)
* LDIF authentication -- is it just usual kinit? or some DS specific
parameter/command?
* What's the path of the database? (only for DS-offline export if that's
the recommended path)
* Precise commands with parameters and options for export and import
* Sanity checks before/after migration
Also:
* This howto should be published well before migration
(so it's indexed by search engines before people start searching in amok after
instances get broken)
* Most of this information is very useful for general backup/recovery in
any SOHO installation
Therefore it's best to prepare it as such and use DB switchover as an example
use-case
* A link to a preliminary draft may be published here, so we can
carefully try it and provide feedback and improvements.
(e.g: someone on this thread had an issue with finding the instance name...)
Thank you all for the hard work, it's fully understood that such a switchover
isn't trivial upgrade.
--
Oron Peled
On Tuesday, 24 June 2025 20:14:44 IDT Chris Adams wrote:
> Once upon a time, Alexander Bokovoy <[email protected]> said:
> > On Аўт, 24 чэр 2025, Chris Adams wrote:
> > >Once upon a time, Ian Pilcher <[email protected]> said:
> > >>Keeping in mind that some people won't be aware of this change before
> > >>they pull the trigger on the update from F42 -> F43, this seems like it
> > >>will render their IdM servers completely broken, with basically no path
> > >>to recover it.
> > >
> > >In the change proposal:
> > >
> > >* A new 389-ds-base-robdb-libs package implements a BerkeleyDb reader
> > >that allows exporting databases into ldif and performing the migration
> > >toward lmdb. This package should be supported until at least F45
> >
> > The reader library does not really allow for non-disruptive operation.
> > It is meant to read-only processing of existing BDB content to produce
> > an LDIF text file to load after the backend replacement. The backend
> > replacement also means that the database is not accessible until the
> > change has been completed.
>
> I was responding to the "no path to recover it" - the read-only DB tool
> allows a path to recover, with manual intervention.
> --
> Chris Adams <[email protected]>
>
--
Oron Peled Voice: +972-4-8228492
"Software is like Entropy: it's hard to grasp, weighs nothing and obeys the
Second Law of Thermodynamics, i.e. it always increases"
-- Norman Augustine
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
