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.
VISIT OUR DIFFERENT FORUMS:
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 >.
Kimo Saper suggested an idea (#3767) · Jun 29, 2018 at 06:18 PM · shelladministrationcloudshellportal
Add to the Manage>Shells section of the CloudShell Portal an admin button that would cause cloudshell to kill and rebuild selected (or all) Shell venv.
In the event of a dependency library update there is no clean or easy way to cause a shell's current venv to be rebuilt.
In addition, in multiple execution server environments, there can be more than on of the venv running, which, if done manually, could lead them to be out of sync.
Last, there should be an option (or automation) to cleanup up old venv. Currently during development, new shell created a new venv. But previous versions persist, which is unnecessary.
Dan Michlin commented · Jul 04, 2018 at 01:00 PM
Hi Kimo, Thanks for the idea, Looking forward for the votes.
Yaniv Kalsky commented · Jul 05, 2018 at 05:18 PM
Regarding the last comment, please note that restarting the execution server cleans the venv folder.
http://help.quali.com/Online%20Help/8.3/Portal/Content/Admn/Cnfgr-Pyth-Env-Cleanup.htm
Yaniv
Kimo Saper commented · Jul 18, 2018 at 09:46 PM
Yes, you can restart said Server (the whole server not just the service) - but I can't administratively trigger that action from CloudShell's portal. And there is also the assumption that the only critical thing running on there is Quali's Execution Server. I may have other services or applications running on that Server, which also happens to be running Quali's Execution Server. If I need to update a vnev because of a backend package push, and I have other things running there, I now have to schedule downtime or otherwise notify about an outage to reboot that machine.
I've ran the configuration tool and that doesn't remove them. Nor does restarting the TestShell Execution Service from the Task Manager.
I also did test the "Restart the host machine" on my Installation (Windows 10) and all the same venv were there after the restart. I've provided feedback directly to help on this point.
I also know the alternative is to go in and kill the specific venv by deleting it - again not an easy administrative task. And that's not what the documentation says to do.
I'll open a ticket on this specifically. But the ability to request from the CloudShell portal to Rebuild that Shell or Script should be an option (and would ensure that the system finds all instances of it)
Kimo Saper commented · Jul 19, 2018 at 05:26 PM
Also, the clean up removes Unused venv. So I have an active shell or script with a venv (currently in inventory per se) but there is a update to a supporting library, then there is no listed method for getting that venv to re-build w/out reloading the item, or deleting the venv.
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.
Gen2 Service Shells need to be able to managed by Categories
Ability to auto-install "Certified Shells"
Domain admins need the ability to create and connect resources in their own domains
Admin level control to create a scheduling Blackout/Service Period
AWS Save Current State of AMI.
Ability to manage Abstract templates between Domains
Vcenter cloud provider: ability to save a deployed VM as OVA file
Email notification for all users or a group of users when Setting up a future maintenance window
Permitted Users on reservations that exceed their current permissions