Re: [Openstack] Quantum/Grizzly - Instance doesn't get IP

2013-09-04 Thread happy idea 
well. my suggestion is to follow this guide
https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst
,
 and reinstall your openstall completely.

 If you are using Ubuntu 13.04:
after upgrade/dist-upgrade you have to reboot the host ,  now the system
had integreted Linux target framework , so now you shoudn't install the
package iscsitarget and iscsitarget-dkms on the controller node , and the
cinder conf file shoud like this:

 /etc/cinder/cinder.conf :

[DEFAULT]
rootwrap_config=/etc/cinder/rootwrap.conf
sql_connection = mysql://cinderUser:cinderPass@10.10.10.51/cinder
api_paste_config = /etc/cinder/api-paste.iniiscsi_helper=tgtadm
volume_name_template = volume-%s
volume_group = cinder-volumes
verbose = True
auth_strategy = keystone
iscsi_ip_address=10.10.10.51

rabbit_host = 10.10.10.51



2013/9/4 Marcelo Dieder 

>  Hi Happy, thanks for your reply.
>
> I checked this guide, but I already have dhcp-agent installed.
>
> root@network:~# apt-get -y install quantum-plugin-openvswitch-agent
> quantum-dhcp-agent quantum-l3-agent quantum-metadata-agent
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> quantum-dhcp-agent is already the newest version.
> quantum-l3-agent is already the newest version.
> quantum-metadata-agent is already the newest version.
> quantum-plugin-openvswitch-agent is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> I also checked the settings that this guide and I added some options that
> I had not configured. Now the error "No active DHCP agents" doesn't appears
> more, but the error (in the Controler (quantum-server)) still appears below:
>
> 2013-09-04 08:25:48  WARNING [quantum.db.agentschedulers_db] Fail
> scheduling network {'status': u'ACTIVE', 'subnets':
> [u'80b21701-4b05-4585-985a-60905ff42531'], 'name': u'public',
> 'provider:physical_network': None, 'admin_state_up': True, 'tenant_id':
> u'27d2b93f11ac4e91a3edb26edb28fb6b', 'provider:network_type': u'gre',
> 'router:external': True, 'shared': False, 'id':
> u'b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0', 'provider:segmentation_id': 2L}
>
> And in all hosts (computer, networking and controller), I have the error:
>
> # quantum agent-list
> Unknown command ['agent-list']
>
> At my network node:
>
> tail -n 10 /var/log/openvswitch/ovs-vswitchd.log
> Sep 04 09:27:23|09614|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
> tap91e05e25-7f device failed: No such device
> Sep 04 09:27:32|09615|netdev|WARN|Dropped 253 log messages in last 12
> seconds (most recently, 1 seconds ago) due to excessive rate
> Sep 04 09:27:32|09616|netdev|WARN|failed to get flags for network device
> tap91e05e25-7f: No such device
> Sep 04 09:27:33|09617|netdev_linux|WARN|Dropped 7 log messages in last 10
> seconds (most recently, 5 seconds ago) due to excessive rate
> Sep 04 09:27:33|09618|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
> tap91e05e25-7f device failed: No such device
> Sep 04 09:27:44|09619|netdev|WARN|Dropped 231 log messages in last 12
> seconds (most recently, 1 seconds ago) due to excessive rate
> Sep 04 09:27:44|09620|netdev|WARN|failed to get flags for network device
> tap91e05e25-7f: No such device
> Sep 04 09:27:48|09621|netdev_linux|WARN|Dropped 11 log messages in last 15
> seconds (most recently, 5 seconds ago) due to excessive rate
> Sep 04 09:27:48|09622|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
> tap91e05e25-7f device failed: No such device
>
> (quantum) net-list
>
> +--+--+---+
> | id   | name |
> subnets   |
>
> +--+--+---+
> | a8f7c937-e8d0-4952-bff6-7d364335df22 | demo-net |
> fd7f324c-25ec-4134-ab97-e827fcf12824 10.5.5.0/24  |
> | b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0 | public   |
> 80b21701-4b05-4585-985a-60905ff42531 xxx.xxx.xxx.0/24 |
>
> +--+--+---+
> (quantum) port-list
>
> +--+--+---++
> | id   | name | mac_address   |
> fixed_ips
> |
>
> +--+--+---++
> | 65c5b6cf-5eef-483e-8b32-8cd07bb83e6d |  | fa:16:3e:58:29:31 |
> {"subnet_id": "80b21701-4b05-4585-985a-60905ff42531", "ip_address":
> "xxx.xxx.xxx.166"} |
> | 806b3d3e-35fe-4356-a833-a8a3d44ec9ca |  | fa:16:3e:7c:00:24 |
> {"subnet_id": "fd7f324c-25ec-4134-ab97-e827fcf12824", "ip_address":
> "10.5.5.1"}|
> | 91e05e25-7f7b-4399-9da2-4

[Openstack] Quantum/Grizzly - Instance doesn't get IP

2013-09-04 Thread claudio 
Hi Marcelo!

 

Seems that you haven't got quantum client installed, and probably you have
some missing packages as well.

My advice is, restart from scratch again but follow the guide that "Happy"
advised you

https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_Mult
iNode/OpenStack_Grizzly_Install_Guide.rst

 

Good luck

 

Claudio Marques

 

  clau...@onesource.pt

  http://www.onesource.pt/

 

 

.

 

Hi Happy, thanks for your reply.

I checked this guide, but I already have dhcp-agent installed. 

root@network:~# apt-get -y install quantum-plugin-openvswitch-agent
quantum-dhcp-agent quantum-l3-agent quantum-metadata-agent
Reading package lists... Done
Building dependency tree   
Reading state information... Done
quantum-dhcp-agent is already the newest version.
quantum-l3-agent is already the newest version.
quantum-metadata-agent is already the newest version.
quantum-plugin-openvswitch-agent is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I also checked the settings that this guide and I added some options that I
had not configured. Now the error "No active DHCP agents" doesn't appears
more, but the error (in the Controler (quantum-server)) still appears below:

2013-09-04 08:25:48  WARNING [quantum.db.agentschedulers_db] Fail scheduling
network {'status': u'ACTIVE', 'subnets':
[u'80b21701-4b05-4585-985a-60905ff42531'], 'name': u'public',
'provider:physical_network': None, 'admin_state_up': True, 'tenant_id':
u'27d2b93f11ac4e91a3edb26edb28fb6b', 'provider:network_type': u'gre',
'router:external': True, 'shared': False, 'id':
u'b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0', 'provider:segmentation_id': 2L}

And in all hosts (computer, networking and controller), I have the error:

# quantum agent-list
Unknown command ['agent-list']

At my network node:

tail -n 10 /var/log/openvswitch/ovs-vswitchd.log
Sep 04 09:27:23|09614|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
tap91e05e25-7f device failed: No such device
Sep 04 09:27:32|09615|netdev|WARN|Dropped 253 log messages in last 12
seconds (most recently, 1 seconds ago) due to excessive rate
Sep 04 09:27:32|09616|netdev|WARN|failed to get flags for network device
tap91e05e25-7f: No such device
Sep 04 09:27:33|09617|netdev_linux|WARN|Dropped 7 log messages in last 10
seconds (most recently, 5 seconds ago) due to excessive rate
Sep 04 09:27:33|09618|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
tap91e05e25-7f device failed: No such device
Sep 04 09:27:44|09619|netdev|WARN|Dropped 231 log messages in last 12
seconds (most recently, 1 seconds ago) due to excessive rate
Sep 04 09:27:44|09620|netdev|WARN|failed to get flags for network device
tap91e05e25-7f: No such device
Sep 04 09:27:48|09621|netdev_linux|WARN|Dropped 11 log messages in last 15
seconds (most recently, 5 seconds ago) due to excessive rate
Sep 04 09:27:48|09622|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
tap91e05e25-7f device failed: No such device

(quantum) net-list
+--+--+-
--+
| id   | name | subnets
|
+--+--+-
--+
| a8f7c937-e8d0-4952-bff6-7d364335df22 | demo-net |
fd7f324c-25ec-4134-ab97-e827fcf12824 10.5.5.0/24  |
| b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0 | public   |
80b21701-4b05-4585-985a-60905ff42531 xxx.xxx.xxx.0/24 |
+--+--+-
--+
(quantum) port-list
+--+--+---+-

---+
| id   | name | mac_address   |
fixed_ips
|
+--+--+---+-

---+
| 65c5b6cf-5eef-483e-8b32-8cd07bb83e6d |  | fa:16:3e:58:29:31 |
{"subnet_id": "80b21701-4b05-4585-985a-60905ff42531", "ip_address":
"xxx.xxx.xxx.166"} |
| 806b3d3e-35fe-4356-a833-a8a3d44ec9ca |  | fa:16:3e:7c:00:24 |
{"subnet_id": "fd7f324c-25ec-4134-ab97-e827fcf12824", "ip_address":
"10.5.5.1"}|
| 91e05e25-7f7b-4399-9da2-42fef05afe31 |  | fa:16:3e:fe:63:6c |
{"subnet_id": "fd7f324c-25ec-4134-ab97-e827fcf12824", "ip_address":
"10.5.5.2"}|
| a9043279-dd30-40b7-a1e3-8d340c5408c3 |  | fa:16:3e:71:60:57 |
{"subnet_id": "80b21701-4b05-4585-985a-60905ff42531", "ip_address":
"xxx.xxx.xxx.165"} |
+--+--+---+-

---+
(quantum) router-list
+--

Re: [Openstack] Quantum/Grizzly - Instance doesn't get IP

2013-09-04 Thread Marcelo Dieder 

Hi Happy, thanks for your reply.

I checked this guide, but I already have dhcp-agent installed.

root@network:~# apt-get -y install quantum-plugin-openvswitch-agent 
quantum-dhcp-agent quantum-l3-agent quantum-metadata-agent

Reading package lists... Done
Building dependency tree
Reading state information... Done
quantum-dhcp-agent is already the newest version.
quantum-l3-agent is already the newest version.
quantum-metadata-agent is already the newest version.
quantum-plugin-openvswitch-agent is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I also checked the settings that this guide and I added some options 
that I had not configured. Now the error "No active DHCP agents" doesn't 
appears more, but the error (in the Controler (quantum-server)) still 
appears below:


2013-09-04 08:25:48  WARNING [quantum.db.agentschedulers_db] Fail 
scheduling network {'status': u'ACTIVE', 'subnets': 
[u'80b21701-4b05-4585-985a-60905ff42531'], 'name': u'public', 
'provider:physical_network': None, 'admin_state_up': True, 'tenant_id': 
u'27d2b93f11ac4e91a3edb26edb28fb6b', 'provider:network_type': u'gre', 
'router:external': True, 'shared': False, 'id': 
u'b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0', 'provider:segmentation_id': 2L}


And in all hosts (computer, networking and controller), I have the error:

# quantum agent-list
Unknown command ['agent-list']

At my network node:

tail -n 10 /var/log/openvswitch/ovs-vswitchd.log
Sep 04 09:27:23|09614|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on 
tap91e05e25-7f device failed: No such device
Sep 04 09:27:32|09615|netdev|WARN|Dropped 253 log messages in last 12 
seconds (most recently, 1 seconds ago) due to excessive rate
Sep 04 09:27:32|09616|netdev|WARN|failed to get flags for network device 
tap91e05e25-7f: No such device
Sep 04 09:27:33|09617|netdev_linux|WARN|Dropped 7 log messages in last 
10 seconds (most recently, 5 seconds ago) due to excessive rate
Sep 04 09:27:33|09618|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on 
tap91e05e25-7f device failed: No such device
Sep 04 09:27:44|09619|netdev|WARN|Dropped 231 log messages in last 12 
seconds (most recently, 1 seconds ago) due to excessive rate
Sep 04 09:27:44|09620|netdev|WARN|failed to get flags for network device 
tap91e05e25-7f: No such device
Sep 04 09:27:48|09621|netdev_linux|WARN|Dropped 11 log messages in last 
15 seconds (most recently, 5 seconds ago) due to excessive rate
Sep 04 09:27:48|09622|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on 
tap91e05e25-7f device failed: No such device


(quantum) net-list
+--+--+---+
| id   | name | 
subnets   |

+--+--+---+
| a8f7c937-e8d0-4952-bff6-7d364335df22 | demo-net | 
fd7f324c-25ec-4134-ab97-e827fcf12824 10.5.5.0/24  |
| b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0 | public   | 
80b21701-4b05-4585-985a-60905ff42531 xxx.xxx.xxx.0/24 |

+--+--+---+
(quantum) port-list
+--+--+---++
| id   | name | mac_address   | 
fixed_ips |

+--+--+---++
| 65c5b6cf-5eef-483e-8b32-8cd07bb83e6d |  | fa:16:3e:58:29:31 | 
{"subnet_id": "80b21701-4b05-4585-985a-60905ff42531", "ip_address": 
"xxx.xxx.xxx.166"} |
| 806b3d3e-35fe-4356-a833-a8a3d44ec9ca |  | fa:16:3e:7c:00:24 | 
{"subnet_id": "fd7f324c-25ec-4134-ab97-e827fcf12824", "ip_address": 
"10.5.5.1"}|
| 91e05e25-7f7b-4399-9da2-42fef05afe31 |  | fa:16:3e:fe:63:6c | 
{"subnet_id": "fd7f324c-25ec-4134-ab97-e827fcf12824", "ip_address": 
"10.5.5.2"}|
| a9043279-dd30-40b7-a1e3-8d340c5408c3 |  | fa:16:3e:71:60:57 | 
{"subnet_id": "80b21701-4b05-4585-985a-60905ff42531", "ip_address": 
"xxx.xxx.xxx.165"} |

+--+--+---++
(quantum) router-list
+--+-++
| id   | name| 
external_gateway_info  |

+--+-++
| 3a703f92-e1d5-4f06-8970-8ae899d40a99 | demo-router | {"network_id": 
"b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0"} |

+--+-+---