[Building Sakai] set up latest sakai-Kaltura tool for Dev environment without screw-up the production

[Liu, Peter]

Hi Aaron,

What I really means is that if I have run it on my dev box with kaltura.rootCategory=dev_sakai, it will not affect current running production, which is running the old Kaltura version.

Do I have a correct understanding there?

Thanks a lot!
Peter

-----Original Message-----
From: azeckoski at gmail.com [mailto:azeckoski at gmail.com] On Behalf Of Aaron Zeckoski
Sent: Wednesday, September 18, 2013 3:16 PM
To: Liu, Peter
Cc: sakai-dev at collab.sakaiproject.org
Subject: Re: set up latest sakai-Kaltura tool for Dev environment without screw-up the production

What you mentioned is correct. The migration is non-destructive in the sense that you can follow the instructions in the README and start it over and run it again if you like.

-AZ


On Wed, Sep 18, 2013 at 3:12 PM, Liu, Peter <peter.liu at yale.edu> wrote:
> Hi,
>
>
>
> We are looking into this latest Sakai-Kaltura tool (tag:20130812).  I 
> have noticed that it will requires a migration of KMC database (automatically).
>
>
>
> At Yale, we have shared one kaltura.partnerid with dev, test, and prod
> servers/clusters environment.   I would like to make sure what I need to do
> is just to assign the kaltura.rootCategory to the following different 
> value without causing issue on KMC side:
>
>
>
> -Dev environment:
>
>   kaltura.rootCategory=dev_sakai
>
>
>
> -Test environment:
>
>   kaltura.rootCategory=test_sakai
>
>
>
> -Prod environment:
>
>   kaltura.rootCategory=prod_sakai
>
>
>
>
>
> Is this correct?  I really don’t want with messing up with the 
> production data on KMC side.
>
>
>
> Has anyone already done this?  Any feedback will be highly appreciated.
>
>
>
> Thanks a lot!
>
> Peter Liu



--
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile