Providing Solutions For Life

OpenStack Dashboard - Horizon - Error: the server refused the connection

When trying to access the instance's console from Horizon, that has been spun up we get the error, "the server refused the connection"



Check the nova.conf file on the Controller node if you have a several node setup.

novncproxy_base_url=http://127.0.0.1:6080/vnc_auto.html

when you inspect the element from chrome, you can see that the instance console is trying to connect to the controller on that port.

Doing a telnet from the box from where your are access on port 6080 should also fail, as that port might not be accessible from outside.

Hence this is clearly issue with the port and if you are on Centos you might already have sensed the culprit! The IPTABLES!

Adding a rule as as the one below and saving the tables should help access the console.

```iptables -I INPUT 7 -m state --state NEW -p tcp --dport 6080 -j ACCEPT```
```service iptables save```

Hope this helps you, leave us those comments!

Update

This error can also come up if the novncproxy has stopped working as well, when we check the status, we see

openstack-nova-novncproxy dead but pid file exists

in that case, doing the following should help

[root@meghdoot images(keystone_admin)]# service openstack-nova-novncproxy start
Starting openstack-nova-novncproxy:                        [  OK  ]
[root@meghdoot images(keystone_admin)]# service openstack-nova-novncproxy status
openstack-nova-novncproxy (pid  22487) is running...

Take aways from the Phoenix project book



I completed reading the awesome Pheonix project book and as is normal for the lessons to fade away, I might forget all of it as the days go by, but the summary of what I loved the most in this book is

Every work center is made up of four things. 
The machine. 
The man. 
The method. 
And the measures.
 And one more
First way helps us understand how to create fast flow of work from Dev to Ops. 
Second way shows us how to shorten and amplify feedback ... 
Third shows us how to create a culture that simultaneously foster  experimentation, learning from failure and understanding that repetition and practice are the  prerequisites to mastery.

 Even though it was monotonous at times, and this book could have continued to be interesting until the last page if it could be shortened, but it was a great book and helped me to come across the master piece "The Goal" which I am reading now


Configuration management in OpenStack

"Don't use Chef or Puppet, use the native Heat for Openstack Config management"

this statement from our peer led me to explore and find out that Heat can only be used for orchestration purpose, in that, it can bring up the virtual machines and the underlining support systems that they would need like routers and switches but would not be able to configure the instances that have come up, for this we would need to continue using Chef or Puppet or Ansible.

"Heat primarily manages infrastructure, but the templates integrate well with software configuration management tools such as Puppet and Chef"
https://wiki.openstack.org/wiki/Heat


Cloud Orchestration is not a replacement for server configuration tools such as Puppet and Chef. They are very complementary. You will continue to use Chef and Puppet to “template-ize” your server software configurations, while Cloud Orchestration and its HOT templates will help you create a full stack that includes all the infrastructure resources required for your stack. Cloud Orchestration allows you to quickly bootstrap your preferred software configuration management solution. With Chef, we have gone several steps further and provided direct support to specify the cookbooks and Berksfile you want deployed.
Source