DB needed for control but some clouds store tokens in sql as well as
locally-defined users. Don't forget analytics and if you use things like
contrail, you have cassandra/mongodb for peripheral services as well.
We're continuing to iterate through the requirements against current
reality - I appre
Database only needed for control operations. During upgrade we disable API
(mark down on LB or take them down). This will prevent users from making any
database changes.
After that flow is "simple"- backup db - do a migration- perform your
validation tests
If all good, bring up your api, if not
On 10 March 2016 at 19:26, Yuriy Brodskiy wrote:
> building a new cloud is not practical for real production environments.
> even if you can afford it, how do you migrate data?
>
> We have been doing upgrades for a while now, and came up with few basic
> principles:
> 1) you don't have to upgrade
building a new cloud is not practical for real production environments.
even if you can afford it, how do you migrate data?
We have been doing upgrades for a while now, and came up with few basic
principles:
1) you don't have to upgrade all at the same time. do it component at the
time
2) stand up
Shameless plug :)
For people currently running a distro but wanting to run CI, please
checkout StackBuffet (https://aptira.com/stackbuffet/)
Currently under beta, looking for customers with real use cases to help us
test
regards,
Kavit
*Kavit Munshi*
*Aptira - Asia Pacific’s leading provider
I have to agree, unless you start with CI/CD as your deployment model,
you're going to be doing full upgrades. And be aware that at least one
package model will overwrite your carefully crafted config files if you
choose the wrong option. Having tried an upgrade to a system in the middle
of an up
- In-place Full Release upgrades (upgrade an entire cloud from Icehouse
to Kilo for instance)
This tends to be the most likely scenario with CI/CD being almost
impossible for anyone using supported openstack components ( such as SDN /
NAS / other hardware integration pieces ).
That's not to
Hey all,
So I've been discussing cloud design with the team and of course the topic
comes up about how upgrades will be handled.
Handling OpenStack code updates generally consists of three paths in my
experience:
- CI/CD (continuous incremental upgrades)
- In-place Full Release upgrades (u
