6:35 a.m.
Did you run 'lago init', and 'lago start' before running 'lago
deploy'?
I missed `lago start` (its hard to find decisive commands across a single
source of documentation, but that will very likely solve my issue). I was
running
lago init
lago ovirt reposetup --reposync-yum-config reposync-config.repo
lago deploy
I think the 'demo tool' feature might be working for basic suite already as
I mentioned, but its not official/standardize yet, we're working
on it
currently and it will have stanard
build / deploy flow which will allow to consume it in a much easier
fashion.
Admittedly most of my issues have been largely due to deciphering
commands/etc from misc docs and jenkins configs. Most things have worked
very easily after figuring out the little details, but Im happy to try out
the demo tool.
On Tue, Sep 19, 2017 at 1:41 AM, Eyal Edri <eedri(a)redhat.com> wrote:
On Tue, Sep 19, 2017 at 9:05 AM, Barak Korren <bkorren(a)redhat.com> wrote:
> On 19 September 2017 at 06:35, Marc Young <3vilpenguin(a)gmail.com> wrote:
> >
> > Is there a lago command I'm missing/some sort of configuration change
> needed
> > that I'm missing to run the lago commands manually?
> > I've been trying to piece together the manual commands from
> run_suite.sh but
> > I dont see it doing anything that I'm outright missing.
> >
> Did you run 'lago init', and 'lago start' before running 'lago
deploy'?
>
> You'd probably see these SSH errors if you just run 'lago deploy'
> after 'lago init' because the VMs are not up yet.
>
> You'll also need to run 'lago ovirt reposetup ...' to make OST deploy
> work, and the parameters you need to pass it may not be trivial.
>
> Practically, just removing the test scenarios you don't need would
> probably be much easier.
>
> As Eyal mentioned before, we're working on 'demotool' which will allow
> you to download a full working oVirt Lago environment.
>
Adding Gal,
I think the 'demo tool' feature might be working for basic suite already
as I mentioned, but its not official/standardize yet, we're working on it
currently and it will have stanard
build / deploy flow which will allow to consume it in a much easier
fashion.
You can try it and see if it helps your need, try the following:
1. Run the manual job [1] and tick the 'create images' option on job
parameters ( also provide link to custom yum repo / jenkins job with RPMs
you want to test if you have any )
2. Once the job is done, download the tar.gz file
3. Follow the intructions on [2], though there might be issues since its
not official yet, but it basically comes down to:
- tar -xzvf $your_image.tar.gz
- lago init ( inside the lago workdir when you opened the files )
- lago ovirt start --with-vms
- lago status or lago ovitrt status should show if the VMs are up
Now you have a running oVirt env, which run all the tests in the basic
suite, so you can try and use it or run api calls against it.
Maybe use lago shell to connect to the one of the VMs if you need, etc...
[1] http://jenkins.ovirt.org/view/oVirt%20system%20tests/
job/ovirt-system-tests_manual/ ( this only helps if the suite passes w/o
errors )
[2] https://docs.google.com/document/d/1MZdpHAjNWlpPFhOXFfMavZbg6Kh38
6PRBg6jG6xslao/edit
>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
>
>
--
Eyal edri
ASSOCIATE MANAGER
RHV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
phone: +972-9-7692018 <+972%209-769-2018>
irc: eedri (on #tlv #rhev-dev #rhev-integ)