Per cloud-init, I think that's doable. I added support for cloud-init so
Ill see if that can get me going on an easy path.
Per uploading: I'm not sure. This might be pretty complex. Vagrant has a
concept of boxes (for non local files its usually just a zip folder with a
metadata manifest) [1] and uploading to their cloud platform atlas [2] but
that kind of gets outside the realm of Vagrant and more into the niche that
Packer[3] fits.
There has been some work on packer with qemu[4] but not oVirt so possibly
thats a good place for another project to fit (ovirt packer provider)
[1]
https://github.com/myoung34/vagrant-ovirt4/tree/master/example_box
[2]
https://www.vagrantup.com/docs/boxes.html
[3]
https://www.packer.io/
[4]
https://www.packer.io/docs/builders/qemu.html
On Thu, Aug 24, 2017 at 8:17 AM, Barak Korren <bkorren(a)redhat.com> wrote:
On 24 August 2017 at 15:35, Marc Young <3vilpenguin(a)gmail.com>
wrote:
>
> Vagrant requires coming up from a template (and a modified one at that
[1].
I was wondering about this approach. Could things be changed so that a
vanilla image (Like the ones hosted on oVirt Glance) and a cloud-init
script would be sufficient?
It would be even better if Vargant could upload the images from
libvirt boxes directly into oVirt.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. |
redhat.com/trusted