openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #06335
Re: Multinode installation (with devstack on the master)
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
--rabbit_host=$MASTER_IP
--rabbit_password=$RABBIT_PASS
--glance_api_servers=$MASTER_IP:9292
My team (creators of devstack) do a multi-node devstack deploys every
day (for development - for production we use crowbar/chef, ubuntu, and
package)
With devstack on multiple nodes you can create a localrc how you
normally would then add:
master node: you need all the services
ENABLED_SERVICES=n-vol,g-api,g-reg,key,n-api,n-cpu,n-net,n-sch,n-vnc,horizon,mysql,rabbit,swift,openstackx
child nodes: you only need the workers
MYSQL_HOST=$MASTER_IP
RABBIT_HOST=$MASTER_IP
GLANCE_HOSTPORT=$MASTER_IP:9292
ENABLED_SERVICES=n-vol,n-cpu,n-net,n-api
notes:
* we run n-api on each node to provide the metadata service (you can
also setup iptables routes to forward requests to the metadata service
to the main nova-api node). We plan on switching to
https://github.com/openstack/nova/blob/master/bin/nova-api-metadata on
the child nodes.
* we use --network_manager=nova.network.manager.FlatDHCPManager with
--force_dhcp_release --multi_host and --send_arp_for_ha
On Tue, Dec 27, 2011 at 10:05 AM, Kiall Mac Innes <kiall@xxxxxxxxxxxx> wrote:
> 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 horizon/dashboard[1]) or 3rd party or DIY native
> packages..
>
> I've created updated packages based on the Ubuntu ones that work for all
> services, and scripted the install along the lines of devstack if they are
> of any use to you, I keep them relatively up to date with the latest diablo
> bug files:
>
> Packages @ https://launchpad.net/~managedit/+archive/openstack
> Scripts @ https://github.com/managedit/openstack-setup
>
> Note 1: The Oneiric keystone/dashboard packages do not currently work. The
> Ubuntu guys are working to fix this, but I don't believe the fixed packages
> have landed yet. Some of them are on this list, they can correct me if I'm
> wrong, or maybe provide an ETA. To reiterate: If you do not plan to
> use keystone/dashboard, then the stock Ubuntu Oneiric packages are fine.
>
> Thanks,
> Kiall
>
>
> On Tue, Dec 27, 2011 at 12:49 PM, Frost Dragon <frostdragon777@xxxxxxxxx>
> wrote:
>>
>> 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 nodes:
>> eth0: will not be used
>> eth1: 192.168.2.2 - 192.168.2.5 (private ips)
>> Will run 'apt-get install nova-compute' alone
>>
>> I'm using ubuntu 11.10 (oneiric). With the above setup, what should be the
>> contents of nova.conf on the compute nodes? Should I specify anything
>> particular in localrc before installing devstack? Is it possible to get
>> openstack running and working with this setup? Thanks in advance for your
>> suggestions.
>>
>> Regards,
>> Sagar
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References