Quantum DB migration

Bug #1099574 reported by Mark McClain
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Invalid
High
Unassigned

Bug Description

Documentation is needed to describe the database migration process from Quantum Folsom to Quantum Grizzly+.

Revision history for this message
Tom Fifield (fifieldt) wrote :
Tom Fifield (fifieldt)
Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → grizzly
dan wendlandt (danwent)
Changed in openstack-manuals:
importance: Medium → High
dan wendlandt (danwent)
Changed in openstack-manuals:
assignee: nobody → Mark McClain (markmcclain)
Revision history for this message
Tom Fifield (fifieldt) wrote :

Hi Mark,

Are you on this?

I have no idea where to start myself.

Anne Gentle (annegentle)
tags: added: neutron
removed: quantum
tags: added: quantum
Revision history for this message
Tom Fifield (fifieldt) wrote :

Hi Mark,

Are you still working on this?

Tom Fifield (fifieldt)
Changed in openstack-manuals:
milestone: grizzly → none
Revision history for this message
Tom Fifield (fifieldt) wrote :

de-assigning, as we have not heard from Mark in a while. If this was done in error, please feel free to reassign

Changed in openstack-manuals:
assignee: Mark McClain (markmcclain) → nobody
Stephen Gordon (sgordon)
Changed in openstack-manuals:
status: Confirmed → Incomplete
Revision history for this message
Edgar Magana (emagana) wrote :

I do not even believe this is needed any longer. Is anyone against marking this bug as "Invalid"

Tom Fifield (fifieldt)
Changed in openstack-manuals:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.