openstack team mailing list archive

[livemoon <mwjpiero@xxxxxxxxx>]

thanks, I have solved this problem.


On Tue, Mar 5, 2013 at 10:09 AM, livemoon <mwjpiero@xxxxxxxxx> wrote:

> I followed this installation guide:
> http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.html
> it is different network configuration between you mention.
>
> mt controller only run nova-api and host run nova-api-metadata
>
> *controller:*
> # management ip
> auto eth0
> iface eth0 inet static
> address 192.168.1.2
> netmask 255.255.255.0
> # public ip
> auto eth1
>     iface eth1 inet static
>     address 172.16.0.211
>     netmask 255.255.255.0
>     gateway 172.16.0.1
>     dns-nameservers 8.8.8.8
>
> *network:*
> # management ip
> auto eth0
> iface eth0 inet static
> address 192.168.1.3
> netmask 255.255.255.0
>  dns-nameservers 8.8.8.8
> # data ip, I don't know why need this interface,but it exists in guide
> auto eth1
> iface eth1 inet static
> address 10.10.10.1
>  netmask 255.255.255.0
> # public interface, use for external router
> auto eth2
> iface eth2 inet manual
> up ifconfig $IFACE 0.0.0.0 up
>  up ip link set $IFACE promisc on
> down ifconfig $IFACE down
>
> *compute:*
> auto eth0
> iface eth0 inet static
> address 192.168.1.4
>  netmask 255.255.255.0
> dns-nameservers 8.8.8.8
>
> auto eth1
> iface eth1 inet static
>  address 10.10.10.2
> netmask 255.255.255.0
>
>
> On Tue, Mar 5, 2013 at 2:45 AM, Dan Wendlandt <dan@xxxxxxxxxx> wrote:
>
>>
>> On Mon, Mar 4, 2013 at 6:44 AM, Sylvain Bauza <sylvain.bauza@xxxxxxxxxxxx
>> > wrote:
>>
>>>  Could you please issue 'route -n' on your VM and check if
>>> 169.254.0.0/16 does have its own route ?
>>> If yes, delete it.
>>>
>>> Another classic error is to forget to add a static route from the
>>> controller node (if hosting metadata service) to the external router IP of
>>> the VM (see
>>> http://docs.openstack.org/folsom/openstack-network/admin/content/adv_cfg_l3_agent_metadata.html)
>>>
>>>
>> The good news is that this will no longer be a requirement in Grizzly,
>> thanks to Mark's work on integrating metadata into Quantum.  Thanks Mark!
>>
>> Dan
>>
>>
>>
>>> -Sylvain
>>>
>>>
>>> Le 04/03/2013 15:29, livemoon a écrit :
>>>
>>> Hi, I am follow http://docs.openstack.org/folsom/basic-install/content/and set up three nodes folsom.
>>> Now I have found my vm cannot get 169.254.169.254 to get cloud-init
>>> data. So I check the network node(quantum), using "iptables -L -t nat", I
>>> have found:
>>>
>>>  *Chain quantum-l3-agent-PREROUTING (1 references)*
>>> *target     prot opt source               destination*
>>> *DNAT       tcp  --  anywhere             169.254.169.254      tcp
>>> dpt:http to:192.168.1.2:8775*
>>>
>>>  I think it is correct, and in the network node, I can ping and curl
>>> "192.168.1.2"(this is controller node"), but not ping and curl
>>> 169.254.169.254.
>>>
>>>  Can anyone help me?
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>>
>> --
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Dan Wendlandt
>> Nicira, Inc: www.nicira.com
>> twitter: danwendlandt
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Blog Site: livemoon.org
> Twitter: mwjpiero
> 非淡薄无以明志，非宁静无以致远
>



-- 
Blog Site: livemoon.org
Twitter: mwjpiero
非淡薄无以明志，非宁静无以致远