NrvrCommander makes CentOS 6.6 and Ubuntu 14.04 VMs


This is an announcement of new features of the free and open source NrvrCommander multi-OS virtual machine making scripting and automation software, which is at version 1.7.1.  What is new:

  • Support for making VMs that run Ubuntu 14.04 LTS.
  • Better support for making VMs that run CentOS 6.6,
    in addition to earlier support of making VMs that run Scientific Linux.
  • Set number of processor cores.
  • Disable USB autoconnect.
  • Optionally install Node.js in VMs.
  • Update several components.

Read the rest of this entry »

NrvrCommander documentation DIY


NrvrCommander should have more documentation. Today I write why I don’t write more documentation today.

There is some good documentation already.

If we would wait for perfection, we would be withholding a working tool.

Read the rest of this entry »

NrvrCommander automation release


What may matter most about the free and open source NrvrCommander: It is in use.

What it is

NrvrCommander makes virtual machines, and it controls them for automation.

NrvrCommander does at least some things other automation software doesn’t, or didn’t when we looked. For example…

… in NrvrCommander’s example scripts the starting points are original OS distributions, from there on scripting, not requiring acceptance of pre-made VM snapshots.
Your appreciation may depend on whom you trust and how many variations you need. In addition to transparency (review, audit) and flexibility (variations by coding a few lines), scripts take arguably 10-5 of the storage space of snapshots.
This is not mandatory, not a limitation: You could start from snapshots, and one example script cleverly uses snapshots.

Read the rest of this entry »

GUI on headless Linux server [SOLVED]


I merely wanted to run NrvrCommander to do load testing with Selenium – a combo working quite well – but circumstances forced me to first regain control of a remote computer I had been driving just fine until one morning VNC stopped working. Presented is a documentation of working solutions, and how we got here.

The failure of VNC started with no clearly identifiable single cause. There have been multiple causes: Read the rest of this entry »