[389-users] NSX/F5 Load Balancing Health Checks
Hi: At the moment we perform TCP health check via F5 on ports 389/636 (historical inheritance) – which isn’t sufficient for HA. We are moving to an env where NSX and F5 may co-exist – and have an opportunity to re-work the LB health check for HA (on existing F5 and upcoming NSX). If running NSX and/or F5 (or other load balancers) – how do you determine health on ldap node? We have 2 read/write (1 active at given time) – replicating to N read-only nodes. ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@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.fedoraproject.org
[389-users] Re: Docker official image
>From my understanding readiness operates when the pod starts. If it doesn't reach the replica your pods will never initialize. An option (for k8s) can be another container (in the pod) "389-ds-headless" which will do all the steps required to enable replication. > Okay - how does the content of secrets.yaml get sent to the process running in the container? By files or by variables but are always present in the container. To enable replicas , k8s provides StatefullSet controller which is better to manage multiple instances/replication. Regards Le lun. 17 juin 2019 à 13:57, aravind gosukonda a écrit : > > > > Is there also a way in k8s that when an event occurs (IE a new container > is launched in a > > pod) that a program can be called in existing containers? (This way we > can automate > > replica addition/removal) > > > What I'm planning to do is to use readiness probes, which can be scripts, > to handle dynamic configuration of replicas. I haven't seen any way that > enables existing containers to know when a new container has been launched > or an old container deleted. > > Regards, > Aravind G > ___ > 389-users mailing list -- 389-users@lists.fedoraproject.org > To unsubscribe send an email to 389-users-le...@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.fedoraproject.org > ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@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.fedoraproject.org
[389-users] precreation nss databases
hi, I'm still evaluating some options to securize dynamic nodes and I have some questions regarding certutil and nss databases: Can I create NSS databases on any directory/server and then move files to "/etc/dirsrv/slapd-instance_name" ? If cert8.db and key3.db files are found in that directory are they used automatically by slapd process on reboot? If both answers are affirmative I'll try to script it and hook it within my node creation flow. is there any other detail I should take care of with this approach? thanks, abosch -- ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@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.fedoraproject.org
[389-users] Re: Docker official image
> > Is there also a way in k8s that when an event occurs (IE a new container is > launched in a > pod) that a program can be called in existing containers? (This way we can > automate > replica addition/removal) > What I'm planning to do is to use readiness probes, which can be scripts, to handle dynamic configuration of replicas. I haven't seen any way that enables existing containers to know when a new container has been launched or an old container deleted. Regards, Aravind G ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@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.fedoraproject.org
