On 2 Apr 2019, at 23:46, Mark Reynolds <mreynolds(a)redhat.com>
wrote:
Hi Jan,
On 4/2/19 5:11 AM, Jan Tomasek wrote:
> Hi,
>
> I'm preparing migration from 389 DS 1.2.5. I'm using single master and 4
> replicas all on RedHat which I would like to abandon in favor Debian
> which is my main platform.
>
> My idea was to use 389-ds 1.4.x line on Debian/Buster, but there is
> completely missing 389-admin package [1]. They ship cockpit-389-ds
> 1.4.0.21-1 which completely doesn't work on Debian. It declares that
> 389-ds-base isn't installed. It is installed and configured.
Well the cockpit UI plugin is not finished yet (but we are VERY close to wrapping it
up).
And as I have mentioned multiple times on this mailing list the 389-admin/console
packages are deprecated and will completely removed in Fedora 31. So I am afraid on
Debian and other platforms that do not have "Cockpit" there will not be any kind
of UI.
Well, we have a much more extensive CLI toolset, so that is our command line UI if you
look at it that way, and that will be available on all platforms ….
>
> Or is it safer to stick with 389-ds 1.3.x which is shipped with RHEL 7 &
> Debian/Stretch? And use 389-admin & 389-console for managing them?
Well like I said the new Cockpit UI is almost done, in 1.4.0.22 the only tabs that are
"not" working are the Monitoring tab (which I will finish this week) and the
"Security tab" - everything else is working now.
I expect/hope the new Cockpit UI will be 100% complete in the next two months (hopefully
sooner).
If you have any feedback or issues too, we’d love to know so we can improve the system.
Thanks!
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs