Request #2111

make thousands of vagrant "box"es importable

Added by Florian Heigl about 8 years ago. Updated about 5 years ago.

Status:PendingStart date:06/01/2013
Priority:NormalDue date:
Assignee:-% Done:


Category:-Estimated time:100.00 hours
Target version:-
Pull request:



I want to propose a feature that allows importing premade virtual machine images that have been prepared using vagrant.
What would it do:

  • allows users to build opennebula / vagrant dual use VMs on their silly laptop and upload them to the ONE IaaS
  • allows users to use the Sunstone interface to import a vagrant VM as a new template simply via it's URL

What I think why this is possible / interesting

  • should work like vagrant does it, that means by using a certain URL
  • concepts are similar, base image and instantiation
  • allow local importing of vagrant box images
  • increase the marketplace volume with tested images
  • save on work for providing images in the marketplace (!!!) -> meaning more reliable and current.
  • vagrant per se is "cool" for many people, especially those that can't pull full PXE setups out of their bag.
  • help larger dev teams use the "full cloud power"
  • need to be aware of security implications of vagrant boxes that everyone keeps ignoring (thats why "tested images" above)
  • vm has a kind of staging where you can "clear" a image to run, or PULL it.
  • ...might be smart to have something: once the vagrant community starts looking into how many of their images are w/rootkits already, ONE could win by being able to revoke a certain images access rights etc. You know: All the cool stuff virtual infrastructure allows.
  • virtualbox dependency can probably be solved - i.e. automated testing on diff hypervisors. compatible HV selection is already solved in ONE

I've kept this shorter than I wanted, but I already spent 8 days pondering the text.
So please just use your imagination to see how many options this gives, and feel free to "help" by editing.


#1 Updated by Ruben S. Montero about 8 years ago

Would it make sense to develop an OpenNebula-Vagrant provider? As described here for AWS....

#2 Updated by Florian Heigl about 8 years ago

I think that makes a lot sense (but is another topic)
Quick to use interfaces could give Opennebula more reputation than any professional feature (we love)

Amazon might be a little pissed about the lost revenue. :)

#3 Updated by Ruben S. Montero over 7 years ago

  • Tracker changed from Feature to Backlog
  • Category deleted (34)

#4 Updated by Valentin Bud over 6 years ago

For whom it may concern there is an OpenNebula Vagrant provider
out there in the wild. It doesn't have all the features provided by
Virtualbox to say, but it works to start, stop VMs on an OpenNebula

It require rOCCI.


#5 Updated by Ruben S. Montero over 6 years ago

  • Tracker changed from Backlog to Request

#6 Updated by Florian Heigl about 5 years ago


I came back to this. The opennebula provider can start templates in OpenNebula, nothing else.
There's also a branch without rOCCI requirement and one that adds suspend/resume, which is nice.

But anyone who sits down with that on the one side and a normal vagrant setup on the other side will notice that the core functionality of vagrant includes retrieving images from ((often) external) sources.

A real solution would need to fetch the 'box' images and wrap them in a template. There's not really anything technical in the way, except that it's more than a day's work and requires strong ONE dev background.

What puzzles me is why this rotted away in the backlog with surely not more than 30 minutes of attention, for something that could've gained a very very large additional user base. Now that the dev crowd moved to docker those are all lost and won't come back. So basically you specifically opted to shrink your user base.

Anyway. Once I got this working in general I'll try to at least create some hook that is able to fetch unpack things and report back.

Also available in: Atom PDF