I think we give it a try then, thank you :-)
Kind regards,
Michael
> Simon Leinen hat am 18. Juni 2016 um 16:21
> geschrieben:
>
>
> Michael Stang writes:
> > Is this one the actual guid for upgrades, and is it valid for every
> > upgrade or ony for specific versions?:
> > http://docs.openstack
Michael Stang writes:
> Is this one the actual guid for upgrades, and is it valid for every
> upgrade or ony for specific versions?:
> http://docs.openstack.org/ops-guide/ops_upgrades.html
Yes, that's part of the official Operations Guide. It is not
version-specific. The examples are based on Ub
Hello Saverio,
thank you for the link, I will have a look at this article.
In place upgrade would be the best way, becaus we do not have to setup
everything from scratch again, also at the moment it would be no problem to make
a new installation because there is not much data by now in our inst
> +1 to everything Daniel said. Nova really expects release-to-release
> upgrades. We do online data migrations between releases. Maybe one
> reason you're getting this to work is we have a nova-manage command to
> force the migration of data between releases rather than doing the
> online data mig
On 6/15/2016 10:30 AM, Daniel P. Berrange wrote:
On Wed, Jun 15, 2016 at 03:19:28PM +, Jesse Keating wrote:
I'll offer a counter point.
We're not doing Juno to Mitaka, however we are doing Kilo to Mitaka, skipping
over Liberty.
The database migrations to get from Kilo to Mitaka have ran sm
On Wed, Jun 15, 2016 at 03:19:28PM +, Jesse Keating wrote:
> I'll offer a counter point.
>
> We're not doing Juno to Mitaka, however we are doing Kilo to Mitaka, skipping
> over Liberty.
>
> The database migrations to get from Kilo to Mitaka have ran smoothly for us.
While it is great that
I'll offer a counter point.
We're not doing Juno to Mitaka, however we are doing Kilo to Mitaka, skipping over Liberty.
The database migrations to get from Kilo to Mitaka have ran smoothly for us.
https://github.com/blueboxgroup/ursula/blob/master/upgrade.yml
-jlk
- Original message -
a¹s, new options added.
From: Melvin Hillsman
Date: Wednesday, June 15, 2016 at 8:07 AM
To: Saverio Proto
Cc: OpenStack Operators
Subject: Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka
+1 on Saverio's response. You will want to upgrade to Mitaka by NOT
jumping releases; J
+1 on Saverio's response. You will want to upgrade to Mitaka by NOT jumping
releases; J - K - L - M not J - M
On Wed, Jun 15, 2016 at 4:13 AM, Saverio Proto wrote:
> Hello,
>
> first of all I suggest you read this article:
>
> http://superuser.openstack.org/articles/openstack-upgrading-tutorial-
Hello,
first of all I suggest you read this article:
http://superuser.openstack.org/articles/openstack-upgrading-tutorial-11-pitfalls-and-solutions
> What is the best way to performe an upgrade from Juno to Mitaka?
I would go for the in place upgrade, but I always upgraded without
jumping versio
Hi,
my name is Michael, I am working at the Baden-Wuerttemberg Cooperative State
University Mannheim.
We have an installation of OpenStack with roundabout 14 nodes each 32 cores (1
controller (glance,keystone, etc.), 1 neutron, 2 objectstores, 1 blockstore, 9
compute nodes) the blockstore, the
11 matches
Mail list logo
