xapi-project / xen-api
80%
master: 80%

LAST BUILD BRANCH: gh-readonly-queue/master/pr-6684-39b166a5e370280fdfad82cd25afd9c202c34a87
DEFAULT BRANCH: master
Repo Added
Files 34
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH gh-readonly-queue/master/pr-6609-09953c302b813fd6dca6ee576cbe5966d6f0fb05
branch: gh-readonly-queue/master/pr-6609-09953c302b813fd6dca6ee576cbe5966d6f0fb05
CHANGE BRANCH
x

coverage: 80.345%. Remained the same
16691444613

push

github

web-flow 
CA-414418: Sessions do not got destroyed after domain  user been removed and performance improvement (#6609)

```
commit 92377bfe2 (HEAD -> private/linl/CA-414418, origin/private/linl/CA-414418)
Author: Lin Liu <Lin.Liu01@cloud.com>
Date:   Thu Jul 31 07:25:30 2025 +0000

    CA-414418: Perf: save user validate result and apply to sessions

    For all sessions created by external/AD users, session revalidate
    will check whether the users are still acitve, and kick off the
    session accordingly.

    However, xapi check the user for every session. The problem here
    is lots of session are created by only a few users. (for the case
    of CVAD and ControlUP). This would cause lot of duplicated check
    for the same user again and again, which is slow and waste lots
    of resources.

    To fix the issue, [(user_sid, check_result)] is defined for every
    round of check. The check result is saved so later check for the
    session with same user can just be applied.

    Signed-off-by: Lin Liu <Lin.Liu01@cloud.com>

commit b0e2b5bfd
Author: Lin Liu <Lin.Liu01@cloud.com>
Date:   Thu Jul 31 06:17:32 2025 +0000

    CA-414418: Detection of AD account removal does not cause logout

    For performance, during revalidate existing sessions, xapi query
    subject details from xapi db first, if the subject is suspend,
    then goes to AD, to make sure unblocked user can login.

    There is a backend thread to update xapi db subject information
    from AD. However, it can not handle the case that the subject
    is removed. (and should not remove the subject for user until
    user remove it explictly). Thus, the subject information is not
    updated and keep alive.

    In this case, subject revalidate always got session not suspend
    from xapi db.

    The issue is fixed by query subject information from AD direclty,
    and session revalidate thread handle the removed subject proper... (continued)

3491 of 4345 relevant lines covered (80.35%)

0.8 hits per line

Relevant lines Covered
4345 RELEVANT LINES 3491 COVERED LINES
0.8 HITS PER LINE
Source Files on gh-readonly-queue/master/pr-6609-09953c302b813fd6dca6ee576cbe5966d6f0fb05

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
16691444613 gh-readonly-queue/master/pr-6609-09953c302b813fd6dca6ee576cbe5966d6f0fb05 CA-414418: Sessions do not got destroyed after domain user been removed and performance improvement (#6609) ``` commit 92377bfe2 (HEAD -> private/linl/CA-414418, origin/private/linl/CA-414418) Author: Lin Liu <Lin.... push web-flow github
80.35
16691444576 gh-readonly-queue/master/pr-6609-09953c302b813fd6dca6ee576cbe5966d6f0fb05 CA-414418: Sessions do not got destroyed after domain user been removed and performance improvement (#6609) ``` commit 92377bfe2 (HEAD -> private/linl/CA-414418, origin/private/linl/CA-414418) Author: Lin Liu <Lin.... push web-flow github
80.35
See All Builds (6016)