Re: [openstack-dev] [Globalization] REST API sorting by status severity vs. alphabetical status key

2014-04-28 Thread Steven Kaufer
ompleted or the old string column if the migration has not completed). Thanks, Steven Kaufer Jay Pipes wrote on 04/28/2014 09:05:51 AM: > From: Jay Pipes > To: openstack-dev@lists.openstack.org, > Date: 04/28/2014 09:07 AM > Subject: Re: [openstack-dev] [Globalization] REST API sort

Re: [openstack-dev] [Globalization] REST API sorting by status severity vs. alphabetical status key

2014-04-28 Thread Jay Pipes
On Wed, 2014-04-23 at 22:07 -0500, Steven Kaufer wrote: > > yeah, we're talking about thousands and thousands of rows that have > to > > be updated before the API can be restarted… > > > > > There's also a possibility of adding support for the status codes, > but > > > keeping the string columns i

Re: [openstack-dev] [Globalization] REST API sorting by status severity vs. alphabetical status key

2014-04-23 Thread Steven Kaufer
> yeah, we're talking about thousands and thousands of rows that have to > be updated before the API can be restarted… > > > There's also a possibility of adding support for the status codes, but > > keeping the string columns in the database, and then using the nova > > object versioning to "migra

Re: [openstack-dev] [Globalization] REST API sorting by status severity vs. alphabetical status key

2014-04-23 Thread Kevin L. Mitchell
On Wed, 2014-04-23 at 18:28 -0400, Jay Pipes wrote: > Worth it, IMO :) yeah, we're talking about thousands and thousands of rows that have to be updated before the API can be restarted… > There's also a possibility of adding support for the status codes, but > keeping the string columns in the da

Re: [openstack-dev] [Globalization] REST API sorting by status severity vs. alphabetical status key

2014-04-23 Thread Jay Pipes
On Wed, 2014-04-23 at 17:19 -0500, Kevin L. Mitchell wrote: > On Wed, 2014-04-23 at 15:29 -0500, Steven Kaufer wrote: > > Thanks for the reply. I agree that changing the datamodel would be > > the ideal solution. But, to be honest, the scope of that change > > frightens me. > > > > How would you

Re: [openstack-dev] [Globalization] REST API sorting by status severity vs. alphabetical status key

2014-04-23 Thread Kevin L. Mitchell
On Wed, 2014-04-23 at 15:29 -0500, Steven Kaufer wrote: > Thanks for the reply. I agree that changing the datamodel would be > the ideal solution. But, to be honest, the scope of that change > frightens me. > > How would you recommend that a change like this would be handled (in > addition to th

Re: [openstack-dev] [Globalization] REST API sorting by status severity vs. alphabetical status key

2014-04-23 Thread Steven Kaufer
gt; To: openstack-dev@lists.openstack.org, > Date: 04/23/2014 02:56 PM > Subject: Re: [openstack-dev] [Globalization] REST API sorting by > status severity vs. alphabetical status key > > Hi Steven, thx for the detailed email. Some comments inline... > > On Wed, 2014-04-23 at 13:59

Re: [openstack-dev] [Globalization] REST API sorting by status severity vs. alphabetical status key

2014-04-23 Thread Jay Pipes
Hi Steven, thx for the detailed email. Some comments inline... On Wed, 2014-04-23 at 13:59 -0500, Steven Kaufer wrote: > I am trying to address the following use case: > > - Assume that the REST APIs support returning data based on a > user-defined sort key (assuming that this get approved: > ht

[openstack-dev] [Globalization] REST API sorting by status severity vs. alphabetical status key

2014-04-23 Thread Steven Kaufer
I am trying to address the following use case: - Assume that the REST APIs support returning data based on a user-defined sort key (assuming that this get approved: https://review.openstack.org/#/c/84451/) - UI contains a table showing items (servers, volumes, etc.) and their status (as a sortab