Updating network configuration on the Overcloud after a deployment

By default, subsequent change(s) made to network configuration templates (bonding options, mtu, bond type, etc) are not applied on existing nodes when the overcloud stack is updated.


TripleO Container steps

Container steps

Similar to baremetal, containers are brought up in a stepwise manner. The
current architecture supports bringing up baremetal services alongside of
containers. Therefore, baremetal steps may be required depending on the service
and they are always executed before the corresponding container step.

The list below represents the correlation between the baremetal and the
containers steps. These steps are executed sequentially:


View the list of images on the undercloud’s docker-distribution registry

To view the list of images on the undercloud’s docker-distribution registry using the following command:

(undercloud) $ curl | jq .repositories[]

To view a list of tags for a specific image, use the skopeo command:

(undercloud) $ curl -s | jq .tags


OSD refusing to start with "ERROR: osd init failed: (1) Operation not permitted"

Main issue is: OSD refusing to start with "ERROR: osd init failed: (1) Operation not permitted"
Log error:


Get IPMI IP address from OS

First check that you have ipmitool installed:

[root@lykan ~]# yum provides ipmitool
Last metadata expiration check: 0:06:54 ago on Thu 21 Nov 2019 10:39:22 PM CST.
ipmitool-1.8.18-10.fc29.x86_64 : Utility for IPMI control
Repo : fedora
Matched from:
Provide : ipmitool = 1.8.18-10.fc29



Improve user experience using QEMU/KVM with Windows guest

A lot of sysadmins, SRE o wherever you want to call us, using native Linux in our laptops have the need to use virtual machines running Windows (some support, pentesting tasks, etc), if you are passionate about running periodics updates by now you figure out the main problem of this, if not, you will; the main problem is that on every kernel upgrade you will lose the modules of vmware or virtualbox, the best solution for this is to use QEMU/KVM.


fake_pxe as pm_type in RHOSP13 (TripleO + OpenStack Queens)

So, in RHOSP13 fake_pxe is being deprecated to change in RHOSP14 for manual-management, the problem is that is just in between the migration, so there is not a clean way to use fake_pxe in RHOSP13.
Other change is in the installation of undercloud, the option enabled_drivers is now DEPRECATED an changed by enabled_hardware_types.

What now, in order to being able to use fake_pxe as a pm_type first install the undercloud without the options enabled_drivers, only use enabled_hardware_types and add at the end manual-management, like this:


How to Boot into Single User Mode in CentOS/RHEL 7

DISCLAIMER: this is not my post is only a copy, in case the original get deleted or whatever, posting on my personal blog get easier for me to find it. You can find the original one in this link https://vpsie.com/knowledge-base/boot-single-user-mode-centos-rhel-vpsie/

The first thing to do is to open Terminal and log in to you CentOS 7 server.

After, restart your server wait for GRUB boot menu to show.

Next step is to select your Kernel version and press


Convert string <-> int64 using golang #go-nuts

I believe that if you are going to work with timestamps is better to do it in epoch stamps, so in GO epoch is type int64.

XFS online resize

You're working on an XFS filesystem, in this case you need to use xfs_growfs instead of resize2fs. Two commands are needed to perform this task :

# growpart /dev/sda 1

growpart is used to expand the sda1 partition to the whole sda disk.

# xfs_growfs -d /dev/sda1

xfs_growfs is used to resize and apply the changes.

# df -h


Subscribe to Headup RSS