[Eagle-i-admins] patch

[Ciriello, Marc]

Hi All:

The word "patch" might be causing some confusion, so let's set it aside
and just talk versions. The goal is to get all of the nodes onto 3.0.4

Depending on what version of the software you are on, you might have a
1-step or a 2-step upgrade process for the repository only. Other
applications can be upgraded in one step, from whatever version you are
on, to 3.0.4. Read on, however, for some important detail.

First, check to see what version of the ontology and software (application
version) you are on - you can check the footer of your SWEET login page
for this information if you can't find it elsewhere.

If you have an ontology version OLDER than 1.8.3.1 (regardless of software
version), please contact me so we can get you back up to speed offline.

For the rest of you, let's look at the application version and see what
steps you need to take to upgrade your repository.

Nodes runningŠ
2.0 MS 2.14
2.0 MS 2.15
2.0 MS 2.16, all originally packaged with ontology version 1.8.3.1 have a
2-step repository upgrade. They shouldŠ
Šupgrade to 2.0 MS3.07 (comes packaged with ontology version 1.8.4), thenŠ
Šupgrade to 3.0.4 (comes packaged with ontology version 1.9.3)
Summary: 2.0 MS 2.1X --> 2.0 MS 3.07 --> 3.0.4

Nodes runningŠ
2.0 MS 3.07, originally packaged with ontology version 1.8.4 have a 1-step
repository upgrade. They shouldŠ
Šupgrade to 3.0.4 (comes packaged with ontology version 1.9.3)
Summary: 2.0 MS 3.07 --> 3.0.4

Note that you need to check for configuration changes in versions you are
skipping - those are not made for you automatically in the upgrade process.

Remember, this is only for the REPOSITORY. All other applications can be
upgraded in one step.

Why (maybe) 2 steps? Data migration. The repository upgrade process also
makes necessary adjustments to your data to keep it compliant with the
latest ontology. Data migration happens at the time of repository upgrade
and is not cumulative, so you might need to take a little more care to
keep your data in good shape and ease it through 2 sequential data
migrations via repository upgrade process.

I hope this helps - please let us know if you encounter any problems.

Marc




On 7/18/14 7:32 PM, "Cherry, Michael" <Michael_Cherry at hms.harvard.edu>
wrote:

>
>> ... Sophia and I were in private conversations. They were
>> unrelated to her public statements on Eagle-i-admin.
>
>Ah good - light is beginning to break.  :-)
>
>So back to my question #2 - what version are you on right now?  (That
>should let me figure out what you need to patch to, so I can point you to
>where to get it.)
>
>Also, if you want to forward me her message(s) to you (off-list please)
>that might get us there sooner.
>
>regards,
>- Mike C
>
>_______________________________________________
>Eagle-i-admins mailing list
>Eagle-i-admins at open.med.harvard.edu
>https://open.med.harvard.edu/mailman/listinfo/eagle-i-admins