Recently I upgrade my openstack setup from grizzly-g3 to grizzly stable, I have not got this bug yet.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Edgar Magana
Sent: Thursday, May 23, 2013 5:56 AM
To: Shu, Xinxin
Subject: [Bug 1160442] Re: when boot many vms with quantum, nova sometimes allocates two quantum ports rather than one

I am not able to reproduce this bug in my setup. I am using almost the same network configuration that the one posted in this bug report but I am using stable/grizzly with only one compute node, I am able to reach up to 200 VMs with no problems at all:

| 284a318b-84df-4008-a386-d4a7b0510dee | vm-178 | ACTIVE | None       | Running     | private=10.0.0.178 |
| b2e1bbec-e93c-4b48-9843-b45a45a33b87 | vm-179 | ACTIVE | None       | Running     | private=10.0.0.182 |
| c8f5d908-79c3-4020-adca-6348f76f44cf | vm-18  | ACTIVE | None       | Running     | private=10.0.0.22  |
| 2f452943-92f5-41c1-a294-f5e52ef97052 | vm-180 | ACTIVE | None       | Running     | private=10.0.0.184 |
| 43314b6c-7f6f-4da3-8054-5a8158a48ef9 | vm-181 | ACTIVE | None       | Running     | private=10.0.0.183 |
| 3821636d-c94b-4030-95d4-47c183893227 | vm-182 | ACTIVE | None       | Running     | private=10.0.0.187 |
| f6b27836-acf3-49a9-a960-a2a6835df534 | vm-183 | ACTIVE | None       | Running     | private=10.0.0.185 |
| c798b778-b471-4a1f-b43c-f9d69873354d | vm-184 | ACTIVE | None       | Running     | private=10.0.0.186 |
| 99a023ec-aeff-4451-9e3c-27316d1ffd78 | vm-185 | ACTIVE | None       | Running     | private=10.0.0.188 |
| 4475818f-801a-4a59-9a85-1113e54e0c18 | vm-186 | ACTIVE | None       | Running     | private=10.0.0.192 |
| 56145c8c-a645-4bdf-84b8-5078c19c39a4 | vm-187 | ACTIVE | None       | Running     | private=10.0.0.189 |
| f2c3074a-43aa-4506-b3a9-43f2ff3f461c | vm-188 | ACTIVE | None       | Running     | private=10.0.0.190 |
| f12c882a-c25b-46f2-8550-7ec807d3b0b7 | vm-189 | ACTIVE | None       | Running     | private=10.0.0.191 |
| 9a40b604-0f9e-44d0-a080-59bfb9adedf5 | vm-19  | ACTIVE | None       | Running     | private=10.0.0.20  |
| 952a25a6-501b-44de-9149-0cb25b217d96 | vm-190 | ACTIVE | None       | Running     | private=10.0.0.194 |
| 5012700f-83a7-4f9d-85a7-796a65043aed | vm-191 | ACTIVE | None       | Running     | private=10.0.0.193 |
| 9d7bbc67-55e1-49e8-8c7b-6f6bd5b2183a | vm-192 | ACTIVE | None       | Running     | private=10.0.0.195 |
| 13192f4b-541f-4e92-b3f5-51e51d28408a | vm-193 | ACTIVE | None       | Running     | private=10.0.0.198 |
| 4ff125dc-8f1d-40b1-9db6-738665cdb8e7 | vm-194 | ACTIVE | None       | Running     | private=10.0.0.197 |
| d8f366e2-5867-421c-ab86-c15c06802f48 | vm-195 | ACTIVE | None       | Running     | private=10.0.0.196 |
| 5ea852aa-02a8-409a-9dc0-8abd5dcd6dc0 | vm-196 | ACTIVE | None       | Running     | private=10.0.0.201 |
| 2c60b14a-d60a-4fbc-9f1c-509c5fb5ed8c | vm-197 | ACTIVE | None       | Running     | private=10.0.0.199 |
| eacddd5d-0e3d-4c7d-9bdb-2f9010ff83e3 | vm-198 | ACTIVE | None       | Running     | private=10.0.0.202 |
| 5dc1f542-abef-4d28-946c-e87b8f5cd48f | vm-199 | ACTIVE | None       | Running     | private=10.0.0.200 |
| bba098a3-de0a-40b0-b09e-4b6916287a97 | vm-2   | ACTIVE | None       | Running     | private=10.0.0.4   |
| 5192cdf0-d4ce-4c02-948e-c5659271da80 | vm-20  | ACTIVE | None       | Running     | private=10.0.0.23  |
| c13cccd3-9d43-4511-93ea-d023e03f8f36 | vm-200 | ACTIVE | None       | Running     | private=10.0.0.203 |

I am using a very simple scripts to boot all these VMs:

emagana@rock:~$ more performance.sh
#!/bin/bash
COUNTER=0
for i in {1..200}
do
   echo "Deploy VM vm-$i"
   nova boot --flavor 42 --image tty-quantum --nic net-id=fced80ba-100f-43f0-ab2e-a2bf657d15ab vm-$i
   let COUNTER=$COUNTER+1
   if [ $COUNTER -eq 300 ]
      then
      sleep 5
      COUNTER=0
   fi
done

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1160442

Title:
  when boot many vms with quantum, nova sometimes allocates two quantum
  ports rather than one

Status in OpenStack Compute (Nova):
  Triaged
Status in OpenStack Quantum (virtual network service):
  Incomplete

Bug description:
  i have install grizzly-g3, but quantum does not work well, when i boot
  128 instances, i found one of instances got more than one fixed ip,
  howerver, when i boot 64 intances, it nerver happened, besides that ,
  sometimes i can not ping vm with floatingip, i did not find any error
  message in my quantum log( all the files in the /var/log/quantum),
  follows are the error output and configurations

  | 97a93600-38e2-4700-9851-15ef56c1d628 | slave  | ACTIVE | demo-int-net=172.16.100.4                   |
  | 99aeb6b8-4252-4839-a7d1-f87853116100 | slave  | ACTIVE | demo-int-net=172.16.100.117                 |
  | 9aa82a35-c9f1-4f44-a108-d14e74eec231 | slave  | ACTIVE | demo-int-net=172.16.100.108, 172.16.100.109 |
  | 9b6b1289-c450-4614-b647-e5ebdffff80a | slave  | ACTIVE | demo-int-net=172.16.100.5                   |
  | 9e0d3aa5-0f15-4b24-944a-6d6c3e18ce64 | slave  | ACTIVE | demo-int-net=172.16.100.35                  |
  | 9ea62124-9128-43cc-acdd-142f1e7743d6 | slave  | ACTIVE | demo-int-net=172.16.100.132                 |

  
  my setup : one db host(db service), one glance host(glance service), on api host(keystone,nova-api,nova-scheduler, nova-conductor, quantum-server,quantum-dhcp, quantum-l3-agent,quantum-plugin-openvswitch-agent), eight compute host(each host with nova-compute, quantum-plugin-openvswitch-agent), i check that all the service on all hosts works well
   
  i used vlan type network and openvswitch plugin:

  my quantum.conf

  [DEFAULT]
  # Default log level is INFO
  # verbose and debug has the same result.
  # One of them will set DEBUG log level output
  debug = True

  # Address to bind the API server
  bind_host = 0.0.0.0

  # Port the bind the API server to
  bind_port = 9696

  
  # Quantum plugin provider module
  # core_plugin =
  core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
  # Advanced service modules
  # service_plugins =

  # Paste configuration file
  api_paste_config = /etc/quantum/api-paste.ini

  # The strategy to be used for auth.
  # Supported values are 'keystone'(default), 'noauth'.
  auth_strategy = keystone

  
  # Modules of exceptions that are permitted to be recreated
  # upon receiving exception data from an rpc call.
  # allowed_rpc_exception_modules = quantum.openstack.common.exception, nova.exception
  # AMQP exchange to connect to if using RabbitMQ or QPID
  control_exchange = quantum

  # RPC driver. DHCP agents needs it.
  notification_driver = quantum.openstack.common.notifier.rpc_notifier

  # default_notification_level is used to form actual topic name(s) or to set logging level
  default_notification_level = INFO

  
  # Defined in rpc_notifier, can be comma separated values.
  # The actual topic names will be %s.%(default_notification_level)s
  notification_topics = notifications

  [QUOTAS]
  # resource name(s) that are supported in quota features
  # quota_items = network,subnet,port

  # default number of resource allowed per tenant, minus for unlimited
  # default_quota = -1

  # number of networks allowed per tenant, and minus means unlimited
  # quota_network = 10

  # number of subnets allowed per tenant, and minus means unlimited
  # quota_subnet = 10

  # number of ports allowed per tenant, and minus means unlimited
  quota_port = 5000
  quota_floatingip = 5000

  # default driver to use for quota checks
  # quota_driver = quantum.quota.ConfDriver

  # =========== items for agent management extension =============
  # Seconds to regard the agent as down.
  # agent_down_time = 5
  # ===========  end of items for agent management extension =====

  [DEFAULT_SERVICETYPE]
  # Description of the default service type (optional)
  # description = "default service type"
  # Enter a service definition line for each advanced service provided
  # by the default service type.
  # Each service definition should be in the following format:
  # <service>:<plugin>[:driver]

  [SECURITYGROUP]
  # If set to true this allows quantum to receive proxied security group calls from nova
  # proxy_mode = False

  [AGENT]
  root_helper = sudo quantum-rootwrap /etc/quantum/rootwrap.conf

  # =========== items for agent management extension =============
  # seconds between nodes reporting state to server, should be less than
  # agent_down_time
  # report_interval = 4

  # ===========  end of items for agent management extension =====

  [keystone_authtoken]
  auth_host = host-keystone
  auth_port = 35357
  auth_protocol = http
  admin_tenant_name = demoTenant
  admin_user = test
  admin_password = 123456
  signing_dir = /var/lib/quantum/keystone-signing

  my dhcp_agent.ini

  [DEFAULT]
  # Where to store dnsmasq state files.  This directory must be writable by the
  # user executing the agent.
  state_path = /var/lib/quantum

  # OVS based plugins(OVS, Ryu, NEC, NVP, BigSwitch/Floodlight)
  interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver

  # The agent can use other DHCP drivers.  Dnsmasq is the simplest and requires
  # no additional setup of the DHCP server.
  dhcp_driver = quantum.agent.linux.dhcp.Dnsmasq

  my ovs_quantum_plugin.ini configure file

  [DATABASE]
  # This line MUST be changed to actually run the plugin.
  sql_connection = mysql://quantum:quantum@host-db/quantum

  # Database reconnection interval in seconds - if the initial connection to the
  # database fails
  reconnect_interval = 2

  [OVS]
  # (StrOpt) Type of network to allocate for tenant networks. The
  # default value 'local' is useful only for single-box testing and
  # provides no connectivity between hosts. You MUST either change this
  # to 'vlan' and configure network_vlan_ranges below or change this to
  # 'gre' and configure tunnel_id_ranges below in order for tenant
  # networks to provide connectivity between hosts. Set to 'none' to
  # disable creation of tenant networks.

  tenant_network_type=vlan

  network_vlan_ranges = DemoNet:1:4094

  bridge_mappings = DemoNet:DemoBridge

  [AGENT]
  # Agent's polling interval in seconds
  polling_interval = 2

  [SECURITYGROUP]

  
  when i execute "quantum router-gateway-set" to add external network id as the router gateway, i found that the status of  port for external network id in the router is DOWN. does it matters,  if it does,  how can i fixed it.

  
  this blocked me for serveral days , can someone help me sovle it, any help will be appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1160442/+subscriptions