These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.
Daniel Delarosa suggested an idea (#3278) · Jan 23, 2018 at 07:18 PM · reservation
Main issue that we are trying to resolve is having prescheduled reservations/resources idle for a long time. Today, we dont get anything in the activity log on whether the users are really using the resources during their reservations since a prescheduled reservation can start and remain idle. Ideally we would like to get a feature OOB where an admin can trigger termination of a reservation if no telnet or any other commands have been input by the user.
Thanks
Maya Ber commented · Jan 25, 2018 at 04:39 AM
Hi @Daniel. Thanks for the ideas :) the topic of idle sandboxes is tricky, since our customers use sandboxes in a very wide variety of ways and for different use cases. Although improving utilization is an important goal for us, it’s hard to define what tells us that a sandbox is idle (not to mention a feature that terminates users’ sandboxes in the middle!). This often depends on what is in the sandbox (network devices, physical servers, VMs in private or public cloud, public cloud services, storage arrays, Traffic generators, Test software, various applications, databases and more), how many elements are in a sandbox, are elements private or shared, what activity the sandbox is used for and other considerations. In your example you mention events like running a command or opening a remote session, but for many of our users not running commands or opening remote sessions doesn’t say much about the usage (e.g. sandboxes that are started by automated processes, or users that use the sandbox in a different way). Other parameters like CPU usage or traffic running somewhere in the sandbox are also problematic (not always relevant, require sampling throughout the day, how often? What to sample? how to aggregate? some of our customers use sandboxes for minutes others for weeks…)
Another way to tackle this is to limit sandbox duration by defining a shorter default duration and allow extending if needed. If users don’t use a sandbox they won’t ask to extend, and you could immediately improve the utilization.
It’s also possible to use reporting, tracking sandbox consumption and providing users/groups with weekly/monthly information about their consumption, to raise their awareness (even if you don’t actually charge them for usage, it changes things when they see the “bill”).
I’m not sure an OOB feature could work here, however if it's important for you to find a way to terminate sandboxes that aren't well utilized, it may be possible to find a way to extend the system with custom work and implement a specific solution that reflects your definition of idle and how to handle idle sandboxes (which is something that our Customer Success can advise on).
Will be happy to hear community member opinions and suggestions on this!
Daniel Delarosa commented · Jan 25, 2018 at 05:26 PM
Hi @Maya.B
I dont understand why this is tricky since we are just asking you to expand the activity logs and use them for something useful. I understand that there are ways to limit the reservations, but in our case, users tend to abuse those privileges, thus this request. As I mentioned before, we do use BI, but we need more than just telling groups about their usage. We are not in the business of raising awareness, we are in the business of cutting costs and saving resources within our company.
Hope it is clear by now, that we are trying to expand the use or your tool within our company but we do need to your help to make it more flexible. Hopefully your product team and roadmap will align to help us achieve our goals. It is good to know that this is a feature that won't be considered though since we now have a reason to look at other tools
Thanks for your time
Alon Saggie commented · Jan 25, 2018 at 07:31 PM
Hi @Daniel,
It was great talking to you today and learn more about your use case.
What you are basically trying to achieve is an automated process to terminate Sandboxes once an idle time is expired. Each group of users will have a different idle time limit.
Your definition for an idle Sandbox is "no resource or Sandbox commands were executed nor application-links operations (e.g. telnet, ssh, RDP, VNC) were used".
The only gap that blocks you from implementing such a script is that application-links are not being registered in the Activity Log today. If we would add such events to the Activity Log you will be then able to develop a script that will utilize the Activity Logs APIs and calculate the Idle Time for each Sandbox, then terminate any Sandbox that exceeded the predefined maximum for the specific group the user belongs to.
I hope this help to clarify the request. Our product team will review this comment and will provide their feedback. Have a good day!
Daniel Delarosa commented · Aug 16, 2018 at 06:49 PM
So there is no hope to get this as an OOB solution and a customized solution is the only way? we are getting asked to figure out the utilization of resources within an testbed for the reasons behind so we need to know ASAP which way, whether is customize, velocity or any other way to accomplish this
thanks
Alon Saggie commented · Aug 17, 2018 at 04:54 PM
Hi Daniel,
The immediate solution would be to have a script that will utilize our Sandbox APIs to monitor the sandbox for activity and take actions based on rules you will define.
I will be happy to have a meeting with you and your team and guide you with the implementation steps.
Feel free to reach out to me at your convenience to schedule this meeting.
Thanks,
Alon
These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.
Help us make things better. Share your great idea or vote for other people's.
Realtime updates to 'Structure' display
Automation trigger at reservation creation time
Improvement to 'Add Sub-Resources' - filter out items already present from the list
Set image/icon per resource (optional)
Improvement to building resources in blueprints
Sandbox API route to add Permitted Users
Limit a user to a number of planned/future reservations
Via API, be able to set start/end time windows where a resource is unavailable