- lago-devel - oVirt List Archives

[09-06-2016] New lago release - 0.21.0
by Gal Ben Haim 14 Jun '16

14 Jun '16

Hi everyone! There's a new lago release with version 0.21.0 ready for you to upgrade! Here are the changes: * Thu Jun 02 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.21.0 f28ea953: Merge pull request #272 from lago-project/show_plugin_import_exception_only_in_debug_level 6336d527: Added a callback function to handle import exception Enjoy! Gal Ben Haim gbenhaim(a)redhat.com RHEV DevOps

3 8

[Request for feedback] Adding [Docker] container support to Lago
by Jan Lieskovsky 08 Jun '16

08 Jun '16

Hello folks, since there's motivation Lago to support containers too (https://github.com/lago-project/lago/issues/149) investigated the possible ways how this could be implemented. Created a WIP PR: [1] https://github.com/lago-project/lago/pull/276 but would appreciate a wider feedback from the list prior continuing on that one. Basically I see three possibilities how [Docker] container support for Lago could be implemented: Approach 1) - Allow Lago container yaml / json init file in "docker-compose.yml" format - Use available "docker-compose" rpm to perform the underlying actions (IOW lago commands would be just wrappers around docker-compose use. E.g. lago start == docker-compose up lago stop == docker-compose down) As a part of this I have added "prefix-provider" support to lago (first commit of [1]). The intention is to define new docker-prefix for lago, which would wrap use of docker-compose, Advantage: Should be easy to implement Disadvantage: Dependency on external docker-compose RPM, which at the moment in F22 doesn't support v2 of docker-compose YAML files yet Approach 2) - allow "docker-compose.yml" as init json/yaml file for lago container configuration, - instead of using "docker-compose" create own docker lago vm provider / plugin (using python-docker-py implementation to access docker service), As part of this I have implemented support for local docker container based provider into Lago (commit 2 of [1]). Advantage: No dependency on external docker-compose RPM Disadvantate: * The need to write own docker-compose.yml file parser (AFAIK python-dockerfile-parse doesn't support parsing them [yet) * Basically we would duplicate the effort the docker-compose tool is doing right now Approach 3) - don't allow docker-compose.yml as Lago container json/yml file, - use rather format instead Advantage: No need for docker-compose.yml parser. We can define custom format, easily to be parsable. Disadvantage: Divergence from commonly used docker-compose.yml files (UX would differ as users would need to get accustomed to different format of configuration file) The question is obvious -- can you hopefully provide comments / opinion, which approach of the above do you like best and why? If having yet another one from the above ones, please share. Thank you for your opinions in advance. Regards, Jan -- Jan iankko Lieskovsky P.S.: Having agreed on an approach how this should be implemented will help us with adding vagrant support to lago too.

2 1

[02-06-2016] New lago release - 0.20.0
by David Caro 02 Jun '16

02 Jun '16

Hi everyone! There's a new lago release with version 0.20.0 ready for you to upgrade! One important change is the ability to use repoman for building the local repo, It also means that repoman is now required when installing python-lago-ovirt, repoman can be found in the following repo: http://resources.ovirt.org/repos/ci-tools/ Here are the other changes: 745e6087: Added possibility to specify ssh-user and ssh-pass on initfile 99e99b75: Detect (and report) any empty domain name possibly c7966a35: Using repoman to merge the reposync downloaded repos 7894c1d4: Added --custom-source option to reposetup 5c5199e9: Allow copying dirs in the vm For the full changelog, you can go to the docs page: http://lago.readthedocs.io/en/0.20/ Enjoy! -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro(a)redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605

1 0

[2016-05-30] Lago Weekly Meeting Minutes
by David Caro 30 May '16

30 May '16

oVirt system tests status: ========================== * 3.6 working * Master working * Image Failing due to appliance known issue (engine is not getting installed on the appliance, fabiand is on it) * New suite on it's way: Hosted engine (lev is working on it) **AI**: create a readthedocs page Last release items: ==================== Lago VM, VMProvider and Service plugins merged and released Next relase items: ================== Lago + repoman integration patch was merged, next lago release will require repoman to be available (ovirt ci-tools repo has the latest version) Installation howto effort ========================== * Installed lago on rhel 7.2 (some difficulties with the deps, probably mixed channels) * For some reason lago requires ovirtlago on start/stop Cheers!! -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro(a)redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605

1 0

Weekly bug status for ovirt-system-tests (using Lago) [ 29/05/16 ]
by Eyal Edri 29 May '16

29 May '16

FYI, Some updates from recent activity on ovirt-system-tests running on Lago. *New training videos:* overview of the framework running on Lago - https://bluejeans.com/s/9FaJ/ <https://mojo.redhat.com/external-link.jspa?url=https%3A%2F%2Fbluejeans.com%…> hands on session on installing and running OST - https://bluejeans.com/s/9Iy0/ <https://mojo.redhat.com/external-link.jspa?url=https%3A%2F%2Fbluejeans.com%…> *Open bugs:* https://goo.gl/eUaPUY *Open issues:* Work is being done to allow running OST locally per patch and on CI per merge.. more news to come soon *Open patches:* (reviews are welcome) https://gerrit.ovirt.org/#/q/project:ovirt-system-tests+status:open * Some patches are open on simplification and cleanup of the tests, should be merged this week. * This is part of preparing ovirt-system-tests to support running tests per commit. *Jenkins jobs: (STABLE!)* http://jenkins.ovirt.org/view/oVirt%20system%20tests/ 3.6 & master tests are stable and running on nightlies - please watch out for any new errors, they probably mean there is a regression! 3.6 NGN job is failing - Tolik/David - do we know what the issue is? *Recently merged patches:* https://gerrit.ovirt.org/#/q/project:ovirt-system-tests+status:merged+since… > -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

[2016-05-26] Weekly lago release 0.19.0
by David Caro 26 May '16

26 May '16

Hi everyone! A new lago release is out, this one adds the possibility to extend lago with three new plugins: * VMPlugin: Allows to modify each and every VM action, useful though when you want to extend the actions a VM can take, or customize some high level behavior (like defining a different set of artifacts to collect) We have lago.vm.DefaultVM (default), ovirtlago.virt.EngineVM (ovirt-engine), ovirtlago.virt.NodeVM (ovirt-node) and ovirtlago.virt.HostVM (ovirt-host). You can specify which one your domain belongs to with the key 'vm-type' and one of the above values, like: domains: my_domain: vm-type: ovirt-engine ... * VMProvider: Allows to implement a different set of low-level methods, like snapshot, or start/stop a vm, to allow to use different virtualization (or not) systems (only LocalLibvirtVMProvider (local-libvirt) and SSHVMProvider (ssh) are implemented right now). You can specify a custom provider for your domains with the 'vm-provider' key, like: domains: my_domain: vm-provider: local-libvirt ... * ServicePlugin: This is the class that implements the service-handling functions for a vm, starting/stopping a service, checking if the service is enabled, etc. Current implementations are SystemdService (systemd), SysVInitService (sysvinit) and SystemdContainerService (systemdcontainer). You can specify a custom service provider for your domain with the key 'service_provider': domains: my_domain: service_provider: systemd ... Another important fixed bug is that now copying a directory to a vm works :) For the latest docs and changelog you can go to the docs page: http://lago.readthedocs.io/en/0.19/ Enjoy! -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro(a)redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605

1 0

[23-05-2016] Lago weekly meeting minutes
by David Caro 23 May '16

23 May '16

23-05-2016 - Agenda * oVirt system tests status: * 3.6 working (had some storage setup timeout on one run, rerunning to try to reproduce) * Master working * Image working * Cleanup and json->yaml refactor patches: * https://gerrit.ovirt.org/57664 * https://gerrit.ovirt.org/57699 * https://gerrit.ovirt.org/57700 * https://gerrit.ovirt.org/57702 * https://gerrit.ovirt.org/57703 * https://gerrit.ovirt.org/57704 * https://gerrit.ovirt.org/57705 * https://gerrit.ovirt.org/57731 * https://gerrit.ovirt.org/57663 * https://gerrit.ovirt.org/57662 * AI: create a readthedocs page * Lago Tutorial * Splitted the docs on two sections * Getting started: In depth explanation of the tutorial same steps * Tutorial: Per-feature explanation with examples * Lago demo * Totally different project, with it’s own maintenance * Very simple introduction on how to generate the lago repos (quick tutorial) * Lago + repoman integration: * https://github.com/lago-project/lago/pull/251 * Have to think a bit how to distribute repoman (currently it’s in ovirt ci-tools repo) * Lago VM, VMProvider and Service plugins * https://github.com/lago-project/lago/pull/260 * Still working out on the documentation but is functionally complete Enjoy! -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro(a)redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605

2 2

Lago and Vagrant
by Eric Helms 22 May '16

22 May '16

I recall seeing some discussion of Lago vs Vagrant and how there could be some leverage between the two. We are currently using Lago in our release testing pipeline, however, for years now we've been using Vagrant for deploying developer and production hand-on testing environments. There are benefits to how we test and build environments to centering on a singular technology. Thus, I had a few questions I was hoping to get some thoughts on: 1) What was the outcome of the Lago vs Vagrant discussions? 2) How to reconcile the built up base of Vagrant use within our group with Lago (or how to sell switching to Lago)? 3) Do you see them as co-existing with different application points? To give an example of a disconnect where centering technology would benefit, we do an installation test currently spinning up a Lago based environment. Users testing our builds are using our existing Vagrant setup to spin up environments. However, we aren't testing the setup and configuration users are using and we end up double building the techniques for setting up environments. Thanks for any thoughts, Eric

3 2

Weekly bug status for ovirt-system-tests (using Lago) [ 22/05/16 ]
by Eyal Edri 22 May '16

22 May '16

FYI, Some updates from recent activity on ovirt-system-tests running on Lago. *Open bugs:* https://goo.gl/eUaPUY *Open issues:* Failure on DirectLun (not merged yet), actually found a blocker by a new test added by Yaniv K, see open patches [1] *Open patches:* (reviews are welcome) https://gerrit.ovirt.org/#/q/project:ovirt-system-tests+status:open * Some patches are open on simplification and cleanup of the tests, should be merged this week. * This is part of preparing ovirt-system-tests to support running tests per commit. *Jenkins jobs: (STABLE!)* http://jenkins.ovirt.org/view/oVirt%20system%20tests/ - stable for the past days. 3.6 & master tests are stable and running on nightlies - please watch out for any new errors, they probably mean there is a regression! *Recently merged patches:* https://gerrit.ovirt.org/#/q/project:ovirt-system-tests+status:merged+since… [1] *Bug 1337909* <https://bugzilla.redhat.com/show_bug.cgi?id=1337909> - NPE when trying to a direct LUN disk -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

New 0.18 version is out!
by David Caro 20 May '16

20 May '16

New lago 0.18 version is out, as the last one was done just a couple of days ago, there are not many changes, just a couple of bugfixes: * Expanding any vars on any url * Pinning down the version of yapf used For the latest docs: http://lago.readthedocs.io/en/0.18/ Cheers! -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro(a)redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605

1 0