graphite-dev team mailing list archive

[Denis Zhdanov <question692978@xxxxxxxxxxxxxxxxxxxxx>]

Question #692978 on Graphite changed:
https://answers.launchpad.net/graphite/+question/692978

Denis Zhdanov posted a new comment:
I would say it's not only Graphite but Django problem. 0.9.15 was probably running on Django 1.4, and you're trying running 1.1.7 on 3.0.x (?), It's jumping over 2 major Django and 2 major Graphite versions - quite bold move IMO, over 8 years of changes!
(e.g. Django even recommeding not jumping even over feature releases).

Sorry, but I can't give you any recommendations. I would say minimally
viable upgrade path will look like:

0.9.15 -> 1.0.0 / django 1.4 -> 1.9.13  / python 2.7
1.0.0 -> 1.1.0 / django 1.9.13 -> 1.11.29 / python 3
1.1.0 -> 1.1.7 / django 1.11.29 -> 2.0.13 -> 2.1.15 -> 2.2.16 -> 3.0.10 / python 3

but I can't give you any guarantees that will work. Mabe you can cut some corners with Django upgrade and do 1.11 -> 3.0.10.
Maybe you can do test it on VM first.
Or export useful data from old DB and reimport it in new DB directly.

-- 
You received this question notification because your team graphite-dev
is an answer contact for Graphite.