and enabling Making it “False” and restarting the service made everything work as we desired, which was to run an instance along with associating an IP to the machine & making it reachable.<\/p>\n Further down the line i was having conversation with Lorin<\/a> on IRC &\u00a0explained what is Namespaces is & how important it is for SDN\/Virtual Networking. I was lucky to go through this<\/a> and this<\/a> link\u00a0\u00a0to understand this magical piece added inside Linux Kernel.<\/p>\n In newbies term Net Namespaces is like LXC for networking, an independent & isolated network virtualNIC. Which means every instance started will have its own VirtualNIC\u00a0associated\u00a0with the greatness of Net Namespaces. Also\u00a0each\u00a0net<\/tt>\u00a0namespace has its own routing table, but also its own iptables chains and rules.<\/p>\n Few weeks back me & my friend wanted to try out OpenStack on CentOS. We followed all steps but after 3 days of debugging we were still not able to figure out the issue. I am total newbie with the networking part of OpenStack, trying to catch up with it. After hitting head around\u00a0forums, launchpad … <\/p>\n# use_namespaces = True<\/code> was our culprit.<\/p>\n
\nHope it helps!!<\/p>\n","protected":false},"excerpt":{"rendered":"