Re: [Openstack] Pike: cinder-volume causes high CPU load (Ceph backend)

Hi Arne, thanks for your answer. I have to admit i screwed it up myself: i built a backup system this week and mixed up Cinder versions, in version 11.0.1 the problem seems to be definitely fixed, no need for manual intervention. matthias Am 2017-11-17 um 15:16 schrieb Arne Wiebalck: Hi Ma

Re: [Openstack] Traits for filter

On 11/17/2017 01:09 AM, Ramu, MohanX wrote: Thank you Jay. I am trying to understand usage of custom traits is that I have a custom trait called "CUSTOM_ABC" which is associated with Resource Provider "Resource provider-1" , So I can launch the instance which is having flavor/image associated

[Openstack] TripleO Newton Installation Failure

Hi All, We are facing one strange problem in openstack overcloud deploy action. We are getting error in ironic-inspector.log as shown below. "Look up error: Could not find a node for attributes {'bmc_address': u'', 'mac': [u'52:54:00:44:3b:b8']}" Upon further troubleshoot we found that during in

Re: [Openstack] Pike: cinder-volume causes high CPU load (Ceph backend)

Hi Matthias, This may be https://bugs.launchpad.net/cinder/+bug/1704106. In our deployment it was necessary to disable the the gathering of the provisioning stats and we simply commented it out: #self._get_usage_info() in def _update_volume_stats(self) from cinder/volume/drivers/rbd.py HTH,

[Openstack] Pike: cinder-volume causes high CPU load (Ceph backend)

Hi, we are running a Cinder Pike instance with Ceph (luminous) backend for use with oVirt (not openstack). We are experiencing the "cinder-volume causes high CPU load" issue. In Cinder 11.0.0 we could successfully apply the fix mentioned in https://ask.openstack.org/en/question/110709/ocata-c

[Openstack] TripelO custom puppet manifest deployment failing - Exception - connect failed

Hi, While applying custom puppet manifest in post deployment section of tripleO, I am getting a "connect failed " error in deployment of this particular puppet manifest. As per puppet concept, one will face this error if server is not reachable on port 8140. I manually checked the connectivity a

Re: [Openstack] TripelO custom puppet manifest deployment failing - Exception - connect failed

I am following this doc Thanks & Regards, Shyam Biradar, Email: shyambiradarsgg...@gmail.com, Contact: +91 8600266938. On Fri, Nov