Re: [Openstack-operators] OpenStack-operators Digest, Vol 76, Issue 30

Hi, I am trying to integrate ODL as external OVS manager and network controller but I could not mange to connect br-ex as ODL_BRIDGE_MAPPING with public interface eth2, ovs vsctl show:- Manager "tcp:192.67.27.27:6640" is_connected: true Manager "ptcp:6641:127.0.0.1" is_connected: true Bridge

[Openstack-operators] unsubscribe

___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Large deployments] Neutron issues in Openstack Large deployment using DVR

Hi Saverio, Thanks for your inputs. Will test with statable/ocata branch code and will share the result. Thanks, Satya.P On Wed, Feb 22, 2017 at 1:54 AM, Saverio Proto wrote: > Hello, > > I would use at least the stable/ocata branch. If you just use master > that is not

Re: [Openstack-operators] HTTP/S Termination with Haproxy + Keystone

Do you have this in your haproxy front end config? reqadd X-Forwarded-Proto:\ https And this in your keystone.conf ? secure_proxy_ssl_header=HTTP_X_FORWARDED_PROTO I think that’s what I had to do to tell haproxy to add a headder that keystone then matched to know when to return https. > On

[Openstack-operators] HTTP/S Termination with Haproxy + Keystone

I'm having a strange issue with keystone after migrating all public endpoints to https (haproxy terminates the SSL connection for each service): openstack endpoint list

[Openstack-operators] [telecom-nfv] Meeting #19 tomorrow

Hi All, We will have our bi-weekly meeting tomorrow. If you can attend, please do, and feel free to add to the agenda as it is quite light right now [1]. Might be a short meeting without some more items. :) Thanks, Curtis. [1]: https://etherpad.openstack.org/p/ops-telco-nfv-meeting-agenda

Re: [Openstack-operators] [Large deployments] Neutron issues in Openstack Large deployment using DVR

Hi Saverio, We have tried to create 20 VMs each time using heat template. There is 1 sec time gap between each VM creation request. When we reached 114 VMs we got the error mentioned in the below mail.Heat template will boot instance from volume and it assigns floating IP to the instance. Except

[Openstack-operators] [scientific][scientific-wg] Reminder: IRC meeting Tuesday 2100

Greetings - We have a Scientific WG IRC meeting shortly, at 2100 UTC in channel #openstack-meeting The agenda is available here[1] and full IRC meeting details are here[2]. This week we’ll survey some new work in the HPC monitoring landscape, look at the study coming together for identity

Re: [Openstack-operators] [Large deployments] Neutron issues in Openstack Large deployment using DVR

Hello Satya, I would fill a bug on launchpad for this issue. 114 VMs is not much. Can you identify how to trigger the issue to reproduce it ? or it just happens randomly ? When you say rebooting the network node, do you mean the server running the neutron-server process ? what version and

Re: [Openstack-operators] [nova] Metadata service over virtio-vsock

On Tue, Feb 21, 2017 at 10:08:54AM -0500, David Medberry wrote: > Doesn't the virtio solution assume/require a libvirt or more exactly a > QEMU/KVM based hypervisor? > > What about the N-1 other hypervisors? vsock is an equivalent of UNIX domain sockets, for host<->guest communication that was

Re: [Openstack-operators] [nova] Metadata service over virtio-vsock

Doesn't the virtio solution assume/require a libvirt or more exactly a QEMU/KVM based hypervisor? What about the N-1 other hypervisors? I think the idea of a "hot remove, hot add" of the configdrive has some merit (but remember it is not always ISO-9660 but could be VFAT as well to aid in some

Re: [Openstack-operators] [nova] Metadata service over virtio-vsock

On Tue, Feb 21, 2017 at 01:09:43PM +, Jeremy Stanley wrote: > On 2017-02-21 06:24:20 -0500 (-0500), Clint Byrum wrote: > [...] > > Why not just make it a virtual USB drive that ejects and > > re-attaches on changes? > [...] > > Is there a graceful way to trigger that from the host so that the

Re: [Openstack-operators] [nova] Metadata service over virtio-vsock

On 2017-02-21 06:24:20 -0500 (-0500), Clint Byrum wrote: [...] > Why not just make it a virtual USB drive that ejects and > re-attaches on changes? [...] Is there a graceful way to trigger that from the host so that the guest knows to unmount it prior to ejection? Or is that not actually

[Openstack-operators] [Large deployments] Neutron issues in Openstack Large deployment using DVR

Hi All, We are trying to deploy Openstack in our production environment. For networking we are using DVR with out L3 HA. We are able to create 114 VMs with out any issue. After creating 114 VMs we are getting the below error. Error: 504 Gateway Time-out The server didn't respond in time.

Re: [Openstack-operators] [nova] Metadata service over virtio-vsock

Excerpts from Daniel P. Berrange's message of 2017-02-21 10:40:02 +: > On Mon, Feb 20, 2017 at 02:36:15PM -0500, Clint Byrum wrote: > > What exactly is the security concern of the metadata service? Perhaps > > those concerns can be addressed directly? > > > > I ask because anything that

Re: [Openstack-operators] [nova] Metadata service over virtio-vsock

On Mon, Feb 20, 2017 at 02:36:15PM -0500, Clint Byrum wrote: > What exactly is the security concern of the metadata service? Perhaps > those concerns can be addressed directly? > > I ask because anything that requires special software on the guest is > a non-starter IMO. virtio is a Linux thing,

Re: [Openstack-operators] [nova] Metadata service over virtio-vsock

On Mon, Feb 20, 2017 at 08:08:00PM +, Jeremy Stanley wrote: > On 2017-02-20 14:36:15 -0500 (-0500), Clint Byrum wrote: > > What exactly is the security concern of the metadata service? Perhaps > > those concerns can be addressed directly? > [...] > > A few I'm aware of: > > 1. It's something