Hi,
I'm planning to perform a 5 node installation of openstack with the
first node being the master and the rest being compute nodes. I have the
following setup:
Master node:
eth0: 10.2.0.1 (public ip)
eth1: 192.168.2.1 (private ip)
Will use devstack to deploy openstack on this node
Compute
It sounds like you are trying to use devstack for a production install,
this is not recommended. As the name implies, "devstack" is for a
development rather than production install of OpenStack..
You would be better off using either the native Ubuntu packages (unless you
plan on using keystone or
Devstack isn't for production. I recommend using packages (even if
they are your own).
repeat: WHAT FOLLOWS IS NOT FOR PRODUCTION!
If you are just experimenting with a multi-node dev deploy - you can
set a few options in your nova.conf:
--sql_connection=mysql://$MYSQL_USER:$PASS@$MASTER_IP/nova
Hi,
Thanks for the replies. I'm setting up openstack primarily for
educational purposes and so am open to experimenting. As I couldn't get the
dashboard running with the ubuntu packages, I opted for devstack. I'm
really impressed with it so far. Instances on the compute nodes weren't
getting me
Hi,
I set up openstack on my second node with devstack as suggested. I
could launch instances from the dashboard on the master node but couldn't
view the vms on the second node with the VNC console in the dashboard. But
the VNC console worked fine with instances launched on the master. On my
la
>
>
>
> In this case, how should i tweak my localrc file to get network access
> for my VMs? I have setup SNAT on the master node to provide external
> network access to machines in the network 192.168.2.0/24. All my VMs are
> given ips in the fixed range 192.168.3.0/24.
>
Is each machine conf
Hi,
192.168.3.0/24 is the fixed_range in my localrc for both nodes. My
second node doesn't have direct access to the public network. It has only
one interface (eth1) connected to the private network. It has an ip of
192.168.2.2. Is there a way set this node up as a compute node without
connecti
Hey Sagar,
It does sound like you need to use eth1 for FLAT_INTERFACE - but note this
parameter is used when your network is first created with nova-manage, so
if you change this you will need to re-run stack.sh (it isn't enough to
update your nova.conf), which is probably best to do after a reboo
Hi,
Thanks for the replies. I tried a clean installation with eth1 as my
flat interface and it worked perfectly well. I can now ping and SSH to my
VMs on either node from the other. They're also getting their metadata
correctly. Only problem is that I can't access VMs on the second node via
the
Hey Sagar,
I'll take a quick guess here that maybe your servers have host names that
don't resolve. So for example, if host1 is 'server1' and host2 is
'server2' the vnc proxy may try connect using those hostnames (connecting
to the latter host would probably fail). A quick fix could be to add an
Hi Anthony,
Thank you very much. That worked like a charm. I can now launch
and access instances running on different nodes. Instances without
disk storage (m1.tiny) work great. But when I try to use flavors with
disk storage, the dashboard displays an 'Error' state after the
'Build' state. Sin
Hi,
Regarding the error I described in my previous post, I ran 'screen -r'
and switched to the g-api screen. I found this message being displayed:
2012-01-01 10:43:22DEBUG [eventlet.wsgi.server] Traceback (most recent
> call last):
> File "/usr/lib/python2.7/dist-packages/eventlet/wsgi.p
Hey Sagar,
Are you able to produce logs from n-cpu? If you are in the screen session,
you should be able to switch to the window (ctrl-a + [number]) of that name
and use ctrl-a + [ to enable interactive scrollback (uses vim keybindings).
I think there is a chance that some data from a previous ru
13 matches
Mail list logo
