search

bilelmsekni / OpenStack-Folsom-Install-guide

A full installation guide for OpenStack Folsom with Quantum
160 stars 136 forks source link

instances no acquire IP #37

Closed daomarn closed 11 years ago

daomarn commented 11 years ago

I use GRE tutorial. Everythins is OK until run an instance. nova boot --image 353b5983-ddcf-4942-9f8e-015a91a9ff66 --flavor 1 mv1 +-------------------------------------+----------------------------------------------------------+ | Property | Value | +-------------------------------------+----------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-SRV-ATTR:host | d2 | | OS-EXT-SRV-ATTR:hypervisor_hostname | d2 | | OS-EXT-SRV-ATTR:instance_name | instance-00000007 | | OS-EXT-STS:power_state | 0 | | OS-EXT-STS:task_state | scheduling | | OS-EXT-STS:vm_state | building | | accessIPv4 | | | accessIPv6 | | | adminPass | P8yyDLiBc4X4 | | config_drive | | | created | 2013-01-15T04:53:05Z | | flavor | m1.tiny | | hostId | 74206baca932d6195094df587e8285ad89a00ce0803f3d20756ef989 | | id | e56a3c07-3886-4446-bd89-82663a41417a | | image | myFirstImage | | key_name | None | | metadata | {} | | name | mv1 | | progress | 0 | | security_groups | [{u'name': u'default'}] | | status | BUILD | | tenant_id | 02541303b9904517adf4589d39876375 | | updated | 2013-01-15T04:53:05Z | | user_id | 85c4db6d2301403698ff6f854dd641d7 | +-------------------------------------+----------------------------------------------------------+

nova list +--------------------------------------+-------+---------+----------+ | ID | Name | Status | Networks | +--------------------------------------+-------+---------+----------+ | e56a3c07-3886-4446-bd89-82663a41417a | mv1 | ACTIVE | | +--------------------------------------+-------+---------+----------+

All my log files are fine. Please help me. Why instances don't catch an IP?

In GRE tutorial shown how to create a network quantum net-create --tenant-id $put_id_of_project_one ext-red

root@d1:~# quantum net-show 949c0aa9-94af-4252-9a74-d0535da18689 +---------------------------+--------------------------------------+ | Field | Value | +---------------------------+--------------------------------------+ | admin_state_up | True | | id | 949c0aa9-94af-4252-9a74-d0535da18689 | | name | ext_red | | provider:network_type | vlan | | provider:physical_network | physnet1 | | provider:segmentation_id | 3 | | router:external | True | | shared | False | | status | ACTIVE | | subnets | 6ec6805f-f79a-4ae5-9e59-4f237ba57503 | | tenant_id | 6c0be957b5e4404daedf42e0491b8c26 | +---------------------------+--------------------------------------+

That command create net with vlan parameters. Is correct in GRE environment?

bilelmsekni commented 11 years ago

Hello there,

Instance are not getting ip addresses because there is something wrong with your quantum. Please check if the plugin agent is working fine because sometimes it doesn't. Creating VLAN networks won't cause problem for GRE tunneling mode.

regards, Bilel

----- Mail original -----

De: "daomarn" notifications@github.com À: "mseknibilel/OpenStack-Folsom-Install-guide" OpenStack-Folsom-Install-guide@noreply.github.com Envoyé: Mardi 15 Janvier 2013 07:33:24 Objet: {Disarmed} [OpenStack-Folsom-Install-guide] instances no acquire IP (#37)

I use GRE tutorial. Everythins is OK until run an instance. nova boot --image 353b5983-ddcf-4942-9f8e-015a91a9ff66 --flavor 1 mv1 +-------------------------------------+----------------------------------------------------------+ | Property | Value | +-------------------------------------+----------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-SRV-ATTR:host | d2 | | OS-EXT-SRV-ATTR:hypervisor_hostname | d2 | | OS-EXT-SRV-ATTR:instance_name | instance-00000007 | | OS-EXT-STS:power_state | 0 | | OS-EXT-STS:task_state | scheduling | | OS-EXT-STS:vm_state | building | | accessIPv4 | | | accessIPv6 | | | adminPass | P8yyDLiBc4X4 | | config_drive | | | created | 2013-01-15T04:53:05Z | | flavor | m1.tiny | | hostId | 74206baca932d6195094df587e8285ad89a00ce0803f3d20756ef989 | | id | e56a3c07-3886-4446-bd89-82663a41417a | | image | myFirstImage | | key_name | None | | metadata | {} | | name | mv1 | | progress | 0 | | security_groups | [{u'name': u'default'}] | | status | BUILD | | tenant_id | 02541303b9904517adf4589d39876375 | | updated | 2013-01-15T04:53:05Z | | user_id | 85c4db6d2301403698ff6f854dd641d7 | +-------------------------------------+----------------------------------------------------------+ nova list +--------------------------------------+-------+---------+----------+ | ID | Name | Status | Networks | +--------------------------------------+-------+---------+----------+ | e56a3c07-3886-4446-bd89-82663a41417a | mv1 | ACTIVE | | +--------------------------------------+-------+---------+----------+ All my log files are fine. Please help me. Why instances don't catch an IP? In GRE tutorial shown how to create a network quantum net-create --tenant-id $put_id_of_project_one ext-red root@d1:~# quantum net-show 949c0aa9-94af-4252-9a74-d0535da18689 +---------------------------+--------------------------------------+ | Field | Value | +---------------------------+--------------------------------------+ | admin_state_up | True | | id | 949c0aa9-94af-4252-9a74-d0535da18689 | | name | ext_red | | provider:network_type | vlan | | provider:physical_network | physnet1 | | provider:segmentation_id | 3 | | router:external | True | | shared | False | | status | ACTIVE | | subnets | 6ec6805f-f79a-4ae5-9e59-4f237ba57503 | | tenant_id | 6c0be957b5e4404daedf42e0491b8c26 | +---------------------------+--------------------------------------+ That command create net with vlan parameters. Is correct in GRE environment? — Reply to this email directly or view it on GitHub . Web Bug from https://github.com/notifications/beacon/I1T5EjfDb5OWgQ2B_759LUqTZ2BaXpmjQBErwbFKRAS2Hp-ijQ0WD9TqZBVyTJYk.gif

daomarn commented 11 years ago

Hi Bilel.

Creating instances with horizon resolve the issue about assign fixed ip. With this I can associate a floating IP.

root@d1:~# quantum floatingip-list +--------------------------------------+------------------+---------------------+--------------------------------------+ | id | fixed_ip_address | floating_ip_address | port_id | +--------------------------------------+------------------+---------------------+--------------------------------------+ | 41bb71b9-da4c-480d-bfc3-b26c971853ad | 20.20.20.5 | 172.31.15.211 | 678a85a7-7430-42c4-a99d-f5efe4303039 |

I cant do ping and access to instance and also I created a security group and I created the ssh and icmp rules, but nothing.

I checked the nova, quantum and openvswitch logs in the 3 servers but everything looks well. but i cant do ping and access to instance.

I generate a security group and create the ssh and icmp rules, but nothig.

Only I can ping the gateway of the instances from network controller (n1). root@d1:~# ping 20.20.20.1 PING 20.20.20.1 (20.20.20.1) 56(84) bytes of data. From 172.31.15.165 icmp_seq=1 Destination Host Unreachable

root@n1:~# ping 20.20.20.1 PING 20.20.20.1 (20.20.20.1) 56(84) bytes of data. 64 bytes from 20.20.20.1: icmp_req=1 ttl=64 time=0.069 ms

Example, net is 20.20.20.0/24, root@d1:~# quantum net-show lan2 +-----------------+--------------------------------------+ | Field | Value | +-----------------+--------------------------------------+ | admin_state_up | True | | id | 16556e94-d160-477d-b48a-c4d188d1ea48 | | name | lan2 | | router:external | False | | shared | False | | status | ACTIVE | | subnets | 95edbc8a-7825-4e6a-a4d5-74ae2f706d89 | | tenant_id | dd6dd7d79a6f49b09b47d32b4e7cc6b6 | +-----------------+--------------------------------------+ root@d1:~# quantum subnet-show sub2 +------------------+------------------------------------------------+ | Field | Value | +------------------+------------------------------------------------+ | allocation_pools | {"start": "20.20.20.2", "end": "20.20.20.254"} | | cidr | 20.20.20.0/24 | | dns_nameservers | | | enable_dhcp | True | | gateway_ip | 20.20.20.1 | | host_routes | | | id | 95edbc8a-7825-4e6a-a4d5-74ae2f706d89 | | ip_version | 4 | | name | sub2 | | network_id | 16556e94-d160-477d-b48a-c4d188d1ea48 | | tenant_id | dd6dd7d79a6f49b09b47d32b4e7cc6b6 | +------------------+------------------------------------------------+

The instance has 20.20.20.5

root@d1:~# nova show 2d74e141-bcdd-4601-a1a8-f24f3417e509 Please enter password for encrypted keyring: Please enter password for encrypted keyring: +------------------------+----------------------------------------------------------+ | Property | Value | +------------------------+----------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | active | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2013-01-16T05:02:07Z | | flavor | m1.tiny (1) | | hostId | 594750dbe10e662a05000ee2ddd9406f477b63c1e064b34d1dcb2352 | | id | 2d74e141-bcdd-4601-a1a8-f24f3417e509 | | image | myFirstImage (353b5983-ddcf-4942-9f8e-015a91a9ff66) | | key_name | mykey | | lan2 network | 20.20.20.5 | | metadata | {} | | name | test5 | | progress | 0 | | security_groups | [{u'name': u'default'}] | | status | ACTIVE | | tenant_id | dd6dd7d79a6f49b09b47d32b4e7cc6b6 | | updated | 2013-01-16T05:02:13Z | | user_id | 85c4db6d2301403698ff6f854dd641d7 | +------------------------+----------------------------------------------------------+

root@d1:~#quantum port-show 678a85a7-7430-42c4-a99d-f5efe4303039 +----------------+-----------------------------------------------------------------------------------+ | Field | Value | +----------------+-----------------------------------------------------------------------------------+ | admin_state_up | True | | device_id | 2d74e141-bcdd-4601-a1a8-f24f3417e509 | | device_owner | compute:nova | | fixed_ips | {"subnet_id": "95edbc8a-7825-4e6a-a4d5-74ae2f706d89", "ip_address": "20.20.20.5"} | | id | 678a85a7-7430-42c4-a99d-f5efe4303039 | | mac_address | fa:16:3e:dc:dd:a8 | | name | | | network_id | 16556e94-d160-477d-b48a-c4d188d1ea48 | | status | ACTIVE | | tenant_id | dd6dd7d79a6f49b09b47d32b4e7cc6b6 | +----------------+-----------------------------------------------------------------------------------+

And the router's port in this network has 20.20.20.1

root@d1:~# quantum port-show 6262a524-6c07-4d1c-af76-77a448926267 +----------------+-----------------------------------------------------------------------------------+ | Field | Value | +----------------+-----------------------------------------------------------------------------------+ | admin_state_up | True | | device_id | 58337a2f-66f4-4ea0-b90a-734e45abe932 | | device_owner | network:router_interface | | fixed_ips | {"subnet_id": "95edbc8a-7825-4e6a-a4d5-74ae2f706d89", "ip_address": "20.20.20.1"} | | id | 6262a524-6c07-4d1c-af76-77a448926267 | | mac_address | fa:16:3e:3d:f3:f7 | | name | | | network_id | 16556e94-d160-477d-b48a-c4d188d1ea48 | | status | ACTIVE | | tenant_id | dd6dd7d79a6f49b09b47d32b4e7cc6b6 | +----------------+-----------------------------------------------------------------------------------+

This mac address is an interface of network controller (n1)

qr-6262a524-6c Link encap:Ethernet direcciónHW fa:16:3e:3d:f3:f7
Direc. inet:20.20.20.1 Difus.:20.20.20.255 Másc:255.255.255.0 Dirección inet6: fe80::f816:3eff:fe3d:f3f7/64 Alcance:Enlace ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST MTU:1500 Métrica:1 Paquetes RX:29 errores:0 perdidos:0 overruns:0 frame:0 Paquetes TX:6 errores:0 perdidos:0 overruns:0 carrier:0 colisiones:0 long.colaTX:0 Bytes RX:1302 (1.3 KB) TX bytes:468 (468.0 B)

Please suggest me check any log or anything I can to do, please.