FreeIPA nightly tests as PRs
by Petr Vobornik
Hi all,
Felipe made nightly testing working as PRs in freeipa main Git Hub repo.
e.g.:
https://github.com/freeipa/freeipa/pull/1624
https://github.com/freeipa/freeipa/pull/1623
This is good. We can see the results publicly in comparison to
"upstream Jenkins". I also believe that it will be more stable. But
time will tell it. A disadvantage is more noise in mail notifications,
but that is not that drastic.
Let's discuss some aspects. First one is definitions of the tests
(.freeipa-pr-ci.yaml) and how to extend them.
We currently use 3 definitions:
* gating, the definition in repo
* nightly master tests
* nighly rawhide tests
Gating definition is in repo. But both nightly are not.
What is the way how other team members can extend this definition?
Where are they kept?
Could we also put them into a repo?
What about the following solution:
1. create a directory with tests definitions, e.g. /ipatests/definitions
2. put these 3 files there
- gating
- nightly_master
- nightly_rawhide
3. make .freeipa-pr-ci.yaml a symlink to /ipatest/definitions/gating
4. for nightly testing do PR which would change only the symlink
Benefits:
- anybody can extend nightly test suite
- the nighlty test suite can be extended right away in a PR which adds the tests
- nightly tests won't fail on merge conflict when somebody extends
current gating spec
Possible alternative is to make it more complex and use something like
includes instead of symlinks, but that would need update of PR-CI and
I don't see a real benefit in comparison to the symlink solution.
--
Petr Vobornik
6 years, 1 month
FreeIPA developement good practices
by Florence Blanc-Renaud
Hi all,
in order to promote good development practices, I would like to write a
wiki page stating FreeIPA expectations and helping contributors to
remain on track (or extend the Contribute/Code wiki page).
The topics include a description explaining our use of the tools (such
as github, pagure etc), but also general development habits that
everyone should enforce.
A draft is available below for your comments/suggestions.
Thanks,
Flo
6 years, 1 month
IPA's NTP service
by Tibor Dudlák
Hello FreeIPA-devel list fellow beings!
I would like to continue the discussion started in [1], and find its
solution.
While using the Single-Sign-on authentication provided via an MIT Kerberos
KDC there must not be any significant clock skew between server and
clients so a time synchronization service is required.
Red Hat Enterprise Linux is about to deprecate ntpd service and will
support chronyd instead. This will happen in release 8 and by this time we
should agree on some changes in IPA - whether to remove or replace the already
used ntpd service. I would like to sum up this change in a design page but
there should be an agreement first.
IPA, as is, checks the system configuration and if there is an NTP service
configured and running then it forces ntpd, meaning it disables any other
NTP service. It also alters its configuration, and restarts the NTP service
instance.
We may now want to consider, as the time sync service change is required,
to NOT configure a service that is not a part of the identity management
such as NTP, and leave it to system/IPA administrators.
IPA install script may only check wheter there is an NTP service running
and if not, it would ask the administrator to configure it before the IPA
installation.
Upgrade of IPA might be more complicated because there will be the ntpd
service entry in LDAP, and the service will be up and running. I would
suggest that we do not remove any working ntpd service already configured
but only disown it from IPA's LDAP tree.
I will be glad for any input from you people and hopefully there will be an
acceptable solution for this soon :)
Thanks!
[1]
https://www.redhat.com/archives/freeipa-devel/2016-November/msg00807.html
--
Tibor Dudlák
Identity management - FreeIPA
Brno, TPB-C, 2C407
Red Hat
6 years, 1 month