If you ever want to deploy Neutron in OpenStack (Icehouse) in high-availability mode, where you have more than one network controller (node), you’ll have to take into account that most of Neutron components will have to run in active-passive mode. Furthermore, virtual routers get associated to a L3 agent at creation time, and virtual networks to a DHCP agent. This association is established via the host name of the agent (L3 or DHCP). Unless explicitly configured, Neutron agents register themselves with a host name that matches the FQDN of the host where they are running.
An example: let’s imagine a scenario where we have two network nodes:
nn2.example.com. By default, the L3 agent running on the host
nn1.example.com will register itself with a host name of
nn1.example.com. The same holds true for the the DHCP agent. The L3 agent on host nn2.example.com is not running yet, but it’s configured in the same way as the other L3 agent. Hence, the L3 agent on host nn2.example.com will register itself using a host named
Now, a user creates a virtual router and, at creation time, it gets associated with the L3 agent running on host
nn1.example.com. At some point, host
nn1.example.com fails. The L3 agent on host
nn2.example.com will be brought up (for example, via Pacemaker). The problem is that the virtual router is associated with an L3 agent named
nn1.example.com, which is now unreachable. There’s an L3 agent named
nn2.example.com, but that won’t do it.
What’s the proper solution to fix this mess? To tell Neutron agents to register themselves with a fictitious, unique host name. Since there will only be one agent of the same type running at the same time (active-passive), it won’t cause any problems. How does one tell the Neutron agents in OpenStack (Icehouse) to use this fictitious name? Just add the following configuration option to
/etc/neutron/neutron.conf inside the
host = my-fictitious-host-name
Tired of your carrier from dropping a custom boot and shutdown animation? Like Movistar does? Do you have an LG G3 D855 phone? Is it rooted? Then it’s just a matter of removing the following files:
This will, hopefully, revert to using the stock boot and shutdown animations.
I was getting clang errors on ffi.h when trying to install python-glanceclient using pip:
$ pip install python-glanceclient
Installing collected packages: python-glanceclient, cryptography, jsonschema, jsonpatch, cffi, jsonpointer, pycparser
Running setup.py install for cryptography
Package libffi was not found in the pkg-config search path.
Perhaps you should add the directory containing `libffi.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libffi' found
Command /usr/local/opt/python/bin/python2.7 -c "import setuptools, tokenize;__file__='/private/tmp/pip_build_brew/cryptography/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-jghJZG-record/install-record.txt --single-version-externally-managed --compile failed with error code 1 in /private/tmp/pip_build_brew/cryptography
Storing debug log for failure in /Users/brew/.pip/pip.log
A fix that seems to work is manually installing libffi and exporting PKG_CONFIG_PATH pointing to it:
$ brew install pkg-config libffi
$ export PKG_CONFIG_PATH=/usr/local/Cellar/libffi/3.0.13/lib/pkgconfig/
$ pip install cffi
$ pip install python-glanceclient
$ glance --version
I found the following article that takes a minimalist approach at managing syslog with Puppet: http://itscblog.tamu.edu/managing-syslog-and-log-forwarding-with-puppet/
I’m attaching OpenStack and DevOps which are the slides of a Tech Talk I delivered as part of the series of Master Talk lectures for the U-TAD Master in Advanced Software Engineering from Telefónica.
I’ve been experience this problem multiple times, when trying to connect using NoMachine Client for Mac OS X to a Linux machine running NoMachine NX Workstation: the remote mouse cursor is invisible. Apparently, the solution consists of uncommenting the following line in the NX server machine, in file /usr/NX/node.cfg: