Re: [openstack-dev] [heat] Rolling upgrades vs. duplication of prop data

On Thu, Jan 5, 2017 at 10:28 PM, Zane Bitter wrote: > On 05/01/17 11:41, Crag Wolfe wrote: > >> Hi, >> >> I have a patch[1] to support the de-duplication of resource properties >> data between events and resources. In the ideal rolling-upgrade world, >> we would be writing

Re: [openstack-dev] [heat] Rolling upgrades vs. duplication of prop data

On 05/01/17 11:41, Crag Wolfe wrote: Hi, I have a patch[1] to support the de-duplication of resource properties data between events and resources. In the ideal rolling-upgrade world, we would be writing data to the old and new db locations, only reading from the old in the first release (let's

[openstack-dev] [heat] Rolling upgrades vs. duplication of prop data

Hi, I have a patch[1] to support the de-duplication of resource properties data between events and resources. In the ideal rolling-upgrade world, we would be writing data to the old and new db locations, only reading from the old in the first release (let's assume Ocata). The problem is that in

Re: [openstack-dev] [heat] Rolling Upgrades

On 10/21/2016 11:57 PM, Zane Bitter wrote: > On 21/10/16 08:37, Michał Dulko wrote: >>> > Finally, a note about Oslo versioned objects: they don't really help >>> > us. They work great for nova where there is just nova-conductor >>> > reading and writing to the DB, but we have multiple

Re: [openstack-dev] [heat] Rolling Upgrades

> From: Crag Wolfe [mailto:cwo...@redhat.com] > > On 10/20/2016 09:30 PM, Rabi Mishra wrote: > > Thanks Crag on starting the thread. Few comments inline. > > ... > > > > For RPC changes, we don't have a great solution right now (looking > > specifically at heat/engine/service.py). If we

Re: [openstack-dev] [heat] Rolling Upgrades

On 10/21/2016 11:25 AM, Crag Wolfe wrote: > Another edge case is that if only the first h-engine is upgraded during > a rolling upgrade and the operator waits awhile before upgrading the > other h-engines, we'll have a case where we are not distributing newer > rpc calls as much as we'd like.

Re: [openstack-dev] [heat] Rolling Upgrades

On 21/10/16 08:37, Michał Dulko wrote: > Finally, a note about Oslo versioned objects: they don't really help > us. They work great for nova where there is just nova-conductor > reading and writing to the DB, but we have multiple heat-engines doing > that that need to be restarted in a rolling

Re: [openstack-dev] [heat] Rolling Upgrades

On 20/10/16 20:02, Crag Wolfe wrote: AFAIK, only sqlalchemy+mariadb is being used in production I believe there are people using Postgres in production, or at least there were at one point. - ZB __ OpenStack

Re: [openstack-dev] [heat] Rolling Upgrades

On 10/20/2016 09:30 PM, Rabi Mishra wrote: > Thanks Crag on starting the thread. Few comments inline. > Happy to get it started. Thanks for the comments. > On Fri, Oct 21, 2016 at 5:32 AM, Crag Wolfe > wrote: > > At Summit, folks will be

Re: [openstack-dev] [heat] Rolling Upgrades

On 10/21/2016 02:02 AM, Crag Wolfe wrote: > At Summit, folks will be discussing the rolling upgrade issue across a > couple of sessions. I personally won't be able to attend, but thought > I would share my thoughts on the subject. > > To handle rolling upgrades, there are two general cases to

Re: [openstack-dev] [heat] Rolling Upgrades

Thanks Crag on starting the thread. Few comments inline. On Fri, Oct 21, 2016 at 5:32 AM, Crag Wolfe wrote: > At Summit, folks will be discussing the rolling upgrade issue across a > couple of sessions. I personally won't be able to attend, but thought > I would share my

[openstack-dev] [heat] Rolling Upgrades

At Summit, folks will be discussing the rolling upgrade issue across a couple of sessions. I personally won't be able to attend, but thought I would share my thoughts on the subject. To handle rolling upgrades, there are two general cases to consider: database model changes and RPC method