Background:
We have staging environments for customers to test their configurations before making those changes in the production environment. We do have ISM staging environments in NA and Europe regions like we have production environments.
Staging environments are currently available like production environments 24x7. However, these environments are being used only by those customers who want to test their changes if they have any. As such, we see that these environments are sparingly used but are up and running all the time. It’s not an optimal use of these environments from a cost perspective.
To optimize the cost, we would like to make some changes as detailed below:
Proposed Change:
When there are no users accessing staging environment for the past 30 minutes, then the system will go offline automatically. If a user is trying to access the staging environment that’s offline, he will be directed to follow the instructions to bring up the system. It takes approximately 2 to 5 minutes before the system comes online for the user to access the staging environment.
Which are the environments that will be impacted with the change?
NA Staging, Europe Staging environments of ISM and Luma.
Trial Environments of ISM and Luma will be considered later.
Why this change?
To optimize the infrastructure costs that we incur in staging/trial environments.
What’s the impact on the customer?
When the system is idle for 30 min, it will go offline. During that time, if a user tries to access staging environment, he will have to follow the instructions to bring up his instance. Probably he will have to wait for 2 to 5 minutes (max) to access the staging environment.
Who can bring up the system that’s offline?
Users who have accounts in their current staging environment can bring up the environment that’s in offline. Those who don’t have access to our staging are obviously can’t bring up this system.
Other things to be noted:
Pl note we will monitor only application access to identify if the system is idle.
We don’t expect a customer to run some tests behind the scene using Rest APIs on our staging environment. Of course, they can test their integrations when the system is up. But customers can’t assume the systems will be up and running 24x7.
We also plan to archive any attachments that they have that are older than 30 days in staging environment. This is to keep the system lean so that it can be brought up quickly.
Screenshots
When a user tries to access the staging environment that’s offline, he will be directed to the below flow to spin the environment up:
After clicking the above link, user will be prompted:
Once the environment is up, the user will be automatically redirected to that ISM/ Luma web page.
Add Comment