Migrations from Essex to Grizzly/Havana
...
I would find it entirely suitable to upgrade from Essex to Folsom, then
migrate from nova-volume to cinder and from nova-network to quantum, then
only to upgrade to Grizzly.
We're in the same spot, upgrading an Essex deployment to Havana. We
On 11/01/2013 11:02 AM, Dean Troyer wrote:
To clarify a bit, while deprecated, nova-network has not lost any
functionality in Havana yet. It also hasn't gained much (if any), but
it still works. The majority of the testing is performed using
nova-network and not neutron (yet).
It is also
On Thu, Oct 31, 2013 at 8:02 PM, Dean Troyer dtro...@gmail.com wrote:
Also, FWIW, I don't see another one of these situations coming anytime
soon. All of the new project activity is around new services/features.
Actually, anyone deploying nova with the baremetal driver will face a
similar
On Fri, Nov 1, 2013 at 1:38 PM, Devananda van der Veen
devananda@gmail.com wrote:
Actually, anyone deploying nova with the baremetal driver will face a
similar split when Ironic is included in the release. I'm targeting
Icehouse, but of course, it's up to the TC when Ironic graduates.
Hi everyone,
Migrations from Essex to Grizzly/Havana are starting to hit my radar of
responsible tasks and I'm disappointed that beyond this old wiki note [1]
and a wealth of questions with very few answers [2], there is very little
available to support the migrations from what used to be part of
Yes, OS as big product tries to split hierarchy of responsibilities.
Currently we have serveral tasks, i suppose.
First one is upgrading from one stable release to another.
Second one is migrating from one release to another.
Currently OpenStack has several deployment projects: TripleO, Fuel (---
On Thu, Oct 31, 2013 at 10:26 AM, Jesse Pretorius
jesse.pretor...@gmail.com wrote:
Hi everyone,
Migrations from Essex to Grizzly/Havana are starting to hit my radar of
responsible tasks and I'm disappointed that beyond this old wiki note [1]
Is your disappointment that there isn't a path from
On 10/31/2013 12:46 PM, John Griffith wrote:
Issues at hand, for now, are:
1) Migrating from nova-volume to cinder
So to be quite honest we never intended to make skips like you
describe. Perhaps that wasn't such a good choice in retrospect. I'm
willing to take a look at putting some
On 31 October 2013 18:46, John Griffith john.griff...@solidfire.com wrote:
Is your disappointment that there isn't a path from Essex --
Grizzly/Havana, or are you unhappy with the content?
Upgrading Essex-Folsom introduced both the challenge of upgrading
nova-volume to cinder and the
On 31 October 2013 19:05, Russell Bryant rbry...@redhat.com wrote:
Right, Nova (and probably other projects, too) only supports N to N+1
upgrades. If you need to go to N+2, you'll need to go through N+1 to
get there.
Dead right, and especially with the aggressive schedule we have this is
On Thu, Oct 31, 2013 at 2:18 PM, Jesse Pretorius
jesse.pretor...@gmail.comwrote:
On 31 October 2013 18:46, John Griffith john.griff...@solidfire.comwrote:
Upgrading Essex-Folsom introduced both the challenge of upgrading
nova-volume to cinder and the challenge of upgrading nova-network to
11 matches
Mail list logo
