On Mon, Mar 14, 2022 at 10:01:46AM +0000, Richard W.M. Jones wrote:
On Mon, Mar 14, 2022 at 09:18:04AM +0000, Daniel P. Berrangé wrote:
> On Sat, Mar 12, 2022 at 10:50:21AM +0000, Richard W.M. Jones wrote:
> > Am I doing this wrong? [see log below] This is using the upstream
> > libvirt-ci checked out just now from gitlab, but it seems as if nbdkit
> > has to be listed as a project under that repo.
> >
> > "./lcitool projects" shows libnbd but not nbdkit.
>
> Indeed, there's only libnbd there. Presumably nbdkit is something
> Martin hasn't got around to adding ?
>
> With recentish changes though there's no longer any need to add
> projects directly to libvirt-ci.git. They can be kept locally
> in the project eg
>
> nbdkit.git/ci/projects/nbdkit.yml
>
> then use 'lcitool --data-dir ci' and it'll find the nbdkit.yml
> when searching for projects.
>
> libvirt-ci.git will only need modifying it distro package
> mappings need additions/changes.
I copied libvirt-ci.git/guests/lcitool/lcitool/ansible/vars/projects/libnbd.yml
to ci/projects/nbdkit.yml. I'll probably have to adjust the packages
in that file, but it did allow me to re-run the command above and
regenerate the templates.
Martin - I guess you must have created that nbdkit.yml file at some
point, but I can't find it in your fork.
> > A second question, since the libvirt-ci project does a bunch of stuff
> > with ansible & containers, regenerating the files like this doesn't
> > require ansible & containers? (I don't want to run those on my
> > development machine.)
>
> ansible is only used when managing VMs, no need for it with containers.
I meant would the "manifest" subcommand do anything weird (ie. not
just updating the templates), but it seems fine.
Yep, the manifest command doesn't do anything with VMs or ansible.
Regards,
Daniel
--
|:
https://berrange.com -o-
https://www.flickr.com/photos/dberrange :|
|:
https://libvirt.org -o-
https://fstop138.berrange.com :|
|:
https://entangle-photo.org -o-
https://www.instagram.com/dberrange :|