Excerpts from Zane Bitter's message of 2014-07-24 12:09:39 -0700:
On 17/07/14 07:51, Ryan Brown wrote:
On 07/17/2014 03:33 AM, Steven Hardy wrote:
On Thu, Jul 17, 2014 at 12:31:05AM -0400, Zane Bitter wrote:
On 16/07/14 23:48, Manickam, Kanagaraj wrote:
SNIP
*Resource*
Status
On 25/07/14 13:50, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-07-24 12:09:39 -0700:
On 17/07/14 07:51, Ryan Brown wrote:
On 07/17/2014 03:33 AM, Steven Hardy wrote:
On Thu, Jul 17, 2014 at 12:31:05AM -0400, Zane Bitter wrote:
On 16/07/14 23:48, Manickam, Kanagaraj wrote:
On 17/07/14 07:51, Ryan Brown wrote:
On 07/17/2014 03:33 AM, Steven Hardy wrote:
On Thu, Jul 17, 2014 at 12:31:05AM -0400, Zane Bitter wrote:
On 16/07/14 23:48, Manickam, Kanagaraj wrote:
SNIP
*Resource*
Status action should be enum of predefined status
+1
Rsrc_metadata - make full name
On Thu, Jul 17, 2014 at 12:31:05AM -0400, Zane Bitter wrote:
On 16/07/14 23:48, Manickam, Kanagaraj wrote:
I have gone thru the Heat Database and found the drawbacks in the
existing model as listed below. Could you review and add anything
missing here. Thanks.
Heat Database model is having
On 07/17/2014 03:33 AM, Steven Hardy wrote:
On Thu, Jul 17, 2014 at 12:31:05AM -0400, Zane Bitter wrote:
On 16/07/14 23:48, Manickam, Kanagaraj wrote:
SNIP
*Resource*
Status action should be enum of predefined status
+1
Rsrc_metadata - make full name resource_metadata
-0. I don't see
On Thu, 2014-07-17 at 08:51 -0400, Ryan Brown wrote:
On 07/17/2014 03:33 AM, Steven Hardy wrote:
On Thu, Jul 17, 2014 at 12:31:05AM -0400, Zane Bitter wrote:
On 16/07/14 23:48, Manickam, Kanagaraj wrote:
SNIP
*Resource*
Status action should be enum of predefined status
+1
Excerpts from Manickam, Kanagaraj's message of 2014-07-16 20:48:04 -0700:
Event
Why uuid and id both used?
The event uuid is the user-facing ID. However, we need to return events
to the user in insertion order. So we use an auto-increment primary key,
and order by that in 'heat event-list
I have gone thru the Heat Database and found the drawbacks in the existing
model as listed below. Could you review and add anything missing here. Thanks.
Heat Database model is having following drawbacks:
1. Duplicate information
2. Incomplete naming of columns
3.
On 16/07/14 23:48, Manickam, Kanagaraj wrote:
I have gone thru the Heat Database and found the drawbacks in the
existing model as listed below. Could you review and add anything
missing here. Thanks.
Heat Database model is having following drawbacks:
1.Duplicate information
2.Incomplete
Hi Zane,
Please find inline answer.
Regards
Kanagaraj M
-Original Message-
From: Zane Bitter [mailto:zbit...@redhat.com]
Sent: Thursday, July 17, 2014 10:01 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [heat]Heat Db Model updates
On 16/07/14 23:48, Manickam
10 matches
Mail list logo
