[Openstack-operators] vmware nsx 6

Hi all, I would like to know if someone have configured openstack neutron with vmware nsx 6. I found old documentation about it. Regards Ignazio ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org

Re: [Openstack-operators] OpenStack Liberty automation script release.

Thank JJ, I have made a change in tools-contrib repo, please review and feedback. Hieu LE. On Sat, Dec 12, 2015 at 1:56 AM, JJ Asghar wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > > > > On Fri, Dec 11, 2015 at 8:19 AM, Bajin, Joseph >

Re: [Openstack-operators] [Neutron][DVR] point of encapsulation/locating routing tables

Did you look at the DVR scenario in the networking guide [1]? DVR and other architectures that use OVS build tunnels between br-tun bridges. [1] http://docs.openstack.org/liberty/networking-guide/scenario-dvr-ovs.html On Tue, Feb 16, 2016 at 12:47 PM, Adam Lawson wrote: > Hi

[Openstack-operators] [Neutron][DVR] point of encapsulation/locating routing tables

Hi everyone: Got a quick question for those of you with some knowledge of OVS and namespaces within the context of DVR. I'm trying to document exactly where namespaces are defined and where encapsulation occurs if using (for instance) VxLAN/GRE tunnels. Is there a quick and dirty slideshare or

Re: [Openstack-operators] How are consumers/operators new to openstack supposed to know about upper-constraints?

  -Original Message- From: Matt Riedemann Reply: Matt Riedemann Date: February 16, 2016 at 09:30:49 To: OpenStack Development Mailing List (not for usage questions) ,

[Openstack-operators] How are consumers/operators new to openstack supposed to know about upper-constraints?

We have a team just upgrading to Liberty and they are having problems. While running down their list of packages they are using, I noticed they have os-brick 0.8.0 which is the latest version (from mitaka). However, os-brick in stable/liberty upper-constraints is at 0.6.0 [1]. So while I

Re: [Openstack-operators] [nova] VM HA support in trunk

I would have to agree with Matt. The ability for any sort of handling of failures either reside within the application or tools around the application to make it work. Having the infrastructure handle the failures, I believe, is a slippery slope that is starting to appear more and more. I

[Openstack-operators] [Openstack][Neutron][Ceilometer]

Hi there, Is anyone currently using neutron-metering-agent at L3 routers level[1] successfully? [1] https://wiki.openstack.org/wiki/Neutron/Metering/Bandwidth Thanks, Rubab ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org

[Openstack-operators] [cinder] About how to make the vm use volume with libiscsi

Hi, All I want to make the qemu communicate with iscsi target using libiscsi directly, and I followed https://review.openstack.org/#/c/135854/ to add 'volume_drivers = iscsi=nova.virt.libvirt.volume.LibvirtNetVolumeDriver’ in nova.conf and then restarted nova services and cinder services, but

[Openstack-operators] OpenStack Contributor Awards

Hi all, I'd like to introduce a new round of community awards handed out by the Foundation, to be presented at the feedback session of the summit. Nothing flashy or starchy - the idea is that these are to be a little informal, quirky ... but still recognising the extremely valuable work

Re: [Openstack-operators] glance-replicator

Hi, Which version of Glance are you using? I am not able to reproduce your error message: glance-replicator compare glance1:9292 glance2:12 [Errno -2] Name or service not known Traceback (most recent call last): Expected error but in your case it feels like a basic arguments construction