How to setup Juniper's Openstack FWaaS Plugin

I have written a tech wiki article on how to install Juniper's OpenStack FWaaS Plugin @ http://forums.juniper.net/t5/Data-Center/How-to...

Tuesday, March 21, 2017

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

Wednesday, February 8, 2017

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 https://github.com/openstack/horizon.git /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

Monday, November 28, 2016

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 @ https://bugs.launchpad.net/devstack/+bug/1619554

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 @ https://bugs.launchpad.net/horizon/+bug/1622684

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.