RHEL OSP 6 Juno: Find out on which controller a tenant router is currently running

On RHEL OSP 6 Juno it`s a bit tricky to find out on which OSP controller the Pacemaker router service for a specific tenant is currently running on. It might be that all routers are running on the same controller but it also can happen that every tenant specific router is running on a different controller node. Continue reading “RHEL OSP 6 Juno: Find out on which controller a tenant router is currently running”

Configure VNC console through Horizon in HA environment the right way

This article shortly describes how to configure the VNC console access to OpenStack instances through Horizon in a high-availability environment. This configuration is currently valid for OpenStack Juno or RHEL OSP 6. If you change these settings after you already deployed instances in your environment theses changes only takes effect for instances which are created AFTER your changes described here. Continue reading “Configure VNC console through Horizon in HA environment the right way”

Foreman Template writing

Foreman uses common ERB style templating. Foreman templates consists of a mixture of Bash scripts and appropriate macros and functions. You can find a list of built-in macros and functions here. Within such macro you can use further Ruby code. For example to extract the last digits og an IP address you can use the following macro:

LAST_DIGIT=< %=@host.ip.to_s.split('.')[-1]%>

Where @host.ip is a built-in macro in Foreman (see link above), to_s is Ruby code and means “convert into string”, split wherever you find a “.” and read the output reverse and take the last value (“-1”).

If you want to check if a template will render correctly for an appropriate host you can open your template in your browser:

https:///unattended/provision?spoof='ip-of-a-host-you-want-to-provision'

Making SELinux context on NFS mounts persistent

If you want to use for example a central NFS export with your Nagios configuration under /etc/nagios on your Nagios server the nfs mount is basically mounted with the “nfs_t” context. To start Nagios you need the context “nagios_etc_t” for /etc/nagios instead. Unfortunately a simple “semanage fcontext -a -t …” is not sufficient. You need to add the context as a mount option to your /etc/fstab file like this:

server:/export /etc/nagios	nfs	vers=4,context="system_u:object_r:nagios_etc_t:s0"  0 0