lago
lago copied to clipboard
lago-project
Ad-hoc virtual testing environment framework
Creating RPM compatible ChangeLog Traceback (most recent call last): File "scripts/version_manager.py", line 10, in import dulwich.repo ImportError: No module named dulwich.repo Failed to generate RPM ChangeLog Makefile:18: recipe for target...
Initial PR: https://github.com/lago-project/lago/pull/576 Other stuff left to move: - [ ] network templates - [ ] snapshot templates At first stage they can be just the same with simple replacements....
It relays on the ENV variable 'LAGO_PREFIX_PATH' which is hard coded in the virt JSONs, and is later passed to libvirt in the disks path. We need to remove that...
Moved from https://bugzilla.redhat.com/show_bug.cgi?id=1272034 Those two dirs tend to be very large in size and files may collide between projects Not everybody has free 20GB on their / dir They should...
commit 7be0dac947352cad8c96c6cd6c48390390a01344 [ykaul@ykaul lago]$ make rpm LAGO_VERSION=0.39.32 python2 setup.py sdist --dist-dir /home/ykaul/github/lago/dist ERROR:root:Error parsing Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/pbr/core.py", line 111, in pbr attrs = util.cfg_to_args(path, dist.script_args) File...
Looking at the logs what happened was: 1. Lago checked the engine was SSH reachable - this was true. 2. Then it tried connecting via SSH and collect the logs...
1. Using pip installation. 2. Can be done in nested VM. 3. Upgrading should be tested also. 4. CLI and SDK tests are required (We can recycle our existing tests).
Initial work: http://lago.readthedocs.io/en/stable/LagoInitFile.html
If the images are already cached, there is no need to require network connection on `init`. Currently, when running `init`, lago's default action is to try to download the repo...