and as Milan mentioned, you can also test on your own custom built rpms
which is detailed here:
On Mon, Jan 21, 2019 at 11:30 AM Milan Zamazal <mzamazal(a)redhat.com> wrote:
Greg Sheremeta <gshereme(a)redhat.com> writes:
> On Sat, Jan 19, 2019 at 5:10 AM Dan Kenigsberg <danken(a)redhat.com>
>> On Sat, 19 Jan 2019, 9:34 Pooja Pandey <
>>> Hi Dan,
>>> Thankyou so much for the reply.I really appreciate your quick response
>>> 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
>> 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:
> ^ that allows us to build rpms from code (an existing gerrit patch),
> 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'.
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: