+++ priyanka Gupta [06/01/15 18:42 +0530]:
Thanks a lot for quick reply.So fresh installation is required , it can not
be upgraded using "ose-upgrade"? thats sad :(
I could easily see us adding logic to OSE 2.x's ose-upgrade tooling to
help assist the migration of applications to 3.x. The 2.x
infrastructure will not be upgraded in place though. In our
experience when changes as large as v3 are involved standing up
parallel infrastructure will provide the highest uptime for
and When enterprise Version 3 will be released ? so that users can try
I'm not yet certain on the timing of when the migration tooling with
be released. Definitely stay tuned to the users list for the public
Beta announcement though.
On Tue, Jan 6, 2015 at 6:17 PM, Brenton Leanhardt <bleanhar redhat com>
+++ priyanka Gupta [06/01/15 15:57 +0530]:
I have worked on Openshift version 2 and have some apps running there.
I saw some blogs which talks about Openshift enterprise Version 3 release.
Now we want to move to V3, but not sure about what changes will it
I know that we can upgrade from previous version to new version using "
Will it be possible to upgrade in this way or re-install will be required?
and will I be able to move my existing running applications from V2 to V3
without any change or what changes it will require to move?
It will be very grateful if some one can answer my question..
I will be waiting for the response...
This is definitely a common question and the short of it is that the
upgrade will require a parallel deployment of OpenShift that
applications will be migrated to. See Clayton's post to the users
Part of the reason for this is that OpenShift Enterprise 3.x will be
based on RHEL 7 and RHEL Atomic (the OS that will run the OpenShift
2.x Node equivalent). Since 2.x is used widely in production we
needed a migration strategy that didn't require systems to be upgraded
in place (that makes rollback really messy).
dev mailing list
dev lists openshift redhat com