Closed hongsudt closed 11 years ago
I added this to the 2.14 Milestone.
@hongsudt do you know what is currently running on this machine? What is the reason for the upgrade? John and I talked and we are just curious.
@joshuaselsky internal is running 2.12, which isn't really going to be a "supported" release, right? It currently only has outside users testing and taking a look around ohmage. previously had IMLab deployment. We are looking to keep it in line with supported versions... @hongsudt any other reasons I'm missing?
It is currently running 2.12 which we don't want to be using.. Upgrading it to 2.13 will allow us to use it for small/students pilots.. If it is not going to take a long time, I would rather upgrade it sooner so we have a usable server.
On Tue, Nov 13, 2012 at 11:44 AM, Joshua Selsky notifications@github.comwrote:
@hongsudt https://github.com/hongsudt do you know what is currently running on this machine? What is the reason for the upgrade? John and I talked and we are just curious.
— Reply to this email directly or view it on GitHubhttps://github.com/cens/ohmageServer/issues/450#issuecomment-10340486.
Can we trash the data on the machine?
No, IMLab data is still needed as far as I know..
NO... Hossein used the server to collect mobility and the students need that for analysis.
On Tue, Nov 13, 2012 at 11:51 AM, Joshua Selsky notifications@github.comwrote:
Can we trash the data on the machine?
— Reply to this email directly or view it on GitHubhttps://github.com/cens/ohmageServer/issues/450#issuecomment-10340754.
Got it. Do you have anyone that needs to use the machine right away?
Can we suggest that people use play.ohmage.org instead of internal? It seems that the two machines have the same purpose.
I am not aware of any that needs the server right away..
Faisal might start collecting data for his work soon, though I am not sure which server he is going to use. We might need it for Dara's cigarette pilot coming in in Jan.
On Tue, Nov 13, 2012 at 11:54 AM, Joshua Selsky notifications@github.comwrote:
Got it. Do you have anyone that needs to use the machine right away?
— Reply to this email directly or view it on GitHubhttps://github.com/cens/ohmageServer/issues/450#issuecomment-10340854.
@jojenki I think play is effectively "external".ohmage.org: does that make sense?
For new pilots, I think so.. For those that want to have access to old data, if we migrate those to new server, it should be ok.
On Tue, Nov 13, 2012 at 11:55 AM, John Jenkins notifications@github.comwrote:
Can we suggest that people use play.ohmage.org instead of internal? It seems that the two machines have the same purpose.
— Reply to this email directly or view it on GitHubhttps://github.com/cens/ohmageServer/issues/450#issuecomment-10340909.
Sure, and with migrating users... I can make a DNS alias for internal.ohmage.org which will point them to play.ohmage.org. Should be a seemless transfer as long as data can be migrated..
@stevenolen can you update your ohmage-status page to include a blurb about the purpose of each VM?
sure thing!
So are we going with nuking internal and using play going forward?
inelegant..since I'm a massive php novice (if that). But it works! http://www.lecs.cs.ucla.edu/~snolen/ohmage-status.php
@hongsudt is destroying internal (given that the data is migrated to play) ok with you?
:+1:
And @stevenolen you can nuke dev.omh.io. We are working on a developer website that will be officially hosted at developers.openmhealth.org and I will alias it to dev.omh.io.
:boom:
teehee.
@hongsudt did you ever decide whether we could get rid of internal and move to play?
We could but all the data need to be migrated. Do we have time to do this?
On Tue, Nov 27, 2012 at 3:04 PM, Joshua Selsky notifications@github.comwrote:
@hongsudt https://github.com/hongsudt did you ever decide whether we could get rid of internal and move to play?
— Reply to this email directly or view it on GitHubhttps://github.com/cens/ohmageServer/issues/450#issuecomment-10781818.
We can do this as part of the lausd upgrade task. It seems like we should just deploy 2.14 on lausd, play, and internal. Any mobility data and any images will have to be manually upgraded. @jojenki is there anything else that is more of a manual task?
We also need to create the icon images.
play (2.13):
internal (2.12):
pilots.omh.io (2.11):
lausd (2.10):
ptsd.omh.io (2.10):
( 1 ) Consider writing a script to do this.
See cens/ohmageServer#467 for issues experienced by @jeroenooms when upgrading.
play.ohmage.org is upgraded.
internal.ohmage.org is upgraded.
lausd, ptsd, and pilots are done pending the fix #475 .
Can we upgrade internal to 2.13?