[Openstack-operators] [openstack-operators][openstack-dev][Rally][HA-testing][multi-scenarios-load-gen] Proposal to change Rally input task format

Hi stackers, When we started Rally we have a just small idea to make some tool that generates load and measures performance. During almost 2 years a lot of changed in Rally, so now it's quite common testing framework that allows to cover various topics like: stress, load, volume, performance, neg

Re: [Openstack-operators] [openstack-dev] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

Wondering if heat should be performing this orchestration. Would provide for a more pluggable front end to the action set. -matt On Feb 25, 2015 2:37 PM, Joe Gordon wrote: > > > > On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell wrote: >> >> >> A few inline comments and a general point >> >> How do w

Re: [Openstack-operators] [openstack-dev] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell wrote: > > A few inline comments and a general point > > How do we handle scenarios like volumes when we have a per-component > janitor rather than a single co-ordinator ? > > To be clean, > > 1. nova should shutdown the instance > 2. nova should then ask

Re: [Openstack-operators] Managing pools of pre-allocated instances

On 2015-02-25 1:21 PM, James Penick wrote: Hey folks, I have a team that uses our OpenStack VM and BM clusters in their CI and CD environments (And yes, they really do need baremetal for some of their CI tests, unless I want to support gigantifriggenormous VM flavors). CI on baremetal works

Re: [Openstack-operators] Managing pools of pre-allocated instances

James Penick wrote: > Hey folks, > I have a team that uses our OpenStack VM and BM clusters in their CI > and CD environments (And yes, they really do need baremetal for some > of their CI tests, unless I want to support gigantifriggenormous VM > flavors). > > CI on baremetal works ok, however t

[Openstack-operators] Managing pools of pre-allocated instances

Hey folks, I have a team that uses our OpenStack VM and BM clusters in their CI and CD environments (And yes, they really do need baremetal for some of their CI tests, unless I want to support gigantifriggenormous VM flavors).   CI on baremetal works ok, however the time it takes to image the hos

Re: [Openstack-operators] qemu 1.x to 2.0

On 2015-02-24 2:25 PM, Joe Topjian wrote: Let me know if you have any more questions with this. :) Looks like I hit an other bug with live migration: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1425619 You can't migrate from QEMU 1.5 (UCA/Havana) to QEMU 2.0 (UCA/Icehouse). -- Mathi

Re: [Openstack-operators] Getting error shell-init: error retrieving current directory: getcwd: cannot access parent directories:

Thanks very much Edgar for your quick response, i will look into the links provided. many many thanks once again. On Wed, Feb 25, 2015 at 9:31 PM, Edgar Magana wrote: > Anwar, > > I have an installation guide that I validate a few weeks ago and I did > not run into any issues: > > https://gith

Re: [Openstack-operators] Getting error shell-init: error retrieving current directory: getcwd: cannot access parent directories:

Anwar, I have an installation guide that I validate a few weeks ago and I did not run into any issues: https://github.com/emagana/OpenStack-Icehouse-Install-Guide/blob/master/OpenStack-Icehouse-Installation.rst Review your steps and I hope you can get it work comparing with my instructions. You

[Openstack-operators] Getting error shell-init: error retrieving current directory: getcwd: cannot access parent directories:

Hello Team, I was setting up Icehouse installation on my centos 6.5 ( 64bit) Everything was fine up to image service installation, it was successfull, but the moment i start process to install Nova service on controller node : i have done following successfully 1. yum install openstack-n