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

2015-01-30 Thread Jesse Keating
On 1/30/15 1:33 PM, Everett Toews wrote: Once I have the token from Keystone, I’ll be talking directly to the services. So either something goes wrong with Keystone and I get no token or I get a token and talk directly to a service. Either way a client knows who it's talking to. That's only tru

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

2015-01-30 Thread Kris G. Lindgren
You are splitting hairs here... If I was talking to nova about a vm but nova was having an issue communicating to neutron to get the vm network/ip details it would be helpful to know the error happened in neutron vs's a generic 500 error. Or if I ask nova to give me an image list (or snapshot crea

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

2015-01-30 Thread Everett Toews
On Jan 30, 2015, at 3:17 PM, Jesse Keating wrote: > On 1/30/15 1:08 PM, Everett Toews wrote: >> Project: A client dealing with the API already knows what project >> (service) they’re dealing with. Including this in an API error message >> would be redundant. That’s not necessarily so bad and it c

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

2015-01-30 Thread Jesse Keating
On 1/30/15 1:08 PM, Everett Toews wrote: Project: A client dealing with the API already knows what project (service) they’re dealing with. Including this in an API error message would be redundant. That’s not necessarily so bad and it could actually be convenient for client logging purposes to ha

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

2015-01-30 Thread Everett Toews
On Jan 29, 2015, at 7:34 PM, Rochelle Grober mailto:rochelle.gro...@huawei.com>> wrote: 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 circ

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

2015-01-30 Thread Jesse Keating
On 1/30/15 11:37 AM, Tim Bell wrote: Any ideas how are the online upgrade teams looking to address this ? Not an easy problem to solve. The direction is additive migrations. Create new columns and tables for new place for the data, but support pulling data from old locations as well. Once al

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

2015-01-30 Thread Tim Bell
> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: 30 January 2015 20:15 > To: openstack-operators@lists.openstack.org > Subject: Re: [Openstack-operators] [all] SQL Schema Downgrades: A Good Idea? > > Great topic, Morgan. Coments inline. > > On 01/29/2015 11:26 AM

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

2015-01-30 Thread Jonathan Proulx
I had the misfortune of doing an in production roll back, grizzly->havana->grizzly I think, though thankfuly before anything new had occurred after upgrade... Restore from DB dump is what I did and what I'd do again. For all reasons previously stated programatic reverse migration just doesn't make

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

2015-01-30 Thread Jay Pipes
Great topic, Morgan. Coments inline. On 01/29/2015 11:26 AM, Morgan Fainberg wrote: 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

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

2015-01-30 Thread Mike Dorman
Awesome, thanks for this update Tim! From: Tim Bell mailto:tim.b...@cern.ch>> Date: Friday, January 30, 2015 at 12:30 AM To: OpenStack Operators mailto:openstack-operators@lists.openstack.org>> Subject: Re: [Openstack-operators] [Large deployment] Meetings The spec for quotas in Nova for hierar

Re: [Openstack-operators] [nova][libvirt] RFC: ensuring live migration ends

2015-01-30 Thread David Medberry
Hi Daniel. Just a quick head's up that I'm very interested in this and taking a look. Thanks for taking an interest in this. I have seen l-m take 45-60 minutes (for lots of RAM, fairly active VMs.). I'll give more feedback this weekend when I have a chance to look at this in detail. On Fri, Jan 30

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

2015-01-30 Thread Eric Windisch
> > > That's a failing of the Nova team that must be addressed. As maintainers > it is our job to produce software that meets the needs of our users. We > have 35% of users reporting they use this EC2 code, so fixing any problems > should be a high priority item & these bugs considered release bloc

[Openstack-operators] [nova][libvirt] RFC: ensuring live migration ends

2015-01-30 Thread Daniel P. Berrange
In working on a recent Nova migration bug https://bugs.launchpad.net/nova/+bug/1414065 I had cause to refactor the way the nova libvirt driver monitors live migration completion/failure/progress. This refactor has opened the door for doing more intelligent active management of the live migratio

[Openstack-operators] OpenStack Community Weekly Newsletter (Jan 23 - 30)

2015-01-30 Thread Stefano Maffulli
Working to bridge the developer/end-user divide in OpenStack The Product Working Group will embark on a listening campaign to improve dialogue between developers and their managers. How to craft a successful OpenStack Summit proposal Inspiration, tips and a kick in the pants for the Feb. 9 dead