DO280 Lab Environment reliability

[John_Daisley]

Does anyone have any tips for getting the lab environment working reliably in DO280? Seemingly every time I start the lab it takes 30-40 minutes before I can actually get a lab start script to run without errors. I often end up having to run the sync utility on the utitlity machine which 30 mins plus or rebuild the environment. It's quite frankly a rubbish learning experience as by the time I have the lab working I've wasted most of the time I have available for study. I've raised support tickets but their response is to run the sync utility but it seems a poor solution!

It's really affecting my exam prep and with this exam every minute of practice counts!

[Chetan_Tiwary_]

@John_Daisley The OCP cluster will take time to get its components ready before you can send requests to the API as we are using a Single-Node Openshift (SNO) setup and it take  a while for the VMs and all the OCP containers to startup.

Please do not run any lab start script until the cluster is up. Once it is up and ready - you can start with any lab exercise you want. 

You can set the auto stop timer as per your requirement so that the cluster will not shutdown and you can practice the labs till you want. Also adjust the auto destroy timer as per your need. 

You can start the labs well in advance before you want to sit and start for practising to compensate for the wait time. Remember that if your labs get stopped or destroyed - then is the wait time of approx 30 mins otherwise once the cluster is ready you can continue till it is stopped or destroyed. 

Please be extra cautious in ch03 where you work on authentication, if the cluster auth is messed up - many times it becomes easier to destroy the cluster and recreate ( ofcourse with the wait time ) than to spend hours in resolving/troubleshooting. 

[John_Daisley]

Thanks for the reply but it's not really a workable solution. I study as and when I have breaks from other things in my day and often have only have an hour here and there to dedicate to it. This prohibts starting the environment in advance as I don't know for sure when I will need it! 

Surely there must be a better way of doing this than having customers waiting like this! It completely ruins the learning experience and leads to frustration.

[Chetan_Tiwary_]

@John_Daisley I totally understand your situation, however the cluster wait time is there by design as of now. May be it will be improved in future course releases. I will forward the feedback to the course development team. Thanks for your understanding and patience!

[rhnoname]

Hi, 

I agree with @Chetan_Tiwary_ the first installation usually takes about 30 minutes, but once the OCP cluster has been installed and ready it should get up in 10 minutes or so.

From my experience with this lab, maybe when you edit the auth on 3rd chapter or when you create a custom project template and therefore the apiserver current pod is terminated and the new one starts, it could - in some cases - take more time than expected if you don't cleanup the applied configuration.

I hope it helps