Please update the images periodicaly

[reidrac]

I'm trying to use 42.2 and it is very useful to have these images in Atlas; but currently it is too old and it requires update (and reboot, there are kernel updates) and that breaks provisioning.

Would it be possible to rebuild these images periodically and push them to Atlas if there are changes?

Thanks a lot for providing the images!

[hwoarang]

This is not a problem but a feature request :) I currently use vagrant images myself so I plan to update them once a month. However, I can't make long term commitments. Right now, there is a blocking issue (http://bugzilla.suse.com/show_bug.cgi?id=1043758) for me which prevents me from updating the image. Once it's resolved I will do a fresh build.

[reidrac]

Thanks!

Perhaps openSUSE infrastructure could be used to automate that.

[hwoarang]

@reidrac sure but it needs a volunteer to drive it forward :)

[denisok]

@hwoarang I can setup jenkins job on our community ci to build images periodically. What I would need are credentials to upload them to cloud.

If you could provide that I will build the job. I think 15 and Tumbleweed is just enough?

[denisok]

I was able to generate images with this simple script:

zypper in -y qemu-kvm libvirt-daemon-qemu libvirt libvirt-devel virtualbox virtualbox-host-source kernel-devel gcc gcc-c++ make

ssh-keygen -t rsa -f /root/.ssh/id_rsa -P ""
cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys

usermod -a -G vboxusers $USER

systemctl enable libvirtd
systemctl start libvirtd

/sbin/vboxconfig

git clone --depth 1 git@github.com:openSUSE/vagrant.git

cd vagrant

wget https://releases.hashicorp.com/packer/1.2.5/packer_1.2.5_linux_amd64.zip
unzip ./packer*

./packer build -parallel=false -only=virtualbox,libvirt -var 'headless=true' definitions/15.0-x86_64.json

and these changes:
#33

[aspiers]

ICBW but I would have thought it would make the most sense to build these automatically in OBS using Kiwi, rather than externally via Packer. That way the image will be automatically rebuilt and published whenever any of its dependencies gets updated. Obviously this "push" model of initiating rebuilds will be quicker than polling, and saves having to reinvent the wheel by building custom Jenkins jobs to do the same thing. It also avoids the requirement for separate CI workers to boot up Packer VMs, since the work would get done by the OBS worker cloud.

This is certainly possible (I've done it) but unfortunately it appears currently undocumented, so I've filed OSInside/kiwi#792 to try to get that fixed.

I suspect there may be other advantages to using Kiwi over Packer, since Kiwi was designed natively for building openSUSE images. But I don't know the details. Perhaps @schaefi can comment on that.

[denisok]

@aspiers yes, I could build vagrant boxes for vagrant, example is this internal link.

I don't understand how it would allow us to skip CI, as you need to rung vagrant with just built box. Could you please elaborate?

As for packer vs kiwi, I really don't care - I see the value of kiwi, but untill it is done packer works just fine now. And small jenkins job would do it very fast and simple.

As for kiwi - I would agree that could be better solution but it is not there yet.

[aspiers]

@denisok commented on 30 Jul 2018, 11:39 BST:

@aspiers yes, I could build vagrant boxes for vagrant, example is this internal link.

I don't understand how it would allow us to skip CI, as you need to rung vagrant with just built box. Could you please elaborate?

Ah OK, yes if you want to do the sensible thing and actually validate that the box you just built works then you are right, it doesn't allow you to skip that :-) I was only talking about skipping the task of building the box, not testing it. So if you use OBS for that, then you only have to build CI to test it, not any CI for building it first. The CI could test the latest version from OBS and then if that works, "promote" it into a more stable repository.

As for packer vs kiwi, I really don't care - I see the value of kiwi, but untill it is done packer works just fine now. And small jenkins job would do it very fast and simple.

As for kiwi - I would agree that could be better solution but it is not there yet.

Yeah I don't really know for sure - deferring to @schaefi who might be able to list more compelling reasons to use KIWI over Packer.

[denisok]

yep, there are couple of image sources in openSUSE:
https://build.opensuse.org/package/show/Virtualization:Appliances:Images/dice-image-vagrant-libvirt
by @schaefi
https://build.opensuse.org/package/show/home:jloehel:vagrant:images/tumbleweed
by @jloehel

I actually used @jloehel templates before - they are working fine.

The only thing I am missing in @schaefi image project is Static link.

It might be a good idea to create some new vagrant images under:
https://build.opensuse.org/project/show/Virtualization:Appliances:Images
and somehow update https://app.vagrantup.com/opensuse after successful build.

[aspiers]

Good news - building Vagrant images via Kiwi has now been documented.

[aspiers]

Documentation now visible: http://suse.github.io/kiwi/building/working_with_images/vagrant_setup.html

[hwoarang]

@denisok what credentials do you need to upload them? If you are referring to Atlas, then you need to create an account there and then @vuntz can add you to the necessary group like he did for me. After that you would be able to upload files to the openSUSE organization. Would that work?

[denisok]

@hwoarang yes - thanks!

[AkihiroSuda]

What's current status?