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 >.
Yaniv Kalsky suggested an idea (#4653) · Jun 26, 2019 at 10:37 PM · scriptpackageupdateexecution serverrequirements
When you execute a script for the first time, it will first create the venv and then install the requirements (if there is a requirements.txt file).
For each subsequent run, before the script runs, there is first a phase of checking for some requirements updates (pip install --update).
This step is also a blocking one, so if you have multiple setup/teardown/other scripts from the same type that should run in parallel - they will be waiting for a 'install req' to finish, which in turn causes a delay in the execution of each such script. Especially if it has multiple requirements with multiple dependencies - this process can take anything between 20 seconds to 2 minutes - and it gets multiplied by each script.
This is really not a needed behavior - packages are not being updated that frequently that we'll need to check for new update for every script execution. Once a day/week can be good enough (if there is a known issue in a specific package and you want to get a new version, you can always force it by deleting the venv or updating the script).
This idea is somewhat related to this one, which is mostly for dev purposes, but with the above idea you're covering day-to-day behavior/slowness.
George Rainovic commented · Jul 03, 2019 at 01:59 AM
Hi Yaniv,
I agree with your idea. In my environment, the existing behavior is causing problems. I'd like to be able to disable updates of venvs.
Muli Wienrib commented · Jul 04, 2019 at 09:14 AM
Hi Yaniv,
You raised two interesting points:
1. After a script has been initialized, every call runs a check for updates in the requirements file, regardless of how much subsequent execution are made in a short period,
e.g. the same script in a sandbox
2. Multiple executions of the same script occur sequentially, further increasing the duration.
The related Idea you mention emphasize the need for different users to be able to determine if and how an update/check-update occurs.
We will look into this and update
Please feel free to further add on the matter
George Rainovic commented · Jul 15, 2019 at 12:51 AM
Is it possible to make timeouts shorter?
Execution Servers will wait less time in situations where Local PyPI Server isn't available then make a decision to continue without updating relevant venvs.
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.
Support version.txt file in a script package
Manage blueprint script visibility in domains
Alerting Service for Execution Servers
CloudShell - UI changes for Blueprint Input
shells should come with execution server selector attribute as a default
Send info about the system events to a message broker (e.g. RabbitMQ)
Prompt for updated apps in the blueprint
Configuration Keys page in the Manage dashboard
Ability to exclude and include execution servers and perform other queries using api