<div dir="ltr">Ive made progress on using pure cloud-init on the centos glance images to get the vagrant pre-requisites included and usable but so far thats introduced two issues that still make template exporting within Lago desirable:<div><br></div><div><ol><li>Time and network resources to download packages as well as CPU/memory bloating from repeated installations of the same packages</li><li>Unable to test network configuration of vagrant, which is a large part of vagrant to leave untested </li><ol><li>By that i mean dhcp/static/multiple network interfaces via blocks such as [1] and [2]</li></ol></ol><div>In the mean time I'm contemplating using the vagrant/ruby sdk to make `vagrant package` export as an oVirt template which would let me call that in the middle of an ovirt-system-tests suite, if I'm not mistaken?</div><div><br></div><div>[1] </div></div><div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div> config.vm.network :private_network,</div><div> :ovirt__network_name => 'ovirtmgmt' #DHCP</div></blockquote>[2]</div><div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><div> config.vm.network :private_network,</div><div> :ovirt__ip => '192.168.2.198', :ovirt__network_name => 'ovirtmgmt', :ovirt__gateway => '192.168.2.125', :ovirt__netmask => '255.255.0.0', :ovirt__dns_servers => '192.168.2.1', :ovirt__dns_search => 'test.local'</div></div><div><br></div><div><br></div></blockquote></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 24, 2017 at 9:32 AM, Yaniv Kaul <span dir="ltr"><<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Aug 24, 2017 at 4:53 PM, Marc Young <span dir="ltr"><<a href="mailto:3vilpenguin@gmail.com" target="_blank">3vilpenguin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">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.</div></blockquote><div><br></div></span><div>Regretfully there's something wrong with the cloud-init on the CirrOS image we download, so it doesn't work well.</div><div>Two alternatives I can think of:</div><div>1. Download a different image - CentOS and Fedora both work well, for example. The downside is that it's a bit slow.</div><div>2. Upload an image using the upload API. This has the advantage that it's (1) quicker and (2) will add an additional test to ovirt-system-tests, which is always a good idea. There's already an example available (<a href="https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk.py" target="_blank">https://github.com/oVirt/<wbr>ovirt-engine-sdk/blob/master/<wbr>sdk/examples/upload_disk.py</a>) .<wbr> </div><div>Downside: will take a bit of space on the git repo, if the image will be on o-s-t git repo.</div><span class=""><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>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.</div></div></blockquote><div><br></div></span><div>Packer support for oVirt is waiting for the Go SDK and for someone to implement it.</div><span class="HOEnZb"><font color="#888888"><div>Y.</div></font></span><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>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)</div><div><br></div><div>[1] <a href="https://github.com/myoung34/vagrant-ovirt4/tree/master/example_box" target="_blank">https://github.com/myoung3<wbr>4/vagrant-ovirt4/tree/master/<wbr>example_box</a></div><div>[2] <a href="https://www.vagrantup.com/docs/boxes.html" target="_blank">https://www.vagrantup.com/docs<wbr>/boxes.html</a></div><div>[3] <a href="https://www.packer.io/" target="_blank">https://www.packer.io/</a></div><div>[4] <a href="https://www.packer.io/docs/builders/qemu.html" target="_blank">https://www.packer.io/docs<wbr>/builders/qemu.html</a></div></div><div class="m_2446060555646380872gmail-HOEnZb"><div class="m_2446060555646380872gmail-h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 24, 2017 at 8:17 AM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>On 24 August 2017 at 15:35, Marc Young <<a href="mailto:3vilpenguin@gmail.com" target="_blank">3vilpenguin@gmail.com</a>> wrote:<br>
><br>
> Vagrant requires coming up from a template (and a modified one at that [1].<br>
<br>
</span>I was wondering about this approach. Could things be changed so that a<br>
vanilla image (Like the ones hosted on oVirt Glance) and a cloud-init<br>
script would be sufficient?<br>
<br>
It would be even better if Vargant could upload the images from<br>
libvirt boxes directly into oVirt.<br>
<span class="m_2446060555646380872gmail-m_1429996649861510267HOEnZb"><font color="#888888"><br>
--<br>
Barak Korren<br>
RHV DevOps team , RHCE, RHCi<br>
Red Hat EMEA<br>
<a href="http://redhat.com" rel="noreferrer" target="_blank">redhat.com</a> | TRIED. TESTED. TRUSTED. | <a href="http://redhat.com/trusted" rel="noreferrer" target="_blank">redhat.com/trusted</a><br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></span></div><br></div></div>
</blockquote></div><br></div>