[ldv-project] Launching Klever

[A. Celenk]

Hello Evgeny,

Thank you very much for Klever, and for your help. I will be eagerly 
waiting for 2.0 release. Till then, I may try to use the current version 
to learn some basics. Here is what I have done:

I could reach the web interface and managed to login as manager, and 
played around a little bit. Considered the warning on the deployment 
tutorial about messing up the computer, I have installed Klever on a 
Ubuntu 18.04 VM. Being a VM, it has low resources. I have started the 
preset Linux 3.14 job with default configurations and got "Given 
resource limits for job and tasks in sum are too high, we do not have 
such amount of resources" error. Then I have checked out manual 
configuration and used "paranoid development" preset configuration, and 
lowered the resources as much as I can (see my attached configuration). 
Nevertheless I am still getting the same error and it fails.

Here are my questions for the current release; if answers would greatly 
change for v2.0, just ignore these and I will be waiting for the new one:

     - Is it fine to use Klever in such a low-resourced VM? If so, what 
my configurations should be? If not, what are the minimum system 
requirements for Klever?
     - How do I upload a new job (e.g. just a single C file, or a 
project with makefile)?

Thank you again,

Regards,

Ahmet


On 16-10-2018 18:00, Evgeny Novikov wrote:
> Also, I would like to inform you that in a couple of weeks we will 
> release Klever 2.0 that will change very many things related with core 
> functionalities. If you have time, then I recommend to wait for this 
> release and try it rather than a version that will be deprecated soon.
>
> 16:08, 16 октября 2018 г., Evgeny Novikov <novikov at ispras.ru>:
>
>     16.10.2018, 13:55, "Evgeny Novikov" <novikov at ispras.ru
>     <mailto:novikov at ispras.ru>>:
>>     Hello Ahmed,
>>     Your question is absolutely right. Klever lacks user
>>     documentation and I think that it will not have it in a near
>>     future. So, if you would like to proceed, most likely you will
>>     have many questions.
>>     You shouldn't run any script to start Klever if deployment was
>>     successful. You just need to open localhost:8998 in your web browser.
>
>     I forgot to mention that there are 3 users created in advance:
>
>       * The first one is Administrator (login: admin, password: admin)
>         that can change user privileges. Most likely you will not need
>         it unlike you are going to create a multiuser setup.
>       * The second one is Manager (login: manager, password: manager).
>         This user can almost everything and you should start with it!
>       * The third one is Service user that serves for internal purposes.
>
>>     If you will have any other questions, please, ask us. We will be
>>     glad to get some feedback from you.
>>     -- 
>>     Evgeny Novikov
>>     Linux Verification Center, ISP RAS
>>     http://linuxtesting.org <http://linuxtesting.org/>
>>     16.10.2018, 11:14, "A. Celenk" <ahmet.celenk at procenne.com
>>     <mailto:ahmet.celenk at procenne.com>>:
>>>
>>>     Hello,
>>>
>>>     I will ask a dumb question: How do we run Klever? I've completed the
>>>     deployment; but couldn't figure out which python script (or some
>>>     other
>>>     thing) should I run to start testing.
>>>
>>>     P.S: I've used example klever-minimal.json.sample as
>>>     configuration file.
>>>
>>>     Thanks a lot,
>>>
>>>     Ahmet Celenk
>>>
>>>
>>>     _______________________________________________
>>>     ldv-project mailing list
>>>     ldv-project at linuxtesting.org <mailto:ldv-project at linuxtesting.org>
>>>     http://linuxtesting.org/cgi-bin/mailman/listinfo/ldv-project
>>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxtesting.org/pipermail/ldv-project/attachments/20181017/f27d793a/attachment.html>
-------------- next part --------------
{
    "allow local source directories use": true,
    "collect total code coverage": true,
    "generate makefiles": true,
    "identifier": "d7ddc2ab1a56b9599fd7c80f6206150e",
    "ignore failed sub-jobs": true,
    "ignore other instances": true,
    "keep intermediate files": true,
    "logging": {
        "formatters": [
            {
                "name": "formatter1",
                "value": "%(asctime)s (%(filename)s:%(lineno)03d) %(name)s %(levelname)5s> %(message)s"
            },
            {
                "name": "formatter2",
                "value": "%(asctime)s (%(filename)s:%(lineno)03d) %(name)s (%(process)d) %(levelname)5s> %(message)s"
            }
        ],
        "loggers": [
            {
                "handlers": [
                    {
                        "formatter": "formatter1",
                        "level": "INFO",
                        "name": "console"
                    },
                    {
                        "formatter": "formatter2",
                        "level": "DEBUG",
                        "name": "file"
                    }
                ],
                "name": "default"
            }
        ]
    },
    "max solving tasks per sub-job": 1,
    "parallelism": {
        "Build": 1,
        "Results processing": 1,
        "Sub-jobs processing": 1,
        "Tasks generation": 1
    },
    "priority": "IDLE",
    "resource limits": {
        "CPU model": null,
        "disk memory size": 500000000,
        "memory size": 500000000,
        "number of CPU cores": 1
    },
    "task scheduler": "Klever",
    "upload input files of static verifiers": true,
    "upload other intermediate files": true,
    "weight": "0"
}