centos – stackblog.net

VNC and firewalld on Centos 7 compute node

mazur OpenStack March 14, 2015March 14, 2015centos, juno, nova, openstack 0 Comment

By default firewalld service is enabled and may cause troubles in accessing via VNC to instances running on Centos compute node.

Solution:

By default zone=public is used, so it is enough just to add 5900/5901 ports or/and vnc-server service to this zone:

firewall-cmd --zone=public --add-port=5900/tcp
firewall-cmd --zone=public --add-port=5901/tcp

1 2	firewall-cmd --zone=public --add-port=5900/tcp firewall-cmd --zone=public --add-port=5901/tcp

Result:

public (default, active)
  interfaces: br-int br-tun eno16777736 eno33554984 eno50332208
  sources:
  services: dhcpv6-client ssh vnc-server
  ports: 5900/tcp 5901/tcp
  masquerade: no
  forward-ports:
  icmp-blocks:
  rich rules:

public (default, active)

interfaces: br-int br-tun eno16777736 eno33554984 eno50332208

sources:

services: dhcpv6-client ssh vnc-server

ports: 5900/tcp 5901/tcp

masquerade: no

forward-ports:

icmp-blocks:

rich rules:

Nova installation on Centos 7

mazur OpenStack March 14, 2015centos, juno, nova, openstack 0 Comment

RabbitMQ

After starting rabbitmq-server service it is not possible to change password using:

rabbitmqctl change_password guest password

1	rabbitmqctl change_password guest password

Error:

Error: unable to connect to node rabbit@localhost: nodedown

1	Error: unable to connect to node rabbit@localhost: nodedown

Solution:
In file /etc/systemd/system/multi-user.target.wants/rabbitmq-server.service change

ExecStartPre=-/bin/sh -c "/usr/lib/rabbitmq/bin/rabbitmqctl status > /dev/null 2>&1"

1	ExecStartPre=-/bin/sh -c "/usr/lib/rabbitmq/bin/rabbitmqctl status > /dev/null 2>&1"

to – add sudo

ExecStartPre=-/bin/sh -c "sudo /usr/lib/rabbitmq/bin/rabbitmqctl status > /dev/null 2>&1"

1	ExecStartPre=-/bin/sh -c "sudo /usr/lib/rabbitmq/bin/rabbitmqctl status > /dev/null 2>&1"

And restart rabbitmq-server:

systemctl restart rabbit-mq

1	systemctl restart rabbit-mq

Nova incompatibility

Packages for nova which are downloaded with yum contain nova version which is incomaptible with that is running on controller node (Ubuntu):

Controller (Ubuntu 14.04):

nova-manage version
2014.2

1 2	nova-manage version 2014.2

Compute (Centos 7):

nova-manage version
2014.2.1-1.el7.centos

1 2	nova-manage version 2014.2.1-1.el7.centos

Problem is described here:
https://ask.openstack.org/en/question/57296/juno-centos-7-buildabortexception-build-of-instance-aborted-failed-to-allocate-the-networks-not-rescheduling/?answer=57883#post-id-57883

Solution:
Install packages from EPEL repo manually (only 3 days older):

https://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-7/

Packages to install:

openstack-nova-common-2014.2-2.el7.centos.noarch.rpm
openstack-nova-compute-2014.2-2.el7.centos.noarch.rpm
python-nova-2014.2-2.el7.centos.noarch.rpm

openstack-nova-common-2014.2-2.el7.centos.noarch.rpm

openstack-nova-compute-2014.2-2.el7.centos.noarch.rpm

python-nova-2014.2-2.el7.centos.noarch.rpm

I had to forcefully install them using rpm -ivh –force then I restarted openstack-nova-compute service.
After this instances spawned correctly, yet I could not reach them (iptables rules missing, so I disabled iptables).

DHCP addresses got distributed to the instances correctly and I could reach internet from them via my Ubuntu-AIO which acts as a gateway to the internet as well.