Ask Your Question

filpano's profile - activity

2014-02-18 11:41:05 -0600 received badge  Famous Question (source)
2014-01-06 04:21:37 -0600 received badge  Famous Question (source)
2013-12-12 00:03:16 -0600 received badge  Notable Question (source)
2013-12-11 22:24:39 -0600 commented answer Single node installation for Havana for testing purposes?

Thank you very much. Since it is exactly what I need, I have accepted this as an answer.

2013-12-11 22:10:31 -0600 received badge  Scholar (source)
2013-12-11 16:13:32 -0600 received badge  Popular Question (source)
2013-12-11 13:48:55 -0600 commented answer Single node installation for Havana for testing purposes?

Does devstack offer the same computational capabilities as OpenStack? That is, does it use the exact same services and resources in its environment?

2013-12-11 12:21:11 -0600 commented answer openstack havana single or multinode implementation with ubuntu 12.04 server

@Anand TS : does that mean that a single-node install on Ubuntu 12.04 is not possible?

2013-12-11 12:19:17 -0600 asked a question Single node installation for Havana for testing purposes?

Hello everyone,

I was looking at a couple of documents including the newly updated official documentation as well at this helpful website and wanted to find out whether it would be possible to have a single-node install of Havana for testing purposes (Ubuntu 12.04 or Debian 7).

I had a working deployment of Folsom working on a single node, but it included some very patchy fixes such as creating a dummy network interface which I would prefer to avoid with Havana, as I wish to actually use Neutron effectively.

Is a single-node install possible? If so, could anyone provide a guide?

2013-10-27 13:32:32 -0600 received badge  Famous Question (source)
2013-10-18 12:48:30 -0600 received badge  Enthusiast
2013-10-16 12:33:31 -0600 received badge  Notable Question (source)
2013-10-15 03:36:14 -0600 received badge  Nice Question (source)
2013-10-15 03:36:07 -0600 received badge  Popular Question (source)
2013-10-14 13:46:08 -0600 asked a question Openstack seems to not map internal IPs to local network properly

Hello everyone,

I have a very confusing issue which I can't seem to resolve.

I followed a guide by Loic Dachary on installing Openstack Folsom on Wheezy, and deployed it on two hosts: a cluster node, and my workstation.

On these two hosts I'm running a benchmarking application that communicated from one host to the other in the following fashion:

image description

The following are the routing tables for the node host, the workstation, and the internal VMs:

image description

(Note: the 10.0.1.0 entry was for an additional network interface. It ended up being unneeded and is not up on any of the VMs. Hence, it has no impact since nothing is being routed to destination 10.0.1.x)

Now, my issue is the following:

The benchmarking application starts an RMI call from one of the VMs on the workstation, (say 10.0.0.2) to one of the VMs on the node (say, 172.23.3.100).

It is my understanding that the following should occur:

  1. The VM sees desination 172.23.x.x network route and goes through the default route 10.0.0.1 (the workstation compute host)

  2. The nova network service sees that 10.0.0.2 is mapped to some IP (say, 172.23.12.1) on the local network. So it changes the source IP to that.

  3. The workstation host sees destination 172.23.x.x and routes through 172.23.1.1 to 172.23.3.8.

  4. Nova network sees the IP and since the mapping say, 172.23.3.100 -> 10.0.0.7 exists, it changes destination to 10.0.0.7.

  5. VM on node with internal IP 10.0.0.7 gets the the request from workstation VM. (@ 172.23.12.1).

This works fine. The actual request gets sent. However, there is something wrong with the reply.

Here's the log of my application run just after the request is sent:

RemoteException was: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
->      java.rmi.ConnectIOException: Exception creating connection to: 10.0.0.7; nested exception is:
->      java.net.NoRouteToHostException: No route to host

So it must be the case that the node VM replied with it's source being 10.0.0.7. In other words, the nova network service never changed the source IP of the node VM to its routable 172.23.x.x address!

How is this possible? Both VM's can ping themselves (node->workstation, workstation->node), and I don't see anything wrong with the routing tables.

The only odd factor I can see is the following traceroute information:

Workstation VM -> Node

root@client-01:~# traceroute 172.23.3.8
traceroute to 172.23.3.8 (172.23.3.8), 30 hops max, 60 byte packets
 1  10.0.0.1 (10.0.0.1)  0.406 ms  0.399 ms  0.390 ms
 2  172.23.3.8 (172.23.3.8)  0.381 ms  0.378 ms  0.422 ...
(more)
2013-10-11 14:40:59 -0600 received badge  Notable Question (source)
2013-10-10 10:00:56 -0600 received badge  Popular Question (source)
2013-08-28 19:17:36 -0600 received badge  Editor (source)
2013-08-28 18:50:31 -0600 asked a question Enabling two-way network bridging on instances?

I'm trying to setup a testing environment using Openstack on a Debian 7 host. My node is located on a private network, at 172.23.3.8 and hosts several different VMs, but I'll take my Webserver VM as an example.

Openstack tells me that the DHCP server assigned the Webserver VM with the IP 172.23.3.100. Similarly, the internal service assigned the private IP 10.0.0.3 to the Webserver VM.

The issue is however, this seems to be a one-way bridge! I can SSH into 172.23.3.100 and I can access the VM located at the internal IP 10.0.0.3. However, the VM itself isn't aware of the mapping. I wished to set up an Apache2 server, and no suprise, I cannot access it from outside the internal 10.x VM network.

Is this intended? Is there a way to circumvent this and allow for two-way mapping? I have been consulting the documentation but haven't found anything that seems promising.

2013-08-01 03:07:22 -0600 received badge  Good Question (source)
2013-07-17 04:26:54 -0600 received badge  Famous Question (source)
2013-07-17 04:26:54 -0600 received badge  Notable Question (source)
2013-07-14 22:29:26 -0600 received badge  Popular Question (source)
2013-07-12 18:44:14 -0600 received badge  Nice Question (source)
2013-07-12 14:11:18 -0600 received badge  Student (source)
2013-07-12 12:38:54 -0600 asked a question Openstack services cannot talk to RabbitMQ: Connection refused but log says unreachable?

I've got single-node Openstack Folsom deployment on a Debian 7.1 server. I've followed the Folsom guide so far and have got everything set up, but when I try to log in through the dashboard, I get the following message:

ConnectionError at /admin/

[Errno 111] Connection refused

Request Method:     GET
Request URL:    https://172.23.18.174/admin/
Django Version:     1.4.5
Exception Type:     ConnectionError
Exception Value:    

[Errno 111] Connection refused

Exception Location:     /usr/lib/python2.7/dist-packages/requests/adapters.py in send, line 243
Python Executable:  /usr/bin/python
Python Version:     2.7.3
Python Path:    

['/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../..',
 '/usr/lib/python2.7',
 '/usr/lib/python2.7/plat-linux2',
 '/usr/lib/python2.7/lib-tk',
 '/usr/lib/python2.7/lib-old',
 '/usr/lib/python2.7/lib-dynload',
 '/usr/local/lib/python2.7/dist-packages',
 '/usr/lib/python2.7/dist-packages',
 '/usr/lib/pymodules/python2.7',
 '/usr/share/openstack-dashboard/',
 '/usr/share/openstack-dashboard/openstack_dashboard']

Server time:    Fri, 12 Jul 2013 16:04:49 +0000

Now I've researched this issue somewhat and have found that connection refused stems from a misconfigured quantum.conf. So I double checked, and my quantum.conf is the following (relevant settings only):

# Address to bind the API server
bind_host = 0.0.0.0

# Port the (sic) bind the API server to
bind_port = 9696

...

# IP address of the RabbitMQ server
rabbit_password = password
# Port where RabbitMQ server is running/listening
rabbit_port = 5672
...
# User ID used for RabbitMQ connections
rabbit_userid = guest

... (everything else is unchanged)

So the login credentials should be OK (nova.conf credentials match too). Other credentials are, of course, sourced upon login.

However, my quantum-server.log shows the following:

2013-07-12 12:00:42 ERROR [quantum.openstack.common.rpc.common] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 29 seconds.

Anyone know what exactly is going on here? One thing that I noticed was that I lack a /etc/rabbitmq/rabbitmq.conf file, although I saw it mentioned somewhere. Might this have anything to do with this?

Upon further inspection, it would seem that the nova services I have installed so far cannot talk to RabbitMQ at all (as nova-scheduler, nova-consoleauth, nova-cert and nova-conductor all show XXX as their state), as I've found the same error message from quantum logs in the nova-cert.log:

2013-07-12 12:26:47.526 ERROR nova.openstack.common.rpc.common [req-705a947d-28b8-4c1e-8475-2afb19ad96a6 None None] AMQP server on 172.23.18.174:5672 is unreachable: Socket closed. Trying again in 30 seconds.

It should be noted that the machine running all these services is 172.23.18.174. However, I've tried setting both IPs in quantum.conf and nova.conf to either one or the other, but this did not alleviate the issue. Anyone know what is going on here?