openstack team mailing list archive

["Choe, Cheng-Dae" <whitekid@xxxxxxxxx>]

when metadata server connecting problem.. please check below

- on network node(l3_agent running) ping to metadata_ip that specified by l3_agent.py
  if you using namespace run in router namespace
  ip netns exec qrouter-d7e9ec57-77c2-4046-aebf-d978ed4a4f83 ping metadata_ip

- meta traffic is transferred with DNAT from 169.254.169.254:80 to metadata_ip:8775

- on metadata server(nova_api server) check connection to vm's subnets such as 172.16.1.3
  openstack does not manage this routing. you manage this routing manually when tenant's subnet are private!
  i wrote little and dirty script manage this routing at external router:
  https://github.com/whitekid/metadata_route_agent


2012. 11. 7., 오전 3:02, Skible OpenStack <skible.openstack@xxxxxxxxx> 작성:

> Hi Yi Sun,
> 
> We are facing the same problem. I guess my networking architecture was not as correct as i thought.
> Although, i have just received a contribution from a friend that filled up the missing pieces and got it to work properly ! If you can bare with me, i will test it out tomorrow and publish it on the guide.
> 
> Best regards.
> Le 06/11/2012 04:55, Yi Sun a écrit :
>> Skible,
>> Followed your guide, everything went through fine until I started my
>> VM. The VM image I used is a ubuntu cloud image
>> (http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img).
>> After boot up, the VM can not access meta server. It complains about
>> "not route found".
>> I run a tcpdump on the VM tap interface, I'm seeing ARP requests to
>> the router for the VM network (10.5.5.1) from the VM but no arp reply.
>> quantum router-list and port-list give something below:
>> root@controller/# quantum router-list
>> 
>> | cc5e1de4-e59e-441d-92ea-da2f803f2903 | demo_net_router | null
>>           |
>> 
>> root@controller/# quantum port-list
>> | 1af24487-4a48-45a7-939f-486e5d7996b3 |      | fa:16:3e:fd:da:ab |
>> {"subnet_id": "cf894ab0-32e7-44e1-9467-cdeeb01597f9", "ip_address":
>> "10.5.5.2"}  |
>> | 61c2bef9-1bd9-4c2d-ad73-28740b4d0759 |      | fa:16:3e:cf:f4:09 |
>> {"subnet_id": "cf894ab0-32e7-44e1-9467-cdeeb01597f9", "ip_address":
>> "10.5.5.3"}  |
>> | 63bea17f-af30-4d75-9aa5-052a426768d6 |      | fa:16:3e:f0:7a:16 |
>> {"subnet_id": "cf894ab0-32e7-44e1-9467-cdeeb01597f9", "ip_address":
>> "10.5.5.1"}  |
>> 
>> But ifconfig on controller does not show interface for router at all
>> 
>> Have you seen the same issue before?
>> Thanks
>> Yi
>> 
>> On Fri, Nov 2, 2012 at 2:36 AM, Skible OpenStack
>> <skible.openstack@xxxxxxxxx> wrote:
>>> Hi Ian,
>>> 
>>> Many thanks for the remark. i fixed it :)
>>> 
>>> Le 02/11/2012 10:22, DarkSinclair a écrit :
>>> 
>>>> Greetings Skible.
>>>> 
>>>> Great work to you and the rest on the guide.  A minor change is required
>>>> in nova.conf configuration for file VNC.  The parameter for
>>>> vncserver_proxyclient_address must be eth0's IP address, otherwise the
>>>> console reports 'failed to connect to server'.
>>>> 
>>>> vncserver_proxyclient_address=172.16.2.250
>>>> #vncserver_proxyclient_address=127.0.0.1
>>>> 
>>>> Regards,
>>>> 
>>>> Ian Sinclair
>>>> 
>>>> On 2012-11-01, at 7:18 AM, Skible OpenStack <skible.openstack@xxxxxxxxx>
>>>> wrote:
>>>> 
>>>> hi Tomokazu,
>>>> 
>>>> oups ! i forget to add that in the guide ! thanks ! i will fix it right
>>>> away !
>>>> 
>>>> As for the noVNC problem ! i think because you haven't installed noVNC on
>>>> the compute node !
>>>> 
>>>> 
>>>> Le 01/11/2012 11:31, Tomokazu Hirai a écrit :
>>>>> Hi Skible,
>>>>> 
>>>>> I installed openstack folsom with your guide and I noticed that
>>>>> compute node's quantum can not access to controller node's
>>>>> rabbitmq-server.
>>>>> 
>>>>> so I added computeNode:/etc/quantum/quantum.conf with :
>>>>> 
>>>>>      rabbit_host = <compute node's IP addr>
>>>>> 
>>>>> now I can access to both node's VMs and VM can access to the
>>>>> Internet. :D
>>>>> 
>>>>> But I still have a problem.
>>>>> 
>>>>> I can not access to VM's noVNC on compute node. I can
>>>>> access to the VM's noVNC on controller node.
>>>>> 
>>>>> Best regards,
>>>>> 
>>>>> -- Tomokazu Hirai @jedipunkz
>>>>> 
>>>>> From: Skible OpenStack <skible.openstack@xxxxxxxxx>
>>>>> Subject: [Openstack] OpenStack Folsom Install Guide
>>>>> Date: Wed, 31 Oct 2012 13:46:31 +0100
>>>>> 
>>>>>> Hi Stackers,
>>>>>> 
>>>>>> i am currently seeing a lot of people having trouble deploying
>>>>>> OpenStack Folsom si i humbly present this guide for those who are
>>>>>> experimented and even those who are still taking their first steps
>>>>>> into the cloud world.
>>>>>> 
>>>>>> The guide has been updated from the last version to support:
>>>>>> 
>>>>>> * Multi Node install
>>>>>> * ubuntu server 12.10
>>>>>> * Quatum Configuration
>>>>>> * No Quantum is you are not interrested
>>>>>> 
>>>>>> Test it to see for yourself how simple and fun has OpenStack
>>>>>> deployment has became !
>>>>>> 
>>>>>> OpenStack Folsom Install Guide
>>>>>> 
>>>>>> <https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst>
>>>>>> 
>>>>>> Cheers
>>>>> _______________________________________________
>>>>> 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
>>>> 
>>> 
>>> _______________________________________________
>>> 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