Ask Your Question

Xeek's profile - activity

2017-09-13 03:39:23 -0500 received badge  Nice Question (source)
2014-11-26 20:29:31 -0500 received badge  Enthusiast
2014-11-25 16:16:50 -0500 received badge  Famous Question (source)
2014-11-25 16:12:03 -0500 received badge  Notable Question (source)
2014-11-25 16:09:42 -0500 received badge  Popular Question (source)
2014-11-23 14:25:54 -0500 commented answer Unable to access instances' consoles from Openstack dashboard

Before juju could overwrite again, I changed the novncproxy_base_url to the compute node as you suggested, but of no use. And accessing http://10.10.10.104:6080/vnc_auto.html via browser says Failed to Connect to server ( code: 1006)

2014-11-23 14:12:40 -0500 commented answer Unable to access instances' consoles from Openstack dashboard

My changes to nova.conf on the compute node are all overwritten by juju. :( It has again set vnc_enabled=false. I found this warning at the top of nova.conf file "Configuration file maintained by Juju. Local changes may be overwritten." Any ideas to prevent this from happening?

2014-11-23 14:12:26 -0500 commented answer Unable to access instances' consoles from Openstack dashboard

My changes to nova.conf on the compute node are all overwritten by juju. :( It has again set vnc_enabled=false. I found this warning at the top of nova.conf file "Configuration file maintained by Juju. Local changes may be overwritten." Any ideas to prevent this from happening?

2014-11-23 03:08:56 -0500 received badge  Supporter (source)
2014-11-23 03:07:39 -0500 commented question Unable to access instances' consoles from Openstack dashboard

@dbaxps I've updated my post with the required data. Pls check.

2014-11-23 03:03:58 -0500 commented answer Unable to access instances' consoles from Openstack dashboard

I've updated my post with latest findings. Pls check.

2014-11-23 03:03:53 -0500 commented answer Unable to access instances' consoles from Openstack dashboard

I've updated my post with latest findings. Pls check.

2014-11-22 05:12:27 -0500 received badge  Student (source)
2014-11-22 02:46:51 -0500 asked a question Unable to access instances' consoles from Openstack dashboard

I successfully deployed openstack services on a MAAS+Juju setup. I logged into the dashboard and created a few instances. When I launch the instance, everything comes up fine( Status = Running ) but I am unable to access the console from the Web GUI. It says "console is currently unavailable. Please try again later." I checked the console logs tab and it seems to be fine. It shows all boot up logs until the login prompt

On searching for this on net someone suggested installing novaconsoleauth and nova-novncproxy on the compute which I did. But still no luck.

Can someone help?

EDIT: Thanks for the help guys. Here's how my nova.conf looks after your suggestions on the compute node

---Snip----
vnc_enabled = True
novncproxy_base_url=http://10.10.10.102:6080/vnc_auto.html
vncserver_proxyclient_address=10.10.10.102(This private IP was assigned to this node my MAAS)
vncserver_listen=0.0.0.0
novnc_enabled = False
ec2_dmz_host = 10.10.10.112
flat_interface = eth1
network_manager = nova.network.manager.FlatDHCPManager

But I am not sure whether the IP I've given is correct as my machine has a bunch of IPs

IP address for eth0:   130.245.158.193(NIC 1)
IP address for eth0:   130.245.158.195(NIC 2)
IP address for br0:    10.10.10.102
IP address for lxcbr0: 10.0.3.1
IP address for br100:  10.0.0.1
IP address for virbr0: 192.168.122.1

$root@slot13:~# netstat -lntp | grep 6080
tcp        0      0 0.0.0.0:6080            0.0.0.0:*               LISTEN      8002/python

And regarding the controller node, I have hosted on an LXC(LXC has a different IP than the machine on which it is running on ) on machine having private IP 10.10.10.104(assigned by MAAS). I went to the node with this IP and changed nova.conf to

----Snip
my_ip=10.10.10.104
vncserver_listen=10.10.10.104
vncserver_proxyclient_address=10.10.10.104

IPs on this controller machine

IP address for br0:    10.10.10.104
IP address for lxcbr0: 10.0.3.1

$root@slot12:~# netstat -lntp | grep 6080
tcp        0      0 0.0.0.0:6080            0.0.0.0:*               LISTEN      25602/python

And re-started nova-consoleauth and nova-novncproxy services on both compute and controller nodes. Still no use :(

2014-11-17 11:29:56 -0500 received badge  Famous Question (source)
2014-11-17 11:29:27 -0500 commented answer How to access instances from the outside world?

192.168.0.0 - 192.168.255.255 belong to the private IP address range right? How can they be used to reach the instances from the outside world?

2014-11-17 06:37:14 -0500 received badge  Notable Question (source)
2014-11-17 04:34:02 -0500 received badge  Popular Question (source)
2014-11-17 02:40:47 -0500 asked a question How to access instances from the outside world?

We've created a few instances on our MAAS+Juju+Openstack cloud. All these instances have been assigned private IPs but can access the internet via NAT. Only our MAAS cluster controller node has a public IP. Now how should we access these instances from the outside world?. Should we assign separate unique public IP address to each of these instances or is it possible to access them all without public IPs via NAT?

I understand there is a concept of associating a floating IP to an instance from a pool of IPs. But where shall I get the IP addresses that are required to be added to the pool?