On Thu, Apr 30, 2015 at 9:25 PM, Jastrzebski, Michal
michal.jastrzeb...@intel.com wrote:
Hello,
After discussions, we've spotted possible gap in versioned objects:
backporting of too-new versions in RPC.
Nova does that by conductor, but not every service has something like
that. I want to
W dniu 5/4/2015 o 8:21 AM, Angus Salkeld pisze: On Thu, Apr 30, 2015 at 9:25
PM, Jastrzebski, Michal
michal.jastrzeb...@intel.com mailto:michal.jastrzeb...@intel.com wrote:
Hello,
After discussions, we've spotted possible gap in versioned objects:
backporting of too-new
On Mon, May 4, 2015 at 6:33 PM, Jastrzebski, Michal
michal.jastrzeb...@intel.com wrote:
W dniu 5/4/2015 o 8:21 AM, Angus Salkeld pisze: On Thu, Apr 30, 2015 at
9:25 PM, Jastrzebski, Michal
michal.jastrzeb...@intel.com mailto:michal.jastrzeb...@intel.com
wrote:
Hello,
After
W dniu 5/4/2015 o 11:50 AM, Angus Salkeld pisze: On Mon, May 4, 2015 at 6:33
PM, Jastrzebski, Michal
michal.jastrzeb...@intel.com mailto:michal.jastrzeb...@intel.com wrote:
W dniu 5/4/2015 o 8:21 AM, Angus Salkeld pisze: On Thu, Apr 30,
2015 at 9:25 PM, Jastrzebski, Michal
Message-
From: Jastrzebski, Michal [mailto:michal.jastrzeb...@intel.com]
Sent: Monday, May 04, 2015 3:39 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [oslo][heat] Versioned objects backporting
W dniu 5/4/2015 o 11:50 AM, Angus Salkeld pisze: On Mon
Hello,
After discussions, we've spotted possible gap in versioned objects: backporting
of too-new versions in RPC.
Nova does that by conductor, but not every service has something like that. I
want to propose another approach:
1. Milestone pinning - we need to make single reference to versions
