Hi,
OVH is a new cloud provider for openstack-infra nodes:
http://www.openstack.org/blog/2015/12/announcing-a-new-cloud-provider-for-openstacks-ci-system-ovh/
It appears that selection of nodes on any cloud provider is a matter of
luck:
"When a developer uploads a proposed change to an
Regarding item #3:
I have mainly seen this issue on stacks that have been snapshotted:
https://bugs.launchpad.net/heat/+bug/1412965
In such cases, the only way to avoid (afaik) is for the owner to
manually delete the snapshots prior to deleting the stack. Heat tries
to auto-delete snapshots
On 12/09/2014 03:54 PM, Ken'ichi Ohmichi wrote:
Hi,
This case is always tested by Tempest on the gate.
https://github.com/openstack/tempest/blob/master/tempest/api/compute/servers/test_delete_server.py#L152
So I guess this problem wouldn't happen on the latest version at least.
Thanks
On 11/24/2014 09:40 AM, Ben Nemec wrote:
On 11/24/2014 08:50 AM, Matthew Gilliard wrote:
1/ assertFalse() vs assertEqual(x, False) - these are semantically
different because of python's notion of truthiness, so I don't think
we ought to make this a rule.
2/ expected/actual - incorrect failure
On 10/30/2014 03:30 PM, Abel Lopez wrote:
It seems that every release, there is more and more emphasis on upgradability.
This is a good thing, I've love to see production users easily go from old to
new.
As an operator, I've seen first hand the results of neglecting the databases
that
Shar,
Hi!
1) install git-review and set it up (poke around openstack docs)
2) after crafting your patch in a new branch (git branch
name-of-branch-you-are-working-on), commit the changes (git add -a),
craft a commit message, save it, and then type git review
If everything is correct, it
On 05/20/2014 10:07 AM, Jay Pipes wrote:
On 05/19/2014 02:32 PM, sridhar basam wrote:
On Mon, May 19, 2014 at 1:30 PM, Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
Stackers,
On Friday in Atlanta, I had the pleasure of moderating the database
session at the Ops
