Re: [Openstack-operators] nova-api response time

2017-05-10 Thread Vladimir Prokofev
> > Have you taken into consideration the TCP setup connection into your > profiling? > > TCP’s slow start process, window size learning etc? > > I feel this could have considerable impact unless you have run few > thousand cycles to average out the time taken so that t

Re: [Openstack-operators] nova-api response time

2017-05-05 Thread Vladimir Prokofev
ctly tie to nova-api. [1] https://docs.openstack.org/developer/rally/overview/stories/keystone/authenticate.html 2017-05-05 13:38 GMT+03:00 Vladimir Prokofev : > Hello Ops. > > So I had a feeling that my Openstack API is running a bit slow, like it > takes a couple of seconds to get

[Openstack-operators] nova-api response time

2017-05-05 Thread Vladimir Prokofev
Hello Ops. So I had a feeling that my Openstack API is running a bit slow, like it takes a couple of seconds to get a full list of all instances in Horizon for example, which is kind of a lot for a basic MySQL select-and-present job. This got me wondering to how can I measure execution times and f

[Openstack-operators] Flavors

2017-03-15 Thread Vladimir Prokofev
A question of curiosity - why do we even need flavors? I do realise that we need a way to provide instance configuration, but why use such a rigid construction? Wouldn't it be more flexible to provide instance configuration as a set of parameters(metadata), and if you need some presets - well, use

Re: [Openstack-operators] live migration fails and libvirtd(?) lockup after trusty > xenial/mitaka > newton upgrade

2016-12-20 Thread Vladimir Prokofev
:59 GMT+03:00 Chris Sarginson : > Hi Vladimir, > > The packages are available on launchpad here: > https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg- > 5ubuntu10.5/+build/10938755 > > On Tue, 20 Dec 2016 at 12:49 Vladimir Prokofev wrote: > >> Using >> compu

Re: [Openstack-operators] live migration fails and libvirtd(?) lockup after trusty > xenial/mitaka > newton upgrade

2016-12-20 Thread Vladimir Prokofev
ff the same faults you are reporting and had to downgrade qemu > packages to version '1:2.5+dfsg-5ubuntu10.5' > > [1] https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1647389 > > On Tue, Dec 20, 2016 at 12:10 AM, Vladimir Prokofev wrote: > >> Hello Ops. >>

[Openstack-operators] live migration fails and libvirtd(?) lockup after trusty > xenial/mitaka > newton upgrade

2016-12-19 Thread Vladimir Prokofev
Hello Ops. I want to pick your brains on a live migration issue, cause I'm kinda stuck atm. I'm running a small HA Ubuntu Openstack cloud - 3 controllers(VMs on Ubuntu/KVM) with ha-proxy LB, corosync/pacemaker manages VIP, Galera DB, 3 compute nodes(using KVM hypervisor), 3 network nodes(VMs on U

Re: [Openstack-operators] Delete cinder service

2016-09-01 Thread Vladimir Prokofev
I've used direct database update to achive this in Mitaka: use cinder; update services set deleted = '1' where ; So far I didn't encounter any negative consequences of this method. 2016-09-01 16:06 GMT+03:00 William Josefsson : > Hi, > > I changed a hostname on my cinder node, and now I can see