Get Ready to Migrate to OpenShift Online 3

Updated August 31, 2017

We have heard your concerns and are working to address them. The end of life for OpenShift Online 2 has been extended to December 31st, 2017 for paying customers. Our OpenShift Online 3 Pro tier offering in EU West (Ireland), mentioned as Pro EMEA (coming soon) on the pricing page, should be available in the October timeframe. Paid users and users with resources in Europe should have received an email today with the details.

Original post

Today we announce the sunset of the previous generation OpenShift Online 2 platform. After September 30th, 2017, all users who did not receive the updated notification will not be able to access Red Hat OpenShift Online 2 (Updated, see above).

The next generation of Red Hat OpenShift Online, a cloud-based container platform that enables developers to build, deploy, host, and scale container-based applications, launched Online Starter in May and Pro in July. Thanks to everyone who has already moved on to our new OpenShift 3 based offerings.

If you’re using the previous generation OpenShift Online 2 platform, you can find step-by-step instructions in our Migration Center to help you easily migrate your applications.

If you still have questions about migrating to OpenShift Online Next Generation, current Silver tier users on our OpenShift v2 platform have the benefit of office hours (check your email associated with your Red Hat accounts) while free/bronze users can send their questions via our help center. More information on the benefits of our next generation platform and getting started can be found App Development with OpenShift Online Guide.

Categories
News, OpenShift Online
Tags
, , ,
  • badera

    Incredible! Do you really talk of end of September 2017? Isn’t it 2018? – You still do not provide every Region in OO3 as you provide with OpenShift Online 2 and you want to shut down OO2? How should it be possible to migrate productive applications with a given deployment process etc. etc. AND TEST them to be reliable in just 4 weeks? You really expect that we can perform a fully technology switch of productive applications just in one month? Without be able to plan this big task a little in advance? This is not respectable.

    • José Zapater

      +1

      • brovienas

        Totally agreed :(

        • Nicolas Blanc

          +1 shame

    • Jacob Lucky

      End of life for OpenShift Online 2 has been extended to December 31st, 2017 for paying customers. Our OpenShift Online 3 Pro tier offering in EU West (Ireland), mentioned as Pro EMEA (coming soon) on the pricing page, should be available in the October timeframe.

      Prior to that time, we recommend users that haven’t already begin familiarizing themselves with the new platform. Kubernetes by Example (http://kubernetesbyexample.com/), our Interactive Learning Portal (https://learn.openshift.com/), our Migration Center (https://www.openshift.com/get-started/migrate.html), and the free OpenShift for Developers eBook (https://www.openshift.com/promotions/for-developers.html) are great places to get started along with our docs (https://docs.openshift.com/).

      • What about the customers using a Bronze plan with free resources only? Will they accounts expire at the end of September? I assume yes (as I didn’t receive the updated announcement), but I’m just asking to be sure.

        • riclf

          EVERYBODY including the Free Plan should be minimally given until Dec 31, 2017. In fact- we all should have been given a YEAR’s notice1

          • I agree. But apparently, we have no strong argument$ here…

        • Shoeb Ahmed

          You can upgrade your plan, I think this can be workaround.

      • DiegoMedeiros

        Hi Jacob. I have a Dokuwiki application on Openshift V2, and I was trying to migrate to Openshift V3, but I don’t find any tutorial about this. I don’t understand anything about kubernetes or JSON, and I’m not able to find how to do this. Can you help me please?

  • Hello,

    • Well, this is really a very short time window to migrate to express it in a temperate way.

    • Since the V3 online was announced, I was hoping for some special migration deal for long time V2 users. The step from three non-idling free custom domain enabled gears to one free idling custom domain disabled project is quite steep indeed. It is literally from to 0 do 50 this time.

    I love OpenShift but this is a somewhat shocking announcement, to be honest.

  • Openshift Alternatives?

    It’s a pity that there is no plan for smaller projects. 50USD per month is fine for businesses but too much for personal projects. Anybody know a decent PaaS (apart from AWS and Heroku) for Tomcat + DB hosting that is less expensive?

    • This is the moment for other PaaS providers to try to take over OpenShift Online customers. Hey there, we’re waiting for your offers! ;)

    • Srccodes Com

      Planning to move to Digital ocean. Pricing seems reasonable to me. Please share if you have already finalized anything. I would like to try the same before i finalize DO.

      • Digital Ocean looks pretty interesting. Currently, I’m evaluating Google Container Engine. If you’re really into Kubernetes, I think it’s worth giving a try.

  • OMG that’s not a sunset, that’s a solar eclipse! One month to migrate enterprise-grade production applications?! Come on Sathish, you’re not serious? I would have expected at least one year! By the way Pro has only been announced publicly in July, not in June… I’m really upset by this way of handling things, why not shut down v2 right away when you’re at it?!

  • Anton Gillert

    Hello,

    this is very… very surprising. We hope that this a mistake and you meant 2018? We are paying Silver Customers and are driving production systems on OS2 now we should migrate in 4 weeks? all theses Systems, with testing migrating databases shifting systems and users? And you think this is a good time to advertise migration to your OS3 platform that doesn’t even provide our Region? If this is really no mistake done by a misplaced keystroke, than I would not count on happy customers moving from OS2 to OS3….

    Again, I hope this is a mistake, since announcing this somewhat relevant information on a Friday is also not well received…

    BR.

  • JoaoReynolds

    Now is as good a time as any to move these projects to Heroku – it will be less work than following those migration guides – have you seen those?

    • James S

      I think I need more qualifications in order to be able to follow the migration guides. Poorly written and clunky wording. Add to that the lack of advance notice for migration.
      Bye bye openshift. Business account moving.

  • Richard Hughes

    Just 4 weeks to migrate a production system… Is that a joke?

  • Christopher Grande

    You must have meant September 30, 2018… 4 weeks, are you kidding?

  • fred

    Is something wrong with your platform ? I don’t like this kind of precipitation from a provider…

  • jawadrashid

    Poor Job Red Hat. I was using Openshift v2 for hosting my own website on free plan. I was aware that v3 was coming with containers and v2 will end and was looking into how to migrate but Openshift just send an email that in 1 month we have to migrate to v3. Very bad. They should have given this deadline earlier. I had been looking for the deadline for few months but it was not announced earlier. Now in 1 month Openshift customers have to migrate. The starter free plan in v3 is a joke. If you try to create a database and wordpress website to go along with it there is not enough storage resources to make wordpress website. This is bad. Basically they want you to choose paid account.

  • Humberto Chamorro Torres

    Dude, you are killing us, the time given is insane.

  • Rick Page

    About a year ago I remember reading that we would be given a sunset plan with ample time. But clearly Openshift v2 and v3 are not meant for production deployments. I wish I understood this two years ago. Well, looks like I can kiss a major client goodbye soon.

    I WAS planning to test against the v2 to make sure the app behaved the same on v3, but I guess I’ll have to put a bunch more risk into the equation and wing it. Now I ask: Why should anyone stay with v3? When a new technology comes along, will we be forced to use v4 within 35 days notice? This stinks out loud.

    This is not a sunset plan this is a rude shove into their new product. People recommend heroku, I may have to revisit them.

    • badera

      >> But clearly Openshift v2 and v3 are not meant for production deployments. <<
      Where do you have such a statement from? Indeed, according their announcement, we could mean it; but according all promotion, it is cleary thought to be usable for production systems…

      • Rick Page

        >>but according all promotion, it is cleary thought to be usable for production systems

        No. I mean I thought it was too, but I was wrong. RedHat OpenShift is clearly not mature or professional enough for me to eat from. Try to migrate your production app. Oh you don’t know what I’m talking about? Then RedHat’s perfect for you.

  • Anderson Luís Furlan

    That is a desrespect with your clients. Only a month? I think to buy a license to move my application to a professional level, but with that announcement the only thing I want to do is to move my application to the heroku services.

  • Hatta Wong

    This is very short notice. I talked to my team and we decided to move to Google Cloud Platform.

  • Joker

    I would be okay with the concept if US East or US West v3 starter were ready for primetime, but they’re not. Absolutely nothing but failed deployments for me. I shouldn’t have to submit a ticket to get a pod up and running when I was just picking and choosing from the web interface. Don’t sunset 2 (Free) until 3 (Starter) is rock solid.

  • Radim Pavlíček

    50$ is too much for a personal project. I won’t be able to migrate in 1 month, so guess what. The app with 150 users will shut down.

  • Robin Williams

    Just as is the case with everybody else who has commented here, my initial reaction was deep shock at the suggested timescales for shutting down OO2 – more on that in a bit …

    However on a positive note, I have found OO2 to be on the whole very reliable and I think the work you have done on OO3 is excellent and it is in my opinion almost, but not quite, ready for production as there are still some technical issues to be ironed out (one of which is the 3+ minute delay after a deployment before a pod is accessible via a route).

    But back to the timescales. Preparing our application for OO3 has taken several weeks – getting to know and understand the new architecture and online software (which only a few days ago had a significant update with quite a few changes) and us having to make quite a few software changes to handle the new architectures (particularly for backing up databases and logs – as the mechanisms we used on OO2 would no longer work). Then there is setting up our application in the new [starter] environment, getting it to work, testing and documenting the installation processes, deployment processes as well as rigorous functional testing. After that there is load testing and tuning (please note metrics are not currently available, so we cannot yet proceed with tuning and capacity planning). After that we need to plan our hosting environment (what resources are required etc) – for development, test and production and put in place appropriate processes. And then we need to put together a migration plan and test that thoroughly before we can contemplate migrating over to OO3.

    I feel very positive about OO3 and am looking forward to moving our applications to it, but bear in mind we are working with live production systems and have responsibilities to our users. So we want to make the migration process as smooth as possible for them as well as for us. I would like our growing business to remain an enthusiastic OpenShift Online customer and hope that you will be able to keep us (your users) happy so we can keep our users happy and so that this can be a win situation all round.

    So in ideal circumstances, I would have expected at least 12 months notice before shutting down OO2, but 6 would probably be OK – and even until the end of the year would be better than the end of September, which is just not viable.

    I do hope you will take note of all the comments in this blog and re-evaluate the previously announced sunset date for OO2. Thank you.

    • Rick Page

      You’re so polite. I also loved the OO2 platform but it seems the people in charge don’t expect us to use openshift for production deployments at all. “I would like our growing business to remain an enthusiastic OpenShift Online customer and hope that you will be able to keep us (your users) happy so we can keep our users happy and so that this can be a win situation all round.” I hope for your sake you drop v3, just remember you may have to do those weeks of work all over again come v4, and in 30 days notice no less. It sounds to me like you realize there is an inherent risk to your paying customers if you stick with openshift as a company.

      Also, may I use some of this text in my correspondence with Redhat?

      • Robin Williams

        sure

  • Rick Page

    Also, v3 is garbage so far. Cannot even run their own examples in the migration guide. Terrible. All sorts of errors and no direction on how to troubleshoot.

  • J. L. Freimam

    Version 3 of the Openshift sucks!

    • Rick Page

      +1

  • Bobby Bailey

    I’m shocked as well. As others have stated, I have been keeping my eye out for word on this transition. I was expecting a 6-12 month transition window. I currently have 500+ students using my software and making this switch in the middle of the fall term is a serious hardship and a risk to my business.

  • Anton Gillert

    Just for you guys here,
    since we are Professional Level Customer we got a fast response when asking Red Hat support to clarify this deadline. They confirmed the deadline, but could not tell us anything about availability of EU West Region (as of now).

    So that’s a lesson learned, putting your services into the public cloud… I’d expect this behaviour from some startup or small company shutting down business altogether. But the name Red Hat lured us into thinking of professional customer care.

  • I am (was?) a happy OO2 user since some time. I’m using the bronze plan with free resources, so maybe I shouldn’t complain, but the time you gave to switch to the new platform is just too short.

    I’m in a relatively comfortable situation just now, as we’ve already dockerized our application, so now we’re ready and able to migrate.

    But we’re going to migrate OUT of Openshift, because we’re not going to take a risk of upgrading to another new version (if any) in the future in such a hurry. Containerizing the app, resolving the issues, rewriting some of its parts, testing and putting everything together can be a considerable effort, even for a small scale app.

    What’s more, the transition process is not instant and should be reversible, so if any serious problem arise, you can just switch back DNS records to the old app, resolve the issues and try again.
    Now, the old app is going to be shut down in a month, so there’s no way to go back. The fact is, the migration should be already done and the old apps should be still up and running as a standby in case there’s a need for failover.

    So to sum up, we’re going to move out of OpenShift as soon as possible, just to mitigate the risks I’ve mentioned.

    • Rick Page

      Thank you for putting this so well. May I use some of this text while I correspond with RedHat?

  • OS3 is a drag – tested it in spring 2017 I was really disappointed. Sad to myself – another HEROKU.

  • Sean Smith

    RH you should seriously consider extending this period as everyone says one month notice is taking a dump on your customers. I will migrate away from OS completely and never return if this is how you treat your customers no matter what tier.

  • villarrealized

    Wow.

  • villarrealized

    Our company was also shocked to hear of such a short timeframe for migration and as I delved into trying to figure it all out, I realized there were a lot of unknowns and in my estimation, lacking documentation. I think I have finally figured out a successful migration process for our production apps. I know for many this announcement and deadline is really bad news. I have attempted to document the process we are using to migrate our apps which consist of Node.js or Node.js + MongoDB. I am sharing a DropBox link to the document I have created with you all. Some of it is specific to our use case and may not apply to you, but I think many of you might be able to benefit from some of what I have put together and hopefully along with the official migration guides it will help you to put all the bits and pieces back together as you migrate to OpenShift 3.

    Cheers and happy migrating!

    Put this text after the DropBox host name in your browser, I cannot paste the full url or it will be flagged and not accepted.

    /s/kmngcd1cdiacl3g/OpenShift-V2-V3-Migration.odt?dl=0

  • Srccodes Com

    Big joke :)

  • Spencer Loveridge

    I think at the very least as a professional company you should have the common courtesy to respond to your users on this thread. It’s pretty poor form that you make the announcement in a blog entry and don’t have the decency to individually email each of your users. What will happen to the V2 users who may not have read this post yet?

    Can you explain:

    – What has changed in your circumstances to mandate a very sudden sunset of V2?
    – Why have you seemingly not contemplated the very short amount of time you are giving your users to migrate?
    – Will this happen again with V3?

    As we are all paying customers then this is incredibly bad service on your behalf and I would suggest you redeem yourselves by responding to these comments before people start to migrate to your competitors in their droves.

    • Grant Shipley

      See the comment from Sathish above where it has been extended for paying customers and people with resources in EU.

      I agree that migrating anything at anytime is a pain. I do think you will find that it is easier than what most people think though. The reason I say this is because v2 used git for everything and v3 uses git for source code / builds as well. The only real challenge would be exporting any databases and then importing them which would require a few minutes of downtime. For mysql, you would use mysqldump or postgres / pgdump.

      I completely understand that moving is a pain. However, I am very proud of the fact that we have been able to offer such an awesome system for many years that is completely free to use. We only asked for an email address and password to sign up. I am also extremely proud that with the complete rewrite to use docker and kubernetes that we are once again able to offer the service completely free to users. We value you folks. We have done a lot of work to be able to keep a free version available for the millions of applications that use it. It certainly isn’t free for us as we have thousands and thousands of nodes to run the applications on but feel having a completely free and open source platform available to developers is a game changer for innovation. OpenShift has essentially removed the platform bottleneck away from developers to allow them quickly spin up and try out new things while also giving them a solid platform that can also be used for production. We did this while being completely open and free. We didn’t force any ads on you or any such nonsense.

      Over the last 2-3 years we have spent a tremendous number of engineering hours making the platform even better by using docker based containers and kubernetes orchestration. In fact, we are the 2nd largest contributor to both of those projects outside of docker inc and google. This was all done in order to get a public cloud offering to our users that would still allow free usage. We have seen the number of users deploying applications to the new platform explode at a tremendous rate and it is in use at some of the largest companies in the world for mission critical production workloads.

      We really hope you folks enjoy using the new platform. And please keep in mind that we are not taking anything away here. We are offering you a new platform that is better, uses defacto standard based containers and orchestration all while keeping it free.

      • griz

        Appreciate what you have written here, and that you have tried to keep a free offering.

        As someone who has only used the freebies so far, I have found the OS2 very generous in terms of resources and the freedom to tinker. I also understand that not having contributed I am worth less than paying customers. Whilst it still feels a bit of a slap to see paid thrown a lifeline that free does not, it’s business.

        Since you stress the free offering in your post, though, the feedback I’d like to leave you is that the new starter tier is hamstrung in ways OS2 was not. OS2 was very generous and I can understand that changing, but OS3 starter is clearly a dev playground with limits that make it unsuitable for much else. The issue is that the financial jump from the OS3 starter to pro is far too big and there should surely be a tier between because going from $0 to $50 a month is just too much.

        I appreciate the service you’ve offered in the past, and your genuine attempts to keep things going, but when you offer 2 choices both unsuitable in their own ways… I will be reluctantly taking the 3rd choice and migrating my projects away.

        • Yes this is something os has to address immediately.. a plan which cost 10 to 20$

  • Sathish Balakrishnan

    We have heard your concerns and working to address them. Paid users and users with resources in Europe will receive an email tomorrow with updated details.

    • Robin Williams

      What about other v2 users who are working hard to migrate to v3 Pro but need more time?

  • winston

    I was not the only one who think 1 month notification is insane. I hope “2017” is typo, it must be “2018”. This is insane

  • Ashish Sukhija

    It shouldn’t be PAAS, It should be PAT- Platform for Testing. I happily switched off. I can’t trust the V3 to be scrapped in a month again some day in near future

  • Witold Samirov

    Please let us know from now, how much we will have time for migration from V3 to V4 ?! Maybe only 1 day !

    Sorry, I’ve tested V3, and it’ really not appealing:

    • Too complicated

    • Resource hunger
    • No complete guide
    • Even very less blog posts in other places (maybe others do not like it?)
    • No project in GitHub
    • DIY seems to be dead

  • Mario Montero

    I have a java system for a non profit organization and we were using the free option with no issues. After seeing this post we decided to invest on a hosting service since the application has added value to the Org. However we discarded to move to V3. We just switched to daily razor, the prices are not high and you don’t need to deal with this short notice changes. Farewell Openshift, you got another user out of your platform.

  • Anderson Luís Furlan

    Please guys extented until 31 October at least for free users! One month more! It is so little time to a big change for us.

  • Farid Kalaidji

    Big joke, I need to rewrite my source codes for applications within such short time. Even tho I have application and/or carts compiled from sources @Github I have a shitload on work to accomplish till the end of 2017, re-test, re-write. Bye projects, bye customer (me). I’d rather see RedHat extending this until somewhere next year, as I am a paying customer. And for the people blaming us wrongly using OpenShift v2 as a PROD platform: yet it was intended to use this way. Also hope migration will be easier the next few months. Not eager to pay, as I always loved OpenShift but seriously looking into migrating to Google, Digital Ocean or Heroku.

  • Farid Kalaidji

    Big joke, I need get rid of OpenShift V2 within such short time. Even tho I have application and/or carts compiled from/at external sources I have a shitload on work to accomplish till the end of 2017, re-write, re-configure and re-test. I’d rather see RedHat extending this until somewhere next year, as I am a paying customer. And for the people blaming us wrongly using OpenShift V2 as a PROD platform: yet it was intended to use this way. Also hope migration will be easier the next few months. Not eager to pay, as I always loved OpenShift V2 but seriously looking into migrating to Google, Digital Ocean or Heroku, don’t like the OpenShift V3 platform at all.

  • Shoeb Ahmed

    OpenShift v 2 was a charm, easy to use and configure. I have started migration to Azure and will be using Linux VM. I have production system running on OpenShift and found it to be stable and used for more than a year. If anyone needs any assistance to migrate Java Application running on wildfly, I can help you out.

  • I knew this was coming from a long time, so I was porting my website to use a static site generator from the last few weeks.

    No more hosting issues, databases and dependency on one platform such as wordpress – I just need to throw-in html files on to any hosting service and voila my site is up again in a matter of minutes!

    Luckily, it appears I will finish my migration before Sep 31st. So, this is in a way a good-bye post! It was good while it lasted. Thank you OpenShift, I am definitely not going to pay $50 per month for hosting that isn’t even tested properly!

  • Kat Katolinko

    4 weeks are not good! Also your migration tutorials are a joke. Why are you doing this? :(

  • Coração Tricolor

    Why not extend the end of life for OpenShift Online 2 to A L L customers?!?!?

  • Faucetlist Faucets

    Hi, first off, I am also shocked about how little time has been given for a fairly major transition. If this is how Red Hat operates I’m very concerned.

    I would like a clear answer to one particular question. We are currently on the bronze (free) plan openshift online v2. If we sign up today for a silver (paid) plan will the extended 12/31/17 deadline apply to us?

    My developers have stated they need more time to adequately test the app’s performance in V3. The 9/30/17 deadline is much too soon.

  • Nicolas Blanc

    Please guys extented until 31 October at least for free users! Thanks

  • Justin Hall

    OpenShift — this is an insane timeline to move to a not-yet-ready product. I’ll be migrating OFF your platform totally unless you can extend the EOL date for all customers. One month to move systems! Crazy. I won’t continue to do business or have any part of a company that thinks that is realistic. PLEASE go back to the drawing board and come back with real dates.

  • Giuseppe Sarno

    Migration Completed…towards AWS!

  • Found very difficult to do migrate to V3, spend countless hours .. but V2 was very lovable :(

    Finally i am moving to Azure Bye Bye Open shift .. thanks for your help