Lab Environment usage calculation

Latest response

Hello

when using red hat online learning environment they said that allowed number of hours in the cloud is 400 . so my question is it should delete the lab after i finish my testing so no count or just shutdown the lab every time i use the course ?

thanks

Responses

also my other point is calculation based on every server running on the same LAB or in overall Lab ?

I believe it is calculated against the whole lab setup, not individual VMS. however, it would be nice to have a live counter on the course page, i am using also my laptop to simulate the environment not to waste the hours. as i get distracted and two hours went without any command typed. latency also is not helping. would love to hear an official response.

The runtime of the lab environments is consumed when any or all of the machines are in a state other than STOPPED. When you have a machine in the group turned on (even if it's a single machine out of several in the group) the lab runtime is being consumed.

If the lab environment is provisioned, but the machines in it are in the STOPPED state, the environment is not counted towards the 400 hour runtime limit.

I think the key thing to focus on is 'runtime' if machines are running, it's being logged against the 400 hour limit, if all machines are not running, it's not consuming any runtime.

We're working on exposing the usage of labs in the UI. I'd like to get these landed in the next couple of weeks, however, our UI developer is going out on leave for most of June. That means that if we miss landing this in the next couple of weeks, it'll have to wait until he returns.

-Scott

The lab usage counter is not yet on the UI.....any idea when we will have this?

Thanks for clarification, I appreciate all of you helping to understand these point

I am waiting for it too, my yearly subscription is nearly ending, would like to see how many hours I did, also I am going to renew, would like to know if I still have hours, would that be rolled to my new subscription?

That is a nice topic you just raised Walid......will it be possible to roll over the 2 second shot exams to a renew subscription or it goes away with the expired subscription? even though you renew before the last one expired....I will like to know this

Oh! I did not think about the retry exams, ha! so in general why one would renew as soon as possible before the subscription expires, what would he/she gain?

I would like to think that, as a user, you wouldn't want your access to lapse. Expired users aren't active users, so their accounts and data are treated differently.

I think we publish new and updated courses pretty frequently, and we're working on a feature to provide access to even newer and more frequent content updates as well. I've just started the planning stages of this, and am working on the product and content work-flow now and expect development work to start in a couple of weeks.

-Scott

Any unused subscription resources do not 'roll-over' upon renewal. However, with a renewal, you get a fresh allotment of lab time as well as exams and retakes (exams and retakes are included in the Standard-level subscription only).

-Scott

I would also like to know when the 'total usage' will be in the UI. Having no time monitor is painful. Not knowing how much time you used and have. I think having the time/usage monitor would give us more chance to focus on the topics rather than the usage of lab time. Not complaining about 400 hours lab though, it's a decent amount of hours you get. But we should really have a usage monitor of some sort.

At this point, the UI element is written, but turned off. After doing the work, we realized that some of you were over the 400 hour limit. As there is no UI item for you to recognize this, nor really know what your usage is, I decided it was incumbent upon Red Hat to contact all those users and make any appropriate one-time adjustments needed prior to throwing the switch on 400 hour enforcement. We've been working on some other stuff, and I've been finding it difficult to make the time to perform this task.

However, if you all think I should, I could just throw the switch and let the cards fall where they may, I could do that as well. Anyone over 400 hours would have their lab machine interface become non-responsive.

I figured my way was a bit nicer and would provide subscribers with a better experience that simply having a numeric meter appear and your labs potentially stop working...

-Scott

I'm confused. when you said over 400 hours, does that mean we can actually exceed the 400 hours limitation and lab will still run?

Your idea sure was nicer. I thought it would just be a time count. If your answer is yes to the question above, I guess the functionality of that option would cause some problems for existing users. Now it became a 50-50 choice. shoot! this is confusing.

Moztaba,

We have always tracked lab usage,and the product description does explicitly state that 400 lab hours is the limit with the product. However, without an element that allowed users to see and manage their own usage, Red Hat did not enforce the 400 hour limit. This policy is going to change very, very shortly as we now have a UI element available. When we were getting ready to release it and add it to the UI, we noticed that some of our user population was already over the 400 hour limit. This means that if we simply turned on the limit, for these users (who previously had no idea that they were at or over the limit) their labs would cease to function. That's not the type of user experience, I, or others at Red Hat, want to provide.

After talking with the business managers in the various geographies and the world-wide managers, it was decided that prior to enabling the limit, we would contact each of the affected users to reconcile their usage. Once this was complete, we would expose the lab usage UI element as well as enforce the lab consumption limit stated in the product.

Now you're waiting for me to complete this audit of our user community and contact those affected, once that is done, we'll expose the UI element and enforce the 400 hour limit.

-Scott

Thanks for the brief explanation, Scott. I guess good things will come soon :). I'm just being sooo cheap on lab timing haha. Good thing we didn't had any restrictions on how many time we can launch and close the labs. Like, for a certain amount of time we HAVE to keep the lab open and we won't be able to close it. That would be bad. But right now it's good.

Thank you, Scott, it has been a good journey so far, and I love how you guys are progressing. looking forward to knowing what was my usage.

You all should now be able to see your lab consumption in the "Reports" information on Red Hat Learning Subscription Basic.

Red Hat Learning Subscription Standard runs on a different platform and we're working to integrate the report data there as well. It is on my list of work in the near future to complete my lab usage audit and enable our already developed UI elements to help with tracking this as well. As that happens, I'll update this thread as well.

-Scott

Great, Looking forward to it!

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.