Home Assistant: Checking configuration.yaml for errors

alexa-512x512

See instructions below on how to verify your configuration.yaml.

Ssh into your Home Assistant host. In my environment, I am running home assistant on a Raspberry Pi 2.

First I ssh as root. I have manually set the root password and have enabled root logins via /etc/ssh/sshd_config.  I have also added a static DNS entry for my Raspberry Pi 2.

 $ ssh root@ha

Su to the user, homeassistant.

root@ha:/var/log# su – homeassistant

Then run the command below.

homeassistant@ha:~ $ /srv/homeassistant/bin/hass –script check_config
Testing configuration at /home/homeassistant/.homeassistant

If you run into an error, you should see output similar to the example below.

homeassistant@ha:~ $ /srv/homeassistant/bin/hass –script check_config
Testing configuration at /home/homeassistant/.homeassistant
17-02-27 18:20:43 ERROR (MainThread) [homeassistant.bootstrap] Invalid config for [media_player.directv]: required key not provided @ data[‘host’]. Got None. (See ?, line ?). Please check the docs at https://home-assistant.io/components/media_player.directv/
Failed config
media_player.directv:
platform: directv

In the example above, there is an issue with my directv config. I will need to troubleshoot.

 

Creating and Deleting OpenStack Pacemaker IP Addresses

bild_go-clusters-34-nichtinsocialmediaverwenden

You can use the steps below if you need to change managed IP resources, for example, if you need to re-IP your RHEL OSP Overcloud endpoints.

In this example, we are changing a managed VIP from one IP to another.

First, we get a good look at the resource that we want to delete. Here we are going to delete the resource ip-99.239.203.25. This resource starts the VIP, 99.239.203.25.

# pcs resource show ip-99.239.203.25
Resource: ip-99.239.203.25 (class=ocf provider=heartbeat type=IPaddr2)
Attributes: ip=99.239.203.25 cidr_netmask=32
Operations: start interval=0s timeout=20s (ip-99.239.203.25-start-interval-0s)
stop interval=0s timeout=20s (ip-99.239.203.25-stop-interval-0s)
monitor interval=10s timeout=20s (ip-99.239.203.25-monitor-interval-10s)

Now let’s actually delete it.

# pcs resource delete ip-99.239.203.25
Attempting to stop: ip-99.239.203.25…Stopped

Now lets create the replacement VIP

# pcs resource create ip-99.239.203.10 ocf:heartbeat:IPaddr2 ip=99.239.203.10 cidr_netmask=32 op monitor interval=10s

Now, let’s take a good look at it.

# pcs resource show ip-99.239.203.10
Resource: ip-99.239.203.10 (class=ocf provider=heartbeat type=IPaddr2)
Attributes: ip=99.239.203.10 cidr_netmask=32
Operations: start interval=0s timeout=20s (ip-99.239.203.10-start-interval-0s)
stop interval=0s timeout=20s (ip-99.239.203.10-stop-interval-0s)
monitor interval=10s (ip-99.239.203.10-monitor-interval-10s)

Now we need to check to make sure that the VIP started on one of our OpenStack controllers.

# pcs status | grep 99.239.203.10
ip-99.239.203.10 (ocf::heartbeat:IPaddr2): Started ctrl01

For good measure, let’s make sure we can ping it.

# ping 99.239.203.10
PING 99.239.203.10 (99.239.203.10) 56(84) bytes of data.
64 bytes from 99.239.203.10: icmp_seq=1 ttl=64 time=0.781 ms
64 bytes from 99.239.203.10: icmp_seq=2 ttl=64 time=1.21 ms

 

 

Your Cloud Installed Before Lunch with QuickStart Cloud Installer 1.0

What if I told you that you can have your Red Hat Enterprise Linux (RHEL) based Cloud infrastructure, with Red Hat Virtualization, OpenStack, OpenShift and CloudForms all setup before you have to s…

Source: Your Cloud Installed Before Lunch with QuickStart Cloud Installer 1.0

Component, Plug-In, and Driver Support in RHEL OpenStack Platform

 

OpenStack-logo

 

This article details all supported drivers and plugins for each RHEL OSP component (Cinder, Glance, Neutron, etc). Last updated 7/11/16.

Link Below:

https://access.redhat.com/articles/1535373

OpenShift Enterprise 3.1 Lab Setup

Overview OpenShift Enterprise is a PaaS platform that enables digital transformation. It lets you build and run traditional (mode 1) as well as cloud-native (mode 2) applications. OpenShift is buil…

Source: OpenShift Enterprise 3.1 Lab Setup

Driving in the Fast Lane – CPU Pinning and NUMA Topology Awareness in OpenStack Compute

Now that we have set up the guest virtual machine instances so that they will only be allowed to run on cores 2, 3, 6, and, 7 we must also set up the host processes so that they will not run on these cores – restricting themselves instead to cores 0, 1, 4, and 5. To do this we must set the isolcpus kernel argument – adding this requires editing the system’s boot configuration.

Source: Driving in the Fast Lane – CPU Pinning and NUMA Topology Awareness in OpenStack Compute

RHEV/oVirt – 503 Service Temporarily Unavailable

OVirt-logo-highres

This post will walk you through fixing the RHEV/oVirt error shown below. Note that this error was received when trying to load the RHEV-M/oVirt Engine web interface.

ovirt-rhev

Note that these instructions worked for me in a known working environment, where the web interface was previously working but had failed after an unscheduled restart of the host.

First lets restart the ovirt-engine.

# service ovirt-engine restart
Stopping oVirt Engine: [FAILED]
Starting oVirt Engine: [ OK ]

Next we restart the ovirt-websocket-proxy

# service ovirt-websocket-proxy restart
Stopping oVirt Engine websockets proxy: [ OK ]
Starting oVirt Engine websockets proxy: [ OK ]

Finally, we restart Apache.

# service httpd restart
Stopping httpd: [ OK ]
Starting httpd: [ OK ]