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 >.
Yoav Ekshtein suggested an idea (#3430) · Mar 15, 2018 at 10:41 AM · drivershellscripts2g shelldevelopment
while developing a shell driver , after every change a new virtual environment gets created.
that may be a lengthy process (2-4 minutes) that is causing the feedback loop to be much longer , with no real necessity.
I suggest , that a driver or shell under development would be able to be have the virtual environment creation set to manual - and let the developer decide when to create a new environment , saving time in the developing process.
Dan Michlin commented · Mar 18, 2018 at 11:33 AM
Hi Yoav,
I think the pain you are raising here is the fact that it takes a long time to create a new virtual environment and that we are creating a new virtual environment every time you upload a new driver to cloudshell.
Disabling the virtual environment creation isn't a good practice since it's very error prone and may lead to missing dependency or a wrong virtual environment for your driver, so it will appear working or not while it's not actually true to the production environment.
We can look into speeding up the process for spinning up virtual environment or only creating a new one if the driver requirements have changes.
Yoav Ekshtein commented · Mar 19, 2018 at 07:42 AM
Hi Dan,
During the normal life of a shell , the virtual environment creation does not happen that often. but when developing , it happens multiple times, even if no changes were made to the requirements.
creating a new environment on changed requirement should be good enough. if I do change the requirements , I will probably need a new venv anyway.
thanks,
Yoav
Natti Katz commented · Jun 26, 2018 at 11:25 AM
I believe by default, virtual environment creation should remain.
Adding a 'dev' flag to the shellfoundry command to disable automatic venv creation could be useful.
Natti
Kimo Saper commented · Jun 27, 2018 at 05:50 PM
Also if there is a Dev Flag, then the system should automatically take down previous venv, so they aren't just hanging out waiting for a restart.
Natti Katz commented · Sep 05, 2021 at 11:07 AM
@kimo if there is a dev flag, that should mean leave the existing venv alone. Normally a new venv is generated everytime you upload shell as this increments internal "version" counter and server has no way of knowing if requirements changed so it creates new venv. If as a developer you know the version did not change, you pass the "dev=True" flag and you can use the existing venv without a rebuild
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.
Storing Reservation specific information for later use
Having access to old(er) versions of shells/drivers/scripts
Get resource context in initialize command if exists
Need a shell standard for a mobile device (phoe, tables,etc)
provide dev helpers to assist with debugging resource drivers
Shell for Ixia with Autoload Support
Standard Child Component Type: Disk
have a message when virtual environment is being created and when it finishes
Ability to define the saving location of OS Image to disk:0, etc