Skip to main content


How to setup Juniper's Openstack FWaaS Plugin

I have written a tech wiki article on how to install Juniper's OpenStack FWaaS Plugin @

This article covers the configuration that needs to be done on the OpenStack side as well as the configuration that needs to be done for the plugin. A reference topology is used and the whole configuration is done as a walk through using the reference model.
Recent posts

WILT: How to reset your forgotten password on IRC

IRC is the platform OpenStack members use to coordinate and have weekly syncups. I recently upgraded my system and in the process lost the saved password for my account. The process to reset was a little difficult to figure out but turns out to be fairly simple. All you need to do is to execute the following command:

/msg NickServ SENDPASS your-account-name

Solved: Fix for Git clone failure due to GnuTLS recv error (-9)

My devstack installation was failing with an error reported by the GnuTLS module as shown below:

$ git clone /opt/stack/horizon --branch master
Cloning into '/opt/stack/horizon'...
remote: Counting objects: 154213, done.
remote: Compressing objects: 100% (11/11), done.
error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received.
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

The following Git config changes fixed the issue for me. Am hoping it will be useful for someone out there:

$ git config http.sslVerify false
$ git config --global http.postBuffer 1048576000

Fixing Openstack Cirros VM : atkbd serio0: Use setkeycodes 00 error

When a Cirros VM is launched in Openstack Newton using the latest branch code you may encounter an error which prevents you from logging into VM's console. As soon as you start typing the username 'cirros' you may find the following error message getting printed on the console:

atkbd serio0: Unknown key released (translates Set 2, ................)
atkbd serio0: Use 'setkeycodes 00 ' to make it known

This is a known issue and is tracked @

I had tough time finding a solution to this problem and the solution turns out to be quite a simple one. This issue is occurring due to a bug in the latest noVNC code and is tracked @

This problem can be solved in two ways (as a workaround):

1. Set NOVNC_BRANCH=v0.6.0 in your local.conf file and restack
2. cd /opt/stack/noVNC
    git checkout v0.6.0
    Now go to your VM console and refresh it. It should start working.

WILT: Fixing Virtual box shared clipboard issue

I have a Windows 10 laptop (host) which uses Virtualbox as the hypervisor. In the Virtualbox, I have a Ubuntu 16.10 VM. Once in a while its required to copy text between the VM and the host and Virtualbox has a feature to enable bi-directional shared clipboard:

This feature does not work sometimes. After going through some discussion forums I came across the below suggestion which solved this problem.

Run the following commands on the VM:
sudo VBoxClient-all stop sudo VBoxClient-all start

Pythonic surprises for a Java programmer - Part 1

I had been a hard core Java programmer through out my career and had moved onto Python a while ago. The transition to python was a roller coaster ride of moments of unbridled exultation, deja vu and mirth followed by those of horror, surprise and deep disgust. Just to crib a bit, Python does not provide encapsulation...arrrghhhhh!!! and the best way to prevent people from calling an internal method seems to be to request them not to do so.
"""      This method is meant to be consumed locally.      Don't call it from outside.... please please please :( """ def _do_something_internal():     -----------------     ----------------- This blog (and a few subsequent ones, hopefully) will capture my observations on some gotchas that "pleasantly" surprise people coming from the Java domain (may be relevant to other languages as well).

Variable Scoping

Scenario 1 :
def method1():     try:           x = 10     except:            pass     print x Expec…

Creating Juniper VSRX 2.0 VM on Virtualbox

Juniper has come out with their latest version of VSRX 2.0 (formerly called as Firefly or VSRX 1.0). This release supports a broader set of features and is more performant than the earlier version. More details about the product can be obtained here

I had recently tried out instantiating VSRX 2.0 on Virtualbox. The process required a few minor tweaks and this blog will cover them.

Download VSRX KVM Applicance from Juniper Website (You need to take care of the legal formalities)Virtualbox 4.3 and aboveDownload qemu-img converter for Windows  The image provided by Juniper is in QCOW2 format. In order to use it in Virtual box you need to convert it to VDI format. To do this you can use the tool qemu-img converter as follows:
#qemu-img.exe convert media-srx-ffp-vsrx-vmdisk-15.1X49-D15.4.qcow2 -O vdi vsrx2.0-1.vdi
The conversion will take a few seconds and you should have the VDI created in the directory. At this piont, you can proceed to create a VM by following these steps: