[cip-dev] [CIP testing strategy] Vagrant disksize plugin introduced, and some other (Vagrant-less) ideas

[cip-dev] [CIP testing strategy] Vagrant disksize plugin introduced, and some other (Vagrant-less) ideas

[Zoran S]

Hello CIP members,

Recently, I have learned that vagrant disksize plugin was introduced.
https://github.com/sprotheroe/vagrant-disksize

This, actually, replaces two native VBox commands (example given below):

  VBoxManage clonehd stretch.vmdk stretch.vdi --format VDI --variant Standard
  VBoxManage modifyhd stretch.vdi --resize 81920

The disksize plugin creates .VDI type of virtual HDD with the
stretched virtual size of 80GB (default .VMDK has limited 10GB size).

Please, do note that third party tool is required to extend the actual
virtual disk limit (as tool example: gparted).

In Vagrant file, you could create/add some code like this:

if !Vagrant.has_plugin?("vagrant-disksize")
   system('vagrant plugin install vagrant-disksize');
end

Vagrant.configure(2) do |config|
  config.vm.provider :virtualbox do |vbox, override|
    config.vm.box = "debian/stretch64"
    config.disksize.size = '80GB'

    vbox.customize ["modifyvm", :id, "--vram", "32"]
    vbox.customize ["modifyvm", :id, "--memory", "4096"]
    vbox.customize ["modifyvm", :id, "--cpus", "4"]
    vbox.customize ["modifyvm", :id, "--firmware", "bios"]
    vbox.customize ["modifyvm", :id, "--acpi", "on"]
    vbox.customize ["modifyvm", :id, "--ioapic", "on"]
    vbox.customize ["modifyvm", :id, "--cpuexecutioncap", "75"]
    vbox.customize ["modifyvm", :id, "--rtcuseutc", "on"]
    vbox.customize ["modifyvm", :id, "--cpuhotplug", "on"]
    vbox.customize ["modifyvm", :id, "--pae", "on"]
    vbox.customize ["modifyvm", :id, "--hwvirtex", "on"]
    vbox.customize ["modifyvm", :id, "--accelerate3d", "on"]
    vbox.customize ["modifyvm", :id, "--clipboard", "bidirectional"]
    vbox.customize ["modifyvm", :id, "--draganddrop", "bidirectional"]
    vbox.customize ["modifyvm", :id, "--usb", "on"]
    vbox.customize ["modifyvm", :id, "--usbehci", "on"]
    ...
_______

I also created [1] VBox VMM configuration and [2] Debian Stretch VM
configuration stages with pre-seed script (both stages execute with
one single command respectively), but [3] Lava VM test machine
creation without Vagrant assistance failed!

In other words I was not able to create [3] Lava VM provisioning stage
(in my first Vagrant-less attempt), using blindly unchanged CIP test
integration scripts.

I need to revisit integration scripts, my best guess. But I'll
continue to work on Vagrant-less test strategy, as my time allows
(engaged in several other projects).

Thank you,
Zoran

[cip-dev] [CIP testing strategy] Vagrant disksize plugin introduced, and some other (Vagrant-less) ideas

[Robert Marshall]

Zoran

Thanks for alerting me to this I'll take a look!

Robert

Zoran S <zoran.stojsavljevic.de@gmail.com> writes:

> Hello CIP members,
>
> Recently, I have learned that vagrant disksize plugin was introduced.
> https://github.com/sprotheroe/vagrant-disksize
>
> This, actually, replaces two native VBox commands (example given below):
>
>   VBoxManage clonehd stretch.vmdk stretch.vdi --format VDI --variant Standard
>   VBoxManage modifyhd stretch.vdi --resize 81920
>
> The disksize plugin creates .VDI type of virtual HDD with the
> stretched virtual size of 80GB (default .VMDK has limited 10GB size).
>
> Please, do note that third party tool is required to extend the actual
> virtual disk limit (as tool example: gparted).
>
> In Vagrant file, you could create/add some code like this:
>
> if !Vagrant.has_plugin?("vagrant-disksize")
>    system('vagrant plugin install vagrant-disksize');
> end
>
> Vagrant.configure(2) do |config|
>   config.vm.provider :virtualbox do |vbox, override|
>     config.vm.box = "debian/stretch64"
>     config.disksize.size = '80GB'
>
>     vbox.customize ["modifyvm", :id, "--vram", "32"]
>     vbox.customize ["modifyvm", :id, "--memory", "4096"]
>     vbox.customize ["modifyvm", :id, "--cpus", "4"]
>     vbox.customize ["modifyvm", :id, "--firmware", "bios"]
>     vbox.customize ["modifyvm", :id, "--acpi", "on"]
>     vbox.customize ["modifyvm", :id, "--ioapic", "on"]
>     vbox.customize ["modifyvm", :id, "--cpuexecutioncap", "75"]
>     vbox.customize ["modifyvm", :id, "--rtcuseutc", "on"]
>     vbox.customize ["modifyvm", :id, "--cpuhotplug", "on"]
>     vbox.customize ["modifyvm", :id, "--pae", "on"]
>     vbox.customize ["modifyvm", :id, "--hwvirtex", "on"]
>     vbox.customize ["modifyvm", :id, "--accelerate3d", "on"]
>     vbox.customize ["modifyvm", :id, "--clipboard", "bidirectional"]
>     vbox.customize ["modifyvm", :id, "--draganddrop", "bidirectional"]
>     vbox.customize ["modifyvm", :id, "--usb", "on"]
>     vbox.customize ["modifyvm", :id, "--usbehci", "on"]
>     ...
> _______
>
> I also created [1] VBox VMM configuration and [2] Debian Stretch VM
> configuration stages with pre-seed script (both stages execute with
> one single command respectively), but [3] Lava VM test machine
> creation without Vagrant assistance failed!
>
> In other words I was not able to create [3] Lava VM provisioning stage
> (in my first Vagrant-less attempt), using blindly unchanged CIP test
> integration scripts.
>
> I need to revisit integration scripts, my best guess. But I'll
> continue to work on Vagrant-less test strategy, as my time allows
> (engaged in several other projects).
>
> Thank you,
> Zoran
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
>

[cip-dev] [CIP testing strategy] Vagrant disksize plugin introduced, and some other (Vagrant-less) ideas

[Zoran S]

Hello Robert,

Please, also check the VBox and Vagrant versions:
VBox version & VBox extension 5.2.14 do not work with Vagrant 2.1.2 (rather
with Vagrant 2.1.1).
VBox version & VBox extension 5.2.12 do work with Vagrant 2.1.2.

At least, this is what I experienced.

(I am working to completely get rid of Vagrant, but I have another
emergency projects, now)
_______

For the CIP testing issue 190 (which is originated by me):
https://gitlab.com/cip-project/cip-testing/testing/issues/190

Here is the workaround/solution:











*And, the last desperate attempt was to swap 2018.5-3 base-uboot.jinja2
with 2017.7 base-uboot.jinja2.Fortunately, I saved this one (The ONLY one
complex one before destroying last Lava 2017.7 machine)),for NO apparent
reason, which (somehow) shows that I have very good psychic abilities!?
;-)And, for the reference, here is the 2017.7 base-uboot.jinja2, presented
as original:Lava 2017.7 generic device-type base-uboot.jinja2
filehttps://pastebin.com/rhs8wt4H <https://pastebin.com/rhs8wt4H>This did
the trick! Everything works like a charm.*

Thank you,
Zoran

On Fri, Jul 13, 2018 at 12:23 PM, Robert Marshall <
robert.marshall@codethink.co.uk> wrote:

> Zoran
>
> Thanks for alerting me to this I'll take a look!
>
> Robert
>
> Zoran S <zoran.stojsavljevic.de@gmail.com> writes:
>
> > Hello CIP members,
> >
> > Recently, I have learned that vagrant disksize plugin was introduced.
> > https://github.com/sprotheroe/vagrant-disksize
> >
> > This, actually, replaces two native VBox commands (example given below):
> >
> >   VBoxManage clonehd stretch.vmdk stretch.vdi --format VDI --variant
> Standard
> >   VBoxManage modifyhd stretch.vdi --resize 81920
> >
> > The disksize plugin creates .VDI type of virtual HDD with the
> > stretched virtual size of 80GB (default .VMDK has limited 10GB size).
> >
> > Please, do note that third party tool is required to extend the actual
> > virtual disk limit (as tool example: gparted).
> >
> > In Vagrant file, you could create/add some code like this:
> >
> > if !Vagrant.has_plugin?("vagrant-disksize")
> >    system('vagrant plugin install vagrant-disksize');
> > end
> >
> > Vagrant.configure(2) do |config|
> >   config.vm.provider :virtualbox do |vbox, override|
> >     config.vm.box = "debian/stretch64"
> >     config.disksize.size = '80GB'
> >
> >     vbox.customize ["modifyvm", :id, "--vram", "32"]
> >     vbox.customize ["modifyvm", :id, "--memory", "4096"]
> >     vbox.customize ["modifyvm", :id, "--cpus", "4"]
> >     vbox.customize ["modifyvm", :id, "--firmware", "bios"]
> >     vbox.customize ["modifyvm", :id, "--acpi", "on"]
> >     vbox.customize ["modifyvm", :id, "--ioapic", "on"]
> >     vbox.customize ["modifyvm", :id, "--cpuexecutioncap", "75"]
> >     vbox.customize ["modifyvm", :id, "--rtcuseutc", "on"]
> >     vbox.customize ["modifyvm", :id, "--cpuhotplug", "on"]
> >     vbox.customize ["modifyvm", :id, "--pae", "on"]
> >     vbox.customize ["modifyvm", :id, "--hwvirtex", "on"]
> >     vbox.customize ["modifyvm", :id, "--accelerate3d", "on"]
> >     vbox.customize ["modifyvm", :id, "--clipboard", "bidirectional"]
> >     vbox.customize ["modifyvm", :id, "--draganddrop", "bidirectional"]
> >     vbox.customize ["modifyvm", :id, "--usb", "on"]
> >     vbox.customize ["modifyvm", :id, "--usbehci", "on"]
> >     ...
> > _______
> >
> > I also created [1] VBox VMM configuration and [2] Debian Stretch VM
> > configuration stages with pre-seed script (both stages execute with
> > one single command respectively), but [3] Lava VM test machine
> > creation without Vagrant assistance failed!
> >
> > In other words I was not able to create [3] Lava VM provisioning stage
> > (in my first Vagrant-less attempt), using blindly unchanged CIP test
> > integration scripts.
> >
> > I need to revisit integration scripts, my best guess. But I'll
> > continue to work on Vagrant-less test strategy, as my time allows
> > (engaged in several other projects).
> >
> > Thank you,
> > Zoran
> > _______________________________________________
> > cip-dev mailing list
> > cip-dev at lists.cip-project.org
> > https://lists.cip-project.org/mailman/listinfo/cip-dev
> >
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180715/b3897935/attachment.html>