Document migration path from Essex to Folsom

Bug #1043032 reported by Tom Fifield on 2012-08-29
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Alvaro Lopez

Bug Description

Tom Fifield (fifieldt) on 2012-08-29
Changed in openstack-manuals:
importance: Undecided → Critical
importance: Critical → High
status: New → Confirmed
milestone: none → folsom
Changed in openstack-manuals:
assignee: nobody → koolhead17 (koolhead17)
Anne Gentle (annegentle) wrote :

This page Vish wrote up should be useful:

Dave Spano (dspano) wrote :

Should make a note that the migration tool does not work with postgresql.

I get this error when running cinder-manage migrate
Sorry, only mysql backups are supported!

koolhead17 (koolhead17) on 2012-12-05
Changed in openstack-manuals:
assignee: koolhead17 (koolhead17) → nobody
Alvaro Lopez (aloga) on 2013-01-21
Changed in openstack-manuals:
assignee: nobody → Alvaro Lopez (aloga)

Fix proposed to branch: master

Changed in openstack-manuals:
status: Confirmed → In Progress

Submitter: Jenkins
Branch: master

commit 380c7c6979e78fd4f15616b015a342d7960af986
Author: Alvaro Lopez Garcia <email address hidden>
Date: Mon Jan 21 16:04:37 2013 +0100

    Added upgrade process from Essex to Folsom.

    It covers Keystone, Glance, Nova and nova-volume to Cinder upgrade,
    but lacks nova-network to Quantum.

    Patchset does minor style and spelling fixes.

    Making sure that the style fixes get in too by testing the merge.
    Sorry about the lack of "git add" on my part with the file rename.

    bug #1043032

    Change-Id: I57b351a83ab00eb13871e7780e320c09e31482d9

Changed in openstack-manuals:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers