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,
:59 GMT+03:00 Chris Sarginson <csarg...@gmail.com>:
> 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 <v...@
his bug[1] that seems
> to give off 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 <v...@prokofev.me&g
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
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