[Pulp-list] Developers: Action Required: The migration that pulp_rpm now has, and what it means for devs

[Lukas Zapletal]

Is this something only developers must do, or this is gonna be the
official way to upgrade Pulp from now on.

I am asking because I am curious what should be put into our Katello
migration script for the next release instead of plain and simple
"pulp-migrate".

THanks

On Thu, Nov 08, 2012 at 09:26:28AM -0500, Randy Barlow wrote:
> Good morning! The pulp_rpm project now has one migration, whereas it
> had no migration module at all before. If you are a developer and
> you wish to apply this migration, you will need to take the
> following steps:
> 
> 1) $ pulp-manage-db
> 
> 2) $ mongo pulp_database
> 
> 3) > db.migration_trackers.update({'name': 'pulp_rpm.migrations'},
> {'$set': {'version': 0}})
> 
> 4) $ pulp-manage-db
> 
> That should set you straight, and you should never have to do that
> again for the pulp_rpm project.
> 
> We need to do this because the DB management script doesn't apply
> migrations to new installs, but instead does a "fast-forward" to the
> latest available version. From that point onward, any new migrations
> would be applied by the script. Because the pulp_rpm project didn't
> have migrations before and now does, it appears to be a "new
> install" to the management script, so it will auto fast-forward your
> DB.
> 
> To mitigate this problem, I suggest we go ahead at set up a
> migration entry point for the pulp_puppet project with no migrations
> in it. If we do this and everyone runs pulp-manage-db while it's in
> that state, the version 0 will be stored in everyone's DB and we
> won't have to do this same process for that project. Sound good?
> 
> -- 
> Randy Barlow
> 
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list

-- 
Later,

 Lukas "lzap" Zapletal
 #katello #systemengine