neutron

nova boot silently picks up IP Address for External Network

Asked by Sunil Srivastava

I ran devstack stack.sh, and it created private and external network.

I could do ssh using private, access Internet from inside VM, and also do Floating IP. nova boot did not have any options for --nic. VMs had not picked up any addresses on External Net.

Then I manually removed the port, network, subnet, gateway and router, besides deleting detaching and deleting floating ip assigned.

Afterwards, I manually did the same steps which devstack stack.sh does and did nova boot without --nic option.

The two VMs I had spawned had also picked up external IP Addresses.

192.168.128/28 was used as external network. 129 went to br-ex, 130 went to gg*, and 131 and 132 got assigned to 2 VMs. I could still do FLoating IP with 133 and 134. Besides ssh from Management Controller Node on Floating IPs, I could only SSH 131 which went to remote node but not to local 132. Routes point to br-ex. There were no DNAT/SNAT rules for 132 and 131.

Following CLIs were run.

quantum net-create ext_net -- --router:external=True
quantum subnet-create --ip_version 4 66bb2246-51db-4b09-a608-e91f83b64bbb $FLOATING_RANGE -- --enable_dhcp=False

This sounds like some bug.

Question information

Language:
English Edit question
Status:
Answered
For:
neutron Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
yong sheng gong (gongysh) said : 		#1

I think in devstack, we are using different tenants for external network and private tenant.
by your manual steps, you may create the networks by one tenant.

Revision history for this message
cai qi shen (caiqishen) said : 		#2

i got the sam problem as yours! I have no idea how to slove it

Can you help with this problem?

Provide an answer of your own, or ask Sunil Srivastava for more information if necessary.

To post a message you must log in.