Migration from 0.32 to 1.3.0

[george1421]

I guess the question to ask here is how many registered hosts are we talking about from the 0.32 install? Depending on the scope the answer may be different than below.

Since there is such a big jump, it would be my opinion to just create a new install of the 1.2.0 trunk, copy the images over to the new server and then recreate the image entries by hand in the new server.

[jburleson]

@george1421 About 500 hosts. I am not sure what you are suggesting here is on topic since the post is about the Host Service Settings and Group Membership and not the images.

[george1421]

@jburleson In a way it is and it isn’t (off point). The upgrade is filled with potential issues. The question would be is it quicker to fix your current upgrade or to just create a new install and then manually (or import) the necessary information into the new build. Its akin to upgrading windows between releases vs a clean install (but the clean install makes you install all of the software again too). So the question is what would be better for YOUR company in the long run. I’m wondering if FOG Project should even support upgrading more than 2 revs back, just because the database has changed so much.

With 500 hosts I might consider sticking with the upgrade and working through the issues.

[Tom Elliott]

@jburleson the nice part is that, unless every host had very pin pointed service settings that must be maintained, you can just join all the hosts into groups, yes again, and apply settings that way.

[jburleson]

As I mentioned in the original post, I already fixed my issues.

My original question still remains, does something need to be mentioned on the migration wiki page about this or was it just a one off issue. If it is not an isolated issue, I think it is appropriate to let people know that they will need to setup their groups again as well as the host service settings.

[Tom Elliott]

@jburleson It’s not a problem, at least not one that I’m aware of. There are quite significant changes, but we should be all right. I’ll test with your DB and see if I can replicate the problem.

[Sebastian Roth]

@Tom-Elliott Interesting post. Did you find the time to try it out? Do you have the DB dump in question?

[Tom Elliott]

@Sebastian-Roth I have the dump, but testing was near impossible. It was “sanitized” of the original information such as the user password and ip information. It wouldn’t allow me to communicate with the db any further.

[Wayne Workman]

@jburleson Could you get Tom a non-sanitized db? He is trustworthy. All of our @Senior-Developers are trustworthy.

[jburleson]

@Wayne-Workman Yeah, give me a minute to fire up the old vm and I will generate a new dump. I have finished the migration and have changed all the passwords so that is no longer an issue. Can I still drop the history and user tracking data? There is almost 9 years worth and it makes the file around 70MB?

[Tom Elliott]

@jburleson Yes, please dump the irrelevant parts. The history, usertracking, and imaging logs aren’t really needed for me to try to replicate.

[Tom Elliott]

Never mind, I edited the file you originally sent me so I could actually use it.

[Tom Elliott]

Thanks for the file.

I have found and fixed both issues reported. 0.32->trunk (1.3 as well when it is released) will maintain proper group associations AND service settings for each host will be fixed as well.

[jburleson]

@Tom-Elliott I have to say, FOG has some of the speediest devs Y’all do great work. The migration from 0.32 to 1.3.0 was pretty straight forward and worked quited well. To be honest, I had expected more issues since I made such a big jump in versions but they were minor and easy to fix. This is a testament to how dedicated the FOG team and community are to this project.

For anyone still running 0.32 (if I was not the last hold out), the migration is straight forward. Follow the directions on the wiki and you will be up and running in no time.

Thanks for the help everyone.