Re: [Openstack-operators] openstack ocata gnocchi statsd errors

Hello Gordon, what do you mean with "coordination service" ? I installed ceilometer and gnocchi following ocata community documentation. Versions are the followings : openstack-gnocchi-statsd-3.1.16-1.el7.noarch python2-gnocchiclient-3.1.0-1.el7.noarch python-gnocchi-3.1.16-1.el7.noarch openstack-

Re: [Openstack-operators] openstack ocata gnocchi statsd errors

i would probably ask this question on gnocchi[1] as i don't know how many devs read this. you should also add what numerical version of gnocchi you're using and what coordination service you're using. if i were to quickly guess, i'm going to to assume you're not using a dedicated coordination s

Re: [Openstack-operators] [openstack-client] - missing commands?

On 6/13/2018 1:42 PM, Flint WALRUS wrote: Hi guys, I use the «new» openstack-client command as much as possible since a couple of years now, but yet I had a hard time recently to find equivalent command of the following: nova force-delete & The command on swift that permit to recursively uplo

Re: [Openstack-operators] large high-performance ephemeral storage

On 6/13/2018 10:54 AM, Chris Friesen wrote: Also, migration and resize are not supported for LVM-backed instances. I proposed a patch to support them (https://review.openstack.org/#/c/337334/) but hit issues and never got around to fixing them up. Yup, I guess I should have read the entire t

Re: [Openstack-operators] large high-performance ephemeral storage

On 6/13/2018 8:58 AM, Blair Bethwaite wrote: Though we have not used LVM based instance storage before, are there any significant gotchas? I know you can't resize/cold migrate lvm-backed ephemeral root disk instances: https://github.com/openstack/nova/blob/343c2bee234568855fd9e6ba075a05c2e70

[Openstack-operators] [openstack-client] - missing commands?

Hi guys, I use the «new» openstack-client command as much as possible since a couple of years now, but yet I had a hard time recently to find equivalent command of the following: nova force-delete & The command on swift that permit to recursively upload the content of a directory and automaticall

[Openstack-operators] PTG Denver 2018 Registration & Hotel Info

The fourth Project Teams Gathering will be held September 10-14th back at the Renaissance Stapleton Hotel in Denver, Colorado (3801 Quebec Street, Denver, Colorado 80207). REGISTRATION AND HOTEL Registration is now available here: https://denver2018ptg.eventbrite.com

Re: [Openstack-operators] large high-performance ephemeral storage

On 06/13/2018 07:58 AM, Blair Bethwaite wrote: Is the collective wisdom to use LVM based instances for these use-cases? Putting a host filesystem with qcow2 based disk images on it can't help performance-wise... Though we have not used LVM based instance storage before, are there any significant

[Openstack-operators] Reminder to add "nova-status upgrade check" to deployment tooling

I was going through some recently reported nova bugs and came across [1] which I opened at the Summit during one of the FFU sessions where I realized the nova upgrade docs don't mention the nova-status upgrade check CLI [2] (added in Ocata). As a result, I was wondering how many deployment too

Re: [Openstack-operators] large high-performance ephemeral storage

fio is fine with me. I'll lazily defer to your expertise on the right fio commands to run for each case. :) If we're going to test within the guest, that's going to introduce a new set of variables, right? Should we settle on a standard flavor (maybe two if we wanted to include both virtio and vir

Re: [Openstack-operators] large high-performance ephemeral storage

Hey Joe, Thanks! So shall we settle on fio as a standard IO micro benchmarking tool? Seems to me the minimum we want is throughput and IOPs oriented tests for both the guest OS workload profile and the some sort of large working set application workload. For the latter it is probably best to ignor

Re: [Openstack-operators] large high-performance ephemeral storage

Lol! Ok, forgive me, I wasn't sure if I had regular or existential Jay on the line :-). On Thu., 14 Jun. 2018, 00:24 Jay Pipes, wrote: > On 06/13/2018 10:18 AM, Blair Bethwaite wrote: > > Hi Jay, > > > > Ha, I'm sure there's some wisdom hidden behind the trolling here? > > I wasn't trolling at a

Re: [Openstack-operators] large high-performance ephemeral storage

Yes, you can! The kernel documentation for read/write limits actually uses /dev/null in the examples :) But more seriously: while we have not architected specifically for high performance, for the past few years, we have used a zpool of cheap spindle disks and 1-2 SSD disks for caching. We have ZF

Re: [Openstack-operators] large high-performance ephemeral storage

On 06/13/2018 10:18 AM, Blair Bethwaite wrote: Hi Jay, Ha, I'm sure there's some wisdom hidden behind the trolling here? I wasn't trolling at all. I was trying to be funny. Attempt failed I guess :) Best, -jay ___ OpenStack-operators mailing list

Re: [Openstack-operators] large high-performance ephemeral storage

Hi Jay, Ha, I'm sure there's some wisdom hidden behind the trolling here? Believe me, I have tried to push these sorts of use-cases toward volume or share storage, but in the research/science domain there is often more accessible funding available to throw at infrastructure stop-gaps than softwar

Re: [Openstack-operators] large high-performance ephemeral storage

On 06/13/2018 09:58 AM, Blair Bethwaite wrote: Hi all, Wondering if anyone can share experience with architecting Nova KVM boxes for large capacity high-performance storage? We have some particular use-cases that want both high-IOPs and large capacity local storage. In the past we have used

[Openstack-operators] large high-performance ephemeral storage

Hi all, Wondering if anyone can share experience with architecting Nova KVM boxes for large capacity high-performance storage? We have some particular use-cases that want both high-IOPs and large capacity local storage. In the past we have used bcache with an SSD based RAID0 write-through caching

[Openstack-operators] Neutron not adding iptables rules for metadata agent

Hi all, So, I'm having the following issue. I'm creating a VM with floating IP. Everything is fine, namespace is there, postrouting and prerouting from the internal IP to the floating IP are there. The only rules missing are the rules to access metadata service: -A neutron-l3-agent-PREROUTING

[Openstack-operators] [openstack-ansible] Restarting our very own "SIG" teams

Hello, TL:DR; If you have spare cycles, join one of our interest groups! In the Queens cycle, I have formalised the "liaisons" work, making them an integral part of the Thursday's meeting agenda. Sadly, that initiative didn't work, as almost no liaison worked/reported on those meetings, and I sto

[Openstack-operators] openstack ocata gnocchi statsd errors

Hello everyone, I installed centos 7 openstack ocata with gnocchi. The gnocchi backand is "file" and /var/lib/gnocchi is on netapp nfs. Sometime a lot of locks are created on nfs and the statsd.log reports the following: 2018-03-05 08:56:34.743 58931 ERROR trollius [-] Exception in callback _flush