On 06/08/15 08:20, Grasza, Grzegorz wrote:
-Original Message-
From: Zane Bitter [mailto:zbit...@redhat.com]
Sent: Thursday, 6 August, 2015 2:57
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Heat] RPC API versioning
We've been talking about this since before s
On 06/08/15 10:08, Dan Smith wrote:
This is, I believe, sufficient to solve our entire problem.
Specifically, we have no need for an indirection API that rebroadcasts
messages that are too new (since that can't happen with pinning) and no
need for Versioned Objects in the RPC layer. (Versioned ob
> This is, I believe, sufficient to solve our entire problem.
> Specifically, we have no need for an indirection API that rebroadcasts
> messages that are too new (since that can't happen with pinning) and no
> need for Versioned Objects in the RPC layer. (Versioned objects for the
> DB are still c
> -Original Message-
> From: Zane Bitter [mailto:zbit...@redhat.com]
> Sent: Thursday, 6 August, 2015 2:57
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [Heat] RPC API versioning
>
> We've been talking about this since before summit w
We've been talking about this since before summit without much
consensus. I think a large part of the problem is that very few people
have deep knowledge of both Heat and Versioned Objects. However, I think
we are at a point where we should be able to settle on an approach at
least for the API<
