Re: [Openstack-operators] [Large deployment] Meetings

2015-01-29 Thread Tim Bell
The spec for quotas in Nova for hierarchical multitenancy was accepted for Kilo (https://review.openstack.org/#/c/129420/) and the code has now been dropped (https://review.openstack.org/#/c/149828/). Bit more polishing to do but hopeful it can make Kilo. Tim From: Matt Van Winkle [mailto:mvan

Re: [Openstack-operators] [openstack-dev] [all][log] Openstack HTTP error codes

2015-01-29 Thread Rochelle Grober
Hi folks! Changed the tags a bit because this is a discussion for all projects and dovetails with logging rationalization/standards/ At the Paris summit, we had a number of session on logging that kept circling back to Error Codes. But, these codes would not be http codes, rather, as others h

Re: [Openstack-operators] [Large deployment] Meetings

2015-01-29 Thread Matt Van Winkle
Updated either pad for today's meeting - https://etherpad.openstack.org/p/Large-Deployment-Team-Meetings Please add to it if you would like to discuss anything specific. I'll see everyone online in a couple of hours. Full disclosure, I'm heading to a little league tryout for my son that "shoul

Re: [Openstack-operators] Deprecation of in tree EC2 API in Nova for Kilo release

2015-01-29 Thread Michael Still
On Thu, Jan 29, 2015 at 1:59 AM, Belmiro Moreira < moreira.belmiro.email.li...@gmail.com> wrote: > I completely agree with Tim and Daniel. > Also, deprecating nova EC2 API without having the community engaged with > the new stackforge “EC2 standalone service” can lead to a no EC2 support at > all.

Re: [Openstack-operators] Deprecation of in tree EC2 API in Nova for Kilo release

2015-01-29 Thread Michael Still
On Thu, Jan 29, 2015 at 2:37 AM, Daniel P. Berrange wrote: > On Wed, Jan 28, 2015 at 01:39:31PM -0800, Michael Still wrote: >> On Wed, Jan 28, 2015 at 12:38 PM, Tim Bell wrote: >> > There are currently 35% of openstack clouds from the survey using >> > this feature. I would therefore propose that

Re: [Openstack-operators] [all] SQL Schema Downgrades: A Good Idea?

2015-01-29 Thread Jesse Keating
On 1/29/15 11:26 AM, Morgan Fainberg wrote: I’m looking at the expectation that a downgrade is possible. Each time I look at the downgrades I feel that it doesn’t make sense to ever really perform a downgrade outside of a development environment. The potential for permanent loss of data / incons

Re: [Openstack-operators] Deprecation of in tree EC2 API in Nova for Kilo release

2015-01-29 Thread George Shuklin
On 01/28/2015 09:56 PM, Sean Dague wrote: The following review for Kilo deprecates the EC2 API in Nova - https://review.openstack.org/#/c/150929/ There are a number of reasons for this. The EC2 API has been slowly rotting in the Nova tree, never was highly tested, implements a substantially olde

Re: [Openstack-operators] Small openstack

2015-01-29 Thread George Shuklin
Hello. If we have two computes, and each is network node, that means both hosts a router. Let say we have two tenants with two instance and two compute hosts. Compute1-tenant1-instance1 compute2-tenant2-instance2 But neutron have no idea about this. Someone asks him 'put router to any l3-ag

Re: [Openstack-operators] [all] SQL Schema Downgrades: A Good Idea?

2015-01-29 Thread John Dewey
On Thursday, January 29, 2015 at 11:40 AM, Fischer, Matt wrote: > > From: Morgan Fainberg (mailto:morgan.fainb...@gmail.com)> > Date: Thursday, January 29, 2015 at 12:26 PM > To: openstack-operators (mailto:openstack-operators@lists.openstack.org)> > Subject: [Openstack-operators] [all] SQL Sch

Re: [Openstack-operators] [all] SQL Schema Downgrades: A Good Idea?

2015-01-29 Thread Fischer, Matt
From: Morgan Fainberg mailto:morgan.fainb...@gmail.com>> Date: Thursday, January 29, 2015 at 12:26 PM To: openstack-operators mailto:openstack-operators@lists.openstack.org>> Subject: [Openstack-operators] [all] SQL Schema Downgrades: A Good Idea? >From an operator perspective I wanted to get i

[Openstack-operators] [all] SQL Schema Downgrades: A Good Idea?

2015-01-29 Thread Morgan Fainberg
From an operator perspective I wanted to get input on the SQL Schema Downgrades. Today most projects (all?) provide a way to downgrade the SQL Schemas after you’ve upgraded. Example would be moving from Juno to Kilo and then back to Juno. There are some odd concepts when handling a SQL migration

Re: [Openstack-operators] [OpenStack-docs] [Openstack-docs] High Availability Guide team

2015-01-29 Thread Sriram Subramanian
As far as I know, yes. I might be little late though. My agenda is to triage the open bugs and possible assignment of bugs. On 28 Jan, 2015 10:59 pm, "Nick Chase" wrote: > Hey, all -- > > Are we doing the HA Guide meeting today (Thursday)? > > Nick > > On 10/15/2014 6:55 PM, David Medberr

Re: [Openstack-operators] Deprecation of in tree EC2 API in Nova for Kilo release

2015-01-29 Thread Daniel P. Berrange
On Wed, Jan 28, 2015 at 01:39:31PM -0800, Michael Still wrote: > On Wed, Jan 28, 2015 at 12:38 PM, Tim Bell wrote: > > There are currently 35% of openstack clouds from the survey using > > this feature. I would therefore propose that this be reviewed with > > the operators in detail before a rapid

Re: [Openstack-operators] Deprecation of in tree EC2 API in Nova for Kilo release

2015-01-29 Thread Belmiro Moreira
I completely agree with Tim and Daniel. Also, deprecating nova EC2 API without having the community engaged with the new stackforge “EC2 standalone service” can lead to a no EC2 support at all. On Thu, Jan 29, 2015 at 4:46 AM, Saju M wrote: > I think, new EC2 API also uses EC2 API in the nova fo