| bhola | frickler, any idea how to get it working? | 00:03 |
|---|---|---|
| *** mhen_ is now known as mhen | 01:42 | |
| DeHackEd | bhola: the concept is that the provider network is a real network (probably either flat or vlan) that already exists. neutron routers are NAT routers, but will also do IP rewrites for VMs on tenant networks to make it appear they have a floating IP assigned even though they still use 192.168.x.x IPs. | 02:12 |
| DeHackEd | can you make routers and have the routers pingable? | 02:13 |
| bhola | DeHackEd, Thanks for your message. I can make routers and attach networks to them. But how I can ping them from outside if there is no IP available/visible from compute/neutron nodes. I can see a number of interfaces created by openstack system on compute node but they are all without IPs. That's what I am saying that at leasat one bridge/switch interface should have an IP so I can access the private networks. | 09:04 |
| bhola | and most of these virtual bridge/switch interfaces state is DOWN if i look at them at compute node's shell. But in the horizon interface it is showing all of the routers/interfaces up | 09:09 |
| bhola | DeHackEd, I think you were offline. Did you read my messages? | 14:29 |
| DeHackEd | neutron makes routers using network namespaces. you won't directly see them on the host, but `ip netns ls` will show them. also any IPs assigned from your provider ("public" IP block) should be in use and pingable | 14:43 |
| bhola | DeHackEd, with command ip netns ls shows nothing. One instance is running at the moment. I can see all the IPs in horizon I have associated an IP from provider network to the instance as floating IP but I cannot access provider network from anywhere. | 14:48 |
| bhola | Another issue is I cannot connect to my instance through console. I am using vnc. it opens in console on horizon but doesn't accept any keyboard entry. So there is no way to connect to the instance. Neither through console nor through floating ip. | 14:51 |
| bhola | Even issuing command "ip route" doesn't any route to provider network. | 14:52 |
| DeHackEd | instructions in the console describe how to get the keyboard grabbed by the vnc interface (as opposed to interpreted by the browser) | 15:05 |
| DeHackEd | floating IPs need routers. they just install a NAT rule: destination is the floating IP, rewrite to the target server's IP and forward (and a matching reverse) | 15:06 |
| bhola | DeHackEd, Yes, that is what I am saying. We should have access to floating IP from compute node's shell. Right? But I don't have access to floating IP. Ip a command shows a list of interfaces and bridges but none of them is assigned any ip. | 17:28 |
| bhola | By the way, where are the instructions to get the keyboard grabbed by vnc? | 17:29 |
| DeHackEd | click the blue header box over the VNC area | 18:05 |
| bhola | I click it but it doesn't grab the keyboard. | 18:10 |
| bhola | is there any specific setting in the config file to change for grabbing the keyboard? | 18:25 |
| drlkf | is it common practice to have a dedicated auth node, and all the compute nodes are controllers? | 20:24 |
| DeHackEd | I suspect it's more common to have a dedicated auth + controller node (eg: nova-scheduler, nova-api, etc) and then the compute nodes are dedicated compute. | 21:55 |
| DeHackEd | or, cluster of controllers if your cluster is large enough or highly available to require that | 21:56 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!