Hi, I've followed the instructions on http://fedoraproject.org/wiki/Test_Day:2012-09-18_OpenStack and on F18 TC3 they work out of the box.
No I try to deploy Quantum using http://fedoraproject.org/wiki/QA:Testcase_Quantum_V2 but these instructions don't seem to work.
The first issue is that the initial "OS_USERNAME=quantum" result in commands such as "keystone tenant-list" ending with an authorization error. When I ignore this bit and use the admin credentials from the keystonerc instead the following instructions work fine.
I can then follow the full setup and 99% of the "How to test" section but when I try to associate a floating ip with "quantum floatingip-associate <floating ip id> <portid>" I run into trouble. Since the value of <portid> isn't mentioned at all I assume it is the port of the virtual machine which was launched with the ip 10.0.0.3 however when I try to execute the command I get:
Could not find an external network gateway reachable from subnet 4a2e2166-b543-4b74-af74-0f3a4b31dd1a. Therefore, cannot associate Port 3c4b6375-7dca-4f58-9fef-e941ea8ff948 with a Floating IP.
This is the subnet: +------------------+--------------------------------------------+ | Field | Value | +------------------+--------------------------------------------+ | allocation_pools | {"start": "10.0.0.2", "end": "10.0.0.254"} | | cidr | 10.0.0.0/24 | | dns_nameservers | | | enable_dhcp | True | | gateway_ip | 10.0.0.1 | | host_routes | | | id | 4a2e2166-b543-4b74-af74-0f3a4b31dd1a | | ip_version | 4 | | name | | | network_id | 26e64cea-5f27-46d9-9ea7-96837057e5fa | | tenant_id | 68722f889ae04b569b765ed9fd2f13da | +------------------+--------------------------------------------+
What's interesting here is that 10.0.0.1 is listed as the gateway_ip yet in the "Expected results" section of the page this IP is listed as the DHCP IP?
Any ideas what is wrong here or how to debug it?
Regards, Dennis
On 12/26/2012 09:36 PM, Dennis Jacobfeuerborn wrote:
Hi, I've followed the instructions on http://fedoraproject.org/wiki/Test_Day:2012-09-18_OpenStack and on F18 TC3 they work out of the box.
No I try to deploy Quantum using http://fedoraproject.org/wiki/QA:Testcase_Quantum_V2 but these instructions don't seem to work.
The first issue is that the initial "OS_USERNAME=quantum" result in commands such as "keystone tenant-list" ending with an authorization error. When I ignore this bit and use the admin credentials from the keystonerc instead the following instructions work fine.
The problem is due to the fact that the Quantum user was not created in keystone. This is due to a change in the script openstack-demo-install. Originally there was a flag ENABLE_QUANTUM which was set as TRUE. This enabled the keystone script https://github.com/openstack/keystone/blob/master/tools/sample_data.sh#L233 to build the relevant Quantum user.
We need to update the documentation.
https://github.com/fedora-openstack/openstack-utils/blob/master/utils/openstack-demo-install
I can then follow the full setup and 99% of the "How to test" section but when I try to associate a floating ip with "quantum floatingip-associate <floating ip id> <portid>" I run into trouble.
The port_id is the ID of the port for the VM. You can get this via "quantum port-list".
Since the value of<portid> isn't mentioned at all I assume it is the port of the virtual machine which was launched with the ip 10.0.0.3 however when I try to execute the command I get:
Could not find an external network gateway reachable from subnet 4a2e2166-b543-4b74-af74-0f3a4b31dd1a. Therefore, cannot associate Port 3c4b6375-7dca-4f58-9fef-e941ea8ff948 with a Floating IP.
Did you create the floating IP network (external network)? Please note that you need to make sure that the correct tenants as used. The keystone configuration above could have been the root cause.
This is the subnet: +------------------+--------------------------------------------+ | Field | Value | +------------------+--------------------------------------------+ | allocation_pools | {"start": "10.0.0.2", "end": "10.0.0.254"} | | cidr | 10.0.0.0/24 | | dns_nameservers | | | enable_dhcp | True | | gateway_ip | 10.0.0.1 | | host_routes | | | id | 4a2e2166-b543-4b74-af74-0f3a4b31dd1a | | ip_version | 4 | | name | | | network_id | 26e64cea-5f27-46d9-9ea7-96837057e5fa | | tenant_id | 68722f889ae04b569b765ed9fd2f13da | +------------------+--------------------------------------------+
What's interesting here is that 10.0.0.1 is listed as the gateway_ip yet in the "Expected results" section of the page this IP is listed as the DHCP IP?
Any ideas what is wrong here or how to debug it?
Regards, Dennis _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
Thanks for the pointers. I tried adding the ENABLE_QUANTUM back in but that just made the script fail. The second try with the unedited script and then manually adding the quantum user succeeded though and I was able to add the floating ip, ping the VM and ssh into it using that ip.
The only problem left now is that while I can ssh into the VM I cannot reach the outside world from the VM. I have an internal network of 10.0.0.0/24 and an external one of 192.168.17.0/24 and the gateway ip's are 10.0.0.1 and 192.168.17.1 respectively. Inside the VM I can ping 10.0.0.1 and 192.168.17.1 (which is configured on br-ex) but nothing beyond that.
Doing a tcpdump on the q{br,vb,vo}715a5e89-79 I can see the ping requests from 10.0.0.3 (internal ip of the VM) to 8.8.8.8 but I don't see them on the physical interface. Same thing when I try to ping the ip of the Host.
Apparently the packets are unable to leave br-ex toward the host system or the internet (I've set /proc/sys/net/ipv4/ip_forward to 1). Any ideas what could be the problem here?
Regards, Dennis
On 12/27/2012 09:11 AM, Gary Kotton wrote:
On 12/26/2012 09:36 PM, Dennis Jacobfeuerborn wrote:
Hi, I've followed the instructions on http://fedoraproject.org/wiki/Test_Day:2012-09-18_OpenStack and on F18 TC3 they work out of the box.
No I try to deploy Quantum using http://fedoraproject.org/wiki/QA:Testcase_Quantum_V2 but these instructions don't seem to work.
The first issue is that the initial "OS_USERNAME=quantum" result in commands such as "keystone tenant-list" ending with an authorization error. When I ignore this bit and use the admin credentials from the keystonerc instead the following instructions work fine.
The problem is due to the fact that the Quantum user was not created in keystone. This is due to a change in the script openstack-demo-install. Originally there was a flag ENABLE_QUANTUM which was set as TRUE. This enabled the keystone script https://github.com/openstack/keystone/blob/master/tools/sample_data.sh#L233 to build the relevant Quantum user.
We need to update the documentation.
https://github.com/fedora-openstack/openstack-utils/blob/master/utils/openstack-demo-install
I can then follow the full setup and 99% of the "How to test" section but when I try to associate a floating ip with "quantum floatingip-associate <floating ip id> <portid>" I run into trouble.
The port_id is the ID of the port for the VM. You can get this via "quantum port-list".
Since the value of <portid> isn't mentioned at all I assume it is the port of the virtual machine which was launched with the ip 10.0.0.3 however when I try to execute the command I get:
Could not find an external network gateway reachable from subnet 4a2e2166-b543-4b74-af74-0f3a4b31dd1a. Therefore, cannot associate Port 3c4b6375-7dca-4f58-9fef-e941ea8ff948 with a Floating IP.
Did you create the floating IP network (external network)? Please note that you need to make sure that the correct tenants as used. The keystone configuration above could have been the root cause.
This is the subnet: +------------------+--------------------------------------------+ | Field | Value | +------------------+--------------------------------------------+ | allocation_pools | {"start": "10.0.0.2", "end": "10.0.0.254"} | | cidr | 10.0.0.0/24 | | dns_nameservers | | | enable_dhcp | True | | gateway_ip | 10.0.0.1 | | host_routes | | | id | 4a2e2166-b543-4b74-af74-0f3a4b31dd1a | | ip_version | 4 | | name | | | network_id | 26e64cea-5f27-46d9-9ea7-96837057e5fa | | tenant_id | 68722f889ae04b569b765ed9fd2f13da | +------------------+--------------------------------------------+
What's interesting here is that 10.0.0.1 is listed as the gateway_ip yet in the "Expected results" section of the page this IP is listed as the DHCP IP?
Any ideas what is wrong here or how to debug it?
Regards, Dennis _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud