How to enable gre/vxlan/vlan/flat network at one cloud at the same time ?
Hi list,
I’m doing some function test based on neutron + ml2 plugin.
I want my cloud can support all kind of network, so I can do further comparison tests between different type of network.
So, I create 4 networks:
neutron net-list
+------
| id | name | subnets |
+------
| 1314f7bb-
| 4e7d06f0-
| c7e26ebc-
| fcd5c1a8-
+------
Because my machine only have 1 NIC port can be used for instances data network, so I start two dhcp agents:
neutron agent-list
+------
| id | agent_type | host | alive | admin_state_up |
+------
| 05e23822-
| 1267a2c6-
| 55f457bf-
| 928495d3-
| 934c721b-
| bd491c90-
| e07c8133-
| e1070c1e-
+------
The DHCP agent started on b-compute05 is working for network flat-1 and vlan-1.
The DHCP agent started on b-network01 is working for network gre-1 and vxlan-3.
The Open vSwitch agent on b-compute05 and b-compute06 is configured to working for flat and vlan.
The Open vSwitch agent on b-compute01 and b-compute02 is configured to working for vxlan and gre.
Then I start to create new instances.
Here comes the issues:
1. Network will not be auto scheduled to the right DHCP agent.
It just randomly chose one of the active DHCP agent, and ignore whether the DHCP agent can work for that type of network or not.
And no error message can be found in /var/log/
Everything looks just fine.
Only, active instances will never get IP addresses from DHCP.
I have to assign network to the right DHCP by hand.
2. Similar issues to nova-scheduler.
Because nova-scheduler scheduler instances without awareness of what type of network compute node support.
So, it will scheduler instances to the wrong compute node that do not actually support the kind of network.
These instances will end with error status, and with error message in /var/log/
2014-01-10 14:59:48.454 9085 ERROR nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.454 9085 TRACE nova.compute.
2014-01-10 14:59:48.620 9085 AUDIT nova.compute.
Anyone know what should I do to avoid these two issues ????
Or any suggestion about what I should do to change the cloud infrastructure to support 4 kind of network at the same time but without these issue ??
Thanks a lot !!
-chen
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- neutron Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask li,chen for more information if necessary.