[Openstack-operators] Provider Networks Help

2018-08-09 Thread Matthew John
Hi, I have setup an OpenStack cloud using OpenStack-Ansible but having issues setting up networking. I need to have two external networks e.g. 10.1.0.0/24 & 10.2.0.0/24 that are accessible to instances. I have two bridges, br-ex and br-ex2, setup on the infra nodes that are able to access the

Re: [Openstack-operators] getting back onto our IRC channel

2018-08-09 Thread Jeremy Stanley
On 2018-08-09 09:56:47 +0200 (+0200), Thierry Carrez wrote: > Jeremy Stanley wrote: > > [...] > > It does indeed sound like you might be caught up in the > > aforementioned SASL-only network blacklist (I wasn't even aware of > > it until this ML thread) which Freenode staff seem to be using to > >

Re: [Openstack-operators] Openstack Version discovery with the cli client.

2018-08-09 Thread Saverio Proto
Thanks ! I think the command I was looking for is: "openstack versions show" But for example for Neutron I get just version v2.0 from Newton to Pike, that tells me very little. The use case is when testing Kubernetes on Openstack, a lot of kubernetes users cannot tell easily the version of

Re: [Openstack-operators] [nova][glance] nova-compute choosing incorrect qemu binary when scheduling 'alternate' (ppc64, armv7l) architectures?

2018-08-09 Thread Chris Apsey
Exactly. And I agree, it seems like hw_architecture should dictate which emulator is chosen, but as you mentioned its currently not. I'm not sure if this is a bug and it's supposed to 'just work', or just something that was never fully implemented (intentionally) and would be more of a

Re: [Openstack-operators] getting back onto our IRC channel

2018-08-09 Thread Thierry Carrez
Jeremy Stanley wrote: [...] It does indeed sound like you might be caught up in the aforementioned SASL-only network blacklist (I wasn't even aware of it until this ML thread) which Freenode staff seem to be using to help block the spam onslaught from some known parts of the Internet. [...]