<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Basing on your architecture picture , I think you mean ping VM that resides on Essex 2 from server containing Essex 1<div>I had a similar networking problem and i honestly don't know i fixed it ( didn't enable tunneling) , this is what i did</div><div>1- ifconfig eth0 0.0.0.0</div><div>2- dhclient br-int ( normally the bridge will take the address of eth0)</div><div><br></div><div>and pinging went back to working fine but i am still testing if there are any side effects</div><div>Try it out and txt me !</div><div><br></div><div>btw , i used your ubuntu 12.04 LTS cloud img and i can't seem to ping it but when i choose another image ( the default tty for example) it ping as a charm , probably you should pick another image !  </div><div> <br><br><div><div id="SkyDrivePlaceholder"></div><hr id="stopSpelling">Subject: RE: [Openstack] Instance IP assignment problem<br>From: emilien.openstack@gmail.com<br>To: skible@hotmail.fr<br>CC: openstack@lists.launchpad.net<br>Date: Thu, 3 May 2012 11:11:04 +0200<br><br>


  
  


Ok :<br>
<br>
<a href="http://paste.openstack.org/show/14797/" target="_blank">http://paste.openstack.org/show/14797/</a><br>
<br>
<br>
I know where is the problem but I dont know yet how to fix it :<br>
<br>
<br>
- Quantum creates TAP interface on ESSEX-2<br>
<br>
- From ESSEX-2, I can't ping VMs on ESSEX-1<br>
<br>
<br>
Here my ovs_quantum_plugin.ini :<br>
<br>
[DATABASE]<br>
sql_connection = mysql://ovs_quantum:<a href="mailto:password@10.15.100.40">password@10.68.1.40</a>:3306/ovs_quantum<br>
<br>
<br>
[OVS]<br>
integration-bridge = br-int<br>
<br>
<br>
[AGENT]<br>
root_helper = sudo<br>
<br>
<br>
<br>
Do we need enable bridge ?<br>
<br>
<br>
<br>
<br>
Le jeudi 03 mai 2012 à 10:00 +0100, Bilel Msekni a écrit :
<blockquote>
    èmm , can you do this on your instance : nova show %instance_Id so that i may see the problem in the resume of spawning ?
</blockquote>
<blockquote>
    and are you sure you have enough fixed ip addresses left for use ?<br>
    <br>
    The configuration of nova and quantum is almost the same as me and the instances are getting Fixed Ips without any problem !
</blockquote>
<blockquote>
    <br>
</blockquote>
<blockquote>
    
<hr align="center">
<br>
    Subject: RE: [Openstack] Instance IP assignment problem<br>
    From: emilien.openstack@gmail.com<br>
    To: skible@hotmail.fr<br>
    CC: salmanmk@live.com; openstack@lists.launchpad.net<br>
    Date: Thu, 3 May 2012 10:48:43 +0200<br>
    <br>
    All seems alright but not working yet.<br>
    <br>
    <br>
    <a href="http://paste.openstack.org/show/14791/" target="_blank">http://paste.openstack.org/show/14791/</a><br>
    <br>
    <br>
    <br>
    I have executed on both servers :<br>
    <br>
    ovs-vsctl add-port br-int eth1<br>
    <br>
    <br>
    Need I do something else ?<br>
    <br>
    How the DHCP is working in this case ?<br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit : <br>
    <blockquote>
        Then the problem isn't in the instance but in the nova-network service , please check if it is working well <br>
        as well as give us the output log when you attempt to create a new instance.<br>
        <br>
        <br>
        
<hr align="center">
<br>
        <br>
        Subject: RE: [Openstack] Instance IP assignment problem<br>
        From: emilien.openstack@gmail.com<br>
        To: skible@hotmail.fr<br>
        CC: salmanmk@live.com; openstack@lists.launchpad.net<br>
        Date: Thu, 3 May 2012 10:21:37 +0200<br>
        <br>
        Fixed IP<br>
        <br>
        <br>
        <br>
        Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : <br>
        <blockquote>
            Fixed IP or Floating IP ?<br>
            <br>
            <br>
            
<hr align="center">
<br>
            <br>
            <br>
            From: emilien.openstack@gmail.com<br>
            To: salmanmk@live.com<br>
            Date: Thu, 3 May 2012 09:55:31 +0200<br>
            CC: openstack@lists.launchpad.net<br>
            Subject: Re: [Openstack] Instance IP assignment problem<br>
            <br>
            Hi,<br>
            <br>
            <br>
            As I told you, I have also a problem for instance IP assignement.<br>
            <br>
            <br>
            <u>My architecture :</u><br>
            <br>
            I use <b>Quantum</b> with <b>OVS plugin</b> on 2 servers Essex-1 & Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent & nova-compute only.<br>
            <br>
            You can see more details <a href="https://github.com/EmilienM/doc-openstack/blob/master/Documentation/How%20to%20setup%20OpenStack%20Essex.pdf" target="_blank">here</a>.<br>
            <br>
            My configurations files are <a href="https://github.com/EmilienM/doc-openstack/tree/master/Configuration%20Files" target="_blank">here</a> and in my documentation.<br>
            <br>
            <br>
            <br>
            <u>Problem Description :</u><br>
            <br>
            When an instance is created in ESSEX-1, all is working (network).<br>
            <br>
            But when the VM is started on ESSEX-2, it does not get an IP address. (<a href="http://paste.openstack.org/show/14775/" target="_blank">log file</a>)<br>
            <br>
            I'm sure the problem comes from OVS connection with ESSEX-1.<br>
            <br>
            <br>
            Do I need to configure something like a trunk or a tunnel between Essex-1 & Essex-2 ?<br>
            <br>
            I miss something in my configuration, if you have any idea...<br>
            <br>
            <br>
            Regards<br>
            <br>
            <br>
            Emilien<br>
            <br>
            <br>
            Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : <br>
            <blockquote>
                <font size="2"><font color="#366092">It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue. </font></font><br>
                <font size="2"><font color="#366092">Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance.</font></font><br>
                <br>
                <font size="2"><font color="#366092">Salman</font></font><br>
                <br>
                <br>
                <br>
                
<hr align="center">
<br>
                <br>
                <br>
                <br>
                Subject: RE: [Openstack] Instance IP assignment problem<br>
                From: emilien.openstack@gmail.com<br>
                To: salmanmk@live.com<br>
                CC: jorge.delacruz@stackops.com; openstack@lists.launchpad.net<br>
                Date: Tue, 1 May 2012 21:26:26 +0200<br>
                <br>
                Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : <br>
                <blockquote>
                    <font size="2"><font color="#366092">Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure.</font></font><br>
                    <font size="2"><font color="#366092">Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could. </font></font><br>
                    <br>
                </blockquote>
                Here my nova.conf and I don't have any interfering DHCP server :<br>
                <br>
                <a href="https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf" target="_blank">https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf</a><br>
                <br>
                <br>
                Thanks<br>
                <br>
                <blockquote>
                    <font size="2"><font color="#366092">Salman</font></font><br>
                    <br>
                    <br>
                    <br>
                    
<hr align="center">
<br>
                    <br>
                    <br>
                    <br>
                    <br>
                    Subject: RE: [Openstack] Instance IP assignment problem<br>
                    From: emilien.openstack@gmail.com<br>
                    To: salmanmk@live.com<br>
                    CC: jorge.delacruz@stackops.com; openstack@lists.launchpad.net<br>
                    Date: Tue, 1 May 2012 21:06:01 +0200<br>
                    <br>
                    Hi Salman,<br>
                    <br>
                    <br>
                    I'm thinking about a networking issue. Where is your L3 gateway in this architecture ? Maybe do you need an ip helper tool to redirect DHCP broadcast ?<br>
                    <br>
                    <br>
                    What do you think about my problem (follow up to my last e-mail) ?<br>
                    <br>
                    <br>
                    Thanks<br>
                    <br>
                    <br>
                    Emilien<br>
                    <br>
                    Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : <br>
                    <blockquote>
                        <font size="2"><font color="#366092">Hi,</font></font><br>
                        <br>
                        <font size="2"><font color="#366092">Here is the error log: http://pastebin.com/KrNZDrvD</font></font><br>
                        <font size="2"><font color="#366092">and nova.conf: http://pastebin.com/Fvd6dSZs</font></font><br>
                        <br>
                        <font size="2"><font color="#366092">Emilien, I am trying to get an understanding of how different Quantum plugins work with OpenStack. Ryu plugin is particularly interesting as it uses an OpenFlow controller to configure Vswitches.</font></font><br>
                        <br>
                        <font size="2"><font color="#366092">The problem I am faced with is  (I think ) that I already have a private network and Quantum should assign IP addresses to instances using DHCP. But instances send out discover message on laucnh but never find a DHCP server (although there are 2 dnsmasqs running). </font></font><br>
                        <br>
                        <font size="2"><font color="#366092">Any ideas?</font></font><br>
                        <br>
                        <font size="2"><font color="#366092">Thanks,</font></font><br>
                        <font size="2"><font color="#366092">Salman</font></font><br>
                        <br>
                        <br>
                        <br>
                        
<hr align="center">
<br>
                        <br>
                        <br>
                        <br>
                        <br>
                        <br>
                        Date: Tue, 1 May 2012 20:43:44 +0200<br>
                        Subject: Re: [Openstack] Instance IP assignment problem<br>
                        From: jorge.delacruz@stackops.com<br>
                        To: emilien.openstack@gmail.com<br>
                        CC: openstack@lists.launchpad.net; salmanmk@live.com<br>
                        <br>
                        Hi Emilien and Salman,<br>
                        Please, could you upload all the files, errors and conf in pastebin or something like that? <br>
                        I have troubles to open in phone :)<br>
                        Thank you<br>
                        El 01/05/2012 20:39, "Emilien Macchi" <<a href="mailto:emilien.openstack@gmail.com">emilien.openstack@gmail.com</a>> escribió:<br>
                        <blockquote>
                            Hi,<br>
                            <br>
                            <br>
                            I have a similar problem when I create a network per project_id with Quantum.<br>
                            <br>
                            <br>
                            My VMs don't get IP and I can't understand why today.<br>
                            <br>
                            But when I create a private network for all projects, VMs get an IP and all is working well.<br>
                            Do you have the same problem ?<br>
                            <br>
                            <br>
                            Salman, I'm interesting about your nova.conf. I can see you are using Ryu ?<br>
                            Can you tell me more about your "use case" or architecture ?<br>
                            <br>
                            <br>
                            Thanks<br>
                            <br>
                            <br>
                            Le mardi 01 mai 2012 à 12:28 -0500, Salman Malik a écrit : <br>
                            <blockquote>
                                <font color="#366092">Hi Jorge,</font><br>
                                <br>
                                <font color="#366092">Thanks for looking into the post.</font><br>
                                <font color="#366092">I have made changes to the nova.conf file so that I only use 10.0.0.x network (but the problem is still the same). For this configuration, I assume that it will give out IPs to instances starting from 10.0.0.11. And just to inform you, my eth1 is configured to be 10.0.0.10 (which is a VM itself, and eth1 is configured as a host-only network with no DHCP) and this interface is plugged in the integration bridge used by quantum plugins.</font><br>
                                <br>
                                <font color="#366092">Thanks,</font><br>
                                <font color="#366092">Salman</font><br>
                                <br>
                                <font color="#366092">PS: Error log of a launched instance is also attached.</font><br>
                                <br>
                                <br>
                                <br>
                                
<hr align="center">
<br>
                                <br>
                                <br>
                                <br>
                                <br>
                                <br>
                                <br>
                                Date: Tue, 1 May 2012 19:03:49 +0200<br>
                                Subject: Re: [Openstack] Instance IP assignment problem<br>
                                From: <a href="mailto:jorge.delacruz@stackops.com">jorge.delacruz@stackops.com</a><br>
                                To: <a href="mailto:salmanmk@live.com">salmanmk@live.com</a><br>
                                CC: <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
                                <br>
                                Im not really sure but you are using range for your environment 10.0.3.x and 10.0.0.x for fixed.<br>
                                Can you attach a nova network conf?<br>
                                Regards<br>
                                El 01/05/2012 18:56, "Salman Malik" <<a href="mailto:salmanmk@live.com">salmanmk@live.com</a>> escribió:<br>
                                <blockquote>
                                    <font color="#366092">Hi Guys,</font><br>
                                    <br>
                                    <font color="#366092">Can anyone provide any insight to the following question:</font><br>
                                    <font color="#366092"><a href="https://answers.launchpad.net/nova/+question/195439" target="_blank">https://answers.launchpad.net/nova/+question/195439</a></font><br>
                                    <br>
                                    <font color="#366092">Thanks,</font><br>
                                    <font color="#366092">Salman</font><br>
                                    <br>
                                    <br>
                                    _______________________________________________<br>
                                    Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
                                    Post to     : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
                                    Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
                                    More help   : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
                                    <br>
                                </blockquote>
<pre>_______________________________________________
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a>
Post to     : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a>
More help   : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a>
</pre>
                            </blockquote>
                            <br>
                            <br>
                        </blockquote>
                    </blockquote>
                    <br>
                    <br>
                </blockquote>
                <br>
                <br>
            </blockquote>
            <br>
            <br>
            _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp<br>
        </blockquote>
        <br>
        <br>
    </blockquote>
    <br>
    <br>
</blockquote>
<br></div></div>                                        </div></body>
</html>