4:49 p.m.
Hello,
I am in the process of building my own container containing ds-389, using this docker file
as the initial guidance ->
https://build.opensuse.org/package/view_file/home:firstyear/389-ds-contai...
(and using /usr/lib/dirsrv/dscontainer to bootstrap the image and bring up the container)
I am having a think about the upgrade process for this instance. If I am storing the
schema/relevant files on persistent storage, will /usr/lib/dirsrv/dscontainer be smart
enough to upgrade the backend on startup if I have built a new container with a new
version of ds-389? In the past, I beleive the installer RPM's were running perl/python
scripts to perform backend updates.
I THINK it is, but I can't find anything definitive.
Any help is appriciated.
Cheers,
Steve
5:39 p.m.
On 6 Jan 2022, at 08:49, Steve F <steve.falzon(a)outlook.com>
wrote:
Hello,
I am in the process of building my own container containing ds-389, using this docker
file as the initial guidance ->
https://build.opensuse.org/package/view_file/home:firstyear/389-ds-contai...
(and using /usr/lib/dirsrv/dscontainer to bootstrap the image and bring up the container)
I am having a think about the upgrade process for this instance. If I am storing the
schema/relevant files on persistent storage, will /usr/lib/dirsrv/dscontainer be smart
enough to upgrade the backend on startup if I have built a new container with a new
version of ds-389? In the past, I beleive the installer RPM's were running perl/python
scripts to perform backend updates.
I THINK it is, but I can't find anything definitive.
Yes, it is smart enough to upgrade on startup. Provided you mount your persistent storage
in the same location, it will do all the upgrading for you :)
It's actually the dirsrv binary itself that does the upgrade, dscontainer just knows
how to launch it.
Hope that helps!
Any help is appriciated.
Cheers,
Steve
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
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/389-users@lists.fedoraproje...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
--
Sincerely,
William Brown
Senior Software Engineer, Identity and Access Management
SUSE Labs, Australia
6:24 p.m.
Perfect, thankyou so much! 🙂
________________________________
From: William Brown <william.brown(a)suse.com>
Sent: Thursday, January 6, 2022 10:39 AM
To: 389-users(a)lists.fedoraproject.org <389-users(a)lists.fedoraproject.org>
Subject: [389-users] Re: Upgrading Containerized ds-389
On 6 Jan 2022, at 08:49, Steve F <steve.falzon(a)outlook.com>
wrote:
Hello,
I am in the process of building my own container containing ds-389, using this docker
file as the initial guidance ->
https://build.opensuse.org/package/view_file/home:firstyear/389-ds-contai...
(and using /usr/lib/dirsrv/dscontainer to bootstrap the image and bring up the
container)
I am having a think about the upgrade process for this instance. If I am storing the
schema/relevant files on persistent storage, will /usr/lib/dirsrv/dscontainer be smart
enough to upgrade the backend on startup if I have built a new container with a new
version of ds-389? In the past, I beleive the installer RPM's were running perl/python
scripts to perform backend updates.
I THINK it is, but I can't find anything definitive.
Yes, it is smart enough to upgrade on startup. Provided you mount your persistent storage
in the same location, it will do all the upgrading for you :)
It's actually the dirsrv binary itself that does the upgrade, dscontainer just knows
how to launch it.
Hope that helps!
Any help is appriciated.
Cheers,
Steve
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
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/389-users@lists.fedoraproje...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
--
Sincerely,
William Brown
Senior Software Engineer, Identity and Access Management
SUSE Labs, Australia
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
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/389-users@lists.fedoraproje...
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
835
days inactive
836
days old
389-users@lists.fedoraproject.org
2 comments
3 participants
participants (3)
-
Steve F -
Steven Falzon
-
William Brown