Red Hat Bugzilla – Bug 1279962
Allow using rpms from anywhere too, not only yum repos
Last modified: 2016-01-26 04:15:06 EST
Description of problem:
For example, from a dir or similar, using repoman probably to fetch them and compose the repo that will be passed onto the vms
Version-Release number of selected component (if applicable):
Steps to Reproduce:
How will the CLI/API UX for this look like? How does it compare to current CLI/API?
Still to be define, but as a first step, adding an option to reposetup to specify any repoman source is a must imo:
lago reposetup --extra-source dir:path/to/my/custom/rpms
I'd also remove the vdsm/engine/ioprocess specific options and associated code, and if needed, do that in another cli verb (like build or similar), but that's another issue
does this bug includes consuming rpms from a workflow or previous job that will generate rpms per patch/commit?
Not so specifically, but will allow to use any rpms on disk or remotely, what opens the possibility to reuse whatever build-artifacts builds (allowing that flow) but also any other flow that get's you some rpms
Moved to https://github.com/lago-project/lago/issues/31