Playing with Juniper vMX on VIRL

@Bastien_Pilat wrote:

It's probably dependant on the hypervisor used to run VIRL, we are running a baremetal VIRL over a Ubuntu server w/ kvm, and it only supports qcow2 image types.
So a .vmdk would have to be converted in our case :
qemu-img convert -O qcow2 <VMDK image file>.vmdk <target image file>.img

The resulting .img file should now be usable in VIRL.
If you're running VIRL over another hypervisor, I don't know which format are supported and how to do the conversion if needed.

As for Subtype/Image association, it's probably done in the subtype parameters, there :
"baseline_image": ""
in the parameters Fred gave. He didn't associate, I think if you put there the name of the image you have defined with glance (--name parameter), it should do the trick automatically. You'll probably also want to define a flavor to be associated with the
"baseline_flavor": ""
parameter.
Again, it can be done with OpenStack, with nova this time. The Juniper OpenStack installation scripts does this:
nova flavor-create vmx-vcp auto 4096 20 1
This adds the flavor in VIRL as well.
With
"baseline_flavor": "vmx-vcp"
in your subtype definition, this should associate it with the flavor

Read full topic