Skip to contentSkip to conversation

RFC: Adding Vagrant file for provisioning

PATCH New Angelo Compagnucci 3 participants 7 messages Sep 9, 2015 – Sep 10, 2015

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 RFC: Adding Vagrant file for provisioning

This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms.

---

This patch is a tentative approach to add a standard and official Vagrant file to buildroot. With this file you can setup an isolated build environment based on Vagrant on all major platforms.

The file is fairly basic right now, it sets up correct Ubuntu version to download and install required packages for buildroot.

I'm open to suggestions and critics!

 docs/manual/getting.txt    |  7 +++++++
 docs/website/download.html |  9 +++++++++
 support/misc/Vagrantfile   | 42 ++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 58 insertions(+)
 create mode 100644 support/misc/Vagrantfile
docs/manual/getting.txt +7 -0
index 3437f93..5b96928 100644
@@ -10,6 +10,13 @@ November. Release numbers are in the format YYYY.MM, so for example
 
 Release tarballs are available at http://buildroot.org/downloads/[].
 
+If you want an isolated developing environment with Vagrant, paste this
+line in your terminal:
+
+--------------------
+wget http://git.buildroot.net/buildroot/tree/support/misc/Vagrantfile; vagrant up
+--------------------
+
 If you want to follow development, you can use the daily snapshots or
 make a clone of the Git repository. Refer to the
 http://buildroot.org/download[Download page] of the Buildroot website
docs/website/download.html +9 -0
index ef87b1c..ece0f19 100644
@@ -32,6 +32,15 @@ This and earlier releases (and their PGP signatures) can always be downloaded fr
 
 <p>
 
+<p>
+If you want an isolated developing environment with Vagrant, paste this
+line in your terminal:
+
+--------------------
+wget http://git.buildroot.net/buildroot/tree/support/misc/Vagrantfile; vagrant up
+--------------------
+</p>
+
 You can also obtain daily snapshots of the latest Buildroot source tree if you
 want to follow development, but cannot or do not wish to use Git.
 
support/misc/Vagrantfile new file +42 -0

42 lines not on this page · raw message

Signature · 1 line
1.9.1
#1 lore raw

PATCH 1/1 RFC: Adding Vagrant file for provisioning

Quoted 7 lines · Angelo Compagnucci

This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms.

---

Quoted 8 lines

This patch is a tentative approach to add a standard and official Vagrant file to buildroot. With this file you can setup an isolated build environment based on Vagrant on all major platforms.

The file is fairly basic right now, it sets up correct Ubuntu version to download and install required packages for buildroot.

I'm open to suggestions and critics!

Here goes:

If you're already on a platform that runs vagrant, then you have enough to run
buildroot as well, so why would you want to put it inside a VM and double your build time? Buildroot really really tries very hard to make sure it runs in any environment, so there should be no need for any of this trickery.

The only limitation you do have is that you need some tools like a compiler and
some VCSes. If that is what you want to work around, then I'd prefer to go the way of a single-user nix environment to import these tools.

Regards,
Arnout

Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
#2 lore raw

PATCH 1/1 RFC: Adding Vagrant file for provisioning

Dear Arnout Vandecappelle ,

2015-09-10 0:14 GMT+02:00 Arnout Vandecappelle <[email protected]>:

Quoted 15 lines · Angelo Compagnucci
Quoted 14 lines

This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms.

---

This patch is a tentative approach to add a standard and official Vagrant file to buildroot. With this file you can setup an isolated build environment based on Vagrant on all major platforms.

The file is fairly basic right now, it sets up correct Ubuntu version to download and install required packages for buildroot.

Quoted 8 lines
Quoted 1 line

I'm open to suggestions and critics!

Here goes:

If you're already on a platform that runs vagrant, then you have enough to run
buildroot as well, so why would you want to put it inside a VM and double your build time? Buildroot really really tries very hard to make sure it runs in any environment, so there should be no need for any of this trickery.

Not true. I know of certain corporate environments in which you have to stick on windows, and usually the people working in these environment use virtual machines also if buildtime will be longer. IMHO with a fairly recent computer you will not notice of being inside a virtual machine.

Also having buildroot on mac is not that easy, Vagrant will solve these problems brilliantly!

Quoted 3 lines

The only limitation you do have is that you need some tools like a compiler and
some VCSes. If that is what you want to work around, then I'd prefer to go the way of a single-user nix environment to import these tools.

Yes, true, when you are on a unix environment!

Quoted 11 lines

Regards,
Arnout

--

Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
Signature · 1 line
Profile: http://it.linkedin.com/in/compagnucciangelo
#3 lore raw

PATCH 1/1 RFC: Adding Vagrant file for provisioning

Quoted 22 lines · Angelo Compagnucci

Dear Arnout Vandecappelle ,

2015-09-10 0:14 GMT+02:00 Arnout Vandecappelle <[email protected]>:

Quoted 19 lines · Angelo Compagnucci
Quoted 7 lines

This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms.

---

Quoted 8 lines

This patch is a tentative approach to add a standard and official Vagrant file to buildroot. With this file you can setup an isolated build environment based on Vagrant on all major platforms.

The file is fairly basic right now, it sets up correct Ubuntu version to download and install required packages for buildroot.

I'm open to suggestions and critics!

Here goes:

Quoted 8 lines
Quoted 4 lines

If you're already on a platform that runs vagrant, then you have enough to run
buildroot as well, so why would you want to put it inside a VM and double your build time? Buildroot really really tries very hard to make sure it runs in any environment, so there should be no need for any of this trickery.

Not true. I know of certain corporate environments in which you have to stick on windows, and usually the people working in these environment use virtual machines also if buildtime will be longer.

So I was wrong about Vagrant not running on Windows? Oh, now I see. Sorry for
my confusion.

At some point I considered that we should host an official VM image. This is a
lot better then, of course!

Quoted 2 lines

IMHO with a fairly recent computer you will not notice of being inside a virtual machine.

Do the test. AFAIK it doubles the build time.

Quoted 3 lines

Also having buildroot on mac is not that easy, Vagrant will solve these problems brilliantly!

Yep, I didn't think of that either.

Regards,
Arnout

Signature · 6 lines
Arnout Vandecappelle      arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
#4 lore raw

PATCH 1/1 RFC: Adding Vagrant file for provisioning

Dear Arnout Vandecappelle,

2015-09-10 10:07 GMT+02:00 Arnout Vandecappelle <[email protected]>:

Quoted 34 lines · Angelo Compagnucci
Quoted 22 lines

Dear Arnout Vandecappelle ,

2015-09-10 0:14 GMT+02:00 Arnout Vandecappelle <[email protected]>:

Quoted 19 lines · Angelo Compagnucci
Quoted 7 lines

This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms.

---

Quoted 8 lines

This patch is a tentative approach to add a standard and official Vagrant file to buildroot. With this file you can setup an isolated build environment based on Vagrant on all major platforms.

The file is fairly basic right now, it sets up correct Ubuntu version to download and install required packages for buildroot.

I'm open to suggestions and critics!

Here goes:

Quoted 8 lines
Quoted 4 lines

If you're already on a platform that runs vagrant, then you have enough to run
buildroot as well, so why would you want to put it inside a VM and double your build time? Buildroot really really tries very hard to make sure it runs in any environment, so there should be no need for any of this trickery.

Not true. I know of certain corporate environments in which you have to stick on windows, and usually the people working in these environment use virtual machines also if buildtime will be longer.

Quoted 5 lines

So I was wrong about Vagrant not running on Windows? Oh, now I see. Sorry for
my confusion.

At some point I considered that we should host an official VM image. This is a
lot better then, of course!

Yes, Vagrant make it simple and replicable.

Quoted 4 lines
Quoted 2 lines

IMHO with a fairly recent computer you will not notice of being inside a virtual machine.

Do the test. AFAIK it doubles the build time.

You can raise the core numbers and memory allocated to your vm, see the variable at the head of the Vagrant file. I have a quad core 4th generation core i7 and the build is slower, but not that much.

Quoted 16 lines
Quoted 2 lines

Also having buildroot on mac is not that easy, Vagrant will solve these problems brilliantly!

Yep, I didn't think of that either.

Regards,
Arnout

--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile) Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven

LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
Signature · 1 line
Profile: http://it.linkedin.com/in/compagnucciangelo
#5 lore raw

PATCH 1/1 RFC: Adding Vagrant file for provisioning

Quoted 30 lines · Angelo Compagnucci

Dear Arnout Vandecappelle,

2015-09-10 10:07 GMT+02:00 Arnout Vandecappelle <arnout@...>:

Quoted 26 lines · Angelo Compagnucci
Quoted 23 lines

Dear Arnout Vandecappelle ,

2015-09-10 0:14 GMT+02:00 Arnout Vandecappelle <arnout@...>:

Quoted 20 lines · Angelo Compagnucci
Quoted 7 lines

This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms.

---

Quoted 8 lines

This patch is a tentative approach to add a standard and official Vagrant file to buildroot. With this file you can setup an isolated build environment based on Vagrant on all major platforms.

The file is fairly basic right now, it sets up correct Ubuntu version to download and install required packages for buildroot.

I'm open to suggestions and critics!

Here goes:

If you're already on a platform that runs vagrant, then you have

enough to run

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

buildroot as well, so why would you want to put it inside a VM and

double your

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

build time? Buildroot really really tries very hard to make sure it

runs in any

Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
Quoted 1 line

environment, so there should be no need for any of this trickery.

Not true. I know of certain corporate environments in which you have to stick on windows, and usually the people working in these environment use virtual machines also if buildtime will be longer.

So I was wrong about Vagrant not running on Windows? Oh, now I see.

Sorry for

Quoted 3 lines
Quoted 3 lines

my confusion.

At some point I considered that we should host an official VM image.

This is a

Quoted 3 lines
Quoted 1 line

lot better then, of course!

Yes, Vagrant make it simple and replicable.

We use strict configuration management practices and part of that is automating reproducible builds. Vagrant allows doing just that (very important use case in my opinion) so I thank you for submitting this; an official VM image would be great for testing purposes as well. Furthermore, you can have Vagrant automate a bunch of commands on top of just building which introduces a lot of options.

Quoted 12 lines
Quoted 5 lines
Quoted 3 lines

IMHO with a fairly recent computer you will not notice of being inside a virtual machine.

Do the test. AFAIK it doubles the build time.

You can raise the core numbers and memory allocated to your vm, see the variable at the head of the Vagrant file. I have a quad core 4th generation core i7 and the build is slower, but not that much.

Quoted 2 lines
Quoted 2 lines

Also having buildroot on mac is not that easy, Vagrant will solve these problems brilliantly!

While our build servers are running native Linux, we use Vagrant + VMs (both Virtualbox and VMware) at work on Macs daily as our development machines. It works great. The past few years, performance has gotten very good and with the recent Macbook Pro PCI-E SSDs, there is not a noticeable drop off in performance. In fact, we also do daily builds on these machines. You just have to make sure you have a beasty machine for it (i7, 8GB RAM minimum, preferably SSD, etc.). This works especially well in corporate scenarios (as mentioned) where you are required to run Windows as the host.

Quoted 15 lines
Quoted 14 lines

Yep, I didn't think of that either.

Regards,
Arnout

--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile) Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven

LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
#6 lore raw

PATCH 1/1 RFC: Adding Vagrant file for provisioning

Dear Nimai Mahajan,

2015-09-10 13:56 GMT+02:00 Nimai Mahajan <[email protected]>:

Quoted 51 lines
Quoted 30 lines · Angelo Compagnucci

Dear Arnout Vandecappelle,

2015-09-10 10:07 GMT+02:00 Arnout Vandecappelle <arnout@...>:

Quoted 26 lines · Angelo Compagnucci
Quoted 23 lines

Dear Arnout Vandecappelle ,

2015-09-10 0:14 GMT+02:00 Arnout Vandecappelle <arnout@...>:

Quoted 20 lines · Angelo Compagnucci
Quoted 7 lines

This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms.

---

Quoted 8 lines

This patch is a tentative approach to add a standard and official Vagrant file to buildroot. With this file you can setup an isolated build environment based on Vagrant on all major platforms.

The file is fairly basic right now, it sets up correct Ubuntu version to download and install required packages for buildroot.

I'm open to suggestions and critics!

Here goes:

If you're already on a platform that runs vagrant, then you have

enough to run

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

buildroot as well, so why would you want to put it inside a VM and

double your

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

build time? Buildroot really really tries very hard to make sure it

runs in any

Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
Quoted 1 line

environment, so there should be no need for any of this trickery.

Not true. I know of certain corporate environments in which you have to stick on windows, and usually the people working in these environment use virtual machines also if buildtime will be longer.

So I was wrong about Vagrant not running on Windows? Oh, now I see.

Sorry for

Quoted 3 lines
Quoted 3 lines

my confusion.

At some point I considered that we should host an official VM image.

This is a

Quoted 2 lines
Quoted 1 line

lot better then, of course!

Quoted 8 lines
Quoted 1 line

Yes, Vagrant make it simple and replicable.

We use strict configuration management practices and part of that is automating reproducible builds. Vagrant allows doing just that (very important use case in my opinion) so I thank you for submitting this; an official VM image would be great for testing purposes as well. Furthermore, you can have Vagrant automate a bunch of commands on top of just building which introduces a lot of options.

Same here. We build a new VM with vagrant for each testing scenario with jenkins and ansible provisioning.

Quoted 13 lines
Quoted 12 lines
Quoted 5 lines
Quoted 3 lines

IMHO with a fairly recent computer you will not notice of being inside a virtual machine.

Do the test. AFAIK it doubles the build time.

You can raise the core numbers and memory allocated to your vm, see the variable at the head of the Vagrant file. I have a quad core 4th generation core i7 and the build is slower, but not that much.

Quoted 2 lines
Quoted 2 lines

Also having buildroot on mac is not that easy, Vagrant will solve these problems brilliantly!

Quoted 8 lines

While our build servers are running native Linux, we use Vagrant + VMs (both Virtualbox and VMware) at work on Macs daily as our development machines. It works great. The past few years, performance has gotten very good and with the recent Macbook Pro PCI-E SSDs, there is not a noticeable drop off in performance. In fact, we also do daily builds on these machines. You just have to make sure you have a beasty machine for it (i7, 8GB RAM minimum, preferably SSD, etc.). This works especially well in corporate scenarios (as mentioned) where you are required to run Windows as the host.

I can confirm. Good hardware produces really good performances.

Quoted 24 lines
Quoted 7 lines
Quoted 7 lines

Yep, I didn't think of that either.

Regards,
Arnout

Quoted 9 lines
Quoted 8 lines

--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile) Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven

LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Signature · 1 line
Profile: http://it.linkedin.com/in/compagnucciangelo