Hi Romain,The v2 migration code introduced will enable future v2 cartridge migrations. But it is not intended to be used for v1 -> v2 migrations.ThanksKrishnaOn Jul 1, 2013, at 5:52 AM, Romain <filirom1 gmail com> wrote:Hi,Is [oo-admin-upgrade](https://github.com/openshift/origin-server/blob/master/broker-util/oo-admin-upgrade) in master going to be of some help ?In this case we should wait for this script to be released in the nighlies RPM.Romain2013/6/26 Romain <filirom1 gmail com>
Yes my username is filirom12013/6/25 Krishna Raman <kraman gmail com>
Hi Romain,Do you have a Trello account? Would like to add you to this card https://trello.com/card/documenting-v1-v2-cartridge-migration/51436ccc2473983151000299/17so that we can track progress.Thanks--krOn Jun 21, 2013, at 8:47 AM, Romain <filirom1 gmail com> wrote:Hi Diego,Now the weekend begin for me, but on tuesday I could take a look on nodejs migration from v1 to v2.Let me know if there are some special things to be aware of before begining.CheersRomain2013/6/21 Krishna Raman <kraman gmail com>
Hi Romain, Diego,
I wanted to put you two in touch with each other. Thanks for helping with the documentation/scripting of v1->v2 migration.
The difference between v1 and v2 versions of each cartridge mainly container changes in directory structure and a few
config changes. I would suggest creating a v1 and a v2 version of each cartridge and performing a diff to see the changes.
Origin release 1 defaults to v1 cartridges and latest code on master is v2. You can use vagrant to spin up a machine.
You may have to disable selinux for now. Im working with Dan Walsh to get a bug fixed in the selinux policy which
prevents creation of gears.
Let me know if I can do anything to expedite.
Thanks again for your help