4:11 a.m.
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.
I tried Fedora 29, there is 1.4.0.21-1.fc29 and it works... somehow.
Schema editation is possible. But database management is broken, it
shows two suffixes dc=example,dc=com and o=ipaca.com which are not
present in 389-ds configuration dse.ldif file. And it is unable to
detect defined suffix. It looks nice, but it seems that many things
might not be working even on Fedora.
Is it possible to manage 389-ds 1.4.x with 389-admin 1.1.46 and
389-admin-console 1.1.12-5.fc29? This is combination Fedora 29 come with.
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?
Thanks for responses
[1]
https://packages.debian.org/search?keywords=389-admin&searchon=names&...
--
-----------------------
Jan Tomasek aka Semik
http://www.tomasek.cz/
8:46 a.m.
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.
I tried Fedora 29, there is 1.4.0.21-1.fc29 and it works... somehow.
Schema editation is possible. But database management is broken, it
shows two suffixes dc=example,dc=com and o=ipaca.com which are not
present in 389-ds configuration dse.ldif file. And it is unable to
detect defined suffix. It looks nice, but it seems that many things
might not be working even on Fedora.
Yeah, so you are looking at "sample" data in the database tab. However,
in 1.4.0.22-1 the database management tab is now complete! That release
is currently in testing, please see the email on this list with the
subject: "Announcing 389 Directory Server 1.4.0.22", you will find
links to the builds, etc. Try it out.
Is it possible to manage 389-ds 1.4.x with 389-admin 1.1.46 and
389-admin-console 1.1.12-5.fc29? This is combination Fedora 29 come with.
Yes, and
it will work in Fedora 30 as well, but come Fedora 31 the old
standalone java UI will be removed.
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).
Regards,
Mark
> Thanks for responses
>
> [1]
>
https://packages.debian.org/search?keywords=389-admin&searchon=names&...
>
7:03 p.m.
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
10 a.m.
Hi Mark,
On 4/2/19 3:46 PM, Mark Reynolds wrote:
> 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.
>...
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.
In fact, it is possible to install Cockpit on Debian Buster, it just
isn't present in the minimal installation. It wasn't working for me, I
will give it another try and send a bug report as Timo Aaltonen ask in
some later email. I need to verify first, I never heard about Cockpit
before.
I expect/hope the new Cockpit UI will be 100% complete in the next
two
months (hopefully sooner).
It looks very nice, I will monitor this mailing list more closely.
Thanks for your work.
--
-----------------------
Jan Tomasek aka Semik
http://www.tomasek.cz/
7:05 p.m.
On 4 Apr 2019, at 01:00, Jan Tomasek <jan(a)tomasek.cz> wrote:
It looks very nice, I will monitor this mailing list more closely. Thanks for your work.
Thank you! Everyone has done a lot to make this happen. If you have any other questions,
feedback, or requests, please let us know. We’d love to help.
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs
1:43 a.m.
On 2.4.2019 12.11, 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.
File a bug on the Debian bugtracker then, I'm not aware of any bugs there.
--
t
1846
days inactive
1848
days old
389-users@lists.fedoraproject.org
5 comments
4 participants
participants (4)
-
Jan Tomasek -
Mark Reynolds -
Timo Aaltonen -
William Brown