On 8/3/2016 11:47 AM, Jonathan D. Proulx wrote:
Hi All,
As a private cloud operatior who doesn't charge internal users, I'd
really like a way to force users to set an exiration time on their
instances so if they forget about them they go away.
I'd though Blazar was the thing to look at and
Hello,
we are doing the upgrade Kilo to Liberty pet by pet.
We already upgraded successfully Keystone and Glance.
Now I started the Nova pet upgrade. For the controller node it was ok.
As soon as I upgraded the compute nodes I had a problem with neutron.
I can't lock the
there are fundamental longevity of life questions with SSDs and tuning.
I'd be interested in hearing about that as well.
On Fri, Aug 5, 2016 at 11:23 AM, Edgar Magana
wrote:
> Tim,
>
>
>
> At Workday team we are working on that, our work is for CEPH performance.
>
On Fri, Aug 05, 2016 at 12:09:50PM +, kostiantyn.volenbovs...@swisscom.com
wrote:
> 3) The question of cfq vs. deadline vs. noop scheduler (apparently both
> in guest and host) where decision should be based on
> workloads/recommendations of OS vendor (/which again might be
>
Tim,
At Workday team we are working on that, our work is for CEPH performance.
Basically, moving janitor and cache to the SSD while we have backend
replication in HDD.
Still way too early for formal report but remind me in a couple of months.
Edgar
From: Tim Bell
Date:
Hi,
I think that https://wiki.mikejung.biz/KVM_/_Xen might be quite useful
Pretty much there won’t be a universal recipe but rather combination of what
are kernel/QEMU/OpenStack… versions
and implementation choices that were made
-Guest OS/host OS kernel version
-QEMU version
-OpenStack release.
Has anyone a good recipe for improving I/O performance when the hypervisor has
SSDs ?
The configuration is CentOS 7 for guest and hypervisor with KVM.
Tim
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org