[rhos-list] how to install more compute nodes
Jacob Liberman
jliberma at redhat.com
Fri Apr 12 13:36:20 UTC 2013
On 04/12/2013 03:34 AM, Vogel Nicolas wrote:
>
> Just 1 more question about floating IP :
>
> For my controller, I used the em1 interface for management purpose and
> for the communication between all openstack services (subnet
> 10.192.1.x./24). I configured then em1 as my “flat interface” for my
> private VM subnet (192.168.x.x/24) and the demonetbr0 bridge. My em2
> interface is the “public interface”. Is that right? Em2 has already a
> fixed IP address and I want to allocate a floating IP from the same
> subnet to em2.
>
yes, if you want the instance to have a public address, the floating IP
can be on the same network as the public interface.
> Thanks,
>
> Nico.
>
> *From:*Jacob Liberman [mailto:jliberma at redhat.com]
> *Sent:* jeudi 11 avril 2013 17:28
> *To:* Vogel Nicolas
> *Cc:* 'rhos-list at redhat.com'; 'Perry Myers'
> *Subject:* Re: [rhos-list] how to install more compute nodes
>
> On 04/11/2013 10:19 AM, Vogel Nicolas wrote:
>
> Thanks Jacob for this infos !
>
> I think I must also create keystonerc_admin and
> keystonerc_username file on my controller and source it on demand
> to make my install right?
>
>
> it depends on how you make the changes
>
> if you are using the command line tools then yes
>
> if you are using packstack the keystonerc will be installed
> automatically wherever you install the client tools
>
> you can also download the user environment vars from the horizon dashboard
>
>
> Do I also have to modify or complete something on my controller
> node so that he knows about the new compute node?
>
>
> no, just start the services on the compute node. it will add itself if
> everything is configured correctly.
>
> you can verify with "nova-manage service list"
>
>
> Cheers,
>
> Nicolas.
>
> *From:*Jacob Liberman [mailto:jliberma at redhat.com]
> *Sent:* jeudi 11 avril 2013 16:51
> *To:* Perry Myers
> *Cc:* Vogel Nicolas; 'rhos-list at redhat.com
> <mailto:rhos-list at redhat.com>'
> *Subject:* Re: [rhos-list] how to install more compute nodes
>
> On 04/11/2013 09:23 AM, Perry Myers wrote:
>
> On 04/11/2013 09:59 AM, Vogel Nicolas wrote:
>
> Hi,
>
>
>
>
>
>
>
> I just finished to install a controller node with the latest official
>
> RedHat doc (but I’m working with CentOS 6.3 and EPEL packages).
>
>
>
> I’m using nova-network with FlatDHCP and not quantum in this test.
>
>
>
> Now I wan’t to extend my cloud with more compute nodes but i’m not
>
> really sure about the different services who must be installed on each
>
> compute node.
>
>
>
> In a first time, I wan’t to centralize all my services on the
>
> controller, the computes nodes must give me just more CPU and more disk
>
> space. So I think that basically I just need to install nova-compute,
>
> nova-api and cinder on the compute nodes is that right?
>
>
>
> nova-compute and cinder, but I do not think you need additional nova-api
>
> on the add'l compute nodes
>
>
> nova-compute, nova-network (if you want multi_host/HA networking)
> and nova-metadata-api if you are passing any customizations to the
> instances during boot
>
> you can run cinder-volumes on all nodes but there are some issues.
> better to use a centralized cinder server or cinder backed by a
> distributed file system.
>
> you specify the other service endpoints in the compute node's
> nova.conf.
>
>
>
>
>
>
> How do I configure this services on the compute node so they know that
>
> Keystone, Glance, etc.. are on the controller?
>
>
>
> Jacob, do you have a writeup around this area? Taking an existing RHOS
>
> install and adding compute nodes to it?
>
>
> yes, it will be publicly available in the next few weeks.
>
> i am happy to answer specific questions before the document is
> available.
>
>
>
>
>
> Perry
>
>
>
> If someone has nova.conf and keystone.conf example from it would be very
>
> helpful.
>
>
>
>
>
>
>
> Here is a nova.conf from a compute node.
>
> The controller IP (glance, keystone, cinder, nova-scheduler) is
> 10.16.37.100
> The compute node IP (nova-compute,nova-network) is 10.16.137.102
>
> the metadata_hostvalue may differ depending on what you are
> running where
>
>
> [DEFAULT]
> verbose=false
> connection_type=libvirt
> sql_connection=mysql://nova:9f63b4ec6b074b1c@10.16.137.100/nova
> <mailto:sql_connection=mysql://nova:9f63b4ec6b074b1c@10.16.137.100/nova>
> state_path=/var/lib/nova
> lock_path=/var/lib/nova/tmp
> glance_api_servers=10.16.137.100:9292
> metadata_host=10.16.137.100
> network_manager=nova.network.manager.FlatDHCPManager
> rootwrap_config=/etc/nova/rootwrap.conf
> service_down_time=60
> volume_api_class=nova.volume.cinder.API
> auth_strategy=keystone
> compute_driver=libvirt.LibvirtDriver
> public_interface=eth0
> dhcpbridge=/usr/bin/nova-dhcpbridge
> flat_network_bridge=br100
> flat_injected=false
> flat_interface=eth1
> floating_range=10.16.143.108/30
> fixed_range=172.16.2.0/24
> network_host=10.16.137.102
> force_dhcp_release=true
> dhcp_domain=novalocal
> logdir=/var/log/nova
> rpc_backend=nova.openstack.common.rpc.impl_qpid
> rabbit_host=localhost
> qpid_hostname=10.16.137.100
> libvirt_type=kvm
> libvirt_inject_partition=-1
> novncproxy_base_url=http://10.16.137.100:6080/vnc_auto.html
> vncserver_listen=10.16.137.102
> vncserver_proxyclient_address=10.16.137.102
> vnc_enabled=true
> image_service=nova.image.glance.GlanceImageService
> multi_host = True
> [trusted_computing]
> [keystone_authtoken]
>
>
> thanks, jacob
>
>
>
>
>
>
>
>
> Thanks in advance,
>
>
>
>
>
>
>
> Nicolas.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rhos-list/attachments/20130412/6a89cc97/attachment.htm>
More information about the rhos-list
mailing list