On Sat, Jan 19, 2019 at 5:10 AM Dan Kenigsberg
<danken(a)redhat.com> wrote:
> On Sat, 19 Jan 2019, 9:34 Pooja Pandey <pooja.pandey(a)msystechnologies.com
> wrote:
>
>> Hi Dan,
>>
>> Thankyou so much for the reply.I really appreciate your quick response on
>> this.
>>
>> I have one more query==>
>>
>> Can we run OST with the ovirt source code if I want to run on any Hyper
>> converged system?
>>
>
> I'm not sure that I'm answering your question, but...
>
> Unfortunately, in OST we have a tight coupling between the provisioning
> tool (Lago) and the tests.
>
> It is possible to decouple them in order to run the tests (minus oVirt
> deployment test) on an existing system. +Eitan used to have a private patch
> for that (limited to the network suite). Finishing it would require some
> effort from you.
>
>> Also not sure I'm answering your question, specifically re "on any
hyperconverged system" -- ?
But this might help:
https://ovirt.org/blog/2016/12/ci-please-build.html
^ that allows us to build rpms from code (an existing gerrit patch), which
we can then feed to OST. We do this in Jenkins quite frequently -- if you
want to do something like this outside of Jenkins, that's probably
possible. I guess you would just have to feed it your rpms, perhaps the
same way it's done in Jenkins, but I'm not sure.
Yes, it's possible to give a local or another repo to -s option of
run_suite.sh. You can put your rpm's somewhere, run `createrepo' on the
given directory and pass it to `run_suite.sh -s'.