[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Introductions and v2 migrations



Im in Mountain View, California. So UTC-7. How about Friday during or after community hour?

--kr

On Jul 11, 2013, at 2:40 PM, Diego Spinola Castro <spinolacastro gmail com> wrote:

> Thanks Romain, lets try sync all timezones. I'm at GMT -3. What about
> you and Krishna?
> 
> 2013/7/11 Romain <filirom1 gmail com>:
>> For the hangout, on Friday (tomorrow) or next week, as you prefer.
>> Your migration script is quite meticulous. Nice shot :)
>> 
>> 
>> 
>> 
>> 2013/7/10 Krishna Raman <kraman gmail com>
>>> 
>>> Hey Diego,
>>> 
>>> Let me know when you 2 are planning the hangout and I will try to join as
>>> well.
>>> 
>>> --kr
>>> 
>>> On Jul 10, 2013, at 12:12 PM, Diego Spinola Castro
>>> <spinolacastro gmail com> wrote:
>>> 
>>>> Hi Romain, i have a very first idea of migration, it worked very well
>>>> for php.
>>>> I'd like to propose a hangout to discuss better.
>>>> You can see what i've done
>>>> 
>>>> https://github.com/getupcloud/getup-utils/tree/master/cartridge-migration.
>>>> 
>>>> 2013/7/2 Romain <filirom1 gmail com>:
>>>>> Hi,
>>>>> 
>>>>> I have migrated php and nodejs applications on my openshift origin.
>>>>> 
>>>>> I released the scripts I used for that, but be aware that they are
>>>>> quite
>>>>> ugly and may not work for you.
>>>>> https://github.com/Filirom1/openshift-cartridge-migration-v1-to-v2
>>>>> 
>>>>> In the readme, I explained how I achieve the migration.
>>>>> 
>>>>> Cheers
>>>>> Romain
>>>>> 
>>>>> 
>>>>> 2013/7/1 Krishna Raman <kraman gmail com>
>>>>>> 
>>>>>> 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.
>>>>>> 
>>>>>> Thanks
>>>>>> Krishna
>>>>>> 
>>>>>> On 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.
>>>>>> 
>>>>>> Romain
>>>>>> 
>>>>>> 
>>>>>> 2013/6/26 Romain <filirom1 gmail com>
>>>>>>> 
>>>>>>> Yes my username is filirom1
>>>>>>> 
>>>>>>> 
>>>>>>> 2013/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/17
>>>>>>>> so that we can track progress.
>>>>>>>> 
>>>>>>>> Thanks
>>>>>>>> --kr
>>>>>>>> 
>>>>>>>> On 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.
>>>>>>>> 
>>>>>>>> Cheers
>>>>>>>> Romain
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 2013/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
>>>>>>>>> --Krishna
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> dev mailing list
>>>>> dev lists openshift redhat com
>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>>> 
>>> 
>> 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]