Re: [Openstack] Allocating dynamic IP to the VMs
any idea, anyone? On 11 May 2013 10:37, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: Hello Sylvain, I am sorry I got caught up with another project in the past few weeks, hence my late reply. Please bare with me. The floating ip is bound to the qg-550803ee-ce bridge. root@controller:~# ip a 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000 link/ether d4:ae:52:bb:aa:20 brd ff:ff:ff:ff:ff:ff inet 192.168.2.225/24 brd 192.168.2.255 scope global eth0 inet6 fe80::d6ae:52ff:febb:aa20/64 scope link valid_lft forever preferred_lft forever 3: eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000 link/ether d4:ae:52:bb:aa:21 brd ff:ff:ff:ff:ff:ff inet 10.10.10.1/24 brd 10.10.10.255 scope global eth1 inet6 fe80::d6ae:52ff:febb:aa21/64 scope link valid_lft forever preferred_lft forever 31: br-int: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN link/ether e6:fe:c6:5e:73:47 brd ff:ff:ff:ff:ff:ff 32: br-ex: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether f6:26:0f:0d:32:45 brd ff:ff:ff:ff:ff:ff inet6 fe80::f426:fff:fe0d:3245/64 scope link valid_lft forever preferred_lft forever 33: tapd648cfe0-f6: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether fa:16:3e:9a:2c:29 brd ff:ff:ff:ff:ff:ff inet 10.5.5.2/24 brd 10.5.5.255 scope global tapd648cfe0-f6 inet6 fe80::f816:3eff:fe9a:2c29/64 scope link valid_lft forever preferred_lft forever 34: br-tun: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN link/ether 5e:2b:f9:ca:c6:40 brd ff:ff:ff:ff:ff:ff 35: qr-9e818b07-92: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether fa:16:3e:01:48:1d brd ff:ff:ff:ff:ff:ff inet 10.5.5.1/24 brd 10.5.5.255 scope global qr-9e818b07-92 inet6 fe80::f816:3eff:fe01:481d/64 scope link valid_lft forever preferred_lft forever 36: qg-550803ee-ce: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether fa:16:3e:fc:87:1c brd ff:ff:ff:ff:ff:ff inet 192.168.2.151/24 brd 192.168.2.255 scope global qg-550803ee-ce inet 192.168.2.152/32 brd 192.168.2.152 scope global qg-550803ee-ce inet6 fe80::f816:3eff:fefc:871c/64 scope link valid_lft forever preferred_lft forever But I can not ping the floating ip. root@controller:~# quantum net-list -- --router:external True +-+--+---+ | id | name | subnets | ++---+---+ | a83c3409-6c79-4bb7-9557-010f3b56024f | ext_net | fb3439f4-2afa-4cdc-86a6-aaee2ce1a3a3 | ++---+---+ root@controller:~# quantum floatingip-list +---+--+++ | id | fixed_ip_address | floating_ip_address | port_id | ++-+++ | 46311a66-5793-43af-be74-612580e505ca | 10.5.5.3 | 192.168.2.152 | 529f6c56-8037-489a-a120-b97675d1745f | +-- -+-+++ Any idea? On 25 March 2013 16:09, Sylvain Bauza sylvain.ba...@digimind.com wrote: Le 25/03/2013 16:00, Chathura M. Sarathchandra Magurawalage a écrit : I can not see anything going through qg- interface. Your iptables seem correct. Could you please ip a and make sure floating ip is bound to qg- ? Are you sure that floating IPs are working properly on your setup ? -Sylvain ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
Hello Sylvain, I am sorry I got caught up with another project in the past few weeks, hence my late reply. Please bare with me. The floating ip is bound to the qg-550803ee-ce bridge. root@controller:~# ip a 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000 link/ether d4:ae:52:bb:aa:20 brd ff:ff:ff:ff:ff:ff inet 192.168.2.225/24 brd 192.168.2.255 scope global eth0 inet6 fe80::d6ae:52ff:febb:aa20/64 scope link valid_lft forever preferred_lft forever 3: eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000 link/ether d4:ae:52:bb:aa:21 brd ff:ff:ff:ff:ff:ff inet 10.10.10.1/24 brd 10.10.10.255 scope global eth1 inet6 fe80::d6ae:52ff:febb:aa21/64 scope link valid_lft forever preferred_lft forever 31: br-int: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN link/ether e6:fe:c6:5e:73:47 brd ff:ff:ff:ff:ff:ff 32: br-ex: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether f6:26:0f:0d:32:45 brd ff:ff:ff:ff:ff:ff inet6 fe80::f426:fff:fe0d:3245/64 scope link valid_lft forever preferred_lft forever 33: tapd648cfe0-f6: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether fa:16:3e:9a:2c:29 brd ff:ff:ff:ff:ff:ff inet 10.5.5.2/24 brd 10.5.5.255 scope global tapd648cfe0-f6 inet6 fe80::f816:3eff:fe9a:2c29/64 scope link valid_lft forever preferred_lft forever 34: br-tun: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN link/ether 5e:2b:f9:ca:c6:40 brd ff:ff:ff:ff:ff:ff 35: qr-9e818b07-92: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether fa:16:3e:01:48:1d brd ff:ff:ff:ff:ff:ff inet 10.5.5.1/24 brd 10.5.5.255 scope global qr-9e818b07-92 inet6 fe80::f816:3eff:fe01:481d/64 scope link valid_lft forever preferred_lft forever 36: qg-550803ee-ce: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether fa:16:3e:fc:87:1c brd ff:ff:ff:ff:ff:ff inet 192.168.2.151/24 brd 192.168.2.255 scope global qg-550803ee-ce inet 192.168.2.152/32 brd 192.168.2.152 scope global qg-550803ee-ce inet6 fe80::f816:3eff:fefc:871c/64 scope link valid_lft forever preferred_lft forever But I can not ping the floating ip. root@controller:~# quantum net-list -- --router:external True +-+--+---+ | id | name | subnets | ++---+---+ | a83c3409-6c79-4bb7-9557-010f3b56024f | ext_net | fb3439f4-2afa-4cdc-86a6-aaee2ce1a3a3 | ++---+---+ root@controller:~# quantum floatingip-list +---+--+++ | id | fixed_ip_address | floating_ip_address | port_id | ++-+++ | 46311a66-5793-43af-be74-612580e505ca | 10.5.5.3 | 192.168.2.152 | 529f6c56-8037-489a-a120-b97675d1745f | +-- -+-+++ Any idea? On 25 March 2013 16:09, Sylvain Bauza sylvain.ba...@digimind.com wrote: Le 25/03/2013 16:00, Chathura M. Sarathchandra Magurawalage a écrit : I can not see anything going through qg- interface. Your iptables seem correct. Could you please ip a and make sure floating ip is bound to qg- ? Are you sure that floating IPs are working properly on your setup ? -Sylvain ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
The basic troubleshooting steps for L3 mapping are : 1. make sure your DNAT/SNAT entries have been populated correctly (using 'iptables -t nat -L -n ) 2. monitor your qg-X interface making sure SNAT is working properly (using 'tcpdump -i qg- -nn) and checking that you actually have *two* TCP requests with the same id (the first one with the private IP, the second one with the public IP) 3. make sure you activated ip_forward in /etc/sysctl.conf and either reboot or sysctl -w the value (and restart quantum-l3-agent in this case) If these 3 steps are OK, then you have a gateway issue, not related to Quantum. -Sylvain Le 24/03/2013 15:49, Chathura M. Sarathchandra Magurawalage a écrit : Thanks Sylvain, I have tried this, but does not seem to work. I can allocate the floating ip to the VM but it is not accessible from the physical network. I can not ping to it from the controller or any other physical nodes. Any idea? On 19 March 2013 16:14, Sylvain Bauza sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote: As per http://docs.openstack.org/folsom/openstack-network/admin/content/demo_logical_network_config.html but slightly modified as per CLI help, quantum net-create ext_net --tenant-id $TENANT_ID --router:external=True quantum subnet-create --ip_version 4 --allocation-pool start=192.168.2.151,end=192.168.2.240 \ --gateway 192.168.2.253 id_of_ext_net192.168.2.0/24 http://192.168.2.0/24 -- --enable_dhcp=False It will create ext_net subnet with preallocated IP range. For each VM, allocate floating IP from this pool and then associate it with the internal port. Hope it can helps, -Sylvain Le 19/03/2013 13:44, Chathura M. Sarathchandra Magurawalage a écrit : Thanks. its 192.168.2.0/24 http://192.168.2.0/24 free ip range: 192.168.2.151 192.168.2.240 gw/dhcp server: 192.168.2.253 On 19 March 2013 08:28, Sylvain Bauza sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote: In that case, please refer to my previous e-mail : use floating IPs bound to the same physical network. That's up to you to know which IP pools are available inside your network. Once you get one, create a external Quantum subnet defined with this IP range. Sorry, I have feeling to explain again and again. If you still don't catch the point, could you please then tell me your physical net/CIDR, your free IP range and your gateway, and I'll mix you up the command to issue. -Sylvain Le 18/03/2013 18:02, Chathura M. Sarathchandra Magurawalage a écrit : Thanks Sylvain, There must be a way of doing this without having to do anything with my default gateway of my physical network? . Even if I have to I do not wan to do anything to the physical gateway. All I need is a way to let the VMs get a dynamic IP from the physical network. How can I do this. For example this can be done on virtual box using a bridge adapter which maps the VM in to the physical network. On 18 March 2013 16:05, Sylvain Bauza sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote: Could you please tell me your physical network CIDR ? Anyway, what you need is not requiring having a floating IP pool inside the same network, you can also play with static routing : if your physical host does have a default gw, you can create a static route from this gw to the VM network gateway. And on the VM network gateway, do the same... -Sylvain Le 18/03/2013 16:53, Chathura M. Sarathchandra Magurawalage a écrit : Hey Sylvain, Basically what I need is to have the VMs mapped to my physical network so that my physical hosts can directly access the VMs. How can I do this? Thanks. On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote: Hi, I don't understand your business. Should you have a 192.168.1.0/24 http://192.168.1.0/24 network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24 http://192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 http://192.168.1.0/24 in Quantum with .1-.100 (for example) as the range,
Re: [Openstack] Allocating dynamic IP to the VMs
Thanks Sylvain, I will check and get back to you on this. I have got one question on this. Does quantum directly request leases from the gateway of the physical network before reserving them to allocate to VMs? On 25 March 2013 10:53, Sylvain Bauza sylvain.ba...@digimind.com wrote: The basic troubleshooting steps for L3 mapping are : 1. make sure your DNAT/SNAT entries have been populated correctly (using 'iptables -t nat -L -n ) 2. monitor your qg-X interface making sure SNAT is working properly (using 'tcpdump -i qg- -nn) and checking that you actually have *two* TCP requests with the same id (the first one with the private IP, the second one with the public IP) 3. make sure you activated ip_forward in /etc/sysctl.conf and either reboot or sysctl -w the value (and restart quantum-l3-agent in this case) If these 3 steps are OK, then you have a gateway issue, not related to Quantum. -Sylvain Le 24/03/2013 15:49, Chathura M. Sarathchandra Magurawalage a écrit : Thanks Sylvain, I have tried this, but does not seem to work. I can allocate the floating ip to the VM but it is not accessible from the physical network. I can not ping to it from the controller or any other physical nodes. Any idea? On 19 March 2013 16:14, Sylvain Bauza sylvain.ba...@digimind.com wrote: As per http://docs.openstack.org/folsom/openstack-network/admin/content/demo_logical_network_config.htmlbut slightly modified as per CLI help, quantum net-create ext_net --tenant-id $TENANT_ID --router:external=True quantum subnet-create --ip_version 4 --allocation-pool start=192.168.2.151,end=192.168.2.240 \ --gateway 192.168.2.253 id_of_ext_net 192.168.2.0/24 -- --enable_dhcp=False It will create ext_net subnet with preallocated IP range. For each VM, allocate floating IP from this pool and then associate it with the internal port. Hope it can helps, -Sylvain Le 19/03/2013 13:44, Chathura M. Sarathchandra Magurawalage a écrit : Thanks. its 192.168.2.0/24 free ip range: 192.168.2.151 192.168.2.240 gw/dhcp server: 192.168.2.253 On 19 March 2013 08:28, Sylvain Bauza sylvain.ba...@digimind.com wrote: In that case, please refer to my previous e-mail : use floating IPs bound to the same physical network. That's up to you to know which IP pools are available inside your network. Once you get one, create a external Quantum subnet defined with this IP range. Sorry, I have feeling to explain again and again. If you still don't catch the point, could you please then tell me your physical net/CIDR, your free IP range and your gateway, and I'll mix you up the command to issue. -Sylvain Le 18/03/2013 18:02, Chathura M. Sarathchandra Magurawalage a écrit : Thanks Sylvain, There must be a way of doing this without having to do anything with my default gateway of my physical network? . Even if I have to I do not wan to do anything to the physical gateway. All I need is a way to let the VMs get a dynamic IP from the physical network. How can I do this. For example this can be done on virtual box using a bridge adapter which maps the VM in to the physical network. On 18 March 2013 16:05, Sylvain Bauza sylvain.ba...@digimind.comwrote: Could you please tell me your physical network CIDR ? Anyway, what you need is not requiring having a floating IP pool inside the same network, you can also play with static routing : if your physical host does have a default gw, you can create a static route from this gw to the VM network gateway. And on the VM network gateway, do the same... -Sylvain Le 18/03/2013 16:53, Chathura M. Sarathchandra Magurawalage a écrit : Hey Sylvain, Basically what I need is to have the VMs mapped to my physical network so that my physical hosts can directly access the VMs. How can I do this? Thanks. On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.comwrote: Hi, I don't understand your business. Should you have a 192.168.1.0/24network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254 being the external gateway. Thanks, -Sylvain Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit : anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have
Re: [Openstack] Allocating dynamic IP to the VMs
Le 25/03/2013 12:49, Chathura M. Sarathchandra Magurawalage a écrit : I have got one question on this. Does quantum directly request leases from the gateway of the physical network before reserving them to allocate to VMs? Nope, not at all. It's up to the administrator to make sure the IP ranges for Openstack are not pooled by any other DHCP server. There is (as per my knowledge) no way to sync up in between quantum-l3-agent and other DHCP servers. Actually, contrary to fixed ip networks in Quantum, floating IP networks are not DHCP managed. Eligibility is made upon next IP address available in Quantum mysql database and directly injected into iptables, that's it. -Sylvain ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
Thanks. root@controller:~# iptables -t nat -L -n Chain PREROUTING (policy ACCEPT) target prot opt source destination quantum-l3-agent-PREROUTING all -- 0.0.0.0/00.0.0.0/0 nova-api-PREROUTING all -- 0.0.0.0/00.0.0.0/0 Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination quantum-l3-agent-OUTPUT all -- 0.0.0.0/00.0.0.0/0 nova-api-OUTPUT all -- 0.0.0.0/00.0.0.0/0 Chain POSTROUTING (policy ACCEPT) target prot opt source destination quantum-l3-agent-POSTROUTING all -- 0.0.0.0/00.0.0.0/0 nova-api-POSTROUTING all -- 0.0.0.0/00.0.0.0/0 quantum-postrouting-bottom all -- 0.0.0.0/00.0.0.0/0 nova-postrouting-bottom all -- 0.0.0.0/00.0.0.0/0 Chain nova-api-OUTPUT (1 references) target prot opt source destination Chain nova-api-POSTROUTING (1 references) target prot opt source destination Chain nova-api-PREROUTING (1 references) target prot opt source destination Chain nova-api-float-snat (1 references) target prot opt source destination Chain nova-api-snat (1 references) target prot opt source destination nova-api-float-snat all -- 0.0.0.0/00.0.0.0/0 Chain nova-postrouting-bottom (1 references) target prot opt source destination nova-api-snat all -- 0.0.0.0/00.0.0.0/0 Chain quantum-l3-agent-OUTPUT (1 references) target prot opt source destination DNAT all -- 0.0.0.0/0192.168.2.152to:10.5.5.3 Chain quantum-l3-agent-POSTROUTING (1 references) target prot opt source destination ACCEPT all -- 0.0.0.0/00.0.0.0/0! ctstate DNAT ACCEPT all -- 10.5.5.0/24 192.168.2.225 Chain quantum-l3-agent-PREROUTING (1 references) target prot opt source destination DNAT tcp -- 0.0.0.0/0169.254.169.254 tcp dpt:80 to: 192.168.2.225:8775 DNAT all -- 0.0.0.0/0192.168.2.152to:10.5.5.3 Chain quantum-l3-agent-float-snat (1 references) target prot opt source destination SNAT all -- 10.5.5.3 0.0.0.0/0 to:192.168.2.152 Chain quantum-l3-agent-snat (1 references) target prot opt source destination quantum-l3-agent-float-snat all -- 0.0.0.0/00.0.0.0/0 SNAT all -- 10.5.5.0/24 0.0.0.0/0 to:192.168.2.151 Chain quantum-postrouting-bottom (1 references) target prot opt source destination quantum-l3-agent-snat all -- 0.0.0.0/00.0.0.0/0 I can not see anything going through qg- interface. I have activated net.ipv4.ip_forward in /etc/sysctl.conf. On 25 March 2013 13:03, Sylvain Bauza sylvain.ba...@digimind.com wrote: Le 25/03/2013 12:49, Chathura M. Sarathchandra Magurawalage a écrit : I have got one question on this. Does quantum directly request leases from the gateway of the physical network before reserving them to allocate to VMs? Nope, not at all. It's up to the administrator to make sure the IP ranges for Openstack are not pooled by any other DHCP server. There is (as per my knowledge) no way to sync up in between quantum-l3-agent and other DHCP servers. Actually, contrary to fixed ip networks in Quantum, floating IP networks are not DHCP managed. Eligibility is made upon next IP address available in Quantum mysql database and directly injected into iptables, that's it. -Sylvain ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
Le 25/03/2013 16:00, Chathura M. Sarathchandra Magurawalage a écrit : I can not see anything going through qg- interface. Your iptables seem correct. Could you please ip a and make sure floating ip is bound to qg- ? Are you sure that floating IPs are working properly on your setup ? -Sylvain ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
Thanks Sylvain, I have tried this, but does not seem to work. I can allocate the floating ip to the VM but it is not accessible from the physical network. I can not ping to it from the controller or any other physical nodes. Any idea? On 19 March 2013 16:14, Sylvain Bauza sylvain.ba...@digimind.com wrote: As per http://docs.openstack.org/folsom/openstack-network/admin/content/demo_logical_network_config.htmlbut slightly modified as per CLI help, quantum net-create ext_net --tenant-id $TENANT_ID --router:external=True quantum subnet-create --ip_version 4 --allocation-pool start=192.168.2.151,end=192.168.2.240 \ --gateway 192.168.2.253 id_of_ext_net 192.168.2.0/24 -- --enable_dhcp=False It will create ext_net subnet with preallocated IP range. For each VM, allocate floating IP from this pool and then associate it with the internal port. Hope it can helps, -Sylvain Le 19/03/2013 13:44, Chathura M. Sarathchandra Magurawalage a écrit : Thanks. its 192.168.2.0/24 free ip range: 192.168.2.151 192.168.2.240 gw/dhcp server: 192.168.2.253 On 19 March 2013 08:28, Sylvain Bauza sylvain.ba...@digimind.com wrote: In that case, please refer to my previous e-mail : use floating IPs bound to the same physical network. That's up to you to know which IP pools are available inside your network. Once you get one, create a external Quantum subnet defined with this IP range. Sorry, I have feeling to explain again and again. If you still don't catch the point, could you please then tell me your physical net/CIDR, your free IP range and your gateway, and I'll mix you up the command to issue. -Sylvain Le 18/03/2013 18:02, Chathura M. Sarathchandra Magurawalage a écrit : Thanks Sylvain, There must be a way of doing this without having to do anything with my default gateway of my physical network? . Even if I have to I do not wan to do anything to the physical gateway. All I need is a way to let the VMs get a dynamic IP from the physical network. How can I do this. For example this can be done on virtual box using a bridge adapter which maps the VM in to the physical network. On 18 March 2013 16:05, Sylvain Bauza sylvain.ba...@digimind.com wrote: Could you please tell me your physical network CIDR ? Anyway, what you need is not requiring having a floating IP pool inside the same network, you can also play with static routing : if your physical host does have a default gw, you can create a static route from this gw to the VM network gateway. And on the VM network gateway, do the same... -Sylvain Le 18/03/2013 16:53, Chathura M. Sarathchandra Magurawalage a écrit : Hey Sylvain, Basically what I need is to have the VMs mapped to my physical network so that my physical hosts can directly access the VMs. How can I do this? Thanks. On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.comwrote: Hi, I don't understand your business. Should you have a 192.168.1.0/24network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254 being the external gateway. Thanks, -Sylvain Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit : anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list: https://launchpad.net/~openstack Post to :
Re: [Openstack] Allocating dynamic IP to the VMs
In that case, please refer to my previous e-mail : use floating IPs bound to the same physical network. That's up to you to know which IP pools are available inside your network. Once you get one, create a external Quantum subnet defined with this IP range. Sorry, I have feeling to explain again and again. If you still don't catch the point, could you please then tell me your physical net/CIDR, your free IP range and your gateway, and I'll mix you up the command to issue. -Sylvain Le 18/03/2013 18:02, Chathura M. Sarathchandra Magurawalage a écrit : Thanks Sylvain, There must be a way of doing this without having to do anything with my default gateway of my physical network? . Even if I have to I do not wan to do anything to the physical gateway. All I need is a way to let the VMs get a dynamic IP from the physical network. How can I do this. For example this can be done on virtual box using a bridge adapter which maps the VM in to the physical network. On 18 March 2013 16:05, Sylvain Bauza sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote: Could you please tell me your physical network CIDR ? Anyway, what you need is not requiring having a floating IP pool inside the same network, you can also play with static routing : if your physical host does have a default gw, you can create a static route from this gw to the VM network gateway. And on the VM network gateway, do the same... -Sylvain Le 18/03/2013 16:53, Chathura M. Sarathchandra Magurawalage a écrit : Hey Sylvain, Basically what I need is to have the VMs mapped to my physical network so that my physical hosts can directly access the VMs. How can I do this? Thanks. On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote: Hi, I don't understand your business. Should you have a 192.168.1.0/24 http://192.168.1.0/24 network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24 http://192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 http://192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254 being the external gateway. Thanks, -Sylvain Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit : anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com mailto:77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com mailto:77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list:https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to :openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe :https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help :https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net
Re: [Openstack] Allocating dynamic IP to the VMs
Thanks. its 192.168.2.0/24 free ip range: 192.168.2.151 192.168.2.240 gw/dhcp server: 192.168.2.253 On 19 March 2013 08:28, Sylvain Bauza sylvain.ba...@digimind.com wrote: In that case, please refer to my previous e-mail : use floating IPs bound to the same physical network. That's up to you to know which IP pools are available inside your network. Once you get one, create a external Quantum subnet defined with this IP range. Sorry, I have feeling to explain again and again. If you still don't catch the point, could you please then tell me your physical net/CIDR, your free IP range and your gateway, and I'll mix you up the command to issue. -Sylvain Le 18/03/2013 18:02, Chathura M. Sarathchandra Magurawalage a écrit : Thanks Sylvain, There must be a way of doing this without having to do anything with my default gateway of my physical network? . Even if I have to I do not wan to do anything to the physical gateway. All I need is a way to let the VMs get a dynamic IP from the physical network. How can I do this. For example this can be done on virtual box using a bridge adapter which maps the VM in to the physical network. On 18 March 2013 16:05, Sylvain Bauza sylvain.ba...@digimind.com wrote: Could you please tell me your physical network CIDR ? Anyway, what you need is not requiring having a floating IP pool inside the same network, you can also play with static routing : if your physical host does have a default gw, you can create a static route from this gw to the VM network gateway. And on the VM network gateway, do the same... -Sylvain Le 18/03/2013 16:53, Chathura M. Sarathchandra Magurawalage a écrit : Hey Sylvain, Basically what I need is to have the VMs mapped to my physical network so that my physical hosts can directly access the VMs. How can I do this? Thanks. On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.com wrote: Hi, I don't understand your business. Should you have a 192.168.1.0/24network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254 being the external gateway. Thanks, -Sylvain Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit : anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
As per http://docs.openstack.org/folsom/openstack-network/admin/content/demo_logical_network_config.html but slightly modified as per CLI help, quantum net-create ext_net --tenant-id $TENANT_ID --router:external=True quantum subnet-create --ip_version 4 --allocation-pool start=192.168.2.151,end=192.168.2.240 \ --gateway 192.168.2.253 id_of_ext_net 192.168.2.0/24 -- --enable_dhcp=False It will create ext_net subnet with preallocated IP range. For each VM, allocate floating IP from this pool and then associate it with the internal port. Hope it can helps, -Sylvain Le 19/03/2013 13:44, Chathura M. Sarathchandra Magurawalage a écrit : Thanks. its 192.168.2.0/24 http://192.168.2.0/24 free ip range: 192.168.2.151 192.168.2.240 gw/dhcp server: 192.168.2.253 On 19 March 2013 08:28, Sylvain Bauza sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote: In that case, please refer to my previous e-mail : use floating IPs bound to the same physical network. That's up to you to know which IP pools are available inside your network. Once you get one, create a external Quantum subnet defined with this IP range. Sorry, I have feeling to explain again and again. If you still don't catch the point, could you please then tell me your physical net/CIDR, your free IP range and your gateway, and I'll mix you up the command to issue. -Sylvain Le 18/03/2013 18:02, Chathura M. Sarathchandra Magurawalage a écrit : Thanks Sylvain, There must be a way of doing this without having to do anything with my default gateway of my physical network? . Even if I have to I do not wan to do anything to the physical gateway. All I need is a way to let the VMs get a dynamic IP from the physical network. How can I do this. For example this can be done on virtual box using a bridge adapter which maps the VM in to the physical network. On 18 March 2013 16:05, Sylvain Bauza sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote: Could you please tell me your physical network CIDR ? Anyway, what you need is not requiring having a floating IP pool inside the same network, you can also play with static routing : if your physical host does have a default gw, you can create a static route from this gw to the VM network gateway. And on the VM network gateway, do the same... -Sylvain Le 18/03/2013 16:53, Chathura M. Sarathchandra Magurawalage a écrit : Hey Sylvain, Basically what I need is to have the VMs mapped to my physical network so that my physical hosts can directly access the VMs. How can I do this? Thanks. On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote: Hi, I don't understand your business. Should you have a 192.168.1.0/24 http://192.168.1.0/24 network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24 http://192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 http://192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254 being the external gateway. Thanks, -Sylvain Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit : anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com mailto:77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com mailto:77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node)
Re: [Openstack] Allocating dynamic IP to the VMs
anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
Hi, I don't understand your business. Should you have a 192.168.1.0/24 network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254 being the external gateway. Thanks, -Sylvain Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit : anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com mailto:77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com mailto:77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
Hey Sylvain, Basically what I need is to have the VMs mapped to my physical network so that my physical hosts can directly access the VMs. How can I do this? Thanks. On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.com wrote: Hi, I don't understand your business. Should you have a 192.168.1.0/24network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254 being the external gateway. Thanks, -Sylvain Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit : anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
Could you please tell me your physical network CIDR ? Anyway, what you need is not requiring having a floating IP pool inside the same network, you can also play with static routing : if your physical host does have a default gw, you can create a static route from this gw to the VM network gateway. And on the VM network gateway, do the same... -Sylvain Le 18/03/2013 16:53, Chathura M. Sarathchandra Magurawalage a écrit : Hey Sylvain, Basically what I need is to have the VMs mapped to my physical network so that my physical hosts can directly access the VMs. How can I do this? Thanks. On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote: Hi, I don't understand your business. Should you have a 192.168.1.0/24 http://192.168.1.0/24 network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24 http://192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 http://192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254 being the external gateway. Thanks, -Sylvain Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit : anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com mailto:77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com mailto:77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list:https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to :openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe :https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help :https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
Thanks Sylvain, There must be a way of doing this without having to do anything with my default gateway of my physical network? . Even if I have to I do not wan to do anything to the physical gateway. All I need is a way to let the VMs get a dynamic IP from the physical network. How can I do this. For example this can be done on virtual box using a bridge adapter which maps the VM in to the physical network. On 18 March 2013 16:05, Sylvain Bauza sylvain.ba...@digimind.com wrote: Could you please tell me your physical network CIDR ? Anyway, what you need is not requiring having a floating IP pool inside the same network, you can also play with static routing : if your physical host does have a default gw, you can create a static route from this gw to the VM network gateway. And on the VM network gateway, do the same... -Sylvain Le 18/03/2013 16:53, Chathura M. Sarathchandra Magurawalage a écrit : Hey Sylvain, Basically what I need is to have the VMs mapped to my physical network so that my physical hosts can directly access the VMs. How can I do this? Thanks. On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.com wrote: Hi, I don't understand your business. Should you have a 192.168.1.0/24network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254 being the external gateway. Thanks, -Sylvain Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit : anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
In that case you have two options: 1) use floating ips 2) create a provider network that bridges to the same physical of the hosts that you want to be able to contact your vms. Aaron On Mon, Mar 18, 2013 at 10:02 AM, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: Thanks Sylvain, There must be a way of doing this without having to do anything with my default gateway of my physical network? . Even if I have to I do not wan to do anything to the physical gateway. All I need is a way to let the VMs get a dynamic IP from the physical network. How can I do this. For example this can be done on virtual box using a bridge adapter which maps the VM in to the physical network. On 18 March 2013 16:05, Sylvain Bauza sylvain.ba...@digimind.com wrote: Could you please tell me your physical network CIDR ? Anyway, what you need is not requiring having a floating IP pool inside the same network, you can also play with static routing : if your physical host does have a default gw, you can create a static route from this gw to the VM network gateway. And on the VM network gateway, do the same... -Sylvain Le 18/03/2013 16:53, Chathura M. Sarathchandra Magurawalage a écrit : Hey Sylvain, Basically what I need is to have the VMs mapped to my physical network so that my physical hosts can directly access the VMs. How can I do this? Thanks. On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.com wrote: Hi, I don't understand your business. Should you have a 192.168.1.0/24network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254 being the external gateway. Thanks, -Sylvain Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit : anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
Hello Chathura, I'm getting error when allocating floating IPs, can you allocate them? I'm creating my networking following this script: https://raw.github.com/EmilienM/openstack-folsom-guide/master/scripts/quantum-networking.sh Thank you. Guilherme. 2013/3/18 Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com Thanks Sylvain, There must be a way of doing this without having to do anything with my default gateway of my physical network? . Even if I have to I do not wan to do anything to the physical gateway. All I need is a way to let the VMs get a dynamic IP from the physical network. How can I do this. For example this can be done on virtual box using a bridge adapter which maps the VM in to the physical network. On 18 March 2013 16:05, Sylvain Bauza sylvain.ba...@digimind.com wrote: Could you please tell me your physical network CIDR ? Anyway, what you need is not requiring having a floating IP pool inside the same network, you can also play with static routing : if your physical host does have a default gw, you can create a static route from this gw to the VM network gateway. And on the VM network gateway, do the same... -Sylvain Le 18/03/2013 16:53, Chathura M. Sarathchandra Magurawalage a écrit : Hey Sylvain, Basically what I need is to have the VMs mapped to my physical network so that my physical hosts can directly access the VMs. How can I do this? Thanks. On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.com wrote: Hi, I don't understand your business. Should you have a 192.168.1.0/24network for management, you could also assign an external network with Quantum based on the same subnet (ie. 192.168.1.0/24). When creating a floating IP pool, Quantum does require at least 3 things : - the CIDR - the beginning and ending IPs - the external gateway So, based on what I previously said, you only need to create a 192.168.1.0/24 in Quantum with .1-.100 (for example) as the range, .254 being the external gateway. Thanks, -Sylvain Le 18/03/2013 16:29, Chathura M. Sarathchandra Magurawalage a écrit : anyone? On 17 March 2013 21:33, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Allocating dynamic IP to the VMs
After reading a little bit more, I think I have found what I need. It is a provider network that I need for the VMs so that they can get access to the other resources in my main network ( such as other physical hosts that are connected to the same network ). My question is, is it possible to do this alongside the use case that I have followed ( Provider router with private networks)? If so how can I do this? Thanks. On 16 March 2013 01:46, Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com wrote: Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Allocating dynamic IP to the VMs
Hello, I want to know how I can allocate a dynamic IP to the VM from the same network as the openstack hosts (controller/network-node/compute node) network/management network . For example, in virtual box you can give your VM an IP from the host's network using a Bridge adapter. How can I do this in openstack? From what I understand floating IP's are used when you have a public IP (which is static) to be allocated to VM's. My openstack installation architecture: http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html Quantum use case: http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
