<html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> On 04/12/2013 03:34 AM, Vogel Nicolas wrote: <blockquote cite="mid:B96312B5522D4C4B962E07BC3602A9D574EADE56@EINTMBX02.einet.ad.eivd.ch" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> <div class="WordSection1"> Just 1 more question about floating IP :<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> </div> </blockquote> yes, if you want the instance to have a public address, the floating IP can be on the same network as the public interface. <blockquote cite="mid:B96312B5522D4C4B962E07BC3602A9D574EADE56@EINTMBX02.einet.ad.eivd.ch" type="cite"> <div class="WordSection1"> Thanks,<o:p></o:p> Nico.<o:p></o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Jacob Liberman [<a class="moz-txt-link-freetext" href="mailto:jliberma@redhat.com">mailto:jliberma@redhat.com</a>] Sent: jeudi 11 avril 2013 17:28 To: Vogel Nicolas Cc: '<a class="moz-txt-link-abbreviated" href="mailto:rhos-list@redhat.com">rhos-list@redhat.com</a>'; 'Perry Myers' Subject: Re: [rhos-list] how to install more compute nodes<o:p></o:p> </div> </div> <o:p> </o:p> On 04/11/2013 10:19 AM, Vogel Nicolas wrote: <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> Thanks Jacob for this infos !<o:p></o:p> 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?<o:p></o:p> </blockquote> 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 <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> Do I also have to modify or complete something on my controller node so that he knows about the new compute node?<o:p></o:p> </blockquote> 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" <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <o:p></o:p> Cheers,<o:p></o:p> <o:p></o:p> Nicolas.<o:p></o:p> <o:p></o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Jacob Liberman [<a moz-do-not-send="true" href="mailto:jliberma@redhat.com">mailto:jliberma@redhat.com</a>] Sent: jeudi 11 avril 2013 16:51 To: Perry Myers Cc: Vogel Nicolas; '<a moz-do-not-send="true" href="mailto:rhos-list@redhat.com">rhos-list@redhat.com</a>' Subject: Re: [rhos-list] how to install more compute nodes<o:p></o:p> </div> </div> <o:p></o:p> On 04/11/2013 09:23 AM, Perry Myers wrote: <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <pre>On 04/11/2013 09:59 AM, Vogel Nicolas wrote:<o:p></o:p></pre> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <pre>Hi,<o:p></o:p></pre> <pre> <o:p></o:p></pre> <pre> <o:p></o:p></pre> <pre> <o:p></o:p></pre> <pre>I just finished to install a controller node with the latest official<o:p></o:p></pre> <pre>RedHat doc (but I’m working with CentOS 6.3 and EPEL packages).<o:p></o:p></pre> <pre> <o:p></o:p></pre> <pre>I’m using nova-network with FlatDHCP and not quantum in this test.<o:p></o:p></pre> <pre> <o:p></o:p></pre> <pre>Now I wan’t to extend my cloud with more compute nodes but i’m not<o:p></o:p></pre> <pre>really sure about the different services who must be installed on each<o:p></o:p></pre> <pre>compute node.<o:p></o:p></pre> <pre> <o:p></o:p></pre> <pre>In a first time, I wan’t to centralize all my services on the<o:p></o:p></pre> <pre>controller, the computes nodes must give me just more CPU and more disk<o:p></o:p></pre> <pre>space. So I think that basically I just need to install nova-compute,<o:p></o:p></pre> <pre>nova-api and cinder on the compute nodes is that right?<o:p></o:p></pre> </blockquote> <pre> <o:p></o:p></pre> <pre>nova-compute and cinder, but I do not think you need additional nova-api<o:p></o:p></pre> <pre>on the add'l compute nodes<o:p></o:p></pre> </blockquote> 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. <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <pre> <o:p></o:p></pre> <pre> <o:p></o:p></pre> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <pre>How do I configure this services on the compute node so they know that<o:p></o:p></pre> <pre>Keystone, Glance, etc.. are on the controller?<o:p></o:p></pre> </blockquote> <pre> <o:p></o:p></pre> <pre>Jacob, do you have a writeup around this area? Taking an existing RHOS<o:p></o:p></pre> <pre>install and adding compute nodes to it?<o:p></o:p></pre> </blockquote> yes, it will be publicly available in the next few weeks. i am happy to answer specific questions before the document is available. <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <pre> <o:p></o:p></pre> <pre>Perry<o:p></o:p></pre> <pre> <o:p></o:p></pre> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <pre>If someone has nova.conf and keystone.conf example from it would be very<o:p></o:p></pre> <pre>helpful.<o:p></o:p></pre> <pre> <o:p></o:p></pre> <pre> <o:p></o:p></pre> </blockquote> </blockquote> 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 <a moz-do-not-send="true" href="mailto:sql_connection=mysql://nova:9f63b4ec6b074b1c@10.16.137.100/nova">sql_connection=mysql://nova:9f63b4ec6b074b1c@10.16.137.100/nova</a> 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=<a moz-do-not-send="true" href="http://10.16.137.100:6080/vnc_auto.html">http://10.16.137.100:6080/vnc_auto.html</a> 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 <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <pre> <o:p></o:p></pre> <pre> <o:p></o:p></pre> <pre>Thanks in advance,<o:p></o:p></pre> <pre> <o:p></o:p></pre> <pre> <o:p></o:p></pre> <pre> <o:p></o:p></pre> <pre>Nicolas.<o:p></o:p></pre> </blockquote> <pre> <o:p></o:p></pre> </blockquote> <o:p></o:p> </blockquote> <o:p> </o:p> </div> </blockquote> </body> </html>