On Thu, Feb 28, 2019 at 1:01 PM Martinez Landa, Hayde < hayde.martinez.landa@intel.com> wrote:
Hi All,
Guillermo and I are currently working on the StarlingX in a box project, we are helding weekly meetings on Thursdays at 9:30 am PDT, We’ll send an update with the Zoom link soon, if anyone is interested in joining the efforts we welcome you.
We’ve been doing some research and looking for different options, first of all we were told to consider the python vbox installer As part of this effort [0], but we want to bring to the table another options.
1) Vagrant [1] - This tool has proven itself over time to provide solutions for development environments easily and fast. 2) GoVM [2]- This tool is young in comparison and it's currently under development but so far has proven itself to be faster and more flexible than vagrant.
Vagrant: Pros: - Has been around for a long time - It is well documented - A lot of people is used to it - Has a lot of provisioning plug-ins - Flexible and easy. Cons: - It is not as fast as GoVM. - It has a lot of overhead taking in count what we need from it - The ramp up is slower compare to GoVM. GoVM: Pros: - It has a small footprint. - It runs very fast (it is made on Go) - The ramp up is faster. - The main developers sits three desks from us (hehe (:) - It has a "compose" like option Cons: - It is not well known yet - The documentation is still lacking - It does not have that many plug ins - It is still under development (which can also be a pro because it will get better)
We also are considering to use Packer[3] to create the main images we are going to work with. Packer is a tool that is well integrated with vagrant since it is also from hashicorp but GoVM can work with those images as well. Right now we are having an issue with creating the base images from starlingx ISO since the installation method is not standard and it requires to create send an user and double password, We are working on solutions for this, will keep you updated.
Overall, I'm not sure that STX should only generate an ISO image. From a high level I'm not sure of the model of the project generating an ISO and then other code using that singular ISO to generate other binary images. I'm especially thinking of potential future Zero Touch Provisioning (ZTP) work. I'm also wondering how this might relate, eventually or not, to devstack. I think this in a box concept is not a localized issue, that this is project wide, and has impact in other areas in terms of our ability to provide important installation and automation capabilities. The discussion area is probably larger than whether to use virtual box, vagrant, govm, or some other tool. So on one hand, getting the vbox code in is important (ie. quick dev environment), but we also have to balance that with future capabilities that to me, look very similar to providing support necessary to systems to get a quick dev environment. That's my $0.02. :) Thanks, Curtis
Please share your thoughts and comments, let us know if you need more information or details on these, and also if you now another tool that works well and can help us in this effort.
[0] https://review.openstack.org/#/c/637958/ [1] https://www.vagrantup.com/ [2] https://github.com/govm-project/govm [3] https://packer.io/
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- Blog: serverascode.com