Hi Michael,
Thank you for sharing your code and for your great feedback.
I have created a wiki page [1] to give this thread more visibility.
A quick note for anyone interested in this migration: Michael's code can be
merged into 3.3.0_to_3.3.80.rb or 3.3.80_to_3.4.0.rb to skip the db_versioning
t
Hi,the following is a longer email, but I believe there are others also having the need to make a "smooth" upgrade from 3.2.x to 3.4Thanx again to Carlos to show me the right way, so how did we do the Migration of 3.2.1 to 3.4 having certain active VMs and not the chance to shut them down.Some back
Hello Carlos,
the mentioned way sounds reasonable and scriptable. I will do the upgrade in
the next
days and keep you informed about success - I will send the steps done to the
list.
Many thanx for your help,
Michael
Am 12.04.2012 um 16:26 schrieb Carlos Martín Sánchez:
> Hi Michael,
>
> T
Hi Michael,
The reason why VMs have to be shut down is because the storage model has
changed quite a bit in this last version, and we couldn't come up with a
migration process that felt solid enough for any deployment.
But, since you said you are ready for lots of manual work, let's try this:
Fi
Hello,
first of all congratulations to the final 3.4 and many thanx for the hard work!
I just wanted to upgrade to 3.4 and started reading.
I noticed reading the upgrade guide that all active VMs have to be shut down.
Is there any chance to upgrade without powering down all VMs? Even with lots
