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
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
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
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
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
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)
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 ?
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
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
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
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
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 (
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
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
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
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
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
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
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
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
20 matches
Mail list logo
