Re: Questions about kernelCI tools

Hello 林 拓真,

1. I guess it is about KCIDB, we have it planned. We totally get why
having a fully self-hosted KernelCI setup would be useful, especially
for teams looking to avoid external dependencies like Google Cloud.

Making KernelCI self-hosted is definitely on our roadmap. The good news
is that we’ve already started thinking about it, but with the number of
features we’re juggling and the small team we have, it’s taking us some
time to get there. For example one of features we are working on, is
making storage backend more "cloud-independent-friendly".

That said, we’d love to hear more about what’s most important to
you—whether it’s prioritizing the self-hosted aspect or any other
features. If there’s interest in collaborating or sponsoring certain
areas, it could really help speed things up.

2.Thank you for report, yes it is a bug, likely appeared during our
latest pydantic upgrade.
I opened issue and will try to fix it this or max next week, as it is
critical for user management bug.
https://github.com/kernelci/kernelci-api/issues/589
You can follow issue to see when it is fixed.


On Thu, 2024-12-12 at 04:29 +0000, 林 拓真 wrote:
> Hello community.
> 
> I am currently trying to run LTP test on LavaLab with Maestro and
> KCIDB.
> Also have currently considered building all modules of KernelCI "on-
> premise".
> then I have two questions about the way I am trying.
> 
> Question 1：
> Is it possible to get rid of the dependency on GoogleCloud?
> (So I am looking for the right way to build KernelCI on-premise more
> quick and easier…)
> 
> Question 2：
> I encountered the error below while trying to build Maestro and,
> trying to get the API access token for connecting to the kernelci-api
> container from the pipeline.
> Following steps here I have tried: (Referred to
> https://docs.kernelci.org/admin/api/)
> ----------------------------------------------------------
> Step 1. Run bash in the kernelci-api container.         
> $ docker exec ?it kernelci-api /bin/bash
> 
> Step 2. Create an administrator within the api app.
> $ python3 ?m api.admin ?email “<administrator-mail-address>”
>    (trapped) error reading bcrypt version
>    Traceback (most recent call last):
>    File "/usr/local/lib/python3.11/site-
> packages/passlib/handlers/bcrypt.py", line 620, in
> _load_backend_mixin
>    version = _bcrypt.__about__.__version__
>                            ^^^^^^^^^^^^^^^^^
>    AttributeError: module 'bcrypt' has no attribute '__about__’
>    Creating admin user...
> 
> This above error I encountered does not seem to be fatal as far as I
> read the KernelCI implementation.
> then I went to the next step.
> 
> 3. Obtain the token of the administrator in the api app.
> $ kci user token admin
> Error: KerError: Value not found for None
> ----------------------------------------------------------
> Is there any missing steps I should do before?
> 
> Thank you.
> Hayashi
>