#4491 Investigate utilizing lib389
Closed: fixed Opened by mkosek.

FreeIPA implements many DS management tasks (creating replication agreements, updating configuration, ...). We should investigate whether the set of operations we do could be ported to 389's lib389 and thus both simplify FreeIPA code and let others use the shared functionality.

We need to start with defining operations we would like to delegate to lib389 and then check the gaps in lib389 (and create 389 ticket). When the gap is small enough, we could do the switch.


Current design of lib389 is available on http://port389.org/wiki/Upstream_test_framework

Stretch goal in 4.2.

This ongoing task is assigned to Thierry.

Processing leftovers from 4.2 backlog - this ticket was found as suitable for consideration in next big feature release - 4.4.

Metadata Update from @mkosek:
- Issue assigned to tbordaz
- Issue set to the milestone: FreeIPA 4.5 backlog

Done in PR https://github.com/freeipa/freeipa/pull/2312

master:

f7511ed Support the 1.4.x python installer tools in 389-ds
8f9b0fc Remove some basic pystyle and pylint errors
383311a Don't try legacy installs
ed955d1 Move lib389 imports to module scope
56f8e20 DS uninstall: fix serverid missing in state restore
104ef41 DS install: fix DS asking for NSS pin during install
e8342d4 DS install: don't fail if SSL already configured
8fb6396 Use the newer way of removing the DS instance
a606b44 Drop dependency on 389-ds-base-legacy-tools
d39bb65 Remove DS perl paths from debian platform

Metadata Update from @rcritten:
- Issue close_status updated to: fixed
- Issue set to the milestone: FreeIPA 4.8 (was: FreeIPA 4.5 backlog)
- Issue status updated to: Closed (was: Open)

master:

  • 9b90ebf4c33e5c4ff4068d557521f8718ec62a36 Remove 389-ds templates now that lib389 is used for installs
Metadata