Eugen Block
Hey guys,
it's been a while since my last response, I wasn't on vacation all this time ;-) We are fighting with our cloud environment and have an open Service Request for an issue where openvswitch causes problems. I didn't count how many times I re-installed our cloud nodes from scratch in the last two weeks
Sorry to hear that :-(
but last week happened something strange. I don't know why, but one single installation worked and I had the chance to see what the network configuration is supposed to look like. Of course I tried to reproduce it, but it didn't work at all since last week. I just wanted to share what I saw, maybe one of you is facing the same question. The difference to our settings when I posted this question lies in the neutron barclamp. When we set up our first environments we used "linuxbridge", but as you read in my question, the instances had no IP and there was a lot of modification required to get it all working as desired.
What kind of modifications? You should not have to do any manual modifications at all, assuming that your Crowbar network config (network.json) is correct.
Then we tried openvswitch with vlan, but we are facing major problems while trying to deploy nova barclamp. As I already mentioned, we got it working only once, but it's not reproducable. Anyway, with openvswitch the instance get their IP injected and you can see it directly in the login prompt. If you configure your security groups and rules correctly, the instances can ping your external network etc. So if - and only if - you get your cloud working with openvswitch, the cloud is able to handle all the traffic correctly, just as Rossella described in her first answer. I just wish that there was a hint or a recommendation or a description which settings should be used when deploying neutron.
Any of the settings we offer in Crowbar should work, but of course which settings to use depends somewhat on your network environment. In order to help you, we'd need exact details plus supportconfig tarballs (or even better, remote access). BTW I cannot stress enough the importance of that last sentence ;-)
Anyway, now I understand the description here: http://docs.openstack.org/openstack-ops/content/network_troubleshooting.html
The configuration on control (network) and compute nodes looked exactly like described. Now I just need to get the cloud working again, which seems to be quite difficult, our SR is open vor weeks now.
Really? :-/ I don't remember seeing anything come through, but maybe I missed it while I was away. What is the SR number, and which support engineer have you been assigned? This is exactly the kind of problem where the support we provide can mean the difference between you experiencing weeks of frustration, and getting the problem solved very quickly. Network configuration in particular is very complicated but we have a lot of experience at it and obviously we know the product very well. So please don't feel you have to solve this alone - let's make sure you get the right kind of support so we can get it resolved quickly! -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org