Perform Schema Rolling Upgrades in Just One Release Cycle
236 views · Published 25 October 2016 · 28:26 · Indexed 21 October 2026
Channel: OpenInfra Foundation · 2016 · Science & Technology
Reliable Openstack deployment should be as close to 100% availability as possible and always up to date with the latest release. To achieve this, during an upgrade services should be stopped and replaced with new one with no API downtime. In projects like keystone, glance or neutron this means keeping compatibility of DB schema between releases. The complexity of maintaining this compatibility, while keeping performance and security on a high level, is a hot topic in the community. Current appro
More from this channel
-
30:59
San Diego 2012 Keynotes: Mark Shuttleworth
-
39:42
Building an OpenStack Security Group
-
32:06
War Stories Moving from Eucalytups to OpenStack
-
41:41
Making clouds faster for fun and profit
-
36:25
Service Resiliency Doesnt always mean HA or cluster
-
41:18
Cloudifying Virtual Desktops
-
28:05
Red Hats Cloud Strategy
-
41:36
OpenStack its impact on the Enterprise and startup community