<div dir="ltr">Hello Jean,<div><br></div><div style>Thanks for your reply.</div><div style><br></div><div style>I followed the instructions in <a href="http://docs.openstack.org/folsom/basic-install/content/basic-install_network.html">http://docs.openstack.org/folsom/basic-install/content/basic-install_network.html</a>. And my Controller and the Network-node is installed in the same physical node.</div>

<div style><br></div><div style>I am using Folsom but without Network namespaces. <br></div><div style><br></div><div style>But in the website you have provided it states that "<span style="color:rgb(0,0,0);font-family:Verdana,Geneva,sans-serif;font-size:13px">If you run both L3 + DHCP services on the same node, you should enable namespaces to avoid conflicts with routes :</span>"</div>

<div style><br></div><div style>But currently quantum-dhcp-agent and quantum-l3-agent are running in the same node? </div><div style><br></div><div style>Additionally the control node serves as a DHCP server for the local network ( Don't know if that would make and difference)</div>

<div style><br></div><div style>Any idea what the problem could be?</div><div style><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 16 February 2013 16:21, Jean-Baptiste RANSY <span dir="ltr"><<a href="mailto:jean-baptiste.ransy@alyseo.com" target="_blank">jean-baptiste.ransy@alyseo.com</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div>Hello Chathura,<br>
      <br>
      Are you using Folsom with Network Namespaces ?<br>
      <br>
      If yes, have a look here :
<a href="http://docs.openstack.org/folsom/openstack-network/admin/content/ch_limitations.html" target="_blank">http://docs.openstack.org/folsom/openstack-network/admin/content/ch_limitations.html</a><br>
      <br>
      <br>
      Regards,<br>
      <br>
      Jean-Baptsite RANSY<div><div class="h5"><br>
      <br>
      <br>
      On 02/16/2013 05:01 PM, Chathura M. Sarathchandra Magurawalage
      wrote:<br>
    </div></div></div>
    <blockquote type="cite"><div><div class="h5">
      <div dir="ltr">Hello guys,
        <div><br>
        </div>
        <div>The problem still exists. Any ideas?</div>
        <div><br>
        </div>
        <div>Thanks </div>
        <div class="gmail_extra">
          <div>
            <div dir="ltr">
              <div><br>
              </div>
            </div>
          </div>
          <div class="gmail_quote">
            On 15 February 2013 14:37, Sylvain Bauza <span dir="ltr"><<a href="mailto:sylvain.bauza@digimind.com" target="_blank">sylvain.bauza@digimind.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              Metadata API allows to fetch SSH credentials when booting
              (pubkey I mean).<br>
              If a VM is unable to reach metadata service, then it won't
              be able to get its public key, so you won't be able to
              connect, unless you specifically go thru a Password
              authentication (provided password auth is enabled in
              /etc/ssh/sshd_config, which is not the case with Ubuntu
              cloud archive).<br>
              There is also a side effect, the boot process is longer as
              the instance is waiting for the curl timeout (60sec.) to
              finish booting up.<br>
              <br>
              Re: Quantum, the metadata API is actually DNAT'd from
              Network node to the Nova-api node (here 172.16.0.1 as
              internal management IP) :<br>
              Chain quantum-l3-agent-PREROUTING (1 references)
              <div><br>
                target     prot opt source               destination<br>
              </div>
              DNAT       tcp  --  <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a>  
                       169.254.169.254      tcp dpt:80 to:<a href="http://172.16.0.1:8775" target="_blank">172.16.0.1:8775</a><br>
              <br>
              <br>
              Anyway, the first step is to :<br>
              1. grab the console.log<br>
              2. access thru VNC to the desired instance<br>
              <br>
              Troubleshooting will be easier once that done.<br>
              <br>
              -Sylvain<br>
              <br>
              <br>
              <br>
              Le 15/02/2013 14:24, Chathura M. Sarathchandra
              Magurawalage a écrit :<br>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
                <div>
                  Hello Guys,<br>
                  <br>
                  Not sure if this is the right port but these are the
                  results:<br>
                  <br>
                </div>
                *Compute node:*
                <div><br>
                  <br>
                  root@computenode:~# netstat -an | grep 8775<br>
                </div>
                tcp        0      0 <a href="http://0.0.0.0:8775" target="_blank">0.0.0.0:8775</a>
                <<a href="http://0.0.0.0:8775" target="_blank">http://0.0.0.0:8775</a>>  0.0.0.0:*
                              LISTEN<br>
                <br>
                *Controller: *
                <div><br>
                  <br>
                  root@controller:~# netstat -an | grep 8775<br>
                </div>
                tcp        0      0 <a href="http://0.0.0.0:8775" target="_blank">0.0.0.0:8775</a>
                <<a href="http://0.0.0.0:8775" target="_blank">http://0.0.0.0:8775</a>>  0.0.0.0:*
                              LISTEN<br>
                <br>
                *Additionally I cant curl 169.254.169.254 from the
                compute node. I am not sure if this is related to not
                being able to PING the VM.*
                <div><br>
                  <br>
                  curl -v <a href="http://169.254.169.254" target="_blank">http://169.254.169.254</a><br>
                  * About to connect() to 169.254.169.254 port 80 (#0)<br>
                  *   Trying 169.254.169.254...<br>
                  <br>
                  Thanks for your help<br>
                  <br>
                  <br>
                  -----------------------------------------------------------------------------------------------------------------------------<br>
                  Chathura Madhusanka Sarathchandra Magurawalage.<br>
                  1NW.2.1, Desk 2<br>
                  School of Computer Science and Electronic Engineering<br>
                  University Of Essex<br>
                  United Kingdom.<br>
                  <br>
                </div>
                Email: <a href="mailto:csarata@essex.ac.uk" target="_blank">csarata@essex.ac.uk</a>
                <mailto:<a href="mailto:csarata@essex.ac.uk" target="_blank">csarata@essex.ac.uk</a>><br>
                          <a href="mailto:chathura.sarathchandra@gmail.com" target="_blank">chathura.sarathchandra@gmail.com</a>
                <mailto:<a href="mailto:77.chathura@gmail.com" target="_blank">77.chathura@gmail.com</a>><br>
                <a href="mailto:77.chathura@gmail.com" target="_blank">77.chathura@gmail.com</a>
                <mailto:<a href="mailto:77.chathura@gmail.com" target="_blank">77.chathura@gmail.com</a>>
                <div><br>
                  <br>
                  <br>
                  On 15 February 2013 11:03, Anil Vishnoi <<a href="mailto:vishnoianil@gmail.com" target="_blank">vishnoianil@gmail.com</a>
                  <mailto:<a href="mailto:vishnoianil@gmail.com" target="_blank">vishnoianil@gmail.com</a>>>
                  wrote:<br>
                  <br>
                      If you are using ubuntu cloud image then the only
                  way to log-in is<br>
                      to do ssh with the public key. For that you have
                  to create ssh key<br>
                      pair and download the ssh key. You can create this
                  ssh pair using<br>
                      horizon/cli.<br>
                  <br>
                  <br>
                      On Fri, Feb 15, 2013 at 4:27 PM, Sylvain Bauza<br>
                </div>
                    <<a href="mailto:sylvain.bauza@digimind.com" target="_blank">sylvain.bauza@digimind.com</a>
                <mailto:<a href="mailto:sylvain.bauza@digimind.com" target="_blank">sylvain.bauza@digimind.com</a>>>
                <div>
                  <br>
                      wrote:<br>
                  <br>
                  <br>
                          Le 15/02/2013 11:42, Chathura M. Sarathchandra
                  Magurawalage a<br>
                          écrit :<br>
                  <br>
                  <br>
                              How can I log into the VM from VNC? What
                  are the credentials?<br>
                  <br>
                  <br>
                          You have multiple ways to get VNC access. The
                  easiest one is<br>
                          thru Horizon. Other can be looking at the KVM
                  command-line for<br>
                          the desired instance (on the compute node) and
                  check the vnc<br>
                          port in use (assuming KVM as hypervisor).<br>
                          This is basic knowledge of Nova.<br>
                  <br>
                  <br>
                  <br>
                              nova-api-metadata is running fine in the
                  compute node.<br>
                  <br>
                  <br>
                          Make sure the metadata port is avaible thanks
                  to telnet or<br>
                          netstat, nova-api can be running without
                  listening on metadata<br>
                          port.<br>
                  <br>
                  <br>
                  <br>
                  <br>
                          _______________________________________________<br>
                          Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
                </div>
                        <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>><br>
                        Post to     : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
                        <mailto:<a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a>><br>
                        Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
                        <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>>
                <div><br>
                          More help   : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
                  <br>
                  <br>
                  <br>
                  <br>
                      --     Thanks & Regards<br>
                      --Anil Kumar Vishnoi<br>
                  <br>
                  <br>
                </div>
              </blockquote>
              <br>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><pre><div><div class="h5">_______________________________________________
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a></div></div><div class="im">
Post to     : <a href="mailto:openstack@lists.launchpad.net" target="_blank">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>
</div></pre>
    </blockquote>
    <br>
  </div>

</blockquote></div><br></div></div>